Learn how to sell digital goods for crypto: pick a payment model, automate delivery, handle fees, refunds and taxes, and start accepting Bitcoin and more.
To sell digital goods for crypto, you need three things: a way to quote a price and generate a payment request, a way to confirm the payment on the blockchain, and a way to deliver the file, license key or account access once it is confirmed. A crypto payment gateway handles all three, so you don’t have to run blockchain nodes or watch wallets by hand. This guide covers how to choose between a gateway and a direct wallet, how to automate delivery safely, what the fees and delays look like, and how to deal with refunds, underpayments and taxes.
A physical product has to be packed, shipped and sometimes returned. A digital product is a file, a key or a login, and it can be delivered in seconds. Crypto payments are also settled in minutes, not days, and they don’t depend on the buyer’s country or bank. For ebooks, templates, software licenses, courses, game items, stock photos and SaaS plans, the two work well together.
There is a practical reason sellers add crypto as well. Some buyers keep a stablecoin balance and prefer to spend it directly. Others live in places where cards are declined or restricted. Offering crypto as one more option, next to cards, widens the group of people who can complete a purchase. It rarely replaces your existing checkout.
The first decision is how the money reaches you. A CoinDesk merchant guide from June 2026 describes three operating models: processor-led acceptance, direct-wallet acceptance and a hybrid. The right one depends on which asset you want to end up holding, how much volatility you can tolerate, and how much of the operational work you want to own.
You publish an address, the buyer sends coins, and you check your wallet. It costs no processing fee beyond the network fee the buyer pays. The trade-offs are real, though. Cobo’s merchant guide notes that direct wallets require manual matching of payments to orders, security and backups, and compliance work. You also carry the price risk and have to handle every refund yourself. For a store that sells ten items a month, that can be fine. For an automated catalog, it quickly becomes a chore.
A processor gives you a hosted checkout, a fresh address for every order, status tracking, plugins for common stores and the option to convert to a stable asset. The same Cobo guide lists the costs: processing fees, third-party custody during settlement and possible geographic restrictions. For most digital sellers the trade is worth it, because the order is matched to the payment automatically and your delivery logic can hang off a status change.
Many sellers split the flow. Small, frequent payments go through a processor with automatic conversion. Larger or recurring buyers can pay a wallet directly. This keeps the checkout simple while letting you hold some assets you actually want.
| Direct wallet | Payment processor | |
|---|---|---|
| Setup effort | Low to start, high to scale | Low, usually a plugin or API key |
| Order matching | Manual | Automatic, per-order address or invoice |
| Delivery automation | Requires custom code | Webhooks or plugin handles it |
| Price risk | You hold what you receive | Optional conversion to stablecoins |
| Refunds | Manual, from your own wallet | Handled through dashboard or API |
| Processing fee | None, only network fees | Percentage or flat fee per payment |
| Control of funds | Full | Depends on settlement setup |
The core rule is simple: payment confirmation triggers delivery, and confirmation means more than the buyer saying they paid. Bitcoin’s developer documentation on payment processing recommends a separate address for each payment request, tied to the order, so you can tell which payment belongs to which purchase. It also advises sending payment requests over HTTPS and keeping private keys off your web servers.
Confirmations are the other half. The same documentation says zero-confirmation payments generally should not be trusted without some risk analysis, and that high-value or fraud-prone transactions should wait for at least six confirmations. For a $9 template you might accept one confirmation, or even a fast-network payment, because the loss from a failed payment is small. For a $900 software license or a bulk game-currency purchase, wait longer. Match the confirmation threshold to the cost of being wrong.
A workable delivery flow looks like this:
Because a webhook can be sent more than once, make the delivery step idempotent: the same event should never issue two licenses.
The plumbing changes with what you sell. Here is how it typically looks for each seller type.
If you sell downloads on WordPress, a plugin is the quickest route. Our Easy Digital Downloads crypto gateway adds crypto as a payment method inside the cart you already use. For broader store setups, see our overview of crypto payments for e-commerce.
No store needed. Send a payment link or invoice in your quote, in dollars, and the client pays in the coin they hold. The link shows a status page, so you know when work can begin or final files can be released.
Crypto does not pull money from a wallet like a card does, so recurring billing works through invoices: a new payment request is issued each cycle and the customer pays it. That sounds like a drawback, but it helps when cards fail or customers lack one. We cover the mechanics in crypto payments for SaaS.
Game servers and apps usually use the API: create an invoice tied to a player ID, wait for the webhook, and credit the item or currency automatically. Keep the confirmation threshold low for small items and higher for expensive bundles.
When many sellers share one checkout, you need to split each payment between the platform and the seller, and pay sellers out in bulk. That is commission splitting and mass payouts, which we describe on our page for crypto payments for marketplaces and platforms.
There are three kinds of cost to keep apart.
Settlement speed depends on the network. Some chains confirm in seconds, others take ten minutes or more per block. If your product is instant, choose which coins to show first on the checkout page accordingly. Our post on optimizing crypto checkout covers fees and abandonment, and the supported coins page lists what you can offer.
This is where most first-time sellers get surprised, so write the rules down early.
Underpaid or overpaid invoices. Buyers sometimes send slightly less because of network fees deducted from their wallet, or more because of a rounding choice. Decide a tolerance, for example accept small shortfalls and flag larger ones for a top-up request. Do not release the product for a partial payment unless you chose that on purpose. Crypto.com’s merchant docs, for instance, mention late and mismatched payments as a standard case that merchants must handle.
Late payments. An invoice quotes an exchange rate for a limited window. If the buyer pays after it expires, the amount may no longer match the dollar price. Set a clear expiry, and give the buyer a way to request a fresh quote.
Refunds. Crypto transfers are irreversible, so there are no chargebacks, which protects you from card-style disputes. It also means a refund is a new payment you send. Refund to the address the payment came from or one the buyer confirms, decide whether you refund the dollar value or the coin amount, and say so in your policy. Exchange-originated payments sometimes come from a shared address, so ask the buyer for a refund address.
Volatility. If you hold what you receive, your revenue moves with the market. If you would rather not, convert to a stablecoin on settlement. The research behind the CoinDesk guide frames this as the core choice: the settlement asset you want, and the volatility you can accept.
Security. Keep keys off web servers, use HTTPS, verify webhook signatures, protect your dashboard with two-factor authentication and limit who can trigger payouts.
Tax rules depend on where you operate, and this is general information, not advice. For anything specific, talk to a CPA or tax attorney who works with digital assets.
In the United States, the IRS treats virtual currency as property. Under IRS Notice 2014-21, a taxpayer who receives virtual currency for goods or services includes its fair market value in U.S. dollars, measured at the time of receipt, in gross income. In practice, record the dollar value of every sale at the moment it confirms. Your gateway’s records help here. If you later sell or swap the coin you received, that can create a separate gain or loss, as the IRS describes in its 2020 material on virtual currency. Converting automatically to a stablecoin at settlement keeps that second step small.
Sales tax on digital goods varies by state, and we go through the practical steps in sales tax on crypto payments. If you sell to buyers abroad, other rules may apply. In the UK, for example, HMRC guidance says VAT is due in the normal way on goods or services sold for crypto, valued at the pound sterling value of the tokens when the transaction takes place. Check the rules of each market you sell into.
We see the same pattern with digital sellers. The ones who succeed with crypto don’t treat it as a novelty button. They treat it as one more payment rail with its own rules for confirmation, conversion and refunds, and they automate each of those from day one.
Three choices matter most. First, keep onboarding light: a merchant who can start accepting payments the same day, with no setup or monthly fees, is a merchant who actually tests the idea. Second, hold as little price risk as you can stomach, since most digital sellers want revenue in dollars, not a bet on a coin. Third, make delivery depend on a confirmed status and nothing else. Those three choices remove most of the headaches people associate with crypto.
We built CryptoPayr around them: no KYC for merchants, instant approval, hosted checkout, plugins and API, and settlement and reconciliation designed so that a finance person can follow the trail. We operate as a regulated MSB.
— Dustin
If you want the processor route, CryptoPayr lets you accept 110+ cryptocurrencies, including Bitcoin and Ethereum, through hosted checkout, payment links, plugins and an API, with optional auto-conversion to stablecoins. Fees are tiered by monthly volume, or flat at $0.10 per payment. See the plans and set up your account on the CryptoPayr homepage, or read how crypto processing works for your stack.
If you run a marketplace or want your own branded checkout, our white-label option lets you offer the gateway under your own name, with fees from 1%.
Selling for crypto usually uses the same business registration you already have for fiat sales. Your obligations around income, sales tax and record keeping still apply, and they depend on your state and country. A tax professional can tell you what your situation requires.
Yes, though not like card auto-billing. The gateway issues a new invoice every billing cycle and the customer pays it, usually after an email reminder. Some SaaS sellers find this works better than cards for customers whose cards fail or who don’t have one.
It depends on the order value and the network. Bitcoin’s developer guidance says high-value or higher-risk payments should wait for at least six confirmations and that unconfirmed payments carry risk. For small downloads, many sellers accept fewer confirmations or use faster networks.
Set a tolerance in advance. Small shortfalls caused by network fees can be accepted, while larger ones should keep the order pending and trigger a request for the difference. Overpayments are typically refunded or credited to the buyer’s account.
Yes. Price your products in dollars and convert the payment to a stablecoin at settlement. You then hold a dollar-pegged balance rather than a volatile coin, though conversion has its own spread and processing costs.
Open a free CryptoPayr account and take your first crypto payment the same day.
Get started for free
What a self-hosted crypto gateway is, what it takes to run one, what it costs, and when a hosted or white-label gateway is the smarter choice for your business.
What zero confirmation crypto payments are, why they stall, the double-spend risk, and a practical way for merchants to decide when to accept one and when to wait.
A crypto payment arrived short of the invoice. Learn why underpayments happen, how to verify them on-chain, and how merchants can fix and prevent them.