Make trusted information reusable across services and channels.
Turn information your organization already holds into verifiable credentials that other services can independently verify.
Why verify the same information again and again?
Organizations already hold information about their customers that they know or have verified. But when another service needs to rely on it, the verification process often starts from scratch.
Put trusted information to work across services.
Cross-service onboarding
Let customers reuse verifiable information across services and organizations instead of submitting it again.
Less duplicated verification, faster onboardingCustomer authentication
Use digitally verifiable customer information to reduce repeated authentication checks.
Faster authentication, less frictionAccount recovery
Use verifiable customer information as an additional assurance signal when restoring account access.
Stronger recovery assuranceCreate. Share. Verify.
Create verifiable credentials
Turn information your organization already knows into something others can verify.
Let the information move
Your users can share it across systems, organizations and workflows.
Check it when it arrives
The recipient can verify the source, integrity and status of the information.
under 60 seconds
We worked with global telecom Telefónica to test a mobile authentication flow for customers calling its contact center. Instead of answering security questions or using SMS OTPS, customers receive a prompt on their phone, unlock with biometrics and tap to approve.
Explore the Telefónica pilot“The solution transforms authentication times from 3–4 minutes with traditional methods to under 60 seconds.”
Glyn Povah, Global Product Development Director, Telefónica
Frequently asked questions
No. Truvera is designed to work alongside the systems you already use to establish, manage, or verify customer information.
Those systems can continue doing what they do today. Truvera gives selected information a way to move into another interaction with verifiable proof behind it.
No. Credential functionality can be embedded into existing apps and workflows where appropriate.
The user experience should fit the workflow rather than requiring customers to move into a separate Truvera-branded application.
Depending on the credential and verification flow, only the information required for the interaction needs to be presented.
Where higher assurance is required, credentials can be bound to the intended holder.
Biometric verification is one possible way to add that assurance, but it is not required for every workflow.
The receiving organization or ecosystem decides which issuers it recognizes as trusted sources for particular information.
Verification can confirm who issued the information. Trust rules determine whether that issuer should count for the workflow.
