Control product flow risk
Screen before account approval, beneficiary creation, payout release, transfer execution, or counterparty acceptance instead of reviewing risk after the event.
Solutions / Real-Time Screening API
Connect AML screening to your workflows before risk moves forward
Use Checklynx as the screening layer between your product systems and compliance operations. The API checks customers, companies, counterparties, vessels, aircraft, and transaction context before onboarding, payments, payouts, transfers, or account changes continue.
CRMOnboarding
PaymentsTransaction event
CoreAccount change
POST/check/sanctions_pep
InputCustomer or counterparty
CoverageSanctions, PEP, wanted
OutputResults + 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
OperationsSupport API, batch, and adverse-media paths
Solve the gap between product events and compliance decisions
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.
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.
Onboarding and KYB
Stop risky customers, companies, sellers, and beneficiaries before activation.
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.