Cardholder names linked to accounts

Detects references to cardholder names linked to accounts in financial and compliance documents. Commonly found in Australian regulatory filings, transaction records, and audit documentation.

Type: regex
Engine: boost_regex
Confidence: medium
Confidence justification: category-aware structural regex with anchor and context constraints replaces phrase-only detection.
Detection quality: Not detected
Jurisdictions: global
Regulations: Anti-Money Laundering and Counter-Terrorism Financing Act 2006 (Cth), Information Privacy Act 2009 (Qld), NDB Scheme (Cth), Privacy Act 1988 (Cth), GDPR
Frameworks: ISO 27001, ISO 27701, PCI-DSS, SOC 2
Data categories: financial
Scope: wide
Risk rating: 4
Platform compatibility: Purview: Compatible, GCP DLP: Compatible, Macie: Compatible, Zscaler: Compatible, Palo Alto: Degraded, Netskope: Unsupported

Pattern

(?is)\b(?:cardholder\s+name|card\s+holder|name\s+on\s+card|account\s+holder|PCI\s+DSS|cardholder\s+data|payment\s+card|primary\s+account\s+number|card\s+account|linked\s+account|card\s+member)\b

Corroborative evidence keywords

cardholder names linked to accounts, cardholder, names, linked, accounts, financial, payments, fiscal, monetary, accounting, treasury, audit, revenue, expenditure, budget, ledger, accounts payable, accounts receivable, balance sheet, profit and loss (+1 more)

Proximity: 300 characters

Should match

cardholder name — Primary topic phrase match
card holder — Case-insensitive topic phrase match
name on card — Alternative topic phrase match
account holder — Additional topic phrase match
Cardholder name: Recorded Payee: Avery Teston Account number: 12345678 — Populated attribute field with a linked record field (85 tier)

Should not match

unrelated generic text without domain phrases — No relevant topic phrases present
placeholder value 12345 — Random text should not match topic-specific regex
bank transfer — Generic word pair from old broad template should not match
Cardholder name: Payee: Account name: Account number: — Empty form: the heading and field labels without values must not corroborate themselves (discovery only)
Policy guidance: this procedure explains how records about cardholder name are handled, who may access them and how long they are kept. It contains no records about any person or system. — Policy guidance naming the topic without any record (discovery only)
Cardholder name: Payee: Avery Teston — Record with the attribute label but no value: the label must not corroborate itself (discovery only)

Known false positives

Financial terminology appearing in published reports, accounting textbooks, regulatory guidance, or template documents without actual transaction data. Mitigation: Require corroborative evidence keywords within the proximity window. Cross-reference with structured financial identifiers to confirm actual sensitive data.
In Australian English, standard business terminology overlapping with financial detection keywords in routine correspondence and documentation. Mitigation: Increase confidence threshold when scanning business correspondence. Layer with transaction-specific patterns for higher precision.