\ No newline at end of file
diff --git a/faq/does-ofac-apply-to-defi-yield-farming/index.html b/faq/does-ofac-apply-to-defi-yield-farming/index.html
new file mode 100644
index 0000000..e2a4efd
--- /dev/null
+++ b/faq/does-ofac-apply-to-defi-yield-farming/index.html
@@ -0,0 +1 @@
+OFAC and DeFi yield farming
OFAC and DeFi yield farming
OFAC and DeFi yield farming
DeFi yield farming generates rewards distributed to liquidity provider wallets. Those distributions are value transfers subject to OFAC. A protocol paying yield to a sanctioned wallet is distributing value to an SDN.
\ No newline at end of file
diff --git a/faq/how-to-audit-crypto-transactions/index.html b/faq/how-to-audit-crypto-transactions/index.html
new file mode 100644
index 0000000..0705497
--- /dev/null
+++ b/faq/how-to-audit-crypto-transactions/index.html
@@ -0,0 +1 @@
+Audit crypto transactions for OFAC
Audit crypto transactions for OFAC
Audit crypto transactions for OFAC
Audit crypto transactions: (1) Export screening logs for the audit period. (2) Verify 100% of transactions were screened. (3) Test with known sanctioned wallets — does blocking work? (4) Check SDN list sync currency. (5) Document findings.
\ No newline at end of file
diff --git a/faq/how-to-screen-defi-transactions/index.html b/faq/how-to-screen-defi-transactions/index.html
new file mode 100644
index 0000000..f8e3404
--- /dev/null
+++ b/faq/how-to-screen-defi-transactions/index.html
@@ -0,0 +1 @@
+Screen DeFi transactions for OFAC
Screen DeFi transactions for OFAC
Screen DeFi transactions for OFAC
Screen DeFi transactions by adding wallet screening at the front-end layer — before users interact with smart contracts. The pattern: connect wallet → screen address → if clean, allow interaction; if match, block.
\ No newline at end of file
diff --git a/faq/ofac-compliance-for-payment-startups-explained/index.html b/faq/ofac-compliance-for-payment-startups-explained/index.html
new file mode 100644
index 0000000..4547ffc
--- /dev/null
+++ b/faq/ofac-compliance-for-payment-startups-explained/index.html
@@ -0,0 +1 @@
+OFAC compliance for payment startups
OFAC compliance for payment startups
OFAC compliance for payment startups
Payment startups min viable compliance: free screening API, one-page written policy, and audit logging. That's it for year one. Add sophistication as you grow.
\ No newline at end of file
diff --git a/faq/ofac-compliance-for-small-business/index.html b/faq/ofac-compliance-for-small-business/index.html
new file mode 100644
index 0000000..0bea58e
--- /dev/null
+++ b/faq/ofac-compliance-for-small-business/index.html
@@ -0,0 +1 @@
+OFAC compliance for small business
OFAC compliance for small business
OFAC compliance for small business
Small business OFAC compliance is achievable: use a free screening API, write a one-page policy, train your team (15-minute session), and keep screening records. The cost is negligible compared to the penalty risk.
\ No newline at end of file
diff --git a/faq/ofac-enforcement-trends-2026/index.html b/faq/ofac-enforcement-trends-2026/index.html
new file mode 100644
index 0000000..080951d
--- /dev/null
+++ b/faq/ofac-enforcement-trends-2026/index.html
@@ -0,0 +1 @@
+OFAC enforcement trends 2026
OFAC enforcement trends 2026
OFAC enforcement trends 2026
2026 trends: (1) Crypto enforcement continues at elevated pace. (2) AI agent payments emerging as a distinct enforcement category. (3) Technology-enabled sanctions evasion (mixers, privacy chains, cross-chain routing) draws enforcement attention. (4) Russia sanctions enforcement remains high priority.
\ No newline at end of file
diff --git a/faq/ofac-screening-accuracy-requirements/index.html b/faq/ofac-screening-accuracy-requirements/index.html
new file mode 100644
index 0000000..32e9fa6
--- /dev/null
+++ b/faq/ofac-screening-accuracy-requirements/index.html
@@ -0,0 +1 @@
+OFAC screening accuracy requirements
OFAC screening accuracy requirements
OFAC screening accuracy requirements
No regulatory accuracy threshold exists, but false negatives — screening saying 'clean' for an actual SDN — are a compliance failure. False positives (flagging clean counterparties) are an operational cost, not a compliance failure.
\ No newline at end of file
diff --git a/faq/ofac-screening-for-b2b-payments/index.html b/faq/ofac-screening-for-b2b-payments/index.html
new file mode 100644
index 0000000..5d7aa67
--- /dev/null
+++ b/faq/ofac-screening-for-b2b-payments/index.html
@@ -0,0 +1 @@
+OFAC screening for B2B payments
OFAC screening for B2B payments
OFAC screening for B2B payments
B2B payments have unique OFAC risks: international counterparties may be in sanctioned jurisdictions, high transaction values amplify penalty exposure, and correspondent banking chains introduce intermediary risk.
\ No newline at end of file
diff --git a/faq/ofac-screening-for-blockchain-gaming/index.html b/faq/ofac-screening-for-blockchain-gaming/index.html
new file mode 100644
index 0000000..03d2a2d
--- /dev/null
+++ b/faq/ofac-screening-for-blockchain-gaming/index.html
@@ -0,0 +1 @@
+OFAC screening for blockchain gaming
OFAC screening for blockchain gaming
OFAC screening for blockchain gaming
Blockchain gaming creates real financial value: play-to-earn rewards, tradeable items, NFT economies. Every value transfer to a player wallet must be screened for OFAC.
\ No newline at end of file
diff --git a/faq/ofac-screening-for-high-risk-jurisdictions/index.html b/faq/ofac-screening-for-high-risk-jurisdictions/index.html
new file mode 100644
index 0000000..63860dc
--- /dev/null
+++ b/faq/ofac-screening-for-high-risk-jurisdictions/index.html
@@ -0,0 +1 @@
+Screening for high-risk jurisdictions
Screening for high-risk jurisdictions
Screening for high-risk jurisdictions
High-risk jurisdictions require enhanced screening: wallet + name + country checks on every transaction, real-time (not batch) screening, and additional due diligence for counterparties in comprehensively sanctioned or high-risk countries.
\ No newline at end of file
diff --git a/faq/ofac-screening-for-marketplace-payments/index.html b/faq/ofac-screening-for-marketplace-payments/index.html
new file mode 100644
index 0000000..ec5b5ae
--- /dev/null
+++ b/faq/ofac-screening-for-marketplace-payments/index.html
@@ -0,0 +1 @@
+OFAC screening for marketplace payments
OFAC screening for marketplace payments
OFAC screening for marketplace payments
Marketplace screening: every transaction has two counterparties — buyer and seller. Both must be screened. The marketplace is the intermediary facilitating the exchange and can be liable if either party is sanctioned.
\ No newline at end of file
diff --git a/faq/ofac-screening-for-metaverse/index.html b/faq/ofac-screening-for-metaverse/index.html
new file mode 100644
index 0000000..3cad77f
--- /dev/null
+++ b/faq/ofac-screening-for-metaverse/index.html
@@ -0,0 +1 @@
+OFAC screening for metaverse platforms
OFAC screening for metaverse platforms
OFAC screening for metaverse platforms
Metaverse economies with real-world value — virtual land, avatar items, service payments — are within OFAC's scope. Any transfer of value, even in a virtual world, is a potential sanctions event.
\ No newline at end of file
diff --git a/faq/ofac-screening-for-nft-gaming/index.html b/faq/ofac-screening-for-nft-gaming/index.html
new file mode 100644
index 0000000..b3cb0f4
--- /dev/null
+++ b/faq/ofac-screening-for-nft-gaming/index.html
@@ -0,0 +1 @@
+OFAC screening for NFT gaming
OFAC screening for NFT gaming
OFAC screening for NFT gaming
NFT gaming: the gaming element doesn't exempt the financial element. Trading, selling, or transferring gaming NFTs to sanctioned wallets is a prohibited transaction.
\ No newline at end of file
diff --git a/faq/ofac-screening-for-payment-facilitators/index.html b/faq/ofac-screening-for-payment-facilitators/index.html
new file mode 100644
index 0000000..4c638f2
--- /dev/null
+++ b/faq/ofac-screening-for-payment-facilitators/index.html
@@ -0,0 +1 @@
+OFAC screening for payment facilitators
OFAC screening for payment facilitators
OFAC screening for payment facilitators
Payment facilitators aggregate multiple merchants under a master account. Every merchant must be screened at onboarding, and every transaction must be screened at processing. The facilitator is the compliance chokepoint for its merchant portfolio.
\ No newline at end of file
diff --git a/faq/ofac-screening-for-sanctioned-countries/index.html b/faq/ofac-screening-for-sanctioned-countries/index.html
new file mode 100644
index 0000000..c991ec9
--- /dev/null
+++ b/faq/ofac-screening-for-sanctioned-countries/index.html
@@ -0,0 +1 @@
+Screening for comprehensively sanctioned countries
Screening for comprehensively sanctioned countries
Screening for comprehensively sanctioned countries
Comprehensively sanctioned countries: Cuba, Iran, North Korea, Syria, and Crimea/occupied Ukraine. Virtually all transactions are prohibited unless specifically licensed. Screening must catch jurisdiction-level restrictions, not just individual SDN matches.
\ No newline at end of file
diff --git a/faq/ofac-screening-for-subscription-payments/index.html b/faq/ofac-screening-for-subscription-payments/index.html
new file mode 100644
index 0000000..0161ecf
--- /dev/null
+++ b/faq/ofac-screening-for-subscription-payments/index.html
@@ -0,0 +1 @@
+OFAC screening for subscription payments
OFAC screening for subscription payments
OFAC screening for subscription payments
Subscription screening: (1) Screen at signup. (2) Re-screen periodically (monthly at minimum) because SDN status can change. (3) Screen the payment method itself — crypto wallet addresses, bank accounts. One-time screening at onboarding is insufficient.
\ No newline at end of file
diff --git a/faq/ofac-screening-frequency-requirements/index.html b/faq/ofac-screening-frequency-requirements/index.html
new file mode 100644
index 0000000..d641509
--- /dev/null
+++ b/faq/ofac-screening-frequency-requirements/index.html
@@ -0,0 +1 @@
+OFAC screening frequency requirements
OFAC screening frequency requirements
OFAC screening frequency requirements
OFAC expects 100% screening coverage, not sampling. Every transaction must be screened at the time of processing. Sampling or periodic screening creates compliance gaps that OFAC considers a program deficiency.
\ No newline at end of file
diff --git a/faq/what-is-ofac-compliance-risk/index.html b/faq/what-is-ofac-compliance-risk/index.html
new file mode 100644
index 0000000..ecad127
--- /dev/null
+++ b/faq/what-is-ofac-compliance-risk/index.html
@@ -0,0 +1 @@
+What is OFAC compliance risk
What is OFAC compliance risk
What is OFAC compliance risk
OFAC compliance risk = probability of violation × penalty severity. Mitigation: screening every transaction (reduces probability), having a documented compliance program (reduces penalty severity if a violation occurs).
\ No newline at end of file
diff --git a/glossary/ofac-blocking-obligation/index.html b/glossary/ofac-blocking-obligation/index.html
new file mode 100644
index 0000000..08bbbc4
--- /dev/null
+++ b/glossary/ofac-blocking-obligation/index.html
@@ -0,0 +1 @@
+OFAC Blocking Obligation
OFAC Blocking Obligation
OFAC Blocking Obligation
When funds are in motion and a sanctions match is identified, the transaction must be blocked — not rejected, not returned, but frozen. The blocking party must file a report with OFAC within 10 business days.
\ No newline at end of file
diff --git a/glossary/ofac-compliance-enforcement-response/index.html b/glossary/ofac-compliance-enforcement-response/index.html
new file mode 100644
index 0000000..353c7f6
--- /dev/null
+++ b/glossary/ofac-compliance-enforcement-response/index.html
@@ -0,0 +1 @@
+OFAC Compliance Enforcement Response
OFAC Compliance Enforcement Response
OFAC Compliance Enforcement Response
Enforcement response: (1) Acknowledge and cooperate — fighting OFAC rarely succeeds. (2) Conduct internal investigation — understand what happened. (3) Remediate — fix the compliance gap. (4) Negotiate settlement — most cases settle. (5) Document lessons learned.
\ No newline at end of file
diff --git a/glossary/ofac-compliance-metrics/index.html b/glossary/ofac-compliance-metrics/index.html
new file mode 100644
index 0000000..6a3568f
--- /dev/null
+++ b/glossary/ofac-compliance-metrics/index.html
@@ -0,0 +1 @@
+OFAC Compliance Metrics
OFAC Compliance Metrics
OFAC Compliance Metrics
Compliance metrics: (1) Screening coverage — % of transactions screened (target 100%). (2) Match rate — % of screens returning matches. (3) Response time — ms per screening call (target <100ms). (4) Alert disposition time — time to investigate and resolve a match alert.
\ No newline at end of file
diff --git a/glossary/ofac-compliance-obligation/index.html b/glossary/ofac-compliance-obligation/index.html
new file mode 100644
index 0000000..4f9e402
--- /dev/null
+++ b/glossary/ofac-compliance-obligation/index.html
@@ -0,0 +1 @@
+OFAC Compliance Obligation
OFAC Compliance Obligation
OFAC Compliance Obligation
The compliance obligation encompasses: screening every transaction, blocking on matches, reporting blocked property, maintaining records for 5+ years, exercising due diligence on counterparties, and implementing a risk-based compliance program.
\ No newline at end of file
diff --git a/glossary/ofac-compliance-program-elements/index.html b/glossary/ofac-compliance-program-elements/index.html
new file mode 100644
index 0000000..e0b17a9
--- /dev/null
+++ b/glossary/ofac-compliance-program-elements/index.html
@@ -0,0 +1 @@
+OFAC Compliance Program Elements
OFAC Compliance Program Elements
OFAC Compliance Program Elements
Five pillars: (1) Management commitment — leadership supports and resources the program. (2) Risk assessment — sanctions risks identified and documented. (3) Internal controls — screening, policies, procedures. (4) Testing/audit — controls verified to work. (5) Training — staff educated on sanctions.
\ No newline at end of file
diff --git a/glossary/ofac-compliance-risk-assessment/index.html b/glossary/ofac-compliance-risk-assessment/index.html
new file mode 100644
index 0000000..5ccccfe
--- /dev/null
+++ b/glossary/ofac-compliance-risk-assessment/index.html
@@ -0,0 +1 @@
+OFAC Compliance Risk Assessment
OFAC Compliance Risk Assessment
OFAC Compliance Risk Assessment
The risk assessment evaluates: (1) Customer risk — who you transact with. (2) Geographic risk — where counterparties are located. (3) Product risk — what you're selling/buying. (4) Channel risk — how transactions occur (including agent/automated).
\ No newline at end of file
diff --git a/glossary/ofac-reporting-obligation/index.html b/glossary/ofac-reporting-obligation/index.html
new file mode 100644
index 0000000..d08afe6
--- /dev/null
+++ b/glossary/ofac-reporting-obligation/index.html
@@ -0,0 +1 @@
+OFAC Reporting Obligation
OFAC Reporting Obligation
OFAC Reporting Obligation
Reporting obligations: (1) Initial blocked property report — within 10 business days of blocking. (2) Annual report of blocked property — by September 30 each year. (3) Rejected transaction reports — when transactions are refused due to sanctions matches.
\ No newline at end of file
diff --git a/glossary/ofac-risk-management-framework/index.html b/glossary/ofac-risk-management-framework/index.html
new file mode 100644
index 0000000..7ce22df
--- /dev/null
+++ b/glossary/ofac-risk-management-framework/index.html
@@ -0,0 +1 @@
+OFAC Risk Management Framework
OFAC Risk Management Framework
OFAC Risk Management Framework
Risk management framework: (1) Identify — where could sanctions violations occur? (2) Assess — how likely and how severe? (3) Mitigate — implement controls (screening, policies, training). (4) Monitor — verify controls work continuously. (5) Report — communicate risk status to stakeholders.
\ No newline at end of file
diff --git a/glossary/ofac-sanctions-compliance-standard/index.html b/glossary/ofac-sanctions-compliance-standard/index.html
new file mode 100644
index 0000000..bdc0879
--- /dev/null
+++ b/glossary/ofac-sanctions-compliance-standard/index.html
@@ -0,0 +1 @@
+OFAC Sanctions Compliance Standard
OFAC Sanctions Compliance Standard
OFAC Sanctions Compliance Standard
The compliance standard: (1) 100% transaction screening coverage. (2) SDN list synced at least daily (hourly best practice). (3) Documented compliance program (written policy, procedures, training records). (4) Independent testing at least annually. (5) Audit trail retained 5+ years.
\ No newline at end of file
diff --git a/glossary/ofac-sanctions-screening-obligation/index.html b/glossary/ofac-sanctions-screening-obligation/index.html
new file mode 100644
index 0000000..8c06088
--- /dev/null
+++ b/glossary/ofac-sanctions-screening-obligation/index.html
@@ -0,0 +1 @@
+OFAC Sanctions Screening Obligation
OFAC Sanctions Screening Obligation
OFAC Sanctions Screening Obligation
The screening obligation: US persons must not transact with SDNs. The only way to know if a counterparty is an SDN is to check — hence the screening obligation. It's a legal requirement, not a best practice.
\ No newline at end of file
diff --git a/glossary/ofac-screening-compliance-review/index.html b/glossary/ofac-screening-compliance-review/index.html
new file mode 100644
index 0000000..8821e0d
--- /dev/null
+++ b/glossary/ofac-screening-compliance-review/index.html
@@ -0,0 +1 @@
+OFAC Compliance Review
OFAC Compliance Review
OFAC Compliance Review
Compliance reviews evaluate program effectiveness: are controls working? Are there gaps? Are screening logs complete? Are matches handled correctly? Reviews should be conducted at least annually, with documented findings and remediation plans.
\ No newline at end of file
diff --git a/glossary/ofac-screening-due-diligence/index.html b/glossary/ofac-screening-due-diligence/index.html
new file mode 100644
index 0000000..7caf523
--- /dev/null
+++ b/glossary/ofac-screening-due-diligence/index.html
@@ -0,0 +1 @@
+OFAC Screening Due Diligence
OFAC Screening Due Diligence
OFAC Screening Due Diligence
Due diligence on screening alerts: a potential match cannot be dismissed without investigation. Compare counterparty details against the SDN entry. If clearly different, document the distinction. If uncertain, escalate. Blanket dismissal of all alerts is a compliance failure.
\ No newline at end of file
diff --git a/glossary/ofac-screening-for-agent-commerce/index.html b/glossary/ofac-screening-for-agent-commerce/index.html
new file mode 100644
index 0000000..75d67e2
--- /dev/null
+++ b/glossary/ofac-screening-for-agent-commerce/index.html
@@ -0,0 +1 @@
+OFAC Agent Commerce Screening
OFAC Agent Commerce Screening
OFAC Agent Commerce Screening
Agent commerce screening addresses the unique challenge of AI agents transacting autonomously. Key requirements: pre-transaction screening gates, per-agent transaction limits, real-time blocking on matches, and agent-specific audit trails.
\ No newline at end of file
diff --git a/glossary/ofac-screening-integration-testing/index.html b/glossary/ofac-screening-integration-testing/index.html
new file mode 100644
index 0000000..fb7c9c1
--- /dev/null
+++ b/glossary/ofac-screening-integration-testing/index.html
@@ -0,0 +1 @@
+OFAC Screening Integration Testing
OFAC Screening Integration Testing
OFAC Screening Integration Testing
Integration testing: (1) Test with known SDN wallet (Tornado Cash: 0x098B...). (2) Verify response is clean: false. (3) Test that payment function blocks on match. (4) Test that clean wallets still process. (5) Test error handling (API down = block).
\ No newline at end of file
diff --git a/glossary/ofac-screening-recordkeeping/index.html b/glossary/ofac-screening-recordkeeping/index.html
new file mode 100644
index 0000000..f45a7ad
--- /dev/null
+++ b/glossary/ofac-screening-recordkeeping/index.html
@@ -0,0 +1 @@
+OFAC Screening Recordkeeping
OFAC Screening Recordkeeping
OFAC Screening Recordkeeping
Recordkeeping: screening logs must be retained for at least 5 years. Each log entry should include: date, counterparty identifier, screening inputs, screening result, disposition, and the identity of the screener (person or agent).
\ No newline at end of file
diff --git a/learn/how-to-implement-ofac-compliance-program/index.html b/learn/how-to-implement-ofac-compliance-program/index.html
new file mode 100644
index 0000000..47e0411
--- /dev/null
+++ b/learn/how-to-implement-ofac-compliance-program/index.html
@@ -0,0 +1 @@
+How to implement an OFAC compliance program
How to implement an OFAC compliance program
How to implement an OFAC compliance program
Implementation steps: (1) Write a one-page compliance policy — who is responsible, what tools you use. (2) Conduct a risk assessment — where is your sanctions exposure? (3) Implement controls — integrate screening API, configure blocking. (4) Train your team — 15-minute annual session. (5) Test — known sanctioned wallets. (6) Maintain — review quarterly.
\ No newline at end of file
diff --git a/learn/how-to-understand-ofac-sanctions/index.html b/learn/how-to-understand-ofac-sanctions/index.html
new file mode 100644
index 0000000..449496e
--- /dev/null
+++ b/learn/how-to-understand-ofac-sanctions/index.html
@@ -0,0 +1 @@
+How to understand OFAC sanctions
How to understand OFAC sanctions
How to understand OFAC sanctions
OFAC sanctions in plain language: the US government maintains a list of people, companies, and countries you can't do business with. Before every transaction, you check the list. If the counterparty is on it, you stop. If not, you proceed. That's the core of it.
\ No newline at end of file
diff --git a/learn/ofac-compliance-checklist-for-developers/index.html b/learn/ofac-compliance-checklist-for-developers/index.html
new file mode 100644
index 0000000..66a9742
--- /dev/null
+++ b/learn/ofac-compliance-checklist-for-developers/index.html
@@ -0,0 +1 @@
+OFAC compliance checklist for developers
OFAC compliance checklist for developers
OFAC compliance checklist for developers
Developer checklist: □ Screening in every payment path □ Known sanctioned wallet tests pass □ Payment blocks on match □ Payment blocks on screening error □ All screens logged with timestamp □ API keys in env vars, not code □ SDN list sync verified hourly □ Code reviewed for bypass paths □ Monitoring alerts configured.
\ No newline at end of file
diff --git a/learn/ofac-compliance-common-mistakes/index.html b/learn/ofac-compliance-common-mistakes/index.html
new file mode 100644
index 0000000..cf47ab9
--- /dev/null
+++ b/learn/ofac-compliance-common-mistakes/index.html
@@ -0,0 +1 @@
+Common OFAC compliance mistakes
Common OFAC compliance mistakes
Common OFAC compliance mistakes
Common mistakes: (1) Not screening all payment channels — agent payments, crypto transfers often missed. (2) Outdated SDN list — weekly sync creates days of exposure. (3) Failing open on errors — allowing transactions when screening is unavailable. (4) No written policy — undocumented program = no program. (5) Not testing — assuming screening works without verifying.
\ No newline at end of file
diff --git a/learn/ofac-compliance-cost-breakdown/index.html b/learn/ofac-compliance-cost-breakdown/index.html
new file mode 100644
index 0000000..91f680d
--- /dev/null
+++ b/learn/ofac-compliance-cost-breakdown/index.html
@@ -0,0 +1 @@
+OFAC compliance cost breakdown
OFAC compliance cost breakdown
OFAC compliance cost breakdown
Cost breakdown: (1) Screening API — $0-$99/month (SanctionsAI free to Pro). (2) Implementation — 1-3 days of developer time. (3) Training — 15-30 minutes per employee annually. (4) Auditing — $0 (self-review) to $10K+ (independent audit). (5) Cost of non-compliance — $330,944 minimum per violation.
\ No newline at end of file
diff --git a/learn/ofac-compliance-for-early-stage-startups/index.html b/learn/ofac-compliance-for-early-stage-startups/index.html
new file mode 100644
index 0000000..3d9a22a
--- /dev/null
+++ b/learn/ofac-compliance-for-early-stage-startups/index.html
@@ -0,0 +1 @@
+OFAC compliance for early-stage startups
OFAC compliance for early-stage startups
OFAC compliance for early-stage startups
Early-stage startup compliance: (1) Free screening API — SanctionsAI free tier (5 checks/day). (2) One-page written policy — who's responsible, what tool you use, what happens on match. (3) Basic logging — record screening results. That covers the minimum. Add more as you grow.
\ No newline at end of file
diff --git a/learn/ofac-compliance-for-solo-developers/index.html b/learn/ofac-compliance-for-solo-developers/index.html
new file mode 100644
index 0000000..2c2466a
--- /dev/null
+++ b/learn/ofac-compliance-for-solo-developers/index.html
@@ -0,0 +1 @@
+OFAC compliance for solo developers
OFAC compliance for solo developers
OFAC compliance for solo developers
Solo developers: you're the compliance officer, the developer, and the operations team. One API call is all you need. SanctionsAI free tier covers 5 checks/day for testing. Dev plan ($19/mo) for production. Write a one-page policy. That's it.
\ No newline at end of file
diff --git a/learn/ofac-compliance-program-components/index.html b/learn/ofac-compliance-program-components/index.html
new file mode 100644
index 0000000..1c03939
--- /dev/null
+++ b/learn/ofac-compliance-program-components/index.html
@@ -0,0 +1 @@
+Components of an OFAC compliance program
Components of an OFAC compliance program
Components of an OFAC compliance program
Program components: (1) Written policy — who, what, when, how. (2) Risk assessment — where is your exposure? (3) Screening procedures — operational step-by-step. (4) Training — who, when, what content. (5) Testing — do controls work? (6) Documentation — keep records of everything.
\ No newline at end of file
diff --git a/learn/ofac-enforcement-case-studies/index.html b/learn/ofac-enforcement-case-studies/index.html
new file mode 100644
index 0000000..1a0e99d
--- /dev/null
+++ b/learn/ofac-enforcement-case-studies/index.html
@@ -0,0 +1 @@
+OFAC enforcement case studies
OFAC enforcement case studies
OFAC enforcement case studies
Case studies: Binance ($968M — inadequate screening for US customers and sanctioned jurisdictions), Tornado Cash (protocol designation — DeFi is not exempt), BitPay ($507K — processed payments from sanctioned jurisdictions despite having screening), BitGo ($98K — similar facts, lower penalty due to cooperation).
\ No newline at end of file
diff --git a/learn/ofac-sanctions-for-beginners/index.html b/learn/ofac-sanctions-for-beginners/index.html
new file mode 100644
index 0000000..bfeeef8
--- /dev/null
+++ b/learn/ofac-sanctions-for-beginners/index.html
@@ -0,0 +1 @@
+OFAC sanctions for beginners
OFAC sanctions for beginners
OFAC sanctions for beginners
Beginner's guide: OFAC is the US Treasury office that enforces economic sanctions. Sanctions prohibit US persons from doing business with certain people, companies, and countries. If you process payments, you need to check who you're paying against OFAC's list. It's free to start (SanctionsAI free tier: 5 checks/day).
\ No newline at end of file
diff --git a/learn/ofac-sanctions-overview/index.html b/learn/ofac-sanctions-overview/index.html
new file mode 100644
index 0000000..b6da499
--- /dev/null
+++ b/learn/ofac-sanctions-overview/index.html
@@ -0,0 +1 @@
+OFAC sanctions: Complete overview
OFAC sanctions: Complete overview
OFAC sanctions: Complete overview
OFAC sanctions represent the US government's primary economic pressure tool. This overview covers: the legal framework (IEEPA, TWEA, various Executive Orders), the sanctions programs (30+ country and thematic programs), compliance obligations (screening, blocking, reporting), and enforcement (civil penalties, criminal referrals).
\ No newline at end of file
diff --git a/learn/ofac-screening-api-integration-patterns/index.html b/learn/ofac-screening-api-integration-patterns/index.html
new file mode 100644
index 0000000..85834f8
--- /dev/null
+++ b/learn/ofac-screening-api-integration-patterns/index.html
@@ -0,0 +1 @@
+OFAC screening API integration patterns
OFAC screening API integration patterns
OFAC screening API integration patterns
Integration patterns: (1) Direct call — screening API called inline before payment. (2) Middleware — HTTP interceptor screens all payment requests. (3) MCP tool — agent calls sanctions_check as a tool. (4) Event-driven — payment events trigger async screening. (5) Sidecar — dedicated screening service alongside payment service.
\ No newline at end of file
diff --git a/learn/ofac-screening-monitoring-setup/index.html b/learn/ofac-screening-monitoring-setup/index.html
new file mode 100644
index 0000000..3d430ea
--- /dev/null
+++ b/learn/ofac-screening-monitoring-setup/index.html
@@ -0,0 +1 @@
+OFAC screening monitoring setup
OFAC screening monitoring setup
OFAC screening monitoring setup
Monitoring setup: (1) Coverage dashboard — % of transactions screened, by payment channel. (2) Match alerts — real-time notification on sanctions match. (3) Error alerts — notification when screening API fails. (4) Latency tracking — screening response time over time. (5) Weekly report — automated summary of screening activity.
\ No newline at end of file
diff --git a/learn/ofac-screening-technology-overview/index.html b/learn/ofac-screening-technology-overview/index.html
new file mode 100644
index 0000000..daab17c
--- /dev/null
+++ b/learn/ofac-screening-technology-overview/index.html
@@ -0,0 +1 @@
+OFAC screening technology overview
\ No newline at end of file
diff --git a/learn/what-is-the-purpose-of-ofac-sanctions/index.html b/learn/what-is-the-purpose-of-ofac-sanctions/index.html
new file mode 100644
index 0000000..499622a
--- /dev/null
+++ b/learn/what-is-the-purpose-of-ofac-sanctions/index.html
@@ -0,0 +1 @@
+What is the purpose of OFAC sanctions?
What is the purpose of OFAC sanctions?
What is the purpose of OFAC sanctions?
Sanctions serve foreign policy goals: (1) Counter-terrorism — cutting off funding to terrorist organizations. (2) Non-proliferation — preventing weapons of mass destruction development. (3) Human rights — penalizing human rights abusers and corrupt officials. (4) Aggression response — responding to territorial aggression (Russia/Ukraine). (5) Cyber deterrence — targeting malicious cyber actors.