30–40%Less compliance review time
CashDirector reports that clustered profiles and fewer false positives help its compliance officers review cases faster.
Industries / Crypto platforms and VASPs
AML and Sanctions Screening for Crypto Platforms and VASPs
Screen customers, companies, transfer parties, and supplied wallet addresses against sanctions identifiers. Keep review evidence connected.
Review queue4 reviews
HighPotential sanctions matchNeeds review
MedPEP review neededAssigned
LowKnown false-positive checkSaved view
Screening decisionIn review
Match reviewPotential match
Source evidence attachedRationale addedCompliance escalation
Audit evidence5 actions recorded
Screening, review, note, escalation, and outcome.
OnboardingCustomer and entity sanctions/PEP checks
TransfersSupplied parties and wallet identifiers
ReviewResults with source context
EvidenceRetrievable transaction-screening runs
Screening for crypto operations
Bring the parties, checks and review context together
A new account, corporate customer or withdrawal can introduce different people, entities and identifiers. Checklynx provides a screening layer for those inputs, while your team controls how results affect onboarding and transfers.
Screen the customer relationship
Check customers, companies and already-identified related parties against sanctions and PEP data where your policy requires it. Use adverse-media checks as a separate source of risk information.
Connect checks to the transfer
Submit the relevant transaction parties and supported wallet-address inputs together. Retain a run reference and per-party results so reviewers can see which information was screened.
Spend less time assembling documentation
Keep transaction-screening evidence retrievable and connect actionable results to case review where applicable. Reduce repeated copying of screening context when preparing reviews and explaining decisions.
From onboarding to transfer review
Choose a screening checkpoint for each business event
Define which subjects enter scope, which information your platform supplies and who responds to a finding. A customer check and a later transfer check may involve different parties and addresses.
| Business event | What your team supplies | How Checklynx supports the check |
|---|---|---|
| Customer onboarding | Person or company information and relevant identifiers | Sanctions and PEP screening with results for review. |
| Corporate relationship review | Already-identified owners, controllers or other parties required by policy | Screening of the supplied parties; ownership discovery and analysis remain separate. |
| Deposit, withdrawal or transfer | Relevant parties, client transaction reference and supported wallet-address inputs | A transaction-screening run with per-party results and retrievable evidence. |
| Customer review after onboarding | Maintained customer records and dashboard-configured monitoring | Re-screening of customer records under the configured workflow. |
Clear responsibilities
Fit screening into the rest of your crypto controls
Your platform and compliance team retain the onboarding and transfer decision. Checklynx supplies screening results and review context; it does not decide whether funds must be held, released, rejected, blocked or reported.
Wallet-address sanctions checks
The Transaction Screening API supports a supplied wallet_address instrument. Its address is checked when the selected profile enables sanctions identity screening. This is a check against supported sanctions identifiers, not wallet ownership verification or an on-chain risk score.
Separate controls, connected context
Use your identity-verification, blockchain-analysis and Travel Rule systems for their respective tasks. Checklynx does not provide chain tracing, wallet attribution or clustering, indirect-exposure analysis, behavioural crypto monitoring or Travel Rule message exchange.
| Trigger | Handoff | Business outcome |
|---|---|---|
| A transfer requires review | Use the returned run and case references where available | Keep the screening evidence connected to the authorised decision. |
| Screening opens a case | Receive supported signed case-opened webhooks | Notify your workflow that review work exists; do not treat the event as a final decision. |
| A customer needs re-screening | Maintain the record and configure monitoring in the dashboard | Review the customer again without implying continuous observation of blockchain activity. |
Plan your crypto screening workflow
Use the implementation guide to map the controls, then go deeper only where your project needs it.
Connect crypto customer and transfer-party screening to the right control point
Use supplied customer, company, transfer-party, and wallet-address data for onboarding, transfer review, portfolio checks, and ongoing screening while keeping blockchain analytics and legal decisions outside the screening result.
01Real-time screening API
Run configured checks at account, beneficiary, transfer-party, or another approved product event.
Explore 02Transaction screeningScreen supplied transfer parties and supported identifiers before the approved routing decision.
Explore 03CSV batch screeningReview supplied customer, counterparty, or wallet-address populations under one controlled configuration.
Explore 04Case managementRoute potential matches with source, customer, transfer, and reviewer context attached.
ExploreSee how crypto screening becomes a governed review record
01Customer and transfer context
Use the customer, company, transfer-party, identifier, and wallet-address data supplied by the crypto workflow.
02Configured screening
03Authorised reviewApply enabled sources and matching rules at the relevant approved event.
Assess potential matches with source and relationship context before the business decision.
04Decision evidenceRetain the outcome and supporting record for governance and later review.
Measured impact in regulated screening review
30–40%Read the CashDirector case study →
20%Less time spent on monthly reviews
Shopware connects retained false-positive decisions, customer screening and ongoing monitoring.
Does Checklynx provide a complete crypto AML platform?
Checklynx provides sanctions and PEP screening, a separate adverse-media workflow, transaction-party screening and review/evidence capabilities. Identity verification, blockchain intelligence, Travel Rule information exchange and behavioural transaction monitoring require their own controls and systems.
What does a wallet-address sanctions check cover?
For the supported wallet_address payment instrument, Checklynx screens the supplied address when sanctions identity screening is enabled in the selected profile. It does not establish ownership, trace funds or calculate indirect on-chain exposure. A no-candidate result is not confirmation that the wallet or transfer is free of sanctions risk.
Can we screen beneficial owners and other related parties?
You can screen the people and entities your team has already identified and supplied for review. Deciding which parties must be checked, establishing the ownership structure and assessing sanctions ownership or control remain separate responsibilities.
How do API checks connect to documentation?
The Transaction Screening API creates a retrievable screening run and may link actionable results to a case. Direct sanctions/PEP and adverse-media checks do not create customer or case records, so your application must retain its own review and decision evidence for those workflows. Use the current developer documentation to select the appropriate model.
Can customer screening continue after onboarding?
Checklynx customer records can be used in dashboard-configured ongoing monitoring. Monitoring configuration and execution are not currently exposed through the public API. This customer re-screening is distinct from on-chain or behavioural monitoring.