Alerts
Alerts is the first page under the Observability section of your Pagos Service Panel. It provides you with a daily health check for your payment processing strategy—no manual setup required.
Navigating the Alerts Section
Navigate to Alerts
Click Alerts under Observability in the main navigation.
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 - Not Available
Grey - Not Available
Grey bars indicate days for which data is not available:
- If a historical date is grey, we didn’t evaluate your data that day for anomalies
- If the most recent date is grey, we may still be processing your incoming data.
- For chargeback metrics, grey can also indicate your chargebacks volume on that date was too low to meet the required threshold.
Green - No New Issues
Green - No New Issues
Green bars indicate no new anomalies were detected that day—your data was consistent with historical measurements.
Green bars following a red one don’t necessarily mean the issue is resolved—our system doesn’t track whether anomalies persist. You should use Visualizations to monitor the metric’s behavior after an alert.
Red - Alert
Red - Alert
Red bars indicate an alert—we have registered an anomaly in your payments data. Where you see red, you may have a problem worth digging into.
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.
Your data connection type determines when Pagos receives and reviews segments of your data for anomalies:
- Direct, no-code data connections (e.g. Braintree, Stripe, Adyen) 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, your dashboard updates continuously.
- File-based connections (e.g. JP Morgan Chase, WorldPay Vantiv) - Alerts appear in the dashboard after Pagos receives and processes your files. To ensure data completeness, this can take up to three days. 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 three days later, after 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
Approval Rate
Approval Rate
The percentage of transactions processed that were ultimately approved, calculated by dividing by the total number of approved transactions by the total number of attempted transactions
Attempted Transaction Count
Attempted Transaction Count
The total number of attempted transactions
Decline Code Rate
Decline Code Rate
The percentage of total attempted transactions declined with a specific decline code; calculated by dividing the total number of declines with that decline code by the total number of attempted transactions
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
Refund Metrics
Refund Count
Refund Count
The total number of refunded transactions
Chargeback Metrics
Chargeback Count
Chargeback Count
The total number of disputed card-based transactions
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.
Export Options
Alerts is a starting point for identifying areas of concern in your payments data. To continue your analysis, you can seamlessly navigate to another area of the Pagos Service Panel and view the same data from a different angle. To do so, click Export in the top-right corner of your focus graph, then select from the following options under Open with:
Metrics
Metrics
Charts
Charts
Open Charts with a custom visualization of the exact same data in your Alerts focus graph. Charts has more features for data manipulation, including additional filter options and chart styles. Save your chart for future use, so you can continue to monitor this concerning data segment.
Events
Events
Open the Events page to view the exact transaction events behind the data in your focus chart.
If you focus the Alerts graph on any particular data segment, those filters will carry over to any of the Open with… options.
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 doesn’t automatically monitor every segment of your business—only those 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
- Card type
- BIN
- Issuing country
- MID