About Payment Downtime API
Downtimes on payment methods and how to receive notifications.
Downtime is when one or more payment options underperform, leading to considerable delays in payment processing. These downtimes are due to technical issues or outages at Razorpay's partner or issuing banks. Razorpay informs you about the downtime to communicate it to your customers and display only the unaffected payment methods while accepting payments from them.
You can poll the API or configure Webhooks to be notified of the downtimes and plan the remediation steps accordingly.
Downtime communication for the payment methods such as cards, netbanking and UPI is available.
Given below is a list of the downtime entity parameters.
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:
cardnetbankingupi
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 are.
scheduled: A downtime is scheduled to happen at a later time.started: The downtime has started and is ongoing.resolved: The downtime is resolved.cancelled: A scheduled downtime that is invalidated. For example, when a scheduled downtime was communicated but was later cancelled by the bank.
scheduled
boolean 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
Payment method that is underperforming.
bank
if method=netbanking
string Bank code of the affected bank. Possible values:
HDFCICICSBINKKBKUTIBPUNB
network
if method=card
string Card network. Possible values:
AMEXDICLMCRUPAYVISAALL
issuer
if method=card
string The 4-character issuer code unique to each issuing bank in India. Possible values:
SBINHDFCICICUTIBCITIPUNBKKBKCNRBBKIDBARBJAKAUBIN
psp
if method=upi
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_payphonepepaytmbhim
vpa_handle
if method=upi
string Affected VPA handle. For example, @oksbi. To learn about the possible values, refer to the
ALL is displayed.card_type
if method=card
string The card type used to process the payment. Possible values:
creditdebit
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:
collectintentin_appOnly applicable for Turbo UPI payments.
Know more about .
To retrieve details of payment downtimes, see this
.To retrieve details of payment downtimes by ID, see this
.The table below lists the webhook events available for payments downtime.
Was this page helpful?