---
title: "Business vs consumer crypto on-ramps: what changes when a company buys stablecoins"
seoTitle: "Business vs consumer crypto on-ramps: what changes"
description: "A consumer on-ramp sells crypto to one person, usually by card. A business on-ramp turns company bank deposits into stablecoins via an API. What differs."
date: "2026-08-23"
updated: "2026-08-23"
author: "BlindPay Team"
category: "stablecoins"
faq:
  - q: "What is the difference between a business and a consumer crypto on-ramp?"
    a: "A consumer on-ramp sells crypto or stablecoins to one person, usually paid by card inside a hosted widget, with KYC on the individual. A business on-ramp converts a company's bank transfers into stablecoins through an API, after KYB on the company and its owners. The conversion is the same. The payment methods, limits, pricing, and integration are not."
  - q: "Can a business buy stablecoins with a credit card?"
    a: "Some consumer on-ramps accept business cards, but it rarely makes sense. Card on-ramps carry higher fees and low purchase caps because the provider has to price in chargebacks on money it already delivered on-chain. For anything beyond a small test, a bank transfer such as ACH, a wire, Pix, or SPEI is cheaper and has higher limits."
  - q: "Do business on-ramps require KYB?"
    a: "Yes. A regulated on-ramp has to verify who it is dealing with, and for a company that means KYB: registration documents, the people who own or control it, its line of business, and often the source of funds. Expect a manual review measured in hours or days, not the minutes a consumer KYC check takes."
  - q: "Is a crypto on-ramp safe?"
    a: "It is as safe as the provider's licensing and controls, and the care you take with the destination. Check that the provider is registered where it operates (in the US, a FinCEN MSB registration you can look up), runs KYC or KYB on every customer, and delivers to the exact wallet and network you specified. A stablecoin transfer can't be reversed once it confirms, so confirm the address before you pay."
  - q: "How long does a business on-ramp take?"
    a: "Onboarding takes longest: a KYB review can take from a few hours to a few business days. After that, each deposit is limited by the bank rail. Pix and SPEI settle in seconds to minutes, a domestic wire in hours, and ACH in one to three business days. The on-chain delivery adds seconds to a few minutes on most networks."
  - q: "Can a platform on-ramp money on behalf of its customers?"
    a: "Only if the provider can see those customers. Regulated on-ramps expect every party whose money moves through the account to be onboarded and screened. A platform that pools many end customers' deposits under its own account, without registering them, is running a nested structure most providers prohibit."
---

A consumer crypto on-ramp sells crypto or stablecoins to one person, usually paid by card inside a hosted widget. A business on-ramp converts a company's bank deposits into stablecoins through an API, after KYB, over rails like ACH, wire, Pix, or SPEI, and delivers them to a treasury or customer wallet. Same conversion, different product.

If you're new to the basics, [what is a crypto on-ramp and off-ramp](/resources/more/what-is-a-crypto-on-ramp-and-off-ramp) covers the core flow. This page is about the split that decides which providers you can even shortlist.

## Key takeaways

- Consumer on-ramps optimize for conversion: cards and mobile wallets, a hosted widget, KYC in minutes, small purchases.
- Business on-ramps optimize for cost and control: bank rails, KYB, quoted rates through an API, and a webhook for every deposit.
- Cards can be disputed after the stablecoins are gone, so card on-ramps price that risk in. Push payments like Pix, SPEI, and wires can't be clawed back by the sender, which is why business flows prefer them.
- The destination matters as much as the source: a personal wallet, a company treasury wallet, or one wallet per end customer.
- Pick by product profile. A consumer wallet, a fintech app, a payout platform, and a treasury team weigh different criteria.

## What is the difference between a consumer and a business on-ramp?

The conversion is identical: fiat in, stablecoins out. Almost everything around it changes.

| | Consumer on-ramp | Business on-ramp |
| --- | --- | --- |
| Who pays | One person | A company, or a platform's verified customers |
| Verification | KYC: ID document, selfie, sanctions screening | KYB: company registration, [beneficial owners](https://www.ecfr.gov/current/title-31/subtitle-B/chapter-X/part-1010/subpart-C/section-1010.230), directors, line of business |
| Typical payment method | Debit or credit card, Apple Pay, Google Pay | ACH, domestic wire, SWIFT, Pix, SPEI, other local bank rails |
| Ticket size | Tens to hundreds of dollars | Thousands to hundreds of thousands per transfer |
| Pricing | One all-in price per purchase | A quote with an exchange rate and a fee |
| Integration | Hosted widget or redirect | REST API plus webhooks |
| Destination | The buyer's own wallet | A treasury wallet, or one wallet per end customer |
| Risk the provider prices in | Card fraud and chargebacks | Compliance: whose money it is, and what it is for |

Most providers specialize in one column. A few run both, but the products behind them are usually separate, with separate pricing and separate onboarding.

## How does a consumer on-ramp work?

A consumer on-ramp is a checkout. The wallet or app embeds it, and the provider runs everything inside.

1. The user taps "buy" inside a wallet app, picks a token and an amount.
2. The provider's widget opens and runs KYC: an ID photo, a selfie, a sanctions check.
3. The widget shows a price that already includes the spread, the network fee, and the card cost.
4. The user pays by card, Apple Pay, or Google Pay.
5. The provider sends the tokens to the wallet address the app passed in.
6. The app gets a callback when the purchase completes.

The wallet app often never touches the money. It passes an address and waits for the callback. That's the appeal: a few lines of front-end code. The tradeoff is control. The provider owns the checkout, the price, and the support ticket when a card gets declined.

## How does a business on-ramp work?

A business on-ramp is an account relationship. The company onboards once, then deposits on a schedule.

1. The company passes KYB. On a platform, each of the platform's business customers passes it too.
2. The provider issues deposit instructions: a [virtual account](/resources/more/what-is-a-virtual-account) with its own account number, or a shared account plus a reference code.
3. The platform requests a quote for the amount, payment method, token, and destination wallet.
4. The company sends the bank transfer.
5. The provider matches the deposit, converts it, and delivers stablecoins on the chosen network.
6. A webhook fires, and the platform reconciles the deposit against its ledger.

Steps 1 and 2 happen once. Steps 3 through 6 repeat for every deposit, and a payroll or treasury team might run them every day. [How to accept bank transfers and settle in stablecoins](/resources/more/accept-bank-transfers-settle-in-stablecoins) walks through the virtual account version end to end.

## Why do consumer on-ramps use cards and business on-ramps use bank rails?

Because of who carries the risk of the money coming back.

A card payment can be disputed by the cardholder after the fact. A stablecoin delivered on-chain can't be pulled back. So a card on-ramp that has already sent USDC is exposed to a chargeback on money it no longer has. It covers that with higher fees, tight purchase caps, and aggressive fraud scoring. [Stablecoin payment fees vs card processing fees](/resources/more/stablecoin-payment-fees-vs-card-processing-fees) has the numbers on what cards cost before any of that.

Push payments work the other way. With Pix, SPEI, a wire, or an ACH credit, the payer's bank sends the money, and the sender can't reverse it on their own. The provider delivers stablecoins after the funds land, so the risk of a clawback is close to zero. That's why business volume runs over bank rails. Nobody tops up a $250,000 treasury wallet by card.

The one bank rail that behaves like a card is an ACH debit, where the provider pulls money from the payer's account. Debits can come back as returns days or weeks later under [Nacha rules](https://www.nacha.org/), so providers that pull by ACH tend to hold delivery or limit amounts.

## Which on-ramp fits which product?

Start from your product, not from a provider list.

| Product | What it needs most | What matters less |
| --- | --- | --- |
| Consumer self-custody wallet | Card and mobile wallet coverage, KYC in minutes, a hosted widget, many countries | Per-transaction cost, deep API control |
| Fintech app or neobank with dollar accounts | Local bank rails in your markets, KYC inside your own onboarding, branded deposit details, an API | A hosted checkout |
| Payout platform or marketplace | Bank deposits in, firm quotes, webhooks, the off-ramp on the other side, [no pre-funding](/resources/more/no-pre-funding-stablecoin-payouts) | Card coverage |
| Corporate treasury | KYB, high limits, wire and SWIFT, delivery to a treasury wallet, predictable settlement times | Widget UX |

A quick test for each:

- **Consumer wallet.** Can a first-time user in your top five countries go from tap to tokens in under five minutes?
- **Fintech app.** Can you show the deposit instructions inside your own UI, under your brand, without sending users to another site?
- **Payout platform.** Does every deposit produce an event with an ID you can reconcile, and does the same provider pay out locally?
- **Treasury.** What are the per-transaction and monthly limits after KYB, and what does it take to raise them?

## Where do the stablecoins land: custodial or non-custodial?

A consumer on-ramp usually delivers to a wallet the buyer controls. A business on-ramp gives you a choice, and the choice decides who is holding the money between the deposit and the next payment.

| Destination | Who holds the keys | Typical use |
| --- | --- | --- |
| The end customer's own wallet | The customer | Self-custody users, fintechs that never want to hold funds |
| A company treasury wallet | The company, or its custodian | Treasury, payout float |
| A wallet the provider holds | The provider (custodial) | Apps that want a balance without running wallets |

Delivering straight to a wallet the customer controls keeps your platform out of custody. Holding balances for customers is a different regulatory position, with different obligations. [Custodial vs non-custodial vs MPC wallets](/resources/more/custodial-vs-non-custodial-vs-mpc-wallets) and [non-custodial payments explained](/resources/more/non-custodial-payments-explained) cover the tradeoffs.

## Are business and consumer on-ramps regulated differently?

No. Licensing follows the activity, not the type of customer.

In the US, a business that accepts fiat and delivers virtual currency is a money transmitter under [FinCEN's 2019 guidance](https://www.fincen.gov/resources/statutes-regulations/guidance/application-fincens-regulations-certain-business-models), whether the buyer is a teenager or a public company. In the EU, the service needs authorization as a crypto-asset service provider under [MiCA](https://www.esma.europa.eu/esmas-activities/digital-finance-and-innovation/markets-crypto-assets-regulation-mica). Brazil regulates it as a virtual asset service provider, covered in [PSAV Brazil explained](/resources/more/psav-brazil-explained).

What changes is the depth of verification. A business customer means KYB instead of KYC: who owns the company, who controls it, what it does, and what the payments are for. The provider also has to understand whether the company is moving its own money or someone else's.

## Where does BlindPay fit?

BlindPay is a business on-ramp. It is not a consumer card widget.

- **Payins over bank rails.** ACH and domestic wire in the US, Pix in Brazil, SPEI in Mexico, PSE in Colombia, and Transfers 3.0 in Argentina. Each payin converts the deposit and delivers stablecoins to a wallet.
- **Virtual accounts.** A US account in the customer's name with its own routing and account number. Each deposit converts to USDC or USDT and settles to the wallet linked at creation. One customer and one wallet per account, and a customer can hold several accounts.
- **Quotes before money moves.** Every payin starts with a quote that locks the amount, the fees, and the destination for 5 minutes. A `cover_fees` flag decides whether the sender or the receiver pays the fee.
- **KYC and KYB in the API.** Individual KYC Standard is automated and takes about 60 seconds. KYB is a manual review that takes 3 hours to 1 business day.
- **Delivery networks.** USDC or USDT on Ethereum, Polygon, Base, Arbitrum, Stellar, Solana, and Tron, depending on the network (USDT only on Tron).
- **Non-custodial delivery.** Payins can deliver straight to an external wallet the customer controls.

**When BlindPay is the right fit:** you're a fintech, payout platform, or treasury team collecting bank transfers in the US or Latin America, and you want stablecoins delivered to wallets your customers control, through one API that also pays out locally.

**When it isn't:** you need card or Apple Pay checkout for retail crypto buyers, or a hosted widget to drop into a consumer wallet. BlindPay also isn't a stablecoin issuer. It converts and moves USDC and USDT, which Circle and Tether issue.

The details are in the docs for [payins](/docs/payins), [virtual accounts](/docs/virtual-accounts), and [KYC requirements](/docs/kb/kyc).

## What to do next

Write down three answers before you talk to any provider: who pays (a person or a company), which rail they pay with, and whose wallet the stablecoins land in. Those three answers rule out half the market.

Then take the shortlist and test the quote. [Stablecoin API quotes explained](/resources/more/stablecoin-api-quotes-explained) shows what a quote should lock and which fields to check.

*This article is general information, not legal, tax, or financial advice. Rails, limits, and supported countries change; confirm current details with each provider.*