Recurring Processing Notifications

You can configure balance templates, bill cycle templates, and product offer or bundle cycle data in My MATRIXX to reference a notification profile with recurring processing information that defines when notifications are sent.

Notification types are listed in Notification Types. They determine the information that is included in the notification message. Notification types are configured in My MATRIXX and include the following for balance, billing, and purchased item cycle notifications:
Table 1. Notification Types
ID Notification Type MATRIXX Data Container (MDC) Description
52 subscriber_recurring_charge MtxRecurringChargeNotification Generated when recurring processing is successfully run for a cycle.
53 group_recurring_charge MtxRecurringChargeNotification Generated when recurring processing is successfully run for a cycle.
60 subscriber_recurring_failure MtxRecurringFailureNotification Generated after a failure to apply recurring processing due to a lack of credit, based on a notification profile in the balance template or bill template.
61 group_recurring_failure MtxRecurringFailureNotification Generated after a failure to apply recurring processing due to a lack of credit, based on a notification profile in the balance template or bill template.
73 device_recurring_charge MtxRecurringChargeNotification Generated when recurring processing is successfully run for a cycle.
70 subscriber_recurring MtxRecurringChargeNotification Generated before recurring processing, based on a notification profile in the balance template or bill template. The notification includes an advice of the charge.
71 group_recurring MtxRecurringChargeNotification Generated before recurring processing, based on a notification profile in the balance template or bill template. The notification includes an advice of the charge.
74 device_recurring_failure MtxRecurringFailureNotification Generated after a failure to apply recurring processing due to a lack of credit, based on a notification profile in the balance template or bill template.
75 device_recurring MtxRecurringChargeNotification Generated before recurring processing, based on a notification profile in the balance template or bill template. The notification includes an advice of the charge.
82 subscriber_recurring_recharge MtxRecurringRechargeNotification Generated for an upcoming recurring recharge based on a notification profile in the balance template or bill template. The notification includes an advice of the charge.
83 group_recurring_recharge MtxRecurringRechargeNotification Generated for an upcoming recurring recharge based on a notification profile in the balance template or bill template. The notification includes an advice of the charge.
113 subscriber_cycle_arrears_recurring_charge MtxRecurringChargeNotification Generated when cycle arrears recurring processing is successfully run for a cycle.
114 group_cycle_arrears_recurring_charge MtxRecurringChargeNotification Generated when cycle arrears recurring processing is successfully run for a cycle.
121 subscriber_cycle_arrears_recurring MtxRecurringChargeNotification Generated before cycle arrears recurring processing, based on a notification profile in the balance template or bill template. The notification includes an advice of the charge.
122 group_cycle_arrears_recurring MtxRecurringChargeNotification Generated before cycle arrears recurring processing, based on a notification profile in the balance template or bill template. The notification includes an advice of the charge.

For each notification type, you can define a filter to dynamically determine whether to generate the notification type. 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 offers and bundles, the normalizations can also use custom extension fields to the offer or bundle template definition, respectively.

When configured, recurring charge notifications (*_recurring_charge) are sent for two reasons:
  • To advise about upcoming recurring charges.
  • To inform about recurring charges recently made.
The CycleStartTime, CycleEndTime, and CycleIntervalId fields indicate if an MtxRecurringChargeNotification notification is for upcoming recurring charges or recent charges.

When the cycle type is purchased item cycle, the CyclePurchasedItemAttr field (MtxPurchasedOfferExtension type) in the MtxRecurringChargeNotification notification populates with any custom attributes.

For more information about configuring notification types, see the discussion about notification types in My MATRIXX Help.

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