Just-in-time vs prefunded stablecoin cards for users and program operators: when conversion happens, top-up fees, float, declines, and tax timing compared.
A just-in-time stablecoin card keeps the money in stablecoins until the moment of purchase and converts only the authorized amount. A prefunded card converts stablecoins into a fiat card balance first, then spends that balance later. Just-in-time avoids load fees and idle balances. Prefunded gives predictable fiat spending but ties up money ahead of time.
Neither model is better in general. The right one depends on who you are: a cardholder deciding where to keep money, or a program operator deciding where to hold float. This guide compares both from each side. For the basics of how a card spends a stablecoin balance, start with what a stablecoin-backed card is.
Key takeaways
They describe when the stablecoin becomes fiat. Just-in-time converts during the purchase. Prefunded converts before it.
Just-in-time funding: the stablecoin stays in the cardholder's wallet or custodial account. When a merchant requests authorization, the issuer processor checks the balance, converts the purchase amount at the current rate, places a hold, and approves or declines in seconds.
Prefunded (top-up) funding: the cardholder loads stablecoins into the card program. The program converts them into a fiat balance at load time. Card purchases then draw down that fiat balance like a prepaid card.
Float: money sitting in a balance waiting to be spent or settled. In a prefunded program, float is the sum of all unspent card balances. In a just-in-time program, float is mostly the pool the program needs to settle with the card network.
The difference looks small on a checkout screen. It changes fees, declines, tax records, and how much capital the operator has to hold. The step-by-step guide to how stablecoin card transactions settle walks through authorization, clearing, and settlement in detail.
The two models trade convenience for predictability. Just-in-time is more flexible and keeps money in stablecoins longer. Prefunded is more predictable at checkout and simpler to account for in fiat.
| Factor | Just-in-time | Prefunded (top-up) |
|---|---|---|
| When conversion happens | At each authorization | At each load |
| Where money sits before spending | Stablecoin wallet or account | Fiat card balance |
| Top-up fees | Usually none, since there is no load step | Often 1% to 2% per load above a free allowance (NGIBANK, March 2026) |
| Conversion cost | Spread applied per purchase | Spread applied once per load |
| Rate exposure | Between authorization and settlement, usually carried by the program | Fixed at load; cardholder carries none afterward |
| Declines from balance | When the wallet drops below the hold amount | When the fiat card balance runs out |
| Idle balance | None on the card side | Unspent loads sit as fiat float |
| Tax event timing (where spending is a disposal) | At each purchase | At each load |
| Best for | Users who want to keep money in stablecoins until they spend | Users and teams who want a fixed fiat budget |
The fee row is where most comparisons go wrong. A card with no load fee can still cost more per purchase if the conversion spread is wide. Stablecoin FX slippage and live quotes explains how a quoted rate turns into the rate you actually get.
At checkout, the program converts only what the merchant asks for. The rest of the balance stays in stablecoins.
The gap between steps 3 and 6 is where rate exposure lives. With dollar stablecoins spent in dollars, that exposure is close to zero. With dollar stablecoins spent in euros or pesos, the program either absorbs the move or prices it into the spread.
A prefunded card front-loads the conversion. The cardholder decides how much to load, and checkout becomes a normal prepaid transaction.
The cardholder sends stablecoins to the program, the program converts them, and the card shows a fiat balance. From then on, the card behaves like any prepaid debit card. A purchase never touches the stablecoin wallet.
That predictability has a cost. NGIBANK's March 2026 guide notes that prefunded cards often charge 1% to 2% per load above a free monthly allowance. Money loaded and not spent also stays in fiat, outside the stablecoin wallet, until the cardholder withdraws it or spends it.
Choose just-in-time if you want money to stay in stablecoins until you spend it. Choose prefunded if you want a fixed fiat budget and are fine paying to load it.
A simple test:
The comparison of stablecoin cards, crypto debit cards, prepaid, and credit puts these models next to the other card types.
For an operator, the funding model decides where capital sits. Prefunded programs hold customer float in fiat. Just-in-time programs need a settlement pool to pay the network while stablecoins are converted.
Prefunded programs collect and convert money before anyone spends it. The operator holds the fiat float, reconciles loads against card balances, and handles refunds of unspent money. Revenue can include load fees, but the operator also carries the operational weight of balances that may sit for weeks.
Just-in-time programs convert on demand. Settlement with the network usually happens the next business day. In the traditional model, the program converts stablecoins to fiat and settles with the network over banking rails. In the emerging model, issuers settle with Visa directly in stablecoins. Visa launched USDC settlement in the United States in December 2025, with broader availability planned through 2026. Either way, the operator still has to pre-position money for settlement, which is its own working capital question.
Card programs are growing fast enough that this matters. Visa reported that stablecoin-linked cards processed about $5.2 billion in 2025, up 319% year over year, across more than 130 programs in more than 50 countries, per its March 2026 stablecoin card report.
Pre-funding hurts most on the payout leg. Card spending is only one way money leaves a stablecoin program. Rent, payroll, supplier invoices, and cash-outs to a bank account usually need a local transfer, not a card.
Traditional cross-border payouts ask the sender to park money in destination-country accounts first. That is the same problem as a prefunded card, at a larger scale: capital sits idle in many places to cover payments that have not happened yet. Correspondent banking vs stablecoin liquidity explains why that capital gets trapped, and what "no pre-funding" means in a stablecoin API shows the alternative.
BlindPay covers the money movement around a card program. A card issuer handles cards. BlindPay handles funding in and paying out.
On the payout side, BlindPay converts USDC or USDT into local currency over Pix, SPEI, ACH, RTP, SEPA, and SWIFT (POBO/COBO), with no pre-funding. A live quote locks the rate and fees before the stablecoins move, and the stablecoins leave the sender's wallet only for the payout that was authorized. That keeps capital in stablecoins until a payment actually happens, the same idea as just-in-time funding on a card.
On the funding side, US virtual accounts give each customer an account number that receives ACH, wire, or SWIFT and converts each deposit into USDC or USDT in the linked wallet. A card program can use that as the bank-transfer entry point for loading balances.
If your program also needs local payouts or bank-transfer funding, test both on a free BlindPay development instance with the payout quickstart. For the full picture of how card issuing works, read what stablecoin card issuing is.
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.