Integration overview (RPP)

Integration into PayU's Redirect Payment Page (RPP) is accomplished by using a combination of server side API calls and HTTPS redirects. API calls can be implemented in one of two ways: XML over HTTPS or SOAP API calls.

In order to complete a successful integration, it is recommended to first do a test integration against the PayU staging environment with details given in the test overview section, before moving to the production environment. Once the test integration process is complete, the staging details will need to be substituted with the production details. These details will be provided by PayU once confirmation of a successful test integration has been received.

Example customer payment sequence

`A summarised simple payment sequence integration is:` `1. Do a setTransaction SOAP call against PayU's API from merchant's website` `2. Redirect browser to the PayU payment page` `3. Customer submits and gets redirected back to merchant's website` `4. Do a getTransaction SOAP call against PayU's API from merchant's website to get transaction payment details e.g. payment successful or declined`

`A summarised simple payment sequence integration is:` `1. Do a setTransaction SOAP call against PayU's API from merchant's website` `2. Redirect browser to the PayU payment page` `3. Customer submits and gets redirected back to merchant's website` `4. Do a getTransaction SOAP call against PayU's API from merchant's website to get transaction payment details e.g. payment successful or declined`

It should be noted that the sequence set out above, is only for a golden path integration and more test cases as well as recommendations are given in test overview section. The summarized payment sequence can change and is dependent on the transaction type used in the setTransaction call, but this is explained in more detail in the transaction types section later on.