JavaScript is disabled. Some features may not work. You can also read the static version: View text version

Credit / Debit Card transaction

Compliance Check: Merchants who are not PCI DSS compliant should refrain from using this API and consume our PayV3.js for cards.
Card Security Code (CVV) is not required in case of Pluxee | Sodexo saved card and token transactions of VISA and MASTERCARD (Select issuing banks only). Refer to List Stored Card API for further details

EMI Support Matrix

The following are the 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.

Scroll inside to view more

EMI Bank	Card Type	EMI Tenure	Supported Gateways
HDFC	Credit	3,6,9,12,18,24,36	RAZORPAY,PAYU,PINELABS,PAYTM_V2,GOCASHFREE,BILLDESK
CITI	Credit	3,6,9,12,18,24	RAZORPAY,PAYU,PINELABS,PAYTM_V2,GOCASHFREE,BILLDESK
ICICI	Credit	3,6,9,12,18,24	RAZORPAY,PAYU,PINELABS,PAYTM_V2,CCAVENUE,GOCASHFREE,BILLDESK
SBI	Credit	3,6,9,12	RAZORPAY,PAYU,PINELABS,PAYTM_V2,CCAVENUE,GOCASHFREE,BILLDESK
AXIS	Credit	3,6,9,12,18,24	RAZORPAY,PAYU,PINELABS,PAYTM_V2,CCAVENUE,GOCASHFREE,BILLDESK
SCB	Credit	3,6,9,12,18,24	RAZORPAY,PAYU,PINELABS,PAYTM_V2,GOCASHFREE,BILLDESK
KOTAK	Credit	3,6,9,12,18,24	RAZORPAY,PAYU,PINELABS,PAYTM_V2,CCAVENUE,GOCASHFREE,BILLDESK
HSBC	Credit	3,6,9,12,18,24	RAZORPAY,PAYU,PINELABS,PAYTM_V2,CCAVENUE,GOCASHFREE,BILLDESK
BOB	Credit	3,6,9,12,18,24	RAZORPAY,PAYU,PINELABS,PAYTM_V2,GOCASHFREE,BILLDESK
AU	Credit	3,6,9,12,18,24	PAYU,PAYTM_V2,GOCASHFREE
AMEX	Credit	3,6,9,12	RAZORPAY,PAYU,PINELABS,PAYTM_V2,CCAVENUE,GOCASHFREE
INDUSIND	Credit	3,6,9,12,18,24	RAZORPAY,PAYU,PINELABS,PAYTM_V2,CCAVENUE,GOCASHFREE,BILLDESK
IDFC	Credit	3,6,9,12,15,18,24,36	PAYU,PAYTM_V2,BILLDESK
JNK	Credit	3,6,9,12	BILLDESK
ONECARD	Credit	3,6,9,12,18,24	RAZORPAY,PAYU,PINELABS,PAYTM_V2
IDBI	Credit	3,6,9,12	PAYU,PAYTM_V2,BILLDESK
FEDERAL	Credit	3,6,9,12,18,24	RAZORPAY,GOCASHFREE
RBL	Credit	3,6,9,12,18,24	RAZORPAY,PAYU,PINELABS,PAYTM_V2,GOCASHFREE,BILLDESK
YES	Credit	3,6,9,12,18,24	RAZORPAY,PAYU,PINELABS,PAYTM_V2,GOCASHFREE,BILLDESK
SBIDC	Debit	6,9,12,18	PAYU,BILLDESK
KOTAKDC	Debit	1,2,3,6,9,12	RAZORPAY,PAYU,PINELABS
FEDERALDC	Debit	3,6,9,12	PAYU
BOBDC	Debit	3,6,9,12,18	RAZORPAY,PAYU
ICICIDC	Debit	3,6,9,12	PAYU,PINELABS,PAYTM_V2
AXISDC	Debit	3,6,9,12,18,24	PAYU,PINELABS
HDFCDC	Debit	3,6,9,12,18	RAZORPAY,PAYU,PINELABS,PAYTM_V2,BILLDESK
BAJAJFINSERV	-	3,6,9,12	RAZORPAY,PAYU, BAJAJFINSERV

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

Scroll inside to view more

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

Request

Response

API Endpoints

Sandbox Link

POST

https://sandbox.juspay.in/txns

Production Link

POST

https://api.juspay.in/txns

                      Content-Type
                      *
                      

String

Mandatory

application/x-www-form-urlencoded

                      x-routing-id
                      *
                      

String

Required

We recommend passing the customer_id as the x-routing-id. If the customer is checking out as a guest, you can pass an alternative ID that helps track the payment session lifecycle. For example, this could be an Order ID or Cart ID.

This ID is associated with the customer. It plays a key role in ensuring consistency and maintaining connections across different systems. If you fail to pass the same x-routing-id for the same customer in all related API calls, it could lead to issues with API functionality. Therefore, it’s crucial that you use the same x-routing-id for all requests tied to the same customer.

Example:- customer_1122

Body

                      order_id
                      *
                      

string

Mandatory

order_id pertaining to the order for which the payment is started.

                      merchant_id
                      *
                      

string

Mandatory

ID of the merchant_account that you hold with us.

                      payment_method_type
                      *
                      

string

Mandatory

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.

                      card_token
                      *
                      

string

Mandatory

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.

                      card_number
                      *
                      

string

Mandatory

A valid credit/debit card number

                      name_on_card
                      
                      

string

Card holder name. Should contain alphabetical characters only.

                      card_exp_year
                      *
                      

string

Mandatory

Represent the expiry year of the card as YY (two digits only)

                      card_exp_month
                      *
                      

string

Mandatory

Represent the expiry month of the card as MM (two digits only)

                      card_security_code
                      *
                      

string

Mandatory

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

                      save_to_locker
                      *
                      

boolean

Mandatory

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.

                      redirect_after_payment
                      *
                      

boolean

Mandatory

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

Mandatory

f 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.

                      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
                      
                      

integer

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

                      offers
                      
                      

array of Strings

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

                      supported_gateway_id
                      
                      

Array of Integers

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

                      tokenize
                      *
                      

boolean

Mandatory

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)

                      transient_info 
                      
                      

JSON Object

AVS

This is a JSON object, that has to be passed in the body that should contain the following keys:

billing_address_line1 [House No. or Name] - Mandatory
billing_address_line2 [Street] - Mandatory
billing_address_country [Country] - Mandatory
billing_address_postal_code [Postal code] - Mandatory
billing_address_country_code_iso [Country code ISO] - Optional
(Note: This field is optional, but if used, all the mandatory billing address fields must be populated. They can be used to pass the user's billing address to the payment gateways, either to capture billing details or for Address Verification (AVS) when required. In AVS flows, the billing address is verified against the cardholder’s address by the downstream PG to help reduce the risk of fraudulent transactions, especially during international card usage.)

Response Body

                      order_id
                      
                      

string

:order_id

                      txn_id
                      
                      

string

:txn_id

                      status
                      
                      

string

PENDING_VBV

                      payment
                      
                      

object

                      authentication.method
                      
                      

string

                      authentication.url
                      
                      

String

Response Body

                      status
                      
                      

string

error

                      error_message
                      
                      

string

Order timed out

                      error_code
                      
                      

string

invalid_request

Have questions?
Need help? Contact support
LLM? Read llms.txt