Q&A: does x402 work with BCH stable coins?

• The x402 protocol itself
• BCH support exists, via a community implementation
• So can it pay BCH stablecoins?
• Important caveats

Question:

does x402 work with BCH stable coins?

Answer:

Short answer: Yes, technically — but with caveats. Let me break it down.

§The x402 protocol itself

x402 (Coinbase’s HTTP 402-based payment standard) is designed to be chain- and token-agnostic. Its whitepaper states it’s “built to support any stablecoin, digital asset, or blockchain,” and stablecoins (primarily USDC) are the dominant settlement asset. The official reference implementation launched on Base and Solana, and it “supports all EVM-compatible chains, Solana, and more” — so BCH isn’t part of the core/official deployment. (x402.org, Coinbase docs)

§BCH support exists, via a community implementation

There’s a third-party package, x402-bch (OPTNLabs), that adds BCH support for x402 v2 “exact” payments. Notably:

• It supports native BCH and CashTokens — including fungible tokens and NFTs (P2PKH, P2SH20, P2SH32 outputs).
• Network IDs: bch:bitcoincash (mainnet) and bch:bchtest (Chipnet).
• In the client spend controls, a CashToken entry uses the token category as the asset identifier, so a stablecoin CashToken can be whitelisted and paid just like any other fungible token (with a per-payment cap on token amount).
• Unlike account-based chains, BCH payments carry a complete client-signed UTXO transaction rather than an account authorization.

(github.com/OPTNLabs/x402-bch)

§So can it pay BCH stablecoins?

In principle, yes — because x402-bch treats any CashToken fungible token as a payable asset, and a stablecoin is just that. BCH does have a CashToken stablecoin: MUSD, launched by the Moria Protocol (an asset-backed, over-collateralized borrowing system using BCH as collateral, with a D3lphi oracle and Proof-of-Reserves). It was the first stablecoin built on BCH CashTokens. (news.bitcoin.com)

§Important caveats

1. x402-bch is a community/third-party implementation, not part of Coinbase’s official x402 stack. Its BCH support is relatively new and its provider transports/full VM execution are still being built out.
2. BCH stablecoins are niche. As of 2026, no mainstream stablecoin (USDC/USDT) runs natively on BCH — MUSD and similar are small, ecosystem-specific projects. BCH itself is an unofficial/independent route for stablecoin payments.
3. The default x402 client only allows USD stablecoin assets unless the app opts in, so supporting a BCH stablecoin requires explicit configuration (whitelisting the token category).

Bottom line: Nothing in x402’s design prevents BCH stablecoin payments, and the x402-bch library can carry CashToken fungible tokens (which includes stablecoins like MUSD). But it relies on a third-party BCH implementation and a small, non-mainstream stablecoin ecosystem — so it works in principle rather than as a widely-supported, production-standard path today.

Public Q&A mirror from the Block tech-support bot.