TOKENISED · REUSABLE · RBI-ALIGNED

One KYC.
Every institution.
Zero re-submission.

Sovio Parichay turns a single verified KYC into a portable, consent-driven token — reusable across banks, fintech, insurance, telecom and travel. No repeated submissions. No data sprawl. RBI-aligned by design.

parichay.sovio.id / verify
v1.2
Home
Wallet
Issue
Share
Audit
Settings
Active token
Parichay Wallet
live
PARICHAY · KYC TOKEN
tok-a1b2c3
issuer
oid.sovio.bank.abc
valid until
2027 · 05 · 17
SignatureECDSA-P256 · valid
sha256:a1b2c3…a47btamper-evident
Built on regulatory frameworks — not proprietary protocols.

Aligned with the directions, standards and consent architecture your compliance team already trusts — across banking, identity and data protection.

RBI Master Direction · KYCReusable KYC Token SpecConsent FrameworkDPDP ActDigiLockerIT Act · Digital SignaturesISO 27001Data LocalisationCREDEBLRBI Master Direction · KYCReusable KYC Token SpecConsent FrameworkDPDP ActDigiLockerIT Act · Digital SignaturesISO 27001Data LocalisationCREDEBLRBI Master Direction · KYCReusable KYC Token SpecConsent FrameworkDPDP ActDigiLockerIT Act · Digital SignaturesISO 27001Data LocalisationCREDEBL
01 · The problem

KYC is repeated everywhere — and that is the failure.

01
The repetition tax
the average KYC submissions per customer per year

Every institution re-runs the same KYC the customer already passed.

A customer walks into a bank, submits PAN, Aadhaar and proof of address — and does the exact same dance at the next bank, the mutual fund, the insurance company. Each entity maintains its own verification pipeline, its own records, its own audit trail. The customer pays in time. The institution pays in cost.

02
The sprawl problem
blast radius across fragmented KYC stores

Storing personal documents in every silo turns each one into a breach surface.

Fragmented KYC creates parallel copies of PAN, Aadhaar and address proofs across dozens of databases — each a target, each a liability under DPDP. The fix is not better vaults. It is removing the need to copy at all.

How Parichay Works

Complete KYC once at any regulated institution

User completes full KYC — Aadhaar, PAN, address proof — at a bank, fintech or KYC-ULA. Standard RBI process, executed once.

This is the only time the customer submits raw documents.

04 · End-to-end flow

A bank account opened in twenty seconds. Zero re-submission.

  1. 00:00
    Priya walks in
    Priya enters a bank branch to open a savings account.
  2. 00:03
    Token requested
    The branch asks if she holds a Parichay token from any institution.
  3. 00:06
    Wallet opened
    Priya opens her wallet app — her mutual-fund issued token is listed.
  4. 00:09
    Consent granted
    She selects scope (KYC verification) and confirms the share.
  5. 00:12
    Signature verified
    The bank verifies the ECDSA signature against the issuer's public key.
  6. 00:16
    KYC accepted
    Bank confirms KYC type, freshness and subject binding. No re-submission.
  7. 00:20
    Account opened
    Audit trail closed. Tamper-evident. Regulator-ready.
05 · Why this is portable & private

Six guarantees. Not policy — properties.

  1. 01Personal data never leaves the issuing institution.
  2. 02Tokens are cryptographically signed and tamper-evident.
  3. 03Every share is governed by a revocable consent receipt.
  4. 04Verification is offline-capable — no issuer round-trip.
  5. 05Tokens are revocable by user or issuer; time-bound by default.
  6. 06Compliance is built-in: RBI Master Direction, DPDP Act, IT Act.
06 · Standards & protocols

Built on RBI directions and open identity standards.

Framework
Title
How Parichay applies it
RBI Master Direction
KYC
Compliance with video KYC, periodic updation and risk categorisation directions.
Reusable KYC Token
Token specification
Standardised token format from RBI's digital-identity working group — interoperable across entities.
Consent Framework
Account Aggregator-style receipts
Machine-readable, auditable, revocable consent for every token share.
DPDP Act
Data localisation & privacy
Personal data stays with the issuer. Token carries proof, not raw data.
IT Act · Digital Signatures
ECDSA-P256 on PKI
Signing conforms to applicable digital-signature frameworks (IT Act, RBI).
Audit & Reporting
Immutable ledger
Issuance, share, verification and revocation logged for regulator reconciliation.
CREDEBL
LF Decentralized Trust
Built on the open-source CREDEBL platform — no proprietary lock-in.

Reusable KYC engineered for every regulated institution.

08 · Technical depth

For architects, compliance leads and integration engineers.

parichay · token.jsonECDSA-P256
{
  "token_version": "parichay-v1",
  "issuer_id":     "oid.sovio.bank.abc",
  "subject_hash":  "sha256:a1b2c3...",
  "verification_jti": "7d295-8b-17f1d-3d-002",
  "kyc_type":      "full",
  "valid_until":   "2027-05-17T18:38:00Z",
  "signature": {
    "algorithm": "ECDSA-P256",
    "value":     "MEUCIQD..."
  }
}
// verify · POST /v1/parichay/verify
receiver = "bank.xyz";
ok = verify_signature(token, issuer_pubkey);
if (ok && fresh(token)) → ACCEPT KYC
else → REJECT (audit logged)
Verify
< 1 ms
offline-capable
Token
≈ 1 KB
self-contained
Issuers
Any RE
bank · fintech · ULA
Consent
Receipted
revocable · auditable
consent-driven sharing

Every token share emits a signed consent receipt — scope, purpose, duration, revocation. Issuer holds the data; user holds the token; receiver holds proof.

No central data store Cryptographic verification Revocable & time-bound Interoperable by spec
BUILD · SCALE · SECURE

See Sovio Parichay
in your ecosystem.

Schedule a personalised demo to see tokenised reusable KYC running in your environment.