Free tools / Card Decline / Complete list
Stripe decline codes: the complete list
Every card decline code Stripe returns, in one table: what it means, whether it is a soft or a hard decline, whether retrying the same card can succeed, who can fix it (the bank, the customer or you), and what to tell the customer. Written for SaaS teams recovering failed subscription payments, not just for developers reading an error.
The list is grouped by what to do about the code rather than alphabetically, because that is the question a failed invoice raises. Each code has a short meaning here; the most common ones have a full guide. The whole table is downloadable as JSON, CSV or Excel, and the same data runs the lookup tool and an open-source npm package.
Checked against Stripe's decline-code reference on 12 November 2026 · 51 codes · 8 categories · 40 hard · 11 soft
Download the list
The same data as this page. JSON holds both languages; CSV and Excel are in the page's language, one row per code with the customer message and the email.
MIT licence: use it in your product, your dunning emails or your support macros.
Soft or hard?
Hard. The same card is refused every time until something changes (a new card, a lifted limit or restriction, an authentication), or Stripe and the card networks ask you not to retry it. Retrying a hard decline costs authorization rate and can cost network fees.
Soft. The bank said no without a lasting reason. A later attempt, such as one scheduled by Stripe's Smart Retries, can succeed.
Temporary refusal (10)
The bank said no without a lasting reason. A later retry, such as one scheduled by Stripe's Smart Retries, often succeeds; a gentle reminder helps.
| Code | What it means | Soft / hard | Retry? | Who fixes it | Guide |
|---|---|---|---|---|---|
| generic_declineGeneric decline | Stripe's most common code: the bank declined without giving a reason, or Stripe itself blocked the payment (Radar, or Adaptive Acceptance on IC+ pricing) before the bank saw it. Check outcome.type and outcome.reason to tell the two apart. | Soft | Likely | The bank | Guide |
| do_not_honorDo not honor | Stripe says only that the bank declined for an unknown reason and that the customer should contact it. In practice it is the bank's opaque 'no' (a temporary lock, a spending rule, a risk score on their side), and a later retry can succeed. | Soft | Likely | The bank | Guide |
| card_declinedCard declined (error code) | Not a decline code: Stripe's error code for any card decline. The reason is in decline_code; when that is empty, treat it like a generic decline. | Soft | Maybe | The bank | Guide |
| try_again_laterTry again later | Declined for a reason the issuer did not give; Stripe's advice is to retry later and, if it keeps failing, have the customer contact their bank. Stripe lists this code as deprecated, so you mostly see it on older payments. | Soft | Likely | The bank | Guide |
| processing_errorProcessing error | A transient error while the payment was being processed, usually on the issuer or network side. | Soft | Likely | The bank | Guide |
| issuer_not_availableIssuer not available | The customer's bank could not be reached to authorize the payment. | Soft | Likely | The bank | Details |
| reenter_transactionRe-enter transaction | The issuer could not process the payment and asks for it to be submitted again. | Soft | Likely | The bank | Details |
| approve_with_idApprove with ID | The payment could not be authorized without identification; for online payments this is effectively a transient decline. | Soft | Likely | The bank | Details |
| call_issuerCall issuer | Stripe gives no reason and says the customer should contact their bank. The network response behind it asks the cardholder to call the bank before the payment can go through, often for a check on the bank's side. | Soft | Maybe | The customer | Details |
| no_action_takenNo action taken | Stripe gives no reason and says the customer should contact their bank; the network response means the bank did not process the request. | Soft | Maybe | The bank | Details |
Insufficient funds (1)
The balance or available credit did not cover the charge at that moment. A retry a few days later often succeeds once the account is topped up.
| Code | What it means | Soft / hard | Retry? | Who fixes it | Guide |
|---|---|---|---|---|---|
| insufficient_fundsInsufficient funds | The account did not have enough balance or credit at the time of the charge. | Soft | Likely | The customer | Guide |
Limit reached (2)
The charge went over a balance, credit or transaction limit set on the card. The issuer keeps refusing the same card until the customer changes that limit, so do not count on a retry: ask for another card or a higher limit.
| Code | What it means | Soft / hard | Retry? | Who fixes it | Guide |
|---|---|---|---|---|---|
| withdrawal_count_limit_exceededWithdrawal limit exceeded | The customer went over the balance or credit limit available on their card. | Hard | No | The customer | Guide |
| card_velocity_exceededCard limit exceeded | The customer went over the balance, credit limit or transaction amount limit available on their card. | Hard | No | The customer | Guide |
Card update needed (16)
The card on file is expired, wrong or closed. Retrying will fail every time; only the customer can replace it.
| Code | What it means | Soft / hard | Retry? | Who fixes it | Guide |
|---|---|---|---|---|---|
| expired_cardExpired card | The card has passed its expiry date. Card networks refresh many cards automatically, but this one was not. | Hard | No | The customer | Guide |
| incorrect_numberIncorrect number | The card number is wrong. | Hard | No | The customer | Guide |
| invalid_numberInvalid number | The card number is not a valid card number. | Hard | No | The customer | Details |
| invalid_accountInvalid account | The card or the account behind it is invalid or closed. | Hard | No | The customer | Guide |
| new_account_information_availableNew account information available | The card was replaced; the issuer has new details (number or expiry). | Hard | No | The customer | Details |
| incorrect_cvcIncorrect CVC | The security code did not match. | Hard | No | The customer | Guide |
| invalid_cvcInvalid CVC | The security code is not valid. | Hard | No | The customer | Details |
| invalid_expiry_monthInvalid expiry month | The expiry month is wrong. | Hard | No | The customer | Details |
| invalid_expiry_yearInvalid expiry year | The expiry year is wrong. | Hard | No | The customer | Details |
| incorrect_zipIncorrect ZIP | The postal code did not match the one on file at the bank. | Hard | No | The customer | Details |
| incorrect_addressIncorrect address | The billing address entered does not match the one the bank has on file. | Hard | No | The customer | Details |
| incorrect_pinIncorrect PIN | Wrong PIN (card-present payments only). | Hard | No | The customer | Details |
| invalid_pinInvalid PIN | Invalid PIN (card-present payments only). | Hard | No | The customer | Details |
| pin_try_exceededPIN tries exceeded | Too many wrong PIN attempts; the card is locked. | Hard | No | The customer | Details |
| offline_pin_requiredOffline PIN required | The card requires a PIN entered on a terminal. | Hard | No | The customer | Details |
| online_or_offline_pin_requiredPIN required | The card requires a PIN to be used. | Hard | No | The customer | Details |
Card not allowed (5)
The card cannot be used for this kind of payment (online, recurring or international), or the bank restricted it. Retrying the same card will not help; the customer has the restriction lifted or uses another card.
| Code | What it means | Soft / hard | Retry? | Who fixes it | Guide |
|---|---|---|---|---|---|
| restricted_cardRestricted card | The customer cannot use this card for this payment; Stripe notes it may have been reported lost or stolen. Banks also return it for cards restricted to some purchase types (online, recurring, international). | Hard | No | The customer | Guide |
| transaction_not_allowedTransaction not allowed | Stripe gives no reason and says the customer should contact their bank. The network response usually means the card is not allowed to make this kind of transaction (online, recurring or international). | Hard | No | The customer | Guide |
| not_permittedNot permitted | The payment is not permitted on this card or account. | Hard | No | The customer | Details |
| service_not_allowedService not allowed | Stripe gives no reason and says the customer should contact their bank; the network response means the bank does not allow this service for the card. | Hard | No | The customer | Details |
| do_not_try_againDo not try again | Stripe gives no reason and says the customer should contact their bank; the network response asks you not to retry. Stripe lists this code as deprecated, so you mostly see it on older payments. | Hard | No | The customer | Details |
Authentication required (3)
The bank wants the cardholder to confirm the payment (3-D Secure / SCA). Stripe cannot retry headlessly; the customer must complete it from the hosted invoice.
| Code | What it means | Soft / hard | Retry? | Who fixes it | Guide |
|---|---|---|---|---|---|
| authentication_requiredAuthentication required | The bank requires 3-D Secure / Strong Customer Authentication for this charge. Common in Europe on the first charge or after a card change. | Hard | No | The customer | Guide |
| authentication_not_handledAuthentication not completed | Related to authentication_required: the bank asked for authentication (3-D Secure / SCA), the payment went ahead without it, and the bank declined again. | Hard | No | The customer | Details |
| mobile_device_authentication_requiredMobile device authentication required | The bank wants the customer to authenticate the payment on their phone or watch (in-person payments). Stripe's advice is to have the customer tap their device again. | Hard | No | The customer | Details |
Blocked card (8)
Lost, stolen, flagged or withdrawn. Do not retry: it can hurt your acceptance rate. Ask for a different card, through a neutral message.
| Code | What it means | Soft / hard | Retry? | Who fixes it | Guide |
|---|---|---|---|---|---|
| fraudulentFraudulent | Stripe flagged the payment as potentially fraudulent. Show the customer a generic decline, not this reason. | Hard | No | The customer | Guide |
| lost_cardLost card | The card was reported lost. The customer usually already has a replacement. | Hard | No | The customer | Guide |
| stolen_cardStolen card | The card was reported stolen. | Hard | No | The customer | Guide |
| pickup_cardPickup card | Stripe: the customer cannot use this card for this payment, possibly because it was reported lost or stolen. On card networks the response asks for the physical card to be withdrawn. | Hard | No | The customer | Guide |
| stop_payment_orderStop payment order | Stripe gives no reason and says the customer should contact their bank. On card networks this response usually means the cardholder asked their bank to stop payments to you, but Stripe does not confirm it. | Hard | No | The customer | Guide |
| revocation_of_authorizationRevocation of authorization | Stripe gives no reason and says the customer should contact their bank. On card networks this response means the authorization for this recurring payment was revoked, usually by the cardholder, but Stripe does not confirm it. | Hard | No | The customer | Details |
| revocation_of_all_authorizationsRevocation of all authorizations | Stripe gives no reason and says the customer should contact their bank. On card networks this response means all recurring authorizations on the card were revoked, usually by the cardholder, but Stripe does not confirm it. | Hard | No | The customer | Details |
| security_violationSecurity violation | Stripe gives no reason and says the customer should contact their bank; the network response names a security block on the card. | Hard | No | The customer | Details |
Check your side (6)
Check the amount, the currency, the card types you accept and your Stripe or Radar setup before retrying. Depending on the code, the customer may also need another card.
| Code | What it means | Soft / hard | Retry? | Who fixes it | Guide |
|---|---|---|---|---|---|
| merchant_blacklistMerchant blacklist | The payment matched a block rule in your Stripe Radar settings (blocked card, email or IP). | Hard | No | You | Details |
| card_not_supportedCard not supported | The card does not support this kind of purchase (e.g. a prepaid or debit card that cannot be used for recurring online payments). | Hard | No | The customer | Guide |
| currency_not_supportedCurrency not supported | The card cannot be charged in this currency. | Hard | No | The customer | Guide |
| invalid_amountInvalid amount | The amount is invalid or above what the card allows. Stripe: if the amount looks right, the customer should check with their bank that a purchase of that size is allowed. | Hard | No | You | Details |
| duplicate_transactionDuplicate transaction | An identical charge was submitted very recently. | Hard | No | You | Details |
| testmode_declineTest mode decline | A Stripe test card was used in live mode (or a decline test card in test mode). | Hard | No | You | Details |
Values that are not decline codes
People paste these from a Charge or a Radar review. They explain a blocked payment, not a bank decline, and the right action differs.
- highest_risk_level
- highest_risk_level is not a decline code: it is Stripe Radar's risk rating, and it means Radar blocked the payment itself before the bank decided. Treat it like a blocked card (do not retry, ask for another card) unless you believe it is a false positive, in which case check your Radar rules.
- elevated_risk_level
- elevated_risk_level is not a decline code: it is Stripe Radar's risk rating. Radar does not block these payments by default, so a failed payment with this rating was most likely stopped by one of your own Radar rules. Check your block and review rules before retrying or asking the customer for another card.
- rule
- This payment was blocked by Stripe Radar (outcome.type "blocked"), not declined by the bank. With outcome.reason "rule" it was one of your own Radar rules. Check which rule matched before charging again or asking the customer for another card.
Have a code, an error message or a webhook?
Paste it in the lookup tool: it finds the decline code inside, shows the verdict and gives you the customer message and the email to send.
Open the lookup toolIn your own code
This list is the open-source npm package stripe-declines (MIT): the data as JSON, a lookup that reads pasted errors and payloads, and a command line. The lookup tool on this site runs on it.
npm install stripe-declinesQuestions about Stripe decline codes
What is the difference between a soft decline and a hard decline?
A soft decline is a refusal without a lasting cause: the bank could not approve the payment at that moment (generic_decline, do_not_honor, insufficient_funds, try_again_later, processing_error). A later attempt can succeed, which is what Stripe's Smart Retries exploit. A hard decline means the same card will be refused every time until something changes: the card is expired, invalid, lost, stolen or restricted, or the bank requires an authentication or asks you not to retry. For a hard decline, ask for another card or the missing action; retrying only lowers your authorization rate.
Where do I find the decline code in Stripe?
On the failed payment in the Stripe Dashboard, under the payment details. In the API it is `last_payment_error.decline_code` on the PaymentIntent, `outcome.reason` on the Charge, and `decline_code` on a card error. `card_declined` is the generic error code, not the reason; the reason is in `decline_code`. Stripe also returns an `advice_code` (`try_again_later`, `do_not_try_again`, `confirm_card_data`) that says what to do with that attempt.
Which Stripe decline codes can be retried?
The soft ones: generic_decline, do_not_honor, try_again_later, processing_error, issuer_not_available, reenter_transaction, approve_with_id, and insufficient_funds a few days later. call_issuer and no_action_taken may succeed once. Every other code in this list is marked as a hard decline: expired or invalid card data, lost, stolen or blocked cards, limits, restrictions, authentication codes and the codes you fix on your own side. When Stripe gives an advice_code with the attempt, follow it over this table.
Can I download the list of Stripe decline codes?
Yes, from the buttons at the top of this page: JSON (both languages, the package's own data file), CSV and Excel (one language, one row per code with the category, the soft or hard status, the retry verdict, who can fix it, the meaning, the action, the customer message and the customer email). The data is MIT-licensed.
How is this list kept up to date?
The data is checked against Stripe's published decline-code reference; the check date is shown above the table. The codes, their categories and the retry verdicts follow the recovery rules FlowMRR applies to real failed invoices, and the open-source package that holds them has tests that fail when a text contradicts a code's verdict. Corrections are welcome on GitHub, with the Stripe documentation that backs them.
Which declined customers should you contact first?
FlowMRR reads your failed payments from Stripe, ranks who to contact first and drafts the recovery email with the right tone for each decline code. You review it and send it yourself.