TAP TAP GO
Ask for the status dictionary
Request a plain-language explanation of every status visible in the app or export. Find out which events change a transaction from one status to another and how the provider recommends handling a transaction that remains unresolved. Do not give staff universal timing promises that the issuer has not confirmed. A status is useful only when the person reading it understands what action, if any, is appropriate at that point.
Avoid duplicate operational decisions
Before asking a merchant to charge again or paying through another method, check the existing transaction with the relevant parties. Record the instruction you receive and keep related attempts together. In the internal ledger, distinguish an unresolved item from a final expense according to the team's accounting process. This reduces the chance that an impatient workaround creates a second problem while the original transaction still needs explanation and the customer cannot identify which attempt succeeded.
Hypothetical example
A hypothetical consultant sees a pending charge after a booking page stops responding. Rather than immediately paying again, she checks the booking and transaction references with support. Her records preserve the first attempt, making it easier to understand the outcome and avoid unnecessary duplicate administration later.
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.
