Flag the Stripe customers who weaponize chargebacks and support.
BoonRadar is a crowdsourced ledger of high-risk buyers. SaaS and commerce founders contribute incidents, we verify evidence, and everyone in the network gets early warning signals before accepting new business.
How the network works
Every report moves through a structured review pipeline so founders can rely on the signal.
Evidence-backed incidents only
Merchants share Stripe dispute IDs, support transcripts, refund history, and internal notes. We require attestations that the submitter has a direct commercial relationship.
Analyst review within two business days
Our trust & safety reviewers validate documents, normalize amounts, and redact personal information. Reports that fail review are removed before reaching the shared feed.
Signal routed to the community
Verified incidents are indexed by email, Stripe customer ID, domain, and company metadata. Members receive automated alerts when a risky buyer overlaps with their CRM or checkout traffic.
Why merchants contribute
Protect revenue
Identify serial refunders and card testers before they impact margins or tie up your support team.
Reciprocal access
Verified contributors unlock the full corpus, CSV exports, and webhook notifications for internal tooling.
Legal guardrails
We operate with US counsel, follow strict evidence requirements, and give flagged parties an auditable dispute channel.
Governance & compliance
Data minimization
We store hashed identifiers, dispute metadata, and business descriptors. Personal consumer data is redacted or encrypted at rest.
Right to respond
Flagged customers can submit appeals with supporting context. Analysts document every decision and notify all contributors tied to the record.
Fair Credit Reporting posture
BoonRadar is not a credit bureau. Access is limited to merchants evaluating transaction risk with existing or prospective customers.
Common questions
Who can join the beta?
Bootstrapped SaaS founders, subscription commerce teams, and marketplaces processing volume through Stripe. We prioritize operators who will both contribute reports and consume the data.
What evidence is required?
At minimum: Stripe dispute screenshots or refund logs, support transcripts, and proof of service delivery. Submissions without documentation are rejected.
How is sensitive information handled?
We hash personal identifiers, strip card numbers, and encrypt raw evidence. Only summarized metadata is shared with the network.
Can reports be removed?
Yes. Verified counter-evidence or policy violations trigger immediate takedown and notify affected merchants.
Ready to help build the shared fraud ledger?
Join founders pooling their data to stop repeat abusers. Your first verified submission unlocks reciprocal intelligence.