← Overview
Layer L1

On / Off-ramps

Fiat ⇄ crypto at the edge — card or bank into stablecoins.

What this layer does

Ramps are the doors between the traditional banking system and the blockchain. An on-ramp turns a card payment or bank transfer into crypto/stablecoins; an off-ramp does the reverse. They handle KYC, payment acceptance, fraud, and the actual fiat settlement so the apps embedding them don't have to.

Where it sits

The very edge of the flow — where a real person's money first becomes on-chain value, and where it leaves again.

What they compete on

Fees, conversion/approval rates, breadth of local payment methods (UPI, PIX, SEPA, ACH), country + chain coverage, and checkout UX.

How to tell them apart

Consumer-brand ramps (MoonPay) optimize for a recognizable purchase flow; developer-first ramps (Transak, Coinbase Onramp) optimize for white-label embedding and the widest local rails; aggregators route across several ramps for the best quote.

Builder's track

Build your own on / off-ramps

  • Payment acceptance: card acquiring (Visa/Mastercard) + local methods (ACH, SEPA, UPI, PIX) with strong fraud/3DS — this is the hardest, most regulated piece.
  • Compliance: KYC/AML vendor, sanctions screening, and money-transmitter / VASP licensing per market (MTLs in the US, MiCA/CASP in the EU).
  • Liquidity: market-maker or exchange relationships to source crypto at a quotable price, plus FX for local currencies.
  • Settlement: custody/treasury to hold inventory + on-chain payout to the user's wallet (and the reverse for off-ramp).
  • Frontend: an embeddable widget (iframe) + SDKs, a quote engine, and webhooks so partners can track order status.
  • The moat is licenses + approval rates + local payment coverage — not the widget. Most builders instead embed an existing ramp (Ramp/MoonPay/Transak/Coinbase) rather than build this stack.

The players