Stripe v2 Payout Methods can be disabled for outbound money movement
Introduced 2026-08-26 · score 0.90
HOW TO USE IT
When processing v2 Payout Methods for payments or transfers, handle `usage_status` values including `disabled`. To stop outbound use, disable the Payout Method; to re-enable it, create a new Outbound Setup Intent.
WHY THIS HELPS
When maintaining an integration that uses v2 Payout Methods for outbound payments or transfers, handle payout methods whose usage_status is disabled.
REQUIREMENTS AND LIMITATIONS
- usage_status: Object indicating whether the Payout Method meets requirements for outbound money movement. The retrieved object example shows `payments` and `transfers` values as `eligible`. The docs page did not expose the allowed values for these sub-keys.
- Payout Method disable endpoint (required): `POST /v2/money_management/payout_methods/:id/disable`; endpoint parameters and runnable example were not accessible in the official docs page.
- A disabled payout method is unavailable for outbound money movement.
- The disabled status is non-terminal; re-enabling requires creating a new Outbound Setup Intent.
- Integrations that do not handle usage_status=disabled for payments and transfers might experience unexpected failures.
FIRST-PARTY EVIDENCE
- https://docs.stripe.com/changelog/dahlia/2026-08-26/disable-payout-methods
- https://docs.stripe.com/api/v2/money-management/payout-methods/object?api-version=2026-08-26.preview
- https://docs.stripe.com/api/v2/money-management/payout-methods?api-version=2026-08-26.preview
Check the installed version and the source before using it. Entry JSON