Cardholder Dispute Dataset Anonymisation with anonym.plus

Anonymise a dispute dataset before you use it for analytics or training.

Cardholder dispute dataset anonymisation is the removal of personal account data from a dispute dataset under PCI DSS v4.0. The standard limits how a stored account number is kept. anonym.plus marks each value on your device, so the set stays analysable while customer data is shielded — supporting UK GDPR anonymisation guidance from the ICO.

When this applies

A dispute file holds thousands of rows with account, customer, and reason columns. You strip those identifiers under the standard before any model is trained.

How anonym.plus handles it

  1. Open the file in anonym.plus on your device.
  2. The tool maps account, customer, and contact columns.
  3. It flags each sensitive cell across the rows.
  4. Keep reason codes and amount columns for analysis.
  5. Turn off the name map for true anonymity.
  6. Save the anonymised set locally.

What you need to provide

PII & financial identifiers detected

Categoryanonym.plus entity typeExample
AccountCREDIT_CARDpan column → [CARD]
NamesPERSONcustomer column → [BUYER]
ContactEMAIL_ADDRESSemail column → [EMAIL]
LocationLOCATIONbilling town → [TOWN]
AmountMONEYdispute amount → kept
DatesDATE_TIMEdispute date → [DATE]

Compliance achieved

Anonymise dispute datasets offline — see plans & start free →

Limitations & cautions

A rare combination of amount, date, and town can still single out a customer even with no name. Review quasi-identifiers, and keep the name map off when you need true anonymity.

Frequently asked questions

How do I make the output non-reversible?

Turn the name map off. Without it there is no path back from a label to a real customer.

Can I keep the reason and amount columns?

Yes. Those stay so analysis and training still work; only personal cells are removed.

Is the file uploaded?

No. The app is fully offline, so the data never leaves your machine.