Google Pay incident
UPDATE: We're aware of a problem with Android CreateButton API, Android IsReadyToPay API, Android LoadPaymentData API, Secure Payment Authentication (SPA), Web CreateButton API, Web IsReadyToPay API and Web LoadPaymentData API affecting a majority of users. We will provide an update by Sep 16, 2026, 3:47 p.m. UTC detailing when we expect to resolve the problem. Please note that this resolution time is an estimate and may change. The affected users are able to access Android CreateButton API, Android IsReadyToPay API, Android LoadPaymentData API, Secure Payment Authentication (SPA), Web CreateButton API, Web IsReadyToPay API and Web LoadPaymentData API, but are seeing error messages, high latency, and/or other unexpected behavior.
Google Pay experienced a major incident on September 16, 2026, lasting 23h 54m. The incident has been resolved; the full update timeline is below.
Update timeline
- monitoring Sep 16, 2026, 04:31 PM UTC
Incident began at 2026-09-16 15:00 (times are in Coordinated Universal Time (UTC) ). Android CreateButton API, Android IsReadyToPay API, Android LoadPaymentData API, Secure Payment Authentication (SPA), Web CreateButton API, Web IsReadyToPay API and Web LoadPaymentData API service has already been restored for some users, and we expect a resolution for all users in the near future. Please note this time frame is an estimate and may change. The affected users are able to access Android CreateButton API, Android IsReadyToPay API, Android LoadPaymentData API, Secure Payment Authentication (SPA), Web CreateButton API, Web IsReadyToPay API and Web LoadPaymentData API, but are seeing error messages, high latency, and/or other unexpected behavior. Affected products: Android CreateButton API, Android IsReadyToPay API, Android LoadPaymentData API, Secure Payment Authentication (SPA), Web CreateButton API, Web IsReadyToPay API, Web LoadPaymentData API