Handle a high-risk crypto deposit
A high-risk deposit needs handling before funds are credited. Score the sender with the risk endpoint, confirm the source with an inbound fund-flow trace, and hold the deposit pending review. Store the evidence for the audit trail.
- A live API key with AML scope.
- The depositing address and the chain of the incoming transaction.
1Score the depositing address
Request the risk score on the sender. A high risk_level or direct high-risk exposure is the trigger to hold. This is a C3 call.
curl https://api.1st-node.com/v1/aml/eth/0xbadf.../risk \
-H "Authorization: Bearer sk_live_..."
> { "score": 88, "risk_level": "high", "confidence": 0.91, "exposure": [{ "category": "mixer", "hops": 1 }] }2Trace the inbound flow
Confirm where the funds came from with an inbound fund-flow trace. This C4 call resolves the path over the requested hops.
curl "https://api.1st-node.com/v1/intel/eth/0xbadf.../flow?dir=in&hops=3" \ -H "Authorization: Bearer sk_live_..."
3Hold the funds pending review
Do not credit the account until review clears. Move the deposit to a hold state so the balance is not spendable while under investigation.
4Store the evidence
Persist the risk response and the trace against the deposit id. Whether funds are released or frozen, the stored evidence justifies the decision.
Perguntas frequentes
Should I reject a high-risk deposit outright?
Hold rather than reject reflexively. Confirm the source with a trace and let review decide; store the evidence supporting whichever outcome you reach.
Why trace inbound rather than trust the score?
The score summarizes exposure; the inbound trace shows the actual path funds took. The path is what a reviewer and an auditor need to see.
Continue lendo
Recarregue, pegue a chave e publique.
Autoatendimento. Pague em cripto ou cartão. Medido por créditos: primitivas pesadas custam mais, as simples são baratas.
Obter chave de API