Create new connections in Card Data Security

  • Release version: Australia
  • Updated March 12, 2026
  • 1 minute to read

    • Configure settings in our tokenizer service and your ServiceNow instance to set up new tokenized connections, routes, and methods in Card Data Security.

    To create a new tokenized connection to another core system other than Visa and Mastercard, refer to the following task list.
    Table 1. Tasks to create an additional connection
    Task Description Where to perform
    Configure the tokenizer service

    Use the tokenizer service website to set up a new connections and service accounts for a Third-Party System.

    		 Tokenizer service
    Set up integration with the Third-Party System Set up a new integration with the Third-Party System. ServiceNow
    Create a request builder and response parser Create request builder and response parser actions for your new connection. Refer to other FSO banking application spokes for examples. ServiceNow
    Create an "Enable Card Data Security" subflow in Workflow Studio for your Third-Party System

    Create a Card Data Security subflow to handle payloads from the Third-Party System.

    Refer to the default subflows in Card Data Security as examples, such as Enable Card Data Security for VROL and Enable Card Data Security for Mastercom.

    		 ServiceNow
    Add a decision table entry with API path and subflow mapping Add a decision table entry to map to the card data security subflow. ServiceNow
    Create a REST message function Create a new REST message function in All > System Web Services > Outbound > REST Message for your Third-Party System. ServiceNow
    Define a REST message HTTP method Define an HTTP method for each route in the connection. ServiceNow
    Add a mapping configuration record for each REST message function In the Tokenizer Resource Configurations table, add an entry for each message function, and map the endpoint URL to the REST message function. ServiceNow