Automated TrueLayer Failed Payment Alerts
Every hour, WebRun opens the TrueLayer payments dashboard, finds any open banking payment that failed, expired, or has been pending too long, posts the exception list to Telegram, and sends an SMS through Twilio when a high-value payment needs attention.
How do I know when a TrueLayer bank payment fails or gets stuck?
WebRun checks TrueLayer's open banking payments every hour, flags any payment that failed, expired, or has been stuck too long, and posts the list with payer, amount, and reason to Telegram. Payments above your threshold also trigger a Twilio text, so a stalled high-value bank payment never sits unnoticed.
- Failed or stuck payments get flagged within the hour
- High-value failures trigger an SMS so nothing big is missed
- Ops sees every failure reason grouped in one Telegram digest
Built for payments ops teams · fintech operations · ecommerce finance 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
truelayer.comin a real browser with your saved login - no setup, no API keys. -
1
TrueLayer - flag failed or stuck payments
WebRun opens TrueLayer to flag failed or stuck payments. - Open the TrueLayer payments dashboard and filter to failed, expired, or pending-too-long payments
- Capture the payer, amount, and failure reason for each one
- Separate payments over your high-value threshold from routine ones
Done when Every failed or stuck payment from the last hour is listed with its reason and amount.
-
2
Telegram - post the exception list to ops
WebRun posts to Telegram to alert ops. - Post the full exception list to the payments ops Telegram channel
- Group entries by failure reason so patterns are easy to spot
Done when Ops has this hour's failed-payment list in Telegram.
-
3
Twilio - text an alert for high-value failures
WebRun sends an SMS through Twilio for high-value failures. - Send a short SMS through Twilio only for payments over your high-value threshold
- Leave every routine failure in the Telegram digest only
Done when Only high-value failures generate an SMS; nothing is texted for routine ones.
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
How fast does it catch a failed payment?
Within the hour. WebRun checks the TrueLayer payments dashboard every hour and posts any failed or stuck payment to Telegram the same run it appears.
Will WebRun retry or resend a failed payment on its own?
No. WebRun only reports on failed or stuck payments it finds in TrueLayer. It never retries, resends, refunds, or moves money itself. Any retry stays queued for a human to trigger.
Why do some failures also send an SMS?
Payments over the threshold you set also get a Twilio text, so a stalled high-value bank payment never sits unnoticed in a channel nobody is watching.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.