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, similar to the following screenshot where they need to enter only the CVV:
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
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 Details API ~~under API Reference.
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:
- Using zero code change approach
- Using complete card details
- Using network tokens
- Using issuer tokens
- Using card tokenized with PayU
- Using card on a decoupled flow with network token or other partner tokenization
- Using card on a decoupled flow with PayU tokenization
- 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
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
If the merchant wants PayU to tokenize the card using a zero code change approach (Model 2), use the request parameters as described in this section.
- Merchant wants to create tokens without making any integration changes at their end
- Merchant is using PayU as a partner for tokenization
This scenario is applicable if any merchant sends the plain card request to PayU and shares the consent for saving the card details.
For the sample request and response, refer to Zero Code Change - Model 2.
This scenario is applicable where a customer is providing the complete card number do the transaction (Card number, Expiry, CVV, and name on card)
- It is a guest checkout
- It is a standard checkout request where there is no need to save the card
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
This scenario is applicable if you wanted to collect payments using network tokens.
- Merchant has the
TAVV(Cryptogram), and the last four digits of the card
- The token could be created by the merchant or through another partner
This scenario is applicable if you are PCI compliant and got the network token and
TAVVfrom 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
This scenario is applicable if you wanted to collect payments using issuer tokens.
- Merchant has the
tokenReferenceId, and the last four digits of the card
- The token could be created by the issuer
This scenario is applicable if you are PCI compliant and got the
tokenReferenceIdand then sending the card transaction request in the form of authentication.
For the sample request and response, refer to Using Issuer Tokens.
If the merchant has tokenized the card with PayU and needs to process the transaction using PayU token only.
- Merchant has created the token using PayU as the partner
This scenario is applicable if any PCI or Non-PCI complied merchant sends the PayU token in a request for fulfilment purposes.
For the sample request and response, refer to Using Card Tokenized with PayU.
This scenario is applicable where you are on a decoupled flow. This is where you are using the PayU for either authentication or authorization only while using tokens created by the network or some other partner.
Decoupled flow: You are sending the authentication request to PayU and if the merchant wishes to send the authorization request eventually or to other aggregators.
For the sample request and response, refer to Using Card on a Decoupled Flow with Network Token or Other Partner Tokenization.
This scenario is the application on a decoupled flow using the PayU for either authentication or authorization only with tokens created in partnership with PayU.
Direct Authorisation Flow: When you have done the authentication from some other aggregator and authorization request is coming to PayU.
For the sample request and response, refer to Using Card on a Decoupled Flow with PayU Tokenization.
Updated 10 days ago