no_action_takenmediumAffects MRR

Stripe no_action_taken Error — Causes, Fix & MRR Impact

The Stripe no_action_taken error occurs when the card issuer declines the transaction without specifying a reason, causing failed charges and MRR risk for SaaS businesses processing subscription payments.

What this means

The bank declined the charge and did not give a reason. The customer should try again later, use another card, or contact their bank.

Why it happens

Issuer did not specify reason

The issuer returned a generic decline code; the exact reason is not exposed to the merchant.

Temporary issuer condition

A temporary issue on the issuer side may resolve on retry.

Account or card status

The account may be under review or restricted; the issuer does not expose details.

Network or system

The decline was passed through as no_action_taken by the network or issuer.

MRR Impact

Generic declines reduce MRR; retries with backoff and dunning can recover a portion. Customer may need to contact issuer.

No action taken is a generic issuer decline; retries and clear messaging help protect MRR.

Avg. recovery rate: Variable; retries help; some cases require customer to contact the bank.

Urgency: within 24h

How to fix it

  1. 1

    Include in retry logic

    Treat no_action_taken as retriable. Schedule retries with exponential backoff and use advice_code when available.

  2. 2

    Show generic message

    Do not display 'no_action_taken'. Use: 'Your card was declined. Please try again, use another card, or contact your card issuer.'

  3. 3

    Send dunning email

    After the first failure, email the customer that the payment did not go through and ask them to verify their card or try another payment method.

  4. 4

    Log for analytics

    Track no_action_taken volume and recovery rate. Compare with do_not_honor and generic_decline to tune retry strategy.

  5. 5

    Escalate after max retries

    After your maximum retries, prompt the customer to contact their bank or update their payment method. Consider in-app banner for high-value accounts.

Detect no_action_taken automatically

Monitor no_action_taken rate; track recovery to tune retry and dunning.

Monitor your Stripe health free →

FAQ

What does Stripe no_action_taken mean?
no_action_taken means the card was declined for an unknown reason. The customer should contact their card issuer. For SaaS, treat like do_not_honor or generic_decline: retry with backoff and send dunning. Do not show the raw code to the customer.
Should I retry no_action_taken?
Yes, with backoff. Many such declines are temporary. Use your retry schedule (e.g. 1, 3, 5 days) and Stripe's advice_code if present. After max retries, ask the customer to contact their bank or use another card.
How do I message no_action_taken?
Use a generic message: 'Your card was declined. Please try again later, use another card, or contact your card issuer for more information.'
Does no_action_taken affect MRR?
Yes. Any decline can cause failed renewals. Retries and dunning improve recovery; track this code to see if it correlates with certain issuers or regions.

Related errors

do_not_honor

The Stripe do_not_honor error occurs when the card issuer declines the transaction without providing a specific reason, causing failed charges and MRR risk for SaaS businesses processing subscription payments.

Affects MRRgeneric_decline

The Stripe generic_decline error occurs when the card is declined for an unspecified reason or blocked by Stripe Radar or Adaptive Acceptance, causing failed charges and MRR risk for SaaS businesses processing subscription payments.

Affects MRR