# Setting up Messaging Profile
source: https://developer.mastercard.com/mdes-pre-digitization/documentation/configuring-services/message-profile-setup/index.md

## Overview {#overview}

The Message profile is where MDES Manager will record a certain configuration of pre-/post- digitization messages that an issuer will apply to an account range. A Message profile may include mandatory messages, conditional messages, and optional messages. Each message may be implemented with either a network service, a web service, or both. The following sections outline how the mandatory, conditional, and optional messages can be configured for the various working modes of the Pre-Digitization API. The legends used to depict the mandatory, conditional, and optional messages are as follows:
![](https://static.developer.mastercard.com/content/mdes-pre-digitization/documentation/img/legends.png)

##### Legend for Mandatory, Conditional, and Optional Messages

Note: Refer to the [Create a Message Profile](https://w201.mastercardconnect.com/hsm3ca267/homememb/library/shared/ENG/MDESMUG/suitehelp/t_MDESMUG_MsgProfiles_CreateMessageProfile.html) section in the MDES Manager Application user guide for more information on how these options can be selected.

## Card Availability and Eligibility Messages Selection {#card-availability-and-eligibility-messages-selection}

In this section, for the Pre-digitization API, the issuer must ++choose one++ of the following options, but not both:

* Authorize Service (AS) -- With AS, both the Tokenization Authorization (TA) and the Tokenization Eligibility (TE) options are disabled from being chosen. In this case, the service authorization is performed by a web service, which can be outsourced by the issuer to a specialized Service Provider.
* Tokenization Authorization (TA) -- With the TA option, the AS option is disabled. The issuer may or may not choose to use the TE option. In this case, the service authorization is a network message and is performed by the issuer or its processor.

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

##### Card Availability and Eligibility - Mandatory Section

Note:   

* "AS OR TA" exclusive selection mode is due to the fact that there cannot be two decisions taken independently by two entities, for example, Issuer Host and web service.
* AS can be considered the equivalent of TA. TE has no web service equivalent.
* Currently, Mastercard Developers supports only one hostname (with port number, if required) and context root for a Messaging Profile with all its API services, then the same Service Provider will support both RAM and DAC.

## Authentication and Activation Messages Selection {#authentication-and-activation-messages-selection}

In this section, choose from the following options:

* Request Activation Methods API (RAM) - If authorization is required but you do not plan to provide the activation methods using the Card Availability and Eligibility response, you can use the Request Activation Methods API. When you inform MDES that a cardholder needs authenticating, MDES sends the RAM API message once, enabling you to respond with the required Activation Methods.

* Activation Code - The issuer must choose who generates the activation code from the following options:

  * **Mastercard (Recommended)**: Select this option if you are using Activation Code as an Activation Method and want MDES to generate and validate those.
  * **Issuer**: Select this option if you are using Activation Code as an Activation Method and do not want MDES to generate and validate the activation code. To deliver the Activation Code, you can then either select a Network Message or the API.
  * **No Activation Code**: Select this option if do not wish to use Activation Codes.
* Generation of Activation Code - The issuer may choose to receive the activation code from one or both of these:

  * Network Messages -
    * Activation Code Notification (ACN) 0100/0200 OR Issuer Token Notification 0620 - These messages provide the Activation Code for Network messages, if generated by Mastercard, and associated data for delivery to cardholder as well as the Cardholder Activation Method preference (how the cardholder receives the code).
  * Pre-Digitization API -
    * Deliver Activation Code API (DAC) - These messages to provide the Activation Code for the Pre-Digitization API, if generated by Mastercard, and associated data for delivery to cardholder as well as the Cardholder Activation Method preference (how the cardholder receives the code).

![](https://static.developer.mastercard.com/content/mdes-pre-digitization/documentation/img/auth-act-msg-select.png)

##### Authentication and Activation - Conditional Section

Note: If ACN and DAC are simultaneously selected, then MDES delivers the Activation Code both to the Issuer Host and to the web service. Each of these entities may use the same type of distribution channel selected by the Cardholder (either email or SMS text), targeted to the same recipient address (email address or mobile phone number), to provide the cardholder with a unique Activation Code, coming on separate paths. This technique is known as a dual channel assurance. It may provide a higher level of security to the activation of a service (at a higher cost) because the cardholder may compare the two Activation Code values received on independently controlled channels and acknowledge the service activation only if they are the same.

## Tokenization Completion Messages Selection {#tokenization-completion-messages-selection}

In this section, the issuer may choose one or both of the following options:

* Tokenization Complete Notification (TCN) for Network Messages -- The TCN option reports the completion of a service activation back to the Issuer Host (e.g., when a service activation was requested with a TA network message).
* Notify Service Activated (NSA) for Pre-digitization API -- The NSA option reports the completion of a service activation to a web service instead of the Issuer Host (e.g., when the service authorization was requested with an AS web service or when a service authorization was requested with a TA network message and a Cardholder activation and authentication was performed with a RAM API message).

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

##### Tokenization Completion - Optional Section

Note: NSA can be considered the equivalent of TCN.

## Token Lifecycle Event Messages Selection {#token-lifecycle-event-messages-selection}

In this section, the issuer may choose one or both of the following options:

* Tokenization Event Notification (TVN) -- The TVN option reports a tokenization event back to the Issuer Host (for example, when the service authorization was requested with a TA network message).
* Notify Token Updated (NTU) -- The NTU option reports a tokenization event to a web service instead of the Issuer Host (for example, when the service authorization was requested with an AS web service).

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

##### Token Lifecycle Event Messages Selection - Optional Section

Note: NTU can be considered the equivalent of the status reporting part of TVN. NTU does not implement the error handling mechanisms for the Activation Code.

## Suspicious Events for MCBP Wallets {#suspicious-events-for-mcbp-wallets}

In this section, the issuer may opt-in to receive notification for suspicious events:

* Notify Suspicious Events (NSE) API - This option allows issuers to receive a notification when suspicious events are detected.

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

##### Suspicious Events for MCBP Wallets - Optional Section