Skip to content

Free tools / Stripe decline codes / stop_payment_order

Stripe stop_payment_order: when the customer stops payments at the bank

Stripe documents stop_payment_order only as a decline for an unknown reason, but on card networks the response usually means the cardholder asked their bank to stop payments to your business. It is less a payment problem than a cancellation signal: the customer chose to block you at the bank, instead of or as well as cancelling in your app.

Abderrahim Ben Jazia, PhDBy · Founder of FlowMRR, previously built and sold AIS (Avance Immédiate Services), French tax-credit softwareUpdated:
Decline code
stop_payment_order
Type
Blocked card
Who can fix it
The customer — needs to act
Will a retry help?
No: do not retry

What it means

Stripe gives no reason and says the customer should contact their bank. On card networks this response usually means the cardholder asked their bank to stop payments to you, but Stripe does not confirm it.

Lost, stolen, flagged or withdrawn. Do not retry: it can hurt your acceptance rate. Ask for a different card, through a neutral message.

Why it happens

  • The customer wanted to cancel and found it easier, or faster, to ask their bank.
  • The customer did not recognise the charge on their statement and asked the bank to stop it.
  • A billing disagreement or frustration with the service, sometimes alongside a dispute.
  • A forgotten subscription the customer believed was already cancelled.

What to do

  1. Do not retry: the bank will block every attempt, and charging against an explicit stop can lead to disputes.
  2. Check Stripe for disputes on earlier charges from the same customer and respond to any before the deadline.
  3. Reach out to understand what happened: did they mean to cancel, or did they not recognise the charge?
  4. If they meant to cancel, cancel the subscription in Stripe so no more invoices are created.
  5. If it was a mistake, ask them to lift the stop with their bank or pay another way through the hosted invoice link.
  6. Make sure your statement descriptor and cancellation flow are clear, so customers recognise your charges and can cancel without going through their bank.

Should you retry?

Never retry. The customer asked their bank to stop these payments. Charge again only if the customer contacts you, wants to continue, and lifts the stop or adds another payment method.

What to tell the customer

Short and neutral, ready for a checkout error, a billing page or a support reply. No placeholders — ready to paste.

Your bank declined this payment and asked us not to retry it. Please contact your bank, or pay with another card.

Customer email template

Neutral wording for this situation. Replace {name}, {product}, {link} and {company}.

Hi {name},

Your bank declined our latest payment for {product} and asked us not to retry it. If you meant to cancel, there is nothing more to do and we will close the subscription. If not, you can pay with another card here and keep your access: {link}

Thanks,
{company}

Handling many failed payments? See how FlowMRR helps you prioritize failed Stripe payments by revenue at risk. Want a ranked list from your own account? Try the free failed payment audit.

Try FlowMRR free

Frequently asked questions

stop_payment_order vs revocation_of_authorization: what is the difference?

Both come from the customer. stop_payment_order is a request to stop payments to you; revocation_of_authorization withdraws permission for this recurring payment, and revocation_of_all_authorizations does so for every recurring payment on the card. All three mean: stop charging and talk to the customer.

Should I count stop_payment_order as churn?

Treat it as a likely cancellation unless the customer tells you otherwise. Reach out while the invoice is still open, then cancel the subscription if they confirm.

Could the customer have done it by mistake?

Yes. People sometimes block a charge they do not recognise, especially when the statement descriptor does not match your product name. A short, friendly message can clear it up.

Contact us
FlowMRR

Let's talk

A question, a technical issue or an idea for a partnership? Write to the FlowMRR team.