Why off-ramps cap how much you can convert per transaction, day, and month, how the caps map to KYC and KYB tiers, and the documents that raise them.
Off-ramp limits cap how much a customer can convert from stablecoins to fiat per transaction, per day, and per month. They exist because anti-money laundering rules are risk-based: a provider sizes each customer's limits to how much it has verified about them. More verification, higher limits. On BlindPay, a verified business starts at $30,000 per transaction, $100,000 per day, and $250,000 per month, and can request more with supporting documents.
Limits are a compliance setting, not a liquidity one. That distinction matters later.
Three reasons, in order of importance.
Risk-based compliance. The FATF standards that national AML rules start from ask providers to match controls to risk. A customer verified with a government ID and a selfie is a known person. A customer who has also shown bank statements and tax returns is a known person with a known source of money. The second one can move more before anything looks unusual.
Damage control. If an account is taken over or a customer turns out to be fronting for someone else, the per-transaction and daily caps bound how much leaves before monitoring catches it. Real-time transaction monitoring covers what watches the payments inside the limits.
Faster onboarding. Tiers let a provider approve people quickly at a low limit and ask for more paperwork only when someone needs more room. That's why an individual can pass automated KYC in about a minute instead of waiting days for a manual review. It's also why onboarding drop-off stays low: nobody uploads a tax return to send $500. The tradeoffs of automated versus manual review are in automated KYC/KYB vs manual onboarding.
BlindPay's defaults, from the KYC reference:
| KYC Standard (individual) | KYB Standard (business) | KYC Enhanced (individual) | |
|---|---|---|---|
| Per transaction | $10,000 | $30,000 | $50,000 |
| Daily | $50,000 | $100,000 | $100,000 |
| Monthly | $100,000 | $250,000 | $500,000 |
| Review | Automated, about 60 seconds | Manual, 3 hours to 1 business day | Manual, 3 hours to 1 business day |
A few details that trip people up:
Usually the monthly one, and usually later in the month than you'd expect.
Take a marketplace on KYB Standard that settles sellers every day, about $15,000 a day. Each payout is well under the $30,000 per-transaction cap. Each day is well under the $100,000 daily cap. The monthly cap is $250,000. Sixteen days in, the total is $240,000, and day 17's payout would push it to $255,000. So day 17 fails at the quote, and so does every day after it.
Payroll hits it differently. Paying 40 contractors $3,000 each on the 1st is $120,000 in one day, over the daily cap even though every single payout is small. The LATAM contractor payroll guide covers how teams schedule runs.
Model a month of real volume against all three caps before launch. It takes ten minutes and saves a support fire drill on day 17.
On BlindPay, through a limit increase request:
Only one request can be in review per customer at a time, and the customer must already be approved. What compliance expects each document to show is in the source of funds guide. On development instances, every request auto-approves at the requested amounts, so you can test the flow end to end.
The documents that work best tell a simple story: this is where the money comes from, and this is why the volume is about to grow. A signed contract with a new client does that better than three random bank statements.
No. They answer different questions.
No pre-funding is about where money sits before a payout. The funds stay in your wallet until the payout executes, instead of sitting in a balance with the provider or in a bank account in the destination country. What no pre-funding means walks through the models, and on/off ramp liquidity with live quotes explains how liquidity gets sourced per quote.
Limits are about how much a verified customer may move. A provider can source liquidity on demand for every quote and still cap each customer at their tier. Both are true at once.
Rails also have floors, which are a different thing again. On BlindPay, SWIFT payouts need at least $100, SEPA payouts need at least 11 USDC (or 10 EUR by receiver amount), and a Tron off-ramp wallet needs at least 200 USDT. Those are minimums set by fees and rail rules, not compliance caps.
Yes. Limits are the outer fence. Inside it, a payout can still be held for review if it's unusual: a first withdrawal, a pattern that doesn't match the customer's history, an amount large relative to past activity, or a possible sanctions match. On BlindPay, US ACH, wire, RTP, and SWIFT payouts also pass through on_hold as a standard step after the crypto is collected. A hold can last up to 30 days; approval resumes the payout, and a timeout without a decision fails it. The on-hold transactions guide has the details.
A payout over the limit is different. It's rejected at the quote, before any money moves, so nothing gets stuck in the middle.
Take your expected monthly off-ramp volume and your largest single payment. Check both against the default tier for your customer type. If either one is close, file the limit increase now, with documents that explain the growth, instead of the week a payout fails.
This article is for general information only and is not legal or financial advice.
Stablecoin transfers settle final in minutes and cannot be reversed. That finality proves custody at every step, but it also opens a fraud gap on the fiat side of the payment.
A side-by-side comparison of automated and manual KYC/KYB for fintechs: onboarding time, false-positive rates, cost per verification, scaling across jurisdictions, and audit-trail quality, plus the cases where a human reviewer is still required.
How compliance agents apply FinCEN, MiCA, FCA, MAS, and Banco Central do Brasil rules to cross-border stablecoin payments: jurisdiction table, the FATF Travel Rule, multi-list sanctions screening, the four components of a compliant program, and questions to ask a compliance provider.