Automated Interswitch Failed Transaction Alerts
Every hour, WebRun opens the Interswitch merchant dashboard, checks for failed and declined transactions, logs each one in Airtable with the amount and failure reason, and emails your ops team a short summary so nothing sits unnoticed until the end of day.
How do I get alerted about failed Interswitch transactions?
WebRun checks your Interswitch merchant dashboard every hour for failed and declined transactions, logs each one in Airtable with its amount and failure reason, and emails your ops team a summary. It never retries a payment or moves money itself, so declines get noticed and explained within the hour instead of at month end.
- Failed transactions get logged and explained within the hour
- Decline reasons are tracked in one place instead of scattered logs
- Ops gets an emailed summary instead of digging through the dashboard
Built for merchants using Interswitch · payments operations · ecommerce finance teams · fintech ops 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
www.interswitch.comin a real browser with your saved login - no setup, no API keys. -
1
Interswitch - check failed transactions
- Open the Interswitch merchant dashboard and pull the latest transactions
- Filter to failed and declined transactions
- Capture the amount, timestamp, and failure reason for each
Done when Every failed or declined transaction this hour is captured with its reason.
-
2
Airtable - log each failure
airtable.com
WebRun opens Airtable to log each failure. - Add a row for each newly failed transaction
- Include the amount, timestamp, and failure reason
- Skip any transaction already logged from a prior run
Done when The Airtable base lists every failed transaction with its reason.
-
3
Gmail - email the ops summary
gmail.com
WebRun emails the ops summary through Gmail. - Email your ops team a short summary of this hour's failures
- Group the count by failure reason
- Send only when there is at least one new failure to report
Done when Your ops team has an emailed summary of this hour's failed transactions.
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 WebRun retry a failed payment or move money to fix it?
No. WebRun never sends a payment, issues a refund, or transfers funds on its own. It only reads transaction status, logs failures, and reports them, leaving any retry or fix for you to make.
Does it log the same failure more than once?
No. It checks the Airtable base before adding a row, so a transaction already logged in an earlier hour is skipped.
What counts as a failed transaction?
Any transaction the Interswitch dashboard marks as failed or declined, including the reason it gives, so the pattern behind repeated failures is easy to spot.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.