Skip to main content
Use this endpoint to retrieve details of a particular order as per the id.

Request

Curl

Response

Success

Parameters

id mandatory : string Unique identifier of the order to be retrieved.

Parameters

id : string The unique identifier of the order. amount : integer The amount for which the order was created, in currency subunits. For example, for an amount of , enter 29500. 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. Refer to the list of supported currencies. 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.

Errors

The API “ provided is invalid.
  • code: 400
  • description: The API credentials passed in the API call differ from the ones generated on the Dashboard. Possible reasons: - Different keys for test mode and live modes.
  • Expired API key.
  • solution: The API keys must be active and entered correctly with no whitespace before or after the keys.
id is not a valid id.
  • code: 400
  • description: The order_id passed is invalid.
  • solution: Use a valid order_id.
The id provided does not exist
  • code: 400
  • description: The order_id does not exist or does not belong to the requestor.
  • solution: Ensure that you use a valid order_id that belongs to the requestor.