Skip to main content
If a Storefront Gateway User is associated to a Storefront Gateway Subscription entity that represents a paid streaming TV service, then this association itself can define the entitlements that user has to the service. If the service involves a variety of functional capabilities, those functions may be captured as Storefront Gateway Features associated to (i.e., contained within) the Storefront Gateway Subscription entity. For example:
  • A customer’s records in a billing system would be represented by a Storefront Gateway Account
  • A Mobile Service Plan (MSP) under the billing account would be represented by a Storefront Gateway Subscription
  • A special capability for the MSP (e.g., unlimited data) may be represented by a Storefront Gateway Feature
How the data from an external system maps to the Account/Subscription/Feature (A/S/F) hierarchy depends on the type of service, the type of service provider, the service provider’s billing system, and the business needs defined during the initial integration between the service provider and Storefront Gateway. The Storefront Gateway data model is flexible enough to map most any external record data to the A/S/F hierarchy, but the needs may vary from tenant to tenant. A Storefront Gateway Subscription is “associated” with its parent Account at the moment the Subscription is created in Storefront Gateway. A Subscription can not exist in Storefront Gateway without a parent or container Account. Conversely, Storefront Gateway Features cannot exist without a parent or container Subscription. A Storefront Gateway Subscription entity contains the following default properties: Subscription entities also contain attributes: