Generic decline: what it means and what to do next
A generic decline is a card refusal with no reason given. How to tell a bank decline from a fraud-filter block, when to retry, and what to tell the customer.

A generic decline means the payment was refused and no specific reason came with it. Most of the time the customer’s bank said no and kept the reason to itself; only the cardholder can get it, by contacting the bank. On Stripe, though, generic_decline can also mean the bank never saw the payment, because Stripe Radar or Adaptive Acceptance blocked it first. So before you retry or tell a customer to call their bank, check where the payment stopped.
This guide covers what the code means on Stripe, Braintree, Adyen and Recurly, how to tell an issuer decline from a block by your own provider, when a retry is allowed, and what to write to the customer. Every rule below comes from the providers’ own documentation, listed in the sources.
What does a generic decline mean?
When a card payment is sent for authorization, the issuing bank answers with a response code. Some codes are specific: insufficient funds, expired card, incorrect CVC. Others only say “declined”. Stripe’s card declines guide puts it plainly: card issuers categorize most declines as generic, “making the exact decline reason unclear”. It adds that, for privacy and security reasons, issuers discuss the specifics of a decline only with their cardholders.
So a generic decline is not a diagnosis. Behind it can sit a fraud screen at the bank, a limit, low funds, a card blocked for online payments or an internal rule. You cannot tell which from the code, and neither can your payment provider.
Stripe describes generic_decline as: “The card was declined for an unknown reason or Stripe Radar or Adaptive Acceptance blocked the payment.” The next step it gives is that the customer needs to contact their card issuer for more information. Its close cousin, do_not_honor, has the same next step but only the first half of the description: “declined for an unknown reason”. For that code, see the do not honor guide.
Did the payment even reach the bank?
This is the question most teams skip. Stripe’s declines overview lists three reasons a payment can fail: issuer declines, blocked payments and invalid API calls. It says that when Stripe blocks a payment, “it doesn’t obtain authorization from the card issuer”. Asking the customer to call their bank about a payment the bank never received wastes their time and yours.
On Stripe, the charge’s outcome object tells you which case you are in:
outcome.type |
outcome.network_status |
What happened | What to do |
|---|---|---|---|
issuer_declined |
declined_by_network |
The bank refused the payment | Read the advice code; retry later or ask for another card |
blocked |
not_sent_to_network |
Stripe blocked it before the bank (Radar or Adaptive Acceptance) | Look at outcome.reason and your Radar rules; a call to the bank will not help |
invalid |
not_sent_to_network |
The API call itself was wrong | Fix the request; nothing to tell the customer |
For a blocked payment, outcome.reason says why: highest_risk_level for Radar’s default block rule, rule for one of your custom rules, and low_probability_of_authorization when Adaptive Acceptance judged the payment unlikely to be authorized. The outcome.seller_message field gives a sentence such as “Stripe blocked this charge as too risky.”
Other providers make the same split in their own words:
- Braintree separates a processor decline, which “indicates that the customer’s bank has refused the transaction request”, from a gateway rejection, which is “blocked by your Braintree gateway settings” (fraud tools, CVV or AVS rules, duplicates, risk thresholds and others). A gateway rejection shows the status “Gateway Rejected” with a reason.
- Adyen returns refusal reason
2“Refused” for a plain refusal, and20“FRAUD” when its pre-authorization risk checks gave a fraud score of 100 or more. - Recurly groups errors by category.
declinedsits under Soft; codes such asfraud_gateway(“declined the transaction due to fraud filters enabled in your gateway”) andfraud_risk_checksit under Fraud.
If you bill with Chargebee, Zuora or Maxio on top of one of these gateways, look for the gateway’s own code in the payment’s error details: that is where the split shows.
- 01 Check where it stopped outcome.type and network_status: a bank decline, or a block by your own provider
- 02 Read the advice code try_again_later, do_not_try_again or confirm_card_data
- 03 Retry, spaced over days Within the network limits, never in a tight loop
- 04 Ask for another card Or a call to the bank; retry at once when the card is updated
What does each provider call a generic decline?
| Where | Generic decline | Retry guidance in the docs |
|---|---|---|
| Stripe | decline_code: generic_decline (also do_not_honor) |
Read outcome.advice_code |
| Braintree | 2046 Declined; also 2000 Do Not Honor and 2038 Processor Declined |
All three marked soft |
| Adyen | Refusal reason 2 “Refused” |
Not given on the refusal reasons page |
| Recurly | declined, also declined_saveable (“declined without specific information”) |
Listed under Soft |
Two details help when reading these codes:
- Braintree’s text for
2000 Do Not Honorcalls it a “generic decline”, and for2046 Declinedsays to contact the bank for card payments, PayPal Support for PayPal and Venmo Support for Venmo. - Adyen has a separate refusal reason,
27“Declined Non Generic”, for responses that “cannot be reliably mapped”. Adyen says this makes it easier to tell generic declines, such as Mastercard “05: Do not honor”, from more specific ones.
Should you retry a generic decline?
Usually yes, a limited number of times and spaced out, unless an advice code says stop. Braintree and Recurly list their generic codes as a soft decline, one that a later retry can fix, but the advice code that comes with it has the final word.
On Stripe, read outcome.advice_code:
try_again_later: the issuer declined, but you can retry.do_not_try_again: do not use the card again for this transaction.confirm_card_data: some card details are wrong; the customer needs to check them.
A Radar block also carries an advice code: Stripe’s example of a blocked payment shows do_not_try_again. Retrying it unchanged would only hit the same rule.
Card network limits. Braintree’s declines article gives the Visa retry categories as they apply to its merchants. 2000 Do Not Honor is in Category 4 and 2046 Declined in Category 2; both are limited to 15 retries over a rolling 30-day period. Above the threshold, the fee is $0.10 per domestic and $0.15 per international transaction. For Mastercard, Braintree says retries “should be based only on the Merchant Advice Codes”, and Mastercard charges $0.10 for every reattempt beyond 10 retries in 24 hours for MAC 03 and MAC 21.
Stripe’s own ceiling is lower. Its card declines guide recommends a maximum of eight retries for charges that permit retries, and warns that issuers can see extra retries as potential fraud, which can cause more declines on legitimate charges. Adyen even has a refusal reason, 46, for transactions it blocked itself “to make sure that you are not charged penalty fees” from excessive retries.
In practice, for a renewal that fails with a generic decline:
- Check
outcome.typefirst. If the payment was blocked by your own provider, review the rule; do not schedule retries. - Never retry in a tight loop. The same request a minute later will most likely get the same answer, and it counts toward the network limits.
- Space retries over days. If the hidden cause was low funds or a daily limit, another day has a better chance.
- Stop on a “do not try again” signal (Stripe
do_not_try_again, Mastercard MAC03or21) and ask for another payment method. - Retry at once when the customer updates their card, instead of waiting for the next scheduled attempt.
How Stripe, Chargebee, Recurly and others schedule their retries is compared in payment retry schedules compared.
What should you tell the customer?
Tell them their bank declined the payment and give them two ways out: contact the bank, or use another card. Never show “generic_decline” or a raw code.
A generic message is also the safe default when the real reason is sensitive. Stripe’s reference says to present fraudulent, lost_card, stolen_card and merchant_blacklist declines in the same manner as generic_decline, without more detail. Adyen’s refusal reasons page says not to expose the details of the refusal reason to shoppers, “to prevent malicious use”. Recurly’s customer message for declined follows the same pattern: “Your transaction was declined. Please use a different card or contact your bank.”
A renewal email for an issuer decline can read:
Subject: Your payment for [Product] didn't go through
Hi [First name],
Your bank declined this month's payment of [amount] for [Product]. Banks don't always say why. Often it is a temporary block that a quick call or message to your bank clears.
You can also use another card here: [update link]
We'll try again on [date]. If your bank lifts the block before then, you don't need to do anything.
For a payment your own fraud rules blocked, the email is different: do not send the customer to their bank. If the customer looks legitimate after review, ask them to try again or to use another payment method, or adjust the rule. More templates are in Stripe decline codes explained.
What mistakes should you avoid?
- Treating every generic decline as the bank’s fault. On Stripe, check
outcome.typeandnetwork_statusbefore you write to the customer. - Retrying a blocked payment. A Radar or gateway rule will block the same request again.
- Ignoring the advice code. The same generic decline can come with “try again later” or “do not try again”.
- Asking the customer to re-enter card details without looking. Stripe says to examine the CVC and address (AVS) checks when a card returns a generic or
do_not_honordecline, and to ask the customer to verify those details if a check failed. - Revealing the real reason. If the code behind the generic message is
stolen_cardorfraudulent, the customer still sees a generic decline.
How do you test a generic decline?
Stripe’s test card 4000000000000002 returns a card_declined error with the decline code generic_decline. Use it in test mode to check that your checkout shows the right message and that your renewal flow sends the email, schedules the retry and stops when the card is updated.
How NoChurn helps
NoChurn reads the decline code and history of every failed renewal. For soft declines such as a generic decline, retries land on likely paydays in the customer’s time zone, inside the days and hours you allow, or you keep your provider’s own retries, such as Stripe Smart Retries. The recovery emails go out on days 0, 3, 7 and 14 by default, each written by AI for that customer and that decline and checked before it leaves; they never show the raw code, and each one links to a hosted card update page with no login. See failed payments.
FAQ
What does “generic decline” mean on a card payment?
The payment was refused without a specific reason. Usually the customer’s bank declined it and only shares the reason with the cardholder. On Stripe, generic_decline can also mean Stripe Radar or Adaptive Acceptance blocked the payment before it reached the bank.
Is a generic decline the same as “do not honor”?
They are close. Both are refusals with no stated reason, and Stripe gives both the same next step: the customer contacts their bank. The difference on Stripe is that generic_decline also covers payments blocked by Radar or Adaptive Acceptance.
Can you retry a generic decline?
Usually, if you wait and the advice code allows it. Braintree marks its generic codes as soft, and Visa limits these categories to 15 retries over a rolling 30 days. Stop on Stripe’s do_not_try_again or Mastercard MAC 03 or 21.
How do I know if Stripe Radar blocked the payment?
Look at the charge’s outcome. A Radar block has type: blocked and network_status: not_sent_to_network, with a reason such as highest_risk_level or rule. An issuer decline has type: issuer_declined and network_status: declined_by_network.
Why won’t the bank tell me the reason?
Stripe states that, for privacy and security reasons, card issuers discuss the specifics of a decline only with their cardholders. Your provider passes on the codes it receives and nothing more.
Sources
All accessed 17 November 2026.