Security and privacy decision
ByeDispute
A competent developer can build a narrow self-hosted replacement that catches common patterns and issues refunds/alerts, but reproducing the vendor's tuned heuristics, polished no-code onboarding, dashboard, and ongoing fraud pattern updates is nontrivial — so keep paying for full coverage unless you only need a basic rule-based guard.
Visit website↗Built by Marc Lou, who ships 32 products in this index
$69/mo
$828/yr
Read off the official pricing page.
$100one-off60 h to build
$30/mo6 h/mo upkeep
On cash alone, building overtakes the subscription at 1 seat.
No open-source build does this yet
Nothing published replaces this one, so a replacement starts from an empty file. Here is what it would have to cover.
What a replacement has to do
- Listen to Stripe webhooks, evaluate payments against fraud patterns, and run configured actions (email alerts, refunds) to prevent disputes.
What it still won’t have
- Years of tuned fraud-detection heuristics and edge patterns the vendor claims
- Polished no-code onboarding and pre-built rule templates
- Hosted dashboard with integrated alerting and linked Stripe payment views
- Ongoing product support, monitoring, and updates from the vendor
What remains hard
- Product polish and ongoing maintenance
First-year cost
Keep paying
Paying is—cheaper in year one.
On cash alone, building overtakes the subscription at 1 seat.
Money you would actually spend
Time you would spend
—
What you would spend
What we assumed
The verdict above measures whether you could build it. This one is only about money.
Runnable build prompt
Build a minimal self-hosted Stripe chargeback protection service using Node.js (Express) + PostgreSQL + Sequelize, deployed to a small cloud VM (e.g., DigitalOcean) behind nginx. Core features in scope: (1) secure Stripe webhook receiver with signature verification; (2) rule engine supporting a small set of configurable heuristics (disposable-email detection via public list or simple regex, early fraud warning events, unusually high chargeback rate per account); (3) action runners to (a) create a refund via the Stripe API and (b) send email alerts via SendGrid; (4) simple admin UI (React) to create/edit rules, view recent alerts, and display consumption (protected transactions); (5) usage metering that decrements a transaction credit counter in Postgres and exposes a monthly quota endpoint. Out of scope: machine-learning model training, multi-tenant billing, marketplace integrations, mobile apps. Require input validation, retries and idempotency for webhook handling, audit logs for actions, basic unit and integration tests (webhook handler, rule evaluation, refund action), and Dockerfiles for service and UI.
How we checked
How the score was reached
- Partly verdict base52
- 2 cited sources+1
- Price verified on pricing page+3
- Evidence score56
The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.
How scoring works →Cited sources · 2
Every page the run actually retrieved.
- official productByeDispute homepage
- official pricingByeDispute pricing section
Integrity checks
What held up, and what did not.
