Crypto payments are less radical than the marketing and more useful than the backlash. Strip away the ideology and the practical question is narrow: can a merchant get paid, settle to spendable money, and not carry price risk? For volatile crypto the honest answer is “sometimes, via a processor.” The interesting action has mostly moved to stablecoins.
Crypto payments accept a volatile coin at checkout but almost always convert it to fiat (or a stablecoin) immediately, so the merchant never carries price risk.
Crypto payments means accepting a cryptocurrency — Bitcoin, Ether, or others — in exchange for goods or services. The defining word is volatile: unlike a stablecoin, the value of the coin moves freely against fiat, so the central design problem is how the merchant avoids carrying that price risk.
In practice almost no merchant who advertises “crypto accepted” actually holds the coin. A payment processor sits in the middle: it takes the customer’s crypto, locks the fiat price at the moment of sale, and settles the merchant in fiat (or a stablecoin) shortly after. The merchant sees a normal sale; the volatility is somebody else’s problem for a few seconds.
That single design choice — convert immediately, settle to fiat — is what makes merchant crypto acceptance workable. It also means most “crypto payments” are, economically, a crypto-to-fiat conversion wrapped around a checkout.
The processor compresses all the volatility risk into the seconds between quote and conversion. The merchant is sold a fiat outcome.
| Step | What happens | Who carries the risk |
|---|---|---|
| Quote | Processor locks a fiat price and a short expiry window at checkout | Processor (for the window’s length) |
| Pay | Customer sends crypto to a processor-controlled address | Network confirmation delay applies |
| Confirm | Processor waits for enough on-chain confirmations to treat it as final | Processor manages reorg / double-spend risk |
| Convert | Processor sells the crypto for fiat (or holds the stablecoin) | Processor — this is where volatility is absorbed |
| Settle | Merchant receives fiat (often next-day) or stablecoin, minus a fee | Merchant carries none — that is the point |
| Volatile crypto (BTC, ETH) | Stablecoin (USDC, USDT) | |
|---|---|---|
| Value | Floats freely vs fiat | Pegged ~1:1 to a fiat currency |
| Merchant risk | High — must convert instantly | Low — already denominated in dollars |
| Why a merchant takes it | Reach a crypto-holding customer; novelty | Cheap, fast, dollar-denominated settlement |
| Typical role | A funding source at checkout | A settlement and treasury rail in its own right |
| Cross-border use | Possible but FX/volatility messy | Strong — the main reason to use it |
This is the distinction that matters most and is most often blurred. They are not the same product and they do not solve the same problem.
Processor fees on crypto/stablecoin acceptance often land below card interchange — commonly quoted around 0.5–1% versus 1.5–3.5%+ for cards. On thin-margin or high-ticket sales that gap is real money.
On-chain payments are push-based and final once confirmed. No chargeback fraud, no representment costs — a genuine advantage for merchants burned by card disputes.
Low fees are worthless if few customers want to pay this way. In most consumer contexts crypto checkout converts a tiny share of buyers — the economics only matter at the volume you actually capture.
Even with instant fiat settlement, you inherit accounting, tax treatment, and reconciliation questions cards never raised. The “saving” can be eaten by back-office cost.
A merchant who keeps Bitcoin instead of converting has stopped accepting payment and started running a trading book. That is a treasury and risk decision — price it as one, and most boards should not.
If you self-custody crypto you hold bearer assets: lose the keys, lose the money, and there is no chargeback or central authority to reverse it. Most merchants should let a regulated processor custody — and should check the processor’s own custody arrangements.
Confirmation times vary by network and congestion; a payment is not final until enough confirmations. Treating an unconfirmed transaction as paid invites double-spend loss.
Accepting crypto pulls you into AML/CFT, sanctions screening, and reporting obligations — and into local rules on whether crypto is even permitted as payment. In South Africa, crypto is regulated as a financial product (FSCA), so “just accept it” is not a free action.
Instant conversion protects the merchant, but the customer still bought a volatile asset to spend it; in markets where people hold crypto as a hedge against a weak local currency, the relevant volatility is the local currency’s, which is a stablecoin story, not a Bitcoin one.
You serve a customer base that genuinely holds and wants to spend crypto (some online, gaming, tech, and diaspora niches), and a processor lets you settle instantly to fiat at a fee below cards. Here it is a low-risk way to capture sales you might otherwise lose.
You are high-ticket and chargeback-exposed, and the finality of on-chain payment plus lower fees offsets the conversion overhead.
In both cases the rule is the same: convert immediately, never hold, and let a regulated processor carry custody and volatility.
For a typical merchant with a mainstream customer base, crypto checkout adds compliance, accounting and operational cost to capture a sliver of demand. The honest answer is usually “not worth it” — and if the real goal is cheap, fast, dollar-denominated settlement, the right tool is a stablecoin, not volatile crypto.
For cross-border or treasury use in weak-currency markets, again reach for stablecoins, where the value is the point and the volatility is engineered out.
Cost of getting it wrong: holding the coin and turning a payments decision into an unhedged trading position; self-custodying and losing keys; or onboarding crypto without the AML/licensing work and inheriting regulatory liability for a rounding-error share of revenue.