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

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Financial Services Operations

ft:clusterId :

    - finso

bundleId :

    - finso

workflow :

    - Customer and Industry


---

# Set up the Verifi Connection \& Credential Alias

# Set up the Verifi Connection \& Credential Alias {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
For Verifi integrations, set up a dedicated Verifi connection alias for Card Data Security operations.

## Before you begin

Role required: admin  
This step is performed for Verifi integrations. This requires:

* A Verifi credential created from the procedure in [Set up a credential](https://www.servicenow.com/docs/4aDuJJHoNSPX1nZXEFedTQ "Create a credential to enable secure authentication for Card Data Security integrations. This credential authenticates your ServiceNow instance with the tokenizer service gateway.").
* A JWT provider created from the procedure in [Set up a JWT Provider](https://www.servicenow.com/docs/~Wox2Be7A5~Gk4BdINNh4A "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.").

See [Set up Verifi integration](https://www.servicenow.com/docs/8qOQAcAhpcrA6DEaEM0jSA#set-up-oauth-for-card-data-security__section_itm_4vn_kjc) for a list of other required values.

## Procedure

1. Navigate to AllIntegration HubConnections \& CredentialsConnection \& Credential Aliases.
2. Select the VerifiCardDataSecurity record.
3. In the Connections related list, select New.
4. Enter the following field values.

   | Field | Value |
   | Credential | \<The credential created from the procedure in [Set up a credential](https://www.servicenow.com/docs/4aDuJJHoNSPX1nZXEFedTQ "Create a credential to enable secure authentication for Card Data Security integrations. This credential authenticates your ServiceNow instance with the tokenizer service gateway.")\> |
   | Connection URL | \<The tokenizer service endpoint URL\> |
   | Issuer | \<The Issuer ID provided by Verifi\> |
   | JWT Provider | \<The JWT Provider created from the procedure in [Set up a JWT Provider](https://www.servicenow.com/docs/~Wox2Be7A5~Gk4BdINNh4A "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.")\> |
   | API Version | \<The API version provided by Verifi, as necessary\> |
   |-|-|

   {#set-up-verifi-connection-credential-alias__choicetable_v4f_gwy_23c}
5. Select Submit.
{#set-up-verifi-connection-credential-alias__steps_dyq_2d4_kjc}

## Result

The VerifiCardDataSecurity record is set up with a dedicated connection alias for Card Data Security.

## What to do next

[Set up the API REST message](https://www.servicenow.com/docs/pq02IXSprDKMvcHPkq~u9g "Configure the API REST message for your integration. This step points outbound REST messages to the correct tokenizer service endpoint.").

*[\>]: and then