QA Checklist

Before releasing your application, run through this Quality Assurance (QA) checklist. It covers functional testing, error handling, and user experience scenarios to minimize issues in the field. Tick each check as you verify it.

1. Functional Testing

Transaction Flows

Successful PaymentTF-1Verify a standard approved transaction using amount 1.01 (code 00) in the sandbox environment. Card Authentication RejectedTF-2Simulate a rejected transaction using amount 1.07 (code 06) and ensure the app handles it gracefully without crashing. Expired CardTF-3Simulate an expired card using amount 6.05 (code 54) and check the user message. Incorrect PINTF-4Simulate a wrong PIN entry using amount 6.06 (code 55) and check the user message. PIN Tries ExceededTF-5Simulate the PIN retry limit using amount 8.06 (code 75) and ensure your app treats it as a terminal failure. Cancelled TransactionTF-6Initiate a payment and cancel it from the SDK UI (back button or close). Ensure your app returns to the previous screen correctly. Receipt GenerationTF-7Verify that transaction data (Auth Code, TID, Date) is correctly captured and printed/emailed on receipts.

Hardware Interactions

NFC ReadHI-1Test with physical cards (Visa, Mastercard) and digital wallets (Apple Pay, Google Pay). Interrupted ReadHI-2Remove the card immediately after tapping but before the "beep". Ensure the SDK prompts to tap again or fails gracefully. Network LossHI-3Turn off internet/Wi-Fi during a transaction. Verify that the app reports a connection error and doesn't hang.

2. Onboarding & Configuration

Merchant Setup

New User OnboardingMS-1Run through the full onboarding flow with a fresh account. Status CheckMS-2Verify that Accept.merchant.onboardingStatus() returns RequiresAction for a pending merchant and ReadyForPayments for an approved one.

3. Security & Compliance

Device Integrity

Root DetectionDI-1(Optional) If you have a rooted test device, verify that the SDK refuses to initialize. PermissionsDI-2Revoke permissions (Camera, Location) and attempt to start the SDK. Ensure your app prompts the user to grant them.

Data Handling

Token ManagementDH-1Verify that the SDK token from POST /merchant/auth/login is fetched from your backend for each session and never hardcoded. No Sensitive DataDH-2Ensure your app logs do not print full card numbers or raw track data.

4. Edge Cases

App BackgroundingEC-1Minimize the app during a transaction and restore it. The transaction should either resume or fail safely. Incoming CallEC-2Call the test device during a payment. The SDK should handle the interruption (usually by pausing or failing). Low BatteryEC-3Test behavior when the device is in "Power Saver" mode (some NFC chips degrade in performance).

5. Production Readiness

Environment SwitchPR-1CRITICAL: Ensure isProduction = true is set for the production build. Production TokensPR-2Verify that the backend is pointing to the production Tapaya API endpoints. Version CheckPR-3Ensure you are using the latest stable version of the Tapaya Accept SDK.