The decision layer between your product and risk data.
PilotChain takes the request, queries the right providers, brings their responses to one scale and applies your risk policy. The output is one decision with an explanation.
Your product
POST /v1/screen
- wallet
- ip
- device
PilotChain · one request
≈ 412 ms- 01Intake1 endpoint
- 02Routing6 providers
- 03Normalization11 signals
- 04Decisionpolicy v14
Blockchain · Sanctions · IP · Device · Email · Card
- Allow
- Review · 75
- Block
Four stages inside one request.
Everything that used to take six integrations and a compliance analyst’s manual work happens in a single API call.
Request pc_82a9f
412 ms- 010 ms
Request intake
POST /v1/screen · scenario: deposit
- 02+ 240 ms
Routing
4 providers · in parallel · 1 fallback
- 03+ 18 ms
Normalization
11 signals → one scale
- 04+ 6 ms
Decisioning
policy “Crypto deposit” v14 · 4 rules
Request intake
One endpoint for any check: address, transaction, IP, device, email, card. Send only the fields you have.
POST /v1/screenRouting
Based on the bundle and scenario, PilotChain picks providers and queries them in parallel. If a source doesn’t respond, fallback kicks in.
ROUTINGNormalization
Different scales, categories and risk labels are mapped to one signal format your rules work with.
NORMALIZATIONDecision
Your policy’s rules, weights and thresholds return allow, review or block — with each signal’s contribution.
DECISIONINGComparison
In-house or with PilotChain.
The same task — building one decision from several risk sources. The difference is who carries the complexity.
In-house
- 6 contracts and 6 invoices
- 6 response formats and 6 scales
- Risk logic hard-coded
- Risk score without explanation
- New check = new integration
With PilotChain
- 1 contract and 1 invoice
- One signal format
- Policy in Rule Lab — no release
- Audit trail for every rule
- New check = a rule in the bundle
Decision, score and reason — in one JSON.
Your system doesn’t need to interpret someone else’s risk labels. The response already contains the outcome, each rule’s contribution and a link to the full decision log.
- decision — allow · review · block
- risk_score — the total on your 0–100 scale
- rules[] — which rules fired and how much they added
- signals[] — normalized provider signals
- request_id — link to the request in MerchantDesk
{
"decision": "REVIEW",
"risk_score": 75, "threshold": 62,
"policy": "crypto_deposit@v14",
"rules": [
{ "id": "RULE_01", "points": 30 },
{ "id": "RULE_07", "points": 22 },
{ "id": "RULE_12", "points": 15 },
{ "id": "RULE_19", "points": 8 }
],
"signals": [ … 11 items ],
"request_id": "pc_82a9f"
}
Infrastructure
What usually takes months to build — already inside.
Parallel querying
Providers are queried at the same time, not one after another.
Fallback
An unavailable source is replaced by a backup with no error on your side.
Webhooks
Asynchronous checks and delivery history for every webhook.
Recurring checks
Background re-screening of addresses — within your limits.