Home
MATRIXX Pricing and Rating
Pricing
Pricing Plans
Pricing plans define the pricing and policies that allow you to control how you provide services to subscribers and how you are paid for those services. Pricing plans are comprised of catalog items, offers, bundles, and supporting objects required to implement pricing.
Thresholds and Credit Limits
Create thresholds and credit limits when you create or change balances and meters.
Thresholds
For many thresholds, the threshold is an amount at which a notification is triggered to alert group administrators or subscribers that a balance or meter has reached or exceeded a specific amount. These thresholds are called soft thresholds because they do not result in a denial of rating. Some thresholds, such as balance-floor thresholds, are hard thresholds in that any operation that exceeds its limit is denied.
Balance-Floor Thresholds
A balance-floor threshold can be defined on a prepaid balance template or a balance amount meter that tracks prepaid balances only, to control the maximum balance amount.

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
- About Pricing and Rating
  MATRIXX Pricing and Rating provides an introduction to MATRIXX pricing and rating functionality and describes how to define the catalog components necessary for rating and policy selection. It also provides an overview of the MATRIXX rating process and an introduction to My MATRIXX, a web-based user interface application you use to create and manage product catalogs.
- Rating
  The following information describes MATRIXX Charging Application rating functionality.
- Pricing
  - Pricing Overview
    The MATRIXX pricing model is highly flexible and enables you to create innovative service offerings and tailor pricing to subscriber needs. It is compatible with the TM Forum (TMF) Shared Information/Data (SID) model.
  - Pricing Data
    The MATRIXX Engine pricing data model is compatible with the Shared Information/Data (SID) standard, as defined by the TM Forum (TMF).
  - Pricing Corrections and Revisions
    Make corrections and revisions to all pricing items except balance classes, meter classes, balances, meters, and products. For information about product offer versions, see the discussion about product offers.
  - Updating Pricing After Purchase
    Not all pricing items can be updated after pricing is loaded and subscribers are using it.
  - Pricing Plans
    Pricing plans define the pricing and policies that allow you to control how you provide services to subscribers and how you are paid for those services. Pricing plans are comprised of catalog items, offers, bundles, and supporting objects required to implement pricing.
    - Balances and Meters
      When you define rates, you specify which balances and meters to impact when rating occurs. The impacts are a result of the price components applied, and represent the financial liabilities to subscribers and groups.
    - Thresholds and Credit Limits
      Create thresholds and credit limits when you create or change balances and meters.
      - Credit Limits
        A credit limit is a hard threshold that triggers when an amount is completely consumed, which triggers a message to be sent to the network, indicating that further usage against the balance or a meter should be disallowed. If notifications are configured, a notification is sent.
      - Thresholds
        For many thresholds, the threshold is an amount at which a notification is triggered to alert group administrators or subscribers that a balance or meter has reached or exceeded a specific amount. These thresholds are called soft thresholds because they do not result in a denial of rating. Some thresholds, such as balance-floor thresholds, are hard thresholds in that any operation that exceeds its limit is denied.
        Credit Floors
        The credit floor is a starting value from which to calculate percentage threshold amounts and is used to manage notifications for prepaid balances.
        Threshold Limits
        Each balance has a threshold limit that is determined internally by the MATRIXX Charging Application as subscribers use balances. The threshold limit helps determine the amount in a balance that can be used, which can be different than the actual balance amount available, taking credit limits into consideration.
        Recurring Thresholds
        You can define a threshold amount that triggers each time that amount impacts the balance. For example, you can create a recurring threshold that triggers each time a subscriber uses 500 prepaid voice minutes.
        Balance-Floor Thresholds
        A balance-floor threshold can be defined on a prepaid balance template or a balance amount meter that tracks prepaid balances only, to control the maximum balance amount.
      - Default Credit Limits and Thresholds
        Default credit limit and notification thresholds are defined in balance and meter templates and provide a system-wide mechanism to ensure subscribers are limited to a maximum spending amount. They enable corporations to comply with bill shock regulations currently enforced in the European Union.
      - Personal Credit Limits and Thresholds
        Personal credit limits and notification thresholds provide a way for subscribers to set their own spending limits and notifications. They are defined on the balances and meters located in a subscriber's wallet rather than in the balance template defined in a pricing plan.
      - Group Credit Limits and Thresholds
        Group credit limit and notification thresholds are defined for the G/L balance and meter instances located in a group wallet or group member wallet. They provide a way to set spending limits for group members and to notify associated users when a balance or meter reaches a threshold amount.
      - Balance Threshold-Based Pricing
        You can grant to a balance when subscribers or groups reach a balance or meter threshold (balance threshold-based pricing).
    - Decision Tables
      Decision tables consist of a number of _glossary/normalizer.html columns that define a set of business logic (one or more condition sets) that can be reused in different circumstances. Decision tables can be combined with a set of results into any type of component table, such as a policy table, rollover table, rate table, _glossary/gl_transaction_type.html table and account table, filter, or priority generator.
    - Contracts
      You can create finance or service contracts. A finance contract defines the terms and conditions of a contract. A service contract defines the terms and charges for a service, for example, voice or data.
    - Final Unit Indication
      You can configure Diameter Final Unit Indication (FUI) information to be static or dynamic.
    - Announcements Components
      MATRIXX Engine uses announcement pricing components for determining the list of announcements to play to a subscriber during a voice call, and the language they must be played in. You configure announcement data to be dynamic, so a different result occurs based on conditions that are valid at the time of rating.
    - Data Modifying
      You use the data modify interface in My MATRIXX to configure data modify actions, data modify profiles, and data modify profile selectors.
    - Filters
      Filters are independent, reusable, pricing items that can be associated with balances, meters, subscription product offers, and notifications.
    - Normalizer Templates
      Normalizer templates identify the MATRIXX Data Container (MDC) and its fields, catalog item parameters, balances, quantities, or times that are normalized during rating to determine which rates to apply. The fields can be located in a network message or in a MATRIXX database MDC, such as a subscriber, device, group, or purchased offer MDC.
    - Normalizer Instances
      Normalizer instances condense large sets of discrete field values into a manageable set of parameters. Each parameter represents the aggregate value set, so that assigning a result to every possible field value is not required.
    - Parameters
      You can configure definitions for parameters that you can use in pricing items such as catalog items, bundles, product offers, and price components.
    - Products
      A product represents the provisioning of a service type when a _glossary/catalog_item.html is purchased for a _glossary/subscription.html, _glossary/device.html, or _glossary/group.html. The products identify the service type, which in turn determines the pricing that can apply.
    - Catalog Items
      Catalog items are customizations of offers and bundles that are offered to a specific group of subscribers.
    - Catalogs
      A catalog contains catalog items and eligibility rules. The eligibility rules determine which catalog items are included or excluded from the catalog. You can also add metadata fields to further define the catalog.
    - Eligibility
      Eligibility rules define requirements and exclusions.
    - Product Offers
      Product offers are the basis for the pricing components that subscriptions, groups, and devices purchase, either singly or in bundles.
    - Bundles
      Bundles group one or more product offers together so they can be purchased as a unit. You can also create bundle-specific charges, grants, and discounts that override or supplement the existing price components defined in individual product offers.
    - Price Components
      MATRIXX price components are reusable pricing items that can be included in any number of product offers. They include charges, discounts, grants, refunds, and forfeitures.
    - Policies
      Policies provide the business logic for real-time policy decisions and rules, allowing you to track subscribers' service usage in real-time and change the behavior of a service based on that usage (for example, by throttling bandwidth).
    - Inbound Roaming
      Configure inbound and emergency roaming requests to define the agreements with third-party operators that allow requests for subscribers that are not identified in MATRIXX.
    - Denial Codes
      Denial codes are a way to deny service access to subscribers for a specific reason. You define them in My MATRIXX and add them to rate table rows in place of a rating formula, so the value is returned to the network based on the row selected during rating.
    - Offer Life Cycle Profiles
      An offer life cycle profile consists of a set of offer statuses, a set of policies associated with each offer status that describe behavior that can be executed in this status, and a set of transitions that can have conditions defined that can trigger a transition and actions defined that are executed after the transition is performed. Both offers and bundles can have an offer life cycle profile defined. Use offer life cycle profiles to customize the behavior of MATRIXX for your business processes.
    - Status Life Cycles
      A status life cycle is a collection of object states, policies, and transition rules that are defined for a specific object type. You can define a status life cycle for user, device, subscription, group, and offer objects to customize the behavior of MATRIXX for your business processes. For example, a device life cycle can begin with a provisioned status, transition to an active status, and finally transition to an inactive status.
    - Status Notification Profiles
      Notification profiles are reusable pricing components that define when expiration and recurring processing failure notifications are sent and the frequency with which those notifications are sent. Notification profiles can be assigned to each status in status life cycles. For a complete list of possible notifications, see the discussion about notifications in MATRIXX Integration.
    - System Attributes
      System attributes are custom properties you can attach to product offers, price components, rate tables, and rate table rows to add metadata to the object in the pricing database. They contain a mapping of attribute values to _glossary/mdc.html fields. The MDC fields get populated with the attribute values during rating and returned to the network in an MDC message.
    - Virtual Fields
      You use virtual fields to avoid creating multiple pricing configurations if your MATRIXX environment accepts multiple rating message types, for example, messages from Diameter and 5G networks.
    - Usage Triggers
      Use usage triggers to add lists of re-authorization triggers to the charging response messages for a session or rating group. Usage triggers are available for both Diameter Gy and 5G charging messages.
    - Usage Trigger Gy and 5G AVPs
      You trigger re-authorization for a session or rating group by assigning the Diameter Gy Trigger-Type and 5G triggerType AVP values listed here to usage trigger profiles.
    - Metadata
      Metadata summarizes basic information about other data and makes working with specific data easier. Metadata provides information about pieces of information that have meaning in relation to another piece of information in My MATRIXX.
  - Planning a Pricing Plan
    Before you create a _glossary/pricing_plan.html, determine how you want to name, organize, and set up the items that form planning a pricing plan.
  - Deploying a Pricing Plan
    Deploying a pricing plan involves compiling the pricing plan into a configuration file and loading the configuration file into the pricing database. During compilation, the pricing schema is validated and any errors that occur are displayed.
  - Group-Owned Pricing
    Groups can own product offers that define service pricing for group members. The product offers can define pricing for both usage and non-usage event types.
  - Taxation
    MATRIXX supports two types of taxation: tax classes and selectors, and US taxation. Tax classes specify tax rates or fixed taxes, and tax selectors dynamically select the tax rate, and apply one or more taxes to a charge. US taxation determines the taxes for a given location, and specifies the tax type, product category the tax applies to, and the tax authority who receives the tax based on CCH tax data.
- Appendices
MATRIXX Pay Now
MATRIXX Subscriber Management
MATRIXX Subscriber Management API
MATRIXX Business API SDK
My MATRIXX Help
MATRIXX Backoffice Customer Tool Help
MATRIXX Third-Party Licenses
Glossary

Balance-Floor Thresholds

A balance-floor threshold can be defined on a prepaid balance template or a balance amount meter that tracks prepaid balances only, to control the maximum balance amount.

For example, an operator requires that subscribers cannot deposit more than $1,000 into their prepaid balance instances. The operator defines a balance-floor threshold of $1,000 and each prepaid balance instance of the subscribers cannot have a balance amount exceeding $1,000.

Enable notifications to generate a notification when the maximum allowable amount for a selected balance is reached.

The following operations are allowed to exceed the limit:

Payment refund
Cancel refund
Cancel grant
Threshold-based grants

When any of the following operations are attempted and the operation results in the balance amount exceeding the balance-floor threshold, then the operation fails (is not allowed) and the BALANCE_FLOOR_THRESHOLD result code is returned:

Recharge
Transfer balance
Adjust balance
Cancel offer
Note: If the cancel offer operation fails due to the balance-floor threshold, the cancel offer and cancel all offers status life cycle transition actions will fail.
Grant balance (purchase and recurring)

Additionally, for balance-floor thresholds:

You cannot enable notifications on balance-floor thresholds.
You cannot specify a balance-floor threshold as a percentage.
The value of a balance-floor threshold must be entered as a negative amount and cannot be zero.
A threshold recharge cannot be triggered by a balance-floor threshold. For more information about threshold recharges, see the discussion about Pay Now auto recharge in MATRIXX Pay Now.

If a balance-floor threshold is not locked, it can be overridden for a subscriber or group using the AddThreshold SubMan APIs. For more information about the AddThreshold APIs, see the discussions about MtxRequestSubscriberAddThreshold and MtxRequestGroupAddThreshold in MATRIXX Subscriber Management API.