No pre-funding still means holding some USDC. How to size one stablecoin float for every payout corridor: lead time, safety stock, and a worked example.
A stablecoin float is the USDC or USDT you keep in your own wallet to fund payouts as they happen. Size it as average daily payout volume times the days it takes to refill the wallet, plus a safety buffer for busy days. One float covers every corridor, so it replaces a separate pre-funded account per country.
"No pre-funding" gets read as "no balance at all". Not quite. Nothing has to sit in Brazil or Mexico before you pay, but the stablecoins still have to be in the funding wallet when you press execute. The question is how much.
Key takeaways
Because a payout pulls stablecoins from a funding wallet at the moment it executes. No pre-funding removes the balances parked in destination countries. It does not remove the balance that pays for each conversion.
Pre-funding is a cost the industry names out loud. The Financial Stability Board lists "liquidity cost for prefunding" among the drivers of high cross-border payment costs in its targets report. The traditional fix is a local account per corridor, topped up in advance. Correspondent banking vs stablecoin liquidity shows how that capital gets trapped.
With a stablecoin payout provider, you request a quote, the quote locks the rate and fees, and executing it pulls the quoted amount from your wallet. At BlindPay, the funding source is a managed wallet balance or an external wallet you control and authorize on-chain (payouts docs). Either way, the money has to be there.
| Pre-funded local accounts | One stablecoin float | |
|---|---|---|
| Where money sits | One bank balance per destination country | One wallet in USDC or USDT |
| Currency of idle money | BRL, MXN, COP, ARS, and so on | Dollars |
| FX exposure on idle money | Yes, on every local balance | No, conversion happens at execution |
| Number of balances to watch | One per corridor | One |
| Refill method | Cross-border wire to each country | One on-ramp or stablecoin transfer |
A float has two parts: cycle stock, which covers normal days until the next top-up lands, and safety stock, which covers the days that run hot. Same reorder math inventory teams use, applied to dollars.
The formula:
Pull D and σ from at least 90 days of payout history. Recalculate before seasonal peaks such as payroll dates.
Lead time depends on the rail you use to buy the stablecoins. At BlindPay, a bank deposit into the instance creates a payin that delivers USDC or USDT to the destination wallet, and the timing follows the rail (overview).
| Top-up route | Documented receive timing at BlindPay | What it means for lead time |
|---|---|---|
| RTP (US) | Instant | Same-day refill, L close to 1 |
| Pix (Brazil) | Instant, up to 5 minutes to confirm | Same-day refill from BRL |
| SPEI (Mexico) | Instant, up to 10 minutes to confirm | Same-day refill from MXN |
| ACH (US) | Up to 5 business days | Plan for L = 5 |
| Domestic wire (US) | Up to 5 business days | Plan for L = 5 |
| Stablecoins already held elsewhere | One on-chain transfer | Minutes, depending on the network |
RTP is the US rail worth planning around. The Clearing House runs it 24/7/365 with final settlement and a $10 million network limit per transaction, which is why it pulls lead time down toward one day.
Two details catch teams out. Business days are not calendar days: payouts over Pix and SPEI run on weekends, while ACH and wire top-ups do not (cut-off times on weekends and holidays). And a deposit into a US virtual account turns into a payin automatically, so a standing transfer from your operating account can refill the float without anyone creating a quote.
Illustrative example. A company pays out $200,000 a month over 22 business days: $80,000 to Brazil, $60,000 to Mexico, $30,000 to Colombia, and $30,000 to Argentina. Daily standard deviations are $1,800, $1,500, $1,000, and $1,000. Service level z = 1.65.
Pre-funded model, refilled every 5 business days, one balance per country:
| Corridor | Daily average | Cycle stock (x5) | Safety stock (1.65 x σ x √5) | Balance |
|---|---|---|---|---|
| Brazil | $3,636 | $18,182 | $6,641 | $24,823 |
| Mexico | $2,727 | $13,636 | $5,534 | $19,171 |
| Colombia | $1,364 | $6,818 | $3,690 | $10,508 |
| Argentina | $1,364 | $6,818 | $3,690 | $10,508 |
| Total | $9,091 | $65,009 |
One pooled stablecoin float. Daily average is $200,000 / 22 = $9,091. Pooled σ, assuming corridors move independently, is √(1,800² + 1,500² + 1,000² + 1,000²) = √7,490,000 = $2,737.
Pooling saves about $9,500 (15%). Faster top-ups save about $42,000 more. What's interesting here is the order of the effects: the float shrinks most when refills get faster, not when corridors share a balance.
At an illustrative 5% annual cost of capital, the difference between $65,009 in four local currencies and $13,607 in dollars is about $2,570 a year, before any FX loss on the local balances.
The float sits wherever your payouts are funded from, on the same network and token you quote with. A quote is priced for a specific network and token pair, so a float on Ethereum cannot fund a quote created for Solana. Does the network change your off-ramp quote? covers how that choice shows up in fees.
| Location | Who controls the keys | How a payout pulls funds |
|---|---|---|
| Your own wallet (self-custody or a wallet provider) | You | You authorize the exact quoted amount on-chain, for example an ERC-20 approve on EVM chains |
| BlindPay managed wallet (beta) | BlindPay, as custodian | One API call, no on-chain signing |
BlindPay operates as a non-custodial payment processor for payout flows from customer-controlled wallets: you authorize the exact amount and BlindPay executes that single transaction. Optional BlindPay-managed wallets (beta) are custodial when you choose that path.
If the float sits in a managed wallet, idle USDC on Base or Polygon can earn yield once BlindPay enables it on the instance. Payouts still work: BlindPay redeems from the vault when the idle balance is short, which adds processing time. The rate is variable, can be zero, and the vault carries smart contract and market risk.
Top up when the balance falls to the reorder point, which equals the float formula itself: D x L + safety stock. Above that line you have enough to cover the lead time. Below it, a busy stretch can leave a payout unfunded.
A simple rule set:
payout.complete webhook, or on a schedule.Refunds feed the float too. If a payout cannot be delivered after the stablecoins are collected, BlindPay refunds them to the quote's refund wallet, or to the sending wallet when none is set. On Pix and other non-USD local rails the refund is automatic, while USD payouts and payouts whose review times out are refunded after an operator review. Count pending refunds as incoming, not as cash on hand.
Two things: the return you give up on the idle balance, and exposure to the stablecoin issuer. The first is the cost of capital times the float. The second is why the float should be sized, not maximized.
USDC's issuer says each token is backed by cash and cash-equivalent reserves and redeemable 1:1 for US dollars, and publishes reserve reports on its transparency page. A peg can still wobble under stress. Stablecoin depeg risk in payments walks through what that means for a working balance, and who carries FX risk in a stablecoin payout explains why the float itself carries no FX risk until a quote executes.
A float sized with the formula keeps both costs bounded. A float sized by habit ("keep a month on hand") usually carries three or four times what the lead time requires.
For the bigger picture of why pre-funding exists at all, read what no pre-funding means in a stablecoin API, and for the vocabulary used here, the on/off-ramp liquidity glossary.
Export the last 90 days of payouts, compute the daily average and standard deviation, and plug them into D x L + 1.65 x σ x √L for the top-up rail you use today. Then run it again with a same-day rail. The gap between the two numbers is the capital a faster refill would free. The payouts docs show how each funding source is authorized.
Seven places blockchain payments beat bank rails: contractor payroll, remittances, B2B suppliers, marketplaces, 24/7 treasury, bill pay, and PSP payouts.
AP2, ACP, and x402 each verify that an AI agent had permission to spend. Here is what every protocol covers, who backs it, and the reconciliation gap none of them close.
The three roles behind every card program, stablecoin cards included: what each one does, who carries liability, and what to ask a provider.