# | Steps | Result |
---|---|---|
#1 | Open connection
| ECR connects to terminal. |
#2 | Terminal first activation
| ECR triggers activation and Terminal activates and connection is on. |
#3 | Perform transaction
| Transaction is approved. |
#4 | Terminal update
| Terminal updates and comes back. |
#5 | Perform failed transaction
| Transaction is declined with response code 116 (insufficient funds), connection is on. |
#6 | Perform Close-Open
| After Open, terminal should be ready to operate. |
#7 | Perform transaction
| At step 3, terminal should return error message “busy”. |
#8 | Perform transaction
| At step 2, ECR should handle busy response from terminal correctly. |
#9 | Reboot terminal
| ECR should detect loss connection with terminal and trigger a Close-Open. |
#10 | Two transactions in a row
| Terminal should either reply “busy” or accept new transaction. |
#11 | Refund transaction
| |
#12 | Abort transaction from ECR
| |
#13 | Abort transaction from terminal
| |
#14 | Timeout management
| All timeout should be handled with no connection loss from ECR. |
#15 | Cancel transaction
| Selected transaction should be cancelled, no need to use card. |
#16 | Connection loss with terminal
| When connection with terminal is lost, Close-Open should be performed. Getlasttransaction should follow to know transaction status of previous transaction if was ongoing. |
#17 | Special character
| Check receipt is printed as expected and connection with terminal is not loss. |
If you implement optional features, you should test these features too (dual mode, loyalty management, offline...).