Transaction Monitoring clients can now aggregate additional transactional and account-level attributes to configure custom rules in order to better detect suspicious activity patterns including:

• Irregularities in counterparties,
• Changes in user behavior compared to historical transactional activity,
• Additional filters for MCC codes, reason codes, return codes,
• Successful and attempted linking of external funding accounts,
• Attempted PII changes such as address and phone numbers changes.

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.

Alloy’s Identity Element Velocity feature offers clients the ability to decision off of identity elements when they are seen across multiple entities; for example, detecting identities that share a SSN or phone number, then taking subsequent actions—such as tagging it informationally, running additional services or determining an outcome.

New updates to Identity Element Velocity include:

• The option to decision off of more identity elements, including email domain, mother’s maiden name and IP address.
• The ability to add more than one PII element to an IEV rule for the same evaluation (while keeping entities, timeframe and velocity count the same). For example, detecting other entities that have used both the same SSN and device alias in an evaluation within a timeframe.

For full details on how to use this feature, see our support article.

New changes have been made to the user interface for What-If Analysis, including the addition of a confidence level to show the level of certainty in the results of the analysis.

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

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.

Credit Underwriting clients can now use JQ expressions with output attributes. This is similar to the existing functionality currently available for input attributes.

An example of using JQ expressions with output attributes is enabling rounding capabilities with credit policies, such as rounding a credit line assignment to the nearest $100 or rounding a number to the nearest hundredth decimal point.

If you’d like to incorporate JQ into your output attributes, reach out to your CSM or [email protected] to learn more.