Failed orders should include more info on transaction details page

[aheckler]

If an order fails for some reason, say insufficient funds, there's a lack of information about that on the transaction details page. Here's an example screenshot:

You can see there that this order, although it failed, has two bits of info present:

• An order number
• A failure/decline reason

Here's the corresponding transaction page under Payments > Transactions:

Not only is the order number missing, but the decline reason is nowhere to be seen.

In the interest of giving our merchants as much info as we can, IMHO we should include this in the transaction detail page.

This idea stems from this post: paJDYF-7eg-p2

[jessy-p]

This issue impacts Transactions (Auth and Capture), so assigning to Pulsar (based on team responsibilities Pc2DNy-3z-p2) @kalessil. Assigning as part of Gamma Triage process PcreKM-yM-p2.

Tagging as part of re-evaluating older issues in the backlog, please have a look and close if no longer relevant.

[kalessil]

@mgascam : please re-evaluate.

[mgascam]

Hi @aheckler, I know some time has passed since you reported this issue, but I was wondering if you could share the steps to reproduce a failed order like the one you described. I'm struggling to recreate it on my end.

For example, when I use a test card that fails due to insufficient funds, I can't get past the checkout step. The order transitions to the "Failed" status, but no payment intent is created on Stripe's end, so I can't access the payment details view.

For context, I'm working on a branch that addresses this issue. It includes unit tests, but I’d like to add testing instructions to verify this flow manually. Unfortunately, I haven’t been able to find a way to trigger it yet, which is why I’m reaching out.

Thanks in advance for your help!

[aheckler]

@mgascam I tried a couple different ways but I don't see how to replicate that either. :/ @AashikP or @francoishvz may know of a way?

[AashikP]

I could not replicate this in test mode

[AashikP]

I've seen a conflict in most cases where the order number is not linked. I just realized we also have this latest example for WooPay: p1734327561455129-slack-C7U3Y3VMY

cc @nicdwilson @reykjalin

[mgascam]

Thanks for attempting to reproduce the issue, @aheckler and @AashikP. Other folks in Gamma also couldn't reproduce it. Since this issue was reported quite some time ago, it's possible that the flow has changed, making it harder to replicate, or it could be related to testing mode.

Regardless, we are now including the failure reason in the timeline after this PR is merged. This will show the failure reason provided by Stripe, which was previously missing. I expect this change will help clarify why transactions fail.

Regarding the order, I didn’t include any changes because we already include it—as long as the order metadata is linked to the payment intent in Stripe, regardless of whether the payment intent fails or not.