Onboarding and KYB
Screen customers, companies, sellers, and beneficiaries before activation, then route potential matches for review.
Solutions / Real-Time Screening API
Real-Time AML Screening API Built for Your Product Flow
Embed real-time AML screening in your product flow, return structured results to your systems, and route potential matches for review under your own policies.
CRMOnboarding
PaymentsTransaction event
CoreAccount change
POST/check/sanctions_pep
InputCustomer or counterparty
CoverageSanctions, PEP, wanted, transaction context
OutputResults + match profiles
ContinueYour product rule
ReviewAnalyst queue
RecordScreening trail
InlineScreen before approval, release, or escalation
RoutingTurn screening results into your next action
EvidenceGive analysts source-backed review packets
WorkflowsOnboarding, payments, payouts, transactions
AML Screening API for Sanctions, PEP and Watchlist Checks
Replace manual lookups and disconnected handoffs with one server-side integration. Check customers and counterparties when risk enters the business, return structured screening data to your product, and give compliance teams the source context they need to review potential matches quickly.
Control product flow risk
Screen before account approval, beneficiary creation, payout release, transfer execution, or counterparty acceptance instead of reviewing risk after the event.
Standardize compliance handoff
Return structured results and match profiles that downstream teams can route into case queues, EDD workflows, or MLRO review without rebuilding evidence manually.
Keep the screening trail connected
Write the request, returned results, downstream action, and reviewer outcome to your customer, transaction, or case record using your own system references.
Turn product events into compliance decisions
Connect the moments where risk enters the business to one screening layer, then apply your own policy to the returned results.
Payments and payouts
Screen parties and transaction context before releasing activity that may create exposure.
Case review and audit
Send analysts structured evidence and keep the final outcome attached for review.
API responseResults ready for your routing rules
Product and compliance teams work from the same structured screening response.
Connect Checklynx workflows to your systems
Connect Checklynx to the customer, payment, and operational journeys your teams already use. Run screening and review workflows through the API, then keep the response and evidence connected to the business event that triggered them.
Customer lifecycle
Build controls into onboarding and refresh
Connect KYC, KYB, customer, beneficial-owner, counterparty, and profile-change events to the appropriate screening workflow.
Money movement
Screen before funds or value move
Apply checks to payment parties, beneficiaries, payouts, transfers, wallets, and transaction-related names at the point your process needs them.
Review operations
Move potential matches into controlled review
Pass structured results and source context into analyst, case, escalation, and evidence workflows without recreating the screening trail.
Portfolio controls
Connect repeatable checks after onboarding
Support customer refresh, batch screening, and configured monitoring workflows as records, source data, or business context change.
Business valueFaster journeysControls inside the product flow Consistent operationsOne connected workflow Stronger evidenceA traceable decision record
Check risk at the relevant business moment instead of adding a separate manual handoff.
Give product, operations, and compliance teams the same structured response and review context.
Keep the request, response, downstream action, and reviewer outcome linked through your own business references.
Request and response examples
Send exactly one name-based search_term or identifier-based search_identity. This server-side example narrows the check to sanctions and entities with the documented default fuzziness level.
Request example
POST /check/sanctions_pep
x-api-key: <api_key>
Content-Type: application/json
{
"search_term": "Northbridge Trading Ltd",
"fuzziness": "1",
"filters": {
"source_type": ["sanctions"],
"group_type": ["entity"]
}
}Response example
{
"results": [
{
"id": "result_7842",
"score": "4.7",
"target": {
"name": "Northbridge Trading",
"group_type": "entity"
},
"source": {
"id": "OFACSDN",
"name": "Office of Foreign Assets Control SDN List",
"region": "USA",
"source_type": "sanctions"
}
}
],
"match_profiles": [
{
"match_profile_id": "profile_7842",
"name": "Northbridge Trading",
"rca_hit": false,
"id_hit": false,
"results_ids": ["result_7842"]
}
]
}Authentication and implementation
Authenticate server-to-server calls with the x-api-key header and keep the key out of browser and mobile code. Store the request, response, and your own business record reference together so analysts can move from a product event to the relevant screening context without rebuilding the trail.
API, portal, batch, or monitoring?
Pick the workflow based on where the decision happens and how much operational control your team needs.
| Workflow | Best for | Typical output |
|---|---|---|
| Real-time API | Onboarding, payments, payouts, beneficiary creation, and backend risk events | Results and match profiles for your routing rules |
| Screening portal | Manual investigations, broad subject searches, and analyst-led review | Search results and review context |
| CSV batch screening | Refreshing customer, counterparty, or supplier files outside the live product path | Bulk results linked to uploaded records |
| Ongoing monitoring | Approved customers, UBOs, counterparties, and payment parties after onboarding | New alerts, suppressed non-matches, cases, and audit evidence |
Smart matching technology
Match complex names without losing control
PEP screening depends on names that appear in many formats, scripts, and source systems. Checklynx helps handle real-world variation while keeping reviewer decisions separate from the matching step.
Phonetic similarity
Catch names that sound alike even when source records use different spellings or local conventions.
Transliteration and spelling
Support non-Latin names, accent differences, reversed word order, and common data-entry variations.
Multiple languages
Represent names and aliases across scripts so reviewers can compare the result against source records.
Nicknames and honorifics
Account for titles, abbreviated names, and short forms while keeping the reviewer in control.
Measured impact after screening results reach review
30–40%Less compliance review time
CashDirector reports that clustered profiles and fewer false positives help its compliance officers review cases faster.
20%Less time spent on monthly reviews
Shopware connects retained false-positive decisions, customer screening and ongoing monitoring.
What can the real-time screening API check?
The screening API supports sanctions, PEP, wanted, and supported watchlist checks, with filters for individuals, entities, vessels, and aircraft. Adverse media is available through a separate adverse-media search path.
Where should teams use real-time AML screening?
Common integration points include onboarding, KYB and KYC submission, account approval, beneficiary setup, counterparty creation, transaction review, payment or payout release, profile updates, and backend risk refresh events.
Does the API replace human review?
No. The API returns structured results and match profiles so your workflow can route potential risk, but review policy and final compliance decisions remain under your team's control.