• Breaking changes
• Public preview

Adds multicurrency support for v2 payout methods Breaking changes Public preview

What’s new

Adds the ability to create v2 Payout Methods that can receive payouts in foreign currencies. Previously, v2 Payout Methods could only be US-issued debit cards that receive payouts in USD or bank accounts that receive payouts in their country’s local currency.

Adds the ability to specify a payout method’s currency by adding the required currency parameter to endpoints that create v2 Payout Methods and adding the supported_currencies property to objects that represent v2 Payout Methods. The supported_currencies property is a single-element array that contains the currency specified in the currency parameter.

currency and supported_currencies are at the top level of creation requests and responses, respectively, for US Bank Accounts and GB Bank Accounts, and in card or bank account hashes for Payout Methods and Outbound Setup Intents.

Also adds the currencies property to the countries hash on the Payout Methods Bank Account Spec object. This property contains currency-specific credential requirements.

Also adds multicurrency payout support to GB bank accounts by making the following updates to the GB Bank Accounts API:

• Makes the sort_code and account_number parameters only required for GBP accounts
• Adds the iban parameter for non-GBP currencies

v2 money movement flows and Global Payouts

v2 money movement flows such as OutboundPayments, OutboundTransfers, and InboundTransfers don’t support multicurrency PayoutMethods. You can use them only with PayoutMethods set up with the local currency.

Why is this a breaking change?

The currency parameter is now required when creating v2 Payout Method credentials. If your integration creates v2 Payout Methods using US Bank Accounts, GB Bank Accounts, or Outbound Setup Intents, you must update your code to specify a currency value.

Impact

v2 Payout Methods now support foreign currencies for payouts. They don’t default to the payout account’s local currency, so you now need to specify the currency when creating them. Attempting to create a v2 Payout Method without specifying the currency parameter will fail.

Multicurrency support on v2 Payout Methods allows you to use them for payouts to connected accounts instead of using External Bank Accounts or External Account Cards.

When creating GB Bank Accounts, you now only need to include the sort_code and account_number for payout accounts that use GBP. For GB Bank Accounts that receive payouts in other currencies, specify the iban parameter instead. You need to include either only the iban or both the sort_code and account_number, depending on the currency.

Each Payout Method can support only one currency. To represent a payout account that accepts multiple currencies, you need to create a separate object for each supported currency.

To identify a Payout Method’s currency, check the supported_currencies property of the corresponding US Bank Account or GBBankAccount, or the Payout Method’s bank_account or card hash.

Changes

Upgrade

1. View your current API version in Workbench.
2. If you use an SDK, upgrade to the corresponding SDK version for this API version.

• If you don’t use an SDK, update your API requests to include Stripe-Version: 2026-03-25. preview

3. Upgrade the API version used for webhook endpoints .
4. Test your integration against the new version.
5. If you use Connect, test your Connect integration .
6. In Workbench, perform the upgrade . You can roll back the version for 72 hours.

Learn more about Stripe API upgrades.

Related changes

• Restricts Accounts v2 identity properties for some Global Payouts use cases
• Adds the restricted property to the Payout Method object
• Expands Global Payouts cross-border payout destinations to three additional countries