Financial services

Account, card and statement test data that still reconciles.

Entity templates, detection rules and scenarios for customer, account, card, transaction and statement data.

A financial-services entity graph (illustrative). An illustrative financial model: a customer owns accounts; accounts have cards, transactions and statements. Subsets and masking must keep these links intact and balances consistent.

Text description

Financial services: Customer → Account → Card → Transaction → Statement

Entities

Customer / party
Account
Card
Transaction
Statement

Sensitive data it helps find

Names, addresses, national identifiers and contact details
Account numbers and IBAN-like identifiers
Payment card numbers (detected with checksum validation)
Balances and transaction descriptions

Masking presets

Format-preserving substitutes for card and account numbers that still pass checksum validation
Consistent masked keys across core banking, card and statement systems
Balance-preserving transformations so statements still reconcile

Synthetic scenarios

An account with overdraft, reversal and chargeback activity
A customer holding joint and sole accounts
Month-end statement generation with balances that reconcile

Regulatory context

Supports PCI DSS–oriented and privacy programmes by keeping cardholder and customer data inside your environment. It does not certify any system for PCI DSS.

Read the financial services tutorial Listen to the pack tour Request a demo