{
  "generatedFrom": "Payments Signal canonical architecture registry",
  "reviewDate": "2026-07-23",
  "blueprint": {
    "id": "architecture-payment-operations",
    "slug": "payment-operations-exceptions-investigations-reconciliation",
    "title": "Payment operations, exceptions, investigations, reconciliation, reporting, and case management",
    "shortTitle": "Payment operations",
    "family": "controls",
    "summary": "Give operators one evidence-based view of payment state, settlement, messages, books, ownership, and safe next action.",
    "audience": "Payment operations, investigations, reconciliation, service management, product, architecture, and business-analysis teams.",
    "reviewDate": "2026-07-23",
    "versionLabel": "Payments Signal reference architecture v1",
    "status": "current",
    "nodes": [
      {
        "id": "ops-state-view",
        "title": "Canonical payment and lifecycle view",
        "kind": "data-store",
        "summary": "Combines business, message, rail, settlement, posting, return, and investigation states without collapsing them into one flag.",
        "responsibilities": [
          "Preserve every state transition and source",
          "Show last confirmed state and uncertainty explicitly"
        ],
        "owner": "Payment platform and operations data owner",
        "inputs": [
          "Authorised business instruction and correlated state"
        ],
        "outputs": [
          "Versioned result, status, and audit evidence"
        ],
        "interfaceContracts": [
          "Versioned canonical payment and lifecycle view contract",
          "Stable identifier, state, error, and audit contract"
        ],
        "controls": [
          "Stable identifiers",
          "Source precedence",
          "No inferred settlement from delivery"
        ],
        "failureModes": [
          "Conflicting statuses",
          "Late event moves state backward",
          "Missing lineage"
        ],
        "recovery": [
          "Quarantine conflict",
          "Rebuild from immutable events",
          "Escalate unresolved settlement state"
        ],
        "lenses": [
          "applications",
          "interfaces",
          "data",
          "controls",
          "operations",
          "resilience"
        ],
        "evidence": [
          {
            "ref": {
              "sourceId": "payments-signal-editorial",
              "locator": "Payment operations, exception, and investigation architecture",
              "label": "simplified-educational-illustration",
              "simplifications": "Queues, statuses, repair rights, investigation messages, service levels, operational roles, customer communication, and accounting action depend on the institution, rail, scheme, message profile, and legal context."
            },
            "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": "ops-monitoring",
        "title": "Operational monitoring and work queues",
        "kind": "application",
        "summary": "Turns failed controls, ageing items, deadline risk, and service degradation into owned work.",
        "responsibilities": [
          "Prioritise by financial and customer risk",
          "Separate noise from an actionable payment case"
        ],
        "owner": "Payment operations and service management",
        "inputs": [
          "Authorised business instruction and correlated state"
        ],
        "outputs": [
          "Versioned result, status, and audit evidence"
        ],
        "interfaceContracts": [
          "Versioned operational monitoring and work queues contract",
          "Stable identifier, state, error, and audit contract"
        ],
        "controls": [
          "Queue completeness",
          "Ageing and cut-off",
          "Owner and escalation",
          "No silent suppression"
        ],
        "failureModes": [
          "Alert storm",
          "Important item buried",
          "Unowned queue"
        ],
        "recovery": [
          "Apply documented degradation controls",
          "Rebuild queue from source events",
          "Escalate by materiality and deadline"
        ],
        "lenses": [
          "applications",
          "interfaces",
          "data",
          "controls",
          "operations",
          "resilience"
        ],
        "evidence": [
          {
            "ref": {
              "sourceId": "payments-signal-editorial",
              "locator": "Payment operations, exception, and investigation architecture",
              "label": "simplified-educational-illustration",
              "simplifications": "Queues, statuses, repair rights, investigation messages, service levels, operational roles, customer communication, and accounting action depend on the institution, rail, scheme, message profile, and legal context."
            },
            "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": "ops-case",
        "title": "Payment case and evidence workspace",
        "kind": "operations",
        "summary": "Keeps one case linked to the payment, messages, journal entries, statements, customer communication, decisions, and deadlines.",
        "responsibilities": [
          "Create one accountable case",
          "Record evidence, hypothesis, action, and decision separately"
        ],
        "owner": "Payment investigations",
        "inputs": [
          "Authorised business instruction and correlated state"
        ],
        "outputs": [
          "Versioned result, status, and audit evidence"
        ],
        "interfaceContracts": [
          "Versioned payment case and evidence workspace contract",
          "Stable identifier, state, error, and audit contract"
        ],
        "controls": [
          "Least privilege",
          "Immutable audit trail",
          "No sensitive data in free-form exports"
        ],
        "failureModes": [
          "Duplicate cases",
          "Evidence copied out of context",
          "Case closed without settlement proof"
        ],
        "recovery": [
          "Merge without losing history",
          "Reopen from retained evidence",
          "Escalate data exposure"
        ],
        "lenses": [
          "applications",
          "interfaces",
          "data",
          "controls",
          "operations",
          "resilience"
        ],
        "evidence": [
          {
            "ref": {
              "sourceId": "payments-signal-editorial",
              "locator": "Payment operations, exception, and investigation architecture",
              "label": "simplified-educational-illustration",
              "simplifications": "Queues, statuses, repair rights, investigation messages, service levels, operational roles, customer communication, and accounting action depend on the institution, rail, scheme, message profile, and legal context."
            },
            "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": "ops-repair",
        "title": "Repair, retry, replay, and release control",
        "kind": "control",
        "summary": "Chooses an allowed recovery action from the last confirmed business and settlement state.",
        "responsibilities": [
          "Distinguish retry from replay, repair, reversal, return, recall, and cancellation",
          "Require the right authority and evidence for value-affecting action"
        ],
        "owner": "Payment operations with product and control authority",
        "inputs": [
          "Authorised business instruction and correlated state"
        ],
        "outputs": [
          "Versioned result, status, and audit evidence"
        ],
        "interfaceContracts": [
          "Versioned repair, retry, replay, and release control contract",
          "Stable identifier, state, error, and audit contract"
        ],
        "controls": [
          "Idempotency",
          "Maker-checker",
          "Settlement-state guard",
          "Original identifier linkage"
        ],
        "failureModes": [
          "Duplicate payment",
          "Unauthorised manual repair",
          "Reversal after final settlement"
        ],
        "recovery": [
          "Stop further action",
          "Trace every attempt",
          "Use the applicable return or investigation process"
        ],
        "lenses": [
          "applications",
          "interfaces",
          "data",
          "controls",
          "operations",
          "resilience"
        ],
        "evidence": [
          {
            "ref": {
              "sourceId": "payments-signal-editorial",
              "locator": "Payment operations, exception, and investigation architecture",
              "label": "simplified-educational-illustration",
              "simplifications": "Queues, statuses, repair rights, investigation messages, service levels, operational roles, customer communication, and accounting action depend on the institution, rail, scheme, message profile, and legal context."
            },
            "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": "ops-network-case",
        "title": "Network and counterparty investigations",
        "kind": "gateway",
        "summary": "Exchanges status requests, cancellation requests, responses, claims, and supporting information with counterparties.",
        "responsibilities": [
          "Choose the correct message and process",
          "Track request, response, timeout, and ownership"
        ],
        "owner": "Payment investigations and correspondent operations",
        "inputs": [
          "Authorised business instruction and correlated state"
        ],
        "outputs": [
          "Versioned result, status, and audit evidence"
        ],
        "interfaceContracts": [
          "Versioned network and counterparty investigations contract",
          "Stable identifier, state, error, and audit contract"
        ],
        "controls": [
          "Counterparty and route authority",
          "Message profile validation",
          "Case correlation",
          "Deadline"
        ],
        "failureModes": [
          "Request sent to wrong party",
          "Duplicate recall",
          "Response not linked"
        ],
        "recovery": [
          "Correct route with a new linked action",
          "Do not erase the original request"
        ],
        "lenses": [
          "applications",
          "interfaces",
          "data",
          "controls",
          "operations",
          "resilience"
        ],
        "evidence": [
          {
            "ref": {
              "sourceId": "payments-signal-editorial",
              "locator": "Payment operations, exception, and investigation architecture",
              "label": "simplified-educational-illustration",
              "simplifications": "Queues, statuses, repair rights, investigation messages, service levels, operational roles, customer communication, and accounting action depend on the institution, rail, scheme, message profile, and legal context."
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "Payments Signal reference architecture v1"
          }
        ],
        "messageIds": [
          "camt-055",
          "camt-056",
          "camt-029",
          "camt-110",
          "camt-111",
          "mt192",
          "mt195",
          "mt196",
          "mt199"
        ],
        "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": "ops-recon",
        "title": "Payment, settlement, and account reconciliation",
        "kind": "control",
        "summary": "Matches instruction, status, settlement, posting, statement, fee, and return evidence.",
        "responsibilities": [
          "Classify timing versus financial breaks",
          "Keep unmatched cash and unmatched instruction distinct"
        ],
        "owner": "Payments reconciliation and treasury operations",
        "inputs": [
          "Authorised business instruction and correlated state"
        ],
        "outputs": [
          "Versioned result, status, and audit evidence"
        ],
        "interfaceContracts": [
          "Versioned payment, settlement, and account reconciliation contract",
          "Stable identifier, state, error, and audit contract"
        ],
        "controls": [
          "Completeness totals",
          "Stable matching grain",
          "Ageing",
          "No unsupported net-off"
        ],
        "failureModes": [
          "False match",
          "Aged nostro break",
          "Return not linked to original"
        ],
        "recovery": [
          "Undo false match",
          "Open a case with exact value and evidence",
          "Correct through approved books"
        ],
        "lenses": [
          "applications",
          "interfaces",
          "data",
          "controls",
          "operations",
          "resilience"
        ],
        "evidence": [
          {
            "ref": {
              "sourceId": "payments-signal-editorial",
              "locator": "Payment operations, exception, and investigation architecture",
              "label": "simplified-educational-illustration",
              "simplifications": "Queues, statuses, repair rights, investigation messages, service levels, operational roles, customer communication, and accounting action depend on the institution, rail, scheme, message profile, and legal context."
            },
            "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": "ops-reporting",
        "title": "Customer, management, and regulatory reporting",
        "kind": "service",
        "summary": "Produces accurate status, advice, statements, service metrics, incident information, and required reports from governed state.",
        "responsibilities": [
          "Use the authoritative state for each report",
          "Explain provisional, rejected, returned, recalled, and settled states plainly"
        ],
        "owner": "Operations reporting, product, finance, and compliance",
        "inputs": [
          "Authorised business instruction and correlated state"
        ],
        "outputs": [
          "Versioned result, status, and audit evidence"
        ],
        "interfaceContracts": [
          "Versioned customer, management, and regulatory reporting contract",
          "Stable identifier, state, error, and audit contract"
        ],
        "controls": [
          "Data lineage",
          "Report completeness",
          "Access and privacy",
          "Revision control"
        ],
        "failureModes": [
          "Customer told paid while settlement is unknown",
          "Statement omits correction",
          "Metrics hide deferred cases"
        ],
        "recovery": [
          "Correct and reissue with lineage",
          "Notify affected owners",
          "Preserve the original report"
        ],
        "lenses": [
          "applications",
          "interfaces",
          "data",
          "controls",
          "operations",
          "resilience"
        ],
        "evidence": [
          {
            "ref": {
              "sourceId": "payments-signal-editorial",
              "locator": "Payment operations, exception, and investigation architecture",
              "label": "simplified-educational-illustration",
              "simplifications": "Queues, statuses, repair rights, investigation messages, service levels, operational roles, customer communication, and accounting action depend on the institution, rail, scheme, message profile, and legal context."
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "Payments Signal reference architecture v1"
          }
        ],
        "messageIds": [
          "pain-002",
          "pacs-002",
          "camt-052",
          "camt-053",
          "camt-054"
        ],
        "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": "ops-command",
        "title": "Incident command and service recovery",
        "kind": "operations",
        "summary": "Coordinates technical recovery, payment-state control, stakeholder decisions, communication, and post-incident action.",
        "responsibilities": [
          "Name one incident authority",
          "Separate platform recovery from payment and settlement recovery"
        ],
        "owner": "Service owner and incident commander",
        "inputs": [
          "Authorised business instruction and correlated state"
        ],
        "outputs": [
          "Versioned result, status, and audit evidence"
        ],
        "interfaceContracts": [
          "Versioned incident command and service recovery contract",
          "Stable identifier, state, error, and audit contract"
        ],
        "controls": [
          "Situation log",
          "Change freeze",
          "Recovery checkpoint",
          "Business validation before reopen"
        ],
        "failureModes": [
          "Systems restored but queues replay unsafely",
          "Conflicting teams act on the same payment",
          "Customer communication outruns evidence"
        ],
        "recovery": [
          "Pause value-affecting automation",
          "Reconcile from the last consistent boundary",
          "Reopen in controlled stages"
        ],
        "lenses": [
          "applications",
          "interfaces",
          "data",
          "controls",
          "operations",
          "resilience"
        ],
        "evidence": [
          {
            "ref": {
              "sourceId": "bis-cpmi-pfmi",
              "locator": "Principle 17",
              "label": "official-requirement"
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "CPMI-IOSCO Principles for financial market infrastructures"
          },
          {
            "ref": {
              "sourceId": "bis-cpmi-cyber-resilience",
              "locator": "Response, recovery, and learning",
              "label": "official-requirement"
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "CPMI-IOSCO cyber-resilience guidance"
          }
        ],
        "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": "ops-e1",
        "from": "ops-state-view",
        "to": "ops-monitoring",
        "title": "Operational event and ageing signal",
        "kind": "event",
        "mode": "asynchronous",
        "purpose": "Create owned work from governed state and time thresholds.",
        "failureBehaviour": "Rebuild the queue from source state after delivery failure.",
        "evidence": [
          {
            "ref": {
              "sourceId": "payments-signal-editorial",
              "locator": "Payment operations, exception, and investigation architecture",
              "label": "simplified-educational-illustration",
              "simplifications": "Queues, statuses, repair rights, investigation messages, service levels, operational roles, customer communication, and accounting action depend on the institution, rail, scheme, message profile, and legal context."
            },
            "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": "ops-e2",
        "from": "ops-monitoring",
        "to": "ops-case",
        "title": "Case trigger",
        "kind": "operator",
        "mode": "operator",
        "purpose": "Open one case with priority, owner, and source evidence.",
        "failureBehaviour": "Deduplicate without removing previous decisions.",
        "evidence": [
          {
            "ref": {
              "sourceId": "payments-signal-editorial",
              "locator": "Payment operations, exception, and investigation architecture",
              "label": "simplified-educational-illustration",
              "simplifications": "Queues, statuses, repair rights, investigation messages, service levels, operational roles, customer communication, and accounting action depend on the institution, rail, scheme, message profile, and legal context."
            },
            "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": "ops-e3",
        "from": "ops-case",
        "to": "ops-repair",
        "title": "Authorised recovery request",
        "kind": "control",
        "mode": "operator",
        "purpose": "Request a bounded repair, retry, replay, release, return, or reversal.",
        "failureBehaviour": "Reject action without authority or settlement evidence.",
        "evidence": [
          {
            "ref": {
              "sourceId": "payments-signal-editorial",
              "locator": "Payment operations, exception, and investigation architecture",
              "label": "simplified-educational-illustration",
              "simplifications": "Queues, statuses, repair rights, investigation messages, service levels, operational roles, customer communication, and accounting action depend on the institution, rail, scheme, message profile, and legal context."
            },
            "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": "ops-e4",
        "from": "ops-repair",
        "to": "ops-state-view",
        "title": "Recovery state event",
        "kind": "event",
        "mode": "asynchronous",
        "purpose": "Record the action and resulting state once.",
        "failureBehaviour": "Reconcile after uncertain action rather than issuing another.",
        "evidence": [
          {
            "ref": {
              "sourceId": "payments-signal-editorial",
              "locator": "Payment operations, exception, and investigation architecture",
              "label": "simplified-educational-illustration",
              "simplifications": "Queues, statuses, repair rights, investigation messages, service levels, operational roles, customer communication, and accounting action depend on the institution, rail, scheme, message profile, and legal context."
            },
            "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": "ops-e5",
        "from": "ops-case",
        "to": "ops-network-case",
        "title": "Investigation or cancellation message",
        "kind": "message",
        "mode": "asynchronous",
        "purpose": "Exchange a correlated request with the correct counterparty.",
        "messageIds": [
          "camt-056",
          "camt-029",
          "camt-110",
          "camt-111"
        ],
        "failureBehaviour": "Age and escalate missing or contradictory responses.",
        "evidence": [
          {
            "ref": {
              "sourceId": "payments-signal-editorial",
              "locator": "Payment operations, exception, and investigation architecture",
              "label": "simplified-educational-illustration",
              "simplifications": "Queues, statuses, repair rights, investigation messages, service levels, operational roles, customer communication, and accounting action depend on the institution, rail, scheme, message profile, and legal context."
            },
            "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": "ops-e6",
        "from": "ops-network-case",
        "to": "ops-state-view",
        "title": "Counterparty response",
        "kind": "message",
        "mode": "asynchronous",
        "purpose": "Add sourced external state without overwriting internal evidence.",
        "messageIds": [
          "camt-029",
          "camt-111",
          "mt196",
          "mt199"
        ],
        "failureBehaviour": "Keep contradictions visible until resolved.",
        "evidence": [
          {
            "ref": {
              "sourceId": "payments-signal-editorial",
              "locator": "Payment operations, exception, and investigation architecture",
              "label": "simplified-educational-illustration",
              "simplifications": "Queues, statuses, repair rights, investigation messages, service levels, operational roles, customer communication, and accounting action depend on the institution, rail, scheme, message profile, and legal context."
            },
            "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": "ops-e7",
        "from": "ops-state-view",
        "to": "ops-recon",
        "title": "Payment and posting lineage",
        "kind": "event",
        "mode": "asynchronous",
        "purpose": "Provide the instruction, state, journal, settlement, and return chain.",
        "failureBehaviour": "Stop matching when lineage or completeness is missing.",
        "evidence": [
          {
            "ref": {
              "sourceId": "payments-signal-editorial",
              "locator": "Payment operations, exception, and investigation architecture",
              "label": "simplified-educational-illustration",
              "simplifications": "Queues, statuses, repair rights, investigation messages, service levels, operational roles, customer communication, and accounting action depend on the institution, rail, scheme, message profile, and legal context."
            },
            "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": "ops-e8",
        "from": "ops-recon",
        "to": "ops-case",
        "title": "Reconciliation break",
        "kind": "operator",
        "mode": "operator",
        "purpose": "Create a material, aged, evidence-rich financial case.",
        "failureBehaviour": "Do not auto-close an unmatched cash movement.",
        "evidence": [
          {
            "ref": {
              "sourceId": "payments-signal-editorial",
              "locator": "Payment operations, exception, and investigation architecture",
              "label": "simplified-educational-illustration",
              "simplifications": "Queues, statuses, repair rights, investigation messages, service levels, operational roles, customer communication, and accounting action depend on the institution, rail, scheme, message profile, and legal context."
            },
            "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": "ops-e9",
        "from": "ops-state-view",
        "to": "ops-reporting",
        "title": "Governed reporting state",
        "kind": "api",
        "mode": "asynchronous",
        "purpose": "Publish customer and management reporting from authoritative state.",
        "failureBehaviour": "Correct reports with traceable revisions.",
        "evidence": [
          {
            "ref": {
              "sourceId": "payments-signal-editorial",
              "locator": "Payment operations, exception, and investigation architecture",
              "label": "simplified-educational-illustration",
              "simplifications": "Queues, statuses, repair rights, investigation messages, service levels, operational roles, customer communication, and accounting action depend on the institution, rail, scheme, message profile, and legal context."
            },
            "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": "ops-e10",
        "from": "ops-command",
        "to": "ops-repair",
        "title": "Incident recovery authority",
        "kind": "control",
        "mode": "operator",
        "purpose": "Constrain replay and reopening during a service incident.",
        "failureBehaviour": "Block bulk replay until the last consistent checkpoint is proven.",
        "evidence": [
          {
            "ref": {
              "sourceId": "bis-cpmi-pfmi",
              "locator": "Principle 17",
              "label": "official-requirement"
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "CPMI-IOSCO Principles for financial market infrastructures"
          },
          {
            "ref": {
              "sourceId": "bis-cpmi-cyber-resilience",
              "locator": "Response and recovery",
              "label": "official-requirement"
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "CPMI-IOSCO cyber-resilience guidance"
          }
        ],
        "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": [
          "ops-monitoring"
        ],
        "interfaceIds": [],
        "placements": {
          "ops-monitoring": {
            "x": 80,
            "y": 100,
            "width": 244,
            "height": 126
          }
        },
        "boundaries": []
      },
      {
        "id": "container",
        "label": "Container",
        "plainPurpose": "The major applications, stores, gateways, controls, and operational ownership boundaries.",
        "nodeIds": [
          "ops-state-view",
          "ops-monitoring",
          "ops-case",
          "ops-repair",
          "ops-network-case",
          "ops-recon",
          "ops-command"
        ],
        "interfaceIds": [
          "ops-e1",
          "ops-e2",
          "ops-e3",
          "ops-e4",
          "ops-e5",
          "ops-e6",
          "ops-e7",
          "ops-e8",
          "ops-e10"
        ],
        "placements": {
          "ops-state-view": {
            "x": 80,
            "y": 100,
            "width": 196,
            "height": 126
          },
          "ops-monitoring": {
            "x": 376,
            "y": 100,
            "width": 196,
            "height": 126
          },
          "ops-case": {
            "x": 672,
            "y": 100,
            "width": 196,
            "height": 126
          },
          "ops-repair": {
            "x": 968,
            "y": 100,
            "width": 196,
            "height": 126
          },
          "ops-network-case": {
            "x": 80,
            "y": 326,
            "width": 196,
            "height": 126
          },
          "ops-recon": {
            "x": 376,
            "y": 326,
            "width": 196,
            "height": 126
          },
          "ops-command": {
            "x": 672,
            "y": 326,
            "width": 196,
            "height": 126
          }
        },
        "boundaries": [
          {
            "id": "container-bank-boundary",
            "label": "Institution-controlled boundary",
            "nodeIds": [
              "ops-state-view",
              "ops-monitoring",
              "ops-case",
              "ops-repair",
              "ops-network-case",
              "ops-recon",
              "ops-command"
            ],
            "kind": "ownership"
          }
        ]
      },
      {
        "id": "component",
        "label": "Component",
        "plainPurpose": "The processing responsibilities and interface contracts that must cooperate for one payment.",
        "nodeIds": [
          "ops-state-view",
          "ops-monitoring",
          "ops-case",
          "ops-repair",
          "ops-network-case",
          "ops-recon",
          "ops-reporting",
          "ops-command"
        ],
        "interfaceIds": [
          "ops-e1",
          "ops-e2",
          "ops-e3",
          "ops-e4",
          "ops-e5",
          "ops-e6",
          "ops-e7",
          "ops-e8",
          "ops-e9",
          "ops-e10"
        ],
        "placements": {
          "ops-state-view": {
            "x": 80,
            "y": 100,
            "width": 196,
            "height": 126
          },
          "ops-monitoring": {
            "x": 376,
            "y": 100,
            "width": 196,
            "height": 126
          },
          "ops-case": {
            "x": 672,
            "y": 100,
            "width": 196,
            "height": 126
          },
          "ops-repair": {
            "x": 968,
            "y": 100,
            "width": 196,
            "height": 126
          },
          "ops-network-case": {
            "x": 80,
            "y": 326,
            "width": 196,
            "height": 126
          },
          "ops-recon": {
            "x": 376,
            "y": 326,
            "width": 196,
            "height": 126
          },
          "ops-reporting": {
            "x": 672,
            "y": 326,
            "width": 196,
            "height": 126
          },
          "ops-command": {
            "x": 968,
            "y": 326,
            "width": 196,
            "height": 126
          }
        },
        "boundaries": [
          {
            "id": "component-bank-boundary",
            "label": "Institution-controlled boundary",
            "nodeIds": [
              "ops-state-view",
              "ops-monitoring",
              "ops-case",
              "ops-repair",
              "ops-network-case",
              "ops-recon",
              "ops-reporting",
              "ops-command"
            ],
            "kind": "ownership"
          }
        ]
      },
      {
        "id": "deployment",
        "label": "Deployment",
        "plainPurpose": "The trust zones, runtime dependencies, external connections, and recovery boundaries.",
        "nodeIds": [
          "ops-state-view",
          "ops-monitoring",
          "ops-network-case"
        ],
        "interfaceIds": [
          "ops-e1",
          "ops-e6"
        ],
        "placements": {
          "ops-state-view": {
            "x": 80,
            "y": 100,
            "width": 244,
            "height": 126
          },
          "ops-monitoring": {
            "x": 444,
            "y": 100,
            "width": 244,
            "height": 126
          },
          "ops-network-case": {
            "x": 808,
            "y": 100,
            "width": 244,
            "height": 126
          }
        },
        "boundaries": [
          {
            "id": "deployment-bank-boundary",
            "label": "Institution-controlled boundary",
            "nodeIds": [
              "ops-state-view",
              "ops-monitoring",
              "ops-network-case"
            ],
            "kind": "ownership"
          }
        ]
      }
    ],
    "traces": [
      {
        "id": "ops-investigate-payment",
        "label": "Investigate an uncertain payment",
        "summary": "Follow an operational signal to a safe, reconciled close without guessing whether money moved.",
        "viewId": "component",
        "steps": [
          {
            "id": "ops-investigate-payment-step-1",
            "title": "Expose the uncertainty",
            "nodeId": "ops-state-view",
            "interfaceId": "ops-e1",
            "plainExplanation": "The view keeps accepted, sent, delivered, settled, posted, and reported states separate.",
            "businessState": "Last confirmed state identified"
          },
          {
            "id": "ops-investigate-payment-step-2",
            "title": "Create owned work",
            "nodeId": "ops-monitoring",
            "interfaceId": "ops-e2",
            "plainExplanation": "Age, cut-off, value, customer impact, and settlement uncertainty determine priority.",
            "businessState": "Case required"
          },
          {
            "id": "ops-investigate-payment-step-3",
            "title": "Assemble the evidence",
            "nodeId": "ops-case",
            "interfaceId": "ops-e5",
            "plainExplanation": "Messages, identifiers, books, statements, and previous actions share one case.",
            "businessState": "Investigation opened"
          },
          {
            "id": "ops-investigate-payment-step-4",
            "title": "Ask the right counterparty",
            "nodeId": "ops-network-case",
            "interfaceId": "ops-e6",
            "plainExplanation": "The correct request travels to the party that can evidence the missing state.",
            "businessState": "External response pending",
            "messageIds": [
              "camt-110",
              "camt-111"
            ]
          },
          {
            "id": "ops-investigate-payment-step-5",
            "title": "Choose the safe action",
            "nodeId": "ops-repair",
            "interfaceId": "ops-e4",
            "plainExplanation": "Settlement and idempotency guards decide whether repair, retry, return, or no value action is safe.",
            "businessState": "Recovery authorised"
          },
          {
            "id": "ops-investigate-payment-step-6",
            "title": "Reconcile every layer",
            "nodeId": "ops-recon",
            "interfaceId": "ops-e8",
            "plainExplanation": "Instruction, settlement, journal, statement, fee, and linked return agree.",
            "businessState": "Financial state aligned"
          },
          {
            "id": "ops-investigate-payment-step-7",
            "title": "Close and report",
            "nodeId": "ops-reporting",
            "plainExplanation": "Customer and management reporting reflect the proven final state.",
            "businessState": "Case closed with evidence"
          }
        ],
        "evidence": [
          {
            "ref": {
              "sourceId": "payments-signal-editorial",
              "locator": "Payment operations, exception, and investigation architecture",
              "label": "simplified-educational-illustration",
              "simplifications": "Queues, statuses, repair rights, investigation messages, service levels, operational roles, customer communication, and accounting action depend on the institution, rail, scheme, message profile, and legal context."
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "Payments Signal reference architecture v1"
          },
          {
            "ref": {
              "sourceId": "bis-cpmi-pfmi",
              "locator": "Principles 17, 23 and 24",
              "label": "official-requirement"
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "CPMI-IOSCO Principles for financial market infrastructures"
          }
        ]
      }
    ],
    "stressCases": [
      {
        "id": "ops-stress-late-status",
        "label": "Status arrives after manual action",
        "trigger": "A late network status contradicts the assumption used for a manual repair.",
        "divergesAfterStepId": "ops-investigate-payment-step-5",
        "traceId": "ops-investigate-payment",
        "affectedNodeIds": [
          "ops-state-view",
          "ops-case",
          "ops-repair",
          "ops-recon"
        ],
        "affectedInterfaceIds": [
          "ops-e4",
          "ops-e6",
          "ops-e7"
        ],
        "lastConfirmedState": "The manual action is recorded; the late external state is newly evidenced.",
        "settlementState": "Settlement must be re-evaluated from source evidence.",
        "fundsState": "There may now be two linked value movements or one duplicate attempt.",
        "owner": "Payment investigations",
        "safeAction": "Freeze further action and reconcile both the original and manual attempt.",
        "requiredEvidence": [
          "Original message",
          "Late status",
          "Manual action reference",
          "Statements and journals"
        ],
        "recoverySteps": [
          "Reconstruct the timeline",
          "Contain duplicates",
          "Use return or correction rules",
          "Correct reporting"
        ],
        "evidence": [
          {
            "ref": {
              "sourceId": "payments-signal-editorial",
              "locator": "Payment operations, exception, and investigation architecture",
              "label": "simplified-educational-illustration",
              "simplifications": "Queues, statuses, repair rights, investigation messages, service levels, operational roles, customer communication, and accounting action depend on the institution, rail, scheme, message profile, and legal context."
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "Payments Signal reference architecture v1"
          }
        ]
      },
      {
        "id": "ops-stress-ledger",
        "label": "Payment engine recovers before ledger",
        "trigger": "The orchestration service is healthy but posting outcome remains uncertain.",
        "divergesAfterStepId": "ops-investigate-payment-step-5",
        "traceId": "ops-investigate-payment",
        "affectedNodeIds": [
          "ops-state-view",
          "ops-repair",
          "ops-command"
        ],
        "affectedInterfaceIds": [
          "ops-e4",
          "ops-e10"
        ],
        "lastConfirmedState": "Payment processing reached the posting boundary.",
        "settlementState": "External settlement may or may not have followed.",
        "fundsState": "A journal may already exist.",
        "owner": "Incident command and ledger operations",
        "safeAction": "Keep value-affecting replay disabled until the journal and settlement boundary are reconciled.",
        "requiredEvidence": [
          "Business key",
          "Ledger transaction log",
          "Network state",
          "Recovery checkpoint"
        ],
        "recoverySteps": [
          "Prove journal state",
          "Recover downstream queues in order",
          "Release controlled replay"
        ],
        "evidence": [
          {
            "ref": {
              "sourceId": "bis-cpmi-pfmi",
              "locator": "Principle 17",
              "label": "official-requirement"
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "CPMI-IOSCO Principles for financial market infrastructures"
          },
          {
            "ref": {
              "sourceId": "payments-signal-editorial",
              "locator": "Payment operations, exception, and investigation architecture",
              "label": "simplified-educational-illustration",
              "simplifications": "Queues, statuses, repair rights, investigation messages, service levels, operational roles, customer communication, and accounting action depend on the institution, rail, scheme, message profile, and legal context."
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "Payments Signal reference architecture v1"
          }
        ]
      },
      {
        "id": "ops-stress-recall",
        "label": "Recall is mistaken for reversal",
        "trigger": "An operator expects a cancellation request to undo a settled payment automatically.",
        "divergesAfterStepId": "ops-investigate-payment-step-4",
        "traceId": "ops-investigate-payment",
        "affectedNodeIds": [
          "ops-repair",
          "ops-network-case",
          "ops-state-view"
        ],
        "affectedInterfaceIds": [
          "ops-e3",
          "ops-e5",
          "ops-e6"
        ],
        "lastConfirmedState": "The original payment may already be settled.",
        "settlementState": "A recall request does not itself reverse settlement.",
        "fundsState": "Funds remain where settlement and beneficiary posting placed them until an accepted return or other process moves value.",
        "owner": "Payment investigations",
        "safeAction": "Send the correct request only with authority; track the response and any separate return.",
        "requiredEvidence": [
          "Original settlement state",
          "Recall authority",
          "camt.056 or MT request",
          "camt.029 or response",
          "Return evidence"
        ],
        "recoverySteps": [
          "Record request and response",
          "Link any pacs.004 or other return",
          "Reconcile both movements"
        ],
        "evidence": [
          {
            "ref": {
              "sourceId": "payments-signal-editorial",
              "locator": "Payment operations, exception, and investigation architecture",
              "label": "simplified-educational-illustration",
              "simplifications": "Queues, statuses, repair rights, investigation messages, service levels, operational roles, customer communication, and accounting action depend on the institution, rail, scheme, message profile, and legal context."
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "Payments Signal reference architecture v1"
          }
        ]
      }
    ],
    "overlays": [
      {
        "id": "ops-overlay-mx-exceptions",
        "label": "MX cancellation, investigation, and return",
        "summary": "Separate customer cancellation, FI-to-FI cancellation, resolution, inquiry, response, and return messages.",
        "nodeIds": [
          "ops-state-view",
          "ops-case",
          "ops-repair",
          "ops-network-case",
          "ops-recon"
        ],
        "interfaceIds": [
          "ops-e3",
          "ops-e4",
          "ops-e5",
          "ops-e6",
          "ops-e7",
          "ops-e8"
        ],
        "relatedFlowIds": [
          "flow-cbpr-corporate-lifecycle",
          "flow-mx-cover"
        ],
        "evidence": [
          {
            "ref": {
              "sourceId": "iso20022-catalogue",
              "locator": "Payment cancellation, investigation, resolution, and return messages",
              "label": "official-requirement"
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "ISO 20022 message catalogue"
          }
        ]
      },
      {
        "id": "ops-overlay-mt-investigations",
        "label": "MT cancellation and free-format investigations",
        "summary": "Preserve request, response, and actual funds movement as separate events during MT coexistence or legacy processing.",
        "nodeIds": [
          "ops-state-view",
          "ops-case",
          "ops-network-case",
          "ops-recon"
        ],
        "interfaceIds": [
          "ops-e2",
          "ops-e5",
          "ops-e6",
          "ops-e8"
        ],
        "relatedFlowIds": [
          "flow-mt-corporate-lifecycle",
          "flow-swift-serial",
          "flow-swift-cover"
        ],
        "evidence": [
          {
            "ref": {
              "sourceId": "swift-standards-mt",
              "locator": "MT 192/195/196/199 investigation messages",
              "label": "official-requirement"
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "Current Swift Standards MT release"
          }
        ],
        "coverageGap": "Detailed field rules and permitted usage require the current Swift release and bilateral or market-practice guidance."
      },
      {
        "id": "ops-overlay-outward-remittance",
        "label": "Outward remittance operations",
        "summary": "Show compliance hold, routing, external status, settlement evidence, customer reporting, and exception ownership for an outward remittance.",
        "nodeIds": [
          "ops-state-view",
          "ops-monitoring",
          "ops-case",
          "ops-repair",
          "ops-network-case",
          "ops-recon",
          "ops-reporting"
        ],
        "interfaceIds": [
          "ops-e1",
          "ops-e2",
          "ops-e3",
          "ops-e4",
          "ops-e5",
          "ops-e6",
          "ops-e7",
          "ops-e8",
          "ops-e9"
        ],
        "relatedFlowIds": [
          "flow-in-outward-remittance"
        ],
        "evidence": [
          {
            "ref": {
              "sourceId": "payments-signal-editorial",
              "locator": "Payment operations, exception, and investigation architecture",
              "label": "simplified-educational-illustration",
              "simplifications": "Queues, statuses, repair rights, investigation messages, service levels, operational roles, customer communication, and accounting action depend on the institution, rail, scheme, message profile, and legal context."
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "Payments Signal reference architecture v1"
          }
        ],
        "coverageGap": "Foreign-exchange, purpose-code, tax, documentation, reporting, and route controls require current Reserve Bank of India and authorised-dealer policy."
      },
      {
        "id": "ops-overlay-cheque",
        "label": "Cheque truncation operations",
        "summary": "Show image and data exchange as evidence, clearing exceptions, settlement reconciliation, return ownership, and customer reporting.",
        "nodeIds": [
          "ops-state-view",
          "ops-monitoring",
          "ops-case",
          "ops-repair",
          "ops-recon",
          "ops-reporting"
        ],
        "interfaceIds": [
          "ops-e1",
          "ops-e2",
          "ops-e3",
          "ops-e4",
          "ops-e7",
          "ops-e8",
          "ops-e9"
        ],
        "relatedFlowIds": [
          "flow-cheque-truncation"
        ],
        "evidence": [
          {
            "ref": {
              "sourceId": "payments-signal-editorial",
              "locator": "Payment operations, exception, and investigation architecture",
              "label": "simplified-educational-illustration",
              "simplifications": "Queues, statuses, repair rights, investigation messages, service levels, operational roles, customer communication, and accounting action depend on the institution, rail, scheme, message profile, and legal context."
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "Payments Signal reference architecture v1"
          }
        ],
        "coverageGap": "Cheque image, clearing, presentment, return, fraud, legal, and settlement rules depend on the selected clearing system and jurisdiction."
      }
    ],
    "decisions": [
      {
        "id": "ops-decision-case",
        "question": "Should every technical alert create a payment case?",
        "options": [
          {
            "label": "Risk-based case creation",
            "consequence": "Reduces noise while retaining rules that prove why a payment needs human ownership."
          },
          {
            "label": "One case per alert",
            "consequence": "Maximises visibility but can bury settlement-risk work in duplicate noise."
          }
        ],
        "guidance": "Create cases from governed state, materiality, deadline, and financial uncertainty—not from raw log volume alone.",
        "evidence": [
          {
            "ref": {
              "sourceId": "payments-signal-editorial",
              "locator": "Payment operations, exception, and investigation architecture",
              "label": "simplified-educational-illustration",
              "simplifications": "Queues, statuses, repair rights, investigation messages, service levels, operational roles, customer communication, and accounting action depend on the institution, rail, scheme, message profile, and legal context."
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "Payments Signal reference architecture v1"
          }
        ]
      },
      {
        "id": "ops-decision-replay",
        "question": "Who may authorise bulk replay after an outage?",
        "options": [
          {
            "label": "Incident command plus business control",
            "consequence": "Coordinates platform recovery with payment, ledger, and settlement evidence."
          },
          {
            "label": "Application team alone",
            "consequence": "Restores throughput faster but can duplicate value when downstream state is unknown."
          }
        ],
        "guidance": "Require a last-consistent checkpoint, idempotency proof, reconciliation plan, rollback boundary, and named business authority.",
        "evidence": [
          {
            "ref": {
              "sourceId": "bis-cpmi-pfmi",
              "locator": "Principle 17",
              "label": "official-requirement"
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "CPMI-IOSCO Principles for financial market infrastructures"
          },
          {
            "ref": {
              "sourceId": "bis-cpmi-cyber-resilience",
              "locator": "Response and recovery",
              "label": "official-requirement"
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "CPMI-IOSCO cyber-resilience guidance"
          }
        ]
      }
    ],
    "targets": [
      {
        "type": "flow",
        "id": "flow-in-outward-remittance"
      },
      {
        "type": "flow",
        "id": "flow-cheque-truncation"
      },
      {
        "type": "message",
        "id": "camt-055"
      },
      {
        "type": "message",
        "id": "camt-056"
      },
      {
        "type": "message",
        "id": "camt-029"
      },
      {
        "type": "message",
        "id": "camt-110"
      },
      {
        "type": "message",
        "id": "camt-111"
      },
      {
        "type": "message",
        "id": "pacs-004"
      },
      {
        "type": "message",
        "id": "pacs-007"
      },
      {
        "type": "message",
        "id": "mt192"
      },
      {
        "type": "message",
        "id": "mt195"
      },
      {
        "type": "message",
        "id": "mt196"
      },
      {
        "type": "message",
        "id": "mt199"
      },
      {
        "type": "mapping",
        "id": "mt192-to-camt-056"
      },
      {
        "type": "mapping",
        "id": "mt195-to-camt-110"
      },
      {
        "type": "mapping",
        "id": "mt196-to-camt-029"
      },
      {
        "type": "mapping",
        "id": "mt196-to-camt-111"
      },
      {
        "type": "mapping",
        "id": "mt199-to-camt-110"
      },
      {
        "type": "mapping",
        "id": "mt199-to-camt-111"
      },
      {
        "type": "mapping",
        "id": "mt103-return-to-pacs-004"
      },
      {
        "type": "mapping",
        "id": "mt103-reject-to-pacs-002"
      }
    ],
    "glossaryTermIds": [
      "cancellation",
      "case-management",
      "investigation",
      "payment-repair",
      "recall",
      "reconciliation",
      "replay",
      "return",
      "reversal"
    ],
    "evidence": [
      {
        "ref": {
          "sourceId": "payments-signal-editorial",
          "locator": "Payment operations, exception, and investigation architecture",
          "label": "simplified-educational-illustration",
          "simplifications": "Queues, statuses, repair rights, investigation messages, service levels, operational roles, customer communication, and accounting action depend on the institution, rail, scheme, message profile, and legal context."
        },
        "verifiedDate": "2026-07-23",
        "versionContext": "Payments Signal reference architecture v1"
      },
      {
        "ref": {
          "sourceId": "bis-cpmi-pfmi",
          "locator": "Principles 8, 17, 23 and 24",
          "label": "official-requirement"
        },
        "verifiedDate": "2026-07-23",
        "versionContext": "CPMI-IOSCO Principles for financial market infrastructures"
      },
      {
        "ref": {
          "sourceId": "bis-cpmi-cyber-resilience",
          "locator": "Response and recovery",
          "label": "official-requirement"
        },
        "verifiedDate": "2026-07-23",
        "versionContext": "CPMI-IOSCO cyber-resilience guidance"
      }
    ],
    "simplifies": "This blueprint places evidence and settlement state before action. Real operating models divide queues, customer service, investigations, treasury, sanctions, fraud, finance, technology, and incident command differently; schemes and jurisdictions decide which messages, time limits, permissions, and value-recovery processes apply."
  },
  "sources": [
    {
      "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."
    },
    {
      "id": "bis-cpmi-pfmi",
      "publisher": "CPMI and IOSCO (Bank for International Settlements)",
      "title": "Principles for financial market infrastructures",
      "sourceType": "industry-paper",
      "publicationDate": "2012-04-16",
      "accessedDate": "2026-07-12",
      "url": "https://www.bis.org/cpmi/publ/d101.htm",
      "applicability": "International risk-management standards for systemically important payment systems and other financial market infrastructures.",
      "notes": "Published by the CPSS (now CPMI) and IOSCO; contains 24 principles plus responsibilities for authorities. This site uses it only for high-level concepts such as settlement finality."
    },
    {
      "id": "bis-cpmi-cyber-resilience",
      "publisher": "Committee on Payments and Market Infrastructures / IOSCO",
      "title": "Guidance on cyber resilience for financial market infrastructures",
      "sourceType": "regulatory-guidance",
      "accessedDate": "2026-07-23",
      "url": "https://www.bis.org/cpmi/publ/d146.htm",
      "applicability": "Sets expectations for governance, identification, protection, detection, response, recovery, testing, situational awareness, and learning at financial market infrastructures.",
      "notes": "The guidance applies to financial market infrastructures. A bank or payment-service provider should translate the control outcomes into its own regulatory, risk, and operating context."
    }
  ],
  "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": "Batch and file-based payments",
      "href": "/2026/07/13/batch-and-file-payments",
      "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": "Cheque clearing and truncation, explained",
      "href": "/2026/07/18/cheque-clearing-and-truncation-explained",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "Confirmation of Payee and APP fraud",
      "href": "/2026/07/18/confirmation-of-payee-and-app-fraud",
      "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": "Domestic versus cross-border payments",
      "href": "/2026/07/13/domestic-vs-cross-border-payments",
      "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 payment hub works: product capabilities",
      "href": "/2026/07/13/payment-hub-product-capabilities",
      "coverage": "direct"
    },
    {
      "type": "article",
      "label": "MT202 COV: cover payments explained",
      "href": "/2026/07/13/mt202-cov-cover-payments",
      "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": "PAPSS: the Pan-African Payment and Settlement System",
      "href": "/2026/07/13/papss-pan-african-settlement",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "Payment Engines",
      "href": "/2026/07/13/payment-engines",
      "coverage": "direct"
    },
    {
      "type": "article",
      "label": "Payment exceptions and investigations",
      "href": "/2026/07/13/payment-exceptions-and-investigations",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "Payment fraud typologies",
      "href": "/2026/07/13/payment-fraud-typologies",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "Payment hub reference and standing data",
      "href": "/2026/07/13/payment-hub-reference-and-standing-data",
      "coverage": "direct"
    },
    {
      "type": "article",
      "label": "Payment message templates",
      "href": "/2026/07/13/payment-message-templates",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "PAYMENTS – BASIC TECHNICAL CONCEPTS – PART 1",
      "href": "/2026/07/13/payments-basic-technical-concepts-part-1",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "Purpose codes in payments",
      "href": "/2026/07/13/purpose-codes-in-payments",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "Reconciliation in payments",
      "href": "/2026/07/13/payments-reconciliation",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "Reversals, returns, recalls, and cancellations",
      "href": "/2026/07/13/reversals-returns-and-cancellations",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "Security and fraud controls in payment operations",
      "href": "/2026/07/13/payment-operations-security-and-fraud",
      "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 – Recall Flow",
      "href": "/2026/07/13/sct-recall-flow",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "SEPA Credit Transfer – Reject Flow",
      "href": "/2026/07/13/sct-reject-flow",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "Sepa Credit Transfer – Return Flow",
      "href": "/2026/07/13/sct-return-flow",
      "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": "Structured remittance information",
      "href": "/2026/07/13/structured-remittance-information",
      "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 investigation and exception messages",
      "href": "/2026/07/13/swift-investigation-and-exception-messages",
      "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 MT101",
      "href": "/2026/07/13/swift-mt101",
      "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 MT9xx: statements and confirmations",
      "href": "/2026/07/13/swift-mt9xx-statements-and-confirmations",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "The camt family: cash management and reporting",
      "href": "/2026/07/13/camt-cash-management-messages",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "The pain.001 payment initiation",
      "href": "/2026/07/13/the-pain-001-payment-initiation",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "The Payment Engine Problem",
      "href": "/2026/07/13/the-payment-engine-problem",
      "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 SWIFT KYC Registry",
      "href": "/2026/07/13/the-swift-kyc-registry",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "The SWIFT Payment Controls Service",
      "href": "/2026/07/13/swift-payment-controls-service",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "Treasury liquidity: pooling, sweeping, and virtual accounts",
      "href": "/2026/07/18/treasury-liquidity-pooling-sweeping-and-virtual-accounts",
      "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": "flow",
      "label": "CBPR+ corporate payment — full MX lifecycle",
      "href": "/explore/cbpr-corporate-lifecycle",
      "coverage": "direct"
    },
    {
      "type": "flow",
      "label": "Cheque truncation clearing",
      "href": "/explore/cheque-truncation",
      "coverage": "direct"
    },
    {
      "type": "flow",
      "label": "Corporate payment — legacy MT lifecycle",
      "href": "/explore/mt-corporate-lifecycle",
      "coverage": "direct"
    },
    {
      "type": "flow",
      "label": "India to USA: an outward remittance (MT103, INR to USD)",
      "href": "/explore/in-outward-remittance",
      "coverage": "direct"
    },
    {
      "type": "flow",
      "label": "ISO 20022 cover payment (pacs.008 + pacs.009 COV)",
      "href": "/explore/mx-cover",
      "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": "Authorised push payment fraud",
      "href": "/glossary#authorised-push-payment-fraud",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Behavioural analytics",
      "href": "/glossary#behavioural-analytics",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Book payment",
      "href": "/glossary#book-payment",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "camt family",
      "href": "/glossary#camt",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "camt.029",
      "href": "/glossary#camt-029",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "camt.056",
      "href": "/glossary#camt-056",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Canonical format",
      "href": "/glossary#canonical-format",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Cash sweeping",
      "href": "/glossary#cash-sweeping",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Cheque return",
      "href": "/glossary#cheque-return",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Cheque truncation",
      "href": "/glossary#cheque-truncation",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Collecting bank",
      "href": "/glossary#collecting-bank",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Confirmation of Payee",
      "href": "/glossary#confirmation-of-payee",
      "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": "Cut-off",
      "href": "/glossary#cut-off",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Drawee bank (paying bank)",
      "href": "/glossary#drawee-bank",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Image-based clearing",
      "href": "/glossary#image-based-clearing",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Input credit file",
      "href": "/glossary#input-credit-file",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Intermediary agent",
      "href": "/glossary#intermediary-agent",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Loro account",
      "href": "/glossary#loro-account",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Message template",
      "href": "/glossary#message-template",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Money mule",
      "href": "/glossary#money-mule",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "MT101",
      "href": "/glossary#mt101",
      "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": "Name verification service",
      "href": "/glossary#name-verification-service",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Nostro account",
      "href": "/glossary#nostro-account",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Notional cash pooling",
      "href": "/glossary#notional-cash-pooling",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "On-us payment",
      "href": "/glossary#on-us-payment",
      "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": "pain family",
      "href": "/glossary#pain",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "pain.001",
      "href": "/glossary#pain-001",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Payment engine",
      "href": "/glossary#payment-engine",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Payment hub",
      "href": "/glossary#payment-hub",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Payment orchestration",
      "href": "/glossary#orchestration",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Physical cash pooling",
      "href": "/glossary#physical-cash-pooling",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Proxy addressing",
      "href": "/glossary#proxy-addressing",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "R-transaction",
      "href": "/glossary#r-transaction",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Recall",
      "href": "/glossary#recall",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Reconciliation",
      "href": "/glossary#reconciliation",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Reference data",
      "href": "/glossary#reference-data",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Reject",
      "href": "/glossary#reject",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Return",
      "href": "/glossary#return",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Rules engine",
      "href": "/glossary#rules-engine",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Scheme adapter",
      "href": "/glossary#scheme-adapter",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Serial payment",
      "href": "/glossary#serial-payment",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Straight-through processing",
      "href": "/glossary#straight-through-processing",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Suspense account",
      "href": "/glossary#suspense-account",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Value date",
      "href": "/glossary#value-date",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Virtual account",
      "href": "/glossary#virtual-account",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Virtual IBAN",
      "href": "/glossary#virtual-iban",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Vostro account",
      "href": "/glossary#vostro-account",
      "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": "MT192 → camt.056",
      "href": "/messages/mappings/mt192-to-camt-056",
      "coverage": "direct"
    },
    {
      "type": "mapping",
      "label": "MT195 → camt.110",
      "href": "/messages/mappings/mt195-to-camt-110",
      "coverage": "direct"
    },
    {
      "type": "mapping",
      "label": "MT196 → camt.029",
      "href": "/messages/mappings/mt196-to-camt-029",
      "coverage": "direct"
    },
    {
      "type": "mapping",
      "label": "MT196 → camt.111",
      "href": "/messages/mappings/mt196-to-camt-111",
      "coverage": "direct"
    },
    {
      "type": "mapping",
      "label": "MT199 answer → camt.111",
      "href": "/messages/mappings/mt199-to-camt-111",
      "coverage": "direct"
    },
    {
      "type": "mapping",
      "label": "MT199 query → camt.110",
      "href": "/messages/mappings/mt199-to-camt-110",
      "coverage": "direct"
    },
    {
      "type": "mapping",
      "label": "MT292 → camt.056",
      "href": "/messages/mappings/mt292-to-camt-056",
      "coverage": "derived"
    },
    {
      "type": "mapping",
      "label": "MT295 → camt.110",
      "href": "/messages/mappings/mt295-to-camt-110",
      "coverage": "derived"
    },
    {
      "type": "mapping",
      "label": "MT296 cancellation answer → camt.029",
      "href": "/messages/mappings/mt296-to-camt-029",
      "coverage": "derived"
    },
    {
      "type": "mapping",
      "label": "MT296 query answer → camt.111",
      "href": "/messages/mappings/mt296-to-camt-111",
      "coverage": "derived"
    },
    {
      "type": "mapping",
      "label": "MT299 answer → camt.111",
      "href": "/messages/mappings/mt299-to-camt-111",
      "coverage": "derived"
    },
    {
      "type": "mapping",
      "label": "MT299 query → camt.110",
      "href": "/messages/mappings/mt299-to-camt-110",
      "coverage": "derived"
    },
    {
      "type": "mapping",
      "label": "MT900 → camt.054",
      "href": "/messages/mappings/mt900-to-camt-054",
      "coverage": "direct"
    },
    {
      "type": "mapping",
      "label": "MT910 → camt.054",
      "href": "/messages/mappings/mt910-to-camt-054",
      "coverage": "direct"
    },
    {
      "type": "mapping",
      "label": "MT940 → camt.053",
      "href": "/messages/mappings/mt940-to-camt-053",
      "coverage": "direct"
    },
    {
      "type": "mapping",
      "label": "MT941 → camt.052",
      "href": "/messages/mappings/mt941-to-camt-052",
      "coverage": "direct"
    },
    {
      "type": "mapping",
      "label": "MT942 → camt.052",
      "href": "/messages/mappings/mt942-to-camt-052",
      "coverage": "direct"
    },
    {
      "type": "mapping",
      "label": "MT950 → camt.053",
      "href": "/messages/mappings/mt950-to-camt-053",
      "coverage": "direct"
    },
    {
      "type": "message",
      "label": "camt.026 — camt.026 — Unable to Apply",
      "href": "/messages/camt-026",
      "coverage": "derived"
    },
    {
      "type": "message",
      "label": "camt.027 — camt.027 — Claim Non-Receipt",
      "href": "/messages/camt-027",
      "coverage": "derived"
    },
    {
      "type": "message",
      "label": "camt.028 — camt.028 — Additional Payment Information",
      "href": "/messages/camt-028",
      "coverage": "derived"
    },
    {
      "type": "message",
      "label": "camt.029 — camt.029 — Resolution of Investigation",
      "href": "/messages/camt-029",
      "coverage": "direct"
    },
    {
      "type": "message",
      "label": "camt.052 — camt.052 — Bank-to-Customer Account Report",
      "href": "/messages/camt-052",
      "coverage": "direct"
    },
    {
      "type": "message",
      "label": "camt.053 — camt.053 — Bank-to-Customer Statement",
      "href": "/messages/camt-053",
      "coverage": "direct"
    },
    {
      "type": "message",
      "label": "camt.054 — camt.054 — Bank-to-Customer Debit/Credit Notification",
      "href": "/messages/camt-054",
      "coverage": "direct"
    },
    {
      "type": "message",
      "label": "camt.055 — camt.055 — Customer Payment Cancellation Request",
      "href": "/messages/camt-055",
      "coverage": "direct"
    },
    {
      "type": "message",
      "label": "camt.056 — camt.056 — FI to FI Payment Cancellation Request",
      "href": "/messages/camt-056",
      "coverage": "direct"
    },
    {
      "type": "message",
      "label": "camt.110 — camt.110 — Investigation Request",
      "href": "/messages/camt-110",
      "coverage": "direct"
    },
    {
      "type": "message",
      "label": "camt.111 — camt.111 — Investigation Response",
      "href": "/messages/camt-111",
      "coverage": "direct"
    },
    {
      "type": "message",
      "label": "MT192 — MT192 — Request for Cancellation",
      "href": "/messages/mt192",
      "coverage": "direct"
    },
    {
      "type": "message",
      "label": "MT195 — MT195 — Queries",
      "href": "/messages/mt195",
      "coverage": "direct"
    },
    {
      "type": "message",
      "label": "MT196 — MT196 — Answers",
      "href": "/messages/mt196",
      "coverage": "direct"
    },
    {
      "type": "message",
      "label": "MT199 — MT199 — Free Format Message",
      "href": "/messages/mt199",
      "coverage": "direct"
    },
    {
      "type": "message",
      "label": "MT900 — MT900 — Confirmation of Debit",
      "href": "/messages/mt900",
      "coverage": "direct"
    },
    {
      "type": "message",
      "label": "MT910 — MT910 — Confirmation of Credit",
      "href": "/messages/mt910",
      "coverage": "direct"
    },
    {
      "type": "message",
      "label": "MT940 — MT940 — Customer Statement Message",
      "href": "/messages/mt940",
      "coverage": "direct"
    },
    {
      "type": "message",
      "label": "MT941 — MT941 — Balance Report",
      "href": "/messages/mt941",
      "coverage": "direct"
    },
    {
      "type": "message",
      "label": "MT942 — MT942 — Interim Transaction Report",
      "href": "/messages/mt942",
      "coverage": "direct"
    },
    {
      "type": "message",
      "label": "MT950 — MT950 — Statement Message",
      "href": "/messages/mt950",
      "coverage": "direct"
    },
    {
      "type": "message",
      "label": "pacs.004 — pacs.004 — Payment Return",
      "href": "/messages/pacs-004",
      "coverage": "direct"
    },
    {
      "type": "message",
      "label": "pacs.007 — pacs.007 — FI-to-FI Payment Reversal",
      "href": "/messages/pacs-007",
      "coverage": "direct"
    },
    {
      "type": "resource",
      "label": "camt.026 field matrix",
      "href": "/downloads/assets/field-matrix-camt-026",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "camt.027 field matrix",
      "href": "/downloads/assets/field-matrix-camt-027",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "camt.028 field matrix",
      "href": "/downloads/assets/field-matrix-camt-028",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "camt.029 field matrix",
      "href": "/downloads/assets/field-matrix-camt-029",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "camt.029 resolution of investigation — raw XML",
      "href": "/downloads/samples/camt-029",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "camt.052 field matrix",
      "href": "/downloads/assets/field-matrix-camt-052",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "camt.052 intraday account report — raw XML",
      "href": "/downloads/samples/camt-052",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "camt.053 account statement — raw XML",
      "href": "/downloads/samples/camt-053",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "camt.053 field matrix",
      "href": "/downloads/assets/field-matrix-camt-053",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "camt.054 debit notification — raw XML",
      "href": "/downloads/samples/camt-054",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "camt.054 field matrix",
      "href": "/downloads/assets/field-matrix-camt-054",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "camt.055 customer cancellation request — raw XML",
      "href": "/downloads/samples/camt-055",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "camt.055 field matrix",
      "href": "/downloads/assets/field-matrix-camt-055",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "camt.056 field matrix",
      "href": "/downloads/assets/field-matrix-camt-056",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "camt.056 payment cancellation request — raw XML",
      "href": "/downloads/samples/camt-056",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "camt.110 field matrix",
      "href": "/downloads/assets/field-matrix-camt-110",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "camt.110 investigation request — raw XML",
      "href": "/downloads/samples/camt-110",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "camt.111 field matrix",
      "href": "/downloads/assets/field-matrix-camt-111",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "camt.111 investigation response — raw XML",
      "href": "/downloads/samples/camt-111",
      "coverage": "derived"
    },
    {
      "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 field matrix",
      "href": "/downloads/assets/field-matrix-mt103",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "MT192 → camt.056 implementation mapping",
      "href": "/downloads/assets/mapping-mt192-to-camt-056",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "MT192 cancellation request — raw FIN",
      "href": "/downloads/samples/mt192",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "MT192 field matrix",
      "href": "/downloads/assets/field-matrix-mt192",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "MT195 → camt.110 implementation mapping",
      "href": "/downloads/assets/mapping-mt195-to-camt-110",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "MT195 field matrix",
      "href": "/downloads/assets/field-matrix-mt195",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "MT195 payment query — raw FIN",
      "href": "/downloads/samples/mt195",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "MT196 → camt.029 implementation mapping",
      "href": "/downloads/assets/mapping-mt196-to-camt-029",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "MT196 → camt.111 implementation mapping",
      "href": "/downloads/assets/mapping-mt196-to-camt-111",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "MT196 field matrix",
      "href": "/downloads/assets/field-matrix-mt196",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "MT196 substantive answer — raw FIN",
      "href": "/downloads/samples/mt196",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "MT199 answer → camt.111 implementation mapping",
      "href": "/downloads/assets/mapping-mt199-to-camt-111",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "MT199 field matrix",
      "href": "/downloads/assets/field-matrix-mt199",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "MT199 free-format payment message — raw FIN",
      "href": "/downloads/samples/mt199",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "MT199 query → camt.110 implementation mapping",
      "href": "/downloads/assets/mapping-mt199-to-camt-110",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "MT292 → camt.056 implementation mapping",
      "href": "/downloads/assets/mapping-mt292-to-camt-056",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "MT292 field matrix",
      "href": "/downloads/assets/field-matrix-mt292",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "MT295 → camt.110 implementation mapping",
      "href": "/downloads/assets/mapping-mt295-to-camt-110",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "MT295 field matrix",
      "href": "/downloads/assets/field-matrix-mt295",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "MT296 cancellation answer → camt.029 implementation mapping",
      "href": "/downloads/assets/mapping-mt296-to-camt-029",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "MT296 field matrix",
      "href": "/downloads/assets/field-matrix-mt296",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "MT296 query answer → camt.111 implementation mapping",
      "href": "/downloads/assets/mapping-mt296-to-camt-111",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "MT299 answer → camt.111 implementation mapping",
      "href": "/downloads/assets/mapping-mt299-to-camt-111",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "MT299 field matrix",
      "href": "/downloads/assets/field-matrix-mt299",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "MT299 query → camt.110 implementation mapping",
      "href": "/downloads/assets/mapping-mt299-to-camt-110",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "MT900 → camt.054 implementation mapping",
      "href": "/downloads/assets/mapping-mt900-to-camt-054",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "MT900 debit confirmation — raw FIN",
      "href": "/downloads/samples/mt900",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "MT900 field matrix",
      "href": "/downloads/assets/field-matrix-mt900",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "MT910 → camt.054 implementation mapping",
      "href": "/downloads/assets/mapping-mt910-to-camt-054",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "MT910 credit confirmation — raw FIN",
      "href": "/downloads/samples/mt910",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "MT910 field matrix",
      "href": "/downloads/assets/field-matrix-mt910",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "MT940 → camt.053 implementation mapping",
      "href": "/downloads/assets/mapping-mt940-to-camt-053",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "MT940 customer statement — raw FIN",
      "href": "/downloads/samples/mt940",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "MT940 field matrix",
      "href": "/downloads/assets/field-matrix-mt940",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "MT941 → camt.052 implementation mapping",
      "href": "/downloads/assets/mapping-mt941-to-camt-052",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "MT941 balance report — raw FIN",
      "href": "/downloads/samples/mt941",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "MT941 field matrix",
      "href": "/downloads/assets/field-matrix-mt941",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "MT942 → camt.052 implementation mapping",
      "href": "/downloads/assets/mapping-mt942-to-camt-052",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "MT942 field matrix",
      "href": "/downloads/assets/field-matrix-mt942",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "MT942 interim transaction report — raw FIN",
      "href": "/downloads/samples/mt942",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "MT950 → camt.053 implementation mapping",
      "href": "/downloads/assets/mapping-mt950-to-camt-053",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "MT950 field matrix",
      "href": "/downloads/assets/field-matrix-mt950",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "MT950 statement message — raw FIN",
      "href": "/downloads/samples/mt950",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "MX cancellation, return, reversal, and investigation lifecycle — ZIP pack",
      "href": "/downloads/packs/mx-exceptions-investigations",
      "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.004 payment return — raw XML",
      "href": "/downloads/samples/pacs-004",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "pacs.007 field matrix",
      "href": "/downloads/assets/field-matrix-pacs-007",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "pacs.007 payment reversal — raw XML",
      "href": "/downloads/samples/pacs-007",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "Payment acceptance-criteria template",
      "href": "/downloads/assets/payment-acceptance-criteria-template",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "Payment lifecycle test cases",
      "href": "/downloads/assets/payment-lifecycle-test-cases",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "Payments BA delivery checklist",
      "href": "/downloads/assets/payments-ba-delivery-checklist",
      "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 Direct Debit B2B implementation guidelines and XSDs",
      "href": "/implementation-resources",
      "coverage": "direct"
    },
    {
      "type": "resource",
      "label": "SEPA Direct Debit B2B rulebook",
      "href": "/implementation-resources",
      "coverage": "direct"
    },
    {
      "type": "resource",
      "label": "SEPA Direct Debit Core implementation guidelines and XSDs",
      "href": "/implementation-resources",
      "coverage": "direct"
    },
    {
      "type": "resource",
      "label": "SEPA Direct Debit Core rulebook",
      "href": "/implementation-resources",
      "coverage": "direct"
    },
    {
      "type": "resource",
      "label": "SEPA direct-debit implementation pack",
      "href": "/downloads/profile-packs/sepa-direct-debit",
      "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": "camt.029 resolution of investigation",
      "href": "/message-samples/camt-029",
      "coverage": "derived"
    },
    {
      "type": "sample",
      "label": "camt.052 intraday account report",
      "href": "/message-samples/camt-052",
      "coverage": "derived"
    },
    {
      "type": "sample",
      "label": "camt.053 account statement",
      "href": "/message-samples/camt-053",
      "coverage": "derived"
    },
    {
      "type": "sample",
      "label": "camt.054 debit notification",
      "href": "/message-samples/camt-054",
      "coverage": "derived"
    },
    {
      "type": "sample",
      "label": "camt.055 customer cancellation request",
      "href": "/message-samples/camt-055",
      "coverage": "derived"
    },
    {
      "type": "sample",
      "label": "camt.056 payment cancellation request",
      "href": "/message-samples/camt-056",
      "coverage": "derived"
    },
    {
      "type": "sample",
      "label": "camt.110 investigation request",
      "href": "/message-samples/camt-110",
      "coverage": "derived"
    },
    {
      "type": "sample",
      "label": "camt.111 investigation response",
      "href": "/message-samples/camt-111",
      "coverage": "derived"
    },
    {
      "type": "sample",
      "label": "MT192 cancellation request",
      "href": "/message-samples/mt192",
      "coverage": "derived"
    },
    {
      "type": "sample",
      "label": "MT195 payment query",
      "href": "/message-samples/mt195",
      "coverage": "derived"
    },
    {
      "type": "sample",
      "label": "MT196 substantive answer",
      "href": "/message-samples/mt196",
      "coverage": "derived"
    },
    {
      "type": "sample",
      "label": "MT199 free-format payment message",
      "href": "/message-samples/mt199",
      "coverage": "derived"
    },
    {
      "type": "sample",
      "label": "MT900 debit confirmation",
      "href": "/message-samples/mt900",
      "coverage": "derived"
    },
    {
      "type": "sample",
      "label": "MT910 credit confirmation",
      "href": "/message-samples/mt910",
      "coverage": "derived"
    },
    {
      "type": "sample",
      "label": "MT940 customer statement",
      "href": "/message-samples/mt940",
      "coverage": "derived"
    },
    {
      "type": "sample",
      "label": "MT941 balance report",
      "href": "/message-samples/mt941",
      "coverage": "derived"
    },
    {
      "type": "sample",
      "label": "MT942 interim transaction report",
      "href": "/message-samples/mt942",
      "coverage": "derived"
    },
    {
      "type": "sample",
      "label": "MT950 statement message",
      "href": "/message-samples/mt950",
      "coverage": "derived"
    },
    {
      "type": "sample",
      "label": "pacs.004 payment return",
      "href": "/message-samples/pacs-004",
      "coverage": "derived"
    },
    {
      "type": "sample",
      "label": "pacs.007 payment reversal",
      "href": "/message-samples/pacs-007",
      "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": "A warning that works: Verification of Payee returns NO MATCH",
      "href": "/explore/exceptions/vop-no-match-abandon",
      "coverage": "derived"
    },
    {
      "type": "scenario",
      "label": "Address does not resolve: an IMPS transfer that fails instantly",
      "href": "/explore/exceptions/in-imps-invalid-mmid",
      "coverage": "derived"
    },
    {
      "type": "scenario",
      "label": "Cannot be applied: a FAST transfer the receiver rejects",
      "href": "/explore/exceptions/sg-fast-beneficiary-reject",
      "coverage": "derived"
    },
    {
      "type": "scenario",
      "label": "Close match: Verification of Payee warns of a near name",
      "href": "/explore/exceptions/vop-close-match",
      "coverage": "derived"
    },
    {
      "type": "scenario",
      "label": "Cover missing: an ISO 20022 cover payment that does not match",
      "href": "/explore/exceptions/mx-cover-mismatch",
      "coverage": "derived"
    },
    {
      "type": "scenario",
      "label": "Held at MAS: a MEPS+ payment short of RTGS-account funds",
      "href": "/explore/exceptions/sg-meps-liquidity-queue",
      "coverage": "derived"
    },
    {
      "type": "scenario",
      "label": "Held for a check: a PAPSS payment paused before it is forwarded",
      "href": "/explore/exceptions/papss-compliance-hold",
      "coverage": "derived"
    },
    {
      "type": "scenario",
      "label": "Held for a net position: a CHIPS payment waiting to net",
      "href": "/explore/exceptions/chips-position-wait",
      "coverage": "derived"
    },
    {
      "type": "scenario",
      "label": "Held in SIC: a Swiss payment waiting for cover",
      "href": "/explore/exceptions/ch-sic-cover-queue",
      "coverage": "derived"
    },
    {
      "type": "scenario",
      "label": "Held in the queue: a CHAPS payment waiting for liquidity",
      "href": "/explore/exceptions/chaps-liquidity-hold",
      "coverage": "derived"
    },
    {
      "type": "scenario",
      "label": "Held, not rejected: a T2 payment queued for liquidity",
      "href": "/explore/exceptions/t2-liquidity-queue",
      "coverage": "derived"
    },
    {
      "type": "scenario",
      "label": "Insufficient funds: a Core direct debit returned",
      "href": "/explore/exceptions/sdd-core-insufficient-funds-return",
      "coverage": "derived"
    },
    {
      "type": "scenario",
      "label": "Just missed the cycle: a STEP2 transfer re-dated to the next batch",
      "href": "/explore/exceptions/step2-missed-cutoff",
      "coverage": "derived"
    },
    {
      "type": "scenario",
      "label": "Missed the half-hour: a NEFT transfer waits for the next batch",
      "href": "/explore/exceptions/in-neft-next-batch",
      "coverage": "derived"
    },
    {
      "type": "scenario",
      "label": "No confirmation at ten seconds: an instant payment with an unresolved outcome",
      "href": "/explore/exceptions/sct-inst-timeout",
      "coverage": "derived"
    },
    {
      "type": "scenario",
      "label": "No refund by design: an authorised B2B collection stands",
      "href": "/explore/exceptions/sdd-b2b-no-refund",
      "coverage": "derived"
    },
    {
      "type": "scenario",
      "label": "No registered mandate: a B2B collection refused up front",
      "href": "/explore/exceptions/sdd-b2b-mandate-not-registered",
      "coverage": "derived"
    },
    {
      "type": "scenario",
      "label": "No take-backs: an RTP payment can only be asked to be returned",
      "href": "/explore/exceptions/rtp-no-recall",
      "coverage": "derived"
    },
    {
      "type": "scenario",
      "label": "Not accepted: an Interac e-Transfer that is declined or expires",
      "href": "/explore/exceptions/ca-interac-declined-expired",
      "coverage": "derived"
    },
    {
      "type": "scenario",
      "label": "Not enough money to send: an SCT rejected at the first gate",
      "href": "/explore/exceptions/sct-insufficient-funds-reject",
      "coverage": "derived"
    },
    {
      "type": "scenario",
      "label": "Not on the list, still blocked: ownership adds up",
      "href": "/screening/lab/ownership-escalation",
      "coverage": "derived"
    },
    {
      "type": "scenario",
      "label": "Nothing settles: a FedNow payment the receiver cannot apply",
      "href": "/explore/exceptions/fednow-receiver-reject",
      "coverage": "derived"
    },
    {
      "type": "scenario",
      "label": "Paid twice: recalling a duplicate SCT",
      "href": "/explore/exceptions/sct-duplicate-recall",
      "coverage": "derived"
    },
    {
      "type": "scenario",
      "label": "Possible match: a Buna payment held for investigation",
      "href": "/explore/exceptions/buna-screening-hold",
      "coverage": "derived"
    },
    {
      "type": "scenario",
      "label": "Queued at Banxico: a SPEI payment short of balance",
      "href": "/explore/exceptions/mx-spei-liquidity-queue",
      "coverage": "derived"
    },
    {
      "type": "scenario",
      "label": "Queued at the BCB: an STR payment short of reserves",
      "href": "/explore/exceptions/br-str-reserves-queue",
      "coverage": "derived"
    },
    {
      "type": "scenario",
      "label": "Queued at the BOJ: a large-value payment short of funds",
      "href": "/explore/exceptions/jp-bojnet-queue",
      "coverage": "derived"
    },
    {
      "type": "scenario",
      "label": "Queued at the RBA: a RITS payment waiting on the ESA",
      "href": "/explore/exceptions/au-rits-queue",
      "coverage": "derived"
    },
    {
      "type": "scenario",
      "label": "Queued at the RBI: an RTGS transfer waiting for funds",
      "href": "/explore/exceptions/in-rtgs-queue",
      "coverage": "derived"
    },
    {
      "type": "scenario",
      "label": "Queued in CHATS: a Hong Kong RTGS payment short of balance",
      "href": "/explore/exceptions/hk-chats-queue",
      "coverage": "derived"
    },
    {
      "type": "scenario",
      "label": "Queued in Lynx: a Canadian wire short of settlement balance",
      "href": "/explore/exceptions/ca-lynx-balance-queue",
      "coverage": "derived"
    },
    {
      "type": "scenario",
      "label": "Returned through the batch: an ACH entry the RDFI cannot apply",
      "href": "/explore/exceptions/ach-return",
      "coverage": "derived"
    },
    {
      "type": "scenario",
      "label": "Returned through Zengin: a retail transfer the receiver cannot apply",
      "href": "/explore/exceptions/jp-zengin-return",
      "coverage": "derived"
    },
    {
      "type": "scenario",
      "label": "Settlement setup unavailable: a FedNow payment rejected before processing",
      "href": "/explore/exceptions/fednow-settlement-relationship-unavailable",
      "coverage": "derived"
    },
    {
      "type": "scenario",
      "label": "Stopped for screening: a sanctions hold at the intermediary",
      "href": "/explore/exceptions/cbpr-sanctions-hold",
      "coverage": "derived"
    },
    {
      "type": "scenario",
      "label": "Strong name, wrong person: identifiers decide",
      "href": "/screening/lab/secondary-identifier-clear",
      "coverage": "derived"
    },
    {
      "type": "scenario",
      "label": "Taking it back: an 8-week no-questions-asked SDD refund",
      "href": "/explore/exceptions/sdd-core-8-week-refund",
      "coverage": "derived"
    },
    {
      "type": "scenario",
      "label": "The account is closed: a returned SCT",
      "href": "/explore/exceptions/sct-closed-account-return",
      "coverage": "derived"
    },
    {
      "type": "scenario",
      "label": "The address that lost its shape: truncated data needs repair",
      "href": "/explore/exceptions/cbpr-truncation-repair",
      "coverage": "derived"
    },
    {
      "type": "scenario",
      "label": "The alias that was the real name",
      "href": "/screening/lab/alias-true-match",
      "coverage": "derived"
    },
    {
      "type": "scenario",
      "label": "The announcement without the money: a cover that never matched",
      "href": "/explore/exceptions/swift-cover-mismatch",
      "coverage": "derived"
    },
    {
      "type": "scenario",
      "label": "The beneficiary bank says no: an instant payment rejected in seconds",
      "href": "/explore/exceptions/sct-inst-beneficiary-reject",
      "coverage": "derived"
    },
    {
      "type": "scenario",
      "label": "The hit hiding in the remittance line",
      "href": "/screening/lab/free-text-message-hit",
      "coverage": "derived"
    },
    {
      "type": "scenario",
      "label": "TIPS explicitly expires an instant payment",
      "href": "/explore/exceptions/tips-timeout-unwind",
      "coverage": "derived"
    },
    {
      "type": "scenario",
      "label": "Too big for Faster Payments: rerouted via CHAPS",
      "href": "/explore/exceptions/fps-limit-reroute",
      "coverage": "derived"
    },
    {
      "type": "scenario",
      "label": "Too late for today: an MT103 that missed the cut-off",
      "href": "/explore/exceptions/swift-missed-cutoff",
      "coverage": "derived"
    },
    {
      "type": "scenario",
      "label": "Unknown FPS proxy: a Hong Kong payment that fails up front",
      "href": "/explore/exceptions/hk-fps-proxy-unresolved",
      "coverage": "derived"
    },
    {
      "type": "scenario",
      "label": "Unknown PayID: an NPP payment that never leaves the app",
      "href": "/explore/exceptions/au-npp-payid-unresolved",
      "coverage": "derived"
    },
    {
      "type": "scenario",
      "label": "Unknown Pix key: a Brazilian payment that fails up front",
      "href": "/explore/exceptions/br-pix-key-unresolved",
      "coverage": "derived"
    },
    {
      "type": "scenario",
      "label": "Unknown UPI ID: a payment that never leaves the phone",
      "href": "/explore/exceptions/in-upi-vpa-unresolved",
      "coverage": "derived"
    },
    {
      "type": "scenario",
      "label": "Unpaid direct debit: the ARUDD return after settlement day",
      "href": "/explore/exceptions/bacs-direct-debit-arudd",
      "coverage": "derived"
    },
    {
      "type": "scenario",
      "label": "Unpaid EMI: a NACH Debit returned through the batch",
      "href": "/explore/exceptions/in-nach-return",
      "coverage": "derived"
    },
    {
      "type": "scenario",
      "label": "Unregistered PayNow: a proxy that maps to no account",
      "href": "/explore/exceptions/sg-paynow-proxy-unresolved",
      "coverage": "derived"
    },
    {
      "type": "scenario",
      "label": "Visible on the Tracker: a gpi payment held for a check",
      "href": "/explore/exceptions/swift-gpi-held-tracked",
      "coverage": "derived"
    },
    {
      "type": "scenario",
      "label": "Waiting on liquidity: a Fedwire payment short of Reserve funds",
      "href": "/explore/exceptions/fedwire-insufficient-balance",
      "coverage": "derived"
    },
    {
      "type": "scenario",
      "label": "Waiting on the direct participant: a CIPS indirect-access delay",
      "href": "/explore/exceptions/cips-indirect-delay",
      "coverage": "derived"
    },
    {
      "type": "scenario",
      "label": "We want it back, they say no: a refused SCT Inst recall",
      "href": "/explore/exceptions/sct-inst-recall-refused",
      "coverage": "derived"
    },
    {
      "type": "scenario",
      "label": "Whose money is this? A request for information before crediting",
      "href": "/explore/exceptions/cbpr-request-for-information",
      "coverage": "derived"
    },
    {
      "type": "scenario",
      "label": "Wrong account number abroad: a returned MT103",
      "href": "/explore/exceptions/swift-invalid-account-return",
      "coverage": "derived"
    },
    {
      "type": "scenario",
      "label": "Wrong account: a Bacs Direct Credit returned through the cycle",
      "href": "/explore/exceptions/bacs-direct-credit-return",
      "coverage": "derived"
    },
    {
      "type": "topic",
      "label": "A day in payment operations",
      "href": "/learn/operations/a-day-in-payment-operations",
      "coverage": "direct"
    },
    {
      "type": "topic",
      "label": "Accounting entries and ledgers",
      "href": "/learn/operations/accounting-entries-and-ledgers",
      "coverage": "direct"
    },
    {
      "type": "topic",
      "label": "Cheque clearing and truncation",
      "href": "/learn/foundations/cheque-clearing-and-truncation",
      "coverage": "derived"
    },
    {
      "type": "topic",
      "label": "Correspondent banking, nostro & vostro",
      "href": "/learn/foundations/correspondent-banking-nostro-vostro",
      "coverage": "derived"
    },
    {
      "type": "topic",
      "label": "Exceptions and investigations",
      "href": "/learn/operations/exceptions-and-investigations",
      "coverage": "direct"
    },
    {
      "type": "topic",
      "label": "MT101: the request for transfer",
      "href": "/learn/swift-mt/mt101-request-for-transfer",
      "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": "MT9xx: confirmations and statements",
      "href": "/learn/swift-mt/mt9xx-statements-and-confirmations",
      "coverage": "derived"
    },
    {
      "type": "topic",
      "label": "Nostro reconciliation",
      "href": "/learn/operations/nostro-reconciliation",
      "coverage": "direct"
    },
    {
      "type": "topic",
      "label": "Payment engines and hub architecture",
      "href": "/learn/operations/payment-hub-architecture",
      "coverage": "direct"
    },
    {
      "type": "topic",
      "label": "Payment security and fraud basics",
      "href": "/learn/operations/payment-security-and-fraud-basics",
      "coverage": "derived"
    },
    {
      "type": "topic",
      "label": "R-transactions: reject, return, recall",
      "href": "/learn/sepa/r-transactions-reject-return-recall",
      "coverage": "derived"
    },
    {
      "type": "topic",
      "label": "Serial versus cover routing",
      "href": "/learn/swift-mt/serial-vs-cover-routing",
      "coverage": "derived"
    },
    {
      "type": "topic",
      "label": "The camt family: cash management & investigations",
      "href": "/learn/iso-20022/camt-family-cash-management",
      "coverage": "derived"
    },
    {
      "type": "topic",
      "label": "The pacs family: interbank messages",
      "href": "/learn/iso-20022/pacs-family-interbank-messages",
      "coverage": "derived"
    },
    {
      "type": "topic",
      "label": "The pain family: payment initiation",
      "href": "/learn/iso-20022/pain-family-payment-initiation",
      "coverage": "derived"
    },
    {
      "type": "topic",
      "label": "Treasury liquidity structures",
      "href": "/learn/operations/treasury-liquidity-structures",
      "coverage": "derived"
    }
  ]
}