T3 reviewed
Published entry path
Shown only where the public pricing source supports it.
R3 platform integration review
Verification APIs for Indian platforms
PRAMAAN helps marketplaces, gig platforms, aggregators, and classifieds scope consent-first onboarding flows with sandbox-first API, webhook, and hosted consent rails.
R3 reviewT3 reviewedSandbox firstWebhooks by scopeWhite-label by agreementNo speed or savings claim
Sample preview — no real PII
API and webhook flow preview
POST /verification_requests
worker_onboarding
Sandbox fixtureHosted consent
consent_url
Subject-controlledWebhook
verification.review_needed
Signed where supportedDecision
Platform policy engine
PRAMAAN is signal sourceNo API secrets shown. Production access requires approval and agreement.
R3
Rollout stage
Pilot, waitlist, and target capabilities stay labelled.
Consent
Processing posture
Pricing, rate limits, production access, white-label, webhooks, support, exports, and DPIA materials require signed scope.
Audience stakes
Platforms need predictable trust states in product flows, not PDF reports copied between ops tools.
The redesign makes every page explain the buyer's operational world before asking for a conversion.
Workflow pressure
Platforms 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
Platform API integration model
API and webhook-ready verification rails for Indian marketplaces, gig platforms, aggregators, and classifieds.
Platforms 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.
CTO
Reliability, idempotency, and security
PRAMAAN view: OpenAPI, sandbox, webhook signatures, audit events.
Trust and safety
Risk review and disputes
PRAMAAN view: Status taxonomy and manual review states.
Product manager
Onboarding conversion
PRAMAAN view: Hosted consent and clear status transitions.
Legal/privacy
Consent boundary and DPIA
PRAMAAN view: Purpose, consent artifact, and DSR routes.
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.
Platforms 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
Platform consent and event posture
Platform integrations must keep purpose, requester, data categories, hosted or embedded consent, downstream sharing, support, correction, DSR, grievance, and dispute routes visible.
Purpose and requester shown before processing
Hosted or embedded consent reviewed before production
Webhook and API events avoid raw documents by default
Refusal, dispute, correction, and manual review stay visible
Sample preview
API and webhook flow preview
Every preview uses dummy, masked data and is labelled so it cannot be confused with a real report.
Sample preview — no real PII
API and webhook flow preview
POST /verification_requests
worker_onboarding
Sandbox fixtureHosted consent
consent_url
Subject-controlledWebhook
verification.review_needed
Signed where supportedDecision
Platform policy engine
PRAMAAN is signal sourceNo API secrets shown. Production access requires approval and agreement.
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
Platform guardrails
Do not imply named platform integrations, government-system hooks, or unlimited production access.
No named platform compatibility unless implemented
Consent boundary remains hosted or explicit
Disputed verification needs review route
Rate limits and production access require agreement
Platform integration scope
T3 reviewed
Pricing, rate limits, production access, white-label, webhooks, support, exports, DPIA materials, templates, and rollout terms require a signed platform scope.
- No fixed public API tier volume or per-check rate
- No turnaround, savings, conversion, or fraud-reduction claim
- No named platform integration or pilot claim without approval
Platform integration review
R3
Platform workflows are R3. Named integrations, unapproved pilots, rate limits, volumes, turnaround, savings, conversion, fraud, or support outcomes are not published without approval.
Integration and operations
API capability grid
Only ship what exists or is approved; label everything else clearly.
OpenAPI docs
Supported
Sandbox fixtures
Supported
Webhook patterns
Supported
Rate limits
By agreement
White-label
By agreement
Proof and pilot clarity
Proof and integration posture
Platform workflows are R3. PRAMAAN does not claim unapproved marketplace pilots, named platform compatibility, production API throughput, fixed per-check economics, or onboarding-speed outcomes.
FAQ
Platforms verification FAQ
Short, specific answers with consent, visibility, pricing, rollout, and limitation boundaries.
Related journeys
Move to the nearest workflow without losing context.
Review a platform verification integration
Start with sandbox fixtures, then scope production access, consent handling, webhooks, support, and commercial terms with trust and privacy review.