Wrong-Contract Payment
Pronunciation: rawng KON-trakt PAY-muhnt
Also known as: Incorrect Token Contract Payment
Definition
A wrong-contract payment is a token transfer made using a contract address other than the contract approved by the payment instruction. The token name and symbol may match the requested asset, but on programmable blockchains the contract address is the authoritative identity of a contract-issued token. It differs from an unsupported token payment because the payer may have intended a supported token but selected the wrong deployment. It differs from an unsupported network payment when the blockchain is correct but the contract on that chain is not.
Overview
A wrong-contract payment is a token transfer made using a contract address other than the contract approved by the payment instruction. The token name and symbol may match the requested asset, but on programmable blockchains the contract address is the authoritative identity of a contract-issued token.
It differs from an unsupported token payment because the payer may have intended a supported token but selected the wrong deployment. It differs from an unsupported network payment when the blockchain is correct but the contract on that chain is not. It should not silently reinterpret the order, overwrite the requested asset, or credit a different destination merely because value arrived. Related operational concepts include Invoice Token Contract, Unsupported Token Payment, and Unsupported Network Payment. They should remain connected through identifiers and evidence without being treated as the same payment state, control, or financial result.
The incorrect contract may represent a counterfeit token, bridged deployment, legacy version, test token, or legitimate asset that the merchant does not support. The system should preserve both the original payment instruction and the transfer actually observed on-chain. The authoritative record for Wrong-Contract Payment should also show the rule version, responsible system, permitted state transition, and any downstream action such as fulfillment, settlement, refund, or manual review.
It differs from an unsupported token payment because the payer may have intended a supported token but selected the wrong deployment. It differs from an unsupported network payment when the blockchain is correct but the contract on that chain is not. Testing should cover duplicated and out-of-order events, incorrect asset or network data, late transactions, provider outages, retries after uncertain responses, and manual intervention after one subsystem has already changed state.
Governance should connect Wrong-Contract Payment to the original obligation, payment instructions, observed transaction, internal state, financial posting, and any fulfillment or refund. The decisive principle remains that a wrong-contract payment is a token transfer made using a contract address other than the contract approved by the payment instruction.
Key Takeaway
A wrong-contract payment is a token transfer made using a contract address other than the contract approved by the payment instruction.
Sources
- ERC-20: Token Standard — Ethereum Improvement Proposals (2026-08-02)
- Supported Currencies — OxaPay (2026-08-02)
- Generate Invoice — OxaPay (2026-08-02)