Check the entire instruction

Read the actual supported funding guidance and identify whether an additional reference, memo or other field is requested for that route. Do not assume such a field is always required or never required. The decision should follow the complete provider instruction for the specific service, asset and customer arrangement.

Ask through the right channel

If the source interface and receiving instruction do not appear compatible, seek clarification before proceeding. Avoid improvising a value from an invoice number or using a code from another service. Tap Tap Go’s proposed crypto-to-bank capability is coming soon, and the appointed programme would determine the exact funding requirements and any supported resolution process.

Imagine this

An illustrative future scenario

Imagine a future user seeing an extra field in one instruction but not understanding how it fits the sending source. He asks for confirmation instead of filling it with a familiar project code, preserving a clear decision before value is moved.

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.