A payment gateway is usually a processor acting for the merchant, so UK GDPR Art. 28 binds what a gateway export may contain to the merchant's own instructions. Art. 30 asks that every such transfer be describable in a record of processing, and Chapter V raises the bar again if the receiving analytics environment sits outside the UK. PCI DSS v4.0 adds the card-specific limit on top: stored account numbers stay limited wherever the export lands. anonym.plus marks each value on your device, so the dataset stays analysable while customer data is shielded.
When this applies
A merchant pulls a monthly export from the payment gateway for an external reporting platform. The file carries account numbers, emails, and amount columns, but the reporting team only needs amounts, timestamps, and status codes.
How anonym.plus handles it
- Open the file in anonym.plus on your device.
- The tool maps columns of account, email, and name data.
- It flags each sensitive cell across the rows.
- Keep numeric amount and currency columns for analysis.
- Apply Replace with a steady label per column.
- Save the de-identified copy locally.
What you need to provide
- The export (CSV, JSON, or TXT).
- An operator (Replace keeps columns analysable).
- Optional name map for a reversible join later.
PII & financial identifiers detected
| Category | anonym.plus entity type | Example |
|---|---|---|
| Account | CREDIT_CARD | pan column → [CARD] |
| Contact | EMAIL_ADDRESS | email column → [EMAIL] |
| Names | PERSON | name column → [BUYER] |
| Bank | IBAN_CODE | iban column → [IBAN] |
| Location | LOCATION | billing town → [TOWN] |
| Amount | MONEY | amount column → kept |
Compliance achieved
- Limits stored account data per PCI DSS v4.0.
- Binds the export's contents to the merchant's instructions, as UK GDPR Art. 28 requires of a processor.
- Keeps the transfer describable in the Art. 30 record of processing once personal fields are removed.
- Lowers the bar the export has to clear under Chapter V where the analytics environment sits outside the UK.
- Offline handling keeps the dataset off any server.
Anonymise gateway exports offline — see plans & start free →
Limitations & cautions
A reversible name map can re-link rows if it is kept, so turn it off for true anonymity. A rare amount or timestamp combination can still single out a customer; consider that before release.
Frequently asked questions
Why does UK GDPR Art. 28 matter to a gateway export?
A gateway usually processes payments as a processor acting for the merchant, not as its own controller. Art. 28 ties what it may do with the merchant's data to the merchant's own instructions, so an export that goes beyond those instructions is a compliance gap even before PCI DSS is considered.
Can I keep the amount and currency columns?
Yes. Numeric columns stay so analysis still works. Only the account, name, and contact cells are de-identified.
Does an offshore analytics environment change anything?
Yes. Chapter V of UK GDPR raises the bar for sending personal data outside the UK. A dataset that already carries no personal fields sidesteps that question rather than having to satisfy it.