Spot the customers who charge back again and again
Every Monday, WebRun reads your chargeback history in Chargeflow, groups disputes by customer, cross-checks each buyer's charge and refund history in Stripe, and builds a repeat-offender watchlist in Google Sheets, proposing blocklist candidates for you to approve rather than blocking anyone on its own.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I identify customers who repeatedly file chargebacks?
WebRun finds your repeat chargeback abusers every Monday. It groups disputes by customer in Chargeflow, cross-checks each buyer's charge and refund history in Stripe to separate friendly fraud from genuine issues, and builds a repeat-offender watchlist in Google Sheets with blocklist candidates for you to approve, so no legitimate customer is ever blocked automatically.
- Repeat abusers are caught across orders, not one at a time
- Genuine one-off disputes stay off the blocklist
- Blocking decisions stay with a human, never automatic
Built for ecommerce merchants · risk teams · Stripe sellers · fraud analysts
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
app.chargeflow.ioin a real browser with your saved login - no setup, no API keys. -
1
Chargeflow - group disputes by customer
chargeflow.io How to Automate Chargeflow
WebRun opens Chargeflow to group disputes by customer. - Open Chargeflow and pull disputes over a rolling window
- Group them by customer email, name, and card fingerprint
- Count repeat disputers and note their reason codes and amounts
Done when Customers with more than one chargeback are identified with their counts.
-
2
Stripe - check each payment history
stripe.com How to Automate Stripe
WebRun opens Stripe to check each payment history. - Look up each repeat disputer's customer record in Stripe
- Read their total charges, refunds, prior disputes, and payment risk signals
- Separate genuine friendly fraud from a one-off delivery problem
Done when Each repeat disputer has their payment history and context attached.
-
3
Google Sheets - build the watchlist
google.com How to Automate Google Sheets
WebRun opens Google Sheets to build the watchlist. - Write a watchlist row per repeat customer with dispute count and value
- Mark clear repeat abusers as blocklist candidates for review
- Leave blocking to a human, WebRun only proposes, it does not block anyone
Done when The watchlist is updated and blocklist candidates are proposed for approval.
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 block customers automatically?
No. WebRun only builds a watchlist and proposes blocklist candidates in the sheet. Blocking a buyer is a business call, so a person reviews and decides, and no customer is blocked by the automation.
How does it tell friendly fraud from a real problem?
It cross-checks each repeat disputer's Stripe history, charges, refunds, and prior disputes, so a customer with one genuine delivery issue is separated from someone who repeatedly disputes valid, delivered orders.
What counts as a repeat offender?
Anyone with more than one chargeback over the window you set. WebRun groups disputes by email, name, and card fingerprint so the same buyer is caught even across slightly different order details.
Related templates
Shopify›Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.