Retrieve merchant-specific downtime information using the PayU API. Fetch real-time and historical downtime details for associated payment entities with customizable date ranges and filters.
Use this endpoint to retrieve merchant-specific downtime information. The response includes downtime details for entities associated with the specified merchant.
Method
POST
Endpoint
/v2/payments/merchant/downtime
Environment
| Environment | URL |
|---|---|
| Production | https://info.payu.in/v2/payments |
Sample Request
curl -X POST 'https://info.payu.in/v2/payments/merchant/downtime' \
-H 'Content-Type: application/json' \
-H "date: {{date}}" \
-H "authorization: {{authorization}}" \
-d '{
"from":"2026-03-22 00:00:00",
"to":"2026-03-24 23:59:59",
"categories":[
"upi"
],
"page":2,
"per_page":25
}'Sample Response
{
"merchant_id":12965582,
"categories":[
"upi",
"nb"
],
"from":"2026-02-20T00:00:00+05:30",
"to":"2026-03-25T02:59:59+05:30",
"count":2,
"page":1,
"per_page":50,
"total_pages":1,
"downtimes":[
{
"entity_name":"Test Merchant(12345678)-TEST SI(123)",
"entity_type":"merchant_id-pg_id",
"method":"upi",
"started_at":"2026-03-24T18:33:59+05:30",
"ended_at":"2026-03-24T18:37:59+05:30",
"status":"recovered",
"instrument":{
"merchant_id":"Test Merchant",
"pg_id":"TEST SI"
},
"summary":{
"duration_minutes":4.0,
"failed_count":347,
"success_rate_during_downtime":6.72,
"srt_drop_rel":78.52,
"severity":"LOW"
}
},
{
"entity_name":"Test Merchant(12345678)-SI",
"entity_type":"merchant_id-mode",
"method":"upi",
"started_at":"2026-03-24T14:01:59+05:30",
"ended_at":"2026-03-24T14:17:59+05:30",
"status":"recovered",
"instrument":{
"merchant_id":"Test Merchant",
"mode":"SI"
},
"summary":{
"duration_minutes":16.0,
"failed_count":8521,
"success_rate_during_downtime":1.21,
"srt_drop_rel":93.66,
"severity":"HIGH"
}
}
]
}{
"error": "merchant_id is invalid"
}Request Headers
| Parameter | Description |
|---|---|
| date | The current date and time. For example, format of the date is Wed, 28 Jun 2023 11:25:19 GMT. |
| authorization | The actual HMAC signature generated using the specified algorithm (sha512) and includes the hashed data. For more information, refer to authorization fields description. |
authorization fields description
| Field | Description |
|---|---|
| username | Represents the username or identifier for the client or merchant, for example smsplus. |
| algorithm | Use SHA512 algorithm for hashing and send this as header value. |
| headers | Specifies which headers have been used in generating the hash, for example date. |
| signature | The HMAC signature generated using the specified algorithm. For more information, refer to hashing algorithm. |
hashing algorithm
You must hash the request parameters using the following hash logic:
Hash logic: sha512(`<Body data>` + '|' + date + '|' + merchant_secret)
Where <Body data> contains the request body posted with the request.
Sample header code
var merchant_key = 'smsplus';
var merchant_secret = 'izF09TlpX4ZOwmf9MvXijwYsBPUmxYHD';
// date
var date = new Date();
date = date.toUTCString();
// authorization
var authorization = getAuthHeader(date);
function getAuthHeader(date) {
var AUTH_TYPE = 'sha512';
var data = isEmpty(request['data']) ? "" : request['data'];
var hash_string = data + '|' + date + '|' + merchant_secret;
var hash = CryptoJS.SHA512(hash_string).toString(CryptoJS.enc.Hex);
return `hmac username="${merchant_key}", algorithm="${AUTH_TYPE}", headers="date", signature="${hash}"`;
}Request Parameters
Mandatory Parameters
Parameters marked with are mandatory.
| Parameter | Description |
|---|---|
| from | string | number The start timestamp. Refer to the Time Format and Validation Rules section for format and validation information. |
| to | string | number The end timestamp. Refer to the Time Format and Validation Rules section for format and validation information. |
| categories | object | string Represents the downtime category. If the value is not passed, no category filter is applied. Possible values:
|
| page | number The page number used for pagination. Defaults to 1. |
| per_page | number Items displayed per page. Defaults to 50. The maximum items per page is 100. |
Time Format and Validation Rules
Supported Input Formats of from and to Parameters
| Format | Example |
|---|---|
YYYY-MM-DD HH:MM:SS | 2026-03-25 10:30:00 |
| ISO8601 with time | 2026-03-25T10:30:00Z |
| Unix epoch (number) | 1715769600 |
| Unix epoch (string) | "1715769600" |
Validation rules:
fromandtovalues must include time granularity (seconds) unless epoch is used.- The
fromvalue must be before thetovalue. - The
fromvalue must be within the last 3 months. - The
tovalue must not be greater than the current server time.
Response Parameters
| Parameter | Description |
|---|---|
| merchant_id | number The unique merchant identifier. |
| categories | array The applied category filters. |
| from | string The start time of the downtime in the ISO8601 format. |
| to | string The end time of the downtime in the ISO8601 format. |
| count | number The total count of matching downtimes. |
| page | number The current page number of the received response. |
| per_page | number The total number of items displayed per page. |
| total_pages | number The total number of pages the response contains. |
| downtimes | array The array of downtime objects. Parameters are described in the Downtime Object section. |
Downtime Object
Parameters and Description
| Parameter | Description |
|---|---|
| entity_name | string The complete entity name with identifiers. |
| entity_type | string The entity type. For example merchant_id-pg_id and merchant_id-mode |
| method | string The payment method or category. For example upi |
| started_at | string The start time of the downtime in the ISO8601 format. |
| ended_at | string The end time of the downtime in the ISO8601 format. |
| status | string The downtime status. Possible values:
|
| instrument | object The entity part details. |
| summary | array The downtime summary details. Parameters are described in the Summary Object section. Parameters are described in the Summary Object section. |
Summary Object
Parameters and Description
| Parameter | Description |
|---|---|
| duration_minutes | number The duration of downtime in minutes. |
| failed_count | number The number of failed transactions during the downtime. |
| success_rate_during_downtime | number The success rate percentage during the downtime. |
| srt_drop_rel | number The relative success rate drop. |
| severity | string The severity level: Possible values:
|
Error Response Parameters
| Error | Description | Solution |
|---|---|---|
Invalid JSON: ... | This error occurs when the json is invalid. | Make sure the json is valid. |
Unknown parameters: ... | This error occurs when you pass unknown parameters. | Make sure to pass valid parameters. |
merchant_id or mid is required for merchant | This error occurs when you do not pass the the merchant ID. | Make sure to pass the merchant ID. |
merchant_id is invalid | This error occurs when you pass an invalid merchant ID. | Make sure to pass the valid merchant ID. |
from is required | This error occurs when you do not pass the from parameter value. | The from is mandatory parameter. Ensure to pass the value. |
to is required | This error occurs when you do not pass the to parameter value. | The to is mandatory parameter. Ensure to pass the value. |
from must include time as HH:MM:SS (...) | This error occurs when the from parameter value format is invalid. | Make sure to pass the from parameter value in the valid format. Refer to the Time Format and Validation Rules section for more information. |
to must not be greater than the current time | This error occurs when the timestamp of the to parameter is a past time. | Ensure the to parameter timestamp is greater than the current time. |
from must be within the last 3 months | This error occurs when the timestamp of the from parameter is greater than 3 months. | Make sure the from timestamp is less than 3 months. |
from must be before to | This error occurs when the from timestamp exceeds the to timestamp. | Make sure the from timestamp is within the to timestamp. |
categories must be from: upi, nb, cards, emi | This error occurs when the category value is other than the following values:
| Make sure the category value is any of the following values:
|