UK open finance infrastructure needs testable governance models

At a glance

What this is: Raidiam is backing a Saïd Business School research programme for the FCA Smart Data Accelerator that examines how UK open finance infrastructure, trust and governance models can be made testable before ecosystem scale creates control failures.

Why it matters: IAM and PAM teams should pay attention because the article treats identity frameworks, accreditation models, trust anchors and liability allocation as core design choices, not downstream administration.

Context

Open finance extends open banking by allowing data sharing across more sectors, which means the control problem shifts from a narrow payments context to a wider ecosystem with more participants, more trust relationships and more governance choices. In that environment, access and liability decisions cannot be treated as static policy statements because they shape how data-sharing networks scale and how safely they can be operated.

For identity and access practitioners, the important point is that the article places identity frameworks, accreditation models, trust anchors and consent representation inside the architecture discussion. That is a genuine governance issue for IAM, since the boundary between participant onboarding, delegated authority and ecosystem trust becomes part of the system design rather than a separate operational layer.

Key questions

Q: What breaks in open finance when identity and trust models are not testable?

A: The ecosystem may still connect technically, but participation, assurance and liability become unclear. That creates a gap between data exchange and governed access, which is where scale turns into control failure. Testable models let regulators and operators see whether identity, consent and trust rules still hold under realistic conditions.

Q: Why do consent and liability need to be designed together in open finance?

A: Because consent tells you whether data may move, while liability tells you who is responsible when the movement is disputed or harmful. If those two are separated, the ecosystem can become operationally functional but governance-poor. Treat them as linked controls in the same architecture decision.

Q: What are the signs that an open finance governance model is too abstract?

A: The model is too abstract when it cannot specify trust anchors, participant assurance, consent representation or testing parameters in a way that engineers and regulators can both evaluate. If the framework cannot be simulated in a sandbox, it is not yet executable governance.

Q: How should regulators compare centrally coordinated and federated ecosystem designs?

A: They should compare how each model assigns accountability, enforces participant assurance and handles cross-sector interoperability. The right choice is the one that can be tested most clearly against real governance questions, not the one that sounds simplest on paper.

Technical breakdown

Why open finance needs testable trust models

Open finance depends on many organisations sharing data through common rails, but scale changes the trust problem. In a small environment, organisations can rely on bilateral agreements and manual oversight; in a multi-sector ecosystem, those assumptions break because participants, data types and liability boundaries multiply. A testable governance model makes the trust rules explicit enough to be simulated, challenged and compared before live rollout. That is especially important where identity frameworks, accreditation and consent representation determine who may participate and on what terms. The architectural question is not only whether access works, but whether the trust model can be proved under structured testing.

Practical implication: treat trust architecture as something that must be exercised in a sandbox, not merely documented in policy.

Identity frameworks and accreditation as ecosystem controls

The article places identity frameworks and accreditation models at the centre of infrastructure design because they determine how participants are admitted, recognised and constrained across the ecosystem. In open finance, those choices function like federated IAM controls: they define the trust anchor, the assurance level attached to each participant and the way delegated access is governed. If those controls are inconsistent, the ecosystem may still connect technically but remain weakly governed operationally. This is why the distinction between interoperability and assurance matters. A system can move data between parties without establishing a durable model for who is trusted, at what level and under what liability conditions.

Practical implication: define participant assurance and trust anchors before broad interoperability is allowed to scale.

Consent, liability and governance cannot be separated

Consent representation is not a user-interface detail in open finance, it is part of the trust model that supports lawful and defensible data sharing. Once multiple sectors and data categories are involved, liability also becomes an architectural variable because responsibility depends on how identity, permissions and routing decisions are encoded. That means governance has to cover more than policy language. It has to specify how consent is represented, how disputes are handled and how responsibility is assigned across centrally coordinated, federated or hybrid designs. The article is pointing to a core lesson: the governance model must be precise enough to survive testing, not just acceptable on paper.

Practical implication: align consent, accountability and liability rules with the technical architecture before pilot expansion.

NHI Mgmt Group analysis

Testable governance is now the minimum viable control for open finance. The article shows that infrastructure choices in open finance are not neutral because they shape participation, resilience and liability. In identity-led ecosystems, a governance model that cannot be simulated or stress-tested is not ready for scale. Practitioners should treat testability as a control objective, not a research preference.

Identity frameworks are becoming ecosystem governance primitives. This article places participant identity, accreditation and trust anchors inside the architecture conversation, which is where they belong. When those elements are weakly defined, interoperability can expand faster than assurance. The practical conclusion is that IAM-style governance must be built into the ecosystem blueprint, not layered on after integration.

Open finance creates a trust architecture problem, not just a data-sharing problem. The real issue is not whether APIs can exchange information, but whether the ecosystem can prove who is trusted, under what conditions and with what liability boundaries. That makes consent representation and standards governance part of the security model. Practitioners should evaluate open finance designs as trust systems first and data pipelines second.

Hybrid ecosystem models will dominate because no single governance pattern solves every boundary problem. The article’s focus on centrally coordinated, federated and hybrid approaches reflects a market that is still searching for the right balance of control and scale. That means regulators and operators will need to compare not just technical interoperability but operational accountability. The practitioner takeaway is to plan for mixed governance models rather than assume one pattern will cover every use case.

Open finance will expose the gap between policy intent and executable controls. The strongest signal in the article is that future frameworks must be expressed as technically coherent blueprints that can be tested in synthetic environments. That is how governance moves from principle to evidence. For practitioners, the discipline now is to translate policy claims into verifiable control behaviour.

What this signals

Testability is becoming the dividing line between open finance strategy and open finance control. For practitioners, the immediate signal is that policy language will not be enough if the architecture cannot be exercised in a sandbox or pilot environment. The safer programme posture is to require identity, consent and liability decisions to be expressed as controls that can be tested before wider rollout.

Open finance will force IAM teams to think in ecosystem terms. Once trust anchors, accreditation and delegated access are part of the design, participant governance stops looking like a back-office function and starts looking like infrastructure. That changes how organisations should plan onboarding, assurance and oversight across multi-party data sharing.

Identity governance debt is the risk of leaving participant trust undefined until integration time. In an ecosystem setting, every vague rule about who is trusted, who can act and who carries liability eventually shows up as operational friction. Practitioners should expect more pressure to document these decisions in architecture reviews rather than policy appendices.

For practitioners

• Map trust anchors to participant assurance levels Define which identity proofing, accreditation and delegation conditions are required before a party can join or act within the ecosystem. Make those conditions explicit enough to be tested against synthetic data and pilot workflows.
• Model consent as a governed control, not a statement Specify how consent is represented, updated and revoked across sectors so that the model can be exercised in the FCA Digital Sandbox and compared across architecture options.
• Test liability allocation across ecosystem patterns Compare centrally coordinated, federated and hybrid designs to see where accountability shifts when data is routed, delegated or transformed across participants.
• Separate interoperability from assurance decisions Do not approve data-sharing pathways solely because APIs can connect. Require assurance, onboarding and monitoring rules that show who is trusted and how that trust is evidenced.

Key takeaways

• Open finance shifts the main governance problem from isolated access management to ecosystem-wide trust design.
• The article’s central message is that identity frameworks, accreditation and liability must be testable before scale.
• Practitioners should expect future open finance programmes to demand executable controls, not just policy commitments.

Key terms

• Open Finance: Open finance is a model for sharing financial data and services beyond a single bank, with customer permission and controlled access. It extends open banking into a broader ecosystem that can include lending, insurance, payments, and investment services, all connected through interoperable interfaces and consent-driven data sharing.
• Trust anchor: A trust anchor is the root authority that signs federation metadata and establishes the policies other participants inherit. In practice, it controls who can join, what cryptographic rules apply, and how trust is delegated across an ecosystem. The security posture of the whole federation depends heavily on this layer.
• Accreditation Model: An accreditation model defines how a participant is approved to join and operate within an ecosystem. It usually combines technical assurance, policy compliance, and organisational eligibility, and it matters because weak accreditation turns interoperable access into unmanaged trust.
• Consent Representation: Consent representation is the machine-readable way a system records what a user or organisation has permitted. In shared-data ecosystems, it must be precise enough to drive access decisions, auditable enough to prove compliance, and durable enough to survive multi-party processing.

Deepen your knowledge

NHI Foundation Level course, the industry's only accredited NHI security programme, covers NHI governance, human identity, identity lifecycle and secrets management. It helps practitioners translate trust and access decisions into controls that can be explained, tested and audited.