Error codes
Soft decline
Stripe
no_action_taken
The card was declined for an unknown reason.
What does no_action_taken mean?
The no_action_taken decline is returned when the issuing bank neither approved nor declined the transaction. This is typically a transient system issue where the authorization request was received but not processed.
Is it a soft or hard decline?
Soft decline. The card is usually valid; the issuer just did not complete the authorization flow.
Common root causes
Transient issuer processing issue
Authorization timeout
Internal issuer system delay
Recommended recovery steps
Retry after 5–30 minutes
If still failing, wait several hours
Monitor for systemic issues across your account
How FlyCode handles no_action_taken
FlyCode detects transient issuer processing issues and times retries for when the bank's authorization system is most likely to complete action. This recovers transactions that would otherwise be lost to ambiguous issuer responses.
What does no_action_taken mean?
The no_action_taken decline is returned when the issuing bank neither approved nor declined the transaction. This is typically a transient system issue where the authorization request was received but not processed.
Is it a soft or hard decline?
Soft decline. The card is usually valid; the issuer just did not complete the authorization flow.
Common root causes
Transient issuer processing issue
Authorization timeout
Internal issuer system delay
Recommended recovery steps
Retry after 5–30 minutes
If still failing, wait several hours
Monitor for systemic issues across your account
How FlyCode handles no_action_taken
FlyCode detects transient issuer processing issues and times retries for when the bank's authorization system is most likely to complete action. This recovers transactions that would otherwise be lost to ambiguous issuer responses.
What does no_action_taken mean?
The no_action_taken decline is returned when the issuing bank neither approved nor declined the transaction. This is typically a transient system issue where the authorization request was received but not processed.
Is it a soft or hard decline?
Soft decline. The card is usually valid; the issuer just did not complete the authorization flow.
Common root causes
Transient issuer processing issue
Authorization timeout
Internal issuer system delay
Recommended recovery steps
Retry after 5–30 minutes
If still failing, wait several hours
Monitor for systemic issues across your account
How FlyCode handles no_action_taken
FlyCode detects transient issuer processing issues and times retries for when the bank's authorization system is most likely to complete action. This recovers transactions that would otherwise be lost to ambiguous issuer responses.
Understanding This Decline Code
Extended content body
Frequently Asked Questions
What does no_action_taken mean?
Should I retry no_action_taken?
Yes — after a short delay. Start with 5–30 minutes. Most no_action_taken declines resolve once the issuer's system completes the authorization cycle.
How does FlyCode recover no_action_taken?
FlyCode uses network-level data to time retries for when the issuer's authorization system is most likely to complete action, recovering transactions that fixed schedules miss during ambiguous issuer responses.
