Use a three-column feature register

Record proposed, in testing and available capabilities separately, with the provider's dated evidence for each. Ask which licensed or authorised partner performs each financial service and what remains before customer access. Include account type, geography and eligibility in the availability field. For Tap Tap Go, proposed European SEPA, virtual IBAN and crypto-to-bank services should be assessed within that partner-led programme context rather than presented as universally live features.

Make the purchase decision on today's evidence

Decide which current capability justifies adoption and which future capability would justify expansion later. Put review dates beside roadmap dependencies instead of allowing them to disappear into a sales conversation. If the future service is essential, ask what contractual commitments and alternatives apply before making your decision. This lets a business support an ambitious product direction while keeping budgets, customer promises and operational continuity tied to evidence it can actually verify at the time.

Imagine this

Hypothetical example

A hypothetical distributor likes a platform's European expansion plan but needs a receiving account immediately. It evaluates the available identity tools on their own merits and keeps its existing account arrangement until the proposed financial capability is confirmed for its business and intended customers.

Make it practical.

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

References & further reading

Background reading — European Payments Council: SEPA Credit Transfer ↗

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