The Alloy SDK now supports the Prove Pre-fill flow. Prove Pre-fill pre-populates application forms with verified identity information, and displays it to the user for confirmation or further edits, reducing consumer friction and fraud.
To get started, simply select "Prove" as a plugin option in your workflow if you are already using the Alloy SDK. Dashboard setup instructions are here and API docs are here. Reach out to your CSM if you'd like to get it set up.
The Alloy SDK now supports the Vouched document verification flow. Vouched leverages proprietary artificial intelligence to fully verify identity and onboard users in seconds.
If you’re already using the Alloy SDK, simply select "Vouched" as a plugin option in your workflow.
No code changes are required. Dashboard setup instructions are here and API docs are here. Reach out to your CSM if you'd like to get it set up.
The Alloy SDK now supports Socure's document verification flow. If you’re already using the Alloy SDK, simply select "Socure" as a plugin option in your workflow. No code changes are required. Dashboard setup instructions are here and API docs are here. Contact your CSM if you'd like to get it set up.
Transaction Monitoring clients can now view the percentile distribution of impacted entities to help determine the appropriate decisioning thresholds to test.
Previously, clients were able to test scenarios by changing rule thresholds and seeing the total number of impacted entities as well as viewing a list of sample entities. By understanding the percentile spread across their customer base, clients can now better optimize their rules by making more informed decisions about setting and adjusting thresholds.
To try this feature, click on the “Show Thresholds” button for the appropriate aggregation to see the percentiles. Once the aggregation is finalized, click the "Test" button on the bottom of the window to see a sample of the impacted Entities with the updated logic (the full list can also be downloaded).
Posted Jul 15, 2022
More flexible aggregations now available for transaction monitoring rules
Transaction Monitoring clients can now build rules on transaction history and PII changes using more granular time range options including minutes and hours.
Furthermore, clients can also run aggregations at the transacting account level for entities with multiple accounts. Previously, aggregations could only be run on the entity as a whole. This change also extends to aggregations for counterparties; this means clients can create rules aggregating counterparty activity relating to a specific account.
These changes enable clients to configure more custom rules in order to better detect suspicious activity and reduce potential false positives for teams to review.
Posted Jul 6, 2022
Assign agent and manager-level permissions in Case Management
Transaction Monitoring clients will now be able to designate two tiers of case management permissions: Agents, which have the first tier of case permissions, and Managers, which have the same first tier permission along with additional permissions with more flexibility.
Both Agents and Managers will be able to view cases of any case type.
Agents will only be able to update cases if they are assigned to it. If a case does not have anyone assigned yet, then an Agent can assign themselves to the case. However, an Agent cannot unassign another Agent from a case, assign themselves to a case if it is already assigned to another Agent or assign another Agent to a case.
Managers will be able to update the status, assign or unassign, and make changes to all case types.
Users can view their permissions in the Settings menu of the Alloy dashboard, under “Agents”:
Please note: only admins can make changes to add/remove permissions. To set this permission, go to Settings > Roles > Permissions.
All case assignment events, as well as case status changes, will be auditable within Alloy.
Posted Jun 17, 2022
Additional transaction attributes now available for aggregation
Transaction Monitoring clients can now aggregate additional transactional and account-level attributes to configure custom rules in order to better detect suspicious activity patterns including:
Irregularities in counterparties,
Changes in user behavior compared to historical transactional activity,
Additional filters for MCC codes, reason codes, return codes,
Successful and attempted linking of external funding accounts,
Attempted PII changes such as address and phone numbers changes.
Posted Jun 3, 2022
Updates to Identity Element Velocity for decisioning on shared identity elements
Alloy’s Identity Element Velocity feature offers clients the ability to decision off of identity elements when they are seen across multiple entities; for example, detecting identities that share a SSN or phone number, then taking subsequent actions—such as tagging it informationally, running additional services or determining an outcome.
New updates to Identity Element Velocity include:
The option to decision off of more identity elements, including email domain, mother’s maiden name and IP address.
The ability to add more than one PII element to an IEV rule for the same evaluation (while keeping entities, timeframe and velocity count the same). For example, detecting other entities that have used both the same SSN and device alias in an evaluation within a timeframe.
