sincecutoff.com
/v1/json /v1/md llms.txt
← all changes

Reject connected accounts with non-zero balances and control payout pausing

Introduced 2026-07-29 · score 0.95

HOW TO USE IT

When rejecting a connected account, call the Reject an account endpoint; for accounts with any balance, use `payouts_action=none` to keep payouts enabled, or omit it to use the default `pause` behavior.

curl https://api.stripe.com/v1/accounts/<account_id>/reject \ -u "<secret_key>:" \ -d reason=fraud \ -d payouts_action=none
curl https://api.stripe.com/v1/accounts/<account_id>/reject \ -u "<secret_key>:" \ -d reason=fraud

WHY THIS HELPS

When maintaining an integration that rejects connected accounts, reject an account with a non-zero balance or keep payouts enabled after rejection.

BEFORE THIS CHANGE

Before the change, rejecting an account with a non-zero balance returned an error, and payouts were always paused during rejection.

REQUIREMENTS AND LIMITATIONS

  • account_id (required): Account ID in the endpoint path.
  • reason (required): Reason for rejection: `fraud`, `terms_of_service`, or `other`.
  • payouts_action: `pause` (default) pauses payouts during rejection; `none` leaves payouts enabled.
  • Prerequisite: Reject is available for connected accounts where the platform is liable for negative balances, including Custom and Express accounts. The API reference says test-mode accounts can be rejected at any time.
  • Prerequisite: Authenticate the request with a Stripe secret key.
  • Docs conflict: The API reference available to search says live-mode accounts can only be rejected after all balances are zero and only documents `reason`; this conflicts with the 2026-07-29 Dahlia release note. The endpoint page could not be accessed with the Dahlia version parameter, so those older reference details are not applied here.

FIRST-PARTY EVIDENCE

Check the installed version and the source before using it. Entry JSON

Report a problem with this card