How ecommerce crypto payments work, what they cost, how to handle tax and refunds, and how to integrate and test them before you launch your store.
Ecommerce crypto payments let a customer pay your online store with Bitcoin, Ethereum or a stablecoin such as USDT or USDC. Your checkout shows a payment request with a wallet address or QR code, the buyer approves it from their wallet, and your store marks the order paid once the network confirms the transfer. To run this well you need a payment gateway, a clear plan for converting or holding what you receive, and a tax and refund process written down before the first sale.
This guide walks through the mechanics, the costs, the rules to check in the US, and a launch checklist you can follow this week.
A crypto payment in ecommerce is a transfer of a digital asset from the customer’s wallet to an address tied to the merchant. According to Chainlink’s explanation of stablecoin ecommerce payments, the checkout generates a unique payment request showing the total in a chosen stablecoin and a destination address. The buyer connects a wallet or scans a QR code and signs the transaction. The network validates the transfer, usually within seconds or minutes, and the store’s backend then flips the order to paid and starts fulfillment.
In practice, you rarely build this yourself. A gateway sits between your store and the blockchain and does four jobs:
The buyer never shares card details with you. That changes your risk profile, but not every obligation, as the compliance section below explains.
You do not need to accept everything on day one, but you do want the coins your buyers already hold.
The Kansas City Fed notes that Congress recently passed the GENIUS Act, a framework for issuing stablecoins, and that stablecoins may suit payments better than coins whose value swings sharply, such as Bitcoin. That matches how most stores approach it: offer a broad menu, nudge buyers toward stablecoins, and auto-convert the rest. We cover the stablecoin route in more detail in our guide to accepting stablecoin payments in the U.S. and on our USDT and USDC page.
The case is practical, not ideological.
Treat these as reasons to try it, and measure the share of orders that use it after launch.
Card acceptance typically bundles several fees into one percentage. Crypto gateways usually charge a single processing fee, plus the network fee the buyer pays to send funds.
Our own pricing is volume-based. The fee falls as your monthly transaction volume grows:
| Tier | Fee |
|---|---|
| Standard | 2% |
| Growth | 1.5% |
| Scale | 1% |
| Enterprise | 0.1% |
If you prefer predictable costs on small tickets, there is also a flat fee of $0.10 per payment, described on our gateway page. We state that there are no setup or monthly fees. White-label deployments start from 1%, covered on the white-label page. Full details are on the pricing page.
Two cost lines sit outside the gateway fee, so put them in your model:
Because a confirmed transaction cannot be reversed by a bank or card provider, you control refunds. That is a benefit for friendly-fraud cases and a responsibility for honest returns. Decide these points in writing:
On volatility, the simplest policy is to price in dollars, lock the rate at checkout, and auto-convert to a stablecoin. Then the dollar value you invoiced is the value you hold.
This is the part stores skip, and it is where problems start. Three things to check.
Tax treatment of what you receive. Rules differ by country. A Slovak law firm explains that an e-shop which keeps crypto instead of converting it creates a further taxable event with every later transaction, which is a heavy administrative load at scale. That example is from Slovakia, not the US, but the principle carries: holding crypto means tracking it. For US stores, our sales tax on crypto payments guide covers what merchants must do, and your CPA should confirm treatment of income and gains for your entity.
Card-data obligations still apply to the rest of your store. BigCommerce’s support team points out that crypto transactions are irreversible and fraud-resistant, yet merchants remain responsible for PCI compliance for any payment information their store accepts, transmits or stores. If you sell in multiple languages, your payment-security and refund documentation should be translated accurately too; precise PSD2 and PCI DSS documentation helps keep policies consistent across markets.
Custody. If you hold meaningful balances, decide who holds the keys. Holding on an exchange adds counterparty risk, and a CPA quoted by Forbes has advised that businesses with significant holdings consider self-custody with hardware wallets. The simplest operational answer for many stores is to auto-convert and withdraw on a schedule.
There are five common routes. Choose by how much engineering time you have.
| Route | Best for | Effort |
|---|---|---|
| Ecommerce plugin | Stores on a hosted or open-source cart | Low |
| Hosted checkout | Any site that can redirect to a payment page | Low |
| Payment links | Invoices, social sales, one-off orders | Very low |
| API | Custom builds and apps | Higher |
| White-label | Platforms that want their own branded gateway | Higher |
We support all of these. Our crypto payments for ecommerce page shows the plugin and hosted options, and our walkthrough on accepting Bitcoin payments on your website goes step by step.
The same gateway behaves differently depending on what you sell.
Our perspective
We see the same pattern in stores that succeed with crypto: they treat it as a normal payment method with clear policies, not an experiment. They price in dollars, take stablecoins first, and let the gateway handle conversion so the finance team sees familiar numbers.
We built CryptoPayr for that kind of merchant. Onboarding is without KYC and approval is instant, so a store can be taking test payments the same day. There are no setup or monthly fees, and the processing fee falls as volume grows. Because we operate as a regulated MSB, merchants get a gateway with a clear legal footing rather than a loose wallet script.
Our advice is simple. Start with one plugin or payment link, accept a short list of coins, run every test case before you announce it, and write your refund policy first. Then let the numbers tell you whether to widen the menu.
Dustin
If you want to move from reading to selling, CryptoPayr gives you hosted checkout, ecommerce plugins, payment links and an API, with 110+ cryptocurrencies including Bitcoin and Ethereum, auto-conversion to stablecoins, and no KYC onboarding. Fees start at 2% and fall to 0.1% as your monthly volume grows.
See how it fits your cart on our ecommerce crypto payments page, or create an account from cryptopayr.com.
No. You can choose auto-conversion to a stablecoin so your balance stays in dollar-pegged form. That keeps price swings away from your books and simplifies tracking.
A confirmed on-chain transfer cannot be reversed by a bank or card provider. Returns are handled by your own refund policy, which is why you should publish it before launch.
Most stores start with USDT and USDC, then add Bitcoin and Ethereum because buyers recognize them. Stablecoins keep the invoiced amount steady, so reconciliation is easier.
Crypto you receive for goods is business income, and later disposal can add further tax events depending on your country and how long you hold it. Ask your CPA how it applies to your entity, and see our guide on sales tax on crypto payments.
Open a free CryptoPayr account and take your first crypto payment the same day.
Get started for free
How crypto payments work in a Shopware 6 store, what to compare in a plugin or gateway, and how to handle refunds, underpayments and order statuses.
Crypto payouts help businesses pay global vendors, creators, and customers faster with lower fees, direct wallet delivery, and flexible stablecoin control.
A crypto payment gateway lets businesses accept digital assets, settle with more control, reduce payment friction, and automate payouts worldwide, easily.