Stripe health alerts
Monitor the health of your API integrations with alerts and insights.
Stripe health alerts offer real-time monitoring and automated notifications for issues that affect your payments flows or any integrations with Stripe products. This service alerts your team about unexpected trends in request failures, transaction volume, or latency. Evaluate these trends to see if they impact your ability to process payments or use Stripe products effectively.
Note
Your reliance on health alerts is at your own risk. Stripe isn’t liable for any losses, damages, or costs relating to the accuracy or inaccuracy of the alerts, and any actions that you might take or refrain from taking based on alerts.
Availability
Health alerts are only available to users with Stripe’s Premium and Enterprise Support plans. If you want to set up health alerts for your team, contact your technical account manager to configure the email addresses or distribution lists to receive these alerts.
Communication channels
Health alerts are sent through various communication channels to inform your team they might need to respond to users.
| Email notifications | Stripe sends email alerts to the pre-configured email addresses or distribution lists. |
| Health tab in Workbench | An interactive tab in Workbench that displays a 30-day history of alerts, including their severity level, status (open or resolved), and trigger time. |
Connect
If you use Stripe Connect, Stripe alerts you about your total volume, which includes both your applicable platform account and its corresponding connected accounts. These alerts are delivered through the same communication channels.
Organizations
If you use Stripe Organizations, which allows you to manage multiple Stripe accounts, Stripe sends alerts at the account ID-level for all accounts within your organization. These alerts are delivered through the same communication channels.
Alert categories
Health alerts monitor the following categories and send you proactive alerts.
Elevated API error rates
These alerts track API requests related to most Stripe payments products. They notify you about any issues that might affect your integration’s ability to process payments.
Stripe sends elevated API error rates alerts for:
| Product | Alert description |
|---|---|
| Payment Intents API | These alerts are usually related to failures for API events related to the setup, management, confirmation, and capture of PaymentIntents. |
| Bank Accounts API | These alerts address failures related to establishing a secure connection between a user and a financial institution (such as a bank), as well as issues with financial data retrieval and the authentication of connection sessions. This connection facilitates the exchange of data, including account information and transaction details. |
| Stripe Terminal | Includes coverage for API actions specific to Terminal such as: |
| Stripe Issuing | Alerts on request failures related to the Issuing API address the authentication, authorization, creation, retrieval, and updates of Stripe-issued payment cards. |
Error codes for elevated API error rates
| Error code | Possible cause |
|---|---|
400 | Indicates malformed requests, where the server can’t understand the syntax of the request. Check your integration for the specified API method in the alert message. |
402 | Indicates that the request contained valid parameters, but it failed due to issues with the financial transaction or payment method validation. |
409 | Occurs when there’s a conflict, such as trying to create a resource that already exists. |
429 | Indicates too many requests sent in a given timeframe, often due to rate-limiting. Elevated counts in this category might mean that a required parameter was omitted. |
500 | Indicates server-side issues with Stripe. While rare, these errors could mean there’s a problem with our servers or there’s a timeout caused by problematic calls on the user’s end. Stripe always investigates 500 errors and notifies you when they’re resolved. |
API latency
The API latency metric measures latency variances per Stripe account for specific API methods. High latency alerts can indicate potential issues in payment processing and are monitored by Stripe to ensure timely responses.
Anomaly alerts
The Authorization rate decline anomaly alert uses machine learning (ML) to detect sudden drops or changes in payment performance in near-real time. It indicates a sudden drop in authorization rates, impacting overall payment success. When available, these alerts also indicate the subsets of payment traffic that are degrading. For example, the alert might indicate the specific card issuing bank or card type that is impacted.
Webhook latency alerts
To minimize service disruptions, we monitor changes in webhook latency to ensure that real-time updates are delivered promptly. To learn more about webhook specific errors and alerts, see Errors.