Stablecoin on ramp off ramp explained for finance

An on-ramp turns fiat into stablecoin at a licensed partner. An off-ramp does the reverse into a local bank account. For a finance team, ramps are the choke point between an invoice paid in USDC and payroll that lands in INR, BRL, or EUR. Pick the wrong ramp for a corridor and the spread, wire fee, and settlement delay show up on the P&L every month. Plaitr routes each payment to the ramp that fits the corridor, so the treasurer sees one balance and one ledger.

Why do finance teams end up with three ramp partners?

A treasurer starts with one provider because one corridor works. Circle Mint mints USDC one to one from a US wire, so a US-facing business signs up first. Then a supplier asks for a payout in Mexico, and Circle Mint does not settle to a Mexican bank account. Bridge covers LATAM payouts, so a second contract goes in. Then a customer in the UK pays in GBP over Faster Payments, and neither Circle nor Bridge holds the local licenses treasury wants. BVNK covers UK and EU with same-day settlement, so a third contract joins the stack.

Each contract carries its own KYB pack, its own API, its own reconciliation format, and its own minimum volume. The finance team now runs three integrations, three settlement schedules, and three sets of monthly statements. Cash sits fragmented across three custodial balances, and the accounting team stitches the postings together at month end.

What does each ramp cost in practice?

Public pricing on the three most common enterprise ramps sets a floor.

Circle Mint charges no fee on USDC minting or on the first $40M of daily redemptions. Redemptions above $40M step to 2 basis points, and amounts above $100M charge 5 basis points. Wire fees stay on the originating and receiving bank, and cross-currency legs carry standard FX. Coverage lists 185+ countries for minting and redeeming, but Circle Mint itself is a KYB-gated institutional account restricted to registered distributors, banks, exchanges, and payment firms. Onboarding runs full institutional KYC and sanctions screening.

Bridge sits at roughly 10 basis points plus network fee on stablecoin movement, with fiat payout adding the underlying rail cost. ACH is near zero. SWIFT typically runs $15 to $30 per wire. Coverage centers on US and EU payouts with parts of LATAM and Africa on the roadmap. Bridge is custodial and enterprise pricing sits behind sales, so procurement validates corridor-level economics directly.

BVNK targets 0.5% to 1% on conversion, negotiated by volume and pair. It supports USDC, USDT, EURC, and PYUSD across eight chains, with same-day settlement in 30+ currencies including GBP, EUR, USD, and SGD. Coverage is 130+ countries. Real-time payment rails such as MXN and BRL settle in minutes. Corridors without RTP rails settle same day or T+1. KYB runs roughly two weeks and requires a $500,000 monthly volume floor plus six months of trading history.

None of these numbers is bad. Each partner is priced for the corridor it serves. The cost shows up when a treasurer forces one provider to serve a corridor another provider is priced for.

Why does the standard multi-partner setup fail, and what does Plaitr do differently?

Three problems compound in the multi-partner setup.

Cash gets stranded. USDC minted through Circle sits in a US bank chain. The Bridge balance holds LATAM float. The BVNK balance holds GBP and EUR. Moving cash between the three costs a bridge, a wire, or a swap, so treasury holds surplus at each provider to avoid stockouts.

Reconciliation gets manual. Each provider posts settlement lines in its own format. Fee lines land in different columns. FX legs get bucketed differently. A month-end that should take an hour turns into two days of matching statements to invoices.

KYB gets redone. Each provider re-runs beneficial ownership, board resolutions, and sanctions. A finance team going live on three ramps in parallel spends six to eight weeks on onboarding before the first payment moves.

The multi-partner setup solves the corridor problem and creates an operations problem in its place.

Plaitr is a non-custodial account. Private keys never touch Plaitr infrastructure. Funds sit at licensed partner banks. Plaitr provides the software layer that reads a payment intent, picks the right ramp for the corridor, and posts the movement to the books on settle.

The treasurer sees one balance. Behind it, Plaitr routes a US fiat leg to a partner priced for US rails, a LATAM payout to a partner with the local license, and an EU settlement to a partner with SEPA access. The finance team signs one KYB pack, one contract, and one integration. Fees stay corridor-priced because the routing goes to the partner that already prices that corridor competitively.

Plaitr is not a bank. Cards are coming soon. Wyoming governing law applies to the account agreement. Banking is delivered through licensed partner institutions.

What does it look like in practice?

A US client pays $18,400 in USDC on Base against an invoice from a Wyoming LLC exporter. Plaitr receives the payment into the business wallet, posts revenue against the invoice on confirmation, and holds the USDC in the business's own control.

The exporter owes an Indian manufacturer INR 12,60,000 for a shipment. Plaitr routes the off-ramp through a partner priced for INR settlement into the manufacturer's Indian bank account. The stablecoin leg costs the network fee. The fiat leg costs the corridor's published rate. Settlement lands the same day because the INR corridor sits on a real-time rail. The exporter never opens an Indian account, never files a separate KYB with a second provider, and never reconciles a second statement.

Later that week, the same exporter pays a design contractor in Lisbon in EUR. Plaitr routes that leg through the partner priced for SEPA, off-ramps EURC to EUR, and settles into the contractor's IBAN. The treasurer sees three ledger entries: revenue in, INR payout out, EUR payout out. One balance. One month-end.

What to do next?

If treasury runs on more than one ramp today, or the KYB queue is holding up a corridor a customer already asked for, see how the routing works end to end. Book a demo at demo.plaitr.com.