Credit / Debit Card transaction
The API supports two card usage modes:
New Card
Use this mode when the card is provided for the first time.
Required parameters:
card_numbercard_exp_yearcard_exp_monthcard_security_codename_on_cardsave_to_locker– set totrueto store the card for future usetokenize– set totrueto generate a reusable card token
Saved Card
Use this mode when a previously saved card is used.
Required parameters:
card_token– received from the list-cards APIcard_security_code
Do not send card number or expiry-related fields when using a saved card.
order_id pertaining to the order for which the payment is started.
Unique identifier of the merchant assigned by us.
Must be CARD.
One of VISA/MASTERCARD/MAESTRO/AMEX/RUPAY/ELO. 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.
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.
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, 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.
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.
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.
The tenure of the EMI in number of months.
THREE_DS/OTP/VISA_CHECKOUT/MOTO (Non 3DS transactions)
The type of EMI ie STANDARD_EMI or NO_COST_EMI
The key offers should be passed only when juspay offers are being used. The value for this key can set as the offerID which is received from /v1/offers/list api
This is a boolean variable and accepts true/false. Required to be passed as true when card needs to be saved for future transactions.
(Note: This is an additional requirement along with save_to_locker)
(Note: Not mandatory for non-Brazilian transactions)
Brazilian identity number without punctuation
Brazilian identity number for companies without punctuation
Nickname that identifies a user's transactional account in Brazil
order_id
txn_id
Example : PENDING_VBV
error
Order timed out
invalid_request
Have questions?
- Need help? Contact support
- LLM? Read llms.txt

