DISABLED_REASON rejected.incomplete_verification CONFIDENCE WHEN SET: HIGH
Rejection

Stripe rejected my account because verification wasn't completed

Rejected because verification was never completed. Stripe asked for identity/business verification, the deadline passed without sufficient documents, and the account was rejected.

What this state actually is

This is the friendliest code in the `rejected.*` family, and it is routinely misread as terminal because of the prefix. Nothing here says Stripe found a problem with your business. It says a deadline passed with required information still outstanding. That is an administrative closure, and administrative closures get reopened when the information arrives. The usual reason it went unnoticed is mundane: the notification emails went to a founder address nobody checks, or landed in spam, while the dashboard banner sat unseen because nobody had cause to log in.

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:

  • Required verification fields sat in `requirements.past_due` past the deadline Stripe set.
  • A document was submitted and failed for poor scan quality, an expired ID, or a name that did not match the account, and the failure notice went unread.
  • The account was dormant. Test-mode or low-volume accounts often accumulate requirements nobody is watching for.
  • Notifications went to an address that no longer exists, or to a shared inbox where nobody owned them.

The playbook

  1. Contact Stripe support and ask to reopen verification. Provide government ID, proof of address, and business registration in one complete submission.
  2. Make sure the legal entity details exactly match your registration documents (name spelling, address, tax ID).

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:

  • The exact list of what was outstanding. It is still visible in the dashboard, and it is the fastest thing to have ready when you contact support.
  • Current, in-date versions of every required document, matching the legal entity exactly.
  • Bank account details in the legal entity's name, which is where these stall most often.
  • A working email address you actually monitor, to update on the account before anything else.

What makes it worse

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

  • Reading `rejected` and starting a new account instead of writing to support. This one is usually reopenable, and the new account creates a duplicate-entity problem that is not.
  • Submitting the same document that failed the first time without fixing why it failed.
  • Leaving the notification address unchanged, which reproduces the exact circumstances that caused the closure.

Typical timeline

Often recoverable via support

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.incomplete_verification mean on a Stripe account?

Stripe asked for identity/business verification, the deadline passed without sufficient documents, and the account was rejected.

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

Contact Stripe support and ask to reopen verification. Provide government ID, proof of address, and business registration in one complete submission. Make sure the legal entity details exactly match your registration documents (name spelling, address, tax ID).

How long does rejected.incomplete_verification take to resolve?

Often recoverable via support

What causes a Stripe account to get rejected.incomplete_verification?

Required verification fields sat in `requirements.past_due` past the deadline Stripe set. A document was submitted and failed for poor scan quality, an expired ID, or a name that did not match the account, and the failure notice went unread. The account was dormant. Test-mode or low-volume accounts often accumulate requirements nobody is watching for. Notifications went to an address that no longer exists, or to a shared inbox where nobody owned them.

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

The exact list of what was outstanding. It is still visible in the dashboard, and it is the fastest thing to have ready when you contact support. Current, in-date versions of every required document, matching the legal entity exactly. Bank account details in the legal entity's name, which is where these stall most often. A working email address you actually monitor, to update on the account before anything else.

What should I avoid doing after getting rejected.incomplete_verification?

Reading `rejected` and starting a new account instead of writing to support. This one is usually reopenable, and the new account creates a duplicate-entity problem that is not. Submitting the same document that failed the first time without fixing why it failed. Leaving the notification address unchanged, which reproduces the exact circumstances that caused the closure.

What to read next

Related codes

Last reviewed