Model 1 - PayU Hosted Checkout Integration

This part of the documentation describes the workflow and how the cards are saved in the vault with PayU Hosted Checkout Integration.



If you are an existing PayU vault user, you do not need to make any changes.

If you are not using the PayU vault, you need to ensure the following:

  • You need to contact your PayU Key Account Manager to get the vault enabled for your merchant ID.
  • After your customer logs on to your website, pass the customer’s user ID to identify and list the user’s saved cards on the PayU Checkout page. This is an extra parameter in the _payment API with which you already integrated. For more information, refer to Repeat Transaction Workflow-Model 1.

For more information on the complete list of parameters for PayU Hosted Checkout Integration, refer to the Collect Payment API - PayU Hosted Checkout under API Reference.

First-time transaction workflow

The first-time transaction workflow for Redirection Flow (PayU Hosted) integration with vault involves:

  1. The customer lands on the PayU checkout page.
  2. The customer enters the card details on the PayU Checkout page.
  1. The customer gives explicit consent to save the cards.
  1. PayU completes the transaction and saves the card in PayU Vault.

PayU displays the payment confirmation similar to the following screenshot.

Repeat transaction workflow

The repeat or subsequent transactions workflow for Redirection Flow (PayU Hosted Checkout) integration involves the following steps:

  1. The customer lands on the PayU Checkout page.
  1. The customer is listed with the saved cards on the PayU Checkout page along with the payment options.

  1. The customer only enters the CVV in case of cards and proceeds with the transaction.