As set out in Digital Fraud, identity controls can all pass — correct credentials, correct second factor, recognised device — while the transaction is still fraudulent, because identity answers only one question and a trust decision depends on several more. Trust-based fraud prevention closes that gap by checking a narrow, specific fact with the organisation actually authoritative for it, at the point the transaction happens, rather than relying on identity checks alone.
A worked pattern: SIM swap fraud
SIM swap fraud — where a fraudster convinces a mobile operator to move a victim's number to a new SIM, intercepting one-time passwords and account-recovery messages — is a well-known account takeover vector. A mobile network operator is directly authoritative about whether a SIM has recently changed. A real-time check of SIM swap recency at the point of authentication, or before a high-value transaction is approved, is a direct application of the MNO-as-Trust-Authority pattern described in MNO Trust Infrastructure: the bank does not need the operator's underlying subscriber record, only a validated answer to a specific question.
Why this is a governance question, not just a technical one
A useful trust-based fraud check needs the same governance any Trust Assertion needs: a clear lawful basis for the query (typically legitimate interest, for fraud prevention specifically), a defined scope for what is being asked, and an audit trail of who queried what, when, and why — without the audit trail itself becoming a new store of personal information. See Trust Authorities and Trust Decision Engine for how that governance is structured.
This page does not claim a specific fraud-reduction outcome, deployment or partnership. It describes a general pattern — real-time validation of a narrow fact from an authoritative source — rather than results from any named pilot.