Create connected accounts with the correct country code for each recipient; Stripe's supported countries list determines available payout methods and timing.
Add an external bank account appropriate for the recipient's country — IBAN for SEPA countries, sort code + account number for UK, BSB for Australia, etc.
Set the payout currency to match the destination bank account's currency; if the connected account earns in a different currency, Stripe applies FX conversion at prevailing rates.
Verify the account's capabilities include 'transfers' and that the country-specific requirements (e.g., director information, VAT number) have been met.
Trigger payouts using the connected account's preferred currency; Stripe will convert from the source settlement currency if necessary.
Monitor payout timing per country — international payouts may have 3-7 business day settlement windows versus domestic 2-day ACH.
Known gotchas
Not all Stripe features are available in every country; check the Stripe global availability page for capability and feature restrictions before committing to a country's payout flow.
FX conversion fees apply when settling in a currency different from the charge currency; factor this into your platform's margin model.
Some countries require additional compliance data (tax IDs, government-issued IDs) before payouts are enabled — collect these during onboarding, not at payout time.
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?