DISABLED_REASON action_required.requested_capabilities CONFIDENCE WHEN SET: HIGH
Recoverable state

Stripe says a capability needs more information

Requested capabilities need additional information. A capability was requested that requires more information before Stripe can enable it.

What this state actually is

This is the mildest state in the set, and frequently it is not a restriction at all but a request. A capability you asked for (card payments, transfers, a payment method in a particular country) has its own requirements beyond the account's baseline, and it stays inactive until those are met. Nothing that was already working stops working. The confusion usually comes from the word 'disabled' in the field name: what is disabled is the capability you have not finished enabling, not the account.

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 newly requested capability whose requirements were never completed. This is the most common case by a distance.
  • A new country or currency that brings its own regulatory collection on top of what the account already satisfied.
  • A payment method with method-specific onboarding. Several require extra business detail before they activate.
  • A change in the business that reopened collection for a capability that was previously active.

The playbook

  1. Complete the capability-specific requirements shown in the dashboard.

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 capability's own requirements list. Capability requirements are tracked separately from account requirements, and reading the wrong list is why people supply things nobody asked for.
  • Whatever business detail the capability needs: registration numbers, licences, or a described use case for the payment method.
  • Confirmation that you actually want the capability. If it was requested speculatively, the cleanest fix is to stop requesting it.

What makes it worse

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

  • Reading it as an account restriction and responding as though the business is under review.
  • Completing the account-level requirements and expecting the capability to activate. They are different lists.
  • Leaving speculative capability requests sitting on the account, which keeps a permanent action-required state on an otherwise clean account.

Typical timeline

Immediate once requirements are met

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

A capability was requested that requires more information before Stripe can enable it.

How do I fix a Stripe account with disabled_reason action_required.requested_capabilities?

Complete the capability-specific requirements shown in the dashboard.

How long does action_required.requested_capabilities take to resolve?

Immediate once requirements are met

What causes a Stripe account to get action_required.requested_capabilities?

A newly requested capability whose requirements were never completed. This is the most common case by a distance. A new country or currency that brings its own regulatory collection on top of what the account already satisfied. A payment method with method-specific onboarding. Several require extra business detail before they activate. A change in the business that reopened collection for a capability that was previously active.

What documents do I need for a action_required.requested_capabilities restriction?

The capability's own requirements list. Capability requirements are tracked separately from account requirements, and reading the wrong list is why people supply things nobody asked for. Whatever business detail the capability needs: registration numbers, licences, or a described use case for the payment method. Confirmation that you actually want the capability. If it was requested speculatively, the cleanest fix is to stop requesting it.

What should I avoid doing after getting action_required.requested_capabilities?

Reading it as an account restriction and responding as though the business is under review. Completing the account-level requirements and expecting the capability to activate. They are different lists. Leaving speculative capability requests sitting on the account, which keeps a permanent action-required state on an otherwise clean account.

What to read next

Related codes

Last reviewed