Stripe do_not_try_again: What It Means and How to Handle It
do_not_try_again is an explicit network instruction that retrying will not work. It is a hard decline that requires immediate customer contact for new payment details.
Contents
do_not_try_again is an explicit instruction from the card network or issuing bank that retrying the charge will not succeed. Unlike soft declines where timing and conditions change, do_not_try_again means the bank has made a definitive determination. The only path forward is new payment information from the customer.
What does do_not_try_again mean?
do_not_try_again maps to specific ISO 8583 network codes that issuers use to signal a permanent decline. Like lost_card and stolen_card, it is a hard decline that requires immediate customer contact rather than retries. The bank is not declining because of a temporary condition. It is declining and explicitly instructing the merchant not to retry.
Common underlying causes include the account being permanently closed, the card being permanently blocked, or the bank having flagged the card for activity that precludes further charges from any merchant.
This is a hard decline. Treat it as permanent.
Why retrying is specifically harmful here
Card networks track merchant retry behavior. Retrying after a do_not_try_again code is a direct violation of network retry rules. Mastercard and Visa can levy fines on merchants who retry charges after receiving explicit do-not-retry signals. The fine structure starts at $1,000 per occurrence for systematic violations.
Unlike generic_decline where a retry might succeed, do_not_try_again will not succeed on any retry. There is no benefit and meaningful downside risk.
How to handle do_not_try_again
Step 1: Stop all retries immediately. Do not retry under any circumstances.
Step 2: Email the customer on day 1. The customer needs to provide new payment details. Their current card cannot be charged. A direct email explaining their payment method needs to be updated is the right first response. Hard decline sequences fire immediately with no retries, unlike soft declines where retries come first.
Step 3: Follow up at day 5 and day 12. Two follow-ups catch customers who missed the first email or who needed time to get a new card.
Step 4: If payment is not resolved after 21 days, pause or cancel. At that point the customer either does not have a replacement card available or has disengaged. Pause the subscription with clear communication rather than a silent cancellation.
- What does do_not_try_again mean on Stripe?
- An explicit instruction from the card network or issuing bank that the charge will not succeed on a retry. It is a permanent hard decline.
- Can I retry a do_not_try_again decline?
- No. Retrying after this code violates card network rules and can result in fines. Stop retries immediately.
- What should I do after a do_not_try_again decline?
- Email the customer on day 1 asking them to update their payment method with a new card. Follow up at day 5 and day 12.
- How is do_not_try_again different from generic_decline?
- generic_decline is a soft decline that often resolves on a retry. do_not_try_again is an explicit hard decline with a network-level instruction not to retry. The response is completely different: retry for generic_decline, email immediately for do_not_try_again.
