{ "generatedFrom": "Payments Signal canonical architecture registry", "reviewDate": "2026-07-23", "blueprint": { "id": "architecture-security-resilience", "slug": "payment-security-trust-observability-continuity", "title": "Payment security, trust boundaries, entitlements, observability, continuity, and recovery", "shortTitle": "Security & resilience", "family": "controls", "summary": "Treat identity, change, secrets, network boundaries, telemetry, continuity, and payment-safe recovery as one control architecture.", "audience": "Security, payment, cloud, infrastructure, operational-resilience, risk, audit, and service-management architects.", "reviewDate": "2026-07-23", "versionLabel": "Payments Signal reference architecture v1", "status": "current", "nodes": [ { "id": "sec-identities", "title": "Workforce, workload, and participant identity", "kind": "security", "summary": "Issues and verifies distinct identities for people, services, devices, counterparties, and network participants.", "responsibilities": [ "Use the right identity type for each actor", "Bind authentication strength to payment risk" ], "owner": "Identity and access management", "inputs": [ "Authorised business instruction and correlated state" ], "outputs": [ "Versioned result, status, and audit evidence" ], "interfaceContracts": [ "Versioned workforce, workload, and participant identity contract", "Stable identifier, state, error, and audit contract" ], "controls": [ "Phishing-resistant privileged access", "Certificate lifecycle", "No shared production identity" ], "failureModes": [ "Stolen credential", "Expired certificate", "Orphan service account" ], "recovery": [ "Revoke and rotate", "Contain affected sessions", "Re-establish trust from verified identity" ], "lenses": [ "applications", "interfaces", "data", "controls", "operations", "resilience" ], "evidence": [ { "ref": { "sourceId": "bis-cpmi-cyber-resilience", "locator": "Protection and identification", "label": "official-requirement" }, "verifiedDate": "2026-07-23", "versionContext": "CPMI-IOSCO cyber-resilience guidance" }, { "ref": { "sourceId": "payments-signal-editorial", "locator": "Payment security, trust boundaries, observability, continuity, and recovery", "label": "simplified-educational-illustration", "simplifications": "Control ownership, cryptographic protocols, recovery objectives, data residency, privileged-access model, continuity sites, and regulatory duties depend on the institution, service, jurisdiction, risk assessment, and deployment." }, "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": "sec-entitlements", "title": "Entitlements and payment authority", "kind": "control", "summary": "Translates job, service, participant, amount, product, and context into an allowed payment action.", "responsibilities": [ "Separate create, approve, release, repair, and administer authority", "Apply least privilege and segregation of duties" ], "owner": "Payment control owner and access governance", "inputs": [ "Authorised business instruction and correlated state" ], "outputs": [ "Versioned result, status, and audit evidence" ], "interfaceContracts": [ "Versioned entitlements and payment authority contract", "Stable identifier, state, error, and audit contract" ], "controls": [ "Maker-checker", "Context and amount limits", "Periodic recertification", "Emergency access review" ], "failureModes": [ "Self-approval", "Dormant privilege", "Service can bypass payment gate" ], "recovery": [ "Remove access", "Review affected actions", "Correct the control path before reopening" ], "lenses": [ "applications", "interfaces", "data", "controls", "operations", "resilience" ], "evidence": [ { "ref": { "sourceId": "payments-signal-editorial", "locator": "Payment security, trust boundaries, observability, continuity, and recovery", "label": "simplified-educational-illustration", "simplifications": "Control ownership, cryptographic protocols, recovery objectives, data residency, privileged-access model, continuity sites, and regulatory duties depend on the institution, service, jurisdiction, risk assessment, and deployment." }, "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": "sec-boundary", "title": "API, message, file, and network security boundary", "kind": "gateway", "summary": "Authenticates, authorises, validates, rate-limits, and records traffic crossing each trust boundary.", "responsibilities": [ "Protect every ingress and egress contract", "Keep external, partner, user, and internal trust zones distinct" ], "owner": "Platform and network security", "inputs": [ "Authorised business instruction and correlated state" ], "outputs": [ "Versioned result, status, and audit evidence" ], "interfaceContracts": [ "Versioned api, message, file, and network security boundary contract", "Stable identifier, state, error, and audit contract" ], "controls": [ "Mutual authentication", "Integrity and replay control", "Schema and size limits", "Denial-of-service protection" ], "failureModes": [ "Spoofed participant", "Replay", "Malicious file", "Boundary unavailable" ], "recovery": [ "Reject before business processing", "Isolate and recover the affected channel", "Use tested alternate paths only" ], "lenses": [ "applications", "interfaces", "data", "controls", "operations", "resilience" ], "evidence": [ { "ref": { "sourceId": "bis-cpmi-pfmi", "locator": "Principles 17 and 22", "label": "official-requirement" }, "verifiedDate": "2026-07-23", "versionContext": "CPMI-IOSCO Principles for financial market infrastructures" }, { "ref": { "sourceId": "bis-cpmi-cyber-resilience", "locator": "Protection, detection, and response", "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" ] }, { "id": "sec-secrets", "title": "Cryptographic keys, secrets, and signing service", "kind": "security", "summary": "Protects key material and performs controlled signing, verification, encryption, and rotation.", "responsibilities": [ "Keep raw key material outside application memory where required", "Prove key use, version, and authority" ], "owner": "Cryptographic security and key custodians", "inputs": [ "Authorised business instruction and correlated state" ], "outputs": [ "Versioned result, status, and audit evidence" ], "interfaceContracts": [ "Versioned cryptographic keys, secrets, and signing service contract", "Stable identifier, state, error, and audit contract" ], "controls": [ "Hardware-backed control where required", "Dual control", "Rotation and revocation", "Usage audit" ], "failureModes": [ "Key compromise", "Signing unavailable", "Expired trust chain" ], "recovery": [ "Revoke and rotate", "Stop affected message release", "Revalidate trust and replay only authorised work" ], "lenses": [ "applications", "interfaces", "data", "controls", "operations", "resilience" ], "evidence": [ { "ref": { "sourceId": "bis-cpmi-cyber-resilience", "locator": "Protection and response", "label": "official-requirement" }, "verifiedDate": "2026-07-23", "versionContext": "CPMI-IOSCO cyber-resilience guidance" }, { "ref": { "sourceId": "payments-signal-editorial", "locator": "Payment security, trust boundaries, observability, continuity, and recovery", "label": "simplified-educational-illustration", "simplifications": "Control ownership, cryptographic protocols, recovery objectives, data residency, privileged-access model, continuity sites, and regulatory duties depend on the institution, service, jurisdiction, risk assessment, and deployment." }, "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": "sec-platform", "title": "Hardened payment runtime and data stores", "kind": "infrastructure", "summary": "Runs payment services with isolation, secure configuration, immutable deployment evidence, backup, and recoverable state.", "responsibilities": [ "Separate environments and duties", "Protect payment, personal, credential, and audit data by classification" ], "owner": "Platform engineering and data owners", "inputs": [ "Authorised business instruction and correlated state" ], "outputs": [ "Versioned result, status, and audit evidence" ], "interfaceContracts": [ "Versioned hardened payment runtime and data stores contract", "Stable identifier, state, error, and audit contract" ], "controls": [ "Approved image and dependency", "Encrypted storage", "Patch and configuration evidence", "Backup integrity" ], "failureModes": [ "Compromised runtime", "Configuration drift", "Corrupt backup" ], "recovery": [ "Isolate workload", "Restore from a verified point", "Reconcile payment state before traffic resumes" ], "lenses": [ "applications", "interfaces", "data", "controls", "operations", "resilience" ], "evidence": [ { "ref": { "sourceId": "bis-cpmi-cyber-resilience", "locator": "Protection and recovery", "label": "official-requirement" }, "verifiedDate": "2026-07-23", "versionContext": "CPMI-IOSCO cyber-resilience guidance" }, { "ref": { "sourceId": "payments-signal-editorial", "locator": "Payment security, trust boundaries, observability, continuity, and recovery", "label": "simplified-educational-illustration", "simplifications": "Control ownership, cryptographic protocols, recovery objectives, data residency, privileged-access model, continuity sites, and regulatory duties depend on the institution, service, jurisdiction, risk assessment, and deployment." }, "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": "sec-observability", "title": "Security and payment observability", "kind": "data-store", "summary": "Correlates logs, metrics, traces, business events, control outcomes, and settlement checkpoints without copying secrets or full payment data unnecessarily.", "responsibilities": [ "Detect abnormal technical and payment behaviour", "Keep telemetry useful, minimised, time-aligned, and tamper-evident" ], "owner": "Security operations and payment service management", "inputs": [ "Authorised business instruction and correlated state" ], "outputs": [ "Versioned result, status, and audit evidence" ], "interfaceContracts": [ "Versioned security and payment observability contract", "Stable identifier, state, error, and audit contract" ], "controls": [ "Clock synchronisation", "Immutable audit", "Sensitive-data minimisation", "Alert ownership" ], "failureModes": [ "Blind spot", "False alert flood", "Sensitive data in logs" ], "recovery": [ "Restore telemetry", "Contain and redact exposed data", "Reconstruct from retained business evidence" ], "lenses": [ "applications", "interfaces", "data", "controls", "operations", "resilience" ], "evidence": [ { "ref": { "sourceId": "bis-cpmi-cyber-resilience", "locator": "Detection and situational awareness", "label": "official-requirement" }, "verifiedDate": "2026-07-23", "versionContext": "CPMI-IOSCO cyber-resilience guidance" }, { "ref": { "sourceId": "payments-signal-editorial", "locator": "Payment security, trust boundaries, observability, continuity, and recovery", "label": "simplified-educational-illustration", "simplifications": "Control ownership, cryptographic protocols, recovery objectives, data residency, privileged-access model, continuity sites, and regulatory duties depend on the institution, service, jurisdiction, risk assessment, and deployment." }, "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": "sec-continuity", "title": "Continuity, backup, and recovery orchestration", "kind": "operations", "summary": "Coordinates alternate capacity, dependency recovery, queue control, data restoration, and staged service reopening.", "responsibilities": [ "Define recovery order and dependency map", "Protect payment correctness while restoring service" ], "owner": "Operational resilience and service owner", "inputs": [ "Authorised business instruction and correlated state" ], "outputs": [ "Versioned result, status, and audit evidence" ], "interfaceContracts": [ "Versioned continuity, backup, and recovery orchestration contract", "Stable identifier, state, error, and audit contract" ], "controls": [ "Tested recovery objective", "Isolated recovery copy", "Queue and ledger checkpoint", "Business validation" ], "failureModes": [ "Failover duplicates payments", "Dependency recovers out of order", "Backup cannot restore" ], "recovery": [ "Freeze replay", "Recover to a consistent boundary", "Reconcile before staged reopen" ], "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, testing, 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" ] }, { "id": "sec-governance", "title": "Risk, change, testing, and assurance", "kind": "operations", "summary": "Owns threat, control, dependency, test, exception, incident, and improvement evidence.", "responsibilities": [ "Assess changes and third parties", "Test cyber, continuity, fraud, access, and payment-safe recovery" ], "owner": "Payment risk, security governance, architecture, and audit", "inputs": [ "Authorised business instruction and correlated state" ], "outputs": [ "Versioned result, status, and audit evidence" ], "interfaceContracts": [ "Versioned risk, change, testing, and assurance contract", "Stable identifier, state, error, and audit contract" ], "controls": [ "Independent assurance", "Change approval", "Penetration and resilience testing", "Exception expiry" ], "failureModes": [ "Risk accepted without owner", "Test excludes settlement and reconciliation", "Known weakness never closes" ], "recovery": [ "Escalate and time-bound", "Retest end to end", "Track corrective action to evidence" ], "lenses": [ "applications", "interfaces", "data", "controls", "operations", "resilience" ], "evidence": [ { "ref": { "sourceId": "bis-cpmi-cyber-resilience", "locator": "Governance, testing, and learning", "label": "official-requirement" }, "verifiedDate": "2026-07-23", "versionContext": "CPMI-IOSCO cyber-resilience guidance" }, { "ref": { "sourceId": "bis-cpmi-pfmi", "locator": "Principles 2 and 17", "label": "official-requirement" }, "verifiedDate": "2026-07-23", "versionContext": "CPMI-IOSCO Principles for financial market infrastructures" } ], "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": "sec-e1", "from": "sec-identities", "to": "sec-entitlements", "title": "Authenticated identity and context", "kind": "control", "mode": "synchronous", "purpose": "Supply verified human, service, device, or participant identity.", "failureBehaviour": "Deny unknown, expired, or weakly authenticated identity.", "evidence": [ { "ref": { "sourceId": "payments-signal-editorial", "locator": "Payment security, trust boundaries, observability, continuity, and recovery", "label": "simplified-educational-illustration", "simplifications": "Control ownership, cryptographic protocols, recovery objectives, data residency, privileged-access model, continuity sites, and regulatory duties depend on the institution, service, jurisdiction, risk assessment, and deployment." }, "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": "sec-e2", "from": "sec-entitlements", "to": "sec-boundary", "title": "Authorised payment capability", "kind": "control", "mode": "synchronous", "purpose": "Constrain which interface and action the identity may use.", "failureBehaviour": "Reject unauthorised actions before payload processing.", "evidence": [ { "ref": { "sourceId": "payments-signal-editorial", "locator": "Payment security, trust boundaries, observability, continuity, and recovery", "label": "simplified-educational-illustration", "simplifications": "Control ownership, cryptographic protocols, recovery objectives, data residency, privileged-access model, continuity sites, and regulatory duties depend on the institution, service, jurisdiction, risk assessment, and deployment." }, "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": "sec-e3", "from": "sec-secrets", "to": "sec-boundary", "title": "Signing and trust service", "kind": "control", "mode": "synchronous", "purpose": "Sign or verify the boundary exchange under current keys.", "failureBehaviour": "Stop release when signature or trust status is uncertain.", "evidence": [ { "ref": { "sourceId": "payments-signal-editorial", "locator": "Payment security, trust boundaries, observability, continuity, and recovery", "label": "simplified-educational-illustration", "simplifications": "Control ownership, cryptographic protocols, recovery objectives, data residency, privileged-access model, continuity sites, and regulatory duties depend on the institution, service, jurisdiction, risk assessment, and deployment." }, "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": "sec-e4", "from": "sec-boundary", "to": "sec-platform", "title": "Validated payment traffic", "kind": "message", "mode": "asynchronous", "purpose": "Admit only authenticated, authorised, intact, bounded traffic.", "failureBehaviour": "Quarantine invalid or replayed traffic.", "evidence": [ { "ref": { "sourceId": "payments-signal-editorial", "locator": "Payment security, trust boundaries, observability, continuity, and recovery", "label": "simplified-educational-illustration", "simplifications": "Control ownership, cryptographic protocols, recovery objectives, data residency, privileged-access model, continuity sites, and regulatory duties depend on the institution, service, jurisdiction, risk assessment, and deployment." }, "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": "sec-e5", "from": "sec-platform", "to": "sec-observability", "title": "Technical and business telemetry", "kind": "event", "mode": "asynchronous", "purpose": "Emit correlated events and control outcomes without avoidable sensitive content.", "failureBehaviour": "Buffer critical audit evidence during telemetry degradation.", "evidence": [ { "ref": { "sourceId": "payments-signal-editorial", "locator": "Payment security, trust boundaries, observability, continuity, and recovery", "label": "simplified-educational-illustration", "simplifications": "Control ownership, cryptographic protocols, recovery objectives, data residency, privileged-access model, continuity sites, and regulatory duties depend on the institution, service, jurisdiction, risk assessment, and deployment." }, "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": "sec-e6", "from": "sec-boundary", "to": "sec-observability", "title": "Boundary security event", "kind": "event", "mode": "asynchronous", "purpose": "Record authentication, authorisation, validation, and rate decisions.", "failureBehaviour": "Preserve boundary evidence locally when the central sink is unavailable.", "evidence": [ { "ref": { "sourceId": "payments-signal-editorial", "locator": "Payment security, trust boundaries, observability, continuity, and recovery", "label": "simplified-educational-illustration", "simplifications": "Control ownership, cryptographic protocols, recovery objectives, data residency, privileged-access model, continuity sites, and regulatory duties depend on the institution, service, jurisdiction, risk assessment, and deployment." }, "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": "sec-e7", "from": "sec-observability", "to": "sec-continuity", "title": "Incident and recovery signal", "kind": "event", "mode": "asynchronous", "purpose": "Trigger owned response from proven service and payment symptoms.", "failureBehaviour": "Escalate blind spots and conflicting signals.", "evidence": [ { "ref": { "sourceId": "bis-cpmi-cyber-resilience", "locator": "Detection, 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" ] }, { "id": "sec-e8", "from": "sec-continuity", "to": "sec-platform", "title": "Controlled recovery action", "kind": "control", "mode": "operator", "purpose": "Restore dependency, state, queue, and traffic in an approved order.", "failureBehaviour": "Block replay until idempotency and ledger state are 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": "payments-signal-editorial", "locator": "Payment security, trust boundaries, observability, continuity, and recovery", "label": "simplified-educational-illustration", "simplifications": "Control ownership, cryptographic protocols, recovery objectives, data residency, privileged-access model, continuity sites, and regulatory duties depend on the institution, service, jurisdiction, risk assessment, and deployment." }, "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": "sec-e9", "from": "sec-governance", "to": "sec-entitlements", "title": "Access policy and review", "kind": "control", "mode": "batch", "purpose": "Publish approved roles, limits, recertification, and emergency-access policy.", "failureBehaviour": "Remove expired or unsupported privilege.", "evidence": [ { "ref": { "sourceId": "payments-signal-editorial", "locator": "Payment security, trust boundaries, observability, continuity, and recovery", "label": "simplified-educational-illustration", "simplifications": "Control ownership, cryptographic protocols, recovery objectives, data residency, privileged-access model, continuity sites, and regulatory duties depend on the institution, service, jurisdiction, risk assessment, and deployment." }, "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": "sec-e10", "from": "sec-governance", "to": "sec-continuity", "title": "Tested recovery requirement", "kind": "control", "mode": "operator", "purpose": "Set and evidence recovery scenarios, objectives, dependencies, and lessons.", "failureBehaviour": "Keep production enablement gated when the test cannot prove payment correctness.", "evidence": [ { "ref": { "sourceId": "bis-cpmi-cyber-resilience", "locator": "Testing and learning", "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": [], "interfaceIds": [], "placements": {}, "boundaries": [] }, { "id": "container", "label": "Container", "plainPurpose": "The major applications, stores, gateways, controls, and operational ownership boundaries.", "nodeIds": [ "sec-entitlements", "sec-boundary", "sec-observability", "sec-continuity", "sec-governance" ], "interfaceIds": [ "sec-e2", "sec-e6", "sec-e7", "sec-e9", "sec-e10" ], "placements": { "sec-entitlements": { "x": 80, "y": 100, "width": 244, "height": 126 }, "sec-boundary": { "x": 444, "y": 100, "width": 244, "height": 126 }, "sec-observability": { "x": 808, "y": 100, "width": 244, "height": 126 }, "sec-continuity": { "x": 80, "y": 326, "width": 244, "height": 126 }, "sec-governance": { "x": 444, "y": 326, "width": 244, "height": 126 } }, "boundaries": [ { "id": "container-bank-boundary", "label": "Institution-controlled boundary", "nodeIds": [ "sec-entitlements", "sec-boundary", "sec-observability", "sec-continuity", "sec-governance" ], "kind": "ownership" } ] }, { "id": "component", "label": "Component", "plainPurpose": "The processing responsibilities and interface contracts that must cooperate for one payment.", "nodeIds": [ "sec-identities", "sec-entitlements", "sec-boundary", "sec-secrets", "sec-platform", "sec-observability", "sec-continuity", "sec-governance" ], "interfaceIds": [ "sec-e1", "sec-e2", "sec-e3", "sec-e4", "sec-e5", "sec-e6", "sec-e7", "sec-e8", "sec-e9", "sec-e10" ], "placements": { "sec-identities": { "x": 80, "y": 100, "width": 196, "height": 126 }, "sec-entitlements": { "x": 376, "y": 100, "width": 196, "height": 126 }, "sec-boundary": { "x": 672, "y": 100, "width": 196, "height": 126 }, "sec-secrets": { "x": 968, "y": 100, "width": 196, "height": 126 }, "sec-platform": { "x": 80, "y": 326, "width": 196, "height": 126 }, "sec-observability": { "x": 376, "y": 326, "width": 196, "height": 126 }, "sec-continuity": { "x": 672, "y": 326, "width": 196, "height": 126 }, "sec-governance": { "x": 968, "y": 326, "width": 196, "height": 126 } }, "boundaries": [ { "id": "component-bank-boundary", "label": "Institution-controlled boundary", "nodeIds": [ "sec-identities", "sec-entitlements", "sec-boundary", "sec-secrets", "sec-platform", "sec-observability", "sec-continuity", "sec-governance" ], "kind": "ownership" } ] }, { "id": "deployment", "label": "Deployment", "plainPurpose": "The trust zones, runtime dependencies, external connections, and recovery boundaries.", "nodeIds": [ "sec-identities", "sec-boundary", "sec-secrets", "sec-platform", "sec-observability" ], "interfaceIds": [ "sec-e3", "sec-e4", "sec-e5", "sec-e6" ], "placements": { "sec-identities": { "x": 80, "y": 100, "width": 244, "height": 126 }, "sec-boundary": { "x": 444, "y": 100, "width": 244, "height": 126 }, "sec-secrets": { "x": 808, "y": 100, "width": 244, "height": 126 }, "sec-platform": { "x": 80, "y": 326, "width": 244, "height": 126 }, "sec-observability": { "x": 444, "y": 326, "width": 244, "height": 126 } }, "boundaries": [ { "id": "deployment-bank-boundary", "label": "Institution-controlled boundary", "nodeIds": [ "sec-identities", "sec-boundary", "sec-secrets", "sec-platform", "sec-observability" ], "kind": "ownership" } ] } ], "traces": [ { "id": "sec-trusted-payment", "label": "Trusted release and recoverable evidence", "summary": "Follow the controls that authenticate, authorise, protect, observe, and safely recover one payment action.", "viewId": "component", "steps": [ { "id": "sec-trusted-payment-step-1", "title": "Establish identity", "nodeId": "sec-identities", "interfaceId": "sec-e1", "plainExplanation": "A human, service, or participant presents current verifiable identity.", "businessState": "Actor authenticated" }, { "id": "sec-trusted-payment-step-2", "title": "Prove authority", "nodeId": "sec-entitlements", "interfaceId": "sec-e2", "plainExplanation": "Role, amount, service, product, and context permit this exact action.", "businessState": "Action authorised" }, { "id": "sec-trusted-payment-step-3", "title": "Protect integrity", "nodeId": "sec-secrets", "interfaceId": "sec-e3", "plainExplanation": "Signing and verification use controlled key material and current trust.", "businessState": "Trust material current" }, { "id": "sec-trusted-payment-step-4", "title": "Validate the boundary", "nodeId": "sec-boundary", "interfaceId": "sec-e4", "plainExplanation": "Identity, authority, integrity, replay, schema, and size checks pass.", "businessState": "Traffic admitted" }, { "id": "sec-trusted-payment-step-5", "title": "Process in a controlled runtime", "nodeId": "sec-platform", "interfaceId": "sec-e5", "plainExplanation": "The runtime uses protected state and emits a correlated business event.", "businessState": "Payment action recorded" }, { "id": "sec-trusted-payment-step-6", "title": "Observe the outcome", "nodeId": "sec-observability", "interfaceId": "sec-e7", "plainExplanation": "Security and payment telemetry can reconstruct the action without exposing unnecessary data.", "businessState": "Control evidence retained" }, { "id": "sec-trusted-payment-step-7", "title": "Keep recovery payment-safe", "nodeId": "sec-continuity", "plainExplanation": "If service fails, queue, ledger, and settlement state govern staged reopening.", "businessState": "Recovery boundary known" } ], "evidence": [ { "ref": { "sourceId": "bis-cpmi-cyber-resilience", "locator": "Governance through recovery", "label": "official-requirement" }, "verifiedDate": "2026-07-23", "versionContext": "CPMI-IOSCO cyber-resilience guidance" }, { "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 security, trust boundaries, observability, continuity, and recovery", "label": "simplified-educational-illustration", "simplifications": "Control ownership, cryptographic protocols, recovery objectives, data residency, privileged-access model, continuity sites, and regulatory duties depend on the institution, service, jurisdiction, risk assessment, and deployment." }, "verifiedDate": "2026-07-23", "versionContext": "Payments Signal reference architecture v1" } ] } ], "stressCases": [ { "id": "sec-stress-credential", "label": "Privileged credential is compromised", "trigger": "A privileged identity is suspected of unauthorised payment or configuration action.", "divergesAfterStepId": "sec-trusted-payment-step-2", "traceId": "sec-trusted-payment", "affectedNodeIds": [ "sec-identities", "sec-entitlements", "sec-observability", "sec-governance" ], "affectedInterfaceIds": [ "sec-e1", "sec-e2", "sec-e5" ], "lastConfirmedState": "Identity and action history exist; legitimacy is uncertain.", "settlementState": "Settlement varies by each affected payment and must be traced.", "fundsState": "Books and external movements must be reviewed individually.", "owner": "Security incident command and payment control owner", "safeAction": "Revoke access, contain sessions, freeze affected authority, and trace every action to payment and settlement evidence.", "requiredEvidence": [ "Authentication events", "Entitlement history", "Configuration changes", "Payment and ledger references" ], "recoverySteps": [ "Rotate credentials", "Review and correct unauthorised actions", "Revalidate controls before restoring access" ], "evidence": [ { "ref": { "sourceId": "bis-cpmi-cyber-resilience", "locator": "Response and recovery", "label": "official-requirement" }, "verifiedDate": "2026-07-23", "versionContext": "CPMI-IOSCO cyber-resilience guidance" }, { "ref": { "sourceId": "payments-signal-editorial", "locator": "Payment security, trust boundaries, observability, continuity, and recovery", "label": "simplified-educational-illustration", "simplifications": "Control ownership, cryptographic protocols, recovery objectives, data residency, privileged-access model, continuity sites, and regulatory duties depend on the institution, service, jurisdiction, risk assessment, and deployment." }, "verifiedDate": "2026-07-23", "versionContext": "Payments Signal reference architecture v1" } ] }, { "id": "sec-stress-key", "label": "Signing service is unavailable", "trigger": "Outbound network messages cannot be signed with current trusted keys.", "divergesAfterStepId": "sec-trusted-payment-step-3", "traceId": "sec-trusted-payment", "affectedNodeIds": [ "sec-secrets", "sec-boundary", "sec-platform" ], "affectedInterfaceIds": [ "sec-e3", "sec-e4" ], "lastConfirmedState": "Payments may be approved internally but cannot cross the protected boundary.", "settlementState": "External settlement has not been initiated for queued messages.", "fundsState": "Internal reservations or postings depend on product design.", "owner": "Network security and payment operations", "safeAction": "Queue securely and invoke only the approved alternate signing or connectivity path.", "requiredEvidence": [ "Key status", "Queued message hashes", "Approval and cut-off", "Alternate-path authority" ], "recoverySteps": [ "Restore trusted signing", "Revalidate queued messages and authority", "Release once with original identifiers" ], "evidence": [ { "ref": { "sourceId": "payments-signal-editorial", "locator": "Payment security, trust boundaries, observability, continuity, and recovery", "label": "simplified-educational-illustration", "simplifications": "Control ownership, cryptographic protocols, recovery objectives, data residency, privileged-access model, continuity sites, and regulatory duties depend on the institution, service, jurisdiction, risk assessment, and deployment." }, "verifiedDate": "2026-07-23", "versionContext": "Payments Signal reference architecture v1" } ] }, { "id": "sec-stress-failover", "label": "Failover restores a stale queue", "trigger": "The recovery site has an earlier queue checkpoint than the ledger or network.", "divergesAfterStepId": "sec-trusted-payment-step-6", "traceId": "sec-trusted-payment", "affectedNodeIds": [ "sec-continuity", "sec-platform", "sec-observability" ], "affectedInterfaceIds": [ "sec-e7", "sec-e8" ], "lastConfirmedState": "Ledger and network may be ahead of the restored queue.", "settlementState": "Some payments may already be settled.", "fundsState": "Replaying the queue could duplicate value.", "owner": "Incident command, ledger, and payment operations", "safeAction": "Stop replay and reconcile business keys across queue, ledger, network, and statements.", "requiredEvidence": [ "Recovery checkpoint", "Queue journal", "Ledger journal", "Network acknowledgements", "Statements" ], "recoverySteps": [ "Rebuild the authoritative queue", "Mark completed work", "Replay only proven missing items", "Validate balances before full reopen" ], "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" } ] } ], "overlays": [ { "id": "sec-overlay-network", "label": "External payment-network boundary", "summary": "Show participant identity, entitlements, signing, message validation, telemetry, and recovery around an external network connection.", "nodeIds": [ "sec-identities", "sec-entitlements", "sec-secrets", "sec-boundary", "sec-platform", "sec-observability", "sec-continuity" ], "interfaceIds": [ "sec-e1", "sec-e2", "sec-e3", "sec-e4", "sec-e5", "sec-e6", "sec-e7", "sec-e8" ], "relatedFlowIds": [ "flow-swift-rma-routing", "flow-swift-gpi", "flow-t2-rtgs", "flow-fedwire-funds" ], "evidence": [ { "ref": { "sourceId": "bis-cpmi-pfmi", "locator": "Principles 17 and 22", "label": "official-requirement" }, "verifiedDate": "2026-07-23", "versionContext": "CPMI-IOSCO Principles for financial market infrastructures" }, { "ref": { "sourceId": "bis-cpmi-cyber-resilience", "locator": "Protection through recovery", "label": "official-requirement" }, "verifiedDate": "2026-07-23", "versionContext": "CPMI-IOSCO cyber-resilience guidance" } ], "coverageGap": "Network-specific controls require current participant security and connectivity documentation." }, { "id": "sec-overlay-continuity", "label": "Payment-safe continuity", "summary": "Keep queue, ledger, network, settlement, and reporting checkpoints visible during failover and replay.", "nodeIds": [ "sec-platform", "sec-observability", "sec-continuity", "sec-governance" ], "interfaceIds": [ "sec-e5", "sec-e7", "sec-e8", "sec-e10" ], "relatedFlowIds": [], "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 testing", "label": "official-requirement" }, "verifiedDate": "2026-07-23", "versionContext": "CPMI-IOSCO cyber-resilience guidance" } ] } ], "decisions": [ { "id": "sec-decision-failover", "question": "What is the unit of recovery?", "options": [ { "label": "Payment-safe checkpoint", "consequence": "Requires cross-system queue, ledger, network, and settlement evidence before replay." }, { "label": "Application availability", "consequence": "May restore a service quickly while leaving value state inconsistent." } ], "guidance": "Set recovery objectives for correct payment state and reconciled value, not process uptime alone.", "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 security, trust boundaries, observability, continuity, and recovery", "label": "simplified-educational-illustration", "simplifications": "Control ownership, cryptographic protocols, recovery objectives, data residency, privileged-access model, continuity sites, and regulatory duties depend on the institution, service, jurisdiction, risk assessment, and deployment." }, "verifiedDate": "2026-07-23", "versionContext": "Payments Signal reference architecture v1" } ] }, { "id": "sec-decision-telemetry", "question": "How much payment data belongs in telemetry?", "options": [ { "label": "Minimised identifiers and outcomes", "consequence": "Supports correlation while reducing exposure and log-handling scope." }, { "label": "Full payloads", "consequence": "Makes some debugging easier but copies sensitive data into another high-risk store." } ], "guidance": "Log stable references, state, control outcomes, versions, and timings; retrieve protected payloads only through authorised case access.", "evidence": [ { "ref": { "sourceId": "bis-cpmi-cyber-resilience", "locator": "Protection and detection", "label": "official-requirement" }, "verifiedDate": "2026-07-23", "versionContext": "CPMI-IOSCO cyber-resilience guidance" }, { "ref": { "sourceId": "payments-signal-editorial", "locator": "Payment security, trust boundaries, observability, continuity, and recovery", "label": "simplified-educational-illustration", "simplifications": "Control ownership, cryptographic protocols, recovery objectives, data residency, privileged-access model, continuity sites, and regulatory duties depend on the institution, service, jurisdiction, risk assessment, and deployment." }, "verifiedDate": "2026-07-23", "versionContext": "Payments Signal reference architecture v1" } ] } ], "targets": [ { "type": "flow", "id": "flow-swift-rma-routing" }, { "type": "flow", "id": "flow-swift-gpi" }, { "type": "flow", "id": "flow-t2-rtgs" }, { "type": "flow", "id": "flow-fedwire-funds" } ], "glossaryTermIds": [ "business-continuity", "cyber-resilience", "entitlement", "idempotency", "least-privilege", "recovery-point-objective", "recovery-time-objective", "segregation-of-duties", "trust-boundary" ], "evidence": [ { "ref": { "sourceId": "bis-cpmi-cyber-resilience", "locator": "All guidance chapters", "label": "official-requirement" }, "verifiedDate": "2026-07-23", "versionContext": "CPMI-IOSCO cyber-resilience guidance" }, { "ref": { "sourceId": "bis-cpmi-pfmi", "locator": "Principles 2, 17 and 22", "label": "official-requirement" }, "verifiedDate": "2026-07-23", "versionContext": "CPMI-IOSCO Principles for financial market infrastructures" }, { "ref": { "sourceId": "payments-signal-editorial", "locator": "Payment security, trust boundaries, observability, continuity, and recovery", "label": "simplified-educational-illustration", "simplifications": "Control ownership, cryptographic protocols, recovery objectives, data residency, privileged-access model, continuity sites, and regulatory duties depend on the institution, service, jurisdiction, risk assessment, and deployment." }, "verifiedDate": "2026-07-23", "versionContext": "Payments Signal reference architecture v1" } ], "simplifies": "This blueprint shows control responsibilities around payment execution and recovery. It does not define a threat model, cryptographic suite, security-zone count, cloud pattern, recovery target, privileged-access product, data-residency rule, regulatory obligation, or certification outcome for a particular institution." }, "sources": [ { "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." }, { "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": "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": "Adverse media screening", "href": "/2026/07/13/adverse-media-screening", "coverage": "derived" }, { "type": "article", "label": "AML transaction monitoring", "href": "/2026/07/13/aml-transaction-monitoring", "coverage": "derived" }, { "type": "article", "label": "AML transaction-monitoring typologies", "href": "/2026/07/13/aml-monitoring-typologies", "coverage": "derived" }, { "type": "article", "label": "AML Typologies Across Sectors: Beyond the Bank", "href": "/2026/07/13/aml-typologies-across-sectors", "coverage": "derived" }, { "type": "article", "label": "Asset freezes and prohibitions", "href": "/2026/07/13/asset-freezes-and-prohibitions", "coverage": "derived" }, { "type": "article", "label": "Batch and file-based payments", "href": "/2026/07/13/batch-and-file-payments", "coverage": "derived" }, { "type": "article", "label": "Beneficial ownership and UBO", "href": "/2026/07/13/beneficial-ownership-and-ubo", "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 email compromise and mandate fraud", "href": "/2026/07/13/business-email-compromise-and-mandate-fraud", "coverage": "derived" }, { "type": "article", "label": "Cash Transaction Reports and the AML Reporting Chain", "href": "/2026/07/13/cash-transaction-reports-and-aml-reporting", "coverage": "derived" }, { "type": "article", "label": "Central bank digital currency, explained", "href": "/2026/07/18/central-bank-digital-currency-explained", "coverage": "derived" }, { "type": "article", "label": "Central versus commercial bank money", "href": "/2026/07/18/central-versus-commercial-bank-money", "coverage": "derived" }, { "type": "article", "label": "CHIPS: clearing and netting", "href": "/2026/07/13/chips-clearing-and-netting", "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": "Customer risk rating and enhanced due diligence", "href": "/2026/07/13/customer-risk-rating-and-edd", "coverage": "derived" }, { "type": "article", "label": "EURO1 and large-value net settlement", "href": "/2026/07/18/euro1-and-large-value-net-settlement", "coverage": "derived" }, { "type": "article", "label": "FATCA, CRS, and Tax-Information Exchange", "href": "/2026/07/13/fatca-crs-and-tax-information-exchange", "coverage": "derived" }, { "type": "article", "label": "High-value payments and HVPS+", "href": "/2026/07/13/high-value-payments-and-hvps-plus", "coverage": "derived" }, { "type": "article", "label": "High-value, netting, and instant settlement systems compared", "href": "/2026/07/13/high-value-vs-instant-settlement-systems", "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": "Information-sharing requests (314(a))", "href": "/2026/07/13/information-sharing-requests-314a", "coverage": "derived" }, { "type": "article", "label": "Instant payments around the world", "href": "/2026/07/13/instant-payments-around-the-world", "coverage": "derived" }, { "type": "article", "label": "Investigating a screening alert", "href": "/2026/07/13/investigating-screening-alerts", "coverage": "derived" }, { "type": "article", "label": "KYC and customer due diligence basics", "href": "/2026/07/13/kyc-and-customer-due-diligence", "coverage": "derived" }, { "type": "article", "label": "Letters of credit and documentary trade", "href": "/2026/07/18/letters-of-credit-and-documentary-trade", "coverage": "derived" }, { "type": "article", "label": "Liquidity and settlement risk in payment systems", "href": "/2026/07/13/payment-liquidity-and-settlement-risk", "coverage": "derived" }, { "type": "article", "label": "Liquidity saving and gridlock resolution", "href": "/2026/07/13/liquidity-saving-and-gridlock-resolution", "coverage": "derived" }, { "type": "article", "label": "Money laundering explained", "href": "/2026/07/13/money-laundering-explained", "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": "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 market infrastructures", "href": "/2026/07/13/payment-market-infrastructures", "coverage": "derived" }, { "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": "Reconciliation in payments", "href": "/2026/07/13/payments-reconciliation", "coverage": "derived" }, { "type": "article", "label": "Sanctions evasion typologies", "href": "/2026/07/13/sanctions-evasion-typologies", "coverage": "derived" }, { "type": "article", "label": "Sanctions screening versus AML and fraud", "href": "/2026/07/13/screening-versus-aml-and-fraud", "coverage": "derived" }, { "type": "article", "label": "Screening for politically exposed persons (PEPs)", "href": "/2026/07/13/pep-screening", "coverage": "derived" }, { "type": "article", "label": "Screening governance, policy, and ownership", "href": "/2026/07/13/sanctions-screening-governance", "coverage": "derived" }, { "type": "article", "label": "Security and fraud controls in payment operations", "href": "/2026/07/13/payment-operations-security-and-fraud", "coverage": "derived" }, { "type": "article", "label": "Stablecoins as a settlement asset", "href": "/2026/07/18/stablecoins-as-a-settlement-asset", "coverage": "derived" }, { "type": "article", "label": "Suspicious activity reporting and escalation", "href": "/2026/07/13/suspicious-activity-reporting", "coverage": "derived" }, { "type": "article", "label": "SWIFT Cancellations and Investigation Messages", "href": "/2026/07/13/swift-cancellations-and-investigation-messages", "coverage": "derived" }, { "type": "article", "label": "SWIFT gpi and payment tracking", "href": "/2026/07/13/swift-gpi-and-payment-tracking", "coverage": "derived" }, { "type": "article", "label": "SWIFT gpi service variants", "href": "/2026/07/13/swift-gpi-service-variants", "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 payment pre-validation", "href": "/2026/07/13/swift-payment-pre-validation", "coverage": "derived" }, { "type": "article", "label": "SWIFT Universal Confirmation and gpi Services", "href": "/2026/07/13/swift-universal-confirmation-and-gpi-services", "coverage": "derived" }, { "type": "article", "label": "Swiss Interbank Clearing: SIC and euroSIC", "href": "/2026/07/13/swiss-interbank-clearing-sic-eurosic", "coverage": "derived" }, { "type": "article", "label": "T2 and Central Liquidity Management", "href": "/2026/07/13/target2-and-central-liquidity-management", "coverage": "derived" }, { "type": "article", "label": "TARGET2-Securities: DvP Settlement in Central-Bank Money", "href": "/2026/07/13/target2-securities-t2s", "coverage": "derived" }, { "type": "article", "label": "Testing and tuning a screening system", "href": "/2026/07/13/testing-and-tuning-screening", "coverage": "derived" }, { "type": "article", "label": "The Bodies Behind AML: FATF, FSRBs, Egmont, and Wolfsberg", "href": "/2026/07/13/aml-bodies-fatf-fsrb-egmont-wolfsberg", "coverage": "derived" }, { "type": "article", "label": "The FATF framework", "href": "/2026/07/13/the-fatf-framework", "coverage": "derived" }, { "type": "article", "label": "The Fedwire Funds Service", "href": "/2026/07/13/fedwire-funds-service", "coverage": "derived" }, { "type": "article", "label": "The MT7xx trade finance message family", "href": "/2026/07/18/the-mt7xx-trade-finance-message-family", "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 risk-based approach to screening", "href": "/2026/07/13/risk-based-approach-to-screening", "coverage": "derived" }, { "type": "article", "label": "The SWIFT Payment Controls Service", "href": "/2026/07/13/swift-payment-controls-service", "coverage": "derived" }, { "type": "article", "label": "The travel rule in payments", "href": "/2026/07/13/the-travel-rule-in-payments", "coverage": "derived" }, { "type": "article", "label": "TIPS: instant settlement in central-bank money", "href": "/2026/07/13/tips-instant-settlement", "coverage": "derived" }, { "type": "article", "label": "Tokenized deposits and the unit of account", "href": "/2026/07/18/tokenized-deposits-and-the-unit-of-account", "coverage": "derived" }, { "type": "article", "label": "Trade-Based Money Laundering: Value Hidden in Trade", "href": "/2026/07/13/trade-based-money-laundering", "coverage": "derived" }, { "type": "article", "label": "Treasury liquidity: pooling, sweeping, and virtual accounts", "href": "/2026/07/18/treasury-liquidity-pooling-sweeping-and-virtual-accounts", "coverage": "derived" }, { "type": "article", "label": "US Real-Time Payments (RTP)", "href": "/2026/07/13/us-real-time-payments-rtp", "coverage": "derived" }, { "type": "article", "label": "What sanctions are and why payments are screened", "href": "/2026/07/13/what-are-sanctions-in-payments", "coverage": "derived" }, { "type": "article", "label": "Who issues sanctions: regimes and authorities", "href": "/2026/07/13/sanctions-authorities-and-regimes", "coverage": "derived" }, { "type": "flow", "label": "A Fedwire funds transfer (US RTGS)", "href": "/explore/fedwire-funds", "coverage": "direct" }, { "type": "flow", "label": "A TARGET2 (T2) settlement (euro RTGS)", "href": "/explore/t2-rtgs", "coverage": "direct" }, { "type": "flow", "label": "SWIFT gpi (tracked correspondent payment)", "href": "/explore/swift-gpi", "coverage": "direct" }, { "type": "flow", "label": "SWIFT route selection — RMA, SSI and accounts", "href": "/explore/swift-rma-routing", "coverage": "direct" }, { "type": "glossary", "label": "Account-based CBDC", "href": "/glossary#account-based-cbdc", "coverage": "derived" }, { "type": "glossary", "label": "Adverse media", "href": "/glossary#adverse-media", "coverage": "derived" }, { "type": "glossary", "label": "Advising bank", "href": "/glossary#advising-bank", "coverage": "derived" }, { "type": "glossary", "label": "Alert", "href": "/glossary#alert", "coverage": "derived" }, { "type": "glossary", "label": "Asset freeze", "href": "/glossary#asset-freeze", "coverage": "derived" }, { "type": "glossary", "label": "Atomic settlement", "href": "/glossary#atomic-settlement", "coverage": "derived" }, { "type": "glossary", "label": "Behavioural analytics", "href": "/glossary#behavioural-analytics", "coverage": "derived" }, { "type": "glossary", "label": "Beneficial owner (UBO)", "href": "/glossary#beneficial-owner", "coverage": "derived" }, { "type": "glossary", "label": "Bill of lading", "href": "/glossary#bill-of-lading", "coverage": "derived" }, { "type": "glossary", "label": "Book payment", "href": "/glossary#book-payment", "coverage": "derived" }, { "type": "glossary", "label": "Canonical format", "href": "/glossary#canonical-format", "coverage": "derived" }, { "type": "glossary", "label": "Case management", "href": "/glossary#case-management", "coverage": "derived" }, { "type": "glossary", "label": "Cash sweeping", "href": "/glossary#cash-sweeping", "coverage": "derived" }, { "type": "glossary", "label": "Cash Transaction Report (CTR)", "href": "/glossary#cash-transaction-report", "coverage": "derived" }, { "type": "glossary", "label": "Central Liquidity Management (CLM)", "href": "/glossary#central-liquidity-management", "coverage": "derived" }, { "type": "glossary", "label": "CHAPS", "href": "/glossary#chaps", "coverage": "derived" }, { "type": "glossary", "label": "CHIPS", "href": "/glossary#chips", "coverage": "derived" }, { "type": "glossary", "label": "CRS (Common Reporting Standard)", "href": "/glossary#crs", "coverage": "derived" }, { "type": "glossary", "label": "Customer due diligence (CDD)", "href": "/glossary#cdd", "coverage": "derived" }, { "type": "glossary", "label": "Cut-off", "href": "/glossary#cut-off", "coverage": "derived" }, { "type": "glossary", "label": "Daily Validation Report (DVR)", "href": "/glossary#daily-validation-report", "coverage": "derived" }, { "type": "glossary", "label": "Designated person", "href": "/glossary#designated-person", "coverage": "derived" }, { "type": "glossary", "label": "Discrepant documents", "href": "/glossary#discrepant-documents", "coverage": "derived" }, { "type": "glossary", "label": "Disposition", "href": "/glossary#disposition", "coverage": "derived" }, { "type": "glossary", "label": "DNFBP (Designated Non-Financial Business or Profession)", "href": "/glossary#dnfbp", "coverage": "derived" }, { "type": "glossary", "label": "Documentary collection", "href": "/glossary#documentary-collection", "coverage": "derived" }, { "type": "glossary", "label": "Egmont Group", "href": "/glossary#egmont-group", "coverage": "derived" }, { "type": "glossary", "label": "Enhanced due diligence (EDD)", "href": "/glossary#edd", "coverage": "derived" }, { "type": "glossary", "label": "ESMIG (Eurosystem Single Market Infrastructure Gateway)", "href": "/glossary#esmig", "coverage": "derived" }, { "type": "glossary", "label": "False positive", "href": "/glossary#false-positive", "coverage": "derived" }, { "type": "glossary", "label": "FATCA (Foreign Account Tax Compliance Act)", "href": "/glossary#fatca", "coverage": "derived" }, { "type": "glossary", "label": "FATF (Financial Action Task Force)", "href": "/glossary#fatf", "coverage": "derived" }, { "type": "glossary", "label": "FedNow Service", "href": "/glossary#fednow", "coverage": "derived" }, { "type": "glossary", "label": "Fedwire Funds Service", "href": "/glossary#fedwire", "coverage": "derived" }, { "type": "glossary", "label": "Fiat-backed stablecoin", "href": "/glossary#fiat-backed-stablecoin", "coverage": "derived" }, { "type": "glossary", "label": "Fifty percent rule", "href": "/glossary#fifty-percent-rule", "coverage": "derived" }, { "type": "glossary", "label": "Financial intelligence unit (FIU)", "href": "/glossary#fiu", "coverage": "derived" }, { "type": "glossary", "label": "FSRB (FATF-Style Regional Body)", "href": "/glossary#fsrb", "coverage": "derived" }, { "type": "glossary", "label": "gpi Cover (gCOV)", "href": "/glossary#gcov", "coverage": "derived" }, { "type": "glossary", "label": "gpi Customer Credit Transfer (gCCT)", "href": "/glossary#gcct", "coverage": "derived" }, { "type": "glossary", "label": "gpi Financial Institution Transfer (gFIT)", "href": "/glossary#gfit", "coverage": "derived" }, { "type": "glossary", "label": "gpi Instant", "href": "/glossary#gpi-instant", "coverage": "derived" }, { "type": "glossary", "label": "gSRP (gpi Stop and Recall Payment)", "href": "/glossary#gsrp", "coverage": "derived" }, { "type": "glossary", "label": "Input credit file", "href": "/glossary#input-credit-file", "coverage": "derived" }, { "type": "glossary", "label": "Intraday liquidity", "href": "/glossary#intraday-liquidity", "coverage": "derived" }, { "type": "glossary", "label": "Issuing bank", "href": "/glossary#issuing-bank", "coverage": "derived" }, { "type": "glossary", "label": "Know your customer (KYC)", "href": "/glossary#kyc", "coverage": "derived" }, { "type": "glossary", "label": "Letter of credit", "href": "/glossary#letter-of-credit", "coverage": "derived" }, { "type": "glossary", "label": "Message template", "href": "/glossary#message-template", "coverage": "derived" }, { "type": "glossary", "label": "Money laundering (ML)", "href": "/glossary#money-laundering", "coverage": "derived" }, { "type": "glossary", "label": "Money laundering reporting officer (MLRO)", "href": "/glossary#mlro", "coverage": "derived" }, { "type": "glossary", "label": "Money mule", "href": "/glossary#money-mule", "coverage": "derived" }, { "type": "glossary", "label": "MT700", "href": "/glossary#mt700", "coverage": "derived" }, { "type": "glossary", "label": "Nested correspondent banking", "href": "/glossary#nested-correspondent", "coverage": "derived" }, { "type": "glossary", "label": "Nominated bank", "href": "/glossary#nominated-bank", "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": "OFAC", "href": "/glossary#ofac", "coverage": "derived" }, { "type": "glossary", "label": "OFSI", "href": "/glossary#ofsi", "coverage": "derived" }, { "type": "glossary", "label": "On-us payment", "href": "/glossary#on-us-payment", "coverage": "derived" }, { "type": "glossary", "label": "Ownership and control", "href": "/glossary#ownership-and-control", "coverage": "derived" }, { "type": "glossary", "label": "Payment engine", "href": "/glossary#payment-engine", "coverage": "derived" }, { "type": "glossary", "label": "Payment hub", "href": "/glossary#payment-hub", "coverage": "derived" }, { "type": "glossary", "label": "Payment market infrastructure", "href": "/glossary#market-infrastructure", "coverage": "derived" }, { "type": "glossary", "label": "Payment orchestration", "href": "/glossary#orchestration", "coverage": "derived" }, { "type": "glossary", "label": "Payment Pre-validation", "href": "/glossary#payment-pre-validation", "coverage": "derived" }, { "type": "glossary", "label": "PEP", "href": "/glossary#pep", "coverage": "derived" }, { "type": "glossary", "label": "Physical cash pooling", "href": "/glossary#physical-cash-pooling", "coverage": "derived" }, { "type": "glossary", "label": "Predicate offence", "href": "/glossary#predicate-offence", "coverage": "derived" }, { "type": "glossary", "label": "Programmable payment", "href": "/glossary#programmable-payment", "coverage": "derived" }, { "type": "glossary", "label": "Proxy addressing", "href": "/glossary#proxy-addressing", "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": "Rescreening", "href": "/glossary#rescreening", "coverage": "derived" }, { "type": "glossary", "label": "Retail CBDC", "href": "/glossary#retail-cbdc", "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": "Sanctions", "href": "/glossary#sanctions", "coverage": "derived" }, { "type": "glossary", "label": "Sanctions list", "href": "/glossary#sanctions-list", "coverage": "derived" }, { "type": "glossary", "label": "Scheme adapter", "href": "/glossary#scheme-adapter", "coverage": "derived" }, { "type": "glossary", "label": "Screening", "href": "/glossary#screening", "coverage": "derived" }, { "type": "glossary", "label": "SDN List", "href": "/glossary#sdn-list", "coverage": "derived" }, { "type": "glossary", "label": "Sectoral sanctions", "href": "/glossary#sectoral-sanctions", "coverage": "derived" }, { "type": "glossary", "label": "Settlement asset", "href": "/glossary#settlement-asset", "coverage": "derived" }, { "type": "glossary", "label": "Singleness of money", "href": "/glossary#singleness-of-money", "coverage": "derived" }, { "type": "glossary", "label": "Straight-through processing", "href": "/glossary#straight-through-processing", "coverage": "derived" }, { "type": "glossary", "label": "Structuring", "href": "/glossary#structuring", "coverage": "derived" }, { "type": "glossary", "label": "Suspense account", "href": "/glossary#suspense-account", "coverage": "derived" }, { "type": "glossary", "label": "Suspicious activity report (SAR)", "href": "/glossary#sar", "coverage": "derived" }, { "type": "glossary", "label": "SWIFT gpi", "href": "/glossary#gpi", "coverage": "derived" }, { "type": "glossary", "label": "T2S (TARGET2-Securities)", "href": "/glossary#t2s", "coverage": "derived" }, { "type": "glossary", "label": "TARGET2 / T2", "href": "/glossary#target2", "coverage": "derived" }, { "type": "glossary", "label": "Terrorist financing (TF)", "href": "/glossary#terrorist-financing", "coverage": "derived" }, { "type": "glossary", "label": "Token-based CBDC", "href": "/glossary#token-based-cbdc", "coverage": "derived" }, { "type": "glossary", "label": "Tokenized deposit", "href": "/glossary#tokenized-deposit", "coverage": "derived" }, { "type": "glossary", "label": "Tokenized settlement", "href": "/glossary#tokenized-settlement", "coverage": "derived" }, { "type": "glossary", "label": "Trade-based money laundering (TBML)", "href": "/glossary#trade-based-money-laundering", "coverage": "derived" }, { "type": "glossary", "label": "True match", "href": "/glossary#true-match", "coverage": "derived" }, { "type": "glossary", "label": "UN Security Council", "href": "/glossary#un-security-council", "coverage": "derived" }, { "type": "glossary", "label": "Unified ledger", "href": "/glossary#unified-ledger", "coverage": "derived" }, { "type": "glossary", "label": "Universal Confirmation", "href": "/glossary#universal-confirmation", "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": "Wholesale CBDC", "href": "/glossary#wholesale-cbdc", "coverage": "derived" }, { "type": "glossary", "label": "Wolfsberg CBDDQ", "href": "/glossary#cbddq", "coverage": "derived" }, { "type": "glossary", "label": "Wolfsberg Group", "href": "/glossary#wolfsberg-group", "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": "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": "scenario", "label": "A clean pass through the filter", "href": "/screening/lab/clean-pass", "coverage": "derived" }, { "type": "scenario", "label": "A common surname collides with the list", "href": "/screening/lab/name-collision-false-positive", "coverage": "derived" }, { "type": "scenario", "label": "Not on the list, still blocked: ownership adds up", "href": "/screening/lab/ownership-escalation", "coverage": "derived" }, { "type": "scenario", "label": "Strong name, wrong person: identifiers decide", "href": "/screening/lab/secondary-identifier-clear", "coverage": "derived" }, { "type": "scenario", "label": "The alias that was the real name", "href": "/screening/lab/alias-true-match", "coverage": "derived" }, { "type": "scenario", "label": "The hit hiding in the remittance line", "href": "/screening/lab/free-text-message-hit", "coverage": "derived" }, { "type": "topic", "label": "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": "Alert investigation and false positives", "href": "/screening/governance/alert-investigation-and-false-positives", "coverage": "derived" }, { "type": "topic", "label": "Asset freezes and restrictions", "href": "/screening/foundations/asset-freezes-and-restrictions", "coverage": "derived" }, { "type": "topic", "label": "Central bank digital currency (CBDC)", "href": "/learn/digital-money/central-bank-digital-currency", "coverage": "derived" }, { "type": "topic", "label": "Exceptions and investigations", "href": "/learn/operations/exceptions-and-investigations", "coverage": "direct" }, { "type": "topic", "label": "Forms of money: central vs commercial bank money", "href": "/learn/digital-money/forms-of-money-central-vs-commercial", "coverage": "derived" }, { "type": "topic", "label": "Governance and policy", "href": "/screening/governance/governance-and-policy", "coverage": "derived" }, { "type": "topic", "label": "Intraday liquidity and queues", "href": "/learn/clearing-settlement/intraday-liquidity-and-queues", "coverage": "derived" }, { "type": "topic", "label": "Money laundering, terrorist financing, and FATF", "href": "/screening/foundations/money-laundering-and-fatf", "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 market infrastructures", "href": "/learn/clearing-settlement/payment-market-infrastructures", "coverage": "derived" }, { "type": "topic", "label": "Payment security and fraud basics", "href": "/learn/operations/payment-security-and-fraud-basics", "coverage": "derived" }, { "type": "topic", "label": "Risk-based screening", "href": "/screening/foundations/risk-based-screening", "coverage": "derived" }, { "type": "topic", "label": "Sanctions screening vs AML vs fraud", "href": "/screening/foundations/sanctions-vs-aml-vs-fraud", "coverage": "derived" }, { "type": "topic", "label": "Stablecoins and tokenized deposits", "href": "/learn/digital-money/stablecoins-and-tokenized-deposits", "coverage": "derived" }, { "type": "topic", "label": "SWIFT gpi and payment tracking", "href": "/learn/swift-mt/swift-gpi-and-tracking", "coverage": "derived" }, { "type": "topic", "label": "Testing and tuning", "href": "/screening/governance/testing-and-tuning", "coverage": "derived" }, { "type": "topic", "label": "Trade finance payments", "href": "/learn/digital-money/trade-finance-payments", "coverage": "derived" }, { "type": "topic", "label": "Treasury liquidity structures", "href": "/learn/operations/treasury-liquidity-structures", "coverage": "derived" }, { "type": "topic", "label": "What sanctions are", "href": "/screening/foundations/what-sanctions-are", "coverage": "derived" }, { "type": "topic", "label": "Who imposes sanctions", "href": "/screening/foundations/sanctions-authorities", "coverage": "derived" } ] }