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.
Publish the right legal and trust pages on your brand before retailers go live — privacy, terms, refund, grievance and accurate Bharat Connect / NPCI wording.

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.
Tick items as you publish them on your brand. Progress saves in this browser.
DPDP-aligned notice with your entity contacts — not a copy of another brand.
OptionPay privacy →Cover platform use and technology-vs-licence boundaries.
Terms framework →SaaS and fee rules — avoid e-commerce “returns” language.
Refund policy →Named officer, channels, acknowledgement and resolution timelines.
Grievance page →Banner + policy; analytics only after Accept all.
Cookie policy →Accurate naming; never imply COU/BOU or RBI licences you do not hold.
Bharat Connect notes →Every consumer/partner journey can reach privacy, terms and grievance.
Policy checklist →Entity docs and diligence pack before production modules.
Due diligence pack →Practical alignment with Indian payment and data-protection expectations. Licences stay with authorised entities named in your contracts.
Privacy and security notices should reflect Indian law: reasonable security practices, lawful processing of personal data, and a path for access / correction / grievance.
Do not claim “RBI approved” unless you hold the relevant licence. Describe technology vs aggregator / BC roles accurately.
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.
Privacy, terms, refund, grievance (with officer and TAT), cookies and acceptable use — on the domain customers and retailers actually use.
Practical compliance tooling for onboarding, monitoring, documentation and partner accountability.
Publish how you collect, use and retain partner and customer data on your domain.
Cover platform use, acceptable behaviour and technology-vs-licence boundaries.
SaaS and platform fee rules — not e-commerce “returns” language.
Named officer, channels, acknowledgement and resolution timelines.
Cookie notice plus acceptable use for APIs and agent networks.
Accurate naming and COU/BOU disclaimers — never imply licences you do not hold.
Each step is designed so compliance owners, ops teams and partners know what is required before production access.
Adapt OptionPay policy frameworks to your legal entity and support contacts.
Have counsel confirm licence claims, retention and grievance officer details.
Footer, checkout/onboarding and app store listings must reach the live pages.
Enable production modules only after policies and KYC gates are complete.
Use them as a starting framework, then replace entity name, contacts, licence statements and product scope with your own legal review.
White-label brands and consumer-facing apps typically must publish privacy, terms and grievance paths. Retailer-only panels still benefit from clear partner terms.
Book a distributor demo for BBPS, AEPS and partner panels. Book an IT consultation for a website, app or custom system.