# Create an Is Credit Card Check

Source: https://userguide.qualytics.io/data-quality-checks/is-credit-card/how-tos/create-a-check/

*Requires the Data Quality (DQ) module.*

Step-by-step tutorial for creating an Is Credit Card check on a text field. For what each property means and how the rule evaluates the data, see the [How It Works](https://userguide.qualytics.io/data-quality-checks/is-credit-card/deep-dive/how-it-works/) page.

> **Note: Permission Required**
>
> You need the **Author** team permission on the datastore to create an Active check, or **Drafter** to create it as a Draft. See the [Permissions](https://userguide.qualytics.io/data-quality-checks/is-credit-card/deep-dive/permissions/) page for the full matrix.

> **Tip: Show me how**
>
> The app can walk you through this. Click **Show me how**  in the check creation form's header, or press `H` while it is open, and the **Add a Check** walkthrough highlights each step while you fill in the real form.

## Field reference

The **Authored Check Details** form is organized in the sections below. Fill them in as you follow the [Steps](https://userguide.qualytics.io/data-quality-checks/is-credit-card/how-tos/create-a-check/#steps).

### Target

| Field | Required | Type | Description |
| --- | --- | --- | --- |
| **Associate with a Check Template** | No | Toggle | Links the check to a Check Template. Enabling it replaces the **Rule Type** dropdown with a **Template** dropdown where you pick an existing template, which then controls the check's properties. When off, you configure everything on this form. |
| **Rule Type** | Yes | Option | The validation logic to apply. Select **Is Credit Card** for this check. Shown only while **Associate with a Check Template** is off. |
| **Table / File** | Yes | Option | The table or file the check runs against. Locked after the check is saved. |
| **Field** | Yes | Option | The field to evaluate. Only text fields and arrays of text are listed, and the check accepts exactly one. An array field can be selected, but the rule has no element-level evaluation; see [Array Fields](https://userguide.qualytics.io/data-quality-checks/is-credit-card/deep-dive/how-it-works/#array-fields). |
| **Filter Clause** | No | Text | A SQL `WHERE` expression that limits the rows the check evaluates. Rows outside the filter are ignored entirely. |
| **Custom Anomaly Description** | No | Toggle | Uses the value of another field on the violating row as the anomaly message instead of the default one. Enabling it shows an **Anomaly Message Field** dropdown where you pick that field. When the selected field is empty for a violating row, the default message is used. |

> **Tip: Create the table or file from the form**
>
> If the table or file you need does not exist yet, click **Add Computed Table**  next to the **Table / File** field while it is empty (**Add Computed File** on a file-based datastore). Once saved, the new one is selected and pinned to the top of the list with a  icon until you close the form. The button appears only with the **Author** or **Editor** team permission on the datastore, and not when you add a check from Explore.

> **Note: A filter that can never run**
>
> **Validate** refuses a filter clause that can never convert a value, such as `amount <> ''` on a number field, or that uses a function Qualytics does not allow, and names the reason. This applies to every rule type that accepts a filter, including checks that compute one value for the whole table, such as **Sum**, and checks with a coverage below 100%. If a check with such a filter reaches a scan, it is reported as **Not Asserted** with that reason, and the other checks on the table still run.

### Pass Criteria

| Field | Required | Type | Description |
| --- | --- | --- | --- |
| **Coverage** | No | Slider | The percentage of evaluated rows that must pass. Defaults to 100%; lower it only when a known fraction of rows is allowed to fail. |

### Impact

| Field | Required | Type | Description |
| --- | --- | --- | --- |
| **Metrics** | No | List | Impact metrics that measure how big a failure is, such as the total amount or the number of customers in the failed records. With an expected range, a metric outside it raises the anomaly's impact and can tag the anomaly. Click **Add your first impact metric** to start. See [Impact Metrics](https://userguide.qualytics.io/data-quality-checks/checks/deep-dive/impact-metrics/). |

### Ownership

| Field | Required | Type | Description |
| --- | --- | --- | --- |
| **Owner** | Yes | Option | The user responsible for the check. Already filled in with the check creator. |
| **Anomaly Assignee** | No | Option | The user automatically assigned to anomalies the check produces. |

### Metadata

| Field | Required | Type | Description |
| --- | --- | --- | --- |
| **Description** | Yes | Text | A plain-language description of what the check enforces. Supports Markdown formatting: click the field to open the Markdown editor. Click the **Apply suggested description**  button for a suggestion based on the rule type. |
| **Tags** | No | Option | Tags applied to the check for filtering and organization. |
| **Additional Metadata** | No | Key-value | Custom key-value pairs, typically links to catalog entries, tickets, or governance records. |

> **Info: No Properties section**
>
> Is Credit Card has no rule-specific properties: the rule is fully defined by the target, the filter, and the coverage.

> **Tip: Let AgentQ fill in the form**
>
> When [AgentQ](https://userguide.qualytics.io/agentq/getting-started/) is configured for your deployment, the **Check Assistant** panel in the check form can author the check for you: describe the rule in plain language (for example, "the card number column must hold valid card numbers") and it proposes a configuration you can apply to the form. Review the filled-in fields, then Validate and Save as usual.

## Steps

Each field is described in the [Field reference](https://userguide.qualytics.io/data-quality-checks/is-credit-card/how-tos/create-a-check/#field-reference) above.

**Step 1**: Select the source datastore from the left menu, then click the **Checks** tab.

**Step 2**: Click **Add** in the top-right corner and select **Check** from the dropdown. The **Authored Check Details** form opens.

> **Warning: No tables available**
>
> On a datastore that has no tables yet, for example one that was just added and has not been synced, the form shows a **No tables available** warning (**No files available** on a file-based datastore) that reads **Run a Sync on this datastore before adding checks.** instead of the check fields. When you open the form from the datastore page and you can run operations on the datastore, the warning also offers a **Run Sync**  button, which closes the form and opens the Sync dialog. Add the check once the Sync finishes. The warning does not appear when you add a check from a check template.

**Step 3**: Select **Is Credit Card** in the **Rule Type** dropdown.

**Step 4**: Fill in the remaining [Target](https://userguide.qualytics.io/data-quality-checks/is-credit-card/how-tos/create-a-check/#target) fields: the table or file, the **Field** to evaluate, and, optionally, a **Filter Clause** and **Custom Anomaly Description**.

**Step 5**: Fill in the [Pass Criteria](https://userguide.qualytics.io/data-quality-checks/is-credit-card/how-tos/create-a-check/#pass-criteria), [Ownership](https://userguide.qualytics.io/data-quality-checks/is-credit-card/how-tos/create-a-check/#ownership), and [Metadata](https://userguide.qualytics.io/data-quality-checks/is-credit-card/how-tos/create-a-check/#metadata) sections. Only the **Description** is required.

**Step 6**: Click **Validate** to test the rule against the selected data without saving it. A success message confirms the rule can run on that data. If validation fails, see [Troubleshooting](https://userguide.qualytics.io/data-quality-checks/is-credit-card/troubleshooting/#validation-fails-when-creating-the-check).

**Step 7**: Click **Save**. A success message confirms that the check was created.

*Last updated: November 10, 2026.*
