PayU test cards

Use these details to try payments in a PayU sandbox (test) account. They work only in the sandbox: never use them in live, and never put real card or bank details into a sandbox.

The test cards depend on which PayU integration you use (see Connecting PayU). For the REST API, register a PayU sandbox account with just an email address, or use the public test POS that PayU lists on its Sandbox Environment page. For the Payment Engine, PayU publishes test cards for the India and South Africa products only. For Turkey and Single Platform, this page lists the cards our own tests use: ask PayU for the current details.

Where these details come from

These are PayU’s test details, not ours. They were copied from PayU’s Sandbox Environment page and its Payment Engine (PaymentsOS) PayU India and PayU South Africa pages on 19 October 2026, and were correct on that date as far as those pages show. PayU can change or withdraw them at any time, and we can’t confirm that they work. Check PayU’s pages for the current details, and ask PayU if one doesn’t behave as described. The Turkey and Single Platform cards are the ones our own tests use, not cards PayU publishes for those products.

How to choose a test result

• The card number sets the result, and each integration has its own cards: check which one your connection uses (Integration Type and Product in the PayU connection here). See PayU’s Sandbox Environment, PayU India and PayU South Africa pages.
• REST API: every test card goes through 3D Secure 2, and is frictionless unless the card says otherwise (Sandbox Environment).
• REST API: some cards are approved only below 1,000 minor units (Sandbox Environment). We convert the amount into minor units for PayU, so enter the amount in the checkout as usual: in a currency with two decimal places, 9.99 is approved and 10.00 is not.
• Payment Engine India: you choose the 3D Secure result by entering a code on PayU’s test authentication page, not in the checkout (PayU India).
• To save cards with the REST API, tick Enable tokenization in the PayU connection here. PayU must first turn on multi-use tokens and zero-amount orders for your POS (Connecting PayU).

Cards: REST API

Use expiry date 12/29 and CVC 123 unless a row says otherwise. PayU says every test card goes through 3D Secure 2, with frictionless authentication unless a row says otherwise.

Successful payments

Card	Number	Notes
Visa	4444 3333 2222 1111	Approved. Can’t be saved for later payments
Mastercard	5434 0210 1682 4014	Approved. Can’t be saved for later payments
Mastercard	5598 6148 1656 3766	Approved. Can’t be saved for later payments

Declines and errors

Number or trigger	Result
5000 1050 1812 6595	Declined
4000 3982 8436 0	Declined
5405 8609 3727 0285	Approved about half the time, declined otherwise
4532 5980 2110 4999	Approved only for amounts below 1,000 minor units of the currency (for example, below 10.00)

3D Secure

Number	Result
4245 7576 6634 9685	Challenge, then approved
5150 0300 9035 0186	3DS Method, then frictionless and approved
4012 0010 3714 1120	3DS Method and challenge, then approved
5100 0523 8453 6818	Challenge, then approved. Without 3D Secure, a soft decline. Expiry date 02/32
4210 8363 9374 2163	Challenge, then approved only for amounts below 1,000 minor units of the currency
5521 4551 8657 7727	Frictionless, authentication fails: not authorised
4147 1393 0369 3610 4147 1393 0369 3628	Challenge, only if your sandbox account was registered with Romania as its main market

PayU lists more cards, including cards for Romanian instalments, on its Sandbox Environment page.

Cards: Payment Engine (India)

Use any future expiry date and CVC 123.

Successful payments

Card	Number	Notes
Debit or credit card	4854 4601 9876 5435
Debit or credit card	5123 4567 8901 2346	For recurring payments

3D Secure

PayU India shows a test authentication page. Enter one of these codes:

Value	Result
123456	Authenticated
000000	Authentication fails

Cards: Payment Engine (South Africa)

PayU’s page says to use CVC 123 with these cards. It gives the expiry 02/2026, which has passed. Our own tests with PayU South Africa’s sandbox use 12/30.

Successful payments

Card	Number	Notes
Visa	4000 0195 4243 8801	Approved. Not enrolled in 3D Secure
Mastercard	5100 0110 6355 5010	Approved. Not enrolled in 3D Secure

Declines and errors

Number or trigger	Result
Visa 4000 0295 2027 2445	3D Secure authenticated, then declined by the bank
Mastercard 5100 0226 1534 2534	3D Secure authenticated, then declined by the bank

3D Secure

Number	Result
Visa 4000 0153 7225 0142	Authenticated, then approved
Mastercard 5100 0186 0908 6541	Authenticated, then approved
Visa 4000 0195 6209 3601	Authentication fails: payment fails
Mastercard 5100 0139 6091 3581	Authentication fails: payment fails

Cards: Payment Engine (Turkey and Single Platform)

PayU doesn’t publish test cards for these products. Our own tests with PayU’s sandbox use these cards, with expiry 12/30 and CVC 123.

Product	Card	Number	Notes
Turkey	Mastercard	5400 0100 0000 0004	Approved. Used in our own tests
Single Platform	Visa	4444 3333 2222 1111	Approved for MOTO (staff-entered) payments. Online payments can go to 3D Secure first. Used in our own tests
Single Platform	Visa	4245 7576 6634 9685	Goes to 3D Secure for online payments. Approved without 3D Secure for MOTO payments. Used in our own tests