Do not honor: how to recover the payment
Quick answer
`do_not_honor` is a generic issuer refusal: the bank declined the charge without stating a reason, so the underlying cause has to be inferred from context.
Worth retrying? Sometimes — a small number of spaced retries is worth attempting.
Why this decline happens
- The issuer's own risk model flagged the transaction, often because the merchant or amount was unfamiliar.
- Internal limits, holds, or account-level restrictions the issuer will not disclose.
- Cross-border or currency characteristics the issuer treats as higher risk.
- Occasionally a soft balance or fraud check that clears on its own within a few days.
Retry strategy that fits this code
- Treat this as a low-confidence retry: worth a small number of spaced attempts, not an aggressive schedule.
- Vary the timing rather than the amount — repeatedly re-presenting the same charge within a day reinforces the issuer's refusal.
- If two spaced retries fail, switch to a customer-facing path such as a different payment method.
- Track do_not_honor rates by issuer; a spike in one bank usually signals a risk-model change, not a customer problem.
What to tell the customer
- Never tell the customer their bank thinks they are fraudulent — you do not know that.
- Say the bank declined the payment without a reason and suggest contacting the bank or using another card.
- Keep the tone neutral; this code frequently hits good long-term customers.
Frequently asked
- What does do not honor actually mean?
- It is the card network's catch-all refusal code. The issuer chose not to approve the charge and did not disclose why, so no specific remedy can be derived from the code alone.
- Will contacting the bank help?
- Often yes. Cardholders can usually get the block lifted in one call, which is why a message that suggests it converts better than silent retries.
Handling this at scale, not one invoice at a time
A single decline code is easy to handle manually. A steady stream of them across different customers, invoice values, and failure reasons is a workflow problem. RRLabs classifies each failure, scores the recovery opportunity, and recommends the next best action — then attributes recovered revenue only once your billing provider confirms the payment succeeded.