Product Updates

Multi-entity Journeys now supported

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.

Multi-entity Journeys example

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.

What-If now available for Credit Underwriting

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.

JQ functionality now available for output attributes

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.

New API allows easy import of final outcome data

New API makes it easy for clients to import “final outcome data” or “client feedback data”. This is data that identifies whether customers are fraudulent or not. This goes beyond approve/deny decisions and looks at a customer’s behavior over time. Alloy clients who import this data can gain additional insights into fraud behaviors of their customers and how to prevent future fraud.

With the release of this new API, we encourage clients to send us final outcome data on a regular cadence. Please reach out to your CSM or [email protected] to get started. Also, please reference our API documentation or client support documentation.

Business attributes now available for Allow/Deny lists

Business attributes are now available for Allow/Deny Lists to be imported and decisioned on. This allows Alloy users to apply decisions based on business data received and reviewed. For more information, please see our documentation.

Improved CSV import process for Allow/ Deny lists

Alloy now provides a better CSV import experience for all users. This update makes it easier to validate the quality and format of the data being imported. Read our full documentation for how to use this new CSV import functionality.

Text strings now supported for Matrix Model Axis Headers

Alloy has introduced the ability to use text strings as the Axis Headers within Matrix Models for Credit Underwriting.

If your credit policy includes calculating a credit line assignment or APR using a two dimensional grid or matrix, Alloy’s Matrix Model feature is a great way to easily handle this logic.

We have expanded our existing Axis Header configurability options to now support the following:

Ranges (FICO Score): 300-500, 500-700, 700-850

Strings (Tier): Low, Medium, High

Webhooks authentication modal now available with support for OAuth 2.0

Alloy added a designated “Authentication” section to the webhooks modal and added support for a new authentication type - OAuth 2.0 client credential flow. With this addition, we now support No Auth, Basic Auth, and OAuth 2.0.

When you create a webhook (or edit an existing webhook), there is now a section to select “authentication type”. You can select None, Basic or OAuth 2.0.

Webhook 1
Webhook 2
Back