Clients using the credit panel will now be able to view payment history for the tradelines returned from Equifax and Experian, 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. 

To get set up on the credit panel, please reach out to your Alloy representative.

Learn more about the original release of tradelines in the credit panel in our February 2024 change log.

The display of Reason Codes in the Evaluation page has been redesigned to allow for easier identification and understanding of reason codes.

Reason codes are now categorized accordingly:

• Tagged Reason Codes - returned reason codes that belong to a reason code group and triggered a threshold that has a tag in the workflow. Tagged reason codes will be displayed next to the group name instead of the service name. Furthermore, the associated tag will also be displayed next to its respective reason code group on the right.
• Untagged Reason Codes - returned reason codes that belong to a reason code group that did not have a tag set in the workflow. 
• Unclassified Reason Codes - returned reason codes that are not a part of any reason code group. Previously, these reason codes were not visible in the dashboard.

As part of our ongoing efforts to improve your experience with our dashboard, we are excited to share that starting January 4th you will see changes in how Reason Codes are displayed in the Evaluations page. These changes are designed to provide you with a more intuitive review experience and empower better decision making.

We have added new capabilities to better serve sponsor banks, BaaS providers, and fintechs in managing compliance, fraud and credit risk at scale with real-time oversight across all partnership programs. Alloy enables embedded finance providers to have full transparency and oversight across their partner portfolio, while providing the flexibility for fintechs to own part of their risk management. These new capabilities include:

• Provisioning dashboard with parent/child account structures: configure different levels of permissions to provide appropriate control. Sponsor banks or BaaS providers (the ‘parent accounts’) are able to designate the level of autonomy or guardrails to put into place for each of their fintechs (the ‘child accounts’) directly in the platform: 
  • Controlled child accounts have restrictions on editing the decisioning logic pushed down by their parent, but still have visibility into their policies, manual reviews, and performance.
  • Autonomous child accounts can create their own custom rules on top of the baseline policies enforced by their parent.
• Build and enforce risk policies at scale: create and push out your policies to one or multiple partners using Journeys. Any edits to the Journey decisioning logic will automatically be passed on to the child entities, ensuring consistency.
• Customize policies: allow more mature Fintech partners to own and define their policies while maintaining oversight.
• Merged lists: detect and decision on bad actors across your entire portfolio with a federated denylist that can be used across all partner accounts.

Learn more about these capabilities here: [embed or link the LAB video]

If you’d like to use Alloy for Embedded Finance, please reach out to your Alloy representative.

Alloy now supports exporting a detailed timeline log of events for entities to enable clients using Onboarding and Credit Underwriting to more easily meet audit requests. This log will include events such as: entity details, any Journey applications and evaluations run on the entity, actions and decisions taken by agents, documents and notes uploaded on the entity, any published attributes being used by the entity and a history of changes on published attributes.

To get started, navigate to the Entities page and select the entity. From the vertical ellipses menu on the top right, click ‘Download Entity Timeline’, and you’ll be able to download a text file with a log of events.

If you’d like to use this feature, please reach out to your Alloy representative.

Clients are now able to export a CSV for a full history of Agent Actions. Previously, all data exports in the platform were limited to 10k rows.  

To get started, click on your user profile icon and select ‘Auditing’. This will bring you to the Agent Actions page where you can click on Export CSV. You'll get a notification under the bell icon and an email notification when the file is ready to be downloaded!

Please note: users must be appropriately permissioned (‘Agent can  view the Audit Actions page’ must be enabled).

System for Cross-domain Identity Management (SCIM) gives clients using SAML for SSO-based login the ability to provision Alloy users directly from their identity provider.

From their identity provider, clients will be able to 

• Grant users access to Alloy
• Remove users’ access to Alloy
• Assign users to roles/ groups in Alloy
• If they are deleted from the identity provider, they will be archived within Alloy 

When users are manually created within Alloy, these users will not be created within the identity provider automatically. However, new users can be linked within the identity provider.

To activate SCIM, clients can reach out to Alloy’s Support Team.

Clients on Journeys will see additional visual updates to the Versions List view for optimal usability:

• Versions are by default sorted in descending order. (Drafts no longer float to the top.)
• Sort by ascending or descending versions by clicking the arrow in the “Version” column.

When expanding details of a specific version:

• A "Dates Active" section shows all the times, and by whom, a given version has been set active. With this built-in audit trail, users no longer need to create a new Journey version every time someone sets an "inactive" version to "active".
• Outcomes used in the Journeys, along with the Services used, appear as well.

Clients using Published Attributes now have the ability to use a Published Attribute as both an Input and an Output attribute within a single workflow. This unlocks the ability to reference the present value of the attribute in order to set the new value of the attribute.

A Published Attribute can be used to dynamically calculate a customer’s compliance risk rating. The rating’s value will update by adding to or subtracting from a prior value in a workflow. By doing this, clients will be able to detect risk earlier than before and have a holistic view of the entity's risk that evolves over time.

An example for updating the String Risk Score on an entity:

To view the history of a Published Attribute’s previous values, click on the three dot menu in the entity panel, click “View Entity Info”, and hover over the clock icon to the right of the attribute’s name.