# Examples of Messaging Profile Configurations
source: https://developer.mastercard.com/mdes-pre-digitization/documentation/configuring-services/example-msg-profile-configs/index.md

The examples presented in this section are described for the following use modes:

* [Web Services Only](https://developer.mastercard.com/mdes-pre-digitization/documentation/configuring-services/example-msg-profile-configs/index.md#web-services-only)
* [Hybrid](https://developer.mastercard.com/mdes-pre-digitization/documentation/configuring-services/example-msg-profile-configs/index.md#hybrid)

Note: Examples of the *Network Messages only* mode can be found in the Pre-Digitization section of the [Mastercard Digital Enablement Service Issuer Implementation Guide](https://techdocs.mastercard.com/bundle/m_MIIG/page/c_MIIG_Predigitization.html)

## Web Services Only {#web-services-only}

### No Consumer-specific Communication Channel {#no-consumer-specific-communication-channel}

Web service manages only the decision of authorizing the service, i.e., digitizing a card presented by the Cardholder through the Token Requestor. Web service does not manage a Cardholder specific Activation Method and communication channel (e.g., SMS or email), and does not manage Cardholder contact information (mobile number or email address).

Web service configures the Issuer Enablement with a default Activation Methods List (AML) for an Account Range. This list includes only Cardholder non-specific Activation Methods, e.g., Cardholder initiated call to a manned/automated call center.

Web service manages no Activation Methods List (AML) in relationship with cardholders.

This maybe the case when:

* Issuers favor detection and reaction fraud mechanisms to upfront investing in device lost \& stolen prevention methods.
* Time to market is short; fast operation prevails against strong risk control.
* Web service is not concerned with cardholder convenience during Cardholder Activation and Authentication, which generally may lead to a high abandonment rate.

Note: Cardholders calling an out-of-band call center is known as being rather time consuming and as not being very user friendly (line busy, operators busy, etc.).

The choice of the Message Profile configuration for this operation mode is shown hereafter, and the Message Profile is referred to as "NoConsumer-specific".

![Web Service Only Example](https://static.developer.mastercard.com/content/mdes-pre-digitization/documentation/img/WebOnly_NoConsumerSpecific.png)

The resulting messages flow is shown below for the following scenario:

* Service activation is successfully completed ("green path") by the cardholder in an out-of-band interaction with the issuer (for example, Cardholder-initiated call to a manned/automated call center).
* Following service activation, a Token with Token Unique Reference (TUR) is generated and activated.
* On Cardholder's demand, which is received at a later stage during the operation of the Token, the Token Requestor requires the deletion of the Token referred to with TUR.

![New image](https://static.developer.mastercard.com/content/mdes-pre-digitization/documentation/img/functionality-explained-for-issuers-v1-bt-page-13.png)

### Integrated Consumer-Specific Communication Channel {#integrated-consumer-specific-communication-channel}

Web service manages:

* Decision of authorizing the service, i.e., digitizing a card as presented by the Cardholder.
* Interaction with Cardholders, registering their preferences for a dedicated Activation Method, communication channel (e.g., SMS, email), and contact information (mobile number or email address).
* Distribution of Activation Code to the Cardholder, using a Cardholder-specific communication channel.

This maybe the case when:

* Issuers favor strong consumer authentication for preventing "lost \& stolen" device fraud.
* Web service is Cardholder centric and invests in decreasing the abandonment rate.

Note: Cardholders getting an Activation Code within the Token Requestor application is considered a good Cardholder experience. Most used communication channels the application may propose to Cardholders are email and SMS, depending on the capabilities of the device on which the digitization is performed.

The choice of the Messaging Profile configuration for this operation mode is shown hereafter, and the Messaging Profile is referred to as "IConsumer-specific".

![Consumer-Specific Communication](https://static.developer.mastercard.com/content/mdes-pre-digitization/documentation/img/WebOnly_ConsumerSpecific.png)

The resulting messages flow is shown below for the following scenario:

* Service activation is successfully completed by MDES through positive verification of the Activation Code.
* Completion ends up with the generation of an active Token with Token Unique Reference (TUR).
* Later, during payment transactions, Token referred to with TUR is suspended due to Mobile PIN being locked.

![New image](https://static.developer.mastercard.com/content/mdes-pre-digitization/documentation/img/functionality-explained-for-issuers-v1-bt-page-15.png)

### Separated Consumer-specific Communication Channel {#separated-consumer-specific-communication-channel}

Web service manages all three activities mentioned in the integrated use case -- i.e., decision of authorizing the service, interaction with Cardholders, and distribution of Activation Code -- but it is preparing to outsource in the future (see note below) the interaction with Cardholders, and the distribution of the Activation Code.
Note: In the current release Open API is supporting one and only one hostname (with port number, if required) and context root for all the API endpoints in a Messaging Profile. Therefore at the moment Issuers cannot assign separate web servers for answering different API calls.

The choice of the Messaging Profile configuration for this operation mode is shown hereafter, and the Messaging Profile is referred to as "SConsumer-specific".

![Separated Consumer-Specific Communication](https://static.developer.mastercard.com/content/mdes-pre-digitization/documentation/img/WebOnly_all.png)

The resulting messages flow is shown below for the following scenario:

* Service activation is successfully completed by MDES through positive verification of the Activation Code.
* Completion ends up with the generation of an active Token with Token Unique Reference (TUR)
* Token referred to with TUR is suspended by the Cardholder.

![New image](https://static.developer.mastercard.com/content/mdes-pre-digitization/documentation/img/functionality-explained-for-issuers-v1-bt-page-21.png)

## Hybrid {#hybrid}

In the use cases described in this section the Issuer Host and the web service share some of the tasks to be fulfilled during pre-digitization/post-digitization.

### Web service Based Communication Channel {#web-service-based-communication-channel}

In this model the Issuer Host fulfils the following two tasks:

* Decision of authorizing the service.
* Interaction with Cardholders for Activation Code management.

However, the distribution of Activation Code to the Cardholder, using a cardholder-specific communication channel, is outsourced to a Communications Service Provider. The choice of the Message Profile configuration for this operation mode is shown hereafter, and the Message Profile is referred to as "WSBased-CC".

![Hybrid](https://static.developer.mastercard.com/content/mdes-pre-digitization/documentation/img/WSBasedCC.png)

The resulting messages flow is shown below. Note that the web service, Notify Service Activated, may inform the Communications Service Provider about the successful completion of its distribution task of the Activation Code.

![New image](https://static.developer.mastercard.com/content/mdes-pre-digitization/documentation/img/functionality-explained-for-issuers-v1-bt-page-19.png)

### Web Service Based Cardholder Activation and Authentication {#web-service-based-cardholder-activation-and-authentication}

In this model the Issuer Host determines the decision of authorizing a service, with no interfering into the Activation Code management. The web service overtakes entirely the management of the Activation Method Lists and the distribution of Activation Code to the Cardholder, using a Cardholder-specific communication channel.

The choice of the Messaging Profile configuration for this operation mode is shown hereafter, and the Messaging Profile is referred to as "WSBased-CAA".

![Web Service Based](https://static.developer.mastercard.com/content/mdes-pre-digitization/documentation/img/WSBasedCAA.png)

The resulting messages flow is shown below.

![New image](https://static.developer.mastercard.com/content/mdes-pre-digitization/documentation/img/functionality-explained-for-issuers-v1-bt-page-17.png)