DISABLED_REASON requirements.pending_verification CONFIDENCE WHEN SET: HIGH
Recoverable state

Stripe is verifying my information. Should I do anything?

Stripe is verifying submitted information. You've submitted the required information and Stripe is verifying it. No action is usually needed unless verification fails.

What this state actually is

You have done the work and Stripe is checking it. In the normal case this needs nothing from you and clears on its own. The one failure mode worth knowing about is that documents can fail quietly. The state moves back to requiring information rather than announcing a rejection, and if the notification address is not being watched, an account can sit in what looks like patience but is actually a stall. Check back after a few days rather than assuming silence means progress.

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:

  • Documents submitted and queued for automated or manual checking, which is the ordinary path.
  • A resubmission after an earlier failure, which typically routes to a human and takes longer than the first pass.
  • Additional screening because a name, address or ownership detail needed a closer look.
  • A high-risk category or a newly added country, both of which lengthen the check.

The playbook

  1. Wait for verification (usually < a few days); watch for follow-up requests.
  2. If it has been stuck for more than a week, contact support. Documents sometimes fail silently on image quality.

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 record of exactly what you submitted and when, so a second round does not repeat a document that already failed.
  • Higher-quality captures of the same documents, ready in case the first pass is rejected on legibility.
  • A monitored email address on the account, since a silent failure is only silent if nobody is reading.

What makes it worse

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

  • Re-uploading the same documents repeatedly. It does not add urgency and can push the case back into the queue.
  • Changing account details mid-check, such as a name spelling, an address or a bank account, which invalidates what is being verified.
  • Assuming no news is good news past about a week. Log in and read the requirements list.

Typical timeline

Usually under a few days

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.

Frequently asked

What does requirements.pending_verification mean on a Stripe account?

You've submitted the required information and Stripe is verifying it. No action is usually needed unless verification fails.

How do I fix a Stripe account with disabled_reason requirements.pending_verification?

Wait for verification (usually < a few days); watch for follow-up requests. If it has been stuck for more than a week, contact support. Documents sometimes fail silently on image quality.

How long does requirements.pending_verification take to resolve?

Usually under a few days

What causes a Stripe account to get requirements.pending_verification?

Documents submitted and queued for automated or manual checking, which is the ordinary path. A resubmission after an earlier failure, which typically routes to a human and takes longer than the first pass. Additional screening because a name, address or ownership detail needed a closer look. A high-risk category or a newly added country, both of which lengthen the check.

What documents do I need for a requirements.pending_verification restriction?

A record of exactly what you submitted and when, so a second round does not repeat a document that already failed. Higher-quality captures of the same documents, ready in case the first pass is rejected on legibility. A monitored email address on the account, since a silent failure is only silent if nobody is reading.

What should I avoid doing after getting requirements.pending_verification?

Re-uploading the same documents repeatedly. It does not add urgency and can push the case back into the queue. Changing account details mid-check, such as a name spelling, an address or a bank account, which invalidates what is being verified. Assuming no news is good news past about a week. Log in and read the requirements list.

What to read next


Related codes

Last reviewed