A stablecoin-backed card spends USDC or USDT wherever Visa or Mastercard works. The four parts behind it, who does what, and where the money comes from.
A stablecoin-backed card is a Visa or Mastercard card that spends a dollar stablecoin balance, usually USDC or USDT. You tap or type the card like any other. Behind the scenes, a card program checks your stablecoin balance, converts the purchase into the merchant's currency, and pays the merchant normally. The merchant never sees crypto.
That is the whole idea. A stablecoin you hold onchain becomes something you can spend at a supermarket, an airline website, or a taxi app.
The interesting part is the plumbing. Four separate pieces have to work together for one tap to go through, and each one is run by a different company. This guide explains those four parts in plain English, with a short diagram in text. For the business and issuing view of the same product, read what stablecoin card issuing is.
Key takeaways
A stablecoin-backed card is a payment card that draws on a stablecoin balance and pays merchants in their own currency. The card looks and behaves like any debit card. Only the money behind it is different.
Two definitions help before going further.
Stablecoin. A token on a blockchain designed to hold a steady value against a currency, usually the US dollar. USDC and USDT are the two largest. What is USDC covers how one is backed and redeemed.
Card program. The company or group of companies that runs the card for you: it holds or reads your balance, approves purchases, and settles with the network. You may know it by the app brand on the card.
Every stablecoin card has the same four parts: a wallet balance, an issuer and program, a card network, and a merchant payout. The card in your hand is just the key that connects them.
Here is the flow as a simple diagram in text:
The balance is where your stablecoins sit before you spend them. In some programs the provider holds the balance in an account it controls (custodial). In others the stablecoins stay in a wallet you control, and the card is allowed to pull from it (self-custodial). Custodial programs are simpler to recover if you lose a phone. Self-custodial programs keep the stablecoins out of the provider's hands until you spend them.
The issuer is the regulated bank or e-money institution whose name sits behind the card number. A program manager runs the product day to day, and an issuer processor answers each purchase request in real time. This is where the stablecoin gets checked and converted.
Visa or Mastercard carries the purchase request from the merchant's side to the issuer and back, then nets and settles the money between banks. The network sets the rules both sides follow.
The merchant's bank, called the acquirer, pays the merchant in local currency on its normal schedule. From the merchant's view, this was an ordinary card sale.
Each company in the chain owns one job. The table shows who that is and what they do on a single purchase.
| Part | Who runs it | What it does on your purchase |
|---|---|---|
| Wallet balance | You, or the card provider | Holds the USDC or USDT you will spend |
| Issuer | A licensed bank or e-money institution | Legal issuer of the card; owns compliance |
| Program manager | The card brand you signed up with | Runs the app, onboarding, and support |
| Issuer processor | A card processing company | Approves or declines in seconds, places a hold |
| Card network | Visa or Mastercard | Routes the request, settles between banks |
| Acquirer | The merchant's bank or payment provider | Pays the merchant in local currency |
One company can wear several of these hats. A big provider may act as program manager and processor at once. What stays constant is that a licensed issuer sits behind every card, and it must identify every cardholder.
The card program converts the stablecoin into fiat at some point between your tap and the merchant getting paid. When that conversion happens depends on the program's funding model.
Some programs convert just in time, at the moment of purchase. Others ask you to load the card first, converting stablecoins into a card balance in advance. Prefunded cards often charge a fee per load, and just-in-time cards keep your balance in stablecoins until you spend. The business comparison of crypto debit and stablecoin cards shows how the choice changes accounting and tax.
There are two settlement models today. In the traditional one, the card program converts stablecoins to dollars and settles with the network over bank rails. In the newer one, the issuer settles with the network directly in a stablecoin.
Traditional model. The program sells stablecoins for fiat through a liquidity partner and pays the network in dollars or another currency, as any issuer would. Nothing about the network changes.
Stablecoin settlement model. Visa announced on December 16, 2025 that US issuer and acquirer partners could settle with Visa in USDC, with Cross River Bank and Lead Bank as the first participants, settling over Solana. On April 29, 2026, Visa said its stablecoin settlement pilot supported nine blockchains and had reached a $7 billion annualized settlement run rate.
That $7 billion is a settlement figure, money moving between institutions. It is not card spending, and it should not be added to card volume numbers.
Stablecoin card spending is growing fast from a small base. Visa's numbers put it at a few billion dollars a year, a tiny slice of total card volume.
Read 0.04% carefully. It means stablecoin cards work at scale on existing rails. It does not mean they replace bank cards.
At checkout, yes. Underneath, no. The difference is what backs the balance and who protects it.
| Stablecoin-backed card | Bank debit card | |
|---|---|---|
| Balance | USDC or USDT, in a wallet or held by the provider | Bank deposit |
| Conversion at purchase | Yes, stablecoin to merchant currency | Only for foreign purchases |
| Deposit insurance | No; the FDIC says its insurance does not cover crypto assets | Usually, up to the legal limit |
| Merchant experience | Same | Same |
| Identity check | Required by the issuer | Required by the bank |
| Funding | Stablecoin transfer, exchange, or bank deposit converted to stablecoins | Bank transfer or paycheck |
The FDIC's fact sheet on crypto companies is explicit that deposit insurance does not apply to crypto assets. That matters more than the checkout experience if the provider runs into trouble.
A stablecoin card only covers the spending moment. Money still has to arrive in the wallet first, and some of it eventually has to leave for a bank account. Those are two separate steps.
Funding in. Most people fund a card with stablecoins bought on an exchange, received as payment, or converted from a bank transfer through a virtual account.
Cashing out. Rent, school fees, and taxes usually need a bank transfer, not a card swipe. For that, the stablecoins go through an off-ramp into a local bank account.
Businesses running card programs feel this most. Their users want to top up from a bank account and withdraw to one, in their own currency.
BlindPay is a stablecoin API for global payments that covers the funding and cash-out legs around a card. Card programs and wallets pair an issuer for the card with a payout and collection layer for the money moving in and out.
A card program that adds this layer lets its users move money between the card wallet and a bank account in their own country.
Check who issues the card, who holds your balance, and what the conversion really costs. Those three answers tell you most of what can go wrong.
If you run a card program or wallet and want the funding and payout legs handled through one API, start with the free development instance in the BlindPay payout quickstart.
The five risks of a stablecoin card: peg, program failure, custody, smart contracts, and fraud, with the August 2026 incident and a safety checklist.
Stablecoin payments are as safe as the issuer, the network, the provider, and your own controls. The seven risks to check, with real incidents and fixes.
Five stablecoin APIs compared for cross-border payments: primary use case, pre-funding requirement, payout regions, and developer experience, plus how to choose by buyer scenario.