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.
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).
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.
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.