Alloy
Alloy Technical Briefing
Published September 28, 2021
Overview
Monica Murthy and Jason Ioannides of Alloy demo the Alloy identity decisioning platform — an "identity command center" financial institutions use to manage the customer lifecycle across fraud detection, KYC, AML, transaction monitoring, and (launching next month) credit underwriting. The briefing focuses on Alloy's onboarding product. At the core is the Alloy workflow — a visual no-code orchestration of 70+ third-party data sources (Iovation, LexisNexis, Socure, Ekata, ID Analytics, and more) that fan out from a single API call and return a consolidated approve/review/decline outcome. Compliance teams can edit rules in plain English (IF ID Analytics score ≥ 850 OR Socure Sigma Fraud ≥ 0.985), add entirely new data sources, and flip conditional-execution gates (skip KYC/AML on obvious frauds) — all from the UI, with version control, a change log, and role-based manual-review queues. Evaluation views expose every signal that fired and every raw data-source response for audit.
0:00 Introduction to Alloy — identity command center
Monica (partnerships lead) introduces Alloy — an identity command center for financial institutions. Alloy gives banks and fintechs a transparent, dynamic way to manage the customer lifecycle across fraud detection, KYC, AML, transaction monitoring, and credit underwriting.
1:30 Workflows — visual Alloy business logic
Jason Ioannides (solutions consulting) walks through Alloy's "workflow" — a visual representation of the Alloy API's business logic. A workflow orchestrates calls to many third-party data sources (Iovation, LexisNexis, Socure, Ekata, ID Analytics, and 70+ others) and resolves their outputs into tags and a final outcome.
3:00 Individual onboarding best-practices workflow
Tour of Alloy's "Best Practices for Individual Onboarding" starter workflow — a small cross-section of the 70+ integrated data sources, used for standard savings / DDA account onboarding by banks.
3:30 Rules as no-code conditional logic
Clicking into the "Fraud Warning" tag reveals a plain-English if statement: if ID Analytics ID Score ≥ 850 OR Socure Sigma Fraud Score ≥ 0.985, apply the tag. Swap data attributes (ID Analytics → Socure synthetic fraud), comparison operators, and thresholds in-UI — no engineering lift.
4:30 Add a new data attribute with no code
Adding an Ekata identity check score to the rule: select the Ekata node, connect it to the tag with OR, pick the identityCheckScore from the attribute dropdown, set the threshold. That's all the change management compliance teams need.
5:30 Conditional data-source execution saves money
Alloy can gate downstream calls on upstream outcomes — if Denied Fraud is set, skip LexisNexis Instant ID and the KYC/AML stack entirely. Fewer data-source calls on obvious frauds = material cost savings at scale.
6:30 Outcomes — approve, manual review, decline
Outcome logic: if denied_fraud is set, decline; else if the KYC checks pass, approve; else route to manual review. All editable in the same no-code UI.
7:00 Add an adverse-media data source in-UI
Live addition of LexisNexis World Compliance as an adverse-media data source: pick the service, wire it into the workflow, add a threshold rule (adverse_media_confidence_score ≥ 0.99), and tag the evaluation. End-to-end in under a minute.
8:00 Version control and change log
Saving a workflow produces a named new version (e.g. v325 → v337) with a human-readable change note and an auto-generated change log. Every historical version is browsable; saving does not auto-activate — flip the active flag manually.
9:30 Evaluation view — tag-by-tag breakdown
The Evaluations view shows per-customer outcomes with a tag-by-tag breakdown of which data sources matched which attributes. In this demo, Todd Spencer fails KYC on name mismatch via LexisNexis — the workflow routes him to manual review with the exact reason surfaced.
11:30 Manual review queue with role-based saved searches
Alloy's review queue supports saved searches (e.g. "KYC Reviews") that can be scoped to specific reviewer roles — KYC team sees KYC cases, loss-prevention team sees fraud cases. Individual reviews lock to a reviewer for 15 minutes and fire an outgoing webhook on status change.
Presented by Jason Ioannides and Monica Murthy — Alloy · website
Topics: Identity & KYC, Compliance & Regulation
