Mask Bank Transactions for Testing and Audits: IBANs, Card Numbers and Account Holders

A transaction file holds names, IBANs and card numbers next to amounts. Testers do not need the identifiers and auditors usually do not either. Mask the identifiers, keep the numbers.

Open the Data Masking

Practise on a sample file first

In the Data Generator, choose Finance & insurance and pick Bank transactions. The columns are a transaction id, posting date, account holder, IBAN, card number (empty on about one row in five), merchant, category, amount and currency. It is random data, so you can mask it and break it as you like.

Testing versus audit: keep different things

For testing, mask the identifiers and keep the shape: formats, lengths and empty cells, so validators and imports behave as in production. For an audit or a reconciliation, keep the amounts and dates exact, because the auditor needs to add them up, and mask only who the money belongs to.

A method for each column

Account holder: Replace with fake data (full name), consistent, so one person keeps one fake name across the file. IBAN: partial masking, keeping the country code and the last four characters. Card number: partial masking, keeping only the last four digits, or see mask credit card numbers. Merchant and category: keep. Amount and date: keep for audits, or add noise to amounts for pure software tests.

Watch the free-text description column if your real export has one. Payment references often contain names, invoice numbers and phone numbers. Set it to Remove, or run the PII detector on it before you decide to keep it.

Card numbers need extra care

Card data is covered by card-industry rules (PCI DSS), which generally do not allow live card numbers in test environments unless those environments are secured like production. Check the version and your own scope with your security team. The safest route for testing is to never bring real card numbers in at all, and use generated ones.

Verify before you hand it over

Total the amount column before and after masking: with identifiers-only masking the sums must be identical. Use a Group and summarize step in Data Transformation on both files and compare. If you start from a PDF or screenshot of a statement, convert it first with bank statement screenshot to Excel, then mask the result.

Limits

Masking lowers the risk but does not make a file anonymous: a rare amount on a known date can still identify a transaction. Read the full method on the test data masking page and follow your bank's data policy. This is not legal or compliance advice.

Open the Data Masking

Related tool pages

  • Test Data Masking: Test data masking in your browser: hide emails, phones, names and card numbers in a production export and keep formats and joins. Free, no upload.
  • GDPR Test Data Generator: GDPR test data without real people: generate synthetic rows that follow the patterns of your own file, in your browser. Not legal advice.
  • Mask Emails in a CSV File: Hide email addresses and phone numbers in a CSV file before you share it. Detects personal columns for you. Free, in your browser.
  • Anonymize CSV Data: Anonymize a CSV before sharing it: hide names, emails, phones and card numbers with the method you choose. Free, in your browser.
  • Mask PII in Excel Files: Find and hide personal data in an Excel file before you share it, such as emails, phone numbers and names. Free, in your browser.
  • Mask Phone Numbers in a CSV: Hide phone numbers in a CSV, Excel or JSON file before you share it. Keep the country code or last digits, or replace with fake numbers. Runs in your browser.

Also try

How to use the Data Masking: step by step

  1. Open the transaction file in Data Masking.
  2. Fake the holder name, partly mask the IBAN and card number.
  3. Keep amount and date for audits, or add noise for tests.
  4. Compare totals before and after, then download.

When to use the Data Masking

  • Test a statement import with no real customers
  • Give an auditor transactions without account holders
  • Share a sample with a vendor to debug a format problem
  • Practise masking card numbers and IBANs

Example

Input: ada@example.com, +1 555 0100

Output: a**@example.com, +1 *** ****

Frequently asked questions

Which columns should I mask in a bank transaction file?

Account holder, IBAN, card number and any free-text reference. Keep amount and date when someone needs to add or reconcile the numbers.

Can I keep the last four digits of a card?

Partial masking can keep the last four digits, which is common in receipts. Check your card-industry rules and company policy for your use.

How do I prove masking did not change the amounts?

Total the amount column by category before and after. With identifier-only masking the totals must match exactly.

Tip: Mask the file first, then share it. Never send the original "just to check" and mask later.