---
sourceDocument: Australia Financial Services Operations
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/financial-services-operations

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Financial Services Operations

ft:clusterId :

    - finso

bundleId :

    - finso

workflow :

    - Customer and Industry


---

# Explore

# Exploring Card Data Security {#ariaid-title1}

Release version: Australia  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Exploring Card Data Security

The Card Data Security application in ServiceNow helps organizations comply with Payment Card Industry Data Security Standard (PCI DSS) requirements by protecting sensitive cardholder data within dispute workflows.
It uses a tokenizer service to replace sensitive information such as Primary Account Numbers (PANs) and sensitive documents with non-sensitive tokens.
This approach prevents storage of sensitive data on the ServiceNow instance, reducing the risk and impact of data breaches.
The application supports tokenization during data intake and detokenization when exchanging data with third-party financial systems like card networks.
Show full answer Show less  
Note: Card Data Security is hosted in the United States and primarily supports dispute cases and transactions. For regional support, customers should contact their ServiceNow representative.

## Key Features

* **Tokenizer Service Vault and Schemas:** Securely stores tokenized card details and documents to avoid sensitive data storage in ServiceNow.
* **Connection and Credential Management:** Enables configuration of service accounts, roles, and authorization, with prebuilt connection aliases for Visa Resolve Online (VROL) and Mastercom.
* **Seamless Passthrough Integration:** Transparently tokenizes and detokenizes PCI data in API requests and responses between ServiceNow and card networks.
* **Document Storage and Management:** Stores inbound sensitive dispute documents securely in the tokenizer vault and allows agents to view or download these attachments.
* **PAN Display and Masking:** Supports configurable display of full PANs or masked PANs (last four digits only) during dispute handling.
* **Card Data Entry Container:** Provides an interface component for entering PANs securely within dispute workflows, requiring administrator setup.
* **Document De-identification:** Offers redaction of predefined sensitive entities in images and PDFs, which also requires additional configuration.

## Why It Matters for ServiceNow Customers

Card Data Security is essential for customers managing card dispute processes that involve handling sensitive payment card information. It ensures PCI compliance by securing cardholder data, reducing risks of breaches and fraud, and enabling secure integration with card networks. This solution supports organizations at all PCI compliance levels, helping maintain operational efficiency while protecting sensitive data.

## Users and Roles

* **Administrators:** Configure and manage the tokenizer vault, connections, and integration routes between ServiceNow, the tokenizer service, and third-party financial systems. They also implement UI components for secure PAN entry.
* **Agents:** Access tokenized card data in dispute cases, reveal masked PANs as needed, and view or download secure attachments related to disputes.

## Practical Application

In typical dispute workflows, Card Data Security tokenizes sensitive data received from card networks before storing or processing it in ServiceNow. When sending data back to third-party systems, it detokenizes to restore the original sensitive information securely. This end-to-end tokenization flow safeguards cardholder data throughout dispute case management.

## Next Steps

ServiceNow customers interested in implementing or managing Card Data Security should explore the following resources:

* Configuring Card Data Security
* Managing Card Data Security
* Card Data Security Reference  
Learn more about Card Data Security and how it can be used to tokenize sensitive card data, display and mask Primary Account Numbers (PANs), and manage sensitive attachments for Dispute Cases and Dispute Transactions.

## Card Data Security overview {#exploring-card-data-security__cf-exploring-parent-overview}

The Card Data Security application helps organizations adhere to Payment Card Industry Data Security Standard (PCI DSS) requirements by protecting cardholder data. It provides a tokenizer service that substitutes sensitive
data in dispute workflows---such as Primary Account Numbers (PANs) and documents---with non-sensitive equivalent values called tokens.

Using tokens prevents sensitive data from being stored on a ServiceNow instance, minimizing the impact of a data breach.

You can configure data to be tokenized as it enters your ServiceNow instance, and have it restored to its original value when it is sent to Third-Party Systems.

(Disclaimer: This application enables data tokenization capabilities for Dispute Cases and Dispute Transactions. Card Data Security is hosted in the United States only. For other regional support, contact
your ServiceNow representative for more information.)

## Value of Card Data Security {#exploring-card-data-security__section_kfp_r5p_23c}

The PCI Data Security Standard requires organizations processing payment card transactions to implement proper security measures. Systems that handle
sensitive financial information, such as payment card data, must meet PCI standards to safeguard payment information and reduce the risk of data breaches and fraud.  
A card disputes solution needs to be PCI compliant for the following reasons:

1. Card dispute flows may store, process, or transmit physical card details.
2. Card dispute case logs may contain sensitive data.
3. Card dispute flows integrate with card networks that transmit card data in their responses.
4. Merchants may submit evidence that contains sensitive data, such as screenshots, receipts, or statements.

Card Data Security provides a secure, PCI-compliant vault for sensitive payment information, while allowing FSO users to maintain operational efficiency in dispute management processes. Whether your organization falls
under PCI Level 1 reporting requirements or operates at lower transaction volumes, Card Data Security can help maintain PCI compliance while streamlining financial services operations.

## Use cases {#exploring-card-data-security__id_vqs_ztz_c3c}

Card Data Security can support dispute management scenarios such as:{#exploring-card-data-security__use-cases-intro}

* Creating a dispute case by entering secure card data{#exploring-card-data-security__use-case-dispute}
{#exploring-card-data-security__use-case-dispute}
* Enhancing an investigation workflow by displaying card information{#exploring-card-data-security__use-case-investigation}
{#exploring-card-data-security__use-case-investigation}
* Document management for PCI-compliant file handling{#exploring-card-data-security__use-case-documentation}
{#exploring-card-data-security__use-case-documentation} {#exploring-card-data-security__use-cases-list}

## Features {#exploring-card-data-security__section_ytg_wny_c3c}

The following table shows the features available in Card Data Security:{#exploring-card-data-security__table_iwt_f4y_c3c__entry__2}

| Feature | Description |
|-|-|
| Built-in tokenizer service vault and schemas | Card Data Security includes schemas to support storing card details and sensitive documents in the tokenizer service vault, so that PANs and sensitive data are not stored in ServiceNow. |
| Manage connections and credentials | Supports defining service accounts, user and role management, and context-aware authorization. Card Data Security provides connection aliases for Visa Resolve Online (VROL) and Mastercom that can be configured to your workflow's requirements. |
| Seamless passthrough integration | The Card Data Security tokenizer service passes through API requests from ServiceNow and responses from card networks, while tokenizing and detokenizing data as required. |
| Tokenize and detokenize PANs in VROL and Mastercom requests and responses | Use included VROL and Mastercom connections, or upload and configure other connections for the tokenizer service. |
| Store inbound documents from VROL and Mastercom in the Card Data Security tokenizer service vault | Sensitive documents sent from VROL and Mastercom are kept in the tokenizer service vault, preventing PCI data from being stored in a ServiceNow instance. |
| List and download documents stored in the Card Data Security tokenizer vault | At the transaction level of a card dispute, use the Attachments contextual side panel to view a list of documents stored in the tokenizer service vault, or download documents to your device. |
| View and mask PANs in card disputes | Show the full PAN or only the last four digits in the dispute workflow. |
| Card Data Security container for entering PANs | Use the Card Data Security container to integrate PAN entry in your disputes workflow. Note: This feature is not pre-configured for the card disputes workflow and requires additional setup by an administrator. |
| Document De-identification | Redact predefined entities in images and PDFs. Note: This feature is not pre-configured for the card disputes workflow and requires additional setup by an administrator. |
[Table 1. Features in Card Data Security]

{#exploring-card-data-security__table_iwt_f4y_c3c}

## Passthrough Integration Workflow Example {#exploring-card-data-security__cf-exploring-parent-workflow}

See how PCI data is tokenized and detokenized with Card Data Security when communicating with card networks.
Figure 1. Tokenization flow with PCI data in response  
1. In a dispute intake workflow with a financial account number, a card network API request is sent.
2. The Card Data Security tokenizer service passes through the request to the card network.
3. The card network sends a response containing PCI data (such as a PAN).
4. The Card Data Security tokenizer service replaces the PAN with a token value and sends the token to the dispute workflow.
{#exploring-card-data-security__cf-exploring-parent-workflow-ol}
Figure 2. Tokenization flow with PCI data in request  
1. In a dispute intake workflow, a card network API request is sent containing the tokenized data.
2. The Card Data Security tokenizer service receives the request and substitutes the tokenized data with the PCI data (such as a PAN). The request containing the PAN is sent to the card network.
3. The card network sends a response.
4. The Card Data Security tokenizer service passes through the response to the dispute workflow.
{#exploring-card-data-security__ol_gjq_rjf_d3c}

## Users {#exploring-card-data-security__cf-exploring-parent-users}

{#exploring-card-data-security__table_qs3_kyk_4fc__entry__2}

| User | Description |
|-|-|
| Administrator | Administrators manage the card vault table. They configure the connections and routes between your ServiceNow instance, our tokenizer service, and the third-party financial systems involved in Dispute Case and Dispute Transaction processing, such as card networks and core banking systems ("Third-Party System(s)"). They can also implement the Card Data Security container in a disputes workflow using UI Builder. |
| Agent | Agents use Card Data Security to view and reveal PANs in a transaction for a card dispute case. At the transaction level of a dispute case, agents can also view and download secure attachments sent from VROL and Mastercom in the Attachments contextual side panel. |
[Table 2. Card Data Security users]

{#exploring-card-data-security__table_qs3_kyk_4fc}

## What to explore next {#exploring-card-data-security__cf-exploring-parent-links}

To learn more about configuring Card Data Security, see:

* [Configuring Card Data Security](https://www.servicenow.com/docs/sqvKMHPvHH70g0JdEherSw "Plan and configure your implementation of Card Data Security by following the tasks listed in this configuration overview.")
* [Managing Card data security](https://www.servicenow.com/docs/sLnRx2wFMhsvpuypAFVkbw "Card data security integrates with a service to enable tokenization and detokenization of data configured for Dispute Cases and Dispute Transactions. Administrators can manage connections and create new routes and methods in the application.")
* [Card Data Security Reference](https://www.servicenow.com/docs/bmzyI4aEXWp4wmurvhJ_jQ "Learn about the components and properties that are installed with Card Data Security.")
{#exploring-card-data-security__ul_us3_kyk_4fc}