Issuer Decline

An issuer decline is what happens when the cardholder's bank says no to a payment request. You get a response code back through the card network, but that's about it. The issuer knows everything about the cardholder's account. You get a two-digit number. If you run a subscription business, you'll see a lot of these. Issuer declines are the single biggest category of failed payments.

The information asymmetry is by design. The issuer protects the cardholder's privacy while giving the merchant just enough to decide what to do next. In practice, that means you're making recovery decisions based on imperfect information.

Why issuers decline transactions

The reasons vary, and the decline code doesn't always reveal the specific cause. Insufficient funds (ISO 8583 code 51) is the most common. Suspected fraud is next, triggered by unusual spending patterns, geographic anomalies, or velocity limits.

• Expired or invalid card: the card number has changed, the card has expired, or the account has been closed (codes 14, 54)
• Generic refusal: the issuer declines without a specific reason, typically "Do Not Honor" (code 05), a catch-all that Adyen's data shows conceals insufficient funds roughly 50% of the time
• MCC-based blocking, where the issuer has decided to block transactions from certain merchant category codes entirely

Soft declines vs hard declines from issuers

Every issuer decline falls into one of two categories. Soft declines are temporary: the card is valid but the payment failed for a transient reason. Retry these. Hard declines are permanent: the card is dead. Stop retrying.

Visa and Mastercard enforce strict retry limits. Visa allows 15 retries within 30 days for soft declines, Mastercard allows 35 but with escalating fees. Retry a hard decline and you're looking at fines of $0.10-$0.50 per excess attempt.

How to recover from issuer declines

For subscription businesses, issuer declines are the primary driver of involuntary churn. The right response depends entirely on the decline type. For soft declines, use smart retry logic to reattempt at optimal times. Silent retries alone recover about 21% of failed payments. For hard declines, stop retrying and contact the customer immediately with recovery emails prompting them to update their card.

Then there's code 05: treat it as a soft decline with a medium retry window of 5-14 days, then escalate to customer outreach if retries don't succeed.

A proper dunning system automates this entire flow, combining smart retries with recovery emails and pre-dunning alerts. Well-configured dunning recovers 50-70% of failed payments.