Read the complete instruction

Prepare a checklist for the asset, supported route or network, destination details and any additional information the eventual provider explicitly requires. Use the instruction supplied for that actual service rather than copying a generic asset description. Leave unknown details unresolved instead of filling them from memory or a past transaction elsewhere.

Check the source can follow it

Ask whether the sending source supports the confirmed instruction and whether any user-specific restrictions apply. Do not describe assets or networks as interchangeable, and do not invent recovery options for an incorrect transfer. Tap Tap Go’s proposed crypto-to-bank service is coming soon; its approved funding methods would be established through the actual programme.

Imagine this

An illustrative future scenario

Imagine a future user seeing a familiar asset name but a different funding instruction from an earlier service. She checks the full supported details and source compatibility before deciding whether the new route fits her task, rather than copying an old destination.

Make it practical.

Use this checklist as you read. Checks are not stored.

Published by Tap Tap Go. Product availability and eligibility vary by programme and market. About our stories.