Payment Integration Verification Matrix

Create a separate record for each proposed country, currency, acquiring provider, merchant account arrangement, terminal model, machine controller and software version. Include the interface or protocol version and the intended network connection. A result for one combination does not establish support for another country, account, firmware version or machine. Start every new record as not assessed. Record ID: Country and currency: Provider and merchant arrangement: Terminal / controller / software versions: Interface and network:

Ask the proposed payment provider to confirm the account prerequisites and the operator responsible for registration, settlement, fees and ongoing service. Record the dated provider response and its scope. A terminal demonstration does not establish that the operator can obtain the required live merchant account. Keep private credentials, full card details and customer information out of this worksheet.

Agree a test procedure for the exact configuration with the supplier and payment provider. Record the amount requested, payment result, machine action and completion signal using non-sensitive test references. Define the expected result before testing and distinguish payment authorisation from completed delivery or service. A payment success screen alone is insufficient evidence of a completed machine transaction.

Document the expected customer and operator behaviour when a payment is declined, cancelled or interrupted. Use an agreed test environment and supported procedure; do not invent live fault tests. Identify whether the machine releases a product or starts a session, what payment status remains and who investigates an unresolved transaction. Preserve failed and untested cases alongside successful observations.

Record who can initiate a reversal or refund, the supported procedure and the evidence linking the payment reference to the machine event. Compare the machine record with the provider record for the agreed test cases. Record discrepancies and ownership of follow-up. Timing, fees and eligibility must come from the applicable provider arrangement rather than a general promise on this page.

Agree how to observe loss and restoration of the required connection without bypassing protection or exposing live customer information. Record whether transactions are blocked, queued or require operator action only after observing the supported behaviour. Identify who can change credentials, update software and retrieve diagnostic records, and document any dependency on a supplier-managed service.

For each row record the expected result, actual observation, dated evidence reference, reviewer and outcome. Use not tested, pass, fail or not applicable; explain any not-applicable decision. A pass applies only to the recorded case and configuration. Keep unresolved actions and retest references. Reassess relevant cases after an account, provider, firmware or interface change. This blank worksheet publishes a verification method, not a list of supported countries or payment providers.