AML

Screen a counterparty before payout

Screening a counterparty before payout catches designated and high-exposure destinations before funds leave. Run a sanctions check and a risk score against the destination, then gate the release. Persist the outcome as payout evidence.

开始之前
  • A live API key with AML scope.
  • The payout destination address and its chain.

1Run the sanctions gate

Start with the C2 sanctions check on the destination. A match stops the payout before any C3 spend.

curl https://api.1st-node.com/v1/aml/eth/0xdead.../sanctions \
  -H "Authorization: Bearer sk_live_..."
> { "match": false }

2Score the destination

For a clean result, request the risk score to measure exposure. This C3 call returns the level that gates the release.

curl https://api.1st-node.com/v1/aml/eth/0xdead.../risk \
  -H "Authorization: Bearer sk_live_..."
> { "score": 12, "risk_level": "low", "confidence": 0.82, "exposure": [] }

3Gate the release

Only release on a clean sanctions result and an acceptable risk band. Anything above your review threshold holds the payout for manual sign-off.

4Store the payout decision

Record the sanctions result and risk response against the payout id. This is the evidence that the destination was screened at release time.

常见问题

Is a pre-payout screen enough on its own?

It covers the destination at release time. Pair it with KYT on the transaction and ongoing monitoring of the counterparty for full coverage.

What if the risk score is medium?

Medium bands should route to review rather than auto-release. Hold the payout for a human decision and store both the score and the outcome.

继续阅读

充值、拿密钥、上线。

自助开通。支持加密货币或银行卡。按额度计费——重型原语更贵,简单调用很便宜。

获取 API 密钥