Accepting crypto adds a checkout path that settles without card rails and carries no chargebacks, but it sits near half a percent of eCommerce turnover today, so it earns its place with a specific audience rather than every store. This guide walks the checkout as your customer sees it, shows what happens when a payment lands short or late, explains how refunds work without chargebacks, and gives you a way to measure whether acceptance paid off. It is written for store owners choosing or changing a provider across the industries that Speend serves.
How to connect: platforms and plugins
Speend reaches your store through a plugin or the REST API, and integration runs about 24 hours with business verification alongside. WooCommerce has a published plugin; Shopify and Magento are supported through the same gateway; any other storefront, including a Bitcoin-first one, connects over the API. Plugin install takes under two hours, and KYB runs 1–3 business days in parallel.
| Platform | Status | How to connect |
|---|---|---|
| WooCommerce | Plugin published (v1.2.0) | Install the WooCommerce plugin |
| Shopify | Supported | Through the gateway |
| Magento | Supported | Through the gateway |
| Custom storefront | REST API | api.speend.io, hosted invoices and payment links |
The order of operations is short. You register the store, pass KYB with your business documents, generate the account keys, run a test payment against the sandbox, then switch the same setup to live. The sandbox mirrors production one to one, so the test order behaves exactly as a real one will, which is the cheapest place to catch a misconfigured webhook before a customer meets it.
The WooCommerce build fits both the classic and the block checkout and runs in two payment modes: Redirect, which sends the buyer to a hosted invoice, and On-site (host-to-host), which keeps them on your checkout. Shoppers pick the coin and network on the storefront with search, refunds go out in crypto from the admin, and order status stays in sync over webhooks, with a light and a dark theme. It needs WordPress 5.8 or newer, WooCommerce 6.0 or newer, and PHP 7.4 or newer with the curl and json extensions.
For a custom build, the REST API lives at api.speend.io, and hosted invoices and payment links let you take crypto without writing checkout code. Whichever path you pick, settlement is the same: funds land on your merchant balance in crypto, or auto-convert to a stablecoin the moment they arrive. The base fee starts at 0.5%, and auto-conversion is from 0% — 0% on Bitcoin, 1% on USDT and Ethereum — which matters once you start comparing crypto acquiring for your store against card processing.
The checkout as your customer sees it
At checkout the customer selects crypto, chooses a coin and network from a searchable list, and receives an invoice with a fixed amount and a countdown. The price they see holds for the life of that invoice, from 1 to 12 hours and two by default, so the exchange rate cannot move under them while they pay. That fixed window is the single most important thing to understand about a crypto checkout.
The buyer’s flow is four steps. They pick crypto as the method, choose the asset and network, get an invoice showing the exact amount, an address as text and QR, and the countdown, and then send from their own wallet or exchange. When the network confirms the transfer, your store marks the order paid and the buyer sees the confirmation like any other successful checkout. Nothing on your side is manual for a clean payment.
Two display modes shape what the buyer actually looks at. Redirect opens a hosted invoice page away from your site; On-site keeps the invoice inside your own checkout. On-site holds the shopper in your flow and tends to read as more trustworthy to a first-time buyer, while Redirect offloads the invoice page entirely; the choice is a small conversion decision worth testing against your own audience rather than assuming.
The coin and network choice is real, not cosmetic. The gateway lists 300+ coins across 18 networks, and a single asset can run on several rails: USDT alone is available on TRON (TRC-20), Ethereum (ERC-20), BNB Smart Chain (BEP-20), Polygon, and Solana. Networks differ in speed and in the fee the buyer pays to send, and that fee is shown for their choice before they confirm. Some networks settle in seconds, while Bitcoin on mainnet takes roughly 10 to 60 minutes. A buyer who wants confirmation fast picks accordingly, which is why the searchable list beats a fixed two-coin menu when you sell accepting crypto in eCommerce to a mixed audience.
You are not stuck with the whole list, either. The available coins and networks are yours to switch on and off from the dashboard, and the storefront reflects the change without a redeploy. A store that wants to avoid holding volatile assets can lean on stablecoins and pair that with auto-conversion at settlement; a store that wants the widest reach can leave more networks on. This is a menu decision, and it sits with you rather than with the buyer.
Underpayment, overpayment, and expiry
When a payment does not match the invoice, your store does not lose the order silently. Each case has a defined state you can see in the admin and act on: a short payment waits for the rest, an overpayment clears, and an expired invoice cancels and returns stock. Crypto removes card disputes, not the ordinary edge cases of getting paid, so these are the states worth knowing before launch.
| What the buyer did | What your store sees | What to do |
|---|---|---|
| Paid the exact amount | Order marked paid | Fulfill |
| Paid less than invoiced | Order waits for the remainder, a note is added | Buyer tops up, or you review the shortfall |
| Paid nothing before the window closed | Invoice cancelled, stock returned | Nothing; the buyer can re-order |
| Paid more than invoiced | Order marked paid | Fulfill, then handle the overage by your policy |
| Payment held by an on-chain screen | Order goes on hold | Wait for the check to clear, then fulfill |
The partial-payment state is the one that surprises new merchants. A buyer who sends less than the invoiced amount does not fail the order outright: the invoice notes the shortfall and waits, and topping up the difference completes it. An overpayment resolves the simple way, as paid. An untouched invoice that runs out its lifetime cancels on its own and puts the reserved stock back. A payment can also pause on an on-chain screen before it clears, which moves the order to on-hold until the check finishes rather than failing it.
Underpayments usually have a mundane cause. A buyer typing the amount by hand into a wallet mistypes it, or sends from an exchange that deducts its withdrawal fee from the transfer so the net arriving falls short of the invoice. Two habits cut the rate: prefer the exact-amount QR over a manual entry, and let the buyer pick a low-fee network so the send fee is a smaller slice of a small order. Neither eliminates the case, which is why the waiting state exists.
Refunds without chargebacks
A confirmed crypto payment cannot be reversed by the buyer, so there are no chargebacks; refunds run the other direction, initiated by you. You send them in crypto from the admin, using a separate payout key that has to be enabled on the account first, and without that key the refund function stays off. This is the trade you are making, and it is worth stating plainly.
A chargeback is a card-network reversal a buyer files with their bank, and it drives most eCommerce payment-fraud losses. Because an on-chain payment settles with finality, that reversal path does not exist for crypto orders. What you gain is the removal of fraud-driven chargebacks on the crypto share of your sales; what you take on is the refund itself. You decide the amount and the asset, you need the buyer’s payout address, and the refund clears as an outgoing payment with its own outcome shown on the order.
Two operational points follow. A refund can be partial, matching a returned item rather than the whole basket, and it goes out as an on-chain payment the buyer has to receive at an address they control, so a refund policy for crypto orders should collect that address as part of the return. For a store with a chargeback problem, removing that dispute channel is the whole point of the switch; for a store without one, it is neutral, and the refund workload is the same as any other manual return.
Want to accept crypto payments on your website?
Fast setup and KYC/KYB, fee starts from 0.5%
Contact UsDid it pay off: what to measure
Crypto acceptance pays off for a specific audience, not every store, and you measure that with order-level metrics rather than a promised conversion lift. Crypto is around 0.5% of eCommerce turnover and under 5% of transactions in most categories, so treat it as incremental volume and measure the increment. Any single number promising a conversion jump should be read as a vendor’s own claim until your own orders confirm it.
The adoption picture, as of September 2026, sets the scale. Crypto sits near 0.5% of eCommerce turnover on market estimates. Roughly 19% of US small businesses accept it in 2026, up from about 12% of North American merchants at the end of 2024, on Merchant Risk Council and JD Power figures, and PayPal reports around 4 in 10 US merchants. On the buyer side, about 2.5% of the US population paid with crypto in 2026, roughly 18% of holders, on EMARKETER’s August 2025 forecast. The shares are real but narrow.
Five metrics tell you whether acceptance earned its fee:
- Crypto-order conversion. Of the buyers who reach the crypto option, how many complete. This isolates the checkout itself from everything upstream.
- Recovered international declines. Cross-border card payments fail often, and a crypto order that a card would have declined is revenue you would not otherwise have booked.
- Chargeback savings. The chargebacks you no longer absorb on the crypto share of sales.
- Crypto-order AOV. The average value of crypto orders against card orders, which tells you whether the audience is worth more per basket.
- New-customer share. How many crypto payers are new to your store rather than existing customers switching rails.
To read those honestly, tag crypto orders from the day you launch and give the test a fixed window, on the order of two to three months, so seasonality and a slow start do not distort the first weeks. The comparison that matters is not crypto against your whole business; it is the crypto cohort against the card orders it plausibly replaced or added, which is why the new-customer and recovered-decline lines carry more weight than raw crypto volume.
Break-even follows from those five. Acceptance clears its cost when recovered cross-border sales, avoided chargeback losses, and genuinely new crypto-native customers together exceed the provider fee on that volume, which runs 0.5% to 2% across the field and from 0.5% with Speend. The catch sits in the incrementality: because crypto runs under 5% of transactions, a store that simply moves existing card volume onto crypto mostly shifts cost around. The gain lives in the orders card rails would not have completed.
So who does it move for? Cross-border and international sellers, storefronts with a crypto-native audience, and categories carrying high card-decline or fraud-chargeback rates. A domestic store whose customers are content with cards will watch that 0.5% show up as 0.5%. Your settlement choice also touches the math: taking 100% crypto, auto-converting to a stablecoin, splitting, or settling on a schedule are all available, and auto-conversion removes price exposure while adding its fee to the cost side.
High-ticket and luxury: one caveat
If you sell high-ticket or luxury goods, do not assume any order size clears by default. Per-transaction limits are set individually and depend on the asset, your merchant profile, and verification, so a large order can need conditions agreed in advance rather than passing on its own. The eCommerce vertical is offered for high-ticket and luxury, but there is no published limit table to point to.
The practical read: during onboarding, confirm the ceiling that applies to your account and your assets before you build a launch promise around large baskets. It is a solvable question, and the honest way to plan for it is to settle it with verification up front rather than to advertise an unlimited checkout you have not confirmed.
FAQ
How does a customer pay with crypto at checkout?
They select crypto, choose a coin and network from a searchable list, and send the exact invoiced amount to the address or QR before the countdown ends. Your store confirms the payment on-chain and marks the order paid, with nothing manual on your side for a clean payment.
What happens with an underpayment?
The order waits for the remainder with a note in the admin, and the buyer can top up the difference to complete it. If it stays short past the invoice window, you review the shortfall. The order is not lost silently.
How do refunds work without chargebacks?
A confirmed crypto payment cannot be charged back, so you issue refunds yourself, in crypto, from the admin. This uses a separate payout key that must be enabled on the account first, and you will need the buyer’s payout address to send it.
How long does the checkout price hold?
For the invoice lifetime, which runs from 1 to 12 hours and defaults to two. Within that window the quoted amount does not move, so a slow-paying buyer is not caught by a rate change.
Should my store accept crypto?
It is worth it if you sell cross-border, to crypto-native buyers, or in a category with high card declines. Measure crypto-order conversion, recovered card declines, and chargeback savings over a set window instead of expecting a conversion lift, since crypto is under 5% of transactions in most categories.
Will a large order go through?
Possibly, but not by default. Per-transaction limits are individual and set by asset, merchant profile, and verification, so for high-ticket sales confirm your ceiling during onboarding rather than assuming any amount clears.
