Guides
Sanctions screening guides for your next task
Learn how to screen a customer, choose lists, review a match, connect the API, and keep ongoing relationships up to date with SanctionsKit.
A good place to start
Choose the question in front of you.
Run your first screening
Choose coverage, enter a subject, and review the result in SanctionsKit.
Follow the screening steps
Work through a match
Compare the evidence, investigate a potential match, and record your decision.
Follow the review process
Build your integration
Connect screening to your application with a practical API walkthrough.
Open the API guideScreening & AML basics
Run customer checks and connect results to your due-diligence process.
What is sanctions screening? A guide to your first check
Sanctions screening compares a person or business with selected sanctions lists. Learn what a result means and how to review it in SanctionsKit.
AML screening: how sanctions checks fit your customer process
Understand the sanctions step in AML screening, from customer details and source selection to case review, outside checks, and repeat screening.
Explore 7 more guides
KYC vs AML vs sanctions screening: a practical comparison
KYC establishes who a customer is. Sanctions screening checks selected lists. Learn how both fit into AML work without merging their results.
OFAC screening vs AML: what each check tells you
Learn how OFAC screening differs from a wider AML process and keep sanctions results, activity reviews, and business decisions separate.
Customer screening: run a check and keep records up to date
Learn how to screen a customer, review a possible match, save the evidence, and keep future checks linked to the right person or business.
Sanctions screening for small businesses: a practical workflow
Screen a supplier or customer without writing code. Learn how to choose coverage, review uncertain matches, keep evidence, and plan repeat checks.
AML case management: hand over a sanctions review clearly
Connect sanctions evidence and analyst decisions to an AML case while keeping identity findings, activity reviews, and approvals clear.
AML compliance software: sanctions screening selection checklist
Assess the sanctions-screening part of an AML software stack: test source scope, analyst review, approvals, evidence and repeat checks.
Sanctions screening software comparison: an evaluation checklist
Use this checklist to compare manual lookup, an internal build and SanctionsKit on source coverage, match review, evidence and operating cost.
Watchlists & coverage
Select available sources and interpret the findings your check returns.
What is watchlist screening? Choose lists and read the result
Learn what a watchlist check covers, how to choose available sources, and why each possible match needs its own source context and review.
Watchlists, sanctions and PEP screening: what is the difference?
Understand why sanctions records, other watchlists, and PEP findings need different evidence, review, and business decisions.
Explore 5 more guides
Global sanctions lists: choose the coverage your check needs
Map required authorities to available sanctions sources, keep underlying list identities clear, and verify which versions each check used.
Restricted-party screening: check trade parties and retain context
Screen buyers, consignees, and end users against selected trade sources while keeping goods, licensing, and shipment decisions separate.
PEP screening: definition, practical steps and an example
PEP screening checks whether a person holds a prominent public role. Learn how to verify identity, assess role evidence and record a review, with a worked example.
Adverse media vs sanctions screening: keep findings distinct
Compare news-based due diligence with sanctions list checks and record external media evidence without turning allegations into official findings.
Sanctions data freshness: check the source and screening versions
Distinguish source imports, active versions, and completed customer screenings so a recent timestamp does not hide an outdated check.
OFAC screening
Select OFAC coverage, run a screening, and record the review and evidence.
What is OFAC, and what does an OFAC check tell you?
Learn what OFAC does, how its sanctions lists fit into a customer check, and what to do with a possible match or a no-match result.
Who must comply with OFAC, and which parties should you check?
Understand the scope of OFAC compliance and build a party roster that keeps customer, company, owner and payment-recipient checks distinct.
Explore 10 more guides
OFAC screening requirements: a policy setup checklist
Turn approved OFAC screening requirements into a working process. Set sources, reviewer roles, outside checks, repeat screening and recordkeeping.
What is the OFAC SDN list? Names, identifiers and review
Understand the OFAC SDN list, the people and entities it covers, and how to compare a possible match with the identity you are screening.
OFAC SDN vs non-SDN lists: choose and review each source
Learn why OFAC SDN and non-SDN coverage are separate, how to select both when required, and why the underlying list matters during review.
OFAC's 50 Percent Rule: screen owners and record the review
See why a company name check can miss an ownership issue. Work through OFAC's 50 Percent Rule examples and record separate owner screenings.
How to run an OFAC check and understand the result
Find OFAC's official search tool, then learn how to run a saved check, review possible matches and keep the evidence in SanctionsKit.
How to perform an OFAC search and review the result
Follow an OFAC screening process from legal-name input and source selection to match review, saved evidence and repeat checks in SanctionsKit.
How to handle a possible OFAC match
Review an OFAC match by comparing identity facts, recording missing evidence and separating the match finding from the business decision.
OFAC batch screening: upload a list and review every result
Run bulk OFAC screening for customers or suppliers. Prepare a CSV, check each row, resolve matches, and keep failed checks visible.
OFAC recordkeeping: plan retention and retrieve screening evidence
Connect OFAC recordkeeping duties with screening retention, case evidence, original documents, holds and exports in SanctionsKit.
Move from OFAC list downloads to a screening API
Plan an OFAC API migration that preserves customer references, checks source availability and connects results to review, evidence and monitoring.
Industry workflows
Screen the parties in your transaction, onboarding, or relationship workflow.
How auto dealers can screen buyers for OFAC matches
Run an OFAC check for each required buyer, connect potential matches to the deal file, and handle purchaser changes before the next sales checkpoint.
Sanctions screening for crypto customer onboarding
Screen crypto customers by legal identity, connect candidates to account review and keep wallet analytics separate from the name-screening result.
Explore 8 more guides
How to connect fintech onboarding to sanctions screening
Connect account intake, API results, analyst review and ongoing monitoring while keeping incomplete sanctions checks visible in fintech onboarding.
Fintech AML screening API integration: requests, results and review
Implement the sanctions-screening step in fintech onboarding with a synthetic request, safe retries, retained results and a clear analyst handoff.
OFAC screening for insurance: policy and claim party checks
Learn how to check policy and claim parties, review possible OFAC matches, and keep the right records when a beneficiary or payee changes.
OFAC screening for lenders: check borrowers and loan parties
Screen required borrowers and guarantors, retain each result with the loan, and handle changed parties before funding and servicing handoffs.
Sanctions screening for MSBs: sender, recipient and review handoffs
Keep MSB transfer parties distinct, recover incomplete screening requests and connect retained results with reviewers and ongoing customer checks.
Sanctions screening for nonprofits: partner and grant checks
Check nonprofit partners and grant recipients, review possible sanctions matches, and keep separate approval and legal assessments linked to the program file.
How to screen real estate transaction parties for OFAC matches
Build a real estate party roster, screen each required identity, record separate ownership work and reconcile changes before the transaction handoff.
OFAC screening for title companies: a closing-file workflow
Connect required OFAC checks with the closing roster, resolve candidate matches and recheck changed payees before the settlement decision.
Matching & case review
Use the review queue, investigate candidates, and complete the case.
Sanctions case management: from possible match to decision
Learn what a sanctions review case contains, how to compare each candidate, and when outside checks and a second approval are needed.
Sanctions name matching: understand fuzzy matches and evidence
Learn how sanctions name matching finds candidates, why a score is not proof of identity, and which facts help a reviewer resolve a match.
Explore 10 more guides
Date of birth in sanctions screening: handle partial dates
Use a birth year, month or full date without inventing detail. Learn how to compare partial sanctions dates and explain what remains unknown.
Sanctions investigation: compare evidence and decide what follows
Investigate a possible sanctions match using the original record, reliable identity facts, and a clear handoff for any unresolved decision.
Sanctions screening false positives: how to review a match
Compare a possible sanctions match with reliable identity facts, explain your decision, and keep unresolved questions visible in SanctionsKit.
How to document a sanctions screening decision
Write a review note that explains the facts, missing evidence, identity decision, and business action, with examples for SanctionsKit cases.
Sanctions alert management: triage cases and failed checks
Sort sanctions matches, changed evidence, failed checks, and pending approvals into the right work queues, with clear owners and follow-up.
Sanctions screening audit trail: find and verify the evidence
Trace a sanctions decision from the original check to analyst notes, outside evidence, and approval. Learn which records and exports to use.
Sanctions screening policy: turn your process into clear controls
Set sources, review rules, matching sensitivity, outside checks, and monitoring in a versioned SanctionsKit policy your team can follow.
Sanctions screening thresholds: compare Standard and Focused
Evaluate matching sensitivity with the same labeled cases. Compare missed candidates and extra alerts before changing a SanctionsKit policy.
Sanctions screening false negatives: trace a missing match
Find why an expected sanctions candidate did not reach review by checking submitted facts, source versions, matching policy, and the handoff.
Sanctions screening testing: build useful acceptance cases
Test API results, failed checks, analyst review, monitoring, and evidence with synthetic cases, then record exactly what each test proves.
Ongoing monitoring
Enroll subjects, manage rescreening schedules, and handle new results.
Continuous sanctions monitoring: how repeat checks work
Learn how ongoing sanctions monitoring saves a subject, runs repeat checks, and sends changed evidence back to a reviewer in SanctionsKit.
Sanctions monitoring vs transaction monitoring: three different jobs
Compare customer rescreening, transaction-party screening, and activity monitoring, then keep their results and follow-up tasks clear.
Explore 3 more guides
Sanctions screening frequency: choose and verify a schedule
Set six-hour, daily, or weekly rescreening, estimate the workload, and check completed results instead of relying on a schedule alone.
Sanctions monitoring program: an operating checklist
Check that the right customers are enrolled, saved facts are current, scheduled screenings finish, and new evidence reaches a reviewer.
Sanctions monitoring webhooks: verify, store, and process events
Build a webhook receiver that checks signatures, handles duplicate deliveries, retrieves current evidence, and keeps human review separate.
API integration
Connect your application, prepare for production, and track API usage.
Sanctions screening API integration: a rollout checklist
Connect a sanctions screening API to real review work. Test result handling, retries, source failures, monitoring, and evidence before Production.
OFAC API: add sanctions screening to your application
Connect to the OFAC screening API, choose SDN or non-SDN coverage, and send matches to your review team. Start with a working sandbox example.
Explore 3 more guides
Integrate SanctionsKit with an AI coding agent and MCP
Connect your coding agent, sign in, and ask it to build a SanctionsKit integration. Start with these three steps.
Sanctions screening API cost: estimate your usage
Estimate sanctions screening API cost with worked examples for check volume and review time. Count completed checks, batch subjects and repeat monitoring.
Build vs buy sanctions screening: compare the ongoing work
Compare building a sanctions screening system with buying one, including data upkeep, matching tests, analyst review, evidence and operating cost.
Language tutorials
Call the SanctionsKit API from your backend using your preferred language.
OFAC API in Node.js: backend customer screening
Build a Node.js OFAC API check with native fetch. Keep keys on the server, retry one saved operation, and send SDN matches to review.
OFAC API in Python: customer screening workers
Run an OFAC API check in Python without extra packages. Use the standard library, preserve retry keys, and save SDN evidence for customer review.
Explore 23 more guides
OFAC API in PHP: onboarding with cURL
Add an OFAC API check to a PHP onboarding form with cURL. Keep the key on the server and link SDN results to the customer’s review.
OFAC API in Ruby: background screening jobs
Use the OFAC API in a Ruby background job with Net::HTTP. Save the screening ID and reuse the same operation key when retrying a customer check.
OFAC API in Go: screening services
Build a Go service for OFAC API checks using the standard HTTP client. Select SDN coverage, handle failed requests, and save results for review.
OFAC API in Rust: screening workers
Call the OFAC API from a Rust worker with a blocking HTTP client. Keep request failures separate from SDN matches and completed no-match results.
OFAC API in Swift: trusted backend screening
Connect a Swift backend to the OFAC API. Keep secret keys out of distributed apps and route SDN matches into a saved review record.
OFAC API in Java: customer onboarding
Add OFAC API checks to a Java onboarding service. Run the Java 21 example with Jackson, then save SDN results and handle retries without duplicate checks.
OFAC API in C# / .NET: ASP.NET onboarding
Connect an ASP.NET service to the OFAC API with C# and HttpClient. Run a sandbox check, preserve retry keys, and link SDN evidence to review.
UK sanctions API in Node.js: FCDO coverage and customer checks
Call the UK sanctions API from Node.js with native fetch. Select the FCDO UK Sanctions List and keep source references with each customer check.
UK sanctions API in Python: customer portfolio checks
Build a Python worker for UK sanctions API checks. Screen a customer portfolio against the FCDO list and retain partial dates for review.
UK sanctions API in Go: explicit source selection
Select the FCDO list in a Go UK sanctions API request. Keep the source ID explicit and treat missing required coverage as a failed check.
Canadian sanctions API in Python: autonomous list customer screening
Use the Canadian sanctions API in Python for the autonomous list. Check customer records and preserve the cited regulation with each possible match.
Canadian sanctions API in Swift: identity review in a backend
Add Canadian autonomous sanctions checks to a Swift backend. Keep API keys on the server and link source records to your identity review.
Canadian sanctions API in PHP: company screening
Screen suppliers with the Canadian sanctions API in PHP. Select the autonomous list and keep bilingual names and company IDs with the result.
Australian sanctions API in Node.js: onboarding with DFAT data
Add Australian sanctions API checks to Node.js onboarding. Select the DFAT list and retain its record references when aliases produce a possible match.
Australian sanctions API in Ruby: DFAT screening jobs
Run Australian sanctions API checks in a Ruby background job. Use DFAT source IDs and save alias evidence with the customer’s review.
Australian sanctions API in C# / .NET: DFAT data in ASP.NET
Call the Australian sanctions API from an ASP.NET service. Use C# to select DFAT coverage, inspect errors, and retain evidence for review.
U.S. CSL API in Java: screen shipment parties
Screen shipment parties through the U.S. CSL API in Java. Keep each candidate’s originating list and restriction with the review evidence.
U.S. CSL API in Rust: review component list evidence
Use the U.S. CSL API in a Rust trade-screening service. Preserve the component list behind each candidate so reviewers can check the actual restriction.
U.S. CSL API in Go: screen trading partners
Build a Go worker for U.S. CSL API checks on trading partners. Link results to local records and keep the originating list visible during review.
EU sanctions API in Node.js: customer screening
Use the EU sanctions API from Node.js to check financial-sanctions records. Preserve source IDs, partial dates and regulation references for review.
EU sanctions API in Python: customer screening workers
Build a Python worker for the EU sanctions API’s financial list. Save each screening ID and compare the listed party with known customer details.
UN sanctions API in Node.js: screen and review UN candidates
Use the UN sanctions API in Node.js for listed people and entities. Keep UN references and aliases with results; vessels need separate coverage.
UN sanctions API in Python: customer screening workers
Use the UN sanctions API in a Python worker for people and entities. Save screening IDs and preserve weak-alias labels for review.
Find a guide for the job in front of you
These guides explain how to use SanctionsKit, from a first name check to a connected review process. Pick the task you need to finish. Each walkthrough links to the workspace or exact API reference when you need it. Use invented people and businesses in Sandbox while learning the steps.
If the subject is new to you, start with what sanctions screening does. It explains possible matches, no-match results and failed checks before taking you through a supplier example. You can then choose a deeper guide with a clear idea of what the result means.
Connect your application
The API quickstart gets your first authenticated request working. Then choose a language tutorial for your application or connect an AI coding agent through MCP. The examples use synthetic records so you can test the flow without real customer data.
Use the rollout guide before switching to Production. It covers source selection, reviewer handoff, retries and errors. A working request is the first step; your application also needs to handle a possible match or a check that cannot finish.
Check a customer and choose the right lists
The customer-screening collection connects a check to onboarding and saved customer records. Use the OFAC collection for OFAC sources and results. The watchlist collection explains how lists differ and helps you choose available coverage.
Choose an industry workflow when your task starts with a deal, payment, loan or partner relationship. Those guides help you keep the parties and their records separate. Your approved process determines who needs a check and which sources belong in it.
Review a match and plan future checks
The case-review collection covers source evidence, decision notes, outside checks and approval. Start there when a possible match needs a person to investigate. The aim is a decision another reviewer can understand and trace to the facts.
The monitoring collection explains repeat checks, schedules, changed identities and webhooks. Use it for continuing relationships after the first screening. Check completed results as well as enabled schedules, so failed or outdated work has an owner.
Common questions
Which SanctionsKit guide should I read first?
Start with the introductory sanctions-screening guide if you need the concepts. Use the API quickstart for a first request, or customer screening for a dashboard walkthrough. Each points to the next task without requiring you to read the whole library.
Are the guide examples real customers or listed parties?
The practice examples are fictional and Sandbox uses synthetic records. Use them to learn product behavior. They do not establish that a source is live or prove matching quality for your real customer population.
Where do I find exact API fields and limits?
Use the documentation linked from the relevant walkthrough. Guides explain the task and decisions; the API references give the request fields, permissions and response formats needed to implement it.
Can I follow these guides without writing code?
Yes. Customer screening, case review, bulk uploads and monitoring have dashboard workflows. Choose those guides for team operations. The developer collection is available when you want to connect the same work to an application.