KYC
This topic describes Rebilly Know your Customer (KYC) features.
KYC and AML features are available as add-ons to your Rebilly account. To activate, contact Rebilly. The KYC and AML features may be used together or separately.
Use Know your Customer (KYC) features to ensure that your customers and leads are who they claim to be. Depending on your industry, KYC checks may be a mandatory requirement. KYC helps you to minimize risk.
To complete the KYC process, the customer, or lead must supply documents that prove their identity and address. These documents can be requested using a link you share with the customer, or uploaded manually on their behalf. Uploaded documents are automatically analyzed by Rebilly, and are added for review, so that you can manually verify or review the check if needed.
How KYC works
This process describes how to use KYC to request and review documents from your customers.
- Configure KYC document thresholds and weights settings for the automated document verification process.
- Select from the following:
- Create an automated KYC document request — specify that new customers must complete a KYC document request before they can make a payment. The customer is redirected to the KYC document gatherer application where they can upload or add pictures of the requested documents.
- Create a KYC document request — specify the document types to request from the customer, and set the number of allowed failed upload attempts for each document type. Select from the following:
- Share the generated link for the KYC document request with the customer.
When the customer opens the link they are redirected to the KYC document gatherer application where they can upload or add pictures of the requested documents. For more information, see KYC document gatherer. - Upload the documents on behalf of the customer.
When you generate the KYC document request, you can choose to upload the documents on behalf of the customer. This is useful if the customer is unable to upload the documents themselves.
- Share the generated link for the KYC document request with the customer.
- Based on your configured thresholds and weights, Rebilly automatically analyzes the uploaded documents and assigns a score based on the verification checks.
- Manually review the KYC documents. Approve or reject the KYC documents based on the automated analysis results.
Features
This section describes KYC features and how to use them.
Create an automated KYC document request
This process describes how to create an automated KYC document request that triggers before or after a transaction is processed. When the event is triggered, the customer is redirected to the KYC document gatherer application where they can upload or add pictures of the requested documents.
Create a rule
- In the left navigation bar, press Automations .
- In the Rules engine section, press Rules engine.
- Press Core events, then press the Gateway account request event.
- Press Ruleset, then in the top right of the screen, press Create rule.
- In the Rule name field, enter unique name to help differentiate between multiple rules.
- Optionally, in the Labels field, enter a label to help categorize the rule.
- Optionally, in the Conditions section, to specify conditions that determine when this rule is triggered, clear the No conditions checkbox, and specify the conditions.
- In the Actions section, press Add new action.
- In the dropdown, select Request KYC.
Specify the KYC document types to request from the customer
- In the Document type dropdown, select a document type to request from the customer. For information on available document types, see Types of KYC documents.
- Depending on the document type, you can specify allowed document subtypes.
- In the Maximum verification attempts per transaction field, enter the number of allowed failed upload attempts for the document type.
- Optionally, to require the customer to take a "selfie" during the document upload process, select the Request selfie checkbox. For more information, see Facial recognition identity verification.
- To add another document type to the request, press Add document type.
Specify KYC document request settings
- To exclude customers based on the previous submission of KYC documents, in the Exclude from customers section, select one of the following:
- Customers with accepted KYC documents: Exclude customers who have already submitted KYC documents that have been accepted.
- Customers who submitted KYC documents of any status: Exclude customers who have already submitted KYC documents of any status.
- No exclusions: Include all customers regardless of their previous KYC document submissions.
- To specify whether the customer must complete the KYC document request, or if it can be skipped, select one of the following:
- Mandatory: Require the customer to complete the KYC document request before the payment.
- Optional: Allow the customer to skip the KYC document request.
- To specify when the KYC request is displayed to the customer, select one of the following:
- Before processing the transaction: Display the KYC request to the customer before they make a payment.
- After processing the transaction: Display the KYC request to the customer after they make a payment.
- To specify what to do if the customer's KYC documents were requested before the transaction is processed, select one of the following:
- Continue processing the transaction: Continue processing the transaction.
- Decline the transaction: Decline the transaction.
- Use a different gateway account and continue processing the transaction: Use a different gateway account to process the transaction. If you select this option, specify the gateway account to use.
- If the KYC document request is set as optional, to configure how the link to skip the request is displayed, select one of the following:
- Display a bypass link to continue processing the transaction on the selected gateway account: Display a link that the customer can press to skip the KYC document request and continue processing the transaction on the selected gateway account.
- Display a bypass link to change the gateway account and continue processing the transaction: Display a link that the customer can press to skip the KYC document request and change the gateway account to continue processing the transaction. If you select this option, specify the gateway account to use.
- In the Document verification level section, select from the following:
- Strict: Strict verification requirements. Use this option for requests that relate to credit transactions.
- Moderate: Moderate verification requirements. Use this option for requests that relate to sale transactions.
- Basic: Basic verification requirements. Use this option for KYC requests that do not require a high level of verification.
- In the bottom right of the screen, press Save rule.
- To exclude customers based on the previous submission of KYC documents, in the Exclude from customers section, select one of the following:
Request KYC documents
To request KYC documents from your customer, see Request KYC documents.
To preview the end-customer experience uploading KYC documents, see KYC document gatherer. This form is localized and translated into 14 languages. The customer will receive further instructions if they attempt to upload an invalid image, such as a selfie or blurry ID.
Upload KYC documents
To upload KYC documents on behalf your customer, see Upload KYC documents.
Review KYC documents
To review and manage KYC documents, see Manage KYC.
Automated KYC document analysis
The following checks occur automatically when identity and address KYC documents are provided, and require no interaction from you or your customer. To configure or adjust KYC document threshold and weight options for each check, see KYC settings.
Document verification levels
When you manually create a KYC document request or create an automated KYC document request, you can specify the document verification or match level. The document verification level determines the level of verification required for the KYC documents.
The following table describes the document verification levels:
| Level | Description |
|---|---|
| Strict | Use this option for requests that relate to credit transactions. |
| Moderate | Use this option for requests that relate to sale transactions. |
| Basic | Use this option for KYC requests that do not require a high level of verification. |
To view document verification levels in data tables, see View KYC document verification levels.
For more information, see:
Identity document checks
KYC identity document verification scores are defined based on the following automated checks. This process happens automatically and requires no interaction from you or your customer.
To configure or adjust KYC document threshold and weight options for each check, see Configure identity document verification scores.
| Name | Description |
|---|---|
| Is identity document | Verifies that the proof document is an identity document. |
| Is published online | Verifies that the proof document is found to be published online. |
| Is tampered | Verifies that the proof document has been tampered with. For example, if the document was altered using an application such as Photoshop. |
| First name | Verifies the customer's first name. |
| Last name | Verifies the customer's last name. |
| Date of birth | Verifies the customer's date of birth. |
| Has minimal age | Verifies that the customer is older than the minimal required age. |
| Issue date | Verifies that the proof document contains a valid issue date. |
| Expiration date | Verifies that the proof document contains a valid expiration date. |
| Contains image | Verifies that the proof document contains an image. |
| Has matching face proof | Verifies that the proof document contains an image that matches a previously submitted face proof image (selfie). |
| Nationality | Verifies the customer's nationality. |
| Document subtype | Verifies that the proof document is one of the permitted proof document subtypes. For a list of subtypes, see subtypes. |
Identity document types
Identity checks are performed on the following document types:
- Passport.
- Driver license.
- National identity card.
- Regional identity card, such as a state or province.
- Social insurance card with photo.
Address document checks
KYC address document verification scores are defined based on the following automated checks. This process happens automatically and requires no interaction from you or your customer.
To configure or adjust KYC document threshold and weight options for each check, see Configure address document verification scores.
| Name | Description |
|---|---|
| First name | Verifies the customer's first name. |
| Last name | Verifies the customer's last name. |
| Region | Verifies the customer's region. |
| City | Verifies the customer's city. |
| Date | Verifies that the proof document contains a valid date. |
| Line 1 | Verifies line one of the customer's address. |
| Phone | Verifies that the proof document contains a valid phone number. |
| Postal code | Verifies that the proof document contains a valid postal code. |
| Document subtype | Verifies that the proof document is one of the permitted proof document subtypes. For a list of subtypes, see subtypes. |
Types of KYC documents
The following document types are supported:
- Proof of identity.
- Proof of address.
- Proof of funds.
- Proof of purchase.
Facial recognition identity verification
For the proof of identity document type, optionally require the user to upload a portrait photograph of themselves (a selfie). This photograph is automatically compared with the ID photograph using face recognition algorithms and is used as a scoring factor.
For additional verification, you can select to use face liveness detection when the customer is taking a "selfie". Face liveness detects if spoofs are presented to the camera, such as printed photos, digital photos, digital videos, or 3D masks, as well as spoofs that bypass the camera, such as pre-recorded or deepfake videos. Face liveness detection uses a strict process. In some cases, such as in an environment with poor lighting, customers may find this difficult to complete.
Supported countries
All countries that are not sanctioned by the US, UN, UK, or EU are supported.
Technical integration
For technical integration information, see KYC integration guide.