Go to Main Contents

:: Industry developments

Campus Wi Authentication & Billing Self-Help Contribution: How the micro-mail payment and automatic renewal payments are settled

The WiFi Authentication & Billing system in the park is inefficient and poorly experienced if it still allows users to pay cash on the front desk. Self-service payments are a label for the operation of the campus billing, with WiFi after the user line on the Portal page...

Your position:Home > Content Centre > Industry News > > Text

The WiFi Authentication & Billing system in the park is inefficient and under-utilized if it still allows users to pay their bills on the front desk. Self-service contributions are a mark of the campus ' s billing operations, and the user company WiFi then selects a set of meals, cleans and automatically runs on Portal pages without manual intervention. But self-service payments do not end with a payment interface, and they pay calls, automatic openings, automatic refunds, refunds, reconciliations, each one of them has a pit.

Basic process for self-service contributions

After the user connects to WiFi in the park, it is redirected to Portal page without authentication status. Portal pages display optional packages (lunar month, day, traffic, etc.) and prices, and users choose a package and jump to pay the page to support micromail payments and payment of treasure-scanners. When the user pays, pay platform callback notification V7 systems, which automatically open matching sets for users and release them online. The NATSHEL_BRAND V7 system supports user self-service payments, the payment of micromails and treasures, and the automatic opening of accounts upon successful payment without manual operation.

Reliability of payment return

The most problematic link for self-service payments is to pay the callback. Users pay, but when a checkback notice for payment platforms is not sent to V7 because network problems are not available, user accounts are not open and users pay no access to the Internet, complaints come in two levels of resolution: the first level is that the payment platform usually retries several times, with the first unsuccessful one running minutes apart, and at most several times again. The second level is V7 has a proactive search mechanism, and if the user pays for a return call, the system actively sends the payment platform ' s query status to confirm that payment is made manually. And put one on Portal."I paid for it. It's not open.", the user clicks and immediately after the user has accessed the system to query the order status as a spin-down.

How do you design the auto-release?

The monthly user has a cumbersome manual renewal fee, which increases the user’s retention and operating income."Autorenewal", the user’s payment authorization is recorded in the system and automatically is deducted from the user account on the day before it expires. Automatic renewal takes several details into consideration: first, a message to the user three days before deduction is sent reminding him of the amount and time of the charge that the automatic extension can be cancelled. Second, the fee failure is repeated, with the balance being withheld every day after the shortfall, and at most three times, the failure closes the automatic renewal fee and informs the user. Third, an automatic renewal authorization must be revoked at any time, the user closes by one key on its self-service page and cannot enforce the user renewal. Fourth, the automatic fee waiver bill should be clear and users can see the time and amount of each deduction.

Rules for the treatment of refunds

The user pays the fee but is required to refund for various reasons, which is an unavoidable situation in operation. Refund rules are to be clear in the user agreement: a full refund is not available within seven days of the month-on-month start-up and more than seven days after the end-up date, refunds are converted on the basis of the number of days already used; refunds are not supported by the day-on-one because services are provided; refunds can be converted against the remaining flow flow. Refund processes recommend manual clearance, applications for refunds are submitted by users on self-service pages and payment accounts are returned by agents or administrators as they approve. V7 supports refund operations, and the system automatically deducts corresponding income from agent splits after refunds, which can be seen in financial reconciliations.

Reconciliations and financial reconciliations

The V7 system supports order management, with purchase orders, payment patterns, amounts, times and status for each contribution. Every morning the system automatically generates statements from the day before, and is matched with bills of credit, payment treasures, and marks differences in orders. Difference orders are usually paid successfully but not open (retrieval lost), system opened but not yet accounted for (very few), refunds are not synchronized. The monthly reconciliation statements export Excel, comprising total income, income from payment patterns, refunds, splits of agents and reconciliations of amounts recorded in the financial system.

User experience of self-help pages

The design of the self-service contribution page directly affects conversion rates. The page should be simple: top displays the name of the park and logo, with a menu (price, content, validity) at the bottom being a payment button. Do not put too many advertisements and notices on the contribution page, users are meant to access the Internet for contributions, and much interference will be abandoned. The package recommends smartness: similar packages based on user history, new users recommend entry packages, old users recommend renewal fees.

Common fault check

Self-service payments are frequently faulty: first, payment is successful but not open, check the return log and active query mechanism to confirm whether the callback is reached or whether the order status is updated. Second, user sweeps result in payment page failure, check for network connectivity of Portal servers to the payout platform, and confirm that firewalls do not intercept the payout platform domain name and IP. Third, reconciliation discrepancies, check the status of orders and pay platform bills, process lost calls. Fourth, automatic fee cutback failed, check for validity of user ' s authorization to pay and adequacy of account balances. Fifth, the user could also access the Internet after refunding the funds and check whether the system had correctly performed shutdown operations and did Radius CoA successfully kick off the user.

The campus WiFi Authentication & Billing self-service contribution, which is centred on the payment of reliable and automatic openings and financial transactions. Retrievals are subject to double safeguards, automatic renewals are subject to alarm and failure, refunds are manually cleared, daily reconciliations ensure consistency between accounts and simple and efficient self-help pages. These links are solid, user fees are good, operators are low, and financial reconciliations are clear so that self-service contributions can actually run.

Access Program I'll be right back. Telephone counselling