The Default Reference component charges one account and up to three credit limit balances through the default reference of the Internal Reference Dictionary. The Default Reference component charges one account and up to three credit limit balances through the default reference of the Internal Reference Dictionary.
The Default Reference is a unique Internal Reference permanently included in the Internal Reference Dictionary.
In a subscription, a charge is defined by the charging mapping made up of several columns (*) that allows you to associate the Default Reference of the charge with any account of a subscriber. When the charging plan is activated, the calculated amount of the price plan is charged to the specified accounts according to the charging mapping.
(*): The columns are Charging Reference, Charged Account, Credit Limit Balance#1, Credit Limit Balance#2, and Credit Limit Balance#3. Charged Account and Credit Limit Balances are part of the subscriber's accounts and are used to control the subscriber's expenses.
|
Note: In the Default Charging, you can remove the Default Reference, and then replace it by any other reference. Unlike the internal references, the Default Reference is unique; however, you can assign the Default Reference to various charging components in the same charging plan. You cannot use this component if the convergent charging services are based on provider contracts. |
Name: Type the name of the component (mandatory).
Description: Allows you to type the description of the component (optional).
Prepaid Account Charging Depending on Account Data State: Allows you to define the conditions for charging the prepaid accounts depending on their state and the component types used in the pricing branch. You are provided with two sliders, one for the Free Function component and one for the other components.
Charge Free Component Rates on: This slider defines the conditions for charging the prepaid accounts when using Free Function components in the pricing branch. The calculated amount of the price plan is charged to the prepaid accounts depending on both the slider position and the current state of the prepaid accounts. The table below shows you the expected charging: Yes (the prepaid accounts can be charged) or No (the prepaid accounts cannot be charged). For example, if you set the slider to 'Blocked', the prepaid accounts can be charged only if their state is 'Active' or 'Blocked'. But if the slider is set to 'Closed', the prepaid accounts can be charged whatever their state. Select one of the slider positions:
|
Slider position |
State of the prepaid accounts |
|||
|
Active |
Blocked |
Locked |
Closed |
|
|
Closed |
Yes |
Yes |
Yes |
Yes |
|
Locked |
Yes |
Yes |
Yes |
No |
|
Blocked |
Yes |
Yes |
No |
No |
|
Active |
Yes |
No |
No |
No |
Charge Rates Other Than Free on: This slider defines the conditions for charging the prepaid accounts when using any components other than Free Function components in the pricing branch. Refer to the description above.
Authorize overspending: Click this option to allow the prepaid account and credit limit balances to be overspent. Select one of the two options:
Only on Credit Limit Balances: The prepaid account and credit limit balances are both debited with calculated amounts of the price plan. When the prepaid account is less than its empty limit, charging is rejected.
On Prepaid Accounts and Credit Limit Balances: The prepaid account and credit limit balances are both debited even if the prepaid account is less than its empty limit.