Certification .Net and VB6
Congratulations, you are getting closer to receive card payments!
Certification.
Once the PinPad integration part is completed in your project, it is necessary to perform test cases with different transactions to certify that the messaging has been implemented correctly, as well as the information on the tickets is in accordance with the regulations we currently have.
Once these test cases are done, 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.
Remember that this transactions are done on 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 the card will be blocked.
CheckList de validación.
| Indicator. | Detail. | Restrictions |
|---|---|---|
| Was the FolioNumber field implemented in the integration? | FolioNumber field handling. | *Mandatory. |
| Were service logs implemented on the point of sale side? | Management of logs at your point of sale. | *Mandatory. |
| Does the integration have a timeout that limits being able to deliver the information from the terminal to the point of sale? | NA. | *Mandatory. |
| What version of the .Net Framework do you have installed? | Version 3.5 or higher. | *Mandatory. |
| What version of the library is implemented? | It is recommended that you have a section where you can easily see which version of the library has been implemented. | Recomended |
| What operating system will be used for the integration (architecture)? | Example: Windows 10 x86 | NA. |
| How is a sale being handled? | What is the action they perform is a thread or timer? | NA. |
Important.
The use of response timeout implemented at the POS prevents the process from being carried out successfully, if by any reason the transaction passes the time limit, it will cause the timeout to freeze and unwanted situations may occur, for example a transaction not reaching the POS.
Transactional operations.
| Type test | Type card | 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 merchant has a card without a PIN. |
| 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. | NA. | During the printing of the merchant's receipt and the printing of the customer's receipt, in the same way, a period of time between 3 to 5 minutes must be expected. | *Mandatory. |
Warning.
Tests with * are required for a certification.
Cancel Operation.
| Type test | Type card | Expected result | Restrictions |
|---|---|---|---|
| Cancellation. | Indistinct | Cancellation of a sale made on the same day. | It is recommended to implement cancellations. |
Reprint Operation.
| Type test | Type card | 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.
Updated 10 months ago