AQuA KYC

One place where your bank talks to CKYC.

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

Three workflows, start to finish.

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.

SYNTHETIC CUSTOMERS · CKYCRR 2.0 SIMULATORBuilt to CERSAI API guide v2.1.
SEARCH AND DOWNLOAD · CKYC RECORDSIMULATED · SYNTHETIC DATA
RUNNING STEP 01 / 04
THE PROBLEM

A branch needs a customer record from the CKYC registry.

A branch officer looks a customer up by PAN. Watch the search, the consent the registry requires, and the trail it leaves.

↯KYC REQUESTBranch · Mobile · Lending● INPUT RECEIVED
    ✓HUMAN REVIEWOfficer decidesACCOUNTABLE
    ◫  EVIDENCE BOARD0 items
    Evidence appears here as each capability runs.
    ◉  NOW RUNNING01 / 04
    CAPABILITY

    Verification hub

    Take the request from whichever channel asked, in one format.

    EVIDENCE ATTACHED
    ▤  EXECUTION TRACEPROCESSING
    ✓ Synthetic data✓ Filed under your own registration✓ Nothing written without approval✓ Human sign-off before any action

    Three connections become one.

    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.

    Usually

    Three builds, three sets of security to keep up to date, three places for something to go quietly wrong.

    With AQuA

    One connection, made under your bank's own registration. Every channel asks the same way and gets the same answer.

    What your staff can do.

    Four things, from any channel.

    Find a customer

    Look someone up by PAN, Aadhaar, passport or CKYC number, and see every record the registry holds for them.

    Get their record

    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.

    Add a new customer

    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.

    Keep records current

    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.

    Three things your auditors will ask about.

    Each channel sees only what it should

    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.

    Nothing of the customer is kept

    Records pass through. No names, addresses, documents or photographs are stored by AQuA, and none appear in its logs.

    One trail of who did what

    Who asked, what permission was taken, who approved - written as the work happens, in one place, for when someone asks six months later.

    Where it stands.

    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.

    Going live.

    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.

    For your technology team
    Interface
    CKYCRR 2.0 REST, built to CERSAI's KYC API Integration & Client Onboarding Guide v2.1. Search, download with consent, create, update.
    Security
    Mutual TLS with your client certificate, OAuth client credentials, and every payload signed then encrypted (JWS over JWE, RS256 / RSA-OAEP-256 / A256GCM) using your keys and CERSAI's certificates.
    Identifiers accepted
    PAN, passport, voter ID, driving licence, Aadhaar, NREGA, NPR, CKYC number and CKYC reference. Several matching records are returned where they exist, each with its status.
    Consent routes
    One-time password to the registry-held mobile, face authentication, or signed physical form. The password is never stored or logged.
    Errors
    The registry's codes are mapped to plain outcomes - not found, rejected with a reason, temporarily unavailable - with safe retries and idempotency keys so nothing is filed twice.
    Deployment
    Java and PostgreSQL, hosted in India on infrastructure you approve, with the outgoing IP addresses CERSAI needs to whitelist for your institution.