What is AllPass.AI?

Allpass.AI is a comprehensive platform designed specifically to streamline and enhance the Know Your Customer (KYC) and Anti-Money Laundering (AML) processes. Our platform offers powerful tools to automate user verification, monitor compliance, and manage regulatory requirements with precision and ease.

No-Code Functionality

One of the standout features of Allpass.AI is its no-code environment, allowing you to easily configure and use the platform without any programming knowledge. This ensures that users can swiftly adapt the platform to their specific needs, reducing the time and effort required to get up and running.

What's Inside This Documentation?

This documentation serves as your guide to fully understanding and utilizing the Allpass.AI platform. Inside, you will find:

• Workplace Functionality Overview: A detailed breakdown of the core features and functionalities available within the Allpass.AI platform, designed to help you manage your compliance tasks effectively.

• Integration Guide: Step-by-step instructions on how to integrate Allpass.AI with your existing systems, ensuring a seamless setup process and optimal performance.

• Web SDK Description: Comprehensive information about our Web SDK, including installation, configuration, and usage details, allowing you to extend and customize the platform to meet your specific needs.

We hope this documentation will help you navigate and maximize the potential of Allpass.AI. Should you need further assistance, our support team is always ready to help.

Sign Up

• Open your web browser and navigate to our website

Assigning roles to users is a straightforward process that ensures each team member has the appropriate permissions for their responsibilities.

New Users

Administrators can easily invite new users by email and assign them roles during the invitation process, as well as manage roles for existing users:

It enhances the verification process by requiring users to take a selfie while holding their identification document.

• Add Selfie with a Document step into the flow canvas at the appropriate position in the flow.

• Click on Selfie with a Document to open its customization options.

The Thank You step is designed to acknowledge and thank users for completing the verification process. It is always placed at the end of the flow.

• Add Thank You Screen step into the flow canvas at the appropriate position in the flow.

• Click on Thank You Screen to open its configuration options.

Header

The Header is located at the top of almost every page on the platform and provides quick access to essential features and information.

The Liveness step is a crucial part of the verification process, designed to confirm that the applicant is a real, live person and not a spoof or fake identity. This step typically involves a video recording of the user performing specific actions, such as blinking or turning their head, to demonstrate liveness. You can find the recording in the Liveness block within the Applicant's profile:

This video serves as proof that the applicant completed the required actions to verify their liveness. While the screenshot only shows a still image, the platform typically allows the reviewer to access and review the entire video to ensure the liveness check was performed correctly.

The Workflow Builder includes a convenient auto-save feature that ensures your work is not lost if you forget to save manually.

If you create or modify a workflow but do not click the Save button before closing the page, the workflow will automatically be saved as a draft. This functionality helps prevent data loss and allows you to continue your work seamlessly at a later time.

• To continue working on a draft workflow, simply navigate to your list of workflows and locate the ones marked as "Draft.”

This page provides the complete list of databases used by the platform to conduct Sanctions and Politically Exposed Persons (PEP) screening. The sources include international sanctions lists, regulatory watchlists, and other authoritative data providers that support comprehensive compliance checks.

Import library to your web application

Start by adding the minified code to your webpage from the unpkg CDN in your HTML file:

<script
 type="text/javascript"
 src="https://unpkg.com/@allpass/web-sdk"
></script>

Or you can install it via npm:

npm install --save @allpass/web-sdk

And then import it in your code:

import Allpass from '@allpass/web-sdk';

Our Platform offers two distinct modes for users: Test Mode and Live Mode. Understanding the differences between these modes is crucial for effectively utilizing our service. Below is a detailed description of each mode.

Test Mode is designed for users to familiarize themselves with the platform’s features and functionality without the risk of affecting real data. It is ideal for initial testing, training, and experimentation. In Test Mode, you are provided with 5 free verifications. This allows you to test the system and understand how it works without any cost.

Live Mode is intended for actual identity verification processes required for compliance. All verifications performed in this mode are real and affect actual data. Verifications performed in Live Mode are billed according to your subscription plan or pay-per-use agreement.

Switching Between Modes

You can switch between Test Mode and Live Mode at any time through the toggle in the header:

When users receive a verification link, the process is designed to be seamless, user-friendly, and flexible, ensuring a smooth and uninterrupted verification journey. Here’s what happens on the user side when they receive a verification link:

• Users will receive the verification link via the specified communication channel.

• The link redirects them to the verification platform, where the process begins.

• If users need to pause the verification process, they can do so without losing their progress. Upon returning, they can resume the verification from the exact step where they left off, ensuring a smooth and uninterrupted user journey.

• Users can start the verification process on one device, such as a desktop computer, and seamlessly continue on another device, like a mobile phone:

• Users proceed through the various verification steps (e.g., Document Check, Liveness Check, etc.) as defined in the verification flow.

• After completing all verification steps, users reach the page specified in the Redirect URL configured during the creation of the Application.

As a compliance officer, you have the capability to restart a verification flow for an applicant if needed. This can be particularly useful if the initial verification flow was not completed successfully.

Here’s how to manually change and restart a verification flow for a user:

• Navigate to the Applicants section from the Sidebar Menu.

• Within the applicant's profile, locate the Flow Tracker.

• Click the Generate Link button

• This will create a unique link to the current verification flow, which you can copy and send to the applicant for them to continue the process.

The User Roles and Permissions functionality allows you to create custom roles for different users within your organization. By specifying access levels for various items in the functionality list, you can ensure that each user has the appropriate permissions for their role. Here’s how it works:

• From the Sidebar Menu, navigate to the My Team section.

• Select Role Management:

• Click on the Add New button:

• Enter a name and a description for the new role.

• You will also see a list of functionalities with corresponding checkboxes.

• Review the list of functionalities and check the boxes for the items you want to grant access to for this role:

• Make sure to tailor the permissions according to the responsibilities associated with the role.

• Once you have selected the appropriate permissions, click on the Save button.

• The new role will now appear in the list of available roles.

The Crypto Wallet and Transaction Monitoring feature enables users to seamlessly track and verify cryptocurrency wallets and transactions. This tool enhances security and compliance by providing robust monitoring capabilities integrated directly into your workflows or accessible through a dedicated interface.

How to Check Wallets and Transactions:

1. Adding to the User Verification Workflow Leverage the Workflow Builder to integrate wallet and transaction checks directly into your user verification process. Follow these steps:

   • Navigate to the Workflow Builder in your dashboard.

   • Select the workflow where you want to include wallet and transaction monitoring.

   • Add the Transaction monitoring step from the available options:

• Configure the parameters, such as the maximum count of addresses and the list of allowed blockchains:

• Verification validity period - defines how long the verification result remains valid after it has been successfully completed. Once the validity period expires, the user must complete the verification step again.

• Save and activate the workflow to automatically verify wallets as part of the user onboarding or verification process.

The Questionnaire Step allows you to gather essential information from users through customized forms. This step can be tailored to include various questions relevant to your compliance process.

• Add the Questionnaire step into the flow canvas at the appropriate position.

• Click on Questionnaire step to open its configuration options.

• Select the desired questionnaire schema from the dropdown menu.

• Verification validity period - defines how long the verification result remains valid after it has been successfully completed. Once the validity period expires, the user must complete the verification step again.

The Address Verification results are displayed in the applicant's profile, offering a detailed overview of validation checks performed on the applicant’s address. Each check includes a status indicator and a concise description of the verification performed, helping users quickly assess the accuracy and completeness of the address information.

The Request Additional Information feature allows compliance officers to gather extra details from applicants without disrupting the regular verification flow.

Here’s how to request additional data from a user:

• Navigate to the Applicants section from the Sidebar Menu.

• Search for and select the applicant whose verification flow you want to restart.

• Once in the applicant's profile, locate the drop-down list for verification flows within the Flow Tracker.

• If available, click the Request Additional Information button:

• Fill in the required details for requesting the additional information.

• Create a unique link to the on-demand verification flow, which you can send to the applicant for them to provide the data you require.

The Email Verification results are displayed in the applicant's profile, providing a comprehensive breakdown of validation points for the applicant’s email address. Each validation point includes a status indicator and a brief description of the check performed:

If you disagree with any result, you have the option to deactivate this service for the applicant by moving the data to History.

The AML Step enhances security and compliance by monitoring user profiles for potential money laundering activities. Users have the option to enable or disable ongoing monitoring as needed.

• Add AML check step into the flow canvas at the appropriate position in the flow.

• Click on AML check to open its configuration options.

• Toggle on or off the ongoing monitoring feature.

• Set the periodicity for ongoing monitoring (e.g., daily, weekly, monthly).

• Take data from questionnaire - a checkbox that allows the system to reuse data collected earlier in the flow via a questionnaire. When selected, relevant user-provided data is automatically populated into this verification step.

• Verification validity period - defines how long the verification result remains valid after it has been successfully completed. Once the validity period expires, the user must complete the verification step again.

The facematch step involves a detailed comparison of the two or more images, providing a confidence percentage and a side-by-side visual representation to help users accurately verify the applicant's identity.

At the top of the section, the system displays the percentage of face match, which indicates the confidence level of the match between the two images:

The section prominently displays the selfie with the document captured during the verification process.

The image can be zoomed in for closer inspection by the reviewer:

The date when the selfie was captured is displayed above the image. This timestamp helps ensure that the selfie is recent and relevant to the current verification session.

Overview

When integrating webhooks, it is mandatory to implement timestamp validation to prevent outdated data from overwriting newer updates. Due to the webhook retry mechanism, which attempts to resend requests in case of failures, there is a possibility that an older webhook event may be delivered after a more recent one.

Potential Issue

If timestamp validation is not implemented, an earlier event may update the system with outdated information, leading to data inconsistency and potential operational issues.

Recommended Implementation

To mitigate this risk, follow these steps when processing webhook events:

1. Validate the timestamp: When receiving a webhook request:

   • Compare the incoming event's timestamp with the most recent processed event timestamp for the given entity.

   • Reject or ignore the event if its timestamp is older than the last recorded update.

Conclusion

Timestamp validation is essential for ensuring that only the latest webhook events are applied to the system. By implementing this check, you can prevent outdated data from being processed and maintain data integrity even in cases where webhook delivery is delayed or retried.

The Questionnaire Results section provides access to the applicant's completed questionnaire, which is often used to gather additional information required for the verification process.

This section allows users to review the applicant’s responses and assess any potential risks or compliance issues.

The results are displayed as a link to the completed questionnaire in a downloadable PDF format:

Download button is provided next to the file name, allowing the reviewer to easily access the PDF file. This feature ensures that the questionnaire results can be reviewed in detail, stored, or shared with other team members as necessary.

The Phone Verification step validates the applicant’s phone number to ensure its authenticity and activity. This step enhances security by confirming that the provided phone number is legitimate and can receive communications, which is essential for preventing fraud.

To add the Phone Verification step:

1. Add Phone Verification: Drag and drop the Phone Verification step into the flow canvas at the desired position within the verification flow.

As a compliance officer, you have the capability to change a verification flow for an applicant if needed. This can be particularly useful if different verification requirements arise.

Here’s how to manually change and restart a verification flow for a user:

• Navigate to the Applicants section from the Sidebar Menu.

• Search for and select the applicant whose verification flow you want to restart.

Conduct manual searches for wallets and transactions via the separate Crypto Monitoring page. Here's how:

• Open the dashboard and locate the Transaction Monitoring tab in the sidebar menu:

• Enter the wallet address or transaction ID in the search bar:

It allows you to align the appearance of the verification flows with your branding preferences. Customize colors, fonts, and button styles effortlessly to match your company's look and feel.

• Open your flow and go to Style tab:

This enhances security by confirming the user's contact information through a one-time password sent to their email. This step helps to ensure that the contact details provided by the user are valid and accessible.

• Add Email Verification step into the flow canvas at the appropriate position in the flow.

• Click on Email Verification to open its configuration options:

The Liveness step is designed to verify the presence of a live person during the verification process.

• Add Liveness Check step into the flow canvas at the appropriate position in the flow.

• Click on Liveness Check to open its configuration options:

Manual Review

As a compliance officer, you have the ability to manage the applicant review process effectively. Here's how to manually handle the review process for an applicant:

• After the system assigns a Completed

The Deactivation option is accessible in all verification steps, including Document Check, Liveness, Selfie Capture, Face Match, AML Check, and more. This ensures that reviewers can maintain control all over the entire verification process.

• When a reviewer identifies an issue or disagrees with the results presented by the verification step, they can deactivate the service instantly. This is done by clicking the Deactivate button located at the top right corner of the respective section:

The User Deletion functionality provides you with the ability to remove an applicant’s data from the system.

• To initiate the deletion of an applicant’s profile, the reviewer can select the Delete option from the action menu next to the applicant’s record in the table view:

• Upon selecting Delete

The reporting functionality in our platform allows compliance officers to generate and download comprehensive reports for each applicant. This feature is crucial for record-keeping, auditing, and sharing verification results with relevant stakeholders. The reports are generated directly from the applicant's profile and provide a detailed overview of all verification steps, changes, and media associated with the applicant.

• To generate a report, navigate to the specific applicant's profile within the platform. This profile contains all the verification data and history related to the applicant.

• In the applicant's profile, locate the Download button, which is typically positioned near the top right corner of the interface. Clicking this button will initiate the process of generating and downloading the report:

• The Duplicate option is easily accessible from the workflow management interface:

• In the Duplicate Workflow window, select the status of the duplicate workflow using the toggle switch. You can choose between Test and Live modes:

The Address Verification step allows you to collect a user’s address and automatically check whether it exists using trusted address data sources (e.g., Google data). This step helps validate address accuracy without requiring document uploads or AI-based document analysis unless explicitly enabled.

• Add the Address verification step into the flow canvas at the appropriate position in the flow.

• Click on Address verification to open its configuration options.

Introduction

This section provides descriptions and guidelines for making requests to our Public API. All data transmitted via our Public API is encrypted to ensure security. For more information on encryption and how to handle encrypted data, please visit the

You can find full description of API here []

The Intro step welcomes users, explains the verification process, and provides necessary instructions. It is always positioned at the beginning of the flow and is a vital element for guiding users through the verification journey. It is especially useful when the flow includes multiple steps, ensuring users are well-informed and prepared before they begin.

• Add Intro Screen step into the flow canvas at the appropriate position in the flow.

• Click on Intro Screen to open its configuration option

The Phone Verification results section provides a detailed summary of checks performed on the applicant’s phone number. Each validation point includes a status indicator along with an explanation of the check:

If you disagree with any result, you can choose to deactivate the service for this applicant by moving the data to History.

In this chapter you can find all information about data structure, types and parameters description

The Company Settings section allows compliance officers to manage important company-related information, ensuring accuracy and relevance.

Below is a detailed description of editable and non-editable fields within Company Settings.

Editable Fields

Non-editable Fields

The Flow Builder is a powerful tool that allows you to design verification workflows by arranging and configuring various verification steps. This feature enables you to tailor the verification process to their specific requirements, ensuring compliance and efficiency.

• From the Sidebar Menu, click on Workflows to open the flow builder interface.

• Click on the Add new button, located at the top right of the Flow Builder page:

A user-friendly interface that allows you to build verification flows by simply dragging and dropping different verification steps into place.

On-demand vs Regular Flows

In our Platform's Flow Builder, you can create two types of verification flows: Regular Flows and On-Demand Flows. Each type serves different purposes and is designed to meet specific verification needs.

Regular Flows are designed for recurring or scheduled verifications that follow a predefined workflow. They are ideal for scenarios where verifications need to be conducted regularly, such as onboarding new users, periodic compliance checks, or ongoing account maintenance.

On-Demand Flows are designed for ad-hoc verifications that are initiated manually as needed. They provide flexibility and control for conducting verifications outside of regular schedules or predefined workflows.

Geo Settings

This feature allows administrators to manage user access to the verification flow based on their geographical location or IP address. Users from restricted countries can be automatically excluded from the process, ensuring compliance with regulatory or company-specific policies.

• Navigate to the workflow where you want to implement country-based restrictions. In the settings panel on the left side, you'll see an option labeled Countries

• Click the Add Permitted Countries button to specify the list of countries where users are allowed to proceed with the verification flow. Only users accessing the system from these countries will be able to continue.

• Alternatively, use the Add Exclusion Countries button to block specific countries. Users accessing the platform from these countries will not be allowed to proceed with the verification flow.

Flow Auto-Approval

The Auto-Approval feature in the flow builder allows the system to automatically approve or reject verification steps without manual intervention. This functionality can be enabled by toggling the Auto-Approval switch within the step configuration settings.

Enable Auto-Approval: Toggle the switch labeled Auto-Approval to the on position.

Add Verification Steps

Click on the Add step and from the available step options, choose the verification steps you need into the flow canvas:

Each step in the flow can be customized with specific settings and criteria to match your verification needs.

Description of the steps is provided further.

The Manual AML Scan allows you to perform targeted searches for individuals or organizations to detect potential financial crime risks. The feature is located in the AML Scan section, accessible from the sidebar menu:

How to Perform a Search Request in the AML Scan Feature:

• From the sidebar menu, click on AML Scan and select Search Page.

• At the top of the search form, select whether you want to search for an Individual or an Organization.

• Fill in the Search Fields: Full Name: Enter the full name of the individual or the organization. Search by Name, by Document or by Identity: You can choose whether to search by full name or an alias. Birth Year or Year Range: If applicable, enter the birth year or a range of years for a more specific match. Match Rate: Define the minimum percentage match rate that the search result should meet (e.g., 80%). Only results that meet or exceed this threshold will be returned. Country: Select the country associated with the individual or organization to narrow down the search.

• If you want a more thorough search that checks additional databases, tick the Deep Search checkbox.

• Click the Scan button to start the search request. The system will scan through PEP, Sanctions, Watchlists, and adverse media databases for any potential matches.

• Once the scan is complete, review the results on the same page or on the Scan Results page to assess potential matches and take further action if needed:

The Scan Result provides you with a detailed overview of any matches found during an AML scan. It includes key functionalities for assessing risk, updating case statuses, and enabling ongoing monitoring.

• Match Status can be updated by the user to classify the result:

• You can activate Monitoring Periodicity for a match, ensuring regular updates and alerts for any new information that may arise about the entity:

• Profile Information displays the matched entity’s key details, including: Name: (e.g., ABIGAÏL DAMASANE).

  Match Source: (e.g., OFAC - Specially Designated Nationals - Treasury).

  Match Type: Shows whether the result refers to an Individual or an Organization and its associated list (e.g., Sanction).

• The

• The Scan Results page provides you with a list of all the cases found:

Method 1: No Code - Creating Verification Through Workplace

1. Navigate to the Applicants Page:

   • Go to the "Verification" section and then select "Applicants."

2. Create a New Verification:

   • Fill in the required details:

     • Application: Choose the relevant application.

3. Generate Verification Link:

   • After providing the necessary information, our system will generate a link.

   • Share this link with the user to grant them access to the verification process.

Method 2: Automated - Creating Verification Through SDK

To automate the verification process, you can use our SDK. This method involves generating a token on your backend and initializing the SDK with the token as a parameter.

Steps for Automated Verification

1. Create a Token:

   • Generate a token on your backend. This step should be done securely to ensure the integrity and security of the verification process. More details can find in section

1. :

   • Use the generated token to initialize the SDK.

   • Pass the token as a parameter when setting up the SDK.

Private Application Key

In order to use the public api you will need to obtain a private key.

You can retrieve your Private Application Key from Applications > Private app key.

Create Allpass.ai Account

In order for your application to communicate with Allpass.ai you need to sign up for an account in our workplace. You have to provide some information about yourself and a company.

Once you have registered, our system will automatically create an application and flow for you. This ensures that you can start using our platform immediately without any additional setup. In addition to the default application and flow created for you, you have the flexibility to create new applications and flows or customize the default ones according to your needs.

Integrate the Verification Flow

Depending on your requirements, you can integrate Allpass.ai via our client-side SDK.

The client-side integration process can be summarized in 2 steps:

1. Install and import our client-side SDK in your application

2. Initialize SDK and our users will complete a Verification through the Verification flow - on completion, you need to track the Verification in your dashboard in workplace and handle it accordingly via the callbacks (e.g. onComplete function)

You can find more details in the of our documentation.

Setup Webhooks

if you want to automate the process of KYC Allpass.ai uses webhooks to notify your backend when an event happens in your client-side SDK. Webhooks are useful for asynchronous events like when an applicant completes an Applicant's verification or passes some step. You should specify your backend endpoint url and import public RSA key

You can find more details in the section of our documentation and how to use it in section.

Retrieve Data From the API

For security purposes, we recommend you to minimize the Data points stored on your server. That being said, if you need to retrieve information related to an Applicant you can do so via the Allpass.ai API. You can retrieve the following types of data:

• Data points collected and shared during an Applicant (E.g. first name, last name, document number, identity score)

• Metadata related to the Applicant (i.e. user agent, timestamp, user references)

You can find more details on the endpoints and the response format in the section of our documentation.

The Document Check section within the Applicant Profile provides a detailed view of the applicant’s identification document verification results. This section is crucial for ensuring the authenticity and validity of the applicant's submitted documents. It is also is designed to notify users of any discrepancies or problems that need immediate attention:

Key Warnings

• Document Expiration: At the top of the section, a warning banner clearly states that the document provided has expired. This is a critical alert, as expired documents cannot be considered valid for verification purposes.

• Duplicate Document Warning: The system can also trigger a warning if a duplicate document is detected within the platform. This ensures that no two profiles share the same document, preventing fraud and identity theft. A warning banner will notify the reviewer if a duplicate document is found, prompting further investigation or action.

Document Status

• Valid: at the top of the section, a "Valid" status will be displayed if the document is in order.

• Non-valid: a status signifies that the document fails to meet the required criteria for successful verification.

Data Cross-check

Next to each data field (e.g., Issuing State Code, Document Number, Date of Expiry), there are icons that indicate the results of the cross-checks from various sources (visual zone, MRZ, chip):

• Green Icon: Indicates that the information has been successfully verified across all available sources (visual zone, MRZ, chip) and there is consistency in the data.

• Red Icon: Signifies that the data could not be fully verified or there are discrepancies between the information from different sources.

• Orange Icon: Shows that the cross-check for that particular field was not conducted or is not applicable.

Data Editing

If needed, the user can edit the document data directly within the platform. Each field next to the document information features an edit icon.

By clicking this icon, the reviewer can manually adjust the data, ensuring that any necessary corrections are made before final approval. This feature is especially useful if minor discrepancies or typographical errors are identified during the review process.

Data Fields

For a detailed explanation of each data field, including the document class code, issuing state code, and personal number, please follwo a dedicated .

This step compares the user’s face across multiple sources to verify their identity. It is crucial for preventing identity fraud and ensuring the integrity of the verification process.

• Add Face Matching step into the flow canvas at the appropriate position in the flow.

• Click on Face Matching to open its configuration options:

There are two ways to run verification flows on our Platform: integrating the flow into your application using API webhooks and manually generating a verification link in the workplace. Here's how each method works:

Integrate the Flow into Your Application This method allows you to seamlessly verify user identities as part of your onboarding or compliance process using API webhooks. It's ideal for verifying your entire user base.

• Log in to your account on the

Notifications on our platform keep you informed about critical events, updates, and actions related to applicants' verificaiton flows. By configuring notification settings, you can ensure the right individuals or groups stay informed at the right time.

Notification Setup Options

Verification statuses help track the progress and outcomes of each verification process, providing clear indicators of where each applicant stands in the verification journey.

Here’s a detailed description of all the verification statuses:

This step enables users to upload and verify identity documents as part of the verification process. It ensures that only valid and compliant documents are accepted, providing a secure and efficient method for identity verification.

• Add Document Check step into the flow canvas at the appropriate position in the flow.

• Click on Document Check to open its configuration options:

Overview

• From the Sidebar Menuclick on Verifications and go to Applicants tab:

Web browser data collection

This glossary offers clear and concise definitions for each term, ensuring that developers, data analysts, and privacy compliance officers can confidently navigate the intricacies of user data from the browser.

SDK Version: SDK stands for Software Development Kit. This term refers to the version of the software toolkit or package used to integrate certain features or functions into an application, typically related to data collection and analysis.

Verification Step Opened but Not Finished

Issue: The verification process was started, but the system did not receive the necessary data.

Getting started

Allpass.ai uses webhooks to notify your backend when an event happens in your client-side SDK. Webhooks are useful for asynchronous events like when an applicant completes a Verification or passes any step. You should specify your backend endpoint URL and get your Encryption Keys.

You can do it within the workplace

This document explains how to integrate the verification flow directly into your web application through our JavaScript component to verify the identity of your users. This stage might be at the signup page of your application, or at a later point to enrich the profiles of your users. The guide assumes the preliminary steps have already been completed as explained in the overview section of the documentation.

You can either follow the integration guide or watch the integration tutorial that shows the same steps. Please be aware that some property or function names might have slightly changed with newer versions. Make sure to compare your implementation with the latest code snippets here in the documentation.

Features

• Read passport data using a smartphone or webcam

• Doc type identification (Machine Learning)

• Parsing doc data (OCR)

Compatibility

This section is a critical component of the platform, providing results that indicate whether an individual has been flagged in any sanction or watchlist databases.

• The top part of the section displays a warning banner, indicating in case the individual has been flagged in one or more databases:

• Below the warning, the details of the match are displayed.

• When conducting AML (Anti-Money Laundering) searches, the results may include various tags that help categorize and identify the nature of the matched entities. These tags fall under two main categories: Record Types and List Types. Below is a detailed explanation of each tag to help you interpret the search results effectively:

• At the bottom of the section, a comments area allows reviewers to add notes or observations related to the AML check. This is useful for documenting reasons behind the selected match status or any other relevant details.

• By clicking on the individual's name or the match percentage, the reviewer can open a detailed profile view of the flagged individual:

• To the right of the match details, a dropdown menu allows the reviewer to categorize the match further:

The available options include:

• Unknown: The match status is not yet determined.

• No Match: The reviewer determines that there is no match.

• Potential Match: The system has flagged a potential match, which is the current selection in the screenshot.

For detailed information about the data sources used in Sanctions and PEP checks, please refer to the page.

How to Use Crypto Wallet and Transaction Check Block

1. Accessing the Applicant’s Page

   • Navigate to the Applicant's page to find the Transaction Monitoring block.

   • This block displays wallet addresses or transaction IDs linked to the applicant, along with their corresponding risk scores and monitoring statuses:

1. Accessing Wallet and Transaction Details

• Click on the wallet or transaction ID in the Transaction Monitoring block to view detailed insights.

• This will open a comprehensive view of blockchain activity, including transaction history, risk factors, and flagged compliance issues:

1. Interpreting Report Details The transaction monitoring report provides comprehensive insights into the sources and uses of funds associated with a monitored crypto wallet. Here's how to interpret key sections of the report:

• Risk scores displayed next to the wallet or transaction ID help gauge the likelihood of suspicious activity:

  • Low Scores: 0-30

  • Medium Scores: 31-69

• The Risk Exposure section provides an overview of the risk profile associated with the monitored wallet and its transactions. It breaks down risks into specific categories to help you quickly identify areas of concern related to fund sources, fund usage, and overall transaction behavior:

• Source of Funds section analyzes the origins of the funds received by the monitored wallet. It identifies the risk levels and potential issues linked to where the funds came from. The source of funds allows users to identify potentially risky inflows, such as funds from high-risk or hacked wallets. Clicking on an entity (e.g., Root Tx or Leaf Tx) will open the corresponding details on a separate page for further analysis.

• Use of Funds provides an analysis of how funds leaving the wallet are being used, helping to determine if the transactions align with legitimate activity. It helps to determine if the wallet's activity includes potentially suspicious transfers, such as sending funds to unknown or high-risk entities. Similar to the source section, users can click on the listed entities to access additional details on a separate page.

• Every Entity listed in the report is clickable. Clicking on a name redirects you to a dedicated Entity Details page, where you can view a deeper analysis, and associated blockchain data:

1. Taking Actions

• Use the Deactivate button to move resolved or unnecessary cases to history and stop monitoring.

• Toggle the Monitoring option ON or OFF to enable or disable ongoing observation of a specific wallet or transaction:

You can also take specific actions from the detailed view page:

• Add to Monitoring Use the Add to Monitoring button to include the wallet address in active monitoring. This ensures that any future transactions or changes related to the wallet are tracked for compliance and risk management purposes

• Exporting Data Use the Download button in the top-right corner to generate a report of transaction details and compliance findings for recordkeeping or regulatory submission.

On the Info tab of the verification dashboard, you can see the user's IP address and device information in the Device Info section:

Key elements displayed include:

• IP Address: The user's public IP address.

• Geolocation Data: A mapped location of the user's IP (e.g., city, region, and country).

• Device Details: Information about the user's browser, operating system, and device type.

Clicking on the IP address or the More link will open a detailed view of the IP properties, geolocation data, and provider details:

The detailed view provides in-depth insights into the user's IP address:

How to Use This Information

• Identify Suspicious Activity: Check for IP addresses flagged as "hosting," "VPN," or "proxy" to detect potential anonymity tools or high-risk behavior.

• Verify User Location: Cross-reference the user's declared location with the geolocation data to ensure consistency.

• Assess Risk Levels: Analyze whether the IP address belongs to a residential ISP or hosting service, as hosted IPs might indicate bot or server activity.

This functionality operates in the background, requiring no user action, and provides a robust layer of security for identity verification processes.

The Dashboard provides a comprehensive view of key metrics, enabling users to monitor applicant progress, verification statuses, and system performance across various dimensions. The dashboard is divided into distinct sections, each designed to offer a quick glance into the platform’s core activities and health.

Key Metrics (Top Bar)

The top section of the dashboard highlights six key application statuses within a selected date range (e.g., Today, Last 7 Days, Last 28 Days):

• Applicants Number: The total count of applicants created.

• Applications in Review: The number of applications currently undergoing verification.

• Applications Completed: The count of fully completed applications.

• Applicants Approved: The number of applications that have been successfully approved.

• Applicants Rejected: The count of applications that were rejected.

The user can filter the data by selecting a specific date range, which will automatically update all displayed information.

Graph: Number of Applicants Created Per Date

This graph displays the daily count of applicants created within the chosen time frame, allowing users to track activity trends, such as peaks and troughs in applicant submissions over time.

Applicant Status Overview

This bar chart shows a breakdown of applicant status across categories:

• Completed: Applicants whose verification process is finished.

• In Progress: Applicants whose verification is ongoing.

• Incomplete: Applicants with incomplete submissions.

Total Applicant Warnings

This donut chart presents the total number of warnings triggered across all applicants:

• Unresolved: Warnings that are yet to be addressed.

• Resolved: Warnings that have been reviewed and cleared.

Applicants Distribution by Country / Phone Number Origin / Document Origin

This section features a world map highlighting the geographical distribution of applicants based on their country of residence, phone number or document origin. A list on the right shows the top countries with the highest number of applicants, such as Ukraine, Spain, and the United Kingdom, for instance.

Verification Overview

This line chart displays the number of verifications conducted within the selected date range, distinguishing between:

• Successful Verifications: Completed successfully.

• Failed Verifications: Those that did not meet the verification criteria or encountered technical issues during the process.

Failed Verification Stages Overview

This chart illustrates at which stage the verification process failed. It helps users identify common failure points and take corrective action to improve the verification process.

Performance Comparisons

There are three performance charts that provide a comparative analysis:

• Successful Verifications Number Compared by Date Range: This line chart compares the number of successful verifications with the target, showing how close or far it is from reaching the goal.

• Total Verifications Compared by Average Number: Shows how the total number of verifications compares to the platform’s average over a specific period, highlighting if it is above or below target.

• Successful Verifications Number Compared with Failed: This line chart contrasts successful and failed verifications, helping users monitor the success rate.

Successful Services Breakdown

A pie chart provides an overview of the success rate across various verification services:

• Liveness: The percentage of successful liveness checks.

• Questionnaire Results: Successful completion of questionnaires.

• OTP Verification: Verification through one-time passwords.

If your IP address is being flagged as a VPN while trying to access certain services, there are a few potential reasons for this behavior. Below is a description of common causes along with solutions for each.

VPN Service is Enabled

• If you have an active VPN service running on your device, it will route your traffic through a virtual private server, causing your IP to be identified as a VPN.

Solution: Check if a VPN Service is Active

• Ensure that no VPN app or service is currently enabled on your device:

  • For iOS: Go to Settings > VPN, and toggle it Off.

  • For Android: Go to Settings > Network & Internet > VPN, and disconnect any active VPN.

  • For Windows: Go to Settings > Network & Internet > VPN, and disconnect any VPN connections.

Shared IP Addresses by ISPs

• Some Internet Service Providers (ISPs) assign shared or dynamic IP addresses. If the IP address you are assigned has previously been associated with VPN services or flagged by websites, it might be detected as a VPN.

Solution: Request a New IP Address

• Restart your modem or router to acquire a new IP address from your ISP. This process can resolve issues related to flagged IP addresses.

Private Relay or Limit IP Address Tracking (iOS devices)

• On iOS devices, when the "Limit IP Address Tracking" feature is enabled, your device hides your real IP address by using a private or proxy-like address. This can sometimes cause certain systems to identify your IP as a VPN.

Solution: Check "Limit IP Address Tracking" on iOS Devices

• If you are using an iPhone or iPad, the "Limit IP Address Tracking" feature may be causing the issue. Follow the steps below to disable it:

  • Open the Settings app.

  • Tap on Wi-Fi.

Use of Public Wi-Fi

• Public Wi-Fi networks often use shared network configurations that can appear similar to VPN traffic.

Solution: Avoid Public Wi-Fi

• Switch to a private Wi-Fi network if possible. Public Wi-Fi often uses shared IPs that may trigger VPN-like detection.

Proxy Settings on Your Device

• Your device may have a proxy configured, either manually or automatically, which could lead to its detection as a VPN.

Check Proxy Settings

• On your device, ensure that no proxy settings are enabled:

  • For iOS: Go to Settings > Wi-Fi > [Your Network] > Configure Proxy, and ensure it is set to "Off."

  • For Android: Go to Settings > Network & Internet > Wi-Fi > [Your Network] > Advanced > Proxy, and ensure it is set to None.

Use of Privacy Tools

• Privacy-focused tools such as DNS-over-HTTPS (DoH) or private DNS settings can be misinterpreted as VPN behavior.

Solution: Disable Privacy Tools Temporarily

• If you are using privacy tools such as private DNS or DNS-over-HTTPS, try disabling them temporarily to see if it resolves the issue.

• You can create new and manage existing applications through the Applications section in Workplace:

• As soon as your application is created you can open it anytime and get the details required for further integration.

The Questionnaire Builder is a powerful tool designed for compliance officers to create custom user surveys and integrate them into the user verification workflow. This functionality enhances the compliance process by allowing the collection of specific information tailored to the organization's needs.

• From the Sidebar Menu, click on Questionnaire to open the flow builder interface. The interface displays all existing questionnaires and provides options to create new ones.

• Users can search for existing questionnaires by name and manage them efficiently.

Place the new HTML element where you want the component to render inside the body of your HTML file:

In order for the verification flow to render correctly, you'll need to pass a valid accessToken as an argument to the start function. You can get accessToken from our public API. You can find more details in the section of our documentation.

You can pass in different handler functions like the onLoad, onStart, onRestart, onPassStep, onComplete or onError method to handle different events of the verification flow to the init function.