The Uwi-Fi system for campus is not a contributory channel."Students line up for cash in the financial window."The time has come. Wet pay and pay the treasures is now the mainstream programme, but in the process of matching third parties, several practical details are easily ignored before they become visible online. This piece has been put together by the actual project.
Reliability of payment of return notice
The payment platform sends a callback notice to the campus wireless wifi system when the user has completed payment through a micromail or payment of treasure. The check system updates the user balance when it receives a callback notice. This process looks simple, but the return call notification is not reliable.——If the system's servers are reset and send time billing, or if the network is in a state of instantaneous fluctuations that result in loss of return requests, the user will encounter"The money's withheld, but the balance is not updated."And that's the most common and most angry payment docking problem.
The solution is two layers. First level: payment platforms usually support automatic retries of callback notifications (up to three to five times, incremental intervals). The billing system needs to ensure that the callback interface is responsive in any case and not rendered unusable because of system maintenance or upgrades. Second layer: fee systems should be proactive in paying for the check-out from the pay-off platform——If you do not receive a callback notice (for example, 30 seconds) after a certain period of time, the system actively calls the payment platform ' s order query interface to confirm the payment status."Payment of successful but not updated balance"The probability of occurrence can be reduced to very low.
and the simultaneous processing of requests for payment
The Uwi-Fi system must be supported by the logic of payment processing.——If the system supports only serial processing of return calls, 201 return requests will need to wait until the first 200 are processed and processing delays will increase, leading to substantial time-consuming payments. The realization of simultaneous distribution requires attention to data consistency: if both simultaneously arriving callback notifications update the balance of the same user, a service or optimistic lock must be used to ensure that the atomic nature of the balance updates does not occur."The two fulls are plus 50 each, but the balance is only up by $50."This problem is not easy to find in a single campus on a small scale, but it is highly likely in a large multi-school setting.
Refund process design after payment fails
Payment failures are two types of: first, payment platform side failure (short balance of bank cards, error of password payment, network time overtime), where the user ' s money is untied and no refund is required. second, fee system failure (rewinding anomalies, loss of balance update, inconsistent order status) where the user ' s money has been withheld but the balance is not updated and requires refund. First, a clear hint of error for the user is provided. Second, there must be three steps in the process: automatic detection of anomalies.→Automatically initiate refunds→Notification of user refunds processed.
Automatic detection of anomalies is done by scanning the payment order forms for the regular billing system and identifying"Payment platform showing success but the billing system balance not updated"The payment system automatically calls the payout platform ' s refund interface after an unusual order is discovered, and the refunds are equal to the payment. After a successful refund, the user is notified (text message or station message). The process should be completely automated and no manual intervention by the carrier is required. Manual intervention is not only slow but also prone to error.——The carrier's judgment."This order needs to be refunded."Data from two systems are checked and the amount may be lost when manually refunds are made.
Reconciliation mechanisms can't be avoided
Once the payment docks for the wireless Wifi system on campus are online, it is necessary to establish a regular reconciliation mechanism: the total chargeable value of the system and the total transaction amount of the payout platform (micro-mail/poon) are reconciled once a week. The reconciliation is not just a check of the total.——The reasons for the discrepancy are: when a callback notice is lost."Payment platform has records but not a billing system"The financial statements of the United Nations peacekeeping operations, including those resulting from delays in the processing of refunds"The billing system has been refunded, but the payment of the platform refunds have not yet been generated", date attribution differences resulting from the settlement of a cross-day account.
The log-down system supports the export of payment order schedules, which are formatted in line with the transaction schedule for the pay-for-money platform."Order creation time"And the payment platform is used"Payment for completion"Some billing systems do not provide a detailed order export function, only the charge aggregate data, where reconciliations can be viewed only in total and not in detail, and it is impossible to accurately position the numbers of problems if there are inconsistencies.——Exported in detail, time-calibre selection and automatic differences.
Cost of payment channel
The fee for micro-credit payments and payment of treasures is usually 0.6% (business standard rate). A wireless Wifi system on campus is withheld if it is connected to the business model. Assuming a monthly charge of $100,000, the fee is $600. For small schools, this cost is not significant, but for large schools (a monthly charge of $500,000 plus), the fee is over $3,000 per month. Some schools have negotiated preferential rates with payment platforms (0.38% or less), but the discount rate is often conditionally limited.——The choice phase includes payment of fees as an operating cost, not just the system’s functionality.
User experience details for self-service charging interfaces
The self-service charge interface of the wireless Wifi system on campus is the most frequently used functional page for students. The details of the interface directly affect fee efficiency and the number of complaints."Ten, 20, 50 dollars."——There's more to it."Custom amount"option. Some students just want to try it for $5. The position of the charge button is clear, not hidden in the 3-level menu.——Update the new balance as soon as the charge is successful and do not let students doubt it"Did you do it?". The full history record must be viewed——To enable students to find out the amount and time of each previous charge, there is evidence of complaints.
Update of third-party payment interface and compatibility maintenance
The interface between the micromail and the treasure payment is not static. The interface version is updated at regular intervals, and the old interface version may be discarded.——The operator needs to follow up on the interface update after the pay platform has issued an update to confirm whether the interface version of the billing system needs to be upgraded. If the billing system provider does not follow the payment platform interface update voluntarily, the school carrier will have to look into the pay platform developers ' bulletin itself.——Is there a commitment to provide system upgrade packages in time for the upgrade of the platform interface and whether they are free of charge?
Bank card payments and a toon on campus docking
In addition to the micro-mails and payment treasures, some schools want to support direct bank card payments and a school-based cash-to-tone transfer. Bank card payments require a banking interface with a network of banks, high technical matching costs, stringent safety requirements, and small and medium-sized schools are not usually worth doing alone.——A cartoon system usually has a standard interface, and the billing system calls the interface to search for balances and deductions. But a key problem with a cartoon docking is the real-time nature of data in a cartoon system itself: if there are delays in updating the balance of a cartoon system (e.g., it takes minutes to synchronize the balance data after the crediting) it may occur when the billing system deducts"A cartoon shows a balance, but it's not enough.". A cartoon system has to be confirmed before the docking.
The practical details of the payment of the docking appear to be cumbersome, but each of them may have a direct impact on students’ contributory experience and the cost of running the school.——When the supplier shows up the payment function, it says:"Support for micro-mail payments and payment of treasures"I won't say."Recall notice risk requires active query". These details are presented at the selection stage, requiring suppliers to demonstrate in a test environment the full payment process (including payment success, payment failure, loss of return) more robust than they would have seen from PPT.