KYC (Know Your Customer) verification is a regulatory requirement that establishes trust between financial institutions and their customers. It is mandatory for all institutions, and related processes must adhere to a customer identification program (CIP). Without KYC, banks' assets, including those of their valued customers, remain exposed to risk. Instnt streamlines the identity document verification process during sign-up to detect fraud, using automated screening to convert more new users into authenticated account holders.
How To Enable KYC Verification
By default, the Instnt dashboard activates the Know Your Customer (KYC) verification feature when creating a workflow. We recommend keeping this setting as it is to allow Instnt to handle the KYC compliance verification checks. The feature functions seamlessly within your workflow, requiring no integration changes. Our streamlined process, powered by AI-based anti-fraud technology, helps customers complete KYC requirements swiftly.
For KYC, both the National ID (SSN) and Date of Birth are required for the US, but for Canada, only Date of Birth is required. Some of these features have dependencies on the rule selection, and the feature-field relations are detailed in the Fields Dictionary. This rule may vary for the US and Canada. For more information on creating a workflow, please refer to the Quick Start Guide.
How It Works
KYC (Know Your Customer) verification feature is a sophisticated process designed to verify the identities of new customers, simplifying the onboarding process for institutions while ensuring a secure identity verification process. You can tailor your identity verification infrastructure to align with the compliance requirements of your business. Learn more about Instnt Field Selector.
This feature encompasses fully automated document verification, liveness authentication for authenticating ID documents, biometric authentication using facial liveness, and sanctions compliance screening solutions to expedite critical screening workflows. It complies with SOC 2, privacy regulations, and various stringent security measures.
Reason Codes in KYC Decisioning
Instnt’s KYC decision process involves several scenarios that result in different outcomes. The KYC decision is represented by reason codes, providing transparency and insight into the factors influencing the outcome. These scenarios include:
- Scenario 1: PII requirements met, verification successful, no watchlist matches - KYC Accept
- Reason Codes Returned:
- KYC100: KYC Accept
- KYC103: Required PII for KYC is provided
- KYC105: Required PII for KYC is verified
- FinTrac KYC114: Sufficient reliable sources found to verify the customer
- KYC107 (Optional): No matches on sanctions, PEP, or adverse media lists
- Reason Codes Returned:
- Scenario 2: At most 2 PII cannot be verified - KYC Review
- Reason Codes Returned:
- KYC101: KYC Review
- KYC103: Required PII for KYC is provided
- KYC106: Required PII for KYC cannot be fully verified
- Reason Codes Returned:
- Scenario 3: All PII verified, watchlist match - KYC Review
- Reason Codes Returned:
- KYC101: KYC Review
- KYC103: Required PII for KYC is provided
- KYC105: Required PII for KYC is verified
- FinTrac KYC114: Sufficient reliable sources found to verify the customer
- KYC108 (Optional): Name match on sanctions lists
- KYC113 (Optional): Name and year of birth match on adverse media lists
- Reason Codes Returned:
For a more comprehensive understanding of these reason codes and their significance, please refer to the Reason Code Glossary, which offers a detailed explanation of the various codes and their implications.