A nostro account is a bank's account at a foreign bank, in that bank's currency. A vostro is the same account seen from the other side. Why both trap cash.
A nostro account is a bank's account at a foreign bank, held in that bank's local currency, used to make and receive payments there. A vostro account is the same account seen from the foreign bank's side. Cross-border payments run through these accounts, and each one needs a balance before the first payment goes out. BlindPay replaces that balance with stablecoin settlement funded at send time.
Key takeaways
A nostro account is an account one bank holds at another bank in a foreign country, denominated in that country's currency. The word is Italian for "ours": from the account holder's view, it is "our money, held with you."
Example: a US bank opens an account in reais at a bank in São Paulo. The US bank can now pay reais to anyone in Brazil by instructing the São Paulo bank to debit that account. In the US bank's books, that is its BRL nostro.
The Committee on Payments and Market Infrastructures (CPMI) describes the arrangement in its correspondent banking report: one bank, the correspondent, "holds deposits owned by other banks (respondents) and provides payment and other services" to them. Reciprocal relationships, the report notes, "may involve the use of so-called nostro and vostro accounts to settle foreign exchange transactions."
A vostro account is the same account, described by the bank that holds it. "Vostro" is Italian for "yours." The São Paulo bank in the example calls the US bank's reais balance a vostro account: "your money, held with us."
A loro account ("theirs") is how a bank refers to an account that a third bank holds somewhere else. If a German bank mentions the US bank's account in São Paulo, it is speaking about a loro account. Usage varies, though. The ECB's glossary and the CPMI report both use "loro" for the other side of a nostro, the account as the holding bank sees it, which is the same thing as a vostro.
| Nostro | Vostro | Loro | |
|---|---|---|---|
| Meaning | "Ours, with you" | "Yours, with us" | "Theirs, with them" |
| Whose view | The bank that owns the money | The bank that holds the money | A third bank talking about the other two |
| Currency | The foreign bank's local currency | The holding bank's own currency | Either |
| Where the real ledger lives | At the foreign bank | In the holding bank's own books | At the holding bank |
| What the owner keeps at home | A mirror account to track the balance | Nothing extra: it is a liability on its books | Nothing |
One account, three names. Which one you use depends on who is talking.
A cross-border payment is a series of debits and credits on accounts that banks hold with each other, with a SWIFT message telling each bank what to do. The CPMI report illustrates the basic case, where bank A pays a customer of bank C through bank B because A and C have no account with each other.
Here's the flow for a US company paying a supplier in Brazil in reais:
When there's no direct relationship, more banks join the chain, each with its own nostro and vostro accounts and its own fee. The CPMI report describes two ways to route this: the serial method, where the MT103 passes through every bank in the chain, and the cover method, where the MT103 goes straight to the beneficiary's bank and the funds follow separately through the correspondents. Each hop can deduct a fee, which is where the OUR, SHA, and BEN charge codes come from. Hidden fees in international wires explains how to read them.
Because the correspondent pays out of the balance in the account. To pay reais in Brazil, there must already be reais in the nostro, or a credit line from the correspondent covering the overdraft.
Three things set how big that balance has to be:
The result is a balance that sits in a foreign currency, earns little, and moves with the exchange rate. Multiply it by every currency a bank pays in. Correspondent banking vs stablecoin liquidity puts numbers on that across five markets.
A simple rule of thumb: required balance equals average daily outflow times the number of days it takes to refill, plus a margin for spikes. This illustrative example uses round numbers for a single corridor.
A payroll platform pays Mexican contractors. Assumptions:
| Line | Calculation | Balance (USD equivalent) |
|---|---|---|
| Cover outflows during the refill | $150,000 × 3 days | $450,000 |
| Safety margin | $150,000 × 2 days | $300,000 |
| Minimum nostro balance | $750,000 | |
| Cost at an assumed 4% a year | $750,000 × 4% | About $30,000 a year |
| Loss on an assumed 5% peso move | $750,000 × 5% | About $37,500, once |
Two features of this math matter more than the totals. The balance scales with volume: double the payroll, double the nostro. And the refill lead time drives everything: cut it from three days to zero, and the main term goes away.
By matching two ledgers that should agree and often don't. The account owner keeps a mirror account, which the CPMI describes as a record "kept for accounting purposes," and compares it against statements from the correspondent.
Those statements traditionally arrive as SWIFT MT950 messages, and increasingly as ISO 20022 camt.053 files. Every entry gets matched to an expected payment or refill. The leftovers are the problem: fees deducted by an intermediary, credits that arrived a day late, or payments that bounced. Each one becomes an investigation, and each investigation is a person's time.
The more nostro accounts a business runs, the more of this it does.
Because banks have been cutting them. The CPMI's quantitative review found the number of active correspondent banks worldwide fell 22% between 2011 and 2019, and the number of active corridors fell roughly 12% over the same period.
The 2016 CPMI report links the retreat to the cost of AML and counter-terrorist-financing compliance and a higher perception of risk. For smaller banks and fintechs in emerging markets, that means fewer correspondents willing to hold their nostro accounts, longer chains for the ones that remain, and more fees along the way. Why cross-border payments are slow shows what each extra hop does to timing.
Four ways, and only one removes the foreign balance from the system rather than moving it to someone else.
| Approach | Who holds the foreign balance | What you pre-fund | Typical speed to the recipient |
|---|---|---|---|
| BlindPay: stablecoin settlement plus local rails, funded at send time | Nobody holds a balance for you; local currency comes from a liquidity provider at payout | Nothing beyond the payout in flight | Minutes on Pix, SPEI, and Transfers 3.0; 1 to 2 business days on ACH, SEPA, and ACH Colombia |
| Your bank's correspondent network | Your bank, in its nostro accounts | Nothing directly, but you pay for it in fees and FX spread | Typically 1 to 5 business days |
| Your own foreign bank accounts | You | A balance in every currency you pay in | Same day, once the balance is there |
| Provider with a pre-funded balance | You, at the provider | A top-up before each payout cycle | Depends on the provider |
The last row is the trap to watch for. A provider can remove your foreign bank accounts and still ask you to keep a balance with it. What "no pre-funding" means in a stablecoin API sorts the funding models, and what a liquidity market is explains why pooled local currency is cheaper than a balance per company.
BlindPay settles the cross-border leg in a stablecoin such as USDC or USDT and pays the recipient over the local rail, so no balance has to sit in the destination currency ahead of time. What is real-time cross-border settlement covers the full model. You fund each payout when you create it.
The flow, from the payouts docs:
Where do the dollars come from? Either a stablecoin wallet you already hold, or a US virtual account that turns incoming ACH, wire, or SWIFT deposits into USDC or USDT. Either way, the balance you keep is in one currency, in one place. Funding from your own wallet stays non-custodial; managed wallets, a beta product, are BlindPay-custodied.
For collections, POBO vs COBO covers how a platform receives international wires in its customer's name without opening a foreign account for each one.
Size the nostro balance for your largest corridor with the formula above, then compare it to funding at send time. Run a test payout on a free development instance with the payout quickstart to see the quote, fund, and settle steps end to end.
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.
A 10-point checklist and a side-by-side of BlindPay, Wise Platform, Airwallex, Thunes, Bridge, and Circle for real-time, low-fee cross-border settlement.