Paying Marketplace Sellers in Their Local Currency
The short answer
A marketplace that pays all sellers in one currency forces every non-euro seller through a retail FX conversion on their statement — a spread they can see, and a reason to question the platform. Paying in each seller's local currency removes that spread and keeps loyalty (and margin) on the platform. A stablecoin settlement layer makes native multi-currency payouts a configuration, not a banking programme.
The cost of one currency for a continent
Settle in EUR and the seller's bank does EUR → local at a retail rate with a fee. The marketplace never sees it; the seller does, every cycle. Across thousands of sellers it's a quiet tax on the whole network — and a churn driver you can't measure on your own P&L.
| Single-currency payout | Native payout | |
|---|---|---|
| Seller receives | EUR, converts retail | SEK / PLN / CZK directly |
| FX spread | Taken by seller's bank | Quoted or captured by you |
| Seller loyalty | Eroded by "lost" FX | Strengthened |
Why marketplaces default to one currency
Adding a payout currency used to mean a banking relationship and often a local entity per market. So platforms pick one and push the conversion downstream. With a settlement layer, 35 currencies are one integration — the rails are rented, not owned, so the currency count climbs without the calendar exploding.
The seller doesn't care about your banking relationships. They care that the number on their statement is right.
What changes
Sub-account per seller, payout in their currency, one record across all of them. The FX you'd have handed to the seller's bank becomes a quoted rate you control. See the SEK/PLN/CZK breakdown in Paying Merchants in SEK, PLN and CZK.
The bottom line
Native payouts are cheaper to build than they used to be and more sticky than they look. The single-currency default is a legacy of expensive rails, not a constraint anymore.
We'll tell you honestly whether we can move it — including when the answer is no.
Get a demo