API Reference
Start typing to search…

Using Network Tokens

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

HTTP Method: POST

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.

Request Parameters

Parameter Description Example
key
mandatory 		String The merchant key is a unique identifier for a merchant account in PayU's database. Your Test Key
api_version
optional 		String The API version for this API. 1
txnid
mandatory 		String The transaction ID is a reference number for a specific order that is generated by the merchant. It is used to track the order and must be unique. PayU's system will not accept duplicate transaction IDs. s7hhDQVWvbhBdN
amount
mandatory 		String This field should contain the payment amount for the transaction. If you want to use the cardless EMI option, the amount must be at least Rs. 8000 10.00
productinfo
mandatory 		String It should be a string containing a brief description of the product.``` Character Limit-100 ``` iPhone
firstname
mandatory 		String The first name of the customer.``` Character Limit-60 ``` Ashish
email
mandatory 		String The email of the customer.``` Character Limit-50 ``` [[email protected]](mailto:[email protected])
phone
mandatory 		String The phone number of the customer. * *Note**: This information is helpful when it comes to issues related to fraud detection and chargebacks. Hence, it is must to provide the correct information. 9876543210
lastname
mandatory 		String The last name of the customer.``` Character Limit-60 ``` Verma
address1
optional 		String The first line of the billing address.``` Character Limit-100 ``` H.No- 17, Block C, Kalyan Bldg, Khardilkar Road, Mumbai
address2
optional 		String The second line of the billing address.Character Limit-100 34 Saikripa-Estate, Tilak Nagar
city
optional 		String The city where your customer resides as part of the billing address. Mumbai
state
optional 		String The state where your customer resides as part of the billing address, Maharashtra
country
optional 		String The country where your customer resides.Character Limit-50 India
zipcode
optional 		String Billing address zip code is mandatory for the cardless EMI option.``` Character Limit-20 ``` 400004
surl
mandatory 		String The "surl" field is the success URL, which is the page PayU will redirect to if the transaction is successful. The merchant can handle the response at this URL after the customer is redirected there. [https://apiplayground-response.herokuapp.com/](https://apiplayground-response.herokuapp.com/)
furl
mandatory 		String The "furl" field is the Failure URL, which is the page PayU will redirect to if the transaction is failed. The merchant can handle the response at this URL after the customer is redirected there. [https://apiplayground-response.herokuapp.com/](https://apiplayground-response.herokuapp.com/)
hash
mandatory 		String It is used to avoid the possibility of transaction tampering. For more information on hash generation process, refer to [Generate Hash](doc:generate-hash-merchant-hosted). eabec285da28fd 0e3054d41a4d24fe 9f7599c9d0b6664 6f7a9984303fd612 4044b6206daf831 e9a8bda28a6200d 318293a13d6c193 109b60bd4b4f8b09 c90972
pg
mandatory 		String The pg parameter determines which payment tabs will be displayed. Here, use 'CC' as the value. CC
bankcode
mandatory 		String Each payment option is identified with a unique bank code at PayU. The merchant must post this parameter with the corresponding payment option's bank code value in it. AMEX
udf1 - udf5
optional 		String User-defined fields (udf) are used to store any information corresponding to a particular transaction. You can use up to five udfs in the post designated as udf1, udf2, udf3, udf4, udf5. Character Limit-255 Payment Preference, Shipping Method, Shipping Address1, Shipping City, Shipping Zip Code, etc.
ccnum
optional 		varchar This parameter must contain the 13 to 19-digit card number for credit or debit cards in general. 512***6789012346
ccname
optional 		varchar It is the customer's name on card. Ashish
ccvv
optional 		varchar This parameter must contain the CVV number of the card – as entered by the customer for the transaction. 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 Network 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 1. 1
additional_info
mandatory 		varchar This parameter will contain the additional information in the following JSON format: {"last4Digits": "1234", "TAVV": "ABCDEFGH","trid":"1234567890", "tokenRefNo":"abcde123456"} {"last4Digits": "1234", "tavv": "ABCDEFGH","trid":"1234567890", "tokenRefNo":"abcde123456"}

📘

Notes for additional_info:

  • The last 4 digits of cards is mandatory for all transactions.
  • Some payment gateways require the Token Requester ID (trid) and Token Reference Number (tokenRefNo) to be passed for processing the transaction. Not passing these values will restrict the number of payment gateways available for processing the transaction.
  • Token Requester ID (trid) and Token Reference Number (tokenRefNo) are mandatory for Diners token transactions.

Response

There are no changes in the response, it will remain as it is like the existing plain card number.