Skip to main content
Available in🇮🇳 India
Card EMI lets your customers pay for a purchase in Equated Monthly Instalments (EMIs) on their credit or debit card. The customer picks a bank and a tenure, and the card issuer converts the payment into EMIs. With the S2S integration, you collect the card details and EMI choice on your own checkout page and send them to Razorpay from your server. Razorpay returns a URL where the customer authenticates the payment with their bank.
Handy TipsContact our Support team to enable S2S Card EMI and the banks you want for your account.

Integration Steps

Follow these steps to integrate Card EMI:
  1. Fetch EMI Plans
  2. Create an Order
  3. Create a Payment
  4. Handle Payment Success and Error Events
  5. Fetch Payment Details and Status
  6. Verify Payment Signature
  7. Integrate Payments Rainy Day Kit
  8. Verify Payment Status

1.1 Fetch EMI Plans

Use the Methods API to get the EMI banks, tenures, interest rates and processing fees available to your account. Show the customer only what this API returns. This API uses only your API key id, passed as the key_id query parameter. Do not send your key secret. Endpoint: GET https://api.razorpay.com/v1/methods
Request
The response contains every payment method enabled for your account. The sample below shows only the Card EMI fields, for three banks.
Response

Response Parameters

boolean
Indicates whether EMI is enabled on your account. Possible values:
  • true: EMI is enabled.
  • false: EMI is not enabled. Do not show the EMI option.
object
Detailed EMI plans, keyed by bank code. Each bank has an array of plans, one per tenure. Each plan contains:
Keys that end with _DC (for example, HDFC_DC) are debit card EMI plans. BAJAJ is Bajaj Finserv EMI. All other keys are credit card EMI plans.
Handy Tips
  • Show only the banks and tenures returned in emi_options.
  • Show a tenure only when the payment amount is at least that plan’s min_amount.
  • If the plan has a processing_fee_plan, show the fee to the customer before they choose the plan.

Supported Banks

Card EMI supports the banks and lenders below. /v1/methods returns only the banks enabled for your account, so your list can be shorter. Contact your Razorpay account manager to enable more banks.
Credit Card EMI
Debit Card EMI
Debit Card EMI is available only to customers the bank has pre-approved. You can check this before checkout with the Eligibility Check API.
Other EMI

1.2 Create an Order

Create an order on your server for every payment. Pass the order id in the payment request in the next step. Endpoint: POST https://api.razorpay.com/v1/orders
Request
Response

Request Parameters

integer
required
The payment amount in paise. For example, for ₹6,000, enter 600000. The amount must be at least the min_amount of the EMI plan the customer chooses.
string
required
The currency of the payment. Card EMI supports only INR.
string
Your receipt number for the order. Maximum 40 characters.
object
Key-value pairs for additional information. Maximum 15 pairs, 256 characters each.

1.3 Create a Payment

Once you create the order and the customer enters their card details and picks an EMI plan, send the payment request from your server. Set method to emi and pass the chosen tenure in emi_duration. Endpoint: POST https://api.razorpay.com/v1/payments/create/json
Request
Response

Request Parameters

integer
required
The payment amount in paise. It must match the order amount and be at least the min_amount of the chosen EMI plan.
string
required
The currency of the payment. Possible value: INR.
string
required
The order id returned in step 1.2.
string
required
The customer’s email address.
string
required
The customer’s phone number.
string
required
The payment method. Possible value: emi.
integer
required
The EMI tenure in months. Use a duration returned in emi_options for the bank that issued the card.
object
required
The card details.
object
Details of the authentication channel.
object
required
Details of the customer’s browser. Not needed when authentication_channel is app.
string
required
The customer’s IP address.
string
The referer header of the customer’s browser request.
string
The user agent of the customer’s browser.
string
The URL on your website where Razorpay sends the customer after the payment, with a POST request that contains the payment result. Pass this URL to receive the success and failure callbacks in step 1.4.
object
Key-value pairs for additional information. Maximum 15 pairs, 256 characters each.

Response Parameters

string
The unique id of the payment.
array
The actions you can take to complete the payment.

1.4 Handle Payment Success and Error Events

Redirect the customer to the url of the redirect action in the next array. The customer authenticates the payment on their bank’s page. Razorpay then sends the customer to your callback_url with a POST request that contains the payment result.

Success Callback

If the payment succeeds, the callback contains these fields:
string
The unique id of the payment.
string
The order id the payment belongs to.
string
The signature you verify in step 1.6.
Callback Example

Failure Callback

If the payment fails, the callback contains an error object. The callback is a form-encoded POST; the example below shows its fields as JSON. Show the customer a failure message and let them retry.
Callback Example
The payment request can also fail before the customer is redirected. These are common Card EMI errors: These errors return HTTP status 400 with error code BAD_REQUEST_ERROR. For example:
Response
Know more about errors.

1.5 Fetch Payment Details and Status

Fetch the payment with the razorpay_payment_id from the callback to check its status and EMI plan. Endpoint: GET https://api.razorpay.com/v1/payments/:id
Request
Response
To get the EMI details in an emi object, add expand[]=emi to the request.
Request
Response (trimmed)

EMI Response Parameters

Without expand[]=emi, the same fields are returned in the emi_plan object.
string
The bank code of the card issuer. For example, HDFC.
string
The card type. Possible values: credit, debit.
integer
The annual interest rate in basis points. For example, 1600 is 16%.
integer
The EMI tenure in months.

1.6 Verify Payment Signature

Signature verification is mandatory. Verify the razorpay_signature from the success callback on your server. This confirms the callback came from Razorpay. Use the order_id stored on your server, not the razorpay_order_id from the callback.
  1. Create a string by joining the order_id from your server and the razorpay_payment_id from the callback with a |.
  2. Generate an HMAC-SHA256 hex digest of the string, using your key secret as the key.
  3. Compare the result with razorpay_signature. If they match, the payment is authentic.
Pseudocode

1.7 Integrate Payments Rainy Day Kit

Use the Payments Rainy Day kit to handle these situations:

1.8 Verify Payment Status

Handy TipsCheck that the payment status is captured before you deliver the product or service. An authorized payment is not yet captured. You can capture payments automatically.
You can check the payment status in one of these ways:
  • Dashboard: Check the payment status in the Transactions section of the Razorpay Dashboard.
  • Webhooks: Subscribe to webhook events such as payment.authorized, payment.captured, order.paid and payment.failed. Know how to set up webhooks.
  • APIs: Poll the Payment APIs to check the payment status.

Next Steps

Step 2: Test Integration
Last modified on November 17, 2026