- Start with the smallest tier that supports your real workflow.
- Do not go live until purpose, consent, billing owner, and support path are clear.
- API/webhook needs should be identified before production rollout.
- Enterprise support terms or custom terms exist only when contracted.
Overview
T1 Launch
Start small when your purpose, consent copy, and first workflow are clear.
T2 Growth
Use when more teams, repeat workflows, or society/business operations need structure.
T3 Advanced
Use when reporting, admin roles, or deeper workflow controls matter.
T4 Enterprise
Sales-assisted for procurement, legal review, higher volume, or custom review needs.
T5 Enterprise+
Use only where a custom enterprise scope is explicitly agreed.
Sandbox first
If API or webhook integration is needed, test sandbox before production access.
Best-fit starting points
Small business
Start with a self-serve tier when checks are low-volume and workflows are simple.
Society or RWA
Use a society-oriented plan when committee roles, worker onboarding, or vendor access need structure.
Staffing company
Review API, bulk, audit export, and consent-copy needs before selecting a tier.
Facility management
Map worker, vendor, and site workflows before requesting production access.
Marketplace or platform
Plan sandbox, webhooks, data minimization, and user support before launch.
Enterprise procurement
Use sales-assist for legal review, DPA, procurement, and custom terms.
Trial readiness checklist
- Verification purpose is defined.
- Consent copy is approved internally.
- Roles and admins are assigned.
- Billing contact is ready.
- API or webhook need is identified.
- DSR and grievance routes are understood.
Business verification flow
- 1Invite the subject for a stated purpose.
- 2Subject reviews notice and gives consent.
- 3Checks run through the guided flow.
- 4Admin reviews source-backed signals.
- 5Audit record is retained according to policy or contract.
- 6Unclear cases route to human review.
Frequently asked questions
Which tier should I start with?›
Start with the smallest tier that supports your workflow, volume, admin roles, and support needs. Use sales-assist when legal, procurement, or custom terms are involved.
Can I test before going live?›
Yes. Use demo, sandbox, or a limited pilot path before production workflows, especially for APIs and webhooks.
What is self-serve vs sales-assist?›
Self-serve is designed for standard plans and public checkout. Sales-assist is for enterprise review, custom terms, legal review, or higher-volume workflows.
Do I need API access?›
You need API access when verification must be triggered or tracked from your own product. Start with sandbox before production keys.
Can I bulk verify?›
Bulk verification should be used only when purpose, consent, roles, and support routes are designed for every subject.
What happens when we outgrow a tier?›
Move to the next plan or sales-assisted path after reviewing volume, controls, reporting, billing, and support needs.
Glossary terms
When to talk to a human
Talk to a human for procurement, legal review, DPA requests, enterprise pricing, or custom tier questions.
Keep raw identity data out of chat
Do not paste Aadhaar, PAN, OTPs, raw documents, full passport numbers, or sensitive screenshots into chat or free-text support fields. Use guided verification, DSR, dashboard, or API flows instead.
Was this helpful?
Feedback helps PRAMAAN improve support answers without collecting raw identity data.
Move safely from answer to action
Use the route that matches the sensitivity of your case. Keep raw documents out of support messages unless a controlled workflow asks for them.