Error codes
Hard decline
Stripe
stop_payment_order
The card was declined for an unknown reason.
What does stop_payment_order mean?
The stop_payment_order decline code is returned when the cardholder has instructed their issuing bank to block this specific charge. Unlike a revocation of authorization (which is forward-looking), a stop payment is typically placed against a specific amount, merchant, or recurring cycle. It usually reflects a customer dispute with the merchant that didn't get resolved directly.
Is it a soft or hard decline?
stop_payment_order is a hard decline. The block is deliberate and enforced at the issuer level. Retries will keep failing, and continuing to retry can increase the chance of the customer filing a formal chargeback.
Common root causes
Customer couldn't cancel through the merchant's flow and called the bank instead
A dispute over a charge the customer considers unauthorized or incorrect
Customer didn't recognize the descriptor on their statement
Billing expectations weren't set clearly at signup (e.g., trial auto-conversion)
Failed service delivery leading to a payment stop
Recommended recovery steps
Stop retrying immediately. Each failed attempt increases chargeback risk. The issuer won't change its mind until the customer releases the stop.
Reach out directly. A timely, helpful customer support contact can often resolve the underlying issue and the customer may re-authorize the charge.
Clarify your descriptor. Unrecognized descriptors are a leading cause of stop payments. Make sure yours is clear and branded.
Offer alternative payment methods. If the relationship is salvageable, a different payment method bypasses the block.
How FlyCode handles stop_payment_order
FlyCode classifies stop_payment_order as a hard decline and halts retry logic to avoid wasted attempts and chargeback exposure. The AI outreach engine contacts the customer through the channel and timing most likely to resolve the underlying complaint, requesting an alternate payment method if the relationship can be preserved. This approach protects both the merchant's processing standing and the customer relationship.
What does stop_payment_order mean?
The stop_payment_order decline code is returned when the cardholder has instructed their issuing bank to block this specific charge. Unlike a revocation of authorization (which is forward-looking), a stop payment is typically placed against a specific amount, merchant, or recurring cycle. It usually reflects a customer dispute with the merchant that didn't get resolved directly.
Is it a soft or hard decline?
stop_payment_order is a hard decline. The block is deliberate and enforced at the issuer level. Retries will keep failing, and continuing to retry can increase the chance of the customer filing a formal chargeback.
Common root causes
Customer couldn't cancel through the merchant's flow and called the bank instead
A dispute over a charge the customer considers unauthorized or incorrect
Customer didn't recognize the descriptor on their statement
Billing expectations weren't set clearly at signup (e.g., trial auto-conversion)
Failed service delivery leading to a payment stop
Recommended recovery steps
Stop retrying immediately. Each failed attempt increases chargeback risk. The issuer won't change its mind until the customer releases the stop.
Reach out directly. A timely, helpful customer support contact can often resolve the underlying issue and the customer may re-authorize the charge.
Clarify your descriptor. Unrecognized descriptors are a leading cause of stop payments. Make sure yours is clear and branded.
Offer alternative payment methods. If the relationship is salvageable, a different payment method bypasses the block.
How FlyCode handles stop_payment_order
FlyCode classifies stop_payment_order as a hard decline and halts retry logic to avoid wasted attempts and chargeback exposure. The AI outreach engine contacts the customer through the channel and timing most likely to resolve the underlying complaint, requesting an alternate payment method if the relationship can be preserved. This approach protects both the merchant's processing standing and the customer relationship.
What does stop_payment_order mean?
The stop_payment_order decline code is returned when the cardholder has instructed their issuing bank to block this specific charge. Unlike a revocation of authorization (which is forward-looking), a stop payment is typically placed against a specific amount, merchant, or recurring cycle. It usually reflects a customer dispute with the merchant that didn't get resolved directly.
Is it a soft or hard decline?
stop_payment_order is a hard decline. The block is deliberate and enforced at the issuer level. Retries will keep failing, and continuing to retry can increase the chance of the customer filing a formal chargeback.
Common root causes
Customer couldn't cancel through the merchant's flow and called the bank instead
A dispute over a charge the customer considers unauthorized or incorrect
Customer didn't recognize the descriptor on their statement
Billing expectations weren't set clearly at signup (e.g., trial auto-conversion)
Failed service delivery leading to a payment stop
Recommended recovery steps
Stop retrying immediately. Each failed attempt increases chargeback risk. The issuer won't change its mind until the customer releases the stop.
Reach out directly. A timely, helpful customer support contact can often resolve the underlying issue and the customer may re-authorize the charge.
Clarify your descriptor. Unrecognized descriptors are a leading cause of stop payments. Make sure yours is clear and branded.
Offer alternative payment methods. If the relationship is salvageable, a different payment method bypasses the block.
How FlyCode handles stop_payment_order
FlyCode classifies stop_payment_order as a hard decline and halts retry logic to avoid wasted attempts and chargeback exposure. The AI outreach engine contacts the customer through the channel and timing most likely to resolve the underlying complaint, requesting an alternate payment method if the relationship can be preserved. This approach protects both the merchant's processing standing and the customer relationship.
Understanding This Decline Code
Extended content body
Frequently Asked Questions
Is stop_payment_order a soft or hard decline?
Should I retry stop_payment_order?
No. Retries won't succeed and can escalate the dispute to a chargeback. Resolve the underlying issue with the customer and collect a different payment method instead.
How does FlyCode handle stop_payment_order?
FlyCode treats stop_payment_order as a hard decline, halts retries immediately, and triggers proactive customer outreach to collect a different payment method — protecting the merchant from chargebacks.
