Update the connected account's payout schedule via POST /v1/accounts/{account} with settings.payouts.schedule.interval set to daily, weekly, monthly, or manual
For automatic schedules, set the appropriate anchor (e.g., weekly_anchor=monday) and delay_days to control when funds are paid out relative to charge settlement
To use manual payouts, set settings.payouts.schedule.interval=manual; Stripe will hold funds in the connected account's balance until explicitly triggered
Trigger a manual payout via POST /v1/payouts on behalf of the connected account using the Stripe-Account header with the connected account id; specify amount and currency
Monitor payout status via payout.paid, payout.failed, and payout.canceled webhook events; retrieve the Payout object to inspect arrival_date and failure_code on failures
For platforms using automatic payouts, understand that delay_days represents a rolling window after each charge settles — consult current docs for minimum delay values per country and payment method
Known gotchas
Switching from automatic to manual payouts halts all scheduled payouts immediately — ensure your operations team is prepared to trigger payouts manually or build automated payout logic before making the switch
delay_days has a minimum value that varies by country and payment method (e.g., card payments in the US may have a minimum rolling delay); setting a value below the minimum will be silently overridden by Stripe — verify the effective schedule by reading the account settings back after update
Manual payouts on behalf of connected accounts require the platform to use the Stripe-Account header; ensure your API client correctly scopes the request to the connected account, otherwise the payout will be created on the platform account
Give your agent this knowledge — and 15,600+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?