Payments Declined or Not Going Through at Checkout
Customers reach checkout but their payment fails, errors out, or never completes — and the pattern of failures tells you whether it's your setup, the processor, or the cards.
Common signs of this issue
- Customers report cards declined or an error at the payment step — while the same cards work elsewhere.
- Orders start but sit in 'pending' or 'failed' status, never reaching paid.
- Your own test purchase fails with a gateway error message.
- It began after a plugin, theme, or payment-setting change — or after the gateway emailed about an account or API update nobody read.
- Only certain payments fail: one card brand, one country, only large amounts, or only some days.
Safe checks you can do yourself
None of these require sharing passwords with anyone.
- Establish the pattern first, because it points at the culprit: ALL payments failing → your configuration or account (keys, mode, SSL, a gateway suspension). SOME failing → issuer declines or fraud rules. Failures started on a date → whatever changed that date.
- Open your payment gateway dashboard (Stripe, PayPal, Square…) and read the declined transactions' reason codes — gateways record why each payment failed ("card_declined," "authentication_required," "invalid API key," "account under review"). This list is the diagnosis; most of this guide is just getting you to read it.
- While there, check for account notices: gateways suspend or restrict accounts (verification requests, disputed charges, policy reviews) and the only symptom on your site is that everything declines.
- Confirm the gateway is in live mode, not test mode — the classic launch-day error — and that API keys are current: gateways rotate, expire, and deprecate keys, and an update or migration can silently revert them.
- Verify your SSL certificate is valid (padlock, no warnings) — payment steps refuse to run on insecure pages, and an expired certificate turns into mysterious payment failures before it turns into visible warnings.
- Place a test transaction (gateway test mode, or a small real charge refunded after) and record the exact error text — then match it against the dashboard's reason code for the same attempt.
- If failures are partial, look for the pattern in the declined list: all one card brand (that brand's processing is misconfigured), all one region (a country/currency restriction), all above an amount (fraud threshold), all with 'authentication' codes (3-D Secure/SCA flow breaking — common for European cards).
What this usually means
When everything declines, the customer's card was never really consulted — the connection between your site and the processor is broken: wrong/expired API keys, test mode, an SSL failure, a suspended gateway account, or a checkout plugin that lost its settings in an update. These are configuration fixes, usually same-day once identified.
When some payments fail, the machinery works and individual payments are being refused: genuine issuer declines (insufficient funds, blocked cards — normal background noise at a few percent), your processor's fraud rules being too aggressive, or a broken verification step (3-D Secure) that fails specific banks' cards. The reason codes distinguish these precisely.
Know your baseline: a few percent of honest payment attempts decline everywhere, always — that's card networks working as designed, not a store problem. What deserves investigation is a decline rate change, a pattern (one brand, one country), or any all-payments outage. Chasing individual normal declines wastes energy better spent reading the dashboard monthly.
What not to do
- Don't loosen or disable fraud protection to rescue declining payments — fraud rules exist because chargebacks cost double the sale plus fees, and processors terminate accounts with high fraud rates. Tune rules using the dashboard's evidence, don't remove them.
- Don't share live API keys in screenshots, forums, or support chats — live keys can authorize charges and refunds; treat them like the store's checkbook. (Test keys are safe to share.)
- Don't re-enter keys repeatedly 'to make sure' during an outage — one careful verification against the gateway dashboard beats five hurried retypes that add typos.
- Don't tell frustrated customers to 'just try another card' as your fix — without diagnosing, you're converting recoverable sales into abandoned ones and reports into silence.
- Don't switch payment providers in a panic over a configuration problem — migrations take days and the same misconfiguration pattern follows careless setups to the new gateway.
When to get help
Payment integrations sit at the intersection of revenue, security, and compliance — the exact spot where careful, experienced hands are cheapest. With your pattern notes and the dashboard's reason codes, a specialist can usually restore payments quickly and verify end-to-end that orders complete and funds actually settle to your bank. Escalate same-day when all payments fail; investigate calmly but promptly when a pattern of partial failures emerges.
Not sure what to do next?
Answer a few short questions and we'll point you to the safest next step — DIY, a freelancer, or a direct review. No passwords required.
Is this a business website? If this issue may be costing you leads, sales, or trust, you may want a direct review instead of trial and error.
Frequently asked questions
Is it the customer's card or my store?
The pattern answers it: all payments failing means your configuration or gateway account (cards were never really consulted); scattered individual failures are normal issuer declines; a pattern (one brand, one country, one amount range) is a specific rule or integration worth fixing.
Where do I see why a payment was declined?
Your payment gateway's dashboard (Stripe, PayPal, etc.) logs every attempt with a reason code — card_declined, expired_card, authentication_failed, invalid key. Reading that list is the single highest-value step in this entire guide.
Why did payments break right after an update?
Checkout plugin and theme updates can reset or corrupt gateway settings, and occasionally an update drops support for an old integration method. Re-verify keys, mode, and the gateway connection after any update that touches checkout — thirty seconds that catches most of these.
What's 3-D Secure and why do European cards keep failing?
It's the bank-verification step (a code or app confirmation) that European rules require for most online card payments. If your checkout's verification flow is broken, those cards fail with authentication-type codes while others sail through. It's a fixable integration issue, and the codes make it identifiable.
What decline rate is normal?
A few percent of attempts declining is universal background noise — expired cards, limits, typos. Worry when the rate jumps, when a pattern appears, or when everything fails. Your gateway dashboard graphs this; glance monthly.
My gateway says my account is under review and payments stopped. What now?
That's an account-level hold, not a website bug — respond to the gateway's verification requests promptly (they're usually identity or business documentation) and payments resume when cleared. Nothing on your site can fix it, and ignoring their emails extends it.