--- 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 --- # Card Data Security container # Card Data Security container {#ariaid-title1} Release version: Australia Updated March 12, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 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 Card Data Security container The Card Data Security container in ServiceNow Australia release enables secure handling of Payment Card Information (PCI) within Financial Services Operations, specifically for card dispute workflows. It integrates with a tokenizer service to protect sensitive card data, allowing users to view and interact with PCI data without exposing the actual card information directly. Proper functioning requires context-aware authorization via OAuth setup. Show full answer Show less ## Key Features * **Secure Card Number Display:** Uses integration with the tokenizer service to show tokenized and detokenized card numbers within the ServiceNow interface. * **Secure Document Handling:** Allows secure viewing and downloading of PCI-related documents stored in the tokenizer service vault. * **Card Number Input:** Provides a secure input method for card numbers through an embedded iframe interface. * **Document Upload:** Supports uploading files containing PCI data securely. * **UI Builder Configuration:** Enables customization and implementation of Card Data Security components such as card number reveal and secure attachment viewer using UI Builder. ## Implementation and Customization The Card Data Security container components are preconfigured for use in UI Builder views, including: * **Card Number Reveal Component:** Preconfigured to display tokenized PAN values and detokenize on user action in both the Dispute Workspace and transaction record pages. It sources the card number from the payment card record's PAN field. * **Secure Attachment Viewer:** Displays attachments in two tabs---Issuer (files added by dispute agents) and Merchant (files from card networks or merchants stored in the tokenizer vault). Using UI Builder, customers can move, customize, or add components like card number input and document upload to workspaces. Configuring the card number reveal component requires setting up a viewport with specific parameters, including the paymentCardSysId. ## Practical Outcomes for ServiceNow Customers * Enhanced security and compliance when handling PCI card data within financial dispute workflows. * Reduced risk of exposing sensitive card information through tokenization and controlled detokenization. * Streamlined and secure management of PCI-related documents and attachments. * Flexible customization options via UI Builder to tailor card data handling components to specific business needs. The Card Data Security container enables secure handling of Payment Card Information (PCI) card data within Financial Services Operations card dispute workflows through integration with a tokenizer service. This allows users to work with sensitive card information without exposing PCI data directly. Note: Card Data Security container requires context-aware authorization to function correctly. See [Set up OAuth for Card Data Security](https://www.servicenow.com/docs/WHVb~2RH7c0~FsFJ4Pdwdg "After you configure your tokenizer service, follow these steps to set up OAuth connectivity with your ServiceNow instance. This connection is required to get file metadata and download URLs from files hosted in the tokenizer service vault.") for more information. ## Key capabilities {#card-data-security-component__id_fz1_stz_c3c} This component offers the following capabilities:{#card-data-security-component__key-capabilities-intro} * Secure card number display within the ServiceNow interface via integration with the tokenizer service (preconfigured in Card Data Security){#card-data-security-component__key-capabilities-reveal} {#card-data-security-component__key-capabilities-reveal} * Secure viewing and download of documents stored in the tokenizer service containing PCI data (preconfigured in Card Data Security){#card-data-security-component__key-capabilities-view} {#card-data-security-component__key-capabilities-view} * Secure card number input through an embedded iframe interface{#card-data-security-component__key-capabilities-input} {#card-data-security-component__key-capabilities-input} * Document upload functionality for files containing PCI data{#card-data-security-component__key-capabilities-upload} {#card-data-security-component__key-capabilities-upload} * Configurable features through UI Builder properties{#card-data-security-component__key-capabilities-config} {#card-data-security-component__key-capabilities-config} {#card-data-security-component__key-capabilities-list} ## Implementing and modifying the component {#card-data-security-component__id_v1z_b5z_c3c} This component displays within UI Builder views.{#card-data-security-component__component-interface-desc} Two capabilities are preconfigured in Card Data Security: a card number reveal component and a secure attachment viewer. Use UI Builder to make changes to the preconfigured Card Data Security components. You may also use UI Builder to implement features in the Card Data Security container that aren't preconfigured in Card Data Security, such as card number input and document upload. For more information about this component's configuration options and adding it to a workspace, see the following resources: * [Component developer documentation for Card Data Security](https://developer.servicenow.com/dev.do#!/reference/next-experience/australia/now-components/sn-card-data-security-container/overview) * [UI Builder setup documentation for Card Data Security](https://developer.servicenow.com/dev.do#!/reference/next-experience/australia/now-components/sn-card-data-security-container/uib-setup) * [Customize UI Builder pages using components](https://www.servicenow.com/docs/access?context=work-components&version=australia&pubname=australia-application-development&ft:locale=en-US) {#card-data-security-component__ul_mx3_h5z_c3c} ## Card Number Reveal Component {#card-data-security-component__section_it1_jbc_g3c} After installing Card Data Security, the card dispute workflow includes this component as a preconfigured card number reveal component. This component is in the transaction record and the Card details section of the Dispute Workspace. In the transaction record page, the value is derived from the PAN field of the payment card linked to the transaction. In the dispute workspace, the value is the payment card's tokenized PAN from the disputed financial transaction. Note: The tokenized PAN value from the tokenizer service is stored in the payment card record's PAN field. When you select the show icon, the card number reveal component detokenizes and displays the original PAN. When you select the hide icon, it restores the redacted value. Figure 1. Card number reveal component in Dispute Workspace Figure 2. Card number reveal component in Transaction record This component is a UI Builder page collection called FSO Card Number Reveal Viewport Pages. Use UI Builder to move this component elsewhere as required. 1. Add a viewport to your desired page. 2. Add the FSO Card Number Reveal Viewport Pages page collection to the viewport. 3. Create a Viewport load request and define the following values:{#card-data-security-component__table_g4p_fvv_33c__entry__2} | Field | Value | |-|-| | Viewport | Card Number Reveal Viewport | | Viewport Route | \ | | Viewport Fields | \ Note: This value is required for the component to function. | [Table 1. Viewport configuration] {#card-data-security-component__table_g4p_fvv_33c} {#card-data-security-component__ol_f4p_fvv_33c}Refer to the related links for more information. ## Displaying and downloading secure attachments {#card-data-security-component__section_w2d_1wd_mjc} After installing Card Data Security, the Attachments view in the contextual side panel displays attachments differently at the transaction level. It displays two preconfigured tabs: * Issuer, which shows files added by the dispute agent. * Merchant, which shows files received from the card network, acquirer, or merchant, stored in the tokenizer service vault. {#card-data-security-component__ul_u1n_2wd_mjc}For more information, see [Manage attachments in Card Data Security](https://www.servicenow.com/docs/CPIi4YfhIMVo13dFyOSHhA "Learn how attachments in the contextual side panel are handled in Card Data Security."). **Related topics** * [UI Builder](https://www.servicenow.com/docs/access?context=ui-builder-overview&version=australia&pubname=australia-application-development&ft:locale=en-US) * [Page collections](https://www.servicenow.com/docs/access?context=page-collections&version=australia&pubname=australia-application-development&ft:locale=en-US) * [Extend your UI experience with viewport components](https://www.servicenow.com/docs/access?context=viewports-overview&version=australia&pubname=australia-application-development&ft:locale=en-US)