# Token Requestor Initiated Tokenization
source: https://developer.mastercard.com/mdes-pre-digitization/documentation/use_case/tokenization/index.md

A cardholder decides to use a digital wallet on their device. They add the payment card details to the digital wallet.
Meanwhile, a merchant has decided to use tokenized cards for transactions initiated through their portal to reduce fraud. The merchant's system is set up to store only tokenized cards, so they have modified their portal to tokenize the card when a cardholder uses it. Additionally, to tokenize the existing cards on file, the merchant has chosen to utilize the bulk file tokenization service that MDES (Mastercard Digital Enablement Service) provides.

Token requestor initiated tokenization involves performing various actions on cardholder card including:

* [Approve](https://developer.mastercard.com/mdes-pre-digitization/documentation/use_case/tokenization/index.md#approve)
* [Decline](https://developer.mastercard.com/mdes-pre-digitization/documentation/use_case/tokenization/index.md#decline)
* [Approve, but require authentication](https://developer.mastercard.com/mdes-pre-digitization/documentation/use_case/pre-tokenization-authentication/index.md)

## Approve {#approve}

Tokenization request received by MDES is authorized as per MDES program implementation. The card is approved for tokenization.

Diagram green-path

## Decline {#decline}

Tokenization request received by MDES is not authorized as per MDES program implementation. The card is not approved for tokenization. The cardholder can communicate offline with the issuer to identify how to tokenize the card.
Diagram red-path

### Endpoints {#endpoints}


API Reference: `GET /authorizeService`


API Reference: `GET /requestActivationMethods`


API Reference: `GET /notifyServiceActivated`

<br />