Introduction

API Reference Guide

API Changelog

API Basics

Authentication & Sandbox Setup

Entity & Metadata

Pagination & Rate Limiting

Best Practices

Glossary

Payments

Orders

Payments

Downtime

Settlements

Instant Settlements

Refunds

Disputes

Documents

Customers

Payment Links

QR Codes

Invoices

Items

Plans

Subscriptions

Add-on

Linked Account

Stakeholder

Product Configuration

Transfers

Smart Collect

Smart Collect With TPV

TPAP Pro

Customer Onboarding

Accounts Management

Payments

Mandates Flow

Bills

About Bills

Bills Entity

Create a Bill

Update a Bill

Delete a Bill

Partners

Account

Product Configuration

Stakeholder

Terms and Conditions

Documents

Webhooks

Payout APIs

Get Started

Account Validation

Composite Account Validation

Contacts

Fund Accounts

Payouts

Payouts to Cards

Payout Composite

Payouts Approval

Payout Idempotency

Payout Links

Payout Wallet - Amazon

Transactions

Api

Payments

Downtime

Entity

API Test Keys

Payment Downtime Entity

The Downtime entity has the following parameters:

Is this page helpful?

Netbanking

UPI - VPA Handle

UPI - PSP

Turbo UPI

Card - Issuer

Card - Network

1
{
2
  "id": "down_F1cxDoHWD4fkQt",
3
  "method": "netbanking",
4
  "begin": 1591946222,
5
  "end": null,
6
  "status": "started",
7
  "scheduled": false,
8
  "severity": "high",
9
  "instrument": {
10
    "bank": "COSB"
11
  },
12
  "created_at": 1591946223,
13
  "updated_at": 1591946297
14
}
id
string

Unique identifier of the downtime's occurrence.

entity
string

Here, it will be payment.downtime.

method
string

The payment method that is experiencing the downtime. Possible values include:

  • card
  • netbanking
  • upi

begin
integer

Timestamp (in Unix) that indicates the start of the downtime. Applicable for both scheduled and unscheduled downtimes.

end
integer

Timestamp (in Unix) that indicates the end of the downtime.
Available only for scheduled downtimes, where the end-time is known. Set to null when the end-time is unknown, possibly during unscheduled downtimes.

status
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.

scheduled
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.

severity
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.

instrument
string

Payment method that is underperforming.

Show child parameters (6)

created_at
integer

Timestamp (in Unix) that indicates the time at which the downtime was recorded in Razorpay servers.

updated_at
integer

Timestamp (in Unix) that indicates the time at which the downtime record was updated in Razorpay servers.

flow
string

Indicates the UPI payments flow being used during the downtime event. Possible values:

  • collect
  • intent
  • in_app Only applicable for Turbo UPI payments.
    Know more about

    the possible values

    .

Payment Downtime Entity

The Downtime entity has the following parameters:

Is this page helpful?

id
string

Unique identifier of the downtime's occurrence.

entity
string

Here, it will be payment.downtime.

method
string

The payment method that is experiencing the downtime. Possible values include:

  • card
  • netbanking
  • upi

begin
integer

Timestamp (in Unix) that indicates the start of the downtime. Applicable for both scheduled and unscheduled downtimes.

end
integer

Timestamp (in Unix) that indicates the end of the downtime.
Available only for scheduled downtimes, where the end-time is known. Set to null when the end-time is unknown, possibly during unscheduled downtimes.

status
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.

scheduled
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.

severity
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.

instrument
string

Payment method that is underperforming.

Show child parameters (6)

created_at
integer

Timestamp (in Unix) that indicates the time at which the downtime was recorded in Razorpay servers.

updated_at
integer

Timestamp (in Unix) that indicates the time at which the downtime record was updated in Razorpay servers.

flow
string

Indicates the UPI payments flow being used during the downtime event. Possible values:

  • collect
  • intent
  • in_app Only applicable for Turbo UPI payments.
    Know more about

    the possible values

    .

Netbanking

UPI - VPA Handle

UPI - PSP

Turbo UPI

Card - Issuer

Card - Network

1
{
2
  "id": "down_F1cxDoHWD4fkQt",
3
  "method": "netbanking",
4
  "begin": 1591946222,
5
  "end": null,
6
  "status": "started",
7
  "scheduled": false,
8
  "severity": "high",
9
  "instrument": {
10
    "bank": "COSB"
11
  },
12
  "created_at": 1591946223,
13
  "updated_at": 1591946297
14
}