1

Navigate to Alerts

Click Alerts under Observability in the main navigation.

2

Review Alerts at a glance

The Alerts page is broken into sections for each key payment metric. Each section contains a visual representation of the last 90 days, with each day (see timezone information below) demonstrated by a grey, green, or red bar:

  • Grey bars indicate historical dates we didn’t evaluate for anomalies; if the most recent date is grey, we may still be processing your incoming data. For chargeback metrics, grey can also indicate you didn’t see enough chargebacks on that date to meet the required threshold.

  • Green bars identify the days when your data was consistent with historical measurements.

  • Red bars alert you to the days when we have registered an anomaly in your payments data. Where you see red, you may have a problem worth digging into.

3

Dig into the data

Under a chosen metric, click the bar for a given day. This opens an Alerts Metric Details page containing the following data visualizations focused on that date:

​
Alert Notifications

When an anomaly occurs in your data and generates an alert, you can receive a notification in the Pagos Service Panel, via email, or even in a Slack channel. Learn how to configure these notifications in the Managing Your Pagos Account guide.

​
Alert Timing

A “day” in the Alerts section is measured as 12:00AM - 11:59PM UTC. If your account is set to a different time zone, the exact measurements shown for a specific day in Alerts may not match what you see for that same day in other charts within the Pagos Service Panel.

Additionally, your data connections determine when Pagos receives and reviews segments of your data for anomalies:

  • Direct, no-code data connections (e.g. Braintree, Stripe, Adyen, etc.) and the Data Ingestion API - We begin reviewing your data from the previous day at approximately 2AM UTC; as we receive and process more data segments, this dashboard will continuously update
  • File-based connections (e.g. JP Morgan Chase, WorldPay Vantiv, etc.) - These files typically arrive later, so alerts may take up to two days to appear; while we review the data, the bar for that day will appear grey.

If you use both direct and file-based data connections, we process and review data segments from your direct connections for anomalies first. Both the day’s bar color and the monitored segments list will populate according to this initial data. Up to two days later, when we’ve processed and reviewed segments from your file-based data connections, the monitored segments for that day—and potentially the corresponding color—will update.

​
Alert Metrics

Identify at a glance when your business experienced unexpected and abnormal changes to the following key payment metrics:

​
Transaction Metrics

To ensure your transaction alerts are based on reliable data, they don’t activate until you meet the following thresholds:

  • Have a history of 45 days of transaction data in your Pagos account
  • Processed a minimum transaction count of ≥100 transactions per day or per hour—depending on the alert type—on at least 75% of those days

​
Chargeback Metrics

To ensure your chargeback alerts are based on reliable data, they don’t activate until you meet the following thresholds:

  • Have a history of 45 days of chargeback data in your Pagos account
  • Received a minimum chargeback count of ≥10 chargebacks per day on at least 50% of those days

​
Focus graph

The first visual on the Alerts Metric Details page is a focus graph. This graph demonstrates the chosen metric over the course of a week for your entire transaction volume, with the focus date in the middle of the week. This provides context on how that focus day measures up against the surrounding days.

For count or value metrics (e.g. attempted transaction count), this will be a bar graph; rate metrics (e.g. approval rate) will appear as line graphs.

If you click the Focus icon for any particular segment in the Alerting Segments or Monitored Segments sections, this graph will change to only show the data for the chosen segment over that same week.

​
Alerting Segments

An anomaly alert for one of your metrics doesn’t always mean there’s been a widespread issue across all of your transaction volume. More often, it indicates specific segments of your business have experienced unexpected changes significant enough to trigger the alert. The Alerting Segments section identifies the exact segment(s) of your business for which the data anomaly is closely tied. Hover over the segment name to reveal a Focus icon; click this icon to change the focus graph to only show data for that particular segment.

With this information, you can filter other charts and graphs in Visualizations (e.g. Metrics, Charts, etc.) by this segment to dig further into the root cause of this sudden change.

For a full list of the segments Alerts monitors for anomalies, see the next section below.

For Decline Code Rate alerts, the alerting segment will identify both the segment(s) of transactions impacted and the exact decline code observed.

​
Monitored Segments

At the bottom of the Alerts Metric Details page, you’ll find a Monitored Segments table listing all the business segments Pagos monitors for anomalies, along with a status of either Issue or No New Issues. Hover over a segment name in this table to reveal a Focus icon. Click this icon to change the focus graph to only show data for that segment.

Pagos automatically monitors the segments of your business with the highest historical transaction counts. To ensure we’re always keeping up with ongoing changes in your own operations, we re-evaluate which of your business segments we automatically monitor on a weekly basis.

We identify a segment by filtering for all transactions associated with a single parameter within one of the following data filters:

  • Processor

  • Payment method

  • Stored credential

  • Card brand

  • Issuing country