security_violationDo not retryStripe decline code: Security violation
The issuer declined for a security reason.
Recovery outlook
Do not retry. A hard or fraud-flagged decline. Retrying wastes attempts and can raise your fraud signals. Flag it and move to a new payment method.
What it means
The issuer flagged the charge as a security violation and declined it.
Why it happens
A fraud or security rule tripped on the issuer side. Suspicious pattern, mismatch, or a protective block.
Can you retry it?
Retrying a security-flagged charge can deepen the block and hurt your risk profile. The customer must clear it with their bank or use another card.
Recovery playbook
- 1Do not retry. It can escalate the flag.
- 2Ask the customer to verify with their issuer.
- 3Offer an alternate payment method.
- 4Review your own fraud signals if these cluster.
How Reecova handles security_violation
Reecova marks security_violation as a hard decline, stops retries so you don't stack fraud signals, and surfaces it for a clean payment-method switch or write-off. It runs across your whole Stripe account automatically, and shows the dollars each code is costing you.