Stage 3: Test
These are the test scenarios that should be covered to ensure that Certification process runs smoothly:
[Mandatory] Setup Flow
[Mandatory] Payment Flow
[Mandatory] Cancellation Flow
[Optional] Refund Flow
[Optional] Tips Flow
Setup Flow
The installation and setup represent the merchant's first experience, so it's imperative that it occurs quickly and seamlessly.
To ensure the best experience, please follow the test cases below to ensure that your integration runs smoothly.
Test Cases: Happy Path
| Case # | Mandatory/Optional | Scenario | Scenario Setup | Actions to take | Expected Result |
|---|---|---|---|---|---|
| 1 | Mandatory | Connect Teya Account to ePOS | Partner goes to add Teya as a Payment Method | Partner Navigates to Settings > Add Payment Method | Partner Prompted to Connect Teya Account |
| 2 | Mandatory | Teya ID Login | - Partner follows above steps to Connect Teya Account - Partner Directed to Teya ID OAuth |
Partner Enters Valid Merchant Teya ID Credentials | 1. Successful login to TeyaID 2. ePOS is Authorised to Communicate to Teya Services on Merchant’s Behalf |
| 3 | Optional | Show Store(s) | ePOS knows which Merchant is using system | Partner views list of stores returned via POSLink | 1. ePOS fetches list of Stores via POSLink 2. List of Stores associated to Merchant is shown on ePOS |
| 4 | Mandatory | Select Store | ePOS presents list of stores on UI | Partner selects store to set-up | 1. ePOS obtains store_id for Card Machine Set-up |
| 5 | Optional | Show Card Machine(s) | ePOS has a card machine pairing UX | Partner navigates to card machine setup area | 1. ePOS fetches list of Card Machines via POSLink 2. List of Pre-Registered Card Machines Shown to Merchant on ePOS App |
| 6 | Mandatory | Select Card Machine(s) | List of Card Machines fetched successfully | Partner Selects Card Machine to Pair | 1. Successful pairing between ePOS and Card Machine 2. ePOS stores terminal_id for sending Payment Requests |
| 7 | Mandatory | Configure Card Machine | Configure card machine for ePOS connection | Enable Pay at Counter Mode in Card Machine features menu | 1. Card Machine now in state ready to automatically pick-up payment requests |
Test Cases: Unhappy Path
| Case # | Mandatory/Optional | Scenario | Scenario Setup | Actions to take | Expected Result | How to avoid |
|---|---|---|---|---|---|---|
| 1 | Mandatory | Refresh token already used | Do not change in background into the new Refresh Token |
1. Do not store the new Refresh Token2. Sends a new request to get the new Refresh Token |
1. ePOS receives a 400 error 2. ePOS Requests user to re-authenticate |
Read here our recommendations |
Payment Flow
Test Cases: Happy Path
| Case # | Mandatory/Optional | Scenario | Scenario Setup | Actions to take | Expected Result |
|---|---|---|---|---|---|
| 1 | Mandatory | Send Payment Request | ePOS has stored the terminal_id |
Partner sends payment request to POSLink | 1. Payment Request sent from ePOS App to POSLink 2. ePOS blocks further Payment Requests being sent 3. Card Machine App Retrieves Payment Request from POSLink |
| 2 | Mandatory | Present Payment Card | Payment Request successfully sent to POSLink and Card Machine retrieves Payment Request from POSLink | 1. Customer prompted to present payment 2. Customer presents payment card |
1. POSLink updates ePOS with Payment Request state 2. ePOS reflects closed Payment Request 3. ePOS allows Partner to send another Payment Request |
Test Cases: Unhappy Path
| Case # | Mandatory/Optional | Scenario | Scenario Setup | Actions to take | Result | How to avoid |
|---|---|---|---|---|---|---|
| 1 | Mandatory | Access token expires during payment | Let the access token reach the time limit of 9 minutes | 1. Send a Payment Request when the Access Token only has 1 minute to live 2. Wait 1 minute 3. Proceed with the payment in the card machine |
1. ePOS receives error that the Access Token is no longer valid 2. ePOS requests new Access Token in background 3. ePOS receives payment successfull |
It's highly recommended that the Access Token is preemptive refreshed before expiring and during ePOS idle time, this way during a payment/refund operation there is no increased time or risk of failing |
| 2 | Mandatory | Send Payment Request but card machine doesn't receive request | ePOS has stored the terminal_id |
1. Turn off card machine 2. Partner sends payment request from ePOS |
1. Payment Request sent from ePOS App to POSLink 2. Error is returned |
Message should be displayed into merchant to check the card machine status. Also, in the eventuality that no response is received then either ePOS can have a timeout and unblock or retry the operation in background. |
Cancellation Flow
Test Cases: Happy Path
| Case # | Mandatory/Optional | Scenario | Scenario Setup | Actions to take | Expected Result |
|---|---|---|---|---|---|
| 1 | Optional | Cancellation Requested from ePOS | Payment Request successfully sent to POSLink and Card Machine retrieves Payment Request from POSLink | Partner sends Cancel Request from POSLink | 1. ePOS updates Card Machine that request is cancelled. |
| 2 | Mandatory | Cancellation on Card Machine | Merchant sends payment request to POSLink, card machine cancels payment | 1.Pay at Counter enabled on card machine 2. Merchant / Customer clicks ‘Cancel’ on Card Machine |
1. POSLink updates ePOS that request is cancelled. |
Refund Flow
In case you decide to implment the Refund flow, the following test cases are mandatory:
Test Cases: Happy Path
| Case # | Mandatory/Optional | Scenario | Scenario Setup | Actions to take | Expected Result |
|---|---|---|---|---|---|
| 1 | Mandatory | Customer wants a refund | A successful Payment Request was made prior | Merchant initiates refund against order on ePOS | 1. ePOS advised if success or fail |
| 2 | Mandatory | Customer wants receipt of refund | A successful Refund Request was made prior | Merchant prints refund via ePOS | 1. Receipt printed from ePOS with refund success or fail state |
Tips Flow
In case you decide to implment the Tips flow, the following test cases are mandatory:
Test Cases: Happy Path
| Case # | Mandatory/Optional | Scenario | Scenario Setup | Actions to take | Expected Result |
|---|---|---|---|---|---|
| 1 | Mandatory | Tip via ePOS | Enable tips on ePOS and enable tipping on card machine | Send tip with payment request via ePOS | 1. Card Machine shows total amount including tip |
| 2 | Mandatory | Tip via Card Machine | Enable tips on ePOS and enable tipping on card machine | Send payment request with no tip present | 1. Card Machine prompts customer for tip on screen |
If you have any questions or need further assistance please don't hesitate to reach out to our support team by sending an email to partnersupport@teya.com.