Separate interface availability from service outcomes

A provider may discuss app uptime, support response, transfer processing or incident resolution. Ask which measure is being quoted and what exclusions or dependencies apply. Request the relevant agreement rather than translating a sales phrase into a guarantee. For a partner-led programme, identify whether the commitment covers the entire customer journey or only the platform's own component, and how third-party incidents are communicated to affected customers.

Match the commitment to your operating need

Describe the purchase or transfer that would be business critical and ask how it would be supported during an incident. Clarify the escalation contact, update process and any contractual remedies with the appropriate advisers. A short response time does not necessarily mean an issue will be resolved within the same period. The evaluation should show what your team can rely on, what it must monitor and which contingency remains its own responsibility when operations cannot wait.

Imagine this

Hypothetical example

A hypothetical distributor hears a promise of rapid support. During diligence, it asks whether that means an initial reply or restoration of a service. The distinction leads to a clearer incident plan and a more realistic internal contingency, rather than an unsupported assumption about how long a disruption could last.

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.