Page Comparison

...

<Secure3d>true</Secure3d>
 
<SupportedPaymentMethods>CREDITCARD_TOKEN</SupportedPaymentMethods>
 
<Customer FirstName="John" LastName="Doe" CountryCode="27" Mobile="27999220020" MerchantUserId="Merch000001"/>
 
<Customfield>
  <Customfield Key="processingType" Value="REAL_TIME_RECURRING"/>
</Customfield>

...

Integration payment sequence/flow

When developing a solution with PayU's redirect some de-risking of transactions can be done be performing a transaction.

Set-up flow with Secure 3D de-risking:

Image Added

Real-time recurring transaction chargeback risk is with the merchant. In order to validate card holder and de-risk the recurring transaction a normal eCommerce transaction can be done prior to a recurring set-up transaction. With redirect transactions PayU will handle all the the necessary actions required provided the setTransaction call include the instruction to perform Secure 3D authentication.

• Step 1
  • Merchant user logged into Merchant user management system.
• Step 2
  • User makes product selections, proceeds to checkout and selects to complete transaction.
    • Merchant system sends setTransaction call to PayU.
      • Secure3d = TRUE, SupportedPaymentMethods= CREDITCARD_TOKEN, merchantUserId=MerchantSuppliedIDValue, processingType=REAL_TIME_RECURRING
    • Merchant site redirects user to PayU hosted payment pages.
  • PayU displays required page, allows user to capture card and perform necessary Secure 3D actions, perform recurring setup and tokenise card for future transactions.
• Step 3
  • On redirect back to the merchant a getTransaction and/or IPN is used to perform lookup of the transaction outcome and token value. Merchant saves this token against the merchantUserId.
• Step 4
  • Merchant display results and update transaction status as required.

Set-up flow without any de-risk (Fraud checks can be added)

Image Added

Real-time recurring transaction chargeback risk is with the merchant. In this flow the merchant might perform other fraud check and do not have the requirement for additional de-risking.

• Step 1
  • Merchant user logged into Merchant user management system.
• Step 2
  • User makes product selections, proceeds to checkout and selects to complete transaction.
    • Merchant system sends setTransaction call to PayU.
      • Secure3d = FALSE, SupportedPaymentMethods= CREDITCARD_TOKEN, merchantUserId=MerchantSuppliedIDValue, processingType=REAL_TIME_RECURRING
    • Merchant site redirects user to PayU hosted payment pages.
  • PayU displays required page, allows user to capture card and perform recurring setup and tokenise card for future transactions.
• Step 3
  • On redirect back to the merchant a getTransaction and/or IPN is used to perform lookup of the transaction outcome and token value. Merchant saves this token against the merchantUserId.
• Step 4
  • Merchant display results and update transaction status as required.

Transaction flow for recurring transactions beyond set-up (Front end - user driven)

Image Added

This flow allows the merchant to enable a quick checkout experience by sending a token to PayU for a recurring transaction. The user needs to provide permission for a quick checkout via recurring transaction and the merchant accepts all fraud related transaction charge backs.

• Step 1
  • Merchant user logged into Merchant user management system.
• Step 2
  • User makes product selections, proceeds to checkout and selects to complete transaction.
    • Merchant system sends setTransaction call to PayU.
      • Secure3d = FALSE, SupportedPaymentMethods= CREDITCARD_TOKEN, merchantUserId=MerchantSuppliedIDValue, processingType=REAL_TIME_RECURRING
    • Merchant site redirects user to PayU hosted payment pages.
  • PayU displays required page, checks if merchantUserId have saved cards, if yes perform recurring transaction. If no card exist setup and tokenise flow is followed.
• Step 3
  • On redirect back to the merchant a getTransaction and/or IPN is used to perform lookup of the transaction outcome and token value. Merchant updates this token against the merchantUserId if required.
• Step 4
  • Merchant display results and update transaction status as required.

API call examples

Please refer to the setTransaction API example page for more information

...