Stablecoin on-ramp vs off-ramp vs payout: what each term means and which you need (2026)

An on-ramp turns fiat money into stablecoins, and an off-ramp turns stablecoins back into fiat. In BlindPay's API, a payin is the bank-transfer receive that does the on-ramp, and a payout is the bank-account delivery that does the off-ramp. The terms describe direction. The products behind them differ by provider.

This glossary-style guide is current as of October 2026. It sits under the series hub, what a stablecoin payouts API is. BlindPay publishes it, so the product names below are BlindPay's.

Key takeaways

• On-ramp means fiat in, stablecoins out. Off-ramp means stablecoins in, fiat out. In BlindPay, these are a payin and a payout.
• BlindPay's docs use Store, Receive and Send for the stablecoin side: holding a balance in a wallet, stablecoins arriving, and stablecoins leaving.
• A virtual account is a dedicated bank account whose deposits settle automatically into stablecoins, which makes it a standing on-ramp for one customer.
• Marketplaces and remittance products usually need both directions. Payroll and supplier payments usually need only the payout.
• Different providers sell the same flow under different names, so compare what is delivered: which currency, which rail, which bank account, and how fast.

What do on-ramp and off-ramp mean in plain payment language?

Think of a ramp as a bridge between bank money and token money. You drive onto the stablecoin network with an on-ramp, and you drive off it with an off-ramp.

A stablecoin is a token pegged to a currency, usually the US dollar, that moves on a blockchain network at any hour. Most businesses do not want customers to touch that layer. They want a customer to pay by bank transfer, and a recipient to be paid into a bank account. The ramps hide the token step.

For the longer background, see what a crypto on-ramp and off-ramp is, how to tell whether your product needs an on-ramp or an off-ramp and the types of off-ramps. This page adds the mapping to BlindPay's API and a money-flow example.

How do the terms map to BlindPay's API?

Payin is the on-ramp, payout is the off-ramp, and Store, Receive and Send describe the wallet in between.

Two points avoid confusion. First, Receive and Send in BlindPay's docs are stablecoin-to-stablecoin concepts. When money enters or leaves as fiat, that is a payin or a payout. Second, a managed wallet is optional. BlindPay-managed wallets (beta) are custodial when you choose them, and BlindPay documents its custody model this way: BlindPay operates as a non-custodial payment processor for payout flows from customer-controlled wallets: you authorize the exact amount and BlindPay executes that single transaction. If a payout cannot be delivered after the stablecoins are collected, BlindPay refunds them to the quote's refund wallet, or to the sending wallet when none is set; on Pix and other non-USD local rails the refund is automatic, while USD payouts and payouts whose review times out are refunded after an operator review. Optional BlindPay-managed wallets (beta) are custodial when you choose that path.

Read the Store, Receive and Send pages for the wallet side, and the payouts docs for the fiat side.

Which one do you need?

It depends on where your money starts and where it ends. Use the list below by business model.

1. Marketplace. You collect from buyers and pay sellers in other countries. You need both directions: payins to collect, payouts to settle sellers. Add a virtual account if buyers are repeat payers.
2. Payroll or contractor platform. The company funds a stablecoin balance and pays staff in local currency. You need payouts, usually with cover_fees set to true so each person gets an exact amount.
3. Remittance company. A sender pays by bank transfer and the family receives local currency. You need both: a payin on the sending side and a payout on the receiving side.
4. Import and export business. A buyer pays you in dollars and you pay suppliers abroad. You need a way to hold dollars (a virtual account or payin) and payouts, including SWIFT (POBO/COBO) where no local rail exists.
5. Treasury. You hold stablecoins and need to cash out to a bank account. You need an off-ramp, either one-off payouts or an offramp wallet that pays out every deposit.

If you only collect and keep stablecoins as your balance, you need only the on-ramp. If you only pay out from a balance you already hold, you need only the payout.

What is a virtual account, and how does it fit?

It is a dedicated bank account in a customer's name that converts every deposit into stablecoins. It is a standing on-ramp, because the account number is the integration.

BlindPay's US virtual accounts accept ACH, wire and SWIFT deposits. Each deposit creates a payin, and BlindPay sends USDC or USDT to the wallet linked at creation. The virtual accounts docs list the account types: a US virtual account costs 1.50 USD per month per active account, and Mexico (SPEI CLABE) and Colombia (Bre-B) accounts are instant. For the concept on its own, read what a virtual account is.

What does the money flow look like from a US bank to a Pix account?

Five stops, in text. This is an illustrative flow for a US customer paying a recipient in Brazil. It is not a promise of timing or fees.

1. The US customer sends dollars by bank transfer. They send ACH or wire to the account details shown to them, either a virtual account in their own name or BlindPay's account with a memo_code. RTP, which The Clearing House runs as an instant, always-on US rail, always uses the shared memo-code account.
2. The deposit becomes a payin. BlindPay matches the deposit, converts it and credits USDC or USDT to the customer's linked wallet. This is the on-ramp.
3. The balance sits in the wallet. Your product shows it as the customer's balance. This is Store.
4. Your app creates a payout quote. The recipient's Pix bank account is already saved. The quote locks the USD to BRL rate and the fees for 5 minutes, and your customer confirms the BRL amount.
5. You execute, and BRL arrives by Pix. BlindPay pulls the stablecoins, converts them and sends reais over Pix, which Banco Central do Brasil runs every hour of the year. Per BlindPay docs, Pix payouts are instant. A payout.complete webhook confirms. This is the off-ramp.

Both ends need identity checks. The business collects KYC data and BlindPay verifies it, while KYB, sanctions screening and travel rule compliance are part of the payin and payout API. The travel rule comes from FATF Recommendation 16. For the Brazil leg in detail, read the USDC to Pix guide.

Why do providers use different names for the same thing?

The market has no shared vocabulary yet. One provider's off-ramp is another's payout, withdrawal or cash-out, and one provider's on-ramp is another's deposit or funding flow.

When you compare options, ignore the label and ask four questions. Which currencies and countries does it deliver? Which local rail carries the money? Is compliance in the same API flow? Does every quote show the full fee before you commit? A product that covers the direction you need, on the rail your recipient uses, is the right one whatever it is called. Types of crypto off-ramps lists the common shapes.

Which is cheaper: the on-ramp or the off-ramp?

Neither is cheaper by nature. Each direction has its own rail, exchange rate and fees, so compare the all-in amount using a live quote.

BlindPay's pricing, in its own canonical wording: BlindPay combines a monthly plan (platform access) with per-transaction fees that vary by rail and network and are disclosed only in the live quote before execute. BlindPay does not publish a static flat rate card; always cite the quote's fee breakdown rather than a fixed bps number. The billing docs add that there is no setup fee and no monthly minimum, and development instances are always free. See pricing for how BlindPay discloses fees.

Methodology and sources

External sources: Banco Central do Brasil on Pix, FATF Recommendation 16 update, June 2025 and The Clearing House on RTP.

BlindPay docs: Store, Receive, Send, Payouts, Virtual accounts, Offramp wallets and Billing. The money-flow example is illustrative. Check the docs for current rails and account types before you design around them.

What to do next

See the supported payin and payout rails in the payouts docs and the payins docs, then open a free development instance and run one payin and one payout end to end.