1. Home
  2. Buy crypto with a prepaid card
  3. Privacy.com Virtual Card

US virtual card guide · Privacy.com & Lithic rules

Can you buy Bitcoin with a Privacy card (Privacy.com)?

Privacy.com is a favorite tool for generating merchant-locked and single-use virtual Visa and Mastercard numbers in the US. Here is why Privacy.com blocks almost every crypto exchange—and how to protect your card details while buying Bitcoin.

Check availability in your country before signing up.The exchange linked here holds US state licences but not in every state (New York and California are not on its list). Supported states are shown at sign-up.

  • High-risk blockPrivacy.com restricts crypto & quasi-cash merchants
  • Apple / Google Paymasks your 16-digit card number without getting blocked
Pale blue virtual payment cards with card numbers
Merchant-lockedPrivacy.com blocks MCC 6051 crypto merchants by policy
By CryptoPrepaid.cards editorial team Facts checked: October 2026 Updated: ~11 min read

People who search for how to buy Bitcoin with a Privacy card are usually security-conscious buyers. They already have a US bank account, they understand how online card fraud works, and they use Privacy.com to generate single-use or merchant-locked virtual Visa and Mastercard numbers so online stores never see their real debit card details. On paper, generating a burner card for a crypto purchase sounds smart. In practice, almost every attempt to buy Bitcoin with a Privacy.com card fails immediately with a merchant-block error. This guide explains why Privacy.com blocks cryptocurrency exchanges on its end, how exchanges treat virtual cards in general, what Privacy.com’s new stablecoin card waitlist is about, and how to buy Bitcoin privately without handing out your raw card number.

The short answer on Privacy.com and buying Bitcoin

Unlike retail gift cards—which usually fail because the crypto exchange blocks the card—a Privacy.com virtual card fails primarily because Privacy.com itself blocks cryptocurrency merchants. When a crypto exchange or on-ramp widget attempts to charge a Privacy Card under Merchant Category Code (MCC) 6051 (quasi-cash / cryptocurrency), Privacy.com’s authorization engine intercepts the request and declines it.

Even if a niche processor is not yet on Privacy.com’s merchant blocklist, Privacy cards run into a second hurdle: many virtual Privacy BINs are classified as commercial or prepaid/virtual debit programs without interactive 3-D Secure SMS challenges, and exchanges that flag a virtual card often ask for a selfie with a physical card or a formal bank statement showing your legal name and card number. For a full look at how virtual cards work in crypto, see our virtual crypto prepaid cards hub and our guide to buying crypto with a prepaid card.

Blockedhigh-risk & crypto merchants on Privacy CardsPrivacy Support
ACH pullhow Privacy.com funds cards from your US bankPrivacy.com
MCC 6051quasi-cash code that triggers Privacy’s blocklistVisa / MC rules
TokenizedApple Pay & Google Pay mask card numbers nativelyEMVCo token spec

How Privacy.com works behind the scenes

Privacy.com (operated by PayWithPrivacy / Lithic infrastructure in partnership with US issuing banks such as Patriot Bank, N.A. and Pathward, N.A.) sits between your checking account and online merchants. When you connect your US bank account or debit card to Privacy.com, you can spin up two main types of virtual cards:

  • Single-Use Cards: Automatically close the moment a single transaction completes, preventing any future recurring charges.
  • Merchant-Locked Cards: Lock permanently to the very first merchant that charges the card, so the 16-digit number is useless if leaked in a data breach at that merchant.

Notice how the money actually moves: when you spend $100 on a Privacy Card, Privacy’s issuing bank fronts the settlement over the Visa or Mastercard network and pulls the $100 from your linked checking account via Automated Clearing House (ACH). Because ACH transfers take several business days to settle and can be returned for insufficient funds (NSF) or unauthorized debit claims up to 60 days later, Privacy.com bears the float and fraud risk on every transaction.

Why Privacy.com blocks cryptocurrency exchanges

That ACH float risk is the exact reason Privacy.com blocks Bitcoin purchases. In its official help center article, Why was a transaction declined when I tried to use a Privacy Card?, Privacy.com explains the decline message “This merchant is not permitted to make charges on Privacy Cards”:

Think about what would happen if Privacy.com allowed instant Bitcoin purchases funded by an ACH bank pull: a fraudster with a compromised bank login could spin up a Privacy virtual card, buy $2,000 of Bitcoin instantly, withdraw the BTC on-chain, and leave Privacy.com holding the bag when the bank reverses the ACH pull three days later. Consequently, Privacy.com blocks Coinbase, Kraken, CEX.IO, MoonPay, Simplex, Ramp, Banxa and Paybis at the issuer level.

Smartphone checkout screen on purple background
Great for SaaS subscriptions, blocked for MCC 6051

Privacy.com’s merchant-locked cards shine when you are signing up for a gym trial, a streaming service or an unfamiliar web shop—but Privacy’s own risk engine stops crypto purchases before they clear.

Do crypto exchanges accept other virtual cards?

What if you use a virtual card that is not issued by Privacy.com—for example, a virtual debit card inside your Chime, Varo Bank, Albert or Revolut app, or a card tokenized through Apple Pay or Google Pay? Here is what major crypto providers publish about virtual cards in general:

How exchanges treat bank-issued virtual debit cards vs Privacy.com burner cards
PlatformBank-issued virtual debit cardPrivacy.com burner cardOfficial verification rule
CEX.IOAcceptedBlocked by Privacy.comAccepts both physical and virtual personal Visa/Mastercard debit and credit cards
SimplexAccepted (Visa in US)Blocked by Privacy.comExplicitly accepts virtual cards if enrolled in 3-D Secure; issuer policies apply
PaybisAccepted (physical preferred)Blocked by Privacy.comAccepts virtual cards with 3DS, but warns extra checks may require a card photo
MoonPayAcceptedBlocked by Privacy.comAllows virtual cards; verification may ask for an app screenshot showing the virtual card number
CoinbaseBank debit onlyRefused (prepaid/commercial BIN + Privacy block)Rejects prepaid, reloadable and business/commercial BINs

Notice one more catch with Privacy.com on exchanges: historically, several Privacy.com BIN ranges have been issued as commercial/business purchasing cards or prepaid cards to maximize merchant acceptance and interchange. Exchanges like Coinbase and Paybis strictly forbid business/corporate BINs on personal accounts, and require your verified legal name—whereas many users type a pseudonym or nickname onto a Privacy.com card, causing an immediate KYC mismatch.

What about Privacy.com’s new Stablecoin Virtual Cards?

While researching Privacy.com in 2026, you may have seen privacy.com/stablecoins, where Privacy.com opened a waitlist for stablecoin-funded virtual cards (“Keep your financial identity private with secure, crypto-backed payment solutions”). It is important not to confuse the direction of that product:

  • Buying Bitcoin with a Privacy Card (Fiat → Crypto): Blocked by Privacy.com’s high-risk merchant rules.
  • Spending stablecoins via a virtual card (Crypto → Fiat merchant): The direction Privacy.com is exploring with its waitlist, and a category that already exists today through live crypto virtual cards such as KAST, RedotPay, MetaMask Card, ether.fi Cash and Laso Finance. Compare all live options on our virtual crypto cards and stablecoin cards hubs.

How to buy Bitcoin without exposing your primary debit card number

If your whole reason for wanting to use Privacy.com is that you do not want to type your main checking account’s 16-digit debit card number into a crypto website, you have three much better tools that actually pass compliance checks:

Three ways to isolate your main debit card when buying Bitcoin in the US

Apple Pay / Google Pay
Dedicated Neobank Debit (Chime / Varo)
US ACH Bank Transfer
Merchant sees your real 16-digit card number?
○
Only the secondary account card
○
Passes 3-D Secure / biometric check?
●
●
N/A (bank rail)
Blocked by Privacy.com high-risk rule?
○
○
○
Instant card lock in mobile app?
●
●
N/A
Accepted at regulated US exchanges?
●
●
●

● yes ◐ partly / some regions ○ no

  1. Use Apple Pay or Google Pay: When you pay with Apple Pay or Google Pay, your phone substitutes a cryptographic Device Account Number (DAN) and a dynamic single-use security code (cryptogram) for your real 16-digit card number. The crypto exchange never receives your raw card digits, yet your bank sees a verified biometric 3-D Secure transaction.
  2. Keep a dedicated “crypto checking” debit card: Open a free, no-minimum US mobile checking account like Chime or Varo Bank. Transfer only the exact dollar amount you want to spend into that account, buy Bitcoin with its Visa debit card, and toggle the card lock switch in the app when you are done.
  3. Use a domestic ACH transfer: Link your bank account via ACH on a FinCEN-registered exchange. No card number is ever transmitted over Visa or Mastercard rails, and deposit fees are typically $0.

Step by step: switching from Privacy.com to a method that clears

  1. 01
    Skip Privacy.com for MCC 6051 crypto checkouts

    Do not keep generating new single-use Privacy cards after a decline; repeated attempts at blocked merchants can flag your Privacy.com account for review.

  2. 02
    Add your personal bank debit card to Apple Pay or Google Pay

    Tokenize your personal Visa or Mastercard debit card inside your phone’s native wallet so the merchant only receives a tokenized Device Account Number.

  3. 03
    Or link your US bank account via ACH

    For larger purchases with zero card processing fees, connect your checking account via ACH on a licensed US exchange.

  4. 04
    Withdraw Bitcoin to your own self-custody wallet

    Once your purchase settles, move your BTC to your own hardware or software wallet so your funds are never left sitting on an exchange.

Our team’s take

We love Privacy.com for sketchy free trials and recurring SaaS subscriptions, where merchant-locked limits save you from surprise renewals. For buying Bitcoin, however, Privacy.com is the wrong tool because its own terms block crypto merchants. Use Apple Pay or Google Pay if you want card-number tokenization, or keep a separate free Chime or Varo checking account as a clean firewall between your main savings and your crypto activity.

— CryptoPrepaid.cards editorial team

For US buyers who want a regulated platform supporting Apple Pay, Google Pay, personal virtual/physical debit cards and ACH transfers, CEX.IO has operated since 2013, is registered with FinCEN as an MSB (NMLS 1804170) and holds Money Transmitter Licenses across roughly 39 US jurisdictions (excluding New York and California). And if you want a virtual card that spends crypto online, see our virtual crypto prepaid cards guide and our no-KYC crypto cards explainer.

Frequently asked questions

Can you buy Bitcoin with a Privacy.com virtual card?
Usually not. Privacy.com states in its official support documentation on declined transactions that it blocks merchants with a high volume of high-risk transactions ("This merchant is not permitted to make charges on Privacy Cards"), which covers nearly all cryptocurrency exchanges and on-ramp widgets. On top of that, many exchanges require 3-D Secure and physical card photo verification that disposable virtual cards cannot pass.
Why does Privacy.com say "This merchant is not permitted to make charges on Privacy Cards"?
Privacy.com funds virtual cards by debiting your linked US bank account via ACH while settling with the merchant over Visa or Mastercard rails. Because crypto purchases are irreversible quasi-cash transactions (MCC 6051), Privacy.com blocks crypto exchanges at the merchant level to prevent ACH return fraud and unauthorized account drain.
Do exchanges accept virtual cards at all?
Yes, if the virtual card is a personal debit or credit card issued directly by your bank or neobank (such as Apple Pay, Google Pay, Chime, Varo or Revolut). CEX.IO and Simplex both state that they accept virtual Visa and Mastercard cards, while Paybis accepts virtual cards but recommends physical cards because compliance checks may ask for a photo of the card.
What is Privacy.com’s Stablecoins virtual card waitlist?
Privacy.com launched an official waitlist at privacy.com/stablecoins for upcoming stablecoin-funded virtual cards, designed to let users fund masked virtual cards with crypto stablecoins rather than buying Bitcoin with a bank-funded Privacy card.
What is the safest way to buy Bitcoin without exposing my main debit card number online?
Instead of a Privacy.com card that gets blocked on MCC 6051, add your personal bank debit card to Apple Pay or Google Pay (which tokenizes your card number via a Device Account Number so the merchant never sees your real 16 digits), or fund a regulated US exchange via an ACH bank transfer.

Sources and official pages

  1. Privacy.com — Official Virtual Cards Platform
  2. Privacy.com Support — Why was a transaction declined when I tried to use a Privacy Card?
  3. Privacy.com — Stablecoin-Funded Virtual Cards Waitlist
  4. CEX.IO Support — Payment Card Verification Guide (Virtual Cards)
  5. Simplex — Can I use a virtual card to purchase cryptocurrency?
  6. Paybis Help — Credit/debit cards (Virtual Card rules)
  7. MoonPay Support — Verifying your cards (Virtual Card screenshots)
Ready when you are

Protect your card details and still get approved.

Use Apple Pay, Google Pay or an ACH transfer on a regulated US exchange to buy Bitcoin without exposing your card number.

Buy Bitcoin

Check availability in your country before signing up.The exchange linked here holds US state licences but not in every state (New York and California are not on its list). Supported states are shown at sign-up.

Keep reading

Need crypto for your card?Buy in minutes Buy crypto