The best on-ramp and off-ramp APIs depend on who is paying. A consumer widget (MoonPay, Transak, Ramp Network, Coinbase, Stripe) sells crypto to a person with a card. An aggregator (Onramper, Meld) routes between those widgets. A business API (Bridge, BVNK, Conduit, Lumx) moves money for a company and pays out to bank accounts.
The split matters because the three groups verify different people. A widget runs KYC (know your customer, the verification of an individual). A business API starts with KYB (know your business, the verification of a company and its owners) and ends with a payout to a local account, such as Pix (Brazil's instant payment system, run by the Central Bank) or SPEI (Mexico's interbank transfer system, run by Banxico). We covered the basics in what a stablecoin on-ramp is and what a stablecoin off-ramp is. Vendor facts below come from public documentation read on November 1 or 2, 2026.
What are the best on-ramp and off-ramp APIs in 2026?
Eleven providers by type, rate behavior and bank payout, from each provider's public documentation as of November 2, 2026 unless the row says otherwise
Provider | Type | Built for | Rate on the quote | Payout to a bank account |
MoonPay, Transak, Ramp Network | Consumer widget | An app's end users buying crypto | Differs by vendor, see the quote-model table below (widget comparison) | Sell flows with bank or card payout, by vendor and country |
Coinbase Onramp and Offramp | Consumer widget | Users of an app who pay by card or Coinbase account | Rate lock not stated on the overview page | Offramp to a US bank account by ACH, from a Coinbase-hosted page |
Stripe crypto onramp | Consumer widget | Customers buying crypto at checkout | Not stated on the overview page | Onramp only on the overview page |
Onramper | Aggregator | Wallets and dApps wanting many on-ramps in one integration | Quotes from all available providers, ranked | Sell quotes and an offramp widget flow |
Meld | Aggregator | Wallets and fintechs wanting many on-ramps in one integration | Not stated on the pages read | Sell flow, and a bank-transfer Virtual Account product |
Bridge | Business API | Platforms moving fiat and stablecoins | An estimate, no lock | Pix, SPEI and other rails, no SWIFT (as of September 2026, see Lumx vs Bridge) |
BVNK | Business API | Enterprises in the US, UK and EU | Locked quote (as of September 2026, see Lumx vs BVNK) | US, UK and EU rails, no Brazil, Mexico or Colombia |
Conduit | Business API | Businesses with USD, EUR and GBP accounts | Quote then execute (as of September 2026, see Lumx vs Conduit) | ACH, wires, SEPA, Faster Payments and SWIFT; Pix not in its payouts API |
Lumx | Business API | Companies moving money between Latin America and the rest of the world | Floating, or locked for 30 seconds, 1 minute or 5 minutes | Pix, SPEI, Colombian rails, ACH, Fedwire, SEPA, Faster Payments, SWIFT in USD |
Read the table by the column that decides your project: a person buying a token fits the widget rows, and a company whose money must land in a bank account fits the business API rows. If you are replacing Bridge or BVNK, see Bridge alternatives and BVNK alternatives. For payout-only providers, see best stablecoin off-ramp APIs.
What does a company need that a widget does not give?
The same purchase seen from a person's widget and from a business API, as of November 2, 2026
Question | Consumer widget | Business API (Lumx) |
Who is verified | A person, with photo ID and a selfie | A company with KYB, or its end users with KYC, through the customer object |
Where the money comes from | A card, or a bank account the person owns | A named virtual account in the customer's name, funded by Pix, SPEI, ACH, SEPA or Faster Payments |
What the buyer receives | Crypto sent to a wallet address | Stablecoin in a custodial wallet that stays funded between operations |
What comes next | The person holds the token | A payout from the same wallet to a bank account, with a status per step |
Size | Set by each vendor, see its docs | KYB Standard: $50,000 per transaction and $100,000 per day or month |
None of the widget pages read documents a company as the buyer: Coinbase's docs describe an app's end users, and Stripe's its customers at checkout.
On Lumx, the limits apply separately to on-ramps, off-ramps and transfers, so an on-ramp never uses up off-ramp headroom.
Do you need an aggregator like Onramper or Meld?
An aggregator sits on top of consumer on-ramps. It earns its place when an app has end users in many countries and wants the best-converting provider per user, and adds a hop when the buyer is one company that wants one provider's rails and a payout.
What each aggregator documents about itself, read on November 2, 2026
Question | Onramper | Meld | Direct business API (Lumx) |
What it is | An aggregator of more than 30 on-ramp providers, with more than 130 payment methods | Three products: White-Label API, hosted Checkout and Virtual Account | One API, with named accounts and custodial wallets |
How the user is routed | Quotes from all available providers, ranked on past success rates, plus fees and KYC friction | Smart routing of users to the best on-ramp, per its overview page | No routing: one provider, one set of rules |
Integration time stated | "Under an hour" for the widget | About 15 minutes for Checkout, about 1 week for the APIs | 2 to 3 weeks through the API to go-live |
If the buyer is a person and the problem is conversion, an aggregator helps. If the buyer is a business, choose a direct API. The same logic separates a stablecoin API vs crypto gateway. Lumx is the direct side: it does not route across providers, and a customer holds one named account per currency.
How the quote model changes the amount delivered
What each provider's documentation says about the rate on a quote, as of November 2, 2026 unless noted
Provider | What the docs state |
MoonPay | Fixed rate for card, floating estimate for bank transfer, with an expiry (read November 1) |
Transak | A temporary price refreshed every minute, crypto sent at the latest rate (read November 1) |
Ramp Network | Quotes per payment method, no lock period stated (read November 1) |
Coinbase | Session tokens are single-use and expire after 5 minutes; the overview page states no rate lock |
Stripe | Not stated on the overview page |
Onramper | Quotes from every available provider; lock terms not stated on the pages read |
Bridge | The exchange-rate endpoint returns an estimate updated roughly every 30 seconds, and its docs say Bridge does not offer a quote that locks a rate |
Lumx | Floating rate, or a locked rate for 30 seconds, 1 minute or 5 minutes, settled by passing the returned |
A refreshing rate suits a card buyer; a finance team matching an invoice needs a held rate. Compare on the amount delivered: quote the same corridor and amount in the same minute.
Lumx documents an example, not a price list: a quote of 59,255.50 BRL to USDC over Pix returns a base amount of 10,000 USDC and a final amount of 9,978 USDC, a gap of 22 USDC, or 0.22%, from the fees.
On Lumx, a floating rate is for display and carries no fee, the 30-second lock has no fee, the 1-minute and 5-minute locks do, and an expired lock is invalid. Fee mechanics are in on-ramp and off-ramp fees explained, and best execution covers when to lock.
Cost, speed, coverage and regulation side by side
What each group states on the pages read, as of November 2, 2026
Question | Widgets, aggregators and the other business APIs | Lumx |
Cost | Not stated on the pages read; ask each vendor for the same corridor and amount | Monthly platform fee plus usage-based per-transaction fees, transparent FX on locked quotes, no pre-funding; no published plans. No pre-funding means no capital sits in settlement accounts before a transaction; the wallet balance is the stablecoin the customer chose to hold. No fee comes out of the amount the recipient gets on Pix, SPEI or Bre-B (Colombia's instant payment system, launched in 2025) |
Speed | Not stated on the pages read | Pix, SPEI, Bre-B and Faster Payments are instant, and the stablecoin credit lands about 5 minutes after a Pix or SPEI deposit. ACH takes 1 to 2 business days, Fedwire is same day, SWIFT takes 1 to 5 |
Coverage | See the first table; BVNK has no Brazil, Mexico or Colombia rails | BRL, MXN, COP, USD, EUR and GBP, with the rails on the coverage page |
Regulation and custody | Not stated on the pages read | Not a bank. Lumx SPSAV Ltda applied for SPSAV authorization and operates under the transition regime of Res. BCB 520/2025, Art. 88. BitGo holds the wallets, segregated per client with no omnibus account; Chainalysis KYT, Sumsub KYC, screening before every transaction |
How a round trip works: fiat in, stablecoin held, fiat out
An on-ramp and an off-ramp are two legs of one movement: fiat becomes a stablecoin, a wallet holds it, and it becomes fiat again at another bank. A widget gives you the first leg and sends the crypto to an address you do not control. A business API keeps it in a wallet tied to the customer, so you fund once and pay many times (on-ramp versus off-ramp by product type). Two rules shape the design: the wallet must hold the balance before a payout, and every payout needs an approved destination, so the payee is screened before money moves.
On Lumx, the on-ramp moves through AWAITING_FUNDS, TRANSFERRING_FIAT, TRADING and TRANSFERRING_STABLECOIN to SUCCESS, and the off-ramp moves through TRANSFERRING_STABLECOIN, TRADING and TRANSFERRING_FIAT to SUCCESS, with a webhook at each step. A floating Pix or SPEI on-ramp expires after 1 day and other rails after 7, and a deposit that lands late is refunded on the same rail. Every payout names a holder relationship on its destination, such as SUPPLIER or EMPLOYEE, and a purpose, which Lumx uses for AML monitoring and regulatory reporting; the destination check reads the holder relationship.
When a business ramp API is the wrong tool
A business API is the wrong tool when the person paying is an individual buying a token with a card inside a wallet or dApp, or when the product is a token catalog sold to individuals: a company check and a payout leg are friction there, and a widget matches the job. It is also wrong when you have no verified business customer, because everything built on named accounts begins with KYB. Keep the widget until a business user arrives.
Which type of provider matches which buyer?
For a person buying a token inside an app, a consumer widget such as Coinbase, Stripe, MoonPay, Transak or Ramp Network is the category, because it verifies the person and sends the token to a wallet. For retail users spread across many countries who pay by card, an aggregator, Onramper or Meld, is the category, because routing is what raises conversion. For one verified company that must land money in a bank account in Brazil, Mexico or Colombia, pick a business API with those rails, and Lumx is one. For a company that only needs US, UK or EU rails, BVNK and Conduit document those rails.
Choosing wrong costs more than the fee: a company that picks a widget learns at the verification step, after the integration is built, that the widget pages describe a person as the buyer.
I recommend shortlisting two providers for your main corridor and asking each the same two questions in writing before any call: whether a legal entity can be the buyer, and what the quoted amount does between confirmation and settlement. Then request a quote from both in the same minute and compare what the recipient would receive.
What a round trip looks like on Lumx
Lumx is stablecoin payments infrastructure for businesses that move money between Latin America and the rest of the world: one API to collect, hold, convert, and pay out in BRL, MXN, COP, USD, EUR, and GBP or in USDC and USDT, over local rails such as PIX, SPEI, PSE, Bre-B, ACH, FEDWIRE, SEPA, and Faster Payments, with SWIFT and on-behalf-of payments and collections (POBO and COBO) in USD, EUR, and GBP, plus named virtual accounts, custodial wallets, and KYB/KYC built in.
Take a US company that sells in Brazil and pays a supplier in Mexico. You create a business customer, request the BRL and MXN accounts in the same call, and the customer completes KYB, which Lumx targets at one business day. At approval, both accounts open right away and a wallet is ready.
For the first leg, you fetch a locked rate or use the floating one and create an on-ramp. Lumx returns the payment details your screen renders, a Pix code for BRL or a CLABE (the 18-digit Mexican bank account number) for MXN. A standing autoconversion rule converts every matching deposit to USDC or USDT in the wallet.
For the second leg, you register the supplier as a destination, wait for approval, and create an off-ramp over SPEI. Lumx converts the stablecoin and sends pesos from a named account. If compliance needs a document before a transaction clears, it moves to RFI (request for information, a compliance hold), with a 24-hour response window.
A coding agent can build the flow from the on-ramp prompt, and the sandbox is open. See supported countries for onboarding and how to integrate an on-ramp API.
Methodology and sources
Vendor facts were read in public documentation. On November 2, 2026: the Coinbase Onramp and Offramp overviews (docs.cdp.coinbase.com), the Stripe fiat-to-crypto onramp overview (docs.stripe.com), the Onramper getting-started and ranking pages (docs.onramper.com), the Meld overview and product pages (docs.meld.io) and the Bridge exchange-rate reference (apidocs.bridge.xyz). On November 1, 2026: the MoonPay, Transak and Ramp Network developer documentation. BVNK and Conduit rows come from our Lumx vs BVNK and Lumx vs Conduit comparisons, as of September 2026. Lumx behavior was read on docs.lumx.io the same day: exchange rates, transactions, accounts, wallets, destinations and limits.
Verified on November 2, 2026. Operational context, not legal, tax, or investment advice.
Cover photo: Daniele Bissoli on Unsplash.
What are the best on-ramp and off-ramp APIs?
It depends on who is paying. MoonPay, Transak, Ramp Network, Coinbase and Stripe document a person as the buyer, Onramper and Meld route between those, and Bridge, BVNK, Conduit and Lumx document companies with bank payouts. On Lumx, a company completes KYB, holds named accounts in its own name and pays out over Pix, SPEI and other local rails from one wallet.
What is the difference between an on-ramp API and an off-ramp API?
An on-ramp API turns fiat into a stablecoin and an off-ramp API turns a stablecoin into fiat at a bank. Most business flows need both, with a wallet in between that holds the balance. On Lumx, both legs run through one API, with an on-ramp that credits the customer's wallet and an off-ramp that debits it and pays a registered destination.
Do I need an aggregator like Onramper or Meld?
An aggregator helps an app whose end users buy crypto in many countries. It adds little when the buyer is one company that wants one provider's rails and a payout. Lumx is a direct API: it does not route across providers, and a customer holds one named account per currency.
Which on-ramp and off-ramp API locks the exchange rate?
Providers differ. MoonPay fixes the rate for cards, Transak refreshes a temporary price every minute, Ramp Network states no lock period, and Bridge's docs say it does not lock a rate. Lumx offers a floating rate for display and a locked rate for 30 seconds, 1 minute or 5 minutes, with no fee on the 30-second lock, settled by passing the exchangeRateId on the transaction.
Can a company use a consumer widget to buy stablecoins?
The widget pages read describe an individual buyer, and none documents a company as the buyer, so ask each vendor in writing. On Lumx, a business customer completes KYB, gets named accounts in BRL, MXN and other currencies, and moves up to $50,000 per transaction on KYB Standard until Enhanced verification raises it.
