Address Network Mismatch

Overview

Address Network Mismatch is a context error rather than necessarily a character-format error. An 0x address can be syntactically valid on several EVM-compatible networks, but the payment request identifies one specific chain and token route.

The system should validate address, Supported Network, pay currency, and token contract as one combination. Checking only whether the address parses correctly cannot establish that the provider monitors the selected destination on that network.

A mismatch differs from Address Format Mismatch. Format mismatch means the string does not meet the expected encoding or destination type. Network mismatch can involve a perfectly well-formed address used on the wrong chain.

Recovery depends on custody and key control. If the same private key controls the destination on both chains, a provider might technically recover funds, but token contracts, account activation, operational policy, or unsupported infrastructure can still make recovery unavailable.

Checkout interfaces should bind network selection before displaying the address and repeat the network beside the QR code and amount. Incoming monitoring should reject or quarantine transfers whose observed chain does not match the payment record.

Prevention controls should include network-specific QR schemes, explicit chain names, token contract verification, and confirmation screens that do not abbreviate similar network names. Support teams should have a documented recovery assessment but should never promise recovery before confirming key control, provider capability, and the technical state of the destination on the unintended chain.

Analytics should record attempted mismatches before funds are sent. Repeated selection errors can reveal confusing labels or interface design, allowing the merchant to improve network naming and warnings instead of relying only on recovery support.