ABCDEFGHIJKLMNOPQRSTUVWXYZ
1
What is this?This spreadsheet is used to manage the certification process for the integration of your POS with mx51 Instore Terminals.
You should have received the certification test cases with instructions to replicate them and what to expect as a result.
Before mx51 can start the official certification process, you are required to run through the test cases and report on them in this spreadsheet.

mx51 will also use this spreadsheet to report to you the results from the run that we do ourselves during the certification.
It is used to give feedback on any failed test cases and to track any required action.
2
3
To start a new run:1. Simply complete the POS Run sheet against the mx51 test suites. You can download the test cases from the mx51 Dev Portal
2. Record your results in the run sheet and leave any comments in the comments column
4
5
6
API Documentation
7
The API specification for the Spice Payments Adaptor is available here - https://developer.mx51.io/reference/ping
8
9
Test Data
10
The test environment uses a financial simulator, and the amounts entered will determine whether the transaction is successful or not.
11
- For successful transactions ensure that an amount $1.00 or higher is used
12
- To ensure a declined response is returned when entering an invalid pin the transaction amount has to be for $0.55
13
- To ensure a declined response is returned for MOTO transactions ensure the transaction amount is for $0.05
14
- Any 4 digit pin can be entered when making transactions. E.g. 1111
15
- Merchant Password = 123456
16
17
Pay at Table Additional Test Data
18
- Table numbers should be restricted to 20 characters or less (alphanumeric), and not contain special characters or spaces
19
20
21
Table of Contents
22
23
Request Header
24
Transactions
25
Retrieve Open Orders (Tables)
26
Transaction Recovery
27
Table Locking*
28
29
Exploratory Testing
30
Every POS is different, and the mx51 Integration team realises that it is not always possible to predict in advance how every integrated feature will be used.
Therefore we also perform exploratory testing to try to uncover any issues with the integration which may not be covered by the standard test cases.
The reason for this is to prevent these issues from reaching production, and from affecting your customers.
We will list any issues we find during exploratory testing in the General Feedback section of the Certification Test Run spreadsheet.
31
32
33
Document History
34
List of test cases changes with each version
35
Document VersionNew Test Cases / Testing Notes AddedModified Test CasesTest Cases RemovedDate Published
36
Created Simplified Spice Pay Table TCs
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80