Use a complete payment identity
A useful payment record identifies the asset, the blockchain network, the destination and any required memo or tag. Omitting one of those fields can make an apparently clear instruction ambiguous. This is particularly relevant when a token exists on several networks.
Similar addresses do not settle compatibility
Some networks use similar address formats. A wallet accepting the text of an address does not prove that the recipient supports the asset on that chain. The receiving service’s explicit instructions matter more than visual similarity.
Tags and internal account routing
Some receiving arrangements use an additional reference to attribute a transfer to a customer account. Whether one is required depends on the service and asset. A review should not publish a universal rule from one operator’s example.
Unsupported transfers are not routine refunds
Recovery options depend on who controls the destination, the asset, the network and the service’s capabilities. A support team may be unable or unwilling to recover an unsupported transfer. Never assume that an address-format match guarantees reversibility.
Keep the comparison specific
Our payment guides deliberately avoid saying that a brand supports every network associated with a coin. A current support list is evidence for what it actually lists, at the time checked. For examples of multi-network assets, read the USDT guide and USDC guide. If instructions remain unclear, do not proceed on the basis of an assumption.