do_not_honorNeeds customer actionStripe decline code: Do not honor
The issuer refused the charge without a specific reason.
Recovery outlook
Needs customer action. The card or account details need to change, or the customer must clear something with their bank. Recovery runs through dunning, not blind retries.
What it means
The bank has chosen not to honor the transaction. Like card_declined, it's a generic refusal, but it usually signals a decision on the issuer's side rather than a data problem.
Why it happens
Common triggers are risk rules, spending controls, a temporary hold, or the cardholder needing to approve or unblock activity with their bank.
Can you retry it?
There's nothing to fix in your integration. A later retry occasionally clears if the hold was temporary, but the dependable recovery is customer-driven: they either resolve it with their bank or pay with another card.
Recovery playbook
- 1Retry once after a delay. Some do_not_honor holds lift on their own.
- 2Trigger dunning that asks the customer to authorize with their bank.
- 3Provide a fast switch to an alternate card.
- 4Stop after a couple of attempts to avoid fraud-signal buildup.
How Reecova handles do_not_honor
Reecova flags do_not_honor as needing customer action and triggers a dunning sequence to collect an updated card or prompt the bank contact, rather than wasting retry attempts. It runs across your whole Stripe account automatically, and shows the dollars each code is costing you.