Overview
7-domain risk intelligence with conservative merging logic
7-Domain Risk Model
- ✓ Cashflows: Salary hits, bounce patterns
- ✓ Bureau: CIBIL score, delinquency history
- ✓ KYC: Identity verification, address proof
- ✓ Device: Fingerprinting, integrity checks
- ✓ Behavior: Loan shopping, velocity signals
- ✓ Sector: Employment stability, industry risk
- ✓ Concentration: Portfolio exposure, guardrails
Conservative Merge Logic
When Dual mode is active, RiskCore executes both Structured and Reasoning engines in parallel, then merges results conservatively:
- ✓ Score: min(Structured, Reasoning)
- ✓ Band: Worse of the two (e.g., A vs B → B)
- ✓ Reasons: Union of both sets
- ✓ Recommendation: Conservative escalation
Tech Stack
Engine selection and execution architecture
Adaptive Engine Routing
RiskCore intelligently selects the best engine(s) based on request constraints:
Structured Engine
- → Schema-locked JSON extraction
- → Strict field validation
- → Fastest execution (typ. 800-1200ms)
- → Best for: High-volume, deterministic scoring
Reasoning Engine
- → Counterfactual reasoning
- → Band smoothing & edge case handling
- → Explainability-first approach
- → Best for: Complex cases, appeals
Dual Mode (Business Critical): Runs both engines, merges conservatively.
Adds ~500ms latency but maximizes safety.
Data Flow
End-to-end underwriting pipeline
Underwriting Data Flow
flowchart LR
A[Bank/CIBIL/KYC/Device] --> B(Feature Builder)
B --> C{Adaptive Router}
C -->|Structured| D[Structured Engine]
C -->|Reasoning| E[Reasoning Engine]
C -->|Dual| D
C -->|Dual| E
D --> F[Merging Logic]
E --> F
F --> G[Explainable JSON]
G --> H[Decision: Approve/Review/Reject]
Model Lifecycle
Versioning, registry, and deployment
Model Lifecycle Sequence
sequenceDiagram
participant DS as Data Science
participant API as API Gateway
participant Repo as Model Registry
participant Router as Router
DS->>Repo: Register model vX
API->>Router: Request underwriting
Router->>Repo: Resolve best model
Router-->>API: Route + constraints
API-->>Client: Response + trace
Interactive Demos
Explore risk calculations in real-time
MOCK mode uses simulated responses. LIVE connects to localhost:3002.
Benefits Matrix
Value for NBFCs and borrowers
For NBFCs
- Faster approvals (seconds vs minutes)
- Lower default risk through conservative merges
- Audit-ready explanations for every decision
For Borrowers
- Transparent decisions with clear reasoning
- Fair terms based on comprehensive analysis
- Speed and clarity throughout application
Frequently Asked Questions
How fast is RiskCore?
Typical response times are 1.5–2.0 seconds for most payloads. Structured Engine alone can respond in under 1 second.
What if JSON must be strict?
Structured Engine is prioritized when strict JSON validation is required. Dual mode is only used for business-critical requests.
Can I customize the risk model?
Yes. Domain weights, band thresholds, and merge policies can be configured per NBFC based on their risk appetite and portfolio characteristics.