Security Violation
What This Means
The bank has flagged a security violation on this transaction or card. This is a serious fraud indicator suggesting the card or transaction has been compromised. SaaS businesses should stop retries and review the account carefully.
Retrying will likely fail again. The customer needs to update their payment method or contact their bank.
Common Causes
- 1Card data was compromised and the bank detected unauthorized access
- 2Transaction triggered the bank's security protocols (e.g., velocity checks)
- 3Card is associated with a known fraud ring or compromised merchant
Recovery Tactics
- 1Stop all retry attempts immediately
- 2Flag the account for manual security review
- 3If the customer is verified as legitimate, ask them to use a different card
- 4Review your Stripe Radar rules to catch similar patterns earlier
How healthy is your Stripe account?
Get a free churn health report. Find pending cancellations, failed payments, and expiring cards putting your MRR at risk.
Run Free AuditRelated Decline Codes
FAQ
Does this mean my system was breached?
No. This decline code comes from the issuing bank and relates to the card, not your system. The security violation could have occurred at any merchant or through a data breach unrelated to your business.
Should I report this to Stripe?
Stripe is already aware of the decline through the normal transaction flow. However, if you see a pattern of security violations, contact Stripe support to review whether your Radar rules need adjustment.
How healthy is your Stripe account?
Get a free churn health report. Find pending cancellations, failed payments, and expiring cards putting your MRR at risk.
Run Free Audit