Fabric Release Notes | Version 6.3
Summary
This release introduces UIStream name-match fallbacks to prevent onboarding drop-offs, aligns the Credit Report API by adding 14+ retail fields, and launches OmniScore Advance, which surfaces raw digital, financial, and professional parameters alongside risk scores for transparent, consent-driven decision-making.
I. UISTREAM | Name Match Validation & PAN Upload Option
The UIstream: DIGILOCKER_AADHAAR_PAN flow is enhanced to handle edge cases where a full-name mismatch occurs during the initial PAN data pull. This update ensures that even if automated background retrieval fails due to a naming discrepancy, the onboarding process continues seamlessly by collecting manual inputs and performing high-precision validation.
Action Required: None. This is a non-breaking, optional enhancement enabled via enable_name_match set to true
Documentation: Refer to Product Documentation and API Reference .
II. Credit Report API Enhancements
Endpoint : v2/financial_services/credit_bureau/credit_report
Now includes missing retail-related fields. Key additions include totalIncome in Personal Info, an enquiries array, and 14 account-level fields such as pastDueAmount, writeOffAmount, and repaymentTenure, ensuring zero data loss.
Documentation: Refer to API Reference .
IV. Intrducing OmniScore Advance
OmniScore Advance to provide granular raw parameters alongside the standard risk scores. This update eliminates ambiguity by surfacing the specific data points that contribute to the final score.
Key Enhancements
- Granular Data Transparency: Surfacing raw parameters across digital, financial, and professional categories to back aggregate scores with quantitative evidence.
- Comprehensive Identity Mapping: Introduction of demographic data blocks and advanced phonetic/textual match scores for identity reconciliation across multiple registries.
- Enriched Sub-Score Attributes: Expanded visibility into platform footprint duration, account activity summaries, and verifiable career milestones for informed decision-making.
- Consent-Driven Retrieval: Mandatory consent flags and purpose statements in request payloads to ensure compliant and authorized access to enriched data.
Documentation : Refer to the API Reference
