TAP TAP GO
Decide what flexibility solves
An open amount field may suit some approved collection workflows, while a fixed invoice amount may be clearer for a defined purchase. Ask the payment provider which formats are available for your use case. Consider who knows the correct amount and how the customer confirms currency. Do not select a flexible field merely because setup is quick if the team will later spend hours identifying underpayments, overpayments or amounts without an obvious order connection.
Define the exception process
If customer entry is necessary, show concise instructions and require the appropriate order reference through supported fields. Decide who contacts customers about differences and how corrections are authorised. Test the receipt and export to confirm that finance can reconstruct the intended purchase. The evaluation should include the buyer's experience and the administrative burden, because a shorter setup process can transfer work to the customer and the accounts team rather than eliminating it from the overall operation.
Hypothetical example
A hypothetical tutor offers several session lengths through a general payment link. Customers occasionally enter the wrong amount. After reviewing available checkout formats, the tutor creates clearer service-specific options and keeps a defined process for correcting existing exceptions, making both purchase and reconciliation easier to follow.
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.
