Collect Payments using a Saved Card

PayU offers you API to save the card details and retrieves them using the Store Card APIs. For example, the stored cards are displayed when your customer performs checkout and lands on the payment page.

This section explains the procedure for getting a customer’s card details and using a saved card to initiate payment.

For all the scenarios mentioned in this section you must follow the

1. Get the saved card details: Get the customer’s card details your merchant key and customer’s registered mail ID to PayU using the get_user_details API. For more information, refer to Get User Cards API - Model 3 API under API Reference.

2. Post Payment to PayU and check response: Make the transaction request with the payment details along with the card nickname to PayU based on the following scenarios of tokenization. For more information, refer to

   • Using complete card details

   • Using network tokens

   📘

   Notes:

   • In addition to the request parameters used for Merchant Hosted Checkout (Seamless integration) payment request, you need to ensure the additional parameters as specified in each scenario specified in this step. For more information on the complete list of parameters, refer to Integrate with Merchant Hosted Checkout.
   • The additional response parameters (if any) are specified for each scenario. For the sample response for a card payment using Merchant Hosted Checkout response, refer to Collect Payment API - Merchant Hosted Checkout

3. Verify the Payment: Verify the transaction details using the Verification APIs. Post the transaction ID using the verify_payment API to verify the payment. For more information, refer to Verify Payment API

Using complete card details

This scenario is applicable where a customer is providing the complete card number do the transaction (Card number, Expiry, CVV, and name on card) 

Applicable Scenarios

• It is a guest checkout  
• It is a standard checkout request where there is no need to save the card 

📘

Note:

Plain card details coming from the merchant, so no changes are applicable in the request & response.

For the sample request and response, refer to Using Complete Card Details

Using network tokens

This scenario is applicable if you wanted to collect payments using network tokens.

Applicable scenarios

• Merchant has the card token, TAVV(Cryptogram), and the last four digits of the card 
• The token could be created by the merchant or through another partner 

📘

Note:

This scenario is applicable if you are PCI compliant and got the network token and TAVV from any other aggregator or schemes and then sending the card transaction request in the form of authentication.

For the sample request and response, refer to Using Network Tokens