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.

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.

Recoverly retries at 2, 5, 10 and 20 days, up to 4 attempts within a 30-day window.

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

Recoverly retries up to 4 times within 30 days. This page is informational and not affiliated with Stripe.