Evaluation Summary: Overview – Alloy

❗️ PII data in an article is all fake for demonstration purposes

Evaluation summaries are comprehensive pages that present key information and data about an entity and its evaluation through a Workflow. A Journey Application can have multiple evaluation summaries that make up the entirety of the Journey Application, if the Journey had multiple Workflows.

Evaluation summaries can have information such as matched data sources, triggered rules (tags), fraud scores, decision reason codes, watchlists, credit reports, and other relevant metadata depending on which data services were configured in the Workflow.

This information is designed to help reviewers quickly understand the outcome and reasoning behind an evaluation, such as why an application was approved, denied, or sent for manual review.

Conditional Display of Evaluation Cards

Evaluation summaries dynamically display data cards based on the information returned during an evaluation. This logic helps reduce visual clutter and ensures reviewers focus on relevant results. Most data cards are shown only if data is returned that would populate that card, however there are select cards that will always be visible outlined below:

If no data is returned for a given card, the entire card is hidden, rather than displaying an empty or partially empty panel.
The following cards will always appear in an evaluation, even if no data is returned:
- Matched Data
- Tags
- Other Data (this card remains visible to allow configuration or data entry, even when empty)
The Watchlist and Credit data cards are vendor specific and will always be displayed if a Watchlist or Credit vendor module is included in the workflow, regardless of whether those modules return data.

This behavior ensures that evaluations only surface cards with meaningful results and the required context and configuration entry points remain available.

Evaluation Summaries

Evaluation summaries pages may contain the following data cards:

Business Updates
Credit
Custom Fields
Customer Updates
Data Sources
Device Details
Diligence
Imported Data
Matched Data
Other Data
Outcome Reasons
Returned Reason Codes
Tags
Transaction Summary
Transactions
Watchlist

Business Updates

The Business Updates card is visible for Ongoing Business Updated Events where you can see the difference between an entity's on record data and any updated information from that event. Each change has the ability to be verified by one or more services or not be evaluated. Easily reverify a change and view what has changed.

Credit

The Credit card appears whenever a Credit-specific vendor module is run in the workflow.

Custom Fields

The Custom Fields card shows the user-defined fields attached to the evaluation. Custom fields let teams capture organization-specific metadata (risk flags, reviewer scores, external IDs, notes, etc.)

Customer Updates

This Customer Updates card is visible for Ongoing Events only, specifically a Person Update Event. The card displays the difference between the historical and the new data for a given Entity. Any services run to verify the new data will also be shown.

Data Sources

The Data Sources card displays the data sources used to decision on the applicant.

A data source paired with a green circle and white checkmark indicates that the data source was executed.

A data source that did not execute is paired with a gray circle and white minus symbol.

In the event of a service failure, an icon will be paired with the data source. When this occurs, you can click on the data vendor and see if there were any errors returned. If the error is temporary, Alloy recommends that the evaluation is rerun.

Device Details

The Device Details card shows devices associated with the evaluation captured by using the iovation SDK. Specifically it displays Device ID, Service, Optionally any Velocity Warning, First Seen Date, Last Seen Date, Device Events Browser Type and Version, IP Address, and OS. Data being displayed may vary based on what information is available from the payload.

Diligence

The Diligence card displays the Fraud scores returned and best practices risk thresholds. These scores reflect the thresholds where the data sources see risk, and not necessarily the rules in the Workflow. To see how the scores affect the outcome, refer to the workflow configuration.

Imported Data

The Imported Data card refers to imported data from earlier journey steps that was used as part of decisioning on a given evaluation. This can consist of Outcome Reasons, Output Attribute, and Matrix Models. Imported objects will be listed by type, workflow, and evaluation token from where they originated from.

Matched Data

The Matched Data card includes the data sources verifying each piece of the applicant’s information.

Matched data sources are in green and non-matched in gray (shown below). This section shows if a data source could match that element, such as address, to the entity.

Please note that whether a piece of data is matched may or may not be connected to the reason an evaluation was decisioned to Manual Review, Denied, or Approved. For that reasoning, see the next section, Tags.

Other Data

The Other Data card can be used to surface metadata fields contained in the raw response (JSON).

For instance, the Other Data section can be customized if your organization wants to see specific vendor attribute information.

To learn more on how to surface information in the Other Data card, please check here.

Outcome Reasons

The Outcome Reasons card shows tags were returned in the evaluation summary and indicate why a particular evaluation received a specific outcome, such as Approved, Denied, or Manual Review. They provide a high-level signal or explanation for the decision made by the Workflow, helping users understand the rationale behind the outcome. For example, if an application is denied, the outcome reason might be "SSN not verified," clarifying the specific rule or condition that led to the denial.

Outcome reasons are distinct from the outcome itself (which is the final decision) and from review reasons (which are selected during manual reviews). They are typically configured by associating certain tags with specific outcomes in the tag settings. When those tags are triggered during an evaluation, they are displayed as outcome reasons in the summary.

Returned Reason Codes

The Returned Reason Codes card displays the reason codes returned whether or not they were used in decisioning.

Transactions

The Transactions card is visible for Transaction Evaluations. It lists all transactions associated for a given Entity: status, status detail, date, external transaction id, external entity id, approval status, created date, settled date, amount, process method, category, interaction point, description, currency, type code, type description, counterparty information ( ID, type, name, number, and country code), notes and documents attached to a given transaction, published attributes, and outcome.

Transaction Summary

The Transaction Summary card is visible for Ongoing Transaction Monitoring Evaluations and displays a summary of the evaluated transaction, including the dollar amount, the status, and the accounts between which the money was exchanged. The card header will vary based on the type of transaction that occurred.

Watchlist

If the data vendor supports watchlist reviews and the setting is enabled, watchlist hits can be reviewed and cleared directly from the Watchlist card. To require review, ensure the reviewer role does not have the permission “Agent can review Journey Applications even if Needs Review Watchlist Matches are not all resolved” enabled.