Merchant acquiring credentials

Detects references to merchant acquiring credentials in financial and compliance documents. Commonly found in international 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. Added context gating and exclusion rules improve precision and reduce incidental matches.

Detection quality

Not detected

Jurisdictions

global

Regulations

GDPR, PCI-DSS

Data categories

financial

Scope

wide

Platform compatibility

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

Pattern

(?is)\b(?:merchant\s+ID|acquiring\s+bank|merchant\s+account|payment\s+gateway|terminal\s+ID|merchant\s+credentials|API\s+key|settlement\s+account|payment\s+processor|merchant\s+number|POS\s+terminal)\b

Corroborative evidence keywords

merchant acquiring credentials, merchant, acquiring, credentials, financial, accounts, payments, api key, api_key, apikey, access key, access token, auth token, authorization, bearer, conn str, connection string, connectionstring, cookie, credential (+44 more)

Proximity: 300 characters

Should match

• merchant ID — Primary topic phrase match
• acquiring bank — Case-insensitive topic phrase match
• merchant account — Alternative topic phrase match
• payment gateway — Additional topic phrase match

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

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 English (as the primary international business language), 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.

References

• https://docs-prv.pcisecuritystandards.org/PCI%20DSS/Standard/PCI-DSS-v4_0_1.pdf
• https://handbook.apra.gov.au/standard/cps-234
• https://www.austrac.gov.au/business/core-guidance/reporting