Create the Authorisation Transaction
Fetch the Token Details
Create Subsequent Payments
Create an Authorisation Transaction
To create an authorisation transaction using the Razorpay APIs, you need to:1.1 Create a Customer
Razorpay links recurring tokens to customers using a unique identifier generated through the Customer API. The following endpoint creates a customer.POST /customers
Request Parameters
Request Parameters
name
: string The name of the customer. For example, Gaurav Kumar.email
: string The email address of the customer. For example, gaurav.kumar@example.com.contact
: string The phone number of the customer. For example, 9876543210.fail_existing optional
: string The request throws an exception by default if a customer with the exact details already exists. You can pass an additional parameter fail_existing to get the existing customer’s details in the response. Possible values:1(default): If a customer with the same details already exists, throws an error.0: If a customer with the same details already exists, fetches details of the existing customer.
notes optional
: object Key-value pair that can be used to store additional information about the entity. Maximum 15 key-value pairs, 256 characters (maximum) each. For example, "note_key": "Beam me up Scotty”.Response Parameters
Response Parameters
id
: string Unique identifier of the customer. For example, cust_1Aa00000000004.entity optional
: string Indicates the type of entity.name
: string Customer’s name. Alphanumeric, with period (.), apostrophe (’), forward slash (/), at (@) and parentheses allowed. The name must be between 3-50 characters in length.contact
: string The customer’s phone number. A maximum length of 15 characters including country code.email
: string The customer’s email address. A maximum length of 64 characters.gstin
: string GST number linked to the customer. For example, 29XAbbA4369J1PA.notes
: json object This is a key-value pair that can be used to store additional information about the entity. It can hold a maximum of 15 key-value pairs, 256 characters (maximum) each. For example, "note_key": "Beam me up Scotty”.created_at
: integer UNIX timestamp, when the customer was created. For example, 1234567890.1.2 Create an Order
Use the Orders API to create a unique Razorpayorder_id that is associated with the authorisation transaction for a one time mandate. To create a one-time mandate, pass the value of the frequency parameter as one_time. The following endpoint creates an order.
POST /orders
Request Parameters
Request Parameters
amount mandatory
: integer Amount in currency subunits. The maximum amount that can be blocked is ₹10,000.currency mandatory
: string The 3-letter ISO currency code for the payment. Currently, we only support INR.customer_id mandatory
: string The unique identifier of the customer. For example, cust_4xbQrmEoA5WJ01.method mandatory
: string The authorisation method. Here, it is upi.receipt optional
: string A user-entered unique identifier of the order. For example, Receipt No. 1. You should map this parameter to the order_id sent by Razorpay.notesoptional
: object Key-value pair that can be used to store additional information about the entity. Maximum 15 key-value pairs, 256 characters each. For example, "note_key": "Beam me up Scotty”.token
: object Details related to the authorisation such as max amount, frequency and expiry information.max_amount mandatory
: integer The maximum amount that can be debited is ₹10,000.expire_at mandatory
: integer The Unix timestamp that indicates when the authorisation transaction must expire. The default and the maximum value allowed is 90 days.frequency mandatory
: string The frequency at which you can charge your customer. The value should be as_presented.type mandatory
: string Indicates the type of payment. Here, the possible value is single_block_multiple_debit.Response Parameters
Response Parameters
id
: string The unique identifier of the order.amount
: integer The amount for which the order was created, in currency subunits.entity
: string Name of the entity. Here, it is order.amount_paid
: integer The amount paid against the order.amount_due
: integer The amount pending against the order.currency
: string ISO code for the currency in which you want to accept the payment. The default length is 3 characters.receipt
: string Receipt number that corresponds to this order.status
: string The status of the order. Possible values:created: When you create an order it is in thecreatedstate. It stays in this state till a payment is attempted on it.attempted: An order moves fromcreatedtoattemptedstate when a payment is first attempted on it. It remains in theattemptedstate till one payment associated with that order is captured.paid: After the successful capture of the payment, the order moves to thepaidstate. No further payment requests are permitted once the order moves to thepaidstate. The order stays in thepaidstate even if the payment associated with the order is refunded.
attempts
: integer The number of payment attempts, successful and failed, that have been made against this order.notes
: json object Key-value pair that can be used to store additional information about the entity. Maximum 15 key-value pairs, 256 characters (maximum) each. For example, "note_key": "Beam me up Scotty”.created_at
: integer Indicates the Unix timestamp when this order was created.1.3 Create an Authorisation Payment
Use this API endpoint to initiate UPI mandate authorisation via intent flow. This step creates a pending token. The customer approves the mandate in their TPAP app.POST /v1/payments/create/json
link returned in the response is a generic UPI URL starting with upi://mandate. To redirect customers to a specific UPI app, replace upi://mandate with the app’s scheme. The query parameters remain unchanged.- For Google Pay, replace
upi://mandatewithgpay://upi/mandate. - For PhonePe, replace
upi://mandatewithphonepe://mandate. - For Paytm, replace
upi://mandatewithpaytmmp://mandate. - For BHIM, replace
upi://mandatewithbhim://upi/mandate. - For CRED, replace
upi://mandatewithcredpay://upi/mandate. - For WhatsApp, replace
upi://mandatewithwhatsapp-consumer://upi/mandate. Use the genericupi://mandatescheme to let the OS prompt the customer to choose their preferred app.
Request Parameters
Request Parameters
amount
: integer The amount you want to charge your customer. This should be the same as the order amount. The maximum amount that can be blocked is ₹10,000.currency
: string The 3-letter ISO currency code for the payment.order_id
: string The unique identifier of the order created.customer_id
: string The unique identifier of the customer you want to charge.upi.flow
: string The UPI payment flow for the transaction. Here, the value must be intent.recurring
: string Determines whether recurring payment is enabled or not.true: Recurring payment is enabled.false: Recurring payment is not enabled.
contact
: string The customer’s phone number.email
: string The customer’s email address.notes
: object Key-value pair you can use to store additional information about the entity. Maximum of 15 key-value pairs, 256 characters each.description
: string A user-entered description for the payment.Success Response Parameters
Success Response Parameters
razorpay_payment_id
: string The unique identifier of the payment created. For example, pay_RtP3bnk51QvOF9.next
: array A list of action objects describing the next steps to complete the payment.next.action
: string The type of action to perform. Possible values:intent: Redirects the customer to their TPAP app to approve the mandate.poll: Used to poll the payment status.
next.url
: string The URL corresponding to the action. For intent, this is a UPI deep link. For poll, this is the Razorpay API endpoint to check payment status.Error Response Parameters
Error Response Parameters
bad_request_error
bad_request_error
- Description: Invalid Mandate Sequence Number.
- Next Steps: Retry after some time during the valid cycle.
bank_account_invalid
bank_account_invalid
- Description: Payment failed because Account linked to VPA is invalid.
- Next Steps: Create a new mandate with the customer.
bank_account_validation_failed
bank_account_validation_failed
- Description: Payment was unsuccessful as the details are invalid. Please retry with the right details.
- Next Steps: Ask the customer to retry again.
bank_not_available
bank_not_available
- Description: Payment was unsuccessful as the bank linked to this UPI ID is temporarily unavailable. Any amount deducted will be refunded within 5-7 working days.
- Next Steps: Retry after some time.
bank_technical_error
bank_technical_error
Temporary Bank Issue
Temporary Bank Issue
- Description: Payment was unsuccessful due to a temporary issue at your bank. Any amount deducted will be refunded within 5-7 working days.
- Next Steps: Retry after some time.
Bank Declined
Bank Declined
- Description: Payment was unsuccessful as it was declined by your bank. Any amount deducted will be refunded within 5-7 working days.
- Next Steps: Retry after some time.
Bank or Wallet Gateway Error
Bank or Wallet Gateway Error
- Description: Payment processing failed due to error at bank or wallet gateway.
- Next Steps: Retry after some time.
General Temporary Issue
General Temporary Issue
- Description: Payment was unsuccessful due to a temporary issue. Any amount deducted will be refunded within 5-7 working days.
- Next Steps: Retry after some time.
Bank Services Halt
Bank Services Halt
- Description: Payment was unsuccessful due to a temporary halt of services at this bank.
- Next Steps: Retry after some time.
credit_to_beneficiary_failed
credit_to_beneficiary_failed
- Description: Payment was unsuccessful due to a temporary issue. Any amount deducted will be refunded within 5-7 working days.
- Next Steps: Retry after some time.
debit_declined
debit_declined
- Description: Payment was unsuccessful as it was declined by remitter bank.
- Next Steps: Create a new mandate with the customer.
debit_instrument_blocked
debit_instrument_blocked
- Description: Payment was unsuccessful as the account linked to this UPI ID is blocked. Try using another account.
- Next Steps: Create a new mandate with the customer.
duplicate_mandate_request
duplicate_mandate_request
- Description: Duplicate mandate request. Please try again with another mandate request.
- Next Steps: Please try again with another mandate request.
gateway_technical_error
gateway_technical_error
Bank or Wallet Gateway Error
Bank or Wallet Gateway Error
- Description: Payment processing failed due to error at bank or wallet gateway.
- Next Steps: Retry after some time.
Temporary Issue with Money Deduction
Temporary Issue with Money Deduction
- Description: Payment was unsuccessful due to a temporary issue. If money got deducted, reach out to the seller.
- Next Steps: Retry after some time.
incorrect_pin
incorrect_pin
- Description: You have entered an incorrect PIN on the UPI app. Please retry with the correct PIN.
- Next Steps: Ask the customer to retry with correct PIN.
insufficient_funds
insufficient_funds
- Description: Transaction failed due to insufficient funds.
- Next Steps: Ask the customer to add balance to their account and retry.
invalid_request
invalid_request
- Description: Payment processing failed due to error at bank or wallet gateway.
- Next Steps: Retry after some time.
invalid_response_from_gateway
invalid_response_from_gateway
- Description: Payment was unsuccessful due to a temporary issue. Any amount deducted will be refunded within 5-7 working days.
- Next Steps: Retry after some time.
invalid_transaction_beneficiary
invalid_transaction_beneficiary
- Description: Beneficiary address resolution failed. Please try again after some time.
- Next Steps: Please try again after some time.
invalid_vpa
invalid_vpa
- Description: You have entered an incorrect UPI ID. Please retry with the correct UPI ID.
- Next Steps: Ask the customer to retry with a valid VPA.
issuer_dispatch_failed
issuer_dispatch_failed
- Description: Payment failed due to some issue at the issuer bank. Please try again after some time.
- Next Steps: Please try again after some time.
limit_exceeded_remitting_bank
limit_exceeded_remitting_bank
- Description: Limit exceeded for remitter bank. Please ask customer to try with another bank account.
- Next Steps: Please ask customer to try with another bank account.
mandate_debit_beyond_psp_amount_cap
mandate_debit_beyond_psp_amount_cap
- Description: Debit amount is beyond payer PSP specified amount cap. Please reduce the amount and try again.
- Next Steps: Please reduce the mandate amount to match customer PSP.
mandate_request_limit_breached
mandate_request_limit_breached
- Description: Maximum number of mandate creation requests exceeded for customer’s bank account. Please wait for some time before initiating new mandate creation requests.
- Next Steps: Please wait for some time before initiating new mandate creation requests.
mobile_number_invalid
mobile_number_invalid
- Description: Registered Mobile number linked to the account has been changed or removed.
- Next Steps: Create a new mandate with the customer.
nature_of_debit_not_allowed
nature_of_debit_not_allowed
- Description: Nature of debit not allowed in customer’s account. Please ask the customer to use a different bank account.
- Next Steps: Please ask the customer to use a different bank account.
no_financial_address_record_found
no_financial_address_record_found
- Description: No financial address record found for this VPA. Please ask customer to try with another bank account.
- Next Steps: Please ask customer to try with other bank account.
no_original_request_found
no_original_request_found
- Description: No mandate details were found in the record during debit. Please try after some time.
- Next Steps: Please try after some time.
payment_collect_request_expired
payment_collect_request_expired
- Description: Payment was unsuccessful as you could not pay with the UPI app within time.
- Next Steps: Retry after some time.
payment_declined
payment_declined
Bank Declined Payment
Bank Declined Payment
- Description: Payment was unsuccessful as it was declined by your bank. Any amount deducted will be refunded within 5-7 working days.
- Next Steps: Ask the customer to retry with other account.
Customer Declined Payment
Customer Declined Payment
- Description: You have declined the payment request on the UPI app. Please retry when you are ready.
- Next Steps: Ask the customer to approve the payment.
payment_failed
payment_failed
- Description: Payment was unsuccessful due to a temporary issue. If amount got deducted, it will be refunded within 5-7 working days.
- Next Steps: Retry after 1 hour.
payment_pending
payment_pending
- Description: The status of your payment is pending. You can either wait or retry to pay successfully.
- Next Steps: Retry after some time.
payment_risk_check_failed
payment_risk_check_failed
- Description: Payment was unsuccessful as your account does not pass the risk checks done by your bank. Try using another account.
- Next Steps: Retry after some time.
payment_timed_out
payment_timed_out
- Description: Payment was unsuccessful as you could not complete it in time.
- Next Steps: Retry after some time.
pre_debit_notification_failed
pre_debit_notification_failed
- Description: Unable to Notify the Customer.
- Next Steps: Retry after some time.
remitter_dispatch_failed
remitter_dispatch_failed
- Description: Payment failed due to some issue at the customer’s. Please try again after some time.
- Next Steps: Please try again after some time.
request_timed_out
request_timed_out
General Timeout - Temporary Issue
General Timeout - Temporary Issue
- Description: Payment was unsuccessful due to a temporary issue. Any amount deducted will be refunded within 5-7 working days.
- Next Steps: Retry after some time.
Timeout - Bank Declined
Timeout - Bank Declined
- Description: Payment was unsuccessful as it was declined by your bank. Any amount deducted will be refunded within 5-7 working days.
- Next Steps: Retry after some time.
Timeout - Recurring Payment Creation
Timeout - Recurring Payment Creation
- Description: Payment was unsuccessful as the recurring payment can not be created at this time. Any amount deducted will be refunded within 5-7 working days.
- Next Steps: Retry after some time.
transaction_frequency_limit_exceeded
transaction_frequency_limit_exceeded
- Description: Payment failed. Please try again with another bank account.
- Next Steps: Create a new mandate with the customer.
transaction_limit_exceeded
transaction_limit_exceeded
Amount Limit Exceeded
Amount Limit Exceeded
- Description: Payment failed because Transaction amount limit has exceeded.
- Next Steps: Reach out to the customer to collect the amount.
Bank Account Amount Limit
Bank Account Amount Limit
- Description: Payment was unsuccessful as you exceeded the amount limit on the bank account linked to this UPI ID.
- Next Steps: Ask the customer to retry after some time.
transaction_not_allowed
transaction_not_allowed
- Description: Payment was unsuccessful as it was declined by your bank. Reach out to your bank for more details. Try using another account.
- Next Steps: Create a new mandate with the customer.
upi_dummy_payment
upi_dummy_payment
- Description: Payment was a dummy payment for one time mandate registration.
- Next Steps: NA
Fetch Tokens
In a Single Block Multiple Debit (SBMD) flow, the Token represents the unique mandate or authorisation.token_id using the Dashboard or the APIs given below.
2.1 Fetch Token by Customer id
A customer can have multiple tokens and these tokens can be used to create subsequent payments for multiple products or services. The following endpoint retrieves tokens linked to a customer.GET /customers/:id/tokens
Path Parameter
Path Parameter
id mandatory
: string The unique identifier of the customer for whom tokens are to be retrieved. For example, cust_1Aa00000000002.Response Parameters
Response Parameters
entity
: string The name of the entity. Here, it is collection.count
: integer The total number of tokens returned in the response.items
: array A list of token objects associated with the customer.id
: string The unique identifier of the token. For example, token_RtOSr9o9lZwv5C.entity
: string The name of the entity. Here, it is token.token
: string The token value used to identify the mandate.bank
: string The bank associated with the token. Returns null for UPI tokens.wallet
: string The wallet associated with the token. Returns null for UPI tokens.method
: string The payment method associated with the token. Here, it is upi.vpa
: json object Details of the customer’s UPI VPA linked to the token.username
: string The username part of the customer’s UPIhandle
: string The handle (bank or PSP) part of the customer’s UPI For example, upi.name
: string The account holder’s name as registered with the bank. Returns null if not available.status
: string The status of the For example, valid. Returns null if not yet validated.received_at
: integer Unix timestamp at which the VPA was received.recurring
: boolean Indicates whether the token is enabled for recurring payments. Possible values:true: Token is enabled for recurring payments.false: Token us not enabled for recurring payments.
recurring_details
: json object Details of the recurring mandate associated with the token.status
: string The status of the recurring mandate. For example, confirmed.failure_reason
: string The reason for mandate failure, if applicable. Returns null if there is no failure.amount_blocked
: integer The amount blocked against the mandate, in currency subunits.amount_debited
: integer The amount debited against the mandate so far, in currency subunits.auth_type
: string The authentication type used. Returns null if not applicable.mrn
: string The mandate reference number. Returns null if not yet assigned.used_at
: integer Unix timestamp at which the token was last used. Returns null if unused.created_at
: integer Unix timestamp at which the token was created.start_time
: integer Unix timestamp at which the mandate validity begins.notes
: array Key-value pairs used to store additional information. Returns an empty array if no notes are added.error_description
: string Description of the error, if any. Returns null for successful mandates.entity_id
: string The identifier of the entity linked to the token. Returns null if not applicable.dcc_enabled
: boolean Indicates whether Dynamic Currency Conversion (DCC) is enabled. Possible values:true: DCC is enabled.false: DCC is not enabled.
max_amount
: integer The maximum amount that can be debited per transaction, in currency subunits.expired_at
: integer Unix timestamp at which the token expires.2.2 Fetch Token by Payment id
The following endpoint fetches thetoken_id using a payment_id.
GET /payments/:id
Path Parameter
Path Parameter
id mandatory
: string The unique identifier of the payment whose details are to be fetched. For example, pay_1Aa00000000002.Response Parameters
Response Parameters
id
: string The unique identifier of the payment. For example, pay_RtP3bnk51QvOF9.entity
: string The name of the entity. Here, it is payment.amount
: integer The payment amount in currency subunits.currency
: string The ISO currency code for the payment. For example, INR.status
: string The status of the payment.order_id
: string The unique identifier of the order associated with the payment.invoice_id
: string The unique identifier of the invoice associated with the payment. Returns null if not applicable.international
: boolean Indicates whether the payment is an international transaction. Possible values:true: It is an international payment.false: It is a domestic payment.
method
: string The payment method used. Here, it is upi.amount_refunded
: integer The amount refunded for the payment, in currency subunits.refund_status
: string The refund status of the payment. Returns null if no refund has been initiated.captured
: boolean Indicates whether the payment has been captured. Possible values:true: It is captured.false: It is not captured.
description
: string A description for the payment. Returns null if not provided.card_id
: string The unique identifier of the card used for the payment. Returns null for UPI payments.bank
: string The bank associated with the payment. Returns null for UPI payments.wallet
: string The wallet used for the payment. Returns null for UPI payments.vpa
: string The customer’s virtual payment address (VPA). Returns null until the mandate is confirmed.email
: string The customer’s email address.contact
: string The customer’s phone number.customer_id
: string The unique identifier of the customer.token_id
: string The unique identifier of the token created for the recurring payment mandate.notes
: json object Key-value pair used to store additional information about the entity. Maximum 15 key-value pairs, 256 characters each.fee
: integer The fee charged by Razorpay for the payment, in currency subunits. Returns null if not yet captured.tax
: integer The tax charged on the Razorpay fee. Returns null if not yet captured.error_code
: string The error code if the payment failed. Returns null for successful payments.error_description
: string The description of the error. Returns null for successful payments.error_source
: string The source of the error. Returns null for successful payments.error_step
: string The step at which the error occurred. Returns null for successful payments.error_reason
: string The reason for the error. Returns null for successful payments.acquirer_data
: json object Acquirer-specific data for the payment.acquirer_data.rrn
: string The retrieval reference number (RRN) assigned by the bank. Returns null until the payment is processed.created_at
: integer Unix timestamp at which the payment was created.upi
: json object UPI details.vpa
: string The customer’s UPI Returns null until the mandate is confirmed.flow
: string The UPI payment flow used. Here, it is intent.token_id via the payment.failed webhook.Path Parameters
Path Parameters
id mandatory
: string The unique identifier of the payment to be retrieved. For example, pay_1Aa00000000002.2.3 Fetch Token by Token id and Customer id
Use this API to fetch token details usingtoken_id and customer_id as path parameters.
GET /v1/customers/:customer_id/tokens/:token_id
Path Parameters
Path Parameters
customer_id mandatory
: string The unique identifier of the customer with whom the token is linked. For example, cust_1Aa00000000002.token_id mandatory
: string The unique identifier of the token to be fetched. For example, token_1Aa00000000001.Response Parameters
Response Parameters
id
: string The unique identifier of the token. For example, token_RtOSr9o9lZwv5C.entity
: string The name of the entity. Here, it is token.token
: string The token value used to identify the mandate.bank
: string The bank associated with the token. Returns null for UPI tokens.wallet
: string The wallet associated with the token. Returns null for UPI tokens.method
: string The payment method associated with the token. Here, it is upi.vpa
: json object Details of the customer’s UPI VPA linked to the token.username
: string The username part of the customer’s UPIhandle
: string The handle (bank or PSP) part of the customer’s UPI For example, upi.name
: string The account holder’s name as registered with the bank.status
: string The status of the For example, valid.received_at
: integer Unix timestamp at which the VPA was received.recurring
: boolean Indicates whether the token is enabled for recurring payments. Possible values: true, false.recurring_details
: json object Details of the recurring mandate associated with the token.status
: string The status of the recurring mandate. For example, confirmed.failure_reason
: string The reason for mandate failure, if applicable.amount_blocked
: integer The amount blocked against the mandate, in currency subunits.amount_debited
: integer The amount debited against the mandate so far, in currency subunits.auth_type
: string The authentication type used. Returns null if not applicable.mrn
: string The mandate reference number. Returns null if not yet assigned.used_at
: integer Unix timestamp at which the token was last used.created_at
: integer Unix timestamp at which the token was created.start_time
: integer Unix timestamp at which the mandate validity begins.notes
: array Key-value pairs used to store additional information. Returns an empty array if no notes are added.error_description
: string Description of the error, if any. Returns null for successful mandates.entity_id
: string The identifier of the entity linked to the token. Returns null if not applicable.dcc_enabled
: boolean Indicates whether Dynamic Currency Conversion (DCC) is enabled. Possible values:true: DCC is enabled.false: DCC is not enabled.
max_amount
: integer The maximum amount that can be debited per transaction, in currency subunits.expired_at
: integer Unix timestamp at which the token expires.Create Subsequent Payments
Once the initial amount block is authorised, you can execute debits against the mandate. For each debit, you need to:3.1 Create an Order to Charge the Customer
You have to create a new order to charge a one time mandate. This order is different from the one created during the authorisation transaction. The following endpoint creates an order.POST /orders
Request Parameters
Request Parameters
amount mandatory
: integer Amount in currency subunits.currency mandatory
: string The 3-letter ISO currency code for the payment.receipt optional
: string A user-entered unique identifier for the order. For example, Receipt No. 1. You should map this parameter to the order_id sent by Razorpay.notes optional
: object Key-value pair you can use to store additional information about the entity. Maximum of 15 key-value pairs, 256 characters each. For example, "note_key": "Beam me up Scotty”.notification
: object Details of the pre-debit notification. This object is optional. You should use it only if you want to control pre-debit notifications and debits. If you do not pass this object, we will automatically try to debit 25 hours after the pre-debit notification is delivered.token_id mandatory
: string The token_id generated when the customer successfully completes the authorisation payment. Different payment instruments for the same customer have different token_id.payment_after optional
: integer UNIX timestamp post which the debit is supposed to happen. Defaults to 25 hours after the pre-debit notification is delivered.payment_capture mandatory
: boolean Determines whether the payment status should be changed to captured automatically or not. Possible values:true: Payments are captured automatically.false: Payments are not captured automatically. You can manually capture payments using the Manually Capture Payments API.
Response Parameters
Response Parameters
id
: string The unique identifier of the order. For example, order_1Aa00000000002.entity
: string The name of the entity. Here, it is order.amount
: integer The amount for which the order was created, in currency subunits.amount_paid
: integer The amount paid against the order, in currency subunits.amount_due
: integer The amount pending against the order, in currency subunits.currency
: string The ISO currency code for the order. For example, INR.receipt
: string The receipt number corresponding to the order.offer_id
: string The unique identifier of the offer applied to the order. Returns null if no offer is applied.status
: string The status of the order.attempts
: integer The number of payment attempts made against this order.notes
: json object Key-value pairs used to store additional information about the entity. Maximum 15 key-value pairs, 256 characters each.created_at
: integer Unix timestamp at which the order was created.3.2 Initiate a Payment
Use the following endpoint to create a payment against the blocked amount.POST /v1/payments/create/json
Request Parameters
Request Parameters
amount
: integer The amount you want to charge your customer. This should be the same as the order amount.currency
: string The 3-letter ISO currency code for the payment.order_id
: string The unique identifier of the order created.customer_id
: string The unique identifier of the customer you want to charge.token
: string The token_id generated when the customer successfully completes the authorisation payment.recurring
: string Determines whether recurring payment is enabled or not.true: Recurring payment is enabled.false: Recurring payment is not enabled.
contact
: string The customer’s phone number.email
: string The customer’s email address.notes
: object Key-value pair you can use to store additional information about the entity. Maximum of 15 key-value pairs, 256 characters each.description
: string A user-entered description for the payment.Response Parameters
Response Parameters
razorpay_payment_id
: string Unique identifier of the payment.razorpay_order_id
: string Unique identifier of the order.razorpay_signature
: string Signature generated for the payment.