diff --git a/Dockerfile b/Dockerfile index e13abcc..a7cc337 100644 --- a/Dockerfile +++ b/Dockerfile @@ -37,6 +37,11 @@ COPY programs/ ./programs/ # Round 48 pSEO — sanctions evasion typologies and jurisdiction risk ratings COPY evasion/ ./evasion/ COPY risk-ratings/ ./risk-ratings/ +# Round 49 pSEO — regulatory framework and compliance deadlines +COPY regulations/ ./regulations/ +COPY deadlines/ ./deadlines/ +# how-to expansion pages (static fallthrough from _howto_page method) +COPY how-to/ ./how-to/ # Interactive shareable tools (compliance-check, ai-spend-optimizer) COPY tools/ ./tools/ # R17 UX system — shared design system across portfolio diff --git a/api.py b/api.py index da314de..60d2225 100644 --- a/api.py +++ b/api.py @@ -3597,7 +3597,7 @@ def do_GET(self): if _os.path.isfile(_rp): with open(_rp, "r", encoding="utf-8") as _fh: return self._serve_text(_fh.read(), "text/html; charset=utf-8") - for _pfx in ("/vs/", "/faq/", "/learn/", "/alternatives-to/", "/penalties/", "/guides/", "/checklists/", "/cost-of/", "/best/", "/templates/", "/stats/", "/redflags/", "/scenarios/", "/programs/", "/benchmarks/", "/evasion/", "/risk-ratings/"): + for _pfx in ("/vs/", "/faq/", "/learn/", "/alternatives-to/", "/penalties/", "/guides/", "/checklists/", "/cost-of/", "/best/", "/templates/", "/stats/", "/redflags/", "/scenarios/", "/programs/", "/benchmarks/", "/evasion/", "/risk-ratings/", "/regulations/", "/deadlines/"): if p.path.startswith(_pfx): _slug = p.path[len(_pfx):].split("?")[0].split("/")[0] if not _slug: @@ -6507,6 +6507,45 @@ def _sitemap_xml(self): ("/best/best-sanctions-screening-for-insurance", "weekly", "0.9", "Best Sanctions Screening For Insurance"), ("/best/best-sanctions-screening-for-ecommerce", "weekly", "0.9", "Best Sanctions Screening For Ecommerce"), ("/best/best-sanctions-screening-for-startups", "weekly", "0.9", "Best Sanctions Screening For Startups"), + ("/how-to/screen-beneficial-owners", "monthly", "0.8", "Screen Beneficial Owners"), + ("/how-to/implement-travel-rule", "monthly", "0.8", "Implement Travel Rule"), + ("/how-to/file-sar-for-sanctions", "monthly", "0.8", "File Sar For Sanctions"), + ("/how-to/conduct-customer-due-diligence", "monthly", "0.8", "Conduct Customer Due Diligence"), + ("/how-to/build-transaction-monitoring-system", "monthly", "0.8", "Build Transaction Monitoring System"), + ("/how-to/respond-to-ofac-subpoena", "monthly", "0.8", "Respond To Ofac Subpoena"), + ("/how-to/conduct-risk-assessment", "monthly", "0.8", "Conduct Risk Assessment"), + ("/how-to/train-staff-on-sanctions", "monthly", "0.8", "Train Staff On Sanctions"), + ("/how-to/handle-false-positive-alerts", "monthly", "0.8", "Handle False Positive Alerts"), + ("/how-to/conduct-enhanced-due-diligence", "monthly", "0.8", "Conduct Enhanced Due Diligence"), + ("/how-to/block-and-reject-transactions", "monthly", "0.8", "Block And Reject Transactions"), + ("/how-to/screen-crypto-transactions", "monthly", "0.8", "Screen Crypto Transactions"), + ("/how-to/conduct-ongoing-monitoring", "monthly", "0.8", "Conduct Ongoing Monitoring"), + ("/how-to/prepare-for-ofac-examination", "monthly", "0.8", "Prepare For Ofac Examination"), + ("/how-to/report-ofac-violations", "monthly", "0.8", "Report Ofac Violations"), + ("/how-to/manage-correspondent-banking-risk", "monthly", "0.8", "Manage Correspondent Banking Risk"), + ("/how-to/document-compliance-program", "monthly", "0.8", "Document Compliance Program"), + ("/regulations/fatf-recommendation-15", "monthly", "0.8", "FATF Recommendation 15"), + ("/regulations/fincen-cdd-rule", "monthly", "0.8", "FinCEN CDD Rule"), + ("/regulations/fincen-travel-rule", "monthly", "0.8", "FinCEN Travel Rule"), + ("/regulations/ofac-itsr", "monthly", "0.8", "OFAC ITSR"), + ("/regulations/ofac-russia-eo14024", "monthly", "0.8", "OFAC Russia Eo14024"), + ("/regulations/ofac-north-korea-nkspea", "monthly", "0.8", "OFAC North Korea NKSPEA"), + ("/regulations/eu-sanctions-regulation", "monthly", "0.8", "EU Sanctions Regulation"), + ("/regulations/uk-ofsi-regime", "monthly", "0.8", "UK OFSI Regime"), + ("/regulations/ofac-reporting-requirements", "monthly", "0.8", "OFAC Reporting Requirements"), + ("/regulations/fincen-aml-requirements", "monthly", "0.8", "FinCEN AML Requirements"), + ("/regulations/ofac-general-licenses", "monthly", "0.8", "OFAC General Licenses"), + ("/regulations/corporate-transparency-act", "monthly", "0.8", "Corporate Transparency Act"), + ("/deadlines/ofac-blocking-report-deadline", "monthly", "0.8", "OFAC Blocking Report Deadline"), + ("/deadlines/sar-filing-deadline", "monthly", "0.8", "SAR Filing Deadline"), + ("/deadlines/voluntary-disclosure-timeline", "monthly", "0.8", "Voluntary Disclosure Timeline"), + ("/deadlines/annual-report-deadline", "monthly", "0.8", "Annual Report Deadline"), + ("/deadlines/ctr-filing-deadline", "monthly", "0.8", "CTR Filing Deadline"), + ("/deadlines/sdb-recordkeeping-deadline", "monthly", "0.8", "SDB Recordkeeping Deadline"), + ("/deadlines/sdn-list-update-frequency", "monthly", "0.8", "SDN List Update Frequency"), + ("/deadlines/rescreening-frequency", "monthly", "0.8", "Rescreening Frequency"), + ("/deadlines/license-application-timeline", "monthly", "0.8", "License Application Timeline"), + ("/deadlines/audit-trail-retention", "monthly", "0.8", "Audit Trail Retention"), ] import datetime today = datetime.date.today().isoformat() @@ -12204,6 +12243,17 @@ def _howto_page(self, slug): } h = HOWTO.get(slug) if not h: + # Fall through to static file (Round 49 expansion pages) + import os as _os + _here = _os.path.dirname(_os.path.abspath(__file__)) + for _fp in ( + _os.path.join(_here, "how-to", slug, "index.html"), + _os.path.join("/home/agentmail/app", "how-to", slug, "index.html"), + ): + _fp = _os.path.normpath(_fp) + if _os.path.isfile(_fp): + with open(_fp, "r", encoding="utf-8") as _fh: + return self._serve_text(_fh.read(), "text/html; charset=utf-8") return _json(self, 404, {"error": "not found"}) today = "2026-07-13" steps_html = "".join(f'
  • Step {i+1}. {s}
    • ' for i, s in enumerate(h["steps"])) diff --git a/deadlines/annual-report-deadline/index.html b/deadlines/annual-report-deadline/index.html new file mode 100644 index 0000000..5c15e87 --- /dev/null +++ b/deadlines/annual-report-deadline/index.html @@ -0,0 +1,64 @@ + + + + + +OFAC annual blocked property report deadline | SanctionsAI + + + + + + + + + + + + + + + + +

    By SanctionsAI team · Updated 2026-08-09

    +

    OFAC annual blocked property report deadline

    +

    If you hold blocked property at any time during the year, you must file an annual report with OFAC by September 30.

    +

    The deadline

    +
    September 30 each year. Required if you held blocked property at any point during the reporting period (October 1 to September 30).
    +

    Who must file

    +

    Any person or entity that holds blocked property, including: banks with frozen accounts, financial institutions that blocked transactions, crypto platforms with frozen wallets, and any entity holding SDN property.

    +

    What to include

    + + + + + +
    InformationDetail
    Property descriptionType, amount, asset identifier (wallet address, account number)
    SDN referenceName and program of the designated person
    Date blockedWhen the property was originally blocked
    Current valueAs of September 30
    Interest earnedAny interest accrued during the year
    +

    Even if you hold no new blocked property: If you still hold property from prior years, you must file the annual report.

    +

    Screen your agent's next payment

    +

    Check any wallet, name, or entity against OFAC, EU, UN sanctions lists in real time.

    +Free wallet checker
    +

    Frequently Asked Questions

    +
    When is the OFAC annual report due?
    September 30 each year. Covers the reporting period October 1 to September 30.
    Must I file if I have no new blocked property?
    Yes, if you still hold blocked property from prior years. The annual report covers ALL property held, not just new blocks.
    What goes in the annual report?
    Property descriptions, SDN references, block dates, current values, and interest earned.
    Where do I file?
    Via the OFAC online reporting portal. The report is filed electronically.
    +
    +

    ← Back to deadlines · SanctionsAI

    + \ No newline at end of file diff --git a/deadlines/audit-trail-retention/index.html b/deadlines/audit-trail-retention/index.html new file mode 100644 index 0000000..d2cb411 --- /dev/null +++ b/deadlines/audit-trail-retention/index.html @@ -0,0 +1,62 @@ + + + + + +Sanctions compliance audit trail retention period | SanctionsAI + + + + + + + + + + + + + + + + +

    By SanctionsAI team · Updated 2026-08-09

    +

    Sanctions compliance audit trail retention period

    +

    Your audit trail is your compliance evidence. OFAC and FinCEN require 5-year retention of all sanctions-related records.

    +

    What constitutes an audit trail

    + + + + + +
    RecordContentsRetention
    Screening logSubject, timestamp, result, SDN list version, API response5 years
    Alert dispositionAlert details, reviewer, decision, rationale, timestamp5 years
    Blocking/rejection recordsTransaction details, SDN match, report filed5 years
    Training recordsAttendee, date, content, completion5 years
    Risk assessmentsDocument, date, approval, next review5 years
    +

    For AI agents

    +

    AI agent screening decisions must be logged with: (1) transaction identifier, (2) counterparty screened, (3) screening result (clean/blocked), (4) SDN list version, (5) timestamp, (6) agent identifier, (7) action taken (proceed/block).

    +
    SanctionsAI logging: Every API call is logged with timestamp, subject, result, and list version. The audit trail is available via the dashboard and exportable for compliance reviews.
    +

    Screen your agent's next payment

    +

    Check any wallet, name, or entity against OFAC, EU, UN sanctions lists in real time.

    +Free wallet checker
    +

    Frequently Asked Questions

    +
    How long must I keep sanctions screening records?
    5 years per OFAC and FinCEN requirements. This applies to screening logs, alert dispositions, blocking reports, and training records.
    What must an AI agent screening log contain?
    Transaction ID, counterparty, result, SDN list version, timestamp, agent ID, and action taken.
    Can audit trails be digital?
    Yes. Digital records are acceptable if they are complete, accurate, and readily retrievable. Most institutions use digital-only audit trails.
    What happens if I cannot produce records during an OFAC exam?
    Failure to maintain records is a sanctions violation. Civil penalties up to $356,571 per violation. Document any records that cannot be produced and explain why.
    +
    +

    ← Back to deadlines · SanctionsAI

    + \ No newline at end of file diff --git a/deadlines/ctr-filing-deadline/index.html b/deadlines/ctr-filing-deadline/index.html new file mode 100644 index 0000000..5376e3f --- /dev/null +++ b/deadlines/ctr-filing-deadline/index.html @@ -0,0 +1,62 @@ + + + + + +Currency Transaction Report (CTR) deadline | SanctionsAI + + + + + + + + + + + + + + + + +

    By SanctionsAI team · Updated 2026-08-09

    +

    Currency Transaction Report (CTR) deadline

    +

    Cash transactions exceeding $10,000 must be reported to FinCEN on a Currency Transaction Report (FinCEN Form 112) within 15 days.

    +

    The deadline

    +
    15 calendar days from the date of the transaction. File electronically via the FinCEN BSA E-Filing System.
    +

    When a CTR is required

    + + + + +
    TransactionCTR required?
    Single cash deposit of $10,001Yes
    Multiple cash deposits totaling $10,000+ in one day from same personYes (aggregation)
    Cash deposit of $9,999No
    Structured deposits ($5,000 + $5,000 same day, separate trips)Yes, AND file SAR for structuring
    +

    Structuring is a crime

    +

    Deliberately breaking up cash transactions to stay under $10,000 is called structuring, and it is a federal crime under 31 USC 5324. If you detect structuring, file BOTH a CTR AND a SAR.

    +

    Screen your agent's next payment

    +

    Check any wallet, name, or entity against OFAC, EU, UN sanctions lists in real time.

    +Free wallet checker
    +

    Frequently Asked Questions

    +
    What is the CTR filing deadline?
    15 calendar days from the date of the cash transaction exceeding $10,000.
    What cash transactions require a CTR?
    Any single cash transaction or aggregated same-day cash transactions from the same person exceeding $10,000.
    What is structuring?
    Deliberately breaking up cash transactions to stay under $10,000 to avoid CTR filing. It is a federal crime. File CTR AND SAR if detected.
    Do I file CTRs for crypto transactions?
    No. CTRs apply to physical currency. Crypto transactions are covered by SAR rules and Travel Rule requirements, not CTRs.
    +
    +

    ← Back to deadlines · SanctionsAI

    + \ No newline at end of file diff --git a/deadlines/license-application-timeline/index.html b/deadlines/license-application-timeline/index.html new file mode 100644 index 0000000..6539c83 --- /dev/null +++ b/deadlines/license-application-timeline/index.html @@ -0,0 +1,62 @@ + + + + + +OFAC specific license application timeline | SanctionsAI + + + + + + + + + + + + + + + + +

    By SanctionsAI team · Updated 2026-08-09

    +

    OFAC specific license application timeline

    +

    When you need OFAC authorization for a transaction that would otherwise be prohibited, you apply for a specific license. The process takes 6-12 months in most cases.

    +

    Typical timeline

    + + + + + +
    StageTimeline
    Application submissionDay 0
    Acknowledgment from OFAC2-4 weeks
    Review and questions (optional)2-6 months
    Decision6-12 months (complex cases longer)
    If approved: license issuedWithin weeks of decision
    +

    What to include in the application

    +

    Required: Applicant information, parties involved, transaction description, purpose and justification, why the transaction should be licensed, and relevant regulatory citations. For crypto: Wallet addresses, transaction hashes, blockchain network.

    +
    Do not proceed before approval: You cannot execute the prohibited transaction until OFAC issues the license. Proceeding before approval is a sanctions violation.
    +

    Screen your agent's next payment

    +

    Check any wallet, name, or entity against OFAC, EU, UN sanctions lists in real time.

    +Free wallet checker
    +

    Frequently Asked Questions

    +
    How long does OFAC license processing take?
    Typically 6-12 months. Complex cases can take longer. Simple humanitarian license requests may be faster.
    What should I include in a license application?
    Applicant info, parties, transaction description, purpose, justification, and regulatory citations. For crypto, include wallet addresses and transaction hashes.
    Can I proceed with the transaction while waiting?
    No. You cannot execute the prohibited transaction until OFAC issues the license. Proceeding is a violation.
    How do I check my application status?
    Contact OFAC's licensing division. Provide your application reference number. Do not contact about status before the acknowledgment period (2-4 weeks).
    +
    +

    ← Back to deadlines · SanctionsAI

    + \ No newline at end of file diff --git a/deadlines/ofac-blocking-report-deadline/index.html b/deadlines/ofac-blocking-report-deadline/index.html new file mode 100644 index 0000000..44e3608 --- /dev/null +++ b/deadlines/ofac-blocking-report-deadline/index.html @@ -0,0 +1,62 @@ + + + + + +OFAC blocking report filing deadline | SanctionsAI + + + + + + + + + + + + + + + + +

    By SanctionsAI team · Updated 2026-08-09

    +

    OFAC blocking report filing deadline

    +

    When you block a transaction involving OFAC-designated property, you must file a blocking report within 10 business days. Missing this deadline is itself a sanctions violation.

    +

    The deadline

    +
    10 business days from the date you block the transaction. No extensions are routinely granted.
    +

    What triggers the deadline

    + + + + +
    TriggerActionDeadline
    SDN wallet match in crypto paymentBlock funds, file report10 business days
    SDN name match in wire transferBlock funds, file report10 business days
    Payment to comprehensively sanctioned jurisdictionBlock funds, file report10 business days
    Property of SDN discovered in accountBlock property, file report10 business days
    +

    How to file

    +

    File electronically via the OFAC reporting portal. Include: blocking date, SDN entry reference, property description, value, account information, and reason for blocking.

    +

    Screen your agent's next payment

    +

    Check any wallet, name, or entity against OFAC, EU, UN sanctions lists in real time.

    +Free wallet checker
    +

    Frequently Asked Questions

    +
    How many days do I have to file a blocking report?
    10 business days from the date of blocking. File via OFAC online portal.
    What if I miss the blocking report deadline?
    Failure to file is itself a sanctions violation. File immediately and document the delay.
    What information goes in a blocking report?
    Blocking date, SDN entry, property description, value, account info, and reason for blocking.
    Do I need to file for every blocked transaction?
    Yes. Each blocked transaction requires a separate blocking report within 10 business days.
    +
    +

    ← Back to deadlines · SanctionsAI

    + \ No newline at end of file diff --git a/deadlines/rescreening-frequency/index.html b/deadlines/rescreening-frequency/index.html new file mode 100644 index 0000000..2c2e04b --- /dev/null +++ b/deadlines/rescreening-frequency/index.html @@ -0,0 +1,60 @@ + + + + + +Customer rescreening frequency for sanctions compliance | SanctionsAI + + + + + + + + + + + + + + + + +

    By SanctionsAI team · Updated 2026-08-09

    +

    Customer rescreening frequency for sanctions compliance

    +

    Onboarding screening is not enough. The SDN list changes constantly. Here is the recommended rescreening frequency by risk tier.

    +

    Risk-based rescreening schedule

    + + + +
    Risk tierRescreening frequencyCustomer profile
    HighDaily (batch against updated SDN)High-risk jurisdiction, PEPs, complex structures
    MediumWeekly or bi-weeklyModerate-risk profiles, standard customers
    LowMonthly or on SDN updatesLow-risk individuals, domestic retail
    +

    Event-triggered rescreening

    +

    Beyond scheduled rescreening, rescreen immediately when: (1) major SDN list update occurs, (2) customer profile changes (new ownership, new geography), (3) adverse media alert, (4) regulatory change affecting the customer's industry or geography.

    +
    Best practice: Daily batch rescreening of ALL customers against the updated SDN list. This catches every new designation regardless of risk tier. Use an automated API for this.
    +

    Screen your agent's next payment

    +

    Check any wallet, name, or entity against OFAC, EU, UN sanctions lists in real time.

    +Free wallet checker
    +

    Frequently Asked Questions

    +
    How often should I rescreen customers?
    Daily batch against updated SDN list for all customers. Event-triggered rescreening for major SDN updates and customer profile changes.
    Should low-risk customers be rescreened?
    Yes. At minimum monthly, or when SDN updates occur. All customers should be in daily batch rescreening for best practice.
    What triggers immediate rescreening?
    Major SDN list updates, customer profile changes, adverse media alerts, and regulatory changes.
    Can rescreening be automated?
    Yes. Daily batch rescreening via API eliminates manual work and ensures no customer is missed.
    +
    +

    ← Back to deadlines · SanctionsAI

    + \ No newline at end of file diff --git a/deadlines/sar-filing-deadline/index.html b/deadlines/sar-filing-deadline/index.html new file mode 100644 index 0000000..b1fa5ce --- /dev/null +++ b/deadlines/sar-filing-deadline/index.html @@ -0,0 +1,60 @@ + + + + + +SAR filing deadline for sanctions violations | SanctionsAI + + + + + + + + + + + + + + + + +

    By SanctionsAI team · Updated 2026-08-09

    +

    SAR filing deadline for sanctions violations

    +

    When you detect suspicious activity potentially related to sanctions violations, you must file a SAR with FinCEN within 30 calendar days.

    +

    The deadlines

    + + + +
    ScenarioDeadline
    Suspect identified30 calendar days from detection
    No suspect identified60 calendar days from detection
    Continuing activity (subject already reported)Every 90 days until activity stops
    +
    Start the clock: The deadline starts when the institution detects the suspicious activity, not when a person reviews it. Automated detection starts the clock immediately.
    +

    SAR vs. OFAC blocking report

    +

    These are separate filings. A SAR goes to FinCEN for suspicious activity reporting. An OFAC blocking report goes to OFAC for blocked property. If you block a transaction AND it is suspicious, file both.

    +

    Screen your agent's next payment

    +

    Check any wallet, name, or entity against OFAC, EU, UN sanctions lists in real time.

    +Free wallet checker
    +

    Frequently Asked Questions

    +
    What is the SAR filing deadline?
    30 calendar days from detection of suspicious activity. 60 days if no suspect identified.
    When does the SAR clock start?
    When the institution detects the suspicious activity, even if no human has reviewed it yet. Automated detection starts the clock.
    Do I file a SAR AND a blocking report?
    They are separate. SAR goes to FinCEN. Blocking report goes to OFAC for blocked property. File both if applicable.
    What if suspicious activity continues?
    File continuing activity SARs every 90 days until the activity stops.
    +
    +

    ← Back to deadlines · SanctionsAI

    + \ No newline at end of file diff --git a/deadlines/sdb-recordkeeping-deadline/index.html b/deadlines/sdb-recordkeeping-deadline/index.html new file mode 100644 index 0000000..a7869a0 --- /dev/null +++ b/deadlines/sdb-recordkeeping-deadline/index.html @@ -0,0 +1,61 @@ + + + + + +OFAC recordkeeping requirements and retention | SanctionsAI + + + + + + + + + + + + + + + + +

    By SanctionsAI team · Updated 2026-08-09

    +

    OFAC recordkeeping requirements and retention

    +

    OFAC requires retaining sanctions-related records for 5 years. This includes screening results, blocking reports, transaction records, and compliance documentation.

    +

    5-year retention requirement

    + + + + + + +
    Record typeRetention periodWhy
    Sanctions screening results5 yearsAudit trail for regulators
    Blocking and rejection reports5 yearsEvidence of compliance
    Transaction records (sanctions-relevant)5 yearsInvestigation evidence
    Customer due diligence records5 years (FinCEN)BSA/AML compliance
    Training records5 yearsCompliance evidence
    Risk assessments and audits5 yearsProgram evidence
    +
    Format: Records can be digital or paper but must be retrievable within a reasonable time. OFAC may request records during examinations or investigations.

    +

    Screen your agent's next payment

    +

    Check any wallet, name, or entity against OFAC, EU, UN sanctions lists in real time.

    +Free wallet checker
    +

    Frequently Asked Questions

    +
    How long must I keep OFAC screening records?
    5 years. This includes the screening result, timestamp, subject screened, and SDN list version used.
    What format should records be in?
    Digital or paper, but must be readily retrievable. OFAC may request records during examinations.
    Do I need to keep records of non-matches?
    Yes. Keep records of all screening results including non-matches. This demonstrates comprehensive screening coverage.
    What if I cannot produce records when requested?
    Failure to maintain records is a sanctions violation. Civil penalties up to $356,571 per violation.
    +
    +

    ← Back to deadlines · SanctionsAI

    + \ No newline at end of file diff --git a/deadlines/sdn-list-update-frequency/index.html b/deadlines/sdn-list-update-frequency/index.html new file mode 100644 index 0000000..f951482 --- /dev/null +++ b/deadlines/sdn-list-update-frequency/index.html @@ -0,0 +1,61 @@ + + + + + +OFAC SDN list update frequency and monitoring | SanctionsAI + + + + + + + + + + + + + + + + +

    By SanctionsAI team · Updated 2026-08-09

    +

    OFAC SDN list update frequency and monitoring

    +

    The OFAC SDN list is updated frequently, sometimes multiple times per week. Compliance teams must monitor updates and rescreen customers when new designations occur.

    +

    Update frequency

    + + + + +
    Update typeFrequencyExample
    New designationsMultiple per weekGeopolitical events, enforcement actions
    Removals (delisting)OccasionalNegotiated settlements, regime changes
    Address/identifier updatesPeriodicNew crypto wallet addresses added
    Alias updatesPeriodicNew known aliases for existing SDNs
    +

    How to monitor

    +

    1. Subscribe to OFAC's email update service. 2. Download the updated SDN list daily. 3. Run batch screening against all existing customers. 4. Investigate any new matches within 24 hours. 5. Document the monitoring process.

    +
    Automated monitoring: Use an API like SanctionsAI that automatically uses the latest SDN list. This eliminates the need for manual list downloads.
    +

    Screen your agent's next payment

    +

    Check any wallet, name, or entity against OFAC, EU, UN sanctions lists in real time.

    +Free wallet checker
    +

    Frequently Asked Questions

    +
    How often is the OFAC SDN list updated?
    Frequently, sometimes multiple times per week. Major designations often follow geopolitical events.
    How do I monitor SDN list changes?
    Subscribe to OFAC email updates. Download the updated list daily. Run batch screening against all customers.
    How quickly must I rescreen after updates?
    Within 24 hours for high-risk customers. Automated rescreening on list updates is best practice.
    Can automated API screening handle updates?
    Yes. SanctionsAI automatically uses the latest SDN list. Every API call screens against the current list, eliminating manual update gaps.
    +
    +

    ← Back to deadlines · SanctionsAI

    + \ No newline at end of file diff --git a/deadlines/voluntary-disclosure-timeline/index.html b/deadlines/voluntary-disclosure-timeline/index.html new file mode 100644 index 0000000..3bdba34 --- /dev/null +++ b/deadlines/voluntary-disclosure-timeline/index.html @@ -0,0 +1,61 @@ + + + + + +OFAC voluntary self-disclosure timeline | SanctionsAI + + + + + + + + + + + + + + + + +

    By SanctionsAI team · Updated 2026-08-09

    +

    OFAC voluntary self-disclosure timeline

    +

    Voluntary self-disclosure to OFAC has no fixed deadline, but speed matters. Disclosing before OFAC discovers the violation independently maximizes penalty mitigation.

    +

    The disclosure timeline

    + + + + +
    StageTimelineAction
    DiscoveryDay 0Identify potential violation
    Initial notificationASAP (days, not weeks)Notify OFAC of apparent violation
    Full reportWithin 180 daysSubmit detailed report with findings
    RemediationOngoingImplement corrective measures
    +

    What makes disclosure 'voluntary'

    +

    To qualify as voluntary: (1) OFAC must not already know about the violation, (2) the disclosure must be made before any OFAC inquiry, subpoena, or investigation, (3) the disclosure must be complete and truthful.

    +
    Penalty impact: Voluntary self-disclosure creates a presumption of mitigation. Combined with cooperation and remediation, penalties can be reduced by 50% or more.
    +

    Screen your agent's next payment

    +

    Check any wallet, name, or entity against OFAC, EU, UN sanctions lists in real time.

    +Free wallet checker
    +

    Frequently Asked Questions

    +
    Is there a deadline for voluntary self-disclosure?
    No fixed deadline, but disclosing ASAP maximizes penalty mitigation. A full report should follow within 180 days of initial notification.
    What makes a disclosure 'voluntary'?
    OFAC must not already know about the violation, no inquiry or subpoena must be pending, and the disclosure must be complete and truthful.
    How much does voluntary disclosure reduce penalties?
    It creates a presumption of mitigation. Combined with cooperation and remediation, penalties can be reduced by 50% or more.
    Should I disclose through counsel?
    Yes. Always use experienced OFAC counsel for voluntary self-disclosure. Counsel manages privilege and strategy.
    +
    +

    ← Back to deadlines · SanctionsAI

    + \ No newline at end of file diff --git a/how-to/block-and-reject-transactions/index.html b/how-to/block-and-reject-transactions/index.html new file mode 100644 index 0000000..df59770 --- /dev/null +++ b/how-to/block-and-reject-transactions/index.html @@ -0,0 +1,61 @@ + + + + + +How to block and reject OFAC-prohibited transactions | SanctionsAI + + + + + + + + + + + + + + + + +

    By SanctionsAI team · Updated 2026-08-09

    +

    How to block and reject OFAC-prohibited transactions

    +

    When sanctions screening identifies a match, you must either block or reject the transaction. The difference matters.

    +

    Block vs. Reject

    + + +
    ActionWhenWhat happensReporting
    BlockSDN property or sanctioned jurisdictionFunds frozen in blocked account10 business days
    RejectCannot process, no blocked propertyFunds returned to sender10 business days
    +

    When to block

    +

    Transaction involves SDN-listed person or comprehensively sanctioned jurisdiction (Iran, North Korea, Syria, Cuba, Crimea). Funds placed in blocked interest-bearing account.

    +

    Blocking procedure

    +

    Step 1: Freeze funds immediately. Step 2: Notify customer (without SAR tipping off). Step 3: File OFAC blocking report within 10 business days. Step 4: File annual report by September 30. Step 5: Maintain records 5 years.

    +
    Do NOT release blocked funds without specific OFAC authorization.
    +

    Screen your agent's next payment

    +

    Check any wallet, name, or entity against OFAC, EU, UN sanctions lists in real time.

    +Free wallet checker
    +

    Frequently Asked Questions

    +
    What is blocking vs. rejecting?
    Blocking freezes funds (SDN matches). Rejecting returns funds (cannot process but no blocked property).
    When must I file a blocking report?
    Within 10 business days of blocking. Annual report by September 30.
    Can I release blocked funds?
    Only with specific OFAC authorization (a license).
    What happens to interest on blocked accounts?
    Interest accrues to the blocked account. Funds remain blocked until OFAC authorizes release.
    +
    +

    ← Back to how-to · SanctionsAI

    + \ No newline at end of file diff --git a/how-to/build-transaction-monitoring-system/index.html b/how-to/build-transaction-monitoring-system/index.html new file mode 100644 index 0000000..48a7c56 --- /dev/null +++ b/how-to/build-transaction-monitoring-system/index.html @@ -0,0 +1,65 @@ + + + + + +How to build a sanctions transaction monitoring system | SanctionsAI + + + + + + + + + + + + + + + + +

    By SanctionsAI team · Updated 2026-08-09

    +

    How to build a sanctions transaction monitoring system

    +

    A transaction monitoring system screens every payment against sanctions lists in real-time and generates alerts for review.

    +

    Core components

    + + + + +
    ComponentFunction
    Sanctions screening engineMatches names/wallets against SDN
    Transaction loggerRecords every screened transaction
    Alert queueRoutes flagged transactions to reviewers
    ReportingGenerates compliance reports
    +

    Step 1: Define screening rules

    +

    Every transaction triggers: counterparty name screening, wallet address screening, jurisdiction check, pattern detection.

    +

    Step 2: Implement real-time API integration

    +

    Insert screening API call before transaction execution. Target latency: sub-500ms.

    +

    Step 3: Design the alert workflow

    +

    Confirmed SDN match (block), potential match (1-hour review), jurisdiction flag (24-hour review), pattern alert (48-hour investigate).

    +
    False positives: Expect 90%+ initially. Tune rules by analyzing historical alerts. Never disable a rule without documented approval.
    +

    Screen your agent's next payment

    +

    Check any wallet, name, or entity against OFAC, EU, UN sanctions lists in real time.

    +Free wallet checker
    +

    Frequently Asked Questions

    +
    How fast must sanctions screening be?
    Real-time transaction screening should complete in under 500ms.
    What is the false positive rate?
    Initial: 90%+. With tuning: 5-10%.
    How long must monitoring records be kept?
    FinCEN requires 5 years. OFAC recommends 5 years.
    Can AI agents do transaction monitoring?
    AI can screen and flag. Alert disposition requires human review.
    +
    +

    ← Back to how-to · SanctionsAI

    + \ No newline at end of file diff --git a/how-to/conduct-customer-due-diligence/index.html b/how-to/conduct-customer-due-diligence/index.html new file mode 100644 index 0000000..5368fb0 --- /dev/null +++ b/how-to/conduct-customer-due-diligence/index.html @@ -0,0 +1,64 @@ + + + + + +How to conduct customer due diligence (CDD) for sanctions | SanctionsAI + + + + + + + + + + + + + + + + +

    By SanctionsAI team · Updated 2026-08-09

    +

    How to conduct customer due diligence (CDD) for sanctions

    +

    The FinCEN CDD Rule (31 CFR 1010.230) requires financial institutions to identify and verify beneficial owners, understand customer relationships, and monitor for suspicious activity.

    +

    The four pillars of CDD

    + + + + +
    PillarRequirementSanctions connection
    Customer identification (CIP)Verify customer identityScreen against OFAC SDN at onboarding
    Beneficial ownershipIdentify 25%+ ownersScreen each beneficial owner against SDN
    Understand relationshipProfile expected activityIdentify sanctions risk factors
    Ongoing monitoringMonitor transactionsRescreen against updated SDN list
    +

    Step-by-step process

    +

    Step 1: Collect customer identity documents.

    +

    Step 2: Screen customer name and all beneficial owners against OFAC SDN, EU, UN lists.

    +

    Step 3: Assign a risk rating based on customer type, geography, and business model.

    +

    Step 4: Set up ongoing monitoring: transaction screening, periodic rescreening, alert investigation.

    +
    For AI agents: Automate CDD by calling SanctionsAI at onboarding and before each transaction.
    +

    Screen your agent's next payment

    +

    Check any wallet, name, or entity against OFAC, EU, UN sanctions lists in real time.

    +Free wallet checker
    +

    Frequently Asked Questions

    +
    What is the FinCEN CDD Rule?
    31 CFR 1010.230 requires identifying and verifying beneficial owners, understanding customer relationships, and conducting ongoing monitoring.
    How often should I rescreen customers?
    High-risk: quarterly. Medium: semi-annually. Low: annually. All after major SDN updates.
    What is enhanced due diligence (EDD)?
    EDD applies to high-risk customers: additional verification, source of funds, adverse media, senior approval.
    Can CDD be automated?
    Yes. Identity verification, sanctions screening, and risk rating can be automated via APIs.
    +
    +

    ← Back to how-to · SanctionsAI

    + \ No newline at end of file diff --git a/how-to/conduct-enhanced-due-diligence/index.html b/how-to/conduct-enhanced-due-diligence/index.html new file mode 100644 index 0000000..55013ec --- /dev/null +++ b/how-to/conduct-enhanced-due-diligence/index.html @@ -0,0 +1,61 @@ + + + + + +How to conduct enhanced due diligence (EDD) | SanctionsAI + + + + + + + + + + + + + + + + +

    By SanctionsAI team · Updated 2026-08-09

    +

    How to conduct enhanced due diligence (EDD)

    +

    EDD applies to high-risk customers: PEPs, high-risk jurisdictions, complex ownership structures.

    +

    When EDD is required

    + +

    EDD steps beyond standard CDD

    + + + + + +
    StepActionDocumentation
    Source of fundsVerify where money comes fromBank statements, tax returns
    Source of wealthVerify how wealth accumulatedBusiness records, salary history
    Adverse mediaSearch for negative newsMedia search results
    Senior approvalCompliance officer approvesSigned approval
    Enhanced monitoringMonthly reviewMonthly review logs
    +

    Screen your agent's next payment

    +

    Check any wallet, name, or entity against OFAC, EU, UN sanctions lists in real time.

    +Free wallet checker
    +

    Frequently Asked Questions

    +
    When is EDD required?
    For PEPs, high-risk jurisdictions, complex structures, cash-intensive businesses, adverse media matches.
    What is the difference between CDD and EDD?
    EDD adds source of funds verification, adverse media, senior approval, enhanced monitoring.
    Who approves EDD customers?
    A senior compliance officer must approve. Board notification for highest-risk.
    How often should I monitor EDD customers?
    Monthly transaction review, more frequent rescreening, immediate alert investigation.
    +
    +

    ← Back to how-to · SanctionsAI

    + \ No newline at end of file diff --git a/how-to/conduct-ongoing-monitoring/index.html b/how-to/conduct-ongoing-monitoring/index.html new file mode 100644 index 0000000..2205cbc --- /dev/null +++ b/how-to/conduct-ongoing-monitoring/index.html @@ -0,0 +1,60 @@ + + + + + +How to set up ongoing sanctions monitoring | SanctionsAI + + + + + + + + + + + + + + + + +

    By SanctionsAI team · Updated 2026-08-09

    +

    How to set up ongoing sanctions monitoring

    +

    Onboarding screening is not enough. The SDN list updates frequently, and a clean customer today may be designated tomorrow.

    +

    Three monitoring layers

    + + + +
    LayerFrequencyWhat to monitor
    Customer rescreeningDaily batchName and entity screening vs updated SDN
    Transaction screeningReal-timeCounterparty name, wallet, jurisdiction
    Periodic reviewAnnual (minimum)Full CDD refresh, risk rating update
    +

    SDN list update process

    +

    OFAC updates frequently. Subscribe to OFAC email updates. On new designations: download updated list, batch screen all customers, investigate matches, block accounts.

    +
    API integration: SanctionsAI provides real-time screening. Insert before transaction execution. Log all results.
    +

    Screen your agent's next payment

    +

    Check any wallet, name, or entity against OFAC, EU, UN sanctions lists in real time.

    +Free wallet checker
    +

    Frequently Asked Questions

    +
    How often is the SDN list updated?
    Frequently, sometimes daily. Subscribe to OFAC email updates.
    How often should I rescreen customers?
    Daily batch against updated SDN. More frequently for high-risk.
    Can I automate ongoing monitoring?
    Yes. Batch screening, real-time transaction screening, automated alerts. Alert disposition needs humans.
    What happens when a customer is newly designated?
    Block accounts, freeze transactions, file blocking report within 10 business days.
    +
    +

    ← Back to how-to · SanctionsAI

    + \ No newline at end of file diff --git a/how-to/conduct-risk-assessment/index.html b/how-to/conduct-risk-assessment/index.html new file mode 100644 index 0000000..9064553 --- /dev/null +++ b/how-to/conduct-risk-assessment/index.html @@ -0,0 +1,65 @@ + + + + + +How to conduct a sanctions risk assessment | SanctionsAI + + + + + + + + + + + + + + + + +

    By SanctionsAI team · Updated 2026-08-09

    +

    How to conduct a sanctions risk assessment

    +

    A sanctions risk assessment identifies your organization's exposure and prioritizes compliance controls. OFAC expects every regulated entity to conduct one.

    +

    Risk categories

    + + + + +
    CategoryRisk factorsScoring
    GeographicCustomer locations, payment routes1-5
    CustomerCustomer types, PEPs, high-risk industries1-5
    Product/ServiceWire transfers, crypto, trade finance1-5
    TransactionVolume, velocity, cross-border %1-5
    +

    Process

    +

    Step 1: Map all products, services, customer segments, and markets.

    +

    Step 2: Score each category (inherent risk before controls).

    +

    Step 3: Assess existing control effectiveness.

    +

    Step 4: Calculate residual risk (inherent minus controls).

    +

    Step 5: Document gaps and create remediation plan.

    +
    OFAC expectation: Risk assessments should be documented, reviewed annually, and updated for business changes.
    +

    Screen your agent's next payment

    +

    Check any wallet, name, or entity against OFAC, EU, UN sanctions lists in real time.

    +Free wallet checker
    +

    Frequently Asked Questions

    +
    How often should I conduct a risk assessment?
    Annually at minimum, and when significant business changes occur.
    What is residual risk?
    Inherent risk minus control effectiveness. Shows actual exposure after mitigations.
    What if residual risk is high?
    Implement additional controls: enhanced screening, more monitoring, additional training.
    Does a risk assessment protect against penalties?
    A documented assessment with remediation plan demonstrates good-faith compliance. OFAC considers it mitigating.
    +
    +

    ← Back to how-to · SanctionsAI

    + \ No newline at end of file diff --git a/how-to/document-compliance-program/index.html b/how-to/document-compliance-program/index.html new file mode 100644 index 0000000..9ba8e45 --- /dev/null +++ b/how-to/document-compliance-program/index.html @@ -0,0 +1,62 @@ + + + + + +How to document your OFAC compliance program | SanctionsAI + + + + + + + + + + + + + + + + +

    By SanctionsAI team · Updated 2026-08-09

    +

    How to document your OFAC compliance program

    +

    An undocumented compliance program is not a compliance program. OFAC expects written policies, procedures, and evidence of execution.

    +

    The five pillars

    + + + + + +
    PillarDocumentation
    Management commitmentBoard-approved policy, designated officer, budget
    Risk assessmentDocumented, updated annually
    Internal controlsScreening procedures, blocking procedures, escalation
    Testing and auditIndependent audit report, findings, remediation
    TrainingCurriculum, completion records, content updates
    +

    Document hierarchy

    +

    Tier 1: Policy (board-approved, high-level). Tier 2: Procedures (operational, detailed). Tier 3: Records (evidence of execution).

    +
    For AI agents: Document API integration architecture, screening logic, audit trail format, and escalation triggers.
    +

    Screen your agent's next payment

    +

    Check any wallet, name, or entity against OFAC, EU, UN sanctions lists in real time.

    +Free wallet checker
    +

    Frequently Asked Questions

    +
    What are the five pillars?
    Management commitment, risk assessment, internal controls, testing/audit, and training.
    How often should policies be updated?
    Annually and when significant changes occur. Document the review.
    What is the compliance officer's responsibility?
    Owns the OFAC program: risk assessment, procedures, screening oversight, training, reporting.
    How long must records be kept?
    OFAC recommends 5 years. FinCEN requires 5 years for SAR/BSA records.
    +
    +

    ← Back to how-to · SanctionsAI

    + \ No newline at end of file diff --git a/how-to/file-sar-for-sanctions/index.html b/how-to/file-sar-for-sanctions/index.html new file mode 100644 index 0000000..da778d2 --- /dev/null +++ b/how-to/file-sar-for-sanctions/index.html @@ -0,0 +1,65 @@ + + + + + +How to file a SAR for sanctions violations | SanctionsAI + + + + + + + + + + + + + + + + +

    By SanctionsAI team · Updated 2026-08-09

    +

    How to file a SAR for sanctions violations

    +

    If you suspect a sanctions violation, you must file a Suspicious Activity Report (SAR) with FinCEN within 30 days.

    +

    TL;DR: A sanctions-related SAR is filed when you detect a transaction involving a sanctioned entity, jurisdiction, or evasion pattern. Deadline: 30 days from detection.

    +

    Step 1: Identify the suspicious activity

    +

    Red flags: transactions involving OFAC-designated addresses or names, payments through sanctioned jurisdictions, structured payments, shell company patterns.

    +

    Step 2: Gather supporting documentation

    + + + +
    Information neededDetails
    Subject informationName, address, DOB, ID, wallet address
    Transaction detailsAmount, date, method, counterparties
    Sanctions screening resultOFAC match details, match date
    +

    Step 3: File the SAR within 30 days

    +

    File via the FinCEN BSA E-Filing System (FinCEN Form 111). The narrative is the most important part.

    +

    Step 4: Notify OFAC if blocked transaction

    +

    If the transaction involves blocked property (SDN match), also file OFAC blocking report within 10 business days and annual report by September 30.

    +
    Important: SARs are confidential. Tipping off a SAR subject is a federal crime under 31 USC 5318.
    +

    Screen your agent's next payment

    +

    Check any wallet, name, or entity against OFAC, EU, UN sanctions lists in real time.

    +Free wallet checker
    +

    Frequently Asked Questions

    +
    When must I file a SAR for a sanctions violation?
    Within 30 calendar days of initial detection. If no suspect is identified, 60 days.
    Can I tell the customer I filed a SAR?
    No. Tipping off is a federal crime under 31 USC 5318.
    Do I file a SAR AND an OFAC blocking report?
    They are separate. SAR goes to FinCEN. Blocking report goes to OFAC for SDN matches.
    Can AI agents automate SAR filing?
    AI can gather data and pre-populate fields, but human review and certification are required.
    +
    +

    ← Back to how-to · SanctionsAI

    + \ No newline at end of file diff --git a/how-to/handle-false-positive-alerts/index.html b/how-to/handle-false-positive-alerts/index.html new file mode 100644 index 0000000..636fb22 --- /dev/null +++ b/how-to/handle-false-positive-alerts/index.html @@ -0,0 +1,63 @@ + + + + + +How to handle false positive sanctions alerts | SanctionsAI + + + + + + + + + + + + + + + + +

    By SanctionsAI team · Updated 2026-08-09

    +

    How to handle false positive sanctions alerts

    +

    False positives account for 90%+ of sanctions screening alerts. A structured workflow ensures you dismiss them correctly.

    +

    Alert disposition workflow

    + + + + +
    Alert typeReview deadlineDisposition criteria
    Exact SDN matchImmediate (block)Treat as true positive until proven otherwise
    Name similarity1 hourCompare DOB, address, nationality, ID
    Fuzzy match4 hoursCompare all identifying fields
    Jurisdiction flag24 hoursVerify route and counterparty location
    +

    False positive criteria

    +

    Document WHY the alert does not match: different DOB, different nationality, different address, different occupation, entity type mismatch.

    +

    Tuning to reduce false positives

    +

    Calibrate fuzzy match thresholds, build exclusion lists for common names, add secondary identifiers, segment by risk tier.

    +
    Never auto-dismiss: Every alert must be reviewed by a human. Auto-dismissal is a top OFAC enforcement finding.
    +

    Screen your agent's next payment

    +

    Check any wallet, name, or entity against OFAC, EU, UN sanctions lists in real time.

    +Free wallet checker
    +

    Frequently Asked Questions

    +
    What is the false positive rate?
    Initial: 90%+. With tuning: 5-10%.
    Can I auto-dismiss false positives?
    No. Every alert must be reviewed and documented by a human.
    How do I reduce false positives?
    Calibrate thresholds, add secondary identifiers, build exclusion lists, segment by risk.
    How long must I keep alert records?
    At least 5 years per OFAC and FinCEN requirements.
    +
    +

    ← Back to how-to · SanctionsAI

    + \ No newline at end of file diff --git a/how-to/implement-travel-rule/index.html b/how-to/implement-travel-rule/index.html new file mode 100644 index 0000000..5c3f907 --- /dev/null +++ b/how-to/implement-travel-rule/index.html @@ -0,0 +1,67 @@ + + + + + +How to implement FATF Travel Rule compliance | SanctionsAI + + + + + + + + + + + + + + + + +

    By SanctionsAI team · Updated 2026-08-09

    +

    How to implement FATF Travel Rule compliance

    +

    The FATF Travel Rule (Recommendation 16) requires VASPs to share originator and beneficiary information for virtual asset transfers above USD/EUR 1,000.

    +

    TL;DR: Travel Rule compliance means collecting and transmitting sender/recipient data for crypto transfers above threshold, screening both parties, and storing data for 5 years.

    +

    Step 1: Determine applicability

    +

    The Travel Rule applies to VASPs (crypto exchanges, custodial wallets). The threshold is USD/EUR 1,000 for cross-border transfers.

    +

    Step 2: Collect required data elements

    + + + +
    Originator dataBeneficiary data
    Full nameFull name
    Account number (wallet address)Account number (wallet address)
    Physical address OR customer ID OR date/place of birthAccount number (wallet address)
    +

    Step 3: Choose a Travel Rule messaging protocol

    +

    Options include TRP, IVMS101, OpenVASP, and TRUST. Choose one that interoperates with your counterparty VASPs.

    +

    Step 4: Integrate sanctions screening

    +

    Before sending or receiving, screen both originator and beneficiary wallet addresses against OFAC SDN.

    +
    Integration: Call GET /sanctions?wallet=0x... before executing any transfer above threshold.
    +

    Step 5: Store records for 5 years

    +

    FATF requires retaining Travel Rule data for at least 5 years. Ensure your storage is auditable.

    +

    Screen your agent's next payment

    +

    Check any wallet, name, or entity against OFAC, EU, UN sanctions lists in real time.

    +Free wallet checker
    +

    Frequently Asked Questions

    +
    What is the FATF Travel Rule threshold?
    USD/EUR 1,000 for cross-border virtual asset transfers.
    Does Travel Rule apply to DeFi?
    FATF says DeFi protocols without a central operator are not VASPs. However, front-end operators may have obligations.
    What data must VASPs share?
    Originator name, wallet, and address/ID/DOB. Beneficiary name and wallet.
    How do I screen crypto transfers?
    Screen both wallets against OFAC SDN before execution. Use GET /sanctions?wallet=0x...
    +
    +

    ← Back to how-to · SanctionsAI

    + \ No newline at end of file diff --git a/how-to/manage-correspondent-banking-risk/index.html b/how-to/manage-correspondent-banking-risk/index.html new file mode 100644 index 0000000..9deb087 --- /dev/null +++ b/how-to/manage-correspondent-banking-risk/index.html @@ -0,0 +1,60 @@ + + + + + +How to manage correspondent banking sanctions risk | SanctionsAI + + + + + + + + + + + + + + + + +

    By SanctionsAI team · Updated 2026-08-09

    +

    How to manage correspondent banking sanctions risk

    +

    Correspondent banking is high-risk because you process transactions for other banks' customers whom you cannot directly screen.

    +

    The nested account problem

    +

    Your respondent bank's customers (nested banks and their customers) may be sanctioned entities. You process their transactions without knowing their identity.

    + + + + +
    Risk levelRespondent profileControls
    LowRegulated bank, FATF-compliantStandard screening, annual review
    MediumModerate-risk jurisdictionEnhanced screening, semi-annual
    HighHigh-risk jurisdiction, weak AMLTransaction-by-transaction, quarterly
    UnacceptableUnder sanctionsTerminate relationship
    +
    Nested account risk: The biggest correspondent banking sanctions risk. Insist on transparency about nested relationships.
    +

    Screen your agent's next payment

    +

    Check any wallet, name, or entity against OFAC, EU, UN sanctions lists in real time.

    +Free wallet checker
    +

    Frequently Asked Questions

    +
    What is correspondent banking sanctions risk?
    Risk that correspondent relationships expose you to violations through respondent banks' customers.
    What are nested accounts?
    Accounts your respondent holds for other banks. You process transactions without knowing the nested banks' customers.
    How do I screen correspondent transactions?
    Screen respondent bank at onboarding. Use SWIFT fields for transaction-level screening.
    Should I terminate high-risk relationships?
    If unacceptable (under sanctions), yes. For elevated risk, apply enhanced monitoring.
    +
    +

    ← Back to how-to · SanctionsAI

    + \ No newline at end of file diff --git a/how-to/prepare-for-ofac-examination/index.html b/how-to/prepare-for-ofac-examination/index.html new file mode 100644 index 0000000..65da5c0 --- /dev/null +++ b/how-to/prepare-for-ofac-examination/index.html @@ -0,0 +1,63 @@ + + + + + +How to prepare for an OFAC compliance examination | SanctionsAI + + + + + + + + + + + + + + + + +

    By SanctionsAI team · Updated 2026-08-09

    +

    How to prepare for an OFAC compliance examination

    +

    OFAC examinations assess your compliance program. Being prepared means having documentation and evidence of screening.

    +

    What examiners request

    + + + + + + +
    DocumentWhy
    Risk assessmentVerify you understand your exposure
    Compliance policyVerify documented procedures exist
    Screening recordsEvidence all customers/transactions screened
    Training recordsEvidence staff are trained
    Audit reportsEvidence of independent review
    Violation historyHow violations were handled
    +

    Preparation checklist

    +

    1. Update risk assessment (current within 12 months). 2. Verify screening coverage (ALL customers and transactions). 3. Test audit trail (can you produce records for any date?). 4. Review training completion (100%). 5. Remediate known gaps. 6. Prepare compliance program overview.

    +
    Pro tip: Conduct mock examinations annually. Simulate the OFAC document request to identify gaps before the real thing.
    +

    Screen your agent's next payment

    +

    Check any wallet, name, or entity against OFAC, EU, UN sanctions lists in real time.

    +Free wallet checker
    +

    Frequently Asked Questions

    +
    How often are OFAC examinations conducted?
    For banks: every 12-18 months. Non-banks: varies by risk profile.
    What documents do I need?
    Risk assessment, compliance policy, screening records, training records, audit reports, governance structure.
    What are common findings?
    Inadequate risk assessments, screening gaps, stale training, missing audit trails.
    How should I handle findings?
    Accept, develop remediation plan with timelines, document implementation.
    +
    +

    ← Back to how-to · SanctionsAI

    + \ No newline at end of file diff --git a/how-to/report-ofac-violations/index.html b/how-to/report-ofac-violations/index.html new file mode 100644 index 0000000..a10e58c --- /dev/null +++ b/how-to/report-ofac-violations/index.html @@ -0,0 +1,61 @@ + + + + + +How to report OFAC violations to regulators | SanctionsAI + + + + + + + + + + + + + + + + +

    By SanctionsAI team · Updated 2026-08-09

    +

    How to report OFAC violations to regulators

    +

    OFAC reporting takes several forms: voluntary self-disclosure, blocking reports, rejection reports, and annual reports.

    +

    Types of reports

    + + + + +
    ReportWhenDeadline
    Voluntary self-disclosureWhen you discover a violationASAP
    Blocking reportWhen you block a transaction10 business days
    Rejection reportWhen you reject a transaction10 business days
    Annual reportSummary of blocked propertySeptember 30
    +

    Voluntary self-disclosure

    +

    If you discover an apparent violation OFAC does not know about, voluntary disclosure can reduce penalties by up to 50%. Include: description, transactions, how discovered, remediation, timeline.

    +
    Penalty mitigation: Voluntary disclosure creates presumption of mitigation. Disclose before OFAC discovers independently.
    +

    Screen your agent's next payment

    +

    Check any wallet, name, or entity against OFAC, EU, UN sanctions lists in real time.

    +Free wallet checker
    +

    Frequently Asked Questions

    +
    What is voluntary self-disclosure?
    Voluntarily reporting an apparent violation OFAC does not know about. Can reduce penalties by up to 50%.
    When must I file a blocking report?
    Within 10 business days of blocking. File via OFAC online portal.
    What is the annual report?
    Summary of all blocked property, due September 30 each year.
    Can I report anonymously?
    OFAC has no formal anonymous mechanism for regulated entities. Report through counsel.
    +
    +

    ← Back to how-to · SanctionsAI

    + \ No newline at end of file diff --git a/how-to/respond-to-ofac-subpoena/index.html b/how-to/respond-to-ofac-subpoena/index.html new file mode 100644 index 0000000..51f9723 --- /dev/null +++ b/how-to/respond-to-ofac-subpoena/index.html @@ -0,0 +1,64 @@ + + + + + +How to respond to an OFAC subpoena or investigation | SanctionsAI + + + + + + + + + + + + + + + + +

    By SanctionsAI team · Updated 2026-08-09

    +

    How to respond to an OFAC subpoena or investigation

    +

    Receiving an OFAC subpoena is serious. Your response quality directly affects enforcement outcomes.

    +

    Step 1: Preserve documents immediately

    +

    Issue a litigation hold. Preserve emails, transaction records, screening logs, compliance policies, training materials.

    +

    Step 2: Engage experienced OFAC counsel

    +

    OFAC enforcement is specialized. Engage counsel with specific OFAC experience.

    +

    Step 3: Conduct an internal investigation

    +

    Under counsel direction, investigate scope: which transactions, which counterparties, which controls failed.

    +

    Step 4: Consider voluntary self-disclosure

    + + + +
    ScenarioAction
    OFAC already knowsCooperate fully
    Unknown violation foundConsider voluntary self-disclosure
    No violation foundDocument and respond
    +
    Do NOT: Destroy documents, contact the subject, discuss publicly, or explain to OFAC without counsel.
    +

    Screen your agent's next payment

    +

    Check any wallet, name, or entity against OFAC, EU, UN sanctions lists in real time.

    +Free wallet checker
    +

    Frequently Asked Questions

    +
    What should I do if I receive an OFAC subpoena?
    Immediately issue a document hold, engage OFAC counsel, and do not discuss with anyone except counsel.
    Can I voluntarily self-disclose during an investigation?
    If the investigation reveals an unknown violation, voluntary disclosure through counsel can reduce penalties.
    How long do I have to respond?
    Typically 30 days. Extensions can be requested through counsel.
    Should I cooperate with OFAC?
    Yes. OFAC rewards cooperation with penalty mitigation. All cooperation through counsel.
    +
    +

    ← Back to how-to · SanctionsAI

    + \ No newline at end of file diff --git a/how-to/screen-beneficial-owners/index.html b/how-to/screen-beneficial-owners/index.html new file mode 100644 index 0000000..7505427 --- /dev/null +++ b/how-to/screen-beneficial-owners/index.html @@ -0,0 +1,66 @@ + + + + + +How to screen beneficial owners for sanctions | SanctionsAI + + + + + + + + + + + + + + + + +

    By SanctionsAI team · Updated 2026-08-09

    +

    How to screen beneficial owners for sanctions

    +

    Beneficial owner screening is required under OFAC's 50 Percent Rule and the Corporate Transparency Act. Any entity majority-owned by a designated person is itself blocked.

    +

    TL;DR: You cannot stop at screening company names. You must identify and screen every individual who owns 25% or more of a corporate counterparty.

    +

    Step 1: Identify the beneficial owners

    +

    Request the corporate ownership structure from your counterparty. Under the Corporate Transparency Act (effective 2024), most US entities must report beneficial owners to FinCEN.

    + + + +
    Ownership thresholdAction
    25% or moreScreen individual against OFAC SDN
    50% or more (combined SDN ownership)Entity is BLOCKED under 50 Percent Rule
    Substantial control (CEO, CFO, board)Screen individual against OFAC SDN
    +

    Step 2: Screen each owner against OFAC SDN

    +

    Use fuzzy name matching, not exact match. Sanctioned individuals often use transliteration variants and aliases.

    +

    Step 3: Check for indirect ownership

    +

    Trace the ownership chain through holding companies. An SDN owning 51% of Company A, which owns 51% of Company B, means Company B is blocked through indirect ownership.

    +
    Common gap: Screening the direct counterparty but not the parent company or ultimate beneficial owner. If an SDN owns the parent, the subsidiary is blocked.
    +

    Step 4: Document and periodically rescreen

    +

    Record the ownership structure, screening date, and results. Rescreen quarterly at minimum.

    +

    Screen your agent's next payment

    +

    Check any wallet, name, or entity against OFAC, EU, UN sanctions lists in real time.

    +Free wallet checker
    +

    Frequently Asked Questions

    +
    What is OFAC's 50 Percent Rule?
    Any entity owned 50% or more, directly or indirectly, by an SDN-listed person is itself designated. You must screen beneficial owners to identify indirect SDN ownership.
    Who counts as a beneficial owner?
    Under the Corporate Transparency Act, anyone who owns 25%+ of an entity or exercises substantial control. OFAC's 50 Percent Rule applies to ownership.
    How often should I rescreen beneficial owners?
    At minimum quarterly, and immediately after major SDN list updates.
    Do AI agents need to screen beneficial owners?
    Yes. AI agents onboarding corporate counterparties should screen company names AND beneficial owners against OFAC SDN.
    +
    +

    ← Back to how-to · SanctionsAI

    + \ No newline at end of file diff --git a/how-to/screen-crypto-transactions/index.html b/how-to/screen-crypto-transactions/index.html new file mode 100644 index 0000000..06f3de3 --- /dev/null +++ b/how-to/screen-crypto-transactions/index.html @@ -0,0 +1,60 @@ + + + + + +How to screen cryptocurrency transactions for sanctions | SanctionsAI + + + + + + + + + + + + + + + + +

    By SanctionsAI team · Updated 2026-08-09

    +

    How to screen cryptocurrency transactions for sanctions

    +

    Crypto sanctions screening is different from name screening: you screen wallet addresses, not names.

    +

    The three screening layers

    + + + +
    LayerWhat to screenWhen
    Wallet addressSending/receiving wallet vs OFAC SDNEvery transaction, real-time
    Transaction historyPast interactions with designated addressesAt onboarding, periodic
    Behavioral patternsMixer interaction, bridge usageOngoing monitoring
    +

    Step-by-step process

    +

    Step 1: Extract sender wallet address. Step 2: Call GET /sanctions?wallet=0x.... Step 3: If blocked=true, reject payment and log. Step 4: Check transaction history for mixer/bridge interaction. Step 5: Record screening result with timestamp.

    +
    Critical: OFAC sanctions are strict liability. Accepting a payment from a designated wallet is a violation even without knowledge. Real-time screening is mandatory.
    +

    Screen your agent's next payment

    +

    Check any wallet, name, or entity against OFAC, EU, UN sanctions lists in real time.

    +Free wallet checker
    +

    Frequently Asked Questions

    +
    How do I screen a crypto wallet?
    Use GET /sanctions?wallet=0x... or the free checker at /tools/wallet-checker.
    What addresses should I screen?
    All OFAC SDN crypto addresses: designated mixers, VASPs, individuals, entities.
    Should I screen transaction history?
    For high-value or high-risk transactions, yes. Check for mixer/bridge interaction.
    Is accepting crypto from a designated wallet a violation?
    Yes. OFAC is strict liability. Real-time screening before acceptance is mandatory.
    +
    +

    ← Back to how-to · SanctionsAI

    + \ No newline at end of file diff --git a/how-to/train-staff-on-sanctions/index.html b/how-to/train-staff-on-sanctions/index.html new file mode 100644 index 0000000..b42cfae --- /dev/null +++ b/how-to/train-staff-on-sanctions/index.html @@ -0,0 +1,63 @@ + + + + + +How to train staff on sanctions compliance | SanctionsAI + + + + + + + + + + + + + + + + +

    By SanctionsAI team · Updated 2026-08-09

    +

    How to train staff on sanctions compliance

    +

    OFAC expects all employees with sanctions exposure to receive regular training. Training gaps are a frequently cited enforcement factor.

    +

    Who needs training?

    + + + + +
    RoleDepthTopics
    All staffBasic awarenessWhat sanctions are, red flags, escalation
    Customer-facingIntermediateSDN screening, jurisdiction blocks
    Compliance teamAdvanced50 Percent Rule, Travel Rule, SAR filing
    AI developersTechnicalAPI integration, screening logic, audit trails
    +

    Training frequency

    +

    Annual at minimum. New employees during onboarding. Additional training after major regulatory changes.

    +

    Content requirements

    +

    Cover: OFAC programs relevant to your business, red flag identification, screening procedures, escalation paths, recent enforcement actions.

    +
    Documentation: Maintain training records (attendee lists, dates, content, completion confirmations).
    +

    Screen your agent's next payment

    +

    Check any wallet, name, or entity against OFAC, EU, UN sanctions lists in real time.

    +Free wallet checker
    +

    Frequently Asked Questions

    +
    How often must sanctions training be conducted?
    Annually at minimum. Additional training after regulatory changes. New employees during onboarding.
    What should training cover?
    OFAC programs, red flags, screening procedures, escalation paths, enforcement lessons.
    Do AI developers need sanctions training?
    Yes. Developers must understand screening logic, audit trails, and escalation.
    Can training be online?
    Yes, if it covers required topics, includes comprehension checks, and maintains records.
    +
    +

    ← Back to how-to · SanctionsAI

    + \ No newline at end of file diff --git a/regulations/corporate-transparency-act/index.html b/regulations/corporate-transparency-act/index.html new file mode 100644 index 0000000..d0202c9 --- /dev/null +++ b/regulations/corporate-transparency-act/index.html @@ -0,0 +1,64 @@ + + + + + +Corporate Transparency Act (CTA) and beneficial ownership | SanctionsAI + + + + + + + + + + + + + + + + +

    By SanctionsAI team · Updated 2026-08-09

    +

    Corporate Transparency Act (CTA) and beneficial ownership

    +

    The Corporate Transparency Act (effective January 1, 2024) requires most US entities to report beneficial ownership information to FinCEN. This creates a national beneficial ownership registry for the first time.

    +

    Who must report?

    + + + + + +
    Entity typeMust report?
    LLCs, corporations, partnershipsYes (unless exempt)
    Large operating companies (20+ employees, $5M+ revenue)Exempt
    Publicly traded companiesExempt (SEC reporting)
    Banks and credit unionsExempt (already regulated)
    Registered investment advisersExempt
    +

    What must be reported?

    +

    Company information: Legal name, trade names, address, EIN/TIN, jurisdiction. Beneficial owner information: Full legal name, date of birth, residential address, government ID number (passport, driver's license).

    +

    Filing deadlines

    +

    Entities existing before January 1, 2024: January 1, 2025. Entities formed in 2024: within 90 days of formation. Entities formed after 2024: within 30 days of formation.

    +
    Sanctions connection: FinCEN's beneficial ownership registry helps identify OFAC's 50 Percent Rule violations. Financial institutions will gain access to this data for compliance.
    +

    Screen your agent's next payment

    +

    Check any wallet, name, or entity against OFAC, EU, UN sanctions lists in real time.

    +Free wallet checker
    +

    Frequently Asked Questions

    +
    What is the Corporate Transparency Act?
    A 2024 law requiring most US entities to report beneficial ownership information to FinCEN. Creates a national UBO registry.
    Who is exempt from CTA reporting?
    Large operating companies (20+ employees, $5M+ revenue), publicly traded companies, banks, and other heavily regulated entities.
    When is the CTA filing deadline?
    Existing entities (before Jan 1 2024): Jan 1, 2025. New entities in 2024: 90 days after formation. After 2024: 30 days.
    How does the CTA connect to OFAC compliance?
    FinCEN's beneficial ownership registry helps identify entities controlled by OFAC-designated persons under the 50 Percent Rule. Financial institutions gain access for compliance.
    +
    +

    ← Back to regulations · SanctionsAI

    + \ No newline at end of file diff --git a/regulations/eu-sanctions-regulation/index.html b/regulations/eu-sanctions-regulation/index.html new file mode 100644 index 0000000..ac35a75 --- /dev/null +++ b/regulations/eu-sanctions-regulation/index.html @@ -0,0 +1,60 @@ + + + + + +EU Sanctions Regulation framework | SanctionsAI + + + + + + + + + + + + + + + + +

    By SanctionsAI team · Updated 2026-08-09

    +

    EU Sanctions Regulation framework

    +

    EU sanctions are adopted through Council Regulations (directly applicable in all member states) and Council Decisions under the CFSP. The framework covers trade, financial, and targeted sanctions.

    +

    How EU sanctions work

    + + + +
    InstrumentLegal basisScope
    Council RegulationTFEU Article 215Directly applicable in all EU member states
    Council Decision (CFSP)TEU Article 29Foreign policy decisions, travel bans
    Implementing RegulationCommissionUpdates to sanctions lists
    +

    Key EU sanctions regimes

    +

    Russia (most extensive, aligned with US/UK), Iran, Syria, North Korea, Belarus, Myanmar, Venezuela, Libya, and others. EU sanctions generally align with UN sanctions but add autonomous measures.

    +
    Multi-list screening: Screen against OFAC SDN, EU consolidated list, and UN list for comprehensive coverage. SanctionsAI checks all three.
    +

    Screen your agent's next payment

    +

    Check any wallet, name, or entity against OFAC, EU, UN sanctions lists in real time.

    +Free wallet checker
    +

    Frequently Asked Questions

    +
    How are EU sanctions adopted?
    Through Council Regulations (directly applicable) and CFSP Decisions. Requires unanimity among all 27 member states.
    Are EU sanctions the same as US sanctions?
    Often aligned but not identical. EU may impose different measures or designate different entities. Screen against both lists.
    Do EU sanctions apply outside the EU?
    EU sanctions apply within EU territory, to EU nationals abroad, and to EU-incorporated companies. Extraterritorial application is limited compared to US secondary sanctions.
    How often is the EU consolidated list updated?
    Frequently. The EU publishes consolidated list updates as Implementing Regulations. Subscribe to EU sanctions notifications.
    +
    +

    ← Back to regulations · SanctionsAI

    + \ No newline at end of file diff --git a/regulations/fatf-recommendation-15/index.html b/regulations/fatf-recommendation-15/index.html new file mode 100644 index 0000000..3437e41 --- /dev/null +++ b/regulations/fatf-recommendation-15/index.html @@ -0,0 +1,63 @@ + + + + + +FATF Recommendation 15: Virtual assets and VASPs | SanctionsAI + + + + + + + + + + + + + + + + +

    By SanctionsAI team · Updated 2026-08-09

    +

    FATF Recommendation 15: Virtual assets and VASPs

    +

    FATF Recommendation 15 is the global standard for AML/CFT regulation of virtual assets and VASPs. Adopted in 2019, updated in 2021, it requires countries to regulate and supervise VASP activities.

    +

    TL;DR: FATF Recommendation 15 requires countries to apply AML/CFT controls to virtual asset activities, license or register VASPs, and implement the Travel Rule for virtual asset transfers.

    +

    Key requirements

    + + + + + +
    RequirementDetail
    Licensing/registrationVASPs must be licensed or registered in their jurisdiction
    SupervisionVASPs subject to supervisory oversight and enforcement
    AML/CFT programCustomer due diligence, record-keeping, suspicious transaction reporting
    Travel Rule (R.16)Share originator/beneficiary data for transfers above USD/EUR 1,000
    Sanctions screeningScreen customers and transactions against UN and national sanctions lists
    +

    Who is a VASP under FATF?

    +

    A VASP is any business that: (1) exchanges virtual assets for fiat or other virtual assets, (2) transfers virtual assets, (3) custodies virtual assets, (4) provides financial services related to virtual assets. This includes exchanges, custodial wallets, and payment processors.

    +
    Compliance tip: SanctionsAI provides API-based screening that satisfies FATF R.15 sanctions screening requirements for VASPs.
    +

    Screen your agent's next payment

    +

    Check any wallet, name, or entity against OFAC, EU, UN sanctions lists in real time.

    +Free wallet checker
    +

    Frequently Asked Questions

    +
    What is FATF Recommendation 15?
    The global standard for AML/CFT regulation of virtual assets and VASPs. Requires countries to regulate, license, and supervise VASP activities.
    Who is a VASP under FATF?
    Any business that exchanges, transfers, or custodies virtual assets, or provides related financial services.
    What is the Travel Rule threshold?
    USD/EUR 1,000 for cross-border virtual asset transfers. VASPs must share originator and beneficiary information.
    Does FATF R.15 apply to DeFi?
    FATF says DeFi protocols without a central operator are not VASPs. Front-end operators and governance participants may have obligations.
    +
    +

    ← Back to regulations · SanctionsAI

    + \ No newline at end of file diff --git a/regulations/fincen-aml-requirements/index.html b/regulations/fincen-aml-requirements/index.html new file mode 100644 index 0000000..b348c89 --- /dev/null +++ b/regulations/fincen-aml-requirements/index.html @@ -0,0 +1,63 @@ + + + + + +FinCEN AML requirements for financial institutions | SanctionsAI + + + + + + + + + + + + + + + + +

    By SanctionsAI team · Updated 2026-08-09

    +

    FinCEN AML requirements for financial institutions

    +

    FinCEN administers the Bank Secrecy Act (BSA), which requires financial institutions to maintain AML programs, file reports, and keep records.

    +

    Core BSA/AML requirements

    + + + + + + +
    RequirementDetail
    AML programWritten program with CIP, CDD, monitoring, training, audit
    Customer Identification Program (CIP)Verify customer identity at onboarding
    SAR filingReport suspicious activity within 30 days
    Currency Transaction Report (CTR)Report cash transactions over $10,000
    RecordkeepingRetain records for 5 years
    OFAC screeningScreen customers and transactions against SDN list
    +

    Which institutions are covered?

    +

    Banks, credit unions, money service businesses (MSBs), securities brokers, futures commission merchants, mutual funds, insurance companies, casinos, and precious metals dealers. Crypto businesses operating as MSBs are covered.

    +
    Integration: SanctionsAI satisfies the OFAC screening component of BSA/AML programs. API-based real-time screening for all transactions.
    +

    Screen your agent's next payment

    +

    Check any wallet, name, or entity against OFAC, EU, UN sanctions lists in real time.

    +Free wallet checker
    +

    Frequently Asked Questions

    +
    What financial institutions need an AML program?
    Banks, credit unions, MSBs, securities brokers, insurance companies, casinos, precious metals dealers. Crypto exchanges operating as MSBs are covered.
    What is a CTR?
    Currency Transaction Report. Required for cash transactions over $10,000. Filed with FinCEN within 15 days.
    What is the SAR filing deadline?
    30 calendar days from initial detection of suspicious activity. 60 days if no suspect identified.
    How long must AML records be kept?
    5 years per FinCEN requirements. Includes CDD records, SARs, CTRs, and transaction records.
    +
    +

    ← Back to regulations · SanctionsAI

    + \ No newline at end of file diff --git a/regulations/fincen-cdd-rule/index.html b/regulations/fincen-cdd-rule/index.html new file mode 100644 index 0000000..49887b8 --- /dev/null +++ b/regulations/fincen-cdd-rule/index.html @@ -0,0 +1,61 @@ + + + + + +FinCEN Customer Due Diligence Rule (31 CFR 1010.230) | SanctionsAI + + + + + + + + + + + + + + + + +

    By SanctionsAI team · Updated 2026-08-09

    +

    FinCEN Customer Due Diligence Rule (31 CFR 1010.230)

    +

    The FinCEN CDD Rule, effective May 2018, requires financial institutions to identify and verify beneficial owners of legal entity customers, understand customer relationships, and monitor for suspicious activity.

    +

    Four core requirements

    + + + + +
    RequirementDescription
    Customer identification and verificationVerify the identity of each customer
    Beneficial ownership identificationIdentify any individual owning 25%+ and one control person
    Understanding customer relationshipsDevelop a customer risk profile
    Ongoing monitoringMonitor for suspicious activity and update customer information
    +

    Beneficial ownership prongs

    +

    Ownership prong: Every individual who owns 25% or more of the equity interests of a legal entity. Control prong: A single individual with significant managerial control (CEO, CFO, managing member).

    +
    Sanctions connection: Each identified beneficial owner must be screened against OFAC SDN. Use SanctionsAI API for automated screening.
    +

    Screen your agent's next payment

    +

    Check any wallet, name, or entity against OFAC, EU, UN sanctions lists in real time.

    +Free wallet checker
    +

    Frequently Asked Questions

    +
    What is the FinCEN CDD Rule?
    31 CFR 1010.230 requires identifying and verifying beneficial owners, understanding customer relationships, and ongoing monitoring.
    What are the beneficial ownership thresholds?
    Ownership prong: any individual owning 25%+. Control prong: one individual with significant managerial control.
    When did the CDD Rule become effective?
    May 11, 2018. Financial institutions must comply as part of their AML program.
    Does the CDD Rule require sanctions screening?
    Yes. Identified beneficial owners must be screened against OFAC SDN as part of customer due diligence.
    +
    +

    ← Back to regulations · SanctionsAI

    + \ No newline at end of file diff --git a/regulations/fincen-travel-rule/index.html b/regulations/fincen-travel-rule/index.html new file mode 100644 index 0000000..115bc7a --- /dev/null +++ b/regulations/fincen-travel-rule/index.html @@ -0,0 +1,62 @@ + + + + + +FinCEN Travel Rule (31 CFR 1010.410) | SanctionsAI + + + + + + + + + + + + + + + + +

    By SanctionsAI team · Updated 2026-08-09

    +

    FinCEN Travel Rule (31 CFR 1010.410)

    +

    The Bank Secrecy Act Travel Rule requires financial institutions to transmit certain information with funds transfers. For transmittals of $3,000 or more, originator and beneficiary data must accompany the transfer.

    +

    Required information

    + + + + + +
    Originator dataBeneficiary data
    NameName
    AddressAddress
    Account numberAccount number
    Originator's bank name/addressBeneficiary's bank name/address
    Payment instructions (if any)Identification of intermediary banks
    +

    Threshold

    +

    $3,000 for funds transfers. The FATF Travel Rule applies a USD/EUR 1,000 threshold for virtual asset transfers, which is separate.

    +
    Sanctions connection: Originator and beneficiary names from Travel Rule data must be screened against OFAC SDN before processing.
    +

    Screen your agent's next payment

    +

    Check any wallet, name, or entity against OFAC, EU, UN sanctions lists in real time.

    +Free wallet checker
    +

    Frequently Asked Questions

    +
    What is the FinCEN Travel Rule threshold?
    $3,000 for funds transfers. For virtual assets, the FATF threshold is USD/EUR 1,000.
    What information must accompany a Travel Rule transfer?
    Originator name, address, account number, and bank. Beneficiary name, address, account number, and bank.
    Does the Travel Rule apply to crypto?
    The FinCEN Travel Rule (31 CFR 1010.410) applies to funds transfers. The FATF Travel Rule (R.16) extends similar requirements to virtual asset transfers.
    How does the Travel Rule connect to sanctions?
    Originator and beneficiary data must be screened against OFAC SDN before processing the transfer.
    +
    +

    ← Back to regulations · SanctionsAI

    + \ No newline at end of file diff --git a/regulations/ofac-general-licenses/index.html b/regulations/ofac-general-licenses/index.html new file mode 100644 index 0000000..8a39b33 --- /dev/null +++ b/regulations/ofac-general-licenses/index.html @@ -0,0 +1,60 @@ + + + + + +OFAC general licenses and exemptions | SanctionsAI + + + + + + + + + + + + + + + + +

    By SanctionsAI team · Updated 2026-08-09

    +

    OFAC general licenses and exemptions

    +

    Not all transactions with sanctioned jurisdictions are prohibited. OFAC issues general licenses (pre-authorized categories) and specific licenses (case-by-case authorization).

    +

    General vs. specific licenses

    + + + +
    TypeHow it worksExample
    General licensePre-authorized in regulations; no application neededPersonal remittances to Iran
    Specific licenseCase-by-case application to OFACRelease of blocked funds for humanitarian purpose
    ExemptionStatutory exemption in the IEEPA or TWEAInformational materials (books, films)
    +

    Common general license categories

    + +
    Before relying on a general license: Read the full text carefully. General licenses have specific conditions, reporting requirements, and limitations. When in doubt, apply for a specific license.
    +

    Screen your agent's next payment

    +

    Check any wallet, name, or entity against OFAC, EU, UN sanctions lists in real time.

    +Free wallet checker
    +

    Frequently Asked Questions

    +
    What is an OFAC general license?
    Pre-authorization for specific categories of transactions with sanctioned jurisdictions. No application needed if your transaction meets the license terms.
    How do I apply for a specific license?
    Submit an application to OFAC via their online portal. Include: parties involved, transaction description, purpose, and why it should be authorized.
    What transactions are commonly licensed?
    Humanitarian (food, medicine), personal remittances, telecommunications, informational materials, and NGO activities.
    Can I rely on a general license without applying?
    Yes, if your transaction falls within the general license terms. But read the full text carefully, as conditions and reporting requirements apply.
    +
    +

    ← Back to regulations · SanctionsAI

    + \ No newline at end of file diff --git a/regulations/ofac-itsr/index.html b/regulations/ofac-itsr/index.html new file mode 100644 index 0000000..77805ba --- /dev/null +++ b/regulations/ofac-itsr/index.html @@ -0,0 +1,61 @@ + + + + + +OFAC Iran Sanctions (ITSR - 31 CFR 560) | SanctionsAI + + + + + + + + + + + + + + + + +

    By SanctionsAI team · Updated 2026-08-09

    +

    OFAC Iran Sanctions (ITSR - 31 CFR 560)

    +

    The Iranian Transactions and Sanctions Regulations (ITSR) implement comprehensive US sanctions on Iran. Virtually all transactions between US persons and Iran are prohibited.

    +

    Scope of prohibitions

    + + + + +
    Prohibited activityException
    Import of Iranian goods/servicesLicensed humanitarian (food, medicine)
    Export of goods/services to IranLicensed agricultural/medical
    Investment in IranNone general
    Financial transactions with IranLicensed personal remittances
    +

    Secondary sanctions

    +

    Non-US persons who conduct significant transactions with Iran's energy, shipping, shipbuilding, or financial sectors may face secondary sanctions under CISADA and IFCA, even if no US jurisdiction is involved.

    +
    Strict liability: OFAC sanctions apply regardless of knowledge or intent. You are liable even if you did not know the counterparty was Iranian.
    +

    Screen your agent's next payment

    +

    Check any wallet, name, or entity against OFAC, EU, UN sanctions lists in real time.

    +Free wallet checker
    +

    Frequently Asked Questions

    +
    What does ITSR prohibit?
    Virtually all transactions between US persons and Iran: imports, exports, investments, financial transactions.
    Are there exceptions to Iran sanctions?
    Yes, for licensed humanitarian transactions (food, medicine), personal remittances, and information exchange. Specific licenses required.
    Do ITSR sanctions apply to non-US persons?
    Primary sanctions apply to US persons. Secondary sanctions under CISADA/IFCA can apply to non-US persons for significant transactions with Iran's energy/financial sectors.
    What are the penalties for ITSR violations?
    Civil penalties up to $356,571 per violation or twice the transaction amount. Criminal penalties up to $20M and 30 years for willful violations.
    +
    +

    ← Back to regulations · SanctionsAI

    + \ No newline at end of file diff --git a/regulations/ofac-north-korea-nkspea/index.html b/regulations/ofac-north-korea-nkspea/index.html new file mode 100644 index 0000000..eff6d72 --- /dev/null +++ b/regulations/ofac-north-korea-nkspea/index.html @@ -0,0 +1,62 @@ + + + + + +OFAC North Korea Sanctions (NKSPEA) | SanctionsAI + + + + + + + + + + + + + + + + +

    By SanctionsAI team · Updated 2026-08-09

    +

    OFAC North Korea Sanctions (NKSPEA)

    +

    The North Korea Sanctions and Policy Enhancement Act (NKSPEA, 2016) imposes comprehensive sanctions on the DPRK. One of the most heavily sanctioned jurisdictions globally.

    +

    Key provisions

    + + + + + +
    ProvisionDetail
    Comprehensive blockingAll DPRK government property blocked
    Secondary sanctionsNon-US persons supporting DPRK WMD, human rights abuses, cyber theft
    TransportationSanctions on DPRK shipping, aviation, transport workers
    FinancialSanctions on DPRK banks and financial facilitators
    CryptoDesignation of DPRK-linked crypto mixers and wallets
    +

    DPRK cyber threat

    +

    The Lazarus Group (designated under DPRK program) is responsible for billions in stolen crypto. OFAC designated Tornado Cash and Blender.io specifically for facilitating DPRK money laundering.

    +
    Crypto risk: North Korea is the most active state-sponsored crypto theft operator. Screen all wallets against OFAC designated DPRK addresses.
    +

    Screen your agent's next payment

    +

    Check any wallet, name, or entity against OFAC, EU, UN sanctions lists in real time.

    +Free wallet checker
    +

    Frequently Asked Questions

    +
    What is NKSPEA?
    The North Korea Sanctions and Policy Enhancement Act (2016), imposing comprehensive sanctions on the DPRK.
    Why was Tornado Cash designated?
    OFAC designated Tornado Cash in August 2022 for processing $455M+ in illicit proceeds for the DPRK-linked Lazarus Group.
    Do North Korea sanctions apply to non-US persons?
    Yes. NKSPEA includes robust secondary sanctions on non-US persons who support DPRK WMD, human rights abuses, or cyber activities.
    What is the Lazarus Group?
    A DPRK state-sponsored hacking group designated under OFAC's North Korea program. Responsible for major crypto exchange hacks and billions in stolen crypto.
    +
    +

    ← Back to regulations · SanctionsAI

    + \ No newline at end of file diff --git a/regulations/ofac-reporting-requirements/index.html b/regulations/ofac-reporting-requirements/index.html new file mode 100644 index 0000000..121063e --- /dev/null +++ b/regulations/ofac-reporting-requirements/index.html @@ -0,0 +1,62 @@ + + + + + +OFAC reporting requirements | SanctionsAI + + + + + + + + + + + + + + + + +

    By SanctionsAI team · Updated 2026-08-09

    +

    OFAC reporting requirements

    +

    OFAC requires several types of reports. Understanding which to file, when, and how is critical for compliance.

    +

    Report types and deadlines

    + + + + + +
    ReportWhenDeadlineHow to file
    Blocking reportTransaction involving SDN property blocked10 business daysOFAC online portal
    Rejection reportTransaction rejected (no blocked property)10 business daysOFAC online portal
    Annual reportSummary of all blocked property heldSeptember 30OFAC online portal
    Voluntary self-disclosureApparent violation discoveredASAPOFAC via email
    Quarterly reportBlocked property transactionsQuarterlyOFAC online portal
    +

    What to include in a blocking report

    +

    Include: blocking date, SDN name, property description, value, account information, and reason for blocking. For voluntary self-disclosure, include: description of the apparent violation, transactions, how discovered, remediation steps, and timeline.

    +
    Voluntary self-disclosure: Can reduce penalties by up to 50%. Disclose before OFAC discovers independently for maximum mitigation.
    +

    Screen your agent's next payment

    +

    Check any wallet, name, or entity against OFAC, EU, UN sanctions lists in real time.

    +Free wallet checker
    +

    Frequently Asked Questions

    +
    When must I file a blocking report?
    Within 10 business days of blocking. File via OFAC online portal with details of the blocked property.
    What is the annual report deadline?
    September 30 each year. Required if you hold blocked property, even from prior years.
    How do I file a voluntary self-disclosure?
    Email OFAC with description of the apparent violation, transactions, how discovered, remediation, and timeline. Do this ASAP.
    What are the penalties for failing to report?
    Failure to file required reports is itself a sanctions violation. Civil penalties up to $356,571 per violation.
    +
    +

    ← Back to regulations · SanctionsAI

    + \ No newline at end of file diff --git a/regulations/ofac-russia-eo14024/index.html b/regulations/ofac-russia-eo14024/index.html new file mode 100644 index 0000000..5a8c66c --- /dev/null +++ b/regulations/ofac-russia-eo14024/index.html @@ -0,0 +1,62 @@ + + + + + +OFAC Russia Sanctions (EO 14024) | SanctionsAI + + + + + + + + + + + + + + + + +

    By SanctionsAI team · Updated 2026-08-09

    +

    OFAC Russia Sanctions (EO 14024)

    +

    Executive Order 14024 (April 2021) authorizes blocking sanctions on the Russian government, financial institutions, oligarchs, and entities supporting Russian harmful foreign activities. Massively expanded after the 2022 invasion of Ukraine.

    +

    Key designation categories

    + + + + + +
    CategoryExamples
    Financial institutionsSberbank, VTB, Gazprombank
    Oligarchs and elitesDesignated individuals with close Kremlin ties
    Defense and militaryRostec, defense manufacturers, military suppliers
    EnergyPrice cap mechanism on Russian oil at $60/barrel
    TechnologyExport controls on semiconductors, dual-use tech
    +

    Oil price cap

    +

    The G7 oil price cap (effective December 2022) prohibits the provision of maritime services (insurance, shipping, finance) for Russian crude oil sold above $60 per barrel. Enforced by OFAC and allied regulators.

    +
    Screening: Russian sanctions designations are frequent. Rescreen all Russia-connected counterparties against the updated SDN list.
    +

    Screen your agent's next payment

    +

    Check any wallet, name, or entity against OFAC, EU, UN sanctions lists in real time.

    +Free wallet checker
    +

    Frequently Asked Questions

    +
    What is Executive Order 14024?
    Authorizes blocking sanctions on Russian government, financial institutions, oligarchs, and entities supporting harmful foreign activities.
    What Russian banks are sanctioned?
    Sberbank (full blocking), VTB (full blocking), Gazprombank (sectoral/debt restrictions). Many smaller banks also designated.
    What is the Russian oil price cap?
    $60/barrel. Maritime service providers (insurance, shipping) cannot service Russian crude sold above this price.
    How often are Russia designations updated?
    Frequently, often monthly or in response to geopolitical events. Rescreen Russia-connected counterparties regularly.
    +
    +

    ← Back to regulations · SanctionsAI

    + \ No newline at end of file diff --git a/regulations/uk-ofsi-regime/index.html b/regulations/uk-ofsi-regime/index.html new file mode 100644 index 0000000..094f8d8 --- /dev/null +++ b/regulations/uk-ofsi-regime/index.html @@ -0,0 +1,62 @@ + + + + + +UK OFSI sanctions regime | SanctionsAI + + + + + + + + + + + + + + + + +

    By SanctionsAI team · Updated 2026-08-09

    +

    UK OFSI sanctions regime

    +

    The UK Office of Financial Sanctions Implementation (OFSI), part of HM Treasury, administers and enforces UK financial sanctions. Post-Brexit, the UK operates an independent sanctions regime.

    +

    Key features

    + + + + + +
    FeatureDetail
    Legal basisSanctions and Anti-Money Laundering Act 2018
    50% RuleEntities 50%+ owned by designated persons are also blocked
    ReportingAll financial institutions must report to OFSI
    PenaltiesCivil penalties up to GBP 1M or 50% of breach value
    Criminal penaltiesUp to 7 years imprisonment
    +

    Post-Brexit independence

    +

    The UK now operates an independent sanctions regime separate from the EU. While often aligned with EU and US sanctions, the UK can impose its own designations. UK financial sanctions apply to all UK persons and within UK territory.

    +
    Screening: Screen against the UK OFSI consolidated list in addition to OFAC and EU lists for comprehensive coverage.
    +

    Screen your agent's next payment

    +

    Check any wallet, name, or entity against OFAC, EU, UN sanctions lists in real time.

    +Free wallet checker
    +

    Frequently Asked Questions

    +
    What is OFSI?
    The UK Office of Financial Sanctions Implementation, part of HM Treasury. Administers and enforces UK financial sanctions.
    Does the UK have a 50% Rule like OFAC?
    Yes. UK financial sanctions apply to entities owned or controlled (50%+) by designated persons, even if not separately listed.
    What are UK sanctions penalties?
    Civil penalties up to GBP 1M or 50% of breach value. Criminal penalties up to 7 years imprisonment.
    Are UK sanctions the same as EU post-Brexit?
    Often aligned but independent. The UK can impose its own designations separate from the EU.
    +
    +

    ← Back to regulations · SanctionsAI

    + \ No newline at end of file