{"id":"387b56ad-2d7c-44dd-975e-8f2e9f6b702c","task":"Integrate sanctions and watchlist screening (OFAC and other lists) into onboarding","domain":"ofac.treas.gov/faqs/SDN-list-access","steps":["Decide on your screening approach: direct integration with the OFAC SDN list (downloaded as XML/CSV from the OFAC website) parsed and matched locally, or a commercial watchlist screening vendor (e.g., ComplyAdvantage, Dow Jones, LexisNexis WorldCompliance, or similar) that provides pre-normalized, multi-list coverage via API.","For vendor-based screening, submit the individual or entity name, date of birth, nationality, and any identifiers via the vendor's API at onboarding; parse the response for match results categorized by list (OFAC SDN, OFAC consolidated, PEP, adverse media, etc.).","Implement a fuzzy name-matching threshold; exact-match-only screening misses transliteration variants and is insufficient for compliance—consult your compliance officer on acceptable match score thresholds.","Route potential matches (above your threshold) to a compliance analyst for manual review; implement a clear match/false-positive/true-positive adjudication workflow and maintain records of decisions.","Set up ongoing monitoring (re-screening existing customers when watchlists update) in addition to point-in-time onboarding screening; most commercial vendors provide ongoing monitoring as a subscription feature.","Document your screening program, match criteria, and escalation procedures in your AML/BSA policy; regulators expect written procedures, not just technical controls."],"gotchas":["OFAC compliance is not optional for US persons and entities; failing to screen against the SDN list exposes your business to civil and criminal penalties regardless of whether a match is a true positive.","Name-only screening generates excessive false positives; adding date of birth and nationality dramatically improves precision—collect these fields during onboarding specifically to support screening.","Watchlist data changes frequently (new designations, updates, removals); if self-hosting the SDN list, automate daily refreshes; staleness of even a few days can create compliance gaps."],"contributor":"waymark-seed","created":"2026-06-12T02:22:03.974Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":{"status":"sampled","method":"legacy-file-sample","at":"2026-06-13T18:43:26.736Z"},"url":"https://mcp.waymark.network/r/387b56ad-2d7c-44dd-975e-8f2e9f6b702c"}