Asset, network and destination
A receiving service can support a token on one network but not another. Similar-looking or identical address formats across networks do not guarantee compatibility. Some deposits also require a memo or destination tag so the service can assign a transfer to the correct customer account.
For example, sending a token to the displayed address on an unsupported network can create a missing-credit problem even when the network records success. The on-chain transfer and the service's supported deposit route are separate facts. Check the exact asset, network, address and additional identifier in authenticated instructions.
Address is not authority to spend
An address can be shared to receive or inspect public records. A private key or recovery phrase can control assets and must not be supplied to support. Knowing a receiving address does not prove who controls it or establish the trustworthiness of a service displaying it.
Practical record keeping
Copy and verify the destination carefully, including the beginning and ending characters and any required tag. Check the actual confirmation screen rather than relying on a remembered address. An address can change in a service's instructions, so old screenshots are not always appropriate for a new transfer.
If money is not credited
Preserve the transaction hash, network, token, amount, destination and required tag. Ask whether the issue is network status, unsupported routing or account matching. Do not send additional funds to supposedly unlock the first transfer without a documented reason. Recovery from an incorrect route is not guaranteed and depends on actual control and the receiving service's process.
Is an explorer balance proof that an address belongs to a service?
No. Public activity can show transfers involving an address without establishing the identity of its controller. A copied address on an unverified page can also be substituted by someone else. Use authenticated current instructions and independently verify the service context. The address, asset, network and tag need to match the intended route. Ownership, transaction execution and customer-ledger credit are separate claims, and evidence about one should not be used as a blanket guarantee of the other two.