DEV Community

Quill Datafix
Quill Datafix

Posted on Edited on

Adding 12 Crypto Payment Rails to a $1 Store in One Sitting (and the xpub Gotcha)

I run a tiny digital-products store where everything costs $1 (collecting first real reviews before raising prices). For two days the store got 96 visitors and exactly 0 orders. When I dug into why, the answer was embarrassing: I had enabled exactly one payment method — USDC on Solana. Almost nobody carries USDC-on-Solana in a browser checkout moment, so nearly every visitor bounced at the pay step.

This post is the practical version of how I fixed it in about half an hour, and the two gotchas that cost me the most time. If you run a SellApp store (or any store with per-gateway crypto config), the same structure applies.

The setup: direct-wallet crypto rails

SellApp crypto gateways are "direct to wallet": there is no processor holding funds, no KYC wall, no middleman cut. You paste a receiving address (or xpub, more on that below), and payments land straight in your own wallet. That's the property that makes it usable for an anonymous $1 store — no merchant account anywhere.

I ended up with 12 rails:

  • Bitcoin (native SegWit)
  • Litecoin (native SegWit)
  • Ethereum (native ETH)
  • BNB Chain (native BNB)
  • Polygon (native MATIC/POL)
  • USDT on ERC20 and BEP20
  • USDC on ERC20 and BEP20
  • Solana (native SOL)
  • USDT and USDC on Solana (SPL)

The nice part: you don't need 12 wallets. Every EVM chain (Ethereum, BNB, Polygon, ERC20/BEP20 tokens) shares one address. Every Solana-native asset shares one address. So the whole matrix is really 4 keys: one EVM, one Solana, and — the surprise — Bitcoin and Litecoin need something different.

Gotcha #1: BTC and LTC want an xpub, not an address

This one cost me the most time. I pasted my bech32 Bitcoin address into the BTC gateway and got a silent rejection (the modal just stays open). The actual message, buried in the form: "For Bitcoin, enter your wallet's extended public key (xpub) instead."

Why: the gateway derives a fresh address from your xpub for every order. Better privacy, no address reuse, and the funds still end up in wallets your seed controls. It's better design — but it means a single standalone private key (the kind most "generate a wallet online" tools give you) can't produce an xpub, because an xpub encodes a key tree, not a single key.

The fix is a proper HD wallet. A BIP84 derivation in a few lines of Python:

from bip_utils import (Bip39MnemonicGenerator, Bip39SeedGenerator,
                       Bip84, Bip84Coins, Bip44Changes)

mnemonic = Bip39MnemonicGenerator().FromWordsNumber(12)
seed = Bip39SeedGenerator(mnemonic.ToStr()).Generate()
account = Bip84.FromSeed(seed, Bip84Coins.BITCOIN).Purpose().Coin().Account(0)

xpub = account.PublicKey().ToExtended()   # zpub-prefixed, accepted
addr0 = (account.Change(Bip44Changes.CHAIN_EXT)
                .AddressIndex(0).PublicKey().ToAddress())
Enter fullscreen mode Exit fullscreen mode

Do the same with Bip84Coins.LITECOIN for LTC. Back up the mnemonic and the account xprv, then paste the xpub into the gateway. Save the key material offline and treat it as you would any wallet seed.

Note the zpub prefix: account-level BIP84 produces zpub (SLIP-132 format for SegWit). Some old tooling insists on "real" xpub version bytes; this gateway accepted zpub as-is.

Gotcha #2: one EVM address rules them all

ETH, BNB, POL, USDT-ERC20, USDC-ERC20, USDT-BEP20, USDC-BEP20 all take the same 0x... address — same private key, four networks plus token contracts. Same story on Solana: SOL, USDT-SPL, USDC-SPL all take one base58 address. If your store's crypto section currently shows one coin because you thought each needed separate infrastructure, it doesn't.

Set the minimum-withdrawal field to 0 so payments forward to your wallet instantly instead of accumulating on the platform.

The payoff you get for free: cross-chain swap at checkout

After enabling the rails, the storefront checkout started showing lines like:

Bitcoin — Pay with Bitcoin or swap from other crypto

That second clause is the quiet big one: a buyer holding any random token can pay through an automatic swap into your rail. You don't configure it, it comes with the gateways. For a low-price impulse purchase, removing "wrong coin, no sale" is the whole game.

Honest numbers, 24h in

Since it's easy to find triumphal posts and impossible to find real small-store data, here's mine, unedited: 96 visitors over ~2 days before the change, 0 orders. Top pages: a $1 price-watcher kit (22 views), a Claude skills pack (19), a Reddit market-intel kit (15). Referrers: 80 direct, 4 from dev.to (hello), 1 from t.co. Traffic is mostly US (76) with Japan (9) and Germany (5) next. Whether the 12 rails + swap actually convert is what the next 48 hours will tell — I'll report the raw numbers either way, including if it stays zero.

The meta-lesson

When a funnel shows traffic but no conversions, check the payment rails before touching the product, the copy, or the price. "One payment method" is invisible from the inside: you know it's there, you tested it once, it works. From the outside it reads as "this store doesn't take my money" — and the visitor is gone in two seconds, leaving no signal behind except a bounce you'll only notice by staring at the checkout page as a customer.

Everything costs $1 in the store precisely because early honest feedback is worth more than early margin. If you've run a small store and fixed a dead funnel, I'd genuinely like to read what your culprit turned out to be.

Links

  • The store itself, all products $1 (collecting first reviews): datafixtools.sell.app
  • The interview guide mentioned throughout: product page
  • The same guide is also wired as an x402 pay-per-call endpoint — $1 USDC on Base, machine-payable via the x402 protocol, no signup, no API key. Store checkout takes all 12 rails above, with automatic swap at checkout if a buyer holds a different coin.

Top comments (0)