> ## Documentation Index
> Fetch the complete documentation index at: https://docs.m1amdocs.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Service Activation

As part of the purchase of a digital service, MarketONE delivers a pre-built process that consists in capturing the customer request, confirming the purchase, enabling service monetization, and the entitlement of the user for the service. If it is required, a provisioning integration request can also be sent to the Merchant backend for the MarketONE user.

## Supported Capabilities

MarketONE user orchestration is delivered as part of Storefront Gateway. The Storefront Gateway process engine contains pre-built processes that capture the purchase and then orchestrate the subscription activation in Commerce Engine. Service activation is performed via Partner Ecosystem Management. Storefront Gateway also integrates with the other BSS systems (if needed) to hand off the request for any fulfillment required. Storefront Gateway maintains the entitlements of the end user to the services purchased, as well as allowing the user to share their services with other members of the household and family (within the restrictions of the services). While Storefront Gateway orchestrates the entire experience, the subscription lifecycle management is maintained in Commerce Engine and the provisioning of the service at the Merchant backend is done via Partner Ecosystem Management. Partner Ecosystem Management maintains the integration with the Merchant and keeps them in sync in case the interfaces are updated by either party.

The following service activation scenarios are supported by MarketONE:

* Creating a new active user via Merchant integration.
* Creating a new active user on the Merchant website via deep linking.
* Associating an existing user account on the service to the new payment method at the time of purchase.
* Disconnecting or canceling a subscriber on the service.

Most of the integrations are done between Partner Ecosystem Management, the Merchant applications, and systems using standard published APIs. However, in cases where the size of the Merchant warrants integration to their specific APIs, modifications to the Partner Ecosystem Management integration layer can be made to make the experience as seamless as possible.

## Recommended Experience

**User Orchestration**

Storefront Gateway has pre-built processes that deliver end-to-end experiences from onboarding a user, associating an account, provisioning a service, delegating, sharing, and managing consent. These processes are leveraged by the MarketONE digital store when the user selects an action. Storefront Gateway then orchestrates the process, and with the pre-integration into Partner Ecosystem Management and Commerce Engine, it manages the entire lifecycle of the process. In cases where the user action necessitates an orchestration or an activity on the legacy BSS, Storefront Gateway can be integrated into the legacy BSS as well. The details of the integration to the legacy stack will be dependent on the specific customer and the use cases. Components which are part of MarketONE should be orchestrated by Storefront Gateway alone to leverage the best practices and integrations out-of-the-box (OOTB).

**Service Activation**

Service activation into the Merchant backend is managed by Partner Ecosystem Management. Storefront Gateway makes the request into Partner Ecosystem Management at the specific step of the process where Merchant activation is needed, and based on the OOTB integrations between Partner Ecosystem Management and the Merchant backend, the service is activated. Partner Ecosystem Management comes with a prescriptive set of APIs which can be used for the integration with the Merchant backend. These APIs range from creating the Merchant product, initiating a payment transaction, and creating and associating a user account into the Merchant backend application.

It is recommended that most Merchants leverage the OOTB MarketONE APIs for integration into the platform. These APIs are available as part of a software development kit (SDK) which can be consumed by the Merchant and can be integrated into the ecosystem. Leveraging these APIs will not only yield to faster onboarding, but also to extending the reach of the Merchants to the broader set of customers on the Amdocs MarketONE platform.

In certain cases Amdocs will support changes to Partner Ecosystem Management (for large digital Merchants like Netflix and Spotify).

**Note:** While changes to the APIs can be done, the end-to-end experience has to be consistent based on the APIs exposed by MarketONE to ensure a frictionless end user engagement.

**Parent topic:**[Developer Best Practices](r_developerBestPractices)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.