TAP TAP GO
Separate status amount and merchant issues
Write one sentence describing the issue: a missing credit, an unexplained amount, an unfamiliar description or an unsuccessful payment. Include the provider's permitted reference, relevant dates and masked identifiers. State what you have already checked. This makes the handoff more useful than a screenshot accompanied by a vague instruction to fix everything, especially when the support team must route different questions to different specialists or external partners.
Keep a single investigation record
Assign one internal owner, retain the ticket reference and note the promised next update. If another team member contacts support, give them the existing record rather than starting a competing explanation. Record the resolution in ordinary language so finance can apply it to the correct item. A useful support history becomes evidence for future provider reviews: recurring questions may reveal unclear product information or a workflow problem that deserves attention beyond the individual transaction.
Hypothetical example
A hypothetical finance assistant reports a refund that has not appeared. The ticket includes the merchant confirmation, original payment reference and expected currency. Support can investigate the precise issue, and the assistant records each update in one place instead of scattering contradictory messages across the team.
Make it practical.
Use this checklist as you read. Checks are not stored.References & further reading
Background reading — CFPB: prepaid card comparison resources (US context) ↗Published by Tap Tap Go. Product availability and eligibility vary by programme and market. About our stories.
