DISABLED_REASON requirements.past_due CONFIDENCE WHEN SET: HIGH
Recoverable state

Stripe disabled my payouts because information is past due

Required verification information is past due. Stripe disabled capabilities because required identity/business fields were not provided by the deadline. This is the most common reason for disabled payouts, and the most fixable.

What this state actually is

This is the best code to have. Nothing is wrong with your business, your charge pattern or your website. A required field was not supplied by its deadline, and the restriction is automatic and automatically reversible. Stripe collects verification progressively as an account grows, so requirements appear at volume and time thresholds you were never told about, which is why this so often lands on accounts that have been running fine for a year. Supply what is listed and the capability restores, frequently within minutes.

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 volume or age threshold crossed, which triggered a fresh round of KYC collection the account had not needed before.
  • A document that failed silently, whether expired, illegible, or in a name that does not match the entity, where the follow-up notice went unread.
  • A beneficial owner over the 25% threshold who was never added, or a director whose details are incomplete.
  • A payout bank account whose name does not match the legal entity on the account.

The playbook

  1. Open Dashboard → Settings → Business (or the banner notification) and complete every field listed under 'Information needed'.
  2. Capabilities are restored automatically once verification passes, typically within minutes to a few days.

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 requirements list itself, in the dashboard. It names each outstanding field exactly. Work that list and nothing else.
  • In-date photo ID for every person the list names, matching the account's spelling of their name.
  • Proof of address dated within three months, and company registration documents for the entity.
  • Bank details in the legal entity's name. A personal account behind a limited company is the most common stall here.

What makes it worse

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

  • Uploading extra documents nobody asked for. It does not accelerate anything and it adds review surface.
  • Submitting details that nearly match: a trading name instead of the registered name, a former address, a shortened first name.
  • Waiting for a support reply before uploading. The requirement is machine-checked; the upload is what clears it.

Typical timeline

Minutes to a few days after submission

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

Stripe disabled capabilities because required identity/business fields were not provided by the deadline. This is the most common reason for disabled payouts, and the most fixable.

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

Open Dashboard → Settings → Business (or the banner notification) and complete every field listed under 'Information needed'. Capabilities are restored automatically once verification passes, typically within minutes to a few days.

How long does requirements.past_due take to resolve?

Minutes to a few days after submission

What causes a Stripe account to get requirements.past_due?

A volume or age threshold crossed, which triggered a fresh round of KYC collection the account had not needed before. A document that failed silently, whether expired, illegible, or in a name that does not match the entity, where the follow-up notice went unread. A beneficial owner over the 25% threshold who was never added, or a director whose details are incomplete. A payout bank account whose name does not match the legal entity on the account.

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

The requirements list itself, in the dashboard. It names each outstanding field exactly. Work that list and nothing else. In-date photo ID for every person the list names, matching the account's spelling of their name. Proof of address dated within three months, and company registration documents for the entity. Bank details in the legal entity's name. A personal account behind a limited company is the most common stall here.

What should I avoid doing after getting requirements.past_due?

Uploading extra documents nobody asked for. It does not accelerate anything and it adds review surface. Submitting details that nearly match: a trading name instead of the registered name, a former address, a shortened first name. Waiting for a support reply before uploading. The requirement is machine-checked; the upload is what clears it.

What to read next

Related codes

Last reviewed