UAT Checklist

This checklist helps partners validate the Tap to Pay integration before production launch. UAT must be completed before production access is approved.

UAT Goal

The goal of UAT is to confirm that:

The SDK is integrated correctly
The app can initialize Tap to Pay
The payment flow works as expected
Error scenarios are handled clearly
Merchant setup is ready for production
The partner and Netevia are aligned before launch

Before UAT

Before starting UAT, confirm:

App Readiness

Confirm the app is ready for UAT:

App installs successfully.
App launches successfully.
User can log in.
Merchant can access the payment flow.
Tap to Pay option is visible.
App uses the correct UAT environment.
App does not include production credentials.
App handles app restart correctly.
App handles background and foreground behavior correctly.

SDK Readiness

Confirm the SDK works inside the app:

SDK initializes successfully.
SDK initialization error is handled clearly.
Tap to Pay preparation completes successfully.
App handles missing configuration.
App handles invalid configuration.
App handles network errors.
SDK version is documented.
App logs include enough information for troubleshooting.
App logs do not expose sensitive data.

Payment Flow Testing

Test the main payment flow:

Receipt and Result

Confirm the app clearly shows the transaction result:

Approved payment result is clear.
Declined payment result is clear.
Canceled transaction result is clear.
Timed-out transaction result is clear.
Failed transaction result is clear.
Receipt option is available after successful payment.
Transaction reference is available for support or reporting, if applicable.

iOS-Specific UAT

For Tap to Pay on iPhone, confirm:

Test device supports Tap to Pay on iPhone.
Required Apple entitlement status is understood.
Required Tap to Pay user experience is implemented.
Tap to Pay button is visible at checkout.
Enrollment flow works as expected.
Terms & Conditions flow works as expected.
Merchant education is available in the app.
Apple review videos can be recorded, if applicable.

Android-Specific UAT

For Android Tap to Pay / SoftPOS, confirm:

Test device meets Android requirements.
NFC is available and enabled.
Required permissions are configured.
Android SDK initializes successfully.
Android payment flow works as expected.
Device-specific issues are documented, if any.

Security Checks

Before UAT sign-off, confirm:

Production credentials are not used in UAT.
Credentials are not hardcoded in the app.
Credentials are not committed to source control.
Sensitive data is not exposed in logs.
Full card data is not stored or displayed.
Access is limited to approved test users.
Partner understands production access requires Netevia approval.

Support Readiness

Confirm support ownership before moving to production:

Partner knows how to contact Netevia for support.
Partner support owner is assigned.
Netevia support contact is confirmed.
Escalation path is understood.
Known UAT issues are documented.
Open blockers are reviewed with Netevia.

UAT Sign-Off

UAT can be considered complete when:

Required test cases are completed.
Critical issues are resolved.
Open non-critical issues are documented.
Partner confirms app readiness.
Netevia confirms payment-side readiness.
Production launch plan is confirmed.
Pilot merchant list is confirmed, if applicable.

Summary

UAT confirms that the partner app, SDK integration, merchant configuration, and payment flow are ready for production.

Production access should not be enabled until UAT is completed and approved by Netevia.

Partner Readiness Checklist

Production Launch Checklist