Netflix Integration

Contents

Overview

The MarketONE PLM domain supports Netflix integration. To better understand the value of this integration, consider the following option. An operator is integrated with Netflix. When a customer purchases a Netflix subscription through this operator (a six-month plan or a twelve-month plan), the operator generates a coupon and sends it to the customer via SMS. Once the customer receives the coupon it is now their responsibility to go onto the Netflix website, navigate to their account, and then enter the coupon code. Once the charge comes in this account gets applied by the operator. This option is less than seamless since it puts the onus on the customer to complete the transaction.

In response to this option the PLM domain offers the following two ways to integrate with Netflix.

Website Integration

The PLM domain provides a widget (iframe) that resides on the operator’s dashboard that a customer can use to purchase Netflix. The customer uses this widget to enter their mobile number to purchase a Netflix subscription. Once the customer enters their mobile number the PLM domain is called (through an account/validate API) to validate the customer’s account. If the account exists, the PLM domain validates it and then sends a token to Netflix. The PLM domain then communicates with Netflix to open up a UI for that particular customer to purchase their Netflix subscription. This integration frees the customer from having to go to the Netflix website and enter a coupon code.

When the PLM domain communicates with Netflix through the widget it does not share the mobile number. Instead, the PLM domain generates a unique identifier for each user (subscriber) to give to Netflix. This is called the Personal Account Identifier (PAI). The PLM domain points a mapping between the MSISDN subscriber and the PAI. This means that every time the PLM domain communicates with Netflix to open up a UI for a customer whose account has been validated, the PLM domain also provides them the PAI for the subscriber. Netflix then records this PAI, and the customer continues with Netflix by either creating a new Netflix ID for carrier billing, or logging into their existing Netflix account and changing their payment method from credit card to pay on bill. From then on, every month when Netflix has to send the PLM domain a transaction for posting, they will always and only send the PLM domain the PAI of the subscriber. The PLM domain then translates the PAI of the account (the subscriber number), and sends it back to the billing system for processing.

At this point they can either create a new Netflix ID (and go to the purchase and select carrier billing), or they can log into their existing Netflix account and then change their payment method from credit card to pay on bill. Once this user journey ends the customer comes back to the operator's website and the whole transaction finishes. But going forward every time every month when Netflix has to send the PLM domain a transaction for posting, they only send the PLM domain PAI. And then the PLM domain translates that PAI account (the subscriber number) and then sends it back to the billing system for processing.

Mobile Device Integration

Netflix services on mobile devices are no longer just for customer consumption. You can now use your mobile device to purchase Netflix services through an Android application that can be preloaded onto Android devices. This means that when an operator sells a new Android device, this Netflix application will be on it.

The customer uses their mobile device to access the application. The application reads from the mobile device that you are a subscriber of the operator. Netflix reads this fact from their end, and they also read your mobile number. Once this is done it automatically sends a request to the PLM domain to validate whether the subscriber’s account is in good standing, or if it has a balance (among other things). Once the PLM domain validates the account, then the rest of the user flow takes place using the Netflix mobile application.

Revision History

Version Description
2019.09 Added this topic.
2019.12 Added Contents and Revision History sections.