{
  "generatedFrom": "Payments Signal canonical architecture registry",
  "reviewDate": "2026-07-23",
  "blueprint": {
    "id": "architecture-sanctions-screening",
    "slug": "sanctions-screening-investigation-governance",
    "title": "Sanctions screening, list ingestion, matching, alert, investigation, tuning, and governance architecture",
    "shortTitle": "Sanctions screening",
    "family": "controls",
    "summary": "Trace how current sanctions data becomes a controlled screening decision, a reviewable alert, and evidence that tuning did not silently remove coverage.",
    "audience": "Sanctions architects, compliance officers, screening engineers, investigators, model-risk teams, payment operations, and auditors.",
    "reviewDate": "2026-07-23",
    "versionLabel": "Payments Signal reference architecture v1",
    "status": "current",
    "nodes": [
      {
        "id": "sanctions-sources",
        "title": "Official lists and regulatory obligations",
        "kind": "external-network",
        "summary": "Provides authoritative sanctions designations, changes, identifiers, programmes, and legal context.",
        "responsibilities": [
          "Obtain current authoritative list data",
          "Interpret programme and jurisdiction scope before configuring controls"
        ],
        "owner": "Sanctions authorities and compliance legal team",
        "inputs": [
          "Authorised business instruction and correlated state"
        ],
        "outputs": [
          "Versioned result, status, and audit evidence"
        ],
        "interfaceContracts": [
          "Versioned official lists and regulatory obligations contract",
          "Stable identifier, state, error, and audit contract"
        ],
        "controls": [
          "Source authenticity",
          "Publication timestamp",
          "Jurisdiction and programme scope"
        ],
        "failureModes": [
          "Source unavailable",
          "Malformed update",
          "Legal scope misunderstood"
        ],
        "recovery": [
          "Retain the last verified version",
          "Escalate legal ambiguity before release decisions"
        ],
        "lenses": [
          "applications",
          "interfaces",
          "data",
          "controls",
          "operations",
          "resilience"
        ],
        "evidence": [
          {
            "ref": {
              "sourceId": "ofac-compliance-framework",
              "locator": "Risk assessment and internal controls",
              "label": "official-requirement"
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "OFAC compliance framework"
          },
          {
            "ref": {
              "sourceId": "fatf-recommendations",
              "locator": "Targeted financial sanctions recommendations",
              "label": "official-requirement"
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "FATF Recommendations"
          }
        ],
        "dataClassification": [
          "Payment, message, status, and operational metadata"
        ],
        "nonFunctionalRequirements": [
          "Durable correlation through stable business and technical identifiers",
          "Capacity and availability matched to the service-level objective",
          "Auditable state changes, configuration, and operator actions"
        ]
      },
      {
        "id": "sanctions-list-hub",
        "title": "List ingestion, quality, and publishing hub",
        "kind": "data-store",
        "summary": "Normalises authoritative records while retaining source lineage, effective time, identifiers, scripts, and change history.",
        "responsibilities": [
          "Validate and version every list update",
          "Publish a complete, signed screening snapshot"
        ],
        "owner": "Sanctions data management",
        "inputs": [
          "Authorised business instruction and correlated state"
        ],
        "outputs": [
          "Versioned result, status, and audit evidence"
        ],
        "interfaceContracts": [
          "Versioned list ingestion, quality, and publishing hub contract",
          "Stable identifier, state, error, and audit contract"
        ],
        "controls": [
          "Completeness totals",
          "Schema and identifier checks",
          "Dual approval",
          "Rollback point"
        ],
        "failureModes": [
          "Partial list published",
          "Duplicate identity merged incorrectly",
          "Transliteration lost"
        ],
        "recovery": [
          "Stop publication",
          "Restore the last approved snapshot",
          "Correct and republish with audit history"
        ],
        "lenses": [
          "applications",
          "interfaces",
          "data",
          "controls",
          "operations",
          "resilience"
        ],
        "evidence": [
          {
            "ref": {
              "sourceId": "payments-signal-editorial",
              "locator": "Sanctions screening control architecture",
              "label": "simplified-educational-illustration",
              "simplifications": "List scope, legal prohibitions, screening timing, matching algorithms, thresholds, disposition authority, reporting, data retention, and governance vary by jurisdiction, institution, customer, product, and risk assessment."
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "Payments Signal reference architecture v1"
          }
        ],
        "dataClassification": [
          "Payment, message, status, and operational metadata"
        ],
        "nonFunctionalRequirements": [
          "Durable correlation through stable business and technical identifiers",
          "Capacity and availability matched to the service-level objective",
          "Auditable state changes, configuration, and operator actions"
        ]
      },
      {
        "id": "sanctions-policy",
        "title": "Screening policy and field-coverage map",
        "kind": "control",
        "summary": "Defines who and what is screened, at which lifecycle points, from which message fields, under which jurisdictional and product rules.",
        "responsibilities": [
          "Map every in-scope field to a screening attribute",
          "Name timing, hold, rescreen, and release policy"
        ],
        "owner": "Sanctions compliance governance",
        "inputs": [
          "Authorised business instruction and correlated state"
        ],
        "outputs": [
          "Versioned result, status, and audit evidence"
        ],
        "interfaceContracts": [
          "Versioned screening policy and field-coverage map contract",
          "Stable identifier, state, error, and audit contract"
        ],
        "controls": [
          "Approved scope",
          "Message-version coverage",
          "No silent field omission",
          "Change impact assessment"
        ],
        "failureModes": [
          "New message field not screened",
          "Wrong jurisdiction profile",
          "Released payment not rescreened after material change"
        ],
        "recovery": [
          "Hold affected traffic",
          "Correct the coverage map and replay controlled test cases"
        ],
        "lenses": [
          "applications",
          "interfaces",
          "data",
          "controls",
          "operations",
          "resilience"
        ],
        "evidence": [
          {
            "ref": {
              "sourceId": "ofac-compliance-framework",
              "locator": "Risk assessment, internal controls, testing, and training",
              "label": "official-requirement"
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "OFAC compliance framework"
          },
          {
            "ref": {
              "sourceId": "payments-signal-editorial",
              "locator": "Sanctions screening control architecture",
              "label": "simplified-educational-illustration",
              "simplifications": "List scope, legal prohibitions, screening timing, matching algorithms, thresholds, disposition authority, reporting, data retention, and governance vary by jurisdiction, institution, customer, product, and risk assessment."
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "Payments Signal reference architecture v1"
          }
        ],
        "dataClassification": [
          "Payment, message, status, and operational metadata"
        ],
        "nonFunctionalRequirements": [
          "Durable correlation through stable business and technical identifiers",
          "Capacity and availability matched to the service-level objective",
          "Auditable state changes, configuration, and operator actions"
        ]
      },
      {
        "id": "sanctions-engine",
        "title": "Matching and screening engine",
        "kind": "service",
        "summary": "Compares normalised party, bank, geography, vessel, goods, and narrative data with the approved list snapshot and policy.",
        "responsibilities": [
          "Apply deterministic normalisation and matching",
          "Return candidates with score, matched fields, list version, and policy version"
        ],
        "owner": "Screening platform engineering",
        "inputs": [
          "Authorised business instruction and correlated state"
        ],
        "outputs": [
          "Versioned result, status, and audit evidence"
        ],
        "interfaceContracts": [
          "Versioned matching and screening engine contract",
          "Stable identifier, state, error, and audit contract"
        ],
        "controls": [
          "Authenticated configuration",
          "List and policy version",
          "Deterministic replay",
          "Capacity and latency limits"
        ],
        "failureModes": [
          "Engine unavailable",
          "Configuration drift",
          "False negative from parsing or threshold"
        ],
        "recovery": [
          "Hold or route under approved continuity policy",
          "Replay from retained input and versions"
        ],
        "lenses": [
          "applications",
          "interfaces",
          "data",
          "controls",
          "operations",
          "resilience"
        ],
        "evidence": [
          {
            "ref": {
              "sourceId": "payments-signal-editorial",
              "locator": "Sanctions screening control architecture",
              "label": "simplified-educational-illustration",
              "simplifications": "List scope, legal prohibitions, screening timing, matching algorithms, thresholds, disposition authority, reporting, data retention, and governance vary by jurisdiction, institution, customer, product, and risk assessment."
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "Payments Signal reference architecture v1"
          }
        ],
        "dataClassification": [
          "Payment, message, status, and operational metadata"
        ],
        "nonFunctionalRequirements": [
          "Durable correlation through stable business and technical identifiers",
          "Capacity and availability matched to the service-level objective",
          "Auditable state changes, configuration, and operator actions"
        ]
      },
      {
        "id": "sanctions-payment-gate",
        "title": "Payment hold and release gate",
        "kind": "control",
        "summary": "Prevents the payment from advancing while an in-scope screening result is unresolved.",
        "responsibilities": [
          "Bind every screening result to the exact payment version",
          "Release, reject, block, or escalate only with authorised evidence"
        ],
        "owner": "Payment operations and sanctions control",
        "inputs": [
          "Authorised business instruction and correlated state"
        ],
        "outputs": [
          "Versioned result, status, and audit evidence"
        ],
        "interfaceContracts": [
          "Versioned payment hold and release gate contract",
          "Stable identifier, state, error, and audit contract"
        ],
        "controls": [
          "Fail-closed or approved continuity posture",
          "No self-release",
          "State and amount integrity"
        ],
        "failureModes": [
          "Payment advances before screening",
          "Release applied to changed payment",
          "Duplicate release"
        ],
        "recovery": [
          "Stop downstream processing",
          "Re-screen changed data",
          "Use maker-checker release"
        ],
        "lenses": [
          "applications",
          "interfaces",
          "data",
          "controls",
          "operations",
          "resilience"
        ],
        "evidence": [
          {
            "ref": {
              "sourceId": "payments-signal-editorial",
              "locator": "Sanctions screening control architecture",
              "label": "simplified-educational-illustration",
              "simplifications": "List scope, legal prohibitions, screening timing, matching algorithms, thresholds, disposition authority, reporting, data retention, and governance vary by jurisdiction, institution, customer, product, and risk assessment."
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "Payments Signal reference architecture v1"
          }
        ],
        "dataClassification": [
          "Payment, message, status, and operational metadata"
        ],
        "nonFunctionalRequirements": [
          "Durable correlation through stable business and technical identifiers",
          "Capacity and availability matched to the service-level objective",
          "Auditable state changes, configuration, and operator actions"
        ]
      },
      {
        "id": "sanctions-alerts",
        "title": "Alert queue and case service",
        "kind": "application",
        "summary": "Creates one reviewable case with candidate, payment, party, list, policy, and matching evidence.",
        "responsibilities": [
          "Deduplicate related candidates without hiding evidence",
          "Prioritise by documented risk and deadline"
        ],
        "owner": "Sanctions operations",
        "inputs": [
          "Authorised business instruction and correlated state"
        ],
        "outputs": [
          "Versioned result, status, and audit evidence"
        ],
        "interfaceContracts": [
          "Versioned alert queue and case service contract",
          "Stable identifier, state, error, and audit contract"
        ],
        "controls": [
          "Queue completeness",
          "Stable case key",
          "No unsupported auto-close"
        ],
        "failureModes": [
          "Alert lost",
          "Duplicate cases obscure ownership",
          "Priority starvation"
        ],
        "recovery": [
          "Rebuild from immutable screening outcomes",
          "Assign and age every open case"
        ],
        "lenses": [
          "applications",
          "interfaces",
          "data",
          "controls",
          "operations",
          "resilience"
        ],
        "evidence": [
          {
            "ref": {
              "sourceId": "payments-signal-editorial",
              "locator": "Sanctions screening control architecture",
              "label": "simplified-educational-illustration",
              "simplifications": "List scope, legal prohibitions, screening timing, matching algorithms, thresholds, disposition authority, reporting, data retention, and governance vary by jurisdiction, institution, customer, product, and risk assessment."
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "Payments Signal reference architecture v1"
          }
        ],
        "dataClassification": [
          "Payment, message, status, and operational metadata"
        ],
        "nonFunctionalRequirements": [
          "Durable correlation through stable business and technical identifiers",
          "Capacity and availability matched to the service-level objective",
          "Auditable state changes, configuration, and operator actions"
        ]
      },
      {
        "id": "sanctions-investigation",
        "title": "Investigation and disposition",
        "kind": "operations",
        "summary": "Compares reliable identifiers, ownership, context, and source evidence before recording a reasoned decision.",
        "responsibilities": [
          "Eliminate or confirm using specific evidence",
          "Escalate unresolved ownership, control, and legal questions"
        ],
        "owner": "Sanctions investigators and escalation teams",
        "inputs": [
          "Authorised business instruction and correlated state"
        ],
        "outputs": [
          "Versioned result, status, and audit evidence"
        ],
        "interfaceContracts": [
          "Versioned investigation and disposition contract",
          "Stable identifier, state, error, and audit contract"
        ],
        "controls": [
          "Four-eyes release where required",
          "Evidence citation",
          "Conflict and authority controls"
        ],
        "failureModes": [
          "Generic disposition",
          "True match released",
          "Personal data copied outside the case"
        ],
        "recovery": [
          "Reopen and contain",
          "Escalate to compliance and legal",
          "Correct downstream reporting and payment action"
        ],
        "lenses": [
          "applications",
          "interfaces",
          "data",
          "controls",
          "operations",
          "resilience"
        ],
        "evidence": [
          {
            "ref": {
              "sourceId": "ofac-compliance-framework",
              "locator": "Internal controls, testing, and auditing",
              "label": "official-requirement"
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "OFAC compliance framework"
          },
          {
            "ref": {
              "sourceId": "payments-signal-editorial",
              "locator": "Sanctions screening control architecture",
              "label": "simplified-educational-illustration",
              "simplifications": "List scope, legal prohibitions, screening timing, matching algorithms, thresholds, disposition authority, reporting, data retention, and governance vary by jurisdiction, institution, customer, product, and risk assessment."
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "Payments Signal reference architecture v1"
          }
        ],
        "dataClassification": [
          "Payment, message, status, and operational metadata"
        ],
        "nonFunctionalRequirements": [
          "Durable correlation through stable business and technical identifiers",
          "Capacity and availability matched to the service-level objective",
          "Auditable state changes, configuration, and operator actions"
        ]
      },
      {
        "id": "sanctions-assurance",
        "title": "Tuning, testing, governance, and audit",
        "kind": "operations",
        "summary": "Measures performance above and below thresholds, approves changes, samples decisions, and proves that coverage remains effective.",
        "responsibilities": [
          "Test known positives, variants, and near misses",
          "Approve and monitor list, parser, rule, and threshold changes"
        ],
        "owner": "Sanctions governance, quality assurance, model risk, and internal audit",
        "inputs": [
          "Authorised business instruction and correlated state"
        ],
        "outputs": [
          "Versioned result, status, and audit evidence"
        ],
        "interfaceContracts": [
          "Versioned tuning, testing, governance, and audit contract",
          "Stable identifier, state, error, and audit contract"
        ],
        "controls": [
          "Independent validation",
          "Below-threshold testing",
          "Change rollback",
          "Management information"
        ],
        "failureModes": [
          "Threshold suppresses true matches",
          "Test data does not represent production formats",
          "Change deployed without approval"
        ],
        "recovery": [
          "Restore the last approved configuration",
          "Rescreen affected records",
          "Investigate control failure and report where required"
        ],
        "lenses": [
          "applications",
          "interfaces",
          "data",
          "controls",
          "operations",
          "resilience"
        ],
        "evidence": [
          {
            "ref": {
              "sourceId": "ofac-compliance-framework",
              "locator": "Testing and auditing",
              "label": "official-requirement"
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "OFAC compliance framework"
          },
          {
            "ref": {
              "sourceId": "payments-signal-editorial",
              "locator": "Sanctions screening control architecture",
              "label": "simplified-educational-illustration",
              "simplifications": "List scope, legal prohibitions, screening timing, matching algorithms, thresholds, disposition authority, reporting, data retention, and governance vary by jurisdiction, institution, customer, product, and risk assessment."
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "Payments Signal reference architecture v1"
          }
        ],
        "dataClassification": [
          "Payment, message, status, and operational metadata"
        ],
        "nonFunctionalRequirements": [
          "Durable correlation through stable business and technical identifiers",
          "Capacity and availability matched to the service-level objective",
          "Auditable state changes, configuration, and operator actions"
        ]
      }
    ],
    "interfaces": [
      {
        "id": "sanctions-e1",
        "from": "sanctions-sources",
        "to": "sanctions-list-hub",
        "title": "Authoritative list update",
        "kind": "file",
        "mode": "batch",
        "purpose": "Ingest a signed or otherwise authenticated source publication.",
        "failureBehaviour": "Do not publish a partial or unverifiable update.",
        "evidence": [
          {
            "ref": {
              "sourceId": "payments-signal-editorial",
              "locator": "Sanctions screening control architecture",
              "label": "simplified-educational-illustration",
              "simplifications": "List scope, legal prohibitions, screening timing, matching algorithms, thresholds, disposition authority, reporting, data retention, and governance vary by jurisdiction, institution, customer, product, and risk assessment."
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "Payments Signal reference architecture v1"
          }
        ],
        "controls": [
          "Authentication and authorisation",
          "Integrity and replay protection",
          "Correlation and audit evidence"
        ],
        "lenses": [
          "interfaces",
          "data",
          "ledger",
          "controls",
          "operations",
          "resilience"
        ],
        "dataClassification": [
          "Payment instruction, status, and correlation metadata"
        ]
      },
      {
        "id": "sanctions-e2",
        "from": "sanctions-list-hub",
        "to": "sanctions-engine",
        "title": "Approved list snapshot",
        "kind": "file",
        "mode": "batch",
        "purpose": "Publish a complete versioned screening snapshot.",
        "failureBehaviour": "Keep the previous approved snapshot active until the new one is proven complete.",
        "evidence": [
          {
            "ref": {
              "sourceId": "payments-signal-editorial",
              "locator": "Sanctions screening control architecture",
              "label": "simplified-educational-illustration",
              "simplifications": "List scope, legal prohibitions, screening timing, matching algorithms, thresholds, disposition authority, reporting, data retention, and governance vary by jurisdiction, institution, customer, product, and risk assessment."
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "Payments Signal reference architecture v1"
          }
        ],
        "controls": [
          "Authentication and authorisation",
          "Integrity and replay protection",
          "Correlation and audit evidence"
        ],
        "lenses": [
          "interfaces",
          "data",
          "ledger",
          "controls",
          "operations",
          "resilience"
        ],
        "dataClassification": [
          "Payment instruction, status, and correlation metadata"
        ]
      },
      {
        "id": "sanctions-e3",
        "from": "sanctions-policy",
        "to": "sanctions-engine",
        "title": "Policy and field map",
        "kind": "control",
        "mode": "synchronous",
        "purpose": "Apply the approved scope, fields, timing, rules, and thresholds.",
        "failureBehaviour": "Reject unknown message versions or route them to a controlled hold.",
        "evidence": [
          {
            "ref": {
              "sourceId": "payments-signal-editorial",
              "locator": "Sanctions screening control architecture",
              "label": "simplified-educational-illustration",
              "simplifications": "List scope, legal prohibitions, screening timing, matching algorithms, thresholds, disposition authority, reporting, data retention, and governance vary by jurisdiction, institution, customer, product, and risk assessment."
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "Payments Signal reference architecture v1"
          }
        ],
        "controls": [
          "Authentication and authorisation",
          "Integrity and replay protection",
          "Correlation and audit evidence"
        ],
        "lenses": [
          "interfaces",
          "data",
          "ledger",
          "controls",
          "operations",
          "resilience"
        ],
        "dataClassification": [
          "Payment instruction, status, and correlation metadata"
        ]
      },
      {
        "id": "sanctions-e4",
        "from": "sanctions-payment-gate",
        "to": "sanctions-engine",
        "title": "Payment screening request",
        "kind": "message",
        "mode": "synchronous",
        "purpose": "Screen the exact payment and party version before release.",
        "messageIds": [
          "pain-001",
          "pacs-008",
          "pacs-009",
          "mt103",
          "mt202cov"
        ],
        "failureBehaviour": "Hold under policy when no conclusive result is available.",
        "evidence": [
          {
            "ref": {
              "sourceId": "payments-signal-editorial",
              "locator": "Sanctions screening control architecture",
              "label": "simplified-educational-illustration",
              "simplifications": "List scope, legal prohibitions, screening timing, matching algorithms, thresholds, disposition authority, reporting, data retention, and governance vary by jurisdiction, institution, customer, product, and risk assessment."
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "Payments Signal reference architecture v1"
          }
        ],
        "controls": [
          "Authentication and authorisation",
          "Integrity and replay protection",
          "Correlation and audit evidence"
        ],
        "lenses": [
          "interfaces",
          "data",
          "ledger",
          "controls",
          "operations",
          "resilience"
        ],
        "dataClassification": [
          "Payment instruction, status, and correlation metadata"
        ]
      },
      {
        "id": "sanctions-e5",
        "from": "sanctions-engine",
        "to": "sanctions-payment-gate",
        "title": "Screening outcome",
        "kind": "control",
        "mode": "synchronous",
        "purpose": "Return clear, alert, unavailable, or error with versions and correlation.",
        "failureBehaviour": "Never turn timeout or error into clear.",
        "evidence": [
          {
            "ref": {
              "sourceId": "payments-signal-editorial",
              "locator": "Sanctions screening control architecture",
              "label": "simplified-educational-illustration",
              "simplifications": "List scope, legal prohibitions, screening timing, matching algorithms, thresholds, disposition authority, reporting, data retention, and governance vary by jurisdiction, institution, customer, product, and risk assessment."
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "Payments Signal reference architecture v1"
          }
        ],
        "controls": [
          "Authentication and authorisation",
          "Integrity and replay protection",
          "Correlation and audit evidence"
        ],
        "lenses": [
          "interfaces",
          "data",
          "ledger",
          "controls",
          "operations",
          "resilience"
        ],
        "dataClassification": [
          "Payment instruction, status, and correlation metadata"
        ]
      },
      {
        "id": "sanctions-e6",
        "from": "sanctions-engine",
        "to": "sanctions-alerts",
        "title": "Candidate alert",
        "kind": "event",
        "mode": "asynchronous",
        "purpose": "Create a durable case for every reviewable candidate.",
        "failureBehaviour": "Replay safely from retained outcomes after queue failure.",
        "evidence": [
          {
            "ref": {
              "sourceId": "payments-signal-editorial",
              "locator": "Sanctions screening control architecture",
              "label": "simplified-educational-illustration",
              "simplifications": "List scope, legal prohibitions, screening timing, matching algorithms, thresholds, disposition authority, reporting, data retention, and governance vary by jurisdiction, institution, customer, product, and risk assessment."
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "Payments Signal reference architecture v1"
          }
        ],
        "controls": [
          "Authentication and authorisation",
          "Integrity and replay protection",
          "Correlation and audit evidence"
        ],
        "lenses": [
          "interfaces",
          "data",
          "ledger",
          "controls",
          "operations",
          "resilience"
        ],
        "dataClassification": [
          "Payment instruction, status, and correlation metadata"
        ]
      },
      {
        "id": "sanctions-e7",
        "from": "sanctions-alerts",
        "to": "sanctions-investigation",
        "title": "Investigation assignment",
        "kind": "operator",
        "mode": "operator",
        "purpose": "Assign complete candidate and payment evidence.",
        "failureBehaviour": "Escalate ageing and missing evidence.",
        "evidence": [
          {
            "ref": {
              "sourceId": "payments-signal-editorial",
              "locator": "Sanctions screening control architecture",
              "label": "simplified-educational-illustration",
              "simplifications": "List scope, legal prohibitions, screening timing, matching algorithms, thresholds, disposition authority, reporting, data retention, and governance vary by jurisdiction, institution, customer, product, and risk assessment."
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "Payments Signal reference architecture v1"
          }
        ],
        "controls": [
          "Authentication and authorisation",
          "Integrity and replay protection",
          "Correlation and audit evidence"
        ],
        "lenses": [
          "interfaces",
          "data",
          "ledger",
          "controls",
          "operations",
          "resilience"
        ],
        "dataClassification": [
          "Payment instruction, status, and correlation metadata"
        ]
      },
      {
        "id": "sanctions-e8",
        "from": "sanctions-investigation",
        "to": "sanctions-payment-gate",
        "title": "Authorised disposition",
        "kind": "control",
        "mode": "operator",
        "purpose": "Release, reject, block, or escalate the exact held version.",
        "failureBehaviour": "Reject a disposition from an unauthorised role or for changed data.",
        "evidence": [
          {
            "ref": {
              "sourceId": "payments-signal-editorial",
              "locator": "Sanctions screening control architecture",
              "label": "simplified-educational-illustration",
              "simplifications": "List scope, legal prohibitions, screening timing, matching algorithms, thresholds, disposition authority, reporting, data retention, and governance vary by jurisdiction, institution, customer, product, and risk assessment."
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "Payments Signal reference architecture v1"
          }
        ],
        "controls": [
          "Authentication and authorisation",
          "Integrity and replay protection",
          "Correlation and audit evidence"
        ],
        "lenses": [
          "interfaces",
          "data",
          "ledger",
          "controls",
          "operations",
          "resilience"
        ],
        "dataClassification": [
          "Payment instruction, status, and correlation metadata"
        ]
      },
      {
        "id": "sanctions-e9",
        "from": "sanctions-assurance",
        "to": "sanctions-policy",
        "title": "Approved configuration change",
        "kind": "control",
        "mode": "operator",
        "purpose": "Publish tested rule, parser, and threshold changes.",
        "failureBehaviour": "Rollback changes that fail production or below-threshold monitoring.",
        "evidence": [
          {
            "ref": {
              "sourceId": "payments-signal-editorial",
              "locator": "Sanctions screening control architecture",
              "label": "simplified-educational-illustration",
              "simplifications": "List scope, legal prohibitions, screening timing, matching algorithms, thresholds, disposition authority, reporting, data retention, and governance vary by jurisdiction, institution, customer, product, and risk assessment."
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "Payments Signal reference architecture v1"
          }
        ],
        "controls": [
          "Authentication and authorisation",
          "Integrity and replay protection",
          "Correlation and audit evidence"
        ],
        "lenses": [
          "interfaces",
          "data",
          "ledger",
          "controls",
          "operations",
          "resilience"
        ],
        "dataClassification": [
          "Payment instruction, status, and correlation metadata"
        ]
      },
      {
        "id": "sanctions-e10",
        "from": "sanctions-engine",
        "to": "sanctions-assurance",
        "title": "Outcome and performance evidence",
        "kind": "event",
        "mode": "asynchronous",
        "purpose": "Measure coverage, latency, alert volume, and threshold behaviour.",
        "failureBehaviour": "Keep sensitive data minimised and access controlled.",
        "evidence": [
          {
            "ref": {
              "sourceId": "payments-signal-editorial",
              "locator": "Sanctions screening control architecture",
              "label": "simplified-educational-illustration",
              "simplifications": "List scope, legal prohibitions, screening timing, matching algorithms, thresholds, disposition authority, reporting, data retention, and governance vary by jurisdiction, institution, customer, product, and risk assessment."
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "Payments Signal reference architecture v1"
          }
        ],
        "controls": [
          "Authentication and authorisation",
          "Integrity and replay protection",
          "Correlation and audit evidence"
        ],
        "lenses": [
          "interfaces",
          "data",
          "ledger",
          "controls",
          "operations",
          "resilience"
        ],
        "dataClassification": [
          "Payment instruction, status, and correlation metadata"
        ]
      }
    ],
    "views": [
      {
        "id": "context",
        "label": "Context",
        "plainPurpose": "Who depends on the architecture, which external service it reaches, and where value ultimately moves.",
        "nodeIds": [
          "sanctions-sources",
          "sanctions-alerts"
        ],
        "interfaceIds": [],
        "placements": {
          "sanctions-sources": {
            "x": 80,
            "y": 100,
            "width": 244,
            "height": 126
          },
          "sanctions-alerts": {
            "x": 444,
            "y": 100,
            "width": 244,
            "height": 126
          }
        },
        "boundaries": []
      },
      {
        "id": "container",
        "label": "Container",
        "plainPurpose": "The major applications, stores, gateways, controls, and operational ownership boundaries.",
        "nodeIds": [
          "sanctions-sources",
          "sanctions-list-hub",
          "sanctions-policy",
          "sanctions-payment-gate",
          "sanctions-alerts",
          "sanctions-investigation",
          "sanctions-assurance"
        ],
        "interfaceIds": [
          "sanctions-e1",
          "sanctions-e7",
          "sanctions-e8",
          "sanctions-e9"
        ],
        "placements": {
          "sanctions-sources": {
            "x": 80,
            "y": 100,
            "width": 196,
            "height": 126
          },
          "sanctions-list-hub": {
            "x": 376,
            "y": 100,
            "width": 196,
            "height": 126
          },
          "sanctions-policy": {
            "x": 672,
            "y": 100,
            "width": 196,
            "height": 126
          },
          "sanctions-payment-gate": {
            "x": 968,
            "y": 100,
            "width": 196,
            "height": 126
          },
          "sanctions-alerts": {
            "x": 80,
            "y": 326,
            "width": 196,
            "height": 126
          },
          "sanctions-investigation": {
            "x": 376,
            "y": 326,
            "width": 196,
            "height": 126
          },
          "sanctions-assurance": {
            "x": 672,
            "y": 326,
            "width": 196,
            "height": 126
          }
        },
        "boundaries": [
          {
            "id": "container-bank-boundary",
            "label": "Institution-controlled boundary",
            "nodeIds": [
              "sanctions-list-hub",
              "sanctions-policy",
              "sanctions-payment-gate",
              "sanctions-alerts",
              "sanctions-investigation",
              "sanctions-assurance"
            ],
            "kind": "ownership"
          }
        ]
      },
      {
        "id": "component",
        "label": "Component",
        "plainPurpose": "The processing responsibilities and interface contracts that must cooperate for one payment.",
        "nodeIds": [
          "sanctions-sources",
          "sanctions-list-hub",
          "sanctions-policy",
          "sanctions-engine",
          "sanctions-payment-gate",
          "sanctions-alerts",
          "sanctions-investigation",
          "sanctions-assurance"
        ],
        "interfaceIds": [
          "sanctions-e1",
          "sanctions-e2",
          "sanctions-e3",
          "sanctions-e4",
          "sanctions-e5",
          "sanctions-e6",
          "sanctions-e7",
          "sanctions-e8",
          "sanctions-e9",
          "sanctions-e10"
        ],
        "placements": {
          "sanctions-sources": {
            "x": 80,
            "y": 100,
            "width": 196,
            "height": 126
          },
          "sanctions-list-hub": {
            "x": 376,
            "y": 100,
            "width": 196,
            "height": 126
          },
          "sanctions-policy": {
            "x": 672,
            "y": 100,
            "width": 196,
            "height": 126
          },
          "sanctions-engine": {
            "x": 968,
            "y": 100,
            "width": 196,
            "height": 126
          },
          "sanctions-payment-gate": {
            "x": 80,
            "y": 326,
            "width": 196,
            "height": 126
          },
          "sanctions-alerts": {
            "x": 376,
            "y": 326,
            "width": 196,
            "height": 126
          },
          "sanctions-investigation": {
            "x": 672,
            "y": 326,
            "width": 196,
            "height": 126
          },
          "sanctions-assurance": {
            "x": 968,
            "y": 326,
            "width": 196,
            "height": 126
          }
        },
        "boundaries": [
          {
            "id": "component-bank-boundary",
            "label": "Institution-controlled boundary",
            "nodeIds": [
              "sanctions-list-hub",
              "sanctions-policy",
              "sanctions-engine",
              "sanctions-payment-gate",
              "sanctions-alerts",
              "sanctions-investigation",
              "sanctions-assurance"
            ],
            "kind": "ownership"
          }
        ]
      },
      {
        "id": "deployment",
        "label": "Deployment",
        "plainPurpose": "The trust zones, runtime dependencies, external connections, and recovery boundaries.",
        "nodeIds": [
          "sanctions-sources",
          "sanctions-list-hub",
          "sanctions-alerts"
        ],
        "interfaceIds": [
          "sanctions-e1"
        ],
        "placements": {
          "sanctions-sources": {
            "x": 80,
            "y": 100,
            "width": 244,
            "height": 126
          },
          "sanctions-list-hub": {
            "x": 444,
            "y": 100,
            "width": 244,
            "height": 126
          },
          "sanctions-alerts": {
            "x": 808,
            "y": 100,
            "width": 244,
            "height": 126
          }
        },
        "boundaries": [
          {
            "id": "deployment-bank-boundary",
            "label": "Institution-controlled boundary",
            "nodeIds": [
              "sanctions-list-hub",
              "sanctions-alerts"
            ],
            "kind": "ownership"
          }
        ]
      }
    ],
    "traces": [
      {
        "id": "sanctions-payment-screen",
        "label": "List update to payment release",
        "summary": "Follow the evidence chain that lets a held payment advance—or keeps it stopped.",
        "viewId": "component",
        "steps": [
          {
            "id": "sanctions-payment-screen-step-1",
            "title": "Receive an official update",
            "nodeId": "sanctions-sources",
            "interfaceId": "sanctions-e1",
            "plainExplanation": "The list hub records the authority, publication, and source version.",
            "businessState": "Source version received"
          },
          {
            "id": "sanctions-payment-screen-step-2",
            "title": "Publish a complete snapshot",
            "nodeId": "sanctions-list-hub",
            "interfaceId": "sanctions-e2",
            "plainExplanation": "Quality and completeness controls pass before the engine receives the list.",
            "businessState": "List snapshot approved"
          },
          {
            "id": "sanctions-payment-screen-step-3",
            "title": "Apply approved scope",
            "nodeId": "sanctions-policy",
            "interfaceId": "sanctions-e3",
            "plainExplanation": "The field map says exactly which payment data reaches which screening attribute.",
            "businessState": "Policy version active"
          },
          {
            "id": "sanctions-payment-screen-step-4",
            "title": "Hold and screen",
            "nodeId": "sanctions-payment-gate",
            "interfaceId": "sanctions-e4",
            "plainExplanation": "The payment cannot advance while the control has no conclusive outcome.",
            "businessState": "Payment held for control",
            "messageIds": [
              "pacs-008"
            ]
          },
          {
            "id": "sanctions-payment-screen-step-5",
            "title": "Create a candidate",
            "nodeId": "sanctions-engine",
            "interfaceId": "sanctions-e6",
            "plainExplanation": "The engine records matched fields, score, list version, and policy version.",
            "businessState": "Alert created"
          },
          {
            "id": "sanctions-payment-screen-step-6",
            "title": "Record a reasoned disposition",
            "nodeId": "sanctions-investigation",
            "interfaceId": "sanctions-e8",
            "plainExplanation": "The investigator cites the identifiers and evidence that support release or escalation.",
            "businessState": "Decision authorised"
          },
          {
            "id": "sanctions-payment-screen-step-7",
            "title": "Apply the decision once",
            "nodeId": "sanctions-payment-gate",
            "plainExplanation": "The gate applies the decision only to the unchanged payment version.",
            "businessState": "Released, rejected, blocked, or escalated"
          }
        ],
        "evidence": [
          {
            "ref": {
              "sourceId": "ofac-compliance-framework",
              "locator": "Five essential compliance components",
              "label": "official-requirement"
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "OFAC compliance framework"
          },
          {
            "ref": {
              "sourceId": "payments-signal-editorial",
              "locator": "Sanctions screening control architecture",
              "label": "simplified-educational-illustration",
              "simplifications": "List scope, legal prohibitions, screening timing, matching algorithms, thresholds, disposition authority, reporting, data retention, and governance vary by jurisdiction, institution, customer, product, and risk assessment."
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "Payments Signal reference architecture v1"
          }
        ]
      }
    ],
    "stressCases": [
      {
        "id": "sanctions-stress-list",
        "label": "List update is incomplete",
        "trigger": "Completeness totals fail during a new official-list update.",
        "divergesAfterStepId": "sanctions-payment-screen-step-2",
        "traceId": "sanctions-payment-screen",
        "affectedNodeIds": [
          "sanctions-list-hub",
          "sanctions-engine"
        ],
        "affectedInterfaceIds": [
          "sanctions-e1",
          "sanctions-e2"
        ],
        "lastConfirmedState": "The previous approved list snapshot remains active.",
        "settlementState": "No settlement state changes because of the failed publication.",
        "fundsState": "Payments follow the approved continuity posture.",
        "owner": "Sanctions data management",
        "safeAction": "Do not publish the partial list; retain and disclose the last verified version.",
        "requiredEvidence": [
          "Source checksum",
          "Record totals",
          "Rejected rows",
          "Previous snapshot"
        ],
        "recoverySteps": [
          "Correct ingestion",
          "Re-run quality checks",
          "Publish under dual approval",
          "Assess any exposure window"
        ],
        "evidence": [
          {
            "ref": {
              "sourceId": "payments-signal-editorial",
              "locator": "Sanctions screening control architecture",
              "label": "simplified-educational-illustration",
              "simplifications": "List scope, legal prohibitions, screening timing, matching algorithms, thresholds, disposition authority, reporting, data retention, and governance vary by jurisdiction, institution, customer, product, and risk assessment."
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "Payments Signal reference architecture v1"
          }
        ]
      },
      {
        "id": "sanctions-stress-engine",
        "label": "Screening engine is unavailable",
        "trigger": "A payment cannot obtain a conclusive screening outcome.",
        "divergesAfterStepId": "sanctions-payment-screen-step-4",
        "traceId": "sanctions-payment-screen",
        "affectedNodeIds": [
          "sanctions-engine",
          "sanctions-payment-gate"
        ],
        "affectedInterfaceIds": [
          "sanctions-e4",
          "sanctions-e5"
        ],
        "lastConfirmedState": "Payment reached the screening gate.",
        "settlementState": "Settlement has not been authorised by this architecture.",
        "fundsState": "Funds may remain reserved or unposted under product rules.",
        "owner": "Payment and sanctions operations",
        "safeAction": "Use the approved fail-closed or formally documented continuity posture; never convert error to clear.",
        "requiredEvidence": [
          "Payment version",
          "Engine health",
          "Continuity decision",
          "Queue position"
        ],
        "recoverySteps": [
          "Restore or invoke approved alternative control",
          "Screen the same payment version",
          "Release only on a conclusive authorised result"
        ],
        "evidence": [
          {
            "ref": {
              "sourceId": "payments-signal-editorial",
              "locator": "Sanctions screening control architecture",
              "label": "simplified-educational-illustration",
              "simplifications": "List scope, legal prohibitions, screening timing, matching algorithms, thresholds, disposition authority, reporting, data retention, and governance vary by jurisdiction, institution, customer, product, and risk assessment."
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "Payments Signal reference architecture v1"
          }
        ]
      },
      {
        "id": "sanctions-stress-threshold",
        "label": "Below-threshold test finds a true match",
        "trigger": "Independent testing finds a relevant target that the live threshold suppressed.",
        "divergesAfterStepId": "sanctions-payment-screen-step-7",
        "traceId": "sanctions-payment-screen",
        "affectedNodeIds": [
          "sanctions-assurance",
          "sanctions-policy",
          "sanctions-engine",
          "sanctions-investigation"
        ],
        "affectedInterfaceIds": [
          "sanctions-e9",
          "sanctions-e10"
        ],
        "lastConfirmedState": "A control weakness is evidenced.",
        "settlementState": "Past settlement states vary and must be investigated.",
        "fundsState": "Affected payments require trace and legal assessment; no blanket reversal is implied.",
        "owner": "Sanctions compliance leadership",
        "safeAction": "Contain the configuration, identify the affected population, rescreen, investigate, and meet reporting duties.",
        "requiredEvidence": [
          "Test case",
          "Configuration version",
          "Affected population",
          "Payment and disposition history"
        ],
        "recoverySteps": [
          "Restore an approved setting",
          "Rescreen scoped records",
          "Investigate and report",
          "Validate the corrective change"
        ],
        "evidence": [
          {
            "ref": {
              "sourceId": "ofac-compliance-framework",
              "locator": "Testing and auditing",
              "label": "official-requirement"
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "OFAC compliance framework"
          },
          {
            "ref": {
              "sourceId": "payments-signal-editorial",
              "locator": "Sanctions screening control architecture",
              "label": "simplified-educational-illustration",
              "simplifications": "List scope, legal prohibitions, screening timing, matching algorithms, thresholds, disposition authority, reporting, data retention, and governance vary by jurisdiction, institution, customer, product, and risk assessment."
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "Payments Signal reference architecture v1"
          }
        ]
      }
    ],
    "overlays": [
      {
        "id": "sanctions-overlay-payment",
        "label": "Transaction screening",
        "summary": "Apply the field map, matching engine, hold, alert, investigation, and release gate to a payment message.",
        "nodeIds": [
          "sanctions-policy",
          "sanctions-engine",
          "sanctions-payment-gate",
          "sanctions-alerts",
          "sanctions-investigation"
        ],
        "interfaceIds": [
          "sanctions-e3",
          "sanctions-e4",
          "sanctions-e5",
          "sanctions-e6",
          "sanctions-e7",
          "sanctions-e8"
        ],
        "relatedFlowIds": [
          "flow-cbpr-pacs008",
          "flow-swift-serial",
          "flow-swift-cover",
          "flow-buna"
        ],
        "evidence": [
          {
            "ref": {
              "sourceId": "payments-signal-editorial",
              "locator": "Sanctions screening control architecture",
              "label": "simplified-educational-illustration",
              "simplifications": "List scope, legal prohibitions, screening timing, matching algorithms, thresholds, disposition authority, reporting, data retention, and governance vary by jurisdiction, institution, customer, product, and risk assessment."
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "Payments Signal reference architecture v1"
          }
        ],
        "coverageGap": "Exact screened fields, list scope, timing, and disposition duties require the institution's approved risk assessment and applicable law."
      },
      {
        "id": "sanctions-overlay-governance",
        "label": "Screening assurance",
        "summary": "Show list lineage, policy, testing, tuning, approval, and rollback as one control system.",
        "nodeIds": [
          "sanctions-sources",
          "sanctions-list-hub",
          "sanctions-policy",
          "sanctions-engine",
          "sanctions-assurance"
        ],
        "interfaceIds": [
          "sanctions-e1",
          "sanctions-e2",
          "sanctions-e3",
          "sanctions-e9",
          "sanctions-e10"
        ],
        "relatedFlowIds": [],
        "evidence": [
          {
            "ref": {
              "sourceId": "ofac-compliance-framework",
              "locator": "Risk assessment, internal controls, testing, and training",
              "label": "official-requirement"
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "OFAC compliance framework"
          }
        ]
      }
    ],
    "decisions": [
      {
        "id": "sanctions-decision-unavailable",
        "question": "What happens when screening is unavailable?",
        "options": [
          {
            "label": "Fail closed",
            "consequence": "Prevents unscreened release but needs queue, liquidity, customer, and service-continuity treatment."
          },
          {
            "label": "Approved compensating control",
            "consequence": "May preserve critical service but must be specifically authorised, evidenced, limited, and reviewed."
          }
        ],
        "guidance": "Never default an error to clear. Document authority, scope, duration, evidence, and retrospective screening for any continuity posture.",
        "evidence": [
          {
            "ref": {
              "sourceId": "payments-signal-editorial",
              "locator": "Sanctions screening control architecture",
              "label": "simplified-educational-illustration",
              "simplifications": "List scope, legal prohibitions, screening timing, matching algorithms, thresholds, disposition authority, reporting, data retention, and governance vary by jurisdiction, institution, customer, product, and risk assessment."
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "Payments Signal reference architecture v1"
          }
        ]
      },
      {
        "id": "sanctions-decision-threshold",
        "question": "Who may change matching thresholds?",
        "options": [
          {
            "label": "Controlled central authority",
            "consequence": "Makes approval and audit clearer but needs market and language-specific evidence."
          },
          {
            "label": "Local operations",
            "consequence": "Can react quickly but risks uncontrolled divergence and suppressed true matches."
          }
        ],
        "guidance": "Use risk-based, tested, versioned, independently reviewed changes with below-threshold monitoring and rollback.",
        "evidence": [
          {
            "ref": {
              "sourceId": "ofac-compliance-framework",
              "locator": "Testing and auditing",
              "label": "official-requirement"
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "OFAC compliance framework"
          }
        ]
      }
    ],
    "targets": [
      {
        "type": "message",
        "id": "pacs-008"
      },
      {
        "type": "message",
        "id": "pacs-009"
      },
      {
        "type": "message",
        "id": "mt103"
      },
      {
        "type": "message",
        "id": "mt202cov"
      },
      {
        "type": "flow",
        "id": "flow-cbpr-pacs008"
      },
      {
        "type": "flow",
        "id": "flow-swift-serial"
      },
      {
        "type": "flow",
        "id": "flow-swift-cover"
      },
      {
        "type": "flow",
        "id": "flow-buna"
      }
    ],
    "glossaryTermIds": [
      "alert",
      "false-negative",
      "false-positive",
      "list-management",
      "match-threshold",
      "sanctions-screening",
      "screening-hold",
      "true-match"
    ],
    "evidence": [
      {
        "ref": {
          "sourceId": "ofac-compliance-framework",
          "locator": "Five essential compliance components",
          "label": "official-requirement"
        },
        "verifiedDate": "2026-07-23",
        "versionContext": "OFAC compliance framework"
      },
      {
        "ref": {
          "sourceId": "fatf-recommendations",
          "locator": "Targeted financial sanctions",
          "label": "official-requirement"
        },
        "verifiedDate": "2026-07-23",
        "versionContext": "FATF Recommendations"
      },
      {
        "ref": {
          "sourceId": "payments-signal-editorial",
          "locator": "Sanctions screening control architecture",
          "label": "simplified-educational-illustration",
          "simplifications": "List scope, legal prohibitions, screening timing, matching algorithms, thresholds, disposition authority, reporting, data retention, and governance vary by jurisdiction, institution, customer, product, and risk assessment."
        },
        "verifiedDate": "2026-07-23",
        "versionContext": "Payments Signal reference architecture v1"
      }
    ],
    "simplifies": "This architecture teaches the control chain from authoritative list through policy, matching, hold, investigation, decision, and assurance. It does not prescribe legal scope, list combinations, matching mathematics, threshold, auto-disposition, release authority, record retention, or reporting duties."
  },
  "sources": [
    {
      "id": "ofac-compliance-framework",
      "publisher": "U.S. Department of the Treasury, Office of Foreign Assets Control",
      "title": "A Framework for OFAC Compliance Commitments",
      "sourceType": "regulatory-guidance",
      "accessedDate": "2026-07-23",
      "url": "https://ofac.treasury.gov/system/files/126/framework_ofac_cc.pdf",
      "applicability": "Describes five essential components of a risk-based sanctions-compliance programme: management commitment, risk assessment, internal controls, testing and auditing, and training.",
      "notes": "The framework informs governance and control architecture. It does not prescribe one screening-system topology or remove the need to apply current law and programme-specific requirements."
    },
    {
      "id": "fatf-recommendations",
      "publisher": "Financial Action Task Force",
      "title": "The FATF Recommendations: International Standards on Combating Money Laundering and the Financing of Terrorism & Proliferation",
      "sourceType": "regulatory-guidance",
      "publicationDate": "2012-02-16",
      "accessedDate": "2026-07-12",
      "url": "https://www.fatf-gafi.org/en/publications/Fatfrecommendations/Fatf-recommendations.html",
      "applicability": "The global standards countries implement against money laundering, terrorist financing, and proliferation financing, including targeted financial sanctions and payment transparency under Recommendation 16.",
      "notes": "Adopted in 2012 and updated regularly since; the June 2025 FATF plenary agreed revisions to Recommendation 16 on payment transparency. Consult the live consolidated text for the current wording."
    },
    {
      "id": "payments-signal-editorial",
      "publisher": "Payments Signal",
      "title": "Payments Signal editorial teaching models",
      "sourceType": "educational-simplification",
      "accessedDate": "2026-07-12",
      "applicability": "This site's own simplified teaching models.",
      "notes": "Used wherever diagrams, scenarios, figures, or example values are didactic constructions rather than sourced facts; every such use carries a simplifications disclosure. All people, companies, banks, and list entries in examples are fictional."
    }
  ],
  "relatedContent": [
    {
      "type": "article",
      "label": "Accounting Entries in Payments",
      "href": "/2026/07/13/accounting-entries-in-payments",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "ACK, NACK, and the Payment Status Report (pacs.002)",
      "href": "/2026/07/13/ack-nack-and-payment-status-report",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "Adverse media screening",
      "href": "/2026/07/13/adverse-media-screening",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "AML transaction monitoring",
      "href": "/2026/07/13/aml-transaction-monitoring",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "AML transaction-monitoring typologies",
      "href": "/2026/07/13/aml-monitoring-typologies",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "AML Typologies Across Sectors: Beyond the Bank",
      "href": "/2026/07/13/aml-typologies-across-sectors",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "Anatomy of a sanctions list entry",
      "href": "/2026/07/13/sanctions-list-entry-anatomy",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "Asset freezes and prohibitions",
      "href": "/2026/07/13/asset-freezes-and-prohibitions",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "Beneficial ownership and UBO",
      "href": "/2026/07/13/beneficial-ownership-and-ubo",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "BIC versus LEI: payment reference data",
      "href": "/2026/07/13/bic-vs-lei-reference-data",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "Book and On-Us Payments",
      "href": "/2026/07/13/book-and-on-us-payments",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "Buna: the Arab region's cross-border payment system",
      "href": "/2026/07/13/buna-arab-regional-payments",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "Business email compromise and mandate fraud",
      "href": "/2026/07/13/business-email-compromise-and-mandate-fraud",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "Cash Transaction Reports and the AML Reporting Chain",
      "href": "/2026/07/13/cash-transaction-reports-and-aml-reporting",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "CBPR+: ISO 20022 for cross-border payments",
      "href": "/2026/07/13/cbpr-plus-cross-border-iso20022",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "CGI-MP: Common ISO 20022 Practice for Corporates",
      "href": "/2026/07/13/cgi-mp-corporate-iso20022",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "Charges and FOREX (FX)",
      "href": "/2026/07/13/charges-and-forex-fx",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "Correspondent banking risk",
      "href": "/2026/07/13/correspondent-banking-risk",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "Correspondent onboarding and de-risking",
      "href": "/2026/07/13/correspondent-onboarding-and-de-risking",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "Customer risk rating and enhanced due diligence",
      "href": "/2026/07/13/customer-risk-rating-and-edd",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "Customer screening versus transaction screening",
      "href": "/2026/07/13/customer-versus-transaction-screening",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "Domestic versus cross-border payments",
      "href": "/2026/07/13/domestic-vs-cross-border-payments",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "FATCA, CRS, and Tax-Information Exchange",
      "href": "/2026/07/13/fatca-crs-and-tax-information-exchange",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "FINplus and Browse",
      "href": "/2026/07/13/finplus-and-browse",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "High-value payments and HVPS+",
      "href": "/2026/07/13/high-value-payments-and-hvps-plus",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "How a fraud detection product works",
      "href": "/2026/07/13/how-a-fraud-detection-product-works",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "How a sanctions screening product works",
      "href": "/2026/07/13/how-a-sanctions-screening-product-works",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "How sanctions lists are delivered and updated",
      "href": "/2026/07/13/sanctions-list-delivery-and-updates",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "Identifiers and data quality in screening",
      "href": "/2026/07/13/screening-identifiers-and-data-quality",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "Information-sharing requests (314(a))",
      "href": "/2026/07/13/information-sharing-requests-314a",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "Investigating a screening alert",
      "href": "/2026/07/13/investigating-screening-alerts",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "KYC and customer due diligence basics",
      "href": "/2026/07/13/kyc-and-customer-due-diligence",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "List aggregation and provenance",
      "href": "/2026/07/13/sanctions-list-aggregation-and-provenance",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "Money laundering explained",
      "href": "/2026/07/13/money-laundering-explained",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "MT202 COV: cover payments explained",
      "href": "/2026/07/13/mt202-cov-cover-payments",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "Name matching and fuzzy logic",
      "href": "/2026/07/13/screening-name-matching-and-fuzzy-logic",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "One corporate payment: the full MX lifecycle and its MT migration path",
      "href": "/2026/07/18/corporate-payment-full-message-lifecycle",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "Other Payment Message Standards Beyond SWIFT",
      "href": "/2026/07/13/other-payment-message-standards",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "PAPSS: the Pan-African Payment and Settlement System",
      "href": "/2026/07/13/papss-pan-african-settlement",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "Payment fraud typologies",
      "href": "/2026/07/13/payment-fraud-typologies",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "Payment transparency and wire stripping",
      "href": "/2026/07/13/payment-transparency-and-wire-stripping",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "Purpose codes in payments",
      "href": "/2026/07/13/purpose-codes-in-payments",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "Reversals, returns, recalls, and cancellations",
      "href": "/2026/07/13/reversals-returns-and-cancellations",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "Sanctions evasion typologies",
      "href": "/2026/07/13/sanctions-evasion-typologies",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "Sanctions screening system architecture",
      "href": "/2026/07/13/sanctions-screening-architecture",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "Sanctions screening versus AML and fraud",
      "href": "/2026/07/13/screening-versus-aml-and-fraud",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "Screening for politically exposed persons (PEPs)",
      "href": "/2026/07/13/pep-screening",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "Screening governance, policy, and ownership",
      "href": "/2026/07/13/sanctions-screening-governance",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "Screening the payment message",
      "href": "/2026/07/13/screening-the-payment-message",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "Secondary identifiers and match confidence",
      "href": "/2026/07/13/secondary-identifiers-and-match-confidence",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "Sending money from India to the US: one remittance, start to finish",
      "href": "/2026/07/16/india-to-usa-outward-remittance",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "SEPA credit transfer – Four Corner model",
      "href": "/2026/07/13/sct-four-corner-model",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "Sepa Credit Transfer – Happy Path",
      "href": "/2026/07/13/sct-happy-path",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "SEPA Instant – Happy Path Flow",
      "href": "/2026/07/13/sepa-instant-happy-path-flow",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "SEPA Instant – Introduction",
      "href": "/2026/07/13/sepa-instant-introduction",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "SEPA Instant R-Message flows",
      "href": "/2026/07/13/sepa-instant-r-message-flows",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "SEPA Payment Messages",
      "href": "/2026/07/13/sepa-payment-messages",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "Serial and cover in ISO 20022: pacs.008 and pacs.009 COV",
      "href": "/2026/07/13/iso-20022-serial-and-cover",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "STEP2: the pan-European ACH",
      "href": "/2026/07/13/step2-pan-european-ach",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "Structured and hybrid addresses in ISO 20022",
      "href": "/2026/07/13/structured-and-hybrid-addresses-iso20022",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "Structured remittance information",
      "href": "/2026/07/13/structured-remittance-information",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "Suspicious activity reporting and escalation",
      "href": "/2026/07/13/suspicious-activity-reporting",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "SWIFT Cancellations and Investigation Messages",
      "href": "/2026/07/13/swift-cancellations-and-investigation-messages",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "SWIFT financial-institution funds transfers",
      "href": "/2026/07/13/swift-financial-institution-funds-transfers",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "SWIFT for trade finance",
      "href": "/2026/07/13/swift-for-trade-finance",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "SWIFT for treasury and securities",
      "href": "/2026/07/13/swift-for-treasury-and-securities",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "SWIFT hosted compliance services",
      "href": "/2026/07/13/swift-hosted-compliance-services",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "SWIFT message validation: mandatory and optional fields",
      "href": "/2026/07/13/swift-message-validation-and-fields",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "SWIFT MT – Payments Perspective",
      "href": "/2026/07/13/swift-mt-payments-perspective",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "SWIFT MT – Serial and Cover Method",
      "href": "/2026/07/13/swift-mt-serial-and-cover-method",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "SWIFT MT103",
      "href": "/2026/07/13/swift-mt-mt103",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "SWIFT MT1xx Customer Payment Messages",
      "href": "/2026/07/13/swift-mt1xx-customer-payment-messages",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "SWIFT MT2xx Financial Institution Messages",
      "href": "/2026/07/13/swift-mt2xx-financial-institution-messages",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "SWIFT MTs – Blocks 1 Through 5",
      "href": "/2026/07/13/swift-mts-blocks-1-through-5",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "SWIFT MTs – Key Details",
      "href": "/2026/07/13/swift-mts-key-details",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "SWIFT System and Service Messages",
      "href": "/2026/07/13/swift-system-and-service-messages",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "Testing and tuning a screening system",
      "href": "/2026/07/13/testing-and-tuning-screening",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "The annual Standards Release (MSR)",
      "href": "/2026/07/13/swift-message-standards-release",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "The Bodies Behind AML: FATF, FSRBs, Egmont, and Wolfsberg",
      "href": "/2026/07/13/aml-bodies-fatf-fsrb-egmont-wolfsberg",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "The Business Application Header (BAH)",
      "href": "/2026/07/13/the-business-application-header",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "The FATF framework",
      "href": "/2026/07/13/the-fatf-framework",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "The ISO 20022 message model",
      "href": "/2026/07/13/iso-20022-message-model",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "The real cost of payments",
      "href": "/2026/07/13/the-real-cost-of-payments",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "The risk-based approach to screening",
      "href": "/2026/07/13/risk-based-approach-to-screening",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "The sanctions screening lifecycle",
      "href": "/2026/07/13/the-sanctions-screening-lifecycle",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "The SWIFT KYC Registry",
      "href": "/2026/07/13/the-swift-kyc-registry",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "The SWIFT message categories",
      "href": "/2026/07/13/swift-message-categories-overview",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "The travel rule in payments",
      "href": "/2026/07/13/the-travel-rule-in-payments",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "Trade-Based Money Laundering: Value Hidden in Trade",
      "href": "/2026/07/13/trade-based-money-laundering",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "Translating MT to MX",
      "href": "/2026/07/13/mt-to-mx-translation",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "Types of lists in a screening product",
      "href": "/2026/07/13/types-of-lists-in-a-screening-product",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "What a payment declares about itself — and who carries it",
      "href": "/2026/07/16/iso-20022-payment-codes-and-agents",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "What sanctions are and why payments are screened",
      "href": "/2026/07/13/what-are-sanctions-in-payments",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "Who issues sanctions: regimes and authorities",
      "href": "/2026/07/13/sanctions-authorities-and-regimes",
      "coverage": "derived"
    },
    {
      "type": "flow",
      "label": "A Buna cross-border payment (Arab region RTGS)",
      "href": "/explore/buna",
      "coverage": "direct"
    },
    {
      "type": "flow",
      "label": "CBPR+ cross-border transfer (pacs.008)",
      "href": "/explore/cbpr-pacs008",
      "coverage": "direct"
    },
    {
      "type": "flow",
      "label": "SWIFT cover payment (MT103 + MT202 COV)",
      "href": "/explore/swift-cover",
      "coverage": "direct"
    },
    {
      "type": "flow",
      "label": "SWIFT serial payment (MT103)",
      "href": "/explore/swift-serial",
      "coverage": "direct"
    },
    {
      "type": "glossary",
      "label": "Adverse media",
      "href": "/glossary#adverse-media",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Alert",
      "href": "/glossary#alert",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Alias",
      "href": "/glossary#alias",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "ANSI X12 (X12/820)",
      "href": "/glossary#ansi-x12",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Asset freeze",
      "href": "/glossary#asset-freeze",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "BACS Standard 18",
      "href": "/glossary#bacs-standard-18",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Bank Payment Obligation (BPO)",
      "href": "/glossary#bank-payment-obligation",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Beneficial owner (UBO)",
      "href": "/glossary#beneficial-owner",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Book payment",
      "href": "/glossary#book-payment",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Business Application Header",
      "href": "/glossary#business-application-header",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Case management",
      "href": "/glossary#case-management",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Cash Transaction Report (CTR)",
      "href": "/glossary#cash-transaction-report",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "CBPR+",
      "href": "/glossary#cbpr-plus",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "CGI-MP (Common Global Implementation – Market Practice)",
      "href": "/glossary#cgi-mp",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Charge bearer",
      "href": "/glossary#charge-bearer",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Correspondent banking",
      "href": "/glossary#correspondent-banking",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Cover payment",
      "href": "/glossary#cover-payment",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "CRS (Common Reporting Standard)",
      "href": "/glossary#crs",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Customer due diligence (CDD)",
      "href": "/glossary#cdd",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Designated person",
      "href": "/glossary#designated-person",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Disposition",
      "href": "/glossary#disposition",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "DNFBP (Designated Non-Financial Business or Profession)",
      "href": "/glossary#dnfbp",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Documentary Credit",
      "href": "/glossary#documentary-credit",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Egmont Group",
      "href": "/glossary#egmont-group",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Enhanced due diligence (EDD)",
      "href": "/glossary#edd",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "False positive",
      "href": "/glossary#false-positive",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "FATCA (Foreign Account Tax Compliance Act)",
      "href": "/glossary#fatca",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "FATF (Financial Action Task Force)",
      "href": "/glossary#fatf",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Fifty percent rule",
      "href": "/glossary#fifty-percent-rule",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Financial intelligence unit (FIU)",
      "href": "/glossary#fiu",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "FSRB (FATF-Style Regional Body)",
      "href": "/glossary#fsrb",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Fuzzy matching",
      "href": "/glossary#fuzzy-matching",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Good-guy list",
      "href": "/glossary#good-guy-list",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "HVPS+",
      "href": "/glossary#hvps-plus",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Input credit file",
      "href": "/glossary#input-credit-file",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Instant payment",
      "href": "/glossary#instant-payment",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Intermediary agent",
      "href": "/glossary#intermediary-agent",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "ISO 20022",
      "href": "/glossary#iso-20022",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "ISO 8583",
      "href": "/glossary#iso-8583",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Know your customer (KYC)",
      "href": "/glossary#kyc",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "KYC Registry",
      "href": "/glossary#kyc-registry",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "LEI",
      "href": "/glossary#lei",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Loro account",
      "href": "/glossary#loro-account",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Message Category",
      "href": "/glossary#message-category",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Money laundering (ML)",
      "href": "/glossary#money-laundering",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Money laundering reporting officer (MLRO)",
      "href": "/glossary#mlro",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "MT message",
      "href": "/glossary#mt-message",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "MT102",
      "href": "/glossary#mt102",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "MT103",
      "href": "/glossary#mt103",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "MT104",
      "href": "/glossary#mt104",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "MT202",
      "href": "/glossary#mt202",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "MT202 COV",
      "href": "/glossary#mt202-cov",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "MT205",
      "href": "/glossary#mt205",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "MT210",
      "href": "/glossary#mt210",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "MX message",
      "href": "/glossary#mx-message",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Nested correspondent banking",
      "href": "/glossary#nested-correspondent",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Nostro account",
      "href": "/glossary#nostro-account",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "OFAC",
      "href": "/glossary#ofac",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "OFSI",
      "href": "/glossary#ofsi",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "On-us payment",
      "href": "/glossary#on-us-payment",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Ownership and control",
      "href": "/glossary#ownership-and-control",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "pacs family",
      "href": "/glossary#pacs",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "pacs.002",
      "href": "/glossary#pacs-002",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "pacs.004",
      "href": "/glossary#pacs-004",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "pacs.008",
      "href": "/glossary#pacs-008",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "pacs.009",
      "href": "/glossary#pacs-009",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Payment Controls Service (PCS)",
      "href": "/glossary#payment-controls-service",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "PEP",
      "href": "/glossary#pep",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Predicate offence",
      "href": "/glossary#predicate-offence",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Private list",
      "href": "/glossary#private-list",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Rescreening",
      "href": "/glossary#rescreening",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Sanctions",
      "href": "/glossary#sanctions",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Sanctions list",
      "href": "/glossary#sanctions-list",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Screening",
      "href": "/glossary#screening",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "SCT",
      "href": "/glossary#sct",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "SCT Inst",
      "href": "/glossary#sct-inst",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "SDN List",
      "href": "/glossary#sdn-list",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Sectoral sanctions",
      "href": "/glossary#sectoral-sanctions",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Serial payment",
      "href": "/glossary#serial-payment",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Structuring",
      "href": "/glossary#structuring",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Suspense account",
      "href": "/glossary#suspense-account",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Suspicious activity report (SAR)",
      "href": "/glossary#sar",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "System message (SWIFT Category 0)",
      "href": "/glossary#system-message",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Terrorist financing (TF)",
      "href": "/glossary#terrorist-financing",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Trade-based money laundering (TBML)",
      "href": "/glossary#trade-based-money-laundering",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Transliteration",
      "href": "/glossary#transliteration",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Travel rule",
      "href": "/glossary#travel-rule",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "True match",
      "href": "/glossary#true-match",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "UETR",
      "href": "/glossary#uetr",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "UN Security Council",
      "href": "/glossary#un-security-council",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "UN/EDIFACT",
      "href": "/glossary#edifact",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Vostro account",
      "href": "/glossary#vostro-account",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Watchlist",
      "href": "/glossary#watchlist",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Wire stripping",
      "href": "/glossary#wire-stripping",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Wolfsberg CBDDQ",
      "href": "/glossary#cbddq",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Wolfsberg Group",
      "href": "/glossary#wolfsberg-group",
      "coverage": "derived"
    },
    {
      "type": "mapping",
      "label": "MT103 /REJT/ convention → pacs.002",
      "href": "/messages/mappings/mt103-reject-to-pacs-002",
      "coverage": "direct"
    },
    {
      "type": "mapping",
      "label": "MT103 /RETN/ convention → pacs.004",
      "href": "/messages/mappings/mt103-return-to-pacs-004",
      "coverage": "direct"
    },
    {
      "type": "mapping",
      "label": "MT103 → pacs.008",
      "href": "/messages/mappings/mt103-to-pacs-008",
      "coverage": "direct"
    },
    {
      "type": "mapping",
      "label": "MT202 → pacs.009",
      "href": "/messages/mappings/mt202-to-pacs-009",
      "coverage": "direct"
    },
    {
      "type": "mapping",
      "label": "MT202 COV → pacs.009 COV",
      "href": "/messages/mappings/mt202cov-to-pacs-009cov",
      "coverage": "direct"
    },
    {
      "type": "message",
      "label": "MT103 — MT103 — Single Customer Credit Transfer",
      "href": "/messages/mt103",
      "coverage": "direct"
    },
    {
      "type": "message",
      "label": "MT202 COV — MT202 COV — General Financial Institution Transfer (Cover)",
      "href": "/messages/mt202-cov",
      "coverage": "direct"
    },
    {
      "type": "message",
      "label": "pacs.008 — pacs.008 — FI to FI Customer Credit Transfer",
      "href": "/messages/pacs-008",
      "coverage": "direct"
    },
    {
      "type": "message",
      "label": "pacs.009 — pacs.009 — Financial Institution Credit Transfer",
      "href": "/messages/pacs-009",
      "coverage": "direct"
    },
    {
      "type": "resource",
      "label": "CBPR+ implementation pack",
      "href": "/downloads/profile-packs/cbpr-plus",
      "coverage": "direct"
    },
    {
      "type": "resource",
      "label": "CBPR+ usage guidelines",
      "href": "/implementation-resources",
      "coverage": "direct"
    },
    {
      "type": "resource",
      "label": "CHAPS and RTGS ISO 20022 handbook and schema access",
      "href": "/implementation-resources",
      "coverage": "direct"
    },
    {
      "type": "resource",
      "label": "CHAPS RTGS implementation pack",
      "href": "/downloads/profile-packs/chaps",
      "coverage": "direct"
    },
    {
      "type": "resource",
      "label": "CHAPS RTGS implementation pack acceptance criteria",
      "href": "/downloads/assets/chaps-acceptance-criteria",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "CHAPS RTGS implementation pack BA checklist",
      "href": "/downloads/assets/chaps-ba-checklist",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "CHAPS RTGS implementation pack field and process matrix",
      "href": "/downloads/assets/chaps-profile-rules",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "CHAPS RTGS implementation pack migration notes",
      "href": "/downloads/assets/chaps-migration-notes",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "CHAPS RTGS implementation pack restricted and release-specific gaps",
      "href": "/downloads/assets/chaps-coverage-gaps",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "CHAPS RTGS implementation pack test cases",
      "href": "/downloads/assets/chaps-test-cases",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "CHIPS implementation pack",
      "href": "/downloads/profile-packs/chips",
      "coverage": "direct"
    },
    {
      "type": "resource",
      "label": "CHIPS implementation pack acceptance criteria",
      "href": "/downloads/assets/chips-acceptance-criteria",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "CHIPS implementation pack BA checklist",
      "href": "/downloads/assets/chips-ba-checklist",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "CHIPS implementation pack field and process matrix",
      "href": "/downloads/assets/chips-profile-rules",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "CHIPS implementation pack migration notes",
      "href": "/downloads/assets/chips-migration-notes",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "CHIPS implementation pack restricted and release-specific gaps",
      "href": "/downloads/assets/chips-coverage-gaps",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "CHIPS implementation pack test cases",
      "href": "/downloads/assets/chips-test-cases",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "CHIPS ISO 20022 usage-guideline resources and rules",
      "href": "/implementation-resources",
      "coverage": "direct"
    },
    {
      "type": "resource",
      "label": "Corporate MX positive lifecycle — ZIP pack",
      "href": "/downloads/packs/corporate-mx-positive",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "Fedwire Funds Service implementation pack",
      "href": "/downloads/profile-packs/fedwire",
      "coverage": "direct"
    },
    {
      "type": "resource",
      "label": "Fedwire Funds Service implementation pack acceptance criteria",
      "href": "/downloads/assets/fedwire-acceptance-criteria",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "Fedwire Funds Service implementation pack BA checklist",
      "href": "/downloads/assets/fedwire-ba-checklist",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "Fedwire Funds Service implementation pack field and process matrix",
      "href": "/downloads/assets/fedwire-profile-rules",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "Fedwire Funds Service implementation pack migration notes",
      "href": "/downloads/assets/fedwire-migration-notes",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "Fedwire Funds Service implementation pack restricted and release-specific gaps",
      "href": "/downloads/assets/fedwire-coverage-gaps",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "Fedwire Funds Service implementation pack test cases",
      "href": "/downloads/assets/fedwire-test-cases",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "Fedwire Funds Service ISO 20022 implementation and technical documents",
      "href": "/implementation-resources",
      "coverage": "direct"
    },
    {
      "type": "resource",
      "label": "High-value payments implementation pack",
      "href": "/downloads/profile-packs/high-value",
      "coverage": "direct"
    },
    {
      "type": "resource",
      "label": "HVPS+ usage guidelines",
      "href": "/implementation-resources",
      "coverage": "direct"
    },
    {
      "type": "resource",
      "label": "ISO 20022 message definitions and XSDs",
      "href": "/implementation-resources",
      "coverage": "direct"
    },
    {
      "type": "resource",
      "label": "MT legacy and migration lifecycle — ZIP pack",
      "href": "/downloads/packs/mt-legacy-migration",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "MT to MX migration notes",
      "href": "/downloads/assets/mt-mx-migration-notes",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "MT103 /REJT/ convention → pacs.002 implementation mapping",
      "href": "/downloads/assets/mapping-mt103-reject-to-pacs-002",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "MT103 /RETN/ convention → pacs.004 implementation mapping",
      "href": "/downloads/assets/mapping-mt103-return-to-pacs-004",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "MT103 → pacs.008 implementation mapping",
      "href": "/downloads/assets/mapping-mt103-to-pacs-008",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "MT103 customer credit transfer — raw FIN",
      "href": "/downloads/samples/mt103",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "MT103 field matrix",
      "href": "/downloads/assets/field-matrix-mt103",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "MT103 rejection convention — raw FIN",
      "href": "/downloads/samples/mt103-reject",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "MT103 return convention — raw FIN",
      "href": "/downloads/samples/mt103-return",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "MT202 → pacs.009 implementation mapping",
      "href": "/downloads/assets/mapping-mt202-to-pacs-009",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "MT202 COV → pacs.009 COV implementation mapping",
      "href": "/downloads/assets/mapping-mt202cov-to-pacs-009cov",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "MT202 COV cover payment — raw FIN",
      "href": "/downloads/samples/mt202cov",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "MT202 COV field matrix",
      "href": "/downloads/assets/field-matrix-mt202cov",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "MT202 field matrix",
      "href": "/downloads/assets/field-matrix-mt202",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "pacs.002 field matrix",
      "href": "/downloads/assets/field-matrix-pacs-002",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "pacs.004 field matrix",
      "href": "/downloads/assets/field-matrix-pacs-004",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "pacs.008 FI-to-FI credit transfer — raw XML",
      "href": "/downloads/samples/pacs-008",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "pacs.008 field matrix",
      "href": "/downloads/assets/field-matrix-pacs-008",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "pacs.009 COV financial institution transfer — raw XML",
      "href": "/downloads/samples/pacs-009",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "pacs.009 field matrix",
      "href": "/downloads/assets/field-matrix-pacs-009",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "Payment lifecycle test cases",
      "href": "/downloads/assets/payment-lifecycle-test-cases",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "PMPG correspondent-payment and reporting market practice",
      "href": "/implementation-resources",
      "coverage": "direct"
    },
    {
      "type": "resource",
      "label": "SEPA Credit Transfer implementation guidelines",
      "href": "/implementation-resources",
      "coverage": "direct"
    },
    {
      "type": "resource",
      "label": "SEPA Credit Transfer rulebook",
      "href": "/implementation-resources",
      "coverage": "direct"
    },
    {
      "type": "resource",
      "label": "SEPA credit-transfer implementation pack",
      "href": "/downloads/profile-packs/sepa-credit",
      "coverage": "direct"
    },
    {
      "type": "resource",
      "label": "SEPA Instant Credit Transfer implementation guidelines and XSDs",
      "href": "/implementation-resources",
      "coverage": "direct"
    },
    {
      "type": "resource",
      "label": "SEPA Instant Credit Transfer rulebook",
      "href": "/implementation-resources",
      "coverage": "direct"
    },
    {
      "type": "resource",
      "label": "Swift Standards MT release material",
      "href": "/implementation-resources",
      "coverage": "direct"
    },
    {
      "type": "resource",
      "label": "T2 functional specifications, validation rules, and binding XSDs",
      "href": "/implementation-resources",
      "coverage": "direct"
    },
    {
      "type": "resource",
      "label": "T2 RTGS implementation pack",
      "href": "/downloads/profile-packs/t2",
      "coverage": "direct"
    },
    {
      "type": "resource",
      "label": "T2 RTGS implementation pack acceptance criteria",
      "href": "/downloads/assets/t2-acceptance-criteria",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "T2 RTGS implementation pack BA checklist",
      "href": "/downloads/assets/t2-ba-checklist",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "T2 RTGS implementation pack field and process matrix",
      "href": "/downloads/assets/t2-profile-rules",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "T2 RTGS implementation pack migration notes",
      "href": "/downloads/assets/t2-migration-notes",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "T2 RTGS implementation pack restricted and release-specific gaps",
      "href": "/downloads/assets/t2-coverage-gaps",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "T2 RTGS implementation pack test cases",
      "href": "/downloads/assets/t2-test-cases",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "TIPS instant-settlement implementation pack",
      "href": "/downloads/profile-packs/tips",
      "coverage": "direct"
    },
    {
      "type": "resource",
      "label": "TIPS instant-settlement implementation pack acceptance criteria",
      "href": "/downloads/assets/tips-acceptance-criteria",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "TIPS instant-settlement implementation pack BA checklist",
      "href": "/downloads/assets/tips-ba-checklist",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "TIPS instant-settlement implementation pack field and process matrix",
      "href": "/downloads/assets/tips-profile-rules",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "TIPS instant-settlement implementation pack migration notes",
      "href": "/downloads/assets/tips-migration-notes",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "TIPS instant-settlement implementation pack restricted and release-specific gaps",
      "href": "/downloads/assets/tips-coverage-gaps",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "TIPS instant-settlement implementation pack test cases",
      "href": "/downloads/assets/tips-test-cases",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "TIPS release specifications and professional-use documentation",
      "href": "/implementation-resources",
      "coverage": "direct"
    },
    {
      "type": "sample",
      "label": "MT103 customer credit transfer",
      "href": "/message-samples/mt103",
      "coverage": "derived"
    },
    {
      "type": "sample",
      "label": "MT103 rejection convention",
      "href": "/message-samples/mt103-reject",
      "coverage": "derived"
    },
    {
      "type": "sample",
      "label": "MT103 return convention",
      "href": "/message-samples/mt103-return",
      "coverage": "derived"
    },
    {
      "type": "sample",
      "label": "MT202 COV cover payment",
      "href": "/message-samples/mt202cov",
      "coverage": "derived"
    },
    {
      "type": "sample",
      "label": "pacs.008 FI-to-FI credit transfer",
      "href": "/message-samples/pacs-008",
      "coverage": "derived"
    },
    {
      "type": "sample",
      "label": "pacs.009 COV financial institution transfer",
      "href": "/message-samples/pacs-009",
      "coverage": "derived"
    },
    {
      "type": "scenario",
      "label": "A clean pass through the filter",
      "href": "/screening/lab/clean-pass",
      "coverage": "derived"
    },
    {
      "type": "scenario",
      "label": "A common surname collides with the list",
      "href": "/screening/lab/name-collision-false-positive",
      "coverage": "derived"
    },
    {
      "type": "scenario",
      "label": "Not on the list, still blocked: ownership adds up",
      "href": "/screening/lab/ownership-escalation",
      "coverage": "derived"
    },
    {
      "type": "scenario",
      "label": "Strong name, wrong person: identifiers decide",
      "href": "/screening/lab/secondary-identifier-clear",
      "coverage": "derived"
    },
    {
      "type": "scenario",
      "label": "The alias that was the real name",
      "href": "/screening/lab/alias-true-match",
      "coverage": "derived"
    },
    {
      "type": "scenario",
      "label": "The hit hiding in the remittance line",
      "href": "/screening/lab/free-text-message-hit",
      "coverage": "derived"
    },
    {
      "type": "topic",
      "label": "Accounting entries and ledgers",
      "href": "/learn/operations/accounting-entries-and-ledgers",
      "coverage": "direct"
    },
    {
      "type": "topic",
      "label": "Aggregation and provenance",
      "href": "/screening/list-data/aggregation-and-provenance",
      "coverage": "derived"
    },
    {
      "type": "topic",
      "label": "Alert investigation and false positives",
      "href": "/screening/governance/alert-investigation-and-false-positives",
      "coverage": "derived"
    },
    {
      "type": "topic",
      "label": "Anatomy of a sanctions list",
      "href": "/screening/list-data/anatomy-of-a-sanctions-list",
      "coverage": "derived"
    },
    {
      "type": "topic",
      "label": "Asset freezes and restrictions",
      "href": "/screening/foundations/asset-freezes-and-restrictions",
      "coverage": "derived"
    },
    {
      "type": "topic",
      "label": "CBPR+: ISO 20022 for cross-border payments",
      "href": "/learn/iso-20022/cbpr-plus-cross-border",
      "coverage": "derived"
    },
    {
      "type": "topic",
      "label": "Charges and foreign exchange",
      "href": "/learn/foundations/charges-and-fx",
      "coverage": "derived"
    },
    {
      "type": "topic",
      "label": "Correspondent banking, nostro & vostro",
      "href": "/learn/foundations/correspondent-banking-nostro-vostro",
      "coverage": "derived"
    },
    {
      "type": "topic",
      "label": "Customer vs transaction screening",
      "href": "/screening/execution/customer-vs-transaction-screening",
      "coverage": "derived"
    },
    {
      "type": "topic",
      "label": "Governance and policy",
      "href": "/screening/governance/governance-and-policy",
      "coverage": "derived"
    },
    {
      "type": "topic",
      "label": "How a payment declares what it is",
      "href": "/learn/iso-20022/payment-type-and-codes",
      "coverage": "derived"
    },
    {
      "type": "topic",
      "label": "Identifiers and data quality",
      "href": "/screening/list-data/identifiers-and-data-quality",
      "coverage": "derived"
    },
    {
      "type": "topic",
      "label": "List delivery and updates",
      "href": "/screening/list-data/list-delivery-and-updates",
      "coverage": "derived"
    },
    {
      "type": "topic",
      "label": "Money laundering, terrorist financing, and FATF",
      "href": "/screening/foundations/money-laundering-and-fatf",
      "coverage": "derived"
    },
    {
      "type": "topic",
      "label": "MT message structure",
      "href": "/learn/swift-mt/mt-message-structure",
      "coverage": "derived"
    },
    {
      "type": "topic",
      "label": "MT-to-MX translation and truncation",
      "href": "/learn/iso-20022/mt-mx-translation-and-truncation",
      "coverage": "derived"
    },
    {
      "type": "topic",
      "label": "MT103: the customer credit transfer",
      "href": "/learn/swift-mt/mt103-customer-credit-transfer",
      "coverage": "derived"
    },
    {
      "type": "topic",
      "label": "MT202 and MT202 COV",
      "href": "/learn/swift-mt/mt202-and-mt202cov",
      "coverage": "derived"
    },
    {
      "type": "topic",
      "label": "Name matching and fuzzy logic",
      "href": "/screening/execution/name-matching-and-fuzzy-logic",
      "coverage": "derived"
    },
    {
      "type": "topic",
      "label": "Payment transparency and the travel rule",
      "href": "/screening/execution/payment-transparency-and-travel-rule",
      "coverage": "derived"
    },
    {
      "type": "topic",
      "label": "Risk-based screening",
      "href": "/screening/foundations/risk-based-screening",
      "coverage": "derived"
    },
    {
      "type": "topic",
      "label": "Sanctions screening vs AML vs fraud",
      "href": "/screening/foundations/sanctions-vs-aml-vs-fraud",
      "coverage": "derived"
    },
    {
      "type": "topic",
      "label": "Screening payment messages",
      "href": "/screening/execution/screening-payment-messages",
      "coverage": "derived"
    },
    {
      "type": "topic",
      "label": "Screening system architecture",
      "href": "/screening/execution/screening-architecture",
      "coverage": "direct"
    },
    {
      "type": "topic",
      "label": "SCT Inst: instant payments",
      "href": "/learn/sepa/sct-inst-instant-payments",
      "coverage": "derived"
    },
    {
      "type": "topic",
      "label": "Secondary identifiers and confidence",
      "href": "/screening/execution/secondary-identifiers-and-confidence",
      "coverage": "derived"
    },
    {
      "type": "topic",
      "label": "Serial versus cover routing",
      "href": "/learn/swift-mt/serial-vs-cover-routing",
      "coverage": "derived"
    },
    {
      "type": "topic",
      "label": "Testing and tuning",
      "href": "/screening/governance/testing-and-tuning",
      "coverage": "derived"
    },
    {
      "type": "topic",
      "label": "The ISO 20022 message model",
      "href": "/learn/iso-20022/iso-20022-message-model-and-xml",
      "coverage": "derived"
    },
    {
      "type": "topic",
      "label": "The pacs family: interbank messages",
      "href": "/learn/iso-20022/pacs-family-interbank-messages",
      "coverage": "derived"
    },
    {
      "type": "topic",
      "label": "The screening lifecycle",
      "href": "/screening/execution/screening-lifecycle",
      "coverage": "derived"
    },
    {
      "type": "topic",
      "label": "The SCT lifecycle",
      "href": "/learn/sepa/sct-lifecycle",
      "coverage": "derived"
    },
    {
      "type": "topic",
      "label": "What sanctions are",
      "href": "/screening/foundations/what-sanctions-are",
      "coverage": "derived"
    },
    {
      "type": "topic",
      "label": "Who imposes sanctions",
      "href": "/screening/foundations/sanctions-authorities",
      "coverage": "derived"
    }
  ]
}