Address Token Mismatch
Pronunciation: uh-DRES TOH-kun mis-MACH
Also known as: Wrong-Token Address Payment
Definition
Address Token Mismatch is a condition in which a payment reaches the expected blockchain address but uses a token or asset different from the one assigned to the payment request.
Overview
What does Address Token Mismatch mean?
Address Token Mismatch is a condition in which a payment reaches the expected blockchain address but uses a token or asset different from the one assigned to the payment request.
How it works in practice
An address-token mismatch occurs when a recipient address, chain and token identity do not jointly match an authorized payment instruction. An EVM address can look valid on several chains while the recipient or gateway supports only one. On token networks, a destination may receive a transfer of a different contract with the same symbol, or an address may be unable to receive a particular asset safely. Payment processing must verify network identifier, contract or mint, destination, amount and any required memo before accepting the deposit.
Further operational details
Operationally, the system validates the destination, network, contract or asset identifier, decimals, expected amount, and assigned payment record before recognizing value. A reliable implementation records the observed transaction, destination, network, token contract, asset identifier, amount, expected payment details, timestamps, and matching result. Performance is evaluated through detection accuracy, false acceptance rate, unresolved value, resolution time, and the number of mismatches prevented before fulfillment.
For governance and audit, use authoritative asset identifiers, network-aware validation, allowlists, explicit mismatch states, automated alerts, quarantine rules, and documented refund or recovery decisions. This makes Address Token Mismatch a controlled operational concept rather than an ambiguous label.
Limits and common misunderstandings
A blockchain explorer showing a transfer to a familiar-looking address does not establish that the merchant supports or controls the received token. Recovery depends on custody setup and is never guaranteed. Customer support should avoid promising recovery solely because the address format matches.
Related glossary terms
Address Reuse Policy; Crypto Payment Address; Address-Based Payment Matching
Example
A customer sends a token labeled USDC on Chain B to an address displayed for USDC on Chain A. The hexadecimal address is identical, but the gateway marks the deposit unsupported and checks actual recovery capability before responding.
Comparison
Address validity is a syntax and network question; token authenticity is an issuer/contract question; payment acceptance combines both with the commercial invoice conditions.
Key Takeaway
Address validity is a syntax and network question; token authenticity is an issuer/contract question; payment acceptance combines both with the commercial invoice conditions.
Sources
- Generate Static Address — OxaPay (2026-08-02)
- Payment Information — OxaPay (2026-08-02)
- Webhook — OxaPay (2026-08-02)