API ReferenceIntegrationsKnowledge Base

Payments

You can accept payments from your customers by integrating your website or app with Razorpay Payment Gateway or using Razorpay products such as Payment Links, Payment Pages, Subscription Links, Invoices and Smart Collect.

If you want to directly integrate with our APIs, reach out to our Support team with your requirements.

This section contains the details of the Payment APIs used to capture payments, fetch details of payments made by customers and add notes to existing payments.

You can try out our APIs on the Razorpay Postman Public Workspace.

Run in Postman

Payment Entity🔗

For ease of understanding, the response for each request is shown on the right panel. The responses can be formatted in JSON.

The various parameters are explained below:

id
string Unique identifier of the payment.
entity
string Indicates the type of entity.
amount
string The payment amount represented in smallest unit of the currency passed. For example, amount = 100 translates to 100 paise, that is ₹1 (default currency is INR).
currency
string The currency in which the payment is made. Refer to the list of international currencies that we support.
status
string The status of the payment. Possible values:
-created
-authorized
-captured
-refunded
-failed
base_amount
string The converted payment amount used to calculate fees and settlements. Represented in smallest unit of the base_currency. This attribute is currently only present if the currency is non-INR.
base_currency
string The conversion currency used to calculate fees and settlements. This currently defaults to INR, and is present only if the currency is non-INR.
method
string The payment method used for making the payment. Possible values:
-card
-netbanking
-wallet
- emi
-upi
order_id
string Order ID, if provided. Know more about Orders API.
description `
string Description of the payment, if any.
international
boolean Indicates whether the payment is done via an international card or a domestic one.
refund_status
string The refund status of the payment. Possible values include:
- null
- partial
- full
amount_refunded
integer The amount refunded in smallest unit of the currency passed.
For example, if amount_refunded = 100, here 100 stands for 100 paise, which is equal to ₹1. INR is the default currency.
captured
boolean Indicates if the payment is captured.
email
string Customer email address used for the payment.
contact
string Customer contact number used for the payment.
fee
integer Fee (including GST) charged by Razorpay.
tax
integer GST charged for the payment.
error_code
string Error that occurred during payment. For example, BAD_REQUEST_ERROR.
error_description
string Description of the error that occurred during payment. For example, Payment processing failed because of incorrect OTP.
error_source
string The point of failure. For example, customer.
error_step
string The stage where the transaction failure occurred. The stages can vary depending on the payment method used to complete the transaction. For example, payment_authentication.
error_reason
string The exact error reason. For example, incorrect_otp.
notes
json object Contains user-defined fields, stored for reference purposes.
created_at
integer Timestamp, in UNIX format, on which the payment was created.

Capture a Payment🔗

After the customer's bank authorises the payment, you must verify if the authorised amount deducted from the customer's account is the same as the amount paid by the customer on your website or app.

You can configure automatic capture of payments on the Razorpay Dashboard.

To change the status of the payment from authorized to captured, send the following request:

/payments/:id/capture

Path Parameter🔗

id mandatory
string Unique identifier of the payment to be captured.

Request Parameters🔗

amount mandatory
string The amount to be captured (should be equal to the authorized amount, in the smallest unit of the chosen currency).
currency mandatory
string ISO code of the currency in which the payment was made. Refer to the list of supported currencies.

After the payment capture, the funds are transferred to your account in T+2 days in case of domestic transaction. For international transactions, the time taken is T+7 business days. The amount sent in the capture request must come from a verified source and be the amount that you are expecting to receive.

Recommendation
While creating a capture request, in the amount field enter only the amount associated with the order that is stored in your database.

Do Not Attempt to Capture Unauthorised Payments
Attempting to capture a payment whose status is not authorized will produce an error.

Fetch a Payment🔗

The following endpoint is used for retrieving a specific payment object using its id.

/payments/:id

Path Parameter🔗

id mandatory
string Unique identifier of the payment to be retrieved.

Query Parameters🔗

expand[] optional
array Used to retrieve additional information about the payment, the method used to make the payment. Using this parameter will cause a sub-entity to be added to the response.

Supported values are:
  • card - Expanded card details, applicable for card and EMI payments.
  • emi - Expanded EMI plan details, applicable for EMI payments.
  • offers - Expanded Offer details, applicable when an offer was applied to the payment.

Examples🔗

The expand[] parameter on the Payments endpoint returns expandable fields in the response:

expand[]=card
Used to expand the card details when the payment method is emi.
expand[]=emi
Used to expand the EMI plan details when the payment method is emi.

Expanded Offers🔗

expand[]=offers
Used to expand the offers applied to a payment, wherever applicable.

Fetch Multiple Payments🔗

The following endpoint is used for retrieving all the payments.

/payments

Query Parameters🔗

from
integer Timestamp, in seconds, from when payments are to be fetched.
to
integer Timestamp, in seconds, till when payments are to be fetched.
count
integer Number of payments to be fetched.
Default value is 10. Maximum value is 100. This can be used for pagination, in combination with the skip parameter.
skip
integer Number of records to be skipped while fetching the payments.
expand[]
array Used to retrieve additional information about the payment, the method used to make the payment. Using this parameter will cause a sub-entity to be added to the response.

Supported values are:
-card - Expanded card details, usable for card and EMI payments.
-emi - Expanded EMI plan details, usable for EMI payments.

Note
By default, only the last 10 records are displayed. You can use the count and skip parameters to retrieve the specific number of records that you need.

Fetch Expanded Card or EMI Details for Payments🔗

You can fetch the expanded card or EMI details for payments using the expand[] query parameter with the Fetch Multiple Payments API.

The table below lists the endpoints:

Details Type

Endpoint

Card

/payments/?expand[]=card

EMI

/payments/?expand[]=emi

There are two sample codes on the right:

  • Request #1 is for retrieving the expanded card details of the payments, in which the payment method is card or emi.
  • Request #2 is for retrieving the expanded EMI plan details of the payments, in which the payment method is emi.

Fetch Payments Based on Orders🔗

The following endpoint retrieves payments corresponding to an order:

/orders/:id/payments

Path Parameter🔗

id mandatory
string Unique identifier of the order for which you want to fetch payment details.

Fetch Card Details of a Payment🔗

You can retrieve the details of the card used to make a payment using the following endpoint:

/payments/:id/card

Path Parameter🔗

id mandatory
string Unique identifier of the payment for which you want to retrieve card details.

Response Entities🔗

id
string Unique identifier of the card used for the payment.
entity
string The value for this attribute will always be card.
name
string Name of the cardholder.
last4
string The last 4 digits of the card number.
network
string The card network. Possible values:
  • American Express
  • Diners Club
  • Maestro
  • MasterCard
  • RuPay
  • Unknown
  • Visa
type
string The card type. Possible values:
  • credit
  • debit
  • prepaid
  • unknown
issuer
string The card issuer. The 4-character code denotes the issuing bank.

This attribute will not be set for the card issued by a foreign bank.
international
boolean This attribute will be set to true if the card is issued by a foreign bank.
emi
boolean This attribute is set to true if the card can be used for EMI payment method.
sub_type
boolean The sub-type of the customer's card. Possible values:
  • business Corporate Card
    Know how to accept payments made by customers using corporate cards.
  • consumer

Update the Payment🔗

You can modify an existing payment to update the Notes field only. Notes can be used to record additional information about the payment. You can add up to 15 key-value pairs with each value of the key not exceeding 256 characters.

Using the PATCH operation, you can replace the entire notes object for the entity.

Request Parameters🔗

To modify the Notes field in a particular payment, construct the API request as follows:

/payments/:id/
id mandatory
string Unique identifier of the payment for which the Notes field should be updated.
notes mandatory
json object Contains user-defined fields and is stored for reference purposes. Know more about notes.
‹›
×