3. Create a One Time Payment
Create and charge a one time payment using Razorpay APIs.
You should perform the following steps to create and charge your customer a one time payment:
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.
Watch Out!
We will not attempt any retry if the debit fails for tokens with the notification object in the created order. You must manually trigger the debit by calling the API, and only after the payment_after timestamp specified in the notification object.
The following endpoint creates an order.
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 Curlec.
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 .
Once you have generated an order_id, use it with the token_id to create a one-time payment. After the payment is complete (authorised or failed), the respective token will move to the cancelled state, and you can no longer use the token. You will get the
The following endpoint creates a one time payment to charge the customer.
mandatory
string The customer's email address. For example, nur.aisyah@example.com.
contact
mandatory
integer The customer's phone number. For example, 60345675444.
currency
mandatory
string 3-letter ISO currency code for the payment. Currently, only INR is allowed.
amount
mandatory
integer The amount you want to charge your customer. This should be the same as the order amount.
order_id
mandatory
string The unique identifier of the order created. For example, order_1Aa00000000002.
customer_id
mandatory
string The unique identifier of the customer you want to charge. For example, cust_1Aa00000000002.
token
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.
description
optional
string A user-entered description for the payment. For example, Creating recurring payment for Nur Aisyah
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”.
Is this integration guide useful?