MoonPay, Transak and Ramp Network are buy-and-sell widgets that an app embeds so its end users can pay with a card or a bank account and pass the provider's identity checks. They differ in integration shape, quote behavior and fee mechanics. All three are built around an individual buyer, not a company buying in its own name.
That last sentence is the reason for this post. The comparison reads each vendor against what it was built for, then covers what changes when the buyer is a business. We covered the basics in what a stablecoin on-ramp is, and the direction question is in on-ramp vs off-ramp for a fintech. Every vendor fact comes from the vendor's own developer documentation, read on November 1, 2026.
How do MoonPay, Transak and Ramp Network compare?
The three widgets on the points that decide an integration, from each vendor's own docs as of November 1, 2026
Point | MoonPay | Transak | Ramp Network |
Integration shapes | SDK modal or in-app web view, Platform API, manual iframes | Redirect, iFrame, JavaScript SDK, mobile WebView, Whitelabel API | Web and mobile SDKs, hosted page, REST API v3 |
Who runs identity checks | MoonPay (hosted), or your screens through its Customer API | Transak, with KYC Reliance to reuse your own check | Basic KYC to start a card purchase, per its getting-started page |
What the check asks for | Photo ID, liveness selfie, residential address, a Social Security number in the US | Simple or Standard tier, by order amount | Not itemized in the pages read |
Production access | Your KYB, then API keys | Your KYB, then the production key | An API key through a request form |
Payment methods named | Cards, EUR, GBP and USD bank transfers, PayPal, Venmo, Pix, Apple Pay, Google Pay | Cards, bank transfers, Apple Pay, Google Pay, by country on its coverage page | Open banking, cards, Apple Pay, Google Pay, SEPA transfer |
Selling crypto | Partner app sends the crypto within 48 hours or the sale fails | Payout to cards, bank transfers, Apple Pay, Google Pay | Bank transfer in the US, payout to Visa and Mastercard |
Rate on the quote | Fixed for card, floating for bank transfer | Temporary, refreshed every minute | Per method, no lock period stated |
None of the three documents a company as the buyer.
MoonPay: merchant of record and three onboarding paths
MoonPay's widget runs through its SDKs, in a modal over your page or in an in-app web view. Its Platform API adds three ways to onboard a customer: hosted onboarding where MoonPay renders login and the full check, onboarding through its Customer API where you build the screens, and guest checkout that defers verification until a purchase needs it.
As merchant of record, MoonPay "assumes full responsibility for all fraud disputes and chargebacks", which helps an app that does not want card risk. It lists more than 100 cryptocurrencies and the longest payment list of the three, as read, including Pix (Brazil's instant payment system, run by the Central Bank).
The identity check is built for a person. Its verification tiers ask for a government photo ID, a liveness selfie and a residential address, and in the United States a Social Security number. KYB (know your business, the verification of a company and its owners) appears in its docs only as the step your own company completes before it hands you API keys.
Transak: the most integration shapes and a partner fee you set
Transak lists the most ways to plug it in: redirect, iFrame, a JavaScript SDK, WebView on Android, iOS and React Native, or a Whitelabel API that lets you build the whole screen.
Through its KYC (know your customer, the verification of an individual) Reliance feature, you can share a check you already ran, so a user does not verify twice. Depending on the order amount, a user completes Simple KYC or Standard KYC. Your company does KYB once to get a production key.
Ramp Network: open banking and a fee range in the docs
Ramp Network describes itself as an aggregator of liquidity, payment methods and payout methods for buying or selling crypto from a dApp. Its bank payments run on open banking, a direct connection to the buyer's bank.
To sell, payout goes to a Visa card in more than 130 countries. The v3 REST API also lists Pix as a payment method and Pix and SPEI (Mexico's interbank transfer system, run by Banxico) as payout methods in its enums. Which are live depends on your key and the country, so ask first. The widget does not work without a production API key, issued through a request form.
What do the quote and the fee commit to?
What each vendor's docs say about the rate and the price of a purchase, as of November 1, 2026
Vendor | The rate on the quote | What the fee is made of | What no page states |
MoonPay | Card and wallet methods return a fixed rate, bank transfers a floating estimate settled when the money arrives; every quote has an expiry | Network, MoonPay and ecosystem fees, itemized | Percentages, and limit amounts |
Transak | A temporary quote refreshed every minute; the crypto is sent at the latest rate when payment settles | Transak's baseline fee plus a partner fee you set, capped at 5% | The baseline percentage, on the pages read |
Ramp Network | Quote endpoints return the amount and fee per payment method | A base fee and an applied fee; the example response shows 0.5% to 2.99%, a 3 EUR minimum fee and a 10 to 10,000 EUR purchase range | A lock period, and a price list |
The Ramp numbers come from an example response whose reference says the final percentage depends on the payment method and purchase size, so read them as an illustration. None of the three publishes what a given purchase costs, so the number to trust is the one in a live quote for your amount.
For a company, the rate row matters most: a card buyer accepts a small move between confirmation and settlement, and a finance team matching an invoice does not. Lumx offers a floating rate that prices at execution and a locked rate held for 30 seconds, 1 minute or 5 minutes, with the 30-second lock carrying no fee and the longer ones carrying one. Lumx pricing is a monthly platform fee plus usage-based per-transaction fees, transparent FX on locked quotes, no pre-funding; no published plans.
Why does a company buying stablecoins need more than a widget?
Four things change when the buyer is a legal entity. The first is who is verified: a company submits company documents and the details of the individuals behind it, not a photo ID and a selfie, as in how a KYB flow works. The second is where the money comes from: a company pays from its own bank account, and the receiving account should carry the company's name so the payment matches the right entity. The third is size: treasury purchases are larger than retail buys, and a limit that is not published cannot be planned against (MoonPay shares its limits through your account team). The fourth is what comes next: a company usually pays someone with what it bought, which is a payout leg with a status per step.
A standard KYB customer can move up to $50,000 per transaction and $100,000 per day or month, with higher limits after enhanced verification, and Lumx targets one business day for KYB. The BRL and MXN accounts open right after the customer is approved. A foreign company can hold a named virtual account (a local account number issued in the customer's own name) in BRL and MXN without a local entity in Brazil or Mexico.
Widget or business API: how to decide
The same purchase on a widget and on a business API with named accounts, as of November 1, 2026
Question | Widget (the three above) | Business API (Lumx) |
Who is the customer | A person, with a personal identity check | A company verified with KYB, or its end users |
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 or SPEI |
Rate | Fixed, refreshed or per method, by vendor | Floating, or locked for 30 seconds, 1 minute or 5 minutes |
After the purchase | Crypto sent to a wallet address | Stablecoin in a custodial wallet, then a payout to a bank account |
Pairs and rails | By the vendor's coverage page | BRL, MXN, USD, EUR and GBP, see Lumx coverage |
The decision follows one question: who is paying. A person who wants a token in a wallet uses a widget. Your company, or a company that is your customer, needs a named account, a company check and a way to pay out afterwards, which a stablecoin API bundles.
I recommend that a product already running a widget for its retail users keep it for them, and put the company's own funding on a separate path from day one. Mixing the two puts a treasury purchase through a flow built for a card buyer and leaves nobody who can match it to an invoice. Before signing with any of the three, I would ask each vendor in writing two things: whether a legal entity can be the buyer, and what the quoted amount does between confirmation and settlement.
If you want the named-account route, the funding mechanics are in how to fund a stablecoin on-ramp. For a named comparison with a provider that sells a business API, see Lumx vs Bridge, and for the wider field, best stablecoin APIs in 2026. To weigh providers, see choosing a stablecoin infrastructure provider and how stablecoin payout pricing works.
Which MoonPay alternatives and Coinbase Onramp alternatives suit a business?
MoonPay, Transak and Ramp Network are not the only consumer onramps a team weighs. Coinbase Onramp converts fiat into crypto sent to a wallet address the user chooses, paid by card, Apple Pay, Google Pay or, in the US, ACH, and its docs describe an app's end users, with no business buyer. Stripe's crypto onramp lets an app's customers buy crypto at checkout, with Stripe as merchant of record handling KYC. Both open only after an application. All of them serve a person buying crypto.
A company looking past that group needs three things none of those pages document: an off-ramp to a local account, a named account in the company's own name for the money coming in, and KYB in place of a personal check. On Lumx, a foreign company holds named accounts in BRL and MXN, collects by Pix, SPEI or PSE (Colombia's pull-payment rail), and pays out by Pix, SPEI, Bre-B (Colombia's instant-payment key system) or ACH Colombia. PSE is collection only.
When a business 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. An API that starts with a company check adds friction for no gain there.
It is also the wrong tool when the catalog is the product: a wallet that sells many tokens to many individuals wants a catalog like MoonPay's 100 or more, not a stablecoin account. And it is the wrong tool when you have no verified business customer: anything built on named accounts begins with KYB, so a product whose users are anonymous cannot start there. Keep the widget, and add a company path when the first business user arrives.
The recommendation is plain: a widget for individuals buying crypto, a business API for companies buying stablecoins to pay people, and both when your product has both kinds of user.
What a company's first purchase 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.
For a company buying USDC from Brazil, you create a business customer and request the BRL account in the same call. The customer accepts the terms and completes KYB, through the verification link or the API. At APPROVED, the account and a wallet on each supported blockchain are ready, and the account moves to ACTIVE.
For the purchase, you create an on-ramp, with a locked rate fetched first or the floating one. 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. The company pays from its bank, and the status moves from AWAITING_FUNDS through TRANSFERRING_FIAT and TRADING to SUCCESS, with a webhook at each step.
For repeat deposits, an autoconversion rule converts every incoming deposit to USDC or USDT without a call per payment. If a deposit or customer needs more information, the status goes to RFI (request for information, a compliance hold that asks for a document before a transaction clears). From the wallet, the company can pay a supplier over a local rail, listed in the operator map and on global payments. Current rates are on the BRL to USDC, MXN to USDC and USD to USDC pages. Going live through the API takes 2 to 3 weeks.
Methodology and sources
Vendor facts were read in public developer documentation on November 1, 2026, and are attributed to each vendor as of that date: the MoonPay on-ramp overview (dev.moonpay.com) with its off-ramp, onboarding, verification tier, quote and fee pages; the Transak documentation (docs.transak.com) with its quote, partner fee and partner FAQ pages; the Ramp Network getting-started page (docs.rampnetwork.com) with its v3 REST reference; and, read on November 2, 2026, the Coinbase Onramp overview (docs.cdp.coinbase.com) and Stripe's crypto onramp overview (docs.stripe.com). Where a page states no number, this post says so. Lumx behavior was read on docs.lumx.io on November 2, 2026, including transaction limits and coverage.
Verified on November 1, 2026. Operational context, not legal, tax, or investment advice.
Cover photo: Bence Balla-Schottner on Unsplash.
What is the difference between MoonPay, Transak and Ramp Network?
All three let an app's users buy and sell crypto inside the app. MoonPay is the merchant of record, Transak offers the most integration shapes, and Ramp Network leans on open banking for bank payments. Lumx is a different kind of product, a business API where the customer is a company with a named account.
Can a company buy stablecoins through MoonPay, Transak or Ramp Network?
The pages read describe a personal identity check, and KYB in the docs is the step the integrating app completes for production access. None documents a company as the buyer, so ask each vendor in writing. On Lumx, a business customer completes KYB, gets a named virtual account in its name and funds it by Pix or SPEI.
Do MoonPay, Transak and Ramp Network lock the exchange rate?
It depends on the method. MoonPay returns a fixed rate for card and wallet payments and a floating estimate for bank transfers, Transak refreshes its quote every minute and sends crypto at the latest rate, and Ramp Network states no lock period. On Lumx, a locked rate holds for 30 seconds, 1 minute or 5 minutes, and a floating rate prices at execution.
What do MoonPay, Transak and Ramp Network charge?
None of them publishes a price for a given purchase. MoonPay itemizes network, MoonPay and ecosystem fees in the quote, Transak adds a partner fee of up to 5% to its baseline fee, and Ramp Network returns a base fee and an applied fee per method. Lumx charges a monthly platform fee plus usage-based per-transaction fees, with transparent FX on locked quotes, no pre-funding and no published plans.
What are the best MoonPay alternatives and Coinbase Onramp alternatives for a business?
For a company, the alternative to a consumer onramp such as MoonPay or Coinbase Onramp is a business API that settles into a local bank account, not another widget. Consumer onramps, Stripe's crypto onramp included, serve a person buying crypto, while a company needs a named account, KYB and an off-ramp it can match to an invoice. Lumx is that kind of API: a business customer completes KYB, gets named virtual accounts in BRL and MXN, funds them by Pix or SPEI and pays out from its wallet over local rails.
