How card programs earn yield on customer float

Every card program sits on a balance it doesn't own yet, and on stablecoin rails that balance can earn right up to the moment it settles.

A card program earns yield on float by splitting customer balances into two parts. A liquid tranche funds daily settlement, and a deployable tranche goes into a yield-bearing position, with the liquid tranche sized to cover peak draw. When the balance is held as a stablecoin, the deployable portion can sit in an onchain vault, earn continuously and still be exited at the moment of a transaction. Upshift's Atomic Vaults are built for this split: the deployable tranche earns in the vault, and a redemption can settle at the moment a card transaction clears.

Plenty of treasury products earn on idle balances. The engineering problem is doing it without adding a delay between a customer tapping a card and the transaction being approved. That problem is why card float has stayed in cash and Treasury bills at most issuers, while the rest of the balance sheet got more sophisticated.

Where float actually comes from in a card program

Float in a card program builds up in the gap between when a transaction is authorised and when it settles with the network. That's typically 24 to 72 hours, depending on the scheme, the merchant category and the batch cycle. During that window the issuer has committed funds to a merchant but hasn't moved them yet, and the balance sits in an operating account doing nothing. Programs that require customers to prefund a wallet or card balance hold a second and usually much larger pool. Customers top up in round numbers and spend gradually. Visa's own work on stablecoins and the future of onchain finance covers why settlement timing changes once the balance is tokenised.

These pools are large. A program with $50 million in monthly spend and a two-day settlement cycle carries roughly $3 to $4 million in settlement float at any moment. A prefunded program can easily hold two to three months of spend in customer balances. Card interchange on that same volume might run 80 to 150 basis points, and against that, a few hundred basis points on the float pool is a material addition to the unit economics. For many programs it's the difference between a negative and positive contribution margin per account. Gauntlet's Idle USDC Report puts numbers on how much stablecoin balance sits unproductive across the market, and the pattern applies directly to issuers.

Card programs hold three distinct pools, and each tolerates a different amount of illiquidity:

• Settlement float is committed and short-dated. It has a known outflow date, which makes it the easiest to model and the least tolerant of redemption delay.
• Customer prefunded balances are unpredictable per account but statistically stable in aggregate. Withdrawal behaviour follows patterns that hold up well across a large enough book.
• Program reserves and collateral posted to the network or the sponsor bank are locked, and in most jurisdictions carry restrictions on what they can be held in.

How do payments companies earn yield on settlement, remittance and payroll float?

Payments companies earn on float by holding the balances that sit between collection and payout in a vault. A liquid buffer inside the vault is sized to the next payout date. Settlement, remittance and payroll float each run on a known outflow schedule, and that schedule sets how much of each balance can be deployed and for how long.

Settlement float

A payment service provider or acquirer holds merchant funds between capture and payout, usually for one or two business days. Many also hold rolling reserves against chargebacks for longer. The payout schedule is published to merchants, which makes this pool the easiest to model. Reserves can be deployed further out, within whatever the acquiring bank's agreement allows.

Remittance float

Remittance companies pre-fund payout partners in destination markets and carry balances in transit between corridors. Held in stablecoins, that pre-funding earns until the moment a payout is released. A corridor that settles onchain can release it on a weekend, too. The buffer is sized per corridor, because peak days differ by market.

Payroll float

Payroll providers collect client funds a few days before pay date and hold them until the payout runs. The amount and the outflow date are known in advance, making payroll float the most predictable of the three. Client funds are often held under trust or safeguarding rules that limit where they can sit. Those rules need a read from counsel before any of the balance is deployed.

How does a card program earn yield on float without slowing approvals?

An approval needs funds available at the instant of authorisation, and any yield structure has to guarantee that. The workable pattern holds a buffer in immediately spendable form. It's sized against the worst observed draw over a rolling window, rather than the average, and the remainder goes into a position that can be unwound atomically when the buffer is drawn down. Authorisation checks against the buffer, which keeps the yield-bearing position out of the transaction path.

A common split is 20 to 30 percent operational float held liquid, 50 to 60 percent deployed into yield, and 10 to 20 percent held as a regulatory reserve in cash or Treasury bills. The spend profile sets the real numbers. A program with lumpy corporate spend needs a much fatter buffer than a consumer program with thousands of small daily transactions, where the law of large numbers does more of the work.

Two failure modes show up again and again. The first is sizing the buffer against average daily draw instead of peak. It works until a payroll cycle or a marketing push moves spend three standard deviations and the program has to unwind a position under pressure. The second is treating a yield position with a redemption queue as though it were cash, until the day the queue matters and the program discovers it's short.

What "atomic redemption" means for card settlement

Atomic redemption describes a structure where the yield-bearing position and the spendable balance settle in the same transaction. A customer's tap draws directly against the position, with no separate withdrawal step. The vault holds a liquidity buffer sized to expected draw, and serves a redemption from that buffer immediately, without waiting for a strategy to unwind. To the customer the balance was always spendable, and to the program it was always earning.

Upshift is non-custodial vault infrastructure for stablecoin yield, used by fintechs, exchanges, wallets, neobanks, chains and asset managers to launch custom yield products. The atomic redemption vault is the vault type built for this problem. Under the Vault-as-a-Service model a program launches its own vault, configured to its own risk parameters. Its buffer size and whitelisted strategies can then follow that program's spend profile.

Credit sits behind the buffer as a second line. Upshift's prime stack serves over $7 billion in monthly transaction volume and can structure a credit facility against a vault (figures as of July 2026). A program that draws past its buffer can lean on that facility while the underlying position unwinds, and an unusual spend day doesn't force a fire sale.

How can card spend run 24/7 when the assets behind it trade 24/5?

Card spend runs 24/7 against a 24/5 asset because the vault keeps a stablecoin buffer that pays each card payment instantly. The vault redeems the exact spend amount at the point of sale. The tokenised Treasury or money market position behind the buffer rebalances on the next business day. The cardholder sees a balance that's always spendable.

Tokenised Treasury funds and money market funds subscribe and redeem with the issuer on business days, while card spend peaks on Saturdays and Sundays. Upshift's Atomic Vaults redeem vault shares and pay the merchant in the same transaction, drawing on the instant redemption buffer. The payment either completes in full or doesn't happen at all.

A weekend of unusual spend can draw the buffer down faster than the fund side can refill it. Upshift Clear can exit tokenised positions for USDC in one transaction at an oracle price. A credit facility can also be structured against the vault while the position unwinds. The three places payments float usually sits compare like this:

The payments use case covers the flow-of-funds review, buffer sizing and integration for card, settlement and payout balances.

Comparing the ways to hold card float

These are the realistic options for a program choosing where float sits. Yields move constantly and none of these are fixed. The figures are typical ranges observed through mid-2026, and none of them is an offer or a promise. The onchain rows all settle against the EIP-4626 tokenised vault standard, which makes a receipt token transferable and composable across interfaces.

Weekends catch card programs out. Card spend rises on Saturdays and Sundays, while money market funds and most tokenised Treasury products settle on a business-day calendar. A program holding float in either structure runs its highest draw against its least available liquidity. Onchain positions settle continuously, which lines up available funds with the shape of the spend. Lending rates float with borrow utilisation, and both Morpho and Aave publish live market data to check before modelling a number into a business case.

Stablecoin balances are becoming a normal part of how payments companies hold money, a shift Bessemer traces in its work on stablecoins moving from DeFi primitive to financial infrastructure. Card programs sit early in that transition. Their float is already short-dated and already in something a vault can hold.

What does a program need before it can deploy float?

A program missing any of these four will stall partway through an integration, and settling them before scoping saves a cycle.

1. A flow-of-funds map. Where each pool sits today, which entity holds it, what the peak draw has been over the last 12 months, and which balances carry restrictions from the sponsor bank or the network.
2. A custody decision. Whoever holds the vault's receipt token has to be able to hold it, and that means the custodian needs to whitelist the vault. This step is most often discovered late, and it puts the custodian on the deal map as a counterparty in its own right.
3. A regulatory read on customer yield. Passing yield to customers as a savings rate or cashback gets different treatment across jurisdictions. E-money rules in particular constrain what can be done with balances held for customers. Programs that deploy customer float without disclosing the arrangement carry real exposure.
4. Risk parameters someone will actually own. Which protocols are whitelisted, what the buffer floor is, who can change it, and what happens on a drawdown. A vault with a policy engine enforcing restrictions at the chain, protocol, token and function level gives each of these a concrete, enforced answer.

What are the real risks of deploying float?

Smart contract risk is the one everyone names first, and it's the tail risk. Audit history and the concentration of exposure per protocol count for more than headline yield. Upshift's contracts have completed 11 smart contract audits across 6 independent firms, and the full audit history is published by firm and date. Non-custodial architecture narrows the blast radius further, because funds only move between the vault contract and whitelisted strategy contracts.

Liquidity risk is the more common failure in practice. A position that pays well but can't be exited on the day it's needed turns a treasury problem into an operational one. The buffer exists for that reason, and it should be sized against observed peaks. Counterparty risk applies wherever the strategy touches a lending venue or a centralised borrower. Exposure limits and transparency on where the capital sits keep it in check. Rate risk cuts both ways, since variable yields fall as well as rise, and a program modelling float income into its unit economics should model the downside case too.

Regulatory risk needs its own line for card programs, because the treatment of yield on customer balances is moving in several jurisdictions at once. A program should expect to disclose how float is deployed, what yield is generated, and how it's split between the customer and the issuer. Wharton's Stablecoin Toolkit is a neutral primer on the financial and market side, for a compliance team that wants something no vendor wrote.

Always make sure to do your own research and be aware of the above and any other risks before depositing.

Frequently asked questions

How much float does a typical card program hold?

Settlement float generally runs one to three days of spend. A program with $50 million in monthly volume carries roughly $3 to $4 million at any moment. Programs that require customers to prefund hold considerably more, often two to three months of spend, because customers top up in round amounts and spend gradually.

Can float earn yield without delaying card authorisations?

Yes, as long as authorisation checks against a liquid buffer. The buffer is sized to cover peak draw and the yield position sits outside the transaction path, which leaves approval speed unchanged. Structures that require a withdrawal step before funds become spendable will add delay.

What is atomic redemption?

Atomic redemption is a structure where the yield-bearing position and the spendable balance settle in the same transaction. A card tap draws directly against the position. Redemptions are served from a liquidity buffer held inside the vault, which means no waiting for a strategy to unwind.

Is yield on card float passed to the customer or kept by the issuer?

Both models exist. Some programs keep the full spread as revenue against interchange, and others pass a portion to customers as a savings rate or cashback to drive acquisition. The split is often a regulatory question as much as a commercial one. E-money rules in several jurisdictions constrain what can be done with balances held on behalf of customers.

What happens if spend spikes above the buffer?

A well-structured program has two lines of defence. The buffer absorbs normal variance, and a credit facility covers the gap while the underlying position unwinds. With both in place, an unusual day doesn't force an exit at a bad price. Programs without the second line should size the buffer considerably more conservatively.

Do stablecoin balances change the picture versus fiat float?

They change the settlement calendar, the constraint that bites hardest for cards. Fiat float held in money market funds settles on business days, while card spend peaks at weekends. Onchain positions settle continuously. Several stablecoin card issuers already settle with Visa and Mastercard in USDC, compared in stablecoin card issuing platforms.

Which custodian needs to be involved?

Whichever one holds the program's assets, because the vault's receipt token has to be a supported asset on their platform. Custodian whitelisting is a gating step. Raise it in the first scoping conversation.

Keep reading

• What is an onchain vault: what a vault is, who holds the assets, and how money moves in and out.
• The DeFi yield strategies onchain vaults run: the strategy shapes, the risk in each, and measured returns.
• How to use an onchain vault in a treasury product: the ETP comparison, fees, and what to decide first.
• Best crypto cards that earn real yield on your balance: the same mechanics from the cardholder's side, and how the product is marketed.
• Why every financial product will run on vaults: the structural argument for why balance-holding products converge on this pattern.
• How the GENIUS Act and CLARITY Act reshape stablecoin yield: the regulatory backdrop for anything involving yield on customer balances.
• Upshift's risk management framework: the buffer, the NAV volatility caps and the whitelisting model in technical detail.
• What are DeFi yield vaults: the ground-up explainer if vaults are new to the reader.