Stripe decline code
security_violation
The issuer declined the charge for a security reason.
Quick answer
security_violation is a hard decline. Retrying will keep failing; the customer has to act.
| Decline code | security_violation |
|---|---|
| Type | Hard (needs customer action) |
| Retrying helps? | No |
| Category | Fraud or security |
| Customer fix | Contact the bank or use a different card. |
Will retrying help?
No, retrying will keep failing
Email the customer to contact their bank or switch cards; do not keep retrying.
A real example
The issuer declines the charge for an unspecified security reason.
What the customer needs to do
Contact the bank or use a different card.
Your recovery approach
Email the customer to contact their bank or switch cards; do not keep retrying.
Copy-paste recovery email
Subject
Quick check on your [Product] payment
Your bank flagged our charge as suspicious, even though it is your legitimate [Product] renewal.
Please confirm the charge with your bank, or add a different card below, and we will get you sorted.
Recover security_violation declines on autopilot
SubRevival reads every decline code and responds correctly, retrying soft declines on smart timing and emailing customers for hard ones, with a hosted card update page. $19/mo flat.
FAQ
What does the Stripe "security_violation" decline code mean?
The issuer declined the charge for a security reason.
Will retrying a "security_violation" decline work?
No. security_violation is a hard decline, so retrying the same card will keep failing. Email the customer to contact their bank or switch cards; do not keep retrying.
How do I recover a payment that failed with "security_violation"?
Email the customer to contact their bank or switch cards; do not keep retrying. Customer action: Contact the bank or use a different card.
Related decline codes
Source: official Stripe decline codes documentation. Recovery guidance is SubRevival's own.