.jpg)
OpenPayd and Lorum both appear in infrastructure evaluations for platforms that need multi-currency accounts and access to local payment rails. Both offer API-driven services, both serve regulated institutions, and both let a platform give its customers their own account details.
The differences are in how the account is structured underneath. OpenPayd issues virtual IBANs against a pooled master account. Lorum provisions named accounts in the end customer's name at the custodian level. That distinction shapes everything from fund attribution to the regulatory profile.
This comparison covers the structural differences between the two providers. It is not a ranking. Both serve legitimate use cases, and the right choice depends on the platform's operational requirements, regulatory obligations, and whether its primary infrastructure need is embedded multi-currency accounts or named custody and clearing.
What OpenPayd provides
OpenPayd is a financial infrastructure provider regulated as an electronic money institution under the FCA, with additional coverage across the EU. It offers embedded finance through a single modular API covering accounts, payments, FX, and virtual IBANs, processes a reported $240 billion annually, and serves banks, fintechs, PSPs, and crypto exchanges.
OpenPayd's core strength is its developer experience and account coverage. Clients can hold accounts in more than 35 currencies, including USD, GBP, EUR, CHF, CAD, JPY, and AUD, through one API, and convert between them at wholesale rates with real-time settlement. The platform is well documented, with a sandbox and an integration path designed to take clients live in days.
The account model is built around a master account, also described as a pooled account, with sub-accounts and virtual IBANs issued beneath it. A platform opens a master account in EUR or GBP, then provisions unlimited virtual IBANs for its customers, with segregation handled through ledger attribution. Coverage is centred on the UK and EU, with further regions served through partners.
What Lorum provides
Lorum is a globally licensed specialist correspondent institution holding six regulatory licences across multiple jurisdictions. The infrastructure is focused on three functions: multi-currency clearing across 30+ markets, named custody accounts, and cash management including wholesale FX. Lorum does not operate a lending book and holds all client funds in 100% reserve.
The account model is structurally different. Lorum provisions named accounts in the end customer's name, each with its own KYC profile and a direct link to the custodian. The custodian knows who the end customer is at the point of clearing, rather than seeing only the platform. The model supports safeguarding, operational, escrow, and stablecoin wallet account types.
Lorum's clearing connectivity spans USD (Fedwire, ACH), EUR (SEPA, SEPA Instant), GBP (Faster Payments, CHAPS), AED (IPP, FTS), and other currencies through direct access to local rails. The platform serves payroll and EOR platforms, fintech and PSPs, trading platforms, and marketplaces across Europe, the Middle East, Asia, and the Americas.
A structural comparison
The table below outlines where the two providers differ across key infrastructure dimensions. These are architectural differences, not feature rankings.
Where each provider fits
OpenPayd is well suited to platforms whose primary requirement is embedding multi-currency accounts and payments into their own product quickly. Its API is among the more developer-friendly in the market, and for fintechs, payout platforms, marketplaces, and exchanges issuing large numbers of virtual IBANs, it offers a mature route with broad currency coverage through a single integration.
Lorum addresses a different set of requirements. Platforms that need named custody accounts rather than virtual IBANs under a master account will find a different architecture: a direct link between the custodian and the end customer, satisfying requirements that are tightening under the FCA's safeguarding regime and PSD3. Clearing spans 30+ markets with direct access to local rails.
The business model difference also matters for counterparty risk. OpenPayd holds client funds under a master account with ledger-level segregation, while Lorum operates independently as a non-lending, 100% reserve institution with funds in individually named accounts. For platforms under safeguarding rules, that difference affects both the audit burden and where client funds sit in an insolvency.
The infrastructure decision
The choice between OpenPayd and Lorum is not about which provider is better. It is about whether the platform's primary need is embedded multi-currency accounts or named custody and clearing. A fintech building international accounts with fast onboarding has different requirements from a payroll platform holding employee funds in named, segregated accounts across jurisdictions.
As regulatory frameworks converge on stricter fund segregation and custody requirements, the distinction between pooled and named architectures becomes more consequential. Platforms should evaluate the account structure, the regulatory framework governing fund protection, and the geographic coverage required, including whether it is direct or partner-routed.
They should also weigh whether the provider's FX capability matches the platform's conversion needs, and how client funds are positioned in the event of provider failure. The answers to these questions will determine which infrastructure is the right fit.
.jpg)
