Crypto-to-fiat settlement is the moment in a card transaction when a cardholder's crypto or stablecoin balance is converted into the card scheme's fiat settlement currency. The cardholder spends from an on-chain balance, but the merchant — and the acquirer behind it — receives ordinary fiat. The conversion is priced and locked at authorisation, in real time, so a tap that draws on USDC or Bitcoin clears through Visa or Mastercard exactly like any debit card. This guide explains how that conversion works inside a card programme: the timing, the spread and FX, who bears price risk, and the compliance that surrounds moving value between crypto and fiat.
Card schemes — Visa, Mastercard and the rest — settle exclusively in fiat. A merchant in Paris expects euros; a merchant in London expects sterling. Crypto-to-fiat settlement is the bridge that lets a cardholder fund a spend from a crypto or stablecoin card balance while the merchant side of the transaction sees nothing but fiat. The crypto element is entirely upstream of the scheme: it is the cardholder's funding source, converted to fiat at the point of authorisation and then settled through the normal card rails.
This is the defining mechanic of every crypto-funded card. Whether the balance is held in Bitcoin, Ether or a fiat-pegged stablecoin such as USDC, the programme must answer one question at the instant of a transaction: how much crypto does it take, right now, to fund this fiat amount? The answer is the conversion rate, and the difference between the wholesale rate the programme obtains and the rate quoted to the cardholder is the spread.
Inside a crypto card programme, crypto-to-fiat settlement runs through a tight sequence of steps that complete in the time it takes a terminal to say "approved":
Codego performs this on-the-fly crypto-to-fiat conversion at the point of sale across 7 regions, so a cardholder can spend a stablecoin balance at any Visa or Mastercard acceptance point without manually selling crypto first. The mechanics are documented in the Visa crypto card API reference.
Two costs sit inside a crypto-to-fiat card transaction, and it matters which party carries each. The first is the conversion spread — the margin between the wholesale crypto-to-fiat rate the programme can source and the rate quoted to the cardholder. The second is the scheme FX margin, which applies whenever the settlement currency differs from the merchant's currency, just as it would on any multi-currency card. These are separate from interchange, which is paid by the merchant's acquirer to the issuer and does not touch the cardholder.
Price risk depends entirely on the funding asset:
With Bitcoin or Ether, the value of the funding balance moves continuously. The cardholder bears price risk up to the moment of conversion; the programme bears short-lived inventory risk between authorisation and the on-chain sweep that settles the position.
With a fiat-pegged stablecoin such as USDC, price risk is minimal — the peg holds the value near the reference fiat. The main residual cost is the cross-currency FX spread when the stablecoin's reference currency differs from the settlement currency. See the USDC card program entry.
Between locking the crypto at authorisation and converting or sweeping it, the programme holds a transient position. Treasury manages this exposure by hedging, by holding fiat float, or by settling on-chain quickly enough that the window is negligible.
It helps to separate two clocks. For the cardholder, settlement of the crypto-to-fiat conversion feels instant: the rate is quoted and locked at authorisation, and the funding balance is committed in that moment. There is no waiting for an exchange order to fill or a bank withdrawal to clear.
For the card scheme, settlement follows the ordinary card cycle — typically clearing the day after authorisation, with the issuer debited and the acquirer credited in fiat on a T+1 basis. The crypto sweep that ultimately funds the programme's fiat position can happen at authorisation, in batches, or on a schedule, depending on how the programme manages its treasury. What the cardholder never sees, and never has to manage, is the gap between the instant lock and the scheme's settlement window.
Crypto-to-fiat settlement carries the compliance obligations of both worlds. On the card side, the programme runs the usual stack: KYC at onboarding, AML and sanctions screening, ongoing transaction monitoring, 3D Secure for card-not-present, and PCI DSS for card data. On the crypto side, additional virtual-asset obligations apply:
Launch a branded crypto-funded card with on-the-fly crypto-to-fiat conversion at the till.
Cards funded from a fiat-pegged stablecoin balance, with minimal conversion price risk.
How a USDC-backed card programme converts and settles at authorisation.
The fee the merchant's acquirer pays the issuer — separate from the conversion spread.
Exploring crypto-to-fiat settlement for your own card programme? Tell us what you want to build and we will map it to the rails.