browse

 Identity document Authenticity verification

When verifying identity documents, Blockpass employs a meticulous three-step process. Initially, users are required to capture a live image of their document. Subsequently, Blockpass utilizes a sophisticated Optical Character Recognition (OCR) engine to authenticate the document and ensure its alignment with government templates. Additionally, the OCR conducts a security assessment of the document's machine-readable zone. The third layer involves scrutinizing the document image for potential signs of tampering or alterations.

Results Summary:

1. CLEAR: This outcome signifies a successful match between the user's data and the submitted document. The image is clear, and there are no reports of the user's documents being lost, stolen, or compromised.

2. CONSIDER: This result indicates issues with the submitted document, such as inadequate picture quality, discrepancies between the app data and document information, scans or pictures of the National ID Document monitor, expired identity documents, or other irregularities hinting at possible document compromise.

 

Sanction lists and PEP certificate

For customers opting for the Plus or Enterprise Plan with AML check, Blockpass scans Sanctions lists, Politically Exposed Person (PEP) records, and Adverse Media data. 

Results Summary:

1. Name not found in Sanctions and PEP List: This outcome confirms that the user's full name is absent from sanction lists, PEP records, or adverse media databases.

2. Potential match found in Sanctions and PEP List: This result suggests that the user's name or a similar one appears in either Sanctions lists, Adverse Media, or the Politically Exposed Person list.

Face Match certificate

  • To verify facial identity, users must provide live selfie images from three different angles, which are then compared against the photo in the identity document.

    Results Summary:

    1. CLEAR: The provided selfie accurately matches the picture on the identity document.

    2. CONSIDER: Issues arise if the submitted selfie is problematic, such as not being the same person when compared to the photo on the ID, or a poor-quality image.

Proof of Address Verification

This process involves comparing data, including the user's name, residential address, proof of address issue date, and IP location.

Results Summary:

1. CLEAR: The user's information and the submitted document's data align, and the IP location matches the user's residential country.

2. CONSIDER: Issues arise if there are disparities between the user's information and the submitted document's data, and/or if the IP location differs from the user's residential country.

 

Crypto Address Certificate (Unhosted Wallet KYC)

Users must connect their wallet to confirm ownership. Blockpass verifies the correctness of the provided signature.

Results Summary:

1. CLEAR: The input signature hash is correct, validating the user's ownership of the wallet.

2. CONSIDER: The input signature hash is incorrect, leading to rejection. Users can rectify this by reconnecting their wallet and resubmitting.

 

Crypto AML Certificate

This assessment gauges the risk associated with the user's submitted wallet, determining if it is linked to illicit activities such as dark market dealings, gambling, client deposits, or large transactions over 10k.

Results Summary:

Blockpass returns a score range from 0 to 100, with 0 being the highest risk and 100 being the lowest risk.

1. CLEAR: A score of >=60 indicates a low risk, confirming the wallet's legitimacy.

2. CONSIDER: A score of <60 raises concerns, necessitating further scrutiny due to potential risks associated with the wallet's activities.

 

Blockpass offers a comprehensive verification process encompassing document authenticity, sanction lists, facial recognition, proof of address, and crypto-related certificates. Users get approval when all criteria are met, ensuring a secure and reliable verification experience.

Previous
Next
360022656353

Comments

0 comments

Article is closed for comments.

Was this article helpful?

1 out of 5 found this helpful
Powered by Zendesk