Prepaid Cloud Infrastructure Automation Configuration

The following items require configuration:

  • Deposit fee
  • Thresholds
  • Delayed of subscription suspension due to low balance
  • Notifications
  • Balance top-up

Deposit

Amount of the deposit fee is set per subscription period of a service plan, within the same-name field.

Thresholds

System uses the following thresholds in calculations:

  • Threshold to send the "low balance" notifications.
  • Threshold to put subscriptions on credit hold.

Values are configured as absolute amount in the system currency (for example, USD). In other words, the threshold is exceeded when available account balance becomes less than N. At that, the available account balance is calculated as follows:

  • <Available Account Balance> = <Documents Balance> - <Total consumption cost> - <Suspend service limit> + <Credit Limit>

Thresholds are configured separately for each Credit Terms.

Low Balance Suspension Delay

When a customer orders a new service/additional resource and sees available credit on the account, he or she may use it entirely to pay even though a part of it may be already "reserved" for the PAYG service. In such a case, with the next daily billing that PAYG subscription would be put on hold due to insufficient balance. Delaying subscription suspension allows the customer to top-up balance before the subscription is actually suspended.

Delayed subscription suspension is configured in Billing panel at System > Settings > Terms > Credit terms > <Credit Terms> (for each Credit Terms).

Notifications

To eliminate possible recurrent sending of "low-balance" notifications to a customer when approaching the threshold, the provider is able to set minimal balance shift value. The shift is set as an absolute value in currency of the system. A renewed notification will not be sent to the customer until the new value of consumption cost exceeds the shift value.

In case when the suspend service limit is exceeded a respective notification will be sent to the customer just once; an ability to send a renewed notification is not provided.

Example:

  • Threshold to send low-balance notifications: 100 $.
  • Threshold to put subscriptions on credit hold: 20 $.
  • Balance shift to resend "low-balance" notifications: 30 $.

Date

Available Account Balance, $

Comment

10-Jan

110

Notification limit is not exceeded. No notification is sent.

11-Jan

90

Notification limit 100 $ is exceeded. A respective notification is sent.

12-Jan

80

Notification limit 100 $ is exceeded. Minimal balance shift of 30 $ is not exceeded (90-80=10 $). No notification is sent.

13-Jan

60

Notification limit 100 $ is exceeded. Minimal balance shift of 30 $ is exceeded (90-60=30 $). A respective notification is sent.

14-Jan

50

Notification limit 100 $ is exceeded. Minimal balance shift of 30 $ is not exceeded (60-50=10 $). No notification is sent.

15-Jan

25

Notification limit 100 $ is exceeded. Minimal balance shift of 30 $ is exceeded (60-25=35 $). A respective notification is sent.

16-Jan

15

Suspend service limit of 20 $ is exceeded. The system puts services on credit hold and sends a respective notification. No other notifications will be sent until the customer’s Account Balance is refilled enough to release services from credit hold.

Note: In case the refilled balance is lower than the low-balance threshold (in our example, the threshold is set to 100 $), the customer will receive a low-balance notification right after the services are released from credit hold.

The following placeholders are available in notifications:

  • @@Cust_Account_CreditLimit@ – a customer credit limit.
  • @@Cust_Account_BalanceInverted@ – a current documents balance (the sum of all Payment without all Invoices).
  • @@Cust_Account_NipUsage@ – an amount of not invoiced purchases or consumption costs.
  • @@Cust_Account_Nip_StopLimit@ – a threshold to put a subscription on credit hold.
  • @@Cust_Account_AvailableCredit@ – an available account balance.

The dependency of all listed placeholders is described by the following formula:

  • Cust_Account_AvailableCredit = Cust_Account_BalanceInverted - Cust_Account_NipUsage - Cust_Account_Nip_StopLimit + Cust_Account_CreditLimit.

Balance Top Up

For amounts with which an account balance is recharged the provider can set minimum and maximum values. Such limits are set at the Settings > System > Customer CP screen with the Allow Standalone Payments option enabled. Every vendor configures this setting individually; it applies to all vendor's payment methods.

CloudBlue, an Ingram Micro business, uses cookies to improve the usability of our site. By continuing to use this site and/or logging in you are accepting the use of these cookies. For more information, visit our Privacy Policy.