Clients can now sandbox test Rule Based Notifications and be alerted for rules which have been hit in their production or sandbox environment. Rule Based Notifications allows you to set up alerts to be informed when pre-defined thresholds are breached, enabling proactive detection of anomalous activities that might indicate fraud.
Set up and configuration only takes a few steps – check out this guide for a few sample rules or learn more here in LAB.
Clients on Journeys can use the CLEAR SDK Plugin to seamlessly and securely verify users. CLEAR’s services allow users to create or leverage an existing CLEAR account to provide verified and secured identity information, which can be leveraged at the time of onboarding or as step-up verification on an ongoing basis.
Existing SDK clients can turn on the CLEAR SDK plugin in the SDK configuration modal. If you’d like to try the Alloy SDK, reach out to your CSM or [email protected] to learn more.
Clients on Journeys can use the LexisNexis ThreatMetrix SDK Plugin for capturing device signals and decisioning on them in Alloy.
To turn on the Threatmetrix SDK Plugin:
For more information on implementing ThreatMetrix through the Alloy SDK, check out our developer documentation.
To purchase the LexisNexis ThreatMetrix data product, please speak with your Alloy representative. Alloy is a reseller of LexisNexis ThreatMetrix.
When end customers submit an application for a new digital banking product, clients will be able to deploy an interface to collect multiple documents as part of their application.
Applicants are shown a prompt with a list of documents they are required to upload. They can drag and drop multiple files into the interface, and scroll through the flow to upload different types of documents.
Collected documents will be stored on the entity’s record and available to review in the dashboard. They can be sent as an array to the client’s preferred vendor for processing.
The document collection landing page is fully customizable, including setting conditions for when to collect documents based on the applicant’s evaluation outcome. See documentation [link] for full details.
Clients using published attributes can now group related attributes for improved readability and a more seamless review experience. Published attributes are attributes associated with an entity that persist and can be used in any subsequent workflow for decisioning. Though published attributes are endlessly customizable, a few common attributes clients have set up include: customer income, employment status, risk score.
Appropriately permissioned agents can now create, edit and order category groupings for published attributes in Settings > Published Attributes. Published attributes that do not have a specified Grouping will be left in an uncategorized Grouping.
Clients using portfolio monitoring can now view and search by entity token and external ID in the portfolio evaluations shortlist. To view the shortlist, navigate to the Evaluations page, toggle to the Portfolio tab, and select your chosen workflow. In the Portfolio Evaluation, you’ll now be able to see ‘Entity Token’ and ‘External Entity ID’ associated with each entity and be able to filter using these identifiers using the search bar.
[insert screenshot]
Clients on Journeys can streamline document collection with Alloy’s Multi-Document Collection SDK Plugin. This new user experience will primarily benefit financial institutions in the UK who are onboarding new customers that require additional due diligence, as well as financial institutions with underwriting policies requiring conditional document verification.
When an end customer submits an application for a new digital financial product, clients will be able to deploy an interface to collect multiple documents as part of the application. In the interface, end customers will see a summary of the required documents to prepare for upload and view progress of their document uploads. Clients will be able to collect as many documents as required within a single user interface.
In addition, clients will be able to set conditions for when to collect documents based on the applicant’s evaluation outcome and customize the document collection landing page accordingly.
More visibility into Data Sources for easier data error troubleshooting.
A data product that is included in multiple nodes of a workflow will be listed multiple times under Data Sources. This reflects the response from the data product at each distinct workflow node.
For workflows running the same data product at multiple nodes, it is recommended to rename the data product on each workflow node (e.g. ID Analytics 1, ID Analytics 2) to make it clear which response is associated with which node.
