Error codes
Soft decline
Stripe
do_not_try_again
The card was declined for an unknown reason.
What does do_not_try_again mean?
The do_not_try_again decline code is an explicit instruction from the issuing bank: stop attempting this transaction. Unlike most declines, this code tells the merchant directly that additional retries will not succeed and should not be attempted.
Is it a soft or hard decline?
Stripe classifies it as a soft decline in the sense that the card account may still be valid, but operationally it should be treated as a definitive stop signal on the current card.
Common root causes
Issuer policy flag preventing further attempts on this specific transaction
Internal account review requiring cardholder intervention
Repeated prior declines triggering a "stop billing" flag
Issuer compliance or regulatory hold
Recommended recovery steps
Respect the issuer instruction. Do not retry the same card for the same transaction.
Try a backup payment method on file immediately.
Route the customer to update payment details with clear messaging.
Avoid flagging the merchant by continuing to retry — doing so can hurt authorization rates across your entire account.
How FlyCode handles do_not_try_again
FlyCode recognizes do_not_try_again as a stop signal and immediately pivots recovery strategy: no further retries on the current card, automatic attempts on backup payment methods, and then a targeted customer outreach flow if needed. This approach preserves issuer trust in your merchant account while still maximizing recovery from each failed payment.
What does do_not_try_again mean?
The do_not_try_again decline code is an explicit instruction from the issuing bank: stop attempting this transaction. Unlike most declines, this code tells the merchant directly that additional retries will not succeed and should not be attempted.
Is it a soft or hard decline?
Stripe classifies it as a soft decline in the sense that the card account may still be valid, but operationally it should be treated as a definitive stop signal on the current card.
Common root causes
Issuer policy flag preventing further attempts on this specific transaction
Internal account review requiring cardholder intervention
Repeated prior declines triggering a "stop billing" flag
Issuer compliance or regulatory hold
Recommended recovery steps
Respect the issuer instruction. Do not retry the same card for the same transaction.
Try a backup payment method on file immediately.
Route the customer to update payment details with clear messaging.
Avoid flagging the merchant by continuing to retry — doing so can hurt authorization rates across your entire account.
How FlyCode handles do_not_try_again
FlyCode recognizes do_not_try_again as a stop signal and immediately pivots recovery strategy: no further retries on the current card, automatic attempts on backup payment methods, and then a targeted customer outreach flow if needed. This approach preserves issuer trust in your merchant account while still maximizing recovery from each failed payment.
What does do_not_try_again mean?
The do_not_try_again decline code is an explicit instruction from the issuing bank: stop attempting this transaction. Unlike most declines, this code tells the merchant directly that additional retries will not succeed and should not be attempted.
Is it a soft or hard decline?
Stripe classifies it as a soft decline in the sense that the card account may still be valid, but operationally it should be treated as a definitive stop signal on the current card.
Common root causes
Issuer policy flag preventing further attempts on this specific transaction
Internal account review requiring cardholder intervention
Repeated prior declines triggering a "stop billing" flag
Issuer compliance or regulatory hold
Recommended recovery steps
Respect the issuer instruction. Do not retry the same card for the same transaction.
Try a backup payment method on file immediately.
Route the customer to update payment details with clear messaging.
Avoid flagging the merchant by continuing to retry — doing so can hurt authorization rates across your entire account.
How FlyCode handles do_not_try_again
FlyCode recognizes do_not_try_again as a stop signal and immediately pivots recovery strategy: no further retries on the current card, automatic attempts on backup payment methods, and then a targeted customer outreach flow if needed. This approach preserves issuer trust in your merchant account while still maximizing recovery from each failed payment.
Understanding This Decline Code
Extended content body
Frequently Asked Questions
What does do_not_try_again mean?
Why should I not retry do_not_try_again?
The issuer explicitly instructs merchants to stop retrying. FlyCode treats this signal seriously — routing customers to backup payment methods or updated card details instead of continuing to retry the original card.
How does FlyCode recover do_not_try_again?
FlyCode treats do_not_try_again as a signal to stop retrying the current card and immediately route the customer to backup payment methods or a payment update flow — maximizing recovery while respecting issuer directives.

