Available Business Rules

Our system applies various business rules to determine the legitimacy and validity of the collected data. Each rule is tailored to specific attributes and criteria, ensuring a comprehensive and accurate verification process.

📘

Currently, none of the business rules are pre-configured in our journeys. To configure any business rules with your journey reach out to your account manager.

Currently, we support the following business rules:

Ownership Check

This check allows businesses to verify a user's identity using a primary identifier (e.g., Aadhaar) to ensure that the data on the provided document matches the user's data on the reference document. We can also match the user-entered data with the data provided by the business to verify whether it's the same user. The data from both sources are fuzzy-matched, with a configurable threshold range from 0 to 100.

This check could be configured with the following journeys

• PAN
• VoterID
• Driving Licence
• Aadhaar
• Bank Account
• Vehicle RC
• CIBIL Credit Report
• Equifax Credit Report
• Employment History
• Bank Statement
• PF Passbook
• ITR
• Payslip

{
  "check_id": "ownership_check",
  "check_result": "PASS|FAIL",
  "status_code": "Visit the link below",
  "metadata": {
    "data_source": "<OTHER_KEY_NAME>|<BUSINESS_PROVIDED>",
    "match_logic": ""
  }
}

Status Codes for Ownership Check.

DOB Range Match Check

This check can be configured with Aadhaar Demographic API to validate the DOB declared with the age band obtained from the UIDAI.

The following verification journeys could be configured with DOB Range Match Check

1. Aadhaar Demographic

{
  "message": "Check successful",
  "check_id": "DOB_VALIDATION_CHECK",
  "check_result": "PASS",
  "status_code": "SUCCESS|DOB_OUT_OF_RANGE",
  "metadata": {}
}

Document Readability Check

This check can be configured with the OCR verification process to assess the readability of the document. The document is evaluated based on the following parameters:

1. Blurriness
2. Brightness
3. Confidence Score

{
  "check_id": "document_readibility_check",
  "check_result": "PASS|FAIL",
  "status_code": "Visit the link below",
  "metadata": {
    "data_source": "<OTHER_KEY_NAME>|<BUSINESS_PROVIDED>",
    "match_logic": ""
  }
}

Status Codes for Document Readability Check.

Aadhaar UIDAI Validation Check

This check could be configured with Aadhaar OCR verification journey. It enables the OCR extracted Aadhaar data to be validated with the data from UIDAI.

{
  "check_id": "aadhaar_validation_check",
  "check_result": "PASS|FAIL",
  "status_code": "Visit the link below",
  "status_message": "",
  "metadata": {}
}

Status Codes for Aadhaar UIDAI Validation Check.

Document Tampering Check

This check could be configured with the OCR verification journeys. It enables the submitted documents to be analysed for any alterations or modifications, ensuring that the documents are authentic and have not been tampered with.

{
  "check_id": "document_tampering_check",
  "check_result": "PASS|FAIL",
  "status_code": "Visit the link below",
  "status_message": "",
  "metadata": {}
}

Status Codes for Document Tampering Check.

Photocopy Check

This check could be configured with the OCR verification journeys. It enables businesses to identify if the submitted documents are photocopies rather than original documents, ensuring the authenticity and originality of the documents provided.

{
  "check_id": "isphotocopy_check",
  "check_result": "PASS|FAIL",
  "status_code": "Visit the link below",
  "status_message": "",
  "metadata": {}
}

Status Codes for Photocopy Check.

At Source Verification Check

This check could be configured with the OCR verification journeys. It enables the data extracted from OCR images to be cross-checked with the data present at the source of truth, ensuring the accuracy and validity of the submitted information.

{
  "check_id": "at_source_verification",
  "check_result": "PASS|FAIL",
  "status_code": "Visit the link below",
  "status_message": "",
  "metadata": {}
}

Status Codes for At Source Verification Check.

Duplicate User Check

This check can be configured with Voter ID, Driving License, and PAN. It enables businesses to verify if the user is attempting to use the same document with different account identifiers.

{
  "check_id": "duplicate_check",
  "check_result": "PASS|FAIL",
  "status_code": "Visit the link below",
  "status_message":"",
  "metadata": {}
}

Status Codes for Duplicate User Check.

Payslip Validation Check

This check can be configured with the payslip verification process. It enables businesses to verify the salary credit history by ensuring that the salary details mentioned in the payslip match those listed in the bank account statement.

The businesses can configure the following attributes:

1. Company Name
2. Salary credited
3. Date of credit

{
  "check_id": "payslip_validation_check",
  "check_result": "PASS|FAIL",
  "status_code": "Visit the link below",
  "status_message":"",
  "metadata": {}
}

Status Codes for Payslip Validation Check.

Background Verification Check

This check can be configured with the Education Verification Journey or the Employment Verification Journey. It enables businesses to verify the legibility of the employment/education history provided by the user.

{
  "check_id": "background_verification_check",
  "check_result": "PASS|FAIL",
  "status_code": "Visit the link below",
  "status_message":"",
  "metadata": {}
}

Status Codes for Background Verification Check.

Criminal Records Check

This check can be configured within the Legal Records Verification process. It enables businesses to verify users based on their past or present criminal case records. For example, a company may use this check to verify an employee before onboarding, allowing only those with no present criminal cases to proceed.

{
  "check_id": "criminal_records_check",
  "check_result": "PASS|FAIL",
  "status_code": "Visit the link below",
  "status_message":"",
  "metadata": {}
}

Status Codes for Legal Records Check.

Civil Records Check

This check can be configured within the Legal Records Verification process. It enables businesses to verify users based on their past or present civil case records. For example, a company may use this check to verify an employee before onboarding, allowing only those with no present civil cases to proceed.

{
  "check_id": "criminal_records_check",
  "check_result": "PASS|FAIL",
  "status_code": "Visit the link below",
  "status_message":"",
  "metadata": {}
}

Status Codes for Legal Records Check.

Past Credit Enquiries Check

This check enables businesses to verify if the number of credit inquiries made by a user in the past year exceeds the business's accepted threshold, which defaults to 0 unless otherwise configured. If the number of inquiries surpasses this threshold, the user is flagged as having more credit inquiries than allowed. For example, if a user made 5 inquiries and the threshold is 3, the user would be flagged accordingly.

This check could be configured with the following keys:

• Experian
• CIBIL

{
  "check_id": "past_credit_enquiries_1_year",
  "check_result": "PASS|FAIL",
  "status_code": "Visit the link below",
  "status_message":"",
  "metadata": {}
}

Status Codes for Past Credit Inquiries Check.

Active Credit Accounts Check

This check enables the businesses to verify if the number of active credit accounts a user holds exceeds the business's accepted threshold, which defaults to 0 unless otherwise configured. If the number of active accounts surpasses this threshold, the user is flagged as having more active credit accounts than allowed. For example, if a user has 7 active accounts and the threshold is 5, the user would be flagged accordingly.

This check could be configured with the following keys:

• Experian
• CIBIL

{
  "check_id": "active_credit_accounts",
  "check_result": "PASS|FAIL",
  "status_code": "Visit the link below",
  "status_message":"",
  "metadata": {}
}

Status Codes for Active Credit Accounts Check.