Fiat on/off-ramp accounts for crypto and stablecoin platforms

A crypto platform that converts USD to USDC and sends it to a customer's wallet, or receives fiat against a stablecoin redemption, needs to prove per-client ownership of every fiat balance in real time. That proof is either built into the account structure or it depends on a database that can drift. This is a custody-architecture decision, and it decides what happens to customer funds if the platform fails.

What is fiat on/off-ramp infrastructure?

Fiat on/off-ramp infrastructure is the set of bank accounts and payment rails that connect fiat currency to a digital-asset platform. An on-ramp takes fiat in and results in crypto or stablecoins in the customer's wallet. An off-ramp takes digital assets in and results in fiat paid out to the customer.

The mechanics are concrete:

• On-ramp. A customer sends USD, EUR, GBP, or AED to the platform. The platform credits the customer, then mints or transfers stablecoins, for example converting USD to USDT or USDC and sending it to the client's wallet.
• Off-ramp. A customer redeems stablecoins or sells an asset. The platform receives the digital leg and pays fiat out to the customer's bank account.
• The reconciliation requirement. Every one of these fiat movements has to be tied to a specific end customer, on receipt and on payout, not at the end of the day.

The fiat leg is where the regulatory and counterparty risk sits. The correspondent dollar and the stablecoin dollar are different instruments, but a platform that offers an on/off ramp lives in both worlds at once and has to reconcile between them precisely.

Why per-client reconciliation matters

The default way platforms build the fiat leg is a single pooled or omnibus account: one bank account in the platform's name, holding every customer's fiat, with an internal ledger recording each customer's share. It is fast to open and cheap to run. It also carries a structural failure mode.

The risk is the gap between what the bank sees and what the customer believes. The bank sees one aggregate balance. The customer assumes an individual account. If the platform's ledger drifts from the bank's records, or the platform becomes insolvent, there is no structural mechanism to establish who owns what. This is the model behind an FBO account, and it is the model that broke.

When Synapse collapsed in April 2024, roughly $265 million across 100,000 accounts was frozen because partner banks could not reconcile beneficial ownership from the internal ledger, as CNBC's reporting on the trustee's findings detailed. The funds existed. The reliable link between each customer and their share did not. That is precisely the exposure a crypto platform inherits when its fiat on/off ramp runs on a pooled account.

Regulation is closing on this directly. The GENIUS Act requires stablecoin issuers to hold 100% reserves in segregated assets and prohibits commingling, and comparable segregation-at-receipt rules are arriving under PSD3 and the FCA's safeguarding regime. Pooled fiat that mixes customer and operational funds sits on the wrong side of that line.

How named on/off-ramp accounts work

A named account inverts the pooled model. Instead of one omnibus account with an internal ledger, each end customer receives a named virtual account in their own name at the custodian. These are named virtual accounts that receive and send funds against the platform's stablecoin wallet, one per client, so attribution is built into the account rather than derived from a database.

The operational flow becomes clean:

• Inbound attribution. Fiat arriving into a customer's named virtual account is that customer's, by construction. There is no matching step to get wrong.
• Outbound attribution. Fiat paid out on an off-ramp leaves the correct named account. The audit trail is the account itself.
• Balance verification, not reconciliation. The sum of all named accounts equals total funds under custody at any moment. Segregation is architectural, not contractual, so there is no ledger to diverge from the bank balance.

The historical objection to named accounts was speed and cost: opening thousands of individual accounts was slow. API-based provisioning removes that objection. Platforms open named custody accounts programmatically, keeping the onboarding speed of a pooled model while gaining structural segregation, exactly as set out in named accounts vs. pooled accounts.

The fiat still has to clear. Lorum provides global multi-currency clearing with direct access to local rails, so the on-ramp and off-ramp legs settle with certainty across USD, EUR, GBP, and AED, and the fiat and stablecoin ledgers stay reconciled by design, a convergence covered in stablecoins and fiat clearing.

Named on/off-ramp accounts vs pooled reconciliation

The two architectures differ on every dimension that matters when a regulator, an auditor, or an insolvency practitioner asks who owns the fiat.

The infrastructure decision

For a crypto exchange, stablecoin platform, or VASP, the fiat on/off ramp is not a payments feature. It is a custody decision that determines regulatory posture, counterparty risk, and what happens to customer funds if the platform fails. A pooled account defers that risk into a ledger. A named account removes it by construction.

Lorum is a globally licensed specialist correspondent institution. It operates a non-lending, 100% reserve model focused on three functions: global multi-currency clearing, named custody accounts, and cash management including wholesale FX. It is the fiat leg of an on/off ramp built to a fiduciary standard, so that for fintech and PSP platforms the funds are provably there because the architecture guarantees it, not because a reconciliation happened to run clean that day.

Frequently asked questions