How Cortex works
Cortex separates policy configuration from per-application processing. Stage 00 establishes how a tenant evaluates risk; stages 01–05 apply that configuration to every application.
00 · Merchant Activation​
The merchant defines four governing artifacts:
| Artifact | Purpose |
|---|---|
| Common Information Model (CIM) | Provides the canonical applicant schema used after normalization. |
| Credit Risk Framework | Defines score categories and the maximum point budget for each category. |
| Risk modelling | Assigns weights to factors such as income, affordability, overdue days, and repayment performance. |
| Rules | Enforces hard policy thresholds regardless of the computed score. |
Activation can be established during onboarding and deliberately tuned as the portfolio and risk appetite evolve.
01 · Origination​
Origination is the front door. It captures application data from channels such as APIs, file uploads, and partner feeds. Its job is to collect the record, not judge it.
02 · Ingestion​
Ingestion is the secure gateway and provenance boundary. Each source is signed and tagged to its tenant so downstream stages know who owns the record and where each input came from.
03 · ETL​
ETL transforms structured and unstructured inputs—including form data, statements, and bureau reports—into a schema aligned with the CIM and the tenant's risk policy.
Optional EDA Store​
Low-confidence or unparsed data can be parked in the Exploratory Data Analysis Store for review. This prevents uncertain extraction from being silently presented as a trusted value.
04 · AIOps​
AIOps converts normalized data into analytical features. More than 60 risk signals can cover areas such as income, income stability, affordability, credit exposure, repayment performance, and source reconciliation.
05 · Actionable Intelligence​
The decision engine applies the configured framework and rules to the enriched record. It returns the TrustScore, category breakdown, attributed reasons, risk factors, recommendation, confidence, conditions, explanation, and override trail.
The outcome can then be delivered to the lender and used to coordinate approved-credit actions.
Continue to decisions and actions.