Stripe's two cross-border payment products: why most coverage gets the difference wrong

Stripe has two cross-border outbound payment products. Most coverage treats them as one. They aren't the same thing — they have different scopes, different fees, different prerequisites, and different futures. If you're evaluating Stripe for international payouts, knowing which is which changes what you build.

Why this distinction matters

Search results for “Stripe cross-border payments” return a wide mix of product descriptions. Some pages describe the Stripe Connect feature; some describe the standalone product; many describe both as if they were one thing. That ambiguity costs builders real time: choosing the wrong product means re-architecting if the requirements don't fit.

The two products solve different jobs. Cross-Border Payouts exists for platforms — marketplaces moving money from their balance to sellers / contractors who are registered as Stripe Connect accounts. Global Payouts exists for anyone sending money to a recipient who doesn't need to have a Stripe account at all. That's the structural difference that drives everything else.

Cross-Border Payouts: the Connect feature

Cross-Border Payouts is a feature inside Stripe Connect, the product Stripe sells to marketplaces and platforms. It moves money from a platform's Stripe balance to a connected account in a different country, settling the connected account's payout in their local currency.

Where it works. Platforms based in the US, UK, EEA member states, Canada, or Switzerland can pay connected accounts in the same set of countries. A US-based platform pays a UK seller; a German platform pays a Canadian contractor. The list is closed: same five regions in, same five regions out.

Where it doesn't work. Outside of those five regions. A US platform that needs to pay a seller in Japan, the Philippines, Brazil, India, or most of Asia doesn't have a Cross-Border Payouts option. The Connect feature isn't built for those corridors.

What it costs. 0.25% per cross-border transaction. Intra-EEA and UK ↔ EEA transfers are free. Currency conversion (when sending to a country with a different currency than the platform's account) carries a separate Stripe FX markup.

What you need. Stripe Connect, configured for Custom or Express connected accounts under a Full Service Agreement with Stripe — the agreement that lets a platform handle API-based onboarding for its sellers rather than redirecting them to Stripe-hosted onboarding. Standard connected accounts (where the seller manages their own Stripe relationship) don't get this feature.

Concrete shape: a US-based marketplace paying a Canadian seller $20,000/week via Stripe Connect pays Stripe $50/week in Cross-Border Payouts fees, plus whatever currency-conversion markup applies (Canadian sellers receive CAD). Standard platform economics; this is the use case the feature was built for.

Global Payouts: the broader product

Global Payouts is a standalone API product launched in its current form during 2024–2025. It moves money from a Stripe balance (or a Stripe Treasury / Stripe Financial Connections account) to a recipient's bank account, debit card, or stablecoin wallet. The recipient doesn't need a Stripe account. The sender doesn't need Stripe Connect.

Where it works. Stripe documents 60+ recipient countries direct, with a wider reach (150+ countries) via partner integrations for local-currency settlement. The spread relative to Cross-Border Payouts is substantial — Global Payouts reaches Latin America, much of Asia, Africa via Paystack, and several Middle East corridors that Cross-Border Payouts doesn't.

What it's for. The use cases Stripe documents include freelancer payments, insurance claim disbursements, affiliate revenue distribution, marketplace seller payouts (where Connect isn't the right shape), employee payroll for remote teams, and reward / rebate programmes. Anything where the sender has a Stripe balance and needs to push money out to many recipients across countries.

How it gets there. Global Payouts is a router rather than a single rail. Depending on the recipient's country, currency, and chosen delivery method, the payment runs over ACH or FedNow (US), SEPA or SEPA Instant (EU), Faster Payments (UK), Visa Direct or Mastercard Send (debit-card destinations), SWIFT (catch-all), local instant payment systems where Stripe has partner integrations, or stablecoin rails (USDC over Polygon or Base via Stripe's Bridge integration). The sender doesn't pick the rail manually; Stripe routes based on what's available and cheapest for the destination.

What's unique: stablecoin destination. Of the three major payment platforms with global payout offerings (Stripe, Adyen, Wise), Stripe is currently the only one with production stablecoin payouts via its 2024 Bridge acquisition. A recipient who wants to receive USDC in a wallet rather than fiat in a bank account is supported. Adyen is in cautious exploration; Wise has not committed.

No Stripe Connect required. This is the product's defining difference from Cross-Border Payouts. A SaaS company paying overseas freelancers, an insurance company processing claims internationally, an HR-tech platform running contractor payouts — none of these need to set up Stripe Connect to use Global Payouts. They configure recipients, fund a Stripe balance, and call the API.

Why two products, and which is the future

Cross-Border Payouts came first — it was built as part of Stripe Connect, designed for the original Stripe target customer (marketplaces and platforms) and shaped by what Stripe could support via its early sponsor-bank relationships in the US, UK, EU, Canada, and Switzerland. Those corridors were where Stripe had banking depth in the 2018–2022 era when the product matured.

Global Payouts is the broader bet — built later, designed for every use case Stripe Connect wasn't optimised for. Stripe's 2024–2025 acquisitions of Bridge (stablecoin infrastructure) and Privy (embedded wallets), and the launch of Tempo (a stablecoin-native L1 with Paradigm), all map onto Global Payouts rather than Cross-Border Payouts. The product roadmap signal is consistent: Global Payouts is where Stripe is investing.

Stripe hasn't announced a sunset date for Cross-Border Payouts and there's no indication that existing Connect platforms using it will lose the feature. But the trajectory is clear: a new builder evaluating Stripe for international outbound payments today should default to Global Payouts unless they have a specific Connect-shaped requirement.

Which one to use

The decision is mechanical once the use case is named:

• You're a marketplace paying sellers in US, UK, EEA, Canada, or Switzerland — and the sellers are set up (or willing to be set up) as Stripe Connect accounts. Use Cross-Border Payouts.

• You're anyone else — SaaS paying freelancers, insurance disbursements, contractor payouts, remote payroll, affiliate programmes, marketplace seller payouts to countries outside the Cross-Border set. Use Global Payouts.

• You need stablecoin destination — any recipient who wants USDC. Global Payouts is currently the only Stripe option, and Stripe is currently the only mainstream payment platform with production stablecoin payouts.

• You're a small business doing modest volumes of cross-currency transfers (the textbook Wise use case). Global Payouts works, but for pure transparency on FX rates, Wise Platform may price better. We cover that comparison in a separate piece.

What this means for US→Philippines remittance

Neither Stripe product is a consumer-remittance tool. They're B2B-shaped — funded from a Stripe balance, called via API, used by businesses pushing money out to many recipients. A US individual sending money to family in the Philippines doesn't open a Stripe account.

Where these products do touch the corridor is at the freelancer and contractor-payout layer. A US-based platform paying remote workers in the Philippines uses Global Payouts; the worker receives PHP into a bank account or e-wallet (or, increasingly, USDC into a wallet they manage themselves). That's adjacent to consumer remittance but operates on different rails — the sender is a business, not an individual. The legal and tax dimensions of paying contractors in USDC are walked through in the

stablecoin salary + payroll-tax piece

.

For the actual consumer remittance question, see the

USDC vs Wise comparison

and the live calculator. Both reflect the cost the route actually delivers today.

Verify against Stripe's own documentation

Country lists, fee percentages, and supported payment methods change. The authoritative source is Stripe's product documentation:

• Stripe Connect Cross-Border Payouts documentation

• Stripe Payouts (broader product documentation)

• Stripe global availability and coverage matrix

• Stripe pricing (current fees by product)

Companion pieces:

Stripe's Tempo, the launch-month reality check

(the chain-side companion to this rails-side piece — why Stripe's own L1 matters to Global Payouts' stablecoin destination story),

Two stablecoin worlds: Tempo, Plasma

(the strategic framing the stablecoin-posture comparison in this piece sits inside),

Stablecoin salary + payroll-tax

(the legal and tax dimensions of paying contractors in USDC — the contractor-payouts pivot from the PH-corridor section above), and

USDC vs Wise for the Philippines

(the consumer-corridor comparison for readers who landed here looking for a remittance answer).

This guide is editorial framing of Stripe's product documentation, not affiliated with or endorsed by Stripe.