# Stripe: payouts_not_allowed
> Stripe returns payouts_not_allowed when payouts are disabled on a connected account. Check the account’s requirements, then collect what is due.
Canonical: https://app369.com/fix/stripe-payouts-not-allowed/
Last updated: 2026-11-11
Stripe returns payouts_not_allowed when payouts have been disabled on a connected account. Stripe says to check the connected account’s status to see whether more information needs to be provided, or whether payouts were disabled for another reason.
**Rather hand it over?** [App Fix Ticket](https://app369.com/fixed-price/flutter-firebase-bug-fix/): One reproducible bug in an existing mobile or web app, diagnosed and fixed.
[Pay $450 for a Diagnosis](https://buy.stripe.com/dRmdRa7K4bWz8CWdwagw003) [**Ask a question first**](https://app369.com/contact/?offer=offer1-diagnosis&ask=1)
Full refund if Simon can’t take it on once he sees your project, or if you cancel before work starts. [Refund terms](https://app369.com/terms-of-service/#refunds).
- Simon does the work himself
- [5.0 from 127 Fiverr reviews, checked Oct 30, 2026](https://app369.com/reviews/)
**Short answer**
Retrieve the connected account and check payouts_enabled and the requirements hash. If requirements are currently_due or past_due, collect that information from the account holder and update the account. Watch account.updated events so the platform knows when payouts are enabled again.
Rather not fix it yourself? [**App Fix Ticket**](https://app369.com/fixed-price/flutter-firebase-bug-fix/) starts with a fixed-price diagnosis, then a fixed price for the fix before any fix work.
## **Why payouts are disabled, and the fix**
1. 01 ### **Payouts are off on the connected account**
> “Payouts have been disabled on the connected account.” [**Stripe, Error codes (payouts_not_allowed)**](https://docs.stripe.com/error-codes) The payouts_enabled attribute on the Account object indicates whether it can accept payouts. If it is false, expect this error.
2. 02 ### **Verification information is due**
> “If either of those attributes is false, check the Account’s requirements hash to determine what information is needed to enable charges and payouts.” [**Stripe, Handle verification with the API (Accounts v1)**](https://docs.stripe.com/connect/handling-api-verification?accounts-namespace=v1) If payouts_enabled is false, check the requirements hash to see what information is needed: currently_due lists what to resolve by the current_deadline, and past_due lists requirements that already disabled capabilities.
3. 03 ### **New requirements appeared after onboarding**
> “Continue watching for account.updated event notifications to see if the requirements hash changes, and ask the connected account for additional information as needed.” [**Stripe, Handle verification with the API (Accounts v1)**](https://docs.stripe.com/connect/handling-api-verification?accounts-namespace=v1) Also check: requirements can change after onboarding, so a platform that isn’t watching account.updated can miss them. Stripe’s guidance is below.
4. 04 ### **Payouts were disabled for another reason** Also check: the requirements hash has a disabled_reason that describes why the account isn’t enabled. If nothing is due and payouts are still off, read that field before contacting Stripe.
Checked against the vendor’s docs on November 11, 2026: [Stripe docs: Error codes](https://docs.stripe.com/error-codes); [Stripe docs: Handle verification with the API (Accounts v1)](https://docs.stripe.com/connect/handling-api-verification?accounts-namespace=v1); [Stripe API: The Account object](https://docs.stripe.com/api/accounts/object).
## **Rather hand it over?**
Fixed scope, fixed price, paid upfront. The work happens in writing; no call needed.
- [from $450**App Fix Ticket**One reproducible bug in an existing mobile or web app, diagnosed and fixed.**See scope and start**](https://app369.com/fixed-price/flutter-firebase-bug-fix/)
- [from $450**AI-Built App Rescue**A Lovable, Bolt or Cursor app checked end to end in 3 days, then its worst problems fixed at a fixed price.****No issues worth fixing, no charge.**** If the Launch Check finds nothing rated medium or higher, Simon refunds the full $450. You keep the report either way. This applies to the first 10 Launch Checks bought after October 30, 2026.**See scope and start**](https://app369.com/fixed-price/ai-app-rescue/)
[**All 127 Fiverr reviews**](https://app369.com/reviews/)
Related: [**Stripe payout failed**](https://app369.com/fix/stripe-payout-failed/) · [**Stripe Connect onboarding incomplete**](https://app369.com/fix/stripe-connect-account-onboarding-incomplete/) · [**Stripe capability not active**](https://app369.com/fix/stripe-capability-not-active/) · [**Stripe stripe_tax_inactive**](https://app369.com/fix/stripe-tax-inactive/)
Questions
## **More on this error**
**Which field shows whether a connected account can be paid out? **+
payouts_enabled on the Account object. Stripe’s API reference describes it as whether the funds in this account can be paid out.
**Can you fix it for me? **+
If one bug is the whole problem, the App Fix Ticket covers it: a written diagnosis first, then the fix. If the app has more going on, the Launch Check is a written check of the whole app. Each issue found is rated critical, high, medium or low, with where it is and how it was confirmed. No issues worth fixing, no charge. If the Launch Check finds nothing rated medium or higher, Simon refunds the full $450. You keep the report either way. This applies to the first 10 Launch Checks bought after October 30, 2026.
A different error?
## **Describe it and get a written quote**
Send the error and what you were doing. You get a written scope, a fixed price and a timeline; Simon replies by email, usually within one business day.
[**Describe your problem **→](https://app369.com/contact/) [**All fixes**](https://app369.com/fix/)