Waitlist
Published entry path
Shown only where the public pricing source supports it.
R8 waitlist for NRIs managing trust from abroad
Coordinate India-side consent from abroad
PRAMAAN is scoping NRI-initiated workflows where the India-side person sees the purpose, consents in India, and any remote sharing is limited to the approved product and policy scope.
R8 waitlistIndia-side consentRemote requesterNo country guaranteeNo payment promiseNo sharing guarantee
Sample preview — no real PII
Remote verification request preview
Requester
NRI family · Dubai
Masked sampleSubject
Caregiver · Bengaluru
India-side consent pendingAllowed signal
Identity/address status
Purpose-limitedRemote view
Limited status
Requires approved scopeCross-border sharing depends on product availability, policy, consent scope, and legal review.
R8 waitlist
Rollout stage
Pilot, waitlist, and target capabilities stay labelled.
Consent
Processing posture
Countries, payments, family sharing, documents, support, and cross-border sharing require approved scope.
Audience stakes
NRIs need India-side trust workflows without overstating cross-border data rights, payment coverage, country availability, document access, or consent delegation.
The redesign makes every page explain the buyer's operational world before asking for a conversion.
Workflow pressure
NRI 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
NRI trust-from-abroad workflow
Waitlist-only coordination for India-side caregiver, tenant, property staff, and home-service verification workflows.
NRI 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.
NRI 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.
NRI workflow
A verification path shaped around this audience, not a generic form.
Consent record
Purpose, requester, timestamp, and support path are part of the result.
Role-based views
Operators see the signal they need without default access to raw documents.
Exception queue
Incomplete, disputed, or adverse signals route to manual review.
Rollout clarity
Live, supported, planned, target, and by-agreement capabilities remain marked.
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
Remote verification request preview
Every preview uses dummy, masked data and is labelled so it cannot be confused with a real report.
Sample preview — no real PII
Remote verification request preview
Requester
NRI family · Dubai
Masked sampleSubject
Caregiver · Bengaluru
India-side consent pendingAllowed signal
Identity/address status
Purpose-limitedRemote view
Limited status
Requires approved scopeCross-border sharing depends on product availability, policy, consent scope, and legal review.
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
Cross-border data guardrails
Use cautious wording for data transfer, payment rails, document support, and remote sharing; do not cite statutory transfer rules unless legally reviewed.
Subject consents in India
Country availability requires approval
Family sharing is live only where implemented
No guarantee that every report can be shared cross-border
NRI waitlist scope
Waitlist
Pricing, payment rails, countries, document support, support hours, family viewers, and remote result views require approved NRI scope before launch.
- No fixed GA date or pilot size
- No country, payment, or document-access guarantee
- No guarantee that every report can be shared cross-border
NRI rollout review
R8 waitlist
NRI flows remain waitlist-only. Production timing, country availability, payment rails, document handling, family sharing, and remote result views are not claimed until approved.
Integration and operations
Operational model
Use dashboard and web flows first; connect APIs or webhooks only where supported by current implementation and agreement.
Hosted flow
Supported
Dashboard view
Supported
API / webhooks
Planned
Manual review
Supported
Proof and pilot clarity
Proof and NRI rollout posture
NRI workflows are R8 waitlist. PRAMAAN does not claim approved countries, cross-border payment rails, Aadhaar availability from abroad, fixed launch timing, pilot size, legal-transfer status, or remote result-sharing coverage.
FAQ
NRI verification FAQ
Short, specific answers with consent, visibility, pricing, rollout, and limitation boundaries.
Related journeys
Move to the nearest workflow without losing context.
Join the NRI verification waitlist
Coordinate India-side consent before any remote trust signal is shared.