Skip to main content

Making payments in the test environment

The test payment gateway makes it possible to make a payment using the payment methods available.

For testing purposes a web interface has been built that simulates the behaviour of the payment method provider (e.g. Komerční banka, Tatra banka), or rather copies the communication with it as faithfully as possible.

💡 GoPay tip:

Enter the payment gateway test credentials into your technical solution and make test payments for orders from the point of view of a paying customer. The payment states should be reflected appropriately in the orders in your system.

Testing can be carried out from any domain.

If you are a new client, you will receive the test credentials after registering.

All operations in the GoPay payment gateway test environment are carried out with fictitious funds and customers must be prevented from accessing the GoPay payment gateway test interface.
​
Please note that the test environment is limited by default and some payment methods cannot be simulated, for example Apple Pay.


​

Test payment cards

We have prepared a set of test payment cards for you for testing the new payment gateway. The result of the authorisation depends on the amount used.

Card type

Card number

Country code of the payment card issuer

MasterCard

5447380000000006

CZE

VISA

4444444444444448

POL

The amount ends in

Example

Result

*00

10.00 CZK

Authorisation successful – payment paid

*04

15.04 EUR

Authorisation unsuccessful – payment declined

💡 GoPay tip:
You can enter any 3 numbers as the CVV/CVC code, e.g. 123, and you can enter any expiry date as long as it is in the future, e.g. 03/28.

The Premium SMS payment method

Payment via Premium SMS requires an SMS to be sent in the GP format.

A fictitious SMS can be sent via the web interface, see below. Within a few minutes of sending the virtual SMS message, the payment should be marked as paid at the merchant outlet.

If the payment gateway requires a verification code to be entered, please use the code given below.

The verification SMS code in the test environment

1111

​

Test scenario

To verify the integration we recommend making these test payments:

  1. Verifying that the payment gateway works correctly
    Making a test payment using all the required payment methods. You will find information about creating a standard payment in the article describing the payment gateway integration procedure.

  2. Verifying correct processing of the CANCELED

    state You can create a payment with the payment card payment method and then an amount with the result – payment declined.

    The second option is to select the online banking button payment method and, after being redirected to the test form, choose the cancel option.

    At the merchant outlet this payment should be marked as cancelled, CANCELED.

    The state is reflected by an automatic HTTP notification (the HTTP notification should be received by your solution with an HTTP 200 confirmation and, as part of the HTTP notification, asynchronously or afterwards, a payment status query should be made); you will find more information about notifications and how to process them in the article describing the payment gateway integration procedure and in the article payment status.

  3. Verifying correct processing of the TIMEOUTED
    state After moving to the payment gateway, close the payment gateway window. The change to the TIMEOUTED state occurs after 1 hour has elapsed. The payment state is reflected by an automatic http notification. You will find more information about notifications and how to process them in the article describing the payment gateway integration procedure and in the article payment status.

  4. Verifying the return to the merchant outlet without the payment being made, and the subsequent processing of the notification of the change in the payment state (payment made)

    • at the GoPay payment gateway, the bank transfer payment method is selected

    • after entering an e-mail address, the details for the bank transfer payment are generated (make a note of them). In the production environment the payment details are also sent to the customer by e-mail.

    • you then have to return to the merchant outlet using the cross in the top right corner and check the order status (it should be “Waiting for payment”).

    • you have to check the transition from the payment gateway to return_url and whether the customer is correctly shown that the bank transfer payment is awaited.

    • then you have to enter the link below into your browser and make the payment using the bank transfer details (the payment details displayed at the payment gateway)

Bank transfer

https://partner.sandbox.gopay.com/gp-gateways/bank/gateway.action

  • Enter the account number 7654322/0100 as the paying customer's account.

  • For payment in CZK, select 7654322/0800 as the target account.

  • For the EUR currency, select IBAN CZ1508000000000007654322, BIC GIBACZPX as the target account and enter the E-payment ID as the variable symbol.

  • After 3 minutes the payment state should change to paid.

Refunds

The test environment makes it possible to simulate a refund (returning a payment to the customer)
using the same payment method, with limited options compared with the production environment.
Refunds can be carried out from the interface of the test GoPay business account,
or by a request via the API.

A full refund is supported in the test environment by these methods:

  • Payment card

  • Online bank transfer (Raiffeisenbank and Česká spořitelna)

  • Offline bank transfer

A partial refund is supported in the test environment by these methods:

  • Online bank transfer (Raiffeisenbank and Česká spořitelna)

  • Offline bank transfer

Did this answer your question?