30–40%Less compliance review time
CashDirector reports that clustered profiles and fewer false positives help its compliance officers review cases faster.
Industries / Remittance
AML Screening Software for Remittance and Money Transfer Companies
Screen senders, recipients, agents, counterparties, and cross-border transfers across sanctions, PEP, adverse media, and watchlist data with fast checks and audit-ready evidence.
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.
SendersCustomer and originator checks
RecipientsBeneficiary and payout review
AgentsPartner and location screening
EvidenceCases, rationale, audit trail
Money movement operations
Built for regulated transfer and payout workflows
Remittance, FX, wallet, PSP, and payout providers need AML checks that keep pace with transfer speed. Checklynx gives teams a practical way to screen the people, entities, identifiers, and counterparties involved in each movement of funds.
Screen both sides of the transfer
Screen every transfer in real time through the Transaction Screening API, using supplied senders, recipients, beneficiaries, banks, agents, and other relevant parties before funds are released.
Use identifiers and payment context to reduce ambiguity
Use supplied tax IDs, identity-document data, payment references and country context. For bank accounts, Checklynx screens the BIC and retains the account number as supporting evidence; supported wallet addresses can enter sanctions-identity screening where relevant.
Keep review evidence in one place
Preserve match sources, analyst rationale, notes, escalation history, decisions, and timestamps for audit, partner, and internal review.
Screening journey
From transfer signal to documented decision
A sender, recipient, agent, or transfer signal becomes owned work, analysts review the underlying match, and the outcome stays tied to the evidence that supported it.
| Stage | Screening context | Business outcome |
|---|---|---|
| Onboarding | Sender, recipient, agent, business customer, director, or UBO profile | Risk is checked before approval or activation. |
| Transfer created | Counterparty, corridor, destination market, BIC and account evidence, payment reference, or wallet address | Potential exposure is reviewed before funds move. |
| Hit reviewed | Sanctions, PEP, adverse media, criminal, or watchlist match context | Analysts decide true positive, false positive, or escalation with evidence. |
| Monitoring update | New sanctions listing, PEP change, adverse media event, or watchlist update | Existing customers and agents stay visible after onboarding. |
| Outcome recorded | Decision, rationale, reviewer, timestamp, attachments, and audit trail | The business can explain who decided what and why. |
Review efficiency
Reduce repeated screening work across transfer operations
Screening should not force analysts to rebuild the same review packet every time a customer sends money. Checklynx keeps decisions, source context, and monitoring history connected to the profile and case.
Sender or recipient hit
Review sanctions, PEP, adverse media, and watchlist context with profile details, identifiers, corridor context, and transfer timing.
Agent or partner review
Batch screen agent networks, payout partners, business customers, directors, and UBOs before or after activation.
Known false positive
Reuse prior decisions where appropriate so the same non-risk hit does not create repeated manual work.
Audit or bank request
Export source-backed evidence, decisions, notes, escalation events, and review history when partners or auditors ask for proof.
| Trigger | Handoff | Business outcome |
|---|---|---|
| Potential sanctions hit | Case review with source context | Analysts can decide before payout or release. |
| New or updated agent | Batch or API screening | Partner risk is reviewed before exposure grows. |
| Repeated non-risk match | Customer-scoped decision memory | The same false positive does not keep returning as new work. |
| Governance request | Case evidence and immutable audit trail | Compliance can explain the decision record. |
Anonymous customer story
Remittance screening in practice
A Spain-based remittance provider explains its migration to Checklynx, ongoing customer monitoring and transaction screening workflow.
Read the customer story →Design the control around the remittance lifecycle
Map parties, transfer events, data, decisions and evidence, then choose the appropriate customer or transaction-screening integration.
Put screening at the control points in a transfer journey
Use event-driven checks for transfers and payouts, batch review for agents and portfolios, and monitoring for approved relationships while preserving the same decision evidence.
01Real-time screening API
Screen supplied parties and identifiers at transfer creation, payout, or another approved event.
Explore 02CSV batch screeningReview supplied agent, partner, or customer populations under one controlled configuration.
Explore 03Ongoing monitoringReturn relevant source or customer-data changes for review after approval.
Explore 04Case managementAssign potential matches with corridor, payment-party, source, and reviewer context attached.
ExploreSee how transfer screening stays connected to review
01Sender, recipient, and agent context
Use the parties and identifiers supplied by the transfer workflow.
02Configured screening
03Human reviewApply the enabled sources and matching rules at the required business event.
Assess potential matches with source and transaction context before the authorised decision.
04Evidence and monitoringKeep outcomes attached and return relevant changes for 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.
What should remittance companies screen?
Remittance teams commonly screen senders, recipients, beneficiaries, payout recipients, agents, business customers, directors, UBOs, payment counterparties, identifiers, and transfer context.
Should both sender and recipient be screened?
In many transfer workflows, screening both sides helps identify sanctions, PEP, adverse media, watchlist, and counterparty exposure before funds are released.
Can screening happen before a transfer is released?
Yes. Checklynx can screen every transfer in real time when the customer configures that workflow and supplies the relevant parties and identifiers. Whether every transfer must be screened is determined by the firm's applicable framework and approved policy.
Does Checklynx replace a full AML program?
No. Checklynx supports screening, monitoring, case review, and audit evidence workflows. Legal obligations and broader AML program design depend on the business model and jurisdiction.
What is remittance and money-transfer screening software?
It supports configured screening of supplied senders, recipients, agents, beneficiaries, counterparties, and supported identifiers at onboarding, transfer, payout, portfolio-review, and monitoring moments. Potential matches still require human review under the organisation's policy.
Is transfer screening the same as behavioural transaction monitoring?
No. Transfer-party screening checks the people, companies, and supported identifiers involved in a payment against enabled sources. Behavioural transaction monitoring looks for unusual activity patterns. They can share case and evidence workflows but remain different controls.