browse

KYC Certificate Results

Identity document Authenticity verification

Blockpass verifies identity documents through a structured three-step process.
First, users capture a live image of their identity document. The system then employs an advanced Optical Character Recognition (OCR) engine to automatically extract key information, including the Given Name, Family Name, and Date of Birth, while validating the document against official government templates. The OCR also performs a security check on the machine-readable zone (MRZ) to confirm authenticity. In the final step, the document image is analyzed for potential signs of tampering, forgery, or other irregularities.

Results Summary:

1. CLEAR: This outcome signifies a successful extraction of data from the ID document. It indicates that the system was able to accurately identify and retrieve the required information — such as the Given Name, Family Name, and Date of Birth — from the submitted image. The document photo is clear, well-lit, and aligns with the formatting standards defined for government-issued identification.

Additionally, this result confirms that the document has not been flagged in any lost, stolen, or compromised records and that the extracted data can be confidently used to proceed with further verification checks within the Blockpass system.

2. CONSIDER: This result indicates issues with the submitted document that prevent complete verification. The image may be of insufficient quality, causing incomplete or inaccurate data extraction (e.g., Given Name: N/A). Other possible factors include scans or photos of a National ID Document displayed on a monitor, expired identification documents, or irregularities suggesting potential 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 verification assesses the authenticity, completeness, and consistency of the submitted proof of address document. Multiple attributes are evaluated to ensure the accuracy and reliability of the provided information.

The Proof of Address (POA) Certificate v6 evaluates the following categories:

  1. Document

    • Accepted Type: Determines whether the submitted document type is accepted for proof of address verification.

    • Authenticity: Evaluates the document’s integrity and overall quality.

    • Issuer Reputation: Assesses the reliability of the document’s issuing entity.

  2. Data Presence

    • Checks the visibility of key data fields such as Full Name, Address, Country, and Issue Date.

  3. Data Comparison

    • Compares extracted document data with the user’s submitted information, including Full Name, Address, Country, Issue Date, and Document Type, to ensure consistency.

  4. Data Validation

    • Confirms data accuracy and validity by verifying Full Name, Address, Country, Issue Date Within Period, and Country of IP, ensuring alignment with Blockpass standards for proof of address verification.

Results Summary:

    1. CLEAR: The document meets verification requirements, demonstrating acceptable authenticity, issuer reputation, complete data presence, and consistent validation results.

    2. CONSIDER: One or more attributes require further review (Consider status) — for example, a non-standard document type, incomplete or mismatched data, a lower authenticity score, or discrepancies between the IP country and the declared address.

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: Verified Result = 1. The signature matches the connected wallet address, confirming the user’s ownership of the wallet. The verification was automatically assessed and approved by the system with no irregularities detected.

2. CONSIDER: Verified Result = 0. The signature does not match the connected wallet address, so ownership cannot be confirmed. Users are advised to reconnect their wallet, follow the correct signing process, and resubmit their verification request.

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 >=40 indicates a low risk, confirming the wallet's legitimacy.

2. CONSIDER: A score of <40 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.

Certificate Expiration

Every certificate issued by Blockpass has an expiration date: 

Certificate Expiration Date
Identity Document Authentication The same day as the expiration date of the submitted Identity Document itself. 
For IDs with no expiration date; the certificate will have a 90-day expiration term.
Face Match

90 days from the certificate date of issue

Sanction List and PEP (AML)

3652 days from the certificate date of issue

Proof of address (POA)

90 days from the POA Document date of issue (not from the certificate date of issue)

Crypto Address (Unhosted Wallet KYC)

7 days from the certificate date of issue

Crypto AML

30 days from the certificate date of issue

* The "certificate date of issue" is when a profile is submitted and Blockpass verifies its information. 

Screenshot 2024-05-08 at 14.10.53.png

Certificates will also expire under the following circumstances:

  • Any data associated with a certificate changes, leading to re-verification and the issuance of a new certificate. In such cases, the certificate date of issue is updated to reflect the issuance date of the new certificate, while the dates of other certificates remain unchanged.

If a user has already been approved and their certificate expires, their application status will continue to display as "APPROVED."

What to do when you encounter an expired certificate:

This depends on the requirements and internal procedures of your business. 

  • If you don’t need to update the information about the user and the user has already been on-boarded by you, you can simply ignore this notification.
  • If you want to receive a new document and a new certificate you can REQUEST A REVIEW to ask users to update their profile and resubmit to your service:
    • The user will be prompted to submit a new document.
    • Upon submission of a new document, the user will be forced to verify their new document first.
    • Due to the new verification, the user’s status will turn to “INCOMPLETE”.
    • Once the document is Verified you will see the new document along with the new certificate in the dashboard, and the status of the application will show as “WAITING FOR REVIEW”.
    • You will receive a notification when the user's information is updated.
Previous
Next
360022656353

Comments

0 comments

Article is closed for comments.

Was this article helpful?

1 out of 8 found this helpful
Powered by Zendesk