# 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. > 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 You can receive health alerts according to your Stripe account. ### Health alert tier - **Basic tier**: All Stripe users receive `402` (payment declined due to partner outage) and `500` (failed API request due to Stripe outage) [error status code](https://docs.stripe.com/health-alerts.md#error-status-codes-for-api-error-alerts) health alerts in email and Workbench. - **Advanced tier**: Users on Stripe’s [Growth, Premium or Enterprise Support plan](https://stripe.com/support-plans) receive health alerts in email, Workbench and webhook events see [more detailed alerts](https://docs.stripe.com/health-alerts.md#advanced-tier-alert-categories). ### Connect If you’re a [Connect](https://docs.stripe.com/connect.md) platform, your health alerts include those for both your platform account and its corresponding connected accounts. ### Organisations If you use [Stripe Organizations](https://docs.stripe.com/get-started/account/orgs.md), you can view alerts and insights across all your accounts in a single view in Workbench. ## Communication channels Stripe notifies you of health alerts through the following communication channels to inform your team about issues with the Stripe ecosystem and, if applicable, any next steps. | | Channel | Notification | | ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | | Email notifications | Stripe sends email alerts to the configured email addresses or distribution lists. | | Health tab in Workbench | An interactive tab in [Workbench](https://docs.stripe.com/workbench/health.md) that displays a 30-day history of alerts, including their severity level, status (open or resolved), and impacted requests. | | Webhook events | Alerts are sent as real-time events to your application’s webhook endpoint when [health events](https://docs.stripe.com/api/v2/core/events/event-types.md#v2_event_types-v2.core.health.api_error.firing) occur in your Stripe account. Consider integrating these events with your internal notification systems like Slack and Pagerduty. | ## Configure health alert preferences If you’re the administrator for your Stripe account, you can opt in or out of basic tier health alerts in **Settings** > [Communication preferences](https://dashboard.stripe.com/settings/communication-preferences#api). To configure email addresses or distribution lists for Advanced tier health alerts, contact your technical account manager. If you’re an administrator of a [Stripe Organization](https://docs.stripe.com/get-started/account/orgs.md) receiving Advanced tier health alerts, you can manage preferences for all accounts in the organisation in **Settings** > [Communication management](https://dashboard.stripe.com/org/settings/communication-management). ## Basic tier alert categories ### Increased API errors These alerts track API requests related to Stripe payments products. They notify you about any issues that might affect your integration’s ability to process payments. Error status codes for increased API error alerts include 402 and 500. Learn more about [error codes](https://docs.stripe.com/error-codes.md) and how to resolve them. Stripe sends increased API error alerts for: | Product | Alert description | | -------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | [Payment Intents API](https://docs.stripe.com/payments/payment-intents.md) | These alerts are usually related to failures for API events related to the setup, management, confirmation, and capture of [PaymentIntents](https://docs.stripe.com/api/payment_intents.md). | | [Bank Accounts API](https://docs.stripe.com/api/customer_bank_accounts.md) | 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](https://docs.stripe.com/terminal.md) | Includes coverage for API actions specific to Terminal such as: - [token setup and activation](https://docs.stripe.com/api/terminal/connection_tokens/object.md) - [refund initiation](https://docs.stripe.com/api/terminal/readers/refund_payment.md) - [device attestation](https://docs.stripe.com/api/terminal/readers/object.md) - [payment intent processing](https://docs.stripe.com/api/errors.md) | | [Stripe Issuing](https://docs.stripe.com/issuing.md) | Alerts on request failures related to the [Issuing API](https://docs.stripe.com/api/issuing/authorizations.md) address the authentication, authorisation, creation, retrieval, and updates of Stripe-issued payment cards. | #### Error status codes for API error alerts | Error status code | Possible cause | | ----------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `402` | Indicates that the request contained valid parameters, but it failed due to issues with the financial transaction or payment method validation. | | `424` | Occurs when the request failed because the API request depended on a previous action and that previous action failed. | | `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 your end. Stripe always investigates `500` errors and notifies you when they’re resolved. | ### Payment method errors Elevated payment method errors indicate an increase in [payment declines](https://docs.stripe.com/declines.md) with the specified payment method. This might be due to a technical issue with the payment method, with the issuer, or with Stripe. Some payment methods, such as [ACH direct debit](https://docs.stripe.com/payments/ach-direct-debit.md), prevent confirmation of the payment status during a notification delay. A `processing` payment success status means that Stripe can’t yet confirm if the payment `failed` or `succeeded`. Learn more about [Immediate or delayed notifications](https://docs.stripe.com/payments/payment-methods.md#payment-notification). ## Advanced tier alert categories In addition to the alert categories in the Basic tier, customers in the Advanced tier will also receive the following alert categories: ### Increased integration errors These alerts monitor errors that impact payment capabilities in your integration including rate limiting issues. They notify you about issues with your Stripe integration that might affect your ability to process payments. Error status codes for increased integration error alerts include 400, 409 and 429. Learn more about [error codes](https://docs.stripe.com/error-codes.md) and how to resolve them. #### Error status codes for integration error alerts | Error status 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. | | `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 time frame, often due to rate-limiting. Elevated counts in this category might mean that a required parameter was omitted. | ### 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 Anomaly alerts use machine learning (ML) to detect sudden drops or changes in payment performance in near-real time. The following table describes different anomaly alert types. | Anomaly alert | Description | | ------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Card authorisation decline** | A sudden decline in [authorisation rates](https://docs.stripe.com/payments/analytics/acceptance.md), impacting overall payment success for cards. When available, these alerts also indicate the subsets of payment traffic that have degraded. For example, the alert might identify the specific card issuing bank or card type that’s impacted. See the [How to reduce network declines](https://stripe.com/guides/optimizing-authorization-rates#how-to-increase-authorization-rates) Stripe guide for actions you can take to try to increase authorisation rates. | | **Terminal authorisation decline** | A sudden decline in successful Terminal payments. These alerts proactively notify you when Stripe detects significant declines in payment approvals across your Terminal devices. These notifications cover all supported payment methods, including major card networks and local debit systems, and can help you identify and address processing issues. | | **Fraudulent transactions increase** (Private preview) | A sudden increase in [fraudulent transactions](https://docs.stripe.com/disputes/prevention.md), increasing the risk of losses. | | **Payment volume decline** (Private preview) | Alerts that use machine learning (ML) to notify users of declines in payment volume, while accounting for weekly fluctuations and seasonal variations. There could be multiple reasons for these declines, such as errors in your Stripe account configuration, scheduled maintenance for your website or mobile application, seasonal fluctuations in your business | ### Webhook latency alerts To minimise 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](https://docs.stripe.com/api/errors.md#errors-code). ### Issuing request timeouts (Private preview) Issuing request timeouts are generated for high timeout volume for [Stripe Issuing](https://docs.stripe.com/issuing.md) webhook authorisation requests. These authorisation requests notify your team to verify the settings for the [Issuing](https://dashboard.stripe.com/settings/issuing/authorizations) page in the Dashboard. To verify the settings, go to **Settings** > **Issuing** > **Authorisations** > **Approvals** in the Dashboard. ### Issuing errors (Private preview) For [Stripe Issuing](https://docs.stripe.com/issuing.md), we monitor webhook authorisation timeouts with your Issuing integration. We notify you when we see an increase in webhook timeouts for Issuing authorisation requests. ### Billing method errors (Private preview) Monitor billing method errors and Stripe’s [Usage-based billing](https://stripe.com/billing/usage-based-billing) errors. ## Generate test health alerts and insights You can generate test health alerts and insights from the Blueprints tab in Workbench. Test alerts appear in the Health tab, but don’t send email notifications. ## See also - [Workbench health alerts](https://docs.stripe.com/workbench/health.md) - [Stripe API error codes](https://docs.stripe.com/api/errors.md#errors-code)