A fiat onramp is the service that lets a customer buy crypto or stablecoins with ordinary money, using a card or bank transfer. This guide explains what happens inside an onramp, the parts you connect when you add one to a product, and the decisions that shape cost and conversion. It is written for product and engineering teams weighing how to let users move from cash to digital assets.
What a fiat onramp actually does
At its simplest, an onramp accepts a payment in a national currency, runs the required checks and delivers the equivalent digital asset to a wallet. Behind that single action sit three functions working together: payment acceptance, compliance, and asset delivery. Payment acceptance handles the card or bank charge. Compliance verifies the customer and screens the transaction. Asset delivery prices the crypto, holds the rate briefly and sends tokens to the destination address. If any one of the three fails, the whole conversion fails, which is why onramps are often described as orchestration rather than a single feature. For where this sits in the wider picture of moving between cash and crypto, see Crypto On-Ramps and Off-Ramps.
The flow from card to wallet
A user-facing onramp typically runs in this order:
- Verification. The customer confirms their identity, and the provider screens against sanctions and risk lists.
- Payment. The customer pays by card, digital wallet such as Apple Pay or Google Pay, or bank transfer.
- Pricing and lock. The service quotes an exchange rate and holds it for a short window, because prices move.
- Delivery. Once the payment clears the checks, the crypto is released to the wallet address, minus fees.
The friction points are verification and payment. Heavier identity checks reduce risk but increase drop-off, while card payments settle quickly yet carry chargeback exposure. Where permitted by applicable regulation and the provider’s risk framework, some providers may use tiered verification approaches, with the level of checks depending on transaction risk, customer profile and jurisdiction.. For a step-by-step view of the flows on both the buy and sell side, see On-Ramps and Off-Ramps: A Closer Look at the Flows.
Ways to integrate an onramp
There are three common patterns, and the right one depends on how much of the experience you want to own.
| Integration pattern | What you get | Best suited to |
|---|---|---|
| Hosted widget | A drop-in interface the provider hosts | Fast launch, minimal build |
| API integration | Direct calls into your own interface | Teams wanting control of the UX |
| Aggregator | One connection to many onramps at once | Wide coverage and routing choice |
A hosted widget is the quickest route, since the provider carries the interface and much of the compliance. A direct API gives you control of the design at the cost of more work. An aggregator connects you to many providers through a single integration and can route each transaction by conversion rate, price or verification friction. Some aggregators reach dozens of onramps through one connection, which widens coverage without a separate build for each.
What drives cost and conversion
Two numbers decide whether an onramp succeeds: the total cost to the customer and the share of attempts that complete. Cost is not only the headline fee. It includes the exchange spread, the payment method surcharge and any network fee for delivering the asset. Conversion depends heavily on payment method availability and the weight of the identity checks, because a customer who cannot pay with a familiar method or who stalls at verification simply leaves. Stablecoins feature heavily on the delivery side, since a token pegged to a currency avoids price movement between payment and settlement, and stablecoin market capitalisation passed 310 billion US dollars by 2026. Matching local payment methods to each market usually moves conversion more than shaving the fee.
Where the regulated duties sit
An onramp is a regulated activity.FATF standards allow jurisdictions to apply a de minimis threshold of up to USD/EUR 1,000 with reduced requirements for certain virtual-asset transfers below that level. In the EU, Regulation 2023/1113 applies originator and beneficiary information requirements to CASP-mediated crypto transfers without an equivalent general €1,000 threshold.. These duties, along with the custody of customer funds and the licence to operate the ramp, belong to the regulated crypto-asset service provider or payment partner. Software that presents the onramp and connects the pieces does not hold that status, so an integration plan should state clearly which regulated entity is the operator of record. A successful fiat onramp integration balances payment coverage, verification, pricing, conversion, user experience and clearly assigned regulatory responsibilities.
Frequently Asked Questions
What payment methods do fiat onramps support?
Most support major debit and credit cards, digital wallets such as Apple Pay and Google Pay, and bank transfers. Local methods vary by market, and offering the right ones for each region tends to lift conversion.
How quickly can I add an onramp to my product?
A hosted widget can be live in days, since the provider carries the interface and much of the compliance. A deeper API integration takes longer but gives more control over the experience.
Why do onramp fees vary so much?
The customer pays a mix of the headline fee, the exchange spread, the payment surcharge and the network fee. Different providers weight these differently, so the cheapest headline rate is not always the cheapest overall.
Do I need a licence to offer a fiat onramp?
The regulated activity, including custody and reporting, sits with the crypto-asset service provider or payment partner that operates the ramp. If you provide the software layer, confirm which licensed entity carries those obligations.
