| Term
| Definition
|
| iBilling
| Transaction processing and subscription management system that handles retail and recurring billing transactions
|
| Client Library
| Client side library for communication with iBilling, consists of Session object, Business Components and Classification Codes.
|
| Session
| The main communication object within client library; abstraction of the server. It serves as a factory for creation of CustomerAccount objects and as a façade for executing server-side search queries. It relies on SessionConnection object for communication protocol implementation.
|
| RMIGates
| iBilling server’s entry point that accepts interchange classes via Java RMI protocol
|
| XMLGates
| iBilling server’s entry point that accepts interchange classes via XML Interchange protocol
|
| Business Components
| Includes the following classes: CustomerAccount, PaymentOption, RevenueTransaction, AssetTransaction, CaptureInfo, PaymentPlan, Charge, Adjustment
|
| CustomerAccount
| Person or organization account within iBilling. Stores basic demographic/contact info
|
| PaymentOption
| Credit card or bank account that can be used for recurring billing. References CustomerAccount
|
| RevenueTransaction
| Account transaction represening request for payment (invoice), reversal of invoice (credit). References CustomerAccount
|
| AssetTransaction
| Account transaction representing payment made (payment), payment returned (refund) or account credit (allowance). References CustomerAccount
|
| CaptureInfo
| Authorization/capture related information for CC and EFT processing. References AssetTransaction
|
| PaymentPlan
| Information for recurring billing: what amount, how often, how long, when to begin, what payment option. References CustomerAccount (also optionally PaymentOption)
|
| Charge
| Future invoice within PaymentPlan. At the moment of billing a Charge is converted into an invoice (RevenueTransaction). Specifies the date when the invoice should be created (may also represent freeze, when invoice is not created). References PaymentPlan.
|
| Adjustment
| Stores the reason explaining why changes were made to the PaymentPlan. Used primarily for reporting and auditing. References PaymentPlan
|
| Classification Codes
| Includes the following classes: Item, Tax, BillingCycle, CustomerAccountGroup. These objects are not used within the client-server communication process, but references to them might be made from the Business Components (using string represented identifiers). The values for objects of this type must be setup within iBilling Portal UI
|
| Item
| A product or service for which a PaymentPlan or a RevenueTransaction might be created
|
| Tax
| A tax that might be charged during the sale (linked to Item)
|
| BillingCycle
| Encodes cycle that recurring billing will follow; needed for PaymentPlan setup. The first 3 letters of the Code for any cycle must represent the time period and day when the cycle hits. Example: M03 - monthly on the 3rd, W02 - weekly on Tue, B8 - biweekly on second Monday
|
| CustomerAccountGroup
| Value used to meaningfully group CustomerAccounts
|
