On September 8, federal banking agencies issued updated guidance allowing banks to use verifiable digital credentials, including state-issued mobile driver's licenses, as part of customer identity verification. On its own, that is a practical modernization of how a bank can confirm who someone is. Seen in context, it is another step in a longer shift. Identity is moving away from information gathered once, through a single onboarding event, toward data that can be verified and maintained through multiple sources over the life of the relationship.

That direction is welcome. It also raises a question many banks have not fully answered. If identity is going to be verified and updated continuously, from more sources and over more time, where does that identity actually live?

The architecture underneath the process matters more than the verification method layered on top of it. In many banks, customer information is distributed across deposit, lending, card, onboarding, and servicing systems. Each maintains its own identifiers and attributes for the same person. Relationships among customers, businesses, accounts, and beneficial owners are not held in one place. They are reconstructed across systems whenever someone needs to see the whole picture. The same customer effectively exists many times over, as partial records that never fully agree.

This fragmentation becomes more consequential as customer information changes. FinCEN requires banks to conduct ongoing monitoring and, on a risk basis, to maintain and update customer information when new information becomes relevant to a customer's risk profile. A change surfaced through transaction activity is therefore not simply a compliance event inside one system. It has to be associated with the same customer everywhere the institution represents that person. When each application holds its own version of the customer, updating one does not update the others, and the institution's view of its own customer quietly drifts out of alignment.

This is where the shape of the record decides the outcome. A change to a customer is only as valuable as the institution's ability to apply it consistently. If identity is an attribute recreated inside each account, every update becomes a synchronization problem across systems. If identity is a single record that accounts reference, an update happens once and is true everywhere.

A unified party model establishes that record once. Accounts, products, transactions, businesses, beneficial owners, and other relationships reference the same underlying party, rather than maintaining separate versions of the customer in each application. When identity is modeled this way, an institution gains:

• One authoritative record per customer, referenced by every account and product
• Relationships among people, businesses, accounts, and beneficial owners held directly, rather than reconstructed on demand
• Risk-profile and identity updates that apply once and stay consistent across the institution
• A current, connected customer view for onboarding, servicing, and monitoring
• A cleaner basis for demonstrating ongoing due diligence to examiners

UniFi applies that model across the financial record. Identity and relationship data stay consistent as customers open products, transact, and change over time, because those events reference one party record rather than many. New verification methods, including digital credentials, then update a single source of identity instead of adding one more siloed copy of it.

The value of the new guidance is not only that banks can accept better credentials. It is that better credentials are largely wasted on a fragmented record. Customer identity becomes far more useful when the institution maintains it as a relationship, rather than recreating it as an attribute of each account.