Compliance decision layer

One API.
Every risk signal.
Your rules.

Blockchain, wallet, IP, device, email and card risk — in a single request. You set the rules and thresholds; PilotChain collects signals from multiple providers and returns one explainable risk decision.

No separate integration with every data provider

Signals from independent providers — in one API response

  • Blockchain analytics
  • Sanctions & watchlists
  • IP intelligence
  • Device intelligence
  • Email risk
  • Card intelligence
  • risk signal types in one API
  • data providers under the hood
  • explainable decision: allow · review · block

A new check is added as a rule in your bundle — no integration changes needed.

Problem

Plenty of data.A single decision — none.

A blockchain provider sees the wallet, not the device. Device intelligence sees the device, not where the crypto came from. An IP service knows the location but nothing about the transaction.

01

6 signals → 6 integrations

Several APIs, dashboards, response formats and contracts. Your compliance team stitches them into one decision by hand.

02

Every provider speaks its own language

Different scales, categories and risk labels are hard to fit into one decision logic.

03

The decision is hard to explain to an auditor

A single risk score isn’t enough. You need a transparent log: which rule fired, which signal triggered it and why.

How it works

Your rules. Our data and infrastructure.

You define what risk means for your business. PilotChain pulls data from the right providers, normalizes the signals and applies your risk policy.

01

Rules · Weights · Thresholds

Your policy

Scenarios for deposit, withdrawal, payment, onboarding and other risk flows.

02

Routing · Normalization · Decisioning

PilotChain

We collect the signals you need and apply your logic.

03

Allow · Review · Block

One decision

Risk score, each rule’s contribution and a full audit trail.

Rule Lab

Tune your risk policy without a release or a developer queue.

Editing

Change signal weights and the threshold — and instantly see how the new policy affects the decision. No new API release for every tweak.

+30
+22
+15
+8
62

Policy result

/100

threshold 62exceeded by 13

Decision

Review

Explainability

Every decision can be explained.

Not just “Risk Score: 75”. PilotChain shows which rule fired, which signal triggered it and why the transaction went to review.

A ready-made audit trail for compliance review

Request pc_82a9f

Risk 75
  • +30

    Sanctions exposure

    Address is linked to a risk entity within the configured depth

    RULE_01
  • +22

    High-risk service

    Provider signal matched a policy category

    RULE_07
  • +15

    IP / country mismatch

    IP country differs from the customer profile

    RULE_12
Threshold ≥ 62exceeded by 13 — decision: REVIEW
Checks

Add new risk signals without a new integration.

Today you need blockchain AML. Tomorrow — IP and device risk. Next month — card intelligence. The PilotChain API stays the same.

Wallet

Wallet screening, exposure, entity links

WALLET_SCREENING

Transaction

Blockchain transaction risk context

TRANSACTION_SCREENING

IP

Geolocation, network and risk signals

IP_SCREENING

Device

Fingerprint and behavioral anomalies

DEVICE_SCREENING

Email

Identity and abuse-related signals

MAIL_SCREENING

Card

Payment card risk intelligence

CARD_SCREENING
Data providers

Several independent sources. One contract — with us.

PilotChain is already integrated with data providers. You don’t have to sign a contract with each of them, pay six invoices or maintain six integrations.

Request pc_82a9f

6 sources · in parallel
  • Blockchain analytics

    Provider A

    182 msResponse
  • Blockchain analytics

    Provider B

    240 msCross-check
  • Sanctions & watchlists

    Provider C

    95 msResponse
  • IP intelligence

    Provider D → E

    131 msFallback
  • Device intelligence

    Provider F

    88 msResponse
  • Email risk

    Provider G

    74 msResponse
11 signals → policy “PSP transaction”Review

Example. Providers and latencies are illustrative.

01

Vendor-neutral

Not tied to a single source. We compare data quality and switch providers with no changes on your side.

02

Cross-checking

Critical signals — sanctions exposure, for example — are verified across several sources.

03

Fallback without downtime

If a provider doesn’t respond, the request goes to a backup source. You still get a decision.

Use cases

One decision layer for different risk scenarios.

01

Crypto exchanges

Screen deposits and withdrawals against blockchain risk, IP, device and customer signals at once.

Starter bundle

  • address
  • transaction
  • device
02

PSP & crypto merchants

Decide on a payment based on card, wallet, IP, email and device risk in a single policy.

Starter bundle

  • card
  • IP
  • device
  • address
03

On / off-ramp

Link fiat → crypto → payout into one risk logic with a clear decision trail.

Starter bundle

  • card
  • IP
  • address
  • mail
04

OTC desks

Check the counterparty and source of funds before the deal and keep an explainable log.

Starter bundle

  • address
  • transaction
  • details
For developers

One integration instead of six.

REST API, webhooks and a sandbox. One request returns the decision, score and decision log. New checks are added as rules in the bundle — no code changes.

  • 1 · Get a sandbox key in MerchantDesk
  • 2 · Send POST /v1/screen with the data you have
  • 3 · Receive the decision in the response or via webhook
Documentation
screen.http
POST /v1/screen
{
  "scenario": "deposit",
  "wallet": { "address": "bc1q…7xk", "network": "BTC" },
  "ip": "185.23.44.10",
  "device_id": "dv_91f3"
}

// 200 OK · 412 ms
{
  "decision": "REVIEW",
  "risk_score": 75, "threshold": 62,
  "rules": [
    { "id": "RULE_01", "signal": "sanctions_exposure", "points": 30 },
    { "id": "RULE_12", "signal": "ip_country_mismatch", "points": 15 }
  ],
  "request_id": "pc_82a9f"
}
Get a sandbox key
Security

Ready for review by your auditor, partner bank and regulator.

Every decision is reproducible and every team action is logged. Due diligence documents are available on request.

Full audit log

Decisions and changes to policies, keys and access — with author and timestamp.

Roles and access

Who sees requests, who changes the policy, who manages keys.

Key isolation

Separate sandbox and production keys, rotation and revocation.

Data minimization

Providers only receive the fields a specific check needs.

Pricing

Pay for checks. Not for six separate platforms.

One invoice

One API. One contract. One invoice. Multiple risk intelligence sources.

Start with one scenario and add checks as you grow — without rebuilding your whole compliance infrastructure.

Start

Launch without an enterprise project.

We build your first working risk flow around your real scenario.

  • One API
  • Your risk policy
  • Multiple data sources
  • Explainable decision
FAQ

Frequently asked questions

Didn’t find an answer? Write to us — we reply within one business day.

Ask a question

They are data sources. PilotChain is the decision layer on top of them: it connects several providers, brings signals to one scale and applies your risk policy.

No. PilotChain is already integrated with providers: you sign one contract with us and get one invoice.

You do. Your compliance team tunes signal weights and thresholds in Rule Lab for every scenario — no releases, no developer queue.

We build the first working risk flow in a single working session. Integration is one POST request, and you get a sandbox key right away.

It depends on the set of checks in the scenario and your volume. You pay for checks, not for separate platforms — write to us and we’ll estimate it for your flow.

A full decision log for every request: which rules fired, which signals triggered them and which policy version was applied, plus a team activity log with author and timestamp.

30-minute working session

Show us one real transaction.

In one working session we’ll go through the signals, tune weights and thresholds and build a risk policy for your process. You’ll leave with a working configuration, not a sales deck.

Build my risk policy

Sandbox key and documentation — on request during the call.