# Stripe: capability_not_active
> Stripe returns capability_not_active when the account lacks an active capability, such as card_payments or transfers, for the endpoint called. The fix.
Canonical: https://app369.com/fix/stripe-capability-not-active/
Last updated: 2026-11-11
Stripe returns capability_not_active when the account a request runs as is missing an active capability that the endpoint needs. On Connect platforms, a connected account’s card_payments, transfers or payment method capability can be unrequested or still waiting on information.
**Rather hand it over?** [Stripe Billing Fix and Setup](https://app369.com/fixed-price/stripe-billing-setup/): Subscriptions, webhooks, customer portal and failed payments set up or fixed, tested in Stripe test mode.
[Pay $950 for Stripe Billing Fix and Setup](https://buy.stripe.com/fZu9AU9Sc5ybcTc4ZEgw00j) [**Ask a question first**](https://app369.com/contact/?offer=offer12-stripe-billing&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**
Read the capabilities array in the error response to see which capability is missing. Retrieve that capability for the account and check its status and requirements. Request it if it is unrequested, collect everything listed in currently_due and past_due from the connected account, and retry once the status is active.
Rather not fix it yourself? [**Stripe Billing Fix and Setup**](https://app369.com/fixed-price/stripe-billing-setup/) handles it at a fixed price, agreed before work starts.
## **Why the capability isn’t active, and the fix**
1. 01 ### **The capability was never requested**
> “For connected accounts without access to a Stripe-hosted Dashboard, including Custom accounts, you must request their capabilities.” [**Stripe, Account capabilities**](https://docs.stripe.com/connect/account-capabilities?accounts-namespace=v1) Accounts without a Stripe-hosted Dashboard, including Custom accounts, only get the capabilities the platform requests. Request it by updating the account or the capability with requested set to true. Accounts with the full Stripe Dashboard, including Standard accounts, get some capabilities requested automatically based on their country.```
await stripe.accounts.update('acct_…', {
capabilities: {
card_payments: { requested: true },
transfers: { requested: true },
},
});
```
2. 02 ### **Requirements are still due**
> “The requirements listed in that hash indicate what information is needed from your connected account to prevent that capability from being disabled.” [**Stripe, Account capabilities**](https://docs.stripe.com/connect/account-capabilities?accounts-namespace=v1) A requested capability stays inactive until the account supplies the information Stripe asks for. Check the requirements hash on the capability to see what is needed, and collect it from the connected account.
3. 03 ### **An inactive card_payments or transfers disables both**
> “If a connected account has both card_payments and transfers, and the status of either one is inactive, then both capabilities are disabled.” [**Stripe, Account capabilities**](https://docs.stripe.com/connect/account-capabilities?accounts-namespace=v1) When an account has both, one inactive capability disables the other too, so a transfer can fail because card_payments is the inactive one.
4. 04 ### **It worked in a sandbox**
> “Sandboxes might not enforce some capabilities.” [**Stripe, Account capabilities**](https://docs.stripe.com/connect/account-capabilities?accounts-namespace=v1) Also check: sandboxes may let an account act without the capability, so the error can first appear in live mode. Test with the capability status, not just a successful sandbox call.
Checked against the vendor’s docs on November 11, 2026: [Stripe docs: Error codes](https://docs.stripe.com/error-codes); [Stripe docs: Account capabilities and configurations](https://docs.stripe.com/connect/account-capabilities?accounts-namespace=v1).
## **Rather hand it over?**
Fixed scope, fixed price, paid upfront. The work happens in writing; no call needed.
- [$950**Stripe Billing Fix and Setup**Subscriptions, webhooks, customer portal and failed payments set up or fixed, tested in Stripe test mode.**See scope and start**](https://app369.com/fixed-price/stripe-billing-setup/)
- [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 Connect onboarding incomplete**](https://app369.com/fix/stripe-connect-account-onboarding-incomplete/) · [**Stripe account_invalid**](https://app369.com/fix/stripe-account-invalid/) · [**Stripe works in test mode but not live**](https://app369.com/fix/stripe-works-in-test-mode-not-live/) · [**Stripe stripe_tax_inactive**](https://app369.com/fix/stripe-tax-inactive/)
Questions
## **More on this error**
**How can I see what an account still needs? **+
Retrieve the capability for the account. Its requirements hash lists past_due, currently_due and eventually_due fields, plus a disabled_reason, and the status shows whether it is active.
**Can requirements be collected before requesting the capability? **+
Yes. Stripe lets you preview a capability’s requirements before requesting it, and recommends collecting that information first so the account isn’t disabled when the request triggers new requirements.
**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/)