Corporate cards funded by stablecoins: authorisation, holds and settlement explained

A corporate card funded from a stablecoin treasury connects two payment systems. Your company may hold USDC or USDT, but the merchant expects payment through conventional card acquiring and settlement rails. When an employee taps the card, stablecoins do not normally move directly to that merchant. The card programme checks a spending ledger, approves or declines the request, and later settles the cleared transaction through the card network.

This separation matters because a stablecoin treasury balance, an available card balance, an authorisation hold and a posted expense are not interchangeable. Each represents a different stage, with different implications for liquidity, accounting and reconciliation.

The transaction flow at a glance

Timings and mechanics vary by programme, merchant type, currency and transaction method. A finance team should confirm supported chains, funding cutoffs, settlement currencies and fee schedules before relying on cards for time-sensitive spending.

Step 1: Stablecoins become card spending capacity

A stablecoin-funded corporate card begins with treasury assets such as USDC or USDT. The programme then makes value available for virtual or physical card spending. Two balances must remain distinct:

• Treasury balance: the company’s holdings of stablecoins, fiat or other supported currencies.
• Available card balance: the amount against which new card authorisations can be approved.

Some programmes require stablecoins to be converted into the card’s settlement currency before they become spendable. Others allocate funding to an internal card ledger and perform conversion through their treasury process. The legal ownership, accounting presentation and timing of conversion can differ, so finance should obtain the programme’s exact funds flow rather than infer it from the user interface.

This setup does not mean a blockchain transaction occurs for every meal, hotel or software purchase. Card authorisation must return quickly, so the decision is generally made against an existing card ledger rather than waiting for an on-chain transaction to confirm.

For a company using a self-custodial or MPC-controlled treasury, signing quorum can protect the movement that funds the card balance. It does not normally apply to each employee purchase. Requiring treasury signers to approve every point-of-sale authorisation would be incompatible with ordinary card use.

Questions to resolve about funding

• Which stablecoin and blockchain combinations can fund the programme?
• Does conversion occur before allocation, when cards are funded or under another process?
• What rate source, spread and transaction fees apply?
• When does an on-chain deposit become available for card authorisation?
• Can unused card funds be returned to fiat or stablecoins, and through which route?

Step 2: Authorisation creates a hold

At checkout, the merchant sends an authorisation request containing information such as the card credentials, merchant identity, merchant category code, transaction currency and requested amount. The programme evaluates that request against its own and the network’s rules.

Common checks include the company’s available balance, the card’s per-transaction or period limit, merchant category restrictions, geographic or channel controls, and whether the card is active, frozen or cancelled. A successful response reserves capacity for the merchant. A failed check can result in a decline.

The authorised amount is only an estimate. If a card balance has 20,000 units of available capacity and a hotel requests a 1,200-unit authorisation, available capacity may fall to 18,800 even though the hotel has not submitted its final bill. Finance should not assume that the hold is a settled expense.

Why holds can exceed the expected purchase

• Hotels: the initial request may include room charges and an incidentals buffer.
• Car rental: the merchant may reserve an amount above the quoted rental price.
• Fuel stations: an automated pump can request a fixed amount before the final fuel total is known.
• Restaurants: the merchant may adjust the authorised amount when a tip is added.
• Subscriptions: a merchant may submit verification, renewal or retry authorisations separately.

Merchants can also submit incremental authorisations, reversals or delayed clearing records. If a 1,200 hotel hold clears at 1,050, the unused 150 should return to available capacity after the relevant adjustment is processed. If the merchant never completes the transaction, the hold should eventually be reversed or expire under programme and network rules. There is no universal expiry period for every merchant and transaction type.

Step 3: Clearing establishes the posted amount

After the purchase, the merchant submits transaction data for clearing. This may occur later the same day, while one to three days is common for ordinary purchases. Delayed, offline or travel-related transactions can take longer.

Clearing replaces the estimated hold with the final posted amount. Differences can result from tips, partial fulfilment, incremental charges, currency movements or merchant adjustments. The programme then settles its obligations through the card ecosystem, and the merchant receives funds through its acquiring provider.

The statement or transaction export should identify the merchant, cardholder, transaction date, posting date, original currency, settlement currency and final amount. Where applicable, finance should also capture conversion rates and separately disclosed fees.

How foreign-currency card spending works

A dollar-denominated stablecoin does not eliminate card foreign exchange. Suppose a card settles in USD and an employee pays EUR 500. The merchant requests authorisation in euros, while the programme may reserve an estimated dollar amount. At clearing, the relevant network or programme conversion rules determine the final posted USD amount. That amount can differ from the hold.

Finance teams should distinguish three possible conversions:

1. Stablecoin conversion: USDC or USDT is converted into the balance used to fund cards.
2. Card FX conversion: the merchant currency is converted into the card’s settlement currency.
3. Merchant currency conversion: the merchant offers to charge the card in its home currency, commonly called dynamic currency conversion.

Each conversion can use a different rate and fee mechanism. Review pricing for the actual stablecoin, chain, settlement currency and card corridor rather than assuming a USD reference value makes international spending exchange-rate neutral.

Accounting and reconciliation

A stablecoin card can create at least two economic events: funding or converting treasury assets, and incurring the card expense. An authorisation hold sits between them but generally represents reserved capacity rather than a completed purchase.

The exact entries depend on whether the programme operates a prefunded balance, an amount payable or another structure, as well as the company’s accounting framework. Operationally, the reconciliation should preserve links among the treasury transfer, conversion record, card authorisation, posted transaction, receipt and accounting entry.

Refunds require the same discipline. A merchant refund is normally a separate posted event rather than deletion of the original expense. Disputes and chargebacks can also pass through provisional and final stages, so finance should not close the case solely because a temporary credit appears.

Controls that matter

Card controls should reflect the purpose of the expense. Useful measures include individual limits, transaction limits, merchant category restrictions, dedicated virtual cards for recurring vendors and prompt card freezing when an employee leaves or credentials are exposed.

Treasury controls remain separate from cardholder controls. For example, Stablerail combines a USDC and USDT business account with approvals and signing quorum for treasury movements, sanctions and address screening before send, corporate cards, payouts, fiat off-ramp and exportable audit evidence. Card limits govern employee spending; treasury approvals govern how value reaches or leaves the card funding environment.

Finance team implementation checklist

1. Document the complete funds flow from stablecoin wallet to available card balance and merchant settlement.
2. Confirm supported stablecoins, chains, base currencies, funding cutoffs and conversion mechanics.
3. Set cardholder, transaction and merchant-category limits based on purchasing purpose.
4. Define how authorisations, expired holds, reversals, refunds and disputes appear in exports.
5. Reconcile final posted amounts rather than booking expenses from pending authorisations.
6. Retain receipts, approvals, conversion records, card changes and transaction exports as audit evidence.
7. Test the process with a low-value purchase, refund and foreign-currency transaction before wider rollout.

The core principle is straightforward: treasury funding, authorisation holds and settled card expenses are distinct stages. A reliable card programme should make those stages visible, while the finance team’s procedures should prevent pending holds from being mistaken for final expenses or stablecoin funding from being confused with merchant settlement.