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 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.

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.

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

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.

New What-If functionality is available for Transaction Monitoring.

The What-If feature allows you to review the impact of any rule or scenario before pushing it out to production and alerting your customers. Try out different scenarios and thresholds, understand which entities would be triggered with the updated logic, and minimize false positives by only capturing the activity you're concerned about.

If you’d like to try or learn more about the What-If feature for Transaction Monitoring, reach out to your CSM or [email protected].

For clients using Journeys, Alloy will now handle the transition and state management of an Entity between workflows and document verification step ups for you.

Read more about Journeys on our blog. If you’d like to try Journeys, reach out to your CSM or [email protected] to learn more.

Alloy is now offering the ability to decision off of identity elements (like SSN, phone number, email, etc.) when they are seen across multiple entities. This is an important step Alloy is taking to proactively prevent fraud. An example scenario would be detecting entities that share a SSN or phone number, then taking subsequent actions—such as tagging it informationally, running additional services, or determining an outcome.

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