Overview
Google Pay API Status Dashboard (Status Dashboard) provides information on ongoing widespread incidents and the status of Google Pay API products. This information can include product disruptions, outages, or informational messages about a temporary issue.
Status Dashboard is designed to be available even if the Google Pay API itself is unavailable or affected by a disruption.
Status Dashboard is available to everyone through the following interfaces:
Use Status Dashboard as the first stop when facing a service disruption for our APIs. It will always have the most accurate information we can provide.
For information specific to your integration that does not affect our broader APIs, see the Google Pay & Wallet Console Support page instead.
Monitored APIs
| Name | Description |
|---|---|
| Android CreateButton API | Provides an up-to-date copy of the Google Pay button. |
| Android IsReadyToPay API | Provides information about the user's Google Pay API eligibility. |
| Android LoadPaymentData API | Enables the Google Pay API payment sheet. |
| Web CreateButton API | Provides an up-to-date copy of the Google Pay button. |
| Web IsReadyToPay API | Provides information about the user's Google Pay API eligibility. |
| Web LoadPaymentData API | Enables the Google Pay API payment sheet. |
Incidents in Google Pay API Status Dashboard
When our engineering or support teams receive a signal that a product is experiencing a significant disruption, we check if the disruption is already listed in Status Dashboard. If the disruption is not listed, we will investigate to replicate the disruption and post an update.
Types
The Google Pay API Status Dashboard shows the following incident types, from greatest to least severity:
- Service Outage: The service is unavailable or unusable for many or all users.
- Service Disruption: The service is available for many or all users, but may be slow or otherwise degraded.
- Service Information: The service is available, but with some limitations or unusual conditions.
- Available: The service is available as expected.
Click an incident's icon to learn more about it, including a full history of the incident's status and updates, with the most recent update at the top.
Detection
Google Pay API uses internal monitoring and external support channels to detect incidents. For more information, see the monitoring chapter in our SRE book.
Initial response
When a team detects an incident, they first perform initial triage to determine its scope and severity. If we determine the scope is sufficient to affect many customers, we add an initial notification to the Google Pay API Status Dashboard. Initial notifications are sparse, frequently only mentioning the name of the affected API. This is because we prioritize fast notification over detail. Detail will be added in subsequent updates as we investigate the incident.
To provide our users with as much actionable information as possible without alarming you with issues that may not affect you, incidents that affect few customers are not added to Status Dashboard, but are communicated directly with the affected users.
Investigation
Product engineering teams are responsible for investigating the root cause of incidents, although they are assisted by our support and site reliability teams. For an overview of our troubleshooting process, refer to the effective troubleshooting chapter of our SRE book.
Mitigation and Fix
An issue is considered fixed only when changes have been made that Google is confident will end the impact indefinitely. For example, the fix could be rolling back a change that triggered an incident.
While an incident is in progress, Google Pay API and the product team attempt to mitigate the issue. Mitigation is when the impact or scope of an issue can be reduced, for example, by temporarily providing additional resources to a product suffering overload.
If no mitigation has been found, when possible, the Google Pay API team finds and communicates workarounds. Workarounds are steps that you can take to solve the underlying need despite the incident. A workaround might be to use different settings for an API call to avoid a problematic code path.
Follow up
While an incident is ongoing, the Google Pay API team provides regular updates. Updates typically provide:
- More information about the incident, such as error messages, zones or regions affected, which features are affected, or percentages of impact.
- Progress towards mitigation, including any workarounds.
- Timelines for communication, tailored to the incident.
- Changes in status, such as when an incident is fixed.
Retrospective
All incidents have a retrospective internally to fully understand the incident and identify reliability improvements that Google can make. These improvements are then tracked and implemented. For more information on post mortems at Google, see the postmortem culture chapter of our SRE book.
FAQ
Read answers to frequently asked questions about the Google Pay API Status Dashboard here.
Where can I find information about past product disruptions and outages?
To view information about product disruptions and outages in the last year, click View history on the dashboard. To view a product's outage history for the last five years, click See more for that product.
Can I build integrations to consume the data displayed in Status Dashboard programmatically?
Yes, you can consume the data displayed on the Status Dashboard in the following ways:
- Through an RSS feed
- Through a JSON History file
The RSS feed and JSON History file provide incident status information which can be consumed programmatically through standard RSS and JSON parsing libraries and tools.
What if I am experiencing an issue, but it is not listed on the dashboard?
The Google Pay API Status Dashboard provides current and historical status information for any major incident that affects Google Pay API products and services. If you are experiencing an issue that is not listed on the dashboard, the issue may be isolated to your projects or instances, or it may be impacting a limited number of customers. You can contact our support team through the Google Pay & Wallet Console about any issues you are experiencing that are specific to your integration. If we determine your issue meets our criteria for Status Dashboard, we will then add it to the dashboard.
Use the Send feedback button on the bottom of the Status Dashboard dashboard to report feedback on the design or behavior of the dashboard itself, not the monitored APIs.