Cards Consent Transaction

key
mandatory

String The merchant key is a unique identifier for a merchant account in PayU's database. For more information, Check your API Key and Salt.

Your Test Key

api_version
optional

ng` The API version for this API.

7

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.
Note: The transaction limit are as per the card holders limit or Rs.10,00,000 (if the card limit is more than Rs.10,00,000).

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]

phone
mandatory

String The phone number of the customer.

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

si
mandatory

This parameter signifies a successful consent taken from the user by the merchant. This parameter must contain 1 for a successful consent. Without this parameter sent as 1, subscription cannot be set up.
Notes: You can modify or cancel existing recurring payment registration as described in the following sections:
_. Manage Recurring Payment for Cards
_. Manage UPI Recurring Transaction

1

si_details
mandatory

This parameter represents mandatory details which need to be passed to during registration transaction from merchant system to PayU.

Note: It is mandatory as per the latest RBI guidelines to pass this information to the payment processor so that same can be forwarded to acquirers and issuers ( for more details refer – https://www.rbi.org.in/Scripts/NotificationUser.aspx?Id=11668&Mode=0 )

This is a JSON object and it includes a set of fields. For more information, refer to SI Parameter JSON Details

hash
mandatory

String It is used to avoid the possibility of transaction tampering. For more information on hash generation process, refer to Hashing Request and Response.
In the case of registration transaction, the formula is used to calculate this hash is similar to the following:
HASH = SHA512(key|txnid|amount|productinfo|firstname|email|udf1|udf2|udf3|udf4|udf5||||||si_details|SALT)

eabec285da28fd
0e3054d41a4d24fe
9f7599c9d0b6664
6f7a9984303fd612
4044b6206daf831
e9a8bda28a6200d
318293a13d6c193
109b60bd4b4f8b09
c90972

pg
mandatory

String The pg parameter must include 'CC' for cards.

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.
 For more information, refer Card Type Codes and Supported Banks for Cards

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
conditional

IntegerThis parameter must contain the card number.
This parameter is required if you are trying to create a mandate using the card details.

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. For stored card using network or issuer, enter the expiry month of the token.

10

ccexpyr
mandatory

integer This parameter must contain the network token expiry year.. For stored card using network or issuer, enter the expiry year of the token.

2022

store_card_token
conditional

varchar This must include the Network token generated at your end.
This parameter is required if you are using the stored card token to register the mandate.

1234 4567 2456 3566

storecard_token_type
conditional

integer This parameter is used to specify the store card token type. It must include any of the following values:

• 0: If PayU token is used.
• 1: If Network token is used.
• 2: If Issuer token is used.
  This parameter is required if you are using the stored card token to register the mandate.

1

additional_info
conditional

varchar This parameter will contain the additional information in the following JSON format:{“last4Digits”: “1234”, “tavv”: “ABCDEFGH”,”trid”:”1234567890”, “tokenRefNo”:”abcde123456”}
This parameter is required if you are using the stored card token to register the mandate, where network or issuer token is used.

{“last4Digits”: “1234”, “tavv”: “ABCDEFGH”,”trid”:”1234567890”, “tokenRefNo”:”abcde123456”}

free_trial
conditional

This is mandatory only if the merchant wants to support free trial use case with card and net banking together that too on PayU Hosted Checkout integration.

In this case, PayU adjusts the transaction amount as INR 2.00 for cards. INR 0.00 for Net Banking and UPI registration irrespective of what amount is passed against the amount field in the request.
This parameter has no significance in the case of seamless flow.