DISABLED_REASON other CONFIDENCE WHEN SET: LOW
Recoverable state

Stripe disabled my account for 'other' reasons

Disabled for reasons Stripe labels 'other'. Stripe set a non-specific disabled reason. The secondary signals in this report are the best guide.

What this state actually is

`other` without a `rejected.` prefix is an unusual state: the account is disabled, but Stripe has not classified it into any of the published categories, and, importantly, it has not been terminated either. That leaves more room than a rejection does. The cause is nearly always legible from the account's own signals even though the field refuses to name it, so the work is diagnostic: read the capability states, the risk numbers and the recent changes, form a specific hypothesis, and take that to support rather than an open-ended question.

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:

  • An edge case the code list does not cover: an unusual entity structure, a jurisdiction change, a migration between account types.
  • An in-progress internal process that has not yet resolved into a specific outcome.
  • A combination of moderate signals, none individually decisive.
  • An upstream decision by a bank or network partner that Stripe is applying rather than originating.

The playbook

  1. Contact Stripe support via the dashboard for specifics, referencing your account status page.

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:

  • Which capabilities are off and which are on. Charges and payouts fail independently, and the combination narrows the cause considerably.
  • The `requirements` object in full. `currently_due`, `eventually_due` and `errors` often name something the top-level reason does not.
  • Dispute rate, early fraud warnings and refund velocity for the last 90 days.
  • A dated list of recent account changes, which is what turns an open question to support into a specific one.

What makes it worse

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

  • Treating it as a rejection. It is not one, and responding as though the account is closed forfeits a recoverable position.
  • Contacting support without a hypothesis. A specific question with evidence attached gets a substantive reply; 'why is my account disabled' gets the template.
  • Making changes while it is unresolved, which muddies the very signals you need to read.

Typical timeline

Unknown until the cause is identified

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

Stripe set a non-specific disabled reason. The secondary signals in this report are the best guide.

How do I fix a Stripe account with disabled_reason other?

Contact Stripe support via the dashboard for specifics, referencing your account status page.

How long does other take to resolve?

Unknown until the cause is identified

What causes a Stripe account to get other?

An edge case the code list does not cover: an unusual entity structure, a jurisdiction change, a migration between account types. An in-progress internal process that has not yet resolved into a specific outcome. A combination of moderate signals, none individually decisive. An upstream decision by a bank or network partner that Stripe is applying rather than originating.

What documents do I need for a other restriction?

Which capabilities are off and which are on. Charges and payouts fail independently, and the combination narrows the cause considerably. The `requirements` object in full. `currently_due`, `eventually_due` and `errors` often name something the top-level reason does not. Dispute rate, early fraud warnings and refund velocity for the last 90 days. A dated list of recent account changes, which is what turns an open question to support into a specific one.

What should I avoid doing after getting other?

Treating it as a rejection. It is not one, and responding as though the account is closed forfeits a recoverable position. Contacting support without a hypothesis. A specific question with evidence attached gets a substantive reply; 'why is my account disabled' gets the template. Making changes while it is unresolved, which muddies the very signals you need to read.

What to read next

Related codes

Last reviewed