PLAYBOOK · BANKING · CRYPTO
Virtual IBANs for FCA-Registered Crypto Exchanges
GBP and EUR rails that survive MLR scrutiny
FCA-registered crypto firms occupy the most banking-hostile corner of UK fintech. This playbook covers what virtual IBANs actually solve for a crypto exchange, why generic EMI accounts get closed within 90 days, and how to structure a banking stack that holds up to MLR audits and Travel Rule obligations.
Why crypto exchanges need vIBANs, not bank accounts
A UK crypto exchange registered under the FCA's MLR regime has two banking problems a standard corporate account cannot solve. The first is segregation: customer fiat held against pending crypto trades must be ringfenced from operating funds, with a clear audit trail from individual customer deposit to pooled custody and back out on withdrawal. The second is correspondent banking risk. Tier-1 UK banks deboard registered cryptoasset firms on a near-quarterly basis, and even where an account survives, inbound SEPA from crypto-adjacent counterparties triggers manual review that breaks the customer experience. Virtual IBANs solve both. Each customer is issued a dedicated GBP or EUR IBAN that routes to a single pooled safeguarded account at the EMI. Deposits land pre-attributed, with no reference-matching, no orphaned payments, and no manual reconciliation.
WHAT GOES WRONG WITH GENERIC EMI ACCOUNTS
Crypto exchanges that open a single shared EMI account and use payment references to attribute deposits typically last 60 to 120 days before the EMI's compliance team notices the volume of inbound from retail individuals, flags it as unlicensed money transmission, and closes the account. The vIBAN structure is materially different — each IBAN is a customer-specific identifier issued under the EMI's own permissions, which is what the EMI's MLRO approved when onboarding the programme.
The regulatory stack underneath
Three frameworks govern how a vIBAN programme for an FCA-registered crypto firm must be operated. The FCA's Money Laundering Regulations (MLR 2017, as amended) apply to the cryptoasset firm itself and dictate customer due diligence depth, source-of-funds expectations, and ongoing monitoring. The EMI providing the vIBAN rails operates under the Electronic Money Regulations 2011, which impose safeguarding obligations — customer funds are pooled and held either in a segregated account at a credit institution or in qualifying liquid assets. And the Travel Rule, transposed into UK law via MLR amendments effective September 2023, requires originator and beneficiary information to flow with crypto transfers above £1,000. In practice the vIBAN provider needs documented evidence they understand the crypto programme before issuing. Generic EMI applications submitted without a crypto-specific compliance pack are routinely rejected at underwriting.
Provider landscape for crypto vIBANs
| Provider tier | Typical setup | Reality for crypto |
|---|---|---|
| UK clearing banks (direct) | GBP CHAPS/Faster Payments, no vIBAN layer | Almost no appetite for FCA-registered crypto firms; relationships are rarely opened from cold |
| UK EMIs with crypto programmes | GBP Faster Payments vIBANs, sometimes SEPA via EU subsidiary | Realistic primary GBP rail; underwriting takes 6-12 weeks; volume and AML caps apply |
| EU EMIs (Lithuania, Ireland, Netherlands) | SEPA and SEPA Instant vIBANs in EUR, sometimes GBP via correspondent | Strong for EUR; crypto-specific desks exist; MiCA alignment increasingly required |
| Multi-provider stacks via consultancy | GBP from EMI A, EUR from EMI B, USD from correspondent | How most production exchanges run — redundancy is the point |
The single-provider model is structurally fragile for crypto. When (not if) an EMI tightens its crypto programme, exchanges with one rail face an existential disruption. Production exchanges typically run at least two GBP routes and two EUR routes, with customer deposit IBANs failover-routed at the application layer.
Money flow and what to have ready
- Customer signs up and completes KYC and source-of-funds checks at the exchange level
- Exchange requests vIBAN issuance from the EMI via API, passing verified identity data
- EMI issues a dedicated GBP IBAN (or EUR, or both) that the customer sees in their exchange account
- Customer deposits GBP via Faster Payments to the dedicated IBAN; EMI credits the pooled safeguarded balance and notifies via webhook
- On withdrawal, the exchange instructs the EMI to send GBP out, with Travel Rule data attached where the originating crypto transaction triggered the threshold
BEFORE YOU APPROACH PROVIDERS
Have your FCA registration confirmation, MLRO-signed risk assessment, Travel Rule tooling evidence (provider name and integration status), wallet screening procedure, customer onboarding flow documented end-to-end, and 12-month volume projections by currency and channel. Programmes presented without these materials are declined before underwriting — not because the exchange is unsuitable, but because the EMI's compliance team cannot defend the file internally. Underwriting typically runs six to twelve weeks per provider; faster outcomes usually signal a provider with limited crypto experience and higher downstream closure risk.
Common failure modes
- Single-provider concentration where one EMI policy change kills the programme overnight
- Mixing crypto and non-crypto flows through the same vIBAN structure, triggering EMI re-review
- Treating the EMI as a black box rather than monitoring their regulatory posture and public accounts
- Inadequate Travel Rule integration causing outbound delays that become customer complaints and then EMI escalations
- Onboarding customers from jurisdictions the EMI's programme excludes, then arguing about it after the fact
HOW ICETREE APPROACHES IT
Our approach for merchants in this combination.
- We map your projected GBP, EUR, and USD volumes against partners in our network with live, currently-issuing crypto programmes — not historical relationships
- We prepare the compliance pack EMIs actually want to see, drawing on what has cleared underwriting in the last six months
- We structure multi-provider redundancy from day one so a single EMI policy change does not stop deposits
- We sit between you and the partner during underwriting, translating crypto operations into the language EMI compliance teams use
- Free to you — partners pay us on placement, so we have no incentive to push you toward the partner who pays the most
FAQ
Common questions answered.
RELATED PLAYBOOKS
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 .