Available Environments

Production

Sandbox

Testing

Sandbox users have the opportunity to test all available functionalities – these are enabled by default for all registered accounts.

Card Payments

For the Sandbox environment, we have prepared a set of test payment cards. It is not possible to conduct transactions using cards with other numbers.

Additionally, it is possible to test 3DS validation according to the following rules:

Regardless of the amounts above, there are several fixed amounts on the Sandbox that trigger errors:

Visa Mobile

Payment with Visa Mobile is based on customers phone number. Phone number can be provided via:

• in payer.phone field in API call to create transaction
• read from frontend component on Tpay transaction portal (only when not provided during transaction creation)

Transaction values allowing for the testing of different scenarios:

Google Pay - test cards

To correctly test the Google Pay integration with Tpay in the Sandbox environment, use the Google test card suite.

Google test cards allow you to:

• Test the payment process without providing real payment card data
• Successfully complete tasks from the Google integration checklist, which is necessary to obtain production access: checklist

If you want to use test cards:

1. Join the test card suite user group: group
2. After entering the site, click the Join group button: googlepay-support-tpay
3. Then, after refreshing the page, You have access to test cards!

Apple Pay

It is possible to test Apple Pay. However, it is necessary to open the link to the created transaction on an iOS device with a configured Apple Pay wallet and a real payment card added. The card is not charged during the process. As with cards and Google Pay, error amounts 500.00, 501.00, 503.00 are supported.

BLIK Payments

Testing payments using the BLIK channel requires providing an authorization code. For test payments, the correct authorization code must start with 777, e.g., 777654.

There are also test amounts that, even if a correct code is provided (i.e., starting with 777) will result in failed payment.

Table below shows selected amounts and corresponding errors.

BLIK payment can be extended by saving a user alias, allowing them to pay without having to provide a BLIK code the next time. The alias is a unique string of characters generated in the merchant's system; the alias type is UID.

To register a PAYID alias in the sandbox environment, two methods can be used:

• Registration via code

• Registration via transaction amount for 777*** codes

When registering via amount, X represents an integer value; example amount values are 10.08, 15.10, 33.15. In this case, codes starting with 777 with any 6-digit completion should be used.

In the sandbox environment, you can test a situation where the bank does not support the BLIK Recurring Payments alias. To trigger the message, use the amount 495.00, any 777*** code, and enter mock in the description field.

Instant Transfer (online, fast)

To test this payment method, select the Bank Transfer option in the payment gateway, and then choose the bank where the payment is to be finalized.

The Sandbox environment mirrors production behavior; therefore, in the case of a negative path, a message about waiting for payment will appear, as banks do not send information about abandoned payments.

Click to Pay

Merchant Onboarding to Click to Pay

For a merchant to process Click to Pay payments, they must have Elavon set as the acquirer for card payments. Merchant onboarding to Click to Pay happens automatically when Elavon card payments are activated in Tpay. All payments processed via the Click to Pay channel will be labeled as Click to Pay in the Merchant Panel.

Click to Pay Payments

To perform a test Click to Pay payment, it is required to have a test payer profile in the Click to Pay service run jointly by Visa and Mastercard. To create a test payer profile in Click to Pay, perform a transaction with card saving, checking the +Save card in Click to Pay_ checkbox and filling in the required data on the card saving form.

Alternatively, a test Click to Pay profile can be created and managed directly at Mastercard or Visa. For the next transaction made with the email registered in the test Click to Pay profile, an OTP (one-time password) form will be displayed during payment, where you should enter the six-digit code received via SMS and/or email. After correct authorization, the saved cards available for payment will be displayed.

If the Add device to trusted checkbox is selected during OTP authorization, OTP will no longer be required.

Click to Pay Test Cards

Real payment cards should not be used in the test environment. To test a payment, use the test cards provided by Visa and Mastercard.

Test cards dedicated to Click to Pay from Mastercard are available at this link.

Test cards dedicated to Click to Pay from Visa are:

In the case of Click to Pay, you can also test payer authentication using 3DS (same rules as for standard card payments), and error amounts 500.00, 501.00, 503.00 are also supported.