Verification results

To determine the customers final status, first the KYC provider makes a decision. Then your application makes a decision using ComPilot's predefined automations and the rules set in the ComPilot Rules Engine. As a developer or compliance officer, it is sometimes useful for you to know what combinations of statuses are possible.

The decisions are shown in the following tables.

KYC decision	Meaning
Passed	The customer has successfully passed the KYC checks
Rejected	The customer has failed the KYC checks and may not retry
Retry	The customer has failed the KYC checks and may retry

Application decision	Meaning
Active	Customer approved by your application
Failed	Customer temporarily banned by your application but can retry
Rejected	Customer permanently banned by your application and cannot retry
To be reviewed	Issue detected by ComPilot and the customer needs to manually be checked

The application decision becomes the customer's status. For more information, see Customer statuses.

For a workflow that uses a KYC provider, the ComPilot Rules Engine, and AML checks, the following cases are possible.

Case 1

Verification scenario	Verification outcome
Approved by KYC provider Approved by ComPilot Rules Engine No AML hits	Customer sees: two green check marks and the options to generate VCs or close the widget Automations: customer status set to Active and risk level set to Low Email: customer receives approval email

Case 2

Verification scenario	Verification outcome
Denied by KYC provider but with retry opportunity ComPilot Rules Engine will not run AML screening will not run	Customer sees: red check from KYC provider and retry option that restarts the process Automations: customer status set to Failed Email: customer receives KYC rejection with retry opportunity email

Case 3

Verification scenario	Verification outcome
Denied by KYC provider but without retry opportunity ComPilot Rules Engine will not run AML screening will not run	Customer sees: two red check marks and the option to close the widget Automations: customer status set to Rejected and risk level set to Low Email: customer receives KYC rejection without retry opportunity email

Case 4

Verification scenario	Verification outcome
Approved by KYC provider Denied by ComPilot Rules Engine AML screening will not run	Customer sees: two red check marks and the option to close the widget Automations: customer status set to Rejected and risk level set to High Email: customer receives application rejection email

Case 5

Verification scenario	Verification outcome
Approved by KYC provider Approved by ComPilot Rules Engine AML hits	Customer sees: green check from KYC provider and pending notification from application Automations: customer status set to To be reviewed Email: customer does not receive email until customer status is set to Rejected or Active

note

Even a single Low risk alert will mean the customer is given a status of To be reviewed.

In this case, if a compliance officer changes the customer status, the following effects will occur:

• If the customer status is changed to Escalated, and the pending notification remains.
• If the customer status is changed to Active, the customer is approved and the appropriate email is sent.
• All other customer statuses reject the user and the appropriate email is sent.