Alloy now supports custom Outcomes in Workflows and Journeys, which gives users the ability to tailor Outcome names, colors, and icons to better align to your organization’s risk review protocols and provide the right context for Evaluations, Applications, Alerts and Investigations. In addition, you can now add a characteristic to your Outcome letting Alloy know if the Outcome was good, bad, or neutral.

Here's what you should know:

• Any existing or new custom Outcomes can be tailored in Settings
• Preview how the customized Outcome will appear throughout the platform during creation
• View the Workflows and Journeys where an Outcome is actively being used in our enhanced Outcome Settings Page

Clients can now view all entities that were evaluated, were processed through a portfolio evaluation, or were not evaluated but may have been passed on through the Events API or legacy Entities API (for example: if the entity was onboarded outside of your Alloy instance and/or there has been no associated activity that has since triggered an alert, that entity would be considered ‘unevaluated’). Previously, the Entities page only displayed entities that had undergone a real-time evaluation.

Additionally, for clients using portfolio workflows, the Entity Detail page now displays a list of portfolio evaluations that the entity has been shortlisted in. These updates enable Alloy to serve as the single source of truth, providing teams with complete visibility into all the entities in their portfolio and allows them to take action on these entities in the future (e.g. create an investigation on that entity).

Clients now have the ability to link separate transactions using a unique identifier. Common examples of disparate but related transactions that clients may want to link include chargebacks, refunds, and disputes.

This can be used by any client utilizing Alloy for transaction monitoring via the Events API.

With this dedicated field in the Alloy platform, we will be able to build more functionality on top of this unique identifier related to alerts and decisioning capabilities.

To set up transaction linking, please reference our API documentation.

US clients using the AI-powered Fraud Attack Radar (FAR) can now benefit from more improvements to the FAR dashboard and will better allow them to autonomously and quickly triage following a suspected fraud attack. Clients will now be able to:

• View a summary of all attacks for the filtered time period
• View the top 4 indicators for an attack in the collapsible drown down
• Mark the status of an attack using the following options: Under Review, Confirmed Attack, Not Fraud Attack

To set up Fraud Attack Radar, navigate to the Workflows page and click the ellipses menu for your chosen workflow. Select ‘Fraud Attack Radar’ to open up the set up configuration. Please note: the model requires a minimum of 2 months of historical data to accurately work and will take roughly 2 weeks to train. The model can only be configured for person-type workflows and may not yield the best results for low volume use cases.

PATCH Application Enhancement

AFEF clients can now update completed or in-flight Applications with the parent slug, giving users the ability to update parent associations at any stage in the applications process via the Applications Endpoint.  Parent auditor accounts are only able to view records assigned to them. To set this up, please reach out to your Alloy representative with any questions.

AFEF Entity Endpoint Enhancement

AFEF clients can confirm their parent mappings via the entity endpoint.  This enhancement gives clients the ability to ensure their mappings are correct in a quick and scalable way. Users can call the entity endpoint and retrieve the parent mapping in the header. To set this up, please reach out to your Alloy representative with any questions.

We have made a few changes recently to our Workflow Editor user interface to help with readability and navigation.

Collapsed (and Expandable) Input Attribute Nodes

All input attributes will now appear collapsed under a single “inputs” node in your Workflow. You can add a child action off of this collapsed node, or you can choose to expand the node by pressing the downward caret on the node, and add individual child actions off of any individual input.

This can help to simply the view of a large complex Workflow with many inputs to make it more readable and digestible.

New Paradigm of Node Ordering

While the order in which nodes were saved to a Workflow version did not previously follow a set pattern, the nodes will now always be ordered in the following way (and this pattern will “stick” even after the Workflow version is saved):

Per column in the Workflow, nodes will be ordered by node type and then in alphabetical order. The order of node types in any given column is the following:

• Service
• Tag
• Output Attribute
• Matrix Model
• Everything else

Example: This Workflow has five columns. In each column, Inputs are at top, followed by Services, then Tags, and so on. Within each node type, the nodes are sorted in alphabetical order. For example, in the third column, the green service nodes are in alphabetical order from top to bottom: Acuant, Acuant, Data Zoo, and TransUnion TLO .

NeuroID's behavioral risk service is now available via the Alloy web SDK for clients to use to prevent fraud. Clients can easily integrate it via the Alloy SDK in their account opening flow to track a user's behavior and send it to Alloy to be decisioned upon.

Please reference Alloy’s API docs or reach out to your CSM help on setup.

Clients can now use the Alloy SDK to integrate TruValidate’s third party device risk to prevent fraud.

The Alloy SDK makes it easy for clients to integrate third party services without the need for extensive development effort. Please note, clients will still need to integrate separately to first party device risk (reverse proxy).

Please reference Alloy’s API docs or reach out to your CSM help on setup.