---
sourceDocument: Australia Financial Services Operations
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/financial-services-operations

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Financial Services Operations

ft:clusterId :

    - finso

bundleId :

    - finso

workflow :

    - Customer and Industry


---

# Set up tokenized REST message

# Set up tokenized REST message record {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

To use tokenized data with a Third-Party System, update the endpoint URL for the Third-Party System's REST message entry in ServiceNow.

## Vorbereitungen

Set up your Third-Party System connections in our tokenizer service. For more information, see [Initial steps to setup schema and connections for Card data security (KB2238661)](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2238661).

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://servicenow-prod.fluidtopics.net/K8CKf2drbQZhzXO49tBnIQ "By integrating spokes with the Financial Services Operations (FSO) applications, flow designers can provide the actions within Workflow Studio for specific applications.").

Role required: admin

## Prozedur

1. Navigate to AllSystem Web ServicesOutboundREST Message.
2. Open the Visa Resolve Online or Mastercom record.  
   Create a new REST Message record if you don't see one for your Third-Party System. For more information, see [Create a REST message](https://www.servicenow.com/docs/access?context=t_ConfiguringARESTMessage&version=australia&pubname=australia-api-reference&ft:locale=en-US).
3. For the Endpoint field in the REST message form, enter the connection's base URI from the tokenizer service.  

   The connection's base path can be viewed in
   the tokenizer service administration
   website by navigating to Connections, expanding the connection, and selecting Sample Request on a route. The base URL is the domain name of the value in the
   Path field.

## Nächste Maßnahme

Repeat these steps for each REST message entry you need to set up.

