Ongoing clients can use the new Multi-Level Attribute (MLA), Count of Days, to return the number of days for which a set of conditions was true for an entity. This can be used to measure how much an entity’s behavior has been suspicious and deviated from the norm over a given time period.

Example use cases:

• Calculate the number of days during which an entity transacted over $10,000 in the past week.
• Calculate the average transaction volumes per day for an entity (the sum of total transactions divided by the count of days in which the entity carried out a transaction).

The Count of Days MLA is available as a filter within the Transaction History service within an Alloy workflow.

Clients can select a custom expiration time for hosted SDK links, in lieu of the default expiration time of two days.

Under SDK Settings in the Alloy Dashboard, scroll to the bottom of the page to see the new setting for adjusting the expiration time of your hosted SDK links.

Learn more about the original release of the Alloy SDK hosted link in our January 2024 change log and the SDK hosted link via API enhancement in our March 2024 change log.

Clients using the credit panel will now be able to view payment history for the tradelines returned from TransUnion, whenever they are made available in the raw response, so agents can get a better understanding of the creditworthiness of their borrowers and make more informed credit decisions. In addition to TransUnion, Equifax and Experian reports in the US are also supported. Learn more about the earlier release of tradelines for Equifax and Experian in the credit panel in our March 2024 change log.

Ongoing Monitoring clients on Journeys with a single review node can now utilize a more simplified alert review experience to seamlessly promote an alert to a case, which reduces the number of clicks between an alert review and case escalation. 

To get started, select the alert from the Alert Queue, assign to an agent, and click the ‘Review’ button on the top right, which will open up a modal. Update the status to ‘Promoted to Case” and enter the relevant details before hitting ‘Review’, which will create a new case.

Clients utilizing Alloy for account activity monitoring will now benefit from improvements to our review experience to power efficient and informed decision making. 

Agents will be presented with a new Alert view, displaying a richer and contextualized set of customer information, including a consolidated view of all the entity’s contact details on record and recent updates to these details, including any third party data services that were run. Agents will easily be able to see what information has changed and whether that is associated with risky behavior.

Interested in account activity monitoring? Reach out to your Alloy representative to get set up.

Starting on April 19, 2024, users with admin permissions can set up SAML authentication and SCIM configuration within the Alloy dashboard.

Within “Settings” on the left side menu, click “Auth Settings” to begin your SAML and SCIM configuration process.

SCIM will be supported for your identity provider if you use Okta or Microsoft Entra.

Within Auth Settings, click “Enable SAML Authentication” to begin configuring SAML and SCIM.

Select your identity provider.

Provide an SSO URL and Audience URI from your identity provider.

Upload the XML file received from the previous step.

Configure SCIM for your organization (strongly recommended).

Clients on Journeys can now use our Alloy hosted SDK and retrieve links and QR codes via the API to send to their customers in the case of a step-up verification. This is in addition to being able to retrieve links and QR codes manually from the Alloy dashboard in the application queue.

Learn more about the original release of the Alloy SDK hosted link in our January 2024 change log.

Today we released an update to the way bearer tokens are generated to support a more scalable infrastructure.  As a part of this change, we updated the format of the bearer token itself and changed the character length.

Clients who do not validate based upon the length or type of the bearer token will not notice this change. However, clients who do validate based on length or type will not be able to access the Alloy API as of March 22nd, 2024.