Prepaid and post-payment are two of the most basic fee models in the network billing system, and the first things that an operating programme is designed to do."Can the system support both models?"The logic behind the two models is completely different. The problem of choosing a wrong model is often greater than selecting a wrong system.
The NatShell V7 Authentication & Billing system supports both models. Prepaid fees are user fees, start-up, daily business clearances, daily stopovers; and subsequent payments are user fees.
Operational logic of the advance payment model
The core of the advance fee is"First charge the net."This model is naturally appropriate for individual users: school students, apartment tenants, rental households, who are mobile and unconnected, and the cost of recovery of arrears would be high if they were paid.
V7 is complete with the support of managers for a renewal fee and, if there are balances in the user account; users for a collection of treasures, micro-credit self-service accounts, charging and renewal charges; and agents for a renewal charge. Daily business closure and daily stoppage checks ensure timeliness of the accounts, while user balances are exhausted without manual intervention.
Conditions applicable to the post-payment model
The post-payment model is suitable for reliable and stable users, such as employees within the enterprise, long-term cooperating institutional clients.
You have to figure out your own collection tools before choosing to pay. If the system does not have access to payment platforms and there is no clear billing mechanism, then it becomes easy to pay."I'm not getting paid first.". The operator will decide whether to make the payment after adoption, depending on its user structure and collection capacity.
Both models can be used in combination.
In practical projects, the two models are often not optional. V7 supports different product packages for different user groups, without interference between each other. That is, in the same system, prepaid fees can be applied to individual users, post-payment payments to agency clients and a fee-free policy for special users.
V7 camp management functions support this: user charging, order record keeping, billing management, financial logs, charge recording, financial statements, business statements, financial reconciliations etc. modules that integrate both modes of accounts into uniform management. Each opening and renewal operation generates bills, which are manually accounted for by the payer, the recipient, the amount received, and the date of receipt, so as to facilitate statistical inquiries.
The balance and the payment is a watershed.
In either case, the logic of processing balances and fees determines user experience and operating costs. Under the prepaid model, the system must be able to accurately determine whether the balance is sufficient, when it expires, whether or not it is alerted before it is down; under the post-payment model, the system should be able to record the amount of arrears, generate bills, support reminders.
V7 contains a text message notification function that supports the sending of SMS messages to open accounts, renewals, incoming and end-of-service users. This capability is valuable for both modes: alerts are received before the payer expires, so that there is no sudden interruption in the network; post-payment clients receive bill reminders, reducing delays. For overcharged money, the system also supports the elimination of value refunds.
User status management also follows the pattern. V7 classifies users as normal, stop-in, end-out, end-up-out, and end-of-life categories, displaying them in a more user-friendly way, allowing easy access to statistics; supports suspensions, stop-instances, and suspensions of consumption. Under prepaid rates, the stop-ins are suitable for students leaving school during summer break; under after-payment, the stop-out is appropriate for temporary control.
The model option also considers the deployment and interface of a system. V7 supports local, cloud-side and distribution deployments, which are managed uniformly on multiple campuses and branches; supports integration with LDAP, supports alignment with one cartoon, and supports docking with the operator BOSS through Radius. Under the prepaid mode, systems are settled daily, down-checked, balances judged in different ways, as deployment patterns vary from station to station, such as when a cloud is deployed, which depends on network availability for down-screening and local deployment is more independent."System support, no use on site."The gap.
In a more detailed way, the user identification and security strategy also influences mode selection. V7 supports double factor authentication, LDAP docking, MAC NATHELL_SEAMLESS_AUTH, and binding user MAC addresses, NASIIP addresses, VLAN addresses, ACIP, SSID. Under prepaid models, identity binding prevents account-sharing and theft; under post-payment patterns, identity binding is the basis for accounting attribution. For demanding strict scenes, dual factor authentication significantly reduces the risk of misappropriation of accounts, but whether and how these capabilities are enabled depends on safety requirements and match conditions in the field, as well as if the type is identified when it is selected.
There is no absolute right or wrong to pay, but it is not appropriate."Both."More practical.