Banking & payments | Modelled case study
Map cryptography across a bank payment rail before migration
Which payment services can move first without breaking clearing, fraud, or settlement dependencies?
The modelled organisation
A recognisable problem reaches the operating agenda
This composite scenario follows the CISO · Head of Payments · Cryptography Lead functions. It is grounded in the cited problem context but does not identify a real customer.
Operating environment
A regulated bank operates real-time and batch payment services across internal platforms, clearing schemes, processors, HSMs, fraud controls, and external counterparties.
What is at stake
A cryptographic change must preserve authorization, settlement finality, scheme interoperability, evidence retention, and uninterrupted customer access.
Situation
Certificates, HSM keys, message signatures, and TLS dependencies are spread across gateways, switches, batch jobs, and counterparties, so a migration plan built from CMDB labels alone misses live cryptographic use.
Event that forces action
A board quantum-readiness deadline or payment-platform modernization programme needs a defensible scope.
Concrete system boundary
Systems this case study puts in scope
The model is specific about the operational surfaces that must be discovered, changed, or independently checked.
payment gateways and switches
clearing and settlement interfaces
HSM key domains
fraud and reconciliation services
Modelled case study walkthrough
How this organisation would use QNSI
The walkthrough connects the real-world problem to a bounded QNSI contribution and an independently reviewable result.
Recognise the operating condition
Certificates, HSM keys, message signatures, and TLS dependencies are spread across gateways, switches, batch jobs, and counterparties, so a migration plan built from CMDB labels alone misses live cryptographic use.
Frame the decision the owners must make
Which payment services can move first without breaking clearing, fraud, or settlement dependencies?
Apply QNSI to the controlled boundary
Use QNSI inventory and policy records to classify payment-path algorithms, owners, data lifetime, and migration constraints, then stage approved NIST-standardized targets.
Leave the team with a concrete result
A payment-rail cryptographic dependency register with owners, exception reasons, and an ordered transition backlog.
Prove the result in the organisation's environment
The bank must validate scheme rules, counterparty interoperability, latency, HSM boundaries, and change-window controls.
What useful success looks like
A decision artifact plus proof from the real environment
The model stops at a target result. It becomes an actual case study only when a customer produces and independently validates this evidence in production.
Decision artifact
A payment-rail cryptographic dependency register with owners, exception reasons, and an ordered transition backlog.
Independent validation boundary
The bank must validate scheme rules, counterparty interoperability, latency, HSM boundaries, and change-window controls.
Real-world problem grounding
Primary sources behind the model
These sources establish the external requirement, failure mode, or risk context used to model this case. They do not endorse HEOSSI or prove that QNSI completed the scenario.
Customer evidence status
This is modelled, not a customer claim
The organisation is a composite and the result is a target state. This page does not prove a deployment, customer outcome, certification, legal conclusion, regulator endorsement, or completed control.