The goal of certification is to verify that your integration has been done correctly and that our joint solution will work reliably for our joint customers.
If you are interested in certification, please contact us with a proposal of dates that suits you.
During certification, we will run the following test scenarios with you:
#
1
2
3
4
5
6
7
8
9
10
11
12
Scenario name
Checking the presence of GP tom
Successful transaction sale
Failed sale transaction
Timeout transaction sale
Exception during card payment
Cancellation of transaction
Deadline
Receipt data
Transaction registration
Request for payment
Getting the transaction status
Getting details about the transaction
Required
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Description
We will check if your application checks for the presence of our application.
We will make a successful card payment including PIN verification.
We will make an unsuccessful card payment (wrong pin, insufficient balance, etc.).
We will test the behavior of your application in case of a timeout.
We will simulate an exception during card payment.
We will make cancellation payments - latest and older.
Let's do a closing.
We will check the compliance with the mandatory data on the receipt.
Call up and check the registration process.
Let's test if the payment application is started and the payment is made after the transactionRequest is called.
We test to see if we get the status of the transaction and if it was completed.
Let's see if we can get the details of the transaction.
Expected behaviour
See the article "Checking an Installed Application"
Initiate payment, GP will be called, the transaction will be processed, completed by the user and your application will be successfully called back.
Initiate the payment, GP will then be called, the transaction will be processed, completed by the user and your application will be successfully called back and display any information about the rejected payment.
The application will correctly respond to the missing response from our application and inform the user.
Reaction to an exception on our side.
Initiate a cancellation, GP will invoke it, the transaction will be processed and your application will be successfully called back and possibly display a successful cancellation.
Starting a deadline, GP will be called, the deadline will be processed and your application will be successfully called back and possibly display information about the successful deadline.
If you will only provide a receipt from your system, you need to supplement it with transaction data from the terminal.
After receiving the request, a transaction ID is generated. This transaction ID will be stored locally and returned to the third party application. Your application should save it and use it to request payment.
Your application should have generated and sent the transaction request. The payment app will run the entire payment process and return the result.
We find out what state the transaction is in and whether the transaction can be retried. (It does not say anything about the success/failure of the transaction).
We get all the details of the transaction (for example: Result, amount, currency,...). For transaction details, it is necessary that the previous step has been completed - i.e. that the transaction has been completed.
You can simulate all these states using our GP tom Simulator, which you can find in the Download.
