string The status of the payment. Possible values: -created -authorized -captured -refunded -failed
string The converted payment amount that will be 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.
string The conversion currency that will be used to calculate fees and settlements. This currently defaults to INR, and is present only if the currency is non-INR.
string The payment method used for making the payment. Possible values: -card -netbanking -wallet - emi -upi
string Order ID, if provided. Read Orders API to learn more.
string Description of the payment, if any.
boolean Indicates whether the payment is done via an international card or a domestic one.
string The refund status of the payment. Possible values include: - null - partial - full.
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.
boolean Indicates if the payment has been captured.
string Customer email address used for the payment.
string Customer contact number used for the payment.
integer Fee (including GST) charged by Razorpay.
integer GST charged for the payment.
string Error that occurred during payment. For example, BAD_REQUEST_ERROR.
string Description of the error that occurred during payment. For example, Payment processing failed because of incorrect OTP.
string The point of failure. For example, customer.
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.
string The exact error reason. For example, incorrect_otp.
json object Contains user-defined fields, stored for reference purposes.
integer Timestamp, in UNIX format, on which the payment was created.
Once the payment is authorized by the customer's bank, you must verify if the authorized amount deducted from the customer's account is the same as the amount paid by the customer on your website or app.
After the 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.
While creating a capture request, in the amount field enter only the amount associated with the Order that is stored in your database.
Attempting to capture a payment whose status is not authorized will produce an error.
The usage of the expand parameter in retrieving the card or the EMI plan details of the payments is shown in the example, displayed 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.
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.