Merchant Onboarding Form Redaction with anonym.plus

Clear owner and bank data from an onboarding form before you archive it.

Merchant onboarding form redaction is the removal of personal data from a new-merchant application under PCI-DSS v4.0. The standard limits how stored account numbers are kept. anonym.plus marks each value on your device, so the record stays on file while principal data is shielded.

When this applies

An onboarding packet gathers the principal's ID, the settlement bank, and contacts. You strip those identifiers under the standard before it is archived.

How anonym.plus handles it

  1. Open the onboarding packet in anonym.plus on your device.
  2. Local OCR reads a scanned, signed application.
  3. The tool flags the principal ID, bank, and contact fields.
  4. Keep the merchant ID and MCC code you must retain.
  5. Swap or black out the confirmed items.
  6. Save the clean copy locally.

What you need to provide

PII & financial identifiers detected

Categoryanonym.plus entity typeExample
NamesPERSONowner Ortiz → [OWNER]
BankUS_BANK_NUMBERsettlement acct → [ACCOUNT]
IdentifiersUS_SSNprincipal SSN → [SSN]
ContactEMAIL_ADDRESSprincipal email → [EMAIL]
LocationLOCATIONbusiness address → [ADDRESS]
OrgORGANIZATIONlegal entity → [ENTITY]

Compliance achieved

Anonymize onboarding forms offline — see plans & start free →

Limitations & cautions

A signed application may carry handwriting OCR reads poorly. Verify flags on scanned pages. The tool removes named fields, not every detail a principal wrote in.

Frequently asked questions

Which fields get flagged on a packet?

Principal name, taxpayer ID, settlement account, address, and contacts. anonym.plus marks each so you can decide what to keep.

Can a scanned, signed application be processed?

Yes. Local OCR reads the scan, so fields on a signed page are flagged for review.

Is the packet uploaded?

No. The app is fully offline, so the principal data stays on your device.