What does "do not honor" mean?

The do_not_honor decline code is one of the most common — and most frustrating — responses a subscription business will encounter. It is a generic decline issued by the cardholder's bank (the issuer) indicating that the transaction has been refused, but without specifying a clear reason.

Unlike more descriptive decline codes such as insufficient_funds or card_expired, "do not honor" gives the merchant almost no actionable information. The issuer may be flagging the transaction for a variety of internal reasons: unusual spending patterns, velocity checks, geographic mismatches, or risk thresholds that the cardholder is unaware of.

Why it matters for subscription businesses

For recurring billing, do_not_honor declines are especially damaging because they often affect customers who have no idea their payment failed. The subscriber's card is valid, they have sufficient funds, and they never intended to cancel — yet the payment is blocked. This makes it a leading driver of involuntary churn.

Because the decline is generic, standard retry logic may not resolve it. A payment that fails at 2 AM might succeed at 10 AM the next day simply because the issuer's risk model evaluates it differently. This is where smart retry strategies and AI-driven recovery tools like FlyCode become critical.

How to handle do_not_honor declines

The best approach combines intelligent retry timing, alternate payment method fallback, and proactive dunning communication. Rather than retrying immediately (which can trigger additional issuer flags), waiting and retrying at optimized intervals significantly improves recovery rates. FlyCode's AI analyzes decline patterns across the card network to determine the optimal retry window for each individual transaction.