A service that converts national currency into digital assets, the inverse of an off-ramp. The same service is called a fiat on-ramp or a crypto on-ramp, and using one is on-ramping. It stands between a bank payment rail and a blockchain: it takes a debit from a card, a bank transfer or an instant payment, verifies who is paying, and delivers an asset to an address. Every on-ramp produces a record of that conversion, and since 1 January 2026 the larger ones report it.
The routes, and what each one leaves behind
The word covers five distinct arrangements. They differ less in what the buyer receives than in who holds the record afterwards.
| Route | What it is | What the record looks like |
|---|---|---|
| Exchange with a fiat gateway | A licensed platform takes a national-currency payment into an account, then executes an order on its own book | The fullest record: account statement, per-transaction export, paying bank account on file |
| Embedded widget | A “buy” button inside a wallet or an app, executed by a third-party provider | The record sits with the provider, not with the app the buyer remembers using; two firms must be identified before it can be retrieved |
| Broker or OTC desk | A bilateral quote for a large order, settled by bank transfer against its own book | A confirmation or contract note, and a bank leg that names both parties |
| Crypto ATM | Cash in, asset out at a physical machine | Thin; identity requirements and receipt detail vary by operator and jurisdiction |
| Peer-to-peer marketplace | The buyer pays another individual directly, with the platform holding the asset in escrow | The platform evidences the asset leg, not the origin of the money that paid for it |
The distinction matters at the point where the record is needed rather than at the point of purchase. A widget purchase and an exchange purchase deliver the same asset; four years later they are not the same document.
How a single purchase runs
- Identity and tax residence. The provider verifies the buyer under its anti-money-laundering obligations and, separately, collects a tax self-certification stating the jurisdiction of tax residence and the taxpayer identification number. These are two checks, not one — the first establishes who the buyer is, the second where the buyer is taxed, and the answers can differ.
- Payment authorisation. The paying account is debited. The name on it must match the verified account holder; third-party funding is refused by most providers as a matter of policy rather than of law.
- Pricing. The provider quotes its own price — a reference rate plus a spread — and holds it for a short window. The quote is the provider’s, not the market’s.
- Delivery. The asset is credited to an address on the provider’s books. Moving it to a self-hosted address is a separate event with its own checks; above a value set by the applicable regime, the provider must verify that the buyer controls the receiving address before it will release.
- Recording. The confirmation states the national-currency amount, the asset and quantity, the rate, the fee and the timestamp. That document, plus the debit on the bank statement, is what the whole transaction reduces to once the screens are gone.
What it costs, and what governs the timing
Four components, of which only the first is normally itemised: the provider’s stated fee; the spread between the quoted price and the reference rate; the cost of the payment rail, which is why card funding is priced above a transfer; and the network fee charged when the asset is withdrawn. Where the paying account is denominated in another currency, a fifth component is the conversion applied by the bank or the provider before the provider’s own pricing begins.
Timing is governed by the rail and by the risk it carries. A card authorises in seconds and is reversible for months, so providers commonly hold withdrawals after card-funded purchases — a blockchain transfer, once made, cannot be pulled back. A bank transfer clears more slowly and attracts fewer holds. A first transaction on a new account sits behind review regardless of rail.
What the transaction produces
Five artefacts, held in four different places: the provider’s confirmation; the debit line on the bank statement; the transaction export from the provider’s account; the self-certification on file with the provider; and — for transactions from 2026 in the reporting jurisdictions — the report the provider makes to its own tax authority. The buyer holds the first three, can usually request the fourth, and never sees the fifth.
Since 1 January 2026, the on-ramp reports
The OECD’s Crypto-Asset Reporting Framework took effect for the first group of jurisdictions on 1 January 2026 — in the EU through DAC8, in the United Kingdom through the 2025 reporting regulations, and in Canada, Japan and South Korea through domestic implementations. Seventy-six jurisdictions had committed as of July 2026. Providers in the first group have been collecting reportable data since the start of 2026; the first UK reports are due to HMRC by 31 May 2027, and the first automatic exchange between EU member-state authorities by 30 September 2027, both covering calendar year 2026. A second group begins collection a year later, with first exchanges in 2028.
Three points of the framework bear directly on the on-ramp leg:
The conversion itself is reportable. Exchanges between crypto-assets and national currency are a reported transaction category, aggregated per user, per asset, per year, alongside the user’s name, address, jurisdiction of residence and tax identification number.
No size floor applies to it. The USD 50,000 figure that circulates in coverage of the framework belongs to a different category — crypto-assets transferred to a merchant in payment for goods or services. It does not exempt small conversions, because conversions are not that category.
The self-certification has an enforcement mechanism attached. Under the EU rules, where a valid self-certification has not been obtained after two reminders and 60 days, the provider is required to block the user from reportable transactions until it is. Relationships opened before 1 January 2026 must be certified by 1 January 2027.
What goes wrong
The paying account does not match. A transfer from a company account for a personally verified user, or from a spouse’s account, is returned or held; the asset is not delivered and the funds sit unattributed until the provider matches them.
The self-certification lapses. The block described above is not a risk assessment the provider makes — it is an obligation, applied to an otherwise well-behaved account.
The provider is no longer authorised where the buyer sits. MiCA’s transitional arrangements closed on 1 July 2026 across every member state, with no extension: a provider operating on a pre-existing national registration cannot serve EU clients without authorisation, and authorisation status is checkable against ESMA’s public register. A buyer’s historical records may therefore sit with a firm that has withdrawn from the market it was used in.
The self-hosted withdrawal fails verification. Where the provider must confirm control of the receiving address, an address that cannot be signed for or tested is one the provider will not release to.
The record cannot be retrieved. An account closed, a provider wound down, an email address abandoned — the confirmation is retrievable while the account is open and the provider is in business, and neither of those is permanent.
Terms it is confused with
An off-ramp runs the same conversion in the opposite direction. An exchange is a market; on-ramping is one function it performs, and many on-ramps are not exchanges. A payment gateway pays a merchant against an order, where an on-ramp delivers the asset to the buyer. An OTC desk quotes bilaterally against its own book rather than routing to a public order book.
A seller of bullion is none of these. Golden Ark Reserve operates no on-ramp: where a purchase is funded from digital-asset proceeds, conversion is performed by a licensed digital-asset platform, and Golden Ark Reserve is settled in national currency against a named order reference, holds no digital assets, and issues no token or claim on metal.
Why the on-ramp matters at the exit, not the entry
An on-ramp is chosen at the moment of arrival and judged at the moment of exit. The consequence of the choice surfaces at the other end of the position, often years later, and it is documentary rather than financial.
When digital assets are converted back and the proceeds settle as national currency against an invoice, the receiving bank and the seller’s compliance file both work backwards along the chain: allocation, settlement, order reference, conversion, and then the origin of the digital assets themselves. The chain terminates at the on-ramp. What that first record contains — the paying account, the national-currency amount, the date, the rate — is what turns “proceeds of digital assets” into an origin a reviewer can accept or reject on its face. Nothing produced downstream reconstructs it: the conversion record, the order reference and the allocation documents all describe events that occur after the money is already in digital form.
From 2026 that first record exists in a second copy the buyer does not hold and cannot amend. The reporting jurisdictions receive it directly from the provider, on a fixed annual cycle, whether or not the buyer ever retrieves their own. For a treasury or family-office file the implication is narrow and concrete: the reconstruction assembled at the point of sale and the copy already held by a tax authority describe the same transactions, and a difference between them is visible without anyone auditing anything.
Where a bullion purchase is funded from digital-asset proceeds, the conversion, the settlement and the documentation that follows are set out on Buy Physical Gold with Crypto.