IDENTITY WALLET / OPTIONAL ADVANCED IDENTITY
An identity your customer can carry.
One identity. Portable preferences. Permission stays with the person.
Portable identity
A permissioned context layer
SELECTED FOR THIS INTERACTION
Nothing else is shared by default.
Concept illustration, not a live product screenshot.
THE PORTABLE HANDOFF
Verify when needed.
Remember with permission.
The goal isn't to put another login in front of every customer. It's to reuse the right proof or preference at the right moment across participating services.
Start with a trusted person.
Resolve or verify an identity through an authorized account, partner, or credential flow.
01 / ESTABLISHAsk for only what's needed.
A participating experience requests a defined attribute or preference, within the customer's approved scope.
02 / PERMISSIONCarry the right context forward.
Only permitted status, proof, or preference is made available to the requesting experience.
03 / PRESENTWHAT MAY TRAVEL
The customer carries the identity.
Your brand keeps its relationship.
No wholesale sharing of another brand's CRM, unrelated purchase history, or unapproved customer attributes. Permission, purpose and destination define what a requesting service can receive.
Verified status
Reusable age, membership, or eligibility references where a supported verification flow is implemented.
Preferences
The settings a person chooses to carry, not an unrestricted copy of their purchase history.
Consent + purpose
A record of what was approved, for which use, and where it can be sent.
Agent permissions
A foundation for linking approved delegated actions to the customer and the limits they establish.
FOR PEOPLE
Keep control. Skip unnecessary repetition.
Carry selected permissions, preferences and verified status into the next approved experience, with the ability to withhold unrelated information.
FOR BUSINESSES
Recognize the relationship. Reduce friction.
Use approved credentials and preferences where a participating integration supports them. Trust ID's standard visitor-recognition tag still works without a wallet prompt or phone OTP.
Explore optional identity infrastructure or talk with us about the appropriate implementation path.
View technical resources