# Omnichannel Tokenization

Verifone offers a seamless tokenization solution for omnichannel with an additional layer of security across all retail sales channels, including in-store, online, and telephone payments. 

Many retailers have multi-channel operations with brick-and-mortar stores using payment terminals, call centers taking payments via phone and eCommerce environments processing payments over the internet.  

Omnichannel tokenization means that tokens can be generated and used interchangeably between different sales channels. The goal of omnichannel tokenization is that it should not matter what was the sales channel that requested the token, it is possible to create and use a token also cross-sales channels.

Through omnichannel tokenization we map the customer journey and take a proactive technical approach to simplify and enhance the journey of consumption. By tokenizing in the core, we can create what typically seem complex links across multiple channels to provide more fluid experiences.

<div data-with-frame="true"><figure><img src="https://verifone.cloud/sites/default/files/inline-images/MicrosoftTeams-image%20%2851%29.png" alt=""><figcaption></figcaption></figure></div>

## Benefits <a href="#benefits" id="benefits"></a>

* Same token is accessible from all channels which simplifies and enhances the purchase journeys for the customer.
* Less impact on the customers who are migrating to a new channel, by being able to use on the new channel the tokens that were created on the old channel.

## Use cases <a href="#use-cases" id="use-cases"></a>

**Use case 1:** The cardholder pays for a product via a POS terminal in a retail shop and the merchant convinces him to also use an extra service, their shop's monthly vitamin delivery service. The cardholder agrees that he would like to also sign up for this subscription delivery from that shop, therefore, he consents that his card details can be saved for later use. During the transaction, the POS terminal triggers the creation of a token. Afterward, the regular payments for the subscription will be automatically processed via the token, the card data not being necessary anymore.

<div data-with-frame="true"><figure><img src="https://verifone.cloud/sites/default/files/inline-images/Usecase%201.png" alt=""><figcaption></figcaption></figure></div>

**Use case 2:** The cardholder buys a product from the merchant’s online store. During checkout, the cardholder signs up for a customer account and authorizes the merchant to store their card details for future payments. His tokenized payment data is saved with the account. Later that week he visits a physical store of the same merchant and uses his credit card when buying a new product. The system recognizes the cardholder and the payment will be processed via the token previously generated and not by using the card data.

<div data-with-frame="true"><figure><img src="https://verifone.cloud/sites/default/files/inline-images/Usecase%202.png" alt=""><figcaption></figcaption></figure></div>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.verifone.com/online-payments/tokenization/omnichannel-tokenization.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.