Payment Service Providers

🔍 Verification: Where applicable, confirm a technical/organisational mechanism exists to obtain verifiable consent from a parent before processing a child's personal data, with due diligence to confirm the parent is an identifiable adult (via reliable existing identity/age details, voluntarily provided details, or a virtual token via a Digital Locker service provider).

🔍 Verification: Confirm the organisation does not process children's personal data in a way likely to cause a detrimental effect on their well-being, and does not undertake behavioural tracking/monitoring or targeted advertising directed at children.

🔍 Verification: Determine whether any Data Principal is, or may be, under 18 years of age (a 'child' under Section 2(f)) - e.g., minor nominees/beneficiaries, guardian-operated minor accounts/policies, or joint applicants. If not applicable, mark this section Not Applicable and document the basis for that conclusion.

🔍 Verification: Where applicable, confirm due diligence is performed to verify a lawful guardian of a person with disability is validly appointed (by a court, designated authority, or local level committee) before obtaining their consent for processing.

🔍 Verification: Confirm consent capture is free, specific, informed, unconditional and unambiguous, involves a clear affirmative act (no pre-ticked boxes, no bundling consent to a loan/policy/account with consent to marketing), and is limited to personal data necessary for the specified purpose.

🔍 Verification: Confirm the mechanism to withdraw consent is comparably easy to the mechanism used to give it; confirm that upon withdrawal, processing based on that consent ceases within a reasonable time (including by Data Processors), without affecting the legality of prior processing or the continuation of the underlying contract (e.g., loan/policy) to the extent it relies on Section 7 rather than consent.

🔍 Verification: Review consent language, loan/policy/account-opening agreements and terms of use for clauses that would be invalid to the extent they infringe the Act/Rules or other law - e.g., purported waivers of the right to complain to the Board.

🔍 Verification: Confirm every consent request is in clear and plain language, offers English/Eighth Schedule language options, and provides the business contact details of the DPO (if applicable) or the person authorised to respond to Data Principal communications.

🔍 Verification: Confirm the organisation can produce evidence, for any Data Principal, that a compliant notice was given and that consent was validly obtained, since the Data Fiduciary bears the burden of proof in any Board proceeding.

🔍 Verification: Where the organisation relies on a Section 7 legitimate use (e.g., 7(a) voluntarily provided data for a specified purpose, 7(b) State-provided subsidy/benefit/service, 7(i) employment-related processing) instead of consent, document the specific limb relied upon and why - do not blend legitimate-use processing into general consent language.

🔍 Verification: If the organisation intends to route consent through a Consent Manager (including for Account Aggregator-linked financial data flows), confirm the Consent Manager is (or will be) registered with the Board once Rule 4 becomes active (13 Nov 2026), and that data-sharing arrangements with it are documented.

🔍 Verification: Identify every country/territory in which personal data is stored or processed, including cloud-hosting regions and offshore support/processing centres, and every foreign vendor/sub-processor involved.

🔍 Verification: The DPDP Act follows a 'restricted-country' (blacklist) approach, not a whitelist/adequacy approach - transfers are permitted by default except to countries or territories the Central Government specifically notifies as restricted. No such notification has been issued as of publication. Do not assume any particular country is either blocked or pre-approved; monitor for notifications.

🔍 Verification: Confirm contracts with foreign vendors/group entities receiving personal data address security safeguards, breach notification and data-return/deletion consistent with the organisation's own obligations under the Act.

🔍 Verification: Confirm a process exists to correct inaccurate/misleading data, complete incomplete data, update data, and erase data on request (unless retention is necessary for the specified purpose, an active contract, or legal/regulatory compliance).

🔍 Verification: Confirm a process exists to give a Data Principal, on request, a summary of personal data processed and processing activities undertaken, plus the identities of other Data Fiduciaries/Data Processors with whom it has been shared (subject to the law-enforcement-sharing carve-out in Section 11(2)).

🔍 Verification: Confirm readily available means of grievance redressal exist, and that Data Principals are informed they must exhaust this internal route before approaching the Board.

🔍 Verification: Confirm the website/app prominently publishes the means to make a rights request and the identifying particulars (customer/policy/account/folio number, email, mobile number, etc.) needed to verify the requester, and that requests are only actioned for Data Principals who previously gave consent to that Data Fiduciary.

🔍 Verification: Confirm a mechanism exists for a Data Principal to nominate another individual to exercise their rights in the event of death or incapacity.

🔍 Verification: Confirm requests are logged, tracked to resolution within a defined internal SLA, and that records are retained to demonstrate timely handling.

🔍 Verification: Confirm whether the organisation processes digital personal data of individuals within India, personal data collected in non-digital form and later digitised, or processes personal data of Data Principals in India from outside India in connection with offering goods or services to them. Confirm whether any processing falls under the personal/domestic-purpose exclusion or the publicly-available-data exclusion under Section 3(c).

🔍 Verification: For each processing activity, determine whether the organisation determines the purpose and means of processing (Data Fiduciary) or processes personal data on behalf of another entity (Data Processor) under a contract. An organisation can be both, for different activities.

🔍 Verification: Before assessing any other control, produce a first-pass map of what personal data is processed, for what purpose, and by which function - this map is the basis for the Data Inventory section below and for every subsequent control.

🔍 Verification: Nominate an accountable owner (formal Data Protection Officer if a Significant Data Fiduciary; otherwise a designated privacy/compliance owner) with authority to run this programme, coordinate with IT/HR/Legal/Vendor Management, and respond to Board or Data Principal communications.

🔍 Verification: Document an internal policy covering notice/consent standards, security safeguards, breach response, retention/erasure, Data Principal rights handling, and vendor management, consistent with this checklist.

🔍 Verification: Because the Act and Rules commence in phases (13 Nov 2025 / 13 Nov 2026 / 13 May 2027) and several matters are pending further Central Government notification (e.g., cross-border restricted-country list, Significant Data Fiduciary designation, data-localisation categories), assign someone to monitor the Official Gazette and MeitY announcements and update this checklist accordingly.

🔍 Verification: Confirm the business contact information of the DPO (if applicable) or another person able to answer Data Principal questions about processing is prominently published on the website/app, and included in every response to a rights-related communication.

🔍 Verification: Confirm an effective mechanism exists to redress Data Principal grievances relating to processing of their personal data specifically (as distinct from, and in addition to, any sectoral customer-grievance or ombudsman mechanism already in place).

🔍 Verification: Confirm the published grievance-response timeline does not exceed the period prescribed for the relevant class of Data Fiduciary, and that operational capacity exists to meet it.

🔍 Verification: Maintain a log of grievances received, actions taken, and time to resolution, including escalation where the internal route is exhausted and the Data Principal may approach the Board.

🔍 Verification: Verify every consent-seeking notice discloses, in clear and plain language: (a) an itemised description of the personal data being collected; (b) the specified purpose(s) and specific description of the goods/services or uses enabled; (c) how to exercise rights under Section 6(4) and Section 13; and (d) how to complain to the Board.

🔍 Verification: Confirm the notice can be understood on its own, without needing to cross-refer to other documents (e.g., a separate terms-of-service, loan agreement, or policy wording) to make sense of what is being collected and why.

🔍 Verification: Confirm the onboarding/application workflow shows the notice to the Data Principal at or before the point consent is sought - not buried afterwards, in fine print, or only on request.

🔍 Verification: For Data Principals who gave consent before the relevant provisions commenced (e.g., existing customers/policyholders/account holders), plan to notify them, as soon as reasonably practicable after commencement, describing the personal data and purpose of processing, their rights, and how to complain to the Board. Consent given earlier remains valid until withdrawn.

🔍 Verification: Confirm the Data Principal has the option to access the notice in English or any language listed in the Eighth Schedule to the Constitution of India, at least on request.

🔍 Verification: Confirm the entire data relating to a payment transaction is stored only in a system located in India; where a foreign leg is involved, confirm that data is deleted from systems abroad within the RBI-prescribed period after processing and that only the domestic copy is retained on an ongoing basis. Treat this as a live, currently-enforceable RBI obligation, independent of the DPDP Act's own (not-yet-notified) cross-border transfer restrictions.

🔍 Verification: Confirm actual card numbers (PAN) are not stored by the entity where prohibited by RBI's tokenisation framework, that card-on-file tokenisation is implemented where applicable, and that any permitted card-data storage meets PCI-DSS security standards - this operates alongside the DPDP Rule 6(1)(a) security-safeguard obligation for the same data.

🔍 Verification: Confirm the incident-response plan produces a single consistent fact set feeding both the shorter RBI/CERT-In incident-reporting timeline and the DPDP Rule 7(2)(b) 72-hour Board report, without treating one as automatically satisfying the other.

🔍 Verification: Where the entity is a Payment Aggregator, confirm merchant KYC data (business identity, beneficial ownership, bank account details) collected to meet PA-PG guidelines is subject to the same DPDP notice, security and retention controls as customer/cardholder data, since merchant representatives and beneficial owners are also Data Principals.

🔍 Verification: Where the entity processes cross-border payment transactions under the PA-CB framework, confirm the data-localisation and reporting requirements specific to cross-border payment aggregation are met, and that any resulting cross-border personal data flow is separately assessed against DPDP Section 16 once that provision commences.

🔍 Verification: Confirm personal/transaction data shared with issuing banks, card networks, or fraud-scoring vendors for risk assessment is limited to what is necessary, documented in the ROPA, and covered by appropriate contracts/lawful basis.

🔍 Verification: Given the very high volume of payment-transaction personal data typically processed, treat SDF designation as a plausible future outcome and consider voluntary readiness (DPO, audit, DPIA capability) ahead of any notification.

🔍 Verification: Confirm transaction-level personal data associated with escrow/nodal account settlement flows (payer/payee identity, amounts, timing) is access-controlled and retained consistently with both RBI settlement-reconciliation requirements and the DPDP retention schedule.

🔍 Verification: Confirm authentication data captured for e-mandates/standing instructions (registration, pre-debit notification acknowledgements) is retained only as long as needed for dispute resolution and audit, consistent with the DPDP retention principles.

🔍 Verification: Confirm an incident-response process exists to detect a personal data breach and escalate it internally without delay to the accountable privacy/security owner.

🔍 Verification: Confirm the breach-notification template covers: description of the breach (nature, extent, timing), consequences relevant to the Data Principal, mitigation measures taken/being taken, safety measures the Data Principal can take, and business contact details for queries - and that it can be delivered via the Data Principal's user account or registered communication channel without delay.

🔍 Verification: Confirm a process exists to intimate the Board without delay of the breach's nature, extent, timing, location of occurrence and likely impact upon becoming aware of it.

🔍 Verification: Confirm a process exists to provide the Board, within 72 hours of becoming aware of the breach (or such longer period as the Board allows on written request): updated/detailed description, facts/circumstances/reasons, mitigation measures, findings on the cause, remedial measures taken, and a report of the intimations given to affected Data Principals.

🔍 Verification: Confirm all actual and suspected breaches are logged in a central register with timeline, actions taken, and outcomes, and that relevant forensic evidence is preserved for investigation.

🔍 Verification: Where the organisation is separately required to report cyber incidents/breaches to a sector regulator or CERT-In, confirm the DPDP breach workflow and the sectoral incident-reporting workflow are coordinated so timelines and facts are consistent across both filings.

🔍 Verification: Document, per processing activity: categories of personal data processed, categories of Data Principals, purpose, and source of collection (direct from Data Principal, third party, public record, etc.).

🔍 Verification: For each processing activity in the ROPA, record whether the lawful basis is Data Principal consent (Section 6) or one of the 'certain legitimate uses' (Section 7, e.g., voluntarily provided data for a specified purpose, employment purposes, compliance with law, medical emergency). Do not default every activity to 'consent' - Section 7 uses have distinct conditions.

🔍 Verification: Identify which systems (core banking/policy admin/trading systems, CRM, cloud storage, on-prem servers, email) store each category of personal data, and which internal roles/departments have access.

🔍 Verification: List every third party (Data Fiduciary or Data Processor) that receives personal data, including technology vendors, KYC/verification agencies, credit bureaus, reinsurers, auditors, and group companies, and note the country/jurisdiction in which each holds or processes the data.

🔍 Verification: For each data category, record the intended retention period, the event that triggers deletion (purpose fulfilled, consent withdrawn, statutory retention period under another law), and whether the organisation falls within any class specified in the Third Schedule to the Rules.

🔍 Verification: Confirm engagement of a Data Processor for any activity related to offering goods/services to Data Principals is under a valid written contract, since the Data Fiduciary remains responsible for compliance regardless of any contrary agreement (Section 8(1)).

🔍 Verification: Confirm DPAs require the processor to notify the Data Fiduciary promptly of any personal data breach, with enough detail to allow the Data Fiduciary to meet its own Board/Data Principal intimation timelines.

🔍 Verification: Cross-check the vendor list (core system providers, cloud hosting, KYC/verification agencies, collections agencies, marketing platforms, IT support, auditors, etc.) against the personal-data map to identify every processor handling personal data on the organisation's behalf.

🔍 Verification: Confirm DPAs contain appropriate provisions requiring the processor to take reasonable security safeguards and maintain confidentiality, and address sub-processor engagement and oversight - particularly for outsourced/offshored processing, consistent with applicable outsourcing directions of the sector regulator.

🔍 Verification: Confirm DPAs require the processor to erase personal data made available to it when the Data Fiduciary is required to erase it (on consent withdrawal or purpose fulfilment), unless retention is required by law.

🔍 Verification: As good practice supporting the Section 8(5) security obligation (and typically required separately under sector-regulator outsourcing norms), assess a vendor's security posture before onboarding and periodically thereafter.

🔍 Verification: Confirm personal data is erased once the Data Principal withdraws consent, or once it is reasonable to assume the specified purpose is no longer being served, unless retention is necessary for compliance with law (including sectoral record-retention directions - see industry-specific section).

🔍 Verification: Confirm that when the organisation is required to erase personal data, it also causes each engaged Data Processor to erase the personal data made available to it for processing.

🔍 Verification: Confirm a retention schedule exists mapping each data category to a retention period justified by either ongoing purpose or a specific other-law requirement, reconciling any tension between DPDP erasure triggers and mandatory sectoral record-keeping periods (see industry-specific section), and that deletion (including from backups, where feasible) is actually carried out on schedule once permitted.

🔍 Verification: Rule 8(3) requires a Data Fiduciary to retain personal data, associated traffic data and other processing logs for a minimum of one year for the purposes specified in the Seventh Schedule, after which they must be erased unless further retention is required by law. Confirm scope with counsel rather than assuming it does or does not apply.

🔍 Verification: Confirm appropriate data security measures are in place, such as encryption, obfuscation, masking, or use of virtual tokens mapped to personal data, at a minimum - particularly for financial identifiers, government ID numbers and account/policy numbers.

🔍 Verification: Confirm appropriate measures control access to the computer resources used to process personal data (role-based access, least privilege, dual control for sensitive financial data, authentication).

🔍 Verification: Confirm an overarching information-security programme documents the technical and organisational measures taken to ensure effective observance of the Act and Rules and prevent personal data breach.

🔍 Verification: Confirm appropriate logs, monitoring and review processes are in place to enable detection, investigation and remediation of unauthorised access.

🔍 Verification: Confirm reasonable measures (e.g., data backups) exist for continued processing in the event confidentiality, integrity or availability of personal data is compromised through destruction or loss of access.

🔍 Verification: Confirm logs and personal data relevant to detecting/investigating unauthorised access and supporting continued processing are retained for at least one year, unless another law requires otherwise.

🔍 Verification: As best practice supporting the general security obligation (and typically also required under sector-regulator IT/cyber-security directions), run periodic vulnerability assessments/penetration testing and employee security-awareness training.

🔍 Verification: No general list of Significant Data Fiduciaries has been notified as of the publication date of this checklist. Monitor Central Government notifications, which will designate specific Data Fiduciaries or classes based on volume/sensitivity of data processed, risk to Data Principal rights, potential impact on sovereignty/integrity, risk to electoral democracy, security of the State, and public order. Given the volume and sensitivity of financial data typically processed, financial-sector entities are a plausible category for future designation - do NOT self-classify as an SDF without a notification or documented legal assessment.

🔍 Verification: If and when notified as an SDF, appoint a Data Protection Officer based in India, reporting to the Board of Directors or equivalent governing body, who acts as the point of contact for grievance redressal.

🔍 Verification: If and when notified as an SDF, appoint an independent data auditor to evaluate compliance with the Act.

🔍 Verification: If and when notified as an SDF, undertake a Data Protection Impact Assessment and audit at least once every 12 months, furnish a report of significant observations to the Board, and observe due diligence that algorithmic/technical measures (e.g., credit-scoring or fraud-detection models) do not pose a risk to Data Principal rights.