Onboarding and KYB
Stop risky customers, companies, sellers, and beneficiaries before activation.
Solutions / Real-Time Screening API
AML Screening API for Real-Time Compliance Decisions
Use Checklynx as the screening layer for onboarding, KYC/KYB, sanctions and PEP checks, customer refresh, payment-party screening, payout review, beneficiary creation, and transaction screening events.
CRMOnboarding
PaymentsTransaction event
CoreAccount change
POST/check/sanctions_pep
InputCustomer or counterparty
CoverageSanctions, PEP, wanted, transaction context
OutputDecision + match profiles
ClearContinue workflow
ReviewCreate case
EvidenceAudit record
InlineScreen before approval, release, or escalation
PolicyRoute clear, hold, review, or EDD outcomes
EvidenceGive analysts source-backed review packets
WorkflowsOnboarding, payments, payouts, transactions
AML Screening API for Sanctions, PEP and Watchlist Checks
Growing teams often have screening spread across manual searches, CSV uploads, disconnected tools, and analyst inboxes. The Real-Time Screening API gives product, risk, and compliance systems one integration point for checking risk, routing decisions, and preserving evidence before the business process moves forward.
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 audit evidence attached
Attach screening inputs, source-backed matches, timestamps, and review outcomes to the customer, transaction, or case record for governance and regulatory review.
Where the API sits in your workflow
Checklynx sits at the decision point between business systems that create risk and compliance operations that need to review it. The goal is not just to search lists. It is to decide whether the workflow can continue, needs a hold, or must move to analyst review.
| Step | What happens | Output |
|---|---|---|
| Trigger from your business system | Call Checklynx from onboarding, CRM, payment, wallet, marketplace, or case-management events. | Screening request |
| Screen before the workflow advances | Check the customer, company, counterparty, vessel, aircraft, or transaction context before approval, payout, transfer, or account change. | Risk response |
| Apply your routing rules | Use the response to clear low-risk activity, hold the workflow, open a review, or trigger enhanced due diligence. | Operational decision |
| Hand off to compliance review | Send results and match profiles into analyst queues with source context, identifiers, aliases, and timestamps. | Review packet |
| Preserve governance evidence | Store the request, response, downstream action, reviewer notes, and final outcome for audit and regulatory review. | Defensible record |
Turn product events into compliance decisions
Connect the moments where risk enters the business to one screening layer that can clear, hold, route, and evidence the decision.
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 responseClear, hold, review, or escalate
One response gives product and compliance teams the same decision trail.
One API surface for screening, routing, and evidence
Use real-time checks, batch refreshes, and adverse-media searches without making analysts rebuild the story in spreadsheets.
Real-time
/check/sanctions_pepScreen at the decision point
Check one customer, company, counterparty, vessel, aircraft, or transaction before the workflow moves.
Batch
/check/sanctions_pep/batchRefresh customer files
Run bulk screening for up to 200 check_items with results keyed back to your own request identifiers.
Media
/check/adverse_mediaAdd risk context
Search adverse media when the review needs negative news, official records, and source-backed context.
Returned with every reviewInputsearch_term or search_identity Decisionclear, hold, review, or EDD Evidenceresults + match_profiles
Use names or structured identity data, then tune by source, group, and fuzziness.
Route the next step directly from the response instead of waiting for a manual lookup.
Keep source-backed matches, grouped profiles, timestamps, and review context attached.
Use one API for the checks your product flow needs
Trigger screening from the moments where risk enters the business, then route the response into the right operational step.
AML Screening API
Run AML checks from onboarding, account changes, customer refreshes, and backend risk events.
Sanctions Screening API
Check people, companies, UBOs, counterparties, vessels, and aircraft against sanctions sources before exposure moves forward.
KYC Screening API
Screen customers and beneficial owners during KYC/KYB submission, beneficiary creation, and profile updates.
Transaction Screening API
Screen payment parties, payout context, transfer counterparties, and transaction-related names before release or escalation.
Request and response examples
Use structured identity data when available, or send a search term with your own request identifier so results can be written back to your workflow.
Request example
POST /check/sanctions_pep
Authorization: Bearer <api_key>
Content-Type: application/json
{
"request_id": "onboarding_48921",
"check_item": {
"type": "company",
"name": "Northbridge Trading Ltd",
"country": "GB",
"related_parties": [
{ "type": "person", "name": "Maria Costa", "role": "ubo" }
]
},
"sources": ["sanctions", "pep", "wanted"],
"fuzziness": "standard"
}Response example
{
"request_id": "onboarding_48921",
"decision": "review",
"results": [
{
"risk_type": "sanctions",
"match_score": 0.91,
"source": "OFAC SDN",
"matched_name": "Northbridge Trading",
"profile_id": "match_prof_7842"
}
],
"match_profiles": [
{
"profile_id": "match_prof_7842",
"aliases": ["Northbridge Trading"],
"identifiers": ["source-backed identifiers"],
"review_context": "Analyst review required"
}
]
}Authentication and implementation
Authenticate API calls with a server-side API key, keep keys out of client-side applications, and use your own request identifiers to connect Checklynx responses back to onboarding, payment, payout, beneficiary, or customer-refresh events.
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 | Structured response for clear, hold, review, or escalation |
| 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 |
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.