Privileged checks,inside the lender's boundary.
Privileged rails like CERSAI, AA/FIU, CKYC and GeM/PFMS need the lender's own credentials and IP — they can't be handed to a third party. AssureConnect runs them inside the lender's boundary; raw payloads never leave it, and AssureLocker receives only the coded signal, masked summary and provenance hash.
The registries bar third-party credential sharing — so we don't try.
CERSAI (and CKYCR, which it operates) prohibit credential sharing and pass-through, and require a unique IP per Reporting Entity. Account Aggregator fetches run under the lender's own FIU. The compliant design isn't to hold those credentials centrally — it's to run the check at the lender and return only the result. That's AssureConnect, and it's what makes the lender-side signals in our packs possible.
The connectors
CERSAI
Id-Based Search for prior charges / double-financing on a receivable — run under the lender's CERSAI membership.
CKYC
CKYCR identity lookup (operated by CERSAI) — same Reporting-Entity rules; lender-run, signal back.
Account Aggregator
Consent-gated cashflow via the lender's own FIU — aggregates only; the raw FI payload is discarded.
GeM / PFMS
Government-buyer signals through the lender's connector — repayment-source certainty for public buyers.
How a check runs
Deploy in the lender's VPC
AssureConnect runs as a connector inside the lender's own environment, holding the lender's credentials, DSC and registered IP. No raw registry records, FI payloads, credentials, DSCs or keys leave the lender boundary.
Run the privileged check there
When a deal needs CERSAI / AA / CKYC / GeM, the call is made by the lender's connector under the lender's identity — never by AssureLocker.
Return a signal, not a record
The connector posts back only a binary/coded signal + a masked summary + a provenance hash. AssureLocker never receives raw registry records or credentials.
Hardened egress (HTTPS-only + SSRF guard + optional mTLS), per-lender DEMO→LIVE gating, and an append-only audit on every live, credential-bound pull.
A messaging layer — not a data store.
AssureConnect is stateless — each check is an independent, credential-bound message. It does not warehouse your data, so it adds no new storage footprint and no new data-custody or security liability. It rides on the credentials and infrastructure you already run.
Processed, then discarded
Raw registry records and FI payloads are processed in-memory inside your environment and dropped. They never persist and never cross the boundary.
Kept: signals + hashes only
What remains is kilobytes, not gigabytes — the coded signal, a SHA-256 provenance hash, and a thin append-only audit line (time, check, result). Account Aggregator keeps only derived aggregate bands, never raw FI data.
Nothing centralised
AssureLocker holds no copy of your raw records or credentials — only the signal + provenance hash that crosses the boundary. There is no central data lake to secure.
AssureConnect powers the privileged signals in every deal.
In the PO and invoice-factoring assessment rooms, the tripartite journey runs the data engine, the borrower interrogator, the analysis engine and the report writer — and when a step needs CERSAI, AA, CKYC or a government-buyer check, AssureConnect runs it lender-side and returns the signal into the pack. The lender sees one coherent, evidence-tiered Risk Signals / Verified Receivables Pack; the privileged data never leaves their boundary.
AssureLocker is a Technology Service Provider. AssureConnect carries signals, never credentials or raw records; the lender owns the credit decision.
Keep your credentials. Get the signals.
What AssureLocker does not do
- Lend, or guarantee any financing outcome
- Hold or move funds, or operate escrow
- Set advance rates or make the credit decision
- Broker loans or act as a recovery agent
Signals and evidence only — the lender’s system of record makes the credit decision and disburses.
Design-partner programme
Shape it on real deals
A closed programme for NBFCs, banks and supply-chain financiers — influence the signals and thresholds, run a controlled pilot on a ring-fenced deal set, and get preferential early-partner terms.