Crypto Card Checkout vs On-Chain: Speed Comparison (2026)

**2.3 seconds.** That's how long a crypto card authorization takes. I timed it last week buying a year of Cloudflare Pro — card details entered, 3D Secure popped up, confirmed, done. The order confirmation email hit my inbox before I'd closed the checkout tab.

The week before, I tried paying for a VPS with on-chain BTC. The checkout page said "waiting for confirmation." I went to make coffee. Came back. Still waiting. Checked Twitter. Still waiting. Forty-two minutes later, the payment finally cleared.

Same crypto. Same me. Wildly different experiences. I felt stupid for not just using the card.

I kept thinking about that gap. How big is it really? Is my one-off timing representative? What does the actual data say about checkout latency across payment methods?

So I pulled together everything I could find — blockchain confirmation statistics, card network authorization benchmarks, merchant checkout analytics, and timing data from crypto payment processors. Here's what the numbers show.

How We Measured This

This isn't original research — it's a synthesis of publicly available timing data from multiple sources:

- **Visa and Mastercard authorization benchmarks** from their respective developer documentation and network performance reports (2025-2026)
- **Blockchain confirmation statistics** from Blockchain.com, Etherscan, and Solscan historical data
- **Payment processor disclosures** from BitPay, Coinbase Commerce, and BTCPay Server documentation
- **Lightning Network benchmarks** from 1ML and Lightning Labs published metrics

Where timing varies (and it does — network congestion, block luck, processor load all affect things), I've noted the typical range rather than cherry-picking best-case numbers. The goal is realistic expectations, not marketing copy.

One limitation: merchant-side processing time varies enormously. A well-optimized checkout might add 500ms. A clunky one might add 5 seconds. I'm focusing on the payment network portion — the part you can't optimize by picking a better merchant.

Card Authorization: 2-4 Seconds, Every Time

A crypto-funded virtual card — whether from VeloCards, Crypto.com, or any other issuer — runs on Visa or Mastercard rails. The merchant doesn't know or care that crypto funded it. To them, it's just a card.

And card authorizations are fast. Really fast.

**Visa's published benchmark:** 99% of transactions authorize in under 3 seconds. The median sits around 1.8 seconds. Mastercard reports similar numbers — their target is 99.9% under 3 seconds.

Here's what happens in those 2-4 seconds:

1. Merchant sends authorization request to acquirer
2. Acquirer routes to card network (Visa/Mastercard)
3. Network routes to issuing bank
4. Issuer checks card validity, balance, fraud signals
5. Response travels back through the chain
6. Merchant displays "approved"

The entire round trip — including fraud scoring, balance checks, and cross-border routing if applicable — happens faster than you can read this sentence aloud.

Why so fast? Decades of optimization. Card networks process north of 65,000 transactions per second globally. Every millisecond matters at that scale. The infrastructure is built for speed — and say what you will about legacy finance, they nailed this part.

The crypto part — converting your BTC, ETH, or USDT to spendable dollars — already happened when you loaded the card. At checkout, you're just spending dollars with extra steps invisible to everyone except your card statement.

For a walkthrough on how card funding works in practice, our [guide to spending Bitcoin on Google Ads](/post/how-to-spend-bitcoin-on-google-ads) covers the mechanics.

On-Chain Bitcoin: 10-60 Minutes (Usually)

Bitcoin's design makes a tradeoff: decentralization and security over speed. Blocks arrive every 10 minutes on average. (Sometimes 1 minute. Sometimes 45 minutes. It's probabilistic.)

But one block isn't enough for most merchants.

**Typical merchant confirmation requirements:**

| Transaction Value | Required Confirmations | Wait Time (avg) |
|------------------|----------------------|-----------------|
| Under $100 | 0-1 | 0-10 min |
| $100-1,000 | 2-3 | 20-30 min |
| $1,000-10,000 | 4-6 | 40-60 min |
| Over $10,000 | 6+ | 60+ min |

Those confirmation thresholds exist for good reason. With one confirmation, a sufficiently motivated attacker with hashrate could theoretically reverse the transaction. With six confirmations, that attack becomes economically infeasible for any realistic transaction value.

BitPay's documentation states they wait for "a minimum of one confirmation" but recommend merchants set their own thresholds based on risk tolerance. Coinbase Commerce waits for network confirmations based on the cryptocurrency and amount.

In practice, I've seen checkout pages stuck on "confirming" for anywhere from 8 minutes to over an hour. Block luck is part of it. Network congestion is another — during high-fee periods, lower-fee transactions can wait multiple blocks to be included.

My VPS experience (42 minutes) wasn't unusual. It was actually on the faster end for a ~$200 payment requiring 3 confirmations.

Ethereum Mainnet: Slightly Better, Still Not Fast

Ethereum improved confirmation times with the merge to proof-of-stake. Blocks now arrive every 12 seconds, not 10 minutes. That sounds like a massive upgrade — and it is, compared to Bitcoin.

But finality is more complex.

**Ethereum confirmation timing:**

- Block time: ~12 seconds
- "Safe" finality: 2 epochs (~12 minutes)
- True finality: 2-3 epochs (~13-20 minutes)

Merchants accepting ETH directly face a choice: accept after a few blocks (faster, some reorg risk) or wait for epoch finality (slower, cryptographically final).

Most merchant services split the difference. Coinbase Commerce considers ETH payments complete after 35 confirmations — roughly 7 minutes. BitPay uses similar thresholds.

That's faster than Bitcoin. But it's still 7+ minutes staring at a "processing" screen. Compare that to a card's 2.3 seconds and the UX gap is obvious.

(I'll be honest — I didn't appreciate this until I tried paying for domain renewals with ETH directly. Sat there like an idiot refreshing the page. The checkout flow felt ancient compared to entering a card number.)

The Speed Exception: Layer 2s and Lightning

Not all crypto payments are slow. Some are genuinely instant — faster than cards, even.

**Lightning Network (Bitcoin L2):**

- Settlement time: milliseconds to seconds
- Typical payment: 1-3 seconds including routing
- Capacity: millions of payments per second theoretically

Lightning is legitimately fast. I've paid Lightning invoices where the "paid" confirmation appeared before my finger left the trackpad. The problem? Merchant adoption. Most crypto-accepting checkouts don't offer Lightning. The ones that do tend to be crypto-native services — exchanges, VPNs, a handful of gaming platforms.

**Solana:**

- Block time: ~400 milliseconds
- Finality: ~2.5 seconds
- Throughput: 65,000+ TPS

Solana is fast enough to compete with cards. In theory. In practice, merchant integration is thin. The same checkout that accepts mainnet ETH often doesn't support Solana. You're stuck with the slower option.

**Ethereum L2s (Arbitrum, Base, Optimism):**

- Block time: 2-4 seconds
- Finality: varies (optimistic rollups have 7-day withdrawal windows, but payment finality is faster)

L2s offer card-competitive speed but face the same adoption hurdle. If a merchant only accepts mainnet payments, your speedy L2 balance is irrelevant.

The pattern is frustrating but predictable. (And yes, I've complained about this to people who don't care.) The payment networks that could be fast aren't widely accepted. The ones that are widely accepted are slow. A card — boring, decades-old card rails — ends up being the fastest option that works everywhere. That's embarrassing for an industry that talks about "disrupting finance."

Side-by-Side: What the Checkout Experience Actually Looks Like

Let me paint the picture with real timing from three payment scenarios. Same purchase — a $149 annual SaaS subscription.

**Scenario 1: Crypto Card**

- 0:00 — Enter card details
- 0:03 — 3D Secure prompt appears
- 0:06 — Authenticate on phone
- 0:08 — "Payment successful" displays
- 0:09 — Confirmation email arrives

Total checkout time: 8 seconds. Of that, 2-3 seconds was card authorization. The rest was me typing and tapping.

**Scenario 2: On-Chain Bitcoin (via BitPay)**

- 0:00 — Click "Pay with Bitcoin"
- 0:05 — QR code/invoice displays
- 0:45 — Scan, confirm in wallet, submit
- 1:00 — "Waiting for confirmation" appears
- 12:00 — First confirmation detected
- 25:00 — "Payment complete" displays

Total checkout time: 25 minutes. Most of it was waiting. I made lunch. This is not how "the future of money" should work.

**Scenario 3: On-Chain USDT (via Coinbase Commerce)**

- 0:00 — Select USDT payment
- 0:08 — Copy address, switch to wallet
- 0:35 — Confirm transaction on Ethereum
- 0:40 — "Confirming" appears
- 8:15 — "Payment successful" displays

Total checkout time: 8+ minutes. Better than Bitcoin. Still not close to card.

The time difference isn't subtle. It's the difference between checkout being a 10-second interruption and checkout being a background task you come back to later.

When On-Chain Actually Makes Sense

I'm not here to say on-chain payments are always wrong. They're not. There are legitimate reasons to wait 20 minutes for confirmation.

**Crypto-native services:** Some platforms don't accept cards at all. DeFi protocols, certain gaming platforms, crypto-focused tools. On-chain is your only option. If you're managing [multiple browser sessions for crypto operations](https://justbrowser.app), you're probably familiar with the drill.

**Proof of payment:** On-chain transactions are immutable receipts. When you need cryptographic proof that payment occurred — disputes, audits, trustless commerce — the blockchain record matters more than speed.

**Sending to wallets, not merchants:** Paying an invoice is different from sending to a friend's wallet. There's no "checkout" flow to optimize. The recipient waits for confirmation regardless of how you pay.

**Privacy considerations:** Card transactions create records at multiple parties — merchant, processor, network, issuer. On-chain transactions are pseudonymous. Depending on your threat model, that tradeoff may favor on-chain despite the speed penalty.

**Ideological preference:** Some people want to use crypto as money, not just as card funding. I get it. Honestly? I respect it. If you're willing to accept the speed tradeoff for the principle, that's a valid choice.

But for standard online shopping — SaaS, ad spend, digital subscriptions, e-commerce — the card wins on pure checkout experience. If you're running ad campaigns and [need to fund them quickly](https://clickzprotect.com), waiting 40 minutes for Bitcoin confirmation isn't viable. You'd lose ad positions while the payment confirms.

What This Means For Spending Decisions

The data points in one direction: for checkout speed, cards beat on-chain by an order of magnitude.

**Card authorization:** 2-4 seconds
**Bitcoin (3 conf):** 20-30 minutes
**Ethereum (35 conf):** 7-8 minutes
**Lightning:** 1-3 seconds (but limited acceptance)
**Solana:** 2-3 seconds (but limited acceptance)

The crypto part of "crypto card" happens before checkout — when you load your card with BTC, ETH, or USDT. By the time you're paying a merchant, you're using Visa/Mastercard infrastructure that's been optimized for speed since the 1970s.

On-chain payments make sense for specific use cases. Speed isn't one of them. If you're paying a merchant that accepts both cards and on-chain, and you care about checkout experience, the card is faster every time.

For tracking where your crypto spend actually goes — whether via card or direct — [JustAnalytics](https://justanalytics.app) provides cleaner attribution than trying to match wallet transactions to conversion events. And if you're doing outreach alongside paid spend, [JustEmails](https://justemails.app) handles the deliverability side.

Frequently Asked Questions

How long does a crypto card transaction take to authorize?

A crypto-funded virtual card authorizes in 2-4 seconds — identical to any other Visa or Mastercard transaction. The crypto-to-fiat conversion happens when you load the card, not at checkout, so the merchant sees a standard card payment.

How long do on-chain Bitcoin payments take to confirm?

Bitcoin's average block time is 10 minutes, but most merchants require 2-6 confirmations for finality. That means 20-60 minutes of waiting before the payment is considered complete. Some services accept 0-conf for small amounts, but that carries double-spend risk.

Are there faster blockchains for direct payments?

Yes. Solana confirms in under 1 second. Lightning Network settles Bitcoin payments in milliseconds. Ethereum L2s like Arbitrum and Base confirm in 2-4 seconds. But merchant adoption for these networks remains limited — most crypto-accepting checkouts still default to mainnet BTC or ETH.

When should I use on-chain payment instead of a crypto card?

On-chain makes sense when the merchant doesn't accept cards (crypto-native services, some DeFi platforms), when you need the transaction recorded on-chain for proof, or when you're sending to another wallet rather than paying a merchant. For standard online purchases, a card is faster and more widely accepted.

---

Spend Crypto Online — Without an Off-Ramp

VeloCards is a **virtual card** for spending BTC, ETH, and USDT at any Visa or Mastercard merchant online. No bank transfer dance, no off-ramp fees, no waiting days for crypto to hit fiat. Tier-based pricing — card creation fees drop as your annual spend grows.

**[Open an account →](https://velocards.com/)** · [See the spend tiers](https://velocards.com/#pricing)