Coming soon, Mercado Pago's Status Page will have a new structure in which events will be organized by affected product and flow. For InStore integrations, components will be divided between QR and Point. In Online Payments, there will be specific components for Checkouts, Subscriptions, and other products.

In addition to incidents, the Status Page will report performance degradations and payment method status by product and site. This gives you more context to assess your integration's behavior and the scope of an event.

The reorganization separates integration interface status from payment method health. With this distinction, a localized change in payment method status will not be communicated as an outage of an interface that remains available.

For example, a change in payment method status for Point in MLA does not automatically mean there is an impact on Point integrations with the Orders API. For this flow, the assessment considers the end-to-end journey: 5XX errors during order creation, orders reaching the terminals, and delivery of the related webhooks.

The confirmed technical scope includes the following products, flows, and services:

• QR: legacy QR integrations and QR integrations with the Orders API.
• Point: Point integrations, Point integrations with the Orders API, and the Devices API.
• Online Payments: Checkout Pro, Checkout API, Bricks, Subscriptions, and Platforms integrations.
• Online Platforms: integrations with Platforms.
• Cross-cutting APIs and services: the Payments, Preferences, and Merchant Orders APIs, as well as IPN, Webhooks, and OAuth.

To avoid notifications caused by transient fluctuations, the Status Page will communicate impacts that last approximately 15 to 30 minutes.

1. Degraded Performance: indicates a lower-severity degradation.
2. Partial Outage: indicates a higher-severity impact.
3. Major Outage: communicates a total impact on the components involved.

The new components will be available starting October 1. If you are subscribed to all components, you do not need to make any changes because notifications will continue to cover the new components.

If you are subscribed to only some of them, from that date access the Status Page, review your preferences, and select the components you want to follow, since equivalent components will not be added automatically.

If you are not yet subscribed, from that date you can subscribe to the components relevant to your integration.

These preferences apply to email, SMS, Slack, and webhook notifications.