Automated Cantaloupe Cashless Payment Failure Detection
Every morning, WebRun opens Cantaloupe, pulls the prior day's cashless transaction data, calculates the decline rate per machine, flags any machine above your configured threshold, and posts the list to Slack so your team can inspect or replace a card reader before more sales are lost.
How do I automatically detect vending machines with cashless payment failures?
WebRun pulls the prior day's cashless payment data from Cantaloupe Seed Pro every morning, calculates each machine's decline rate, and posts a ranked list of problem machines to Slack. Your ops team sees which card readers need inspection before the issue quietly costs another day of sales.
- Card reader faults are caught daily instead of discovered by a driver on route
- Ops team gets a ranked list of problem machines each morning
- Lost cashless sales are minimized by faster intervention
Built for vending operators · cashless payment managers · route supervisors · convenience service operators
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.cantaloupe.com/products/software/seed-proin a real browser with your saved login - no setup, no API keys. -
1
Cantaloupe - pull cashless transaction decline rates
cantaloupe.com
WebRun opens Cantaloupe to pull cashless transaction decline rates. - Open Cantaloupe Seed Pro and navigate to the cashless payments or transaction report
- Filter to the prior business day's transactions
- Calculate the decline or failure rate for each machine
- Flag machines whose failure rate exceeds the threshold you configured (e.g. more than 10% of attempts)
Done when Every machine with an elevated cashless failure rate is listed with its rate and location.
-
2
Slack - post flagged machines to ops team
slack.com
WebRun opens Slack to post flagged machines to ops team. - Post the flagged machine list to your ops Slack channel
- Include machine ID, location, failure rate, and total failed transactions for each
- Sort by highest failure rate first so the worst offenders are visible immediately
Done when Ops team has a prioritized list of card reader problems in Slack.
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
What counts as a failure rate worth flagging?
You set the threshold when configuring WebRun. A common starting point is machines where more than 10% of cashless attempts declined or errored. Adjust higher or lower to match your fleet norms.
Does it contact the card processor or initiate any refunds?
No. WebRun only reads transaction data and posts an internal Slack alert. Any processor outreach or refunds are left for your team to handle.
Can it distinguish between a bank decline and a card reader hardware fault?
It surfaces the machine-level failure rate from Cantaloupe. Distinguishing hardware faults from bank declines requires your team to review the detail in Cantaloupe after the alert.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.