Stripe flagged my account with a watchlist match. Is it over?

What this state actually is

The single most important thing about this code is what it is not: it is not `rejected.listed`. Screening has surfaced a possible match and Stripe has paused the account while it checks, which means the outcome is still open and largely in your hands. Most of these are false positives on name similarity and clear once the identity is disambiguated. The accounts that end up terminated from here are overwhelmingly the ones that sat on the request for weeks. An unanswered verification request eventually converts into a rejection.

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 close to a sanctions-list entry. Common names generate these constantly; the screening is deliberately over-inclusive because the cost of a miss is a regulatory breach.
• A partial match on date of birth or address for any director or beneficial owner.
• A newly added owner or director whose details triggered a fresh screen on an account that was previously clear.
• An expansion into a new country that brought the account under an additional screening regime.

The playbook

1. Submit any identity or business documents Stripe requests promptly. Resolution is usually document-driven.
2. Check the dashboard notifications for the specific request; unanswered requests convert to rejections.

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:

• A clear, unexpired government photo ID for each flagged person: full page, all four corners, no glare.
• Proof of address dated within the last three months: a utility bill or bank statement in the same name and format as the account details.
• Company registration and ownership documents that establish the full beneficial-ownership chain.
• Anything that positively distinguishes the person from the listed entity: a middle name, a different nationality, a date of birth that does not match.

What makes it worse

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

• Waiting to see whether it resolves itself. It does not, and the pending state converts to a rejection on a timer.
• Sending a photo of a document at an angle, cropped, or with fields obscured. Document rejections are usually about legibility, and each round trip costs days.
• Submitting details that do not exactly match the account: a shortened first name, a former address, a trading name where the legal name is required.

Typical timeline

Days, if documents are submitted promptly

Related codes

• under_review: Account is under Stripe review (not rejected)
• requirements.past_due: Required verification information is past due
• requirements.pending_verification: Stripe is verifying submitted information
• All disabled_reason codes