This scenario is applicable if you wanted to collect payments using issuer tokens.
HTTP Method: POST
Environment
| Test Environment | https://test.payu.in/_payment |
| Production Environment | https://secure.payu.in/_payment |
Applicable scenarios
- Merchant has the card token, trMerchantId, tokenReferenceId, and the last four digits of the card
- The token could be created by the issuer
Note
This scenario is applicable if you are PCI compliant and got the issuer token, trMerchantId, and tokenReferenceId and then sending the card transaction request in the form of authentication.
Additional parameters
| Parameter | Description | Value |
|---|---|---|
| ccvv mandatory | varchar This parameter must contain the CVV number of the card – as entered by the customer for the transaction.Note: If your customer is returning to your website to shop, you must fetch all the customer's stored cards from PayU, collect the CVV for the card the customer will be using to make payment and then post the CVV number to PayU. | 123 |
| ccexpmon mandatory | integer This parameter must contain the network token expiry month. | 10 |
| ccexpyr mandatory | integer This parameter must contain the network token expiry year. | 2022 |
| store_card_token mandatory | varchar This must include the issuer token generated at your end. | 1234 4567 2456 3566 |
| storecard_token_type mandatory | integer This parameter is used to specify the store card token type. For this scenario, you must include 2. | 2 |
| additional_info mandatory | varchar` This parameter will contain the additional information in the following JSON format: {"trMerchantId":"INBANPAYUWIBPAY011","tokenReferenceId":"02ac786d-0081-4b1a-a2a6-b0755a83964c"," tokenBank":"HDFC","last4Digits":"8179"} | {"trMerchantId":"INBANPAYUWIBPAY011","tokenReferenceId":"02ac786d-0081-4b1a-a2a6-b0755a83964c","tokenBank":"HDFC","last4Digits":"8179"} |
Response
There are no changes in the response, it will remain as it is like the existing plain card number.