Add wallet support to crypto checkout with hosted checkout, plugins, or an API fallback. Cover mobile handoffs, secure requests, and gasless options.
Support injected wallets, WalletConnect sessions, deep-link URIs and QR codes, and a hosted checkout, in that order of priority, and add gasless sponsorship where your contracts allow it. For most online stores, the fastest route to live wallet support is a hosted checkout page with an API fallback for custom flows. This combination covers desktop and mobile shoppers without demanding a long engineering project.
TL;DR:
- Support injected wallets for desktop, WalletConnect for mobile handoffs, and deep links or QR codes, while keeping a visible address and network fallback.
- Use BIP 21 style payment requests with HTTPS endpoints; avoid deprecated BIP70, which adds certificate management and server signing overhead for merchants.
- Sponsor gas where you control the contracts, but fund relayers, add rate limits, and let customers pay their own fees on unsupported chains.
- Auto convert volatile receipts to fiat or stablecoins, and use order metadata plus verified webhooks to match payments without manual block explorer checks.
Shoppers reach your checkout from different devices with different wallet setups, so one connection method never covers everyone. Supporting a layered set of options keeps the payment screen from becoming a dead end.
Graceful degradation matters here. When a shopper’s wallet does not support WalletConnect or the deep link fails to open an installed app, a visible fallback keeps the sale alive instead of forcing an abandoned cart.
Payment requests only work reliably when they follow formats that wallets already know how to parse. Following BIP21 and EIP-681 style URIs lets you encode the recipient address, amount, and network identifier directly into a link or QR code, and most wallets support these formats as a basic fallback for prefilled payments, according to the Bitcoin developer guide.
What to implement:
What to avoid: BIP70, the original payment protocol that added signed, certificate-backed payment requests, is deprecated. The Bitcoin developer guide on payment processing notes that BIP70 carries security and implementation flaws, and recommends migrating to BIP21-style URIs with secure HTTPS fallbacks instead.
One source worth noting: payment requests transmitted without HTTPS are exposed to man-in-the-middle address substitution, and the same Bitcoin developer documentation warns that private keys should never be stored on a public web server.
Signed payment requests, the x509-certificate-based approach BIP70 used, require certificate management and server-side signing keys. That operational overhead is a large part of why simpler, URI-based fallbacks remain the dominant pattern for most merchants today.
Asking a customer to hold a separate native token just to pay network fees is one of the clearest conversion killers in crypto checkout. A shopper who wants to pay in a stablecoin but has no ETH for gas will often abandon the purchase rather than go buy a small amount of a token they will never use again.
Pro Tip: Run gasless sponsorship as a small-scale test on one product line before rolling it out store-wide, so you can see real funding costs before committing to it everywhere.
The integration model you pick determines how fast you launch and how much custody responsibility you take on.
Once a wallet payment lands, it has to turn into something your bookkeeping can use. Two decisions shape that process: whether you hold the crypto or convert it, and how you match each transaction back to an order.
Tax and reporting rules for crypto income differ by country and change over time, so treat the technical reconciliation setup as separate from the tax question and loop in your finance or tax advisor on how receipts should be classified and reported. Our processing overview covers how settlement options connect to these reconciliation details for merchants comparing providers.
Wallet payments remove card-network fraud protections, so the security work shifts to the integration itself. A few controls cover most of the risk.
Pro Tip: Write a short help-desk script for “wrong network” and “payment not detected” errors before launch. These two issues account for most wallet checkout support tickets.
Shipping wallet-enabled checkout does not require a long build when you sequence the work correctly.
| Checklist step | Fastest path | What it solves |
|---|---|---|
| Integration model | Hosted checkout or plugin | Live wallet support without a long build |
| Wallet flows | Injected, WalletConnect, QR/deep link | Covers desktop and mobile shoppers |
| Fee handling | Gasless sponsorship where supported | Removes the native-token purchase step |
| Settlement | Auto-convert to stablecoin or fiat | Reduces volatility and accounting work |
| Reconciliation | Webhooks and order metadata | Matches payments to orders automatically |
We built our hosted checkout and WooCommerce plugin around exactly this sequence, with no-KYC onboarding so merchants can move from signup to a live payment link without a lengthy approval process.
Wallet friction costs sales long before a customer ever sees a price. Every extra tap, every confusing network prompt, every “I don’t have gas” moment is a chance for someone to close the tab. Supporting the common connection flows and removing the gas-token requirement are two of the simplest changes with an outsized effect on checkout completion.
We built our own payment gateway around that same instinct: no-KYC onboarding, support for a broad range of cryptocurrencies, and tiered fees that decrease with higher volume. Merchants weighing whether wallet support is worth the engineering time should treat it as a reach and conversion question first, and a technical one second.
— Dustin
We built our gateway so you can add wallet support without the engineering timeline a custom build usually takes. Our hosted checkout covers the connection flows described above out of the box, and our WooCommerce plugin gets a storefront accepting wallet payments in a short install rather than a sprint.
If your integration needs go beyond a standard storefront, perhaps a fully bespoke payment architecture built into internal systems, partners like Bitecode build modular blockchain payment components for exactly that kind of custom engineering work.
Start by setting up your account and generating a test payment link, or install the WooCommerce plugin if that is your platform, and have a working wallet checkout live the same day.
There is no single best wallet for every shopper, since the right choice depends on the device and network the customer already uses. For checkout purposes, supporting multiple connection methods, injected wallets, WalletConnect, and QR/deep links, matters more than picking one wallet brand to favor.
Tax authorities’ visibility into wallet activity depends on each country’s own reporting rules and varies widely by jurisdiction, so this is a question for a qualified tax advisor in your specific country rather than a general rule. Merchants should keep clean, exportable transaction records through their payment processor so that question is easy to answer when it comes up.
Standard PayPal checkout is built around cards and bank-linked balances rather than direct wallet-to-wallet crypto payments at checkout. Merchants who want shoppers to pay from an external crypto wallet need a dedicated crypto payment gateway that supports wallet connection methods like WalletConnect and QR codes.
The fastest way is a hosted checkout page from a payment gateway, which handles wallet connection, confirmation, and settlement without a custom build. We offer a hosted checkout with no-KYC onboarding, flat per-payment fees starting from a low amount, and support for a broad range of cryptocurrencies for merchants who want to launch quickly.
Open a free CryptoPayr account and take your first crypto payment the same day.
Get started for free
Cut crypto checkout fees and reduce abandonment with five changes you can ship in a sprint, from fee visibility to gas sponsorship and payout routing.
Merchant playbook to hedge crypto payments and keep treasury liquid: auto convert, staged stablecoins, routing, FX hedges, and no KYC onboarding.
Developer focused roadmap to accept Stellar payments via four integration routes. Includes a production checklist, trustline guidance, and a CryptoPayr...