Error codes
Soft decline
Stripe
restricted_card
The customer can't use this card to make this payment (it's possible it was reported lost or stolen).
What does restricted_card mean?
The restricted_card decline code is returned when the issuing bank has placed one or more restrictions on the card that block this specific transaction. The card is valid and active, but the issuer has flagged it with rules that prevent the charge from going through as attempted.
Is it a soft or hard decline?
restricted_card is a soft decline. Restrictions can be lifted by the issuer or bypassed with a different card, so recovery is often possible through retries, account updates, or customer outreach — the underlying account is not closed.
Common root causes
International transaction blocks — the card is restricted from charges outside the cardholder's home country
Merchant category restrictions — corporate or parental controls blocking subscription or digital merchants
Temporary holds placed by the issuer after suspicious activity elsewhere
Recurring payment blocks set up by the cardholder
Travel or fraud alerts that have not been cleared
Recommended recovery steps
Retry intelligently. Some restrictions are time-based or triggered by velocity, and a well-timed retry can succeed once the issuer's flag clears.
Request a backup payment method. If the restriction is persistent (e.g., a corporate card policy), the customer will need to provide a different card.
Use network tokens and route through the right acquirer. Acquirer and BIN routing sometimes resolves restriction mismatches transparently.
Prompt the customer to contact their bank. Many restrictions can be lifted instantly with a phone call — but this should be a last resort since it adds friction.
How FlyCode handles restricted_card
FlyCode's per-merchant ML models recognize the patterns behind restricted_card declines and distinguish between temporary restrictions (where smart retries work) and persistent ones (where customer action is needed). For persistent cases, FlyCode's outreach engine requests an alternate payment method at the optimal moment, maximizing response rates while minimizing subscription churn.
What does restricted_card mean?
The restricted_card decline code is returned when the issuing bank has placed one or more restrictions on the card that block this specific transaction. The card is valid and active, but the issuer has flagged it with rules that prevent the charge from going through as attempted.
Is it a soft or hard decline?
restricted_card is a soft decline. Restrictions can be lifted by the issuer or bypassed with a different card, so recovery is often possible through retries, account updates, or customer outreach — the underlying account is not closed.
Common root causes
International transaction blocks — the card is restricted from charges outside the cardholder's home country
Merchant category restrictions — corporate or parental controls blocking subscription or digital merchants
Temporary holds placed by the issuer after suspicious activity elsewhere
Recurring payment blocks set up by the cardholder
Travel or fraud alerts that have not been cleared
Recommended recovery steps
Retry intelligently. Some restrictions are time-based or triggered by velocity, and a well-timed retry can succeed once the issuer's flag clears.
Request a backup payment method. If the restriction is persistent (e.g., a corporate card policy), the customer will need to provide a different card.
Use network tokens and route through the right acquirer. Acquirer and BIN routing sometimes resolves restriction mismatches transparently.
Prompt the customer to contact their bank. Many restrictions can be lifted instantly with a phone call — but this should be a last resort since it adds friction.
How FlyCode handles restricted_card
FlyCode's per-merchant ML models recognize the patterns behind restricted_card declines and distinguish between temporary restrictions (where smart retries work) and persistent ones (where customer action is needed). For persistent cases, FlyCode's outreach engine requests an alternate payment method at the optimal moment, maximizing response rates while minimizing subscription churn.
What does restricted_card mean?
The restricted_card decline code is returned when the issuing bank has placed one or more restrictions on the card that block this specific transaction. The card is valid and active, but the issuer has flagged it with rules that prevent the charge from going through as attempted.
Is it a soft or hard decline?
restricted_card is a soft decline. Restrictions can be lifted by the issuer or bypassed with a different card, so recovery is often possible through retries, account updates, or customer outreach — the underlying account is not closed.
Common root causes
International transaction blocks — the card is restricted from charges outside the cardholder's home country
Merchant category restrictions — corporate or parental controls blocking subscription or digital merchants
Temporary holds placed by the issuer after suspicious activity elsewhere
Recurring payment blocks set up by the cardholder
Travel or fraud alerts that have not been cleared
Recommended recovery steps
Retry intelligently. Some restrictions are time-based or triggered by velocity, and a well-timed retry can succeed once the issuer's flag clears.
Request a backup payment method. If the restriction is persistent (e.g., a corporate card policy), the customer will need to provide a different card.
Use network tokens and route through the right acquirer. Acquirer and BIN routing sometimes resolves restriction mismatches transparently.
Prompt the customer to contact their bank. Many restrictions can be lifted instantly with a phone call — but this should be a last resort since it adds friction.
How FlyCode handles restricted_card
FlyCode's per-merchant ML models recognize the patterns behind restricted_card declines and distinguish between temporary restrictions (where smart retries work) and persistent ones (where customer action is needed). For persistent cases, FlyCode's outreach engine requests an alternate payment method at the optimal moment, maximizing response rates while minimizing subscription churn.
Understanding This Decline Code
Extended content body
Frequently Asked Questions
Is restricted_card a soft or hard decline?
Why would an issuer restrict a card?
Common reasons include international transaction blocks, merchant category restrictions, parental controls, corporate card policy limits, or temporary holds placed after suspicious activity.
How does FlyCode recover restricted_card declines?
FlyCode uses network-level signals to identify when a restriction is temporary and retries at optimal times. When customer action is required, it triggers AI-driven outreach to request a backup payment method.
