Your branch, your app and your loan desk all need the same customer records. Today each one is wired to the registry separately. AQuA KYC does it once, for all of them.
AQUA KYC / WATCH IT RUN
Each one plays out step by step on a synthetic customer. Pause or replay at any point. Every run ends the same way - with a person deciding, not the software.
A branch officer looks a customer up by PAN. Watch the search, the consent the registry requires, and the trail it leaves.
Take the request from whichever channel asked, in one format.
Everything above is evidence and a proposal. Nothing has changed in any bank system.
The registry is strict about security and fussy about formats. Most banks do that work once per channel - and then wonder why three systems give three different answers about the same customer.
Four things, from any channel.
Look someone up by PAN, Aadhaar, passport or CKYC number, and see every record the registry holds for them.
The registry asks for the customer's permission first. AQuA handles that - a one-time password, a face check, or a signed form for customers with no mobile.
File someone who isn't in the registry yet. Mistakes are caught before anything is sent, and possible duplicates go to an officer to decide.
Periodic re-KYC, with the change going to the registry and to your own systems at the same time. The customer is asked once, not once per system.
The branch may need the full record. A customer-facing app does not. The loan desk can look up but not change anything. Set once, applied to every request.
Records pass through. No names, addresses, documents or photographs are stored by AQuA, and none appear in its logs.
Who asked, what permission was taken, who approved - written as the work happens, in one place, for when someone asks six months later.
Working today: finding customers, getting their records with a one-time password, Updates, face and signed-form permission and adding new customers to the registry. All of them are built and tested from end to end.
What "tested" means here: AQuA runs against a copy of the registry we built from CERSAI's own API guide, with the same security it uses. That proves the software against the published specification. Before going live it needs a run on CERSAI's testbed with your bank's registration in place.
The software is ready. Three things belong to you, because the regulator says so: your CERSAI registration, your certificates and registered IP addresses, and your own security review of any vendor in this position.
On our side, every build is scanned for code and dependency vulnerabilities before it ships, and security sits with our founder rather than being someone's side task.
Your bank is the Reporting Entity. Every call is made under your code, with your credentials. AssetQuant is the connection and never becomes a party to your filing. CERSAI registers Reporting Entities, not technology vendors - so no one can honestly claim to be a "CERSAI-certified" product, and we don't.