Known Issues

The Javascript SDK for Wink Login 1.3 is suitable to be called in webapps for browser access or inside Webview for native apps. It is not yet available as a native Android or iOS SDK
The Javascript SDK is more suitable for client side applications and might not work correctly with some server side programming environments such as Nodejs. These versions might be available upon request ( please check with your Wink Account Representative ).
Enrollment is a 2 step process ( face liveness check + face and voice capture ). This process can take 10-12 seconds. If the user face is not present for the entire 10-12 seconds, enrollment can fail
User DOB is not validated. User can provide fake DOB. If user cannot remember fake DOB in the future when requested for authentication, user can be locked out unless they can access Wink Login in acceptable conditions by providing good face and voice
User phone number and email address are not checked for possession. It is possible for users to provide fake data. Future versions of Wink Login will provide device and email possession check feature ( ensuring the user has access to the provide phone number and email )
Voice liveness check accuracy: To pass voice liveness, user must provide good voice without too much background noise ensuring especially the presence of 3-4 digit number being loud and clear in the speech.
Service Not Available Error: SDK might display “Service not available” error on rare occasions if there are issues with the user’s device, internet connection or Wink server down situations
Wink Login SDK might show inconsistencies of performance if used in an iFrame or popups. It is best used in redirect mode by the host app.
We sometimes get multiple random numbers and lengthy numbers in the voice test . This might lead to voice liveness failure.
In yellow case screen on session expiry forces user to kill browser to restart
Face image of user is shown only if voice liveness is true.