PLAYBOOK · BANKING · iGAMING
Multi-Currency Accounts for High-Volume iGaming Operators
segregated, safeguarded, FX-efficient
iGaming operators need a banking stack that survives a regulator's player-fund reconciliation request, settles PSP flow in 10+ currencies, and doesn't leak GGR to FX. Generic business accounts close gambling MCCs the moment they see them. This playbook shows the three-account architecture that actually works across MGA, UKGC, Gibraltar and Curaçao licences.
Most iGaming operators discover within their first month of multi-jurisdiction trading that a standard business current account cannot carry the load. Player deposits arrive in EUR, GBP, CAD, BRL and crypto-on-ramped stablecoins; PSP settlements land in mixed currencies on T+2 to T+7; supplier payments demand EUR and USD; and the regulator wants a separately identifiable player liability balance at all times. A generic multi-currency wallet — the kind a SaaS company uses — fails at the regulatory, FX and AML layers.
Why a generic wallet fails for iGaming
Most digital business accounts are built for e-commerce or SaaS — single liability holder, predictable inflows, low-risk MCC. iGaming breaks every assumption. Deposits are customer liabilities (not revenue) until played; chargeback risk is concentrated in cards but settlement happens via 20+ APMs; and the regulator can demand a reconciliation between liability ledger and bank balance with 24 hours' notice. EMI-issued IBANs from generic providers typically restrict gambling MCCs in their terms of service. When compliance flags inbound PSP settlements with gambling references, the account is frozen — often mid-weekend, with player withdrawals queued.
WORTH KNOWING
Under MGA Directive 2 of 2018 (Player Protection Directive), licensees must maintain player funds in a separate, identifiable account before the licence is even issued. The MGA reserves viewing rights over the account. Curaçao's LOK regime (in force since 2024) imports a comparable segregation test. UKGC operators at 'medium' protection level must hold player funds in a separate bank account; 'high' protection requires a trust or insurance wrapper.
The three-account architecture
| Account | Purpose | Provider type | Currencies |
|---|---|---|---|
| Player liability | Holds deposits and pending withdrawals. Segregated, reconciled daily to the wallet ledger. | Tier-2 bank or EMI with documented gambling programme and safeguarding under EMI/PSR rules | GBP, EUR + 2-4 player-facing currencies |
| Operational multi-currency | PSP settlements land here; outbound supplier and tax payments; FX hub | EMI or challenger bank with multi-currency IBANs and gambling-permitted MCC | 8-15 currencies incl. CAD, BRL, MXN, NZD, ZAR |
| Treasury / corporate | Profit retention, group treasury, dividends, GGR tax warehousing | Tier-1 or tier-2 bank in the licensing jurisdiction | Base currency + USD |
- Player deposits land at the PSP in the player's local currency; PSP settles T+2 to T+7 to the operational account.
- A scheduled sweep moves the player-liability portion into the segregated account, sized against the live liability ledger.
- Withdrawals are paid from the segregated account directly to the player's original deposit method.
- Operational expenses are paid from the operational account after FX conversion at the EMI's spread.
- Profit is swept weekly or monthly into the treasury account; gaming duty and GGR tax are accrued into a sub-ledger.
The FX problem nobody warns you about
A Tier-1 operator running across the UK, Germany, Brazil and Canada will see 1-2% of GGR evaporate into FX spread if it relies on a single base-currency account. PSP settlements are forced into the base currency at the acquirer's spread (typically 1.5-3.5%), then reconverted out for supplier payments at the bank's spread (1-2%), then converted again for affiliate payouts. A multi-currency IBAN setup — where each player-facing currency settles into its own balance and is held until matched against an outbound need — collapses two of those three conversions. For a £40M GGR operator, this can mean six- to seven-figure annual savings.
Provider landscape
| Provider type | Best for | Watch-outs |
|---|---|---|
| EU EMIs with documented gambling programmes (Lithuania, Malta, Estonia licences) | Operational multi-currency account, safeguarded player balances, 10+ IBANs | Volume caps, conservative withdrawal limits, monthly source-of-funds reviews |
| UK EMIs under FCA EMR with gambling appetite | GBP UKGC-aligned segregation, Faster Payments out | Few have explicit gambling permissions; vetting is heavy |
| Tier-2 banks in Malta, Gibraltar, Isle of Man | Treasury and corporate account in licensing jurisdiction | Slow onboarding (3-6 months), high minimum balances |
| Crypto-friendly EMIs / VASPs | Stablecoin on/off-ramps for crypto-permitted licences (Curaçao LOK, Anjouan) | Often refuse fiat gambling MCCs; use as an adjunct |
| Correspondent / SWIFT-only banks | High-value B2B supplier payments, group treasury | No multi-currency IBANs; not suitable for player flow |
- Apostilled licence copy and corporate structure chart, plus KYC packs on every UBO.
- Player fund reconciliation methodology signed by the MLRO and finance director.
- Source-of-funds / source-of-wealth files for UBOs — MGA IIPRD or FCA-aligned MLR.
- PSP settlement letters confirming which acquirers settle into the account and in what currencies.
- Geo-blocking and player verification policy showing how unlicensed-jurisdiction deposits are prevented.
Plan for 8-16 weeks from first introduction to a live multi-currency stack for a freshly licensed operator. Operators with an existing licence and clean operating history (12+ months, no regulatory actions) often close in 4-8 weeks. The cost structure is usually a setup fee per IBAN, a monthly account fee per currency, transaction fees on inbound and outbound (lower on SEPA/Faster Payments, higher on SWIFT), and an FX margin of 0.4-1.5% depending on volume tier. Some EMIs require a security deposit or rolling reserve against the safeguarded balance — typically 2-5% of average player liability.
BEFORE YOU APPROACH PROVIDERS
Have your licence(s) issued (or in advanced application), a finalised corporate structure with KYC packs on each UBO, your PSP settlement contracts, a reconciliation policy signed by the MLRO, and a 12-month volume forecast broken down by currency. Operators who arrive with this pack typically get terms in 3-4 weeks; those without spend the first six weeks gathering it under pressure.
HOW ICETREE APPROACHES IT
Our approach for merchants in this combination.
- We map your licence-by-licence segregation obligations before introducing any provider — MGA Directive 2 of 2018, UKGC LCCP, GRA Code of Practice and Curaçao LOK each demand a different shape of account.
- We match you to EMIs and banks that have documented gambling MCC permissions in writing, not verbal assurances that fail at month three.
- We model your FX leakage across base-currency vs multi-IBAN settlement and present the annual saving before you commit to a provider.
- We run all introductions in parallel so you have two or three offers to compare — single-provider dependency is the largest operational risk in iGaming banking.
- We stay in the loop through onboarding and reconciliation policy sign-off, so your MLRO and finance director are aligned with the provider's expectations from day one.
FAQ
Common questions answered.
Want IceTree on your side?
Run the Approval Predictor for a 2-minute estimate of your acquirer fit, expected reserve range, and what to prepare — specific to and .