---
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 tokenized HTTP connection \& credential aliases

# Set up tokenized HTTP connection \&
credential aliases {#ariaid-title1}

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

Configure
a connection in Card Data Security using an API key for authentication.

## Before you begin

Role required: admin

Define
the authentication type when setting up a Service Account in the tokenizer service. API keys are long-lived, whereas JWT bearer tokens are time-limited. The tokenizer service generates an API key after you create a Service
Account. For more information, see [Initial setup for Vault schema, Connections and Service Account for Card data security (KB2830577)](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2830577).

In ServiceNow,
install and set up
integrations to the Third-Party Systems (such as Visa Spoke or Mastercard Spoke). Card Data Security requires these integrations to function correctly. For more information, see [Integrating with spokes](https://www.servicenow.com/docs/0uoDSb8J08_cGL9I5rQn_w "By integrating spokes with the Financial Services Operations (FSO) applications, flow designers can provide the actions within Workflow Studio for specific applications.").

## About this task

You will see records for VROLCardDataSecurity or MastercomCardDataSecurity if Visa Spoke or Mastercard Spoke are installed. These are separate to your existing third-party service connection aliases.
Modify these records as required.

## Procedure

1. Navigate to AllIntegration HubConnections \& CredentialsConnection \& Credential Aliases.
2. Open the VROLCardDataSecurity or MastercomCardDataSecurity record.  
   If you require another third-party connection, create a new Connection \& Credential alias. For more information, see [Create a Connection \& Credential alias](https://www.servicenow.com/docs/access?context=connection-alias&version=australia&pubname=australia-platform-security&ft:locale=en-US).
3. In the Related Links section, select ConnectionsNew.
4. Follow the steps in [Create an HTTP(s) connection](https://www.servicenow.com/docs/access?context=create-https-connection&version=australia&pubname=australia-platform-security&ft:locale=en-US) to create a new credential record for this connection.
5. Enter the following field value.

   | Tokenizer service authentication method | Credential type |
   | API key | API Key Credentials |
   |-|-|

   {#create-a-new-tokenizer-route__choicetable_sls_4fc_qfc}
6. In the new record form for the credential, use the API key generated from our tokenizer service.  

## What to do next

Repeat these steps for each route you need to set up.

*[\>]: and then