Congratulations, you are getting closer to being able to make card payments!
Certification
Once the pin pad integration part of your project is completed, it is necessary to run a test matrix with different transactions to certify that the messaging has been implemented correctly. As well as the information reflected in the tickets is in accordance with the regulations in which we are governed.
If everything is correct, you can proceed to register with productive credentials and deploy a productive pilot to verify that everything is working correctly.
Note.
It is required that the certification have some cards to carry out the tests. These may be Debit or Credit cards with PIN and digital signature. Expired or canceled cards can be used.
Remembering that the integration is carried out in a test environment and no charge is made to the card.
Important.
Consider that in case of using a card with a PIN, it must be entered correctly since the terminal validates that it is the correct one and in case of entering it incorrectly it could cause the card to be blocked.
Validation CheckList.
| Indicator | Restrictions | |
|---|---|---|
| Validation of the access token. | How often do you perform the token generation? | *Mandatory. |
| FolioNumber Field Handling | Was the FolioNumber field implemented in the integration? | *Mandatory. |
| Traceability field management | Was the traceability object implemented in the integration? | *Mandatory. |
| Management of logs at your point of sale. | Were service logs implemented on the point of sale side? | *Mandatory. |
Important
The use of response timeout implemented at the point of sale prevents the process from being carried out successfully, since if the person takes more than the established time to carry out the transaction, it will cause the timeout to not respond and errors or unwanted situations will occur. such as the transaction not being concluded at the point of sale.
Transactional operations
| Test type | Card type | Expected result | Restrictions |
|---|---|---|---|
| Regular sale. | Credit-Chip. | Approved transaction. | *Mandatory |
| Regular sale. | Debit-Chip. | Approved transaction. | *Mandatory |
| Regular sale. | Card without PIN | Approved transaction. | Only if the business has a card without a PIN (AMEX). |
| Regular sale. | Band card. | Approved transaction. | Only if the business has Band. |
| Sale MSI (3 , 6, 9, 12 y 18) | Credit. | Approved transaction. | Optional only if the merchant does not implement the MSI. |
| Sale MSI. | Debit. | Cause error "Promotion not valid for this type of card"). | Optional only if the merchant does not implement the MSI. |
| Cancel sale by means of the terminal button. | NA. | "Canceled by user" | *Mandatory |
| Error handling. | Indistinct. | Provoke fraud rule code 34 transaction rejected (Test in conjunction with Netpay). | *Mandatory |
| Timeout test at point of sale for response times. This test is intended to detect that there are no defined response times at the point of sale to be certified, since if a scenario arises in which the customer takes time to carry out the transaction, the response information must be able to be received successfully. at the point of sale regardless of the time it takes for the customer. | NA. | Sale. During the printing of the merchant's receipt and the printing of the client's receipt, in the same way, a period of time between 3 to 5 minutes must be expected. | *Mandatory |
Warning.
Tests with * are mandatory for certification.
Cancellation Operation.
| Test type | Card type | Expected result | Restrictions |
|---|---|---|---|
| Cancellation | Indistinto | Cancellation of a sale made on the same day. | It is recommended to implement cancellations. |
Reprint Operation.
| Test type | Card type | Expected result | Restrictions |
|---|---|---|---|
| Re-Print approved ticket. | N/A | The terminal will print the ticket correctly. | Optional only if the merchant does not implement reprinting. |
| Re-print ticket of a canceled sale. | N/A | The terminal will print the ticket correctly. | Optional only if the merchant does not implement reprinting. |
Steps after successful certification.
- An email will be received with the results, the same obtained with the certified operations in a controlled testing environment.
- The commercial team will be coordinating the generation of productive and pilot accesses.
Note.
Validate that the Merchant Network does not have a block on the following ports and EndPoints:
Ports: 3334, 3317 and 443
Endpoint: suite.netpay.com.mxExample of timeout failure when blocking ports:
OkHttp : <-- HTTP FAILED: java.net.SocketTimeoutException: failed to connect to suite.netpay.com.mx/200.53.144.37 (port 443) after 25000ms
System.err: java.net.SocketTimeoutException: failed to connect to suite.netpay.com.mx/200.53.144.37 (port 443) after 25000ms.