Fraud suspected fraud_suspected
What this decline means
A risk system — the bank's or the platform's — scored this charge as possibly fraudulent and blocked it. On a subscription renewal for a real customer, it is very often a false positive, but the block is real.
Why it happens on subscription renewals
- The issuer's fraud model flagged the charge: new spending pattern, mismatched geography, or velocity across the account.
- Store-side or platform-side risk rules scored the transaction as high-risk.
- The card was recently involved in an actual fraud case elsewhere and the whole account is under tightened screening.
The merchant playbook
- Do not blindly re-run the charge. Retrying into a fraud flag reinforces it — repeated attempts read as exactly the behavior the model is hunting.
- Verify the subscriber is who they've always been: long history, consistent address, normal order — if yes, this is a false positive to resolve, not a customer to drop.
- Contact the customer through a channel you already have (their account email) and suggest they confirm the charge with their bank; once whitelisted, a single retry clears.
- If legitimate renewals for multiple customers trip fraud flags, review your own risk settings and charge descriptor — an unclear billing name inflates both fraud flags and disputes.
Should you retry?
Not immediately, and never repeatedly. Resolve the flag first (customer confirms with bank, or risk review clears it), then retry once. Hammering a fraud flag makes everything worse.
Common questions
My subscriber is obviously legitimate — why was their renewal flagged?
Fraud models score transactions, not relationships. A renewal can trip a model because of things entirely outside your store — account takeover attempts elsewhere, travel, or issuer-side rule changes.
Does a fraud-suspected decline mean I should cancel the subscription?
No — pause and investigate. If the customer confirms the charge, recovery is one retry away. Cancelling a loyal subscriber over a false positive is the most expensive possible response.
Related codes: call_issuer · do_not_honor · authentication_required · or see the
full decline-code guide.
Where Moorly fits: Moorly reads the decline reason behind every failed renewal in your existing subscription app and applies the playbook above automatically — the right treatment per code, with a dollar figure on what each failure family costs your store. It starts read-only. Join the early-access list →
Moorly is an independent product by Velun Labs and is not affiliated with Shopify, Appstle Inc., or Seal Subscriptions s.r.o. Code names follow Shopify's public API documentation as of August 2026; bank behavior varies by issuer — always confirm against your own admin.