DISABLED_REASON rejected.fraud CONFIDENCE WHEN SET: HIGH
Rejection

Stripe rejected my account for fraud. Can I get it back?

Stripe rejected the account for suspected fraud. Stripe's risk systems or reviewers concluded the account was involved in fraudulent activity (stolen cards, card testing, or misrepresented business). This is a terminal rejection: Stripe typically holds remaining funds 90–120 days to cover chargebacks, then pays out what remains.

What this state actually is

This is the most severe code Stripe sets. It means the risk team concluded the account was being used to process fraudulent transactions. That is not the same as concluding your business is fraudulent; it means the charge pattern matched fraud closely enough that a reviewer closed the account rather than ask questions. Because the decision is made against signals Stripe will not enumerate (sharing them would tell actual fraudsters what to avoid), you are appealing something you cannot see. Treat reinstatement as unlikely and spend your effort on the two things that are still in your control: recovering the balance, and not compounding the damage.

How to confirm this is your code

Stripe exposes the code in the requirements.disabled_reason field of your Account object. Check it with a direct API call, GET /v1/accounts/{ACCOUNT_ID}, or connect Opsidion read-only and it reads the field for you, along with the verification errors, capability state, and 90 days of risk signals that explain why Stripe set it. The dashboard banner usually paraphrases this code, but the field itself is the source of truth.

What puts an account in this state

Roughly in order of how often we see each one:

  • A cluster of early fraud warnings, the TC40 and SAFE reports issuers file when a cardholder reports a charge as fraud. These arrive before disputes do, and a spike is the single strongest predictor of this code.
  • Card testing: a burst of small-value authorisations, mostly declined, often from a narrow set of IPs or a single BIN range. Even when you are the victim of it rather than the operator, an account that lets it run reads identically from outside.
  • A dispute rate climbing well past the ~0.75% intervention threshold with fraud-coded reason codes rather than service or product ones.
  • Mismatch between the declared business and the actual charge pattern: a stated average order value of $40 against a run of $900 charges, or transactions concentrated in a country the business has no stated presence in.

The playbook

  1. Reply to Stripe's rejection email or dashboard notice with evidence: supplier invoices, fulfillment/tracking records, customer communications.
  2. If you believe specific charges triggered it, refund the suspicious ones and document why the rest are legitimate.
  3. Appeals rarely succeed for fraud rejections, so line up a processor that underwrites your risk profile at the same time. Do NOT open a new Stripe account for the same business: ban evasion leads to immediate re-termination and MATCH-listing risk.

What to have ready before you respond

Every round trip with Stripe costs days, so the goal is to make the first reply the complete one:

  • Your full charge history for the period under question, exported before you lose dashboard access. Stripe keeps the account readable for a while after closure, but do not rely on it.
  • Fulfilment proof for the disputed transactions: delivery confirmations, access logs for digital goods, signed contracts for services.
  • Whatever you have on the fraud you absorbed yourself. If you were the target of card testing, the traffic logs and any Radar rules you added in response show that you acted.
  • A written timeline of anything unusual on the account: a viral moment, a new market, a promotion, a compromised API key.

What makes it worse

The avoidable mistakes. Each of these turns a slow problem into a harder one:

  • Opening a new Stripe account for the same business. It is detected quickly through the entity, bank account and device signals, re-terminated, and each attempt raises the odds of a MATCH listing that blocks you at other processors for five years.
  • Sending an angry or long appeal. The reviewer scans for new information, not for tone or volume. One page, with specifics and attachments, is read; ten pages of grievance are not.
  • Refunding everything at once to bring the dispute rate down. It does not retroactively change the ratio, it drains the balance that would otherwise cover chargebacks, and it can read as an attempt to obscure the record.

Typical timeline

Appeals rarely succeed; funds held 90–120 days

One warning that applies to every rejected.* code: do not open a fresh Stripe account for the same business. Stripe detects it quickly, re-terminates, and repeat evasion is how merchants end up on the card networks' MATCH list, which blocks onboarding at other processors for five years.

Get the full diagnosis, not just the code

The code tells you the category; it doesn't tell you which charge pattern, website issue, or verification field caused it. Opsidion's $49 diagnosis ranks every probable cause from your account's own signals, and auto-refunds if it finds nothing assessable.

Diagnose my account Explore the demo

Frequently asked

What does rejected.fraud mean on a Stripe account?

Stripe's risk systems or reviewers concluded the account was involved in fraudulent activity (stolen cards, card testing, or misrepresented business). This is a terminal rejection: Stripe typically holds remaining funds 90–120 days to cover chargebacks, then pays out what remains.

How do I fix a Stripe account with disabled_reason rejected.fraud?

Reply to Stripe's rejection email or dashboard notice with evidence: supplier invoices, fulfillment/tracking records, customer communications. If you believe specific charges triggered it, refund the suspicious ones and document why the rest are legitimate. Appeals rarely succeed for fraud rejections, so line up a processor that underwrites your risk profile at the same time. Do NOT open a new Stripe account for the same business: ban evasion leads to immediate re-termination and MATCH-listing risk.

How long does rejected.fraud take to resolve?

Appeals rarely succeed; funds held 90–120 days

What causes a Stripe account to get rejected.fraud?

A cluster of early fraud warnings, the TC40 and SAFE reports issuers file when a cardholder reports a charge as fraud. These arrive before disputes do, and a spike is the single strongest predictor of this code. Card testing: a burst of small-value authorisations, mostly declined, often from a narrow set of IPs or a single BIN range. Even when you are the victim of it rather than the operator, an account that lets it run reads identically from outside. A dispute rate climbing well past the ~0.75% intervention threshold with fraud-coded reason codes rather than service or product ones. Mismatch between the declared business and the actual charge pattern: a stated average order value of $40 against a run of $900 charges, or transactions concentrated in a country the business has no stated presence in.

What documents do I need for a rejected.fraud restriction?

Your full charge history for the period under question, exported before you lose dashboard access. Stripe keeps the account readable for a while after closure, but do not rely on it. Fulfilment proof for the disputed transactions: delivery confirmations, access logs for digital goods, signed contracts for services. Whatever you have on the fraud you absorbed yourself. If you were the target of card testing, the traffic logs and any Radar rules you added in response show that you acted. A written timeline of anything unusual on the account: a viral moment, a new market, a promotion, a compromised API key.

What should I avoid doing after getting rejected.fraud?

Opening a new Stripe account for the same business. It is detected quickly through the entity, bank account and device signals, re-terminated, and each attempt raises the odds of a MATCH listing that blocks you at other processors for five years. Sending an angry or long appeal. The reviewer scans for new information, not for tone or volume. One page, with specifics and attachments, is read; ten pages of grievance are not. Refunding everything at once to bring the dispute rate down. It does not retroactively change the ratio, it drains the balance that would otherwise cover chargebacks, and it can read as an attempt to obscure the record.

What to read next

Related codes

Last reviewed