...
- Merchant's website issues a doTransaction SOAP call against PayU's API
- PayU's API reponds with the result of the transaction:
2.1. If <secure3D> is not present in the response - indicating that the card is not enrolled:
2.1.1. Validate whether transaction was failed or successful against the API response
2.1.2. No further processing required and website indicates payment result to the customer.
2.2. If <secure3D> is present in the response - indicating that the card is enrolled:
2.2.1. Present the <secure3DUrl></secure3DUrl> tag content to the browser which will redirect the customer to the bank's 3D Secure page
2.2.2. Customer receives OTP via SMS
2.2.3. Customer enters the received OTP on bank's 3D Secure page - Browser automatically redirects customer back to PayU where a message is briefly displayed.
- Browser automatically redirects customer back to merchant's website (url specified within returnUrl parameter).
- Merchant website issues a getTransaction SOAP call against PayU's API from merchant's website and validates payment result e.g. payment successful or declined as per Transaction result validation. The merchant will also recieve an
- IPN to the url specified within notificationUrl parameter with the result of the transaction.
| Warning |
|---|
| It should be noted that the sequence set out in this document (as well as above and flowchart below), is only for a golden path integration. |
...
3D
...
3D Secure OTP page examples
Example of intermediate redirect page to bank/card issuer's 3D secure OTP capture page
Example of bank/card issuer's 3D secure OTP capture page
API call examples
...