Help for owners
Customers reach my checkout but do not pay, and I think something is broken
Short answer
Some abandonment is normal, but a sudden drop or a gap between 'started checkout' and 'paid' usually has a technical cause: card declines, blocked payments, a form that rejects valid input, a page that fails on phones, or a slow step. Test the whole checkout yourself on a phone, then compare against your payment provider's decline records.
Does this sound like your situation?
- Many people add to the cart or start checkout, but far fewer finish.
- Customers email to say the card was declined, although the card works elsewhere.
- The checkout works for me on my laptop, but sales from phones are low.
- Sales dropped after a site update, a plugin change or a new payment option.
- I see no errors anywhere, so I cannot tell what is going wrong.
Why does this happen?
Payments fail for reasons you can read
Stripe lists three reasons a payment fails: the card issuer declines it, the provider's fraud tool blocks it, or the website sends an invalid request. Each shows up in the dashboard with a reason. Blocked payments are stopped before the bank is asked, and a rule you set yourself can block a good customer.
Confirmed by docs.stripe.com
The payment form fights the browser
Web.dev's guidance on payment forms says card fields should use the right autocomplete values and a numeric keyboard on mobile, and should avoid the number input type. A form that blocks spaces in a card number, rejects a three or four digit security code or breaks autofill makes honest customers fail.
Confirmed by web.dev
Validation rules reject real card types
The same guidance says to test every card type you support, because brands use different number and security code formats. A rule written for one brand quietly rejects the others.
Confirmed by web.dev
A step in the flow is slow or breaks on phones
Heavy scripts, a shipping lookup that times out, a coupon box that reloads the page or a button that sits under the keyboard can stop a customer without any message. These rarely show up when you test on a fast desktop.
Nobody is watching the failures
If failed payments, form errors and script errors are not recorded anywhere, a broken checkout looks exactly like customers changing their minds.
What can I do about it today?
- Run the whole checkout yourself on a phoneUse a real phone on mobile data, not your office wifi. Go from a product page to the final confirmation, with every payment option you offer. Write down every step that feels slow or confusing.
- Look at the declines in your payment dashboardOpen the list of failed and blocked payments. Note the reasons, and whether they cluster on one card type, one country or one date.
- Find the date the drop beganCompare it with the dates of site updates, plugin updates, price changes and new shipping or tax rules. A sharp start date points at a change.
- Ask three recent abandonersA short, polite email to people who started but did not pay ('Did something go wrong?') often names the problem in one reply.
- Do not switch off fraud protectionBlocking is annoying when it hits a good customer, but turning it off can invite fraud and disputes. Review individual blocked payments instead.
- Do not change the checkout while you investigateKeep notes first. Changing several things at once makes it impossible to know what helped.
When should I bring someone in?
- Payments are failing with errors that you cannot explain from the dashboard.
- The problem began after an update and the previous version cannot easily be restored.
- You want the checkout measured step by step but have no analytics set up.
How do I handle it?
- Walk the checkout like a customerI test it on real phones and desktop browsers, with several card types and failure cases, and record where it breaks or slows.
- Separate bank declines from my own faultsI read the provider's decline reasons and the server logs side by side, so that issuer declines are not confused with invalid requests from the site.
- Measure each stepI add event tracking from cart to confirmation, so the drop-off point is a number, not a guess.
- Fix one thing at a timeEach change is released alone, after a backup, with a tested way back, and the next days of data show whether it helped.
- Set up alerts for the futureA spike in failed payments or errors sends a message to you, so a broken checkout is found in hours rather than weeks.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
How do I know what a normal abandonment rate is?
I do not quote a figure, because it varies by product, price and traffic. A sudden change in your own numbers, or a big gap on one device or card type, is the useful signal.
Could it be the price or shipping cost rather than a fault?
Yes. That is why I check declines, errors and device differences first. If nothing technical shows, the cause is probably in the offer, not the code.
Will I lose sales while you investigate?
Investigating is read-only. Changes are made one at a time after a backup, so the checkout stays live.
Do I need new analytics?
Often a few events are enough: cart, payment form shown, payment attempted, payment paid, and error. I add only what answers the question.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.