The trust problem
A bank typically knows a customer's identity, accounts, transaction history, how and where they normally transact, and significant purchases such as a vehicle or a home. As AI begins to analyse that information and increasingly act on the bank's behalf, the relevant question changes from "does the AI have enough data?" to "does the AI have access to the right trusted information, from an authoritative source, for the purpose it is acting on?"
Who could act as the Trust Authority
The bank itself, for facts it is already authoritative about — account ownership, an established customer relationship, verified identity, transaction history consistent with past behaviour.
Who is the Trust Consumer
Internal AI systems acting on the bank's behalf, and external partners — such as insurers or merchants — that need to rely on a specific fact the bank already holds, without receiving the underlying customer record.
What trusted outcome is required
Confirmation that a person controls a particular account, that a transaction is consistent with an established relationship, that an identity has been verified, or that an instruction came from someone with the authority to give it — without needing every piece of underlying personal information used to establish those facts.
What changes when trust becomes reusable
The bank does not have to disclose everything it knows to prove a specific fact. Fraud prevention, onboarding and AI decision-making can all draw on trusted outcomes instead of broader data exports, reducing both the volume of data moved and the risk that comes with holding it.
This page reflects Gwirio's existing thinking on banking and financial services. It describes a proposed application of Trust Infrastructure, not an existing Gwirio deployment or named customer relationship.