What Happens If a Customer Sends Crypto on the Wrong Network?

Wrong-network payments are one of the most common crypto checkout support problems. A customer may choose USDT correctly, but send it over a different network than the merchant requested.

From the merchant perspective, the order should not be fulfilled just because the customer says the transfer was sent. The payment must be detected on a supported network and reconciled to the invoice or deposit flow.

The wrong-network problem

Many assets exist across several networks. USDT can be sent on TRON, Ethereum, BSC, Polygon, TON and other networks depending on wallet support. If the checkout expects one network and the customer chooses another, the payment may not match the expected invoice.

Recovery depends on the asset, network, address control and platform policy. Merchants should never promise automatic recovery for every wrong-network transfer.

Merchant response

The first step is to keep the order pending until the payment system reports a final status. Operators should collect the transaction hash, selected asset, network used, amount and customer order reference.

If the network and asset are supported, the processor may be able to identify the payment context. If not, the case may require manual review or may be unrecoverable depending on custody and chain conditions.

How to prevent mistakes

• Show the network name clearly next to the address.
• Use network-specific labels such as USDT TRC20 or USDT on TON.
• Do not hide warning text behind secondary screens.
• Make the expected asset and network visible in the invoice UI.
• Use status-based fulfillment instead of customer screenshots.

Support workflow

A good support flow should separate user intent from payment truth. Ask for the transaction hash, check the payment status, verify whether the network is supported and only then decide whether to fulfill, credit, refund or escalate.

Document the policy before launch. The policy should explain what happens when the customer sends the wrong asset, wrong network, wrong amount or pays after expiration.

Risk controls

Wrong-network handling belongs next to broader crypto payment risk controls. Suspicious activity, AML-aware states, underpayments, overpayments and late payments all need explicit merchant workflows.

See Crypto payment risk controls for the operational model.