← Back
Stripe
Stripe adds multicurrency support to v2 payout methods
Stripe APIStripe · apibreaking-changefeature · docs.stripe.com ↗

Multicurrency Payouts Now Available

Stripe has expanded its v2 PayoutMethods API to support foreign currency payouts. Previously, v2 PayoutMethods were limited to US-issued debit cards receiving USD payouts or bank accounts restricted to their country's local currency. This update enables developers to create payout methods that accept payouts in multiple currency options.

What Changed

The following additions enable multicurrency support:

  • currency parameter is now required when creating v2 PayoutMethod credentials via UsBankAccounts, GbBankAccounts, or OutboundSetupIntents endpoints
  • supported_currencies property added to PayoutMethod objects as a single-element array containing the specified currency
  • GB Bank Accounts flexibility: sort_code and account_number are now optional (required only for GBP); iban parameter added for non-GBP currencies
  • currencies property added to PayoutMethodsBankAccountSpec for currency-specific credential requirements

Breaking Changes and Migration

This is a breaking change requiring immediate action. The currency parameter is now mandatory, and any code that creates v2 PayoutMethods without specifying it will fail. Developers must update integrations to explicitly declare the desired payout currency.

Key considerations:

  • Each PayoutMethod supports only one currency—create separate objects for accounts accepting multiple currencies
  • For GB bank accounts, provide either iban alone or both sort_code and account_number depending on the currency
  • Check the supported_currencies property to identify a PayoutMethod's currency

Migration Steps

  1. Update to API version 2026-03-25.preview (or upgrade your SDK to the corresponding version)
  2. Modify code creating PayoutMethods to include the required currency parameter
  3. Update webhook endpoint API versions
  4. Test thoroughly before performing the final upgrade in Workbench (72-hour rollback window available)