Home
MATRIXX Subscriber Management
Managing Purchase Packages
Use purchase packages to dynamically group catalog items and package them so they can be purchased as a single unit by a subscriber or group. Purchased items can be added to or removed from a purchase package through the purchase package APIs without requiring pricing changes, providing a single entity for promotional and business operations.
Understanding Bundles Versus Purchase Packages
subscr_care/c_purchpkg_bundle_compare.html#concept_urn_1tm_nyb__table_hg2_tzq_35b describes the differences between a bundle and a purchase package.

Welcome
MATRIXX Release Notes
MATRIXX Architecture
MATRIXX Installation and Upgrade
MATRIXX Configuration
MATRIXX Security
MATRIXX Integration
MATRIXX Diameter Integration
MATRIXX Call Control Framework Integration
MATRIXX TM Forum Integration
MATRIXX 5G Integration
MATRIXX 5G Event Streaming
MATRIXX Event Streaming
MATRIXX Administration
MATRIXX Web App Administration
MATRIXX Monitoring and Logging
MATRIXX Policy
MATRIXX Kafka CDR Consumer
MATRIXX Pricing and Rating
MATRIXX Pay Now
MATRIXX Subscriber Management
- About Subscriber Management
  MATRIXX Subscriber Management provides an overview of subscriber-related data, including users, groups, subscriptions, devices, balances, and notifications. You can capture any attribute of a subscription and base rating on it, enforce subscription and group spending limits across all services and networks, and notify users associated with subscriptions and groups when the subscriptions and groups are nearing spending limits.
- Subscriber Authorization
  Authorization is the process of verifying the subscriber's balance has the amount required to allow usage. MATRIXX Engine supports service authorization and cut-offs to ensure subscriber usage is valid and revenue loss does not occur.
- Subscription-User Association
  You can associate a subscription with a user in a many-many relationship using the user APIs.
- Subscription-Device Association
  When a network message is received, the device information is used to guide the service usage to the subscription. A subscription can have any number of associated devices.
- Managing Subscriptions
  Managing subscriptions includes adding subscriptions to groups, removing subscriptions from groups, setting the status of subscription objects, and associating users with subscriptions. You can perform these operations by using MATRIXX Backoffice Customer Tool and any custom applications that call the SubMan APIs.
- Managing Devices
  You can create, provision, and delete devices by calling the SubMan APIs and scheduling automated tasks.
- Managing Users
  Managing users includes creating and deleting users, associating users with subscriptions, and assigning roles to users. You can perform these operations by using MATRIXX Backoffice Customer Tool and any custom applications that call the SubMan APIs.
- Managing Product Offers
  Managing product offers includes purchasing and canceling product offers, and removing expired product offers. You can purchase and cancel product offers by using MATRIXX Backoffice Customer Tool and any custom applications that call the SubMan APIs. Expired product offers are removed from _glossary/subscription.html and group wallets automatically after a configured amount of time.
- Managing Purchase Packages
  Use purchase packages to dynamically group catalog items and package them so they can be purchased as a single unit by a subscriber or group. Purchased items can be added to or removed from a purchase package through the purchase package APIs without requiring pricing changes, providing a single entity for promotional and business operations.
  - Creating Purchase Packages
    Create a new purchase package by specifying the purchase package data in the PurchasePackageData parameter in the PurchaseOffer API request. After the purchase package is created, all catalog items purchased in the PurchaseOffer request are associated with the new purchase package. For a complete list of PurchasePackageData parameters, see the discussion about MtxPurchasePackageData in MATRIXX Subscriber Management API.
  - Activating a Purchase Package
    When a purchase package has purchased items in a pre-active state, they are activated at the same time and share the same cycle.
  - Modifying Purchase Packages
    Use the ModifyPurchasePackage APIs to modify data in an existing purchase package.
  - Adding Owned Purchased Items
    After a purchase package is created, an existing purchased item owned by the purchase package owner can be added to the purchase package using the AddToPurchasePackage APIs.
  - Removing Purchased Items
    To remove a purchased item from a purchase package, use the RemoveFromPurchasePackage APIs. The purchased item is removed from the purchase package but is not canceled.
  - Suspending or Resuming a Purchase Package
    Each purchased item in a purchase package can be independently suspended and resumed by specifying the purchased item resource ID using the SuspendOffer and ResumeOffer APIs. To suspend or resume all purchased items in a purchase package, specify the purchase package resource ID using the SuspendOffer and ResumeOffer APIs.
  - Canceling a Purchase Package
    Each purchased item in a purchase package can be independently canceled by specifying the purchased item ResourceId in the CancelOffer SubMan APIs, or cancel all purchased items in a purchase package by specifying the purchase package ResourceId in the CancelOffer SubMan APIs.
  - Purchase Package Cycle
    A purchase package defines a cycle. When a purchased item is added to the purchase package, the purchase package cycle definition overrides the cycle data of the product offer and bundle definitions in pricing.
  - Purchase Package Recurring Processing
    Recurring processing occurs at the purchase package level (not at the purchased item level), and applies recurring pricing components during purchase, renewal, and resume operations.
  - Purchase Package Offer Life Cycle and Grace Period
    A purchase package is not associated with an offer life cycle profile and does not have an overall status. Each purchased item in a purchase package has its own offer life cycle profile and can have its own offer status, and the purchased items can have different offer status.
  - External Payment Requests
    You can configure MATRIXX Engine to automatically request external payments based on a recurring cycle.
  - Extending a Purchase Package
    Purchase packages can contain extended attributes that define additional information about the purchase package.
  - Purchase Package Normalization
    Normalizers can be applied on individual product offer data or on the purchase package.
  - Purging Purchase Packages from the System
    Purchased items within a purchase package have their own validity time and can be independently canceled, but a purchase package does not have an explicit validity time. When all purchased items have been removed from a purchase package or have been purged after becoming inactive, the purchase package is automatically deleted from the database.
  - Purchase Package Discount Component Scope
    Apply the scope of a discount to a product offer to determine the charges to which the discount is applied. For example, select Any Purchased Items of Owner to apply discounts to charges from all purchased items owned by the event initiator. In addition to offers owned by the event initiator, you can enable discount pricing components to be selected from offers owned by the group, subscriber, or device.
  - Purchase Package Discount Filters
    Configure filters to allow percentage discount price components from a catalog item in a purchase package to determine which charging price components the discount should be applied to other specific catalog items in the same purchase package.
  - Purchased Items With and Without a Purchase Package
    subscr_care/c_purchpkg_purchased_items.html#concept_jyq_ysm_nyb__table_twj_rdr_35b describes the differences between purchased items purchased in a PurchaseOffer request as a purchase package and purchased items purchased in a PurchaseOffer request (no purchase package).
  - Understanding Bundles Versus Purchase Packages
    subscr_care/c_purchpkg_bundle_compare.html#concept_urn_1tm_nyb__table_hg2_tzq_35b describes the differences between a bundle and a purchase package.
  - Events and Notifications
    Events and notifications are generated for purchase packages.
- Rehoming
  Rehoming is the process of moving a user, group, device, or subscription from one sub-domain to a different sub-domain in a multi-domain platform.
MATRIXX Subscriber Management API
MATRIXX Business API SDK
My MATRIXX Help
MATRIXX Backoffice Customer Tool Help
MATRIXX Third-Party Licenses
Glossary

Understanding Bundles Versus Purchase Packages

Bundles Versus Purchase Packages describes the differences between a bundle and a purchase package.

Table 1. Bundles Versus Purchase Packages
	Bundle	Purchase Package
Contents	A bundle contains one or more product offers. A catalog item is associated with a bundle. You define the bundle and catalog item in pricing first. When purchasing a bundle, all the product offers configured in the bundle are purchased. You cannot add more product offers to the bundle. You cannot remove a product offer from the bundle.	A purchase package contains one or more purchased catalog items. You specify the list of catalog items and the purchase package data at purchase time. The purchase package is not defined in pricing. You can add purchased items to the purchase package. You can remove purchased items from the purchase package.
Offer Lifecycle	The bundle is associated with an offer lifecycle profile and the status of the bundle is for the entire purchased item. Suspend, resume, and cancel operate on the bundle level.	Each purchased item in a purchase package has its own offer lifecycle profile and its own status. Suspend, resume, and cancel can operate on individual purchased item level or on the purchase package level.
Validity Time	Validity time is defined on a bundle. A bundle has the start time and end time.	A purchase package does not have validity time. Each purchased item in a purchase package has its own start time and end time.

For more information about bundles, see the discussion about bundles in MATRIXX Pricing and Rating.