Yes. PRAMAAN checks require the person being verified to see the purpose and consent before processing.

Views are role-scoped and should prefer signals or verdicts over raw identity documents.

What if consent is refused?

The PRAMAAN check does not run. The requester should use a documented manual process.

Does PRAMAAN guarantee the decision?

No. PRAMAAN provides verification signals for human review and does not guarantee future behaviour or legal outcomes.

Where are support and rights routes?

Support, DSR, correction, and grievance routes are linked through the Trust and legal pages.

The page shows public pricing only where currently supported; otherwise it uses pilot, waitlist, or custom-contract language.

R5 federation oversight review

Federation oversight with consent proof

PRAMAAN can support scoped federation and association workflows with aggregate verification visibility, member-held detail, and documented consent boundaries.

Start federation review See enterprise tier

R5 reviewCustom scopeAggregate reportingMember-held detailNo mandate claimNo raw PII by default

Sample preview — no real PII

Aggregate federation dashboard

Member orgs

Scoped members

Aggregate

Coverage

Status bands

No raw PII

Review queue

Member-held detail

Scoped escalation

Consent proof

Available per org

Boundary documented

Dummy aggregate data. This is not a regulator mandate or government approval claim.

Custom

Published entry path

Shown only where the public pricing source supports it.

Rollout stage

Pilot, waitlist, and target capabilities stay labelled.

Consent

Processing posture

Federation scope, support, exports, branding, and public-sector handoff require signed agreement.

Audience stakes

Oversight bodies need aggregate visibility without becoming a shared PII warehouse.

The redesign makes every page explain the buyer's operational world before asking for a conversion.

Workflow pressure

Regulators users need verification that fits the way they already operate.

Consent pressure

The person being verified must see the purpose and consent before processing starts.

Evidence pressure

Teams need a readable signal and audit trail without exposing more PII than required.

Specialized module

Federation oversight model

Aggregate verification visibility for federations, associations, and oversight bodies without raw PII by default.

Regulators teams

Operations owners

Compliance reviewers

People being verified

Who this is for

Role-based trust, not one generic buyer.

Each stakeholder gets the decision surface they need while the person being verified keeps consent and rights visible.

Regulators owner

Risk, time, and decision clarity

PRAMAAN view: Status, consent, and exception queue.

Person being verified

Purpose, control, and correction

PRAMAAN view: Consent notice, report visibility, support and DSR routes.

Reviewer

What to do with an incomplete signal

PRAMAAN view: Review-needed state and responsible-use notes.

Workflow

Request, consent, signal, review, and audit stay connected.

The person being verified sees the purpose before checks run; the operator receives a decision-support signal and escalation path.

Request1
Choose the purpose
The workflow starts with an explicit purpose and requester role.
Consent2
Subject consents or declines
The person sees the purpose, support route, and sharing boundary.
Review3
Reviewer sees permitted signals
Operational views prefer verdicts and status over raw identity documents.

Capabilities

Built around the segment's daily operating model.

Capabilities are useful only when the live/planned/target boundary is visible.

Workflow

Regulators workflow

A verification path shaped around this audience, not a generic form.

Consent

Consent record

Purpose, requester, timestamp, and support path are part of the result.

Access

Role-based views

Operators see the signal they need without default access to raw documents.

Review

Exception queue

Incomplete, disputed, or adverse signals route to manual review.

Status

Rollout clarity

Live, supported, planned, target, and by-agreement capabilities remain marked.

Guardrails

Responsible use

The page explains what PRAMAAN does not replace or guarantee.

Consent and DPDP

Consent and DPDP-native workflow

Each page keeps consent, purpose, minimization, DSR, support, and grievance paths visible.

Explicit consent before checks

Purpose shown before processing

Operational views prefer signals over raw documents

DSR, correction, support, and grievance routes visible

Sample preview

Aggregate federation dashboard

Every preview uses dummy, masked data and is labelled so it cannot be confused with a real report.

Sample preview — no real PII

Aggregate federation dashboard

Member orgs

Scoped members

Aggregate

Coverage

Status bands

No raw PII

Review queue

Member-held detail

Scoped escalation

Consent proof

Available per org

Boundary documented

Dummy aggregate data. This is not a regulator mandate or government approval claim.

Use cases

Specific workflows a buyer can recognize.

Primary workflow

Use PRAMAAN for the highest-frequency verification path.

Less document forwarding and clearer consent.

Exception review

Route amber, incomplete, or disputed signals to a human reviewer.

Better decisions without automatic rejection.

Renewal or expiry

Refresh signals when a badge, pass, or role context becomes stale.

No reliance on old screenshots.

Responsible use

Oversight boundaries

The page avoids implying official adoption, regulatory mandate, government approval, surveillance, or shared PII across members.

Aggregate reporting by default

Member opt-out and contract terms matter

No government-system integration claim

No raw PII across members without lawful basis and consent

Federation scope

Custom

Pricing, member coverage, exports, branding, support, public-sector handoff, and rollout terms require a signed federation scope.

No fixed public annual range
No member-count or outcome claim without approval
Government-class workflows move through R9 public-sector review

Federation review posture

Regulator and federation content is R5. Names, member counts, mandates, deployments, integrations, or outcomes are not published without approval.

Integration and operations

Federation rails

Only approved rails should be represented as available for a federation workflow.

Aggregate dashboard

By agreement

Member-held detail

By agreement

Evidence exports

By agreement

Branding

By agreement

Government handoff

Planned

Proof and pilot clarity

Proof and mandate posture

Federation workflows are R5. PRAMAAN does not claim an official mandate, live government approval, active federation deployment, or approved member count on this page.

FAQ

Regulators verification FAQ

Short, specific answers with consent, visibility, pricing, rollout, and limitation boundaries.

Related journeys

Move to the nearest workflow without losing context.

Societies

Replace your visitor-pass queue

Visitors

Society gate QR with consent

Government

Public-sector waitlist

Enterprise

Contract-scoped controls

TrustPrivacy Notice TrustConsent TrustDPA TrustSub-processors CommercialPricing CommercialContact sales HelpDPDP FAQ

Explore a federation-scoped verification review

Design aggregate oversight without collapsing member boundaries or implying an official mandate.

Start federation review Open trust center

Federation oversight with consent proof

Aggregate federation dashboard

Published entry path

Rollout stage

Processing posture

Oversight bodies need aggregate visibility without becoming a shared PII warehouse.

Workflow pressure

Consent pressure

Evidence pressure

Federation oversight model

Role-based trust, not one generic buyer.

Regulators owner

Person being verified

Reviewer

Request, consent, signal, review, and audit stay connected.

Choose the purpose

Subject consents or declines

Reviewer sees permitted signals

Built around the segment's daily operating model.

Regulators workflow

Consent record

Role-based views

Exception queue

Rollout clarity

Responsible use

Consent and DPDP-native workflow

Aggregate federation dashboard

Aggregate federation dashboard

Specific workflows a buyer can recognize.

Primary workflow

Exception review

Renewal or expiry

Oversight boundaries

Federation scope

Federation review posture

Federation rails

Proof and mandate posture

Regulators verification FAQ

Is consent required?

Who sees the data?

What if consent is refused?

Does PRAMAAN guarantee the decision?

Where are support and rights routes?

Is pricing live?

Move to the nearest workflow without losing context.

Explore a federation-scoped verification review