Stripe decline code
no_action_taken
The issuer didn't act on the authorization request — effectively a non-response that's treated as a decline.
Primary source: Stripe’s official decline codes reference
Why it happens
- A transient non-response on the issuer side.
- Verification that wasn't completed in time.
- A temporary processing glitch.
Should you retry it?
Sometimes — it depends on the issuer
Because nothing was decided, a later retry can succeed. Retry on a measured schedule.
How to recover it
Retry on a moderate schedule. Reach out to the customer only if attempts keep failing.
Let Stripe's retry schedule run first. For invoices that stay unpaid after it ends, Recoverly opens a case and — with your approval — sends a 3-step payment-update sequence (Day 0 / 3 / 7) linking to Stripe's hosted payment page.
See how much failed-payment revenue you can recover
Connect Stripe (we only read) and Recoverly shows your recoverable revenue in 30 seconds.
Related decline codes
Written by the Recoverly team · Published June 25, 2026 · Last reviewed July 17, 2026
Recoverly finds invoices Stripe’s retries left unpaid and — with your approval — sends payment-update emails, then verifies what actually came back. This page is informational and not affiliated with Stripe.