diff --git a/api.py b/api.py
index 33b58af..29d9ee2 100644
--- a/api.py
+++ b/api.py
@@ -5236,6 +5236,256 @@ def _sitemap_xml(self):
("/penalties/sinbad-mixer", "monthly", "0.7", "Sinbad Mixer"),
("/penalties/ofac-crypto-penalty-timeline", "monthly", "0.7", "Ofac Crypto Penalty Timeline"),
("/penalties/ofac-non-crypto-penalties", "monthly", "0.7", "Ofac Non Crypto Penalties"),
+ ("/faq/can-ofac-enforcement-apply-retroactively", "monthly", "0.7", "Can Ofac Enforcement Apply Retroactively"),
+ ("/faq/can-ofac-freeze-crypto-in-self-custody", "monthly", "0.7", "Can Ofac Freeze Crypto In Self Custody"),
+ ("/faq/can-ofac-sanction-a-crypto-exchange", "monthly", "0.7", "Can Ofac Sanction A Crypto Exchange"),
+ ("/faq/can-ofac-sanction-a-crypto-protocol", "monthly", "0.7", "Can Ofac Sanction A Crypto Protocol"),
+ ("/faq/can-ofac-sanction-a-stablecoin", "monthly", "0.7", "Can Ofac Sanction A Stablecoin"),
+ ("/faq/can-ofac-sanction-defi-frontends", "monthly", "0.7", "Can Ofac Sanction Defi Frontends"),
+ ("/faq/can-ofac-track-crypto-transactions", "monthly", "0.7", "Can Ofac Track Crypto Transactions"),
+ ("/faq/does-ofac-apply-to-gaming-crypto", "monthly", "0.7", "Does Ofac Apply To Gaming Crypto"),
+ ("/faq/does-ofac-apply-to-layer-2-networks", "monthly", "0.7", "Does Ofac Apply To Layer 2 Networks"),
+ ("/faq/does-ofac-apply-to-lightning-network", "monthly", "0.7", "Does Ofac Apply To Lightning Network"),
+ ("/faq/does-ofac-apply-to-non-us-companies", "monthly", "0.7", "Does Ofac Apply To Non Us Companies"),
+ ("/faq/does-ofac-apply-to-stablecoin-lending", "monthly", "0.7", "Does Ofac Apply To Stablecoin Lending"),
+ ("/faq/does-ofac-apply-to-stablecoin-yield", "monthly", "0.7", "Does Ofac Apply To Stablecoin Yield"),
+ ("/faq/does-ofac-require-screening-for-stablecoin-issuance", "monthly", "0.7", "Does Ofac Require Screening For Stablecoin Issuanc"),
+ ("/faq/does-ofac-screening-replace-aml", "monthly", "0.7", "Does Ofac Screening Replace Aml"),
+ ("/faq/how-does-sanctionsai-compare-to-chainalysis", "monthly", "0.7", "How Does Sanctionsai Compare To Chainalysis"),
+ ("/faq/how-to-add-ofac-screening-to-existing-app", "monthly", "0.7", "How To Add Ofac Screening To Existing App"),
+ ("/faq/how-to-audit-ofac-compliance-program", "monthly", "0.7", "How To Audit Ofac Compliance Program"),
+ ("/faq/how-to-build-ofac-compliance-program", "monthly", "0.7", "How To Build Ofac Compliance Program"),
+ ("/faq/how-to-handle-sanctions-false-positive", "monthly", "0.7", "How To Handle Sanctions False Positive"),
+ ("/faq/how-to-implement-ofac-screening", "monthly", "0.7", "How To Implement Ofac Screening"),
+ ("/faq/how-to-integrate-ofac-screening-into-agent", "monthly", "0.7", "How To Integrate Ofac Screening Into Agent"),
+ ("/faq/how-to-monitor-sanctions-compliance", "monthly", "0.7", "How To Monitor Sanctions Compliance"),
+ ("/faq/how-to-respond-to-ofac-inquiry", "monthly", "0.7", "How To Respond To Ofac Inquiry"),
+ ("/faq/how-to-screen-crypto-exchanges-for-ofac", "monthly", "0.7", "How To Screen Crypto Exchanges For Ofac"),
+ ("/faq/how-to-screen-stablecoin-payments", "monthly", "0.7", "How To Screen Stablecoin Payments"),
+ ("/faq/how-to-stay-compliant-with-ofac", "monthly", "0.7", "How To Stay Compliant With Ofac"),
+ ("/faq/how-to-test-ofac-screening", "monthly", "0.7", "How To Test Ofac Screening"),
+ ("/faq/how-to-verify-ofac-compliance", "monthly", "0.7", "How To Verify Ofac Compliance"),
+ ("/faq/what-are-ofac-sanctions-programs-explained", "monthly", "0.7", "What Are Ofac Sanctions Programs Explained"),
+ ("/faq/what-is-a-sanctions-match", "monthly", "0.7", "What Is A Sanctions Match"),
+ ("/faq/what-is-a-sanctions-screening-api-key", "monthly", "0.7", "What Is A Sanctions Screening Api Key"),
+ ("/faq/what-is-a-sanctions-screening-false-positive-rate", "monthly", "0.7", "What Is A Sanctions Screening False Positive Rate"),
+ ("/faq/what-is-a-sanctions-screening-tool", "monthly", "0.7", "What Is A Sanctions Screening Tool"),
+ ("/faq/what-is-an-ofac-risk-score", "monthly", "0.7", "What Is An Ofac Risk Score"),
+ ("/faq/what-is-ofac-compliance-for-agent-developers", "monthly", "0.7", "What Is Ofac Compliance For Agent Developers"),
+ ("/faq/what-is-ofac-compliance-for-ai-agent-payment-networks", "monthly", "0.7", "What Is Ofac Compliance For Ai Agent Payment Netwo"),
+ ("/faq/what-is-ofac-compliance-for-bridges", "monthly", "0.7", "What Is Ofac Compliance For Bridges"),
+ ("/faq/what-is-ofac-compliance-for-cross-border-fintech", "monthly", "0.7", "What Is Ofac Compliance For Cross Border Fintech"),
+ ("/faq/what-is-ofac-compliance-for-crypto-payments", "monthly", "0.7", "What Is Ofac Compliance For Crypto Payments"),
+ ("/faq/what-is-ofac-compliance-for-payment-companies", "monthly", "0.7", "What Is Ofac Compliance For Payment Companies"),
+ ("/faq/what-is-ofac-compliance-for-payment-infrastructure-providers", "monthly", "0.7", "What Is Ofac Compliance For Payment Infrastructure"),
+ ("/faq/what-is-ofac-compliance-for-web3", "monthly", "0.7", "What Is Ofac Compliance For Web3"),
+ ("/faq/what-is-ofac-compliance-for-web3-gaming", "monthly", "0.7", "What Is Ofac Compliance For Web3 Gaming"),
+ ("/faq/what-is-ofac-screening-for-agent-payments", "monthly", "0.7", "What Is Ofac Screening For Agent Payments"),
+ ("/faq/what-is-ofac-screening-for-agent-payments-explained", "monthly", "0.7", "What Is Ofac Screening For Agent Payments Explaine"),
+ ("/faq/what-is-ofac-screening-for-agentic-commerce", "monthly", "0.7", "What Is Ofac Screening For Agentic Commerce"),
+ ("/faq/what-is-ofac-screening-for-ai-agent-marketplaces", "monthly", "0.7", "What Is Ofac Screening For Ai Agent Marketplaces"),
+ ("/faq/what-is-ofac-screening-for-airdrops", "monthly", "0.7", "What Is Ofac Screening For Airdrops"),
+ ("/faq/what-is-ofac-screening-for-aml-programs", "monthly", "0.7", "What Is Ofac Screening For Aml Programs"),
+ ("/faq/what-is-ofac-screening-for-bridge-operators", "monthly", "0.7", "What Is Ofac Screening For Bridge Operators"),
+ ("/faq/what-is-ofac-screening-for-central-bank-digital-currency", "monthly", "0.7", "What Is Ofac Screening For Central Bank Digital Cu"),
+ ("/faq/what-is-ofac-screening-for-charities", "monthly", "0.7", "What Is Ofac Screening For Charities"),
+ ("/faq/what-is-ofac-screening-for-cross-border-payments", "monthly", "0.7", "What Is Ofac Screening For Cross Border Payments"),
+ ("/faq/what-is-ofac-screening-for-cross-chain-bridges", "monthly", "0.7", "What Is Ofac Screening For Cross Chain Bridges"),
+ ("/faq/what-is-ofac-screening-for-crypto-atms", "monthly", "0.7", "What Is Ofac Screening For Crypto Atms"),
+ ("/faq/what-is-ofac-screening-for-crypto-compliance", "monthly", "0.7", "What Is Ofac Screening For Crypto Compliance"),
+ ("/faq/what-is-ofac-screening-for-crypto-debit-cards", "monthly", "0.7", "What Is Ofac Screening For Crypto Debit Cards"),
+ ("/faq/what-is-ofac-screening-for-crypto-payment-processors", "monthly", "0.7", "What Is Ofac Screening For Crypto Payment Processo"),
+ ("/faq/what-is-ofac-screening-for-crypto-wallets", "monthly", "0.7", "What Is Ofac Screening For Crypto Wallets"),
+ ("/faq/what-is-ofac-screening-for-custodial-wallets", "monthly", "0.7", "What Is Ofac Screening For Custodial Wallets"),
+ ("/faq/what-is-ofac-screening-for-custody-providers", "monthly", "0.7", "What Is Ofac Screening For Custody Providers"),
+ ("/faq/what-is-ofac-screening-for-dao-treasuries", "monthly", "0.7", "What Is Ofac Screening For Dao Treasuries"),
+ ("/faq/what-is-ofac-screening-for-defi-lending", "monthly", "0.7", "What Is Ofac Screening For Defi Lending"),
+ ("/faq/what-is-ofac-screening-for-defi-protocols", "monthly", "0.7", "What Is Ofac Screening For Defi Protocols"),
+ ("/faq/what-is-ofac-screening-for-defi-yield", "monthly", "0.7", "What Is Ofac Screening For Defi Yield"),
+ ("/faq/what-is-ofac-screening-for-digital-wallets", "monthly", "0.7", "What Is Ofac Screening For Digital Wallets"),
+ ("/faq/what-is-ofac-screening-for-enterprise-blockchain", "monthly", "0.7", "What Is Ofac Screening For Enterprise Blockchain"),
+ ("/faq/what-is-ofac-screening-for-governance-tokens", "monthly", "0.7", "What Is Ofac Screening For Governance Tokens"),
+ ("/faq/what-is-ofac-screening-for-kyc-providers", "monthly", "0.7", "What Is Ofac Screening For Kyc Providers"),
+ ("/faq/what-is-ofac-screening-for-nft-marketplaces", "monthly", "0.7", "What Is Ofac Screening For Nft Marketplaces"),
+ ("/faq/what-is-ofac-screening-for-oracles", "monthly", "0.7", "What Is Ofac Screening For Oracles"),
+ ("/faq/what-is-ofac-screening-for-otc-desks", "monthly", "0.7", "What Is Ofac Screening For Otc Desks"),
+ ("/faq/what-is-ofac-screening-for-payment-aggregators", "monthly", "0.7", "What Is Ofac Screening For Payment Aggregators"),
+ ("/faq/what-is-ofac-screening-for-payment-apis", "monthly", "0.7", "What Is Ofac Screening For Payment Apis"),
+ ("/faq/what-is-ofac-screening-for-payment-gateways", "monthly", "0.7", "What Is Ofac Screening For Payment Gateways"),
+ ("/faq/what-is-ofac-screening-for-payment-networks", "monthly", "0.7", "What Is Ofac Screening For Payment Networks"),
+ ("/faq/what-is-ofac-screening-for-payment-orchestration", "monthly", "0.7", "What Is Ofac Screening For Payment Orchestration"),
+ ("/faq/what-is-ofac-screening-for-payment-routing", "monthly", "0.7", "What Is Ofac Screening For Payment Routing"),
+ ("/faq/what-is-ofac-screening-for-payment-terminals", "monthly", "0.7", "What Is Ofac Screening For Payment Terminals"),
+ ("/faq/what-is-ofac-screening-for-programmatic-payments", "monthly", "0.7", "What Is Ofac Screening For Programmatic Payments"),
+ ("/faq/what-is-ofac-screening-for-real-world-assets", "monthly", "0.7", "What Is Ofac Screening For Real World Assets"),
+ ("/faq/what-is-ofac-screening-for-remittance", "monthly", "0.7", "What Is Ofac Screening For Remittance"),
+ ("/faq/what-is-ofac-screening-for-smart-contract-wallets", "monthly", "0.7", "What Is Ofac Screening For Smart Contract Wallets"),
+ ("/faq/what-is-ofac-screening-for-stablecoin-payment-rails", "monthly", "0.7", "What Is Ofac Screening For Stablecoin Payment Rail"),
+ ("/faq/what-is-ofac-screening-for-stablecoin-transfers", "monthly", "0.7", "What Is Ofac Screening For Stablecoin Transfers"),
+ ("/faq/what-is-ofac-screening-for-staking", "monthly", "0.7", "What Is Ofac Screening For Staking"),
+ ("/faq/what-is-ofac-screening-for-token-launches", "monthly", "0.7", "What Is Ofac Screening For Token Launches"),
+ ("/faq/what-is-ofac-screening-for-token-vesting", "monthly", "0.7", "What Is Ofac Screening For Token Vesting"),
+ ("/faq/what-is-ofac-screening-for-treasury-management", "monthly", "0.7", "What Is Ofac Screening For Treasury Management"),
+ ("/faq/what-is-ofac-screening-for-validators", "monthly", "0.7", "What Is Ofac Screening For Validators"),
+ ("/glossary/ofac-blocked-property", "monthly", "0.7", "Ofac Blocked Property"),
+ ("/glossary/ofac-compliance-audit", "monthly", "0.7", "Ofac Compliance Audit"),
+ ("/glossary/ofac-compliance-documentation", "monthly", "0.7", "Ofac Compliance Documentation"),
+ ("/glossary/ofac-compliance-gap", "monthly", "0.7", "Ofac Compliance Gap"),
+ ("/glossary/ofac-compliance-reporting", "monthly", "0.7", "Ofac Compliance Reporting"),
+ ("/glossary/ofac-compliance-technology", "monthly", "0.7", "Ofac Compliance Technology"),
+ ("/glossary/ofac-compliance-testing", "monthly", "0.7", "Ofac Compliance Testing"),
+ ("/glossary/ofac-compliance-third-party-risk", "monthly", "0.7", "Ofac Compliance Third Party Risk"),
+ ("/glossary/ofac-compliance-training", "monthly", "0.7", "Ofac Compliance Training"),
+ ("/glossary/ofac-contractual-compliance", "monthly", "0.7", "Ofac Contractual Compliance"),
+ ("/glossary/ofac-delisting", "monthly", "0.7", "Ofac Delisting"),
+ ("/glossary/ofac-designation-authority", "monthly", "0.7", "Ofac Designation Authority"),
+ ("/glossary/ofac-enforcement-action", "monthly", "0.7", "Ofac Enforcement Action"),
+ ("/glossary/ofac-enforcement-precedent", "monthly", "0.7", "Ofac Enforcement Precedent"),
+ ("/glossary/ofac-enforcement-priority", "monthly", "0.7", "Ofac Enforcement Priority"),
+ ("/glossary/ofac-facilitation-risk", "monthly", "0.7", "Ofac Facilitation Risk"),
+ ("/glossary/ofac-independent-audit", "monthly", "0.7", "Ofac Independent Audit"),
+ ("/glossary/ofac-kyc-integration", "monthly", "0.7", "Ofac Kyc Integration"),
+ ("/glossary/ofac-list-synchronization", "monthly", "0.7", "Ofac List Synchronization"),
+ ("/glossary/ofac-name-screening", "monthly", "0.7", "Ofac Name Screening"),
+ ("/glossary/ofac-payment-screening", "monthly", "0.7", "Ofac Payment Screening"),
+ ("/glossary/ofac-rejected-vs-blocked", "monthly", "0.7", "Ofac Rejected Vs Blocked"),
+ ("/glossary/ofac-risk-assessment-framework", "monthly", "0.7", "Ofac Risk Assessment Framework"),
+ ("/glossary/ofac-risk-based-approach", "monthly", "0.7", "Ofac Risk Based Approach"),
+ ("/glossary/ofac-risk-indicator", "monthly", "0.7", "Ofac Risk Indicator"),
+ ("/glossary/ofac-screening-alert-fatigue", "monthly", "0.7", "Ofac Screening Alert Fatigue"),
+ ("/glossary/ofac-screening-api-endpoint", "monthly", "0.7", "Ofac Screening Api Endpoint"),
+ ("/glossary/ofac-screening-automation", "monthly", "0.7", "Ofac Screening Automation"),
+ ("/glossary/ofac-screening-availability", "monthly", "0.7", "Ofac Screening Availability"),
+ ("/glossary/ofac-screening-batch", "monthly", "0.7", "Ofac Screening Batch"),
+ ("/glossary/ofac-screening-benchmark", "monthly", "0.7", "Ofac Screening Benchmark"),
+ ("/glossary/ofac-screening-caching", "monthly", "0.7", "Ofac Screening Caching"),
+ ("/glossary/ofac-screening-compliance-tech-stack", "monthly", "0.7", "Ofac Screening Compliance Tech Stack"),
+ ("/glossary/ofac-screening-coverage", "monthly", "0.7", "Ofac Screening Coverage"),
+ ("/glossary/ofac-screening-coverage-analysis", "monthly", "0.7", "Ofac Screening Coverage Analysis"),
+ ("/glossary/ofac-screening-data-retention", "monthly", "0.7", "Ofac Screening Data Retention"),
+ ("/glossary/ofac-screening-error-handling", "monthly", "0.7", "Ofac Screening Error Handling"),
+ ("/glossary/ofac-screening-escalation", "monthly", "0.7", "Ofac Screening Escalation"),
+ ("/glossary/ofac-screening-for-ai", "monthly", "0.7", "Ofac Screening For Ai"),
+ ("/glossary/ofac-screening-for-belarus", "monthly", "0.7", "Ofac Screening For Belarus"),
+ ("/glossary/ofac-screening-for-cuba", "monthly", "0.7", "Ofac Screening For Cuba"),
+ ("/glossary/ofac-screening-for-cyber", "monthly", "0.7", "Ofac Screening For Cyber"),
+ ("/glossary/ofac-screening-for-human-rights", "monthly", "0.7", "Ofac Screening For Human Rights"),
+ ("/glossary/ofac-screening-for-iran", "monthly", "0.7", "Ofac Screening For Iran"),
+ ("/glossary/ofac-screening-for-myanmar", "monthly", "0.7", "Ofac Screening For Myanmar"),
+ ("/glossary/ofac-screening-for-narcotics", "monthly", "0.7", "Ofac Screening For Narcotics"),
+ ("/glossary/ofac-screening-for-non-proliferation", "monthly", "0.7", "Ofac Screening For Non Proliferation"),
+ ("/glossary/ofac-screening-for-north-korea", "monthly", "0.7", "Ofac Screening For North Korea"),
+ ("/glossary/ofac-screening-for-ransomware", "monthly", "0.7", "Ofac Screening For Ransomware"),
+ ("/glossary/ofac-screening-for-russia", "monthly", "0.7", "Ofac Screening For Russia"),
+ ("/glossary/ofac-screening-for-sanctions-evasion", "monthly", "0.7", "Ofac Screening For Sanctions Evasion"),
+ ("/glossary/ofac-screening-for-sanctions-lists", "monthly", "0.7", "Ofac Screening For Sanctions Lists"),
+ ("/glossary/ofac-screening-for-syria", "monthly", "0.7", "Ofac Screening For Syria"),
+ ("/glossary/ofac-screening-for-terrorism", "monthly", "0.7", "Ofac Screening For Terrorism"),
+ ("/glossary/ofac-screening-for-transnational-crime", "monthly", "0.7", "Ofac Screening For Transnational Crime"),
+ ("/glossary/ofac-screening-for-ukraine", "monthly", "0.7", "Ofac Screening For Ukraine"),
+ ("/glossary/ofac-screening-for-venezuela", "monthly", "0.7", "Ofac Screening For Venezuela"),
+ ("/glossary/ofac-screening-governance", "monthly", "0.7", "Ofac Screening Governance"),
+ ("/glossary/ofac-screening-integration-pattern", "monthly", "0.7", "Ofac Screening Integration Pattern"),
+ ("/glossary/ofac-screening-jurisdictional-risk", "monthly", "0.7", "Ofac Screening Jurisdictional Risk"),
+ ("/glossary/ofac-screening-key-management", "monthly", "0.7", "Ofac Screening Key Management"),
+ ("/glossary/ofac-screening-log", "monthly", "0.7", "Ofac Screening Log"),
+ ("/glossary/ofac-screening-methodology", "monthly", "0.7", "Ofac Screening Methodology"),
+ ("/glossary/ofac-screening-penalty-calculator", "monthly", "0.7", "Ofac Screening Penalty Calculator"),
+ ("/glossary/ofac-screening-policy", "monthly", "0.7", "Ofac Screening Policy"),
+ ("/glossary/ofac-screening-programs-list", "monthly", "0.7", "Ofac Screening Programs List"),
+ ("/glossary/ofac-screening-rate-limiting", "monthly", "0.7", "Ofac Screening Rate Limiting"),
+ ("/glossary/ofac-screening-real-time", "monthly", "0.7", "Ofac Screening Real Time"),
+ ("/glossary/ofac-screening-remediation", "monthly", "0.7", "Ofac Screening Remediation"),
+ ("/glossary/ofac-screening-response-time", "monthly", "0.7", "Ofac Screening Response Time"),
+ ("/glossary/ofac-screening-sdk", "monthly", "0.7", "Ofac Screening Sdk"),
+ ("/glossary/ofac-screening-sdk-documentation", "monthly", "0.7", "Ofac Screening Sdk Documentation"),
+ ("/glossary/ofac-screening-transaction-volume", "monthly", "0.7", "Ofac Screening Transaction Volume"),
+ ("/glossary/ofac-screening-webhook", "monthly", "0.7", "Ofac Screening Webhook"),
+ ("/glossary/ofac-secondary-sanctions", "monthly", "0.7", "Ofac Secondary Sanctions"),
+ ("/glossary/ofac-strict-liability", "monthly", "0.7", "Ofac Strict Liability"),
+ ("/glossary/ofac-transaction-monitoring", "monthly", "0.7", "Ofac Transaction Monitoring"),
+ ("/glossary/ofac-wallet-clustering", "monthly", "0.7", "Ofac Wallet Clustering"),
+ ("/glossary/sanctions-screening-engine", "monthly", "0.7", "Sanctions Screening Engine"),
+ ("/glossary/sanctions-screening-service-provider", "monthly", "0.7", "Sanctions Screening Service Provider"),
+ ("/learn/how-ofac-enforcement-has-evolved-for-crypto", "monthly", "0.7", "How Ofac Enforcement Has Evolved For Crypto"),
+ ("/learn/how-ofac-enforces-crypto-sanctions", "monthly", "0.7", "How Ofac Enforces Crypto Sanctions"),
+ ("/learn/how-ofac-penalties-are-calculated", "monthly", "0.7", "How Ofac Penalties Are Calculated"),
+ ("/learn/how-ofac-sanctions-impact-crypto-development", "monthly", "0.7", "How Ofac Sanctions Impact Crypto Development"),
+ ("/learn/how-ofac-sanctions-work-for-crypto-startups", "monthly", "0.7", "How Ofac Sanctions Work For Crypto Startups"),
+ ("/learn/how-to-add-ofac-screening-to-defi-frontend", "monthly", "0.7", "How To Add Ofac Screening To Defi Frontend"),
+ ("/learn/how-to-audit-sanctions-screening-code", "monthly", "0.7", "How To Audit Sanctions Screening Code"),
+ ("/learn/how-to-build-ofac-compliance-culture", "monthly", "0.7", "How To Build Ofac Compliance Culture"),
+ ("/learn/how-to-build-sanctions-screening-into-agent-framework", "monthly", "0.7", "How To Build Sanctions Screening Into Agent Framew"),
+ ("/learn/how-to-choose-ofac-sanctions-screening-tool", "monthly", "0.7", "How To Choose Ofac Sanctions Screening Tool"),
+ ("/learn/how-to-choose-ofac-screening-solution-for-startup", "monthly", "0.7", "How To Choose Ofac Screening Solution For Startup"),
+ ("/learn/how-to-design-ofac-compliant-payment-system", "monthly", "0.7", "How To Design Ofac Compliant Payment System"),
+ ("/learn/how-to-handle-ofac-compliance-in-ci-cd", "monthly", "0.7", "How To Handle Ofac Compliance In Ci Cd"),
+ ("/learn/how-to-integrate-ofac-screening-into-payment-api", "monthly", "0.7", "How To Integrate Ofac Screening Into Payment Api"),
+ ("/learn/how-to-integrate-sanctions-screening-into-ci-cd-pipeline", "monthly", "0.7", "How To Integrate Sanctions Screening Into Ci Cd Pi"),
+ ("/learn/how-to-monitor-ofac-screening-in-production", "monthly", "0.7", "How To Monitor Ofac Screening In Production"),
+ ("/learn/how-to-scale-ofac-screening-for-high-volume", "monthly", "0.7", "How To Scale Ofac Screening For High Volume"),
+ ("/learn/how-to-test-ofac-screening-integration", "monthly", "0.7", "How To Test Ofac Screening Integration"),
+ ("/learn/ofac-compliance-for-defi-protocol-developers", "monthly", "0.7", "Ofac Compliance For Defi Protocol Developers"),
+ ("/learn/ofac-compliance-for-multisig-wallets", "monthly", "0.7", "Ofac Compliance For Multisig Wallets"),
+ ("/learn/ofac-compliance-for-open-source-projects", "monthly", "0.7", "Ofac Compliance For Open Source Projects"),
+ ("/learn/ofac-compliance-for-payment-engineering", "monthly", "0.7", "Ofac Compliance For Payment Engineering"),
+ ("/learn/ofac-compliance-for-payment-orchestration-platforms", "monthly", "0.7", "Ofac Compliance For Payment Orchestration Platform"),
+ ("/learn/ofac-compliance-for-stablecoin-projects", "monthly", "0.7", "Ofac Compliance For Stablecoin Projects"),
+ ("/learn/ofac-compliance-for-token-projects", "monthly", "0.7", "Ofac Compliance For Token Projects"),
+ ("/learn/ofac-compliance-for-web3-developers-guide", "monthly", "0.7", "Ofac Compliance For Web3 Developers Guide"),
+ ("/learn/ofac-compliance-maturity-model", "monthly", "0.7", "Ofac Compliance Maturity Model"),
+ ("/learn/ofac-sanctions-compliance-for-crypto-startups", "monthly", "0.7", "Ofac Sanctions Compliance For Crypto Startups"),
+ ("/learn/ofac-sanctions-compliance-for-exchanges", "monthly", "0.7", "Ofac Sanctions Compliance For Exchanges"),
+ ("/learn/ofac-sanctions-compliance-for-fintech", "monthly", "0.7", "Ofac Sanctions Compliance For Fintech"),
+ ("/learn/ofac-sanctions-compliance-for-validators", "monthly", "0.7", "Ofac Sanctions Compliance For Validators"),
+ ("/learn/ofac-sanctions-screening-for-developers-guide", "monthly", "0.7", "Ofac Sanctions Screening For Developers Guide"),
+ ("/learn/ofac-sanctions-screening-for-devops", "monthly", "0.7", "Ofac Sanctions Screening For Devops"),
+ ("/learn/ofac-sanctions-screening-for-engineering-managers", "monthly", "0.7", "Ofac Sanctions Screening For Engineering Managers"),
+ ("/learn/ofac-sanctions-screening-for-enterprise", "monthly", "0.7", "Ofac Sanctions Screening For Enterprise"),
+ ("/learn/ofac-screeening-for-agent-developers", "monthly", "0.7", "Ofac Screeening For Agent Developers"),
+ ("/learn/ofac-screeening-for-payment-infrastructure", "monthly", "0.7", "Ofac Screeening For Payment Infrastructure"),
+ ("/learn/ofac-screening-best-practices-for-developers", "monthly", "0.7", "Ofac Screening Best Practices For Developers"),
+ ("/learn/ofac-screening-cost-benefit-analysis", "monthly", "0.7", "Ofac Screening Cost Benefit Analysis"),
+ ("/learn/ofac-screening-for-agent-frameworks", "monthly", "0.7", "Ofac Screening For Agent Frameworks"),
+ ("/learn/ofac-screening-for-blockchain-companies", "monthly", "0.7", "Ofac Screening For Blockchain Companies"),
+ ("/learn/ofac-screening-for-blockchain-infrastructure", "monthly", "0.7", "Ofac Screening For Blockchain Infrastructure"),
+ ("/learn/ofac-screening-for-cross-chain-developers", "monthly", "0.7", "Ofac Screening For Cross Chain Developers"),
+ ("/learn/ofac-screening-for-crypto-compliance-teams", "monthly", "0.7", "Ofac Screening For Crypto Compliance Teams"),
+ ("/learn/ofac-screening-for-layer-2-projects", "monthly", "0.7", "Ofac Screening For Layer 2 Projects"),
+ ("/learn/ofac-screening-for-nft-projects", "monthly", "0.7", "Ofac Screening For Nft Projects"),
+ ("/learn/ofac-screening-for-payment-engineering-teams", "monthly", "0.7", "Ofac Screening For Payment Engineering Teams"),
+ ("/learn/ofac-screening-for-payment-startups", "monthly", "0.7", "Ofac Screening For Payment Startups"),
+ ("/learn/ofac-screening-for-smart-contract-developers", "monthly", "0.7", "Ofac Screening For Smart Contract Developers"),
+ ("/learn/ofac-screening-implementation-patterns", "monthly", "0.7", "Ofac Screening Implementation Patterns"),
+ ("/learn/ofac-screening-implementation-timeline", "monthly", "0.7", "Ofac Screening Implementation Timeline"),
+ ("/learn/ofac-screening-security-considerations", "monthly", "0.7", "Ofac Screening Security Considerations"),
+ ("/learn/what-are-ofac-sanctions-for-crypto", "monthly", "0.7", "What Are Ofac Sanctions For Crypto"),
+ ("/learn/what-are-ofac-sanctions-penalties-for-crypto", "monthly", "0.7", "What Are Ofac Sanctions Penalties For Crypto"),
+ ("/learn/what-happens-when-ofac-screening-fails", "monthly", "0.7", "What Happens When Ofac Screening Fails"),
+ ("/learn/what-is-ofac-compliance-for-blockchain-developers", "monthly", "0.7", "What Is Ofac Compliance For Blockchain Developers"),
+ ("/learn/what-is-ofac-compliance-for-crypto-wallet-developers", "monthly", "0.7", "What Is Ofac Compliance For Crypto Wallet Develope"),
+ ("/learn/what-is-ofac-compliance-for-defi-developers", "monthly", "0.7", "What Is Ofac Compliance For Defi Developers"),
+ ("/learn/what-is-ofac-compliance-for-developers", "monthly", "0.7", "What Is Ofac Compliance For Developers"),
+ ("/learn/what-is-ofac-compliance-for-fintech-infrastructure", "monthly", "0.7", "What Is Ofac Compliance For Fintech Infrastructure"),
+ ("/learn/what-is-ofac-compliance-for-payment-product-managers", "monthly", "0.7", "What Is Ofac Compliance For Payment Product Manage"),
+ ("/learn/what-is-ofac-compliance-for-platform-engineering", "monthly", "0.7", "What Is Ofac Compliance For Platform Engineering"),
+ ("/learn/what-is-ofac-compliance-for-web3-startups", "monthly", "0.7", "What Is Ofac Compliance For Web3 Startups"),
+ ("/learn/what-is-ofac-compliance-testing-methodology", "monthly", "0.7", "What Is Ofac Compliance Testing Methodology"),
+ ("/learn/what-is-ofac-risk-based-compliance", "monthly", "0.7", "What Is Ofac Risk Based Compliance"),
+ ("/learn/what-is-ofac-sanctions-compliance-monitoring", "monthly", "0.7", "What Is Ofac Sanctions Compliance Monitoring"),
+ ("/learn/what-is-ofac-sanctions-compliance-training", "monthly", "0.7", "What Is Ofac Sanctions Compliance Training"),
+ ("/learn/what-is-ofac-sanctions-screening-explained", "monthly", "0.7", "What Is Ofac Sanctions Screening Explained"),
+ ("/learn/what-is-ofac-screening-for-payment-security", "monthly", "0.7", "What Is Ofac Screening For Payment Security"),
+ ("/penalties/blender-io", "monthly", "0.7", "Blender Io"),
+ ("/penalties/bybit", "monthly", "0.7", "Bybit"),
+ ("/penalties/crypto-com", "monthly", "0.7", "Crypto Com"),
+ ("/penalties/garantex-sanctions", "monthly", "0.7", "Garantex Sanctions"),
+ ("/penalties/hydra-market", "monthly", "0.7", "Hydra Market"),
+ ("/penalties/kucoin", "monthly", "0.7", "Kucoin"),
+ ("/penalties/ofac-crypto-penalty-timeline", "monthly", "0.7", "Ofac Crypto Penalty Timeline"),
+ ("/penalties/ofac-non-crypto-penalties", "monthly", "0.7", "Ofac Non Crypto Penalties"),
+ ("/penalties/okx", "monthly", "0.7", "Okx"),
+ ("/penalties/sinbad-mixer", "monthly", "0.7", "Sinbad Mixer"),
]
import datetime
today = datetime.date.today().isoformat()
diff --git a/faq/can-ofac-freeze-crypto-in-self-custody/index.html b/faq/can-ofac-freeze-crypto-in-self-custody/index.html
new file mode 100644
index 0000000..1d8e540
--- /dev/null
+++ b/faq/can-ofac-freeze-crypto-in-self-custody/index.html
@@ -0,0 +1 @@
+Can OFAC freeze crypto in self-custody? | FAQ
Can OFAC freeze crypto in self-custody?
Can OFAC freeze crypto in self-custody?
OFAC cannot directly seize or freeze crypto in a self-custodied wallet. What it can do: designate the address, making it illegal for US persons to transact with it, and pressure exchanges, stablecoin issuers, and service providers to block interactions with the address.
\ No newline at end of file
diff --git a/faq/can-ofac-sanction-a-crypto-protocol/index.html b/faq/can-ofac-sanction-a-crypto-protocol/index.html
new file mode 100644
index 0000000..035e80c
--- /dev/null
+++ b/faq/can-ofac-sanction-a-crypto-protocol/index.html
@@ -0,0 +1 @@
+Can OFAC sanction a crypto protocol? | FAQ
Can OFAC sanction a crypto protocol?
Can OFAC sanction a crypto protocol?
Yes — Tornado Cash established that crypto protocols are not exempt from OFAC designation. OFAC designated the protocol's smart contract addresses, and US persons are prohibited from interacting with them. This precedent applies to any protocol, decentralized or not.
\ No newline at end of file
diff --git a/faq/does-ofac-apply-to-gaming-crypto/index.html b/faq/does-ofac-apply-to-gaming-crypto/index.html
new file mode 100644
index 0000000..e2718dc
--- /dev/null
+++ b/faq/does-ofac-apply-to-gaming-crypto/index.html
@@ -0,0 +1 @@
+Does OFAC apply to gaming and crypto? | FAQ
Does OFAC apply to gaming and crypto?
Does OFAC apply to gaming and crypto?
Gaming economies with real value — play-to-earn rewards, tradeable in-game items, gaming NFTs — are subject to OFAC. Paying rewards to a sanctioned wallet or trading a gaming NFT with a sanctioned player are potential violations.
\ No newline at end of file
diff --git a/faq/does-ofac-apply-to-lightning-network/index.html b/faq/does-ofac-apply-to-lightning-network/index.html
new file mode 100644
index 0000000..cf9289a
--- /dev/null
+++ b/faq/does-ofac-apply-to-lightning-network/index.html
@@ -0,0 +1 @@
+Does OFAC apply to Lightning Network? | FAQ
Does OFAC apply to Lightning Network?
Does OFAC apply to Lightning Network?
Lightning Network payments are not exempt from OFAC. Lightning nodes routing payments may face compliance obligations if they process transactions involving sanctioned parties. The routing node's jurisdiction and the transaction's US nexus determine the extent of OFAC applicability.
\ No newline at end of file
diff --git a/faq/does-ofac-apply-to-stablecoin-lending/index.html b/faq/does-ofac-apply-to-stablecoin-lending/index.html
new file mode 100644
index 0000000..3877b29
--- /dev/null
+++ b/faq/does-ofac-apply-to-stablecoin-lending/index.html
@@ -0,0 +1 @@
+Does OFAC apply to stablecoin lending? | FAQ
Does OFAC apply to stablecoin lending?
Does OFAC apply to stablecoin lending?
Stablecoin lending platforms distribute value (yield) to wallet addresses. Those distributions are subject to OFAC — lending to or distributing yield to a sanctioned wallet is a prohibited transaction.
\ No newline at end of file
diff --git a/faq/how-to-add-ofac-screening-to-existing-app/index.html b/faq/how-to-add-ofac-screening-to-existing-app/index.html
new file mode 100644
index 0000000..799cef7
--- /dev/null
+++ b/faq/how-to-add-ofac-screening-to-existing-app/index.html
@@ -0,0 +1 @@
+How to add OFAC screening to an existing application | FAQ
How to add OFAC screening to an existing application
How to add OFAC screening to an existing application
Adding screening to an existing app: (1) Map every code path where payments are initiated. (2) Add a screening API call at the start of each path — before payment authorization. (3) Test each path with sanctioned wallets. (4) Enable logging. (5) Deploy. The change is typically under 10 lines of code per payment path.
\ No newline at end of file
diff --git a/faq/how-to-audit-ofac-compliance-program/index.html b/faq/how-to-audit-ofac-compliance-program/index.html
new file mode 100644
index 0000000..febdada
--- /dev/null
+++ b/faq/how-to-audit-ofac-compliance-program/index.html
@@ -0,0 +1 @@
+How to audit an OFAC compliance program | FAQ
How to audit an OFAC compliance program
How to audit an OFAC compliance program
Audit steps: (1) Review screening coverage — are all payment paths covered? (2) Test with known sanctioned wallets — does blocking work? (3) Review screening logs — any gaps or patterns? (4) Check SDN list sync currency — when was your last update? (5) Document findings and remediation actions.
\ No newline at end of file
diff --git a/faq/how-to-implement-ofac-screening/index.html b/faq/how-to-implement-ofac-screening/index.html
new file mode 100644
index 0000000..569ae4e
--- /dev/null
+++ b/faq/how-to-implement-ofac-screening/index.html
@@ -0,0 +1 @@
+How to implement OFAC sanctions screening | FAQ
How to implement OFAC sanctions screening
How to implement OFAC sanctions screening
Implement OFAC screening in 5 steps: (1) Choose a screening API (SanctionsAI free tier is fine for testing). (2) Wire the screening call before payment authorization in your code. (3) Test with known sanctioned wallets — confirm blocking works. (4) Enable audit logging. (5) Deploy and monitor.
\ No newline at end of file
diff --git a/faq/how-to-respond-to-ofac-inquiry/index.html b/faq/how-to-respond-to-ofac-inquiry/index.html
new file mode 100644
index 0000000..6e37085
--- /dev/null
+++ b/faq/how-to-respond-to-ofac-inquiry/index.html
@@ -0,0 +1 @@
+How to respond to an OFAC inquiry or subpoena | FAQ
How to respond to an OFAC inquiry or subpoena
How to respond to an OFAC inquiry or subpoena
OFAC inquiry response: (1) Acknowledge receipt promptly. (2) Consult sanctions counsel before responding substantively. (3) Gather requested documents — screening logs, policies, transaction records. (4) Respond within the stated deadline. (5) Be truthful — false statements to OFAC are a separate offense. (6) Cooperate — cooperation is a mitigating factor.
\ No newline at end of file
diff --git a/faq/how-to-stay-compliant-with-ofac/index.html b/faq/how-to-stay-compliant-with-ofac/index.html
new file mode 100644
index 0000000..4cd1814
--- /dev/null
+++ b/faq/how-to-stay-compliant-with-ofac/index.html
@@ -0,0 +1 @@
+How to stay compliant with OFAC sanctions | FAQ
How to stay compliant with OFAC sanctions
How to stay compliant with OFAC sanctions
OFAC compliance checklist: (1) Screen every transaction — no exceptions. (2) Keep your SDN list current — sync at least daily. (3) Maintain audit logs — every screening result with timestamp. (4) Train your team annually. (5) Document your program in writing. (6) Review and update quarterly.
\ No newline at end of file
diff --git a/faq/how-to-test-ofac-screening/index.html b/faq/how-to-test-ofac-screening/index.html
new file mode 100644
index 0000000..e3501b1
--- /dev/null
+++ b/faq/how-to-test-ofac-screening/index.html
@@ -0,0 +1 @@
+How to test OFAC sanctions screening | FAQ
How to test OFAC sanctions screening
How to test OFAC sanctions screening
Testing procedure: (1) Use a known sanctioned wallet address (Tornado Cash: 0x098B716B8Aaf21512996dC57EB0615e2383E2f96). (2) Call your screening function with this address. (3) Confirm the result is clean: false. (4) Test that your payment function BLOCKS (not just logs) on match. (5) Repeat with a clean wallet to confirm normal payments still work.
\ No newline at end of file
diff --git a/faq/what-is-a-sanctions-screening-api-key/index.html b/faq/what-is-a-sanctions-screening-api-key/index.html
new file mode 100644
index 0000000..73d7e61
--- /dev/null
+++ b/faq/what-is-a-sanctions-screening-api-key/index.html
@@ -0,0 +1 @@
+What is a sanctions screening API key? | FAQ
What is a sanctions screening API key?
What is a sanctions screening API key?
A screening API key identifies and authenticates your application when calling a sanctions screening service. Free tiers (like SanctionsAI's 5 checks/day) typically don't require keys. Paid tiers use keys for authentication, rate limiting, and billing. Store keys securely — they grant access to your screening data.
\ No newline at end of file
diff --git a/faq/what-is-a-sanctions-screening-false-positive-rate/index.html b/faq/what-is-a-sanctions-screening-false-positive-rate/index.html
new file mode 100644
index 0000000..e0cd415
--- /dev/null
+++ b/faq/what-is-a-sanctions-screening-false-positive-rate/index.html
@@ -0,0 +1 @@
+What is an acceptable false positive rate? | FAQ
What is an acceptable false positive rate?
What is an acceptable false positive rate?
False positive rates vary by screening method: wallet screening (<1% FP rate — addresses are unique), name screening (5-15% — names vary and overlap). The tradeoff: lower thresholds catch more SDNs but generate more false positives to review. SanctionsAI's default threshold balances both.
\ No newline at end of file
diff --git a/faq/what-is-ofac-compliance-for-agent-developers/index.html b/faq/what-is-ofac-compliance-for-agent-developers/index.html
new file mode 100644
index 0000000..af09af9
--- /dev/null
+++ b/faq/what-is-ofac-compliance-for-agent-developers/index.html
@@ -0,0 +1 @@
+OFAC compliance for agent developers | FAQ
OFAC compliance for agent developers
OFAC compliance for agent developers
Agent developers: sanctions screening is not a feature to add later. It's infrastructure that must be present from the first payment. Plan for it in your agent's architecture: a pre-payment screening call on every payment path, blocking logic, and audit logging.
\ No newline at end of file
diff --git a/faq/what-is-ofac-compliance-for-ai-agent-payment-networks/index.html b/faq/what-is-ofac-compliance-for-ai-agent-payment-networks/index.html
new file mode 100644
index 0000000..c984c6a
--- /dev/null
+++ b/faq/what-is-ofac-compliance-for-ai-agent-payment-networks/index.html
@@ -0,0 +1 @@
+OFAC compliance for AI agent payment networks | FAQ
OFAC compliance for AI agent payment networks
OFAC compliance for AI agent payment networks
Agent payment networks are infrastructure for autonomous value transfer. They must incorporate sanctions screening as a protocol-level concern — not leave it to individual implementers. The x402 specification, for example, should include a sanctions screening step in the payment flow.
\ No newline at end of file
diff --git a/faq/what-is-ofac-compliance-for-cross-border-fintech/index.html b/faq/what-is-ofac-compliance-for-cross-border-fintech/index.html
new file mode 100644
index 0000000..f976e9a
--- /dev/null
+++ b/faq/what-is-ofac-compliance-for-cross-border-fintech/index.html
@@ -0,0 +1 @@
+OFAC compliance for cross-border fintech | FAQ
OFAC compliance for cross-border fintech
OFAC compliance for cross-border fintech
Cross-border fintech combines multiple OFAC risk factors: international transactions, multiple jurisdictions, correspondent banking relationships, and often crypto or digital payment rails. Screening must cover every jurisdiction and every intermediary in the payment chain.
\ No newline at end of file
diff --git a/faq/what-is-ofac-compliance-for-payment-companies/index.html b/faq/what-is-ofac-compliance-for-payment-companies/index.html
new file mode 100644
index 0000000..f9fd6cd
--- /dev/null
+++ b/faq/what-is-ofac-compliance-for-payment-companies/index.html
@@ -0,0 +1 @@
+OFAC compliance for payment companies | FAQ
OFAC compliance for payment companies
OFAC compliance for payment companies
Payment companies process transactions — the core activity OFAC regulates. Every payment must be screened for: counterparty sanctions, jurisdictional restrictions, and prohibited transaction types. The volume of transactions makes automated, API-based screening essential.
\ No newline at end of file
diff --git a/faq/what-is-ofac-compliance-for-payment-infrastructure-providers/index.html b/faq/what-is-ofac-compliance-for-payment-infrastructure-providers/index.html
new file mode 100644
index 0000000..50192a2
--- /dev/null
+++ b/faq/what-is-ofac-compliance-for-payment-infrastructure-providers/index.html
@@ -0,0 +1 @@
+OFAC compliance for payment infrastructure providers | FAQ
OFAC compliance for payment infrastructure providers
OFAC compliance for payment infrastructure providers
Payment infrastructure providers are the plumbing of the financial system — and they have comprehensive screening obligations. Every transaction processed, every API call that moves money, must include sanctions screening. The provider's scale makes automated screening non-negotiable.
\ No newline at end of file
diff --git a/faq/what-is-ofac-compliance-for-web3-gaming/index.html b/faq/what-is-ofac-compliance-for-web3-gaming/index.html
new file mode 100644
index 0000000..9331792
--- /dev/null
+++ b/faq/what-is-ofac-compliance-for-web3-gaming/index.html
@@ -0,0 +1 @@
+OFAC compliance for Web3 gaming | FAQ
OFAC compliance for Web3 gaming
OFAC compliance for Web3 gaming
Web3 gaming combines gaming with real financial value. Player wallets receiving rewards, trading NFTs, or participating in game economies must be screened. A game that pays play-to-earn rewards to a sanctioned wallet has distributed value to an SDN.
\ No newline at end of file
diff --git a/faq/what-is-ofac-screening-for-agent-payments-explained/index.html b/faq/what-is-ofac-screening-for-agent-payments-explained/index.html
new file mode 100644
index 0000000..f37c753
--- /dev/null
+++ b/faq/what-is-ofac-screening-for-agent-payments-explained/index.html
@@ -0,0 +1 @@
+OFAC screening for agent payments explained | FAQ
OFAC screening for agent payments explained
OFAC screening for agent payments explained
AI agents processing payments are a new compliance frontier. The legal framework is in place: strict liability applies to agent-initiated payments just as it does to human-initiated ones. Pre-payment screening — one API call per transaction — is the minimum viable control.
\ No newline at end of file
diff --git a/faq/what-is-ofac-screening-for-agentic-commerce/index.html b/faq/what-is-ofac-screening-for-agentic-commerce/index.html
new file mode 100644
index 0000000..e66a7b9
--- /dev/null
+++ b/faq/what-is-ofac-screening-for-agentic-commerce/index.html
@@ -0,0 +1 @@
+OFAC screening for agentic commerce | FAQ
OFAC screening for agentic commerce
OFAC screening for agentic commerce
Agentic commerce is the emerging pattern of AI agents conducting commercial transactions without human intervention. Every autonomous purchase, sale, or payment must be screened for sanctions. The agent's commerce logic must include a pre-transaction screening gate.
\ No newline at end of file
diff --git a/faq/what-is-ofac-screening-for-ai-agent-marketplaces/index.html b/faq/what-is-ofac-screening-for-ai-agent-marketplaces/index.html
new file mode 100644
index 0000000..beb6f21
--- /dev/null
+++ b/faq/what-is-ofac-screening-for-ai-agent-marketplaces/index.html
@@ -0,0 +1 @@
+OFAC screening for AI agent marketplaces | FAQ
OFAC screening for AI agent marketplaces
OFAC screening for AI agent marketplaces
AI agent marketplaces are emerging platforms where agents transact with each other. Both the buying agent and the selling agent must be screened. The marketplace operator facilitates the transaction and bears compliance responsibility for what happens on its platform.
\ No newline at end of file
diff --git a/faq/what-is-ofac-screening-for-airdrops/index.html b/faq/what-is-ofac-screening-for-airdrops/index.html
new file mode 100644
index 0000000..d6ed313
--- /dev/null
+++ b/faq/what-is-ofac-screening-for-airdrops/index.html
@@ -0,0 +1 @@
+OFAC screening for airdrops | FAQ
OFAC screening for airdrops
OFAC screening for airdrops
Airdrops distribute tokens to wallet addresses — and those distributions are subject to OFAC. An airdrop that lands in a sanctioned wallet is a prohibited transaction. Screen the recipient list before executing the airdrop.
\ No newline at end of file
diff --git a/faq/what-is-ofac-screening-for-bridge-operators/index.html b/faq/what-is-ofac-screening-for-bridge-operators/index.html
new file mode 100644
index 0000000..5a8b72d
--- /dev/null
+++ b/faq/what-is-ofac-screening-for-bridge-operators/index.html
@@ -0,0 +1 @@
+OFAC screening for bridge operators | FAQ
OFAC screening for bridge operators
OFAC screening for bridge operators
Bridge operators are intermediaries facilitating cross-chain value transfers. Every transfer has a source chain/wallet and destination chain/wallet — both must be screened. The bridge operator can be liable for facilitating transfers involving sanctioned addresses.
\ No newline at end of file
diff --git a/faq/what-is-ofac-screening-for-central-bank-digital-currency/index.html b/faq/what-is-ofac-screening-for-central-bank-digital-currency/index.html
new file mode 100644
index 0000000..b5440f3
--- /dev/null
+++ b/faq/what-is-ofac-screening-for-central-bank-digital-currency/index.html
@@ -0,0 +1 @@
+OFAC screening for CBDCs | FAQ
OFAC screening for CBDCs
OFAC screening for CBDCs
CBDCs will likely incorporate sanctions screening at the infrastructure level — the central bank or authorized intermediaries will screen transactions. However, entities building on CBDC rails (payment apps, agent frameworks) should maintain independent screening.
\ No newline at end of file
diff --git a/faq/what-is-ofac-screening-for-cross-chain-bridges/index.html b/faq/what-is-ofac-screening-for-cross-chain-bridges/index.html
new file mode 100644
index 0000000..fbf0302
--- /dev/null
+++ b/faq/what-is-ofac-screening-for-cross-chain-bridges/index.html
@@ -0,0 +1 @@
+OFAC screening for cross-chain bridges | FAQ
OFAC screening for cross-chain bridges
OFAC screening for cross-chain bridges
Cross-chain bridges are value transfer points — and every transfer has a source and destination. Both must be screened. A bridge that moves assets from a sanctioned wallet on one chain to a clean wallet on another has facilitated sanctions evasion.
\ No newline at end of file
diff --git a/faq/what-is-ofac-screening-for-crypto-atms/index.html b/faq/what-is-ofac-screening-for-crypto-atms/index.html
new file mode 100644
index 0000000..aad7715
--- /dev/null
+++ b/faq/what-is-ofac-screening-for-crypto-atms/index.html
@@ -0,0 +1 @@
+OFAC screening for crypto ATMs | FAQ
OFAC screening for crypto ATMs
OFAC screening for crypto ATMs
Crypto ATMs are financial access points — they must verify customer identity (KYC) and screen for sanctions (OFAC) at the point of transaction. An ATM that dispenses crypto to a sanctioned individual has facilitated a prohibited transaction.
\ No newline at end of file
diff --git a/faq/what-is-ofac-screening-for-crypto-compliance/index.html b/faq/what-is-ofac-screening-for-crypto-compliance/index.html
new file mode 100644
index 0000000..0794626
--- /dev/null
+++ b/faq/what-is-ofac-screening-for-crypto-compliance/index.html
@@ -0,0 +1 @@
+OFAC screening for crypto compliance | FAQ
OFAC screening for crypto compliance
OFAC screening for crypto compliance
Crypto compliance is incomplete without OFAC screening. Every transaction — from exchange withdrawals to DeFi interactions to agent payments — must include a sanctions check. The screening call costs under 100ms and fractions of a cent.
\ No newline at end of file
diff --git a/faq/what-is-ofac-screening-for-crypto-debit-cards/index.html b/faq/what-is-ofac-screening-for-crypto-debit-cards/index.html
new file mode 100644
index 0000000..e3ed765
--- /dev/null
+++ b/faq/what-is-ofac-screening-for-crypto-debit-cards/index.html
@@ -0,0 +1 @@
+OFAC screening for crypto debit cards | FAQ
OFAC screening for crypto debit cards
OFAC screening for crypto debit cards
Crypto debit cards link a crypto wallet to a payment card. Each transaction involves converting crypto to fiat and processing a card payment — two compliance events. Both the card issuer and the underlying wallet must maintain screening.
\ No newline at end of file
diff --git a/faq/what-is-ofac-screening-for-crypto-payment-processors/index.html b/faq/what-is-ofac-screening-for-crypto-payment-processors/index.html
new file mode 100644
index 0000000..da3e903
--- /dev/null
+++ b/faq/what-is-ofac-screening-for-crypto-payment-processors/index.html
@@ -0,0 +1 @@
+OFAC screening for crypto payment processors | FAQ
OFAC screening for crypto payment processors
OFAC screening for crypto payment processors
Crypto payment processors that enable merchants to accept crypto sit between merchant and customer. Both must be screened: is the merchant sanctioned? Is the customer's wallet sanctioned? The processor facilitates the transaction and bears compliance responsibility.
\ No newline at end of file
diff --git a/faq/what-is-ofac-screening-for-custody-providers/index.html b/faq/what-is-ofac-screening-for-custody-providers/index.html
new file mode 100644
index 0000000..724c8dc
--- /dev/null
+++ b/faq/what-is-ofac-screening-for-custody-providers/index.html
@@ -0,0 +1 @@
+OFAC screening for custody providers | FAQ
OFAC screening for custody providers
OFAC screening for custody providers
Custody providers hold assets for clients. OFAC expects screening at: (1) Account opening — screen the client and beneficial owners. (2) Deposits — screen the source wallet. (3) Withdrawals — screen the destination wallet. (4) Periodic re-screening — re-check on SDN list updates.
\ No newline at end of file
diff --git a/faq/what-is-ofac-screening-for-defi-lending/index.html b/faq/what-is-ofac-screening-for-defi-lending/index.html
new file mode 100644
index 0000000..898ec5b
--- /dev/null
+++ b/faq/what-is-ofac-screening-for-defi-lending/index.html
@@ -0,0 +1 @@
+OFAC screening for DeFi lending protocols | FAQ
OFAC screening for DeFi lending protocols
OFAC screening for DeFi lending protocols
DeFi lending protocols pay interest to lenders. Those payments are subject to OFAC. If a sanctioned wallet deposits assets and earns interest, the protocol has distributed value to an SDN. Front-end wallet screening is the minimum defense.
\ No newline at end of file
diff --git a/faq/what-is-ofac-screening-for-digital-wallets/index.html b/faq/what-is-ofac-screening-for-digital-wallets/index.html
new file mode 100644
index 0000000..44ba9fa
--- /dev/null
+++ b/faq/what-is-ofac-screening-for-digital-wallets/index.html
@@ -0,0 +1 @@
+OFAC screening for digital wallets | FAQ
OFAC screening for digital wallets
OFAC screening for digital wallets
Digital wallet providers process payments and hold user funds. OFAC expects screening at both the transaction level (each payment is screened) and the account level (each user is screened at onboarding and periodically thereafter).
\ No newline at end of file
diff --git a/faq/what-is-ofac-screening-for-enterprise-blockchain/index.html b/faq/what-is-ofac-screening-for-enterprise-blockchain/index.html
new file mode 100644
index 0000000..0d8fbd1
--- /dev/null
+++ b/faq/what-is-ofac-screening-for-enterprise-blockchain/index.html
@@ -0,0 +1 @@
+OFAC screening for enterprise blockchain | FAQ
OFAC screening for enterprise blockchain
OFAC screening for enterprise blockchain
Enterprise blockchain networks with known participants still need sanctions screening. While permissioned networks have lower anonymity risk, participants may be designated or subject to sanctions between onboarding and transaction. Screen at onboarding and before every significant transaction.
\ No newline at end of file
diff --git a/faq/what-is-ofac-screening-for-governance-tokens/index.html b/faq/what-is-ofac-screening-for-governance-tokens/index.html
new file mode 100644
index 0000000..e3a0c5e
--- /dev/null
+++ b/faq/what-is-ofac-screening-for-governance-tokens/index.html
@@ -0,0 +1 @@
+OFAC screening for governance token distribution | FAQ
OFAC screening for governance token distribution
OFAC screening for governance token distribution
Governance token distribution to sanctioned wallets has dual risk: (1) The distribution itself is a prohibited transfer. (2) The SDN now holds governance power in your protocol, creating ongoing compliance exposure.
\ No newline at end of file
diff --git a/faq/what-is-ofac-screening-for-oracles/index.html b/faq/what-is-ofac-screening-for-oracles/index.html
new file mode 100644
index 0000000..939db10
--- /dev/null
+++ b/faq/what-is-ofac-screening-for-oracles/index.html
@@ -0,0 +1 @@
+OFAC screening for oracle networks | FAQ
OFAC screening for oracle networks
OFAC screening for oracle networks
Oracle networks primarily provide data, not process payments. Direct OFAC obligations are limited. However, if an oracle network's data feeds trigger financial transactions (e.g., liquidation on a lending protocol), the downstream effects may create indirect exposure.
\ No newline at end of file
diff --git a/faq/what-is-ofac-screening-for-otc-desks/index.html b/faq/what-is-ofac-screening-for-otc-desks/index.html
new file mode 100644
index 0000000..e9b4751
--- /dev/null
+++ b/faq/what-is-ofac-screening-for-otc-desks/index.html
@@ -0,0 +1 @@
+OFAC screening for OTC trading desks | FAQ
OFAC screening for OTC trading desks
OFAC screening for OTC trading desks
OTC desks facilitate large trades between parties. Every counterparty must be screened — the combination of large transaction values and often limited counterparty information makes OTC trading high-risk for sanctions compliance.
\ No newline at end of file
diff --git a/faq/what-is-ofac-screening-for-payment-aggregators/index.html b/faq/what-is-ofac-screening-for-payment-aggregators/index.html
new file mode 100644
index 0000000..a1cfbb5
--- /dev/null
+++ b/faq/what-is-ofac-screening-for-payment-aggregators/index.html
@@ -0,0 +1 @@
+OFAC screening for payment aggregators | FAQ
OFAC screening for payment aggregators
OFAC screening for payment aggregators
Payment aggregators consolidate payments from multiple merchants. Every merchant onboarded must be screened for sanctions. Every transaction processed must be screened. The aggregator is the compliance chokepoint for its entire merchant portfolio.
\ No newline at end of file
diff --git a/faq/what-is-ofac-screening-for-payment-networks/index.html b/faq/what-is-ofac-screening-for-payment-networks/index.html
new file mode 100644
index 0000000..093e3e7
--- /dev/null
+++ b/faq/what-is-ofac-screening-for-payment-networks/index.html
@@ -0,0 +1 @@
+OFAC screening for payment networks | FAQ
OFAC screening for payment networks
OFAC screening for payment networks
Traditional payment networks screen transactions for sanctions at the network level. Crypto payment networks and agent payment protocols (x402, AP2, ACP) must build equivalent screening into their infrastructure. The technology exists — the gap is adoption.
\ No newline at end of file
diff --git a/faq/what-is-ofac-screening-for-payment-orchestration/index.html b/faq/what-is-ofac-screening-for-payment-orchestration/index.html
new file mode 100644
index 0000000..4e6f367
--- /dev/null
+++ b/faq/what-is-ofac-screening-for-payment-orchestration/index.html
@@ -0,0 +1 @@
+OFAC screening for payment orchestration | FAQ
OFAC screening for payment orchestration
OFAC screening for payment orchestration
Payment orchestration platforms route transactions across providers — and each routing decision is a compliance decision. Screen before routing: is the destination provider, the payment method, and the counterparty all clear of sanctions?
\ No newline at end of file
diff --git a/faq/what-is-ofac-screening-for-payment-routing/index.html b/faq/what-is-ofac-screening-for-payment-routing/index.html
new file mode 100644
index 0000000..ce85845
--- /dev/null
+++ b/faq/what-is-ofac-screening-for-payment-routing/index.html
@@ -0,0 +1 @@
+OFAC screening for payment routing | FAQ
OFAC screening for payment routing
OFAC screening for payment routing
Payment routing — whether through correspondent banks, payment processors, or crypto bridges — creates multiple compliance touchpoints. Every intermediary in the chain may have OFAC obligations. The originator is ultimately responsible for the entire payment path.
\ No newline at end of file
diff --git a/faq/what-is-ofac-screening-for-payment-terminals/index.html b/faq/what-is-ofac-screening-for-payment-terminals/index.html
new file mode 100644
index 0000000..2d9835a
--- /dev/null
+++ b/faq/what-is-ofac-screening-for-payment-terminals/index.html
@@ -0,0 +1 @@
+OFAC screening for payment terminals | FAQ
OFAC screening for payment terminals
OFAC screening for payment terminals
Payment terminals — whether point-of-sale devices or digital checkout flows — process transactions that must be screened. The terminal operator, payment processor, and merchant may each have compliance obligations depending on the payment flow.
\ No newline at end of file
diff --git a/faq/what-is-ofac-screening-for-programmatic-payments/index.html b/faq/what-is-ofac-screening-for-programmatic-payments/index.html
new file mode 100644
index 0000000..7d551bb
--- /dev/null
+++ b/faq/what-is-ofac-screening-for-programmatic-payments/index.html
@@ -0,0 +1 @@
+OFAC screening for programmatic payments | FAQ
OFAC screening for programmatic payments
OFAC screening for programmatic payments
Programmatic payments are made by code — and screened by code. Add a screening API call immediately before the payment API call. The screening result determines whether the payment proceeds. This pattern works for any payment API: Stripe, Coinbase, x402, or direct wallet transfers.
\ No newline at end of file
diff --git a/faq/what-is-ofac-screening-for-real-world-assets/index.html b/faq/what-is-ofac-screening-for-real-world-assets/index.html
new file mode 100644
index 0000000..5889dac
--- /dev/null
+++ b/faq/what-is-ofac-screening-for-real-world-assets/index.html
@@ -0,0 +1 @@
+OFAC screening for tokenized real-world assets | FAQ
OFAC screening for tokenized real-world assets
OFAC screening for tokenized real-world assets
Tokenized real-world assets represent ownership of physical or financial assets. Transfers of these tokens are subject to OFAC — selling a tokenized real estate share to a sanctioned wallet is a prohibited transaction.
\ No newline at end of file
diff --git a/faq/what-is-ofac-screening-for-smart-contract-wallets/index.html b/faq/what-is-ofac-screening-for-smart-contract-wallets/index.html
new file mode 100644
index 0000000..eac3750
--- /dev/null
+++ b/faq/what-is-ofac-screening-for-smart-contract-wallets/index.html
@@ -0,0 +1 @@
+OFAC screening for smart contract wallets | FAQ
OFAC screening for smart contract wallets
OFAC screening for smart contract wallets
Smart contract wallets are programmable wallets that can execute complex transaction logic. They face the same OFAC obligations as any wallet: every outgoing transaction must screen the recipient. The programmability of the wallet doesn't exempt it — it may increase risk if the logic can circumvent screening.
\ No newline at end of file
diff --git a/faq/what-is-ofac-screening-for-stablecoin-payment-rails/index.html b/faq/what-is-ofac-screening-for-stablecoin-payment-rails/index.html
new file mode 100644
index 0000000..6085484
--- /dev/null
+++ b/faq/what-is-ofac-screening-for-stablecoin-payment-rails/index.html
@@ -0,0 +1 @@
+OFAC screening for stablecoin payment rails | FAQ
OFAC screening for stablecoin payment rails
OFAC screening for stablecoin payment rails
Stablecoin payment rails are the infrastructure for crypto-denominated payments. Both the rail operator (Circle, Tether) and the end user (you, your agent) have screening obligations. The rail operator screens at the contract level; you screen at the application level.
\ No newline at end of file
diff --git a/faq/what-is-ofac-screening-for-staking/index.html b/faq/what-is-ofac-screening-for-staking/index.html
new file mode 100644
index 0000000..db2463a
--- /dev/null
+++ b/faq/what-is-ofac-screening-for-staking/index.html
@@ -0,0 +1 @@
+OFAC screening for staking rewards | FAQ
OFAC screening for staking rewards
OFAC screening for staking rewards
Staking rewards are distributions of value. If a validator or staking pool distributes rewards to a sanctioned wallet, the distribution is a prohibited transaction. Screen staking reward recipients the same as any payment.
\ No newline at end of file
diff --git a/faq/what-is-ofac-screening-for-token-vesting/index.html b/faq/what-is-ofac-screening-for-token-vesting/index.html
new file mode 100644
index 0000000..f0befa6
--- /dev/null
+++ b/faq/what-is-ofac-screening-for-token-vesting/index.html
@@ -0,0 +1 @@
+OFAC screening for token vesting | FAQ
OFAC screening for token vesting
OFAC screening for token vesting
Token vesting involves periodic distributions. Each distribution is a separate transaction that must be screened. A vesting contract that releases tokens to a wallet that becomes sanctioned mid-vesting creates a violation at each subsequent release.
\ No newline at end of file
diff --git a/faq/what-is-ofac-screening-for-treasury-management/index.html b/faq/what-is-ofac-screening-for-treasury-management/index.html
new file mode 100644
index 0000000..325de68
--- /dev/null
+++ b/faq/what-is-ofac-screening-for-treasury-management/index.html
@@ -0,0 +1 @@
+OFAC screening for treasury management | FAQ
OFAC screening for treasury management
OFAC screening for treasury management
Treasury operations involve high-value payments to counterparties. Every treasury payment must be screened — the combination of high value and potential international counterparties makes these transactions high-risk for OFAC.
\ No newline at end of file
diff --git a/faq/what-is-ofac-screening-for-validators/index.html b/faq/what-is-ofac-screening-for-validators/index.html
new file mode 100644
index 0000000..32ecbb2
--- /dev/null
+++ b/faq/what-is-ofac-screening-for-validators/index.html
@@ -0,0 +1 @@
+OFAC screening for blockchain validators | FAQ
OFAC screening for blockchain validators
OFAC screening for blockchain validators
Validators that include sanctioned transactions in blocks may have facilitation exposure. Several major validators have implemented OFAC-compliant transaction filtering. MEV (Maximal Extractable Value) adds complexity: validators may be seen as actively choosing which transactions to include.
\ No newline at end of file
diff --git a/glossary/ofac-blocked-property/index.html b/glossary/ofac-blocked-property/index.html
new file mode 100644
index 0000000..4b48836
--- /dev/null
+++ b/glossary/ofac-blocked-property/index.html
@@ -0,0 +1 @@
+OFAC Blocked Property | Glossary
OFAC Blocked Property
OFAC Blocked Property
Blocked property is any asset — funds, crypto, securities, real estate — that cannot be transferred because an SDN has an interest in it. The blocking party must: hold the property, file a report within 10 business days, and await OFAC authorization for disposition.
\ No newline at end of file
diff --git a/glossary/ofac-compliance-documentation/index.html b/glossary/ofac-compliance-documentation/index.html
new file mode 100644
index 0000000..a5d929b
--- /dev/null
+++ b/glossary/ofac-compliance-documentation/index.html
@@ -0,0 +1 @@
+OFAC Compliance Documentation | Glossary
OFAC Compliance Documentation
OFAC Compliance Documentation
Compliance documentation is the paper trail that proves your program exists and operates. OFAC considers documented programs a significant mitigating factor. Undocumented programs are treated as if they don't exist.
\ No newline at end of file
diff --git a/glossary/ofac-compliance-third-party-risk/index.html b/glossary/ofac-compliance-third-party-risk/index.html
new file mode 100644
index 0000000..71c48ca
--- /dev/null
+++ b/glossary/ofac-compliance-third-party-risk/index.html
@@ -0,0 +1 @@
+OFAC Third-Party Risk | Glossary
OFAC Third-Party Risk
OFAC Third-Party Risk
Third-party risk: your vendors can create sanctions exposure for you. A payment processor that doesn't screen, a KYC provider that misses a sanctioned customer, or a technology partner in a sanctioned jurisdiction — all create downstream risk for your organization.
\ No newline at end of file
diff --git a/glossary/ofac-contractual-compliance/index.html b/glossary/ofac-contractual-compliance/index.html
new file mode 100644
index 0000000..3cce1cd
--- /dev/null
+++ b/glossary/ofac-contractual-compliance/index.html
@@ -0,0 +1 @@
+OFAC Contractual Compliance | Glossary
OFAC Contractual Compliance
OFAC Contractual Compliance
Contractual compliance provisions require counterparties to represent they are not SDNs, agree to screening, and accept transaction blocking. These provisions provide legal protection but do not replace operational screening — you must still screen, not just contractually promise to.
\ No newline at end of file
diff --git a/glossary/ofac-facilitation-risk/index.html b/glossary/ofac-facilitation-risk/index.html
new file mode 100644
index 0000000..eaa8871
--- /dev/null
+++ b/glossary/ofac-facilitation-risk/index.html
@@ -0,0 +1 @@
+OFAC Facilitation Risk | Glossary
OFAC Facilitation Risk
OFAC Facilitation Risk
Facilitation risk arises when your actions enable a prohibited transaction by another party. Examples: processing a payment that routes through a sanctioned intermediary, providing services that a sanctioned entity benefits from, or operating a platform where sanctioned parties transact.
\ No newline at end of file
diff --git a/glossary/ofac-independent-audit/index.html b/glossary/ofac-independent-audit/index.html
new file mode 100644
index 0000000..e6ca4f1
--- /dev/null
+++ b/glossary/ofac-independent-audit/index.html
@@ -0,0 +1 @@
+OFAC Independent Audit | Glossary
OFAC Independent Audit
OFAC Independent Audit
An independent audit brings an outside perspective to your compliance program. Auditors review documentation, test controls, interview personnel, and issue findings. OFAC considers independent audits a strong mitigating factor in enforcement actions.
\ No newline at end of file
diff --git a/glossary/ofac-rejected-vs-blocked/index.html b/glossary/ofac-rejected-vs-blocked/index.html
new file mode 100644
index 0000000..db73ecc
--- /dev/null
+++ b/glossary/ofac-rejected-vs-blocked/index.html
@@ -0,0 +1 @@
+OFAC Rejected vs Blocked Transaction | Glossary
OFAC Rejected vs Blocked Transaction
OFAC Rejected vs Blocked Transaction
Rejected: you identify a potential sanctions match and refuse to process the transaction — no funds moved, no blocked property report required. Blocked: funds were already in motion when the match was identified — a blocked property report is mandatory within 10 days.
\ No newline at end of file
diff --git a/glossary/ofac-risk-assessment-framework/index.html b/glossary/ofac-risk-assessment-framework/index.html
new file mode 100644
index 0000000..4ad2d02
--- /dev/null
+++ b/glossary/ofac-risk-assessment-framework/index.html
@@ -0,0 +1 @@
+OFAC Risk Assessment Framework | Glossary
OFAC Risk Assessment Framework
OFAC Risk Assessment Framework
The risk assessment framework evaluates four dimensions: customer risk, geographic risk, product/service risk, and channel/agent risk. Each dimension is scored (Low/Medium/High) and controls are mapped to each risk.
\ No newline at end of file
diff --git a/glossary/ofac-screening-alert-fatigue/index.html b/glossary/ofac-screening-alert-fatigue/index.html
new file mode 100644
index 0000000..5c21883
--- /dev/null
+++ b/glossary/ofac-screening-alert-fatigue/index.html
@@ -0,0 +1 @@
+OFAC Screening Alert Fatigue | Glossary
OFAC Screening Alert Fatigue
OFAC Screening Alert Fatigue
Alert fatigue occurs when the volume of false positives is so high that compliance teams cannot review them all effectively — and real matches slip through. Mitigation: tune screening thresholds, use multi-parameter screening to reduce false positives, and automate false-positive resolution where possible.
\ No newline at end of file
diff --git a/glossary/ofac-screening-automation/index.html b/glossary/ofac-screening-automation/index.html
new file mode 100644
index 0000000..e97ba0c
--- /dev/null
+++ b/glossary/ofac-screening-automation/index.html
@@ -0,0 +1 @@
+OFAC Screening Automation | Glossary
OFAC Screening Automation
OFAC Screening Automation
Screening automation replaces manual SDN list searches with API-driven, real-time checks. For AI agents and high-volume payment systems, automation is the only viable approach — manual screening cannot keep pace with machine-speed transactions.
\ No newline at end of file
diff --git a/glossary/ofac-screening-availability/index.html b/glossary/ofac-screening-availability/index.html
new file mode 100644
index 0000000..e837159
--- /dev/null
+++ b/glossary/ofac-screening-availability/index.html
@@ -0,0 +1 @@
+OFAC Screening Availability | Glossary
OFAC Screening Availability
OFAC Screening Availability
Screening availability is operationally critical. If your screening API is down, you face a choice: block all transactions (revenue impact) or process unscreened transactions (compliance risk). Design your system to fail closed — block transactions when screening is unavailable.
\ No newline at end of file
diff --git a/glossary/ofac-screening-batch/index.html b/glossary/ofac-screening-batch/index.html
new file mode 100644
index 0000000..2b63f8d
--- /dev/null
+++ b/glossary/ofac-screening-batch/index.html
@@ -0,0 +1 @@
+Batch OFAC Screening | Glossary
Batch OFAC Screening
Batch OFAC Screening
Batch screening processes multiple checks at once — useful for periodic portfolio reviews, customer base re-screening, and historical transaction analysis. It's complementary to real-time screening, not a substitute.
\ No newline at end of file
diff --git a/glossary/ofac-screening-caching/index.html b/glossary/ofac-screening-caching/index.html
new file mode 100644
index 0000000..eb65d94
--- /dev/null
+++ b/glossary/ofac-screening-caching/index.html
@@ -0,0 +1 @@
+OFAC Screening Caching | Glossary
OFAC Screening Caching
OFAC Screening Caching
Caching can reduce API costs and latency for repeat counterparties. However, cached results become stale when the SDN list updates — a counterparty that was clean when cached may be designated later. Cache TTL must be short (minutes, not hours) and invalidated on list updates.
\ No newline at end of file
diff --git a/glossary/ofac-screening-compliance-tech-stack/index.html b/glossary/ofac-screening-compliance-tech-stack/index.html
new file mode 100644
index 0000000..53ea804
--- /dev/null
+++ b/glossary/ofac-screening-compliance-tech-stack/index.html
@@ -0,0 +1 @@
+OFAC Compliance Technology Stack | Glossary
OFAC Compliance Technology Stack
OFAC Compliance Technology Stack
A compliance tech stack typically includes: a screening API (SanctionsAI), log storage (database or managed service), alert management (notification system for matches), and reporting tools (for regulator and auditor requests). The stack scales with transaction volume and organizational complexity.
\ No newline at end of file
diff --git a/glossary/ofac-screening-coverage-analysis/index.html b/glossary/ofac-screening-coverage-analysis/index.html
new file mode 100644
index 0000000..027193c
--- /dev/null
+++ b/glossary/ofac-screening-coverage-analysis/index.html
@@ -0,0 +1 @@
+OFAC Screening Coverage Analysis | Glossary
OFAC Screening Coverage Analysis
OFAC Screening Coverage Analysis
Coverage analysis answers: are 100% of transactions screened? If not, which payment types, channels, or agent types are missed? Common gaps: agent payments, API-driven transactions, and crypto transfers through non-custodial wallets.
\ No newline at end of file
diff --git a/glossary/ofac-screening-data-retention/index.html b/glossary/ofac-screening-data-retention/index.html
new file mode 100644
index 0000000..510f49d
--- /dev/null
+++ b/glossary/ofac-screening-data-retention/index.html
@@ -0,0 +1 @@
+OFAC Screening Data Retention | Glossary
OFAC Screening Data Retention
OFAC Screening Data Retention
Data retention for screening logs: OFAC expects records to be available for investigation — 5 years is the standard minimum. Screening logs must include: timestamp, counterparty identifier, screening inputs, screening result, and disposition.
\ No newline at end of file
diff --git a/glossary/ofac-screening-error-handling/index.html b/glossary/ofac-screening-error-handling/index.html
new file mode 100644
index 0000000..5ac0361
--- /dev/null
+++ b/glossary/ofac-screening-error-handling/index.html
@@ -0,0 +1 @@
+OFAC Screening Error Handling | Glossary
OFAC Screening Error Handling
OFAC Screening Error Handling
Error handling is a compliance decision: if the screening API is unavailable or returns an error, do you allow the transaction (fail open) or block it (fail closed)? OFAC expects fail-closed — blocking on uncertainty. This protects compliance but requires high screening API availability.
\ No newline at end of file
diff --git a/glossary/ofac-screening-escalation/index.html b/glossary/ofac-screening-escalation/index.html
new file mode 100644
index 0000000..af539e2
--- /dev/null
+++ b/glossary/ofac-screening-escalation/index.html
@@ -0,0 +1 @@
+OFAC Screening Escalation Procedure | Glossary
OFAC Screening Escalation Procedure
OFAC Screening Escalation Procedure
Escalation procedure: when a potential match is identified, who reviews it? In what timeframe? What information do they need? What are the possible dispositions (true match → block/report, false positive → document/dismiss)? Every screening program needs a documented escalation path.
\ No newline at end of file
diff --git a/glossary/ofac-screening-for-belarus/index.html b/glossary/ofac-screening-for-belarus/index.html
new file mode 100644
index 0000000..39124cf
--- /dev/null
+++ b/glossary/ofac-screening-for-belarus/index.html
@@ -0,0 +1 @@
+OFAC Belarus Sanctions Screening | Glossary
OFAC Belarus Sanctions Screening
OFAC Belarus Sanctions Screening
Belarus sanctions target government officials and state-owned enterprises — particularly after Belarus facilitated Russia's actions in Ukraine. Multiple Belarusian banks and defense-sector entities are designated. Screen carefully, but not all Belarus transactions are prohibited.
\ No newline at end of file
diff --git a/glossary/ofac-screening-for-cuba/index.html b/glossary/ofac-screening-for-cuba/index.html
new file mode 100644
index 0000000..1d2d494
--- /dev/null
+++ b/glossary/ofac-screening-for-cuba/index.html
@@ -0,0 +1 @@
+OFAC Cuba Sanctions Screening | Glossary
OFAC Cuba Sanctions Screening
OFAC Cuba Sanctions Screening
Cuba sanctions are comprehensive — virtually all transactions prohibited unless specifically authorized. Exceptions exist for: family remittances, humanitarian projects, certain telecommunications services, and travel under 12 authorized categories. Screen every Cuba-related transaction carefully.
\ No newline at end of file
diff --git a/glossary/ofac-screening-for-cyber/index.html b/glossary/ofac-screening-for-cyber/index.html
new file mode 100644
index 0000000..66c1c39
--- /dev/null
+++ b/glossary/ofac-screening-for-cyber/index.html
@@ -0,0 +1 @@
+OFAC Cyber-Related Sanctions | Glossary
OFAC Cyber-Related Sanctions
OFAC Cyber-Related Sanctions
Cyber sanctions under EO 13694 (as amended) target: state-sponsored cyber actors (Russian GRU, Chinese APT groups, North Korean Lazarus), ransomware operators (Evil Corp), and entities facilitating malicious cyber activity (cryptocurrency exchanges processing ransomware payments).
\ No newline at end of file
diff --git a/glossary/ofac-screening-for-human-rights/index.html b/glossary/ofac-screening-for-human-rights/index.html
new file mode 100644
index 0000000..a681e1d
--- /dev/null
+++ b/glossary/ofac-screening-for-human-rights/index.html
@@ -0,0 +1 @@
+OFAC Human Rights Sanctions | Glossary
OFAC Human Rights Sanctions
OFAC Human Rights Sanctions
The Global Magnitsky Human Rights Accountability Act authorizes sanctions on individuals and entities involved in: gross human rights abuses, significant corruption, or actions undermining democratic processes. Designations are not country-specific — they apply worldwide.
\ No newline at end of file
diff --git a/glossary/ofac-screening-for-iran/index.html b/glossary/ofac-screening-for-iran/index.html
new file mode 100644
index 0000000..7aaeb67
--- /dev/null
+++ b/glossary/ofac-screening-for-iran/index.html
@@ -0,0 +1 @@
+OFAC Iran Sanctions Screening | Glossary
OFAC Iran Sanctions Screening
OFAC Iran Sanctions Screening
Iran is subject to comprehensive US sanctions. Prohibited: virtually all transactions with Iranian persons, entities, and the government. Exceptions: humanitarian goods (food, medicine), personal communications services, and certain information services under general licenses.
\ No newline at end of file
diff --git a/glossary/ofac-screening-for-myanmar/index.html b/glossary/ofac-screening-for-myanmar/index.html
new file mode 100644
index 0000000..6c07e7a
--- /dev/null
+++ b/glossary/ofac-screening-for-myanmar/index.html
@@ -0,0 +1 @@
+OFAC Myanmar Sanctions Screening | Glossary
OFAC Myanmar Sanctions Screening
OFAC Myanmar Sanctions Screening
Myanmar sanctions target the military regime (Tatmadaw), military-owned enterprises (gems, timber, banking), and officials involved in the coup and subsequent human rights abuses. Not comprehensive — transactions with non-designated Myanmar persons are generally permissible.
\ No newline at end of file
diff --git a/glossary/ofac-screening-for-narcotics/index.html b/glossary/ofac-screening-for-narcotics/index.html
new file mode 100644
index 0000000..f0f12b1
--- /dev/null
+++ b/glossary/ofac-screening-for-narcotics/index.html
@@ -0,0 +1 @@
+OFAC Counter-Narcotics Sanctions | Glossary
OFAC Counter-Narcotics Sanctions
OFAC Counter-Narcotics Sanctions
Narcotics sanctions target drug trafficking organizations (cartels) under the Foreign Narcotics Kingpin Designation Act. Designated: cartel leaders, facilitators, front companies, and financial networks. These designations appear on the SDN list and carry full blocking and transaction prohibitions.
\ No newline at end of file
diff --git a/glossary/ofac-screening-for-non-proliferation/index.html b/glossary/ofac-screening-for-non-proliferation/index.html
new file mode 100644
index 0000000..ee6b3a7
--- /dev/null
+++ b/glossary/ofac-screening-for-non-proliferation/index.html
@@ -0,0 +1 @@
+OFAC Non-Proliferation Sanctions | Glossary
OFAC Non-Proliferation Sanctions
OFAC Non-Proliferation Sanctions
Non-proliferation sanctions target entities involved in the development, production, or transfer of weapons of mass destruction and their delivery systems. Designations cover North Korean, Iranian, and other WMD programs, plus the entities that supply them.
\ No newline at end of file
diff --git a/glossary/ofac-screening-for-north-korea/index.html b/glossary/ofac-screening-for-north-korea/index.html
new file mode 100644
index 0000000..2746d0a
--- /dev/null
+++ b/glossary/ofac-screening-for-north-korea/index.html
@@ -0,0 +1 @@
+OFAC North Korea Sanctions Screening | Glossary
OFAC North Korea Sanctions Screening
OFAC North Korea Sanctions Screening
North Korea is subject to comprehensive OFAC sanctions — virtually all transactions with North Korean persons, entities, or the government are prohibited. OFAC has specifically targeted North Korean cyber actors (Lazarus Group) and their cryptocurrency theft and laundering operations.
\ No newline at end of file
diff --git a/glossary/ofac-screening-for-ransomware/index.html b/glossary/ofac-screening-for-ransomware/index.html
new file mode 100644
index 0000000..71e3f91
--- /dev/null
+++ b/glossary/ofac-screening-for-ransomware/index.html
@@ -0,0 +1 @@
+OFAC Ransomware Screening | Glossary
OFAC Ransomware Screening
OFAC Ransomware Screening
Ransomware screening: OFAC has designated ransomware groups (Evil Corp, Conti, REvil variants) and their wallets. Paying ransom to a designated entity is prohibited — even through intermediaries. OFAC's 2020 advisory warned that facilitators (insurers, negotiators) may also face liability.
\ No newline at end of file
diff --git a/glossary/ofac-screening-for-russia/index.html b/glossary/ofac-screening-for-russia/index.html
new file mode 100644
index 0000000..5c8f1d0
--- /dev/null
+++ b/glossary/ofac-screening-for-russia/index.html
@@ -0,0 +1 @@
+OFAC Russia Sanctions Screening | Glossary
OFAC Russia Sanctions Screening
OFAC Russia Sanctions Screening
Russia sanctions are extensive but not comprehensive — many transactions with non-designated Russian persons remain permissible. However, the SDN list includes hundreds of Russian individuals and entities, and sectoral sanctions restrict transactions in financial services, energy, and defense.
\ No newline at end of file
diff --git a/glossary/ofac-screening-for-sanctions-evasion/index.html b/glossary/ofac-screening-for-sanctions-evasion/index.html
new file mode 100644
index 0000000..45f5798
--- /dev/null
+++ b/glossary/ofac-screening-for-sanctions-evasion/index.html
@@ -0,0 +1 @@
+Sanctions Evasion Detection | Glossary
Sanctions Evasion Detection
Sanctions Evasion Detection
Evasion detection goes beyond point-in-time screening to identify patterns: structuring (breaking large transactions into small ones), layering (routing through multiple intermediaries), and concealment (using privacy tools or shell companies). These patterns are red flags even without a direct SDN match.
\ No newline at end of file
diff --git a/glossary/ofac-screening-for-sanctions-lists/index.html b/glossary/ofac-screening-for-sanctions-lists/index.html
new file mode 100644
index 0000000..5baebe4
--- /dev/null
+++ b/glossary/ofac-screening-for-sanctions-lists/index.html
@@ -0,0 +1 @@
+Sanctions Lists | Glossary
Sanctions Lists
Sanctions Lists
OFAC maintains multiple lists: SDN (Specially Designated Nationals — blocked persons), SSI (Sectoral Sanctions Identifications — restricted but not blocked), FSE (Foreign Sanctions Evaders), NS-PLC (Non-SDN Palestinian Legislative Council), and CAPTA (financial institutions subject to correspondent account sanctions).
\ No newline at end of file
diff --git a/glossary/ofac-screening-for-syria/index.html b/glossary/ofac-screening-for-syria/index.html
new file mode 100644
index 0000000..523da18
--- /dev/null
+++ b/glossary/ofac-screening-for-syria/index.html
@@ -0,0 +1 @@
+OFAC Syria Sanctions Screening | Glossary
OFAC Syria Sanctions Screening
OFAC Syria Sanctions Screening
Syria is subject to comprehensive US sanctions. Prohibited: virtually all transactions with Syrian persons, entities, and the government. Humanitarian exceptions exist for food, medicine, and medical devices. The ongoing conflict adds complexity — screen carefully for government and designated entity connections.
\ No newline at end of file
diff --git a/glossary/ofac-screening-for-terrorism/index.html b/glossary/ofac-screening-for-terrorism/index.html
new file mode 100644
index 0000000..2dddec0
--- /dev/null
+++ b/glossary/ofac-screening-for-terrorism/index.html
@@ -0,0 +1 @@
+OFAC Counter-Terrorism Sanctions | Glossary
OFAC Counter-Terrorism Sanctions
OFAC Counter-Terrorism Sanctions
Counter-terrorism sanctions under EO 13224 target terrorist organizations (ISIS, al-Qaeda, Hamas, Hezbollah, Taliban, and many others), their leaders, financiers, and facilitators. SDGT designations are among the most numerous on the SDN list and carry broad prohibitions.
\ No newline at end of file
diff --git a/glossary/ofac-screening-for-transnational-crime/index.html b/glossary/ofac-screening-for-transnational-crime/index.html
new file mode 100644
index 0000000..6459ed9
--- /dev/null
+++ b/glossary/ofac-screening-for-transnational-crime/index.html
@@ -0,0 +1 @@
+OFAC Transnational Crime Sanctions | Glossary
OFAC Transnational Crime Sanctions
OFAC Transnational Crime Sanctions
Transnational crime sanctions under EO 13581 target organizations involved in: human trafficking, wildlife trafficking, illicit trade, cybercrime, and other transnational criminal activity. Designations focus on the financial networks that enable these organizations.
\ No newline at end of file
diff --git a/glossary/ofac-screening-for-ukraine/index.html b/glossary/ofac-screening-for-ukraine/index.html
new file mode 100644
index 0000000..7f8e443
--- /dev/null
+++ b/glossary/ofac-screening-for-ukraine/index.html
@@ -0,0 +1 @@
+OFAC Ukraine/Russia Sanctions Screening | Glossary
OFAC Ukraine/Russia Sanctions Screening
OFAC Ukraine/Russia Sanctions Screening
Ukraine-related sanctions: Crimea region — comprehensive sanctions, virtually all transactions prohibited. Donetsk and Luhansk (DNR/LNR) — targeted sanctions on officials and entities. Extensive SDN designations of Russian officials, oligarchs, and entities involved in the invasion.
\ No newline at end of file
diff --git a/glossary/ofac-screening-for-venezuela/index.html b/glossary/ofac-screening-for-venezuela/index.html
new file mode 100644
index 0000000..4aade17
--- /dev/null
+++ b/glossary/ofac-screening-for-venezuela/index.html
@@ -0,0 +1 @@
+OFAC Venezuela Sanctions Screening | Glossary
OFAC Venezuela Sanctions Screening
OFAC Venezuela Sanctions Screening
Venezuela sanctions are targeted — not comprehensive. Designated: government officials, PDVSA (state oil company), the Venezuelan government's digital currency (Petro), and entities involved in corruption or human rights abuses. Transactions with non-designated Venezuelan persons are generally permissible.
\ No newline at end of file
diff --git a/glossary/ofac-screening-governance/index.html b/glossary/ofac-screening-governance/index.html
new file mode 100644
index 0000000..ee82cde
--- /dev/null
+++ b/glossary/ofac-screening-governance/index.html
@@ -0,0 +1 @@
+OFAC Screening Governance | Glossary
OFAC Screening Governance
OFAC Screening Governance
Governance defines who is responsible for compliance. Key elements: designated compliance officer, reporting line to senior management or board, defined review cadence (at least annually), and documented escalation paths for compliance issues.
\ No newline at end of file
diff --git a/glossary/ofac-screening-jurisdictional-risk/index.html b/glossary/ofac-screening-jurisdictional-risk/index.html
new file mode 100644
index 0000000..80495f4
--- /dev/null
+++ b/glossary/ofac-screening-jurisdictional-risk/index.html
@@ -0,0 +1 @@
+OFAC Jurisdictional Risk | Glossary
OFAC Jurisdictional Risk
OFAC Jurisdictional Risk
Jurisdictional risk tiers: Comprehensively sanctioned (Cuba, Iran, North Korea, Syria, Crimea) — virtually all transactions prohibited. Targeted sanctions (Russia, Belarus, Venezuela) — specific entities and sectors restricted. High-risk (China/Hong Kong, Myanmar) — enhanced due diligence warranted.
\ No newline at end of file
diff --git a/glossary/ofac-screening-key-management/index.html b/glossary/ofac-screening-key-management/index.html
new file mode 100644
index 0000000..acdb3c1
--- /dev/null
+++ b/glossary/ofac-screening-key-management/index.html
@@ -0,0 +1 @@
+OFAC Screening API Key Management | Glossary
OFAC Screening API Key Management
OFAC Screening API Key Management
API key management: store keys in environment variables or secrets managers (not in code), rotate keys periodically, use separate keys for development and production, and restrict key access to authorized systems. A compromised screening key can be used to bypass screening.
\ No newline at end of file
diff --git a/glossary/ofac-screening-penalty-calculator/index.html b/glossary/ofac-screening-penalty-calculator/index.html
new file mode 100644
index 0000000..0cc3d68
--- /dev/null
+++ b/glossary/ofac-screening-penalty-calculator/index.html
@@ -0,0 +1 @@
+OFAC Penalty Calculator | Glossary
OFAC Penalty Calculator
OFAC Penalty Calculator
Penalty calculators estimate potential fines based on OFAC's Enforcement Guidelines. Inputs: violation type (egregious/non-egregious), transaction value, voluntary disclosure status, and presence of mitigating factors. Output: estimated penalty range. SanctionsAI provides free penalty estimation at /cost/ofac-enforcement-actions.
\ No newline at end of file
diff --git a/glossary/ofac-screening-programs-list/index.html b/glossary/ofac-screening-programs-list/index.html
new file mode 100644
index 0000000..a9c6bfe
--- /dev/null
+++ b/glossary/ofac-screening-programs-list/index.html
@@ -0,0 +1 @@
+OFAC Sanctions Programs List | Glossary
OFAC Sanctions Programs List
OFAC Sanctions Programs List
OFAC programs include: Balkans, Belarus, Burma/Myanmar, Central African Republic, China (Xinjiang/Hong Kong), Cuba, Cyber-Related, DRC, Ethiopia, Foreign Interference, Global Magnitsky, Haiti, Iran, Iraq, Lebanon, Libya, Mali, Nicaragua, North Korea, Russia/Ukraine, Somalia, Sudan, Syria, Terrorism, Transnational Crime, Venezuela, Yemen, Zimbabwe, and more.
\ No newline at end of file
diff --git a/glossary/ofac-screening-rate-limiting/index.html b/glossary/ofac-screening-rate-limiting/index.html
new file mode 100644
index 0000000..8481079
--- /dev/null
+++ b/glossary/ofac-screening-rate-limiting/index.html
@@ -0,0 +1 @@
+OFAC Screening Rate Limiting | Glossary
OFAC Screening Rate Limiting
OFAC Screening Rate Limiting
Rate limiting controls API usage: free tier (5 checks/day), Dev plan (10K/month), Pro plan (100K/month). Rate limits are enforced per API key. Exceeding limits typically results in 429 (Too Many Requests) responses — your application should handle this gracefully.
\ No newline at end of file
diff --git a/glossary/ofac-screening-real-time/index.html b/glossary/ofac-screening-real-time/index.html
new file mode 100644
index 0000000..1a5e693
--- /dev/null
+++ b/glossary/ofac-screening-real-time/index.html
@@ -0,0 +1 @@
+Real-Time OFAC Screening | Glossary
Real-Time OFAC Screening
Real-Time OFAC Screening
Real-time screening checks counterparties at transaction time — not in batch, not end-of-day, not weekly. The screening completes in under 100ms and the transaction either proceeds (clean) or is blocked (match). This is the gold standard for payment screening.
\ No newline at end of file
diff --git a/glossary/ofac-screening-remediation/index.html b/glossary/ofac-screening-remediation/index.html
new file mode 100644
index 0000000..ccba9b2
--- /dev/null
+++ b/glossary/ofac-screening-remediation/index.html
@@ -0,0 +1 @@
+OFAC Screening Remediation | Glossary
OFAC Screening Remediation
OFAC Screening Remediation
Remediation closes compliance gaps. Examples: adding screening to previously un-screened payment paths, upgrading screening technology, improving list sync frequency, enhancing documentation, or providing additional training.
\ No newline at end of file
diff --git a/glossary/ofac-screening-response-time/index.html b/glossary/ofac-screening-response-time/index.html
new file mode 100644
index 0000000..cea34d6
--- /dev/null
+++ b/glossary/ofac-screening-response-time/index.html
@@ -0,0 +1 @@
+OFAC Screening Response Time | Glossary
OFAC Screening Response Time
OFAC Screening Response Time
Response time is critical for payment screening — it adds directly to the user's perceived transaction time. Sub-100ms is the standard; sub-50ms is excellent. Slower response times may work for batch or periodic screening but not for real-time payment decisions.
\ No newline at end of file
diff --git a/glossary/ofac-screening-sdk-documentation/index.html b/glossary/ofac-screening-sdk-documentation/index.html
new file mode 100644
index 0000000..7a8deba
--- /dev/null
+++ b/glossary/ofac-screening-sdk-documentation/index.html
@@ -0,0 +1 @@
+OFAC Screening SDK Documentation | Glossary
OFAC Screening SDK Documentation
OFAC Screening SDK Documentation
SDK documentation is the developer's entry point to screening. Good documentation includes: quickstart guide, API reference with examples, integration patterns for common frameworks, error handling guidance, and testing procedures.
\ No newline at end of file
diff --git a/glossary/ofac-screening-webhook/index.html b/glossary/ofac-screening-webhook/index.html
new file mode 100644
index 0000000..2a3058c
--- /dev/null
+++ b/glossary/ofac-screening-webhook/index.html
@@ -0,0 +1 @@
+OFAC Screening Webhook | Glossary
OFAC Screening Webhook
OFAC Screening Webhook
A screening webhook pushes match notifications to your application rather than requiring you to poll for results. When a sanctions match occurs, the webhook fires immediately — enabling real-time blocking and alerting.
\ No newline at end of file
diff --git a/glossary/ofac-transaction-monitoring/index.html b/glossary/ofac-transaction-monitoring/index.html
new file mode 100644
index 0000000..5a6ff70
--- /dev/null
+++ b/glossary/ofac-transaction-monitoring/index.html
@@ -0,0 +1 @@
+OFAC Transaction Monitoring | Glossary
OFAC Transaction Monitoring
OFAC Transaction Monitoring
Transaction monitoring goes beyond point-in-time screening to detect patterns: structuring, rapid-fire small payments, jurisdictional hopping, and other evasion techniques. It's the detective control that complements preventative screening.
\ No newline at end of file
diff --git a/glossary/sanctions-screening-service-provider/index.html b/glossary/sanctions-screening-service-provider/index.html
new file mode 100644
index 0000000..da64518
--- /dev/null
+++ b/glossary/sanctions-screening-service-provider/index.html
@@ -0,0 +1 @@
+Sanctions Screening Service Provider | Glossary
Sanctions Screening Service Provider
Sanctions Screening Service Provider
Service providers range from API-only solutions (SanctionsAI) to full-service compliance platforms. Selection criteria: technology quality, list coverage, integration patterns, pricing model, support quality, and regulatory track record.
\ No newline at end of file
diff --git a/learn/how-ofac-enforcement-has-evolved-for-crypto/index.html b/learn/how-ofac-enforcement-has-evolved-for-crypto/index.html
new file mode 100644
index 0000000..5ac8ec9
--- /dev/null
+++ b/learn/how-ofac-enforcement-has-evolved-for-crypto/index.html
@@ -0,0 +1 @@
+How OFAC enforcement has evolved for crypto 2018-2026 | Learn
How OFAC enforcement has evolved for crypto 2018-2026
How OFAC enforcement has evolved for crypto 2018-2026
Evolution: 2018 — first crypto wallet addresses added to SDN list. 2019 — early enforcement actions (Ericsson, no crypto-specific cases). 2020 — first crypto penalties (BitGo, BitPay). 2021 — exchange designations begin (SUEX, Chatex). 2022 — mixer designations (Tornado Cash, Blender.io), enforcement ramps. 2023 — record penalties (Binance $968M). 2024-2026 — agent focus emerges, comprehensive framework in place.
\ No newline at end of file
diff --git a/learn/how-ofac-sanctions-impact-crypto-development/index.html b/learn/how-ofac-sanctions-impact-crypto-development/index.html
new file mode 100644
index 0000000..b1e0633
--- /dev/null
+++ b/learn/how-ofac-sanctions-impact-crypto-development/index.html
@@ -0,0 +1 @@
+How OFAC sanctions impact crypto development | Learn
How OFAC sanctions impact crypto development
How OFAC sanctions impact crypto development
Sanctions impact development: (1) Protocol design — consider whether your protocol can be used for sanctions evasion. (2) Deployment — where and how you deploy matters. (3) UI choices — front-end wallet screening is a design decision. (4) Open source — publishing sanctions-circumvention tools has drawn enforcement attention.
\ No newline at end of file
diff --git a/learn/how-ofac-sanctions-work-for-crypto-startups/index.html b/learn/how-ofac-sanctions-work-for-crypto-startups/index.html
new file mode 100644
index 0000000..5d357c6
--- /dev/null
+++ b/learn/how-ofac-sanctions-work-for-crypto-startups/index.html
@@ -0,0 +1 @@
+How OFAC sanctions work for crypto startups | Learn
How OFAC sanctions work for crypto startups
How OFAC sanctions work for crypto startups
Crypto startup timeline: (1) Pre-launch — research OFAC obligations for your product type. (2) MVP — integrate free screening API, write one-page policy. (3) First customers — upgrade to paid screening, enable logging. (4) Growth — add monitoring, periodic testing. (5) Scale — dedicated compliance resource, independent audit.
\ No newline at end of file
diff --git a/learn/how-to-add-ofac-screening-to-defi-frontend/index.html b/learn/how-to-add-ofac-screening-to-defi-frontend/index.html
new file mode 100644
index 0000000..c9331d9
--- /dev/null
+++ b/learn/how-to-add-ofac-screening-to-defi-frontend/index.html
@@ -0,0 +1 @@
+How to add OFAC screening to a DeFi frontend | Learn
How to add OFAC screening to a DeFi frontend
How to add OFAC screening to a DeFi frontend
Frontend integration: (1) When a user connects a wallet, screen the address against the SDN list. (2) If clean, allow interaction. (3) If match, display a blocking message and prevent contract interaction. (4) The check runs client-side or through your backend — either way, the wallet never reaches the smart contract.
\ No newline at end of file
diff --git a/learn/how-to-audit-sanctions-screening-code/index.html b/learn/how-to-audit-sanctions-screening-code/index.html
new file mode 100644
index 0000000..a090dac
--- /dev/null
+++ b/learn/how-to-audit-sanctions-screening-code/index.html
@@ -0,0 +1 @@
+How to audit sanctions screening code | Learn
How to audit sanctions screening code
How to audit sanctions screening code
Code audit checklist: (1) Is the screening call before payment authorization in every payment path? (2) Does the code handle screening errors (fail closed)? (3) Are screening results logged with timestamp and inputs? (4) Is there a way to bypass screening in the code (remove it)? (5) Are API keys hardcoded (they shouldn't be)? (6) Is cache TTL appropriately short?
\ No newline at end of file
diff --git a/learn/how-to-build-ofac-compliance-culture/index.html b/learn/how-to-build-ofac-compliance-culture/index.html
new file mode 100644
index 0000000..78eec4c
--- /dev/null
+++ b/learn/how-to-build-ofac-compliance-culture/index.html
@@ -0,0 +1 @@
+How to build an OFAC compliance culture | Learn
How to build an OFAC compliance culture
How to build an OFAC compliance culture
Building compliance culture: (1) Leadership commitment — CEO/CTO must visibly support compliance. (2) Training — every employee touching payments gets annual sanctions training. (3) Communication — regular updates on compliance status and changes. (4) Accountability — compliance metrics in team OKRs. (5) Recognition — celebrate compliance wins, not just revenue wins.
\ No newline at end of file
diff --git a/learn/how-to-build-sanctions-screening-into-agent-framework/index.html b/learn/how-to-build-sanctions-screening-into-agent-framework/index.html
new file mode 100644
index 0000000..e61de5e
--- /dev/null
+++ b/learn/how-to-build-sanctions-screening-into-agent-framework/index.html
@@ -0,0 +1 @@
+How to build sanctions screening into an agent framework | Learn
How to build sanctions screening into an agent framework
How to build sanctions screening into an agent framework
Framework integration: (1) Add a sanctions_check tool to your framework's default toolset. (2) Provide a payment guard — a pre-payment hook that calls screening. (3) Make blocking the default — agents halt on match unless explicitly overridden by a human. (4) Document the compliance expectations for framework users.
\ No newline at end of file
diff --git a/learn/how-to-choose-ofac-screening-solution-for-startup/index.html b/learn/how-to-choose-ofac-screening-solution-for-startup/index.html
new file mode 100644
index 0000000..241ccb1
--- /dev/null
+++ b/learn/how-to-choose-ofac-screening-solution-for-startup/index.html
@@ -0,0 +1 @@
+How to choose an OFAC screening solution for a startup | Learn
How to choose an OFAC screening solution for a startup
How to choose an OFAC screening solution for a startup
Startup selection criteria: (1) Free tier — test before paying. (2) API simplicity — one endpoint, clear documentation, code examples. (3) Integration time — should take hours, not weeks. (4) Pricing — transparent, volume-based, no enterprise sales process. (5) Support — responsive when you need help. SanctionsAI is built for this use case.
\ No newline at end of file
diff --git a/learn/how-to-design-ofac-compliant-payment-system/index.html b/learn/how-to-design-ofac-compliant-payment-system/index.html
new file mode 100644
index 0000000..7a2e9a3
--- /dev/null
+++ b/learn/how-to-design-ofac-compliant-payment-system/index.html
@@ -0,0 +1 @@
+How to design an OFAC-compliant payment system | Learn
How to design an OFAC-compliant payment system
How to design an OFAC-compliant payment system
Payment system design: (1) Screening gate — positioned immediately before payment authorization. (2) Result routing — clean → proceed, match → block, error → fail closed. (3) Logging — timestamped record of every screen with inputs, result, and disposition. (4) Monitoring — real-time alerts on matches, periodic coverage analysis.
\ No newline at end of file
diff --git a/learn/how-to-handle-ofac-compliance-in-ci-cd/index.html b/learn/how-to-handle-ofac-compliance-in-ci-cd/index.html
new file mode 100644
index 0000000..2dd7f8e
--- /dev/null
+++ b/learn/how-to-handle-ofac-compliance-in-ci-cd/index.html
@@ -0,0 +1 @@
+How to handle OFAC compliance in CI/CD pipelines | Learn
How to handle OFAC compliance in CI/CD pipelines
How to handle OFAC compliance in CI/CD pipelines
CI/CD integration: (1) Dependency screening — check third-party dependencies against sanctions lists in CI. (2) Deployment validation — verify screening integration is present and working before promoting to production. (3) Compliance gates — automated checks that prevent deployment if screening coverage drops. (4) Test automation — sanctioned wallet tests run in CI.
\ No newline at end of file
diff --git a/learn/how-to-integrate-ofac-screening-into-payment-api/index.html b/learn/how-to-integrate-ofac-screening-into-payment-api/index.html
new file mode 100644
index 0000000..5bc010b
--- /dev/null
+++ b/learn/how-to-integrate-ofac-screening-into-payment-api/index.html
@@ -0,0 +1 @@
+How to integrate OFAC screening into a payment API | Learn
How to integrate OFAC screening into a payment API
How to integrate OFAC screening into a payment API
Integration pattern: (1) In your payment endpoint, add the screening call before the payment processing call. (2) If screening returns clean, proceed with payment. (3) If match, return an error to the caller and log the event. (4) The screening call adds ~50-90ms to your endpoint's response time.
\ No newline at end of file
diff --git a/learn/how-to-integrate-sanctions-screening-into-ci-cd-pipeline/index.html b/learn/how-to-integrate-sanctions-screening-into-ci-cd-pipeline/index.html
new file mode 100644
index 0000000..c621a8a
--- /dev/null
+++ b/learn/how-to-integrate-sanctions-screening-into-ci-cd-pipeline/index.html
@@ -0,0 +1 @@
+How to integrate sanctions screening into CI/CD pipeline | Learn
How to integrate sanctions screening into CI/CD pipeline
How to integrate sanctions screening into CI/CD pipeline
CI/CD integration: (1) Pre-commit — lint rules that flag payment code without screening calls. (2) CI tests — unit and integration tests with sanctioned wallets. (3) Pre-deploy — verify screening integration is present in the deployment artifact. (4) Post-deploy — smoke test screening on the deployed instance. (5) Monitoring — alert if screening coverage drops post-deployment.
\ No newline at end of file
diff --git a/learn/how-to-monitor-ofac-screening-in-production/index.html b/learn/how-to-monitor-ofac-screening-in-production/index.html
new file mode 100644
index 0000000..c24de7b
--- /dev/null
+++ b/learn/how-to-monitor-ofac-screening-in-production/index.html
@@ -0,0 +1 @@
+How to monitor OFAC screening in production | Learn
How to monitor OFAC screening in production
How to monitor OFAC screening in production
Production monitoring: (1) Coverage — what % of transactions are screened? Target 100%. (2) Match rate — how many screening calls return matches? Spikes may indicate attacks. (3) Response time — is screening staying under 100ms? (4) Error rate — screening failures should be near zero. (5) Alerts — notify on match, on screening failure, on coverage drop.
\ No newline at end of file
diff --git a/learn/how-to-scale-ofac-screening-for-high-volume/index.html b/learn/how-to-scale-ofac-screening-for-high-volume/index.html
new file mode 100644
index 0000000..a9a67af
--- /dev/null
+++ b/learn/how-to-scale-ofac-screening-for-high-volume/index.html
@@ -0,0 +1 @@
+How to scale OFAC screening for high transaction volume | Learn
How to scale OFAC screening for high transaction volume
How to scale OFAC screening for high transaction volume
Scaling strategies: (1) Connection pooling — reuse HTTP connections to the screening API. (2) Async screening — fire-and-forget for non-critical checks. (3) Caching — cache results for repeat counterparties with short TTL. (4) Batching — for periodic reviews, batch check thousands of addresses. (5) Infrastructure — dedicated screening service with high availability.
\ No newline at end of file
diff --git a/learn/how-to-test-ofac-screening-integration/index.html b/learn/how-to-test-ofac-screening-integration/index.html
new file mode 100644
index 0000000..6f2632c
--- /dev/null
+++ b/learn/how-to-test-ofac-screening-integration/index.html
@@ -0,0 +1 @@
+How to test OFAC screening integration | Learn
How to test OFAC screening integration
How to test OFAC screening integration
Testing: (1) Unit test — call screening with a known sanctioned wallet, assert result is not clean. (2) Integration test — attempt payment to sanctioned wallet through the full payment path, assert blocked. (3) Regression test — ensure clean wallets can still transact. (4) Load test — verify screening handles expected transaction volume.
\ No newline at end of file
diff --git a/learn/ofac-compliance-for-defi-protocol-developers/index.html b/learn/ofac-compliance-for-defi-protocol-developers/index.html
new file mode 100644
index 0000000..88bbb93
--- /dev/null
+++ b/learn/ofac-compliance-for-defi-protocol-developers/index.html
@@ -0,0 +1 @@
+OFAC compliance for DeFi protocol developers | Learn
OFAC compliance for DeFi protocol developers
OFAC compliance for DeFi protocol developers
DeFi developer obligations: (1) Front-end screening — check wallets before allowing protocol interaction. (2) Smart contract immutability — if your contracts can't be updated, you can't add screening later. (3) Governance token distribution — screen recipients. (4) Documentation — document your compliance approach for regulators.
\ No newline at end of file
diff --git a/learn/ofac-compliance-for-multisig-wallets/index.html b/learn/ofac-compliance-for-multisig-wallets/index.html
new file mode 100644
index 0000000..40b7ff3
--- /dev/null
+++ b/learn/ofac-compliance-for-multisig-wallets/index.html
@@ -0,0 +1 @@
+OFAC compliance for multisig wallets | Learn
OFAC compliance for multisig wallets
OFAC compliance for multisig wallets
Multisig compliance: (1) Signer screening — every signer on a multisig should be screened for sanctions. (2) Transaction screening — proposed transactions should be screened before signing. (3) DAO treasuries — treasury multisigs have the same compliance obligations as any entity. (4) Signer rotation — when signers change, re-screen all signers.
\ No newline at end of file
diff --git a/learn/ofac-compliance-for-open-source-projects/index.html b/learn/ofac-compliance-for-open-source-projects/index.html
new file mode 100644
index 0000000..fa3e6d1
--- /dev/null
+++ b/learn/ofac-compliance-for-open-source-projects/index.html
@@ -0,0 +1 @@
+OFAC compliance for open source projects | Learn
OFAC compliance for open source projects
OFAC compliance for open source projects
Open source and sanctions: (1) Contributions — are contributors from sanctioned jurisdictions? OFAC has general licenses for open source contributions in some cases. (2) Dependencies — are any dependencies from sanctioned entities? (3) Hosting — where is your code hosted and who can access it? (4) Documentation — include a sanctions compliance notice if applicable.
\ No newline at end of file
diff --git a/learn/ofac-compliance-for-payment-engineering/index.html b/learn/ofac-compliance-for-payment-engineering/index.html
new file mode 100644
index 0000000..29cc256
--- /dev/null
+++ b/learn/ofac-compliance-for-payment-engineering/index.html
@@ -0,0 +1 @@
+OFAC compliance for payment engineering | Learn
OFAC compliance for payment engineering
OFAC compliance for payment engineering
Payment engineering and compliance: (1) API design — the screening call must be in the critical path, not an afterthought. (2) Failure modes — fail closed (block on screening failure). (3) Testing — unit tests with known sanctioned wallets. (4) Deployment — screening must work in all environments (dev, staging, prod).
\ No newline at end of file
diff --git a/learn/ofac-compliance-for-payment-orchestration-platforms/index.html b/learn/ofac-compliance-for-payment-orchestration-platforms/index.html
new file mode 100644
index 0000000..97f3e1b
--- /dev/null
+++ b/learn/ofac-compliance-for-payment-orchestration-platforms/index.html
@@ -0,0 +1 @@
+OFAC compliance for payment orchestration platforms | Learn
OFAC compliance for payment orchestration platforms
OFAC compliance for payment orchestration platforms
Orchestration platforms make routing decisions — and each decision must consider sanctions. Before routing a transaction to Provider A vs Provider B, screen both the provider and the counterparty. The orchestration layer is the compliance decision point.
\ No newline at end of file
diff --git a/learn/ofac-compliance-for-stablecoin-projects/index.html b/learn/ofac-compliance-for-stablecoin-projects/index.html
new file mode 100644
index 0000000..43ad745
--- /dev/null
+++ b/learn/ofac-compliance-for-stablecoin-projects/index.html
@@ -0,0 +1 @@
+OFAC compliance for stablecoin projects | Learn
OFAC compliance for stablecoin projects
OFAC compliance for stablecoin projects
Stablecoin compliance: (1) Issuance — screen minting addresses. (2) Reserve management — screen banks and counterparties holding reserves. (3) Redemption — screen burn addresses. (4) Freezing — implement address-freezing capability for OFAC compliance. (5) Monitoring — screen all transfers to the extent technically feasible.
\ No newline at end of file
diff --git a/learn/ofac-compliance-for-token-projects/index.html b/learn/ofac-compliance-for-token-projects/index.html
new file mode 100644
index 0000000..e0c0876
--- /dev/null
+++ b/learn/ofac-compliance-for-token-projects/index.html
@@ -0,0 +1 @@
+OFAC compliance for token projects | Learn
OFAC compliance for token projects
OFAC compliance for token projects
Token project lifecycle: (1) Pre-launch — design tokenomics with sanctions compliance in mind. (2) Launch — screen initial distribution recipients. (3) Exchange listing — exchanges will screen; ensure your token complies. (4) Ongoing distributions — airdrops, staking rewards, governance — screen all recipients. (5) Community — establish compliance expectations for token holders.
\ No newline at end of file
diff --git a/learn/ofac-compliance-for-web3-developers-guide/index.html b/learn/ofac-compliance-for-web3-developers-guide/index.html
new file mode 100644
index 0000000..858bce5
--- /dev/null
+++ b/learn/ofac-compliance-for-web3-developers-guide/index.html
@@ -0,0 +1 @@
+OFAC compliance for Web3 developers: Complete guide | Learn
OFAC compliance for Web3 developers: Complete guide
OFAC compliance for Web3 developers: Complete guide
\ No newline at end of file
diff --git a/learn/ofac-compliance-maturity-model/index.html b/learn/ofac-compliance-maturity-model/index.html
new file mode 100644
index 0000000..9a505e8
--- /dev/null
+++ b/learn/ofac-compliance-maturity-model/index.html
@@ -0,0 +1 @@
+OFAC compliance maturity model | Learn
OFAC compliance maturity model
OFAC compliance maturity model
Maturity model: Level 1 — Ad-hoc (manual checks, no policy). Level 2 — Basic (API integrated into main payment path, basic policy). Level 3 — Managed (all payment paths covered, monitoring, logs). Level 4 — Optimized (continuous testing, independent audits, dedicated resource). Level 5 — Leading (real-time monitoring, AI-driven alert handling, industry benchmark). Most startups start at Level 2 and reach Level 3 within 3 months.
\ No newline at end of file
diff --git a/learn/ofac-sanctions-compliance-for-validators/index.html b/learn/ofac-sanctions-compliance-for-validators/index.html
new file mode 100644
index 0000000..4466002
--- /dev/null
+++ b/learn/ofac-sanctions-compliance-for-validators/index.html
@@ -0,0 +1 @@
+OFAC sanctions compliance for validators | Learn
OFAC sanctions compliance for validators
OFAC sanctions compliance for validators
Validator compliance: (1) Transaction inclusion — validators that include sanctioned transactions may have facilitation exposure. (2) OFAC-compliant validators — some validators use OFAC-compliant relays that filter sanctioned transactions. (3) MEV — extracting MEV from sanctioned transactions compounds the exposure. (4) Jurisdiction — validators operating in the US have clear OFAC obligations.
\ No newline at end of file
diff --git a/learn/ofac-sanctions-screening-for-developers-guide/index.html b/learn/ofac-sanctions-screening-for-developers-guide/index.html
new file mode 100644
index 0000000..b5832ac
--- /dev/null
+++ b/learn/ofac-sanctions-screening-for-developers-guide/index.html
@@ -0,0 +1 @@
+OFAC sanctions screening for developers: Complete guide | Learn
OFAC sanctions screening for developers: Complete guide
OFAC sanctions screening for developers: Complete guide
Developer's guide: (1) Understand the requirement — strict liability, screen every payment. (2) Choose an API — free tier for testing, paid for production. (3) Integrate — one API call before payment. (4) Test — known sanctioned wallets. (5) Deploy — with monitoring and alerting. (6) Maintain — review logs, update integration as needed.
\ No newline at end of file
diff --git a/learn/ofac-sanctions-screening-for-devops/index.html b/learn/ofac-sanctions-screening-for-devops/index.html
new file mode 100644
index 0000000..33aa419
--- /dev/null
+++ b/learn/ofac-sanctions-screening-for-devops/index.html
@@ -0,0 +1 @@
+OFAC sanctions screening for DevOps | Learn
OFAC sanctions screening for DevOps
OFAC sanctions screening for DevOps
DevOps for screening: (1) Deployment — screening must be in every environment (dev, staging, prod). (2) Monitoring — screening coverage, response time, error rate, match rate. (3) Alerting — matches, failures, coverage drops. (4) Incident response — documented runbook for screening outages. (5) Disaster recovery — failover strategy when screening API is unavailable.
\ No newline at end of file
diff --git a/learn/ofac-sanctions-screening-for-engineering-managers/index.html b/learn/ofac-sanctions-screening-for-engineering-managers/index.html
new file mode 100644
index 0000000..2fb4855
--- /dev/null
+++ b/learn/ofac-sanctions-screening-for-engineering-managers/index.html
@@ -0,0 +1 @@
+OFAC sanctions screening for engineering managers | Learn
OFAC sanctions screening for engineering managers
OFAC sanctions screening for engineering managers
Engineering manager checklist: (1) Integration effort — typically 1-3 days for a single payment path, 1-2 weeks for comprehensive coverage. (2) Team readiness — developers need basic sanctions awareness training. (3) Testing investment — build a test suite with sanctioned wallets. (4) Ongoing cost — API pricing scales with volume.
\ No newline at end of file
diff --git a/learn/ofac-screening-best-practices-for-developers/index.html b/learn/ofac-screening-best-practices-for-developers/index.html
new file mode 100644
index 0000000..da25b8c
--- /dev/null
+++ b/learn/ofac-screening-best-practices-for-developers/index.html
@@ -0,0 +1 @@
+OFAC screening best practices for developers | Learn
OFAC screening best practices for developers
OFAC screening best practices for developers
Developer best practices: (1) Screen early — before payment, not after. (2) Fail closed — block on screening failure. (3) Log everything — inputs, result, timestamp, agent identity. (4) Test thoroughly — sanctioned wallets in test suite. (5) Cache carefully — short TTL, invalidate on list updates. (6) Monitor continuously — coverage, match rate, response time.
\ No newline at end of file
diff --git a/learn/ofac-screening-cost-benefit-analysis/index.html b/learn/ofac-screening-cost-benefit-analysis/index.html
new file mode 100644
index 0000000..63e5a5b
--- /dev/null
+++ b/learn/ofac-screening-cost-benefit-analysis/index.html
@@ -0,0 +1 @@
+OFAC screening cost-benefit analysis | Learn
OFAC screening cost-benefit analysis
OFAC screening cost-benefit analysis
Cost-benefit: Screening cost — $0-$99/month (SanctionsAI free to Pro). Cost of one violation — $330,944 minimum. Even at the Pro tier, one year of screening ($1,188) is 0.36% of the minimum penalty. For AI agents that can accumulate violations at machine speed, the math is even more stark. Screening is the cheapest insurance you can buy.
\ No newline at end of file
diff --git a/learn/ofac-screening-for-blockchain-infrastructure/index.html b/learn/ofac-screening-for-blockchain-infrastructure/index.html
new file mode 100644
index 0000000..d26557a
--- /dev/null
+++ b/learn/ofac-screening-for-blockchain-infrastructure/index.html
@@ -0,0 +1 @@
+OFAC screening for blockchain infrastructure | Learn
OFAC screening for blockchain infrastructure
OFAC screening for blockchain infrastructure
Blockchain infrastructure providers: (1) Node operators — processing blocks that include sanctioned transactions may have exposure. (2) RPC providers — relaying transactions to sanctioned addresses is facilitation. (3) Indexers — querying data about sanctioned entities is generally not restricted (information, not value transfer).
\ No newline at end of file
diff --git a/learn/ofac-screening-for-cross-chain-developers/index.html b/learn/ofac-screening-for-cross-chain-developers/index.html
new file mode 100644
index 0000000..3ea0e50
--- /dev/null
+++ b/learn/ofac-screening-for-cross-chain-developers/index.html
@@ -0,0 +1 @@
+OFAC screening for cross-chain developers | Learn
OFAC screening for cross-chain developers
OFAC screening for cross-chain developers
Cross-chain compliance: (1) Every bridge is a screening point — source chain, destination chain, and the bridge itself. (2) Multi-chain tokens — a token on 5 chains has 5x the screening surface area. (3) Cross-chain messages — if a message triggers a value transfer, screen it. (4) Unified monitoring — cross-chain screening logs should be centralized.
\ No newline at end of file
diff --git a/learn/ofac-screening-for-crypto-compliance-teams/index.html b/learn/ofac-screening-for-crypto-compliance-teams/index.html
new file mode 100644
index 0000000..fbae606
--- /dev/null
+++ b/learn/ofac-screening-for-crypto-compliance-teams/index.html
@@ -0,0 +1 @@
+OFAC screening for crypto compliance teams | Learn
OFAC screening for crypto compliance teams
OFAC screening for crypto compliance teams
Compliance team operations: (1) Daily — review screening logs for matches and anomalies. (2) Weekly — check screening coverage across all payment channels. (3) Monthly — review SDN list updates and their impact on screened entities. (4) Quarterly — test screening effectiveness with sanctioned wallets. (5) Annually — independent audit and program review.
\ No newline at end of file
diff --git a/learn/ofac-screening-for-layer-2-projects/index.html b/learn/ofac-screening-for-layer-2-projects/index.html
new file mode 100644
index 0000000..4a04e78
--- /dev/null
+++ b/learn/ofac-screening-for-layer-2-projects/index.html
@@ -0,0 +1 @@
+OFAC screening for Layer 2 projects | Learn
OFAC screening for Layer 2 projects
OFAC screening for Layer 2 projects
L2 compliance layers: (1) Sequencer — the entity ordering transactions may face OFAC obligations for including sanctioned transactions. (2) Bridge — the L1↔L2 bridge must screen cross-chain transfers. (3) Applications — dApps on L2s must screen wallets at the front-end. (4) Token — L2 native tokens distributed to sanctioned wallets create exposure.
\ No newline at end of file
diff --git a/learn/ofac-screening-for-nft-projects/index.html b/learn/ofac-screening-for-nft-projects/index.html
new file mode 100644
index 0000000..74548b9
--- /dev/null
+++ b/learn/ofac-screening-for-nft-projects/index.html
@@ -0,0 +1 @@
+OFAC screening for NFT projects | Learn
OFAC screening for NFT projects
OFAC screening for NFT projects
NFT project compliance: (1) Mint — screen minting wallets. (2) Marketplace — screen buyers and sellers. (3) Royalties — screen royalty distribution addresses. (4) Airdrops — screen recipient lists. (5) Community — educate community about sanctions risks. The screening pattern is the same as any token project — every value transfer point needs a check.
\ No newline at end of file
diff --git a/learn/ofac-screening-for-payment-engineering-teams/index.html b/learn/ofac-screening-for-payment-engineering-teams/index.html
new file mode 100644
index 0000000..52cbc3e
--- /dev/null
+++ b/learn/ofac-screening-for-payment-engineering-teams/index.html
@@ -0,0 +1 @@
+OFAC screening for payment engineering teams | Learn
OFAC screening for payment engineering teams
OFAC screening for payment engineering teams
Engineering team checklist: (1) Screening integration in all payment paths — done. (2) Testing suite with sanctioned wallets — written and passing. (3) Monitoring and alerting — configured. (4) Documentation — integration docs and runbooks written. (5) Disaster recovery — what happens when screening API is down documented.
\ No newline at end of file
diff --git a/learn/ofac-screening-for-smart-contract-developers/index.html b/learn/ofac-screening-for-smart-contract-developers/index.html
new file mode 100644
index 0000000..99a9b09
--- /dev/null
+++ b/learn/ofac-screening-for-smart-contract-developers/index.html
@@ -0,0 +1 @@
+OFAC screening for smart contract developers | Learn
OFAC screening for smart contract developers
OFAC screening for smart contract developers
Smart contract considerations: (1) Immutability — if your contract can't be upgraded, you can't add screening later. (2) Upgradeability — consider proxy patterns that allow adding screening. (3) Access control — consider whether sanctioned addresses should be blocked at the contract level. (4) Events — emit events for compliance-relevant transactions to enable off-chain monitoring.
\ No newline at end of file
diff --git a/learn/ofac-screening-implementation-patterns/index.html b/learn/ofac-screening-implementation-patterns/index.html
new file mode 100644
index 0000000..ccabf22
--- /dev/null
+++ b/learn/ofac-screening-implementation-patterns/index.html
@@ -0,0 +1 @@
+OFAC screening implementation patterns | Learn
OFAC screening implementation patterns
OFAC screening implementation patterns
Implementation patterns: (1) Pre-payment gate — screening call immediately before payment. (2) Middleware — screening as HTTP middleware intercepting all payment requests. (3) Event-driven — payment events trigger asynchronous screening. (4) Sidecar — screening as a separate service queried by the payment service.
\ No newline at end of file
diff --git a/learn/ofac-screening-implementation-timeline/index.html b/learn/ofac-screening-implementation-timeline/index.html
new file mode 100644
index 0000000..b7126fd
--- /dev/null
+++ b/learn/ofac-screening-implementation-timeline/index.html
@@ -0,0 +1 @@
+OFAC screening implementation timeline | Learn
OFAC screening implementation timeline
OFAC screening implementation timeline
Implementation timeline: Day 1 — basic API integration, test with sanctioned wallet. Day 2-3 — integrate into all payment paths. Week 2 — add monitoring, logging, alerting. Week 3 — compliance documentation, training. Week 4 — independent review, production hardening. Most startups can reach basic coverage in under a week.
\ No newline at end of file
diff --git a/learn/ofac-screening-security-considerations/index.html b/learn/ofac-screening-security-considerations/index.html
new file mode 100644
index 0000000..f39882e
--- /dev/null
+++ b/learn/ofac-screening-security-considerations/index.html
@@ -0,0 +1 @@
+OFAC screening security considerations | Learn
OFAC screening security considerations
OFAC screening security considerations
Security considerations: (1) API key protection — store in secrets manager, rotate regularly. (2) Data privacy — screening inputs (names, wallets) may be sensitive; ensure your screening provider has appropriate data handling. (3) Bypass prevention — ensure screening cannot be disabled or skipped through configuration or error handling. (4) Audit — log all screening configuration changes.
\ No newline at end of file
diff --git a/learn/what-happens-when-ofac-screening-fails/index.html b/learn/what-happens-when-ofac-screening-fails/index.html
new file mode 100644
index 0000000..cad132f
--- /dev/null
+++ b/learn/what-happens-when-ofac-screening-fails/index.html
@@ -0,0 +1 @@
+What happens when OFAC screening fails | Learn
What happens when OFAC screening fails
What happens when OFAC screening fails
Screening failure consequences: (1) Undetected violations — transactions to SDNs proceed without your knowledge. (2) Discovery — OFAC, blockchain analytics, or counterparty reporting reveals the violation. (3) Investigation — OFAC investigates, potentially going back years. (4) Enforcement — penalties, settlements, or criminal referral. (5) Remediation — fix the screening gap, implement controls, consider voluntary disclosure.
\ No newline at end of file
diff --git a/learn/what-is-ofac-compliance-for-blockchain-developers/index.html b/learn/what-is-ofac-compliance-for-blockchain-developers/index.html
new file mode 100644
index 0000000..91d55a1
--- /dev/null
+++ b/learn/what-is-ofac-compliance-for-blockchain-developers/index.html
@@ -0,0 +1 @@
+OFAC compliance for blockchain developers | Learn
OFAC compliance for blockchain developers
OFAC compliance for blockchain developers
Blockchain developers face OFAC at the application layer: (1) Front-end screening — check wallet addresses before allowing user interaction. (2) Smart contract design — consider whether your contracts could be used by sanctioned parties. (3) Deployment responsibility — where you deploy and who can access it matters.
\ No newline at end of file
diff --git a/learn/what-is-ofac-compliance-for-crypto-wallet-developers/index.html b/learn/what-is-ofac-compliance-for-crypto-wallet-developers/index.html
new file mode 100644
index 0000000..8a93a54
--- /dev/null
+++ b/learn/what-is-ofac-compliance-for-crypto-wallet-developers/index.html
@@ -0,0 +1 @@
+OFAC compliance for crypto wallet developers | Learn
OFAC compliance for crypto wallet developers
OFAC compliance for crypto wallet developers
Wallet developer obligations: (1) Self-custody wallets — provide screening as a feature (users need to check before sending). (2) Custodial wallets — screen every transaction (you process them). (3) Smart contract wallets — screen in the transaction-building logic. SanctionsAI's API integrates into all three.
\ No newline at end of file
diff --git a/learn/what-is-ofac-compliance-for-fintech-infrastructure/index.html b/learn/what-is-ofac-compliance-for-fintech-infrastructure/index.html
new file mode 100644
index 0000000..2f20136
--- /dev/null
+++ b/learn/what-is-ofac-compliance-for-fintech-infrastructure/index.html
@@ -0,0 +1 @@
+OFAC compliance for fintech infrastructure | Learn
OFAC compliance for fintech infrastructure
OFAC compliance for fintech infrastructure
Fintech infrastructure providers are the foundation other fintechs build on — and they bear the compliance responsibility for the transactions flowing through their rails. Screening must be embedded in every service: account opening, card issuing, ACH transfers, wire transfers, and crypto transactions.
\ No newline at end of file
diff --git a/learn/what-is-ofac-compliance-for-payment-product-managers/index.html b/learn/what-is-ofac-compliance-for-payment-product-managers/index.html
new file mode 100644
index 0000000..1a86415
--- /dev/null
+++ b/learn/what-is-ofac-compliance-for-payment-product-managers/index.html
@@ -0,0 +1 @@
+OFAC compliance for payment product managers | Learn
OFAC compliance for payment product managers
OFAC compliance for payment product managers
Product manager considerations: (1) User experience — screening adds <100ms, imperceptible to users. (2) False positives — a small % of legitimate users may be flagged, need a resolution flow. (3) International users — different jurisdictions have different sanctions lists. (4) Onboarding — screening should be part of signup flow, not an afterthought.
\ No newline at end of file
diff --git a/learn/what-is-ofac-compliance-for-platform-engineering/index.html b/learn/what-is-ofac-compliance-for-platform-engineering/index.html
new file mode 100644
index 0000000..e332274
--- /dev/null
+++ b/learn/what-is-ofac-compliance-for-platform-engineering/index.html
@@ -0,0 +1 @@
+OFAC compliance for platform engineering | Learn
OFAC compliance for platform engineering
OFAC compliance for platform engineering
Platform engineering: build screening as a platform service — a shared API, a library, or a middleware that product teams consume. This ensures consistent screening across all products, centralized monitoring, and a single integration point for list updates and configuration changes.
\ No newline at end of file
diff --git a/learn/what-is-ofac-compliance-testing-methodology/index.html b/learn/what-is-ofac-compliance-testing-methodology/index.html
new file mode 100644
index 0000000..bc59d3e
--- /dev/null
+++ b/learn/what-is-ofac-compliance-testing-methodology/index.html
@@ -0,0 +1 @@
+OFAC compliance testing methodology | Learn
OFAC compliance testing methodology
OFAC compliance testing methodology
Testing methodology: (1) Positive tests — known SDN wallets should return match. (2) Negative tests — clean wallets should return clean. (3) Edge cases — malformed addresses, empty inputs, special characters. (4) Failure tests — what happens when the screening API is down? (5) Regression tests — new deployments don't break screening.
\ No newline at end of file
diff --git a/learn/what-is-ofac-screening-for-payment-security/index.html b/learn/what-is-ofac-screening-for-payment-security/index.html
new file mode 100644
index 0000000..c3ab5f5
--- /dev/null
+++ b/learn/what-is-ofac-screening-for-payment-security/index.html
@@ -0,0 +1 @@
+OFAC screening for payment security | Learn
OFAC screening for payment security
OFAC screening for payment security
Screening as security: (1) Prevention — screening prevents prohibited transactions just as authentication prevents unauthorized access. (2) Detection — match alerts detect potential violations. (3) Response — blocking and reporting respond to detected violations. (4) Recovery — voluntary disclosure and remediation mitigate damage. Security teams should own screening alongside other security controls.