Introduction to the Is Credit Card Check
The Is Credit Card check asserts that every value in a text field is a credit card number. Unlike Contains Credit Card, which accepts a number found anywhere inside the text, this rule expects the value itself to be the card number.
This section is the complete guide to the check. The Deep Dive covers the definition, properties, and full evaluation semantics, explains how anomalies are reported, walks through production examples, and collects best practices; the How-tos are step-by-step tutorials for creating, editing, and deleting a check; the API page documents the payload for programmatic use; and the FAQ answers the most frequent questions.
Next Steps
-
How It Works
The complete reference: definition, field scope, validation semantics, NULL handling, arrays, filter behavior, and coverage.
-
Anomaly Reporting
The anomaly messages the check produces, what the numbers mean, Source Records highlighting, and Custom Anomaly Description.
-
Examples
Three production scenarios with sample data, anomaly messages, and the SQL equivalent of what the check evaluates.
-
Best Practices
Guidelines for choosing the right column, handling masked values, pairing rules, and keeping the signal clean.
-
Permissions
The team permission each action needs: view, create, edit, archive, restore, and delete.
-
Create a Check
Step-by-step tutorial for creating an Is Credit Card check on a text field.
-
Edit a Check
Step-by-step tutorial for changing the target field, filter, coverage, or organizational properties.
-
Delete a Check
Step-by-step tutorial for archiving a check and deleting it permanently.
-
Troubleshooting
Common problems with masked values, separators, NULLs, and anomaly reporting, and how to resolve them.
-
API
Payload shape and field notes for creating an Is Credit Card check programmatically.
-
FAQ
Short answers to questions about validation, masking, NULLs, and anomaly reporting.