Stripe fraudulent: What It Means and How to Handle It
fraudulent is a hard decline from Stripe Radar. Do not retry. Do not send a standard dunning email. Review the account before taking any action.
Contents
fraudulent means Stripe Radar blocked the charge because it detected a high probability of fraud. This is a hard decline. The charge will not succeed on a retry. The response is different from every other decline code because the card itself may be stolen.
What does fraudulent mean on Stripe?#
fraudulent appears when Stripe’s Radar fraud detection system blocks a charge, or when the issuing bank declines and indicates the transaction is suspected fraud. In both cases, the result is the same: the charge is declined and should not be retried.
This is not a temporary condition. Radar blocks charges based on risk signals including velocity patterns, device fingerprints, IP reputation, card BIN analysis, and the collective fraud intelligence across Stripe’s merchant network. A fraudulent decline means Radar assessed the risk as too high to let through.
Why you should not retry a fraudulent decline#
Retrying a charge that Radar blocked tells Radar you want to override its risk assessment. Repeated retries on a blocked charge can trigger Stripe account-level flags and, in extreme cases, increase your fraud score across the platform.
If the card is genuinely stolen, retrying also means attempting to charge a fraudster rather than your customer. The customer will eventually dispute any successful charge, and you will lose.
How to handle fraudulent#
Step 1: Stop all retries. No retry will change Radar’s risk assessment unless you modify your Radar rules or the underlying risk signals change.
Step 2: Review the account for fraud signals. Before taking any action, check the account for indicators that it was created with a stolen card: recent account creation, unusual usage patterns, multiple declined cards on the account, mismatched billing and shipping addresses, or a known high-risk IP or country.
Step 3: If the account looks suspicious, do not email. Sending a dunning email to a fraudulent account alerts the fraudster that the charge was blocked. Flag the account for manual review instead.
Step 4: If the account looks legitimate, investigate. Legitimate customers occasionally get caught by Radar rules that are too aggressive on subscription renewals. A well-configured billing descriptor can also reduce fraudulent dispute volume by ensuring customers recognize legitimate charges. If the customer has a long history of successful charges and clean account activity, the block may be a false positive. Check your Radar rules and consider whether adjustments are warranted.
Step 5: If it is a legitimate customer, contact them directly. If you determine the account is legitimate and the Radar block appears to be a false positive, reach out to the customer via email or in-app and ask them to contact their bank or try a different payment method.
What Foxhound does with fraudulent#
Foxhound classifies fraudulent as a hard decline and suppresses all retries. Accounts with fraud signals are flagged for manual review. Accounts without fraud signals that appear to be legitimate false positives are routed to a manual outreach queue rather than the standard dunning sequence.
- What does fraudulent mean on Stripe?
- Stripe Radar blocked the charge due to high fraud risk, or the issuing bank indicated suspected fraud. It is a hard decline.
- Can I retry a fraudulent decline?
- No. Retrying will not succeed and repeated attempts against a Radar-blocked charge can affect your fraud score. Stop retries immediately.
- Should I email the customer after a fraudulent decline?
- Not with a standard dunning email. First review the account for fraud signals. If the account appears to be a legitimate false positive, contact the customer directly. If the account looks fraudulent, flag it for review and do not contact.
- How do I know if a fraudulent decline is a false positive?
- Check the account history. A customer with many months of successful charges, consistent login patterns, and no recent account changes is more likely to be a false positive than a new account with a mismatched billing address and no prior activity.