Simulate Application Review

Highnote's application review simulation lets you test the following:

• The status of an application
• Your application review workflow
• Document uploads

1. A Highnote account
2. Access to the Highnote API, API Explorer, or dashboard
3. A card product

Do not use production data in the test environment. Use only dummy or test data explicitly created for testing purposed.

The Highnote test environment lets you experiment, build integrations, and train your team on the Highnote platform. To ensure the security of your real-world data, do not use it for testing -- this includes sensitive information such as customer details, financial data, or personally identifiable information (PII).

To simulate an application review workflow, we recommend using the following sequence:

1. Create an account holder with specific simulated values.

2. Open an application to simulate an IN_REVIEW or DENIED status.

3. Simulate a document upload session.

4. Update the status of the document.

5. Update the identity verification status of the account holder.

6. Optionally Simulate additional document upload sessions, e.g., if identity re-verification fails.

7. Update the application status to approve or deny.

To simulate an application with the status of IN_REVIEW or DENIED, you must create an account holder with specific simulated values (provided below). These values differ depending on whether the applicant is undergoing Know-Your-Customer (KYC) or Know-Your-Business (KYB) verification:

• KYC: Verification for person applications
• KYB: Verification for business applications

KYC verification is used to verify the identity of the following types of applicants:

• USPersonAccountHolder
• USBusinessAuthorizedPerson
• USBusinessUltimateBeneficialOwner

Use the following values when creating an account holder to simulate the following application statuses:

For DENIED applications, you can use additional values to produce failure tags and simulate different failure scenarios:

After creating an account holder with simulated values, open an application.

KYB verification is used to verify the identity and details of a USBusinessAccountHolder. KYC verification is also required for each USBusinessAuthorizedPerson or USBusinessUltimateBeneficialOwner under a USBusinessAccountHolder.

Use the following values when creating an account holder to simulate the folowing application statuses:

For DENIED applications, you can use additional values to produce failure tags and simulate different failure scenarios:

After creating an account holder with simulated values, open an application.

Once an application has entered IN_REVIEW status, you can begin a document upload session to simulate adding supporting documents.

Use the following steps to simulate the document upload session:

1. Optional Generate a client token .

2. Start document upload session.

3. Create document upload link.

4. End the document upload session.

Once you've closed the document upload session, you can simulate the review status of each document by assigning a new status of APPROVED or DENIED.

Use the following mutation to simulate the review status for each document uploaded in the upload session:

• In the Test environment, you can approve an application with the identity verification status set to any value: PASSED, PENDING, DENIED.
• In the Live environment, the identity verification status of each account holder must be set to PASSED before you can approve an application.

Once a document review status is assigned, you can simulate the identity verification status of an account holder, represented by the currentVerification field.

For business account holders that have multiple authorized persons or owners, all account holder identities must pass for an application to be approved.

Use the following mutation to simulate an identity verification status change, and update newVerificationStatus from IN_REVIEW to PASSED or DENIED:

Note: If you are only simulating one document upload session, skip this simulation.

The following scenarios may require additional document upload sessions:

• The document provided by the account holder is insufficient to approve the application.
• You need to add primary authorized persons or beneficial owners to a business account holder.
• An application has multiple applicants, each of which requires multiple document types.

When simulating additional document upload sessions:

• The application status remains IN_REVIEW,
• The currentVerification.status for each unverified application remains PENDING.
• The currentVerification.reason for each requested application updates to DOCUMENT_UPLOAD_REQUESTED.

Use the following mutation to simulate additional document upload sessions. Provide a specific documentType for each applicantId. See document types.

Warning: This mutation lets you approve or deny an application status, but it does not approve each of the verification components. Verification components must be approved before you can create a financial account. To update verification components, see Update the identity verification status.

To simulate an application status, you can update the application from IN_REVIEW to APPROVED or DENIED.

Use the following mutation to update the application status: