Insights Contact

Trackers

Data Governance & Privacy Tracker

How payment data should be governedEvery rule on this tracker touches one or more of these six steps in the data life cycle1Collect• Clear notice and consent• Only the data you need• Purpose written downWho: Product, PrivacyExample: India consent managers2Classify• Label data by sensitivity• Name a data owner• Card data kept apartWho: Data ownersExample: Card data vs personal data3Store and locate• Know where data lives• Residency and security• Encrypt and limit accessWho: Engineering, SecurityExample: Payment data kept in India4Use and share• Use only for stated purpose• Check AI and model decisions• Contracts with partnersWho: Product, RiskExample: California ADMT notices5Retain and delete• Retention schedule per type• Handle delete requests• Purge old copies and backupsWho: Operations, RecordsExample: State deletion requests6Prove• Data maps and records• Risk assessments• Audit and attestationWho: Compliance, AuditExample: CCPA risk assessmentsWatched every monthCPPA · State AGs · FTC · CFPB · European Commission · EDPB · India DPB · RBI · OAICHow payment datashould be governedSix steps in the data life cycle1Collect• Clear notice and consent• Only the data you need• Purpose written downWho: Product, PrivacyExample: India consent managers2Classify• Label data by sensitivity• Name a data owner• Card data kept apartWho: Data ownersExample: Card data vs personal data3Store and locate• Know where data lives• Residency and security• Encrypt and limit accessWho: Engineering, SecurityExample: Payment data kept in India4Use and share• Use only for stated purpose• Check AI and model decisions• Contracts with partnersWho: Product, RiskExample: California ADMT notices5Retain and delete• Retention schedule per type• Handle delete requests• Purge old copies and backupsWho: Operations, RecordsExample: State deletion requests6Prove• Data maps and records• Risk assessments• Audit and attestationWho: Compliance, AuditExample: CCPA risk assessmentsWatched every monthCPPA · State AGs · FTC · CFPB · EUEDPB · India DPB · RBI · OAIC

← All trackers

Data and privacy rules that change how payment firms collect, store, use, share and delete data, with the opportunity each one opens up. Each row links to its source and to our guide.

Updated monthly · Last updated: · Items leave the tracker once their month has passed.

Who governs payment data

RegionLaws and rulesPayments angleWho enforces
United States (federal)
Our guide →
Gramm-Leach-Bliley Act (financial privacy and Safeguards Rule), Fair Credit Reporting Act, CFPB open banking rule (Section 1033)Bank and fintech customer data, credit decisions, data sharing with aggregatorsFTC, CFPB and the bank regulators
United States (states)
Our guide →
State privacy laws, led by California (CCPA and CPPA regulations); many exempt data or firms already covered by Gramm-Leach-Bliley, so check each lawFintechs, merchants and non-bank payment firms; website tracking, opt-out signals, automated decisionsState attorneys general; California Privacy Protection Agency
European Union
Our guide →
GDPR, Data Act, AI Act; DORA for ICT risk in financeLawful basis, data sharing and cloud switching, AI used for credit decisionsNational data protection authorities, EDPB, financial supervisors
India
Our guide →
Digital Personal Data Protection Act 2023 and DPDP Rules 2025; RBI rule that payment data is stored only in IndiaConsent, breach reporting, payment data localisationData Protection Board of India; Reserve Bank of India
Australia
Our guide →
Privacy Act 1988 and the Australian Privacy Principles; Consumer Data Right for open bankingPrivacy policies, automated decisions, open banking dataOffice of the Australian Information Commissioner (OAIC)

What changed this month

A short log of new and changed data and privacy rules, updated every month. Newest month first.

Week of Nov 16, 2026

  • Chile personal data law moved here from Payment Rules; the CFPB Section 1033 rewrite now lives on the Open banking tracker.
  • Coverage widened beyond the US, EU, India and Australia: added Sri Lanka, Indonesia, South Korea, Japan, Canada, Hong Kong and Paraguay, plus the EU GDPR cross-border enforcement rules.
  • Tracker launched with 14 data and privacy rule changes across the US, EU, India and Australia.
  • India: consent managers can now register under the DPDP Rules (from Nov 13, 2026); the main duties follow on May 13, 2027.
  • Australia: automated decision transparency starts Dec 10, 2026.
  • US: California opt-out signal and automated decision rules, plus Louisiana and Oklahoma privacy laws, all start Jan 1, 2027.

Data governance change tracker

Soonest first. Tap a region or a status to filter; tap again to clear.

FILTER BY REGION

FILTER BY STATUS

RegionRule or changeWhat it meansOpportunityKey date
IndiaDPDP Rules: consent managers can register
Ministry of Electronics and IT; Data Protection Board
Our guide → · Source: Hogan Lovells
Consent managers must register with the Data Protection Board and meet set conditions before they handle consent for users.Consent APIs, consent records and partner checks for payment apps in India.Since Nov 13, 2026
Just started
ChileNew personal data law
Chile Personal Data Protection Agency
Our guide → · Source: Our Chile guide
Starts Dec 1, 2026; may move to Oct 15, 2027.Build privacy-ready payment products now.Dec 1, 2026 (may move)
Change pending
AustraliaPrivacy Act: automated decision transparency
OAIC
Our guide → · Source: OAIC
Privacy policies must say when a computer program makes or shapes decisions that significantly affect people.List credit, fraud and onboarding models; update privacy policies and notices.Dec 10, 2026
Deadline soon
United States
California
Browsers must offer a one-click opt-out signal (AB 566)
California legislature
Our guide → · Source: Venable
Web browsers must include a built-in way to send an opt-out signal, so far more visitors will send one.Check that payment sites and apps detect and honour opt-out signals.Jan 1, 2027
Deadline soon
United States
California
CCPA rules for automated decision-making apply
California Privacy Protection Agency
Our guide → · Source: CPPA
Businesses that use automated tools to make significant decisions about consumers must meet new notice and rights rules.Notices and request flows for credit, fraud and account decisions.Jan 1, 2027
Deadline soon
United States
Louisiana and Oklahoma
Two new state privacy laws take effect
State attorneys general
Our guide → · Source: Morgan Lewis
Residents gain rights to access, correct, delete and opt out, under laws similar to most other states.Update privacy notices, request handling and data maps.Jan 1, 2027
Deadline soon
Sri LankaPDPA core duties start
Data Protection Authority of Sri Lanka
Our guide → · Source: Daily FT
Rules on lawful processing, breaches and controller and processor contracts start. Rights and penalties follow later.Map Sri Lankan customer data and update notices and processor contracts.Jan 1, 2027
Deadline soon
European UnionData Act: cloud switching charges must end
European Commission
Our guide → · Source: McCann FitzGerald
Cloud providers can no longer charge customers for switching provider or moving their data out.Cloud exit plans and cheaper multi-cloud for payment platforms.Jan 12, 2027
Deadline soon
IndonesiaPDP implementing rules (GR 33/2026) apply
Ministry of Communication and Digital Affairs
Our guide → · Source: PwC Indonesia
Detailed rules on breaches, overseas transfers, impact assessments, DPOs, audits and fines take effect.Transfer assessments, breach playbooks and audit evidence for Indonesian data.Jan 16, 2027
Deadline soon
South KoreaPIPA: personal data for AI development
Personal Information Protection Commission
Our guide → · Source: PIPC
Lawfully collected personal data may be used to build AI, with regulator approval and safeguards.Governed training data for fraud and credit models in Korea.Mar 9, 2027
Upcoming
European UnionGDPR cross-border enforcement rules apply
European Parliament and Council
Our guide → · Source: European Commission
Common steps for complaints and investigations that involve more than one EU country.Ready complaint handling and evidence packs for multi-country cases.Apr 2, 2027
Upcoming
United States
Alabama
Alabama privacy law takes effect
Alabama attorney general
Our guide → · Source: Morgan Lewis
Alabama residents gain the usual set of privacy rights.Add Alabama to request handling and notices.May 1, 2027
Upcoming
IndiaDPDP core duties apply: notice, consent, security, breach reporting
Ministry of Electronics and IT; Data Protection Board
Our guide → · Source: Hogan Lovells
The main duties start: clear notices, valid consent, security safeguards, breach reporting and deletion.Consent capture, breach playbooks and retention rules for Indian payment data.May 13, 2027
Upcoming
European UnionData Act: unfair-terms rules reach older long-term contracts
European Commission
Our guide → · Source: Bird and Bird
Rules against one-sided data terms extend to long-running contracts signed before September 2025.Review cloud and data-sharing contracts with vendors and partners.Sep 12, 2027
Upcoming
ParaguayFirst full data protection law applies
Congress of Paraguay
Our guide → · Source: VitalLaw
A full personal data law with rights, duties and a regulator starts to apply.Data maps and consent for payment and lending services in Paraguay.Nov 27, 2027
Upcoming
European UnionAI Act: high-risk rules apply, including credit scoring
European Commission; national authorities
Our guide → · Source: Orrick
High-risk AI systems listed in the Act, such as credit scoring of people, must meet data quality, documentation and oversight rules.Model inventories, data quality checks and human oversight for lending and fraud models.Dec 2, 2027
Moved from Aug 2026
Upcoming
United States
California
CCPA risk assessments for existing processing due
California Privacy Protection Agency
Our guide → · Source: Morrison Foerster
Processing that started before 2026 and needs a risk assessment must have one documented by this date.Privacy risk assessments for tracking, profiling and decision models.Dec 31, 2027
Upcoming
United States
Vermont
Vermont privacy law takes effect
Vermont attorney general
Our guide → · Source: Morgan Lewis
Vermont residents gain privacy rights under one of the stricter state laws.Data minimisation and request handling for Vermont customers.Jan 1, 2028
Upcoming
United States
California
First risk-assessment attestation to the CPPA
California Privacy Protection Agency
Our guide → · Source: CPPA
Businesses must send the agency an attestation and a summary of their risk assessments.Evidence packs and sign-off for privacy risk assessments.Apr 1, 2028
Upcoming
CanadaBill C-36: new federal privacy law
Government of Canada
Our guide → · Source: Government of Canada
Would replace PIPEDA with a new regulator, fines and checks before data leaves Canada.Plan transfer risk checks for Canadian payment data now.Bill in Parliament
Proposed
Hong KongPDPO reform: mandatory breach reporting
Privacy Commissioner for Personal Data
Our guide → · Source: South China Morning Post
Plans to make breach reporting mandatory, with penalties, possibly in phases.Build breach detection and reporting steps before it becomes law.Consultation planned
Proposed
JapanAPPI amendments: fines, biometric and child data
Personal Information Protection Commission
Our guide → · Source: A&O Shearman
Law passed in July 2026 adds administrative fines and tighter rules for biometric and children’s data.Review biometric login and consent flows for customers in Japan.In force by Jul 2028
Change pending

WHO DOES WHAT

Roles, review, certification and sign-off

Every data rule on this page needs a named owner. These are the usual data governance roles in a payments firm, what each one does, and how work moves from review to certification to sign-off, with evidence kept for auditors and regulators.

1. Roles and responsibilities

Data owner
Senior business leader, for example the head of payments.
  • Accountable for a data set: who may use it and how good it must be
  • Approves access and data sharing
  • Certifies access and quality every quarter
  • Accepts remaining risk in writing
Data steward
Day-to-day keeper of the data, inside the business team.
  • Keeps definitions, data map and record of processing
  • Runs quality checks and drives fixes
  • Prepares evidence for each review
  • Raises issues to the data owner
Data custodian (IT)
Platform, database or cloud team that runs the systems.
  • Applies access controls, encryption and backups
  • Runs retention and deletion jobs
  • Keeps logs and system evidence
  • Supports breach containment
Data Protection Officer
Privacy lead required by GDPR, DPDP and similar laws.
  • Advises on privacy law and checks compliance
  • Approves privacy impact assessments
  • Owns regulator contact and breach notices
  • Signs off privacy readiness for new rules
CISO
Head of information security.
  • Sets security standards for data
  • Leads incident and breach response
  • Tests controls and reviews exceptions
  • Reports cyber risk to leadership
Chief Data Officer
Runs the data governance program and council.
  • Sets data policy and standards
  • Chairs the data governance council
  • Tracks issues and exceptions to closure
  • Gives the annual governance sign-off
Executive sponsor
Senior executive, for example the COO or Chief Risk Officer.
  • Funds the data governance program
  • Accepts remaining risk in writing
  • Gives the final approval with the CDO
  • Reports data risk to the board
Internal audit
Independent third line.
  • Tests a sample of controls each year
  • Checks evidence is complete
  • Reports findings to the audit committee
  • Confirms fixes are done
Data users and vendors
Analysts, product and AI teams, and outside processors.
  • Use data only for approved purposes
  • Complete training each year
  • Vendors follow contract terms and allow audits
  • Report suspected misuse quickly

2. Who is accountable for what (RACI)

ActivityData ownerStewardCustodian (IT)DPOCISOCDOInternal audit
Classify data and keep the data mapARCCCII
Approve access to dataACRICII
Data quality checks and fixesARCIIII
Privacy impact assessment for a new product or AI useRCCACII
Cross-border transfer and data location checksCCRACII
Retention and deletionARRCIII
Breach response and regulator noticeIIRARII
Impact of a new rule from this trackerRCCACII
Quarterly access and quality certificationARRICIC
Annual governance sign-offRCCRCAC
Independent testing of controlsIICCCIA

A accountable (one per activity, approves) · R responsible (does the work) · C consulted · I informed

3. Review, certify and sign off

STEP 1 · QUARTERLY
Review
Stewards run access and data quality reviews; IT pulls the access lists and logs.
Evidence: Access list, quality report, open issues
STEP 2 · QUARTERLY
Certify
Each data owner confirms access is right and quality is acceptable, or lists exceptions with a fix date.
Evidence: Signed certification per data set
STEP 3 · QUARTERLY
Challenge
DPO and CISO review exceptions, privacy impact assessments and incidents; anything high risk goes to the council.
Evidence: Exception log, DPO and CISO notes
STEP 4 · YEARLY AND PER NEW RULE
Sign off
CDO gives the governance sign-off with the DPO; the executive sponsor accepts any remaining risk.
Evidence: Sign-off record, risk acceptance
STEP 5 · YEARLY
Audit
Internal audit tests a sample and checks the evidence trail.
Evidence: Audit report and fix tracking

4. Sign-off record

Keep one line per review cycle or new rule. No line, no sign-off.

ItemReviewed byCertified bySigned off byDateEvidence
Example: card payments data, Q4 access reviewData stewardData ownerCDO, then executive sponsorQuarter endAccess list, quality report, signed form

Roles differ by firm size. Small firms often combine the data owner and steward, or the DPO and privacy officer. General guidance, not legal advice.

Runbook: from a data or privacy rule to sign-off

How to take any data or privacy rule on this tracker, in any region, from first sight to signed-off evidence. Use one runbook per rule. Each phase says when, why, what, who and how, and the evidence to keep.

▸1. Plan · Decide if the item applies to you, how big the change is, and who owns it.

When: As soon as an item appears on the tracker. Target: at least 90 days before the key date (T-90). For proposed rules, inside the comment window.

Why: Late discovery is the main reason teams miss deadlines, pay fines or ship rushed changes. Early planning turns a rule into a normal roadmap item.

What: Decide if the item applies to you, how big the change is, and who owns it.

Who: Owner: Data owner. With: Data Protection Officer (reads the rule), Data steward (data map), Chief Data Officer (priority).

Example: Australia automated decision transparency. List every model that makes or shapes credit, fraud or onboarding decisions.

How

  1. Open the official source linked in the tracker and read the actual text, not only the summary.
  2. Map it to your products, rails, systems, vendors and customers in scope.
  3. Run a short gap analysis: what we do today versus what the rule needs.
  4. Size the work (small, medium, large) and add it to the roadmap with a target date.
  5. Log risks, assumptions, issues and dependencies in the RAID log.

Evidence to keep

  • Impact assessment (applies / does not apply, with reason)
  • Gap analysis
  • Epic or change request with owner and target date
  • RAID log entry
▸2. Prepare · Turn the rule into requirements, a design, a test plan and a rollout plan.

When: T-90 to T-60 days.

Why: Clear requirements and a test plan stop rework and give auditors a straight line from the rule to the change.

What: Turn the rule into requirements, a design, a test plan and a rollout plan.

Who: Owner: Data steward. With: Data Protection Officer (privacy impact and transfer assessments), Data custodian (IT), CISO.

Example: draft the new privacy policy text with Legal and agree which systems and data it covers.

How

  1. Write requirements that quote the rule clause they come from.
  2. Agree the design and any vendor or partner changes, with dates.
  3. Build a traceability matrix: rule clause, requirement, test case, evidence.
  4. Plan test data, environments and a rollback.
  5. Book change windows and tell support and operations teams.

Evidence to keep

  • Requirements with rule references
  • Design or configuration decision
  • Traceability matrix (draft)
  • Test plan and rollback plan
▸3. Execute · Build or configure, test, and release the change safely.

When: T-60 days to go-live.

Why: This is where the change is built and proven. Testing against the rule, not just the feature, is what protects you.

What: Build or configure, test, and release the change safely.

Who: Owner: Data custodian (IT). With: Data steward, CISO (security controls).

Example: build and test consent capture, opt-out signal handling and deletion flows end to end.

How

  1. Build or configure the change behind a flag where possible.
  2. Run unit, system, regression and negative tests, plus UAT with the business.
  3. Fix defects and re-test; keep the defect log current.
  4. Hold a go/no-go meeting with clear criteria.
  5. Release, watch live metrics and keep the rollback ready.

Evidence to keep

  • Test results and defect log
  • UAT sign-off
  • Go/no-go record
  • Change ticket and release notes
▸4. Evidence · One evidence pack that shows the rule was understood, built, tested and approved.

When: Collected all the way through; packaged by T-7 days.

Why: If it is not written down, it did not happen. Good evidence makes audits short and calm.

What: One evidence pack that shows the rule was understood, built, tested and approved.

Who: Owner: Data steward. With: Data custodian (system evidence), Data owner (certification).

Example: keep data maps, consent logs, risk assessments and the published policy version together.

How

  1. Create one folder per tracker item with a simple index.
  2. Store each document with date, version and owner.
  3. Complete the traceability matrix with links to every test and approval.
  4. Add screenshots or exports of live configuration where relevant.
  5. Record training or communications sent to staff and customers.

Evidence to keep

  • Evidence index
  • Final traceability matrix
  • Configuration proof
  • Training and communication records
▸5. Audit · Second line (Compliance or Risk) tests the control; Internal Audit may sample it later.

When: From T-7 days to 30 days after go-live.

Why: An independent check finds gaps before a regulator, scheme or customer does.

What: Second line (Compliance or Risk) tests the control; Internal Audit may sample it later.

Who: Owner: Internal audit (independent). With: Data Protection Officer.

Example: the privacy officer samples customer requests to check they were handled correctly and on time.

How

  1. Walk through the evidence pack against the rule text.
  2. Re-perform a sample of key tests or checks.
  3. Raise findings with a rating, owner and due date.
  4. Track findings to closure and re-test the fix.

Evidence to keep

  • Control test results
  • Findings log with owners and dates
  • Closure evidence for each finding
▸6. Review · Post-implementation review: did it work, what broke, what we learned.

When: About 30 days after go-live.

Why: A short look back confirms the change works in real life and makes the next rule easier.

What: Post-implementation review: did it work, what broke, what we learned.

Who: Owner: Chief Data Officer (governance council). With: Data owner, Data Protection Officer, CISO.

Example: track request volumes, response times and complaints for 30 days after go-live.

How

  1. Check live metrics: errors, rejects, exceptions, complaints, incidents.
  2. Confirm all findings and defects are closed or accepted.
  3. Note lessons learned and update this runbook if needed.
  4. Update the tracker status and any related guides.

Evidence to keep

  • Post-implementation review notes
  • Metrics snapshot
  • Lessons learned
▸7. Sign-off · Named people confirm the item is done and the evidence is complete.

When: After the review, and before closing the item.

Why: Formal sign-off shows clear ownership and closes the loop for auditors.

What: Named people confirm the item is done and the evidence is complete.

Who: Owner: Executive sponsor (approves) with the Chief Data Officer. Signers in order: Data steward, Data custodian (IT), Data owner, CISO, Data Protection Officer.

Example: sign-off includes the data protection or privacy officer.

How

  1. Share the evidence pack and review notes with the approvers.
  2. Each approver confirms their part in writing, with date.
  3. Archive the pack in your GRC tool or records system.
  4. Close the epic and the RAID entries.

Evidence to keep

  • Signed approvals (name, role, date)
  • Archived evidence pack
  • Closed epic and RAID items

Sign-off

Sign in this order: Prepared, then Reviewed, then Certified, then Approved. Each signer checks the evidence of the lines above. Close the item only when every line has a name, date and evidence link. The person who prepares cannot approve.

#RoleStageConfirmsEvidenceName and date
1Data stewardPreparedData map, quality and access review doneData map, quality report, access list________________
2Data custodian (IT)ReviewedAccess controls, encryption and retention jobs in placeSystem evidence, logs________________
3Data ownerCertifiedAccess and quality certified for the data setSigned certification________________
4CISOCertifiedSecurity controls and breach readiness confirmedControl test, incident plan________________
5Data Protection OfficerCertifiedPrivacy law met; impact and transfer assessments approvedPrivacy impact assessment, transfer assessment________________
6Chief Data OfficerApprovedGovernance sign-off; exceptions trackedCouncil minutes, sign-off________________
7Executive sponsorApprovedAccepts remaining risk and closes the itemSigned risk acceptance________________

Tip: copy this runbook into your own tracker or GRC tool, one copy per rule. Dates are relative to the key date shown in the tracker (T-90 means 90 days before).

Risk and control self-assessment (RCSA): Data governance and privacy

The main risks for this area, the controls that reduce them, and the risk left after those controls. 5 risks are specific to this area and 6 are shared by every tracker (C1 to C6). Owners match the roles in the Who owns this section above. Reviewed every quarter and checked by the second line. Preventive controls lower likelihood; detective and corrective controls lower impact. Read more in our RCSA guide.

High residual
0
from 4 inherent
Medium residual
3
from 7 inherent
Low residual
8
from 0 inherent

11 risks assessed for this area. Controls bring every high inherent risk down to medium or low.

How to read the heat map: each dot is a risk. It starts at its inherent rating (no controls) and moves to its residual rating (after controls). Score = likelihood x impact: 1 to 6 Low, 8 to 12 Medium, 15 to 25 High. Mid-blue dots are this area; navy dots are shared risks.

Likelihood
5
10
15
20
25
4
8
12
16
20
3
6
9
12
15
2
4
6
8
10
1
2
3
4
5
R1
R2
R3
R4
R5
C1
C2
C3
C4
C5
C6
12345
Impact

QUARTERLY RCSA CYCLE

IdentifyList risks for this area
AssessRate likelihood and impact
Map controlsLink each risk to controls
TestCheck controls work, with evidence
RateSet residual risk
ActAgree actions, owners, dates
ReportShare results and sign off

RISK AND CONTROL REGISTER

IDTypeRisk and causeControlOwnerInherentResidual
DG-R1This areaPayment data is wrong, incomplete or kept too long
Cause: No named data owners; no quality rules or retention schedule
Data owners per domain; quality checks; retention and deletion schedule
Preventive and detective · Monthly
Data ownerMedium 12
L3 x I4
Low 6
L2 x I3
Control: Partly effective
DG-R2This areaPayment data is stored or moved where the law does not allow it
Cause: No map of where data lives and how it flows
Data-flow map; transfer check before any new vendor, region or partner
Preventive · Per change
Data Protection OfficerHigh 15
L3 x I5
Low 5
L1 x I5
Control: Effective
DG-R3This areaPersonal data is used without valid consent or notice
Cause: Consent not recorded per purpose; new uses not reviewed
Consent records per purpose; privacy review of new uses, including AI models
Preventive · Per change
Data Protection OfficerMedium 12
L3 x I4
Medium 8
L2 x I4
Control: Partly effective
DG-R4This areaA data breach is not reported on time
Cause: Detection and notice steps unclear
Breach playbook with each country clock; yearly drill
Preventive · Yearly
CISOMedium 10
L2 x I5
Low 5
L1 x I5
Control: Effective
DG-R5This areaToo many people can see personal data
Cause: Access not reviewed
Quarterly access certification by data owners
Detective · Quarterly
Data ownerMedium 12
L3 x I4
Low 6
L3 x I2
Control: Effective
C1SharedA rule change is missed
Cause: No owner watches the sources; news arrives late
Weekly tracker review; every new item gets a named owner within 5 days
Preventive and detective · Weekly
Data Protection OfficerHigh 20
L4 x I5
Medium 8
L2 x I4
Control: Effective
C2SharedA rule is read the wrong way
Cause: Summaries used instead of the rule text; no expert review
The impact assessment is signed against the source text
Preventive · Per item
Data Protection OfficerHigh 15
L3 x I5
Medium 10
L2 x I5
Control: Effective
C3SharedA deadline is missed
Cause: Work starts too late; dependencies not tracked
Planning starts at T-90; RAID log and go/no-go before release
Preventive and detective · Per item
Data ownerHigh 16
L4 x I4
Low 6
L2 x I3
Control: Effective
C4SharedTesting does not cover the rule
Cause: Tests check features, not rule clauses
Traceability from each rule clause to a test, with sign-off
Preventive · Per release
Data stewardMedium 12
L3 x I4
Low 4
L1 x I4
Control: Effective
C5SharedEvidence is missing at audit time
Cause: Documents spread across tools; no index
Evidence pack with an index, checked at T-7
Preventive · Per item
Data stewardMedium 9
L3 x I3
Low 3
L1 x I3
Control: Effective
C6SharedAudit findings stay open
Cause: No due dates or follow-up
Findings log with owner and due date; monthly review
Preventive and detective · Monthly
Chief Data OfficerMedium 9
L3 x I3
Low 4
L2 x I2
Control: Partly effective

Open actions

  • DG-R1: add quality rules for payment reference data. Owner: Data steward.
  • DG-R3: link consent records to every AI model that uses personal data. Owner: Data Protection Officer.
  • Test two controls in this area each quarter and keep the results in the evidence pack. Owner: Data Protection Officer.

Quarterly attestation

Data owner and Data steward (first line): confirm risks, controls and ratings are current. ________________

Data Protection Officer (second line review): confirms the review and challenge. ________________

Executive sponsor: accepts residual risk. ________________

This is a sample RCSA for planning and training. Adjust risks, ratings and owners to your own organisation before use. The full cross-area register is in the monthly portfolio status report.

This tracker is a summary for planning, not legal advice. Dates can change, so always check the official source before acting. The Opportunity column is our own view. Summaries are written in our own words; linked pages remain the property of their publishers. Corrections: sp@paymentconsultant.top.

© 2026 SP Sankar · paymentconsultant.top. This tracker, its summaries, diagrams and layout are original work and are protected. Please do not copy, republish or scrape this page without written permission. You are welcome to link to it. See also Payment Rules Tracker and Payment Tech News.