Platform · KYT
Wallet risk scoring, counterparty attribution, exposure tracing, and rule-based transaction monitoring that ties a blockchain transfer back to the verified customer who made it.
curl -X POST https://api.verifix.ae/v1/transactions/screen \
-H "Authorization: Bearer $VERIFIX_KEY" \
-d '{
"customer_id": "cus_2LX...",
"direction": "inbound",
"asset": "BTC",
"amount": "1.482",
"counterparty_address": "bc1q...7f4a"
}'
{
"decision": "escalate",
"wallet_risk": 78,
"exposure": [
{ "category": "sanctioned_entity", "hops": 2, "share": 0.11 },
{ "category": "mixer", "hops": 1, "share": 0.34 }
],
"triggered_rules": ["mixer_exposure_gt_25pct"]
}What it checks
No bundled black box. Each check is listed, configurable, and visible in the decision it produced.
Inbound and outbound addresses scored on attribution and exposure. Supported chains and assets: the major public chains and their tokens are covered.
Addresses attributed to exchanges, mixers, darknet markets, ransomware, gambling, and sanctioned entities where attribution data exists.
Indirect exposure traced across hops with the share of value from each risk category, so a two-hop mixer path is not invisible.
Thresholds, velocity, structuring, and geography rules across fiat rails, using the same rule engine as the on-chain side.
Originator and beneficiary data handling for transfers above the applicable threshold — the AED 3,500 threshold, with Notabene and TRP messaging.
Every alert is attached to the verified customer and their KYC evidence, so a monitoring hit opens with full context.
How it runs
The same sequence whether you call the API directly or use the hosted flow.
Transactions are submitted against a customer ID that already carries a verified identity and risk profile.
Counterparty attribution, exposure tracing, and your monitoring rules evaluate before you release funds.
Escalations land in the case queue with the exposure breakdown, transaction graph, and the customer's history.
Investigation outcomes export into internal SAR/STR workflows — reports are exported per case and per period for your regulator.
Exposure
Indirect
Hops
3
Action
Alert raised
Modules
Each one is a separate module you can switch on, order, threshold, or skip inside a journey.
Post-onboarding risk: rule-based transaction monitoring, on-chain wallet exposure, and Travel Rule counterparty data.
transaction_monitoringRuns your rule set over each transaction in real time or in batch: velocity, structuring, threshold avoidance, unusual corridors, dormancy reactivation, peer-group deviation.
wallet_screeningScores a crypto address before you pay out or credit a deposit: sanctioned address exposure, darknet, mixer, scam, and high-risk exchange exposure, direct and indirect.
transaction_tracingTraces funds back through hops to the originating cluster and forward to the destination, giving the analyst the picture rather than a lone score.
travel_ruleExchanges originator and beneficiary information with counterparty institutions on qualifying transfers, and records what was sent, received, or refused.
counterparty_vasp_discoveryAttributes a destination address to an institution and resolves whether a Travel Rule message can be delivered to it, or whether the destination is an unhosted wallet.
travel_rule_scopeDecides whether a transfer is in scope before any personal data leaves your tenant, using the threshold and transfer rules of the applicable regime.
unhosted_wallet_proofCollects proof that a self-custody destination belongs to your customer: signed message, declaration, or in-session verification, retained as an artefact.
ongoing_wallet_monitoringWatches previously cleared addresses and raises an alert when a wallet becomes sanctioned or gains exposure after you approved it.
See the full module catalog — every KYC, KYB, AML, KYT, and platform module with its inputs and outputs.
Evidence retained
Questions
A 30-minute walkthrough with a compliance engineer, or a sandbox key in your inbox today.