---
title: "International Transfers"
description: "Understand Stripe's cross-border transfer restrictions. Transfers require accounts in the same country/region, with cross-border support between US, CA, UK, EEA, and Switzerland. Learn about supported corridors, fees, and workarounds."
url: "https://docs.splitpayplugin.com/faqs/international-transfers/"
---
## The same-region restriction

Stripe Connect transfers generally require the platform and connected accounts to be in the **same country or region**. This is a Stripe platform limitation, not a Split Pay limitation. However, Stripe does support **cross-border transfers** between certain regions — see the exception below.

**Where Stripe Connect is available at all.** Stripe Connect *platforms* are only available in a subset of countries (roughly 45 today, including the US, Canada, UK, EEA countries, Switzerland, Australia, New Zealand, Japan, Singapore, Hong Kong, Brazil, Mexico, India, and a growing list of others). Even where Connect is available, some countries are gated behind *invite-only* review or beta access. Before you build out a marketplace, confirm Connect is generally available in your platform’s country on Stripe’s [Connect availability](https://docs.stripe.com/connect/availability) page. If your platform country is invite-only or unsupported, no amount of plugin configuration will create transfers.

**Transfers outside supported corridors will fail.** For example, a US platform account cannot create transfers to an Australian or Japanese connected account. Stripe will return an error if you attempt this.

## Stripe's transfer regions

Stripe groups countries into regions for the purpose of Connect transfers. Transfers are permitted **within a region** and also **across certain supported corridors**.

| Region | Countries / Area |
| --- | --- |
| **United States** | US |
| **Canada** | CA |
| **United Kingdom** | UK |
| **EEA (European Economic Area)** | Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Liechtenstein, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden |
| **Switzerland** | CH |
| **Australia** | AU |
| **Japan** | JP |
| **Other** | Additional regions per Stripe's [cross-border documentation](https://docs.stripe.com/connect/cross-border-payouts) |

## Cross-border corridor exception

Stripe supports **cross-border transfers on the payments balance** between the following regions:

*   **United States**
*   **Canada**
*   **United Kingdom**
*   **EEA** (European Economic Area)
*   **Switzerland**

This means a US platform *can* transfer to connected accounts in Canada, the UK, EEA countries, and Switzerland — and vice versa. Transfers between any two regions in this corridor are supported.

**Example:** A US-based platform can transfer to a connected account in Germany (EEA), the UK, or Canada. A French platform can transfer to a connected account in the US or Switzerland. All combinations within this corridor are supported.

**Cross-border transfers carry a 0.25% Stripe fee.** Stripe charges 0.25% of each cross-border transfer to cover regulatory and processing costs. The fee is waived for transfers within the EEA and between the UK and the EEA — so a Greek platform paying a German or UK vendor pays no fee, while the same platform paying a US vendor pays 0.25%. This is a Stripe fee, not a Split Pay fee; see Stripe's [cross-border payouts documentation](https://docs.stripe.com/connect/cross-border-payouts) for current pricing.

**Outside the corridor:** Regions not listed above (Australia, Japan, Brazil, etc.) do **not** participate in cross-border transfers. Platforms in those regions can only transfer to connected accounts within the same country.

## Stripe's official position

From Stripe's [documentation on Separate Charges and Transfers](https://docs.stripe.com/connect/separate-charges-and-transfers#transfer-availability):

> "Stripe supports cross-border transfers on the payments balance between the United States, Canada, United Kingdom, EEA, and Switzerland. In other scenarios, your platform and any connected account must be in the same region."

This means the charge type used by Split Pay (Separate Charges and Transfers) supports transfers within the same region **and** across the US/CA/UK/EEA/CH corridor. All other cross-border transfers will fail.

## Workarounds for unsupported regions

If your vendors are in regions outside the supported corridor (e.g., Australia, Japan, Brazil), the following workarounds are available:

### Option 1: register your platform in the vendor's region

If you primarily work with vendors in a specific region, consider registering your Stripe platform account in that region. For example, if most of your vendors are in Australia, register your Stripe account as an Australian entity.

This typically requires a legal entity (business registration) in that region. Consult with a legal or financial advisor before setting up cross-border business structures.

### Option 2: direct or destination charges (not currently supported)

Stripe offers alternative charge types — **Direct Charges** and **Destination Charges** — that have different cross-border capabilities. Split Pay currently uses the **Separate Charges and Transfers** model. While this model does support cross-border transfers within the US/CA/UK/EEA/CH corridor, Direct or Destination Charges may offer additional flexibility for other regions.

Support for Direct or Destination charge types may be considered in future versions. If this is critical for your business, please [contact our support team](https://gauchoplugins.com/support) to express interest.

### Option 3: manual payouts outside Stripe

For international vendors in unsupported regions, some businesses handle payouts manually using alternative methods such as:

*   Bank wire transfers
*   PayPal payouts
*   International payment services (Wise, Payoneer, etc.)

In this case, you would use Split Pay's [transfer tracking](../../features/viewing-transfers/) to calculate the amounts owed, then process the actual payout through your preferred international payment method.

## Built-in country/region warning

Split Pay automatically detects when your connected accounts are in a different country than your platform account and displays a warning on the **Integrations** tab (top-level **Split Pay** menu, 3.7.0+). On Split Pay versions before 3.7.0 the same warning appeared on the legacy *Stripe Configuration* tab.

**Proactive detection.** When you sync your connected accounts, the plugin stores each account's country. If any account's country doesn't match your platform country, a warning box appears listing the mismatched accounts — helping you catch region issues before transfers fail.

The warning shows:

*   Your platform account's country (e.g., "United States")
*   Each connected account that doesn't match, along with its registered country
*   A message indicating which accounts may be affected by region restrictions

This check runs every time you visit the Integrations tab, so you'll always know if a newly connected account has a country mismatch. Accounts within the supported cross-border corridor (US, CA, UK, EEA, CH) will still work, but accounts outside the corridor will fail.

## How to check your account's region

To verify your Stripe account region:

Log in to the [Stripe Dashboard](https://dashboard.stripe.com).

Navigate to **Settings → Business details**.

Your registered country determines your region. Compare it against the regions table above.

To check a connected account's region, go to **Connect → Accounts** and view the account's country. Or simply check the **Split Pay → Integrations** tab for the built-in warning described above.