What this site teaches — and what it doesn't.
Every topic below is listed with the deepest level actually written for it. Where coverage stops at the practitioner level, that is a scope decision, not an accident. Nothing on this page is aspirational.
- Topics
- 71
- To practitioner depth (L2)
- 0
- To technical depth (L3)
- 30
- To standards depth (L4)
- 41
- Message references
- 14
- Glossary terms
- 233
- Checkpoint questions
- 75
- Exception scenarios
- 56
- Screening cases
- 6
- Sources
- 69
PAYMENTS
Payments foundations
- What a payment actually isL3 — Technical details · NOT-REVIEWED
- Money, accounts, and ledgersL3 — Technical details · NOT-REVIEWED
- The parties in a paymentL3 — Technical details · NOT-REVIEWED
- The payment lifecycleL3 — Technical details · NOT-REVIEWED
- Instruments, rails, and schemesL3 — Technical details · NOT-REVIEWED
- Clearing versus settlementL4 — Standards & sources · NOT-REVIEWED
- Correspondent banking, nostro & vostroL4 — Standards & sources · NOT-REVIEWED
- Charges and foreign exchangeL3 — Technical details · NOT-REVIEWED
- Open banking, PSD2, and payment APIsL4 — Standards & sources · NOT-REVIEWED
- Cross-border payment networks beyond correspondent bankingL4 — Standards & sources · NOT-REVIEWED
Clearing & settlement
- Clearing and settlement mechanismsL3 — Technical details · NOT-REVIEWED
- RTGS versus deferred net settlementL4 — Standards & sources · NOT-REVIEWED
- Intraday liquidity and queuesL3 — Technical details · NOT-REVIEWED
- Payment market infrastructuresL4 — Standards & sources · NOT-REVIEWED
- Settlement risk, finality, and CLSL4 — Standards & sources · NOT-REVIEWED
- National and regional payment systemsL4 — Standards & sources · NOT-REVIEWED
SWIFT & MT
- The SWIFT network and BICsL3 — Technical details · NOT-REVIEWED
- MT message structureL4 — Standards & sources · NOT-REVIEWED
- MT103: the customer credit transferL4 — Standards & sources · NOT-REVIEWED
- MT101: the request for transferL3 — Technical details · NOT-REVIEWED
- MT202 and MT202 COVL4 — Standards & sources · NOT-REVIEWED
- MT9xx: confirmations and statementsL3 — Technical details · NOT-REVIEWED
- Serial versus cover routingL4 — Standards & sources · NOT-REVIEWED
- The annual Standards Release (MSR)L4 — Standards & sources · NOT-REVIEWED
- SWIFT gpi and payment trackingL4 — Standards & sources · NOT-REVIEWED
- SWIFT connectivity, messaging services, and the CSPL4 — Standards & sources · NOT-REVIEWED
- SWIFTRef and reference data directoriesL4 — Standards & sources · NOT-REVIEWED
- The Swift services portfolio and platformL4 — Standards & sources · NOT-REVIEWED
ISO 20022 & CBPR+
- Why ISO 20022 existsL3 — Technical details · NOT-REVIEWED
- The ISO 20022 message modelL4 — Standards & sources · NOT-REVIEWED
- The pain family: payment initiationL4 — Standards & sources · NOT-REVIEWED
- The pacs family: interbank messagesL4 — Standards & sources · NOT-REVIEWED
- The camt family: cash management & investigationsL4 — Standards & sources · NOT-REVIEWED
- CBPR+: ISO 20022 for cross-border paymentsL4 — Standards & sources · NOT-REVIEWED
- MT-to-MX translation and truncationL4 — Standards & sources · NOT-REVIEWED
- The ISO 20022 migration timelineL4 — Standards & sources · NOT-REVIEWED
- How a payment declares what it isL4 — Standards & sources · NOT-REVIEWED
SEPA & instant payments
- SEPA: one euro payments areaL3 — Technical details · NOT-REVIEWED
- The SCT lifecycleL4 — Standards & sources · NOT-REVIEWED
- SCT Inst: instant paymentsL4 — Standards & sources · NOT-REVIEWED
- R-transactions: reject, return, recallL4 — Standards & sources · NOT-REVIEWED
- SEPA timelines and reachabilityL4 — Standards & sources · NOT-REVIEWED
- Verification of PayeeL4 — Standards & sources · NOT-REVIEWED
- SDD Core: payments that pullL4 — Standards & sources · NOT-REVIEWED
- SDD refunds: money with a return pathL4 — Standards & sources · NOT-REVIEWED
Operations & architecture
- A day in payment operationsL3 — Technical details · NOT-REVIEWED
- Payment engines and hub architectureL4 — Standards & sources · NOT-REVIEWED
- Accounting entries and ledgersL3 — Technical details · NOT-REVIEWED
- Exceptions and investigationsL3 — Technical details · NOT-REVIEWED
- Nostro reconciliationL3 — Technical details · NOT-REVIEWED
- Payment security and fraud basicsL3 — Technical details · NOT-REVIEWED
SANCTIONS SCREENING
Sanctions foundations
- What sanctions areL3 — Technical details · NOT-REVIEWED
- Who imposes sanctionsL3 — Technical details · NOT-REVIEWED
- Asset freezes and restrictionsL3 — Technical details · NOT-REVIEWED
- Sanctions screening vs AML vs fraudL3 — Technical details · NOT-REVIEWED
- Risk-based screeningL3 — Technical details · NOT-REVIEWED
- Money laundering, terrorist financing, and FATFL4 — Standards & sources · NOT-REVIEWED
List data & identifiers
- Anatomy of a sanctions listL4 — Standards & sources · NOT-REVIEWED
- Identifiers and data qualityL3 — Technical details · NOT-REVIEWED
- List delivery and updatesL4 — Standards & sources · NOT-REVIEWED
- Aggregation and provenanceL3 — Technical details · NOT-REVIEWED
Screening execution
- Customer vs transaction screeningL3 — Technical details · NOT-REVIEWED
- The screening lifecycleL3 — Technical details · NOT-REVIEWED
- Name matching and fuzzy logicL4 — Standards & sources · NOT-REVIEWED
- Secondary identifiers and confidenceL3 — Technical details · NOT-REVIEWED
- Screening payment messagesL4 — Standards & sources · NOT-REVIEWED
- Screening system architectureL3 — Technical details · NOT-REVIEWED
- Payment transparency and the travel ruleL4 — Standards & sources · NOT-REVIEWED
Investigation & governance
- Alert investigation and false positivesL4 — Standards & sources · NOT-REVIEWED
- Governance and policyL4 — Standards & sources · NOT-REVIEWED
- Testing and tuningL3 — Technical details · NOT-REVIEWED
REVIEW LIFECYCLE — WHERE EVERY OBJECT STANDS
Every auditable learning object carries a machine-readable coverage record. An object is not-reviewed until an editorial pass has actually happened; nothing here awards itself a better status. Premium voice means the lesson has been rewritten to the structured block model and passed editorial plus adversarial factual review.
- topics
- 0/71 reviewed
- articles
- 198/198 reviewed · 198 premium
- glossary terms
- 0/233 reviewed
- messages
- 0/14 reviewed
- samples
- 0/11 reviewed
- flows
- 0/47 reviewed
- exception scenarios
- 0/56 reviewed
- screening cases
- 0/6 reviewed
- comparisons
- 0/11 reviewed
- quizs
- 0/16 reviewed
- paths
- 0/7 reviewed
- capstones
- 0/1 reviewed
- Glossary classes
- 8A · 166B · 59C
HUMAN REVIEW GATES — HONESTLY BLOCKED
- Subject-matter-expert reviewNo qualified human payments or sanctions expert has reviewed this content yet. Every coverage record carries this gate as blocked until a named reviewer signs off.
- Learner validationNo zero-domain learner cohort has been tested against the material. Until at least five genuine beginners complete the defined comprehension tasks, no page claims to be learner-validated.
DELIBERATELY OUT OF SCOPE (FOR NOW)
- Card payments, wallets, and merchant acquiringA different ecosystem (schemes, interchange, acquiring) deserving its own curriculum rather than a thin appendix here.
- Full SWIFT Standards MT field specificationsThe complete specifications are licensed SWIFT documentation; we teach curated practitioner subsets and link to the official sources.
- CBPR+ message-by-message usage guideline detailThe full usage guidelines require SWIFT MyStandards access; our CBPR+ content relies on public materials and says so.
- Jurisdiction-specific legal interpretation of sanctionsLegal effect varies by jurisdiction and case; institutions take legal advice. We teach the operational controls, not legal conclusions.
- Real production data of any kindEvery sample, scenario, person, and institution on this site is fictional or illustrative by design.