Skip to main content

Testing Your Integration

For a basic integration that only redirects the buyer to PayU, the public test point of sale (POS) is enough. To test all API messages, including refunds, set up your own account in the Sandbox environment.

The public test POS below works in the production environment (https://secure.payu.com). For the Sandbox environment, use the public Sandbox POS.

Public Test POS Credentials (Production)
POS ID (pos_id):                    145227  
Second key (MD5):                   13a980d4f851f3d9a1cfc792fb1f5e50  
OAuth protocol - client_id:         145227  
OAuth protocol - client_secret:     12f071174cb7eb79d4aac5bc2f07563f

Test Cases​

Use the following test cases to make sure your website handles these scenarios correctly:

  1. Verify that the buyer is redirected to PayU when PayU responds with HTTP 302 to your POST request to the /api/v2_1/orders endpoint.
  2. Confirm that you receive and parse PayU notifications correctly and respond with HTTP 200.
  3. Ensure you correctly establish the order status during its lifecycle. Keep in mind that order status is provided only via notifications, while the status returned in the response applies only to the request, not to the order.
  4. Check that you provide the continueUrl parameter and that the buyer is redirected to this URL after the payment.
  5. Be prepared to handle the error message passed in the query string added to the continueUrl.
  6. For card tokenization, make sure your website handles all payment authorization scenarios.

Test cases 1 and 2 can be performed in the Management Panel or through the API.

Topics in this Section

On this page