Card dispute case records

Detects references to card dispute case records 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

identifier/document-structure anchored regex with constrained context replaces phrase-only detection. Added context gating and exclusion rules improve precision and reduce incidental matches.

Detection quality

Topic false positive

Jurisdictions

global

Regulations

AML/CTF Act (Cth), IPA 2009 (Qld), NDB Scheme (Cth), Privacy Act 1988 (Cth), SOCI Act 2018 (Cth), GDPR, PCI-DSS

Frameworks

ISO 27001, ISO 27701, PCI-DSS, SOC 2

Data categories

financial

Scope

wide

Risk rating

7

Platform compatibility

Purview: Compatible, GCP DLP: Compatible, Macie: Compatible, Zscaler: Compatible, Palo Alto: Degraded, Netskope: Unsupported

Pattern

(?i)\b(?:card\s+dispute\s+case\s+records?|chargeback|transaction\s+dispute|cardholder\s+dispute|representment|arbitration)\b

Corroborative evidence keywords

card dispute case records, card, dispute, case, records, financial, accounts, payments, fiscal, monetary, accounting, treasury, audit, revenue, expenditure, budget, ledger, accounts payable, accounts receivable, balance sheet (+26 more)

Proximity: 300 characters

Should match

• Card dispute case records — Topic phrase present
• card dispute case records — Topic phrase, lowercase
• this record references the card dispute case records held on file — Topic phrase within surrounding text
• chargeback — Source-authored dispute vocabulary surfaces at 65 discovery_only

Should not match

• unrelated generic text — No relevant phrase context
• placeholder value 12345 — Random text should not match phrase marker
• generic narrative without identifier/document anchors — Should not match plain mention
• template example placeholder record identifier — Template/sample context should be excluded even when anchor words are present
• Customers may dispute a card transaction within 30 days. — Consumer-guidance prose contains no dispute-case anchor phrase — must not match
• chargeback case record — Artefact label reaches discovery only via the dispute-vocabulary branch — must not enforce
• PCI DSS training covers chargeback terminology. — Compliance-training topic reaches discovery only — must not enforce
• Example chargeback case CB-00000, reason code 13.1 — Template/example exclusion suppresses even the discovery-only dispute vocabulary

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.