Onboard a VASP customer with AML checks
Onboarding a customer at a VASP means establishing an AML baseline before the first transaction. Combine a sanctions check with an address risk score to derive an initial risk level. Store both so later monitoring has a reference point.
- A live API key with AML scope.
- The customer's declared deposit wallet address and chain.
1Screen the wallet against sanctions
Run the C2 sanctions check first as a gating step. A match ends onboarding before any further calls are spent.
curl https://api.1st-node.com/v1/aml/tron/TQ5f.../sanctions \ -H "Authorization: Bearer sk_live_..."
2Score the wallet's exposure
For a clean address, request the risk score. This C3 call returns the exposure categories that set the customer's initial risk band.
curl https://api.1st-node.com/v1/aml/tron/TQ5f.../risk \
-H "Authorization: Bearer sk_live_..."
> { "score": 24, "risk_level": "low", "confidence": 0.79, "exposure": [] }3Set an initial risk level
Map the returned risk_level to your onboarding tiers. Low can proceed automatically; medium and high require enhanced due diligence before activation.
4Store the onboarding baseline
Persist the sanctions result and the risk response against the customer record. This baseline is the reference for detecting later drift and is part of the audit trail.
常见问题
Should sanctions run before or after the risk score?
Run sanctions first. It is the cheaper C2 call and a match ends onboarding immediately, so you avoid spending a C3 risk score on a rejected customer.
What confidence value is high enough to act on?
Confidence reflects how well-attributed the exposure is. Treat low-confidence high scores as review candidates rather than automatic rejections.
继续阅读
充值、拿密钥、上线。
自助开通。支持加密货币或银行卡。按额度计费——重型原语更贵，简单调用很便宜。
获取 API 密钥