Failed & declined payments

funnelish · August 1, 2026, 6:55pm

Some payments will fail. Even a perfectly configured funnel sees declines: issuing banks refuse a meaningful share of all online card attempts, and no setting anywhere makes that number zero. The skill isn’t eliminating declines; it’s telling apart the three very different things a failed payment can mean, because each has a different fix:

Your setup is broken: every payment fails, and the fix is in your configuration.
The gateway or bank said no: some payments fail, and the fix (when there is one) is routing or method coverage.
The customer bailed: the payment was never completed, and the fix is checkout experience.

First: find out what actually happened

Two tools, two different questions:

Funnelish shows you the pattern. Open Analytics → Payment methods for the payment methods report: every method and gateway side by side, with its acquisition rate, purchase fail rate, failed purchase count, orders and revenue. One glance answers the questions that decide everything downstream: is it one gateway failing or all of them, how big is the problem, and when did it start (narrow the date range to see). A gateway showing an 80% fail rate next to another at 15% isn’t a mystery; it’s a diagnosis.

Your gateway’s dashboard shows you the reason. Funnelish tells you a payment didn’t complete; Stripe, PayPal, NMI, Airwallex, Checkout.com or RazorPay tells you why: the decline code, the risk decision, the 3DS outcome. Once the report has told you where to look, look up the individual failed attempts there.

No trace of the attempts in the gateway at all? Then the payments never reached it. That’s a configuration problem, and it’s the next section.

When everything fails: it’s configuration

If no payment goes through at all, work down this list. It’s ordered by how often each one turns out to be the cause:

Test Mode is still on, in the funnel’s top bar. Orders appear in Funnelish, no money appears anywhere. First item on the launch checklist for a reason.
The gateway holds test credentials. Checkout.com keys contain test, RazorPay’s start rzp_test_. Check what’s actually pasted in.
The gateway was never selected and saved on the payment form. It exists on your account, but this form isn’t pointing at it. See Add payment methods to your checkout.
The method isn’t enabled on the gateway’s side. Stripe-backed methods (Klarna, iDEAL, Bancontact, SEPA, Przelewy24, EPS) each need turning on in the Stripe dashboard. Each method’s article covers where.
Your gateway account isn’t fully activated. KYC pending, verification incomplete, or (NMI specifically) the account itself is in Test Mode, which stops real transactions processing. See NMI.
Credentials were pasted with whitespace or swapped (public in the private field, Key ID instead of Key). Clear both fields and re-paste rather than editing in place.

When some fail: reading real declines

A decline is the issuing bank or the gateway’s risk system saying no to one specific payment. They come in two kinds, and the difference decides whether anything can be done:

Soft declines are circumstantial: the issuer’s risk rules, velocity limits, a regional acquiring quirk, a temporary gateway problem. The same card can succeed on another attempt or through another acquirer, which is exactly what Gateway Pools automate.

Hard declines are about the card itself: wrong CVV, expired, invalid number, insufficient funds, reported stolen. These fail everywhere, and retrying achieves nothing. The customer needs a different card or a different method.

Common patterns worth recognising:

Declines clustered on European customers → 3D Secure. In the UK and EEA, payments without authentication get declined by the issuer, not approved. Checkout.com exposes the controls directly; see Checkout.com.
Declines clustered on one card brand → that brand isn’t enabled on your merchant account. Amex is the usual case.
Klarna declines → Klarna’s own per-customer credit decision. Nothing to fix on your side. See Klarna.
A method disappearing rather than declining → currency or country mismatch. Several European methods are EUR-only and hide themselves when the funnel’s currency doesn’t match.
Payments worked yesterday, all decline today → something changed on the gateway’s side: regenerated keys, an account flipped into test mode, a verification requirement coming due.

When the customer bails

Not every failed payment is a refusal. Plenty are abandonments: a 3DS challenge closed instead of completed, a wallet sheet dismissed, a Klarna flow left halfway. In your gateway these show as incomplete or abandoned rather than declined.

A consistent pattern of abandonment at the payment step is checkout feedback, not a technical fault. The levers: offer the methods your buyers actually trust (local methods matter enormously outside card-first markets), make the trusted method the pre-selected default, and keep the form short. Every extra field costs completions.

Recovering the revenue

Three layers, in order of leverage:

Route around soft declines automatically with Gateway Pools: a retry on a genuinely different acquirer recovers payments your primary refused. Mind the two caveats: it can’t rescue hard declines, and it costs a per-transaction fee. Setup and routing rules are in the Gateway Pools guide.
Offer a fallback method. A declined card doesn’t have to end the sale if PayPal or a local method is one click away. This is the cheapest decline recovery there is.
Follow up. A failed payment with captured contact details is a lead, not a loss. An automation that emails “your payment didn’t go through, here’s your cart” recovers a real percentage, because many failures were accidents the customer would happily fix.

Catch it early: monitoring

The expensive failures aren’t the ones you’re debugging. They’re the ones running unnoticed while ads spend. Two habits prevent that:

After any launch or payment change, watch Analytics → Live view. Real-time sessions, purchases and conversion rate over the last ten minutes. If you’ve just switched gateways, changed a payment form, or turned off Test Mode, a few minutes here confirms orders are actually flowing, and a conversion rate that falls off a cliff mid-campaign is your earliest possible signal that payments broke.

Review the payment methods report periodically, not just in a crisis. Fail rates drift. A gateway that quietly slips from 15% to 30% declines costs you real revenue without ever producing a support ticket. The same comparison is also the data for smarter routing: if one gateway consistently out-approves another, that’s which one should lead your gateway pool, or be your default.

What to tell a customer who can’t pay

Support tickets about declined payments usually can’t be solved by you, because the bank’s decision isn’t yours. What helps:

Ask them to try another card or another payment method. That resolves the majority.
For a repeated decline on a good card, the customer should call their bank. Issuers often block first-time payments to unfamiliar merchants, and one call whitelists you.
Don’t retry the same card again and again. Repeated attempts look like card testing to acquirers and can hurt your standing.

Payment processing is the fiddliest part of building a funnel. Gateway credentials, currencies, country rules, the form itself: a lot of moving parts, and the one area where a mistake costs you orders rather than just looking wrong.

If you’ve found the decline code and it still doesn’t make sense, start a topic in Ask the community with the gateway and what the dashboard shows. For anything tied to your account or a specific transaction, contact us on chat support.