Set alerts so a spike in payment declines never surprises you again
When a gateway underperforms, an issuer tightens its rules, or a new market starts acting up, your authorization rate can slip without anyone noticing. If your team relies on end-of-month finance reports to spot these issues, you're reacting too late. This recipe shows you how to build real-time monitors in Chargebee Reveal: the payments intelligence layer for your stack. It instantly catches warning signals that could harm your payment health and lands them straight to your Slack.
Catch every revenue leak,
the moment it starts
Let payment issues find you, not the other way around. Once set up, you don't need to stare at a dashboard all day. If your decline rate crosses your threshold, Chargebee Reveal pings Slack right away with the exact metrics, affected segment, and suggested fixes. Here's what your team gets, the instant it fires:
The cost of a payment leak is measured in time-to-notice
A decline spike that runs for three weeks before anyone spots it is three weeks of lost renewals you'll never get back. The fix is rarely the hard part. Finding out quickly is. Alerts turn "we noticed in the quarterly review" into "we caught it before lunch."
The gap between a leak starting and you noticing is pure lost revenue. Alerts close that gap to near-zero, so problems surface while they're still small.
Nobody has to sit and stare at a chart. Reveal watches every metric for you and only speaks up when something's wrong, in the channel your team already lives in.
Each alert carries the metric, the segment, and the deviation, so whoever gets it can act without a five-tab investigation first.
What you need on the counter
Alerts sit on top of your payments data, so a little prep up front makes the build smooth. Here's the short list to have ready before Step 1.
Read-only API keys for the gateways you run, you'll plug these in at Step 1. Connect guides: Stripe, Adyen, Braintree, PayPal, Cybersource, Shopify Payments.
One number worth watching, decline rate, auth rate, refunds. The full metrics list is in the step below.
The channel or people who should hear the alert, plus their handles. Reveal delivers over Slack.
Build your first alert, end to end
We'll start from a blank slate, no data connected yet, and go all the way to a live monitor firing in Slack. First you connect your gateways and let the data populate, then the alert builder walks you through four screens: Select, Configure, Describe, and Communicate. We'll build one real alert, "tell me when USD decline rate spikes," with the pro moves along the way.
Connect gateway API keys on Reveal
The first step is to plug in your gateways with read-only API keys. It's five clicks, no engineering, and no writing access to your accounts. Head to Sources, hit Add source, and follow the guide for each gateway you run.
- Add each gateway from Sources › Add source using read-only keys
- Step-by-step connect guides: Stripe, Adyen, Braintree, PayPal, Cybersource, Shopify Payments
- If you use more than one gateway, connect all your gateways, the cross-stack view is where the real leaks show up
Let your payments data populate
Once your gateways are connected, Chargebee Reveal pulls in and processes your transaction history. Your latest transaction data starts loading instantly but ideally give it roughly 24 hours, so you can leverage all the data of past six months. This is a one-time wait, and then the dataset stays current automatically.
- Reveal ingests your last ~6 months of transaction history
- Typical wait is around 24 hours, larger datasets take a little longer
- You'll get an intimation when your full data is reflected on Reveal
Open Alerts and choose the alert type
In the left nav, go to Alerts and hit Create. Reveal's alert builder opens on the first of its three tabs, Choose. Here you pick between the two kinds of monitor. This one decision shapes everything after it, so it's worth understanding both.
- Threshold-based fires when a metric crosses a fixed line you set, e.g. decline rate
above 20% - Range-based fires when a metric strays outside its normal band, great for catching anomalies you can't hand-pick a number for
- Give the alert a clear title up top, you'll thank yourself when you have twenty of them
Build the condition for the alert,
one plain-English sentence
This is the heart of the recipe. Reveal turns the whole condition into a fill-in-the-blanks sentence, so you're not writing rules, you're reading one. For our example: trigger when Decline Rate by transactions for USD is greater than 20% over the past 6 hours.
- Pick the metric (see the full list of metrics just below this section)
- Add optional filters:
currency,processor,payment method,country,card scheme - Set the condition and threshold, e.g.
greater than 20% - Choose the time window, past N
hoursordays, and your time zone
Send it where your team already looks
The last screen decides who hears about it and where. Route the alert to Slack, pick the channel, and add the handles of the people who should be on it. Hit 'Save', and Reveal starts watching. That's the whole build.
- Choose the Slack channel to notify
- Add the recipients or channel who should get it
- Hit save, the monitor is now live and checking in real time
- Manage every alert from the Alerts list: status, type, and the configured value at a glance
Metrics worth putting an alert on
Any metric Reveal computes can carry an alert. These are the ones most teams start with, grouped by what they protect. The complete list lives in the metrics reference.
Revenue health
Leak detection
Top line
Risk signal
Risk signal
Recovery health
Every metric can be sliced further with the optional filters, currency, processor, payment method, country, and card scheme, so you can watch "US debit decline rate on one processor" rather than a blended number that hides the pocket. See how these read in decline-rate analysis and authorization-rate analysis.
Two ways to say “tell me when this is wrong”
Most first alerts should be threshold-based, they're simple and predictable. Reach for range-based once you know a metric's normal rhythm and want to catch anything unusual without hand-picking a number. Here's how each behaves.
You set the number. The alert fires the moment the metric goes past it. Predictable and easy to reason about.
You set an upper and lower bound. The alert fires when the metric drifts outside its usual range. Best for catching anomalies.
Put a watch on your payments, before the next surprise.
Connect your gateways, pick one metric that matters, and build your first alert in about ten minutes. Reveal runs the audit for free, so you'll also see the leaks that are worth alerting on in the first place.