Add Crypto Checkout to Your Store: 4 Ways to Go Live

Why "we should accept crypto" stalls at the checkout page

Most store owners have already decided they want a crypto option. They've watched cards decline legitimate cross-border orders, handed 3% of every sale to a processor, and eaten chargebacks on products that were already delivered. The demand side isn't the problem.

What stalls the project is the integration. "Crypto checkout" sounds like a blockchain engineering effort: hire someone who knows web3, run nodes, handle token contracts, audit everything, and hope nothing breaks in your existing cart. Your developer is booked for the quarter, the agency quotes weeks of work, and the idea slides to the backlog — again.

There's also a quieter trap: picking the wrong kind of provider. Many "crypto gateways" are custodial — they receive your customers' payments into their account and pay you out later, on their schedule, after their reviews. That's the acquirer model wearing a crypto costume, and it reimports the exact problems (holds, freezes, withdrawal thresholds) you were trying to escape.

What shipping it "next quarter" actually costs

Delaying the integration isn't neutral. Every month your store runs card-only, the meter keeps running:

• Processing fees you can't recover: 2.9% + $0.30 per sale (more cross-border, plus FX) comes straight out of margin. A store doing $30,000/month leaves roughly $1,000+ on the table every month it waits.
• Orders that never happen: customers in Argentina, Turkey, Nigeria, and dozens of other markets watch their cards fail "for compliance." Many of them hold stablecoins precisely because their local rails don't work — and they buy from whoever accepts them.
• Chargebacks on delivered goods: digital products and fast-shipped orders stay reversible for months on card rails. Each dispute costs the sale, the product, and a $15–$25 fee.
• A competitor gets there first: stablecoin checkout is becoming a standard payment method, not a novelty. The store that adds it first captures the crypto-holding segment in your niche.

The irony is that the integration everyone postpones is, with the right architecture, an afternoon of configuration.

Why DIY and custodial gateways both fall short

If you've researched how to add crypto payments, you've probably met the two bad defaults:

• The DIY route — pasting a wallet address on your site. It technically works and completely fails as checkout: there's no per-order amount, no way to know which customer paid, no payment detection, no handling of underpayment or overpayment, no volatility protection, and reconciliation becomes a spreadsheet nightmare. Your store never learns the order was paid, so nothing ships automatically.
• The custodial gateway. Integration is easy, but your revenue lands in the provider's balance, not your wallet. You wait for payout runs, pass their risk reviews, and live with the possibility of a frozen account — the same structural custody problem card processors have, minus the consumer protections.

A proper crypto checkout needs both halves: real checkout mechanics (exact amounts, payment detection, webhooks, order status) and non-custodial settlement (funds go straight to a wallet you control). That combination is exactly what a non-custodial crypto payment processor is for.

The four ways to add crypto checkout to your store

Payzum is a non-custodial, crypto-only processor built as a drop-in: it slots into the store you already run instead of asking you to rebuild it. Every path below ends the same way — the customer pays in USDC, USDT, or another supported coin; the transaction confirms on-chain in seconds; and the funds settle directly to your own wallet, optionally auto-converted to stablecoins. Pick the door that matches your stack:

1. Drop-in plugin — for stores on a standard e-commerce platform

If your store runs on a mainstream cart platform, the plugin is the shortest path. It appears at checkout as one more payment method next to cards, renders the payment screen for the exact order total, and marks the order paid via webhook the moment the transaction confirms. Your theme, cart logic, and card processor stay untouched.

2. Hosted checkout — redirect, modal, or inline

For custom carts, Payzum hosts the payment page itself. You send the customer to it (full redirect), open it over your page (modal), or embed it in your flow (inline). The hosted page handles everything crypto-specific — QR code, wallet interaction, network choice, exact amounts, confirmation states — so your team never touches key management or chain logic.

3. Payment links & buttons — no code at all

Create a link in the dashboard for a product, an amount, or an open "pay what's due," and share it anywhere: your site as a button, an email, a DM, an Instagram bio, a WhatsApp chat. This is the zero-developer path — many stores use links to test crypto demand for a week before touching their checkout at all.

4. REST API + signed webhooks — full control

Developers who want the checkout experience fully in-house can create charges programmatically through the REST API, listen for signed webhooks to drive the order lifecycle, and rehearse the whole flow in the integration playground before a real coin moves. Invoices support expiration windows and overpayment detection, so edge cases are handled by the platform instead of your support inbox.

Which path should you pick?

• Standard platform store (fashion, gadgets, supplements) → drop-in plugin.
• Custom cart or headless storefront → hosted checkout (redirect or inline).
• Social sellers, pre-orders, invoicing → payment links & buttons.
• Marketplaces and product teams → REST API + signed webhooks.

Whichever door you choose, you can layer on recurring crypto subscriptions, donations/tip-jars, and invoices later — it's one account and one wallet across all of them. See the full capability list on the Payzum features page.

How to add crypto checkout, step by step

Here's the whole project, end to end. For most stores it fits in an afternoon:

1. Create your account and pass KYC. Sign up at merchant.payzum.com. There's no merchant-account underwriting or weeks-long risk review before you can start.
2. Connect the wallet you control. Point settlement at your own address — MetaMask, Phantom, a hardware wallet — and optionally enable auto-convert to USDC/USDT so every sale lands dollar-stable regardless of what the customer pays with. USDC is a fully reserved dollar stablecoin, so $100 charged is $100 kept.
3. Wire up your integration path and test it. Install the plugin, drop in hosted checkout, create your first payment links, or hit the REST API — then run the flow in the integration playground and confirm your signed webhooks fire before going live. Full reference in the docs.
4. Go live and get paid in seconds. A customer picks "pay with crypto," pays the exact quoted amount, and the network confirms — Base and Polygon in ~2 seconds, Solana in under a second. The webhook flips the order to paid, fulfillment triggers, and the funds are already in your wallet.

Store use cases: what adding crypto checkout unlocks

Four concrete setups we see stores run, each using a different integration path:

• DTC brand recovering cross-border sales: a skincare brand on a mainstream cart platform installs the drop-in plugin in an afternoon. International shoppers whose cards were declining now pay in USDC on Polygon; orders confirm instantly and the brand keeps the full amount minus cents of network gas.
• Digital goods store ending friendly fraud: a shop selling templates, plugins, and game keys moves digital-product checkout to hosted checkout. Every download that's paid for stays paid for — on-chain finality means there's no 120-day dispute window to abuse.
• Instagram/WhatsApp seller with no website changes: a boutique that closes sales in DMs generates a payment link per order. The customer taps, pays from any wallet, and the seller sees confirmation in seconds — no cart integration at all.
• Subscription box on the API: a product team wires the REST API and signed webhooks into its own checkout and adds recurring crypto billing. Renewals stop dying to disputes, and settlement hits the company wallet the moment each cycle charges.

Payzum vs custodial crypto gateways: what changes at checkout

Common integration objections — answered

Will adding crypto break my existing checkout?

No. Crypto checkout runs alongside your card processor as an additional payment method, not a replacement. The plugin and hosted checkout don't touch your card flow, your theme, or your order pipeline beyond marking crypto orders as paid. If nobody used it, your store would behave exactly as it does today — the downside case is zero.

How do refunds work if payments are final?

Finality removes involuntary reversals — the bank clawing back a sale months later. It doesn't remove customer service. When a refund is warranted, you send the funds back from your wallet on your terms and your policy. You decide, not an issuing bank with a dispute quota, and fraudulent "item not received" claims on delivered goods simply stop working.

Do I need to run nodes, manage tokens, or hold keys on my server?

No. Payzum handles payment detection and confirmation across all supported chains — Bitcoin, Ethereum, Solana, Polygon, Base, Arbitrum, Optimism, BNB Chain, Avalanche. Your side is a normal wallet address for settlement and, if you use the API, verifying webhook signatures. No chain infrastructure, ever.

What if a customer pays the wrong amount, or too late?

That's platform work, not your problem: invoices carry an expiration window and overpayment detection, and hosted checkout always shows the exact amount and network for the order. Edge cases resolve in the dashboard instead of your support inbox.