Every platform that scales globally hits the same wall: to collect funds in a new currency, you typically need a local banking relationship, a local account, and a separate reconciliation process to match. Multiply that by every market you enter, and "going global" starts to look like running 20 different local back-office operations at once, creating fragmented operations that are harder for finance and operations teams to manage.
Mangopay Virtual Accounts were built to remove that friction, with one architecture applied the same way, currency by currency. Today, we're extending that coverage from seven to 24 currencies.
Mangopay Virtual Accounts now support 24 currencies, all delivered through our existing LU IBAN.
The new currency list: AED, AUD, CAD, CHF, CNH, CZK, DKK, EUR, GBP, HKD, HUF, ILS, JPY, MXN, NOK, NZD, PLN, RON, SAR, SEK, SGD, TRY, USD, ZAR
Each wallet holds exactly one currency.
Each Virtual Account is attached to exactly one wallet.
Each Virtual Account, therefore, supports exactly one currency.
There's no blending, no conversion, and no single account that accepts all 24 currencies. For example, a Virtual Account in MXN only ever holds and reports MXN. This is a deliberate design choice: keeping each currency in its own wallet and its own account means clean, independent reconciliation. Every balance and every set of account details maps to exactly one currency, with no ambiguity about what landed where.
For platforms operating across multiple markets, currency infrastructure is rarely the exciting part of going global, but it's one of the most operationally painful. The alternative to a setup like this is usually a patchwork of local accounts, correspondent banking arrangements, and manual reconciliation processes that don't scale and don't talk to each other.
Virtual Accounts change that equation. By attaching a dedicated account to each wallet, platforms get one IBAN per currency, issued through Mangopay's payments infrastructure, instead of negotiating and maintaining separate banking relationships themselves. Payers still get something concrete to send funds to, like a named, real account rather than a generic reference, but the real win is on the platform side: less banking admin and fewer reconciliation headaches.
For finance teams, it means cleaner books. Each payment maps to one wallet, one currency, one account. Reconciliation becomes a byproduct of the architecture rather than a separate workload.
For product and ops teams, it means faster market expansion. Adding support for a new currency no longer requires a separate banking setup or integration work. Platforms already using Mangopay Virtual Accounts can extend into new currency corridors without changing their main architecture.
For platforms with complex fund flows - marketplaces managing buyer payments, seller payouts, and platform fees across multiple markets - the consistency of the model matters as much as the coverage. Every currency works the same way. Every Virtual Account behaves the same way. The operational logic doesn't need to change as you grow.
The best payment infrastructure is the kind your customers never think about. A buyer in Tokyo sends JPY, the seller in Johannesburg receives ZAR. The platform sees clean balances, clean reconciliation, with no manual intervention. With Mangopay, you receive in JPY, convert via our wallets, and send local payouts in ZAR.
That's what 24-currency Virtual Account coverage is designed to make possible. Not a new feature to manage, but one less thing standing between your platform and the markets you're building for.
If your platform is expanding into new currency markets, contact us to learn how virtual accounts can support your plans.
Availability is subject to vertical, region, and risk profile.