Pawapay status

Pawapay currently reports degraded service, which is narrower than a full outage. Open incident: Performance degradation affecting Mozambique Vodacom services. It started yesterday at 22:18 UTC. PayAtlas last checked the status page today at 01:50 UTC.

They are the states Pawapay publishes on its official status page. Operational means the service works normally. Degraded means part of it is slower or failing for some customers, regions or payment methods, while the rest still works. Outage means a major disruption: a service, or a key part of it, is unavailable. Resolved marks an incident Pawapay has closed; the time it was resolved shows when you hover it.

Not on its own. Firemap shows what Pawapay publishes about its platform, not the state of your account. An incident may affect only some regions, payment methods or integrations. Check your own transaction logs and decline codes, and contact Pawapay support with specific transaction IDs if you see failures.

From official status pages only. Firemap reads each page it tracks automatically every few minutes and records every status change and incident the provider publishes there. Nothing about Pawapay is added or edited by hand.

They come from different sources. The official status is what Pawapay has confirmed, and providers often post an incident only after the first failures. Community reports come from users and can show a problem earlier, but it may be local: one bank, one country or one integration. Treat reports without an official incident as an early signal, not a confirmed outage.

Start with your own data: error rates, decline codes and response times by payment method, card scheme and country. Compare them with the scope of the incident on the status page. Make sure the backup provider supports the same methods and currencies, move a small share of traffic first, and switch back once the incident is resolved and your metrics recover.

Firemap tracks the official status pages of payment providers listed on PayAtlas. Each page is checked automatically, and every incident is stored with its start time and, once resolved, its end time. When Firemap has data for Pawapay, this page shows up to 90 days of status history and incidents from the last 30 days.

Firemap can confirm only what Pawapay has published on its status page: the current status, incidents with their start time and, once resolved, end time, and how long the page has been tracked. It cannot confirm the impact on a specific merchant, transaction or region unless Pawapay says so, and it cannot see problems the provider has not reported.