OTT Integration: Overview

Overview
User Onboarding Journey
How the Integration Works
Standard OTT Provider Integrations
Revision History

Overview

In MarketONE's over-the-top (OTT) managed subscription model, a customer purchases OTT services at the OTT provider's portal. That purchase is processed by MarketONE and the user's service entitlements are provisioned to the OTT service.

User Onboarding Journey

A customer purchases a digital service directly from the OTT provider (e.g., Spotify streaming service). The purchase, the management, and the cancellation of the service subscription is managed by the OTT. The OTT prompts the user to choose their service provider (SP) to enable direct carrier billing (DCB). The OTT onboards with MarketONE at the SP, supporting DCB integration. The customer then logs into the OTT application to create the OTT user profile. MarketONE then integrates to the SP BSS to manage account validation and DCB transations.

How the Integration Works

This onboarding and monetization flow requires that the OTT-driven subscriptions integrate with MarketONE. The following images provide a generic example of this integration in action.

1. Validating the User Account from the OTT

The user selects direct carrier billing (DCB) on their OTT service. They then enter their mobile number for validation, thereby invoking the POST /account/validate API call.

2. Validating the User Account from the CSP

MarketONE requests the validation of the user account from the SP by invoking the POST /account/validate API call. Once the validation is finished, the SP notifies MarketONE with the results.

3. Generating the One-Time User PIN

Once the user account is validated, the OTT then invokes the POST /pin API call to generate a one-time PIN for the user.

4. Requesting MarketONE to Send the One-Time User PIN

The OTT then requests MarketONE to send the one-time PIN to the user by invoking the POST /notification API call.

5. Requesting the SP to Send the One-Time User PIN

MarketONE then requests the SP to send the one-time PIN to the user by invoking the POST /notification API call. The user then receives the PIN from the SP notification system.

6. Validating the One-Time User PIN

The user then enters the one-time PIN on the OTT application, and is validated by MarketONE by invoking the POST /pin/validate API call. This also confirms that the subscription has been purchased.

7. Sending the Transaction for Posting

The OTT then leverages the POST /transaction API call to send the transaction for posting.

8. Sending the Transaction for Billing

MarketONE then leverages the POST /transaction API call to send the transaction to the SP for direct carrier billing (DCB). The user is then notified of the charge by the SP.

Standard OTT Provider Integrations

The following table contains the standard OTT integrations that MarketONE presently supports:

OTT Provider	Description
	Google Play Store. Direct Carrier Billing (DCB) for charges.
	Apple iTunes Store. DCB for charges.
	Netflix. Subscription video on demand (SVOD). Standard Netflix OTT integration. Netflix managed pricing.
	Spotify. World's leading subscription streaming music service.
	DirectTV Go. International subscription TV everywhere streaming service.
	Mexican Football League. D2C subscription video on demand service.