Certifikace & Testovací scénáře

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.

MAKE AN APPOINTMENT FOR CERTIFICATION

Během certifikace s vámi absolvujeme následující testovací scénáře.
Scénáře 1–16 jsou společné pro všechny API, zatímco scénáře 17–20 se vztahují pouze na app2app API:

Scenario name

Checking the presence of GP tom

Successful transaction sale

Successful transaction return

Failed sale transaction

Timeout transaction sale

Exception during card payment

Cancellation of transaction

Deadline

Receipt data

DCC data - sale

DCC data – cancellation

Transaction registration

Request for payment

Getting the transaction status

Getting details about the transaction

Required

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 perform a successful return transaction.

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.

We will check the DCC data on the receipt for the scenario status=ACCEPTED, regionSchemaIndicator=1 and the transactionAmount will be with 3 decimal digits (amount 9991).

We will check the DCC data on the receipt for the scenario status=ACCEPTED, regionSchemaIndicator=1 and the transactionAmount will be without a decimal point (amount 9992).

We will check the DCC data on the receipt for the scenario status=ACCEPTED, regionSchemaIndicator=2 and the transactionAmount will be with 2 decimal numbers (amount 9993).

We check the DCC data on the receipt for the scenario status=ACCEPTED, regionSchemaIndicator=0 (amount 9994).

We check the DCC data on the receipt for the status=NOT_ACCEPTED scenario

We check the DCC data on the receipt for the transaction cancellation scenario with status=NOT_ACCEPTED

We check the DCC data on the receipt for the transaction cancellation scenario with status=ACCEPTED

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.

The receipt needs to display DCC data according to the visual, where we will specifically focus on the text "Markup" and the Transaction amount must be with 3 decimal places.

The receipt needs to display DCC data according to the visual, where we will specifically focus on the text "Markup" and the Transaction amount must be without decimal places.

The receipt needs to display DCC data according to the visual, where we will specifically focus on the text "Markup over ECB rate" and the Transaction amount must be with 2 decimal places.

The receipt needs to display DCC data according to the visual, where we will specifically focus on the text "Markup".

In this case, the customer has chosen to pay in the terminal currency and there is no need to display any DCC data on the receipt.

This is a cancellation of a classic transaction where no DCC data needs to be displayed.

This is a DCC transaction reversal, where you need to add the text “The transaction amount, currency and the exchange rate are the same as for the original transaction. The currency conversion is provided by Global Payments.”

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.

API

app2app, deep link, Cloud

app2app

Všechny tyto stavy můžete simulovat pomocí našeho GP tom Simulatoru, který najdete v sekci ke stažení.

Home

app2app API

Cloud API

iOS API

Certification & Test Scenarios

How do you like this tutorial?

Handbook