August 22, 2026
How to Accept Cryptocurrency Payments in Your Online Store: What Actually Changes
Read article
Adding crypto to a store that already works costs you two fees, not one. The gateway takes its rate, and your platform charges you for using a payment provider that isn't its own. They stack. On Shopify Basic, a gateway charging 1% costs you 3% per payment, because Shopify adds 2% for any third-party provider. The same order on a card costs 2.9% plus 30¢.
Which sets up the sharpest thing on this page: on Shopify, your plan decides whether crypto saves you anything at all. Native USDC is priced exactly like a card, so by itself it saves nothing. On Basic, a third-party gateway lands at the card price too, because the platform's 2% eats the whole difference. From Grow upward that cut falls to 1%, then 0.6%, then 0.2%, and the same gateway comes out 33–57% below the card rate. Off Shopify, where no platform takes a cut at all, the gap is widest — as long as you take your payouts in crypto.
What breaks in checkout: nothing, if crypto sits as one more button next to the card form. What changes is everything after the click. An order counts as paid when the network confirms it, not when the buyer writes "I've sent it". Every refund becomes an outbound transfer you send by hand. And the rate you were quoted only buys the acceptance of the money — taking it out of the account has its own price.
Below: availability, your platform's share, one order costed end to end, and the rules to write before launch. Figures as of 11 August 2026.
The region list is the first filter. Shopify Payments takes USDC — a dollar-pegged stablecoin — only in the United States except Alaska, New York and Texas, in Mexico, in most of Europe and in Hong Kong. Registered outside that list, your native path is closed. The crypto paths of Stripe and PayPal close the same way: Stripe's is generally available to US businesses and in private preview only for the EU, Hong Kong, Mexico and Switzerland, and PayPal's Pay with Crypto is open to US merchants outside New York — so if your business sits outside those lists, check what Stripe's crypto support actually covers before you plan around it. Outside those lists there is no access at all, and the platform fork below is your map.
The EU refund rule is the second, and it is narrower than it looks. Directive 2011/83/EU, article 13(1) governs one situation: the consumer withdraws from a distance contract. Then the trader reimburses all payments received within 14 days of being informed, using the same means of payment the consumer used — unless the consumer expressly agrees to another means and bears no cost for it. Article 16 carves out goods made to the consumer's specification, and digital content, but only where performance began with his express prior consent and his acknowledgment that he thereby loses the right of withdrawal. A store selling keys that never collects that acknowledgment still owes the refund. (EU, as of the date above. Not legal advice: faulty-goods returns run under a different directive.)
Forget which gateway is best. The platform you already run sets both the path and the price.
Shopify Payments accepts USDC natively, on Base, Ethereum L1, Optimism, Polygon and Arbitrum. Its rate is published on the same pricing page as everything else, and it is the card rate of your plan: 2.9% + 30¢ on Basic, 2.7% + 30¢ on Grow, 2.5% + 30¢ on Advanced. No third-party surcharge applies there, because the payment goes through Shopify Payments. The constraints work as operating rules:
Put a third-party crypto gateway on Shopify instead and you get bitcoin, more assets and more networks. You also get a surcharge on every payment that bypasses Shopify Payments: 2% on Basic, 1% on Grow, 0.6% on Advanced, 0.2% on Plus.
WooCommerce says it on its own crypto page: it doesn't provide crypto services, and it publishes no fee figures. The plumbing is a plugin, so the plugin is what you inspect — though taking crypto on WooCommerce without a plugin is possible too.
In the WordPress.org catalogue, crypto payment plugins for WooCommerce run from a few dozen active installs to 8,000+, most of them in the hundreds and low thousands. The WooCommerce PayPal Payments plugin holds more than 800,000 — two orders of magnitude between the ecosystem you are used to and the one you are joining.
The largest crypto plugin has 8,000+ installs and was updated on 31 July 2026 against WordPress 7.0.3. Its free tier stops at five sales a month, so the moment the method works, you are on a paid plan. Two others declare compatibility only up to WordPress 6.9.6 and 6.8.7 against a current 7.0.3. None of that makes a plugin bad. It makes three checks mandatory: last update date, tested-up-to version, free-tier ceiling.
If your store already takes PayPal, it's fair to ask whether PayPal could take the crypto instead of a separate plugin. As of September 2026, PayPal's Pay with Crypto is open only to US merchants outside New York with a verified PayPal Business account and approved Expanded Checkout, and since 1 August 2026 it charges 1.5% per payment and pays you in dollars rather than coins. Whether that fits your store depends on where PayPal accepts crypto payments and what to do if your business doesn't qualify.
Search your own platform's catalogue for "crypto", "USDT" and "bitcoin" before you plan anything. An empty result leaves exactly one path, and it is not a plugin: a hosted payment widget or the gateway's API, plus developer time.
Ask for that work as a list. CryptumPay integration works through the widget or the API, your domain has to be added to the project before anything works, and charging a fixed order amount requires a call from your server. Those are the line items to put in front of a developer, along with an invoice per order and a status callback handled.
What justifies the one-off bill is the arithmetic below: off Shopify, with payouts taken in crypto, the net saving against card acquiring runs about $5 to $15 on every $1,000 of crypto orders. Divide the developer's quote by that and you have the turnover at which the work pays for itself. If you plan to convert every payout to bank money, run the sum again on the numbers below before you commission anything — the saving mostly goes away.
Through a third-party gateway on Shopify, add the two rates together. A gateway charging 1% on Basic costs you 3% per payment: 1% to the gateway, 2% to Shopify. The card on the same plan is 2.9% + 30¢, or $3.20 on a $100 order. So crypto saves you twenty cents. On a $30 order the card takes $1.17 and crypto takes 90¢. That gap is almost entirely the fixed 30 cents: the cheaper your average order, the better crypto looks.
Your own plan line, with a 1% gateway:
Now the same arithmetic as a warning. Market gateway rates span 0.4% to 2% per successful payment, and a 2% gateway on Basic means 4%. That beats the card only on orders under about $27, where the fixed 30¢ still dominates. Above $27 you pay more than you pay today, on every order.
Off Shopify there is no platform cut, and the saving is real — on one condition, which is where you take the money out. A 1% gateway stands against card acquiring at 2.5–3.5%, or up to 5% through an aggregator. Keep your payouts in crypto and the net lands around 0.5–1.5% of turnover, those $5 to $15 per $1,000. Convert every payout into bank money and the saving mostly evaporates, as the chain below shows. For orientation, CryptumPay charges 1% per successful payment, from 0.5% at volume, and the fee can be passed to the customer.
The whole chain, on one order. A $100 order on WooCommerce, paid in USDT on TRON, at a 1% gateway. The buyer's wallet pays the network fee: about $2.08 to an address that has held USDT before, about $4.16 to a fresh one — his money, not yours. The gateway takes $1 and credits you $99. Moving it out costs 0.5% plus a flat 0.50 EUR in crypto, or 1.5% plus that same flat fee when it converts to bank money. All in: about $2.05 on that order staying in crypto, about $3.04 converting. Hold those two next to card acquiring at 2.5–3.5%. The $2.05 beats a card everywhere. The $3.04 sits inside the card band itself — about half a point better than a 3.5% acquirer, about half a point worse than a 2.5% one. On Shopify Basic, add the platform's 2% at the front of either. And ask about a monthly minimum before you sign anything — one large provider switches on $1,000 a month whenever quarterly turnover falls below $90,000.
Network fees are a commercial decision as much as a technical one. ERC-20 runs $0.40 to $15 depending on load, BEP-20 sits at $0.10–0.30, and the cheap-as-cents reputation of TRC-20 is years out of date. On a $30 order a $4 fee is a 13% surcharge your customer will notice. On Shopify's native USDC checkout the gas is sponsored and he pays nothing extra. The market-wide picture of rates and payout tariffs belongs to the guide on accepting bitcoin and crypto on your website; the fee mechanics are in how crypto network fees work.
In what currency. You hold whatever the buyer paid, unless the provider converts it at crediting into your settlement asset: the single asset your balance is denominated in, usually a dollar stablecoin. Both models are common, and the setting is yours. On Shopify's native path the same choice appears as your payout method, and it decides which balance refunds come out of.
At whose rate. If it converts, it converts at the provider's rate at the moment of crediting, and that spread sits nowhere in the percentage you were quoted. Ask which rate source the provider uses, then check one real payout against a public quote in your first week.
When you can spend it. The balance moves when the payment is credited — the same moment your order becomes paid. How fast it reaches your bank is the payout schedule, not the blockchain, so settle that in the same conversation as the payout fee.
The invoice holds a rate for about 15–30 minutes, with 15 the common setting. Then it expires, and an expired invoice is a normal status: the buyer opens a new one at the current rate. Money arriving after expiry does not vanish either. It lands in a status of its own, and the provider either sends it back or credits it by hand — ask which, before launch.
The order is paid on network confirmation. For Bitcoin that is roughly six confirmations, about an hour. That hour is Bitcoin's alone. For a stablecoin on TRON or an L2 there is no published figure to give you: the wait is set by how many confirmations your provider requires on that network. Get the threshold per network in writing and build the shipping rule on it.
The release rule, stated. Ship or unlock on the final state — the one where the provider says the money is yours. Never on "transaction seen", and never on a screenshot. States run in a predictable sequence: on CryptumPay, for instance, created → pending → crediting → finished, with underpayments and overpayments settled automatically. Your warehouse picks from the last state; everything before it is a payment still in flight.
Underpayment and overpayment are routine. A buyer sends slightly less because his wallet took the fee out of the amount, or slightly more by rounding. A competent gateway handles both automatically and returns the difference, so these never reach your reconciliation.
The failure you will actually see is a buyer holding enough USDT and no native coin for the gas — the network's own fuel — or a payment sent on a network you don't accept. Both are checkout-design problems with known fixes: see how to reduce failed crypto payments and, for the gas problem, gasless USDT.
A crypto payment cannot be reversed. Every refund is a new transfer that you send, and three decisions have to be made once, in advance.
How much: everything the customer paid. The full order amount, with no deduction for the gateway's cut. In the EU that is the norm's plain instruction — reimburse all payments received from the consumer. Elsewhere, netting your 1% out of a refund is the kind of saving that costs you a public review. Work in the currency the order was priced in: he paid a hundred dollars' worth and gets a hundred dollars' worth, with the coin count following the rate on the day you send it.
In what asset: the one he paid, where you still hold it. That is the cleanest reading of "the same means of payment". When you settled into something else and no longer hold his asset, refund in your settlement asset — with his express agreement, which the directive allows as long as it costs him nothing. Take that agreement in the same message where you collect his wallet address. On Shopify's native path the asset is decided for you: USDC.
Who pays the network fee: you. In the EU that follows from the norm, since the consumer must bear no cost for the reimbursement. Elsewhere it is a policy choice, and a refund arriving $4 light is a support conversation nobody wants twice.
One habit worth building: read the refund address back to the customer before sending. Money sent to a wrong address is gone, and there is no bank to call.
It is true, and genuinely valuable if you sell digital goods or software keys. A confirmed blockchain transaction does not get pulled back weeks later by a card network, and on Shopify's USDC path the customer cannot open a dispute at all.
The other half is that your buyer loses his protection mechanism too, and he knows it. The dispute doesn't disappear. It stops going to Visa and starts going to your support inbox, where there is no arbitrator and no ruling. Whatever you decide is the outcome.
So the risk is moved, not removed: out of a rules-based process you don't control, into a policy-based one you do. Good trade for a store with a written refund policy and someone answering email. Worse trade without them, because your first unhappy crypto customer becomes a public review instead of a chargeback.
Yes, if: you sell digital goods or subscriptions, you sell internationally, card declines from abroad are costing you orders, or customers are actually asking. Crypto recovers orders you are otherwise losing outright.
No, if: you sell locally to customers who pay by card and nobody has asked. That is a payment method, a policy and a support scenario bought for zero extra orders.
Only with preparation, if: you ship physical goods. You need the confirmation threshold for each network in writing, a release rule tied to the final state, and the refund rule agreed before launch.
And by platform: native USDC on Shopify is the same published rate as a card, and a gateway on Basic lands near it too — take it there for the orders it recovers rather than the fees it saves. From Grow upward a gateway is 33–57% below the card rate. Off Shopify it is the cheapest method you have, provided the money leaves as crypto; convert every payout to bank money and you are back inside the card band, with the monthly minimum still to pay.
Will adding crypto break my current checkout?
No, if you add it as one more option beside the card form. Card processing is untouched. What changes is behind the order: paid status now depends on network confirmation, and every refund becomes an outbound transfer you send by hand.
Does Shopify accept bitcoin?
Not natively. Shopify Payments takes USDC only, on Base, Ethereum L1, Optimism, Polygon and Arbitrum, in the US except Alaska, New York and Texas, plus Mexico, most of Europe and Hong Kong. Its USDC rate matches the card rate of your plan. To accept BTC you need a third-party gateway, and Shopify then adds its provider fee — 2% on Basic, down to 0.2% on Plus.
When do I ship an order paid in bitcoin?
After the network confirms it: roughly six confirmations, about an hour. Ship on the state where your provider calls the payment final, never on a screenshot. For a stablecoin on a faster network the threshold is your provider's to state, so ask for it per network.
A customer paid after the invoice expired. Where is his money?
Not lost. A late payment gets its own status, and the provider either returns it to the sender or credits it manually against the order. Which of the two happens is a provider setting, so find out yours before launch and tell support what to say.
Create an account and connect the checkout yourself, or talk to sales and we will plan the integration with you.
