Stripe decline codes

The card is valid, but the account does not have enough balance or credit to cover the charge at the moment it was attempted.

The card has passed its expiration date, so the charge can never succeed on the card currently on file.

A generic refusal from the issuing bank with no specific reason given. The ambiguity is intentional, so the bank does not reveal fraud logic.

The bank or Stripe Radar declined the charge without a specific reason. Catch-all when the issuer returns no detailed code.

The issuer declined the charge. Stripe surfaces a more specific decline_code where the bank provides one; otherwise this is the high-level result.

A temporary error occurred while processing the card, usually on the issuer or network side rather than with the card itself.

A temporary issue prevented the charge. The issuer is signaling that the same card may work shortly.

Stripe could not reach the card issuer to authorize the charge. This is a connectivity issue, not a card problem.

The transaction could not be processed for an unknown transient reason and should be attempted again.

The payment cannot be authorized yet because the issuer needs to confirm the cardholder's identity.

The card requires Strong Customer Authentication (3D Secure) under PSD2, common for EU and UK cards. A silent off-session charge fails until the customer authenticates.

The CVC security code provided does not match the card. The charge will keep failing until correct details are entered.

The CVC security code is not valid for this card.

The card number is incorrect, so the charge cannot be processed.

The card number is invalid or does not exist.

The expiration month on the card is invalid.

The expiration year on the card is invalid.

The ZIP or postal code failed address verification (AVS) with the issuer.

The card does not support this type of purchase (for example, certain subscriptions or currencies).

The card does not support the currency of the charge.

The linked savings account does not have enough balance to cover the charge.

The customer has exceeded the balance, credit limit, or number of transactions the issuer permits in a window.

The customer has hit the number of withdrawals or transactions their bank allows in a period.

The charge was flagged as likely fraudulent by Stripe Radar or the issuer. This can occasionally hit legitimate recurring charges.

The card was reported lost. The issuer returns a generic decline to avoid tipping off potential fraud.

The card was reported stolen. The issuer declines and withholds the specific reason.

The issuer has flagged the card (often lost, stolen, or compromised) and does not want it used.

The payment matches a value on the issuer's or Radar block list.

The issuer declined the charge for a security reason.

The issuer wants to speak with the cardholder before approving the charge, often a fraud or verification hold.

The card has a restriction (for example, a regional or usage limit) that prevents this charge.

The card does not permit this type of transaction.

The issuer does not permit the charge.

The card or account is invalid or closed.

The card has new information (often a new number after reissue). The stored card is out of date.

The cardholder revoked permission for this recurring charge with their bank.

The cardholder placed a stop on this recurring payment with their bank.

A transaction with the same amount and card was submitted very recently, so the issuer treated this as a duplicate.