Bitcoin Cash exists for a particular reason: when the Bitcoin community split in 2017 over how to scale, BCH took the "bigger blocks" path while Bitcoin took the Lightning-and-second-layer path. That divergence has produced two networks with different operational profiles. BCH kept the on-chain, larger-block model — and it kept the merchant-payments framing as its primary use case.
MixPay routes BCH natively. This post is the reference for what that means and which merchants actually find BCH useful.
What BCH does well
The chain's design choices are oriented around payment throughput on the base layer:
- Larger block sizes (32 MB cap on BCH versus 1 MB on Bitcoin pre-SegWit) — more transactions fit in each block.
- Lower per-transaction fees in steady state because of the larger throughput envelope.
- Same ten-minute block cadence as Bitcoin — finality semantics are familiar.
- Wallet support that overlaps significantly with Bitcoin — the protocol fork preserved enough of the original design that wallet ecosystems span both.
That last point is worth flagging: a customer with a wallet that supports BCH almost certainly already has a Bitcoin wallet too. The integration cost on the customer side is negligible.
Where BCH shows up commercially
BCH's volume share in MixPay's published chain-distribution data is small — single-digit basis points. The merchants who specifically benefit aren't the same merchants choosing TRON or Solana; they're a different audience:
- Long-time crypto holders. Customers who acquired BCH through the 2017 fork airdrop and have held it as part of a Bitcoin-adjacent position. Some of those holders have meaningful balances they prefer to spend rather than convert.
- Privacy-conscious users with BCH preferences. A subset of the privacy community uses BCH alongside or instead of BTC because of the on-chain economics; CashFusion and similar tools shape that preference.
- Specific regional communities. BCH has stronger merchant adoption in a handful of geographies, particularly where the "Bitcoin as payment" framing has been promoted by local grassroots organising.
For most consumer-facing merchants, BCH won't be a primary chain. For the merchants who do receive a BCH-paying audience, supporting it removes friction without adding operational overhead.
How MixPay handles BCH
The merchant flow is the same as every other chain MixPay routes. Customer pays BCH from any BCH-compatible wallet, MixPay confirms the on-chain transaction, applies a real-time price quote, and settles into the merchant's chosen stablecoin.
Operationally:
- Zero merchant fees at the MixPay layer.
- Stablecoin settlement isolates the merchant from BCH price movement.
- No infrastructure on the merchant side — MixPay handles node and chain operations.
- Same reporting surface — BCH-routed transactions appear in the same dashboard as every other settled payment.
A note on chain identity
For accuracy: MixPay routes the Bitcoin Cash (BCH) chain that emerged from the 2017 fork, not Bitcoin SV (BSV) which was a subsequent fork from BCH. Customer-side wallets generally make this distinction clear by displaying chain-specific addresses (BCH uses the bitcoincash: cashaddr format).
If your customer base includes long-time crypto holders or privacy-aware payment communities, BCH on MixPay is one more option in their wallet they don't have to convert away from. The full asset and chain coverage is on the accept page.