TAP TAP GO
Make the requested detail recognisable
A payment route may need an order or booking reference under its actual configuration. Show the customer where to find that reference and how it relates to the offer. Do not invent a required field or assume the system automatically knows the project simply because the customer arrived through a Tap Tap Go profile.
Keep instructions proportionate
Ask only for the relevant information and avoid putting private project detail into a short payment field. The aim is a clear connection between the agreed offer and the financial record, not a new questionnaire at checkout.
Hypothetical worked scene
In a hypothetical supported checkout, a workshop customer needs to enter a booking reference. The organiser's instructions identify the reference on the confirmation message, reducing guesswork. The example concerns that particular configured route and does not claim every Tap Tap Go QR automatically identifies customers or links payments to event records.
Make it practical.
Use this checklist as you read. Checks are not stored.References & further reading
Tap Tap Go Journal: publisher and product context ↗Published by Tap Tap Go. Product availability and eligibility vary by programme and market. About our stories.
