One question, asked at four moments
Has anyone else already caught this person doing one of a fixed list of things? A member asks it when it is about to extend trust, and gets back reason codes and dates, never a name.
Before the welcome offer
The signup bonus is the cheapest thing a ring farms. A hit here costs the operator nothing and the ring its reason to exist.
Before money moves
Payment fingerprints and verified phones survive the device and email rotation that defeats a single operator's checks.
Before cash leaves
The last chance to apply a record, and the one where the stakes for the operator are highest.
When something looks wrong
A fraud team with a suspicion can ask whether the same identifiers already carry a confirmed record elsewhere.
Why it is built this way
Query, never dump
Members ask about one hashed identifier at a time. Nobody can list, export or reverse the store. A member whose query volume looks like enumeration is cut off.
Each member decides alone
A hit is information. What to do with it is each operator's own written policy, and members never see or align each other's policies.
Fixed codes, with evidence
Eight reason codes, each with a minimum evidence standard and an expiry. A member files only what it has itself closed an account for, never a suspicion.
A dispute path from day one
A person can dispute a record through the neutral operator. The filing member has 30 days to confirm its evidence or the record is withdrawn.
There is no code for skill. Winning, being limited, or being good at this is not fraud, and the member agreement forbids ever adding a code for it.
Who it is for
Pick'em and daily fantasy operators too small to build this alone. The rings that hit one small operator hit the next one the same week, and today nobody warns anybody.
The exchange is being formed now. It starts as a bilateral pilot between operators that each have a named fraud contact and a ring they have already caught, and grows from there. Read what the pilot asks of a founding member.