Unsupported Asset Payment

Overview

An unsupported asset payment occurs when a payer sends a cryptocurrency or token that the receiving merchant, invoice, address, or processor is not configured to accept. The transfer may be valid on-chain while remaining unmatched, uncredited, or operationally unrecoverable in the payment system.

Typical causes include selecting the wrong token in a wallet, confusing assets that share a ticker, sending an unapproved contract version, or reusing an address outside its supported scope. It differs from an unsupported-network payment: the network may be correct while the asset is not approved. Related operational concepts include Accepted Cryptocurrency, Accepted Payment Network, and Payment Status. They should remain connected through identifiers and evidence without being treated as the same payment state, control, or financial result.

The system may detect the transfer through address monitoring but cannot safely treat it as fulfillment of the intended invoice. For a payer, Unsupported Asset Payment should make the merchant, amount, asset, network, destination, expiration, and fee expectations easy to verify. The authoritative record for Unsupported Asset Payment should also show the rule version, responsible system, permitted state transition, and any downstream action such as fulfillment, settlement, refund, or manual review.

Typical causes include selecting the wrong token in a wallet, confusing assets that share a ticker, sending an unapproved contract version, or reusing an address outside its supported scope. For a payer, Unsupported Asset Payment should make the merchant, amount, asset, network, destination, expiration, and fee expectations easy to verify.

Operational ownership for Unsupported Asset Payment should cover configuration changes, access, monitoring, customer treatment, accounting, and escalation. This supports the central requirement that an on-chain transfer is not a valid payment when the received asset is outside the merchant’s approved asset-network configuration.