{
  "generatedFrom": "Payments Signal canonical architecture registry",
  "reviewDate": "2026-07-23",
  "blueprint": {
    "id": "architecture-enterprise-payments",
    "slug": "enterprise-payments-landscape",
    "title": "Enterprise payments capability and system landscape",
    "shortTitle": "Enterprise landscape",
    "family": "foundation",
    "summary": "Start with the whole estate: the customer asks, the bank controls and records, an external arrangement clears or settles, and operations prove the result.",
    "audience": "Aspiring payment architects, solution architects, business analysts, operations leads, and technology teams",
    "reviewDate": "2026-07-23",
    "versionLabel": "Reference architecture v1",
    "status": "current",
    "nodes": [
      {
        "dataClassification": [
          "Payment instruction and operational metadata"
        ],
        "nonFunctionalRequirements": [
          "Traceable processing with stable identifiers",
          "Capacity and availability matched to the supported payment service",
          "Auditable state changes and operator actions"
        ],
        "evidence": [
          {
            "ref": {
              "sourceId": "payments-signal-editorial",
              "label": "simplified-educational-illustration",
              "locator": "Component: Customer or operations user",
              "simplifications": "Component boundaries and product names vary between institutions."
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "Payments Signal reference architecture v1"
          }
        ],
        "id": "customer",
        "title": "Customer or operations user",
        "shortTitle": "Customer",
        "kind": "actor",
        "summary": "The person or system that asks the bank to move money.",
        "responsibilities": [
          "Provide the payment intent",
          "Approve the instruction",
          "Receive a clear outcome"
        ],
        "owner": "Customer, corporate treasury, or bank operations",
        "inputs": [
          "Invoice, beneficiary details, amount, currency, requested execution date"
        ],
        "outputs": [
          "Approved payment instruction"
        ],
        "interfaceContracts": [
          "Channel authentication and payment-initiation contract"
        ],
        "controls": [
          "Strong authentication where applicable",
          "Entitlement and approval limits"
        ],
        "failureModes": [
          "Incorrect details",
          "Duplicate submission",
          "Expired approval"
        ],
        "recovery": [
          "Repair before release",
          "Cancel while still cancellable",
          "Submit a new instruction only after outcome is known"
        ],
        "lenses": [
          "business",
          "ownership",
          "controls"
        ],
        "relatedTargets": [
          {
            "type": "topic",
            "id": "foundations.parties-in-a-payment"
          },
          {
            "type": "topic",
            "id": "foundations.payment-lifecycle"
          }
        ]
      },
      {
        "dataClassification": [
          "Payment instruction and operational metadata"
        ],
        "nonFunctionalRequirements": [
          "Traceable processing with stable identifiers",
          "Capacity and availability matched to the supported payment service",
          "Auditable state changes and operator actions"
        ],
        "evidence": [
          {
            "ref": {
              "sourceId": "payments-signal-editorial",
              "label": "simplified-educational-illustration",
              "locator": "Component: Payment channel",
              "simplifications": "Component boundaries and product names vary between institutions."
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "Payments Signal reference architecture v1"
          }
        ],
        "id": "channel",
        "title": "Payment channel",
        "kind": "channel",
        "summary": "The controlled doorway through which an instruction enters the bank.",
        "responsibilities": [
          "Capture data",
          "Authenticate the user",
          "Apply channel limits",
          "Return immediate status"
        ],
        "owner": "Digital channels or corporate channels",
        "inputs": [
          "Customer instruction and authentication evidence"
        ],
        "outputs": [
          "Normalised intake request"
        ],
        "interfaceContracts": [
          "API, file, host-to-host, branch, or operator-entry contract"
        ],
        "controls": [
          "Authentication",
          "Entitlements",
          "Input validation",
          "Rate and amount limits"
        ],
        "failureModes": [
          "Malformed request",
          "Authentication failure",
          "Channel timeout"
        ],
        "recovery": [
          "Reject safely before acceptance",
          "Preserve a client reference for retry and enquiry"
        ],
        "lenses": [
          "business",
          "applications",
          "interfaces",
          "controls",
          "ownership"
        ]
      },
      {
        "dataClassification": [
          "Payment instruction and operational metadata"
        ],
        "nonFunctionalRequirements": [
          "Traceable processing with stable identifiers",
          "Capacity and availability matched to the supported payment service",
          "Auditable state changes and operator actions"
        ],
        "evidence": [
          {
            "ref": {
              "sourceId": "payments-signal-editorial",
              "label": "simplified-educational-illustration",
              "locator": "Payment hub reference boundary",
              "simplifications": "A real bank may distribute these capabilities across several products, services, or legacy platforms."
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "Payments Signal reference architecture v1"
          },
          {
            "ref": {
              "sourceId": "iso20022-catalogue",
              "label": "official-requirement",
              "locator": "Payments business area and message catalogue"
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "ISO 20022 catalogue — select the implementation community and message version in force"
          }
        ],
        "id": "payment-hub",
        "title": "Payment hub and processing core",
        "shortTitle": "Payment hub",
        "kind": "application",
        "summary": "The bank’s coordinator: it decides what happens next and remembers what already happened.",
        "responsibilities": [
          "Validate and enrich",
          "Coordinate screening and fraud checks",
          "Choose a route",
          "Control posting and release",
          "Track the complete lifecycle"
        ],
        "owner": "Payments technology and payments product",
        "inputs": [
          "Accepted intake request",
          "Reference data",
          "Control outcomes"
        ],
        "outputs": [
          "Recorded payment state",
          "Posting request",
          "Network instruction",
          "Status"
        ],
        "interfaceContracts": [
          "Canonical payment contract",
          "State and idempotency contract"
        ],
        "messageIds": [
          "pain-001",
          "pain-002",
          "pacs-008",
          "pacs-002"
        ],
        "controls": [
          "Duplicate detection",
          "Validation",
          "State transition rules",
          "Four-eyes repair where required"
        ],
        "failureModes": [
          "Stalled workflow",
          "Conflicting status",
          "Incorrect route",
          "Partial downstream success"
        ],
        "recovery": [
          "Resume from the last durable state",
          "Reconcile before replay",
          "Escalate ambiguous outcomes"
        ],
        "lenses": [
          "applications",
          "interfaces",
          "data",
          "controls",
          "ownership",
          "operations",
          "resilience"
        ],
        "relatedTargets": [
          {
            "type": "topic",
            "id": "ops.payment-hub-architecture"
          }
        ]
      },
      {
        "dataClassification": [
          "Payment instruction and operational metadata"
        ],
        "nonFunctionalRequirements": [
          "Traceable processing with stable identifiers",
          "Capacity and availability matched to the supported payment service",
          "Auditable state changes and operator actions"
        ],
        "evidence": [
          {
            "ref": {
              "sourceId": "payments-signal-editorial",
              "label": "simplified-educational-illustration",
              "locator": "Component: Reference and standing data",
              "simplifications": "Component boundaries and product names vary between institutions."
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "Payments Signal reference architecture v1"
          }
        ],
        "id": "reference-data",
        "title": "Reference and standing data",
        "kind": "data-store",
        "summary": "The controlled facts used to validate, enrich, and route a payment.",
        "responsibilities": [
          "Provide BICs and clearing identifiers",
          "Provide calendars and cut-offs",
          "Provide standing settlement instructions"
        ],
        "owner": "Reference-data operations",
        "inputs": [
          "Official directories",
          "Scheme publications",
          "Approved internal configuration"
        ],
        "outputs": [
          "Versioned routing and enrichment facts"
        ],
        "interfaceContracts": [
          "Read contract with effective dates and provenance"
        ],
        "controls": [
          "Maker-checker updates",
          "Freshness monitoring",
          "Rollback",
          "Provenance"
        ],
        "failureModes": [
          "Stale directory",
          "Missing route",
          "Incorrect effective date"
        ],
        "recovery": [
          "Stop affected routing",
          "Restore a verified version",
          "Revalidate impacted payments"
        ],
        "lenses": [
          "applications",
          "data",
          "controls",
          "ownership",
          "operations",
          "resilience"
        ]
      },
      {
        "dataClassification": [
          "Payment instruction and operational metadata"
        ],
        "nonFunctionalRequirements": [
          "Traceable processing with stable identifiers",
          "Capacity and availability matched to the supported payment service",
          "Auditable state changes and operator actions"
        ],
        "evidence": [
          {
            "ref": {
              "sourceId": "payments-signal-editorial",
              "label": "simplified-educational-illustration",
              "locator": "Component: Screening and fraud controls",
              "simplifications": "Component boundaries and product names vary between institutions."
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "Payments Signal reference architecture v1"
          }
        ],
        "id": "screening-risk",
        "title": "Screening and fraud controls",
        "shortTitle": "Control services",
        "kind": "control",
        "summary": "The checkpoints that decide whether processing may continue, must pause, or must stop.",
        "responsibilities": [
          "Screen relevant parties and text",
          "Assess fraud risk",
          "Return a reasoned outcome"
        ],
        "owner": "Financial crime and fraud operations",
        "inputs": [
          "Payment parties, identifiers, addresses, remittance, device and behaviour signals"
        ],
        "outputs": [
          "Proceed, hold, reject, or investigate outcome"
        ],
        "interfaceContracts": [
          "Time-bounded control-decision contract"
        ],
        "controls": [
          "List currency",
          "Decision trace",
          "Threshold governance",
          "Case correlation"
        ],
        "failureModes": [
          "Control unavailable",
          "Alert spike",
          "Unmapped field",
          "Duplicate alert"
        ],
        "recovery": [
          "Apply the documented failure posture",
          "Queue or stop safely",
          "Re-screen after recovery"
        ],
        "lenses": [
          "controls",
          "interfaces",
          "data",
          "ownership",
          "operations",
          "resilience"
        ],
        "relatedTargets": [
          {
            "type": "topic",
            "id": "screening-execution.architecture"
          }
        ]
      },
      {
        "dataClassification": [
          "Payment instruction and operational metadata"
        ],
        "nonFunctionalRequirements": [
          "Traceable processing with stable identifiers",
          "Capacity and availability matched to the supported payment service",
          "Auditable state changes and operator actions"
        ],
        "evidence": [
          {
            "ref": {
              "sourceId": "payments-signal-editorial",
              "label": "simplified-educational-illustration",
              "locator": "Component: Customer and internal ledger",
              "simplifications": "Component boundaries and product names vary between institutions."
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "Payments Signal reference architecture v1"
          }
        ],
        "id": "customer-ledger",
        "title": "Customer and internal ledger",
        "shortTitle": "Ledger",
        "kind": "ledger",
        "summary": "The bank’s books: holds, debits, credits, suspense, fees, and settlement-account mirrors.",
        "responsibilities": [
          "Check available funds",
          "Reserve or post value",
          "Preserve balanced accounting",
          "Expose booking evidence"
        ],
        "owner": "Core banking and finance",
        "inputs": [
          "Authorised posting command"
        ],
        "outputs": [
          "Posting result and immutable accounting reference"
        ],
        "interfaceContracts": [
          "Idempotent posting contract"
        ],
        "controls": [
          "Balanced entries",
          "Posting uniqueness",
          "Reversal instead of erasure",
          "Account entitlement"
        ],
        "failureModes": [
          "Insufficient funds",
          "Posting timeout",
          "Conflicting duplicate",
          "Unbalanced entry"
        ],
        "recovery": [
          "Query by posting key",
          "Reverse with an equal and opposite entry",
          "Never retry blindly"
        ],
        "lenses": [
          "ledger",
          "applications",
          "interfaces",
          "data",
          "controls",
          "ownership",
          "resilience"
        ],
        "relatedTargets": [
          {
            "type": "topic",
            "id": "foundations.money-and-bank-accounts"
          },
          {
            "type": "topic",
            "id": "ops.accounting-and-ledgers"
          }
        ]
      },
      {
        "dataClassification": [
          "Payment instruction and operational metadata"
        ],
        "nonFunctionalRequirements": [
          "Traceable processing with stable identifiers",
          "Capacity and availability matched to the supported payment service",
          "Auditable state changes and operator actions"
        ],
        "evidence": [
          {
            "ref": {
              "sourceId": "payments-signal-editorial",
              "label": "simplified-educational-illustration",
              "locator": "Component: Rail or network gateway",
              "simplifications": "Component boundaries and product names vary between institutions."
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "Payments Signal reference architecture v1"
          }
        ],
        "id": "network-gateway",
        "title": "Rail or network gateway",
        "shortTitle": "Gateway",
        "kind": "gateway",
        "summary": "The edge adapter that speaks one external network’s protocol.",
        "responsibilities": [
          "Transform the outbound envelope",
          "Sign and transmit",
          "Receive acknowledgements and reports"
        ],
        "owner": "Payments connectivity",
        "inputs": [
          "Released network instruction"
        ],
        "outputs": [
          "Delivery evidence, acknowledgement, status, report"
        ],
        "interfaceContracts": [
          "Network-specific transport and security contract"
        ],
        "messageIds": [
          "pacs-008",
          "pacs-002",
          "camt-052",
          "camt-053",
          "mt103",
          "mt940"
        ],
        "controls": [
          "Network entitlement",
          "Message signing",
          "Sequence and duplicate checks",
          "Delivery reconciliation"
        ],
        "failureModes": [
          "Network unavailable",
          "Transport rejection",
          "Unknown delivery outcome"
        ],
        "recovery": [
          "Query network evidence",
          "Resubmit only under the network’s duplicate rules",
          "Escalate ambiguity"
        ],
        "lenses": [
          "applications",
          "interfaces",
          "controls",
          "ownership",
          "operations",
          "resilience"
        ]
      },
      {
        "dataClassification": [
          "Payment instruction and operational metadata"
        ],
        "nonFunctionalRequirements": [
          "Traceable processing with stable identifiers",
          "Capacity and availability matched to the supported payment service",
          "Auditable state changes and operator actions"
        ],
        "evidence": [
          {
            "ref": {
              "sourceId": "bis-cpmi-pfmi",
              "label": "official-requirement",
              "locator": "Principles 8, 9, 17, and 22"
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "CPMI-IOSCO Principles for financial market infrastructures",
            "asOf": "2012-04-16"
          },
          {
            "ref": {
              "sourceId": "payments-signal-editorial",
              "label": "simplified-educational-illustration",
              "locator": "External payment network boundary",
              "simplifications": "Clearing and settlement may be performed by different infrastructures and at different times."
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "Payments Signal reference architecture v1"
          }
        ],
        "id": "payment-network",
        "title": "Payment network or market infrastructure",
        "shortTitle": "External rail",
        "kind": "external-network",
        "summary": "The external arrangement that exchanges, clears, or settles obligations under its own rules.",
        "responsibilities": [
          "Validate participant submissions",
          "Apply service rules",
          "Clear or settle as applicable",
          "Return evidence"
        ],
        "owner": "Scheme, network, clearing system, or central bank",
        "inputs": [
          "Network-valid instruction"
        ],
        "outputs": [
          "Acceptance, rejection, clearing result, settlement result, reports"
        ],
        "interfaceContracts": [
          "Scheme or infrastructure rulebook and usage guideline"
        ],
        "controls": [
          "Participant eligibility",
          "Message validation",
          "Finality rules",
          "Operational timetable"
        ],
        "failureModes": [
          "Scheme rejection",
          "Liquidity queue",
          "Service outage",
          "Participant unavailable"
        ],
        "recovery": [
          "Follow scheme contingency and enquiry procedures",
          "Preserve finality and duplicate rules"
        ],
        "lenses": [
          "business",
          "interfaces",
          "ledger",
          "controls",
          "ownership",
          "operations",
          "resilience"
        ]
      },
      {
        "dataClassification": [
          "Payment instruction and operational metadata"
        ],
        "nonFunctionalRequirements": [
          "Traceable processing with stable identifiers",
          "Capacity and availability matched to the supported payment service",
          "Auditable state changes and operator actions"
        ],
        "evidence": [
          {
            "ref": {
              "sourceId": "payments-signal-editorial",
              "label": "simplified-educational-illustration",
              "locator": "Component: Receiving institution",
              "simplifications": "Component boundaries and product names vary between institutions."
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "Payments Signal reference architecture v1"
          }
        ],
        "id": "receiving-bank",
        "title": "Receiving institution",
        "shortTitle": "Receiving bank",
        "kind": "infrastructure",
        "summary": "The institution that accepts the interbank instruction and credits or otherwise services the receiving account.",
        "responsibilities": [
          "Validate receipt",
          "Apply controls",
          "Post the beneficiary side",
          "Return status and reporting"
        ],
        "owner": "Receiving institution",
        "inputs": [
          "Interbank payment and settlement evidence"
        ],
        "outputs": [
          "Beneficiary posting, status, return or investigation"
        ],
        "interfaceContracts": [
          "Scheme or correspondent bilateral contract"
        ],
        "controls": [
          "Beneficiary validation",
          "Screening",
          "Posting correlation",
          "Return controls"
        ],
        "failureModes": [
          "Invalid beneficiary",
          "Account closed",
          "Posting delay",
          "Return required"
        ],
        "recovery": [
          "Reject before finality where allowed",
          "Return through the governed process after settlement"
        ],
        "lenses": [
          "business",
          "interfaces",
          "ledger",
          "controls",
          "ownership",
          "operations"
        ]
      },
      {
        "dataClassification": [
          "Payment instruction and operational metadata"
        ],
        "nonFunctionalRequirements": [
          "Traceable processing with stable identifiers",
          "Capacity and availability matched to the supported payment service",
          "Auditable state changes and operator actions"
        ],
        "evidence": [
          {
            "ref": {
              "sourceId": "payments-signal-editorial",
              "label": "simplified-educational-illustration",
              "locator": "Component: Operations, investigations, and reconciliation",
              "simplifications": "Component boundaries and product names vary between institutions."
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "Payments Signal reference architecture v1"
          }
        ],
        "id": "operations",
        "title": "Operations, investigations, and reconciliation",
        "shortTitle": "Operations",
        "kind": "operations",
        "summary": "The people and queues that resolve anything the automated path cannot prove safely.",
        "responsibilities": [
          "Monitor queues",
          "Repair permitted data",
          "Investigate holds",
          "Reconcile postings and external evidence"
        ],
        "owner": "Payment operations",
        "inputs": [
          "Exceptions, alerts, acknowledgements, statements, ledger entries"
        ],
        "outputs": [
          "Released, repaired, returned, escalated, or reconciled outcome"
        ],
        "interfaceContracts": [
          "Case, audit, and evidence contract"
        ],
        "controls": [
          "Segregation of duties",
          "Reason codes",
          "Service-level monitoring",
          "Audit trail"
        ],
        "failureModes": [
          "Queue backlog",
          "Incorrect manual release",
          "Missing evidence",
          "Premature closure"
        ],
        "recovery": [
          "Prioritise by risk and cut-off",
          "Require evidence before release or replay",
          "Reopen unresolved cases"
        ],
        "lenses": [
          "business",
          "controls",
          "ownership",
          "operations",
          "resilience"
        ],
        "relatedTargets": [
          {
            "type": "topic",
            "id": "ops.payment-operations-day"
          },
          {
            "type": "topic",
            "id": "ops.exceptions-investigations"
          },
          {
            "type": "topic",
            "id": "ops.reconciliation"
          }
        ]
      }
    ],
    "interfaces": [
      {
        "dataClassification": [
          "Payment and status data"
        ],
        "controls": [
          "Authentication",
          "Authorisation",
          "Integrity",
          "Correlation",
          "Audit"
        ],
        "evidence": [
          {
            "ref": {
              "sourceId": "payments-signal-editorial",
              "label": "simplified-educational-illustration",
              "locator": "Interface: Payment request",
              "simplifications": "The transport and interface contract are illustrative; implementations select their own protocol."
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "Payments Signal reference architecture v1"
          }
        ],
        "id": "customer-to-channel",
        "from": "customer",
        "to": "channel",
        "title": "Payment request",
        "kind": "api",
        "mode": "synchronous",
        "purpose": "Capture an authenticated request with a stable customer reference.",
        "protocol": "API, file, host-to-host, or operator entry",
        "failureBehaviour": "Reject before acceptance and return a reusable correlation reference.",
        "lenses": [
          "business",
          "interfaces",
          "data",
          "controls"
        ]
      },
      {
        "dataClassification": [
          "Payment and status data"
        ],
        "controls": [
          "Authentication",
          "Authorisation",
          "Integrity",
          "Correlation",
          "Audit"
        ],
        "evidence": [
          {
            "ref": {
              "sourceId": "iso20022-catalogue",
              "label": "official-requirement",
              "locator": "Payments initiation message definitions"
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "ISO 20022 catalogue — select the implementation community and message version in force"
          }
        ],
        "id": "channel-to-hub",
        "from": "channel",
        "to": "payment-hub",
        "title": "Accepted instruction",
        "kind": "message",
        "mode": "asynchronous",
        "purpose": "Hand one normalised instruction to the processing core.",
        "messageIds": [
          "pain-001"
        ],
        "failureBehaviour": "The channel must distinguish not accepted from accepted but still processing.",
        "lenses": [
          "applications",
          "interfaces",
          "data",
          "operations"
        ]
      },
      {
        "dataClassification": [
          "Payment and status data"
        ],
        "controls": [
          "Authentication",
          "Authorisation",
          "Integrity",
          "Correlation",
          "Audit"
        ],
        "evidence": [
          {
            "ref": {
              "sourceId": "payments-signal-editorial",
              "label": "simplified-educational-illustration",
              "locator": "Interface: Routing facts",
              "simplifications": "The transport and interface contract are illustrative; implementations select their own protocol."
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "Payments Signal reference architecture v1"
          }
        ],
        "id": "reference-to-hub",
        "from": "reference-data",
        "to": "payment-hub",
        "title": "Routing facts",
        "kind": "api",
        "mode": "synchronous",
        "purpose": "Supply versioned routing, calendar, and enrichment data.",
        "failureBehaviour": "Do not guess a route when authoritative reference data is missing or stale.",
        "lenses": [
          "applications",
          "interfaces",
          "data",
          "controls",
          "resilience"
        ]
      },
      {
        "dataClassification": [
          "Payment and status data"
        ],
        "controls": [
          "Authentication",
          "Authorisation",
          "Integrity",
          "Correlation",
          "Audit"
        ],
        "evidence": [
          {
            "ref": {
              "sourceId": "payments-signal-editorial",
              "label": "simplified-educational-illustration",
              "locator": "Interface: Control decision",
              "simplifications": "The transport and interface contract are illustrative; implementations select their own protocol."
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "Payments Signal reference architecture v1"
          }
        ],
        "id": "hub-to-controls",
        "from": "payment-hub",
        "to": "screening-risk",
        "title": "Control decision",
        "kind": "control",
        "mode": "synchronous",
        "purpose": "Obtain a proceed, hold, or stop outcome before the irreversible boundary.",
        "failureBehaviour": "Apply the approved failure posture; never silently bypass the checkpoint.",
        "lenses": [
          "interfaces",
          "data",
          "controls",
          "operations",
          "resilience"
        ]
      },
      {
        "dataClassification": [
          "Payment and status data"
        ],
        "controls": [
          "Authentication",
          "Authorisation",
          "Integrity",
          "Correlation",
          "Audit"
        ],
        "evidence": [
          {
            "ref": {
              "sourceId": "payments-signal-editorial",
              "label": "simplified-educational-illustration",
              "locator": "Interface: Posting command",
              "simplifications": "The transport and interface contract are illustrative; implementations select their own protocol."
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "Payments Signal reference architecture v1"
          }
        ],
        "id": "hub-to-ledger",
        "from": "payment-hub",
        "to": "customer-ledger",
        "title": "Posting command",
        "kind": "posting",
        "mode": "synchronous",
        "purpose": "Reserve or post value exactly once using a durable posting key.",
        "failureBehaviour": "Query the posting result before any retry when the response is unknown.",
        "lenses": [
          "applications",
          "interfaces",
          "ledger",
          "data",
          "controls",
          "resilience"
        ]
      },
      {
        "dataClassification": [
          "Payment and status data"
        ],
        "controls": [
          "Authentication",
          "Authorisation",
          "Integrity",
          "Correlation",
          "Audit"
        ],
        "evidence": [
          {
            "ref": {
              "sourceId": "payments-signal-editorial",
              "label": "simplified-educational-illustration",
              "locator": "Interface: Released instruction",
              "simplifications": "The transport and interface contract are illustrative; implementations select their own protocol."
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "Payments Signal reference architecture v1"
          }
        ],
        "id": "hub-to-gateway",
        "from": "payment-hub",
        "to": "network-gateway",
        "title": "Released instruction",
        "kind": "message",
        "mode": "asynchronous",
        "purpose": "Transmit the scheme-specific payment only after release controls pass.",
        "messageIds": [
          "pacs-008",
          "mt103"
        ],
        "failureBehaviour": "Record delivery evidence and prevent an unproved duplicate submission.",
        "lenses": [
          "applications",
          "interfaces",
          "data",
          "controls",
          "operations",
          "resilience"
        ]
      },
      {
        "dataClassification": [
          "Payment and status data"
        ],
        "controls": [
          "Authentication",
          "Authorisation",
          "Integrity",
          "Correlation",
          "Audit"
        ],
        "evidence": [
          {
            "ref": {
              "sourceId": "payments-signal-editorial",
              "label": "simplified-educational-illustration",
              "locator": "Interface: Network message",
              "simplifications": "The transport and interface contract are illustrative; implementations select their own protocol."
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "Payments Signal reference architecture v1"
          }
        ],
        "id": "gateway-to-network",
        "from": "network-gateway",
        "to": "payment-network",
        "title": "Network message",
        "kind": "message",
        "mode": "asynchronous",
        "purpose": "Cross the institution boundary using the network’s secured transport.",
        "messageIds": [
          "pacs-008",
          "mt103"
        ],
        "failureBehaviour": "A transport acknowledgement proves delivery, not necessarily settlement or beneficiary credit.",
        "lenses": [
          "interfaces",
          "data",
          "controls",
          "resilience"
        ]
      },
      {
        "dataClassification": [
          "Payment and status data"
        ],
        "controls": [
          "Authentication",
          "Authorisation",
          "Integrity",
          "Correlation",
          "Audit"
        ],
        "evidence": [
          {
            "ref": {
              "sourceId": "bis-cpmi-pfmi",
              "label": "official-requirement",
              "locator": "Principles 8 and 9"
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "CPMI-IOSCO Principles for financial market infrastructures",
            "asOf": "2012-04-16"
          }
        ],
        "id": "network-to-receiver",
        "from": "payment-network",
        "to": "receiving-bank",
        "title": "Cleared or routed payment",
        "kind": "settlement",
        "mode": "asynchronous",
        "purpose": "Carry the accepted obligation and, where applicable, settlement evidence to the receiver.",
        "failureBehaviour": "Apply the service’s reject, return, timeout, and contingency rules.",
        "lenses": [
          "business",
          "interfaces",
          "ledger",
          "controls",
          "operations"
        ]
      },
      {
        "dataClassification": [
          "Payment and status data"
        ],
        "controls": [
          "Authentication",
          "Authorisation",
          "Integrity",
          "Correlation",
          "Audit"
        ],
        "evidence": [
          {
            "ref": {
              "sourceId": "iso20022-catalogue",
              "label": "official-requirement",
              "locator": "Payments clearing and settlement and cash-management message definitions"
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "ISO 20022 catalogue — select the implementation community and message version in force"
          }
        ],
        "id": "evidence-to-operations",
        "from": "payment-network",
        "to": "operations",
        "title": "Status and settlement evidence",
        "kind": "message",
        "mode": "asynchronous",
        "purpose": "Feed acknowledgements, statements, and settlement results into monitoring and reconciliation.",
        "messageIds": [
          "pacs-002",
          "camt-052",
          "camt-053",
          "mt940"
        ],
        "failureBehaviour": "Keep unmatched evidence in a controlled queue rather than inventing an outcome.",
        "lenses": [
          "interfaces",
          "data",
          "ledger",
          "operations",
          "resilience"
        ]
      },
      {
        "dataClassification": [
          "Payment and status data"
        ],
        "controls": [
          "Authentication",
          "Authorisation",
          "Integrity",
          "Correlation",
          "Audit"
        ],
        "evidence": [
          {
            "ref": {
              "sourceId": "payments-signal-editorial",
              "label": "simplified-educational-illustration",
              "locator": "Interface: Internal books",
              "simplifications": "The transport and interface contract are illustrative; implementations select their own protocol."
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "Payments Signal reference architecture v1"
          }
        ],
        "id": "ledger-to-operations",
        "from": "customer-ledger",
        "to": "operations",
        "title": "Internal books",
        "kind": "event",
        "mode": "asynchronous",
        "purpose": "Provide the internal side of posting and balance reconciliation.",
        "failureBehaviour": "A missing or duplicate event creates a reconciliation break; it does not change the ledger fact.",
        "lenses": [
          "data",
          "ledger",
          "operations",
          "controls"
        ]
      }
    ],
    "views": [
      {
        "id": "context",
        "label": "Context",
        "plainPurpose": "See who asks, who processes, which outside network carries the obligation, and who receives it.",
        "nodeIds": [
          "customer",
          "channel",
          "payment-hub",
          "network-gateway",
          "payment-network",
          "receiving-bank",
          "operations"
        ],
        "interfaceIds": [
          "channel-to-hub",
          "gateway-to-network",
          "network-to-receiver",
          "evidence-to-operations"
        ],
        "placements": {
          "customer": {
            "x": 60,
            "y": 180
          },
          "channel": {
            "x": 380,
            "y": 180
          },
          "payment-hub": {
            "x": 700,
            "y": 180
          },
          "network-gateway": {
            "x": 1020,
            "y": 180
          },
          "payment-network": {
            "x": 1340,
            "y": 180
          },
          "receiving-bank": {
            "x": 1660,
            "y": 180
          },
          "operations": {
            "x": 1020,
            "y": 460
          }
        },
        "boundaries": [
          {
            "id": "bank-boundary",
            "label": "SENDING INSTITUTION",
            "nodeIds": [
              "channel",
              "payment-hub",
              "network-gateway",
              "operations"
            ],
            "kind": "ownership"
          },
          {
            "id": "external-boundary",
            "label": "EXTERNAL PAYMENT ARRANGEMENT",
            "nodeIds": [
              "payment-network"
            ],
            "kind": "network"
          }
        ]
      },
      {
        "id": "container",
        "label": "Container",
        "plainPurpose": "Open the sending bank and see the major applications, books, controls, and connection edge.",
        "nodeIds": [
          "customer",
          "channel",
          "payment-hub",
          "reference-data",
          "screening-risk",
          "customer-ledger",
          "network-gateway",
          "payment-network",
          "receiving-bank",
          "operations"
        ],
        "interfaceIds": [
          "customer-to-channel",
          "channel-to-hub",
          "reference-to-hub",
          "hub-to-controls",
          "hub-to-ledger",
          "hub-to-gateway",
          "gateway-to-network",
          "network-to-receiver",
          "evidence-to-operations",
          "ledger-to-operations"
        ],
        "placements": {
          "customer": {
            "x": 60,
            "y": 140
          },
          "channel": {
            "x": 380,
            "y": 140
          },
          "payment-hub": {
            "x": 700,
            "y": 140
          },
          "network-gateway": {
            "x": 1060,
            "y": 140
          },
          "payment-network": {
            "x": 1420,
            "y": 140
          },
          "receiving-bank": {
            "x": 1420,
            "y": 440
          },
          "reference-data": {
            "x": 380,
            "y": 440
          },
          "screening-risk": {
            "x": 700,
            "y": 360
          },
          "customer-ledger": {
            "x": 700,
            "y": 580
          },
          "operations": {
            "x": 1060,
            "y": 560
          }
        },
        "boundaries": [
          {
            "id": "sending-bank-trust",
            "label": "SENDING BANK TRUST BOUNDARY",
            "nodeIds": [
              "channel",
              "payment-hub",
              "reference-data",
              "screening-risk",
              "customer-ledger",
              "network-gateway",
              "operations"
            ],
            "kind": "trust"
          },
          {
            "id": "network-trust",
            "label": "NETWORK TRUST BOUNDARY",
            "nodeIds": [
              "payment-network"
            ],
            "kind": "network"
          }
        ]
      },
      {
        "id": "component",
        "label": "Component",
        "plainPurpose": "Focus on the processing core and the contracts that keep control, books, and delivery aligned.",
        "nodeIds": [
          "channel",
          "payment-hub",
          "reference-data",
          "screening-risk",
          "customer-ledger",
          "network-gateway",
          "operations"
        ],
        "interfaceIds": [
          "channel-to-hub",
          "reference-to-hub",
          "hub-to-controls",
          "hub-to-ledger",
          "hub-to-gateway",
          "ledger-to-operations"
        ],
        "placements": {
          "channel": {
            "x": 80,
            "y": 280
          },
          "reference-data": {
            "x": 420,
            "y": 90
          },
          "payment-hub": {
            "x": 620,
            "y": 280
          },
          "screening-risk": {
            "x": 420,
            "y": 520
          },
          "customer-ledger": {
            "x": 800,
            "y": 520
          },
          "network-gateway": {
            "x": 1120,
            "y": 280
          },
          "operations": {
            "x": 1120,
            "y": 520
          }
        }
      },
      {
        "id": "deployment",
        "label": "Deployment",
        "plainPurpose": "See the availability zones and external boundaries that must fail independently and recover predictably.",
        "nodeIds": [
          "channel",
          "payment-hub",
          "reference-data",
          "screening-risk",
          "customer-ledger",
          "network-gateway",
          "payment-network",
          "operations"
        ],
        "interfaceIds": [
          "channel-to-hub",
          "reference-to-hub",
          "hub-to-controls",
          "hub-to-ledger",
          "hub-to-gateway",
          "gateway-to-network",
          "ledger-to-operations"
        ],
        "placements": {
          "channel": {
            "x": 100,
            "y": 200
          },
          "payment-hub": {
            "x": 420,
            "y": 200
          },
          "reference-data": {
            "x": 420,
            "y": 480
          },
          "screening-risk": {
            "x": 760,
            "y": 100
          },
          "customer-ledger": {
            "x": 760,
            "y": 360
          },
          "network-gateway": {
            "x": 1080,
            "y": 200
          },
          "payment-network": {
            "x": 1400,
            "y": 200
          },
          "operations": {
            "x": 1080,
            "y": 520
          }
        },
        "boundaries": [
          {
            "id": "channel-zone",
            "label": "CHANNEL ZONE",
            "nodeIds": [
              "channel"
            ],
            "kind": "trust"
          },
          {
            "id": "processing-zone",
            "label": "PAYMENTS PROCESSING ZONE",
            "nodeIds": [
              "payment-hub",
              "reference-data",
              "screening-risk",
              "customer-ledger"
            ],
            "kind": "trust"
          },
          {
            "id": "connectivity-zone",
            "label": "NETWORK CONNECTIVITY ZONE",
            "nodeIds": [
              "network-gateway"
            ],
            "kind": "trust"
          },
          {
            "id": "external-zone",
            "label": "EXTERNAL NETWORK",
            "nodeIds": [
              "payment-network"
            ],
            "kind": "network"
          }
        ]
      }
    ],
    "traces": [
      {
        "id": "enterprise-credit-transfer",
        "label": "One controlled credit transfer",
        "summary": "Asha Traders sends one supplier payment from capture through reconciliation.",
        "viewId": "container",
        "steps": [
          {
            "id": "capture",
            "title": "Capture the instruction",
            "nodeId": "channel",
            "interfaceId": "customer-to-channel",
            "plainExplanation": "Asha Traders asks Bank Alfa to pay its supplier.",
            "businessState": "RECEIVED"
          },
          {
            "id": "accept",
            "title": "Accept into processing",
            "nodeId": "payment-hub",
            "interfaceId": "channel-to-hub",
            "plainExplanation": "The bank records one instruction with a stable identity.",
            "businessState": "ACCEPTED",
            "messageIds": [
              "pain-001"
            ]
          },
          {
            "id": "enrich",
            "title": "Resolve the route",
            "nodeId": "reference-data",
            "interfaceId": "reference-to-hub",
            "plainExplanation": "The hub reads current routing, calendar, and settlement facts.",
            "businessState": "ENRICHED"
          },
          {
            "id": "control",
            "title": "Apply control decisions",
            "nodeId": "screening-risk",
            "interfaceId": "hub-to-controls",
            "plainExplanation": "Screening and fraud controls decide whether processing may continue.",
            "businessState": "CONTROLLED",
            "controlEvidence": "Proceed decision and configuration version"
          },
          {
            "id": "post",
            "title": "Record the customer-side value",
            "nodeId": "customer-ledger",
            "interfaceId": "hub-to-ledger",
            "plainExplanation": "The bank reserves or posts the value on its own books.",
            "businessState": "POSTED",
            "ledgerEffect": "Balanced customer and internal settlement-account entries"
          },
          {
            "id": "release",
            "title": "Release to the network",
            "nodeId": "network-gateway",
            "interfaceId": "hub-to-gateway",
            "plainExplanation": "The bank creates and secures the network-specific instruction.",
            "businessState": "RELEASED",
            "messageIds": [
              "pacs-008"
            ]
          },
          {
            "id": "network",
            "title": "Clear or settle under the service rules",
            "nodeId": "payment-network",
            "interfaceId": "gateway-to-network",
            "plainExplanation": "The external service validates and processes the instruction.",
            "businessState": "NETWORK_ACCEPTED"
          },
          {
            "id": "credit",
            "title": "Service the receiving account",
            "nodeId": "receiving-bank",
            "interfaceId": "network-to-receiver",
            "plainExplanation": "The receiving institution credits the beneficiary when its rules and settlement evidence allow.",
            "businessState": "BENEFICIARY_CREDITED"
          },
          {
            "id": "reconcile",
            "title": "Prove the result",
            "nodeId": "operations",
            "interfaceId": "evidence-to-operations",
            "plainExplanation": "Operations match internal postings, network evidence, and reporting to one economic payment.",
            "businessState": "RECONCILED",
            "messageIds": [
              "camt-053"
            ]
          }
        ],
        "evidence": [
          {
            "ref": {
              "sourceId": "payments-signal-editorial",
              "label": "simplified-educational-illustration",
              "locator": "Enterprise trace",
              "simplifications": "The trace compresses institution-specific approval, posting, clearing, and settlement timing into one readable sequence."
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "Payments Signal reference architecture v1"
          },
          {
            "ref": {
              "sourceId": "iso20022-catalogue",
              "label": "official-requirement",
              "locator": "Payments initiation, clearing and settlement, and cash-management catalogues"
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "ISO 20022 catalogue — select the implementation community and message version in force"
          }
        ]
      }
    ],
    "stressCases": [
      {
        "id": "enterprise-screening-hold",
        "label": "Screening hold",
        "trigger": "The control service finds a possible sanctions-list match.",
        "divergesAfterStepId": "control",
        "traceId": "enterprise-credit-transfer",
        "affectedNodeIds": [
          "payment-hub",
          "screening-risk",
          "operations"
        ],
        "affectedInterfaceIds": [
          "hub-to-controls"
        ],
        "lastConfirmedState": "The payment is accepted and enriched but not released.",
        "settlementState": "Interbank settlement has not occurred.",
        "fundsState": "Any customer-side reservation remains controlled on Bank Alfa’s books.",
        "owner": "Sanctions investigation with payment operations monitoring the payment state",
        "safeAction": "Keep the instruction on hold until an authorised investigator records and applies a disposition.",
        "requiredEvidence": [
          "Matched fields",
          "Watchlist record and version",
          "Investigator reasoning",
          "Release or stop authority"
        ],
        "recoverySteps": [
          "Resolve the alert",
          "Apply the recorded outcome once",
          "Resume from the held state or stop under policy"
        ],
        "evidence": [
          {
            "ref": {
              "sourceId": "payments-signal-editorial",
              "label": "simplified-educational-illustration",
              "locator": "Screening-hold stress case",
              "simplifications": "Legal treatment and failure posture depend on the applicable regime and institution policy."
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "Payments Signal reference architecture v1"
          }
        ]
      },
      {
        "id": "enterprise-ledger-timeout",
        "label": "Ledger response timeout",
        "trigger": "The posting request times out after the ledger may already have accepted it.",
        "divergesAfterStepId": "post",
        "traceId": "enterprise-credit-transfer",
        "affectedNodeIds": [
          "payment-hub",
          "customer-ledger",
          "operations"
        ],
        "affectedInterfaceIds": [
          "hub-to-ledger",
          "ledger-to-operations"
        ],
        "lastConfirmedState": "Control checks passed; the posting outcome is unknown.",
        "settlementState": "The network instruction has not been released.",
        "fundsState": "The customer may already be debited or reserved, so a blind retry could double post.",
        "owner": "Payment-platform operations with core-ledger support",
        "safeAction": "Query the ledger using the original idempotency key before retrying or reversing anything.",
        "requiredEvidence": [
          "Posting key",
          "Ledger journal result",
          "Payment state history",
          "Operator decision"
        ],
        "recoverySteps": [
          "Query",
          "Correlate",
          "Adopt the proven result",
          "Retry only if the ledger proves no posting exists"
        ],
        "evidence": [
          {
            "ref": {
              "sourceId": "payments-signal-editorial",
              "label": "simplified-educational-illustration",
              "locator": "Ledger-timeout stress case",
              "simplifications": "Posting APIs and recovery commands vary by ledger platform."
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "Payments Signal reference architecture v1"
          }
        ]
      },
      {
        "id": "enterprise-network-ambiguity",
        "label": "Unknown network delivery outcome",
        "trigger": "The connection drops after transmission but before a delivery acknowledgement returns.",
        "divergesAfterStepId": "network",
        "traceId": "enterprise-credit-transfer",
        "affectedNodeIds": [
          "payment-hub",
          "network-gateway",
          "payment-network",
          "operations"
        ],
        "affectedInterfaceIds": [
          "hub-to-gateway",
          "gateway-to-network"
        ],
        "lastConfirmedState": "The instruction was released; external acceptance is not yet proven.",
        "settlementState": "Unknown until network evidence or reporting is received.",
        "fundsState": "The sending-side posting exists; the external outcome must be established before replay.",
        "owner": "Payment operations and network-connectivity support",
        "safeAction": "Use the network enquiry and duplicate-control procedure; do not create a new payment.",
        "requiredEvidence": [
          "Original network reference",
          "Transport log",
          "Network acknowledgement or enquiry",
          "Settlement report"
        ],
        "recoverySteps": [
          "Hold automatic retry",
          "Query delivery",
          "Reconcile late evidence",
          "Resume, return, or investigate based on proven status"
        ],
        "evidence": [
          {
            "ref": {
              "sourceId": "bis-cpmi-pfmi",
              "label": "official-requirement",
              "locator": "Principle 17 — operational risk"
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "CPMI-IOSCO Principles for financial market infrastructures",
            "asOf": "2012-04-16"
          }
        ]
      }
    ],
    "overlays": [],
    "decisions": [
      {
        "id": "enterprise-state-owner",
        "question": "Which component owns the authoritative payment lifecycle?",
        "options": [
          {
            "label": "Payment hub",
            "consequence": "One processing record can coordinate channels and rails, but the hub must not pretend to own ledger or settlement facts."
          },
          {
            "label": "Channel",
            "consequence": "Channel-specific state is simple at first but fragments processing and duplicate control across products."
          }
        ],
        "guidance": "Name one lifecycle owner and name the external facts it consumes; do not create two components that can both independently release the same instruction.",
        "evidence": [
          {
            "ref": {
              "sourceId": "payments-signal-editorial",
              "label": "simplified-educational-illustration",
              "locator": "Architecture decision: lifecycle ownership",
              "simplifications": "Institutions choose different system-of-record boundaries."
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "Payments Signal reference architecture v1"
          }
        ]
      },
      {
        "id": "enterprise-posting-boundary",
        "question": "When does customer posting occur relative to network release?",
        "options": [
          {
            "label": "Post or reserve before release",
            "consequence": "Controls funds before the payment leaves, but ambiguous downstream outcomes require careful reconciliation."
          },
          {
            "label": "Post after external acceptance",
            "consequence": "Reduces some reversals but requires a safe reservation and exposes a different partial-failure window."
          }
        ],
        "guidance": "Specify reservation, posting, release, reversal, and reconciliation as separate states with idempotent commands.",
        "evidence": [
          {
            "ref": {
              "sourceId": "payments-signal-editorial",
              "label": "simplified-educational-illustration",
              "locator": "Architecture decision: posting boundary",
              "simplifications": "Rail rules, credit policy, and ledger capability determine the final sequence."
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "Payments Signal reference architecture v1"
          }
        ]
      },
      {
        "id": "enterprise-control-failure",
        "question": "What happens when an in-line control is unavailable?",
        "options": [
          {
            "label": "Queue or stop",
            "consequence": "Protects the control objective but consumes the payment service’s time budget and creates an operations queue."
          },
          {
            "label": "Use an approved alternate control",
            "consequence": "Can preserve service only if the alternate has documented coverage, evidence, and authority."
          }
        ],
        "guidance": "Write and test the failure posture per payment service; never discover it during an outage.",
        "evidence": [
          {
            "ref": {
              "sourceId": "bis-cpmi-pfmi",
              "label": "official-requirement",
              "locator": "Principle 17 — operational risk"
            },
            "verifiedDate": "2026-07-23",
            "versionContext": "CPMI-IOSCO Principles for financial market infrastructures",
            "asOf": "2012-04-16"
          }
        ]
      }
    ],
    "targets": [
      {
        "type": "topic",
        "id": "foundations.payment-lifecycle"
      },
      {
        "type": "topic",
        "id": "foundations.parties-in-a-payment"
      },
      {
        "type": "topic",
        "id": "foundations.instruments-and-rails"
      },
      {
        "type": "topic",
        "id": "ops.payment-hub-architecture"
      },
      {
        "type": "flow",
        "id": "flow-cbpr-corporate-lifecycle"
      }
    ],
    "glossaryTermIds": [
      "payment-rail",
      "clearing",
      "settlement",
      "ledger",
      "straight-through-processing",
      "idempotency"
    ],
    "evidence": [
      {
        "ref": {
          "sourceId": "bis-cpmi-pfmi",
          "label": "official-requirement",
          "locator": "Principles 8, 9, 17, and 22"
        },
        "verifiedDate": "2026-07-23",
        "versionContext": "CPMI-IOSCO Principles for financial market infrastructures",
        "asOf": "2012-04-16"
      },
      {
        "ref": {
          "sourceId": "iso20022-catalogue",
          "label": "official-requirement",
          "locator": "Payments business area"
        },
        "verifiedDate": "2026-07-23",
        "versionContext": "ISO 20022 catalogue — select the implementation community and message version in force"
      },
      {
        "ref": {
          "sourceId": "payments-signal-editorial",
          "label": "simplified-educational-illustration",
          "locator": "Whole-estate synthesis",
          "simplifications": "The diagram is a vendor-neutral teaching construction. Real institutions split, combine, outsource, and duplicate these capabilities."
        },
        "verifiedDate": "2026-07-23",
        "versionContext": "Payments Signal reference architecture v1"
      }
    ],
    "simplifies": "The landscape shows one sending institution, one receiving institution, and one external arrangement. Real payments may cross several intermediaries, control platforms, ledgers, gateways, and settlement venues."
  },
  "sources": [
    {
      "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": "iso20022-catalogue",
      "publisher": "ISO 20022 Registration Authority",
      "title": "ISO 20022 Catalogue of messages",
      "sourceType": "official-standard",
      "accessedDate": "2026-07-12",
      "url": "https://www.iso20022.org/catalogue-messages",
      "applicability": "Defines the current versions of all ISO 20022 message definitions, including the pain, pacs, and camt messages taught on this site.",
      "notes": "Each message set is described by a Message Definition Report; earlier versions remain available in the ISO 20022 messages archive."
    },
    {
      "id": "payments-signal-editorial",
      "publisher": "Payments Signal",
      "title": "Payments Signal editorial teaching models",
      "sourceType": "educational-simplification",
      "accessedDate": "2026-07-12",
      "applicability": "This site's own simplified teaching models.",
      "notes": "Used wherever diagrams, scenarios, figures, or example values are didactic constructions rather than sourced facts; every such use carries a simplifications disclosure. All people, companies, banks, and list entries in examples are fictional."
    }
  ],
  "relatedContent": [
    {
      "type": "article",
      "label": "Accounting Entries in Payments",
      "href": "/2026/07/13/accounting-entries-in-payments",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "ACK, NACK, and the Payment Status Report (pacs.002)",
      "href": "/2026/07/13/ack-nack-and-payment-status-report",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "Batch and file-based payments",
      "href": "/2026/07/13/batch-and-file-payments",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "BIC versus LEI: payment reference data",
      "href": "/2026/07/13/bic-vs-lei-reference-data",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "Book and On-Us Payments",
      "href": "/2026/07/13/book-and-on-us-payments",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "Business Analyst Interview Question",
      "href": "/2026/07/13/business-analyst-interview-question",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "Cards vs account-to-account rails",
      "href": "/2026/07/18/cards-vs-account-to-account-rails",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "CBDC and digital money",
      "href": "/2026/07/13/cbdc-and-digital-money",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "Cheques and paper instruments",
      "href": "/2026/07/13/cheques-and-paper-instruments",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "Domestic Payment Schemes in the UK – Part 1",
      "href": "/2026/07/13/domestic-payment-schemes-in-the-uk-part-1",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "Domestic Payment Schemes in the UK – Part 3",
      "href": "/2026/07/13/domestic-payment-schemes-in-the-uk-part-3",
      "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 payment hub works: product capabilities",
      "href": "/2026/07/13/payment-hub-product-capabilities",
      "coverage": "direct"
    },
    {
      "type": "article",
      "label": "How a sanctions screening product works",
      "href": "/2026/07/13/how-a-sanctions-screening-product-works",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "IBAN and BIC: anatomy and validation",
      "href": "/2026/07/13/iban-and-bic-anatomy-and-validation",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "India's UPI and IMPS: An Overlay on Instant Rails",
      "href": "/2026/07/13/india-upi-and-imps",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "Misc Payment Concepts",
      "href": "/2026/07/13/misc-payment-concepts",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "Non-Bank Payment Providers",
      "href": "/2026/07/13/non-bank-payment-providers",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "One corporate payment: the full MX lifecycle and its MT migration path",
      "href": "/2026/07/18/corporate-payment-full-message-lifecycle",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "Other Payment Message Standards Beyond SWIFT",
      "href": "/2026/07/13/other-payment-message-standards",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "Parties in a Payment System",
      "href": "/2026/07/13/parties-in-a-payment-system",
      "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 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": "Payment Messages",
      "href": "/2026/07/13/messages",
      "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": "Payments Interview Preparation",
      "href": "/2026/07/13/payments-interview-preparation",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "Payments Interview Questions",
      "href": "/2026/07/13/payments-interview-question",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "Payments Quiz – Basics 2",
      "href": "/2026/07/13/payments-quiz-basics-2",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "Polish Banking and Payment Systems",
      "href": "/2026/07/13/polish-banking-and-payment-systems",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "Proxy and alias addressing",
      "href": "/2026/07/13/proxy-and-alias-addressing",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "Purpose codes in payments",
      "href": "/2026/07/13/purpose-codes-in-payments",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "Push versus pull payments",
      "href": "/2026/07/13/push-vs-pull-payments",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "Reconciliation in payments",
      "href": "/2026/07/13/payments-reconciliation",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "Request to Pay and e-mandates",
      "href": "/2026/07/13/request-to-pay-and-e-mandates",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "Reversals, returns, recalls, and cancellations",
      "href": "/2026/07/13/reversals-returns-and-cancellations",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "Risks in Payment Systems",
      "href": "/2026/07/13/risks-in-payment-systems",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "Sanctions screening system architecture",
      "href": "/2026/07/13/sanctions-screening-architecture",
      "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": "Stablecoins and crypto rails",
      "href": "/2026/07/13/stablecoins-and-crypto-rails",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "Standing orders and scheduled payments",
      "href": "/2026/07/13/standing-orders-and-scheduled-payments",
      "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 hosted compliance services",
      "href": "/2026/07/13/swift-hosted-compliance-services",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "SWIFT investigation and exception messages",
      "href": "/2026/07/13/swift-investigation-and-exception-messages",
      "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 four-corner model",
      "href": "/2026/07/13/the-four-corner-model",
      "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": "Types of lists in a screening product",
      "href": "/2026/07/13/types-of-lists-in-a-screening-product",
      "coverage": "derived"
    },
    {
      "type": "article",
      "label": "What a payment declares about itself — and who carries it",
      "href": "/2026/07/16/iso-20022-payment-codes-and-agents",
      "coverage": "derived"
    },
    {
      "type": "flow",
      "label": "CBPR+ corporate payment — full MX lifecycle",
      "href": "/explore/cbpr-corporate-lifecycle",
      "coverage": "direct"
    },
    {
      "type": "glossary",
      "label": "Beneficiary",
      "href": "/glossary#beneficiary",
      "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": "Case management",
      "href": "/glossary#case-management",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Central bank money",
      "href": "/glossary#central-bank-money",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Commercial bank money",
      "href": "/glossary#commercial-bank-money",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Credit transfer",
      "href": "/glossary#credit-transfer",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Creditor",
      "href": "/glossary#creditor",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Creditor agent",
      "href": "/glossary#creditor-agent",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Cut-off",
      "href": "/glossary#cut-off",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Debtor",
      "href": "/glossary#debtor",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Debtor agent",
      "href": "/glossary#debtor-agent",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Direct debit",
      "href": "/glossary#direct-debit",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "E-money institution (EMI)",
      "href": "/glossary#e-money-institution",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Input credit file",
      "href": "/glossary#input-credit-file",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Instructing / instructed agent",
      "href": "/glossary#instructing-instructed-agent",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Intermediary agent",
      "href": "/glossary#intermediary-agent",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Money transfer operator (MTO)",
      "href": "/glossary#money-transfer-operator",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Nostro account",
      "href": "/glossary#nostro-account",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "On-us payment",
      "href": "/glossary#on-us-payment",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Ordering customer",
      "href": "/glossary#ordering-customer",
      "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 institution (PI)",
      "href": "/glossary#payment-institution",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Payment instrument",
      "href": "/glossary#payment-instrument",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Payment rail",
      "href": "/glossary#payment-rail",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Payment scheme",
      "href": "/glossary#payment-scheme",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "PSP",
      "href": "/glossary#psp",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Reconciliation",
      "href": "/glossary#reconciliation",
      "coverage": "derived"
    },
    {
      "type": "glossary",
      "label": "Sponsor bank",
      "href": "/glossary#sponsor-bank",
      "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": "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": "ISO 20022 message definitions and XSDs",
      "href": "/implementation-resources",
      "coverage": "direct"
    },
    {
      "type": "resource",
      "label": "MT to MX migration notes",
      "href": "/downloads/assets/mt-mx-migration-notes",
      "coverage": "derived"
    },
    {
      "type": "resource",
      "label": "Payment lifecycle test cases",
      "href": "/downloads/assets/payment-lifecycle-test-cases",
      "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": "Exceptions and investigations",
      "href": "/learn/operations/exceptions-and-investigations",
      "coverage": "direct"
    },
    {
      "type": "topic",
      "label": "Instruments, rails, and schemes",
      "href": "/learn/foundations/instruments-and-rails",
      "coverage": "direct"
    },
    {
      "type": "topic",
      "label": "Money, accounts, and ledgers",
      "href": "/learn/foundations/money-and-bank-accounts",
      "coverage": "direct"
    },
    {
      "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": "Screening system architecture",
      "href": "/screening/execution/screening-architecture",
      "coverage": "direct"
    },
    {
      "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": "The parties in a payment",
      "href": "/learn/foundations/parties-in-a-payment",
      "coverage": "direct"
    },
    {
      "type": "topic",
      "label": "The payment lifecycle",
      "href": "/learn/foundations/payment-lifecycle",
      "coverage": "direct"
    }
  ]
}