# FAQs
source: https://developer.mastercard.com/mdes-pre-digitization/documentation/faqs/index.md

A Sandbox environment is not available for pre-digitization APIs as these are Outbound APIs (i.e. An Issuer exposes the services and MDES consumes those services). MDES does not provide a token requestor simulator. It is recommended that each Issuer works with their corresponding wallet provider/token requestor for testing in MTF and verifying in Production. An issuer will receive notifications when:

* the token lifecycle update is triggered as a result of the Service Provider update (for example, the service provider suspends or deletes the token)
* the state of a token changes as a result of an update made by an Issuer via the Customer Services API.

If the token state has changed based on an update supplied by Issuer via the 0302 file then the notification is not provided to the Issuer.
The notification is only provided when token status has changed. If the update is initiated but failed or is not completed, the status does not change. Therefore, no notification is provided for failed or incomplete update. For example, the Notify Token Updated is provided when Account holder suspends or deletes the token. The first 48 characters of the consumer key (prior to the '!' character). A project can be in the 'Under Review' status for a maximum of 30 days. After that it is automatically switched to the **Decline** status.
Note: Mastercard CIS does not get a notification for any changes in the Project created on Mastercard Developers. Contact your Mastercard representative to get the latest list of CAs. Typically, Issuers should aim to process requests in 300ms or less. Mastercard recommends that the issuer should support a minimum of 50 TPS. Contact your Mastercard representative during onboarding to get the MDES outbound IP addresses. Yes, MDES supports a hybrid model for pre-digitization messages. Refer to the details [here](https://developer.mastercard.com/mdes-pre-digitization/documentation/configuring-services/example-msg-profile-configs/index.md#hybrid). No, the current version of Authorize Service does not support operator-specific data for the token profile. Issuers are recommended to use ISO messages to support this functionality.