Card-to-crypto checkout: how customers without crypto can still pay you in crypto

The most common reason merchants do not accept crypto is not that they dislike it — it is that their customers do not have any. Worldwide, an estimated 400–500 million people own cryptocurrency, but over 4 billion people have credit or debit cards. If accepting crypto requires your customer to already hold it, you have excluded most of the world.

Card-to-crypto checkout solves this. It lets a customer pay for your goods with a Visa or Mastercard, and you receive cryptocurrency as if they had paid on-chain. This article explains exactly how it works, how it differs from being redirected to a third-party exchange, and what the merchant actually receives.

The problem with "pay with crypto" in 2026

Crypto payment adoption for merchants has historically been limited by a chicken-and-egg problem: merchants do not accept crypto because customers do not have it; customers do not acquire crypto because they cannot spend it. Card-to-crypto checkout breaks this cycle by making the crypto acquisition happen transparently during the payment flow itself.

From the customer's perspective, they do exactly what they do for any online purchase: enter their card number, billing address, and CVV. The crypto mechanics are invisible. The merchant gets the benefit — lower fraud risk, no chargebacks, crypto settlement — without needing customers to have a wallet.

How card-to-crypto checkout works technically

The technical flow involves three parties: your checkout, a fiat on-ramp provider, and the payment gateway. Here is how a typical card-to-crypto payment flows:

1. Customer selects "Pay with card" on the payment page. This option is presented alongside wallet payment options (WalletConnect, TON, etc.).
2. The fiat on-ramp iframe or redirect opens — a regulated service that accepts cards. The customer enters their card details, which go directly to the on-ramp provider, not your server or the payment gateway.
3. The on-ramp provider processes the card payment, verifies identity as required (quick KYC for small amounts, stricter for large), and purchases the specified crypto on the customer's behalf.
4. The purchased crypto is sent on-chain to the invoice address generated by your payment gateway. This is a real on-chain transaction.
5. The payment gateway detects the on-chain deposit, confirms it per its standard confirmation logic, and marks the invoice as paid.
6. Webhook fires to your backend, and you fulfil the order.

From your integration perspective, steps 2–4 are handled entirely by the on-ramp provider and the checkout UI. You receive the same webhook event you would receive from a direct crypto payment. The card payment is invisible at your API layer.

The on-ramp provider's role

The fiat on-ramp provider is a regulated financial entity — in most cases, an e-money institution or a licensed virtual asset service provider (VASP). They handle card processing (Visa/Mastercard acquiring), KYC/AML on the buyer, and the crypto purchase execution.

In PawPayments, this role is played by Guardarian, a licensed crypto exchange based in Estonia (VASP registered with the FIU). When a customer clicks "Buy with card," the Guardarian widget opens inside the payment page. The customer's card data goes to Guardarian, not to PawPayments and not to the merchant.

This is a critical security property: the merchant is never in the payment chain for the card transaction. They receive only an on-chain deposit. This means the merchant does not need a card processing licence, does not handle cardholder data, and is not liable for card fraud in the on-ramp leg.

Card-to-crypto vs third-party redirect

There is an important distinction between an embedded card-to-crypto checkout and a simple redirect to a third-party exchange. Many gateways advertise "pay with card" but implement it as a link to a separate exchange website where the customer must:

• Create or log into an exchange account
• Complete KYC if not already verified
• Buy crypto with a card on that exchange
• Withdraw the crypto to their wallet
• Come back to your payment page and pay from the wallet

This process takes 15–30 minutes, requires the customer to already have (or create) an exchange account, and abandons most customers at step 1. It is not a card-to-crypto checkout — it is a link to a crypto exchange dressed up as a feature.

A proper embedded card-to-crypto checkout completes in 2–5 minutes within the payment page itself, with no account creation required. The distinction matters enormously for conversion.

KYC requirements inside the on-ramp flow

On-ramp providers are required by law to conduct KYC on buyers above certain thresholds. The specific thresholds depend on jurisdiction and on the on-ramp provider's risk policy. Typical rules:

• Below €100–150 per transaction: card verification only (3DS), no identity documents required in many jurisdictions.
• €150–€1,000 per transaction: light KYC — email, date of birth, and sometimes a photo of an ID document. One-time.
• Above €1,000: full KYC with government ID, selfie, proof of address. This is stored and not repeated on future purchases.

The KYC is done by the on-ramp provider, not by the merchant. The merchant does not receive or store any identity documents. This is the correct privacy-preserving architecture.

Fees in a card-to-crypto transaction

Card-to-crypto transactions carry higher fees than direct wallet payments because they involve additional parties:

• Card interchange fee: paid to the customer's card-issuing bank, typically 1–1.8% of the transaction amount. This is the dominant cost.
• On-ramp margin: the on-ramp provider adds a spread on the crypto purchase, typically 1–2%.
• Gateway fee: the payment gateway's standard per-transaction fee (typically 0.5–1%).
• Network fee: the on-chain transaction fee, which varies by network.

Total cost to the customer for a card-to-crypto payment is typically 2–4% above the crypto-native equivalent. For customers willing to pay this premium for convenience, it is reasonable. For crypto-native customers, direct wallet payment is always cheaper.

What the merchant actually receives

Once the on-chain deposit confirms, the merchant's payment gateway account is credited exactly as it would be for a direct crypto payment. If the gateway uses auto-conversion, the deposit is converted to a stablecoin or fiat and credited to the balance. If not, the original asset is credited.

The merchant cannot distinguish a card-to-crypto payment from a wallet payment in their transaction history — except that card-to-crypto payments always come from the on-ramp provider's wallet address, which can be recognised in analytics. Both appear as on-chain deposits to the invoice address.

One nuance worth highlighting: even when the merchant prices an invoice in a specific asset, the customer is not strictly locked into that asset. With PawPayments, if a buyer ends up sending a different supported cryptocurrency — say, USDC on Polygon instead of USDT on Ethereum (both EVM, same address format) — the deposit is still detected, valued at the live rate and credited to the merchant. The customer is not forced to find an exchange to swap into the "correct" coin first.

This means the merchant receives the same settlement quality: irreversible, no chargeback risk, on-chain verifiable. The card fraud risk (chargebacks from card-not-present fraud) sits with the on-ramp provider, not with the merchant.

Supported regions

Card-to-crypto availability depends on where the on-ramp provider is licenced and where it can acquire cards. In 2026, major on-ramp providers like Guardarian support most of Europe and many other regions, but are restricted in the United States (where state-by-state money transmitter licensing creates significant compliance complexity) and certain sanctioned jurisdictions.

Before relying on card-to-crypto checkout as a primary payment method, verify that the on-ramp provider supports your primary customer geography. Most providers publish their supported countries list.

When card-to-crypto checkout is the right choice

Card-to-crypto checkout makes sense when:

• Your customer base is primarily non-crypto-native but crypto-curious — they are willing to try crypto payments but do not already hold any.
• You want the benefits of crypto settlement (no chargebacks, fast settlement, lower fraud rates) without restricting your checkout to existing crypto holders.
• Your average transaction value is in the range where the 2–4% card-to-crypto premium is acceptable to customers (typically $50–$2,000).

It is less compelling for high-volume, low-margin merchants where the premium eats into margins, or for markets with deep crypto penetration where most customers already have wallets and prefer direct payment.

Summary

Card-to-crypto checkout is a technically elegant solution to the adoption gap: it lets any customer with a payment card benefit from on-chain crypto settlement, with no wallet setup, no exchange account, and no crypto knowledge required. The on-ramp provider handles the card processing, the on-chain purchase, and the KYC. The merchant receives an ordinary on-chain deposit. Chargebacks and card fraud risk stay with the on-ramp provider.

The key distinction to understand: a proper embedded card-to-crypto flow operates entirely within the payment page. A redirect to an exchange is a different product — evaluate it accordingly.

If you would like to see the embedded version in action, PawPayments will get you covered with a card-to-crypto checkout that lives inside the same payment page as wallet payments — same invoice, same webhook, no separate exchange detour for the customer.