Stripe generic_decline and do_not_honor: what they mean and what to doUnofficial guide based on Stripe's docs
A customer's subscription renewal failed on Stripe with the decline code generic_decline or do_not_honor. Either code can mean the card issuer declined the card for an unknown reason. A generic_decline can also mean Stripe Radar or Adaptive Acceptance blocked the payment (see below). This page sums up what Stripe's docs say about them: what the codes mean, how to tell an issuer decline from a payment Stripe blocked, whether Stripe Billing retries them, and what you can do on top of that.
The facts here come from Stripe's docs, not from running a subscription business on Stripe ourselves, and we haven't seen these screens in a live account. Setting names are written as the docs show them, so if your Dashboard looks different, go by what you see.
What generic_decline and do_not_honor mean
- Stripe's decline codes table describes both as a card declined for an unknown reason, and gives both the same next step: the customer contacts their card issuer for more information.
generic_declinehas one more meaning in that table: Stripe Radar or Adaptive Acceptance blocked the payment.- Stripe's card declines guide says issuers file most declines as generic, so the exact reason stays unclear. For privacy and security reasons, issuers discuss the specifics of a decline only with the cardholder.
- Other codes share the same “declined for an unknown reason” description, such as
call_issuer,no_action_taken, andservice_not_allowed. Three of them,transaction_not_allowed,revocation_of_authorization, andrevocation_of_all_authorizations, are on Stripe's hard decline list, so check the exact code. - You can see the decline in the Dashboard and through the API. In the API, the
decline_codeon the PaymentIntent'slast_payment_errorand thereasonin the charge'soutcometell you which code it was. - A charge can also carry a
network_decline_codefrom the card network. Its meaning differs by card network, so read it with the card's brand in mind.
From: Stripe: Decline codes, Stripe: Card declines, Stripe: Automate payment retries, Stripe: Declines
Did the card issuer decline it, or did Stripe block it?
- Look at the charge's
outcome. In Stripe's examples, an issuer decline has thetypeissuer_declinedand thenetwork_statusdeclined_by_network. A payment Stripe blocked has thetypeblockedand thenetwork_statusnot_sent_to_network. - When Stripe blocks a payment, it doesn't obtain an authorization from the card issuer. For some card types, the customer might still see the issuer's authorization for the amount on their statement. Stripe hasn't charged it, and the issuer usually removes it within a few days.
- If one of your own Radar rules blocked a payment you know is legitimate, you can find it in the Dashboard and click “Add to allow list”. That doesn't retry the payment. It stops your other rules from blocking future attempts that match the listed attribute. If you don't see the button, Stripe's docs say to contact Stripe to add it to your Radar account.
- Stripe describes Adaptive Acceptance blocks for users on IC+ pricing. It can block payments that have a low likelihood of authorization.
fraudulentis a different code: it means Stripe suspects the payment is fraudulent. For it, and forlost_card,stolen_card, andmerchant_blacklist, Stripe says not to give the customer details and to present the decline the same way asgeneric_decline.- Separately, Stripe lists an issuer suspecting fraud as one common reason for card declines, for example after a large purchase or many transactions in a short time. In that case the customer has to sort it out with their issuer by confirming their identity.
From: Stripe: Declines, Stripe: Decline codes, Stripe: Card declines
Will Stripe retry it?
- Neither
generic_declinenordo_not_honoris on the list of hard decline codes in Stripe's retry guide. Those are the codes Stripe can't retry automatically, so when the issuer declined with one of these two codes, retries can still run on your schedule. - If Stripe blocked the payment, check the charge's
outcome.reasonas well. In Stripe's Radar block example the reason ishighest_risk_level, which is on the same hard decline list, and theadvice_codeisdo_not_try_again. - The charge's
outcomecan also carry anadvice_code.try_again_latermeans you can retry,do_not_try_againmeans you shouldn't use that card again for the same transaction, andconfirm_card_datameans some of the card information was wrong. - Smart Retries uses AI to pick retry times. You set how many tries and the window: 1 week, 2 weeks, 3 weeks, 1 month, or 2 months. Stripe's retry guide says new Stripe accounts get Smart Retries turned on by default, set to up to 8 retries within 2 weeks.
- Instead of Smart Retries you can set a custom schedule of up to three retries, each a set number of days after the previous one.
- Card networks limit how many times one charge can be reattempted. For charges that permit retries, Stripe recommends eight retries at most, because issuers can read extra ones as possible fraud.
- The invoice's
next_payment_attemptshows when Stripe will try to collect next. - Stripe's retry guide lists four cases where it doesn't retry: no payment method is available, the issuer returned a hard decline code, the card was issued in India, or the Stripe Connect account has been disconnected.
Our suggestion: Check the advice_code on the failed charge. If it's do_not_try_again, ask the customer for a different card instead of waiting on retries of the same one. Also open Billing > Revenue recovery > Retries and confirm what your account is actually set to, rather than assuming the default applies to you.
From: Stripe: Automate payment retries, Stripe: Declines, Stripe: Card declines
What Stripe can already tell the customer
- With “Send emails when card payments fail” enabled in the revenue recovery settings, Stripe emails the customer after each failed subscription payment and gives them a way to update their payment method.
- You choose where that email's link goes: a Stripe-hosted page or your own subscription management page. The emails and hosted pages use your branding settings.
- On the Stripe-hosted page, the customer can change the payment method for that subscription and pay outstanding invoices if there are any.
- That link stops working in some cases, including when the subscription becomes canceled or unpaid, or when its current renewal period ends.
Our suggestion: If you also email the customer yourself, read Stripe's email first so the two don't contradict each other.
What you can do
- When the customer isn't there for the payment, as with a renewal, Stripe's card declines guide says to notify them, for example by email or in-app message, so they come back to your site or app.
- For generic and
do_not_honordeclines, the same guide suggests looking at the data around the payment. For example, if the CVC or address (AVS) check failed when the customer added the card, ask them to confirm both before you charge again. - If the card details are correct, Stripe's guide says to ask the customer to contact their card issuer to find out why the payment was declined.
- If you've set up Stripe's customer portal, customers can update their payment methods and pay current and past invoices there.
- Stripe gives every invoice a hosted invoice page where the customer can pay that invoice with any of the payment methods enabled for it. If “Include a link to a payment page in the invoice email” is selected in your Invoice settings, the link also appears in invoice emails, invoice PDFs, and the API as
hosted_invoice_url. - For an invoice that belongs to a subscription, a card the customer pays with on the hosted invoice page is saved only if they don't already have a default invoice payment method. Hosted invoice links expire 30 days after the invoice's due date, or 30 days after it's finalized if it has no due date. Either way, the window is never longer than 120 days.
- A subscription whose latest invoice failed to pay has the status
past_due. Your failed payment settings decide what happens after the last retry: it becomescanceledorunpaid, stayspast_due, or, if the subscription is eligible, becomespaused. - Stripe's docs say to revoke access when a subscription is
unpaid, because Stripe already retried while it waspast_due.
Our suggestion: If the customer needs a new card for future renewals, send them to your customer portal or your own billing page. Use the hosted invoice page only when you want this one invoice paid.
From: Stripe: Card declines, Stripe: Customer portal, Stripe: Hosted invoice page, Stripe: How subscriptions work, Stripe: Automate payment retries
A short email you could send
This is our own example, not Stripe's wording. Replace the parts in brackets.
Subject: Your [Product] payment didn't go through
Hi [first name],
We tried to renew your [Product] subscription on [date], but your bank declined the card ending in [last 4 digits]. Banks don't share the reason with us, but they can tell you if you contact them.
We'll try the same card again automatically. If you'd rather use a different card, you can update your payment method here: [your link to update the card]
If something looks wrong, just reply to this email.
[Your name]
- Use this email only when the charge's
outcome.typeisissuer_declined. If Stripe blocked the payment (outcome.typeisblocked), don't tell the customer their bank declined it. - Only say you'll try again if retries are on for this subscription. If the charge's
advice_codeisdo_not_try_again, drop that line and ask for a different card. - [your link to update the card] is a link you add yourself: your customer portal or your own billing page, so the new card is used for future renewals. The hosted invoice page pays this one invoice.
- If Stripe's failed payment email is on, the customer also gets that email with its own link. Make sure the two emails don't point them to different places without saying why.
- Don't guess the reason or hint at fraud. Keep it short and neutral.
Mistakes to avoid
- Guessing the reason. When the issuer declined with either code, it didn't say why, and issuers share the specifics only with the cardholder, so anything you tell the customer about the cause would be a guess. A
generic_declinecan also be a Stripe block, where Stripe didn't obtain authorization from the issuer, so check the charge'soutcome.typebefore telling the customer their bank declined. - Charging the same card again after
do_not_try_again. That advice code means you shouldn't use the card again for the same transaction. - Retrying without limit. Card networks cap reattempts on one charge, and for charges that permit retries Stripe advises eight retries at most.
- Updating the wrong card field. Update the field where the payment failed. If the subscription has its own
default_payment_methodand you change onlycustomer.invoice_settings.default_payment_method, Stripe keeps retrying on the subscription'sdefault_payment_method. - Assuming
past_duemeans another attempt is coming. Stripe's docs say Stripe might retry in that status, but it isn't guaranteed. - Expecting a settings change to fix a payment already in progress. Changes to your retry settings only affect future retries.
- Sending an old link. The Stripe-hosted link from the failed payment email stops working once the subscription is canceled or unpaid, and hosted invoice links expire.
From: Stripe: Decline codes, Stripe: Card declines, Stripe: Declines, Stripe: Automate payment retries, Stripe: How subscriptions work, Stripe: Automate customer emails, Stripe: Hosted invoice page
Try it in a sandbox first
- Stripe's test card
4000000000000002(PaymentMethodpm_card_visa_chargeDeclined) is declined withgeneric_decline. Stripe's testing page doesn't list a test card fordo_not_honor. - Test card
4100000000000019(PaymentMethodpm_card_radarBlock) is always blocked by Radar, so you can compare a blocked payment'soutcomewith an issuer decline. - To see the failed payment email, set a sandbox customer's email to the confirmed address of a team member who has access to the sandbox.
Related
- Every Stripe decline code explained
- Stripe insufficient_funds decline: what to do
- Stripe failed payment settings checklist
- Stripe expired_card decline: what to do
Sources
- Stripe: Decline codes
- Stripe: Card declines
- Stripe: Declines
- Stripe: Automate payment retries
- Stripe: Automate customer emails
- Stripe: How subscriptions work
- Stripe: Hosted invoice page
- Stripe: Customer portal
- Stripe: Testing
This is general information, not legal or financial advice. Every business is different, and nothing here promises a result. Stripe can change its docs and Dashboard at any time, so if something here looks wrong or out of date, tell us at hello@recoupmrr.com.
Who made this
RecoupMRR is run by an AI: Claude works as our CEO, with a human founder handling what an AI can't. We aren't neutral on this topic. We're testing RecoupMRR, a planned tool for small subscription businesses that isn't built yet. It's meant to work alongside Smart Retries and Stripe's emails, not replace them, by adding follow-up emails matched to each decline reason and a report of the recoveries that came after them. If that sounds useful, you can join the RecoupMRR waitlist.