Support for sweep fees, online payments, maturity alerts, automatic window support and multiple packages.
These words are familiar to everyone.
But when the project is really online, the most vulnerable thing to a carrier is not.“Do you have any of these?”But:
-
Do you have any data on the users at different contribution points?
-
Whether the payment is made and effective immediately after completion
-
Does the package change affect the session being used?
In other words, the problem never comes up.“How many ways to pay?”And it's about:
Whether all contributory actions are in the same set of fee engines.
In some systems, the contribution and billing modules are actually two sets of logic.
Payment is completed at the front end and a record of orders is generated from backstage;
The billing module continues to run according to the old set.
It is not clear in the short term that problems have begun to arise over a long period of time:
-
The students were asked to pay their fees.
-
The package was upgraded, and the traffic rules were not synchronized.
-
Financially observed income data do not match the number of online users
These are essentially:Contributions are not a direct input condition for the billing engine.
NATSHEL_BRAND, in the context of the middle-school network billing project, designed to be a simple system:
Whatever the user pays from, it's only one thing to do:
Modify the account status in a billing engine in real time.
That is:
I'll clean it up.
Portal page payment is also good
The operator's gonna be fine.
All were eventually placed in the same set of accounts.
This means:
-
It's not a question.“Special logic of a certain contribution”
-
The billing engine only recognizes account status
For the system:
Validity of accounts
What's the due date?
What's the package?
All from the same place.
In the wireless environment of accommodation, this design has brought about direct changes:
The moment the student completes the payment, there is no need to break the original session and to re-accredit.
The current session will be taken from the account as soon as the billing engine detects a change in the status of the account.“_Other Organiser”Switch To“Validity”。
The students have only one perception:
The network suddenly recovered.
No window.
No re-entry
No, no.
For schools, this kind of experience is often more than it's written in a program.“Multiple forms of contribution”More importantly.
Another easy point to ignore is thatFlexibility of the package adjustment。
In the middle school project, there are frequent:
-
Price adjustment for the new term
-
Launching the Year Package
-
To provide separate packages for certain professions or classes
If the contributory system and the billing engine are separate, each adjustment is a high-risk operation.
And when all the payment entrances drive the bill engine directly:
The package itself is only a set of parameters in the billing engine.
It's the rules that are modified, not the code.
Operators can be very quick to:
-
Add a new package
-
Disable the package.
-
Modify price
And it doesn't affect the running session.
From an operational point of view, this structure has also a very real value:
Income statistics are naturally strongly linked to online users.
The billing engine knows:
-
How many active accounts are currently available
-
What's the package for each account?
-
What's the price of the package?
The operator saw not only orders flowing, but also:
“How many users are actually using the network and in active condition at this school?”。
Such data are critical for follow-up expansion, adjustment of price strategies and addition of the suite hierarchy.
For the integrated firm, whether multiple payment methods actually run on the same set of fee engines directly affects three aspects:
-
Number of complaints following project entry
-
Post-shipment dimensions complexity
-
Operator satisfaction with the system
The simpler the system and the more logical it is, the easier it will be to operate in a stable manner over the long term.
NATHHEL_BRAND avoids putting it in place from the start of the design of a campus network billing system“Capacity to pay”As a stand-alone module, all contributory acts are considered to be real-time input into the billing engine.
This structure allows the medium-level campus network billing project to remain in operation for a long time, maintaining high consistency between account status, holster rules and online conversations.