Correspondent banking keeps cross-border payouts liquid by parking cash in nostro accounts in every country. What that trapped capital costs a treasury team, and what stablecoin liquidity changes.
To guarantee fast settlement in several currencies, companies pre-fund accounts in every country they pay into. Reais in Brazil. Pesos in Mexico. Euros in Europe. Each balance is sized for the busiest payout day plus the days it takes to refill it by wire, and it sits there, earning little and moving with the exchange rate, until it is spent. That is trapped capital, and correspondent banking needs it to work.
Stablecoin liquidity removes the country-by-country balance. This guide walks through why the old model needs pre-funding, what it costs in numbers a treasury team can check, and what to ask before switching.
Correspondent banking moves money by debiting and crediting balances that banks hold at each other. No money travels. Ledgers update.
A US company paying a supplier in Colombia typically goes through a chain like this:
Every arrow in that chain is a nostro/vostro pair. The originating bank's "nostro" is its balance at the correspondent. The correspondent sees the same balance as a "vostro". Settlement means debiting one and crediting the other, then reconciling the statements.
Because each bank in the chain is a separate business with its own fees, screening, and hours.
The result is the 1 to 5 business day window most finance teams already plan around. It is also why fast local payouts over this model need cash already sitting in the destination country.
Trapped capital is working capital held in pre-funded accounts so payments can settle on time. It is the cost of speed on correspondent rails, and it shows up in four places on a treasury report:
It also grows in steps. Add a sixth country and you add a sixth balance, a sixth bank, and a sixth currency position. In markets with currency controls, a local balance can be hard to move back out at all.
It replaces a balance in every country with a single funding source and conversion at payment time.
The treasury keeps dollars, or USDC and USDT, in one place. When a payout is due, it requests a quote, funds exactly the quoted amount, and the stablecoins move on-chain in seconds. A liquidity provider converts them into local currency and pays the recipient over the local rail. Nothing was parked in the destination country beforehand.
At BlindPay, that single funding source is one of three: a stablecoin wallet you control, a BlindPay-managed wallet, or a US virtual account that turns ACH, wire, or SWIFT deposits into USDC or USDT. The differences between funding models, including the "provider balance" model that looks like no pre-funding but isn't, are covered in what "no pre-funding" means in a stablecoin API.
The local currency still has to exist somewhere. The liquidity provider holds it as working inventory across all its customers, which is the pooling effect described in what a liquidity market is. You stop paying for your own idle buffer.
This is an illustrative scenario with round numbers, not data from a real company. Use it as a template and swap in your own figures.
A payments company sends 2,000,000 dollars a month in payouts to five markets, once a week. Under the correspondent model, it keeps about two weeks of volume in each country: one weekly cycle plus up to five business days to refill by international wire. That works out to roughly half a month of volume per country.
| Market | Local rail | Monthly payout volume (USD) | Pre-funded balance, correspondent model (USD) | Destination-currency balance, stablecoin model (USD) |
|---|---|---|---|---|
| Brazil | Pix | 800,000 | 400,000 | 0 |
| Mexico | SPEI | 500,000 | 250,000 | 0 |
| Colombia | ACH Colombia | 300,000 | 150,000 | 0 |
| Argentina | Transfers 3.0 | 200,000 | 100,000 | 0 |
| Eurozone | SEPA | 200,000 | 100,000 | 0 |
| Total | 2,000,000 | 1,000,000 | 0 |
What that million dollars costs, with the assumptions stated:
| Cost line (illustrative) | Correspondent model | Stablecoin model |
|---|---|---|
| Idle capital | 1,000,000 USD at all times | None beyond the payouts in flight |
| Yield given up at 4% a year | About 40,000 USD a year | None; dollars stay in treasury until payout day |
| Loss on a 3% adverse FX move | About 30,000 USD across five currencies | Limited to the minutes between quote and settlement |
| Local bank relationships | 5 | 0 (one integration) |
| Refill wires | About 5 a week, one per market | 0 |
| Double the volume | Balances double to 2,000,000 USD | Still 0 |
The last row is the one that matters for a growing company. Under pre-funding, trapped capital scales with volume and with every new market. Funded at send time, it stays at zero, and a new market is a new bank account type instead of a treasury project.
The trade-off is timing. You need the funds on hand when you send, and a payout has to be created inside the quote's window, five minutes by default at BlindPay. USD deposits into a virtual account by ACH or wire can take days to land, so plan the deposit, not a balance. How long a stablecoin payout takes has the timing by rail.
Ask these in writing. The answers expose the real funding and liquidity model fast.
For reference, here is how BlindPay answers them. Payouts are funded when you create them, with no pre-funded balance. Quotes lock the rate and fees for five minutes by default, and the quote response shows the market rate next to BlindPay's rate. Payouts settle over Pix, PIX Safe, and TED in Brazil, SPEI in Mexico, ACH Colombia, Transfers 3.0 in Argentina, ACH, wire, and RTP in the US, SEPA in Europe, and international SWIFT. BlindPay operates as a non-custodial payment processor, and a refunded payout returns the stablecoins to the funding source; stablecoin refunds process immediately. Pricing is published, with per-rail minimums instead of a volume floor. KYC and KYB run inside the API before money moves.
When the counterparty requires a wire, when the corridor has no stablecoin liquidity, or when the payment is a large one-off between two banks that already know each other. SWIFT reaches almost every bank on earth, and that coverage is real. Many teams run both: stablecoin liquidity for recurring payouts into markets with instant local rails, SWIFT for the long tail.
Pull last quarter's balances in every foreign account and add them up. That number is your trapped capital. Then read the payout quickstart and run one payout on a development instance to see what funding at send time looks like, or talk to the BlindPay team about moving a specific corridor.
This article is general information, not legal, tax, or financial advice.
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.
Seven stablecoin payment platforms compared for US fintechs in 2026: what makes an API production-ready, how each provider handles compliance, settlement speed against ACH, and how to run the evaluation.
How to choose a stablecoin payment provider in 2026: the four provider types, a comparison of 10 options, and the questions that decide the fit.