Go-live readiness

White-Label Policy Checklist

Publish the right legal and trust pages on your brand before retailers go live — privacy, terms, refund, grievance and accurate Bharat Connect / NPCI wording.

White-Label Policy Checklist

OptionPay IT Solutions Private Limited provides software. This site does not claim an RBI Payment Aggregator licence, Payment Bank licence, NPCI membership, or Bharat Connect COU/BOU status. Bill pay, AEPS, UPI and related rails run through authorised banks and scheme participants. Licensing for your model is confirmed in writing during onboarding.

6Core policies
TATGrievance SLAs
MarksClaim hygiene
BrandYour domain
Interactive

Your go-live checklist

Tick items as you publish them on your brand. Progress saves in this browser.

0%0 / 8 done
  • Privacy policy on your brand domain

    DPDP-aligned notice with your entity contacts — not a copy of another brand.

    OptionPay privacy →
  • Terms of service published

    Cover platform use and technology-vs-licence boundaries.

    Terms framework →
  • Refund / cancellation policy

    SaaS and fee rules — avoid e-commerce “returns” language.

    Refund policy →
  • Grievance officer + TAT live

    Named officer, channels, acknowledgement and resolution timelines.

    Grievance page →
  • Cookie notice & consent

    Banner + policy; analytics only after Accept all.

    Cookie policy →
  • Bharat Connect / NPCI claim hygiene

    Accurate naming; never imply COU/BOU or RBI licences you do not hold.

    Bharat Connect notes →
  • Footer & onboarding links wired

    Every consumer/partner journey can reach privacy, terms and grievance.

    Policy checklist →
  • KYC / go-live pack ready

    Entity docs and diligence pack before production modules.

    Due diligence pack →
Book demo
Guidelines

What this page covers — and what it does not

Practical alignment with Indian payment and data-protection expectations. Licences stay with authorised entities named in your contracts.

IT Act 2000 & DPDP 2023

Privacy and security notices should reflect Indian law: reasonable security practices, lawful processing of personal data, and a path for access / correction / grievance.

RBI-facing wording

Do not claim “RBI approved” unless you hold the relevant licence. Describe technology vs aggregator / BC roles accurately.

NPCI / Bharat Connect wording

Do not imply OptionPay or a white-label brand is NPCI or a COU/BOU unless that entity is authorised. Link to scheme-accurate pages.

Must-publish pages

Privacy, terms, refund, grievance (with officer and TAT), cookies and acceptable use — on the domain customers and retailers actually use.

Capabilities

Controls that support regulated operations

Practical compliance tooling for onboarding, monitoring, documentation and partner accountability.

Privacy (DPDP-aligned)

Publish how you collect, use and retain partner and customer data on your domain.

Terms of service

Cover platform use, acceptable behaviour and technology-vs-licence boundaries.

Refund / cancellation

SaaS and platform fee rules — not e-commerce “returns” language.

Grievance + TAT

Named officer, channels, acknowledgement and resolution timelines.

Cookies & AUP

Cookie notice plus acceptable use for APIs and agent networks.

Bharat Connect / NPCI copy

Accurate naming and COU/BOU disclaimers — never imply licences you do not hold.

How it works

A clear path from onboarding to ongoing review

Each step is designed so compliance owners, ops teams and partners know what is required before production access.

  • Policies must match your operating model and partner agreements
  • Marketing badges cannot invent RBI or NPCI membership
  • Grievance TATs should be operationally achievable
  • OptionPay can supply frameworks; you remain the publishing entity
01

Draft on brand

Adapt OptionPay policy frameworks to your legal entity and support contacts.

02

Legal review

Have counsel confirm licence claims, retention and grievance officer details.

03

Publish & link

Footer, checkout/onboarding and app store listings must reach the live pages.

04

Go-live gate

Enable production modules only after policies and KYC gates are complete.

FAQ

Common compliance questions

Can we copy OptionPay policies as-is?

Use them as a starting framework, then replace entity name, contacts, licence statements and product scope with your own legal review.

Do retailers need these pages?

White-label brands and consumer-facing apps typically must publish privacy, terms and grievance paths. Retailer-only panels still benefit from clear partner terms.

Ready to go live — or to build software?

Book a distributor demo for BBPS, AEPS and partner panels. Book an IT consultation for a website, app or custom system.

Chat with usRequest Demo