Alloy's Document Verification software development kit (SDK) has expanded to include ten new document types. A variety of income document verifications (see below) are now available to better support credit underwriting and Canadian dual authentication. Additionally, provincial and indigenous identity documents are now supported for onboarding Canadian applicants. Clients currently using the web SDK don't need to make any changes or download any new files—they can simply start using the new functionality.

The Following documents are now fully supported within Alloy's Document Verification SDK:

Identity documents:

• License (USA, UK and Canada)

• Passport

• Canada Provincial ID

• Canada Indigenous Card

Proof of income/tax documents:

• Paystub

• Bank Statement

• W-2

• 1099

• 1120

• 1065

• T1 (Canadian tax doc)

• T4 (Canadian tax doc)

To enable additional document types within the Alloy SDK, follow the steps below:

1. Set up document verification workflow(s) with relevant services

2. In your Journey, add a “DocV” node for each document type you want to collect. For example, a node for license OR passport and then a second node for paystub OR bank statement.

3. Download the Alloy SDK by running yarn add @alloyidentity/web-sdk. Further instructions are available for web, iOS, and Android.

4. In the initialization parameters, each journey node requires its own nested array. For example, if you wanted to collect a license OR passport AND a bank statement OR paystub, you would write: documents: [['license','passport'],['bank_statement','paystub']].

Once configured, your users can choose document types from the options you’ve selected, whether on web, iOS, or Android.

To learn more about the Alloy Document Verification SDK, view our documentation. If you'd like to add Alloy’s Document Verification SDK to your Alloy workflow, reach out to your CSM or [email protected] to learn more.

A new "Contact Support" widget has been added to the lower left corner of the Alloy dashboard, giving all clients the option to access help articles and submit a support ticket directly from the dashboard.

Clicking on the widget will give users the option to ask a question and see relevant articles. If they need additional help, they can submit a ticket to the Alloy support team from within the widget.

Agents can now assign applications to themselves and other agents from the Application Queue. This will prevent duplication of work between multiple agents and provide an audit trail of reviewer history. All clients using Journeys and the Application Queue will now see the new ‘Assign’ drop-down option on the right side of the application view.

1. The ‘Review’ button will remain disabled until an agent has been assigned.
2. Once users click on the ‘Assign’ button, a list of all applicable agents will be displayed for the user to select from.
3. Based on the permissions that are configured, admins will be able to assign applications to themselves and other agents. Agents will only be able to assign to themselves. Please note that for existing clients, these permissions will have to be manually configured for the different roles. For clients who start using Alloy after today, these permissions will be set up for them by default.
4. Once an agent has been assigned, their name will appear in the button and replace the ‘Assign’ text. The ‘Review’ button will be enabled once an agent is assigned. Agents can un-assign themselves from an application by clicking the 'x' to the right of their name.

Note: In the small edge case where more than one user is assigned to an application at the same time, we will assign it to the first agent and display an error message to the rest.

For clients using Journeys, applications that include multiple entities applying together are now supported within the Application Queue. This includes use cases that involves multiple applications for joint applications as well as business applications. Agents can now see applications that include multiple entities within a unified view and no longer have to toggle between multiple views in order to review each entity within an application. Both evaluation and journey application reviews can be handled from the same screen.

This functionality replaces our Groups feature in a more unified and user-friendly way. To view multi-entity applications within the Application Queue, clients must be integrated with Journeys and use the new “entities array” api schema. View our documentation for additional details.

If you’d like to try Journeys, reach out to your CSM or [email protected] to learn more.

A log of Alloy’s outgoing webhooks is now available within the Settings menu of the Alloy dashboard, under "Webhook Logs."

You can filter/search by any column, free type search or search for anything contained in the webhook payload, for example, a specific entity token. You can also see the attempt number; Alloy will attempt to send all webhooks up to 10 times with exponential backoff. Click on a specific log to see more details, including all previous attempts for a webhook.

Clients using Journeys can now track any changes made to the Journey and view which version is active with Journey version management.

Versions are listed in a table in chronological order, in the order a Journey version was live in production. Draft versions are visible at the top of table. Users can see the dates the Journey was active, any notes, its current status and who created the Journey.

Changes to the Journey status, including the ability to edit a draft, can be made by clicking the ellipsis menu on the right side of the table for the corresponding version. The active Journey can be edited by clicking on the corresponding ellipsis menu and selecting ‘Use as Draft.’ Versions can also be archived using the ellipsis menu.

By clicking the corresponding arrow on the left side of the table, users can expand a version’s details to see the creation date, changes from the parent version (if applicable), the Journey token, and the workflows, document verification, action nodes and Journey outcomes configured within the Journey version.

To learn more about Journeys and Journey version management, view our documentation. If you’d like to try Journeys, reach out to your CSM or [email protected] to learn more.

Multi-entity and multi-branch Journeys can now be configured in the Alloy dashboard, supporting use cases that involve multiple entities running through Journeys, such as joint applications, business applications and router flows.

You can also now configure various branches within a Journey to create sub-journeys if you require differing logic for each entity type, for example, a “persons” branch and a “businesses” branch. This allows you to route the entities within an application through the applicable branch.

To learn more about multi-entity Journeys, view our documentation. If you’d like to try Journeys, reach out to your CSM or [email protected] to learn more.

Alloy clients can now use What-If Analysis for complex workflows such as Credit Underwriting, including those with matrix models.

For example, when running a What-If Analysis on an Underwriting workflow featuring matrix models, any changes to a threshold range and/or matrix value will be accounted for in the Preview Changes panel. Results are displayed in the Preview Changes panel after an expected run time of 1-2 minutes.

To learn more about the What-If Analysis feature, view our documentation here.