Map the relevant parties
Use a stable transfer reference with each party’s own subject details. Choose the sources your policy requires.
Sanctions screening software for money services businesses
Give customer and remittance checks a review path.
Run sanctions checks for the people in your MSB or remittance process. Keep each sender’s and recipient’s result clear. Agents can send possible matches to your team for review.
Paid plans start at $59/month for 5,000 checks each month. API and review dashboard included. See pricing.
250 free live screenings. One lifetime allowance. No credit card required.
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 transfer involves more than one person. The sender can return no-match while the beneficiary still needs review. Your app must show those two outcomes and keep errors separate from completed checks.
Keep failure visible in the integration
Send possible matches to the shared review queue. Give the principal business the facts and references needed to act.
Preserve the analyst handoff
Track corrected requests, repeat checks, and monitoring in the same allowance. Keep payment and fraud decisions in your own system.
Put it into practice
Connect screening to the next business step.
A recipient name is corrected before a remittance.
A transfer has a completed sender check but an open beneficiary case. The agent needs to show exactly which party still requires attention.
The shared reference connects two distinct results. The principal business can review the open question before applying its own transfer rules.
- 01
Define the policy checkpoint
List the sender, beneficiary, and other parties required at this step. Collect their known legal details.
- 02
Screen and route the result
Run each check and save its result ID. Review possible matches and leave required source failures incomplete.
- 03
Maintain continuing relationships
Follow the principal business’s review and approval process. Keep the transfer decision separate from the list-check result.
Two people in a fictional remittance
Example Willow Remit receives a transfer request in this invented example. One person sends the money; another is due to receive it. The firm’s policy sets who needs checks and when. Each person gets a separate screening linked to the transfer reference.
The sender returns no-match. The person due to receive funds has a similar-name match. Keep both results and send the open question for review. If you retry the same request, use the same body and idempotency key. If the name or other facts change, create a new request.
Scroll horizontally to compare every column.
| Work item | Screening evidence | Boundary |
|---|---|---|
| Sender | Person identity and retained selected-source result. | Does not determine the beneficiary’s identity. |
| Beneficiary | Independent screening and candidate review. | Missing details remain open questions. |
| Transfer workflow | Party references and reviewed case outcomes. | Behavioral monitoring, fraud, and payment decisions remain separate. |
Test the unresolved party and a source failure
Start free with 250 live screenings. Use them in the API or dashboard. Your first workspace gets this allowance once, with no monthly reset. No credit card is needed.
Try a sender and recipient with facts your team may share. Correct one name and run a new check. Ask staff to show who still needs review and which facts each result used.
The optional demo uses made-up records for a quick tour. Use the sandbox to test errors without using live checks.
Estimate completed subjects, not just transfer count. Required related parties and later rescreens can add checks. Compare plans and verify the sources in coverage. A synthetic demonstration does not establish live source availability.
Give agents a clear review handoff
Keep the transfer reference with both results. If an agent cannot resolve a possible match, it should reach the responsible reviewer with the known facts and open question. Keep the sender’s completed check visible without treating it as a result for the recipient.
The MSB guide gives practical steps. SanctionsKit does not look for patterns in payments. Use separate fraud and transaction-monitoring tools for that work. The principal business still decides whether to make the transfer.
TRY IT WITH YOUR TEAM
See if SanctionsKit fits your team.
Check your sources, try a free live check and estimate your monthly cost.
Check source coverage
Find your required sources, what they cover and when they were refreshed.
Explore coverageTry a match review
Use your free live checks to find possible matches. Compare the evidence and save a decision.
Start with 250 free checksEstimate monthly cost
Count new checks, rows in uploaded lists and repeat checks from monitoring.
See workload examples
Evaluate the fit
Screening questions for money services businesses.
Does one screening cover both sender and beneficiary?
No. Each person is a separate subject with a separate result. Use a shared transfer reference to connect the checks, then follow your policy for each party.
Does checking a sender and beneficiary replace transaction monitoring?
No. Each check compares a submitted sender or beneficiary with selected sources. It does not analyze payment patterns or detect suspicious transaction behavior. Keep transaction monitoring and review as separate controls for your transfers.
What happens if a required source is unavailable?
The request fails explicitly. Keep the check incomplete and resolve the cause or follow the approved change-of-scope process. Do not drop the source silently or turn the failure into no-match.
How can an agent send a match to the principal business?
Keep the screening and transfer references with the case. Assign or escalate it under the organization’s review process, with the known facts and unresolved question. The responsible reviewer records the next decision.
When should we reuse an idempotency key?
Reuse it only to retry the same unchanged request. A corrected name or other changed identity detail needs a new request. This keeps a retry distinct from a new check.
See SanctionsKit in action
Explore screening and review for money services businesses.
Start with 250 free live checks. Use the API or dashboard to review matches and save decisions. Choose a paid plan when you need more checks.
250 free live screenings. One lifetime allowance. No credit card required.