KYC Integration Test Plan

Task O12 - Tested a full user and account create where KYC fails

Overview

The integration plan is meant to give Partners an overview of the applicable QA tests that should be performed prior to moving into a production based environment.

Simulating KYC Failures

When submitting a user for KYC - POST Create User it is possible to set up the user so that it will eventually trigger a failure response.

When creating a user, its lastname property must have a KYC error name such as SSN_NOT_MATCH, where SSN_NOT_MATCH is the enum name of the KYC error code you wish to trigger.

For example, if the receiving lastname is SSN_NOT_MATCH, an error of K102 will be posted within minutes after the original KYC had been triggered. This mirrors how KYC errors and KYC attempts work in production.

Once the lastname property is modified back with any other string, an APPROVED KYC response is returned.

Available KYC enum names that are acceptable can be found here

Non-document approvals

For Partners onboarding customers where their basic_info.data.country is USA, AUS, or GBR, there will be no need to Upload documents since DriveWealth will perform KYC without any such requirement unless specified. Only endpoints required for Onboarding and initiating the KYC process are Create User and Create Account.

However, it's recommended that Partners still implement the full KYC flow in the event the customer cannot be verified based upon non-documentary measures and would then be required to upload an appropriate document.

DW Path - DriveWealth fully performs KYC

Test Suite 1: Testing in UAT

1. Create User and Account in UAT
2. Create User and Account using Negative test cases as depicted in simulate KYC failures
3. If KYC fails for the first time,
   a. retry by adding failure info again as above.
   b. retry by adding any other information than above.
4. If KYC fails a second time, add documents.

Expected results

1. Users and accounts are successfully created and approved.
2. KYC fails with the corresponding failure codes as depicted on the document. More information will be requested.
3. a. Adding failure info a second time will fail KYC again and DW system will request for documentation.
   b. Adding non-failure info will have the KYC, user and account approved.
4. KYC will be approved in UAT.

Status matrix

Test Suite 2: Testing in UAT with PROD feed for KYC

1. Create User and Account with actual PII Information
2. Create User and Account with incorrect PII Information.
3. If KYC fails for the first time,
   a. retry by adding wrong information again
   b. retry by adding accurate PII information
4. If KYC fails a second time,
   a. add actual documents.
   b. Add junk/low resolution/incorrect documents.

Expected Results:

1. User and Account Successfully created with KYC, User and Account all approved.
2. KYC fails with appropriate failure reasons, more information requested.
3. a.KYC fails again. Documentation will be required to be uploaded.
   b. KYC Approved, Account and User approved.
   4.a.KYC will be approved, the user and account will be approved.
   b. KYC will fail, entering a Manual review.

Status matrix

General comments
For Non Doc Partners relying on DriveWealth for KYC, it is recommended to integrate into our Upload Documents API to be utilized when required. This will not be required during Onboarding flow, but will be required when KYC fails 2 times w/o documentation. Having this incorporated will eliminate the need for manual work to reach out to Customers.
Note: While KYC is still pending, Accounts and Users will still be in a PENDING status.

DW and Partner Path - BOTH DW and Partner Perform KYC

(Partner performs initial KYC)
Test Suite 1: Testing in UAT

1. Create User and Account in UAT.
2. Create User and Account using Negative test cases as depicted in: simulate KYC failures
3. If KYC fails for the first time,
   a. retry by adding failure info again as above.
   b. retry by adding any other information than above.
4. If KYC fails a second time, add documents.

Expected Results:

1. Users and accounts are successfully created and approved.
2. KYC fails with the corresponding failure codes as depicted on the document. More information will be requested.
3. a. Adding failure info a second time will fail KYC again and DW system will request for documentation.
   b. Adding non-failure info will have the KYC, user and account approved.
4. KYC will be approved in UAT.

Status matrix

Test Suite 2: Testing in UAT with PROD feed for KYC

1. Create User and Account with actual PII Information
2. Create User and Account with incorrect PII Information.
3. If KYC fails for the first time,
   a. retry by adding wrong information again
   b. retry by adding accurate PII information
4. If KYC fails a second time,
   a. add actual documents.
   b. Add junk/low resolution/incorrect documents.

Expected Results:

1. User and Account Successfully created with KYC, User and Account all approved.
2. KYC fails with appropriate failure reasons, more information requested.
3. a.KYC fails again. Documentation will be required to be uploaded.
   b. KYC Approved, Account and User approved.
   4.a.KYC will be approved, user and account will be approved.
   b. KYC will fail, entering a Manual review.

Status matrix

Note: Accounts and Users will still be in an APPROVED status even if KYC is PENDING since it is assumed that the Partner has performed KYC before onboarding the customer with DriveWealth.

Document approvals

• For Partners onboarding customers where their basic_info.data.country is NOT USA, AUS, or GBR, there will be an absolute need to Upload documents. In case of Document approvals, the process will involve using the Create User, Create Account and Upload documents endpoints.

DriveWealth fully performs KYC

Test Suite 1: Testing in UAT

1. Create User, Upload documents and Create Account in UAT.
2. Create User, Upload documents and Create Account using Negative test cases as depicted in simulate KYC failures
3. If KYC fails for the first time,
   a. retry by adding failure info again as above.
   b. retry by adding any other information than above.
4. If KYC fails a second time,
   a. retry by adding failure info again as above.
   b. retry by adding any other information than above.

Expected Results:

1. Users, documents and accounts are successfully created and approved.
2. KYC fails with the corresponding failure codes as depicted on the document. New documents will be requested.
3. a. Adding failure info a second time will fail KYC again and request for documentation.
   b. Adding non-failure info will have the KYC, user, documents and account approved.
4. a. Adding non-failure info will have the KYC, user, documents and account approved.
   b. Adding failure info a third time will fail KYC again and go into Manual Review

Status matrix

Test Suite 2: Testing in UAT with PROD feed for KYC

1. Create User, documents and Account with actual PII Information and actual PII documents.
2. Create User, documents and Account with mismatching/incorrect PII Information.
3. If KYC fails for the first time,
   a. retry by adding incorrect document/information again
   b. retry by adding accurate info and documents PII information
4. If KYC fails a second time,
   a. retry by adding incorrect document/information again
   b. retry by adding accurate info and documents PII information

Expected Results:

1. User, documents and Accounts are successfully created and approved
2. KYC fails with appropriate failure reasons, new documents will be requested.
3. a.KYC fails again. Documentation will be required to be uploaded.
   b. KYC Approved, Account and User approved.
   4.a.KYC will fail, entering a Manual review
   b. KYC will be approved, user and account will be approved.

Status matrix

Note: In the above scenarios the Account and User status will be PENDING until KYC is approved.

DW and Partner Path - BOTH DW and Partner perform KYC

(Partner performs initial KYC)
Test Suite 1: Testing in UAT

1. Create User, Upload documents and Create Account in UAT.
2. Create User, Upload documents and Create Account using Negative test cases as depicted in simulate KYC failures
3. If KYC fails for the first time,
   a. retry by adding failure info again as above.
   b. retry by adding any other information than above.
4. If KYC fails a second time,
   a. retry by adding failure info again as above.
   b. retry by adding any other information than above.

Expected Results:

1. Users, documents and accounts are successfully created and approved.
2. KYC fails with the corresponding failure codes as depicted on the document. New documents will be requested.
3. a. Adding failure info a second time will fail KYC again and request for documentation.
   b. Adding non-failure info will have the KYC, user, documents and account approved.
4. a. Adding non-failure info will have the KYC, user, documents and account approved.
   b. Adding failure info a third time will fail KYC again and go into Manual Review

Status matrix

Test Suite 2: Testing in UAT with PROD feed for KYC

1. Create User, documents and Account with actual PII Information and actual PII documents.
2. Create User, documents and Account with mismatching/incorrect PII Information.
3. If KYC fails for the first time,
   a. retry by adding incorrect document/information again
   b. retry by adding accurate info and documents PII information
4. If KYC fails a second time,
   a. retry by adding incorrect document/information again
   b. retry by adding accurate info and documents PII information

Expected Results:

1. User, documents and Accounts are successfully created and approved
2. KYC fails with appropriate failure reasons, new documents will be requested.
3. a.KYC fails again. Documentation will be required to be uploaded.
   b. KYC Approved, Account and User approved.
   4.a.KYC will fail, entering a Manual review.
   b. KYC will be approved, user and account will be approved.

Status matrix

Note: Only difference from the above is that Accounts and Users will still be in a APPROVED status even if KYC is PENDING since it is assumed that the Partner has performed KYC before Onboarding the customer with DW.

Partner Path (Partners with a Reliance Provision)

Test Suite:
Create User and Create Account in UAT.

Expected Results:
Users and accounts are successfully created and approved.

Comments:
There is no Need to test for negative use cases as all users will be 100% approved instantly in both UAT and PROD. Since DriveWealth doesn’t perform additional KYC, there will not be any KYC failures in future.