For fintechs & financial institutions
An online KYC form that never stores identity data in the clear
Collect identity documents, tax IDs, and address proof during onboarding through a branded form where every field is encrypted in the customer’s browser before it is sent.
Meridian Pay
Customer onboarding — KYC verification
Full legal name and date of birth
Government photo ID
encryptedUpload — passport, licence, or national ID
PAN / tax identification number
encryptedProof of address
encryptedUpload — utility bill or statement
Selfie for identity match
encryptedUpload
Source of funds declaration
Politically exposed person (PEP) declaration
Consent to identity verification and screening
Fields marked are encrypted in the browser before this form is sent.
The problem this solves
KYC onboarding pulls in the most sensitive bundle a business ever collects: government ID, PAN or tax number, a selfie or liveness capture, and proof of address. Any tool that can read that data at rest is a target.
KYC and AML obligations sit alongside data-protection duties — DPDP in India, GDPR in the EU — that expect this data to be genuinely secured, not just SSL-in-transit.
Why the encryption matters here
Every field and document is encrypted client-side with RSA-3072 and AES-256 before transmission. The key is generated in the customer’s browser and never sent to VerifID, so the platform cannot read an ID, a PAN, or a selfie.
Your compliance team decrypts with the key you hold. A breach of the form platform yields ciphertext, not a database of identity documents.
DPDP & GDPR: How zero-knowledge collection supports DPDP, GDPR, and PDPA obligations at once. Read more →
How it works
- 1
Brand the KYC form
Add your product branding and the identity fields your onboarding flow requires.
- 2
Embed or link it
Drop the form into your signup flow as an iframe, or send the link directly to the customer.
- 3
Verify with your key
Your compliance team decrypts submissions to run checks. Nothing was readable in transit or at rest by the platform.
Frequently asked questions
Can the KYC form be embedded in our signup flow? ▾
Yes. Published forms provide an iframe embed, so the KYC step can sit inside your own onboarding pages while still encrypting in the customer’s browser.
Does client-side encryption satisfy KYC record-keeping rules? ▾
KYC rules require you to obtain and retain the records; they do not require the records to be readable by a third-party platform. Encrypting client-side and holding the key yourself lets you meet retention duties while narrowing exposure.
How are documents deleted at the end of the retention period? ▾
Delete the encrypted submissions. Because only your team holds the key, destroying the key renders any residual copies permanently unreadable.
Can VerifID staff see uploaded IDs? ▾
No. The decryption key never leaves your control, so submission content is not readable by VerifID.
Build this form for your organisation
Start on the free plan, add your branding, and publish an encrypted version in minutes.