security_violation
Issuer's fraud system detected a violation.
What just happened
Could be CVC failure, BIN mismatch, or velocity flag.
Retry strategy
Don't retry. Increases fraud-flag risk.
What to tell the customer
Your bank flagged a security issue. Please contact them or use a different card.
Recommended action
Manual review. Customer-success outreach.
Want to see what this looks like on your Stripe?
See how often "security_violation" hits your Stripe account in the last 30 days — and how much MRR is at risk because of it.
Related codes
Frequently asked questions
Is "security_violation" a soft or hard decline?+
It's classified as a fraud / risk: Issuer flagged the charge. Don't retry without customer contact — risks chargebacks.
Should I retry a "security_violation" decline?+
Don't retry. Increases fraud-flag risk.
What should I tell my customer when this happens?+
Your bank flagged a security issue. Please contact them or use a different card.
How do I prevent this decline going forward?+
Manual review. Customer-success outreach.
Does Rechurn handle this decline code automatically?+
Yes. Rechurn classifies "security_violation" and runs the optimal retry cadence with a personalized email sequence. Run a free audit to see how many of your failed charges are this code.