Create new connections in Card Data Security

  • Release version: Zurich
  • Updated July 31, 2025
  • 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 Location Description
    Set up connections to the tokenizer service Tokenizer service

    Use the Connections view in our tokenizer service website to set up a new connection to a Third-Party System.

    Use the Route view in our tokenizer service website to add or modify connection routes and field configurations.

    For more information, refer to the tokenizer service documentation.

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

    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.

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