TAP TAP GO
Describe the actual workplace
Tell the provider whether staff use a shared reception tablet, personal phones or managed company devices. Ask how its service supports separate users, session controls and recovery in that environment. Do not assume a personal mobile-account model can simply be copied onto a shared device. The design should make it clear who performed an action and who is responsible for closing access when a shift ends or a colleague changes role.
Walk through a busy handover
Test the process for moving between users, reviewing a transaction and escalating a problem. Keep payment credentials out of shared notes and avoid making one person's private phone the undocumented recovery method for an entire team. Consult the appropriate security owner about the setup. The practical goal is a process staff can follow during real customer activity, not a theoretical policy that becomes impossible to use when the reception area is busy and people need to switch quickly.
Hypothetical example
A hypothetical clinic uses a tablet at reception. Before enabling a new payment workflow, its administrator asks how separate staff actions and sessions can be managed. The answer shapes the setup, preventing an account created for one employee from quietly becoming a shared financial identity for the whole front desk.
Make it practical.
Use this checklist as you read. Checks are not stored.References & further reading
Background reading — PCI Security Standards Council: merchant resources ↗Published by Tap Tap Go. Product availability and eligibility vary by programme and market. About our stories.
