Stripe provides real-time monitoring and alerting for your critical payments path. This service notifies your team when there are unexpected trends in request failures, volume, or latency that affect your ability to process individual payments.

Merchant Health Alerting is available for users with our Premium and Enterprise Support plans. If you'd like to receive merchant health alerts, please reach out to your technical account manager to set up the email addresses or distribution lists that should receive notifications.

Why real-time alerts?

Merchant Health Alerts help payments teams quickly identify the root cause of unexpected request failures. As a result, these alerts are both real-time and fully automated. They’re tailored to your Stripe usage, and utilize tailored, data-driven thresholds that account for seasonality and adjust for durable trends.

If you have payment request failures (see the list of supported endpoints below), Stripe will send your team dynamic alerts with detailed summaries of the unsuccessful requests and the associated endpoints. Any subsequent related errors will thread on the original alert email, providing automated, timely updates so that Stripe and your team can jointly resolve any issues.

After receiving an alert, you can review the associated errors in your developer dashboard.

Alert response

The majority of issues are detected and resolved automatically. If an issue doesn't self-resolve, our on-call Support team rapidly investigates to triage the issue and identify the source.

If Stripe identifies a bug or failure in our product, the on-call Support team opens an incident, which pages the relevant Stripe engineering team. Our Incident Response Management team works directly with the engineering team to share periodic updates and own the issue through resolution.

If the failures originate from issues with either your specific integration or an upstream partner, our Support team will reach out directly with any recommended next steps. You can reply to that outreach, or you can engage your account team during business hours.

In both cases, our team will provide a summary when the issue is resolved.

Alerting coverage

Alerts--relevant 400, 402, 409, 429, and 500 errors, and API latency errors--cover the critical payments path for the following products:

• Payment Intents: includes requests related to Cards, Link, LPMs, and Invoices.
• Bank Connections: includes requests related to account linkage, retrieval, and session latency.
• Terminal: includes requests to token activation, token creation, and payment intent processing.
• Issuing: includes requests related to webhook timeouts and latency.

Other product alerting and insight coverage

• Authorization Rate Decline: includes requests related to sudden drops in authorization rates
• Fraud Disputes: includes requests when there is an increase in fraudulent transactions & disputes
• Traffic Volume Decline: includes requests related to changes in traffic volume to Stripe’s API
• Local Payment Methods (LPMs): includes requests related to many LPMs, for example, PayPal, Wechat Pay, Klarna, and Amazon Pay

Alert categories

You can access a 30-day history of Merchant Health Alerts in the Health tab of Workbench.

For more info, read our full error code documentation. Errors typically mean that Stripe or a financial partner are experiencing an issue and we’re investigating.

• Elevated 429 or 409 errors: Indicate failures due to the information provided (e.g., a required parameter was omitted).
• Elevated 402 errors: Typically the result of failed financial transactions or validations.
• Elevated 500 errors: Indicate an error with Stripe’s servers (these are rare; Stripe maintains global uptime of 99.9995%+). 500s could either be an error on the Stripe side or a timeout (due to a problematic call) on the user’s end.
• Latency variance: Measures API latency for specific API methods, benchmarked per account against our data model’s thresholds.

Contact sales to learn more about merchant health alerting and Stripe's support offerings.