diff --git a/api.py b/api.py
index ff741e1..33b58af 100644
--- a/api.py
+++ b/api.py
@@ -5135,6 +5135,107 @@ def _sitemap_xml(self):
("/scenarios/agent-retries-blocked-payment-autonomously", "monthly", "0.7", "Agent retries blocked payment"),
("/scenarios/cross-border-agent-payment-to-russia", "monthly", "0.7", "Cross-border payment to Russia"),
("/scenarios/agent-screens-but-ignores-match", "monthly", "0.7", "Agent ignores sanctions match"),
+ ("/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-crypto-wallets", "monthly", "0.7", "What Is Ofac Screening For Crypto Wallets"),
+ ("/faq/what-is-ofac-screening-for-stablecoin-transfers", "monthly", "0.7", "What Is Ofac Screening For Stablecoin Transfers"),
+ ("/faq/what-is-ofac-screening-for-defi-protocols", "monthly", "0.7", "What Is Ofac Screening For Defi Protocols"),
+ ("/faq/how-to-integrate-ofac-screening-into-agent", "monthly", "0.7", "How To Integrate Ofac Screening Into Agent"),
+ ("/faq/can-ofac-track-crypto-transactions", "monthly", "0.7", "Can Ofac Track Crypto Transactions"),
+ ("/faq/what-is-ofac-screening-for-nft-marketplaces", "monthly", "0.7", "What Is Ofac Screening For Nft Marketplaces"),
+ ("/faq/can-ofac-sanction-defi-frontends", "monthly", "0.7", "Can Ofac Sanction Defi Frontends"),
+ ("/faq/what-is-ofac-screening-for-dao-treasuries", "monthly", "0.7", "What Is Ofac Screening For Dao Treasuries"),
+ ("/faq/does-ofac-apply-to-layer-2-networks", "monthly", "0.7", "Does Ofac Apply To Layer 2 Networks"),
+ ("/faq/what-is-ofac-compliance-for-web3", "monthly", "0.7", "What Is Ofac Compliance For Web3"),
+ ("/faq/how-to-screen-stablecoin-payments", "monthly", "0.7", "How To Screen Stablecoin Payments"),
+ ("/faq/what-is-a-sanctions-screening-tool", "monthly", "0.7", "What Is A Sanctions Screening Tool"),
+ ("/faq/how-does-sanctionsai-compare-to-chainalysis", "monthly", "0.7", "How Does Sanctionsai Compare To Chainalysis"),
+ ("/faq/what-is-ofac-screening-for-payment-apis", "monthly", "0.7", "What Is Ofac Screening For Payment Apis"),
+ ("/faq/does-ofac-require-screening-for-stablecoin-issuance", "monthly", "0.7", "Does Ofac Require Screening For Stablecoin Issuanc"),
+ ("/faq/what-is-ofac-compliance-for-crypto-payments", "monthly", "0.7", "What Is Ofac Compliance For Crypto Payments"),
+ ("/faq/can-ofac-sanction-a-crypto-exchange", "monthly", "0.7", "Can Ofac Sanction A Crypto Exchange"),
+ ("/faq/what-is-ofac-screening-for-custodial-wallets", "monthly", "0.7", "What Is Ofac Screening For Custodial Wallets"),
+ ("/faq/does-ofac-apply-to-stablecoin-yield", "monthly", "0.7", "Does Ofac Apply To Stablecoin Yield"),
+ ("/faq/what-is-an-ofac-risk-score", "monthly", "0.7", "What Is An Ofac Risk Score"),
+ ("/faq/how-to-monitor-sanctions-compliance", "monthly", "0.7", "How To Monitor Sanctions Compliance"),
+ ("/faq/what-is-ofac-compliance-for-bridges", "monthly", "0.7", "What Is Ofac Compliance For Bridges"),
+ ("/faq/can-ofac-sanction-a-stablecoin", "monthly", "0.7", "Can Ofac Sanction A Stablecoin"),
+ ("/faq/what-is-ofac-screening-for-agent-payments", "monthly", "0.7", "What Is Ofac Screening For Agent Payments"),
+ ("/faq/what-is-a-sanctions-match", "monthly", "0.7", "What Is A Sanctions Match"),
+ ("/faq/how-to-handle-sanctions-false-positive", "monthly", "0.7", "How To Handle Sanctions False Positive"),
+ ("/faq/what-is-ofac-screening-for-kyc-providers", "monthly", "0.7", "What Is Ofac Screening For Kyc Providers"),
+ ("/faq/what-are-ofac-sanctions-programs-explained", "monthly", "0.7", "What Are Ofac Sanctions Programs Explained"),
+ ("/faq/how-to-screen-crypto-exchanges-for-ofac", "monthly", "0.7", "How To Screen Crypto Exchanges For Ofac"),
+ ("/faq/what-is-ofac-screening-for-aml-programs", "monthly", "0.7", "What Is Ofac Screening For Aml Programs"),
+ ("/faq/does-ofac-screening-replace-aml", "monthly", "0.7", "Does Ofac Screening Replace Aml"),
+ ("/faq/what-is-ofac-screening-for-remittance", "monthly", "0.7", "What Is Ofac Screening For Remittance"),
+ ("/faq/what-is-ofac-screening-for-charities", "monthly", "0.7", "What Is Ofac Screening For Charities"),
+ ("/faq/how-to-build-ofac-compliance-program", "monthly", "0.7", "How To Build Ofac Compliance Program"),
+ ("/faq/what-is-ofac-screening-for-defi-yield", "monthly", "0.7", "What Is Ofac Screening For Defi Yield"),
+ ("/faq/can-ofac-enforcement-apply-retroactively", "monthly", "0.7", "Can Ofac Enforcement Apply Retroactively"),
+ ("/faq/what-is-ofac-screening-for-token-launches", "monthly", "0.7", "What Is Ofac Screening For Token Launches"),
+ ("/faq/how-to-verify-ofac-compliance", "monthly", "0.7", "How To Verify Ofac Compliance"),
+ ("/faq/what-is-ofac-screening-for-payment-gateways", "monthly", "0.7", "What Is Ofac Screening For Payment Gateways"),
+ ("/faq/does-ofac-apply-to-non-us-companies", "monthly", "0.7", "Does Ofac Apply To Non Us Companies"),
+ ("/glossary/ofac-strict-liability", "monthly", "0.7", "Ofac Strict Liability"),
+ ("/glossary/ofac-secondary-sanctions", "monthly", "0.7", "Ofac Secondary Sanctions"),
+ ("/glossary/ofac-enforcement-action", "monthly", "0.7", "Ofac Enforcement Action"),
+ ("/glossary/ofac-compliance-audit", "monthly", "0.7", "Ofac Compliance Audit"),
+ ("/glossary/ofac-wallet-clustering", "monthly", "0.7", "Ofac Wallet Clustering"),
+ ("/glossary/ofac-risk-indicator", "monthly", "0.7", "Ofac Risk Indicator"),
+ ("/glossary/ofac-name-screening", "monthly", "0.7", "Ofac Name Screening"),
+ ("/glossary/ofac-kyc-integration", "monthly", "0.7", "Ofac Kyc Integration"),
+ ("/glossary/ofac-screening-coverage", "monthly", "0.7", "Ofac Screening Coverage"),
+ ("/glossary/ofac-payment-screening", "monthly", "0.7", "Ofac Payment Screening"),
+ ("/glossary/ofac-compliance-technology", "monthly", "0.7", "Ofac Compliance Technology"),
+ ("/glossary/ofac-screening-sdk", "monthly", "0.7", "Ofac Screening Sdk"),
+ ("/glossary/ofac-compliance-reporting", "monthly", "0.7", "Ofac Compliance Reporting"),
+ ("/glossary/ofac-designation-authority", "monthly", "0.7", "Ofac Designation Authority"),
+ ("/glossary/ofac-delisting", "monthly", "0.7", "Ofac Delisting"),
+ ("/glossary/ofac-enforcement-priority", "monthly", "0.7", "Ofac Enforcement Priority"),
+ ("/glossary/ofac-compliance-training", "monthly", "0.7", "Ofac Compliance Training"),
+ ("/glossary/sanctions-screening-engine", "monthly", "0.7", "Sanctions Screening Engine"),
+ ("/glossary/ofac-risk-based-approach", "monthly", "0.7", "Ofac Risk Based Approach"),
+ ("/glossary/ofac-compliance-gap", "monthly", "0.7", "Ofac Compliance Gap"),
+ ("/glossary/ofac-screening-api-endpoint", "monthly", "0.7", "Ofac Screening Api Endpoint"),
+ ("/glossary/ofac-screening-for-ai", "monthly", "0.7", "Ofac Screening For Ai"),
+ ("/glossary/ofac-screening-log", "monthly", "0.7", "Ofac Screening Log"),
+ ("/glossary/ofac-screening-policy", "monthly", "0.7", "Ofac Screening Policy"),
+ ("/glossary/ofac-compliance-testing", "monthly", "0.7", "Ofac Compliance Testing"),
+ ("/glossary/ofac-screening-methodology", "monthly", "0.7", "Ofac Screening Methodology"),
+ ("/glossary/ofac-list-synchronization", "monthly", "0.7", "Ofac List Synchronization"),
+ ("/glossary/ofac-screening-benchmark", "monthly", "0.7", "Ofac Screening Benchmark"),
+ ("/glossary/ofac-enforcement-precedent", "monthly", "0.7", "Ofac Enforcement Precedent"),
+ ("/glossary/ofac-screening-integration-pattern", "monthly", "0.7", "Ofac Screening Integration Pattern"),
+ ("/learn/how-ofac-penalties-are-calculated", "monthly", "0.7", "How Ofac Penalties Are Calculated"),
+ ("/learn/what-is-ofac-compliance-for-developers", "monthly", "0.7", "What Is Ofac Compliance For Developers"),
+ ("/learn/ofac-screeening-for-agent-developers", "monthly", "0.7", "Ofac Screeening For Agent Developers"),
+ ("/learn/what-is-ofac-compliance-for-defi-developers", "monthly", "0.7", "What Is Ofac Compliance For Defi Developers"),
+ ("/learn/what-is-ofac-sanctions-screening-explained", "monthly", "0.7", "What Is Ofac Sanctions Screening Explained"),
+ ("/learn/ofac-sanctions-compliance-for-crypto-startups", "monthly", "0.7", "Ofac Sanctions Compliance For Crypto Startups"),
+ ("/learn/what-are-ofac-sanctions-for-crypto", "monthly", "0.7", "What Are Ofac Sanctions For Crypto"),
+ ("/learn/what-is-ofac-sanctions-compliance-training", "monthly", "0.7", "What Is Ofac Sanctions Compliance Training"),
+ ("/learn/ofac-screening-for-payment-startups", "monthly", "0.7", "Ofac Screening For Payment Startups"),
+ ("/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/how-to-choose-ofac-sanctions-screening-tool", "monthly", "0.7", "How To Choose Ofac Sanctions Screening Tool"),
+ ("/learn/ofac-screening-for-blockchain-companies", "monthly", "0.7", "Ofac Screening For Blockchain Companies"),
+ ("/learn/ofac-sanctions-compliance-for-exchanges", "monthly", "0.7", "Ofac Sanctions Compliance For Exchanges"),
+ ("/learn/what-are-ofac-sanctions-penalties-for-crypto", "monthly", "0.7", "What Are Ofac Sanctions Penalties For Crypto"),
+ ("/learn/ofac-screening-for-agent-frameworks", "monthly", "0.7", "Ofac Screening For Agent Frameworks"),
+ ("/learn/what-is-ofac-compliance-for-web3-startups", "monthly", "0.7", "What Is Ofac Compliance For Web3 Startups"),
+ ("/learn/ofac-sanctions-screening-for-enterprise", "monthly", "0.7", "Ofac Sanctions Screening For Enterprise"),
+ ("/learn/ofac-sanctions-compliance-for-fintech", "monthly", "0.7", "Ofac Sanctions Compliance For Fintech"),
+ ("/learn/ofac-screeening-for-payment-infrastructure", "monthly", "0.7", "Ofac Screeening For Payment Infrastructure"),
+ ("/penalties/crypto-com", "monthly", "0.7", "Crypto Com"),
+ ("/penalties/okx", "monthly", "0.7", "Okx"),
+ ("/penalties/bybit", "monthly", "0.7", "Bybit"),
+ ("/penalties/kucoin", "monthly", "0.7", "Kucoin"),
+ ("/penalties/garantex-sanctions", "monthly", "0.7", "Garantex Sanctions"),
+ ("/penalties/hydra-market", "monthly", "0.7", "Hydra Market"),
+ ("/penalties/blender-io", "monthly", "0.7", "Blender Io"),
+ ("/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"),
]
import datetime
today = datetime.date.today().isoformat()
diff --git a/faq/can-ofac-enforcement-apply-retroactively/index.html b/faq/can-ofac-enforcement-apply-retroactively/index.html
new file mode 100644
index 0000000..d49bb93
--- /dev/null
+++ b/faq/can-ofac-enforcement-apply-retroactively/index.html
@@ -0,0 +1 @@
+Can OFAC enforcement apply retroactively? | FAQ
Can OFAC enforcement apply retroactively?
Can OFAC enforcement apply retroactively?
Yes, within limits. The statute of limitations for OFAC civil penalties is 5 years from the date of the violation. However, OFAC can investigate older conduct and consider it as part of a pattern. Criminal violations under IEEPA also have their own statutes of limitations.
\ No newline at end of file
diff --git a/faq/can-ofac-sanction-a-crypto-exchange/index.html b/faq/can-ofac-sanction-a-crypto-exchange/index.html
new file mode 100644
index 0000000..b4b6b70
--- /dev/null
+++ b/faq/can-ofac-sanction-a-crypto-exchange/index.html
@@ -0,0 +1 @@
+Can OFAC sanction a crypto exchange? | FAQ
Can OFAC sanction a crypto exchange?
Can OFAC sanction a crypto exchange?
Yes — and exchanges have faced the most significant enforcement. OFAC has designated entire exchanges (SUEX, Chatex, Garantex) and imposed record penalties on others (Binance $968M, Bittrex $29M). The lesson: exchanges must screen every transaction or face liability.
\ No newline at end of file
diff --git a/faq/can-ofac-sanction-a-stablecoin/index.html b/faq/can-ofac-sanction-a-stablecoin/index.html
new file mode 100644
index 0000000..7d66ac2
--- /dev/null
+++ b/faq/can-ofac-sanction-a-stablecoin/index.html
@@ -0,0 +1 @@
+Can OFAC sanction a stablecoin? | FAQ
Can OFAC sanction a stablecoin?
Can OFAC sanction a stablecoin?
OFAC designates addresses and entities, not token contracts per se. However, if a stablecoin's issuer or a controlling multisig were designated, US persons would be prohibited from interacting with the stablecoin. The 50 Percent Rule could also apply if SDNs control the issuer.
\ No newline at end of file
diff --git a/faq/can-ofac-sanction-defi-frontends/index.html b/faq/can-ofac-sanction-defi-frontends/index.html
new file mode 100644
index 0000000..aac2988
--- /dev/null
+++ b/faq/can-ofac-sanction-defi-frontends/index.html
@@ -0,0 +1 @@
+Can OFAC sanction DeFi front-ends? | FAQ
Can OFAC sanction DeFi front-ends?
Can OFAC sanction DeFi front-ends?
While the Tornado Cash smart contracts themselves were designated, the front-end operators faced separate legal exposure. OFAC can and has targeted the individuals and entities operating DeFi front-ends that facilitate access to designated protocols.
\ No newline at end of file
diff --git a/faq/can-ofac-track-crypto-transactions/index.html b/faq/can-ofac-track-crypto-transactions/index.html
new file mode 100644
index 0000000..0dae495
--- /dev/null
+++ b/faq/can-ofac-track-crypto-transactions/index.html
@@ -0,0 +1 @@
+Can OFAC track crypto transactions? | FAQ
Can OFAC track crypto transactions?
Can OFAC track crypto transactions?
Yes. Blockchain transactions are public by default. OFAC, working with blockchain analytics firms and exchanges, can trace fund flows across multiple chains, through mixers, and to centralized exchange deposit addresses. The transparency of public blockchains makes crypto enforcement more tractable than traditional finance.
\ No newline at end of file
diff --git a/faq/does-ofac-apply-to-layer-2-networks/index.html b/faq/does-ofac-apply-to-layer-2-networks/index.html
new file mode 100644
index 0000000..36ccc17
--- /dev/null
+++ b/faq/does-ofac-apply-to-layer-2-networks/index.html
@@ -0,0 +1 @@
+Does OFAC apply to Layer 2 networks? | FAQ
Does OFAC apply to Layer 2 networks?
Does OFAC apply to Layer 2 networks?
Layer 2 scaling solutions do not create a sanctions-free zone. Transactions on Arbitrum, Optimism, Base, Polygon, and other L2s are funds transfers subject to OFAC jurisdiction. The screening obligation is identical regardless of which layer processes the transaction.
\ No newline at end of file
diff --git a/faq/does-ofac-apply-to-non-us-companies/index.html b/faq/does-ofac-apply-to-non-us-companies/index.html
new file mode 100644
index 0000000..0c7648c
--- /dev/null
+++ b/faq/does-ofac-apply-to-non-us-companies/index.html
@@ -0,0 +1 @@
+Does OFAC apply to non-US companies? | FAQ
Does OFAC apply to non-US companies?
Does OFAC apply to non-US companies?
OFAC jurisdiction extends beyond US borders through several hooks: US persons (citizens, residents, entities) anywhere in the world, US dollar clearing (virtually all USD transactions touch a US bank), US-origin goods and technology, and secondary sanctions (targeting non-US persons for certain activities).
\ No newline at end of file
diff --git a/faq/does-ofac-apply-to-stablecoin-yield/index.html b/faq/does-ofac-apply-to-stablecoin-yield/index.html
new file mode 100644
index 0000000..934936f
--- /dev/null
+++ b/faq/does-ofac-apply-to-stablecoin-yield/index.html
@@ -0,0 +1 @@
+Does OFAC apply to stablecoin yield products? | FAQ
Does OFAC apply to stablecoin yield products?
Does OFAC apply to stablecoin yield products?
Stablecoin yield products involve multiple transfers: the deposit, periodic yield distributions, and eventual withdrawal. Every transfer is a potential sanctions touchpoint. Screen the depositor wallet, the yield distribution address, and the withdrawal destination.
\ No newline at end of file
diff --git a/faq/does-ofac-require-screening-for-stablecoin-issuance/index.html b/faq/does-ofac-require-screening-for-stablecoin-issuance/index.html
new file mode 100644
index 0000000..00e6252
--- /dev/null
+++ b/faq/does-ofac-require-screening-for-stablecoin-issuance/index.html
@@ -0,0 +1 @@
+Does OFAC require screening for stablecoin issuance? | FAQ
Does OFAC require screening for stablecoin issuance?
Does OFAC require screening for stablecoin issuance?
Stablecoin issuers must screen at two critical points: minting new tokens (who is receiving them?) and burning/redemption (who is sending them?). Both Circle and Tether maintain screening programs for these operations, and OFAC expects it.
\ No newline at end of file
diff --git a/faq/does-ofac-screening-replace-aml/index.html b/faq/does-ofac-screening-replace-aml/index.html
new file mode 100644
index 0000000..2ed36c8
--- /dev/null
+++ b/faq/does-ofac-screening-replace-aml/index.html
@@ -0,0 +1 @@
+Does OFAC screening replace AML compliance? | FAQ
Does OFAC screening replace AML compliance?
Does OFAC screening replace AML compliance?
OFAC screening checks counterparties against sanctions lists. AML compliance involves customer due diligence, suspicious activity reporting, and transaction monitoring. You need both — OFAC screening alone doesn't satisfy AML obligations, and AML programs without OFAC screening miss prohibited transactions.
\ No newline at end of file
diff --git a/faq/how-does-sanctionsai-compare-to-chainalysis/index.html b/faq/how-does-sanctionsai-compare-to-chainalysis/index.html
new file mode 100644
index 0000000..9d630ce
--- /dev/null
+++ b/faq/how-does-sanctionsai-compare-to-chainalysis/index.html
@@ -0,0 +1 @@
+How does SanctionsAI compare to Chainalysis? | FAQ
How does SanctionsAI compare to Chainalysis?
How does SanctionsAI compare to Chainalysis?
SanctionsAI and Chainalysis serve different markets. SanctionsAI: screening API for developers and AI agents, free tier, sub-100ms. Chainalysis: enterprise blockchain analytics, investigation tools, compliance suite, enterprise pricing. See detailed comparison: /vs/chainalysis.
\ No newline at end of file
diff --git a/faq/how-to-build-ofac-compliance-program/index.html b/faq/how-to-build-ofac-compliance-program/index.html
new file mode 100644
index 0000000..548e894
--- /dev/null
+++ b/faq/how-to-build-ofac-compliance-program/index.html
@@ -0,0 +1 @@
+How to build an OFAC compliance program | FAQ
How to build an OFAC compliance program
How to build an OFAC compliance program
Building an OFAC compliance program: (1) Get management commitment — written policy, signed by leadership. (2) Conduct a risk assessment — where is your sanctions exposure? (3) Implement controls — screening technology, procedures, logs. (4) Test and audit — verify controls work. (5) Train your team — document who was trained and when.
\ No newline at end of file
diff --git a/faq/how-to-handle-sanctions-false-positive/index.html b/faq/how-to-handle-sanctions-false-positive/index.html
new file mode 100644
index 0000000..7c0ef45
--- /dev/null
+++ b/faq/how-to-handle-sanctions-false-positive/index.html
@@ -0,0 +1 @@
+How to handle a sanctions screening false positive | FAQ
How to handle a sanctions screening false positive
How to handle a sanctions screening false positive
False positive procedure: (1) Compare the counterparty's details (DOB, address, nationality) against the SDN entry. (2) If clearly different, document the distinction and close the alert. (3) If uncertain, escalate for enhanced due diligence. Never dismiss without documentation.
\ No newline at end of file
diff --git a/faq/how-to-integrate-ofac-screening-into-agent/index.html b/faq/how-to-integrate-ofac-screening-into-agent/index.html
new file mode 100644
index 0000000..9d2dfaa
--- /dev/null
+++ b/faq/how-to-integrate-ofac-screening-into-agent/index.html
@@ -0,0 +1 @@
+How to integrate OFAC screening into an AI agent | FAQ
How to integrate OFAC screening into an AI agent
How to integrate OFAC screening into an AI agent
Integration is one function call: before the agent signs a payment, call the screening API with the recipient's wallet, name, and country. If clean, proceed. If match, block and alert. MCP integration: sanctions_check(name='...', wallet='0x...'). REST: GET /sanctions?wallet=0x... CLI: agentmail check --wallet 0x...
\ No newline at end of file
diff --git a/faq/how-to-monitor-sanctions-compliance/index.html b/faq/how-to-monitor-sanctions-compliance/index.html
new file mode 100644
index 0000000..65c12c5
--- /dev/null
+++ b/faq/how-to-monitor-sanctions-compliance/index.html
@@ -0,0 +1 @@
+How to monitor sanctions compliance | FAQ
How to monitor sanctions compliance
How to monitor sanctions compliance
Monitoring requires: (1) Automated screening logs — every check is timestamped and stored. (2) Weekly log reviews — look for patterns, spikes in high-risk jurisdictions, missed checks. (3) Real-time alerts — a sanctions match should trigger immediate notification, not a silent log entry.
\ No newline at end of file
diff --git a/faq/how-to-screen-crypto-exchanges-for-ofac/index.html b/faq/how-to-screen-crypto-exchanges-for-ofac/index.html
new file mode 100644
index 0000000..23e5797
--- /dev/null
+++ b/faq/how-to-screen-crypto-exchanges-for-ofac/index.html
@@ -0,0 +1 @@
+How to screen crypto exchanges for OFAC compliance | FAQ
How to screen crypto exchanges for OFAC compliance
How to screen crypto exchanges for OFAC compliance
Exchange OFAC compliance: (1) Screen at customer onboarding — combine KYC with OFAC check. (2) Screen every deposit address — who is sending funds? (3) Screen every withdrawal address — where are funds going? (4) Maintain timestamped screening logs. (5) Block and report on matches.
\ No newline at end of file
diff --git a/faq/how-to-screen-stablecoin-payments/index.html b/faq/how-to-screen-stablecoin-payments/index.html
new file mode 100644
index 0000000..75e4b28
--- /dev/null
+++ b/faq/how-to-screen-stablecoin-payments/index.html
@@ -0,0 +1 @@
+How to screen stablecoin payments for OFAC | FAQ
How to screen stablecoin payments for OFAC
How to screen stablecoin payments for OFAC
Screening a stablecoin payment takes one API call: pass the recipient wallet to /sanctions. If clean, proceed. If match, block. This adds under 100ms to your payment pipeline. SanctionsAI free tier covers 5 checks/day — production plans from $19/mo.
\ No newline at end of file
diff --git a/faq/how-to-verify-ofac-compliance/index.html b/faq/how-to-verify-ofac-compliance/index.html
new file mode 100644
index 0000000..4190bef
--- /dev/null
+++ b/faq/how-to-verify-ofac-compliance/index.html
@@ -0,0 +1 @@
+How to verify OFAC compliance program effectiveness | FAQ
How to verify OFAC compliance program effectiveness
How to verify OFAC compliance program effectiveness
Verify your compliance program: (1) Test with known sanctioned wallets — does your system block them? (2) Review screening logs weekly — any missed checks, patterns? (3) Periodic independent audit — an external review of your program. (4) Document all findings and remediation actions.
\ No newline at end of file
diff --git a/faq/what-are-ofac-sanctions-programs-explained/index.html b/faq/what-are-ofac-sanctions-programs-explained/index.html
new file mode 100644
index 0000000..c1befa7
--- /dev/null
+++ b/faq/what-are-ofac-sanctions-programs-explained/index.html
@@ -0,0 +1 @@
+OFAC sanctions programs explained | FAQ
OFAC sanctions programs explained
OFAC sanctions programs explained
OFAC sanctions programs fall into two categories: country-specific (Iran, North Korea, Cuba, Syria, Russia/Ukraine, Venezuela, etc.) and thematic (Counter-Terrorism, Counter-Narcotics, Cyber, Global Magnitsky, Non-Proliferation). Each program has its own legal authority and scope of prohibitions.
\ No newline at end of file
diff --git a/faq/what-is-a-sanctions-match/index.html b/faq/what-is-a-sanctions-match/index.html
new file mode 100644
index 0000000..2b12ad3
--- /dev/null
+++ b/faq/what-is-a-sanctions-match/index.html
@@ -0,0 +1 @@
+What is a sanctions screening match? | FAQ
What is a sanctions screening match?
What is a sanctions screening match?
A sanctions match is when your screening tool flags a counterparty as potentially matching an SDN list entry. It's not a confirmed violation — it's an alert requiring investigation. True match: the counterparty IS the SDN (block the transaction). False positive: similar name, different person (document and dismiss).
\ No newline at end of file
diff --git a/faq/what-is-a-sanctions-screening-tool/index.html b/faq/what-is-a-sanctions-screening-tool/index.html
new file mode 100644
index 0000000..cb7ece4
--- /dev/null
+++ b/faq/what-is-a-sanctions-screening-tool/index.html
@@ -0,0 +1 @@
+What is a sanctions screening tool? | FAQ
What is a sanctions screening tool?
What is a sanctions screening tool?
A sanctions screening tool is any software that programmatically checks a counterparty against sanctions lists. Modern tools are APIs — you send a query (wallet, name, country) and get a result (clean or match) in milliseconds. No manual PDF searching required.
\ No newline at end of file
diff --git a/faq/what-is-an-ofac-risk-score/index.html b/faq/what-is-an-ofac-risk-score/index.html
new file mode 100644
index 0000000..69193b9
--- /dev/null
+++ b/faq/what-is-an-ofac-risk-score/index.html
@@ -0,0 +1 @@
+What is an OFAC sanctions risk score? | FAQ
What is an OFAC sanctions risk score?
What is an OFAC sanctions risk score?
An OFAC risk score is a 0-100 rating that quantifies sanctions exposure for a given transaction. Factors: counterparty wallet history, jurisdictional risk, mixer interaction, exchange deposit patterns, and PEP indicators. SanctionsAI's /risk endpoint provides per-transaction risk scores.
\ No newline at end of file
diff --git a/faq/what-is-ofac-compliance-for-bridges/index.html b/faq/what-is-ofac-compliance-for-bridges/index.html
new file mode 100644
index 0000000..0491d2a
--- /dev/null
+++ b/faq/what-is-ofac-compliance-for-bridges/index.html
@@ -0,0 +1 @@
+OFAC compliance for blockchain bridges | FAQ
OFAC compliance for blockchain bridges
OFAC compliance for blockchain bridges
Blockchain bridges move assets between chains — and every transfer has a source and destination address. If the source or destination is sanctioned, the bridge operator may have facilitated a prohibited transaction. Screen both ends of every bridge transfer.
\ No newline at end of file
diff --git a/faq/what-is-ofac-compliance-for-crypto-payments/index.html b/faq/what-is-ofac-compliance-for-crypto-payments/index.html
new file mode 100644
index 0000000..f106ab6
--- /dev/null
+++ b/faq/what-is-ofac-compliance-for-crypto-payments/index.html
@@ -0,0 +1 @@
+OFAC compliance for crypto payments | FAQ
OFAC compliance for crypto payments
OFAC compliance for crypto payments
Crypto payment compliance in three steps: (1) Screen the recipient wallet before every payment. (2) Screen the counterparty name if available. (3) Log every screening result with timestamp. Block on matches — don't just log and continue.
\ No newline at end of file
diff --git a/faq/what-is-ofac-compliance-for-web3/index.html b/faq/what-is-ofac-compliance-for-web3/index.html
new file mode 100644
index 0000000..88165fc
--- /dev/null
+++ b/faq/what-is-ofac-compliance-for-web3/index.html
@@ -0,0 +1 @@
+What is OFAC compliance for Web3? | FAQ
What is OFAC compliance for Web3?
What is OFAC compliance for Web3?
Web3's decentralized architecture does not exempt it from OFAC. Wherever there is a US person, a US dollar, or US nexus, sanctions obligations attach. The question is not whether OFAC applies — it's who in the stack has compliance responsibility.
\ No newline at end of file
diff --git a/faq/what-is-ofac-screening-for-agent-payments/index.html b/faq/what-is-ofac-screening-for-agent-payments/index.html
new file mode 100644
index 0000000..202fdbe
--- /dev/null
+++ b/faq/what-is-ofac-screening-for-agent-payments/index.html
@@ -0,0 +1 @@
+OFAC screening for AI agent payments | FAQ
OFAC screening for AI agent payments
OFAC screening for AI agent payments
AI agents with payment authority must screen before every payment — just like any payment processor. The difference: agents can process hundreds of payments per minute, making automated, real-time screening essential. A single API call per payment is the minimum viable control.
\ No newline at end of file
diff --git a/faq/what-is-ofac-screening-for-aml-programs/index.html b/faq/what-is-ofac-screening-for-aml-programs/index.html
new file mode 100644
index 0000000..4972aac
--- /dev/null
+++ b/faq/what-is-ofac-screening-for-aml-programs/index.html
@@ -0,0 +1 @@
+OFAC screening within AML programs | FAQ
OFAC screening within AML programs
OFAC screening within AML programs
AML and OFAC screening serve different but complementary purposes. AML detects suspicious patterns (structuring, unusual activity). OFAC screening identifies prohibited counterparties (SDNs, blocked persons). An AML program without OFAC screening is incomplete — you can't detect prohibited transactions through pattern analysis alone.
\ No newline at end of file
diff --git a/faq/what-is-ofac-screening-for-charities/index.html b/faq/what-is-ofac-screening-for-charities/index.html
new file mode 100644
index 0000000..cae423c
--- /dev/null
+++ b/faq/what-is-ofac-screening-for-charities/index.html
@@ -0,0 +1 @@
+OFAC screening for charitable organizations | FAQ
OFAC screening for charitable organizations
OFAC screening for charitable organizations
Charities operating in or sending funds to sanctioned jurisdictions face elevated OFAC scrutiny. While humanitarian exemptions and general licenses exist, the compliance burden is high. Every recipient must be screened, transactions must fit within the scope of applicable licenses, and documentation must be rigorous.
\ No newline at end of file
diff --git a/faq/what-is-ofac-screening-for-cross-border-payments/index.html b/faq/what-is-ofac-screening-for-cross-border-payments/index.html
new file mode 100644
index 0000000..39bcc20
--- /dev/null
+++ b/faq/what-is-ofac-screening-for-cross-border-payments/index.html
@@ -0,0 +1 @@
+OFAC screening for cross-border payments | FAQ
OFAC screening for cross-border payments
OFAC screening for cross-border payments
Cross-border payments multiply sanctions risk because they involve multiple jurisdictions, each with its own sanctions regime. A payment from the US to a European company that routes through a Middle Eastern correspondent bank may touch three sets of sanctions lists.
Why cross-border is higher risk
Every intermediary in the payment chain adds a compliance checkpoint. The US originator is liable for what the correspondent banks do downstream. Screening the ultimate beneficiary is necessary but not sufficient — the payment path matters.
\ No newline at end of file
diff --git a/faq/what-is-ofac-screening-for-crypto-wallets/index.html b/faq/what-is-ofac-screening-for-crypto-wallets/index.html
new file mode 100644
index 0000000..2022e8b
--- /dev/null
+++ b/faq/what-is-ofac-screening-for-crypto-wallets/index.html
@@ -0,0 +1 @@
+OFAC screening for crypto wallets | FAQ
OFAC screening for crypto wallets
OFAC screening for crypto wallets
Crypto wallet screening is the fastest and most accurate form of OFAC screening. Wallet addresses are unique — there is no fuzzy matching ambiguity. The SanctionsAI API checks against 947 SDN-listed addresses in under 100ms.
How it works
Pass a wallet address to the screening endpoint. The API checks it against a regularly synced index of OFAC-designated addresses. Result: clean (proceed) or match (block). Free tier covers 5 checks/day.
\ No newline at end of file
diff --git a/faq/what-is-ofac-screening-for-custodial-wallets/index.html b/faq/what-is-ofac-screening-for-custodial-wallets/index.html
new file mode 100644
index 0000000..4768d03
--- /dev/null
+++ b/faq/what-is-ofac-screening-for-custodial-wallets/index.html
@@ -0,0 +1 @@
+OFAC screening for custodial wallets | FAQ
OFAC screening for custodial wallets
OFAC screening for custodial wallets
Custodial wallet providers act as intermediaries — they hold user funds and process transactions. OFAC expects custodians to screen both incoming deposits (who is sending funds?) and outgoing withdrawals (where are funds going?). Failure to screen exposes the custodian to facilitation liability.
\ No newline at end of file
diff --git a/faq/what-is-ofac-screening-for-dao-treasuries/index.html b/faq/what-is-ofac-screening-for-dao-treasuries/index.html
new file mode 100644
index 0000000..374a2c1
--- /dev/null
+++ b/faq/what-is-ofac-screening-for-dao-treasuries/index.html
@@ -0,0 +1 @@
+OFAC screening for DAO treasuries | FAQ
OFAC screening for DAO treasuries
OFAC screening for DAO treasuries
DAOs are not exempt. If a DAO treasury sends funds to a sanctioned wallet — whether by governance vote, multisig, or automated agent — the transaction is a sanctions violation. The decentralized nature of the DAO does not shield it from OFAC liability.
\ No newline at end of file
diff --git a/faq/what-is-ofac-screening-for-defi-protocols/index.html b/faq/what-is-ofac-screening-for-defi-protocols/index.html
new file mode 100644
index 0000000..3fc4760
--- /dev/null
+++ b/faq/what-is-ofac-screening-for-defi-protocols/index.html
@@ -0,0 +1 @@
+OFAC screening for DeFi protocols | FAQ
OFAC screening for DeFi protocols
OFAC screening for DeFi protocols
DeFi protocols face unique OFAC challenges. The front-end operator may be liable for providing an interface that allows sanctioned wallets to interact with the protocol. Front-end wallet screening is the baseline defense.
\ No newline at end of file
diff --git a/faq/what-is-ofac-screening-for-defi-yield/index.html b/faq/what-is-ofac-screening-for-defi-yield/index.html
new file mode 100644
index 0000000..32b5936
--- /dev/null
+++ b/faq/what-is-ofac-screening-for-defi-yield/index.html
@@ -0,0 +1 @@
+OFAC screening for DeFi yield protocols | FAQ
OFAC screening for DeFi yield protocols
OFAC screening for DeFi yield protocols
DeFi yield protocols distribute value to wallet addresses — and those distributions are transfers subject to OFAC. If a sanctioned wallet receives yield from your protocol, the protocol has distributed funds to an SDN. Screen yield distribution addresses the same way you screen any other payment.
\ No newline at end of file
diff --git a/faq/what-is-ofac-screening-for-kyc-providers/index.html b/faq/what-is-ofac-screening-for-kyc-providers/index.html
new file mode 100644
index 0000000..fbed3f0
--- /dev/null
+++ b/faq/what-is-ofac-screening-for-kyc-providers/index.html
@@ -0,0 +1 @@
+OFAC screening for KYC providers | FAQ
OFAC screening for KYC providers
OFAC screening for KYC providers
KYC identifies customers; OFAC screening determines whether you can transact with them. A KYC process that doesn't include sanctions screening misses the most critical compliance check. The two should be integrated — verify identity, then screen for sanctions, in a single workflow.
\ No newline at end of file
diff --git a/faq/what-is-ofac-screening-for-nft-marketplaces/index.html b/faq/what-is-ofac-screening-for-nft-marketplaces/index.html
new file mode 100644
index 0000000..00c7a9f
--- /dev/null
+++ b/faq/what-is-ofac-screening-for-nft-marketplaces/index.html
@@ -0,0 +1 @@
+OFAC screening for NFT marketplaces | FAQ
OFAC screening for NFT marketplaces
OFAC screening for NFT marketplaces
NFT marketplaces are intermediaries — OFAC expects screening of both parties on every trade. The marketplace facilitates the exchange of value between buyer and seller; if either is sanctioned, the marketplace may have facilitated a prohibited transaction.
\ No newline at end of file
diff --git a/faq/what-is-ofac-screening-for-payment-apis/index.html b/faq/what-is-ofac-screening-for-payment-apis/index.html
new file mode 100644
index 0000000..e2963cf
--- /dev/null
+++ b/faq/what-is-ofac-screening-for-payment-apis/index.html
@@ -0,0 +1 @@
+OFAC screening for payment APIs | FAQ
OFAC screening for payment APIs
OFAC screening for payment APIs
Payment APIs process transactions, but screening responsibility varies. Stripe screens fiat payments; Coinbase Commerce may screen crypto payments. However, OFAC's strict liability means the developer — not the API provider — bears ultimate responsibility. Add your own screening layer.
\ No newline at end of file
diff --git a/faq/what-is-ofac-screening-for-payment-gateways/index.html b/faq/what-is-ofac-screening-for-payment-gateways/index.html
new file mode 100644
index 0000000..3ee446d
--- /dev/null
+++ b/faq/what-is-ofac-screening-for-payment-gateways/index.html
@@ -0,0 +1 @@
+OFAC screening for payment gateways | FAQ
OFAC screening for payment gateways
OFAC screening for payment gateways
Payment gateways sit at the intersection of merchants and customers. OFAC expects screening in both directions: is the merchant sanctioned? Is the customer sanctioned? The gateway facilitates the transaction and can be liable for prohibited payments flowing through its infrastructure.
\ No newline at end of file
diff --git a/faq/what-is-ofac-screening-for-remittance/index.html b/faq/what-is-ofac-screening-for-remittance/index.html
new file mode 100644
index 0000000..c34e6fa
--- /dev/null
+++ b/faq/what-is-ofac-screening-for-remittance/index.html
@@ -0,0 +1 @@
+OFAC screening for remittance services | FAQ
OFAC screening for remittance services
OFAC screening for remittance services
Remittance services face dual-sided screening: the sender and the recipient must both be screened. Remittances to comprehensively sanctioned countries (Cuba, Iran, North Korea, Syria, Crimea) are generally prohibited. Remittances to individuals in targeted-sanctions countries require screening against the SDN list.
\ No newline at end of file
diff --git a/faq/what-is-ofac-screening-for-stablecoin-transfers/index.html b/faq/what-is-ofac-screening-for-stablecoin-transfers/index.html
new file mode 100644
index 0000000..7647110
--- /dev/null
+++ b/faq/what-is-ofac-screening-for-stablecoin-transfers/index.html
@@ -0,0 +1 @@
+OFAC screening for stablecoin transfers | FAQ
OFAC screening for stablecoin transfers
OFAC screening for stablecoin transfers
Stablecoins are not exempt from sanctions. A USDC transfer to a sanctioned wallet is a prohibited transaction under OFAC's strict liability standard. The asset being pegged to USD does not change the legal obligation.
Issuer freezes
Circle (USDC) and Tether (USDT) have frozen millions in sanctioned addresses. Your agent's transfer may be frozen at the contract level after the fact — but the violation already occurred the moment the transfer was initiated.
\ No newline at end of file
diff --git a/faq/what-is-ofac-screening-for-token-launches/index.html b/faq/what-is-ofac-screening-for-token-launches/index.html
new file mode 100644
index 0000000..d8855ef
--- /dev/null
+++ b/faq/what-is-ofac-screening-for-token-launches/index.html
@@ -0,0 +1 @@
+OFAC screening for token launches and ICOs | FAQ
OFAC screening for token launches and ICOs
OFAC screening for token launches and ICOs
Token launches, ICOs, and airdrops involve distributing tokens to wallet addresses — and those distributions are subject to OFAC. Selling tokens to or airdropping tokens to a sanctioned wallet is a prohibited transaction. Screen every participant wallet before distribution.
\ No newline at end of file
diff --git a/glossary/ofac-compliance-audit/index.html b/glossary/ofac-compliance-audit/index.html
new file mode 100644
index 0000000..2072631
--- /dev/null
+++ b/glossary/ofac-compliance-audit/index.html
@@ -0,0 +1 @@
+OFAC Compliance Audit | Glossary
OFAC Compliance Audit
OFAC Compliance Audit
An OFAC compliance audit evaluates a sanctions compliance program against regulatory expectations. Auditors examine screening coverage, list currency, match handling procedures, documentation, and training. A clean audit is a powerful mitigating factor in any enforcement action.
\ No newline at end of file
diff --git a/glossary/ofac-compliance-gap/index.html b/glossary/ofac-compliance-gap/index.html
new file mode 100644
index 0000000..02af34d
--- /dev/null
+++ b/glossary/ofac-compliance-gap/index.html
@@ -0,0 +1 @@
+OFAC Compliance Gap | Glossary
OFAC Compliance Gap
OFAC Compliance Gap
A compliance gap is any area where your screening program falls short of regulatory expectations. Common gaps: unscreened payment channels (agent payments, crypto transfers, API-based payments), outdated SDN list, no audit logs, missing policies, or untested blocking procedures.
\ No newline at end of file
diff --git a/glossary/ofac-compliance-reporting/index.html b/glossary/ofac-compliance-reporting/index.html
new file mode 100644
index 0000000..66c5f36
--- /dev/null
+++ b/glossary/ofac-compliance-reporting/index.html
@@ -0,0 +1 @@
+OFAC Compliance Reporting | Glossary
OFAC Compliance Reporting
OFAC Compliance Reporting
Compliance reporting includes: initial blocked property report (within 10 business days of blocking), annual report of blocked property (by September 30), and rejected transaction reports. Failure to report is itself a compliance violation.
\ No newline at end of file
diff --git a/glossary/ofac-compliance-technology/index.html b/glossary/ofac-compliance-technology/index.html
new file mode 100644
index 0000000..6722dbf
--- /dev/null
+++ b/glossary/ofac-compliance-technology/index.html
@@ -0,0 +1 @@
+OFAC Compliance Technology | Glossary
OFAC Compliance Technology
OFAC Compliance Technology
Compliance technology spans from free APIs (SanctionsAI free tier) to enterprise platforms ($50K+/year). The technology stack has evolved from manual PDF searches to real-time, API-based screening that integrates directly into payment pipelines and agent frameworks.
\ No newline at end of file
diff --git a/glossary/ofac-compliance-testing/index.html b/glossary/ofac-compliance-testing/index.html
new file mode 100644
index 0000000..02d57fc
--- /dev/null
+++ b/glossary/ofac-compliance-testing/index.html
@@ -0,0 +1 @@
+OFAC Compliance Testing | Glossary
OFAC Compliance Testing
OFAC Compliance Testing
Compliance testing validates that your screening program actually works. Key tests: screen known sanctioned wallets (should return match), attempt payments to sanctioned addresses (should be blocked), review screening logs for gaps, and verify list sync frequency.
\ No newline at end of file
diff --git a/glossary/ofac-compliance-training/index.html b/glossary/ofac-compliance-training/index.html
new file mode 100644
index 0000000..97e3cd7
--- /dev/null
+++ b/glossary/ofac-compliance-training/index.html
@@ -0,0 +1 @@
+OFAC Compliance Training | Glossary
OFAC Compliance Training
OFAC Compliance Training
Compliance training is a pillar of OFAC's five-part framework. Employees must understand what sanctions are, how screening works, what to do on a match, and the consequences of violations. Training must be documented (who, when, what) and conducted at least annually.
\ No newline at end of file
diff --git a/glossary/ofac-delisting/index.html b/glossary/ofac-delisting/index.html
new file mode 100644
index 0000000..309088b
--- /dev/null
+++ b/glossary/ofac-delisting/index.html
@@ -0,0 +1 @@
+OFAC Delisting | Glossary
OFAC Delisting
OFAC Delisting
Delisting is the removal of a person or entity from the SDN list. The designated party files a petition with OFAC demonstrating that the basis for designation no longer applies. OFAC reviews and either grants or denies. Delisting can take months to years.
\ No newline at end of file
diff --git a/glossary/ofac-designation-authority/index.html b/glossary/ofac-designation-authority/index.html
new file mode 100644
index 0000000..6fdd702
--- /dev/null
+++ b/glossary/ofac-designation-authority/index.html
@@ -0,0 +1 @@
+OFAC Designation Authority | Glossary
OFAC Designation Authority
OFAC Designation Authority
Every OFAC designation is grounded in a specific legal authority: an Executive Order (e.g., EO 13224 for terrorism, EO 14024 for Russia) or a statute (e.g., IEEPA, the Global Magnitsky Act). The designation authority determines the scope of the prohibition and the parties covered.
\ No newline at end of file
diff --git a/glossary/ofac-enforcement-action/index.html b/glossary/ofac-enforcement-action/index.html
new file mode 100644
index 0000000..2dde467
--- /dev/null
+++ b/glossary/ofac-enforcement-action/index.html
@@ -0,0 +1 @@
+OFAC Enforcement Action | Glossary
OFAC Enforcement Action
OFAC Enforcement Action
An OFAC enforcement action is a formal resolution of a sanctions violation investigation. It ranges from a cautionary letter (no penalty, just a warning) to a civil penalty (monetary fine) to a criminal referral (DOJ prosecution). Most enforcement actions are civil settlements.
\ No newline at end of file
diff --git a/glossary/ofac-enforcement-precedent/index.html b/glossary/ofac-enforcement-precedent/index.html
new file mode 100644
index 0000000..f203266
--- /dev/null
+++ b/glossary/ofac-enforcement-precedent/index.html
@@ -0,0 +1 @@
+OFAC Enforcement Precedent | Glossary
OFAC Enforcement Precedent
OFAC Enforcement Precedent
Enforcement precedent comes from published OFAC enforcement actions. Key precedents: Tornado Cash (protocols can be designated), Binance ($968M penalty set the high-water mark), BitGo/BitPay (crypto-specific enforcement began in 2020), and the increasing focus on automated/agent transactions.
\ No newline at end of file
diff --git a/glossary/ofac-enforcement-priority/index.html b/glossary/ofac-enforcement-priority/index.html
new file mode 100644
index 0000000..02beab2
--- /dev/null
+++ b/glossary/ofac-enforcement-priority/index.html
@@ -0,0 +1 @@
+OFAC Enforcement Priority | Glossary
OFAC Enforcement Priority
OFAC Enforcement Priority
OFAC's enforcement priorities evolve but current focus areas include: cryptocurrency and virtual assets, ransomware payments, Russia sanctions evasion (especially post-2022), Iran sanctions circumvention, and emerging technology including AI agents with payment capabilities.
\ No newline at end of file
diff --git a/glossary/ofac-kyc-integration/index.html b/glossary/ofac-kyc-integration/index.html
new file mode 100644
index 0000000..3f4fd78
--- /dev/null
+++ b/glossary/ofac-kyc-integration/index.html
@@ -0,0 +1 @@
+OFAC-KYC Integration | Glossary
OFAC-KYC Integration
OFAC-KYC Integration
KYC-OFAC integration means screening for sanctions at the same time you verify customer identity. Rather than running KYC checks first and OFAC screening later, the two are combined: verify who the customer is AND check if they're sanctioned simultaneously.
\ No newline at end of file
diff --git a/glossary/ofac-list-synchronization/index.html b/glossary/ofac-list-synchronization/index.html
new file mode 100644
index 0000000..211f3ae
--- /dev/null
+++ b/glossary/ofac-list-synchronization/index.html
@@ -0,0 +1 @@
+OFAC List Synchronization | Glossary
OFAC List Synchronization
OFAC List Synchronization
List sync is how your screening tool stays current with OFAC's daily updates. Best practice: hourly sync — the fastest practical frequency. Daily sync is the minimum acceptable. Weekly or monthly syncs create compliance gaps where newly designated entities can transact undetected.
\ No newline at end of file
diff --git a/glossary/ofac-name-screening/index.html b/glossary/ofac-name-screening/index.html
new file mode 100644
index 0000000..656c51c
--- /dev/null
+++ b/glossary/ofac-name-screening/index.html
@@ -0,0 +1 @@
+OFAC Name Screening | Glossary
OFAC Name Screening
OFAC Name Screening
Name screening checks person and entity names against OFAC's SDN list. It's more complex than wallet screening because names vary (aliases, transliterations, misspellings). Effective name screening requires fuzzy matching algorithms that catch near-matches while keeping false positives manageable.
\ No newline at end of file
diff --git a/glossary/ofac-payment-screening/index.html b/glossary/ofac-payment-screening/index.html
new file mode 100644
index 0000000..6f96ac0
--- /dev/null
+++ b/glossary/ofac-payment-screening/index.html
@@ -0,0 +1 @@
+OFAC Payment Screening | Glossary
OFAC Payment Screening
OFAC Payment Screening
Payment screening is the core OFAC compliance activity: before any funds move, check the recipient against the SDN list. If clean, proceed. If match, block. This single check is the most important control in any sanctions compliance program.
\ No newline at end of file
diff --git a/glossary/ofac-risk-based-approach/index.html b/glossary/ofac-risk-based-approach/index.html
new file mode 100644
index 0000000..a63b0bd
--- /dev/null
+++ b/glossary/ofac-risk-based-approach/index.html
@@ -0,0 +1 @@
+OFAC Risk-Based Approach | Glossary
OFAC Risk-Based Approach
OFAC Risk-Based Approach
A risk-based approach means calibrating compliance intensity to risk level. High-risk transactions (crypto, cross-border, high-value) get enhanced screening; low-risk transactions (domestic, known counterparties) may use standard screening. OFAC expects a risk-based approach rather than a one-size-fits-all program.
\ No newline at end of file
diff --git a/glossary/ofac-risk-indicator/index.html b/glossary/ofac-risk-indicator/index.html
new file mode 100644
index 0000000..a11272d
--- /dev/null
+++ b/glossary/ofac-risk-indicator/index.html
@@ -0,0 +1 @@
+OFAC Risk Indicator | Glossary
OFAC Risk Indicator
OFAC Risk Indicator
Risk indicators are flags that a transaction may involve sanctions risk even without a direct SDN match. Key indicators: counterparty in a high-risk jurisdiction, prior mixer interaction, lack of KYC information, unusually complex transaction path, or new wallet with no history.
\ No newline at end of file
diff --git a/glossary/ofac-screening-api-endpoint/index.html b/glossary/ofac-screening-api-endpoint/index.html
new file mode 100644
index 0000000..f4176f6
--- /dev/null
+++ b/glossary/ofac-screening-api-endpoint/index.html
@@ -0,0 +1 @@
+OFAC Screening API Endpoint | Glossary
OFAC Screening API Endpoint
OFAC Screening API Endpoint
The API endpoint is the interface where your application sends screening queries. SanctionsAI's primary endpoint is GET /sanctions?wallet=X&name=Y&country=Z. It returns a JSON response: {"clean": true/false, "matches": [...]}. Sub-100ms response time.
\ No newline at end of file
diff --git a/glossary/ofac-screening-benchmark/index.html b/glossary/ofac-screening-benchmark/index.html
new file mode 100644
index 0000000..e4a06c6
--- /dev/null
+++ b/glossary/ofac-screening-benchmark/index.html
@@ -0,0 +1 @@
+OFAC Screening Benchmark | Glossary
OFAC Screening Benchmark
OFAC Screening Benchmark
Screening benchmarks measure tool performance: accuracy (does it catch all SDNs?), speed (milliseconds per check), and false-positive rate (how many clean counterparties get flagged?). SanctionsAI publishes benchmark results at /benchmarks.
\ No newline at end of file
diff --git a/glossary/ofac-screening-coverage/index.html b/glossary/ofac-screening-coverage/index.html
new file mode 100644
index 0000000..b16c960
--- /dev/null
+++ b/glossary/ofac-screening-coverage/index.html
@@ -0,0 +1 @@
+OFAC Screening Coverage | Glossary
OFAC Screening Coverage
OFAC Screening Coverage
Screening coverage measures how many of your transactions are actually screened for sanctions. 100% coverage (every transaction screened) is the standard. Sampling (screening only a portion) creates compliance gaps. Automated API-based screening makes 100% coverage achievable at negligible cost.
\ No newline at end of file
diff --git a/glossary/ofac-screening-for-ai/index.html b/glossary/ofac-screening-for-ai/index.html
new file mode 100644
index 0000000..f464338
--- /dev/null
+++ b/glossary/ofac-screening-for-ai/index.html
@@ -0,0 +1 @@
+OFAC Screening for AI | Glossary
OFAC Screening for AI
OFAC Screening for AI
AI screening adapts traditional sanctions compliance to the agent context. Key differences: velocity (agents can process hundreds of payments/minute), opacity (agent decision paths may be hard to audit), and scope (agents may interact with unanticipated counterparties).
\ No newline at end of file
diff --git a/glossary/ofac-screening-integration-pattern/index.html b/glossary/ofac-screening-integration-pattern/index.html
new file mode 100644
index 0000000..c8dee0d
--- /dev/null
+++ b/glossary/ofac-screening-integration-pattern/index.html
@@ -0,0 +1 @@
+OFAC Screening Integration Pattern | Glossary
OFAC Screening Integration Pattern
OFAC Screening Integration Pattern
Integration patterns: Pre-payment gate (screen immediately before payment authorization — recommended), event-driven (screen when a payment event is emitted), batch (screen accumulated transactions periodically — not recommended for real-time). SanctionsAI supports all three.
\ No newline at end of file
diff --git a/glossary/ofac-screening-log/index.html b/glossary/ofac-screening-log/index.html
new file mode 100644
index 0000000..b82ce09
--- /dev/null
+++ b/glossary/ofac-screening-log/index.html
@@ -0,0 +1 @@
+OFAC Screening Log | Glossary
OFAC Screening Log
OFAC Screening Log
A screening log is the primary audit record of your compliance program. Each entry should include: timestamp, screening inputs (wallet, name, country), screening result (clean or matched), disposition (proceeded, blocked, rejected), and the identity of the agent or system that performed the check.
\ No newline at end of file
diff --git a/glossary/ofac-screening-methodology/index.html b/glossary/ofac-screening-methodology/index.html
new file mode 100644
index 0000000..439e486
--- /dev/null
+++ b/glossary/ofac-screening-methodology/index.html
@@ -0,0 +1 @@
+OFAC Screening Methodology | Glossary
OFAC Screening Methodology
OFAC Screening Methodology
Screening methodology determines how matches are identified. Exact matching: fastest, lowest false positives, misses aliases. Fuzzy matching: catches aliases and spelling variations, more false positives. AI-based: best balance of catch rate and precision, newer technology.
\ No newline at end of file
diff --git a/glossary/ofac-screening-policy/index.html b/glossary/ofac-screening-policy/index.html
new file mode 100644
index 0000000..3a0dcc5
--- /dev/null
+++ b/glossary/ofac-screening-policy/index.html
@@ -0,0 +1 @@
+OFAC Screening Policy | Glossary
OFAC Screening Policy
OFAC Screening Policy
A screening policy is the written document that defines your compliance program. It should cover: what transactions are screened, which lists are used, how often lists are updated, what happens on a match, who is responsible, and how the program is tested and reviewed.
\ No newline at end of file
diff --git a/glossary/ofac-screening-sdk/index.html b/glossary/ofac-screening-sdk/index.html
new file mode 100644
index 0000000..97e82ff
--- /dev/null
+++ b/glossary/ofac-screening-sdk/index.html
@@ -0,0 +1 @@
+OFAC Screening SDK | Glossary
OFAC Screening SDK
OFAC Screening SDK
An OFAC screening SDK packages sanctions checking into a library (Python, JavaScript, Rust) that developers drop into their application. It handles API calls, error handling, and result parsing — reducing the integration to a single function call. SanctionsAI's MCP server serves this role for AI agents.
\ No newline at end of file
diff --git a/glossary/ofac-secondary-sanctions/index.html b/glossary/ofac-secondary-sanctions/index.html
new file mode 100644
index 0000000..ce3fe10
--- /dev/null
+++ b/glossary/ofac-secondary-sanctions/index.html
@@ -0,0 +1 @@
+Secondary Sanctions | Glossary
Secondary Sanctions
Secondary Sanctions
Secondary sanctions target non-US persons for certain activities (e.g., significant transactions with Iran's energy sector, support for Russia's defense sector). They don't require a US nexus — they threaten to cut the target off from the US financial system unless the activity stops.
\ No newline at end of file
diff --git a/glossary/ofac-strict-liability/index.html b/glossary/ofac-strict-liability/index.html
new file mode 100644
index 0000000..7e9728c
--- /dev/null
+++ b/glossary/ofac-strict-liability/index.html
@@ -0,0 +1 @@
+Strict Liability | Glossary
Strict Liability
Strict Liability
Strict liability means a sanctions violation occurs regardless of whether you knew about it or intended it. If your agent pays a sanctioned wallet, the violation exists — even if you had no idea. This is why pre-payment screening is the minimum viable defense: it prevents violations, not excuses them.
\ No newline at end of file
diff --git a/glossary/ofac-wallet-clustering/index.html b/glossary/ofac-wallet-clustering/index.html
new file mode 100644
index 0000000..017295d
--- /dev/null
+++ b/glossary/ofac-wallet-clustering/index.html
@@ -0,0 +1 @@
+OFAC Wallet Clustering | Glossary
OFAC Wallet Clustering
OFAC Wallet Clustering
Wallet clustering identifies groups of addresses controlled by the same entity — essential for sanctions enforcement because a designation on one address may indicate risk across the entire cluster. Blockchain analytics firms use shared inputs, change addresses, and behavioral patterns to build clusters.
\ No newline at end of file
diff --git a/glossary/sanctions-screening-engine/index.html b/glossary/sanctions-screening-engine/index.html
new file mode 100644
index 0000000..aac6167
--- /dev/null
+++ b/glossary/sanctions-screening-engine/index.html
@@ -0,0 +1 @@
+Sanctions Screening Engine | Glossary
Sanctions Screening Engine
Sanctions Screening Engine
The screening engine is the heart of any sanctions compliance tool — it takes counterparty data (name, wallet, country), searches against the sanctions database, applies matching algorithms (exact, fuzzy, AI), and returns a result. Engine quality determines screening accuracy and speed.
\ No newline at end of file
diff --git a/learn/how-ofac-penalties-are-calculated/index.html b/learn/how-ofac-penalties-are-calculated/index.html
new file mode 100644
index 0000000..bec8551
--- /dev/null
+++ b/learn/how-ofac-penalties-are-calculated/index.html
@@ -0,0 +1 @@
+How OFAC penalties are calculated | Learn
How OFAC penalties are calculated
How OFAC penalties are calculated
OFAC penalty calculation: (1) Determine if the violation is egregious or non-egregious. (2) Calculate the base penalty based on the statutory maximum ($330,944 or 2x transaction value). (3) Apply aggravating factors (increase). (4) Apply mitigating factors (decrease). (5) The result is the recommended penalty — subject to negotiation and settlement.
\ No newline at end of file
diff --git a/learn/how-to-choose-ofac-sanctions-screening-tool/index.html b/learn/how-to-choose-ofac-sanctions-screening-tool/index.html
new file mode 100644
index 0000000..51b6125
--- /dev/null
+++ b/learn/how-to-choose-ofac-sanctions-screening-tool/index.html
@@ -0,0 +1 @@
+How to choose an OFAC sanctions screening tool | Learn
How to choose an OFAC sanctions screening tool
How to choose an OFAC sanctions screening tool
Selection criteria: Accuracy (false positive rate, catch rate), Speed (<100ms for real-time), Coverage (SDN + other lists), Integration patterns (REST, MCP, SDKs), Pricing (free tier, transparent scaling), Audit trail (timestamped, searchable logs), and support (docs, responsiveness).
\ No newline at end of file
diff --git a/learn/ofac-sanctions-compliance-for-crypto-startups/index.html b/learn/ofac-sanctions-compliance-for-crypto-startups/index.html
new file mode 100644
index 0000000..3f0bdd1
--- /dev/null
+++ b/learn/ofac-sanctions-compliance-for-crypto-startups/index.html
@@ -0,0 +1 @@
+OFAC compliance for crypto startups | Learn
OFAC compliance for crypto startups
OFAC compliance for crypto startups
Crypto startup compliance MVP: (1) Wire a screening API into your payment path. (2) Write a one-page compliance policy. (3) Enable audit logging. (4) Document what happens on a sanctions match. That's it — you don't need a compliance department or enterprise software in year one.
\ No newline at end of file
diff --git a/learn/ofac-sanctions-compliance-for-exchanges/index.html b/learn/ofac-sanctions-compliance-for-exchanges/index.html
new file mode 100644
index 0000000..83cffb9
--- /dev/null
+++ b/learn/ofac-sanctions-compliance-for-exchanges/index.html
@@ -0,0 +1 @@
+OFAC sanctions compliance for exchanges | Learn
OFAC sanctions compliance for exchanges
OFAC sanctions compliance for exchanges
Exchange compliance covers: (1) Customer onboarding — KYC + OFAC screening combined. (2) Transaction screening — every deposit and withdrawal address checked. (3) Ongoing monitoring — re-screening on list updates, transaction pattern analysis. (4) Reporting — blocked property reports, annual reports. (5) Training — staff trained on sanctions procedures.
\ No newline at end of file
diff --git a/learn/ofac-sanctions-compliance-for-fintech/index.html b/learn/ofac-sanctions-compliance-for-fintech/index.html
new file mode 100644
index 0000000..4ba33b9
--- /dev/null
+++ b/learn/ofac-sanctions-compliance-for-fintech/index.html
@@ -0,0 +1 @@
+OFAC sanctions compliance for fintech | Learn
OFAC sanctions compliance for fintech
OFAC sanctions compliance for fintech
Fintech compliance covers OFAC (sanctions screening) and FinCEN (AML/BSA). The two are operationally linked: KYC identifies the customer, OFAC screening determines if you can transact with them. Build a unified workflow: verify identity → screen for sanctions → assess AML risk → process transaction → log everything.
\ No newline at end of file
diff --git a/learn/ofac-sanctions-screening-for-enterprise/index.html b/learn/ofac-sanctions-screening-for-enterprise/index.html
new file mode 100644
index 0000000..05fec72
--- /dev/null
+++ b/learn/ofac-sanctions-screening-for-enterprise/index.html
@@ -0,0 +1 @@
+OFAC sanctions screening for enterprise | Learn
OFAC sanctions screening for enterprise
OFAC sanctions screening for enterprise
Enterprise screening requirements: multi-jurisdiction list coverage (OFAC, EU, UN, UK, etc.), high-throughput API (100K+ checks/month), custom matching rules, integration with existing GRC platforms, dedicated support, SLA guarantees, and SOC 2 compliance. SanctionsAI Pro tier ($99/mo) covers the mid-market; enterprise solutions start at $50K+/year.
\ No newline at end of file
diff --git a/learn/ofac-screeening-for-agent-developers/index.html b/learn/ofac-screeening-for-agent-developers/index.html
new file mode 100644
index 0000000..5d0018a
--- /dev/null
+++ b/learn/ofac-screeening-for-agent-developers/index.html
@@ -0,0 +1 @@
+OFAC screening for AI agent developers | Learn
OFAC screening for AI agent developers
OFAC screening for AI agent developers
Agent developers need: (1) An inventory of every payment path the agent can use. (2) A pre-payment screening call on every path. (3) Blocking logic — agent must halt on match, not just log. (4) Testing with known sanctioned wallets. (5) Audit logging enabled from day one.
\ No newline at end of file
diff --git a/learn/ofac-screeening-for-payment-infrastructure/index.html b/learn/ofac-screeening-for-payment-infrastructure/index.html
new file mode 100644
index 0000000..7371df4
--- /dev/null
+++ b/learn/ofac-screeening-for-payment-infrastructure/index.html
@@ -0,0 +1 @@
+OFAC screening for payment infrastructure | Learn
OFAC screening for payment infrastructure
OFAC screening for payment infrastructure
Payment infrastructure screening covers the full transaction chain. Each intermediary (correspondent banks, payment processors, clearing houses) adds a compliance touchpoint. Infrastructure providers must screen at their point in the chain and may have obligations to ensure downstream screening as well.
\ No newline at end of file
diff --git a/learn/ofac-screening-for-agent-frameworks/index.html b/learn/ofac-screening-for-agent-frameworks/index.html
new file mode 100644
index 0000000..c0c3fa0
--- /dev/null
+++ b/learn/ofac-screening-for-agent-frameworks/index.html
@@ -0,0 +1 @@
+OFAC screening for AI agent frameworks | Learn
OFAC screening for AI agent frameworks
OFAC screening for AI agent frameworks
Framework integration: LangChain (add a sanctions_check tool to the agent's toolset), CrewAI (wrap payment tasks with a screening pre-check), AutoGen (register a screening function in the agent's function map), OpenAI Agents SDK (add screening as a guardrail before payment tool calls). SanctionsAI's MCP server works across all frameworks.
\ No newline at end of file
diff --git a/learn/ofac-screening-for-blockchain-companies/index.html b/learn/ofac-screening-for-blockchain-companies/index.html
new file mode 100644
index 0000000..29f90bb
--- /dev/null
+++ b/learn/ofac-screening-for-blockchain-companies/index.html
@@ -0,0 +1 @@
+OFAC screening for blockchain companies | Learn
OFAC screening for blockchain companies
OFAC screening for blockchain companies
Blockchain companies have OFAC exposure across layers: front-end operators (screen wallets before allowing interaction), wallet providers (screen deposits and withdrawals), protocol developers (may face liability if the protocol is designated), and enterprise blockchain services (screen all enterprise transactions).
\ No newline at end of file
diff --git a/learn/ofac-screening-for-payment-startups/index.html b/learn/ofac-screening-for-payment-startups/index.html
new file mode 100644
index 0000000..5926b75
--- /dev/null
+++ b/learn/ofac-screening-for-payment-startups/index.html
@@ -0,0 +1 @@
+OFAC screening for payment startups | Learn
OFAC screening for payment startups
OFAC screening for payment startups
Before your first transaction: (1) Choose a screening API (free tier is fine for testing). (2) Wire it into your payment function — before authorization. (3) Test with known sanctioned wallets. (4) Write a one-page compliance policy. (5) Enable logging. You can add sophistication later — start with these five.
\ No newline at end of file
diff --git a/learn/what-are-ofac-sanctions-for-crypto/index.html b/learn/what-are-ofac-sanctions-for-crypto/index.html
new file mode 100644
index 0000000..557195f
--- /dev/null
+++ b/learn/what-are-ofac-sanctions-for-crypto/index.html
@@ -0,0 +1 @@
+What are OFAC sanctions for crypto? | Learn
What are OFAC sanctions for crypto?
What are OFAC sanctions for crypto?
OFAC sanctions apply to cryptocurrency exactly as they apply to any other asset. Key applications: wallet addresses on the SDN list (947 and growing), exchange designations (SUEX, Chatex, Garantex), mixer sanctions (Tornado Cash, Blender.io), and DeFi protocol considerations (front-end liability, smart contract designations).
\ No newline at end of file
diff --git a/learn/what-are-ofac-sanctions-penalties-for-crypto/index.html b/learn/what-are-ofac-sanctions-penalties-for-crypto/index.html
new file mode 100644
index 0000000..6209cd5
--- /dev/null
+++ b/learn/what-are-ofac-sanctions-penalties-for-crypto/index.html
@@ -0,0 +1 @@
+OFAC sanctions penalties for crypto | Learn
\ No newline at end of file
diff --git a/learn/what-is-ofac-compliance-for-defi-developers/index.html b/learn/what-is-ofac-compliance-for-defi-developers/index.html
new file mode 100644
index 0000000..0814428
--- /dev/null
+++ b/learn/what-is-ofac-compliance-for-defi-developers/index.html
@@ -0,0 +1 @@
+OFAC compliance for DeFi developers | Learn
OFAC compliance for DeFi developers
OFAC compliance for DeFi developers
DeFi developers face OFAC through their front-end interfaces. The front-end is the access point — and the operator providing that access may have compliance obligations. Front-end wallet screening is the baseline; on-chain screening solutions are emerging for protocol-level compliance.
\ No newline at end of file
diff --git a/learn/what-is-ofac-compliance-for-developers/index.html b/learn/what-is-ofac-compliance-for-developers/index.html
new file mode 100644
index 0000000..7d1575a
--- /dev/null
+++ b/learn/what-is-ofac-compliance-for-developers/index.html
@@ -0,0 +1 @@
+OFAC compliance for developers | Learn
OFAC compliance for developers
OFAC compliance for developers
Developers building payment applications have OFAC obligations: if your code processes payments, it must screen counterparties. The screening call goes before the payment call. One API call, under 100ms, free tier available. Test with known sanctioned wallets before shipping.
\ No newline at end of file
diff --git a/learn/what-is-ofac-compliance-for-web3-startups/index.html b/learn/what-is-ofac-compliance-for-web3-startups/index.html
new file mode 100644
index 0000000..9b844d7
--- /dev/null
+++ b/learn/what-is-ofac-compliance-for-web3-startups/index.html
@@ -0,0 +1 @@
+OFAC compliance for Web3 startups | Learn
OFAC compliance for Web3 startups
OFAC compliance for Web3 startups
Web3 startup compliance: (1) Screen wallet addresses at every value transfer point (payments, airdrops, rewards). (2) Document your screening approach — a one-page policy. (3) Use a free/low-cost screening API. (4) Log everything. (5) Review monthly. You can start with SanctionsAI's free tier (5 checks/day) and scale with the $19/mo plan.
\ No newline at end of file
diff --git a/learn/what-is-ofac-risk-based-compliance/index.html b/learn/what-is-ofac-risk-based-compliance/index.html
new file mode 100644
index 0000000..fcc97a9
--- /dev/null
+++ b/learn/what-is-ofac-risk-based-compliance/index.html
@@ -0,0 +1 @@
+What is risk-based OFAC compliance? | Learn
What is risk-based OFAC compliance?
What is risk-based OFAC compliance?
Risk-based compliance means focusing resources where risk is highest. Crypto payments > fiat payments. Cross-border > domestic. New counterparties > established relationships. High-value > low-value. OFAC expects this calibration — a program that treats all transactions identically may miss high-risk patterns.
\ No newline at end of file
diff --git a/learn/what-is-ofac-sanctions-compliance-monitoring/index.html b/learn/what-is-ofac-sanctions-compliance-monitoring/index.html
new file mode 100644
index 0000000..e4d8f69
--- /dev/null
+++ b/learn/what-is-ofac-sanctions-compliance-monitoring/index.html
@@ -0,0 +1 @@
+OFAC sanctions compliance monitoring | Learn
OFAC sanctions compliance monitoring
OFAC sanctions compliance monitoring
Compliance monitoring includes: weekly screening log reviews (patterns, gaps), periodic testing with known sanctioned wallets (confirm blocking works), real-time alerts on matches, and annual independent audits. Monitoring proves your program is operational — not just documented.
\ No newline at end of file
diff --git a/learn/what-is-ofac-sanctions-compliance-training/index.html b/learn/what-is-ofac-sanctions-compliance-training/index.html
new file mode 100644
index 0000000..1a09a97
--- /dev/null
+++ b/learn/what-is-ofac-sanctions-compliance-training/index.html
@@ -0,0 +1 @@
+What is OFAC sanctions compliance training? | Learn
What is OFAC sanctions compliance training?
What is OFAC sanctions compliance training?
Compliance training educates employees on sanctions regulations and procedures. Minimum content: what sanctions are, which lists exist, how screening works in your organization, how to recognize and report potential matches, and the consequences of violations. Conduct annually and document attendance.
\ No newline at end of file
diff --git a/learn/what-is-ofac-sanctions-screening-explained/index.html b/learn/what-is-ofac-sanctions-screening-explained/index.html
new file mode 100644
index 0000000..d26a8e0
--- /dev/null
+++ b/learn/what-is-ofac-sanctions-screening-explained/index.html
@@ -0,0 +1 @@
+OFAC sanctions screening explained | Learn
OFAC sanctions screening explained
OFAC sanctions screening explained
OFAC sanctions screening is the practice of checking who you're doing business with against a government list of prohibited parties. It's required by law for US persons. In practice, it's one API call before every payment — fast, automated, and inexpensive. The alternative (not screening) exposes you to penalties up to $330,944 per violation.
\ No newline at end of file
diff --git a/penalties/blender-io/index.html b/penalties/blender-io/index.html
new file mode 100644
index 0000000..fca9429
--- /dev/null
+++ b/penalties/blender-io/index.html
@@ -0,0 +1 @@
+Blender.io OFAC mixer designation | Penalties
Blender.io OFAC mixer designation
Blender.io OFAC mixer designation
Blender.io was designated in May 2022 — the first mixer designation, predating Tornado Cash by three months. OFAC alleged Blender laundered over $20 million from North Korea's Lazarus Group, including proceeds from the Axie Infinity/Ronin Bridge hack. The designation established that mixers are in scope for OFAC sanctions.
\ No newline at end of file
diff --git a/penalties/bybit/index.html b/penalties/bybit/index.html
new file mode 100644
index 0000000..d1e0ffb
--- /dev/null
+++ b/penalties/bybit/index.html
@@ -0,0 +1 @@
+Bybit OFAC compliance profile | Penalties
Bybit OFAC compliance profile
Bybit OFAC compliance profile
Bybit serves a global user base and processes significant derivatives and spot trading volume. Non-US exchanges still face OFAC risk through USD clearing, US person customers, and secondary sanctions exposure. Screening at onboarding and transaction level is the baseline defense.
\ No newline at end of file
diff --git a/penalties/crypto-com/index.html b/penalties/crypto-com/index.html
new file mode 100644
index 0000000..8646e24
--- /dev/null
+++ b/penalties/crypto-com/index.html
@@ -0,0 +1 @@
+Crypto.com OFAC penalties | Penalties
Crypto.com OFAC penalties
Crypto.com OFAC penalties
Crypto.com operates in multiple jurisdictions and processes significant crypto transaction volume. Like all major exchanges, it faces OFAC compliance obligations: customer screening, transaction monitoring, and sanctions list compliance. See also: Binance OFAC penalty.
\ No newline at end of file
diff --git a/penalties/garantex-sanctions/index.html b/penalties/garantex-sanctions/index.html
new file mode 100644
index 0000000..3ea264b
--- /dev/null
+++ b/penalties/garantex-sanctions/index.html
@@ -0,0 +1 @@
+Garantex OFAC sanctions designation | Penalties
Garantex OFAC sanctions designation
Garantex OFAC sanctions designation
Garantex was designated by OFAC in April 2022 under EO 14024 for operating in Russia's financial services sector and facilitating illicit finance. It remains active but designated — US persons are prohibited from transacting with it. The designation is notable because Garantex continues to operate, illustrating the limits of unilateral sanctions.
\ No newline at end of file
diff --git a/penalties/hydra-market/index.html b/penalties/hydra-market/index.html
new file mode 100644
index 0000000..23b6238
--- /dev/null
+++ b/penalties/hydra-market/index.html
@@ -0,0 +1 @@
+Hydra Market OFAC sanctions | Penalties
Hydra Market OFAC sanctions
Hydra Market OFAC sanctions
Hydra Market was designated alongside Garantex in April 2022. The coordinated action targeted both the marketplace (Hydra) and its financial infrastructure (Garantex). German authorities seized Hydra's servers the same day — a rare example of simultaneous designation and law enforcement action.
\ No newline at end of file
diff --git a/penalties/kucoin/index.html b/penalties/kucoin/index.html
new file mode 100644
index 0000000..11d29b0
--- /dev/null
+++ b/penalties/kucoin/index.html
@@ -0,0 +1 @@
+KuCoin OFAC settlement and compliance | Penalties
KuCoin OFAC settlement and compliance
KuCoin OFAC settlement and compliance
KuCoin settled with US authorities in 2024 over AML and sanctions compliance failures. The case underscored that non-US exchanges serving US customers face full OFAC exposure. Lesson: geographic claims of not serving the US are not a defense if US customers are actually on the platform.
\ No newline at end of file
diff --git a/penalties/ofac-non-crypto-penalties/index.html b/penalties/ofac-non-crypto-penalties/index.html
new file mode 100644
index 0000000..f4d6a55
--- /dev/null
+++ b/penalties/ofac-non-crypto-penalties/index.html
@@ -0,0 +1 @@
+Non-crypto OFAC penalties — traditional finance | Penalties
Non-crypto OFAC penalties — traditional finance
Non-crypto OFAC penalties — traditional finance
Non-crypto OFAC penalties provide context for crypto enforcement. Notable cases: Standard Chartered ($657M for Iran sanctions), BNP Paribas ($8.9B — the largest OFAC penalty in history), Societe Generale ($1.3B), UniCredit ($1.3B). Crypto enforcement ($1.4B total) is significant but still a fraction of traditional finance penalties.
\ No newline at end of file
diff --git a/penalties/okx/index.html b/penalties/okx/index.html
new file mode 100644
index 0000000..d3eb753
--- /dev/null
+++ b/penalties/okx/index.html
@@ -0,0 +1 @@
+OKX OFAC compliance and penalties | Penalties
OKX OFAC compliance and penalties
OKX OFAC compliance and penalties
OKX, as a major global exchange, operates in a complex sanctions landscape. While headquartered outside the US, its exposure to OFAC arises through US dollar transactions, US customers, and correspondent banking relationships. Exchange-level sanctions screening is the primary defense.
\ No newline at end of file
diff --git a/penalties/sinbad-mixer/index.html b/penalties/sinbad-mixer/index.html
new file mode 100644
index 0000000..2c7d37d
--- /dev/null
+++ b/penalties/sinbad-mixer/index.html
@@ -0,0 +1 @@
+Sinbad.io mixer OFAC designation | Penalties
Sinbad.io mixer OFAC designation
Sinbad.io mixer OFAC designation
Sinbad.io was designated in November 2023 — OFAC alleged it was the rebranded successor to Blender.io, launched after Blender's designation. This established an important precedent: OFAC will pursue successor entities that attempt to evade designation through rebranding. The mixer had processed millions in Lazarus Group-linked funds.