TAP TAP GO
Treat the instruction as a complete set
Ask the provider to specify the asset, network, address and any additional reference required for your account. Verify those details inside the official service rather than copying them from a social post or old conversation. Ask what the provider recommends for checking compatibility and whether it supports a permitted test. Do not infer that a familiar ticker means every version or network route is accepted by the proposed product.
Know the exception process first
Request the procedure for a deposit that does not appear and ask which identifiers support will need. Keep transaction references and provider instructions without exposing private keys or recovery phrases. Confirm whether instructions can change and how customers are notified. A careful evaluation is about the reliability of the complete funding route, including support and recordkeeping, rather than simply comparing how many asset names are displayed on the provider's marketing page or onboarding screen.
Hypothetical example
A hypothetical creator recognises an asset name in two applications but notices different network labels. She pauses and asks the receiving provider for confirmation rather than assuming compatibility. The answer determines whether that route is suitable before any funding operation is initiated or a spending promise is made.
Make it practical.
Use this checklist as you read. Checks are not stored.References & further reading
Background reading — European Supervisory Authorities: crypto-asset consumer warning ↗Published by Tap Tap Go. Product availability and eligibility vary by programme and market. About our stories.
