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

A corporate card funded from a stablecoin treasury connects two different payment systems. Your company may hold USDC or USDT, while the merchant expects to be paid through conventional card acquiring and settlement rails.

The important point is that stablecoins do not normally move to the merchant when an employee taps a card. Instead, the card programme checks an available spending balance, approves or declines the transaction, and later settles the cleared amount through the card network. Stablecoins fund that balance either through an earlier conversion into fiat or through the programme’s treasury funding process.

This guide explains the full flow for a crypto corporate card, including authorisation, holds, clearing, settlement and foreign-currency spending.

The transaction flow at a glance

Exact timings and funding mechanics vary by card programme, merchant category, transaction type and currency. Finance teams should confirm the applicable funding cutoff times, supported base currencies and fee schedule before relying on a card for time-sensitive spending.

Step 1: funding cards from a stablecoin treasury

With a stablecoin-funded corporate card, the company starts with a treasury balance such as USDC or USDT. Virtual or physical cards are then funded from that treasury balance according to the card programme’s operating model.

There are two balances to distinguish:

• Treasury balance: the company’s USDC, USDT, fiat or multi-currency holdings.
• Available card balance: the amount currently available for card authorisations.

These balances may not always be identical. A programme can require stablecoins to be converted into the card’s settlement currency before they become spendable. Another model may calculate available capacity against an allocated treasury balance and perform conversion as part of the funding process.

This does not mean a blockchain transaction occurs for every coffee, hotel or software payment. Card authorisation must happen within seconds, so it is generally checked against an existing card ledger rather than waiting for an on-chain transfer to confirm.

For a company using self-custodial MPC vaults, quorum signing can protect the treasury movement that funds the card balance. It does not normally apply to each employee card transaction. Requiring directors to sign every card authorisation would make ordinary card use impractical.

Step 2: authorisation and the available-balance check

When a cardholder pays, the merchant sends an authorisation request. It normally includes the card details, merchant identity, merchant category code, transaction currency and an amount.

The card programme checks the request against factors such as:

• the company’s available card balance;
• the individual card’s spending limit;
• merchant category code, or MCC, restrictions;
• the card’s active, frozen or cancelled status;
• applicable programme and network rules.

If approved, the response returns to the merchant and a hold is placed on the available balance. If the request breaches a limit or the balance is insufficient, it can be declined.

The authorised amount is not necessarily the final expense. It is an estimate reserved for the merchant until clearing.

How card holds work

A hold reduces what the company can spend but is not yet a completed transaction. For example, if the available card balance is $20,000 and a hotel obtains a $1,200 authorisation, the available balance may fall to $18,800 even though the hotel has not submitted its final bill.

Holds are particularly relevant for:

• Hotels: the initial amount can include room charges plus an incidentals buffer.
• Car rental: the rental company may reserve more than the quoted base price.
• Fuel stations: automated pumps can request a fixed amount before the final fuel total is known.
• Restaurants: the initial authorisation may be adjusted to include a tip.
• Subscriptions: merchants can test or renew a card using separate authorisation events.

When the merchant clears the transaction, the final amount replaces the hold. If a $1,200 hotel hold clears at $1,050, the extra $150 becomes available again. If the merchant does not complete the transaction, the hold should eventually expire or be reversed under the relevant programme and network rules.

Hold duration is not universal. Finance teams should avoid treating an authorisation as a final expense or assuming unused funds will return on a fixed date.

Step 3: clearing and final settlement

After the purchase, the merchant submits the final transaction record for clearing. This can happen later the same day, but one to three days is common. Some sectors and delayed transactions take longer.

Clearing establishes the posted amount. The card programme then settles its obligations through the card ecosystem, while the merchant receives funds through its acquiring provider. The company’s statement should show the completed transaction, its settlement currency and any applicable fees or exchange-rate information.

A stablecoin card therefore has two separate economic events that finance teams may need to reconcile:

• the conversion or allocation of USDC or USDT into card spending capacity; and
• the card transaction that is authorised and subsequently posted.

Teams searching for a USDC card business setup should ask whether conversion happens before spending, how the exchange rate is recorded, and whether card expenses settle against a USD, EUR, GBP or other base-currency balance.

What happens when the merchant charges a foreign currency?

Foreign spend can involve more than one conversion. Suppose the card’s base currency is USD and an employee pays EUR 500 in France. The transaction is authorised in euros, but the amount reserved against the card balance may be shown as an estimated US dollar equivalent.

At clearing, the network or programme applies the relevant exchange rate under its rules. The final posted USD amount can differ from the authorisation hold because exchange rates or the final merchant amount changed.

Finance teams should separate:

• Stablecoin conversion: for example, converting USDT into the fiat balance used to fund cards.
• Card FX conversion: converting the merchant’s transaction currency into the card’s settlement currency.
• Merchant currency conversion: when a merchant offers to charge in the card’s home currency, often called dynamic currency conversion.

Each conversion can have a different rate and fee. Review the published pricing for the relevant corridor and card programme rather than assuming that a dollar-denominated stablecoin removes FX costs. A stablecoin card can simplify treasury funding, but it does not make foreign-currency card spending exchange-rate neutral.

Controls that matter for finance teams

Card controls should be designed around the expense, not just the employee. Useful controls include individual card limits, approval limits and MCC restrictions. A software purchasing card, for example, can have a defined limit and be restricted to relevant merchant categories.

Virtual cards can be issued for online purchases and recurring vendors, while physical cards support travel and point-of-sale spending. Cards should be frozen or cancelled promptly when an employee leaves, a project ends or card details are exposed.

The audit log should connect card issuance, limit changes, treasury funding and posted transactions. Supporting evidence such as receipts, invoices and approvals can then be included in an evidence pack for accounting or audit review.

Questions to ask before using stablecoins to fund cards

• Which stablecoins, blockchain networks and card settlement currencies are supported?
• When does stablecoin-to-fiat conversion occur?
• Which rate and fees apply to treasury conversion and foreign card spend?
• How quickly does funding become available for authorisation?
• How are holds, reversals, refunds and disputed transactions displayed?
• Can limits and MCC restrictions be set by card or cardholder?
• What records are available for reconciliation and audit?

The core accounting principle is straightforward: treat treasury funding, authorisation holds and settled card expenses as distinct stages. That separation makes it easier to understand available cash, investigate differences and reconcile a stablecoin-funded card programme without mistaking temporary holds for completed spending.