stop_payment_orderhighAffects MRR

Stripe stop_payment_order Error — Causes, Fix & MRR Impact

The Stripe stop_payment_order error occurs when the card issuer declines the transaction (e.g. due to a stop payment order), causing failed charges and MRR risk for SaaS businesses processing subscription payments.

What this means

The bank declined the charge (there may be a stop payment on the account). The customer should try again later, use another card, or contact their bank.

Why it happens

Stop payment by cardholder

The customer may have requested their bank to stop recurring or certain payments.

Issuer-initiated stop

The issuer placed a stop on the account or card (e.g. dispute or fraud).

Generic issuer decline

The issuer declined and the network returned stop_payment_order; exact reason not exposed.

Account status

Account or card status (e.g. closed, restricted) may result in this code.

MRR Impact

Declines reduce MRR; retries and dunning may recover some; customer may need to re-authorize or use another method.

Stop payment order is handled like generic; retries and update flow protect MRR.

Avg. recovery rate: Variable; retries and alternative payment method help.

Urgency: within 24h

How to fix it

  1. 1

    Include in retry logic

    Treat as retriable with backoff. Use advice_code when available.

  2. 2

    Show generic message

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

  3. 3

    Send dunning email

    Email that the payment did not go through and ask the customer to update their payment method or contact their bank.

  4. 4

    Offer payment method update

    Provide a link to add another card or switch payment method. Customer may have stopped the old card intentionally.

  5. 5

    Log and track

    Track stop_payment_order; if volume is high, consider messaging about managing subscriptions and payment methods.

Detect stop_payment_order automatically

Track stop_payment_order; compare with other generic declines.

Monitor your Stripe health free →

FAQ

What does Stripe stop_payment_order mean?
stop_payment_order means the card was declined for an unknown reason; the cardholder or issuer may have requested a stop on payments. Stripe recommends the customer contact their card issuer. For SaaS, treat like a generic decline: retry with backoff and show a generic message; send dunning.
Should I retry stop_payment_order?
You can retry with backoff; sometimes the stop is temporary or the customer will resolve with the bank. If retries fail, ask the customer to use another card or contact their issuer.
How do I message this?
Use a generic message: 'Your card was declined. Please try again later, use another card, or contact your card issuer for more information.'
Does stop_payment_order affect MRR?
Yes. Retries and dunning can recover some revenue; offering another payment method helps.

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 MRRrevocation_of_all_authorizations

The Stripe revocation_of_all_authorizations error occurs when the card issuer declines the transaction (possibly after revoking authorizations), 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