Developer Best Practices

Contents

Overview

This section contains developer best practices for implementing and optimizing the Amdocs MarketONE solution. Each Recommended Experience section listed in the Summary table below promotes the use of practices that have been derived from delivering frictionless end user experiences. Due to the geography and the location of the service provider, the type of service being delivered, and the market segment being addressed, it is expected that these experiences may vary. It is therefore strongly recommended that they be aligned to the following guidelines to achieve the business objectives laid down for MarketONE.

Summary

The following table contains links to developer best practices topics found in this section, along with a summary of the Recommended Experience required for launching an end-to-end offering for over-the-top (OTT) provider onboarding and monetization.

Topic Recommended Experience
Billing Methods Credit Card, Direct Carrier Billing (DCB), and other payment methods, are supported via the MarketONE Subscription Management (SLM) domain.
The SLM domain should be the only application to manage the credit card information of the user.
A token of the payment method should be managed and maintained in the MarketONE User Management (ULM) domain to allow for quicker retrieval and to support payment sharing scenarios.
Billing Parameters All charges should be billed in advance and not in arrears.
Prorations are not supported. Customers have service until the paid through date, even if they cancel in the middle of the cycle.
Subscription charges can be offset with the billing cycle, and should be maintained as such (with a note against the item on the invoice).
Companion App The purchase and management of over-the-top (OTT) provider services will be done via unassisted (digital) channels only.
Assisted channels (like call centers) should guide the customer via a link to the unassisted experience to ensure a consistent end user experience.
Content Management MarketONE manages the product related content (artwork, description, and images).
Communications service providers (CSPs) can use their own CMS and integrate it into MarketONE.
Eligibility The ULM domain holds the user profile related to demographics and segments (etc).
Maintaining and populating the user profile will be external to MarketONE.
The ULM domain will maintain the user identity and have the services associated to the customer account populated from the BSS.
The rule engine (delivered as part of MarketONE) will retrieve the user profile and the user identity, combined with the product list, from the SLM domain and execute the eligibility rules before responding back to the MarketONE digital store.
Pricing All product pricing, including discounts and coupon code configurations, is managed and maintained within the SLM domain.
Product Groups All products are configured and maintained within the SLM domain.
Combining the products into one group for display is done in the MarketONE digital store.
Service Activation The orchestration of the entire user experience is managed via the ULM domain process engine.
The ULM domain has pre-built out-of-the-box (OTTB) processes and pre-integrations to the SLM domain and the MarketONE Partner Management (PLM) domain which should be leveraged for a faster TTM.
OOTB APIs for OTT integrations should be leveraged for onboarding an OTT provider, ensuring the user experience is consistent.
For advanced use cases like associating an existing OTT account to the purchase, should be done via deep linking on the MarketONE digital store.
The actual provisioning of the service on the OTT backend is done via the PLM domain.
Settlements Wholesale flat or revenue share are the recommended settlement models.
Price plans for settlements can be tiered if they part of the agreement.
Trial Period The SLM domain manages the trial period for the OTT product.
To make the experience consistent, the same trial period should be configured for all OTT services.
Trial Validation The SLM domain can validate credit cards via tokens to ensure a user does not get multiple trial periods on the same credit.
CSPs should capture credit card at the time of purchase, even if there is a trial period and the user is not being charged until it ends.

Revision History

Version Description
2020.03 Added this topic.