Ask what evidence applies to your case

Describe the intended activity and ask the provider what documents or records it expects. Keep acquisition records, relevant account statements and transaction identifiers organised where applicable. Avoid assuming that one screenshot will satisfy every question or that documents accepted by one provider will automatically satisfy another. The objective is an accurate history you can explain through the official review process, not an attempt to bypass checks or simplify facts that the provider needs to assess.

Preserve context alongside identifiers

A transaction hash alone may not describe the commercial reason for a movement. Keep an internal note linking relevant records to the business activity, with appropriate access restrictions. If information is missing, say so and ask how to proceed rather than creating an unsupported explanation. This discipline is useful before scaling a payment workflow: it exposes recordkeeping gaps while the number of transactions is manageable and gives the responsible person a consistent way to answer future questions.

Imagine this

Hypothetical example

A hypothetical founder prepares to use a new funding route and gathers the existing records that explain the asset history. One step lacks documentation, so she raises the gap with the provider before proceeding. The conversation becomes a specific review question rather than a hurried explanation after an expected payment is delayed.

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.