top of page
FAQ's
Implementing V2verify. Here's how.
Contactless Authentication - V2verify supports a fast, natural authentication experience without requiring passwords, PINs, callback codes, or physical contact.
Security - V2verify uses a simple voice interaction as part of a multi-factor authentication process designed to confirm the right live user in real time.
User experience - Users complete authentication through a fast, natural interaction without needing to remember passwords, PINs, callback codes, or security questions.
Privacy - During the authentication event, no PII is exchanged. The system returns an authentication result without exposing unnecessary personal data or the mechanics behind the decision.
Additional Q&A
Q.
What if the user has a cold or is in a loud environment?
A.
V2verify is designed to support real-world use, including normal variation in a user’s voice or environment. However, very loud environments can still affect capture quality. A good rule of thumb: if the user would struggle to carry on a normal phone conversation, the environment may not be ideal for authentication.
Q.
Voice reproduction technology is continually evolving, what are the chances of a recording breaking in?
A.
V2verify does not rely on voice alone. The platform uses layered authentication to evaluate the live interaction and the broader access context before returning an authentication result. This helps protect against recordings, replay attempts, synthetic voice threats, and other impersonation risks.
Q.
Is the technology hard to implement?
A.
Integration with V2verify is a simple process. We can provide our technology through our app (v2branded or white-labeled), or we can integrate it into an IVR, an existing app (with an SDK), or other technology through an Open API. The system can be deployed on-premise, on any cloud platform, or a hybrid environment. The ecosystem also scales easily and can be used for many use-cases without needing to modify the underlying technology.
Q.
How does V2verify handle user onboarding?
A.
Initial identity proofing remains controlled by the organization using V2verify. For example, employees are verified through the company’s existing onboarding process, and customers are verified through the institution’s existing account-opening or enrollment process. V2verify is then used to authenticate that verified user in future access or approval events.
Q.
Does V2verify use the public phone network for authentication?
A.
No. V2verify authentication is completed through a secure, encrypted channel and does not depend on the public phone network. The authentication event returns a result without exchanging PII.
bottom of page