- Use the right purpose before starting.
- Get explicit consent through the guided flow.
- Pay only through PRAMAAN checkout surfaces.
- Escalate unclear, amber/red, or account-specific cases to human support.
Overview
No account required where supported
Some retail flows are designed for self-serve verification without a business contract.
Rs 99 where applicable
Use the public pricing page for current pricing and scope.
Explicit consent required
The check should not run unless the subject completes the consent flow.
Refund clock where eligible
Refund eligibility follows the published refund policy, not informal support promises.
Result delivery
Use the product flow and current settings for delivery channel; do not assume every channel is available.
Trust score/report
Read the report as source-backed signals and next steps, not an absolute guarantee.
Guided timeline
- 1Open /verify-anyone.
- 2Choose verification purpose.
- 3Complete DPDP consent.
- 4Pay through UPI/card where the flow requires payment.
- 5Receive the result or report through the supported channel.
- 6Escalate unclear results if needed.
How to read the result
- Trust Score: an explainable PRAMAAN signal, not a legal guarantee.
- Source-backed signals: what sources supported the result and where interpretation needs caution.
- Partner verification signals: checks completed through configured verification rails.
- Manual review: used where a match, source, or dispute should not be auto-decided.
- Amber/red outcomes: review next steps and use human handoff if unclear.
- What a result does not prove: it does not guarantee future conduct, employment suitability, or legal safety.
Safety checklist
- Get consent.
- Use the correct purpose.
- Do not upload irrelevant data.
- Do not forward raw documents in WhatsApp, screenshots, or groups.
- Do not treat a verification result as a legal guarantee.
Frequently asked questions
Do I need an account?›
Some T0 self-serve flows are designed without a business account. Use the current product flow as the source of truth.
What does Rs 99 include?›
Where Rs 99 applies, the pricing page explains the current scope. Business and enterprise workflows may differ.
Why is consent required?›
Consent makes the purpose, data use, result visibility, and rights path clear before verification processing.
How fast is the result?›
PRAMAAN is designed for fast self-serve checks, but do not treat speed language as a guarantee. Use the refund policy for eligible timing commitments.
What if the result is unclear?›
Use human handoff with the verification reference. Do not paste raw Aadhaar, PAN, OTPs, or documents into support.
What if payment succeeds but result fails?›
Use billing support with payment ID, verification ID, timestamp, and account contact details.
Glossary terms
When to talk to a human
Use human handoff for unclear results, billing-sensitive cases, legal questions, or account-specific verification issues.
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.