Sanctions screening for crypto customer onboarding

Start with the legal customer identity

Use SanctionsKit for the person or company opening an account. A username, wallet address and legal customer are different things. First verify who the customer is through your approved process. Then send the name and other supported facts for the list check.

SanctionsKit compares the subject with selected sources. It does not trace blockchain transactions, score wallet exposure or study transaction patterns. Keep those checks separate and visible. One account flag should not hide which checks were done and which still need work.

Submit a result your team can review

For a manual check, open New screening, enter the legal name and known identity details, and select the approved policy. Create a saved profile with the customer-party reference if future checks are needed.

For an integration, follow the fintech request example. Call POST /api/v1/screenings with standard retention and a stable reference. Keep the key server-side and test with synthetic Sandbox inputs. Confirm Production coverage supports the subject. Pasting a wallet address into a name field does not perform wallet screening.

Attach review to the correct account party

Find saved results in Screening history and open candidates in the Review queue. Give a company and its director separate result IDs when both need a check. They may share an account, but they are not the same party.

For a fictional company customer, compare a director's common-name candidate with trusted dates and IDs. Record whether it is the same person and why, then record the separate business decision. A policy can require an outside ownership check. SanctionsKit does not find the owners or work out their shares.

Connect separate wallet and activity evidence

Record the wallet-check provider or process, input, scope, time and result in your authorized control record. Link relevant evidence from a case when needed. Never put private keys, credentials or unrelated transaction data in review notes.

A customer no-match does not clear a withdrawal address. A new address does not by itself change the customer's legal identity. Use OFAC's virtual-currency guidance and your current procedure to determine the separate checks required.

Monitor identity changes and unfinished checks

Create the approved customer monitor in Monitoring. Select the saved profile and policy, then confirm its first result. Assign the inbox and cases to a reviewer. These checks repeat the name and identity search; they do not watch what a wallet does.

If the customer's legal details change, confirm the new facts in the saved profile and any paused linked monitor. Keep failed checks and open candidates visible in the account flow. Test these handoffs in Sandbox before you use them in an approved Production workflow.

Frequently asked questions