Map the relevant parties
Identify each person or organization required under your policy and retain its transaction or relationship role. Do not substitute the sender’s result for a recipient check.
Sanctions screening software for money services businesses
Give remittance-party checks a clear review path.
Screen MSB customers and counterparties with defined sources, documented review, and monitoring linked to the continuing relationship.
API and compliance dashboard included in every plan.
SanctionsKitIllustrative workflow
Customer onboarding
Known identity
Selected lists
Review path
Completed screeningContinue your policy workflow
Potential matchInvestigate in the dashboard
Identity verification and transaction monitoring remain separate.
Built around your work
A party check is one part of the transaction process.
A remittance or money-services workflow can involve sender, recipient, agent, and business counterparties. The service needs to know which identities were screened while preserving separate AML, fraud, licensing, and reporting controls.
Keep failure visible in the integration
Treat a timeout or unavailable source as an incomplete check, not no match. Use safe retries and retain the internal operation reference.
Preserve the analyst handoff
Give reviewers the original source candidate and submitted identity. Document the identity conclusion separately from the authorized transaction disposition.
A practical use case
Give remittance-party checks a clear review path.
Screen MSB customers and counterparties with defined sources, documented review, and monitoring linked to the continuing relationship.
The review challenge
A remittance or money-services workflow can involve sender, recipient, agent, and business counterparties. The service needs to know which identities were screened while preserving separate AML, fraud, licensing, and reporting controls.
How SanctionsKit helps
Identify each person or organization required under your policy and retain its transaction or relationship role. Do not substitute the sender’s result for a recipient check. Treat a timeout or unavailable source as an incomplete check, not no match. Use safe retries and retain the internal operation reference.
- 01
Define the policy checkpoint
Identify where screening belongs in customer onboarding and party-review workflows. Confirm the sources and data required for each subject type.
- 02
Screen and route the result
Use the server-side API or dashboard and branch explicitly on completed outcomes. Route unresolved identities and technical issues to the appropriate owners.
- 03
Maintain continuing relationships
Use monitoring for selected customers or counterparties and record changes. Keep transaction-monitoring and regulatory filing processes separate.
Evaluate the fit
Screening questions for money services businesses.
Does this replace an MSB AML program?
No. FinCEN describes MSB-specific obligations. SanctionsKit supports selected-source screening and review, not the entire AML program or filing process.
Can we screen both sender and recipient?
They can be submitted as separate supported subjects under your policy. Keep the relationship between each result and the relevant party.
Is this transaction monitoring?
No. Submitting a party identity from a transaction is different from analyzing transaction behavior or detecting suspicious patterns.
What happens if a required source is unavailable?
The workflow must treat the check as incomplete and follow the documented error or exception process. It must not silently clear the party with reduced coverage.
See SanctionsKit in action
Explore screening and review for money services businesses.
Try the interactive demo with synthetic examples. Compare plans for your team’s screening volume.