fraudulent
Issuer or Stripe Radar flagged the charge as fraud.
What just happened
Either the bank or Stripe's fraud engine determined this is suspicious activity.
Retry strategy
Don't retry. Repeated attempts trigger penalties and chargebacks.
What to tell the customer
This transaction was flagged for fraud review. Please contact us if this is a mistake.
Recommended action
Halt all automation. Manual review by customer support — never re-attempt this card.
Want to see what this looks like on your Stripe?
See how often "fraudulent" 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 "fraudulent" 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 "fraudulent" decline?+
Don't retry. Repeated attempts trigger penalties and chargebacks.
What should I tell my customer when this happens?+
This transaction was flagged for fraud review. Please contact us if this is a mistake.
How do I prevent this decline going forward?+
Halt all automation. Manual review by customer support — never re-attempt this card.
Does Rechurn handle this decline code automatically?+
Yes. Rechurn classifies "fraudulent" 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.