For telcos, fintechs & banks

See the fraud your competitors already confirmed.

Fraudsters reuse the same numbers, wallets and IDs across networks — and today each institution discovers them alone, one loss at a time. Adoor members share confirmed fraud signals on hashed identifiers, so the first confirmed report anywhere becomes protection everywhere.

Give-to-get — sustained access requires contributing confirmed reports

Network/Give to get
Live
First confirmed report01 / N
hashed · +233 55 ••• •221
Reported by · Fintech · GH
Network-wide effect
Telco
warned
Fintech
warned
Bank
warned
One report inprotectednetwork-wide
Why join

The fraudster's advantage is reuse. This ends it.

01
One loss per network, not per member

After the first member confirms a fraudster, every other member is warned on first contact. Cross-network reuse — the fraudster's biggest advantage — stops working.

02
Nothing to leak, nothing to fear

You share one-way keyed hashes, never raw customer data. Attribution is sector + country only — contributing never names your institution or advertises an incident.

03
Neutral by structure

Adoor is a private consortium platform, not a regulator: no enforcement power, no competing product, and give-to-get rules that apply equally to every member.

What membership includes

Everything you need to act on shared intelligence.

01
Real-time risk lookups

Score any identifier before onboarding or payout — allow / step-up / review / block with human-readable reasons. Engineered for p95 under 150 ms.

02
Confirmed-fraud reporting

Contribute validated fraud reports with evidence. Corroboration-weighted scoring means no single reporter can condemn an identifier alone.

03
Fraud-ring graphs

Entity resolution and ring detection across the whole network — including agent collusion patterns no single institution can see in its own data.

04
Exposure alerts & webhooks

Signed SFIX webhooks, SSE and polling. When an identifier you've transacted with is later confirmed fraudulent, you know within seconds.

05
Disputes & trust scoring

A built-in dispute workflow protects the innocent; reporter trust scores and anomaly monitors protect the pool from poisoning.

06
Compliance evidence

Append-only hash-chained audit, access-review exports, retention certificates — evidence your own auditors and regulators can sample.

Integration

Integration in three steps.

01/Keys & SDK
Get keys & the edge SDK

Scoped API keys plus the zero-dependency SDK — pip install adoor or npm i @adoor/sdk. It hashes identifiers inside your infrastructure (HMAC-SHA256 with the consortium pepper); raw values never leave. No engineers? The offline Edge Hasher runs entirely in a browser.

02/Two calls
Wire two calls

client.lookup(...) before money moves; client.report(...) when your team confirms fraud. Typed clients, RFC 7807 errors, idempotency keys, sandbox keys for staging.

03/Alerts
Subscribe to alerts

Register a webhook endpoint and receive signed exposure alerts, ring updates and dispute events — replay-protected, at-least-once.

Onboarding

From signed pilot to live decisions.

Request access → a design-partner pilot → your onboarding pack. Integration is deliberately small: two API calls, wired once.

Your onboarding pack
API key
sk_live_…

Authenticates your org. Scoped to lookups:read + reports:write.

Test key
sk_test_…

A non-production key for integration work. Scope and protect it like a live key.

Consortium pepper
versioned

The shared secret that keys your edge hash so it joins the network's.

Webhook secret
X-Adoor-Signature

Verifies signed exposure-alert callbacks.

Every secret lives in your secrets manager — never in source, never in a browser.

How/The pepper

You hash each identifier at your edge with the consortium pepper — h1 = HMAC(pepper, normalize(id)). The platform then applies a second, platform-only pepper server-side to form the stored join key. Your raw values never leave your systems, and the central pepper never leaves ours.

Why/One hash, every on-ramp

The Python SDK, the TypeScript SDK, the offline Edge Hasher and the server share one hashing implementation, proven byte-identical by a parity suite. Pick any on-ramp — the same identifier yields the same value_hash, so your hashes join everyone else's on the network.

Membership

Priced per institution, not per seat.

Indicative structure — commercial terms are agreed per institution during the design-partner pilot. Every tier follows give-to-get: sustained lookup access requires contributing confirmed reports.

Design partner
Pilot terms
Recommended
  • Full API access during the pilot
  • Direct line to the engineering team
  • Shape the ruleset and data standards
  • Founding-member pricing at graduation
Member
Annual + usage
  • Real-time lookups & reporting
  • Exposure alerts & webhooks
  • Ring graphs & network intelligence
  • Dispute workflow & compliance exports
Enterprise
Custom
  • mTLS, IP allowlisting, SSO
  • In-region hosting options
  • Custom retention & DPA terms
  • Dedicated support & SLAs