Contains Credit Card Check Examples

The situation: A payment integration writes the masked card reference into card_reference. Rows where the column holds a token, a bank slip number, or a note instead of a card number break reconciliation with the acquirer.

Check configuration

Payload

{
    "description": "Card reference must hold a credit card number.",
    "rule": "containsCreditCard",
    "fields": ["card_reference"],
    "container_id": 301,
    "coverage": 1,
    "filter": null,
    "properties": {},
    "tags": ["payments", "format"],
    "additional_metadata": {"jira": "DATA-7201"},
    "anomaly_message_field": null,
    "template_id": null,
    "status": "Active",
    "owner_id": 7,
    "default_anomaly_assignee_id": 15
}

Sample Data

What gets flagged

Payment P-002 holds a bank slip identifier where the card number should be. P-004 is NULL and passes without firing an anomaly. Coverage is 100%, so the failing row is reported as a Record Anomaly.

Flowchart

graph TD
    A["No filter, evaluate all rows"] --> B["Read card_reference as text"]
    B --> C{"Is value NULL?"}
    C -->|Yes| D["Row passes"]
    C -->|No| E{"Does it contain<br/>a credit card number?"}
    E -->|Yes| D
    E -->|No| F["Flag row.<br/>Record Anomaly per failing row."]

Equivalent SQL

-- Rows the Contains Credit Card check would flag.
SELECT p.*
FROM payments p
WHERE p.card_reference IS NOT NULL
  AND p.card_reference NOT RLIKE '<credit card pattern>';

The situation: The transactions table mixes card payments with transfers and vouchers. Only rows whose method is card must carry a card number in instrument; the other methods legitimately hold other identifiers.

Check configuration

Payload

{
    "description": "Card transactions must carry a credit card number.",
    "rule": "containsCreditCard",
    "fields": ["instrument"],
    "container_id": 302,
    "coverage": 1,
    "filter": "method = 'card'",
    "properties": {},
    "tags": ["payments", "format"],
    "additional_metadata": {"jira": "DATA-7233"},
    "anomaly_message_field": null,
    "template_id": null,
    "status": "Active",
    "owner_id": 7,
    "default_anomaly_assignee_id": 15
}

Sample Data (filtered to method = 'card')

Why the filter matters

The filter runs before the evaluation, so transfers and vouchers are never tested for a card number. Only card transactions are evaluated.

What gets flagged

T-02 holds the placeholder pending, so it is the only row reported. Coverage is 100%, so the failure is reported as a Record Anomaly, and the message ends with the filter that scoped the evaluation.

Flowchart

graph TD
    A["Apply filter: method = 'card'"] --> B["Read instrument as text"]
    B --> C{"Does it contain<br/>a credit card number?"}
    C -->|Yes| D["Row passes"]
    C -->|No| E["Flag row.<br/>Anomaly message ends with<br/>[filter: method = 'card']"]

Equivalent SQL

-- Rows the check would flag on card transactions.
SELECT t.*
FROM transactions t
WHERE t.method = 'card'
  AND t.instrument IS NOT NULL
  AND t.instrument NOT RLIKE '<credit card pattern>';

The situation: A legacy import left free-text values in stored_card. A cleanup job is rewriting them, and a small fraction is expected to stay broken until it finishes, so the check tolerates up to 0.5% failures.

Check configuration

Payload

{
    "description": "Stored card column must hold a credit card number.",
    "rule": "containsCreditCard",
    "fields": ["stored_card"],
    "container_id": 303,
    "coverage": 0.995,
    "filter": null,
    "properties": {},
    "tags": ["legacy", "payments"],
    "additional_metadata": {"jira": "DATA-7290"},
    "anomaly_message_field": null,
    "template_id": null,
    "status": "Active",
    "owner_id": 7,
    "default_anomaly_assignee_id": 41
}

Sample Data

What gets flagged

Wallets W-02 and W-03 still hold free-text and a truncated value. W-04 is NULL, so it passes without firing an anomaly but still counts in the scanned total. Only 50% of the rows pass, which is below the 99.5% coverage threshold, so the check reports a single Shape Anomaly for the dataset with a sample of the offending rows. Coverage below 100% does not produce Record Anomalies.

Flowchart

graph TD
    A["No filter, evaluate all rows"] --> B["Read stored_card as text"]
    B --> C{"Is value NULL?"}
    C -->|Yes| D["Row passes"]
    C -->|No| E{"Does it contain<br/>a credit card number?"}
    E -->|Yes| D
    E -->|No| F["Flag row.<br/>Passing rate falls below the 99.5%<br/>coverage, so one Shape Anomaly is reported."]

Equivalent SQL

-- Rows the check would flag.
SELECT w.*
FROM wallets w
WHERE w.stored_card IS NOT NULL
  AND w.stored_card NOT RLIKE '<credit card pattern>';