---
title: "What does \"no pre-funding\" mean in a stablecoin API?"
seoTitle: "What does no pre-funding mean in a stablecoin API?"
description: "No pre-funding means each payout is funded when you send it, not from a balance parked in advance. The three funding models, the math, and what to ask."
date: "2026-08-21"
category: "payments"
author: "BlindPay Team"
faq:
  - q: "What does no pre-funding mean for cross-border payments?"
    a: "It means you fund each payout at the moment you send it, instead of keeping a balance in advance, either in a bank account in each destination country or in a balance held with your payment provider. With a stablecoin API, value moves on-chain at payout time and converts to local currency at a quoted rate, so there is no local balance to draw from."
  - q: "Does BlindPay require pre-funding?"
    a: "No. Each BlindPay payout is funded when you create it, from a stablecoin wallet you control, a BlindPay-managed wallet, or a virtual USD account that converts ACH, wire, or SWIFT deposits into USDC or USDT. There is no minimum balance to maintain in any destination currency."
  - q: "Why do traditional cross-border providers require pre-funding?"
    a: "Because fast local payouts over bank rails need money already sitting in the destination country. The provider, or you, keeps local currency in a local bank account and pays out from it, then refills it with slower international wires. That float is the price of speed on traditional rails."
  - q: "How much working capital does no pre-funding free up?"
    a: "It depends on volume and how long top-ups take. A company paying 900,000 USD every two weeks across three countries typically keeps 1.5 payout cycles in local balances, about 1.35 million USD. Funding each payout at send time frees that capital and cuts FX exposure from weeks to the length of a transfer."
  - q: "Is there any downside to funding payouts at send time?"
    a: "You need the funds available when you send, and you need to create the payout before the quote expires, which is five minutes by default. With a self-custodied EVM wallet there is also an on-chain approval step. Managed wallets skip that step."
---

No pre-funding means each payout is funded at the moment you send it, instead of from a balance you parked in advance. You don't keep reais in a Brazilian bank account to pay Brazilian contractors, and you don't top up a balance with your provider a week before payroll. With a stablecoin API, value moves on-chain at payout time, converts to local currency at a quoted rate, and lands over the local rail. The money leaves your treasury when the payment happens. Not before.

It sounds like a small operational detail. It isn't. Trapped capital is a CFO problem, not a crypto problem, and it's the difference between money that works and money that waits.

## Why did cross-border payouts ever need pre-funding?

Because fast local payouts over bank rails need money that's already local.

If you want a contractor in Mexico paid over SPEI today, someone needs pesos in a Mexican bank account today. An international wire to get those pesos there takes 1 to 5 business days. So either you, or your provider, keeps a pile of pesos in Mexico and refills it with slower wires.

That pile is pre-funding. Banks have run it for decades through nostro and vostro accounts, balances one bank keeps at another in each currency it settles. It's the price of speed on traditional rails. Multiply it by every country you pay into.

## What are the three funding models?

Every payout provider uses one of these. Ask which one before you sign.

| Model | How it works | Capital tied up | FX exposure |
| --- | --- | --- | --- |
| Pre-funded local accounts | You hold a bank account and a balance in each destination currency, and pay out from it | One to two payout cycles per country | Weeks, on every foreign balance |
| Pre-funded provider balance | You top up a balance with your provider in advance; it pays from its own local liquidity | At least one payout cycle, plus top-up lead time | Low to medium, depending on the balance currency |
| Funded at send time | You fund each payout when you create it, from a wallet or a virtual USD account | None beyond the payout itself | Minutes, the length of the transfer |

The middle model is the sneaky one. It gets marketed as "no pre-funding" because you don't hold foreign bank accounts. But if the payout draws from a balance you had to top up days earlier, you're still pre-funding. You just moved the float to the provider.

## How does funding at send time actually work?

At BlindPay, a payout is funded from one of three sources, and none of them is a pre-loaded balance in the destination currency.

**1. A stablecoin wallet you control.** You hold USDC or USDT in your own wallet on a supported network. You request a quote, approve the exact quoted amount on-chain, and create the payout. BlindPay pulls only that amount, only at that moment.

**2. A managed wallet.** BlindPay generates the address and holds the keys, so there's no on-chain approval step. You still decide when funds go in and when each payout goes out.

**3. A virtual USD account.** A [virtual USD account](/virtual-accounts) is a US account number in your customer's name. Send dollars to it by ACH, wire, or SWIFT, and each deposit converts to USDC or USDT in the linked wallet. From there, the payout flow is the same.

In all three, the sequence is:

1. Request a quote. The rate, fees, and exact receive amount are locked for five minutes.
2. Fund the payout with the quoted stablecoin amount.
3. Stablecoins move on-chain in seconds.
4. Local currency lands over Pix, SPEI, ACH, SEPA, or another rail.

Nothing sits in Brazil. Nothing sits in Mexico. No destination-currency balance waits for payroll day.

## What's the working-capital math?

An illustrative example. A staffing company pays contractors every two weeks, about 900,000 USD per cycle:

- Brazil: 450,000 USD
- Mexico: 270,000 USD
- Colombia: 180,000 USD

**With pre-funded local accounts.** Top-up wires take up to five business days, so the finance team keeps about 1.5 cycles in each country to be safe. That's roughly 1,350,000 USD sitting in three foreign bank accounts at all times. If that cash could earn 4% in short-term Treasury bills, the company gives up about 54,000 USD a year in yield. And it holds 1.35 million dollars' worth of reais and pesos, so a 3% adverse move in those currencies is a 40,500 USD swing it didn't plan for.

**With a pre-funded provider balance.** Better. No foreign bank accounts. But the balance still has to hold at least one cycle, plus the top-up lead time, so 900,000 USD or more sits idle with the provider.

**Funded at send time.** The treasury keeps its dollars until payout day. On payout day it funds exactly 900,000 USD worth of payouts, each at a quoted rate. Idle capital: zero. FX exposure: minutes.

Now add a fourth country. With pre-funded accounts, that's a new bank relationship, a new buffer, and a new currency position. Funded at send time, it's a new `type` on a bank account. The expansion stops being a treasury project.

## What are the trade-offs?

Being honest about it. Funding at send time has three constraints:

- **You need the funds on hand when you send.** Stablecoins in the wallet, or a USD deposit that has already landed in the virtual account. USD deposits by ACH or wire can take up to five business days to arrive, so plan the deposit, not the balance. Rail-by-rail timing is in [how long a stablecoin payout takes](/resources/more/stablecoin-payout-settlement-times).
- **Quotes expire.** A payout quote is valid for five minutes by default. Create the payout inside the window, or request a new quote.
- **Self-custodied EVM wallets need an approval.** You approve the quoted amount on-chain before creating the payout. Managed wallets skip this.

None of these ask you to park capital. They ask you to be ready at the moment of payment, which is what treasury wants anyway.

## What should you ask a provider about pre-funding?

Five questions that expose the funding model fast:

1. **Does a payout draw from a balance I topped up in advance?** If yes, it's pre-funded, whatever the website says.
2. **Is there a minimum balance, per currency or overall?**
3. **Who holds the destination-currency liquidity, and when is it sourced?**
4. **Is the FX quote binding, and for how long?**
5. **If a payout fails, where do the funds go, and how fast?** At BlindPay, stablecoin refunds return to the originating wallet right away.

Get the answers in writing. For the rest of the evaluation, read [how to choose a stablecoin API](/resources/more/how-to-choose-a-stablecoin-api), and for how stablecoins sit inside a multi-rail strategy, read [stablecoins in payment orchestration](/resources/more/stablecoin-payment-orchestration-cross-border-payouts).

## Where does BlindPay fit?

[BlindPay](/global-payments) is a stablecoin API built on the funded-at-send-time model. Each payout is funded when you create it, from your own wallet, a managed wallet, or a virtual USD account. Payouts land in local currency over Pix, PIX Safe, and TED in Brazil, SPEI in Mexico, ACH in Colombia, Transfers 3.0 in Argentina, ACH, RTP, and wire in the US, SEPA in Europe, and SWIFT (POBO/COBO) to 100+ countries.

KYC, KYB, and sanctions screening run inside the API before money moves. Official SDKs cover Node, Python, Go, PHP, and Swift, and [pricing is published](/pricing).

## What to do next

Pull last quarter's payout volume by country and add up the balances you kept in each one. That number is your pre-funding cost. Then run one test payout on a development instance with the [payout quickstart](/docs/quickstart-payout) and see what funding at send time looks like in practice.

*This article is for general information only and is not legal, tax, or financial advice.*