API Test Keys

Orders Entity

The Orders entity has the following parameters:

Is this page helpful?

Entity

1{
2  "id": "order_DaZlswtdcn9UNV",
3  "entity": "order",
4  "amount": 50000,
5  "amount_paid": 0,
6  "amount_due": 50000,
7  "currency": "INR",
8  "receipt": "Receipt #20",
9  "status": "created",
10  "attempts": 0,
11  "notes": {
12    "key1": "value1",
13    "key2": "value2"
14  },
15  "created_at": 1572502745
16}

id

string

The unique identifier of the order.

amount

integer

Payment amount in the smallest currency sub-unit. For example, if the amount to be charged is ₹299.00, then pass 29900 in this field. In the case of three decimal currencies, such as KWD, BHD and OMR, to accept a payment of 295.991, pass the value as 295990. And in the case of zero decimal currencies such as JPY, to accept a payment of 295, pass the value as 295.

Watch Out!

As per payment guidelines, you should pass the last decimal number as 0 for three decimal currency payments. For example, if you want to charge a customer 99.991 KD for a transaction, you should pass the value for the amount parameter as 99990 and not 99991.

partial_payment

boolean

Indicates whether the customer can make a partial payment. Possible values:

true: The customer can make partial payments.
false (default): The customer cannot make partial payments.

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. Refer to the

list of supported currencies

Handy Tips

Razorpay has added support for zero decimal currencies, such as JPY, and three decimal currencies, such as KWD, BHD, and OMR, allowing businesses to accept international payments in these currencies. Know more about

Currency Conversion

(May 2024).

receipt

string

Receipt number that corresponds to this order. Can have a maximum length of 40 characters and has to be unique.

status

string

The status of the order. Possible values:

created: When you create an order it is in the created state. It stays in this state till a payment is attempted on it.
attempted: An order moves from created to attempted state when a payment is first attempted on it. It remains in the attempted state till one payment associated with that order is captured.
paid: After the successful capture of the payment, the order moves to the paid state. No further payment requests are permitted once the order moves to the paid state. The order stays in the paid state 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.

Orders Entity

The Orders entity has the following parameters:

Is this page helpful?

id

string

The unique identifier of the order.

amount

integer

Watch Out!

partial_payment

boolean

Indicates whether the customer can make a partial payment. Possible values:

true: The customer can make partial payments.
false (default): The customer cannot make partial payments.

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. Refer to the

list of supported currencies

Handy Tips

Currency Conversion

(May 2024).

receipt

string

Receipt number that corresponds to this order. Can have a maximum length of 40 characters and has to be unique.

status

string

The status of the order. Possible values:

created: When you create an order it is in the created state. It stays in this state till a payment is attempted on it.
attempted: An order moves from created to attempted state when a payment is first attempted on it. It remains in the attempted state till one payment associated with that order is captured.
paid: After the successful capture of the payment, the order moves to the paid state. No further payment requests are permitted once the order moves to the paid state. The order stays in the paid state 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.

Entity

1{
2  "id": "order_DaZlswtdcn9UNV",
3  "entity": "order",
4  "amount": 50000,
5  "amount_paid": 0,
6  "amount_due": 50000,
7  "currency": "INR",
8  "receipt": "Receipt #20",
9  "status": "created",
10  "attempts": 0,
11  "notes": {
12    "key1": "value1",
13    "key2": "value2"
14  },
15  "created_at": 1572502745
16}