# Configuring Pre-Digitization Services
source: https://developer.mastercard.com/mdes-pre-digitization/documentation/configuring-services/index.md

Web services are provided as an alternative to Network Messages. Issuers integrating with MDES can use web services for easier and faster implementation. For configuring web services, refer to the following sections:

* [Message Profile Setup](https://developer.mastercard.com/mdes-pre-digitization/documentation/configuring-services/message-profile-setup/index.md)
* [Working Modes](https://developer.mastercard.com/mdes-pre-digitization/documentation/configuring-services/working-modes/index.md)
* [Connectivity Requirements](https://developer.mastercard.com/mdes-pre-digitization/documentation/configuring-services/connectivity-reqs/index.md)

## Comparing Web Services and Network Messages {#comparing-web-services-and-network-messages}

The table below gives an overview of the Pre-Digitization APIs and the corresponding equivalent Network Message, if any:

|           Web Services           |        Network Message Equivalent        |
|----------------------------------|------------------------------------------|
| --                               | Tokenization Eligibility (TE)            |
| Authorize Service (AS)           | Token Authorization (TA)                 |
| Request Activation Methods (RAM) | --                                       |
| Deliver Activation Code (DAC)    | Activation Code Notification (ACN)       |
| Notify Service Activated (NSA)   | Tokenization Complete Notification (TCN) |
| Notify Token Updated (NTU)       | Tokenization Event Notification (TVN)    |
| Validate Activation Code (VAC)   | --                                       |
| Notify Suspicious Events (NSE)   | --                                       |

## Web Services Limitations {#web-services-limitations}

Currently, when compared to Network Messages the Pre-Digitization API web services have some limitations.

* Issuers migrating from Network Messages to Pre-Digitization APIs must be aware that customized operator data cannot be sent in the AuthorizeService response. Therefore, it is not possible for them to perform Token Level Personalization Data for their loyalty programs.
* The NotifyTokenUpdated (NTU) API request does not implement the error handling mechanism for the Activation Code. The three Tokenization Event Reason Codes listed above are not included in the NTU API request. Therefore an Issuer's web service is unable to conduct Activation Code management with Consumers in case of errors.

The AuthorizeService response and the NotifyTokenUpdated request do not cover the functionalities outlined in the table below:

| API Service Response/request |                                Type of Service                                 | Type of Network Support |              |   |
|------------------------------|--------------------------------------------------------------------------------|-------------------------|--------------|---|
|                              |                                                                                | Network Messages        | Web Services |   |
| AuthorizeService response    | Support Token Level Personalization Data                                       | Yes                     | No           |   |
| NotifyTokenUpdated request   | Receive information on the incorrect typing of the Activation Code by Consumer | Yes                     | No           |   |
|                              | Receive information on the Activation Code retries exceeded by Consumer        | Yes                     | No           |   |
|                              | Receive information on the Activation Code expiration                          | Yes                     | No           |   |

Due to the above limitations, most Issuers keep the Tokenization Authorization and the Tokenization Event Notifications on the mainframe, but outsource the activation phase on the "yellow path" to a specialized Service Provider.

![](https://static.developer.mastercard.com/content/mdes-pre-digitization/documentation/img/issuers-token-activation-web-v2.png)

Future MDES releases (to be announced) will address the identified limitations and will make the adoption of the complete web-based Pre-Digitization messaging profiles possible, with no need for Network Services.