Home
MATRIXX Subscriber Management
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.
Pre-Active Purchased Items
A pre-active purchased item is a purchased catalog item that can be activated at a later time by a status life cycle transition, a _glossary/subscription.html, group, or device SubMan modify request, by usage-triggered activation, and by time-triggered activation.
Pre-Active Purchased Item Activation
A pre-active purchased item can be activated as the result of a status life cycle transition, by a _glossary/subscription.html, group, or device SubMan modify request, by usage-triggered activation, and by time-triggered activation. If the purchased item is a bundle, all product offers in the bundle are activated at the same time.
Activation Events
When you activate a pre-active purchased item, an MtxPurchasedItemActivationEvent EDR is generated.

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.
  - Purchasing Product Offers
    Product Offer versions can be purchased as catalog items for a subscriber, group, or device and can be configured to trigger a notification to be sent at purchase time.
  - Purchasing Bundles
    Bundle versions can be purchased as catalog items for a subscriber, group, or device and can be configured to trigger a purchase notification. When a bundle is purchased, all product offers in the bundle can be used for rating and policy decisions.
  - Purchased Items
    A purchased item is a customization of a purchased catalog item.
  - Pre-Active Purchased Items
    A pre-active purchased item is a purchased catalog item that can be activated at a later time by a status life cycle transition, a _glossary/subscription.html, group, or device SubMan modify request, by usage-triggered activation, and by time-triggered activation.
    - Pre-Active Purchased Item Activation
      A pre-active purchased item can be activated as the result of a status life cycle transition, by a _glossary/subscription.html, group, or device SubMan modify request, by usage-triggered activation, and by time-triggered activation. If the purchased item is a bundle, all product offers in the bundle are activated at the same time.
      - Activation by Usage
        When you create a product offer in My MATRIXX, you can specify if the purchased item is automatically activated if usage is received with a service type that matches that of the offer.
      - Activation by Time
        When you purchase a catalog item (product offer or bundle) in a pre-active state, you can specify a time at which the offer or bundle is activated if it has not been activated.
      - Activation with Status Life Cycles
        Pre-active offers owned by a _glossary/subscription.html can be activated in a status life cycle when the MtxStatusActionActivateAllOffer transition action is triggered in a subscription life cycle.
      - Activation with the SubMan APIs
        You can use the SubMan APIs to activate a pre-active purchased item by changing the Status field to purchased.
      - Activation Components
        In My MATRIXX, you can add purchased item activation components to a product offer that are applied when a purchased item that was purchased in a pre-active state is activated.
      - Activation Filters
        Activation filters added to a subscription product offer in My MATRIXX determine when product offers and bundles are activated by usage.
      - Activation Events
        When you activate a pre-active purchased item, an MtxPurchasedItemActivationEvent EDR is generated.
      - Activation Revenue Recognition
        Purchase charges can pay for a purchase grant or an activation grant. Revenue is recognized at purchase time only if the purchase charges pay for purchase grants. An activation grant can be the target of a purchase charge or activation charge and in this case, the revenue recognition type is set to pending. If a purchase charge pays for an asset, the revenue recognition type is determined by the asset type. Consumption-based assets are liability assets; daily (or straight-line) assets are non-liability assets.
    - Pre-Active Purchased Item Cancelation
      You can cancel a pre-active purchased item using the SubMan APIs. Offers that are canceled as the result of a status life cycle cancel action can include pre-active purchased items.
    - Pre-Active Purchased Item Expiration
      When purchasing a product offer or bundle in a pre-active state, the purchase request can optionally include an expiration time. If the purchased item is not activated by the specified expiration time, it is automatically expired and canceled and is not activated.
    - MtxPurchasedOfferData
      Request to purchase a catalog item. One of CatalogItemId, ProductOfferId, or ExternalId must be present.
    - MtxPurchasedOfferInfo
      Information returned in a response for a purchased offer.
    - MtxPurchaseEventOfferInfo
      No Description
    - MtxPurchaseEventBundleInfo
      No Description
  - Pending Activation Purchased Items
    When purchasing a catalog item, you can specify that pending activation is allowed when there are enough funds for the purchase charge but not enough funds for activation and recurring charges.
  - Canceling Product Offers
    Subscription, one time, and global product offers can be canceled at any time for a subscriber, group, or device and can be configured to trigger a notification to be sent at the cancelation time. A contract product offer terminates either when the contract term ends or when the subscriber terminates the contract early through a cancel offer operation.
  - Canceling Bundles
    Bundles can be canceled at any time for a subscriber, group, or device and can be configured in My MATRIXX to trigger a cancelation notification. Product offers within a bundle cannot be canceled individually when purchased as part of a bundle. Only the product offer bundle can be canceled.
  - Removing Expired Purchased Offers
    Purchased product offers that have expired (purchased individually or as part of a bundle), either because they have been canceled or their validity period has ended, are removed from the owning subscriber, group, or device 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.
- 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

Activation Events

When you activate a pre-active purchased item, an MtxPurchasedItemActivationEvent EDR is generated.

The MtxPurchasedItemActivationEvent EDR references all recurring events generated for prorated recurring processing, and those recurring events reference the MtxPurchasedItemActivationEvent EDR. The EventTypeArray in the MtxPrimaryEvent MDC includes event type 43 (purchased_item_activation). For more information about event types, see MATRIXX Integration.

The operation types for pre-active purchased item activation are:

purchased_item_activation_subscriber = 79
purchased_item_activation_group = 80
purchased_item_activation_device = 81

You can customize non-usage events such as the purchased item activation events in My MATRIXX. For information about mapping operations and creating event subtypes, see My MATRIXX Help.

If a purchased item was purchased in a pre-active state and is not activated before it is canceled, the MtxCancelEvent EDR PreActiveState field value is true and the PurchaseEventId field indicates the ID of the purchase event.

When the initial state of a purchased offer is pre-active, in the GlInfoArray for the purchase charges, the RevenueRecognitionType value is 5 (pending_activation). Purchased item activation events can include GL info records that have a null reference (the value is not set) to the index into the balance update array in the event indicating that the purchase charges are deferred. For more information about the GlInfoArray, see the discussion about MtxEventGlInfo in MATRIXX Integration.

Note: For SubMan activation requests, when the request fails due to insufficient funds, the response includes CREDIT_LIMIT_REACHED (38). Also:

If the request fails due to insufficient funds, the response includes CREDIT_LIMIT_REACHED (38).
If the operation fails because a balance threshold was crossed, the response includes BALANCE_FLOOR_REACHED (81).
If the request fails because of an invalid life cycle state, the response includes PERMISSION_DENIED (33).

For more information about SubMan error codes, see the discussion about SubMan API result codes.

If a purchased_item_activation_failure_* operation type is configured to generate an EDR, a MtxPurchasedItemActivationFailureEvent EDR is generated.