Guide
A Stripe renewal was declined. What do_not_honor, insufficient_funds and the other decline codes mean, and what to do about each
A customer on a $49 monthly plan renews overnight. In the morning the invoice is open, the subscription is past due, and the payment says declined: do_not_honor. That code sounds final and it isn't. It also doesn't say much. Most decline codes tell you one useful thing: whether waiting will fix it, or whether the customer has to do something. That is the only decision you need to make.
Where to find the code
Open the failed payment in the Stripe Dashboard: it shows the decline reason and a short suggested next step. In the API the same information is on the charge, in outcome.reason, and Stripe adds an advice_code with one of three values: try_again_later (you can retry), do_not_try_again (don't use this card again for this payment) and confirm_card_data (some card details are wrong). For a subscription, the invoice also shows the attempt count and the date of the next retry. Read the advice code first. It is the closest thing to a straight answer the bank gives.
The codes that usually fix themselves
insufficient_funds means what it says: the card or account didn't have enough available on that day. On a debit card that is often just timing, before payday, and a retry a few days later goes through. issuer_not_available, processing_error and reenter_transaction mean the bank or the network didn't answer properly; Stripe's own advice for those is to try again. These are the cases Smart Retries are built for. Stripe's recommended default is 8 tries within 2 weeks, timed by its model rather than on fixed days.
The vague ones: do_not_honor and generic_decline
Stripe's decline code reference describes do_not_honor as declined for an unknown reason, and generic_decline the same way. It adds that generic_decline can also mean Stripe Radar or Adaptive Acceptance blocked the payment, so it isn't always the bank. Stripe says most issuer declines are generic, and that banks only discuss the specific reason with their cardholder. That is why the next step Stripe gives for both is the same: the customer needs to contact their card issuer. In practice, let the retries run, and send the customer a short note at the same time asking them to check with their bank or use another card. Don't wait for the last retry before telling them.
The codes retries cannot fix
Stripe's retry documentation lists the hard declines it will not retry automatically: incorrect_number, lost_card, pickup_card, stolen_card, revocation_of_authorization, revocation_of_all_authorizations, authentication_required, highest_risk_level and transaction_not_allowed. For these, Stripe keeps the retries on the schedule and the attempt count keeps going up, but no charge is actually made until the customer adds a new payment method. expired_card belongs in the same practical group: Stripe's advice is that the customer needs to use another card. If you see any of these, the retries are not doing anything for you. Only the customer can fix it, so ask them now.
What to tell the customer, and what not to
Keep it short and blame nobody: the renewal didn't go through, here is the link to update the card, the account stays open while they do. Stripe is explicit that for fraudulent, lost_card, stolen_card and merchant_blacklist you should not pass on the detailed reason; present it to the customer as a generic decline. Never tell a customer their card was reported stolen. For authentication_required, which shows up on renewals for cards that need 3D Secure, the customer has to come back and confirm the payment themselves, so the note should send them to the invoice page rather than just ask for a new card.
What happens if every retry fails
You choose it in Billing, Revenue recovery, Retries. After the last attempt the subscription is cancelled, marked unpaid (invoices keep being created and stay in draft), left past due (invoices keep trying on the retry settings), or paused if it is eligible. Stripe makes no further attempts after the final one, and changing the setting only affects future retries. Cancelling is the tidy option and the costly one: a customer who never decided to leave is now counted as churn. These are customers lost to failed cards, and they are the cheapest customers to win back, because they still want the product.
What a declined renewal does to payouts and the books
Nothing moved, so nothing is in a payout. A declined charge never settles, so it creates no balance transaction and never appears inside a payout; your next deposit is simply smaller than you expected, with no line explaining the difference. That is why failed payments are easy to miss from the bank side. In the books, it depends on how you record Stripe. If you record revenue from payouts or from paid charges, there is nothing to book until the money arrives. If your bookkeeper records revenue when the Stripe invoice is issued, the open invoice is money owed to you, and if the retries fail and you void it or mark it uncollectible, that entry has to be reversed or written off in the same month, or revenue is overstated.
See the ones the retries didn't recover
Conciliq reads your Stripe account with a read-only key every morning. Alongside the payout check, it lists failed payments that Stripe's retries did not recover, with the customer, the amount and the number of attempts, and drafts a short note you send from your own email. You decide who gets it. We can see your data, never touch it.
Check yours
Does the money Stripe paid you match your books?
Upload a Stripe export or paste a read-only key. Every payout in the last 90 days, matched to the cent, usually in under a minute. Nothing stored.
Run the free audit →Questions people ask
- What does do_not_honor mean on a Stripe payment?
- That the customer's bank declined the payment without giving a reason. Stripe's next step is for the customer to contact their card issuer. On a subscription renewal, let Stripe's retries run and ask the customer at the same time to check with their bank or add another card.
- Will Stripe retry a declined subscription payment?
- Yes, if retries are set up in Billing, Revenue recovery, Retries. Stripe recommends Smart Retries with 8 tries within 2 weeks. It does not actually retry hard declines such as lost_card, stolen_card, pickup_card, incorrect_number, authentication_required or transaction_not_allowed until the customer adds a new payment method.
- Does a failed Stripe payment show up in my payout?
- No. A declined charge never settles, so it has no balance transaction and is not part of any payout. The payout is just smaller than the sales you expected. If your books record revenue when the invoice is issued, reverse or write off invoices that are never paid.
More guides
- Why your Stripe payout doesn't match your sales (and how to check it)
- QuickBooks' Stripe connector imports payouts, not fees. Here is what that does to your books
- Stripe payout breakdown: what every line inside a payout means
- Why a Stripe refund comes out of a later payout
- How a Stripe dispute hits your payout, and how to record it in your books
- A customer's card expires before their next Stripe renewal. What happens, and what to do
- Stripe debited your bank account. Why your balance went negative, and how to book it
- Stripe says the payout is Paid, but the money isn't in your bank. What each payout status means, and what to do
- How to reconcile Stripe payouts in Xero: what Xero matches on its own, and what it can't
- Stripe put a reserve on your account. What it does to your payouts, when the money comes back, and how to book it
- You charged in euros or pounds and Stripe paid you in dollars. Where the conversion fee went, and how to reconcile it
- Your Stripe 1099-K is bigger than the money that hit your bank. Why, and how to tie it to your books
- When does Stripe pay you? The payout schedule, the first-payout wait, and what each setting does to your books
- How to record Stripe payouts and fees in QuickBooks Online by hand: the clearing account method, step by step
- How to read Stripe's payout reconciliation report: what each section means, which download to use, and how to tie every deposit to your books
- Your Stripe payout includes sales tax you owe. How to record it in QuickBooks, and why Stripe's tax report won't match your deposits
- A customer paid a year upfront through Stripe. How to record it in QuickBooks so one month doesn't look like a record
- Stripe sent an early fraud warning. Should you refund the charge or wait, and what each choice does to your payout
- Why your Stripe fees are more than 2.9% + 30¢, and how to find what each extra charge is
- A Stripe ACH payment looked paid, then failed days later. Why it happens, what it does to your payout, and how to book it
- A customer paid a Stripe invoice by check or bank transfer. How to mark it paid, why it never shows up in a payout, and how to book it
- You gave a customer a Stripe coupon. What it does to the charge, the fee and the payout, and how to record the discount in QuickBooks
- A Stripe refund failed. Where the money went, why your payout is suddenly bigger, and how to get the customer paid
- Hundreds of small Stripe payments failed overnight. What a card testing attack is, what to do first, and what it does to your payouts and books
- A customer downgraded or cancelled and Stripe gave them a credit, not a refund. Where the money is, why your next payout is smaller, and how to book it
- QuickBooks shows double your Stripe income. Why the sync app and the bank feed both recorded it, and how to fix it
- Stripe says a subscription is incomplete, past due, unpaid or paused. What each status means for the customer, your payouts and your books
- You took Stripe Capital financing and your payouts got smaller. How the repayment works, and how to record it in QuickBooks or Xero
- You took a Stripe Instant Payout and now nothing reconciles. How to match instant payouts, their fee and the smaller payouts after them
- Stripe fee calculator: what your payouts really cost