Stablecoin card vs crypto debit card: prepaid, credit, which coin

A crypto debit card is a Visa or Mastercard card that spends a volatile asset, such as bitcoin held on an exchange, by selling it at the moment of purchase. A stablecoin card spends a dollar-pegged balance such as USDC, so the amount debited tracks the purchase. Either can be built as prepaid, debit or credit backed by collateral.

What are the four kinds of crypto and stablecoin card?

The two names in the title describe different things. "Crypto debit card" says what is sold at the swipe: a volatile asset the issuer converts to fiat for the merchant. "Stablecoin card" says what the balance is made of: a coin pegged to a currency. Neither says how the card is built in law, and that is the second axis: debit, prepaid, or credit repaid from collateral. Rain's card-issuing page lists credit and prepaid products and describes its debit cards as Visa debit issued by a bank, which is why a stablecoin card is a funding choice, not a legal category. If the term is new, start with what a stablecoin is and what stablecoin card issuing is.

Four card types compared by what is spent, what happens at the swipe and who holds the funds. Sources are listed under Methodology and sources, all read on November 1, 2026.

The first column carries the most bookkeeping. Kraken's card page warns that spending crypto may be a taxable event because conversion to fiat can create capital gains or losses, and the IRS virtual currency FAQ treats virtual currency as property, so a sale means recognizing a capital gain or loss. On a card funded from bitcoin, that is one sale per purchase. The IRS page does not mention stablecoins, so confirm with a tax adviser how your coin is treated. The fee and settlement rows are covered in how stablecoin card transactions settle, and the rules that decide who is protected in US and EU regulation.

Who holds the money behind each card?

This is the question that separates the four types more than rewards or fees do, because it decides what is left if something goes wrong at the other end. On an exchange-issued crypto debit card, the balance is a claim on the exchange, so the card works as long as the exchange does. On a prepaid card, the issuer holds what was loaded. On a credit card backed by collateral, the funds sit in a contract that backs each authorization.

Rain's real-time funding, as described on its site, is an example of the third case. The user connects a wallet and approves how much the card may spend. At each purchase only that purchase's amount is committed to the collateral contract, where it stays until it is liquidated to repay Rain's extension of credit, and the rest stays in the wallet. The approval can be revoked at any time.

I recommend asking who holds the funds before anything else, ahead of rewards, fees or coin. I would not put company money on a card that spends from an exchange balance, because the balance is a claim on someone else's books and the company cannot move it without the exchange. A wallet the company's own platform controls, with a spend approval the cardholder can revoke, answers the question in one sentence.

In the Lumx stack, the balance sits in the cardholder's custodial wallet. Every customer gets a wallet on each supported blockchain, provisioned with the customer and enabled once the customer is approved after identity verification (per the wallets docs, read on November 1, 2026). For a Rain-issued card, the card spends from that wallet balance through Rain's real-time funding, currently in beta per Rain, and the approval is the cardholder's to revoke. Rain stays part of the customer's stack, not a Lumx product.

How a card purchase settles, and where stablecoins enter

The swipe has two legs. On the cardholder side, the card type decides what is debited and from where. On the network side, the issuer settles with Visa or Mastercard for what its cardholders spent. Stablecoins can appear on either leg, and they change different things.

On the network side, Mastercard announced that issuers and acquirers can settle card transactions in regulated stablecoins, including on weekends and holidays. Lumx's Stable News write-up lists USDC, PYUSD, USDG, USDP, RLUSD and SoFiUSD across eight blockchain networks. Rain says the same shift cuts the reserve a program holds: in a fiat program, settlement with the network typically takes two business days and the company keeps three to five days of projected spend in reserve, per Rain's fiat vs stablecoin cards page. That is the issuer's economics, not the cardholder's. A cardholder swiping a prepaid card and one swiping a credit card backed by collateral see the same terminal.

Tax follows the funding side, not the settlement side. One line is enough here: spending anything other than a currency can create a taxable disposal in some countries, and the Brazilian rules are covered in are stablecoin cards taxed in Brazil.

The card itself comes from the issuer in your stack. What Lumx does at this point is the money around it: the deposit that credits the wallet before the swipe, and the off-ramp that debits the wallet after.

Which stablecoin to hold for card spend

Decide by where the money will be spent, not by which coin ranks higher. Hold USDC when the issuer lists it. Of the six stablecoins in the Mastercard announcement above, USDC is listed and USDT is not, and Rain's real-time funding beta lists USDC on Base and Arbitrum and USDT0 on Plasma. For a cardholder whose balance already arrives in USDT, hold USDT and check that the issuer accepts it before funding. Which coin a given card accepts is the issuer's list, not the network's. The wider ranking is in USDC vs USDT for payments.

Where each coin fits for card spend, with the networks Lumx wallets support for it, from the Lumx docs read on November 1, 2026.

Lumx wallets hold both coins, and an autoconversion rule picks USDC or USDT and the network for every deposit that matches it.

Where Lumx sits when a card balance comes from Pix or SPEI

The pattern is the same whichever card type the issuer builds: a local-currency deposit becomes stablecoin in the wallet, and a cash-out turns it back into a local bank transfer. Lumx is stablecoin payments infrastructure for businesses that move money between Latin America and the rest of the world: one API to collect, hold, convert, and pay out in BRL, MXN, COP, USD, EUR, and GBP or in USDC and USDT, over local rails such as PIX, SPEI, PSE, Bre-B, ACH, FEDWIRE, SEPA, and Faster Payments, with SWIFT and on-behalf-of payments and collections (POBO and COBO) in USD, EUR, and GBP, plus named virtual accounts, custodial wallets, and KYB/KYC built in.

For card top-ups only four of those rails matter, and each has its own account detail.

For the top-up, each cardholder gets a named virtual account (a local account number issued in the customer's own name). In Brazil the cardholder pays through Pix (Brazil's instant payment system, run by the Central Bank), and the sender's Pix payment is matched to the autoconversion rule by the code on the deposit. In Mexico the cardholder pays through SPEI (Mexico's interbank transfer system, run by Banxico) with a reference, and the rule matches on that reference. In Colombia the COP account takes Bre-B (Colombia's instant payment system) through the account's Bre-B key, or PSE (Colombia's online bank-transfer network). Each deposit must be worth at least 50 USD in the account's currency, or it is not converted.

Top-up and cash-out by currency, from the Lumx docs read on November 1, 2026.

Country and rail coverage is on the coverage page. Cash-out starts with the platform, not the card. Your app calls the Lumx API to run an off-ramp from the wallet to a destination registered under the cardholder, with the holder relationship set to self. A withdrawal larger than the wallet balance fails with an insufficient-balance error. With a Rain-issued card, your app sets the withdrawable amount: wallet balance minus what open authorizations commit. For the Rain side of the stack, see Lumx vs Rain.

When a card is the wrong tool

A card pays merchants. For a landlord in São Paulo who takes Pix or a supplier in Mexico City who invoices over SPEI, a card plus a cash withdrawal is the long way around. Use a direct payout to the local bank account instead, from the same wallet. The comparison of the two is in stablecoin card vs local payout, and the payout side is on the global payments page.

A crypto debit card is also the wrong tool for company spend that must close in dollars. If every swipe is a sale, finance books one expense and one gain or loss per purchase. A stablecoin card usually leaves a much smaller gain or loss to book, and a prepaid card adds a hard cap per cardholder. Pick credit backed by collateral only when the company wants to keep treasury in stablecoin and spend against it, and ask the issuer how collateral is liquidated before signing.

Methodology and sources

We compared the four card types on what is spent, who holds the funds, what happens at the swipe, budget behavior and tax at spend. Card and issuer behavior comes from the vendors' own pages, read on November 1, 2026: Rain's real-time funding, card issuing and fiat vs stablecoin cards pages (see Lumx vs Rain), and Kraken's card page for an exchange-issued card. The tax rule is the IRS FAQ on virtual currency transactions, based on Notice 2014-21, page last reviewed June 30, 2026.

Lumx behavior comes from the docs pages on wallets, autoconversion rules, accounts, destinations, payment rail cut-off times and coverage, all read on November 1, 2026.

Network claims cite the Mastercard announcement as summarized in our Stable News post, because Visa and Mastercard pages block automated readers. For country availability, check the issuer's own list.

To see the top-up work before any card exists, test it in the sandbox with the simulate-deposit endpoint.

Verified on November 1, 2026. Operational context, not legal, tax, or investment advice.

Cover photo: Shane Hoving on Unsplash.