Stripe Declined Payments: Codes and Fixes
Every Stripe decline code grouped by what to do next: fix the data, authenticate, retry later or stop. Plus advice codes, retry limits and Radar blocks.
Article summary
TL;DR
A Stripe decline comes from the card issuer, from Stripe's own fraud tools, or from bad data. Check the payment's outcome type first. Then read the decline code: fix the data, authenticate, retry later, or stop. Stripe recommends at most 8 retries per charge, and `generic_decline` can mean Stripe blocked the payment itself.
- Stripe names three failure types: issuer declines, blocked payments and invalid API calls.
- When Stripe blocks a payment, "it doesn't obtain authorization from the card issuer".
- `generic_decline` covers an unknown issuer reason or a payment that "Stripe Radar or Adaptive Acceptance blocked".
- Stripe recommends "a maximum of eight retries" per charge; Visa allows up to 20 attempts in 30 days, none after a category 1 code.
- Stripe Billing doesn't retry 9 hard decline codes, including `lost_card`, `authentication_required` and `highest_risk_level`, until the customer adds a new card.
On this page
This page covers Stripe's codes and tools only. For Visa's two-digit codes and retry categories at any processor, see declined payments: decline codes and retry rules. More Stripe guides are in the Stripe hub.
First, find out who said no
Not every Stripe decline reaches the bank. The outcome of the charge tells you which of three gates refused it1Stripe Docs, Declines, read November 2, 2026.
Fig. 1Three places a Stripe payment can fail
approved declined or closed routing step
- Your integrationtype: invalid, not sent to network
- checked byRadar and Adaptive Acceptancetype: blocked, not sent to network
- sent toCard issuertype: issuer_declined, with a codeDeclined
read outcome.type before the code
outcome.type | network_status | Who refused | What it tells you |
|---|---|---|---|
issuer_declined | declined_by_network | The card issuer | A decline code, plus the network's own code and advice code1Stripe Docs, Declines, read November 2, 20262Stripe Docs, Card declines, read November 2, 2026 |
blocked | not_sent_to_network | Radar, your rules, or Adaptive Acceptance | A reason such as highest_risk_level or low_probability_of_authorization1Stripe Docs, Declines, read November 2, 2026 |
invalid | not_sent_to_network | Your integration | The request was wrong; the payment never ran1Stripe Docs, Declines, read November 2, 2026 |
Adaptive Acceptance blocks apply to accounts on IC+ pricing. Stripe says they avoid "unnecessary network costs" such as excessive retry penalties, on payments with a low chance of approval1Stripe Docs, Declines, read November 2, 2026.
Stripe decline codes, grouped by what you do next
Stripe lists about 50 card decline codes3Stripe Docs, Decline codes, read November 2, 2026. Most of them call for one of eight actions:
| What to do | Stripe decline codes | Retry the same card? |
|---|---|---|
| Ask the customer to correct the data | incorrect_number, invalid_number, incorrect_cvc, invalid_cvc, invalid_expiry_month, invalid_expiry_year, incorrect_zip, incorrect_address, expired_card | Only with corrected details3Stripe Docs, Decline codes, read November 2, 2026 |
| Run authentication | authentication_required, authentication_not_handled | After 3D Secure; off-session, bring the customer back3Stripe Docs, Decline codes, read November 2, 2026 |
| Offer another card or method | insufficient_funds, withdrawal_count_limit_exceeded, card_velocity_exceeded, card_not_supported, currency_not_supported, invalid_amount | Later, within the limits below3Stripe Docs, Decline codes, read November 2, 2026 |
| Try again shortly | issuer_not_available, processing_error, reenter_transaction, approve_with_id | Once, then the customer calls the issuer3Stripe Docs, Decline codes, read November 2, 2026 |
| Customer calls the bank | generic_decline, do_not_honor, call_issuer, no_action_taken, not_permitted, security_violation, service_not_allowed, transaction_not_allowed, invalid_account, new_account_information_available | Sparingly; Billing never retries transaction_not_allowed3Stripe Docs, Decline codes, read November 2, 20264Stripe Docs, Automate payment retries, read November 2, 2026 |
| Stop, show a generic message | lost_card, stolen_card, pickup_card, restricted_card, fraudulent, merchant_blacklist | No3Stripe Docs, Decline codes, read November 2, 20264Stripe Docs, Automate payment retries, read November 2, 2026 |
| Stop billing this card | revocation_of_authorization, revocation_of_all_authorizations, stop_payment_order | NoThe customer withdrew consent at the bank3Stripe Docs, Decline codes, read November 2, 20264Stripe Docs, Automate payment retries, read November 2, 2026 |
| Check for a double charge | duplicate_transaction | Only if no recent payment exists3Stripe Docs, Decline codes, read November 2, 2026 |
Source: Stripe Docs, Decline codes, and Automate payment retries, read November 2, 20263Stripe Docs, Decline codes, read November 2, 20264Stripe Docs, Automate payment retries, read November 2, 2026. do_not_try_again and try_again_later as decline codes are deprecated3Stripe Docs, Decline codes, read November 2, 2026.
To apply Visa's retry categories, read network_decline_code, not the Stripe code. Its meaning "differs based on the card network", so check the card brand first2Stripe Docs, Card declines, read November 2, 2026.
Advice codes: Stripe's own next step
Next to the decline code, Stripe adds an advice_code in the outcome2Stripe Docs, Card declines, read November 2, 2026. When it's there, follow it before your own logic.
Fig. 2Stripe's three advice codes
do_not_try_again
Don't use the card again for this transaction. Ask for another card or method.
try_again_later
The issuer allows a retry. If it fails again, the customer contacts the issuer.
confirm_card_data
Some details are wrong. The customer checks the card and re-enters them.
the shortest route to the right next step
Mastercard also sends Merchant Advice Codes, which Stripe passes as network_advice_code2Stripe Docs, Card declines, read November 2, 2026. A blocked payment always carries do_not_try_again1Stripe Docs, Declines, read November 2, 2026.
generic_decline and do_not_honor
These two mean "no reason given", and most declines end up there: "Card issuers categorize most declines as generic"2Stripe Docs, Card declines, read November 2, 2026. Stripe describes both as "declined for an unknown reason"3Stripe Docs, Decline codes, read November 2, 2026. Work through this list before asking the customer to call:
- Check the outcome type. If it's
blocked, the refusal is yours: a Radar rule or a high risk score1Stripe Docs, Declines, read November 2, 20263Stripe Docs, Decline codes, read November 2, 2026. - Check CVC and address results. If either failed when the card was added, ask the customer to confirm both2Stripe Docs, Card declines, read November 2, 2026.
- Compare card country and IP country. A mismatch can be a legitimate fraud decline, or a traveler2Stripe Docs, Card declines, read November 2, 2026.
- Look at the amount. Issuers flag "large purchases or a large volume of transactions over a short period of time"2Stripe Docs, Card declines, read November 2, 2026.
- Then hand over. Issuers discuss a decline's details "only with their cardholders"2Stripe Docs, Card declines, read November 2, 2026.
If a Radar rule blocked a customer you know, "Add to allow list" in the Dashboard stops it from blocking future matching payments. It doesn't retry the blocked one1Stripe Docs, Declines, read November 2, 2026.
How many times you can retry on Stripe
Fewer than the network allows. Stripe recommends "a maximum of eight retries for charges that permit retries", because issuers "might see creating additional retries as potential fraud"2Stripe Docs, Card declines, read November 2, 2026. Visa's limit is wider: up to 20 attempts in 30 days for categories 2 to 4, and none after category 1, such as lost, stolen or closed account5Visa Core Rules and Visa Product and Service Rules, sections 1.7.2.1 and 7.3.6.3, edition October 24, 2026.
On Stripe Billing, Smart Retries picks the timing. You set a number of tries over 1 week to 2 months; "the recommended default setting is 8 tries within 2 weeks"4Stripe Docs, Automate payment retries, read November 2, 2026. After a hard decline, retries stay scheduled but only run once a new payment method is added4Stripe Docs, Automate payment retries, read November 2, 2026.
An Acquirer, a Merchant, a Payment Facilitator, or a VisaNet Processor that reattempts an Authorization Request following a Decline Response [...] must not intentionally manipulate any data elements from the original Authorization Request.
Sending a declined card to another processor is still a reattempt: a category 1 code stays final there too5Visa Core Rules and Visa Product and Service Rules, sections 1.7.2.1 and 7.3.6.3, edition October 24, 2026. Spacing and schedules: smart retries. Renewals that fail: subscription payment failures.
Why high-risk merchants see more declines on Stripe
Some of it is the issuer, some of it is Stripe. Here is how to tell them apart.
Fig. 3Decline patterns on high-risk Stripe accounts
- Many "blocked" with highest_risk_levelRadar scores your traffic as riskyReview rules and allow-list known customers; don't loosen everything
- Declines concentrated on foreign cardsCard issued in another country than your accountStripe suggests accounts in your larger markets
- do_not_honor on large first ordersIssuer fraud models on big, new purchases3D Secure, CVC and postal code at checkout
- authentication_required on renewalsOff-session payment needs the customerEmail a link to pay and authenticate
half of these are fixable on your side
A few more causes Stripe documents:
- Card type restrictions. FSA and HSA cards are often limited to certain merchants, so the issuer declines anything else2Stripe Docs, Card declines, read November 2, 2026.
- New accounts in Asia Pacific. Visa's MERP, effective October 2026, weighs authorization declines with fraud and disputes. Stripe advises watching declines closely "during your first months of processing"6Stripe Docs, Dispute and fraud card monitoring programs, read November 2, 2026.
- Insufficient funds. Stripe suggests adding a buy now, pay later option2Stripe Docs, Card declines, read November 2, 2026.
How to measure progress: Stripe says to analyze unique declines and "exclude failed retries"1Stripe Docs, Declines, read November 2, 2026. More on the metric: authorization rate. Balancing fraud blocks and approvals: fraud and 3D Secure.
What to tell the customer
Something neutral, every time. The person at your checkout may not be the cardholder.
Watch out
For lost_card, stolen_card, fraudulent and merchant_blacklist, Stripe says not to give details and to present them "in the same manner as generic_decline"3Stripe Docs, Decline codes, read November 2, 2026. A message such as "Your bank declined this payment. Try another card or contact your bank" works for all of them.
After a decline, step by step
- Read
outcome.type:blocked,invalidorissuer_declined1Stripe Docs, Declines, read November 2, 2026. - Read
advice_codeand follow it when present2Stripe Docs, Card declines, read November 2, 2026. - Read the decline code and match it to an action in the table above3Stripe Docs, Decline codes, read November 2, 2026.
- On
issuer_declined, readnetwork_decline_codeto apply the network's retry rules2Stripe Docs, Card declines, read November 2, 20265Visa Core Rules and Visa Product and Service Rules, sections 1.7.2.1 and 7.3.6.3, edition October 24, 2026. - On-session: prompt the customer to try again or use another method2Stripe Docs, Card declines, read November 2, 2026.
- Off-session: notify the customer by email or in-app to come back and pay2Stripe Docs, Card declines, read November 2, 2026.
- Retry within limits: at most 8 times at Stripe, never after category 1 or a hard decline2Stripe Docs, Card declines, read November 2, 20264Stripe Docs, Automate payment retries, read November 2, 20265Visa Core Rules and Visa Product and Service Rules, sections 1.7.2.1 and 7.3.6.3, edition October 24, 2026.
Based on Stripe Docs (Declines, Card declines, Decline codes, Automate payment retries), read November 2, 2026, and Visa Core Rules, October 24, 2026.
By industry
| Industry | What changes | Guide |
|---|---|---|
| Supplements | Big bundles, new customers from ads and renewals on cards that changed trigger more issuer declines | Reducing payment declines for supplement brands |
| Skincare | Beauty checkouts already lose many shoppers; wallets and a clear descriptor matter more | Reducing payment declines for skincare brands |
| Fitness | Big equipment orders that issuers flag as unusual, and refills charged to cards that changed | Reducing payment declines for fitness brands |
| Info products | High prices and foreign cards fail at the first checkout, then installments and membership renewals | Reducing payment declines for info product businesses |
| Online pharmacy | HSA and FSA cards the store isn't set up for, and authorizations that expire during prescription review | Reducing payment declines for online pharmacies |
| Telehealth | Capture after the clinician's review must fall within the 7-day hold; refill charges fail on changed cards | Reducing payment declines for telehealth companies |
How Tagada helps
A second route when Stripe says no
- Acceptance: "If you sell something real, we will get you paid."7TagadaPay, tagadapay.io, read November 2, 2026
- Routing: "Every transaction is scored against your live MID network in real time." Route to the processor most likely to approve it, and retry on decline, with "no engineering required." TagadaPay reports a +18% approval uplift.7TagadaPay, tagadapay.io, read November 2, 2026
- Stripe included: "Already on Stripe, NMI or Airwallex? We orchestrate those too."7TagadaPay, tagadapay.io, read November 2, 2026
- Fraud and security: "Native 3DS2, device intelligence, and rules engine: approve real customers, block the rest."7TagadaPay, tagadapay.io, read November 2, 2026
- A vault you own: cards, customer profiles and subscription data stay portable, so a second processor doesn't mean re-collecting cards.
Tagada follows Visa and Mastercard rules and the laws that apply to payments. A category 1 decline stays final on every route. Tagada CRM plans are on the pricing page.

Frequently asked questions
What does generic_decline mean on Stripe?
What does do_not_honor mean on Stripe?
Why does Stripe keep declining my customers' cards?
How many times can I retry a declined payment on Stripe?
Is a Stripe decline the same as a Stripe account restriction?
Sources
Checked November 2, 2026- Stripe Docs, Declines, read November 2, 2026
- Stripe Docs, Card declines, read November 2, 2026
- Stripe Docs, Decline codes, read November 2, 2026
- Stripe Docs, Automate payment retries, read November 2, 2026
- Visa Core Rules and Visa Product and Service Rules, sections 1.7.2.1 and 7.3.6.3, edition October 24, 2026
- Stripe Docs, Dispute and fraud card monitoring programs, read November 2, 2026
- TagadaPay, tagadapay.io, read November 2, 2026
TagadaPay
One decline shouldn't lose the sale
Tell us what you sell and how you sell it. Each application is underwritten, and approval is not guaranteed.
- 01Tell us what you sell and how
- 02Underwriting reviews your business
- 03Process through TagadaPay alongside your other processors
