We are experiencing silent checkout failures that we cannot explain.
This issue is a place to discuss and explore... as we don't have a huge amount of information yet.
We know that many card errors from Stripe are not creating error messages visible to the users.
We also suspect that there might be a rare race condition when someone checks out with a sold out item in the cart. This is unconfirmed so probably outside the scope of this specific issue, but something to bear in mind when reporting such things.
If checkout fails the user should be notified and this should be recorded in Bugsnag
There are times when the checkout fails silently.
This section was added by @luisramos0
One example we can reproduce (although not exactly a bug because the user is shown an error message next to the card number).

There is a way to see the error message in this case:
Same as above but on step 6, instead of watching, click anywhere on the page while the "processing payment..." is there and see the flash error being displayed.
bug-s2: a non-critical feature is broken, no workaround
Related PRs in progress: #5076, #5060
Related issues / discussions: #5003
Another report of a silent failed checkout with a card user in the UK.
@luisramos0 You are spot on with the steps to reproduce. From a user:
_I now realise I had reversed some numbers in my credit card number - oops. It is worth knowing that there was nothing coming up on the page to alert me of an error, and it said "Processing my payment" so I thought all was in order. It was only when I attempted it for a third time that I realised what I had done._
Can we make this S2 about relaying all error messages from Stripe?
I am going to try to fix this between now and tomorrow morning.
I think I might have a report of this in Aus with perhaps a couple of twists / new information. Putting here rather than creating a new issue but can separate if people think it's differetn
New user - Flock Stock & Basil have set up a shop. They had first oc today and took 4 orders - but had two other 'orders' from excited friends testing that never showed up. Not in orders or with email confirmations etc.
The twist - cash / direct debit payment method - no stripe involved
When I go to look at their 'incomplete' orders I can see a couple from logged in users - or at least that have user email, so I think that means that they've made it to checkout. They also say 'Balance Due' which suggests that the payment method might have been recorded? and this one also has Address marked in red (suggesting problem?)

But when I try to open up this order to have a closer look I get a snail. same on any other incomplete orders
info in dev tools means nothing to me

I am seeking more info from these two failed customers about what happened, but they really thought they had ordered. This is scary - I see people turning up at farmers markets being mad mad mad . .
might the PR you have done @Matt-Yorkley also make sense re. the case I've described above?
The scope of this issue is very specific Kirsten, and PR #5076 will fix it.
In some cases, like rejected cards from stripe, users are not seeing the error message and they are left in the checkout page. They can retry. Some confused users may think that the order was placed.
I dont think your problem is this one because your error is a server side one (I know this because the order is left in the address state).
BUT PR #5076 will also add an user error message to further server side errors on checkout. I think the one you describe can be one of these, after #5076 the user will get to see an error message.
Also, I think there will be bugsnag errors (server side ones) for both the user checkout and your order edit errors. We need to look for them.
I cannot find a bugsnag error for the checkout, which confirms my theory that PR #5076 will fix the problem: I mean the part of showing the error message to the user. Maybe it is something the user can fix on the checkout form. But maybe it is not so I am adding a bugsnag error for these situationss as well as part of #5076
I found the server side one:
https://app.bugsnag.com/yaycode/openfoodnetwork/errors/5e7c2499183e6e0018839df6?filters[event.since][0][type]=eq&filters[event.since][0][value]=30d&filters[error.status][0][type]=eq&filters[error.status][0][value]=open
This order has no shipment because the order (and the user itself) have no bill_address or ship_address. I dont know how that was possible as the fields are mandatory on the checkout form. This needs a separate issue.
Summary:
new issue for the customer case I described above - vague because I can't replicate - S3 until we find it's happening a lot https://github.com/openfoodfoundation/openfoodnetwork/issues/5126