The Refill object is design to handle prepaid Charges such as recharge or top-ups. By using our mobile prepaid service example, this concept is easily understood. However, On-Demand or Pay as You Go types of products that are deployed ‘in the Cloud’ can get very messy and complicated.

The good news about the Refill object is that it is not so complicated to understand. The bad news is that it has a whole different set of components. It has its own Class, its own Logic and its own Plan. We cannot reuse the CIP, Charge or Charge Plan objects that we have created thus far.

Capture

 

Refill Item Class

  • Similar to a Chargeable Item Class (CIC)
  • Defines the structure of a Refill Item
  • Includes the following default properties:
    – Date
    – Amount
    – Currency
  • Includes additional user-defined properties
  • Information in an instantiation of the Refill Item Class is utilized by Refill Logic within a Refill Plan to determine correct amount by which to refill a prepaid account

Capture

Refill Logic

  • Equivalent to a Charge for the refilling process
  • Defines an algorithm whose purpose is to refill a customer prepaid account
  • Refill Plan Logic can be customized utilizing the following:
    – Counters and parameters, redefined or linked
    – Prepaid account reference linked to refill plan level account
    – User identifiers linked to refill plan identifiers
    – Configuration for creation of refill records (Result Data)
    – Tier Tables, Translation Tables cannot be redefined

Capture

Refill Plan

  • New structured object to manage refilling functionality in the catalog of the Service Provider
  • Accessible from provisioning system via web service call to Refill Plan
  • Should be combined with a Charge Plan in the CRM or provisioning system, in order to model new commercial products/offers
  • Each Refill Plan contains a Refill Logic module that defines the amount to refill

Capture

Average Rating
0 out of 5 stars. 0 votes.
My Rating:

0 Comments

Leave a Reply

Your email address will not be published. Required fields are marked *