---
sourceDocument: Australia Financial Services Operations
sourceDocumentLink: https://www.servicenow.com/docs/r/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


---

# Set up OAuth for Card Data Security

# Set up OAuth for Card Data Security {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

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.

## Token Authentication in Card Data Security {#set-up-oauth-for-card-data-security__section_ejd_czy_23c}

Card Data Security uses JSON Web Tokens (JWT) for authentication. It uses the following token types for authentication:

* Regular tokens---used for authentication in backend connections.{#set-up-oauth-for-card-data-security__section_ejd_czy_23c-li1}
{#set-up-oauth-for-card-data-security__section_ejd_czy_23c-li1}
* Context-aware tokens---required for user interactions in the UI, such as viewing documents in the data vault.{#set-up-oauth-for-card-data-security__section_ejd_czy_23c-li2}
{#set-up-oauth-for-card-data-security__section_ejd_czy_23c-li2} {#set-up-oauth-for-card-data-security__ul_lky_p1z_23c}

## Set up card network integration {#set-up-oauth-for-card-data-security__section_hcw_wzx_23c}

When you set up OAuth for card network integration, set up each following connection type.{#set-up-oauth-for-card-data-security__table_a3r_h1y_g3c__entry__4}

| Name | Connection Alias | Description | Procedure |
|-|-|-|-|
| Service Token | CardDataSecurity.ServiceToken | For Vault API interactions and backend requests, such as retrieving file download URLs or external document metadata. | Perform all the following steps for this connection type. |
| Client Token | CardDataSecurity.ClientToken | For obtaining context-aware bearer tokens that are used in detokenization requests. Used for viewing files and revealing PAN values. | Perform all the following steps for this connection type. |
| Data Token Signer | CardDataSecurity.DataTokenSigner | Required for context-aware authorization. Signs data tokens that are used to make detokenization requests to the data vault. Used for revealing PAN values. | Refer to [Set up a Token Signer](https://www.servicenow.com/docs/cJ1w_8R3oF6BEtIR9dzZEg "Configure a token signer to enable secure JWT-based authentication for tokenizer service integration. This task involves creating an OAuth entity profile with JWT Bearer grant type, setting up OAuth credentials, and establishing a connection alias that links to your tokenizer service endpoint.") for specific steps on this connection type. |
[Table 1. Connection types]

{#set-up-oauth-for-card-data-security__table_a3r_h1y_g3c}  
1. [Create a JKS file](https://www.servicenow.com/docs/Frw8~QFQdgBRyZS57_jrGQ "Generate a Java KeyStore (JKS) file for OAuth authentication setup. This process involves extracting the private key from a credentials JSON file and converting it through PEM format to create the required JKS file.")
2. [Create an X.509 Certificate](https://www.servicenow.com/docs/alsJKVFvCY3wsClsit8Zyg "Create an X.509 certificate record in ServiceNow by uploading a Java Key Store (JKS) file and configuring the certificate settings. This enables secure authentication and encryption for Card Data Security applications.")
3. [Set up a JWT key](https://www.servicenow.com/docs/72L_TDQ7o9RWBQnveWVqvA "Configure a JWT key to enable secure authentication for Card Data Security. This is used to sign the authentication tokens that ServiceNow sends to external systems.")
4. [Set up a JWT Provider](https://www.servicenow.com/docs/NXylDHDLNMcK_FHGhdIIjw "Configure a JWT Provider to enable secure token-based authentication for Card Data Security by setting up signing configurations and claim values. This provider generates JSON Web Tokens that authenticate requests to the tokenizer service using credentials from your tokenizer service JSON file.")
5. [Set up an OAuth Provider](https://www.servicenow.com/docs/kGLWBKq1cSjYhVmMZRlbkQ "Configure an OAuth provider to enable secure authentication between ServiceNow and a third-party tokenizer service for Card Data Security. This setup establishes the necessary connection credentials and JWT configuration required for secure data tokenization operations.")
6. [Set up the Connection \& Credential records](https://www.servicenow.com/docs/4Dyrxd90cKceRjjIMzLjUw "Configure the Connection & Credential records for Card Data Security. This establishes the primary outbound connection that routes requests from ServiceNow to external APIs via the tokenizer service.")
7. [Set up a credential](https://www.servicenow.com/docs/Y4JAnay5YEWRf3SWIxTAIw "Create a credential to enable secure authentication for Card Data Security integrations. This credential authenticates your ServiceNow instance with the tokenizer service gateway.")
8. [Set up the API REST message](https://www.servicenow.com/docs/2svS20YwjGOREMTlEZB2Dw "Configure the API REST message for your integration. This step points outbound REST messages to the correct tokenizer service endpoint.")
{#set-up-oauth-for-card-data-security__ol_gsp_yzx_23c}

## Set up Verifi integration {#set-up-oauth-for-card-data-security__section_itm_4vn_kjc}

Prepare the following values before you set up this integration. Obtain these values from your Verifi onboarding documentation or account manager, and from your tokenizer service connection setup procedure.

* Signing algorithm: typically HMAC256 (confirm with Verifi).
* JWT Signing Key: a unique key provided by Verifi.
* JWT Expiry Interval: value in seconds, provided by Verifi.
* Issuer ID: provided by Verifi.
* API Version: provided by Verifi.
* Tokenizer service connection URL: URL used to route requests to Verifi's APIs.
* Tokenizer service API key: provided by the tokenizer service during connection setup.
{#set-up-oauth-for-card-data-security__ul_npq_mxn_kjc}  
Perform the following tasks:

1. [Set up a JWT key](https://www.servicenow.com/docs/72L_TDQ7o9RWBQnveWVqvA "Configure a JWT key to enable secure authentication for Card Data Security. This is used to sign the authentication tokens that ServiceNow sends to external systems.")
2. [Set up a JWT Provider](https://www.servicenow.com/docs/NXylDHDLNMcK_FHGhdIIjw "Configure a JWT Provider to enable secure token-based authentication for Card Data Security by setting up signing configurations and claim values. This provider generates JSON Web Tokens that authenticate requests to the tokenizer service using credentials from your tokenizer service JSON file.")
3. [Set up the Connection \& Credential records](https://www.servicenow.com/docs/4Dyrxd90cKceRjjIMzLjUw "Configure the Connection & Credential records for Card Data Security. This establishes the primary outbound connection that routes requests from ServiceNow to external APIs via the tokenizer service.")
4. [Set up a credential](https://www.servicenow.com/docs/Y4JAnay5YEWRf3SWIxTAIw "Create a credential to enable secure authentication for Card Data Security integrations. This credential authenticates your ServiceNow instance with the tokenizer service gateway.")
5. [Set up the Verifi Connection \& Credential Alias](https://www.servicenow.com/docs/K~K86JzM3hOhQOXdc85RDA "For Verifi integrations, set up a dedicated Verifi connection alias for Card Data Security operations.")
6. [Set up the API REST message](https://www.servicenow.com/docs/2svS20YwjGOREMTlEZB2Dw "Configure the API REST message for your integration. This step points outbound REST messages to the correct tokenizer service endpoint.")
{#set-up-oauth-for-card-data-security__ol_qcx_pvn_kjc}