The types of crypto off-ramps are payment APIs, off-ramp wallets, exchanges, OTC desks and wallet-embedded ramps. They differ on who they serve, who holds the funds before conversion, how much one transaction can move and whether the cash can land in a third party's bank account. For a business paying suppliers, that last question usually picks the type.
The basics are in what a stablecoin off-ramp is, and the shortlist is in the best stablecoin off-ramp APIs. This post sorts the options so you can rule out three types early. To weigh the two directions, start with on-ramp versus off-ramp for a fintech.
What are the main types of crypto off-ramps?
Five, and they split along one line: some cash out your own balance, others pay other people.
The five types of crypto off-ramp, as a model of the typical pattern. It is not a survey: terms vary by venue, so check each provider's own terms.
Type | Built for | Who typically holds the funds before conversion | Third party's bank account | How limits typically work |
Payment API | A company or platform paying suppliers, contractors or users in local currency | Depends on the provider's model | Yes, with the payee and the relationship to the payee recorded | Tiered by the customer's verification level |
Off-ramp wallet | A business that receives stablecoins from clients and wants local currency | The provider, from deposit to payout | Typically the bank account linked to the wallet | Set by the provider, and they vary |
Exchange | Cashing out your own balance now and then | The exchange, from deposit until you withdraw | Typically an account in your own name | Withdrawal limits that depend on the account's verification level |
OTC desk | One large block, priced by negotiation | Depends on the desk | Typically the party that signed the desk's agreement | A minimum block, quoted per trade |
Wallet-embedded ramp | A consumer selling crypto inside a wallet app | The ramp provider, during the conversion | Typically the user's own account | Consumer limits set by the ramp |
Lumx sits in the first row: a payment API with a local last mile. It also has an OTC desk for much larger operations, but it is not an exchange or a wallet ramp.
How each type moves the money, and who can be paid
A payment API runs the job behind one integration. You register the payee's bank account as a destination, wait for it to be approved (a payout cannot run against a destination that is not), ask for a quote, send the stablecoin and follow the status by webhook, while the provider converts and pays out on the local rail.
An off-ramp wallet inverts the order: the provider gives you a wallet address tied to a bank account, and whatever arrives is converted and paid out. An exchange typically has you run each step by hand and withdraw to your own bank. An OTC desk typically quotes one block and wires the fiat after onboarding. Each venue's terms decide. The wallet type fits a business paid in USDC by its own customers, not one paying many payees, because each address maps to one account. It is not a virtual account, which is an on-ramp tool.
On Lumx the sale happens when the platform decides: the payout is an explicit API call from the customer's custodial wallet to a registered destination, and the platform picks a floating quote, a real-time reference with no lock, or a locked quote. The payout moves through TRANSFERRING_STABLECOIN, TRADING and TRANSFERRING_FIAT to SUCCESS, and each step emits an offramp.* webhook event, so the platform needs no polling.
Consumer and business off-ramps differ mainly on who gets paid. A consumer ramp runs KYC (know your customer, the verification of an individual) and pays the user's own account; a business ramp runs KYB (know your business, the verification of a company and its owners) and pays suppliers and staff. Paying a third party adds a disclosure duty: the provider has to know who the payee is and why. See first-party versus third-party payouts.
On Lumx every destination is tied to a customer and carries a holder relationship: SELF for the customer's own account, or SUPPLIER, EMPLOYEE, BUSINESS_PARTNER and other values for third parties. Each payout also carries a purpose code such as TRADE_TRANSACTIONS or PROFESSIONAL_SERVICES. Destination verification includes sanctions screening and the name check (VoP or CoP) that Lumx's banking partners run, and the SELF check covers the name. The customer behind it has passed KYB checks. A supplier can be paid as a disclosed destination holder, but funds that belong to non-onboarded parties cannot be pooled in the customer's account, a rule Lumx calls nested payments.
Limits by type, and the numbers on a payment API
We state no exchange, OTC or wallet-ramp figures, because they change by venue. What you can compare is the shape: exchanges and wallet ramps usually cap by verification level, an OTC desk usually sets a minimum block, and a payment API caps by verification tier.
In Colombia, Bre-B (Colombia's instant payment system) caps a single transaction at 1,000 UVB, about COP 12.1 million, under the Banco de la República's rules, for every provider. We describe the corridor in payout limits and cutoffs by rail.
Default Lumx limits by verification tier, in USD. Enhanced tiers are set per customer after review.
Limit | KYC Standard | KYC Enhanced | KYB Standard | KYB Enhanced |
Per transaction | $7,500 | $25,000 and up | $50,000 | $50,000 and up |
Daily | $15,000 | $50,000 and up | $100,000 | $100,000 and up |
Monthly | $15,000 | $50,000 and up | $100,000 | $100,000 and up |
Each transaction type counts against its own limit. A payout over a limit is rejected with TRANSACTION_LIMIT_EXCEEDED, and a customer can request a higher limit with a supporting document. A limit increase is not a compliance hold, unless it is required to approve a transaction. A USD 200,000 payout fits the API and falls under Enhanced verification.
What reaches the recipient, and how fast, on each rail?
Payout rails on Lumx by currency, with cut-off and settlement as published in the Lumx docs on November 1, 2026. The Colombia rows are effective November 2026, and no ACH Colombia settlement time is published.
Currency | Rail | Cut-off (local time) | Settlement |
BRL | Pix | None | Instant, 24/7 |
MXN | SPEI | None | Instant, 24/7 |
EUR | SEPA | None. Payments of EUR 100k or more between 4:30 PM and 2:30 AM UK time route to SEPA Credit Transfer | SEPA Instant, or same or next business day for a SEPA Credit Transfer |
GBP | Faster Payments | None | Instant, up to £1M per payment, 24/7 |
USD | ACH | 2:00 PM ET | 1 to 2 business days |
USD | FEDWIRE | 3:00 PM ET | Same business day, typically within hours |
USD | SWIFT | 3:00 PM ET | 1 to 5 business days |
COP | Bre-B | Not listed in the SLA page | Instant rail, capped at 1,000 UVB per transaction |
COP | ACH Colombia | Not listed in the SLA page | Not published; no per-payment limit |
Pix (Brazil's instant payment system) and SPEI (Mexico's interbank transfer system) land a payout within minutes at any hour. In Colombia, payout runs over Bre-B or ACH Colombia, chosen when the destination is registered, and ACH Colombia is the rail above the Bre-B cap. BRL is Pix only. SWIFT is USD only, and it is where the cost hides: each correspondent bank on the way can add hours or days and deduct fees outside Lumx's control.
On Lumx a payout reaches the bank rail once the stablecoin transfer and the trade are done, and the rail's own reference comes back with the status. You always send EUR as rail SEPA, and Lumx picks the scheme automatically. Live rates are on USDC to BRL and USDC to MXN, a stablecoin corridor names one pair and one rail, and the coverage page and supported countries list show where each rail is available.
How do the types compare on price and timing?
A model of typical price, checks and custody. No figures are given because fees and limits are set per venue and we have no primary source for them.
Type | How it is typically priced | Speed | Verification | Custody |
Payment API | Platform fee plus per-transaction fees, and the FX rate on the quote | The rail, after the stablecoin transfer and the trade | KYB, and the payee registered as a destination | Depends on the provider |
Off-ramp wallet | Usually a fee or spread per conversion | Starts at deposit, then the rail | Verification at signup | The provider, from deposit to payout |
Exchange | Usually trading and withdrawal fees | Deposit, sell, withdraw, then the rail | KYC or KYB on the account | The exchange |
OTC desk | A spread agreed per trade | Agreed per trade, usually a wire | Onboarding before the first trade | Depends on how the desk settles |
Wallet-embedded ramp | A fee or spread shown before you confirm | Minutes to the rail, then the rail | Consumer KYC | The ramp provider, during conversion |
Every type ends on the same bank rails, so speed is the stablecoin transfer plus the rail table above, and cost is the provider's fee plus what the receiving bank adds.
On Lumx the stablecoin sits in the customer's custodial wallet until the payout call, and the customer passes KYB (know your business) before the first payout. Pricing is 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 parked in settlement accounts before a payout, and the wallet can still hold a balance.
Why do businesses off-ramp stablecoins instead of Bitcoin?
Because the number on the invoice has to be the number that arrives: a stablecoin such as USDC or USDT is built to hold one dollar, while Bitcoin can move between the send and the conversion.
On Lumx you choose the rate. A floating rate is a real-time reference with no lock. A locked rate holds for 30 seconds, 1 minute or 5 minutes, with no extra fee at 30 seconds and a fee from 1 minute, and only a locked rate lets you quote a target amount.
Choosing a type by the recipient first
I would choose the type by asking who the recipient is before asking what it costs. If the payee is anyone other than the company itself, an exchange or a wallet ramp is out on day one, and the price comparison between the remaining types gets short. I would also ask an OTC desk for a quote on any single block large enough to matter and compare it with an API quote for the same amount, because only the comparison shows whether the negotiation and the manual setup are worth it.
When a payment API is the wrong type
It is the wrong type when you cash out your own balance once a quarter, because the integration costs more than the withdrawals save. It is wrong for one block with no recurring flow, since an OTC quote can beat an API price. It is wrong when the stablecoin must stay in self-custody, and when the corridor has no local rail on the provider's list. For blocks far above API size, Lumx's OTC desk is the route.
What the payment API type 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.
In practice, a platform onboards its customer, funds the customer's wallet with stablecoin or an on-ramp, registers the payee as a destination and triggers the off-ramp. With the Lumx global payments API, the destination goes through verification first, and the platform learns the outcome from the destinations.approved or destinations.final_rejection webhook before it triggers the payout. Lumx is custodial: the stablecoin sits in the customer's wallet until the payout call. When transaction monitoring flags an on-ramp or off-ramp, it is held for review. Compliance contacts the customer by email or Slack (operations@lumx.io is the channel) and asks about the relationship between sender and receiver and the purpose, an RFI (request for information). The 24-hour window applies to every transaction, and the transaction may be refunded if there is no answer. There is no transaction RFI API yet; it is due between late 2026 and the first quarter of 2027.
The final amount of a locked quote already includes Lumx's fee and any partner fee. The operator map shows who else works in these corridors, and what a stablecoin API is explains the category.
Methodology and sources
We sorted off-ramps by four criteria: who can be paid, who holds the funds, how limits work and which rail ends the trip. The type rows are a model, not a survey. Lumx facts come from docs read on November 1, 2026: Coverage, cut-off times, Transaction Limits, Destinations, Wallets, Transactions, Exchange Rates, RFI, Webhooks and Nested Payments. We state no limit, speed or fee for exchanges, OTC desks or wallet ramps, because those are set per venue and we have no primary source for them. The Bre-B cap is from the Banco de la República's Circular Reglamentaria Externa DSP-465, Asunto 18, numeral 3.2 (March 31, 2026 sheet), and the COP 12,110,000 figure from its Conozca Bre-B page, cited by name.
The regulatory texts are BCB Resolution 520/2025 of November 10, 2025, 31 CFR 1010.100(ff), read on Cornell's Legal Information Institute, Brazil's Law 14.478 of December 21, 2022 and FinCEN guidance FIN-2019-G001 of May 9, 2019.
Verified on November 1, 2026. Operational context, not legal, tax, or investment advice.
Cover photo: Chris DUNN on Unsplash.
What are the types of crypto off-ramps?
Five: payment APIs, off-ramp wallets, exchanges, OTC desks and wallet-embedded ramps. Payment APIs and off-ramp wallets serve businesses. Exchanges and wallet ramps typically cash out your own balance, and OTC desks handle one large block. Lumx is a payment API that pays out from a customer's USDC or USDT wallet to a registered destination.
Can a crypto off-ramp pay someone else's bank account?
With a payment API, yes, as long as the provider records who the payee is and why they are paid. Exchanges and wallet ramps typically withdraw to an account in your own name, and an OTC desk typically settles to the party that signed its agreement, but each venue's terms decide. On Lumx, each destination carries a holder relationship such as SUPPLIER or EMPLOYEE, and each payout carries a purpose code.
Is a virtual account a type of off-ramp?
No. A virtual account receives a bank transfer and ends in stablecoin, which makes it an on-ramp tool. On Lumx, a named virtual account collects the money in, and the payout runs as an off-ramp from the customer's wallet.
Are crypto off-ramps regulated?
Yes, in the two jurisdictions we sourced. In Brazil the framework is Law 14.478 of December 21, 2022 and Central Bank Resolution 520/2025, which sets the authorization of virtual asset service providers (SPSAV, Sociedade Prestadora de Serviços de Ativos Virtuais). In the United States, FinCEN guidance FIN-2019-G001 of May 9, 2019 applies money transmitter rules to a business that exchanges convertible virtual currency, and a money services business is defined in 31 CFR 1010.100(ff). Lumx applied for the SPSAV authorization and operates under the transition regime of Resolution 520/2025, Article 88.
Which type of off-ramp should a business use for supplier payouts?
A payment API, because it pays third parties, runs business verification and reports each step by webhook. On Lumx, a supplier payout is an off-ramp to a destination registered with the SUPPLIER relationship, over Pix, SPEI, Bre-B, ACH, FEDWIRE, SEPA, Faster Payments or SWIFT in USD.
