Event Generation for Failed Transactions

The Charging Server generates events and notifications at the end of successful transactions and failed operations.

Failure events are generated for:

Purchase failure
Purchased item activation failure
Recurring failure
Usage authorization failure
Balance transfer failure

Failure Event Categories lists each failure and how it is determined. Each Event Detail Record (EDR) includes the failure reason and information specific to each failure.

Table 1. Failure Event Categories
Failed Operation	Reason	Event
Purchase	Credit limit reached. Balance floor reached. Life cycle status permission denied.	MtxPurchaseFailureEvent
Purchased Item Activation	Credit limit reached Balance floor reached	MtxPurchasedItemActivationFailureEvent
Recurring	Credit limit reached. Balance floor reached.	MtxRecurringFailureEvent
Usage Authorization	Credit limit reached. Rate table denial. Life cycle status permission denied.	MtxUsageAuthorizationEvent
Balance Transfer	Credit limit reached. Balance floor reached.	MtxBalanceTransferEvent

Note: Usage failure events are not generated for Gy Immediate Event Charging (IEC) and Advice of Charge (AoC) requests (CCR-E with Requested-Action=2 (CHECK_BALANCE) or 3 (PRICE_ENQUIRY). For more information about Advice of Charge, see the discussion about Advice of Charge. For more information about Immediate Event Charging, see the discussion about rating one-time events.

For more information about each event, see the discussion about EDRs in MATRIXX Integration.

Purchase Operation Failure

If the purchase operation involves multiple offers or bundles, there is a single failure event generated for the purchase operation.

If the purchase operation is wrapped inside a multi-request that fails:

If the offer owner is created with the purchase operation in the multi-request, there is no failure event because the entire multi-request fails.
If the offer owner was previously created and the multi-request contains the purchase operation that failed, then a failure event is generated.

Operation and Event Types

Failure Event Mapping describes the mapping of failure event types to operation types. By default, events are not generated for the failure operations. You must enable event generation in My MATRIXX.

Table 2. Failure Event Mapping
Event Type	Operation Type
BALANCE_TRANSFER_FAILURE	balance_transfer_failure_group balance_transfer_failure_subscriber
PURCHASE_FAILURE	purchase_failure_device purchase_failure_group purchase_failure_subscriber
PURCHASED_ITEM_ACTIVATION_FAILURE	purchased_item_activation_failure_device purchased_item_activation_failure_group purchased_item_activation_failure_subscriber
RECURRING_FAILURE	recurring_failure_group recurring_failure_subscriber

For information about pre-active purchased item activation failure, see the discussion about pre-active purchated item activation failure. For more information about event types, see the discussion about event types in MATRIXX Pricing and Rating. For more information about operation and event types, see the discussions about operation types and event mapping properties in My MATRIXX Help.