> ## Documentation Index
> Fetch the complete documentation index at: https://razorpay-881012b3.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Payment Downtime Entity

> Know about the Payment Downtime entity parameters and their description.

<div style={{display:"flex",flexWrap:"wrap",alignItems:"center",gap:"0.35rem 0.9rem",border:"1px solid rgba(128,128,128,0.28)",borderRadius:"0.5rem",padding:"0.45rem 0.75rem",margin:"0 0 1.25rem",fontSize:"0.875rem"}}>
  <span style={{fontWeight:600}}>Available in</span>
  <span>🇮🇳 India</span>
  <span>🇸🇬 Singapore</span>
  <span>🇺🇸 United States</span>
</div>

The Downtime entity has the following parameters:

<ResponseExample>
  ```json Netbanking theme={null}
  {
    "id": "down_F1cxDoHWD4fkQt",
    "method": "netbanking",
    "begin": 1591946222,
    "end": null,
    "status": "started",
    "scheduled": false,
    "severity": "high",
    "instrument": {
      "bank": "COSB"
    },
    "created_at": 1591946223,
    "updated_at": 1591946297
  }
  ```

  ```json UPI - VPA Handle theme={null}
  {
    "id": "down_F8LCfthx90fMOo",
    "method": "upi",
    "begin": 1593412063,
    "end": null,
    "status": "started",
    "scheduled": false,
    "severity": "high",
    "instrument": {
      "vpa_handle": "oksbi"
    },
    "created_at": 1593412092,
    "updated_at": 1593412092
  }
  ```

  ```json UPI - PSP theme={null}
  {
    "id": "down_F8LCfthx90fMOo",
    "method": "upi",
    "begin": 1593412063,
    "end": null,
    "status": "started",
    "scheduled": false,
    "severity": "high",
    "instrument": {
      "psp": "bhim"
    },
    "created_at": 1593412092,
    "updated_at": 1593412092
  }
  ```

  ```json Turbo UPI theme={null}
  {
    "entity": "collection",
    "count": 1,
    "items": [
      {
        "id": "down_F1cxDoHWD4fkQt",
        "entity": "payment.downtime",
        "method": "upi",
        "begin": 1591946222,
        "end": null,
        "status": "started",
        "scheduled": false,
        "severity": "high",
        "instrument": {
          "flow": "in_app"
        },
        "created_at": 1591946223,
        "updated_at": 1591946297
      }
    ]
  }
  ```

  ```json Card - Issuer theme={null}
  {
    "id": "down_F7LroRQAAFuswd",
    "method": "card",
    "begin": 1593196031,
    "end": null,
    "status": "started",
    "scheduled": false,
    "severity": "high",
    "instrument": {
      "issuer": "SBIN",
      "card_type": "credit"
    },
    "created_at": 1593196089,
    "updated_at": 1593196089
  }
  ```

  ```json Card - Network theme={null}
  {
    "id": "down_F7LroRQAAFuswd",
    "method": "card",
    "begin": 1593196031,
    "end": null,
    "status": "started",
    "scheduled": false,
    "severity": "high",
    "instrument": {
      "network": "VISA",
      "card_type": "credit"
    },
    "created_at": 1593196089,
    "updated_at": 1593196089
  }
  ```
</ResponseExample>

<ResponseField name="id" type="string">
  Unique identifier of the downtime's occurrence.
</ResponseField>

<ResponseField name="entity" type="string">
  Here, it will be `payment.downtime`.
</ResponseField>

<ResponseField name="method" type="string">
  The payment method that is experiencing the downtime. Possible values include:

  * `card`
  * `netbanking`
  * `upi`
</ResponseField>

<ResponseField name="begin" type="integer">
  Timestamp (in Unix) that indicates the start of the downtime. Applicable for both scheduled and unscheduled downtimes.
</ResponseField>

<ResponseField name="end" type="integer">
  Timestamp (in Unix) that indicates the end of the downtime.<br /> Available only for scheduled downtimes, where the end-time is known. Set to `null` when the end-time is unknown, possibly during unscheduled downtimes.
</ResponseField>

<ResponseField name="status" type="string">
  Status of the downtime. Possible statuses:

  * `scheduled`: A downtime is scheduled to happen at a later time.
  * `started`: The downtime has started and is ongoing.
  * `resolved`: The downtime is resolved.
  * `updated`: An ongoing downtime that has been updated after its start. For example, when the severity of the downtime changes from medium to high.
</ResponseField>

<ResponseField name="scheduled" type="boolean">
  Indicates if the downtime is scheduled or unscheduled. Possible values:

  * `true`: This is a scheduled downtime by the issuer, network, or the bank, which was informed to Razorpay.
  * `false`: This is an unscheduled downtime.
</ResponseField>

<ResponseField name="severity" type="string">
  Severity of the downtime. Possible values:

  * `high`: Possible when all the payment methods are affected by downtime. Observed when the issuer, bank or network is down.
  * `medium`: Possible when a higher number of declines in transactions or low success rates are observed with the payment methods.
  * `low`: Possible when the reason for the downtime is unknown. Impact on payment methods is minimal.
</ResponseField>

<ResponseField name="instrument" type="string">
  Payment method that is underperforming.
</ResponseField>

<ResponseField name="bank" type="string">
  Bank code of the affected bank. Possible values:

  * `HDFC`
  * `ICIC`
  * `SBIN`
  * `KKBK`
  * `UTIB`
  * `PUNB`
</ResponseField>

<ResponseField name="network" type="string">
  Card network. Possible values:

  * `AMEX`
  * `DICL`
  * `MC`
  * `RUPAY`
  * `VISA`
  * `ALL`
</ResponseField>

<ResponseField name="issuer" type="string">
  The 4-character issuer code unique to each issuing bank in India. Possible values:

  * `SBIN`
  * `HDFC`
  * `ICIC`
  * `UTIB`
  * `CITI`
  * `PUNB`
  * `KKBK`
  * `CNRB`
  * `BKID`
  * `BARB`
  * `JAKA`
  * `UBIN`
</ResponseField>

<ResponseField name="psp" type="string">
  Code of the affected Payment Service Provider (PSP). This is populated only when VPA handles associated with the PSP are down. If a PSP is associated with multiple VPA handles, it is marked down only when **all** the handles associated with it are down. For example, `google_pay` is marked down only when all Google Pay handles - `oksbi`, `okhdfcbank`, `okicici` and `okaxis` are down. Possible values for this parameter are:

  * `google_pay`
  * `phonepe`
  * `paytm`
  * `bhim`
</ResponseField>

<ResponseField name="vpa_handle" type="string">
  Affected VPA handle. For example, `@oksbi`. To learn about the possible values, refer to the [list of handles supported by NPCI](https://www.npci.org.in/what-we-do/upi/3rd-party-apps). If the entire UPI system is experiencing a downtime, the value `ALL` is displayed.
</ResponseField>

<ResponseField name="card_type" type="string">
  The card type used to process the payment. Possible values:

  * `credit`
  * `debit`
</ResponseField>

<ResponseField name="created_at" type="integer">
  Timestamp (in Unix) that indicates the time at which the downtime was recorded in Razorpay servers.
</ResponseField>

<ResponseField name="updated_at" type="integer">
  Timestamp (in Unix) that indicates the time at which the downtime record was updated in Razorpay servers.
</ResponseField>

<ResponseField name="flow" type="string">
  Indicates the UPI payments flow being used during the downtime event. Possible values:

  * `collect`
  * `intent`
  * `in_app` Only applicable for Turbo UPI payments. <br />
    Know more about [the possible values](/docs/payments/payment-methods/upi).
</ResponseField>