Correspondent banking vs stablecoin liquidity: why pre-funding traps your capital

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.

How does correspondent banking actually move money?

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:

  1. Originating bank. The company's bank debits its account and sends a SWIFT payment message.
  2. USD correspondent. If the originating bank has no direct relationship with the destination bank, a large correspondent bank, often in New York, moves the dollars between the two on its books.
  3. Local correspondent. A bank in Colombia with a relationship to that correspondent receives the dollars and converts them to pesos, from its own balances or the local FX market.
  4. Beneficiary bank. The supplier's bank credits the pesos, after its own compliance screening.

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.

Why does each hop add cost and delay?

Because each bank in the chain is a separate business with its own fees, screening, and hours.

  • Fees. Intermediaries can deduct a fee from the principal as the payment passes through. The SWIFT charge code on the payment (OUR, SHA, or BEN) decides who pays those fees, and with SHA or BEN the recipient often gets less than was sent.
  • Screening. Each bank runs its own sanctions and AML checks. A question at any hop pauses the payment until someone answers it.
  • Cut-offs and time zones. Miss a correspondent's daily cut-off and the payment waits a business day. International SWIFT payouts at BlindPay, for example, have a 10:30 AM ET cut-off and can take up to five business days. Weekends and local holidays stack on top.
  • Fewer routes. The BIS Committee on Payments and Market Infrastructures reported that active correspondent banks worldwide fell about 22 percent between 2011 and 2019, with Latin America showing the steepest regional decline. Fewer correspondents means longer chains or no route at all.

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.

What is trapped capital, and why does treasury care?

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:

  • Opportunity cost. Cash in a foreign operating account earns little. The same cash in short-term government bills, or in the business, earns more.
  • FX exposure. Every foreign balance is an open currency position. A 3 percent move against you on a large peso balance is a real loss, even if no payment went wrong.
  • Counterparty exposure. A balance at a local bank is exposed to that bank, for as long as it sits there.
  • Operational load. One bank relationship, one KYC file, one set of statements to reconcile, and one refill schedule per country.

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.

How does stablecoin settlement remove country-by-country pre-funding?

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.

What does trapped capital cost? A five-country example

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.

MarketLocal railMonthly payout volume (USD)Pre-funded balance, correspondent model (USD)Destination-currency balance, stablecoin model (USD)
BrazilPix800,000400,0000
MexicoSPEI500,000250,0000
ColombiaACH Colombia300,000150,0000
ArgentinaTransfers 3.0200,000100,0000
EurozoneSEPA200,000100,0000
Total2,000,0001,000,0000

What that million dollars costs, with the assumptions stated:

Cost line (illustrative)Correspondent modelStablecoin model
Idle capital1,000,000 USD at all timesNone beyond the payouts in flight
Yield given up at 4% a yearAbout 40,000 USD a yearNone; dollars stay in treasury until payout day
Loss on a 3% adverse FX moveAbout 30,000 USD across five currenciesLimited to the minutes between quote and settlement
Local bank relationships50 (one integration)
Refill wiresAbout 5 a week, one per market0
Double the volumeBalances double to 2,000,000 USDStill 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.

What should you ask a liquidity partner before switching?

Ask these in writing. The answers expose the real funding and liquidity model fast.

  • Does a payout draw from a balance I topped up in advance? If yes, it is pre-funded, whatever the website says.
  • Are FX quotes live and binding? Ask for the quote id, the expiry, and what happens if you submit late.
  • Which local rails does it settle to, directly? Named rails, such as Pix, SPEI, ACH, RTP, SEPA, and SWIFT, with a settlement window for each.
  • Is the model custodial or non-custodial? Who holds the funds between your treasury and the recipient's bank, and for how long?
  • Where do funds go when a payout can't settle? And how fast do they come back?
  • Is there a minimum balance or a volume floor? Per currency, per rail, or across the account.
  • Who runs KYC, KYB, and sanctions screening? And does it happen once at onboarding or on every payment?

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 does correspondent banking still make sense?

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.

What to do next

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.

FAQ