As described in the Product Overview, IdentityX is comprised of both the IdentityX Server component and the IdentityX Authenticator application on the customer’s mobile device. When the customer initiates a transaction on the Service Provider’s website (e.g., transferring money through online banking), a request is made to the IdentityX Server for verification. The IdentityX Server determines which verification methods are required (e.g., some combination of biometrics, passwords, and/or GPS location) based on the type of request from the Service Provider and makes the appropriate request to the IdentityX Authenticator application on the mobile phone.
The IdentityX Authenticator application runs on the customer's mobile device. It is responsible for receiving authentication requests from the server and displaying them in a transaction list for the customer to act upon. When the customer selects a transaction, the IdentityX Authenticator application presents a GUI to capture whatever authentication credentials are required, whether PIN and/or some form of biometric. Once the customer submits their data, the Authenticator sends this information to the server for comparison to the information already on record for that individual.
Depending upon how the IdentityX solution is configured, a successful validation may be directly communicated to the Service Provider, or the IdentityX Server could return a one time use password to the Authenticator for display. The customer would then be required to enter this number on the Service Provider's application to provide proof of a successful IdentityX authentication.
The IdentityX Authenticator application is a standalone component which may be rebranded to suit the Service Provider. Alternately, if the Service Provider wishes to embed this functionality into its own mobile application, the IdentityX Authenticator SDK is available to facilitate this integration.