OTT Onboarding: Checklist

Contents

Overview

This topic contains standard questions that must be answered, and specific information that must be considered, when an over-the-top (OTT) provider onboards to MarketONE.

Standard Questions

General Information

  • What is the name of the OTT?
  • What is the OTT website?
  • What is the technical contact information?
  • What is the commercial contact information?
  • What is the OTT address?
  • What is the OTT product category?
  • What is the OTT product that is offered?
  • What are the countries in which the OTT operates?
  • What service provider(s) (SP) is the OTT currently engaged with?
  • What is the current target launch time with the current engagement?

Charges

  • What is the transaction currency?
  • Do you support refunds?
  • Is the tax included in your transactions and refunds?
  • Do you support upgrades/downgrades of your products/services (MarketONE managed subscriptions)?
  • Do you support suspend resume on your products/services (MarketONE managed subscriptions)?

Service Level Agreement (SLA)

  • What is the known or regularly planned downtime?
  • Can the downtime be made public?

Subscription Flows

OTT Managed Subscription Flow

  • The OTT provider has complete control of the subscription lifecycle (pricing and billing cycle and charging of the service offers).
  • OTT providers will leverage MarketONE to provide a Direct Carrier Billing (DCB) option as a payment method to the end-user.
  • End-Users will view this as another method to pay for the service, similar to how a credit card is used to pay for the service.
  • This model can also be used for one-time payment purchases, as well as recurring subscription payments.

MarketONE Managed (CSP Initiated) Subscription Flow

  • MarketONE controls the subscription lifecycle for a given set of subscriptions applied to an OTT service.
  • MarketONE is responsible to inform the OTT provider about the service entitled via a service provisioning call, or about supporting the ability to actively query the entitlements.
  • Examples of this include services purchased directly for a SP channel (possibly at a reduced price, or free period, or in combination with other bundled services).
  • The end-user will go to the SP channels to manage the subscriptions related to the service.

Required Information

MarketONE requires the following configuration information from the OTT provider in order to be set up on the platform.

Product Offering Details

  • Product name
  • Product description (optional)
  • Product code
  • Product category (cloud services, commerce, connectivity, content, devices)

OTT Provisioning End Point

  • Endpoint URLs (optionally with a port number)
  • For example: https://acme.company.com/m1-subscription-events:443

API Key

  • One API_KEY per SP for the sandbox (for additional security which will be added in an authorization header).
  • The API Key is used for callbacks from MarketONE to the OTT in the MarketONE managed subscription flow.

Email Address

  • The email address to receive the optional error notification.

Retry Options for Callbacks (MarketONE Managed Subscriptions)

  • DURATION_VAL: the number of times the OTT wants MarketONE to retry the callbacks.
  • INTERVAL_VAL: the number of seconds between retries.

Revision History

Version Description
2020.07 Added this topic.