Phonetic similarity
Catch names that sound alike even when source records use different spellings or local conventions.
Solutions / Transaction Screening
AML Transaction Screening Software for Payments and Counterparties
Screen the supplied parties, names, and supported identifiers in payment, payout, transfer, remittance, wallet, and counterparty events. Route potential sanctions and watchlist matches for human review before value moves.
Checklynx
Transaction screeningTRX-80421 · Bank transfer
ReviewNHOriginatorNorthbridge
EUR 12,450→EMBeneficiaryElena Marin
1 actionable resultIBAN ···· 4821Evidence linked
InlineScreen before payment release
ContextParties, wallets, and transaction fields
RoutingClear, hold, review, or escalate
EvidenceKeep screening and decision records
Transaction-party screening
Check the parties and identifiers attached to a transaction
A payment event can involve an originator, beneficiary, counterparty, account, wallet, or other supplied identifier. Checklynx screens the submitted parties and supported fields against enabled risk sources, returns structured results, and keeps the screening evidence connected to the business event.
Stop prohibited activity earlier
Screen counterparties, beneficiaries, senders, receivers, wallets, and relevant transaction context before the workflow completes.
Give operations a clear next step
Return structured results that can hold a payment, continue a low-risk flow, or create an analyst review task.
Keep a defensible payment record
Attach screening inputs, matched sources, timestamps, and review outcomes to the transaction history.
Transaction screening workflow
From payment event to controlled release or review
Submit the relevant transaction parties and identifiers, screen them against the enabled sources, apply your routing rules, and retain the result and authorised decision with the transaction record.
Payment eventCounterparty screened before value moves
Screen the supplied parties, names, and supported identifiers in payment, payout, transfer, remittance, wallet, and counterparty events. Route potential sanctions and watchlist matches for human review before value moves.
Payment routeReview with evidence
Audit evidenceRequest, response, hold state, reviewer outcome
| Stage | Enterprise context | Outcome |
|---|---|---|
| Payment initiation | Checkout, payout, transfer, remittance, wallet event | Screen parties and context before release. |
| Risk response | Results, match profiles, source types, identifiers | Route the payment to clear, hold, or review. |
| Compliance review | Case queue, analyst notes, escalation | Resolve potential matches with evidence attached. |
| Audit trail | Request, response, decision, timestamps | Reconstruct what happened if challenged. |
Operational handoff
Connect transaction decisions to cases and webhooks
Transaction screening is most useful when the result changes what the business system does next. Checklynx connects the screening result to case management and webhook updates so payment, product, and compliance teams stay aligned.
Case management handoff
When a transaction or counterparty needs review, the result can become an owned case with hit context, notes, timeline activity, attachments, escalation, and final disposition. Compliance teams review the evidence while the payment workflow remains held or controlled.
Webhook-driven workflow updates
Use webhooks to notify downstream systems when screening events, review outcomes, or case status changes need to update payment holds, customer records, operational dashboards, or audit workflows.
| Trigger | Handoff | Business outcome |
|---|---|---|
| Potential match | Create or update a case | Analyst owns review with evidence attached. |
| Review outcome | Send event through webhook handoff | Payment or product workflow can clear, hold, or escalate. |
| Case status change | Notify operational systems | Dashboards and records stay aligned with compliance work. |
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.
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 in transaction-party 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 is AML transaction screening software?
AML transaction screening software checks the parties, names, counterparties, and supported identifiers supplied with a payment or transfer event against enabled sanctions, watchlist, and other screening sources. Potential matches can be held or routed for human review according to the organisation’s policy.
Which transaction parties can be screened?
The submitted data may include originators, senders, receivers, beneficiaries, counterparties, payment parties, companies, and supported account or wallet identifiers. The organisation remains responsible for deciding which parties and fields must enter scope for each payment flow.
When should transaction screening run?
Common checkpoints include beneficiary creation, payment initiation, payout approval, transfer execution, remittance processing, wallet events, counterparty acceptance, and other moments before funds or value are released.
Is transaction screening the same as transaction monitoring?
No. Checklynx transaction screening checks supplied parties and supported identifiers against screening sources. Behavioural transaction monitoring analyses activity patterns, amounts, velocity, typologies, and anomalies and requires separate controls or systems.
Does a potential match automatically block a payment?
No. Checklynx returns screening results and review context. The customer’s policies and systems determine whether to continue, hold, reject, investigate, or escalate a transaction, and accountable people remain responsible for consequential compliance decisions.