The Alloy SDK now supports the Prove Pre-fill flow. Prove Pre-fill pre-populates application forms with verified identity information, and displays it to the user for confirmation or further edits, reducing consumer friction and fraud.

To get started, simply select "Prove" as a plugin option in your workflow if you are already using the Alloy SDK. Dashboard setup instructions are here and API docs are here. Reach out to your CSM if you'd like to get it set up.

Transaction Monitoring clients can now set up sanctions screening checks for the counterparties that their users are transacting with to ensure ongoing compliance and mitigate counterparty risk. The transacting counterparties will be checked for exact and ‘fuzzy’ matches (e.g. abbreviations, misspellings, transliterations) against the most up-to-date watchlists using our data providers.

As with entity sanction screening, results are surfaced in Case Management to allow agents to take prompt action upon suspicious activity.

To get started with ongoing sanction screening, please reach out to your CSM or [email protected].

The Alloy SDK now supports the Vouched document verification flow. Vouched leverages proprietary artificial intelligence to fully verify identity and onboard users in seconds.

If you’re already using the Alloy SDK, simply select "Vouched" as a plugin option in your workflow.

No code changes are required. Dashboard setup instructions are here and API docs are here. Reach out to your CSM if you'd like to get it set up.

The Alloy SDK now supports Socure's document verification flow. If you’re already using the Alloy SDK, simply select "Socure" as a plugin option in your workflow. No code changes are required. Dashboard setup instructions are here and API docs are here. Contact your CSM if you'd like to get it set up.

If you’d like to see a demo or learn more about the Alloy SDK watch our “Using the Alloy SDK to optimize customer onboarding” webinar.

Clients can now set expiration dates for Journeys which will move applications to an end state based on the configured time-frame. This ensures applications do not remain in a pending state indefinitely and enables more accurate reporting on application decisioning.

To set an expiration time-frame for a Journey, navigate to the Journeys page and click on the ellipsis menu for the Journey and select ‘Set Application Expiration’.

Toggle the ‘Expiration Off’ button and set the expiration timeframe in the ‘Days to Expiration’ field before clicking ‘Save’.

If an application then runs through this Journey and hits the expiration date, the application will automatically move to a ‘Expired’ terminal node and end state.

The login page now has a new look and feel. When navigating to your Alloy instance, you’ll notice a newly designed experience with the same reliable login functionality.

SDK Theme Customizations

Clients using the Alloy SDK can now customize colors and components for Alloy-built plugins in the SDK. This feature allows Alloy clients to style plugins to better match their own branding. For example, this SDK matches the green and grey colors of the company.

There are three ways to pass styling into the SDK, listed in hierarchical order:

1. initParam.colors (the color parameter that previously existed in the SDK init params)
   1. “Primary” will override the color of the buttons
   2. “Secondary” will override the hover color of the buttons
2. initParam.customStyle.componentOverride
3. initParam.customStyle.theme

See API docs for more details here.

Clients can now have applications automatically assigned to agents when they require a Review. This feature evenly distributes applications across all agents that have permission to review an application.

Instructions below

1. If a client wants to use the auto-assignment functionality, they’ll need to add permissions to the specific role types through the ‘Settings’ page

• The ‘Agent can be auto assigned Journey Applications’ permission should be checked off

2. Once that permission is added, anytime an application requires a Review, it’ll be automatically assigned to the agent with the least number of applications assigned to them.