Skip to main content

Quick Implementation

1

Add HTML Element

First, add a container element to your HTML:
You may need to adjust your Content Security Policy (CSP) settings to allow the IDV module to function correctly. Refer to this page for more details.
2

Initialize Module

Create and mount the biometrics component:
3

Handle Events

Set up event listeners for biometric operations:

Provider-Specific Implementation

Implementation Flow

  1. Mount component
  2. User clicks “Upload Recording”
  3. Receive detection_complete event
  4. Background processing begins
  5. Receive results event

Example Usage

Biometrics Events

When the Biometrics component is successfully mounted, it will emit a ready event.To listen to this event, use:
When the Biometrics component successfully detects your information, it will emit a detection_complete event. This event will be emitted immediately before results. To listen to this event, use:
The end-user data is being submitted during this event. To listen to this event, use:
where the data types for the parameters are:
checkStatus will consist of either COMPLETE or FAILED, where
  • “COMPLETE”: The process and the check results are ready.
  • “FAILED”: The process is done but there was a genuine failure validating the captured ID and face.
document: the document object generated after the OCR extractentityId: FrankieOne’s internal reference for the individual
The component has run unsuccessfully. You can handle this event using a custom loading spinner or additional styles. To listen to this event, use:
To listen to this event, use:
input_required will emit entityId and current status of the process, such as:
  • waiting for Document upload WAITING_DOC_UPLOAD
  • waiting for selfie upload WAITING_SELFIE_UPLOAD
  • uploaded document has invalid type AWAITING_DOCUMENT_UPLOAD_INVALID_TYPE
  • or the process is either incomplete or interrupted INCOMPLETE / INTERRUPTED.
For Incode, a lack of camera access permissions triggers the INTERRUPTED event.
On error events, we throw all events from vendor back to you. To listen to this event, use:
If you’re using Incode, the possible messages are: InternalServerError, OSVersionNotSupported, and browserNotSupported

Implementation Best Practices

Mobile Optimization

Ensure proper viewport settings for mobile devices.

Error Handling

During development, test with both providers (if applicable) to ensure consistent behavior across different biometric implementations.
For detailed event documentation and advanced configurations, refer to the complete Biometrics Event Reference .