Changelog
What’s new.
Platform and API updates. Sandbox and roadmap items are labelled as such.
- Platform
ULI interface — Verified Collateral Pack (lender-side consume)
A new AssureConnect capability that consumes a lender's own Unified Lending Interface (ULI) feeds — land records, registry and asset data the lender is already entitled to — to produce a Verified Collateral Pack and an Entity Asset-Backing VC alongside the existing receivables and PO evidence. Raw ULI data stays at the lender; the hub receives only the derived collateral signal and a verifiable hash, on a separate collateral axis from the trade-evidence packs. DEMO by default; live ULI access runs per pilot lender under the lender's own credentials and consent. Signals only — the credit decision stays with the lender.
- Platform
Evidence freshness layer — staleness detection and reuse policy
Each signal in a Risk Signals Pack now carries a verified-at timestamp and a freshness class (FRESH / AGING / STALE / EXPIRED) based on the signal type: registry lookups (GSTN, MCA21) refresh every 30 days, GST returns every 60, AA cashflow every 90, and static artefacts like e-Aadhaar on explicit re-verification. Stale signals block pack re-issuance; fresh signals are reused within their validity window — materially lowering the cost of Refresh-grade reused packs versus Complex ones. Freshness is displayed per-signal on the pack face and queryable via the /v1/factoring/:id/freshness endpoint.
- API
Verified Receivables Pack — invoice factoring
Assess a receivable on your own off-exchange book: a tiered evidence rail (e-invoice IRN, GST/e-way movement, party KYB, CERSAI charge + AA cashflow lender-side via AssureConnect, buyer confirmation) distilled into an Evidence Confidence Score, with a conflict engine weighting related-party, no-e-way and double-financing heaviest. Every status change notifies the parties over email + SMS + in-platform. Signals only — the lender decides.
- Docs
Developer hub, Trust centre & Postman collection
Public API reference (Swagger), a downloadable Postman collection, sample Risk Signals Pack JSON, webhook examples, error codes, and a Trust & Security page with live data-source rail status.
- API
Securitisation-evidence API
Read-only, API-key-gated endpoint exposing a deal's anchored, reconciled evidence + verifiable hashes to authorised consumers (PTC investor / co-lender / arranger). Evidence and hashes only — never value tokens.
- API
LMS adapter — decisions-in, signals-out
Signed (HMAC) webhook to ingest normalised LMS decision events, and a disbursement-ready packet endpoint for the lender's LMS to pull.
- Platform
e-Invoice connection (via GSP)
Fetch a customer's GSTN-signed e-invoices through a licensed GST Suvidha Provider — sanctioned and server-to-server — then cryptographically verify each against the official NIC key. No browser extension required.
- API
PO Risk Signals Pack — DEMO | LIVE
Three-party (Buyer→Borrower→Subcontractor) evidence pack with trade-relationship, related-party, subcontractor-capacity, double-financing, bank-cashflow (consent-based), e-invoice authenticity and counterparty-establishment signals. Deterministic sandbox mode for integration.
- Security
Post-quantum signing for long-lived records
Issuer-signed SD-JWTs, verification receipts and OID4VP requests now sign with ML-DSA-65 (NIST FIPS 204).