An off-ramp wallet turns every USDC or USDT deposit into fiat paid to a linked bank account, with no quote or payout call. How it works, fees, minimums.
An off-ramp wallet is a blockchain deposit address tied to one bank account. Every USDC or USDT deposit it receives converts to fiat and pays out to that bank account on its own, with no quote call and no payout call. You share the address with whoever pays you, and the money shows up as a bank transfer.
Think of it as the reverse of a virtual account. A virtual account turns incoming fiat into stablecoin. An off-ramp wallet turns incoming stablecoin into fiat.
Four steps, and only the first needs code:
That's the whole thing. No quote to request, no rate to confirm, no on-chain approval to sign.
It depends on the provider. BlindPay's offramp wallets accept these:
| Network | Stablecoins | Minimum deposit | Additional fee per deposit |
|---|---|---|---|
| Polygon | USDC and USDT | No fixed minimum | 0 |
| Base | USDC | No fixed minimum | 0 |
| Arbitrum | USDC | No fixed minimum | 0 |
| Tempo | USDC | No fixed minimum | 0 |
| Arc | USDC | No fixed minimum | 0 |
| Ethereum | USDC | No fixed minimum | 1 USDC |
| Solana | USDC | 50 USDC | 0.50 USDC |
| Tron | USDT | 200 USDT | 15 USDT |
"No fixed minimum" means the deposit only has to cover its own fees. The network is part of the address. A USDC transfer sent on the wrong chain is a different asset in the wrong place, so tell senders the network, not just the address.
Three fees stack on each deposit: the chain's additional fee from the table above, a percentage fee, and the bank transfer fee for the payout rail. The percentage and bank transfer fees depend on your pricing.
BlindPay's docs work through one example: 100 USDT sent on Tron, paid out over ACH.
The bank account receives $84.50. Send the same 100 USDT on Polygon, with the same example percentage and ACH fees, and it receives $99.50. Same payment, same bank, $15 apart, all of it from the network choice.
That's the flat-fee lesson from off-ramp fees explained in miniature. Fixed costs punish small deposits, so pick the network by the size of the payments it will carry.
| Off-ramp wallet | Quote and payout call | |
|---|---|---|
| Who starts it | Anyone who can send an on-chain transfer | Your integration, through the API |
| Rate | Market rate when the deposit lands | Locked in the quote, 5 minutes by default |
| On-chain approval | None; the sender just transfers | Needed for external wallets (for example, an ERC-20 approve) |
| Destination | One fixed bank account | Any approved bank account per payout |
| Best for | Third-party payers, exchange withdrawals, recurring settlement to one account | Payouts to many recipients, payments that need a known amount |
The deciding question: who controls the send? If it's you, a payout call gives you a locked rate and an exact delivered amount. If it's someone else, or a system that can only make a plain transfer, an off-ramp wallet removes the coordination entirely. A marketplace seller who gets paid by buyers in USDC is the textbook case; the LatAm marketplace payouts guide shows the wider flow.
Four things, all avoidable:
Once a payout exists, it follows the normal lifecycle: processing, then completed, failed, or refunded. Stablecoin payout statuses explained covers each state, and webhooks and reconciliation covers matching deposits to payouts.
Create a customer, add their bank account, then create the offramp wallet on that bank account with the network you want. The response returns the deposit address. On development instances the wallets live on testnets (Tron has none) and receive USDB, BlindPay's test stablecoin, with no additional fee, so you can test the full deposit-to-payout loop before going live.
Read the offramp wallets reference, then create one in the sandbox and send it a test deposit.
This article is for general information only and is not financial advice.
Five stablecoin APIs compared for cross-border payments: primary use case, pre-funding requirement, payout regions, and developer experience, plus how to choose by buyer scenario.
Ten stablecoin APIs compared for 2026: BlindPay, Circle, Bridge, BVNK, Fireblocks, Crossmint, Zero Hash, Conduit, Sphere, and Borderless, across rails, custody, pricing, and compliance.
Why a company should treat crypto debit cards and stablecoin cards differently: budget predictability, custody risk, per-swipe tax events, accounting, and spend controls.