Purchased Item Cycle Notifications

A purchased item cycle can reference notification profiles for generating notifications for recurring processing or recurring processing failure.

Purchased item cycle information is included in the following MATRIXX Data Containers (MDCs):
  • MtxRecurringChargeNotification
  • MtxRecurringFailureNotification
Note: When the cycle type is purchased item cycle, the CyclePurchasedItemAttr field (MtxPurchasedOfferExtension type) in MtxRecurringChargeNotification and MtxRecurringFailureNotification populates with any custom attributes.
Notification types for recurring processing include:
  • Recurring Notification
    These notifications are generated before recurring processing as determined by the notification profile in a balance template or billing template. They include an Advice of Charge (AoC). The notification type for these notifications is determined by the purchased item owner: subscriber, group, or device. The notification types are:
    • SUBSCRIBER_RECURRING (70)
    • GROUP_RECURRING (71)
    • DEVICE_RECURRING (75)
    Note: If a purchased item or purchase package is in a recoverable state, a recurring advance notification is not generated.
  • Recurring Charge Notifications
    These notifications are generated at the time recurring processing is successfully executed for a cycle. The notification types are:
    • SUBSCRIBER_RECURRING_CHARGE (52)
    • GROUP_RECURRING_CHARGE (53)
    • DEVICE_RECURRING_CHARGE (73)
  • Recurring Failure Notifications
    These notifications are generated after failure to apply recurring processing due to lack of credit as determined by the notification profile in the balance template or billing template. The notification types are:
    • SUBSCRIBER_RECURRING_FAILURE (60)
    • GROUP_RECURRING_FAILURE (61)
    • DEVICE_RECURRING_FAILURE (74)
    Note: If a purchased item is in a recoverable state when recurring processing fails, a recurring failure notification and event are not generated.

For purchased item cycles, the recurring notification and recurring failure notification profiles are specified in the product offer template or bundle template that defines the cycle in Cycle Data.

For each notification type, a filter can dynamically determine whether to generate the notification. For notifications related to purchased item cycles, the normalizations within these filters can use fields from the purchased offer record for the purchased offer or bundle. For cycles from purchased bundles, the normalizations can also use custom extension fields to the bundle template definition in pricing. For cycles from purchased product offers, the normalizations can use custom extensions to the product offer template definition in pricing.

For more information about recurring cycle notifications, see the discussion about cycle processing in MATRIXX Pricing and Rating.