Use case
Customer onboarding sanctions screening workflow
Add sanctions checks to your customer screening process. Review matches, keep evidence and resolve failed checks before making the account-opening decision.
On this page
Check a customer and save the review
Use the dashboard to run a customer check. Or connect the API to your onboarding app. Your team can review possible matches and keep the evidence with the account decision.
Start free with 250 live screenings for your first workspace. Run new-customer checks through the API or dashboard, then ask a colleague to review a match. Both tools share this one-time allowance. It does not reset each month, and no credit card is needed. As your customer list grows, Starter gives you 5,000 checks each month for $59/month. The API and review dashboard are included.
Collect facts you can support
Start with the customer’s name. Choose whether the subject is a person or an organization. Add a known date or reliable ID when your process has a reason to collect it. Leave unknown facts blank. Do not guess a birth date or nationality.
Choose the required sources before you run the check. A saved organization policy records why you screen and which sources each subject type needs. It also records outside checks, approval rules, and when the retention period starts. Each screening keeps a copy of the policy used.
Give each result a clear next step
Send a possible match to review. A completed no-match result can finish the list-check step under your policy. An invalid request, unavailable source, or processing failure leaves the check incomplete. Resolve that issue through your approved process.
For example, an error response may contain no match data because the check failed. That is not a reason to open an account. Save the result ID and selected sources with the customer record. The reviewer can then find the check that actually ran.
Complete the other required customer checks
List screening does not replace checks of identity, ownership, or political exposure, often called PEP screening. Your activity may need other due diligence too. Carry out those checks through your approved process. Keep their status with the case.
The case can hold each check’s status, the reviewer’s reasons, and an evidence reference. Required checks that are still open prevent completion. Your team should make the account decision from the full review. A screening score alone cannot decide it.
Decide what happens after the account is opened
Keep evidence for the period your policy requires. If you need ongoing monitoring, disclose and authorize the subject data you will keep. Count future rescreens when you plan usage. A one-time check with minimal retention does not start a monitor.
Keep notes focused on the facts used to compare the customer with the listed party. Review a past decision again when new evidence calls for it. Stop keeping input when the approved reason for it ends.
Frequently asked questions
Does a no-match result approve a new customer?
No. It finishes the selected list check without a possible match. Other required checks and your team’s account decision remain separate. Save the result with the reasons for that decision.
Can we add screening to our current onboarding application?
Yes. Use the screening API to send the facts you know and the sources you need. Handle matches, no matches, and errors on separate paths. Your team can review saved results in the included dashboard.
Should we fill missing customer details with estimates?
No. Use facts you can support and leave the rest unknown. A guessed birth date or nationality can mislead a reviewer and affect how names are compared.
Does a first customer check start ongoing monitoring?
No. Decide whether you need repeat checks and may keep the input for that purpose. Plan for each completed rescreen in your usage, and follow your policy for how long to keep the data.