Skip to content
PramaanDPDP Live
Refund transparency

Refund and dispute paths stay evidence-based

The Rs 99 PRAMAAN Verified Check uses payment, consent, status, duplicate-payment, and support evidence to decide the right refund or dispute path.

Last reviewed
2026-06-08
Applies to
Rs 99 PRAMAAN Verified Check

Consent first

Refund and dispute evaluation never starts until the Data Principal gives explicit consent.

Payment captured

The Rs 99 payment must be captured successfully before a refund or dispute state can be evaluated.

Status evidence

PRAMAAN checks payment, consent, duplicate-payment, failed-payment, revocation, and reviewable-status events.

Support when needed

Some cases are system-led, while edge cases use the support path with an evidence reference.

Refund and dispute timeline

  1. 01

    Data Principal consent

    Explicit consent is captured for the verification purpose.

  2. 02

    Checkout and capture

    The Rs 99 payment capture event is linked to the verification reference.

  3. 03

    Check status updates

    The check moves through supported processing, reviewable, failed, duplicate, or revoked states.

  4. 04

    Outcome or support path

    The user receives status, support guidance, or a dispute route based on the evidence state.

  5. 05

    Refund evaluation

    Eligibility is evaluated and a refund instruction is generated where the supported conditions apply.

Eligible refund conditions

  • Rs 99 PRAMAAN Verified Check payment was captured successfully.
  • The Data Principal gave explicit consent.
  • The check did not reach a reviewable status because of a PRAMAAN-side processing, revocation, duplicate-payment, or supported failed-payment state.
  • The payment was not already refunded or reversed.
  • The request is not blocked by fraud, abuse, chargeback misuse, or legal-retention review.

Not covered by this policy

  • Consent decline or withdrawal before processing.
  • OTP, browser, app-store, bank, or payer-device delays before payment capture.
  • Report generated or status made reviewable before a supported refund condition applies.
  • Enterprise, society, household, API, or worker badge plans.
  • Abuse, fraud, chargeback misuse, or checks without a lawful purpose.

Evidence used for refund evaluation

Refund and dispute evaluation is based on operational evidence, not unsupported promises or informal goodwill approval.

Payment ID
Confirms the captured Rs 99 payment.
Verification ID
Links the payment to the PRAMAAN Verified Check.
Status events
Stores consent, processing, duplicate, failed, revoked, and reviewable status signals.
Refund instruction ID
Records the outbound payment instruction.

Refund FAQ

Do I need to contact support?
Some supported states are handled from system evidence, and some need a support request. Bank, app-store, and payment settlement timelines still apply.
What if the person refuses consent?
PRAMAAN does not run the verification. That follows the consent-decline, cancellation, or reversal path, not a completed-check refund promise.
Does the refund path apply to all plans?
No. This page covers the Rs 99 PRAMAAN Verified Check. Other plans follow their contract, invoice, app-store, or plan-specific terms.
Does a refund erase my data?
No. Refunds and data-rights workflows are separate. Use DSR for access, correction, erasure, grievance, or nomination requests.

The policy is narrow by design.

Start a PRAMAAN Verified Check, view live status, or contact support for payment questions outside the supported refund path.