Credit / Debit Card transaction

This table lists valid combinations for emi_bank and emi_tenure, although you need to check if bank has approved all the tenures for your gateway account. JusPay does not validate this for you.

EMI Bank	EMI Tenure	Supported Gateways
HDFC	3,6,9,12,18,24	PAYU, HDFC, RAZORPAY, BILLDESK
CITI	3,6,9,12,18,24	PAYU
ICICI	3,6,9,12,18,24	PAYU, ICICI, CCAVENUE, RAZORPAY,BILLDESK
SBI	3,6,9,12	PAYU, CCAVENUE, BILLDESK
AXIS	3,6,9,12	PAYU, ICICI, CCAVENUE, RAZORPAY, BILLDESK
SCB	3,6,9,12,18,24	ICICI, PAYU,BILLDESK
KOTAK	3,6,9,12	ICICI, CCAVENUE, PAYU, RAZORPAY, BILLDESK
HSBC	3,6,9,12	ICICI, CCAVENUE, PAYU, BILLDESK
AMEX	3,6,9,12	PAYU, CCAVENUE, RAZORPAY
INDUSIND	3,6,9,12,18,24	PAYU, CCAVENUE, RAZORPAY
RBL	3,6,9,12,18,24	RAZORPAY, PAYU,BILLDESK
YES	3,6,9,12,18,24	PAYU, BILLDESK
ICICIDC	3,6,9,12	PAYU
AXISDC	3,6,9,12	PAYU
HDFCDC	3,6,9,12,18	PAYU, BILLDESK
BOB	3,6,9,12,18	PAYU,RAZORPAY
BAJAJFINSERV	3,6,9,12	PAYU

Note:

Please make sure that the respective EMI bank and tenure are enabled for your account at the gateway end, else the transaction might fail.

Please find the eligibility amount range below for some of the EMI options as provided by PayU

EMI Option	Amount Range
HDFC Debit Card EMI	5,00,000>=Txn amount>=5,000
Bajaj Finserv EMI	Transaction amount>=4,499
Zest Money EMI	3,00,000>=Transaction amount>=1,000
Axis Debit Card EMI	1,00,000>=Transaction amount>=5,000

The response for the Credit / Debit Card transaction API is a Payment Status Object wwwwww(click to open table)

Parameter	Type	Description
order_id	String	Unique Identifier for the order.
txn_id	String	Transaction ID for the payment attempt.
status	String	Status of the transaction. See Appendix below for status mapping. PENDING_VBV indicates that the transaction requires authentication to complete.
payment.authentication.method	String	HTTP Method for authentication. Can be one of GET or POST (See redirection instructions in the "Handling the Redirection Method" section.)
payment.authentication.url	String	URL to which the user has to be taken to for completing the authentication
payment.authentication.params	Object	Present only when the method is POST. This a mapping via a list of key:value pairs that must be sent along with the URL for authentication. Do not hardcode the params in your client * Never assume that you will receive param “x” or param “y”. This is completely dynamic and will vary on a case by case basis.

APPENDIX - Payment status codes and meaning:

Status	ID	Meaning
NEW	10	Newly created order
PENDING_VBV	23	Authentication is in progress
CHARGED	21	Successful transaction
AUTHENTICATION_FAILED	26	User did not complete authentication
AUTHORIZATION_FAILED	27	User completed authentication, but bank refused the transaction
JUSPAY_DECLINED	22	User input is not accepted by the underlying PG
AUTHORIZING	28	Transaction status is pending from bank

⭣

The request consists of Payment Method Details, Card Details, and optional EMI Parameterswwwwww(click to open tables)
Each parameter in tables is also listed below:

Payment Method Details:

Field		Type	Description
order_id	*	String	Order_id pertaining to the order for which the payment is started.
merchant_id	*	String	ID of the merchant_account that you hold with us.
payment_method_type	*	String	Must be CARD.
payment_method		String	One of VISA/MASTERCARD/MAESTRO/AMEX/RUPAY. This is usually inferred from the card number itself and we will take care of this if you are unable to provide this from your end.
redirect_after_payment	*	Boolean	This is a boolean variable and accepts true/false. We recommend that you set this to true and use the redirection flow. If set to true, then the user is redirected to the return_url configured for the order. If set to false, then the user will be stopped at the response page from the gateway. Your client should be able to read the page/title to infer that the user has completed the transaction.
format	*	String	If it is set to json, then the response will be HTTP 200 with a JSON formatted text. Otherwise, the response is HTTP 302 with the Location attribute having the destination URL.

* = Required

Card Details:

Note:

Card Security Code (CVV) is not required in case of Sodexo saved card transactions.

Field		Type	Description
card_token	*	String	A valid card token obtained using /card/list API. If you send this parameter, then card_number, name_on_card, card_exp_year, and card_exp_month fields are not required. If the token is generated using the /card/tokenize API, card_number, name_on_card, card_exp_year, card_exp_month and card_security_code fields are not required.
card_number	*	String	A valid credit/debit card number. Not required if card token is used.
name_on_card		String	Card holder name. Should contain alphabetical characters only.
card_exp_year	*	String	Represent the expiry year of the card as YY (two digits only)
card_exp_month	*	String	Represent the expiry month of the card as MM (two digits only)
card_security_code	*	String	CVV of the card. Usually three digits. Not required in case of SODEXO saved card transactions.
save_to_locker		Boolean	This is a boolean variable and accepts true/false. If set to true, then the card will be saved in locker when the transaction is successful. Else, the card will not be saved.

* = Conditionally required if card_token is not used.

EMI Parameters:

Field	Type	Description
is_emi	Boolean	Default is false. Set it to true if the user wishes to perform an EMI transaction on the given card.
emi_bank	String	Represents the bank that issued the card. Value must be one of the entries mentioned under EMI Bank in the support matrix below.
emi_tenure	int32	The tenure of the EMI in number of months.
auth_type	String	THREE_DS/OTP/VISA_CHECKOUT
emi_type	String	The type of EMI ie STANDARD_EMI or NO_COST_EMI