Sandbox Environment

The Sandbox environment is a near-replica of PayU's production system, designed for integration and testing purposes. To access the test environment, you need to register separately with just an email address. After registering and creating a store and payment point, you will have the ability to perform test transactions. This allows you to simulate various scenarios and evaluate the functionality of your integration before deploying it in the live production environment.

Traffic limitations in the Sandbox environment

The Sandbox environment is not designed for performance testing. If excessive traffic is detected, access will be temporarily blocked, and the client will receive an HTTP 429 response code.

Sandbox availability status

You can check the availability of the sandbox environment at the status page.

Testing options

If you intend to test PayU integration in a sandbox environment, there is no requirement to create your own account. You can utilize the public test Point of Sale (POS), for which we have provided the authorization keys below. However, we recommend creating your own account to gain access to a fully customizable administration panel, providing greater control and flexibility during your testing and integration process.

Public POS

Credentials of the Public POS on the Sandbox Environment

POS ID (pos_id):                    300746
Second key (MD5):                   b6ca15b0d1020e8094d9b5f8d163db54
OAuth protocol - client_id:         300746
OAuth protocol - client_secret:     2ee86a66e5d97e3fadc400c9f19b065d

Your Sandbox Account

To access your personal test management panel, start by registering at the sandbox environment. Providing your email address on the registration page is enough. After submitting your email address, you will receive an email containing a link to set up a password for your account. Once you complete this step, proceed to log in using the same email address. This will grant you entry into your new account within the Sandbox, where you can fully explore and customize your test environment to conduct thorough integration and testing activities.

Available Functionalities

Pay-by-link payments

Polish Transfers

• mTransfer - mBank (m),
• Płać z iPKO (p),
• Pekao24Przelew - BankPekao (o).

Czech Transfers

• Česká spořitelna (cs),
• Komerční banka (kb).

Slovak Transfers

• (besteron) Tatra banka, a. s. (tatra),
• Slovenská sporiteľňa, a. s. (sporo).

Additional (random) data about buyer (to retrieve with retrieving transaction data service) is available only for methods:

• Pekao24Przelew - Bank Pekao (o) (the next day),
• Komerční banka (kb) (instantly).

Other Functionalities

• Apple Pay,
• BLIK,
• Google Pay,
• Mass Collect,
• Recurring Payments,
• PayU Installments,
• Pay Later,
• Visa Checkout,
• PayU|Mobile (Android and iOS),
• Payouts (Panel, API),
• Statements,
• Refunds (Panel, API).

Test Cards

3DS 2 Support

OneClick payments with the test cards require a CVV unless specified otherwise in the Behavior column.

---

Due to SCA/PSD2 requirements, test cards with a default value in the 3DS Result column cannot be used to store the card/token.

All test cards support authentication via the 3DS 2 protocol, resulting in a successful frictionless authentication unless stated otherwise.

In practice this means that all orders with card token or card number in plain text as a payment method will return WARNING_CONTINUE_3DS status, unless the order is out of scope of SCA (like recurring payments or MOTO).

In order to test card payments on sandbox, please use the following credentials.

Available Test Cards on the Sandbox Environment

Number	Month	Year	CVV	3DS Result	Behavior
4444333322221111	12	29	123	default	Positive authorization.
5434021016824014	12	29	123	default	Positive authorization.
5598614816563766	12	29	123	default	Positive authorization.
5000105018126595	12	29	123	default	Negative authorization.
4000398284360	12	29	123	default	Negative authorization.
4245757666349685	12	29	123	Challenge required.	Positive authorization.
5150030090350186	12	29	123	3DS Method required and then successful frictionless.	Positive authorization.
4012001037141120	12	29	123	3DS Method and challenge required.	Positive authorization.
5100052384536834	12	29	123	Challenge params if sdk object sent in the order request.	Positive authorization.
5100052384536818	02	32	123	Challenge required / if no 3DS is used, returns soft decline (SSD).	Positive authorization.
5521455186577727	12	29	123	Frictionless negative authentication.	No authorization (authentication fails).
5405860937270285	12	29	123	default	50% chance for successful authorization.
4532598021104999	12	29	123	default	Successful authorization only for amount below 1000 minor units of given currency.
4210836393742163	12	29	123	Challenge	Successful authorization only for amount below 1000 minor units of given currency.
5436062405627681	12	29	123	challange	For amounts greater than 300 minor units, iframeAllowed takes a value of false.