Implementation Through URL Forwarding

Initial Steps

With this integration option, the biometric operation process is conducted entirely on the MobbID Gateway domain, outside the integrator client's corporate domain.

To implement this method, simply add a link to your HTML page that points to the gatewayUrl, which is provided by the integrator client’s server.

Example Code

<a href="{{ gatewayUrl }}">Start Biometric Operation</a>

Key Details

1. Process Flow
   • When the user clicks the link, the gatewayUrl will open in a new browser tab.
   • The biometric operation process will then be initiated on the MobbID Gateway domain.
2. Redirect URL
   • At the end of the biometric operation, the user will be redirected to the redirectUrl, provided that the integrator client server has specified it during the configuration.

This integration approach allows for a simple and effective implementation, ensuring the biometric operation is carried out securely and independently of the integrator client's domain.

Error management

If an error occurs a modal dialog (can optionally be disabled) will be shown to the user with a brief description of the problem. By clicking the Accept button, the user will be automatically redirected to the redirectUrl (if exists) that the integrator client has provided.

A parameter with key error will be added to the redirectUrl with the type of error that occurred during the process, these being the errors that can occur during the onboarding process:

• BiometricError: A problem occurred during the biometric operation process.
• ConnectionError: The user's device does not have a stable network connection or is not available.
• HardwareError: The user's device does not have a camera and/or microphone (if necessary), or is not available for use due to a hardware problem.
• PermissionError: The user has not granted access permissions to the camera and/or microphone (if required).
• SupportError: The process cannot be completed because an unexpected error has occurred (contact us to report it).
• TimeoutError: The process has been canceled because the user has exceeded the maximum time set.
• TokenError: The processId has expired and is no longer valid.

In some cases, in addition, a parameter with key cause will also be added to the redirectUrl, which will indicate a more specific cause of the error, and allow the integrator to perform more specific actions. Here are the specific possible causes of each error:

HardwareError

• DeviceError: The user's camera is not accessible by the browser and cannot be accessed (generic hardware error).
• DeviceNotAvailableError: The user's device does not have a camera.
• DeviceNotReadableError: The user's camera is in use by another process and cannot be accessed.

PermissionError

• DeviceNotAllowedError: The user has not granted access permissions to the camera.