KYCKART
KYCKART Guide · November 2026Guide

Consent Management Platforms for DPDP: What BFSI Buyers Should Evaluate

Compare internal consent management platforms and DPBI-registered Consent Managers under India's DPDP Act, and evaluate seven key capabilities for BFSI.

calendar_monthNov 18, 2026
schedule8 min read
library_books12 Cited Sources
Consent Management Platforms for DPDP: What BFSI Buyers Should Evaluate

A consent management platform (CMP) is internal software a bank, NBFC, insurer, or fintech uses to show privacy notices, record consent, and stop processing on withdrawal. India's Digital Personal Data Protection (DPDP) Act does not require buying a CMP. It will, however, impose strict consent and proof duties from 13 May 2027. A CMP is separate from a Consent Manager, which is a third-party company registered with the Data Protection Board of India (DPBI).

Where things stand (November 2026)

  • •Consent Manager registration took effect on 13 November 2026, and dpbi.gov.in opened on 14 November 2026. No list of registered Consent Managers or final DPBI API spec was located as of 19 November 2026.
  • •Core Data Fiduciary duties, Data Principal rights, and penalty powers under the DPDP Act and Rules start on 13 May 2027.
  • •This article is for general information and is not legal, regulatory, tax, or compliance advice; its buyer criteria, comparisons, analysis, and FAQs are practical guidance rather than legal conclusions. Institutions should consult qualified legal or compliance counsel before making regulatory or procurement decisions.
  • 02

    Seven Capabilities BFSI Buyers Should Evaluate

    BFSI buyers should test any CMP against the consent, withdrawal, and proof duties starting 13 May 2027.

    The law does not mandate CMP software, though fiduciaries will face strict consent, withdrawal, and proof duties from May 2027. From May 2027, DPBI fines will reach up to ₹50 crore for notice, consent, or withdrawal breaches, up to ₹200 crore for children's-data or breach-notice failures, and up to ₹250 crore for weak security safeguards. See our DPDP compliance timeline.

    Assess vendors against seven features from the law and MeitY and the National e-Governance Division's (NeGD) non-binding Consent Management Systems blueprint (summarised by AZB & Partners):

    1. Standalone, multilingual notices.From May 2027, every consent request will need a plain notice separate from general terms (Section 5 and Rule 3), listing data, purpose, and withdrawal or complaint links in English or any of the 22 languages in the Constitution's Eighth Schedule.
    2. Granular consent and age checks. Consent will need to be free, specific, informed, unconditional, and clear. For children under 18 or persons with disabilities with a guardian, firms will need verifiable parental or guardian consent via tools such as DigiLocker-backed or government-verified tokens.
    3. Proof for DPBI audits. The burden of proof will sit on the Data Fiduciary in any DPBI dispute (Section 6(10)). Firms will need to prove notice text, language, and timestamp, and keep logs for at least one year.
    4. Easy withdrawal and processor sync. Withdrawing consent will need to be roughly as easy as giving it. Firms will need to stop processing within a reasonable time and make Data Processors stop, unless another law applies.
    5. Rights channels and 90-day grievances. Firms will need digital channels for access, correction, erasure, and nomination requests. Under Rule 14(3), grievances will need a response within 90 days.
    6. Retention and deletion triggers. Fiduciaries and processors will need to erase data on withdrawal or once the purpose ends, unless another law requires retention (Section 8(7)). Large e-commerce, social media (2 crore+ users), and online gaming firms will also face three-year inactivity erasure with 48-hour notice.
    7. API readiness and access controls. The non-binding NeGD blueprint highlights standard APIs, role-based access control (RBAC), preference dashboards, alerts, and immutable logs. Since no final DPBI Consent Manager API spec was located as of 19 November 2026, modular APIs matter.
    03

    Where a CMP Stops and BFSI KYC Systems Start

    A CMP tracks consent states and withdrawal signals, while KYC systems handle identity checks and statutory five-year financial retention.

    Two active laws require BFSI firms to keep core records even after consent withdrawal:

    • •PMLA retention: Under Section 12 of the Prevention of Money-Laundering Act, 2002 (PMLA), regulated entities must keep transaction records for five years, and identity and account files for five years after the relationship ends or account closes.
    • •RBI KYC retention: Under Chapter VII ("Record Management"), Paragraph 50 of the RBI Commercial Banks KYC Directions, 2025 (Commercial Banks version), banks must keep transaction records for five years and identity records for five years post-relationship. NBFCs follow the separate RBI NBFC KYC Directions, 2025, where paragraph numbers differ. Both replaced the repealed 2016 Direction.

    A CMP manages notices, consent records (consent artefacts), withdrawals, and rights workflows. It does not run Customer Due Diligence (CDD), verify Officially Valid Documents (OVDs), conduct video KYC (V-CIP), or govern KYC archives.

    BFSI buyers also face an open question on Account Aggregators (AAs). Per PRS Legislative Research, RBI-regulated NBFC-AAs work only inside finance on Reserve Bank Information Technology (ReBIT) APIs (₹2 crore net-owned-fund baseline), routing data blind between Financial Information Providers and Financial Information Users. DPBI Consent Managers span all sectors. No joint RBI and MeitY or DPBI circular aligning AA consent artefacts with DPDP notices was located as of 19 November 2026.

    04

    What This Means for You

    Read together, the November 2026 portal launch and May 2027 deadline point to a two-stage plan: build internal consent controls now, and add Consent Manager APIs once DPBI publishes technical standards.

    The practical takeaway is that a front-end pop-up creates audit risk once the burden-of-proof rule starts in May 2027. If onboarding captures consent while Data Processors run separate lists, withdrawal may not stop vendor processing. Blunt deletion could also clash with five-year PMLA and RBI KYC mandates unless your CMP separates optional consent from retained KYC files.

    Before picking a vendor or scoping a build, ask four questions:

    • •Audit proof: Can it export timestamped proof of notice version, language, and customer action?
    • •Processor sync: How does it send withdrawals to Data Processors and log that processing stopped?
    • •Selective deletion: Can it erase optional data while keeping KYC files required under PMLA and RBI's 2025 KYC Directions?
    • •API updates: Will the vendor support DPBI's Consent Manager APIs without heavy change fees once published?

    KYCKART sits on the onboarding and KYC side of this boundary and is not a CMP vendor. KYCKART's customer onboarding solution handles identity verification and KYC workflows, linking onboarding checks with consent evidence and statutory recordkeeping.

    Frequently Asked Questions

    Author: Bhanujeet Choudhary, Head of Compliance, KYCKART
    Published: 18 November 2026

    Disclaimer: This article is published for institutional compliance education and industry analysis. It does not constitute formal legal, regulatory, or technical advisory. Banking and NBFC institutions must reference primary circulars from the Reserve Bank of India and PMLA regulations.

    KYCKART

    Map consent to your KYC retention duties

    Talk to KYCKART about how consent records, KYC retention and DPDP obligations fit together in a BFSI stack.

    Talk to our teamarrow_forward