Charges

Charges create a debit to a subscriber's currency or asset balance. When there are multiple valid balance instances in a subscriber or group wallet, the one to which the charge is applied is the balance instance that expires first.

Charges can be associated with usage events and non-usage events and can have any number of rates defined for them. For example, a purchase charge might have different rates based on the time period during which the purchase is made. Similarly, a voice charge might have multiple rates based on the area code of the number called.

Charges can be applied one-time, in response to an activity performed by a subscriber or customer care representative, or they can be applied on a recurring basis, in response to a balance or billing cycle. They do not impact meters. Charges can contain one or more rate tables that get applied in the order in which they are listed in the charge component.

Charges can be applied to a suspended or resumed product offer or bundle containing a product offer.

When there are multiple charges applied to an event, you can use rate tags to differentiate some charges from others so they can be grouped and reported separately in the Event Detail Records (EDRs) generated by MATRIXX Engine. For information about how rate tags are used in pricing, see the discussion about using rate tags to group charges in EDRs. For information about creating a rate tag, see the discussion about creating a rate tag in My MATRIXX Help.

For information about charges in arrears for charges that occurred in the previous recurring cycle that are applied at the end of the current cycle, see the discussion about cycle charges and discounts in arrears.