Create a connected account with type 'express' via POST /v1/accounts, supplying country, email, and the capabilities you need (e.g., card_payments, transfers).
Generate an Account Link via POST /v1/account_links with account, refresh_url, return_url, and type 'account_onboarding'; redirect the user to the returned URL.
After the user returns, retrieve the account via GET /v1/accounts/{id} and inspect the capabilities object; each capability has a status field (active, inactive, pending).
If requirements.currently_due or requirements.past_due is non-empty, generate a new Account Link and re-direct the user to complete missing fields.
Once all required capabilities are active, proceed to create charges or transfers on behalf of that connected account.
Subscribe to the account.updated webhook to detect capability status changes asynchronously rather than polling.
Known gotchas
Account Links expire quickly (minutes); never cache or reuse them — generate a fresh one each time the user needs to return to onboarding.
Capabilities may enter a 'pending' state while Stripe reviews submitted information; do not treat 'pending' as equivalent to 'active'.
The refresh_url is called when the link expires mid-session — your server must handle it by generating a new Account Link immediately.
Give your agent this knowledge — and 15,800+ more routes
One MCP install gives any agent live access to the full route map across 5,800+ 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?