# Support
source: https://developer.mastercard.com/mdes-digital-enablement/documentation/support/index.md

## FAQ {#faq}

Mastercard is decommissioning MDES for Merchants (M4M) and replacing it with Secure Card on File (SCOF). SCOF provides the strategic platform for future remote commerce capabilities and enables access to additional services available through Mastercard Checkout Solutions. Existing M4M customers are expected to migrate to SCOF before the M4M decommissioning date. Yes. All merchants using M4M APIs should plan to migrate to SCOF. Continued use of M4M APIs after the decommissioning date is not supported. No. New remote commerce tokenisation implementations should be built using SCOF. New customer integrations are expected to onboard directly to SCOF rather than M4M. No. Mastercard provides a migration path that allows existing M4M tokens to be migrated to SCOF without requiring merchants or consumers to retokenize previously enrolled credentials. After migration, token lifecycle management activities and future API interactions will be managed through SCOF. Merchants should transition their integrations and operational processes to use SCOF services once migration is completed. The migration process consists of onboarding to SCOF and then migrating existing M4M token records using the migration capabilities provided by Mastercard. Merchants should complete onboarding before initiating token migration activities. Yes. SCOF operates as a separate service. Merchants should expect to provision and use SCOF-specific credentials and onboarding artifacts rather than reusing existing M4M credentials. SCOF provides access to a broader set of Mastercard Checkout Solutions capabilities and future enhancements. Examples include integration opportunities with services such as Click to Pay, Automated Billing Updater, Token Authentication Framework, and other value-added services available on the platform. Merchants who do not complete migration should expect disruption to M4M services as Mastercard executes the decommissioning plan. Migration should therefore be planned and completed before the announced deadline. All new remote commerce tokenisation use cases, integrations, and enhancements should be implemented using SCOF APIs and services. Merchants should avoid investing in new development against legacy M4M APIs that are being decommissioned. Refer the [tutorials](https://developer.mastercard.com/mastercard-checkout-solutions/tutorial/m4m_migration/) section that details how to move from M4M to Secure Card on File.

## Get Help {#get-help}

### Contact us for technical support. {#contact-us-for-technical-support}