Automated Adyen Payment Refusal Monitoring
Every hour, WebRun signs into Adyen, reads the payments refused in the last hour, groups them by refusal reason, payment method, and issuing country, compares the authorisation rate against your normal band, posts the breakdown to Microsoft Teams, and texts you when refusals spike.
How do I spot a spike in refused card payments quickly?
Every hour WebRun signs into Adyen, reads the payments refused in the last hour, and groups them by refusal reason, payment method, and issuing country. It compares the authorisation rate against your normal band, posts the breakdown to Microsoft Teams, and texts you through Twilio when refusals spike.
- A broken payment method is caught in an hour, not at month end
- Every alert names the refusal reason driving the jump
- Quiet hours stop triggering false alarms
Built for payments teams · ecommerce operators · fintech operations · revenue teams
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
ca-live.adyen.comin a real browser with your saved login - no setup, no API keys. -
1
Adyen - read the last hour of refusals
adyen.com
WebRun opens Adyen to read the last hour of refusals. - Sign into the Adyen Customer Area and filter payments to the last hour
- Capture every refused payment with its refusal reason, payment method, and issuing country
- Work out the authorisation rate for the hour and compare it against the same hour last week
Done when The hour's refusals are grouped by reason with an authorisation rate calculated.
-
2
Microsoft Teams - post the reason breakdown
microsoft.com
WebRun opens Microsoft Teams to post the reason breakdown. - Post the payments channel the hour's authorisation rate and the top refusal reasons
- Break the refusals down by payment method and issuing country
- Say plainly whether the rate is inside your normal band or outside it
Done when The hour's refusal breakdown is in Teams with the rate stated.
-
3
Twilio - text you when refusals spike
twilio.com
WebRun opens Twilio to text you when refusals spike. - Text the on-call owner when the refusal rate rises above your threshold
- Name the dominant refusal reason and the payment method behind the jump
- Never retry, capture, or refund a payment. WebRun reports and a person decides what to change
Done when The on-call owner has been texted about any spike above threshold.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it retry or refund any payments?
No. Retrying a charge or issuing a refund moves real money, so WebRun never does either. It reports the refusals and the reasons, and a person makes the call in Adyen.
Does it contact the shoppers whose payment failed?
No. Everything stays internal: a Teams post and a text to your on-call owner. No shopper is emailed or messaged from this run.
How does it know a rate is abnormal?
It compares each hour's authorisation rate against the same hour in previous weeks and against the threshold you set, so an ordinary quiet hour does not trigger an alert.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.