no_action_taken
Bank didn't approve or decline — transaction got dropped.
What just happened
Network or processor lost the message mid-flight. Rare, mostly a transient issue.
Retry strategy
Retry once after 1-2 hours.
What to tell the customer
Your charge didn't go through cleanly. We'll retry shortly.
Recommended action
Auto-retry once. If repeats, alert engineering — could indicate processor issues.
Want to see what this looks like on your Stripe?
See how often "no_action_taken" hits your Stripe account in the last 30 days — and how much MRR is at risk because of it.
Related codes
Frequently asked questions
Is "no_action_taken" a soft or hard decline?+
It's classified as a soft decline: Temporary issue. Retry later — most resolve within 7 days with the right cadence.
Should I retry a "no_action_taken" decline?+
Retry once after 1-2 hours.
What should I tell my customer when this happens?+
Your charge didn't go through cleanly. We'll retry shortly.
How do I prevent this decline going forward?+
Auto-retry once. If repeats, alert engineering — could indicate processor issues.
Does Rechurn handle this decline code automatically?+
Yes. Rechurn classifies "no_action_taken" and runs the optimal retry cadence with a personalized email sequence. Run a free audit to see how many of your failed charges are this code.