Stripe says my account matched a prohibited persons or sanctions list

What this state actually is

This code covers two very different situations that need opposite responses, and Stripe's notice will not distinguish them. A sanctions match (OFAC or an equivalent regime) is a legal obligation Stripe cannot waive, but it is also frequently a false positive on a common name, and false positives get cleared with documents. A MATCH listing is a card-network record placed by a previous acquirer, lasts five years, and blocks onboarding across the industry; that one has to be resolved with the bank that listed you, not with Stripe. Work out which you are dealing with before you spend effort in the wrong place.

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 name, date of birth or address close enough to a sanctions-list entry to trip automated screening. This is common with names that are common in the first place.
• A MATCH listing from a prior processor, usually after a closure for excessive chargebacks or a policy breach. Many merchants have no idea they were listed; notification is inconsistent.
• A director, beneficial owner or the business address matching, rather than you personally. Screening runs against everyone on the account, not just the signer.
• An address or operating country under a sanctions regime, including where the business is registered elsewhere but operated from there.

The playbook

1. If another processor terminated you before, you may be on the card networks' MATCH list. Ask your former acquirer to confirm it and, if the listing is wrong, to remove it.
2. If this is mistaken identity (a name collision with a sanctioned party), submit identity documents through the dashboard to disambiguate.
3. Sanctions matches are non-negotiable for Stripe; a compliance attorney is the right next step if you believe it's wrong.

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:

• Government photo ID and proof of address for every person named on the account. The fastest way to clear a false-positive sanctions match is to disambiguate the identity.
• Company registration documents showing the full ownership chain.
• Any correspondence from a previous processor about a closure, which is where a MATCH listing would have originated.
• A written request to your previous acquirer asking whether they listed you and under which reason code. You are entitled to ask, and it is the only way to confirm.

What makes it worse

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

• Assuming it is permanent without checking which list. A false-positive sanctions hit can clear in days on documents; treating it as terminal wastes a recoverable account.
• Trying to route around a MATCH listing with a different director or entity. Acquirers screen the business, the principals and the bank details, and the attempt itself is a listable offence.
• Ignoring the underlying cause. If a previous processor listed you for chargebacks, the same pattern will produce the same result at the next one.

Typical timeline

Document-driven; MATCH listings last 5 years

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.

Related codes

• rejected.incomplete_verification: Rejected because verification was never completed
• rejected.other: Rejected for unspecified risk reasons
• rejected.fraud: Stripe rejected the account for suspected fraud
• All disabled_reason codes