Credit / Debit Card transaction for EMI
application/x-www-form-urlencoded
order_id pertaining to the order for which the payment is started.
ID of the merchant_account that you hold with us.
Must be CARD
Values can be of one of VISA/MASTERCARD/MAESTRO/AMEX/RUPAY
A valid card token obtained using /card/list API. If you send this parameter, then card_number, name_on_card, card_exp_year, 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.
NOTE: expiry of card_token is 15 mins from the time generation.
A valid credit/debit card number
Card holder name. Should contain alphabetical characters only.
Represent the expiry year of the card as YY (two digits only)
Represent the expiry month of the card as MM (two digits only)
CVV of the card. Usually three digits. Optional for all VISA saved cards, PLUXEE | SODEXO saved cards, and saved cards of select issuing banks of MASTERCARD
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.
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.
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.
Default is false. Set it to true if the user wishes to perform an EMI transaction on the given card.
Represents the bank that issued the card. Value must be one of the entries mentioned under EMI Bank in the support matrix below.
Bank code can be referred here.
The tenure of the EMI in number of months.
THREE_DS/OTP/VISA_CHECKOUT
The type of EMI ie STANDARD_EMI
Array of gateway IDs should be passed, only for EMI transactions. If an EMI plan is supported by a specific set of gateways, then the same list should be passed in this field so that transaction will get routed to the proper gateway. Read ‘gateway_id‘ from ‘supported_gateways‘ in EMI Plans v2 response
order_id pertaining to the order for which the payment is started.
ID of the merchant_account that you hold with us.
Must be CONSUMER_FINANCE.
Value must be CONSUMER_FINANCE
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.
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.
Default is false. Set it to true if the user wishes to perform an EMI transaction on the given card.
Represents the bank that issued the cardless EMI. Value must be one of the entries mentioned under EMI Bank in the support matrix below.
Bank code can be referred here.
The tenure of the EMI in number of months.
The type of EMI ie STANDARD_EMI
Array of gateway IDs should be passed, only for EMI transactions. If an EMI plan is supported by a specific set of gateways, then the same list should be passed in this field so that transaction will get routed to the proper gateway. Read ‘gateway_id‘ from ‘supported_gateways‘ in EMI Plans v2 response
:order_id
:txn_id
PENDING_VBV
error
Order timed out
invalid_request

