Store payment management method and system
By weighting and dynamically adjusting the evaluation indicators of payment channels, high-success-rate and low-cost payment channels are selected, solving the problem of unstable payment requests in chain retail business and improving the success rate and stability of payment services.
Patent Information
- Application Number
- CN202610231519.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-02-27
- Publication Date
- 2026-03-24
AI Technical Summary
In chain retail business, payment requests from franchised stores may be affected by network fluctuations, leading to poor selection of payment channels and impacting the success rate and stability of payment services.
By testing payment channel evaluation metrics, such as payment success rate in N minutes, average transaction response time, and channel fee rate, a weighted summation calculation is performed to select the payment channel with the highest channel score for acquiring and settling transactions. Furthermore, the weight settings are optimized by dynamically adjusting weight rules and using a PID controller to ensure that the selection of payment channels meets current operational needs.
It improves the success rate and stability of in-store payment processing, avoids the quality instability issues caused by traditional random routing methods, and ensures the smoothness of payment services and user satisfaction.
Smart Images

Figure CN121724614A_ABST
Abstract
Description
TECHNICAL FIELD
[0001] The present application relates to the technical field of financial network payment, in particular to a store payment management method and system. BACKGROUND
[0002] In a chain retail business, a franchise store can be connected to multiple payment channels, but each payment channel may cause network fluctuations due to reasons such as telecom service providers and servers, resulting in that the payment request of the franchise store cannot be responded, so it is necessary to realize the automatic switching of the store collection channel through payment routing.
[0003] At present, payment routing adopts a random way when selecting a payment channel, which may match a payment channel with poor quality, which not only affects the user experience of payment service, but also may cause payment failure, and it is difficult to guarantee the stability of payment service.
[0004] Therefore, how to improve the success rate and stability of store collection payment is a technical problem to be solved by those skilled in the art. SUMMARY
[0005] To solve the above technical problems, the present application provides a store payment management method which can improve the success rate and stability of store collection payment. The present application also provides a store payment management system which has the same technical effect.
[0006] The first object of the present application is to provide a store payment management method.
[0007] The above application object of the present application is achieved by the following technical scheme: A store payment management method, comprising: When the automatic routing is triggered, detecting channel evaluation indexes of each payment channel in a routing queue of a store, wherein the channel evaluation indexes include an N-minute payment success rate, an average transaction response time and a channel rate; According to the channel evaluation indexes of each payment channel, respectively performing weighted summation calculation to obtain a channel score of each payment channel, and the specific calculation formula is: Channel score = N-minute payment success rate x a + (preset maximum transaction response time - average transaction response time) x b + (preset industry standard rate - channel rate) x c; In the formula, a represents a preset payment success rate weight, b represents a preset response time weight, and c represents a preset channel rate weight; Selecting the payment channel with the highest channel score as a target payment channel, and performing collection settlement by using the target payment channel.
[0008] Preferably, in the store payment management method, the calculation method of the N-minute payment success rate is: The number of orders successfully paid in N minutes in the first preset time period is divided by the number of orders initiated to the payment channel in the first preset time period to obtain the N-minute payment success rate of the payment channel.
[0009] Preferably, in the store payment management method, the calculation method of the average transaction response time is: The sum of the transaction response times of all orders of the payment channel in the second preset time period is divided by the number of orders initiated to the payment channel in the second preset time period to obtain the average transaction response time of the payment channel.
[0010] Preferably, in the store payment management method, the preset payment success rate weight a, the preset response time weight b, and the preset channel rate weight c are dynamically configured through a preset weight adjustment rule, and the preset weight adjustment rule includes: Detecting the real-time store number of the store according to a first preset period; Determining the store passenger flow state according to the real-time store number and a preset passenger flow threshold, wherein the store passenger flow state is one of a low passenger flow state, a medium passenger flow state, and a high passenger flow state; If the store passenger flow state is the low passenger flow state, setting the preset channel rate weight c > the preset payment success rate weight a > the preset response time weight b; If the store passenger flow state is the medium passenger flow state, setting the preset payment success rate weight a > the preset response time weight b = the preset channel rate weight c; If the store passenger flow state is the high passenger flow state, setting the preset response time weight b > the preset payment success rate weight a > the preset channel rate weight c.
[0011] Preferably, in the store payment management method, the preset weight adjustment rule further includes: If the current date is a set holiday, the preset payment success rate weight a and the preset response time weight b are increased.
[0012] Preferably, in the store payment management method, the preset weight adjustment rule further includes: If the current single price of the store is greater than or equal to a preset single price threshold, the preset channel rate weight c is increased, and if not, the preset payment success rate weight a is increased.
[0013] Preferably, in the store payment management method, the preset weight adjustment rule further comprises: According to a second preset period, the difference between the current channel evaluation index and the preset target value is calculated respectively to obtain a payment success rate difference, an average response time difference and a channel rate difference; A PID controller is designed for the preset payment success rate weight a, the preset response time weight b and the preset channel rate weight c respectively, and the payment success rate difference, the average response time difference and the channel rate difference are input into the three PID controllers respectively to obtain a payment success rate weight adjustment amount, a response time weight adjustment amount and a channel rate weight adjustment amount; According to the current preset payment success rate weight, the current preset response time weight and the current preset channel rate weight, and the payment success rate weight adjustment amount, the response time weight adjustment amount and the channel rate weight adjustment amount, the dynamically adjusted preset payment success rate weight, the dynamically adjusted preset response time weight and the dynamically adjusted preset channel rate weight are calculated.
[0014] Preferably, in the store payment management method, the payment success rate difference is calculated in the following manner: E_s(t)=S_target-S_actual(t); In the formula, E_s(t) represents the payment success rate difference at the current time t, S_target represents the preset payment success rate target value, and S_actual(t) represents the N-minute payment success rate at the current time t. The average response time difference is calculated in the following manner: E_t(t)=T_actual(t)-T_target; In the formula, E_t(t) represents the average response time difference at the current time t, T_actual(t) represents the average transaction response time at the current time t, and T_target represents the preset average response time target value. The channel rate difference is calculated in the following manner: E_c(t)=C_actual(t)-C_target; In the formula, E_c(t) represents the channel rate difference at the current time t, C_actual(t) represents the channel rate at the current time t, and C_target represents the preset channel rate target value.
[0015] Preferably, in the store payment management method, the expression of the PID controller corresponding to the preset payment success rate weight a is as follows: ΔW_s(t) = Kp_s x E_s(t) + Ki_s x ∫E_s(t)dt + Kd_s x dE_s(t) / dt; wherein Kp_s represents a first proportional coefficient, Ki_s represents a first integral coefficient, Kd_s represents a first differential coefficient, and ΔW_s(t) represents the payment success rate weight adjustment amount; The expression of the PID controller corresponding to the preset response time weight b is: ΔW_t(t) = Kp_t x E_t(t) + Ki_t x ∫E_t(t)dt + Kd_t x dE_t(t) / dt; wherein Kp_t represents a second proportional coefficient, Ki_t represents a second integral coefficient, Kd_t represents a second differential coefficient, and ΔW_t(t) represents the response time weight adjustment amount; The expression of the PID controller corresponding to the preset channel rate weight c is: ΔW_c(t) = Kp_c x E_c(t) + Ki_c x ∫E_c(t)dt + Kd_c x dE_c(t) / dt; wherein Kp_c represents a third proportional coefficient, Ki_c represents a third integral coefficient, Kd_c represents a third differential coefficient, and ΔW_c(t) represents the channel rate weight adjustment amount.
[0016] Preferably, in the store payment management method, the calculation of the dynamically adjusted preset payment success rate weight, the dynamically adjusted preset response time weight, and the dynamically adjusted preset channel rate weight from the current preset payment success rate weight, the current preset response time weight, and the current preset channel rate weight, and the payment success rate weight adjustment amount, the response time weight adjustment amount, and the channel rate weight adjustment amount comprises: The calculation of the updated preset payment success rate weight, the updated preset response time weight, and the updated preset channel rate weight from the current preset payment success rate weight, the current preset response time weight, and the current preset channel rate weight, and the payment success rate weight adjustment amount, the response time weight adjustment amount, and the channel rate weight adjustment amount comprises: a_new = a' + ΔW_s(t); b_new = b' + ΔW_t(t); c_new = c' + ΔW_c(t); In the formula, a' represents the preset payment success rate weight, b' represents the preset response time weight, c' represents the preset channel fee rate weight, a_new represents the updated preset payment success rate weight, b_new represents the updated preset response time weight, and c_new represents the updated preset channel fee rate weight; According to the updated preset payment success rate weight, the updated preset response time weight, and the updated preset channel fee rate weight, normalization is performed to obtain a dynamically adjusted preset payment success rate weight, a dynamically adjusted preset response time weight, and a dynamically adjusted preset channel fee rate weight, and the calculation formula is: w_total=a_new+b_new+c_new; a_final=a_new / w_total; b_final=b_new / w_total; c_final=c_new / w_total; In the formula, w_total represents the weight sum, a_final represents the dynamically adjusted preset payment success rate weight, b_final represents the dynamically adjusted preset response time weight, and c_final represents the dynamically adjusted preset channel fee rate weight.
[0017] Preferably, the store payment management method further comprises: Performing health examination on the merchant number of the payment channel of the store, specifically including: requesting pre-ordering from the payment channel of the store according to a preset examination period, if the pre-ordering is successful, determining that the merchant number of the payment channel is available, if the pre-ordering fails, determining that the merchant number of the payment channel is unavailable; Performing channel keep-alive on the payment channel available for the merchant number, specifically including: switching the current payment channel of the store to the payment channel available for the merchant number to be kept alive according to a preset keep-alive period, until the number of payment successful orders of the payment channel available for the merchant number to be kept alive reaches a preset order number.
[0018] Preferably, the store payment management method further comprises: According to a preset constraint condition, determining whether each payment channel in the routing queue of the store is available, if not, deleting the payment channel from the routing queue; The preset constraint condition includes one or more of the following conditions: Determining whether the merchant number of the payment channel exists, if not, determining that the payment channel is unavailable; Determining whether the merchant number of the payment channel is available, if not, determining that the payment channel is unavailable; determining whether the payment channel supports the payment method of the current payment order, and if not, determining that the payment channel is unavailable; determining whether the current payment period is within the preset available period of the payment channel, and if not, determining that the payment channel is unavailable; determining whether the current payment period is within the preset maintenance period of the payment channel, and if so, determining that the payment channel is unavailable; determining whether the payment channel supports the preset fund settlement method of the store, and if not, determining that the payment channel is unavailable.
[0019] Preferably, in the store payment management method, the settlement of the collected funds to the bank internal account using the target payment channel includes: using the target payment channel to complete the collection and settling the collected funds to the bank internal account.
[0020] Preferably, in the store payment management method, after using the target payment channel to complete the collection and settling the collected funds to the bank internal account, the method further includes: checking and clearing the collected funds of the bank internal account with the channel bill to determine the internal account balance of the store; According to the withdrawal request of the store and the internal account balance of the store, the transaction funds are withdrawn to the bank account of the store.
[0021] The second object of the present application is to provide a store payment management system.
[0022] The above-mentioned second object of the present application is achieved by the following technical scheme: A store payment management system, comprising: a detection unit configured to detect channel evaluation indicators of each payment channel in a routing queue of a store when an automatic routing trigger is triggered, wherein the channel evaluation indicators include an N-minute payment success rate, an average transaction response time, and a channel rate; a calculation unit configured to respectively perform weighted summation calculation according to the channel evaluation indicators of each payment channel to obtain a channel score of each payment channel, and the specific calculation formula is: Channel score = N-minute payment success rate × a + (preset maximum transaction response time - average transaction response time) × b + (preset industry standard rate - channel rate) × c; wherein a represents a preset payment success rate weight, b represents a preset response time weight, and c represents a preset channel rate weight; a payment unit configured to select the payment channel with the highest channel score as a target payment channel and use the target payment channel for settlement of collection.
[0023] The technical scheme has the following beneficial effects. When the automatic routing is triggered, the channel evaluation indexes of each payment channel in the routing queue of the store are detected; the channel evaluation indexes of each payment channel are respectively subjected to weighted summation calculation to obtain channel scores of each payment channel, the channel score=N minute payment success rate x a+(preset maximum transaction response time length-average transaction response time length) x b+(preset industry standard rate-channel rate) x c; the payment channel with the highest channel score is selected as a target payment channel, and the target payment channel is used for settlement, so that the influence of the three channel evaluation indexes is comprehensively considered, the target payment channel with high payment success rate, short response time and low channel cost can be selected from the routing queue, the success rate and stability of the target payment channel are effectively ensured, the cost control is considered, the unstable quality problem caused by the traditional random routing mode is effectively avoided, and the smoothness of store settlement and payment and user satisfaction are further ensured.
[0024] In summary, the technical scheme can improve the success rate and stability of store settlement and payment. BRIEF DESCRIPTION OF DRAWINGS
[0025] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the drawings needed to be used in the embodiments or prior art description will be briefly introduced. Obviously, the drawings in the following description are only some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative labor.
[0026] Figure 1 A flowchart of a store payment management method in an embodiment of the present application; Figure 2 A structural diagram of a store payment management system in an embodiment of the present application. DETAILED DESCRIPTION
[0027] In order to make those skilled in the art better understand the technical solutions in the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below. Obviously, the described embodiments are only some of the embodiments of the present application, not all. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative labor are within the scope of protection of the present application.
[0028] In the embodiments of the present application, it should be understood that the disclosed method and system can be implemented in other ways. The system embodiments described below are only schematic. The division of units and modules is only a logical function division. There can be another division manner in actual implementation. For example, a plurality of units or modules can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the components shown or discussed can be indirect coupling or communication connection through some interfaces, devices or modules, and can be electrical, mechanical or other forms.
[0029] In addition, each functional unit in the embodiments of the present application can be integrated into one processor, or each unit can be a separate device, or two or more units can be integrated into one device. Each functional unit in the embodiments of the present application can be implemented in the form of hardware or hardware plus software functional units.
[0030] Those skilled in the art can understand that all or part of the steps of the following method embodiments can be completed by program instructions and related hardware. The aforementioned program instructions can be stored in a computer readable storage medium, and the program instructions are executed to perform the steps of the method embodiments. The aforementioned storage medium includes mobile storage devices, read-only memories (ROM), magnetic disks or optical disks, and various media that can store program codes.
[0031] It should be understood that if "system", "device", "unit" and / or "module" are used in the present application, it is only a method for distinguishing different components, elements, parts, portions or assemblies at different levels. However, if other words can achieve the same purpose, the words can be replaced by other expressions.
[0032] In addition, the terms "first", "second" are only used for descriptive purposes, and cannot be understood as indicating or implying relative importance or implicitly indicating the number of indicated technical features. Therefore, the features defined as "first", "second" can explicitly or implicitly include one or more features. In the description of the present application, the meaning of "a plurality of" or "several" is two or more, unless otherwise explicitly specified.
[0033] If flowcharts are used in the present application, the flowcharts are used to illustrate the operations performed by the system according to the embodiments of the present application. It should be understood that the preceding or subsequent operations do not necessarily be executed in sequence. On the contrary, each step can be processed in reverse order or simultaneously. Meanwhile, other operations can be added to these processes, or one or more steps can be removed from these processes.
[0034] It should also be noted that in the present document, such as the term "comprise", "contain" or any other variant thereof is intended to cover the non-exclusive inclusion, so that the article or device including a series of elements not only includes those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such article or device. Without more limitations, the element defined by the statement "comprises a" does not exclude the presence of another identical element in the article or device comprising the above element.
[0035] Embodiments of the present application are written in a progressive manner.
[0036] As shown in Figure 1 The embodiments of the present application provide a store payment management method, comprising: S101. When the automatic routing is triggered, detecting the channel evaluation index of each payment channel in the routing queue of the store; In S101, specifically, the triggering mode of automatic routing can be set based on actual application requirements. For example, if the store adopts the master-backup strategy, it prefers to use the master payment channel for collection settlement. When it is detected that the master payment channel request is abnormal or the response is abnormal, the automatic routing can be triggered. If the store does not adopt the master-backup strategy, the automatic routing can also be triggered directly when receiving the collection payment request. The present application is not limited to this. In the routing queue of the store, a plurality of payment channels are pre-set, including third-party payment channels and bank payment channels, etc. The payment channel with the best quality needs to be selected in the routing queue to ensure the payment service experience. When the automatic routing is triggered, the channel evaluation index of each payment channel in the routing queue of the store is detected.
[0037] Among them, the channel evaluation index includes N-minute payment success rate, average transaction response time and channel rate. The value of N can be dynamically configured based on the acceptable payment response time, for example, N can take the value of 1, that is, the 1-minute payment success rate is used as the channel evaluation index, and the present application is not limited to this. The transaction response time is the time when the payment system receives the response result returned by the payment channel minus the time when the payment system initiates the payment request to the payment channel. The channel rate refers to the proportion of the procedure fee required when using the payment channel.
[0038] In some embodiments, the N-minute payment success rate is calculated by dividing the number of orders successfully paid by the payment channel within N minutes in the first preset time period by the number of orders initiated to the payment channel in the first preset time period. Specifically, the first preset time period can be dynamically configured based on timeliness requirements, for example, it can be set to the previous M days, the previous M hours, etc., and preferably it can be set to the previous day, i.e. the number of orders successfully paid by the payment channel within N minutes in the previous day ÷ the number of orders initiated to the payment channel in the previous day = N-minute payment success rate, which is not limited in the present application.
[0039] In other embodiments, the average transaction response time is calculated by dividing the sum of transaction response times of all orders of the payment channel in the second preset time period by the number of orders initiated to the payment channel in the second preset time period. Specifically, the second preset time period can be dynamically configured based on timeliness requirements, for example, it can be set to the previous M days, the previous M hours, etc., and preferably it can be set to the previous day, i.e. the sum of transaction response times of all orders of the payment channel in the previous day ÷ the number of orders initiated to the payment channel in the previous day = average transaction response time, which is not limited in the present application.
[0040] S102. According to the channel evaluation indicators of each payment channel, respectively, weighted sum calculation is performed to obtain the channel score of each payment channel; In S102, specifically, the specific calculation formula of the channel score is: Channel score = N-minute payment success rate × a + (preset maximum transaction response time - average transaction response time) × b + (preset industry standard rate - channel rate) × c; In the formula, a represents a preset payment success rate weight, b represents a preset response time weight, and c represents a preset channel rate weight. The specific values of a, b and c can be pre-set based on actual requirements. For example, if the store pays more attention to payment stability, a higher preset payment success rate weight can be set; if the store pays more attention to the smoothness of user payment experience, a higher preset response time weight can be set; if the store takes cost control as the core target, a higher preset channel rate weight can be set, so that the channel score calculation is more in line with the actual operation requirements of the store. The preset maximum transaction response time can be set based on actual conditions, for example, the normal transaction response time is generally within 3 minutes, and the preset maximum transaction response time can be set to 5 minutes, which is not limited in the present application. The industry standard rate can be determined based on the general rate level of similar channels in the current payment industry or the reference value published by the industry association.
[0041] The channel score of each payment channel is calculated by the above formula, which can evaluate the quality of the payment channel from three dimensions of payment success rate, response time and channel cost, and is beneficial to screening the payment channel with the best comprehensive performance and providing a quantitative basis for the selection of the target payment channel. Through this multi-dimensional weighted evaluation method, both the success rate and stability of the payment service are taken into account, and cost control is also considered, which can effectively avoid the quality instability problem caused by the traditional random routing method, and further ensure the smoothness of the store's payment and user satisfaction.
[0042] S103. Selecting the payment channel with the highest channel score as the target payment channel, and using the target payment channel to perform the settlement.
[0043] In S103, specifically, after obtaining the channel scores of the payment channels, the payment channel with the highest channel score is selected as the target payment channel for the settlement of the store. In this way, the influence of the three channel evaluation indexes is comprehensively considered, the target payment channel with high payment success rate, short response time and low channel cost can be selected from the routing queue, the problem of matching to a poor quality channel by the traditional random routing method can be effectively avoided, and the quality of the payment service of the store is improved, the user payment experience is ensured while the operating cost is reduced.
[0044] Currently, the payment routing adopts a random method when selecting a payment channel, which may match to a poor quality payment channel. This not only affects the user experience of the payment service, but also may cause payment failure, and it is difficult to ensure the stability of the payment service.
[0045] In the above embodiment, when the automatic routing is triggered, the channel evaluation indexes of each payment channel in the routing queue of the store are detected; the channel evaluation indexes of each payment channel are weighted and summed respectively to obtain the channel score of each payment channel, the channel score is N-minute payment success rate x a + (preset maximum transaction response time - average transaction response time) x b + (preset industry standard rate - channel rate) x c; the payment channel with the highest channel score is selected as the target payment channel, and the settlement is performed using the target payment channel. In this way, the influence of the three channel evaluation indexes is comprehensively considered, the target payment channel with high payment success rate, short response time and low channel cost can be selected from the routing queue, the success rate and stability of the target payment channel are effectively ensured, cost control is also considered, the quality instability problem caused by the traditional random routing method can be effectively avoided, and the smoothness of the store's payment and user satisfaction are further ensured. In summary, the above embodiment can improve the success rate and stability of the store's payment.
[0046] In view of the limitations of the above fixed weight setting, i.e., the inability to flexibly adapt to the dynamic changes of priority under different operating scenarios of the store. In other embodiments of the present application, the preset payment success rate weight a, the preset response time weight b and the preset channel fee rate weight c are dynamically configured through a preset weight adjustment rule, and the preset weight adjustment rule includes: S201. According to the first preset period, detecting the real-time store number of the store; In S201, specifically, the first preset period can be set based on actual application requirements, for example, the first preset period is set to 5 minutes, i.e., detecting the real-time store number of the store once every 5 minutes. Wherein, the real-time image of the store can be collected through the camera in the store, and then the real-time store number of the store is detected based on the real-time image and the preset personnel detection algorithm. Other reasonable ways can also be used to detect the real-time store number of the store, and the present application is not limited thereto.
[0047] S202. According to the real-time store number and the preset passenger flow threshold, determining the store passenger flow state; In S202, specifically, the preset passenger flow threshold and the store passenger flow state can be set based on actual application requirements, for example, the preset passenger flow threshold includes a first preset passenger flow threshold and a second preset passenger flow threshold, and the store passenger flow state is one of a low passenger flow state, a medium passenger flow state and a high passenger flow state. When the real-time store number is less than the first preset passenger flow threshold, the store passenger flow state is determined to be a low passenger flow state, when the real-time store number is greater than or equal to the first preset threshold and less than or equal to the second preset threshold, the store passenger flow state is determined to be a medium passenger flow state, and when the real-time store number is greater than the second preset threshold, the store passenger flow state is determined to be a high passenger flow state. In specific embodiments, the first preset passenger flow threshold is set to 5 people, and the second preset passenger flow threshold is set to 10 people, and the store passenger flow state can be defined as follows: Low passenger flow state: real-time store number < 5 people; Medium passenger flow state: 5 people ≤ real-time store number ≤ 10 people; High passenger flow state: real-time store number > 10 people.
[0048] S203. If the store passenger flow state is a low passenger flow state, set the preset channel fee rate weight c > the preset payment success rate weight a > the preset response time weight b; if the store passenger flow state is a medium passenger flow state, set the preset payment success rate weight a > the preset response time weight b = the preset channel fee rate weight c; if the store passenger flow state is a high passenger flow state, set the preset response time weight b > the preset payment success rate weight a > the preset channel fee rate weight c.
[0049] In S203, specifically, when the store is in a low customer flow state, since the user payment demand is relatively small, the store can pay more attention to cost control, therefore the preset channel rate weight c is set to the highest, the preset payment success rate weight a is next, and the preset response time weight b is the lowest; when the store is in a medium customer flow state, the store needs to prioritize payment stability and balance between cost and experience, therefore the preset payment success rate weight a is set to the highest, the preset response time weight b and the preset channel rate weight c remain consistent; when the store is in a high customer flow state, there can be a large number of users simultaneously initiating payment requests, and the payment response speed directly affects user experience and transaction efficiency, therefore the preset response time weight b is prioritized, the preset payment success rate weight a is next, and the preset channel rate weight c is the lowest. In specific embodiments, the weight settings in the above three store customer flow states can be set according to Table 1, and the application is not limited thereto.
[0050] Table 1 Store customer flow state and weight setting
[0051] In this embodiment, through this dynamic weight adjustment strategy based on real-time customer flow state, the payment routing decision can be more suitable for the current operation scene of the store, further optimizing the adaptability of the payment service, and achieving optimal payment channel selection in different customer flow situations, so as to balance the dynamic balance of cost, stability and user experience. This dynamic adjustment method breaks through the limitations of fixed weights, so that the selection of payment channels can be flexibly adapted to changes in store operation scenes, effectively improving the intelligent level and practical application value of the payment routing system.
[0052] In other embodiments of the application, the preset weight adjustment rule further includes: S204. Determine whether the current date is a set holiday, and if so, increase the preset payment success rate weight a and the preset response time weight b.
[0053] In S204, specifically, the set holiday can include store member day, holiday, etc. The store generally invests more marketing costs to attract customers during the set holiday, in order to ensure a good holiday shopping experience for consumers, the preset payment success rate weight a and the preset response time weight b can be increased, so that the payment routing is more inclined to select payment channels with high payment success rate and fast response through weight inclination. This targeted adjustment can effectively deal with the concentrated payment requests that may occur during the holiday, reduce user waiting time and failure probability in the payment link, help the store maintain high-quality payment service level during the traffic peak period, and also better handle the customer flow conversion brought by holiday marketing, improve the overall operation efficiency of the store.
[0054] S205. Determine whether the current average order value of the store is greater than or equal to the preset average order value threshold. If yes, increase the preset channel fee rate weight c. If no, increase the preset payment success rate weight a.
[0055] Specifically, in S205, the preset average order value threshold can be set based on actual application needs. When the current average order value of a store is less than the preset threshold, the preset payment success rate weight 'a' is increased; when the current average order value is greater than or equal to the preset threshold, the preset channel fee rate weight 'c' is increased. This weight adjustment based on average order value can optimize the balance between cost and experience for different transaction amount scenarios: in high-average-order-value transaction scenarios, stores can use weight bias to make payment routing more inclined to choose payment channels with lower channel fees, thereby significantly reducing the cost of a single transaction; in low-average-order-value transaction scenarios, stores can use weight bias to make payment routing more inclined to choose payment channels with higher payment success rates, improving payment success rates can effectively avoid user dissatisfaction caused by small-amount payment failures, thereby maintaining the store's service reputation.
[0056] In other embodiments of this application, the preset weight adjustment rule further includes: S206. According to the second preset cycle, calculate the difference between the current channel evaluation index and the preset target value respectively to obtain the payment success rate difference, the average response time difference and the channel fee rate difference; Specifically, in S206, the second preset period can be set based on actual application needs. For example, the second preset period can be set to 5 minutes, that is, the difference in payment success rate, the difference in average response time, and the difference in channel fee rate are calculated every 5 minutes. This application is not limited to this. The preset target values include a preset target value for payment success rate, a preset target value for average response time, and a preset target value for channel fee rate. Their specific values can be set based on actual application needs. For example, the preset target value for payment success rate can be set to 99.99%, the preset target value for average response time can be set to 800ms, and the preset target value for channel fee rate can be set to 0.20%. This application is not limited to this.
[0057] In some embodiments, the payment success rate difference is calculated as follows: E_s(t) = S_target - S_actual(t); In the formula, E_s(t) represents the difference in payment success rate at the current time t, S_target represents the preset target value for payment success rate, and S_actual(t) represents the payment success rate at the current time t over N minutes; The average response time difference is calculated as follows: E_t(t) = T_actual(t) - T_target; In the formula, E_t(t) represents the difference in average response time at the current time t, T_actual(t) represents the average transaction response time at the current time t, and T_target represents the preset target value for average response time; The formula for calculating the channel fee rate difference is: E_c(t) = C_actual(t) - C_target; In the formula, E_c(t) represents the channel rate difference at the current time t, C_actual(t) represents the channel rate at the current time t, and C_target represents the preset channel rate target value.
[0058] S207. Design an independent PID controller for each of the preset payment success rate weight a, preset response time weight b, and preset channel fee rate weight c. Input the difference in payment success rate, the difference in average response time, and the difference in channel fee rate into the three PID controllers respectively to obtain the adjustment amount of payment success rate weight, response time weight, and channel fee rate weight. In S207, specifically, an independent PID controller is designed for each weight. Each PID controller adjusts three key parameters—proportional coefficient Kp, integral coefficient Ki, and derivative coefficient Kd—to make the output reach the target value quickly, accurately, and stably. The proportional coefficient Kp is used to determine the response speed to the current error, the integral coefficient Ki is used to eliminate the historical accumulated steady-state error, and the derivative coefficient Kd is used to measure the future trend of error change, playing a "damping" role to prevent overshoot.
[0059] The expression for the PID controller corresponding to the preset payment success rate weight 'a' is: ΔW_s(t)=Kp_s×E_s(t)+Ki_s×∫E_s(t)dt+Kd_s×dE_s(t) / dt; In the formula, Kp_s represents the first proportional coefficient, Ki_s represents the first integral coefficient, Kd_s represents the first differential coefficient, and ΔW_s(t) represents the weight adjustment amount for payment success rate. The expression for the PID controller corresponding to the preset response time weight b is: ΔW_t(t)=Kp_t×E_t(t)+Ki_t×∫E_t(t)dt+Kd_t×dE_t(t) / dt; In the formula, Kp_t represents the second proportional coefficient, Ki_t represents the second integral coefficient, Kd_t represents the second differential coefficient, and ΔW_t(t) represents the response time weight adjustment amount; The expression for the PID controller corresponding to the preset channel fee rate weight c is: ΔW_c(t)=Kp_c×E_c(t)+Ki_c×∫E_c(t)dt+Kd_c×dE_c(t) / dt; In the formula, Kp_c represents the third proportional coefficient, Ki_c represents the third integral coefficient, Kd_c represents the third differential coefficient, and ΔW_c(t) represents the channel fee rate weight adjustment.
[0060] S208. Based on the current preset payment success rate weight, the current preset response time weight, and the current preset channel fee rate weight, as well as the adjustment amounts of the payment success rate weight, response time weight, and channel fee rate weight, calculate the dynamically adjusted preset payment success rate weight, the dynamically adjusted preset response time weight, and the dynamically adjusted preset channel fee rate weight.
[0061] In S208, specifically, firstly, based on the current preset payment success rate weight, the current preset response time weight, and the current preset channel fee rate weight, as well as the adjustment amounts for the payment success rate weight, response time weight, and channel fee rate weight, the updated preset payment success rate weight, the updated preset response time weight, and the updated preset channel fee rate weight are calculated. The calculation formula is as follows: a_new=a'+ΔW_s(t); b_new=b'+ΔW_t(t); c_new=c'+ΔW_c(t); In the formula, a' represents the current preset payment success rate weight, b' represents the current preset response time weight, c' represents the current preset channel fee rate weight, a_new represents the updated preset payment success rate weight, b_new represents the updated preset response time weight, and c_new represents the updated preset channel fee rate weight. Based on the updated preset payment success rate weight, updated preset response time weight, and updated preset channel fee rate weight, normalization is performed to obtain the dynamically adjusted preset payment success rate weight, dynamically adjusted preset response time weight, and dynamically adjusted preset channel fee rate weight. The calculation formula is as follows: w_total = a_new + b_new + c_new; a_final = a_new / w_total; b_final = b_new / w_total; c_final = c_new / w_total; In the formula, w_total represents the weight sum, a_final represents the dynamically adjusted preset payment success rate weight, b_final represents the dynamically adjusted preset response time weight, and c_final represents the dynamically adjusted preset channel fee rate weight.
[0062] After calculating a_final, b_final, and c_final, they can be substituted into the channel scoring formula above. In other words, the channel scoring formula is updated as follows: Channel score = N-minute payment success rate × a_final + (maximum preset transaction response time - average transaction response time) × b_final + (preset industry standard rate - channel rate) × c_final.
[0063] In this embodiment, by introducing PID control, the system can continuously and automatically find the optimal balance between the three core objectives—success rate, response speed, and cost—instead of relying on manually preset fixed weights. The PID output changes continuously, so the adjustment of channel weights is also smooth and gradual, effectively avoiding the impact of traffic switching caused by weight jumps and ensuring a more stable overall payment system. The integral in the PID accumulates experience; if a payment channel performs poorly for a long period, the integral term accumulates this "bad impression," continuously reducing its weight until the problem is resolved. This effectively eliminates long-term unstable payment channels. Furthermore, the PID controller can be flexibly adjusted according to strategic indicators. For example, if a store wants to focus on improving payment success rate, it only needs to increase the payment success rate target or increase the Kp_s parameter of its PID controller, making the optimization direction clear and controllable.
[0064] In other embodiments of this application, the above-described store payment management method further includes: S301. Perform a health check on the merchant ID of the store's payment channel, specifically including: requesting a pre-order from the store's payment channel according to a preset check cycle. If the pre-order is successful, the merchant ID of the payment channel is deemed to be usable; if the pre-order fails, the merchant ID of the payment channel is deemed to be unusable. In S301, specifically, a Merchant ID refers to a unique identifier assigned to a store by the payment service provider. This identifier is used to verify the store's legal status as a payment entity in the payment transaction process and is linked to core business parameters such as the store's payment settlement account, transaction fee agreement, fund clearing path, and risk control rules. Each store typically holds a separate Merchant ID for different payment channels, and its validity directly affects whether the corresponding payment channel can normally accept user payment requests. The preset check cycle can be set based on actual application needs. For example, a pre-order can be requested for the store's payment channel every day at midnight (without actual payment). If the pre-order is successful, it indicates that the Merchant ID is available; if it fails, it indicates that the Merchant ID is unavailable. This pre-order operation verifies the availability of the Merchant ID and proactively checks for issues such as invalidation, freezing, or abnormal configuration. This ensures that the payment channel has a legal identity authentication foundation in actual transaction scenarios, reducing payment failures caused by Merchant ID issues from the source and providing a proactive guarantee for the smooth completion of payment transactions.
[0065] S302. Keep the payment channels available for the merchant account active, specifically including: according to the preset active period, switch the store's current payment channel to the payment channel available for the merchant account to be active, until the number of successfully paid orders through the payment channel available for the merchant account to be active reaches the preset number of orders; In S302, specifically, the purpose of channel keep-alive is to ensure that the payment channel remains available and is not shut down due to prolonged inactivity. The preset keep-alive period can be set based on actual application needs, such as a specific day of the week or the xth day of the month. The time period is generally chosen during off-peak business hours, such as 13:00-14:00. Channel keep-alive can target only the payment channels available to the merchant account. After the preset time period, the store's current payment channel is switched to the payment channel available to the merchant account to be kept active, until the number of successfully completed orders on the payment channel available to the merchant account to be kept active reaches the preset order quantity. After that, it can be switched back to the original payment channel. The preset order quantity can be set based on actual needs, and this application does not impose specific restrictions on it.
[0066] S303. Based on preset constraints, determine whether each payment channel in the store's routing queue is available. If it is not available, delete the payment channel from the routing queue.
[0067] In S303, specifically, the preset constraints include one or more of the following conditions: (1) Determine if the merchant number of the payment channel exists. If not, the payment channel is deemed unusable. (2) Determine whether the merchant number of the payment channel is available. If not, the payment channel is deemed unavailable. (3) Determine whether the payment channel supports the payment method of the current payment order. If not, the payment channel is deemed unavailable. For example, if the payment method of the current payment order is WeChat Pay, and the payment channel does not support the payment method, the payment channel is deemed unavailable and is removed from the routing queue.
[0068] (4) Determine whether the current payment period is within the preset available period of the payment channel. If not, determine that the payment channel is unavailable. (5) Determine whether the current payment period is within the preset maintenance period of the payment channel. If so, the payment channel is deemed unavailable. (6) Determine whether the payment channel supports the store's preset fund settlement method. If not, the payment channel is deemed unusable. For example, if the store needs to settle the acquiring funds to the bank's internal account, but the payment channel does not support this settlement method, the payment channel is deemed unusable and removed from the routing queue.
[0069] By setting the above constraints, the availability of payment channels can be comprehensively verified from multiple dimensions, ensuring that only payment channels that meet the requirements of the current transaction scenario, are in normal status, and have compliant configurations are retained in the routing queue. This screening process effectively avoids routing payment requests to invalid or mismatched payment channels, reducing payment failures caused by channel unavailability. It also optimizes the range of routing selection, improves the accuracy and efficiency of payment routing decisions, and provides a reliable candidate set for subsequent payment channel selection based on channel scoring, further guaranteeing the stability of in-store payment services and user experience.
[0070] In the aforementioned automatic routing scenario, directly switching payment channels, while ensuring payment stability, results in multiple inflows to the store during the next day's fund settlement, causing significant inconvenience for store reconciliation. If N channels are switched the previous day, the store will receive N inflows the following day. To mitigate the inconvenience caused by payment channel switching for store reconciliation, in other embodiments of this application, one implementation of the step of using the target payment channel for acquiring and settling specifically includes: S401. Complete the acquiring transaction using the target payment channel and settle the acquiring funds to the bank's internal account.
[0071] Specifically, in S401, the acquiring system is linked to the bank's internal account product. Funds from acquiring transactions across various payment channels are cleared to this internal account, where the bank acts as escrow for the cleared funds, rather than directly settling them into the store's legal representative's bank account. For example, funds acquired through payment channels A and B will both be cleared to the store's internal bank account on day D+1. For instance, if channel A acquires 100 yuan and channel B acquires 50 yuan, 150 yuan will be credited to the internal bank account the following day. The payment system provides the store with access to account balance and transaction history. The store can see the 150 yuan balance and initiate a withdrawal to the legal representative's bank account, thus achieving a single-transaction settlement of funds after acquiring transactions through multiple payment channels.
[0072] The aforementioned store payment management methods also include: S402. Reconcile and separate the acquiring funds in the bank's internal account with the channel bills to determine the balance of the store's internal account; In S402, specifically on D+1 day, acquiring funds from multiple payment channels are settled into the bank's internal account. After the payment system receives the channel invoices, it performs data verification between the two parties. The verification may result in the following situations: (1) For leveling. Normal sorting and separation processing; (2) If the quantity of long or short items is equal to the difference data of the previous day or earlier, it is marked as a daily cut order and processed normally. Specifically, the quantity of long or short items on the current day is checked twice with the quantity of long or short items on the previous day or earlier. If they are equal, the system marks it as a daily cut order. For example, if the order number is 123456, the quantity of long items is on day D1 and the quantity of short items is on day D2. Combining the quantities of D1 and D2 will result in an equal balance. (3) Long items. Long item data will not be sorted. (4) Shortage. Shortage data will not be cleared.
[0073] Then, a clearing process is initiated with the bank's internal accounts. A list of stores whose acquiring settlement method is the bank's internal account is filtered, clearing data is compiled, and a clearing request is sent to the bank to determine the store's internal account balance. Several possible clearing results may occur: (1) The clearing data and the incoming funds are completely consistent, and the clearing is successful; (2) If the clearing data is less than the incoming funds, the clearing will fail. You need to contact the channel to verify the discrepancy between the bill and the funds, and then re-upload the clearing data.
[0074] S403. Based on the store's withdrawal request and the store's internal account balance, withdraw the transaction funds to the store's bank account.
[0075] In S403, specifically, after the clearing is completed, the balance of the internal account corresponding to the store increases, and the store can initiate a withdrawal request to withdraw the transaction funds of the previous day to the store's bank card. This application is not limited to this.
[0076] In this embodiment, all payment collection funds are settled to the bank's internal account. Funds collected by a store through multiple channels can be credited to the store in one transaction. This reduces the inconvenience caused to store reconciliation by switching payment channels without affecting the store's reconciliation (i.e., the store still receives a single payment).
[0077] like Figure 2 As shown, in another embodiment of this application, a store payment management system is provided, including: The detection unit 10 is used to detect the channel evaluation indicators of each payment channel in the store's routing queue when automatic routing is triggered. The channel evaluation indicators include the payment success rate in N minutes, the average transaction response time, and the channel fee rate. Calculation unit 11 is used to perform weighted summation calculations based on the channel evaluation indicators of each payment channel to obtain the channel score for each payment channel. The specific calculation formula is as follows: Channel score = N-minute payment success rate × a + (maximum preset transaction response time - average transaction response time) × b + (preset industry standard fee rate - channel fee rate) × c; In the formula, a represents the preset payment success rate weight, b represents the preset response time weight, and c represents the preset channel fee rate weight. Payment unit 12 is used to select the payment channel with the highest channel score as the target payment channel and use the target payment channel to perform acquiring settlement.
[0078] In other embodiments of this application, the calculation method for the N-minute payment success rate in the above-mentioned store payment management system is as follows: The payment success rate of the payment channel in N minutes is obtained by dividing the number of orders successfully paid through the payment channel within the first preset time period by the number of orders that initiated payment to the payment channel within the first preset time period.
[0079] In other embodiments of this application, the average transaction response time in the above-mentioned store payment management system is calculated as follows: The average transaction response time of the payment channel is obtained by dividing the sum of the transaction response times of all orders in the second preset time period by the number of orders that initiated payment to the payment channel in the second preset time period.
[0080] In other embodiments of this application, the above-mentioned store payment management system further includes: an adjustment unit, used to dynamically configure a preset payment success rate weight a, a preset response time weight b, and a preset channel fee rate weight c according to preset weight adjustment rules, wherein the preset weight adjustment rules include: The real-time number of customers in the store is detected according to the first preset cycle. The store's customer flow status is determined based on the real-time number of customers and the preset customer flow threshold. The store's customer flow status is one of the following: low customer flow, medium customer flow, and high customer flow. If the store's customer flow status is low, set the preset channel fee rate weight c > preset payment success rate weight a > preset response time weight b; If the store's customer flow status is medium, set the preset payment success rate weight a > preset response time weight b = preset channel fee rate weight c; If the store's customer traffic status is high, set the preset response time weight b > preset payment success rate weight a > preset channel fee rate weight c.
[0081] In other embodiments of this application, the preset weight adjustment rules in the above-mentioned store payment management system further include: Determine if the current date is a set holiday. If so, increase the preset payment success rate weight 'a' and the preset response time weight 'b'.
[0082] In other embodiments of this application, the preset weight adjustment rules in the above-mentioned store payment management system further include: Determine whether the current average order value of the store is greater than or equal to the preset average order value threshold. If so, increase the preset channel fee rate weight c. If not, increase the preset payment success rate weight a.
[0083] In other embodiments of this application, the preset weight adjustment rules in the above-mentioned store payment management system further include: According to the second preset cycle, the difference between the current channel evaluation index and the preset target value is calculated respectively to obtain the payment success rate difference, average response time difference and channel fee rate difference; For each of the preset payment success rate weight a, preset response time weight b, and preset channel fee rate weight c, an independent PID controller is designed. The difference in payment success rate, the difference in average response time, and the difference in channel fee rate are input into the three PID controllers respectively to obtain the adjustment amount of payment success rate weight, response time weight, and channel fee rate weight. Based on the current preset payment success rate weight, the current preset response time weight, and the current preset channel fee rate weight, as well as the adjustment amounts of the payment success rate weight, response time weight, and channel fee rate weight, the dynamically adjusted preset payment success rate weight, the dynamically adjusted preset response time weight, and the dynamically adjusted preset channel fee rate weight are calculated.
[0084] In other embodiments of this application, the calculation method for the payment success rate difference in the above-mentioned store payment management system is as follows: E_s(t) = S_target - S_actual(t); In the formula, E_s(t) represents the difference in payment success rate at the current time t, S_target represents the preset target value for payment success rate, and S_actual(t) represents the payment success rate at the current time t over N minutes; The average response time difference is calculated as follows: E_t(t) = T_actual(t) - T_target; In the formula, E_t(t) represents the difference in average response time at the current time t, T_actual(t) represents the average transaction response time at the current time t, and T_target represents the preset target value for average response time; The formula for calculating the channel fee rate difference is: E_c(t) = C_actual(t) - C_target; In the formula, E_c(t) represents the channel rate difference at the current time t, C_actual(t) represents the channel rate at the current time t, and C_target represents the preset channel rate target value.
[0085] In other embodiments of this application, in the above-mentioned store payment management system, the expression for the PID controller corresponding to the preset payment success rate weight 'a' is: ΔW_s(t)=Kp_s×E_s(t)+Ki_s×∫E_s(t)dt+Kd_s×dE_s(t) / dt; In the formula, Kp_s represents the first proportional coefficient, Ki_s represents the first integral coefficient, Kd_s represents the first differential coefficient, and ΔW_s(t) represents the weight adjustment amount for payment success rate. The expression for the PID controller corresponding to the preset response time weight b is: ΔW_t(t)=Kp_t×E_t(t)+Ki_t×∫E_t(t)dt+Kd_t×dE_t(t) / dt; In the formula, Kp_t represents the second proportional coefficient, Ki_t represents the second integral coefficient, Kd_t represents the second differential coefficient, and ΔW_t(t) represents the response time weight adjustment amount; The expression for the PID controller corresponding to the preset channel fee rate weight c is: ΔW_c(t)=Kp_c×E_c(t)+Ki_c×∫E_c(t)dt+Kd_c×dE_c(t) / dt; In the formula, Kp_c represents the third proportional coefficient, Ki_c represents the third integral coefficient, Kd_c represents the third differential coefficient, and ΔW_c(t) represents the channel fee rate weight adjustment.
[0086] In other embodiments of this application, the above-mentioned store payment management system calculates dynamically adjusted preset payment success rate weights, dynamically adjusted preset response time weights, and dynamically adjusted preset channel fee rate weights based on the current preset payment success rate weight, the current preset response time weight, and the current preset channel fee rate weight, as well as the adjustment amounts of the payment success rate weight, response time weight, and channel fee rate weight, including: Based on the current preset payment success rate weight, current preset response time weight, and current preset channel fee rate weight, as well as the adjustment amounts for the payment success rate weight, response time weight, and channel fee rate weight, the updated preset payment success rate weight, updated preset response time weight, and updated preset channel fee rate weight are calculated using the following formulas: a_new=a'+ΔW_s(t); b_new=b'+ΔW_t(t); c_new=c'+ΔW_c(t); In the formula, a' represents the current preset payment success rate weight, b' represents the current preset response time weight, c' represents the current preset channel fee rate weight, a_new represents the updated preset payment success rate weight, b_new represents the updated preset response time weight, and c_new represents the updated preset channel fee rate weight. Based on the updated preset payment success rate weight, updated preset response time weight, and updated preset channel fee rate weight, normalization is performed to obtain the dynamically adjusted preset payment success rate weight, dynamically adjusted preset response time weight, and dynamically adjusted preset channel fee rate weight. The calculation formula is as follows: w_total = a_new + b_new + c_new; a_final = a_new / w_total; b_final = b_new / w_total; c_final = c_new / w_total; In the formula, w_total represents the weight sum, a_final represents the dynamically adjusted preset payment success rate weight, b_final represents the dynamically adjusted preset response time weight, and c_final represents the dynamically adjusted preset channel fee rate weight.
[0087] In other embodiments of this application, the above-mentioned store payment management system further includes: The inspection unit is used to perform a health check on the merchant ID of the store's payment channel. Specifically, it includes: requesting a pre-order from the store's payment channel according to a preset inspection cycle. If the pre-order is successful, the merchant ID of the payment channel is considered to be usable. If the pre-order fails, the merchant ID of the payment channel is considered to be unusable. The keep-alive unit is used to keep the available payment channels of a merchant account active. Specifically, it includes switching the store's current payment channel to the payment channel available to the merchant account to be kept active according to a preset keep-alive period, until the number of successfully paid orders through the payment channel available to the merchant account to be kept active reaches a preset number of orders.
[0088] In other embodiments of this application, the above-mentioned store payment management system further includes: The constraint unit is used to determine whether each payment channel in the store's routing queue is available based on preset constraint conditions. If it is not available, the payment channel is deleted from the routing queue. The preset constraints include one or more of the following conditions: Determine if the merchant ID of the payment channel exists; if not, the payment channel is deemed unavailable. Determine if the merchant ID of the payment channel is available; if not, then the payment channel is deemed unavailable. Determine whether the payment channel supports the payment method of the current payment order; if not, the payment channel is deemed unavailable. Determine whether the current payment period is within the preset available period of the payment channel; if not, determine that the payment channel is unavailable. Determine whether the current payment period is within the preset maintenance period of the payment channel; if so, determine that the payment channel is unavailable. Determine whether the payment channel supports the store's preset fund settlement method. If not, the payment channel is deemed unavailable.
[0089] In other embodiments of this application, in the above-mentioned store payment management system, the payment unit 12, when performing acquiring settlement using the target payment channel, is specifically used for: The acquiring process is completed using the target payment channel, and the acquired funds are settled into the bank's internal account.
[0090] In other embodiments of this application, the above-mentioned store payment management system further includes: The processing unit is used to reconcile and clear the acquiring funds of the bank's internal accounts with the channel bills in order to determine the balance of the store's internal accounts; The withdrawal unit is used to withdraw transaction funds to the store's bank account based on the store's withdrawal request and the store's internal account balance.
[0091] The above description of the disclosed embodiments enables those skilled in the art to make or use this application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this application. Therefore, this application is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims
1. A store payment management method, characterized in that, include: When automatic routing is triggered, the channel evaluation indicators of each payment channel in the store's routing queue are detected. The channel evaluation indicators include the payment success rate in N minutes, the average transaction response time, and the channel fee rate. Based on the channel evaluation indicators of each payment channel, a weighted summation is performed to obtain the channel score for each payment channel. The specific calculation formula is as follows: Channel score = N-minute payment success rate × a + (maximum preset transaction response time - average transaction response time) × b + (preset industry standard fee rate - channel fee rate) × c; In the formula, a represents the preset payment success rate weight, b represents the preset response time weight, and c represents the preset channel fee rate weight. The payment channel with the highest channel score is selected as the target payment channel, and the acquiring and settlement are carried out using the target payment channel.
2. The method as described in claim 1, characterized in that, The calculation method for the N-minute payment success rate is as follows: The payment success rate of the payment channel in N minutes is obtained by dividing the number of orders successfully paid through the payment channel within the first preset time period by the number of orders that initiated payment to the payment channel within the first preset time period.
3. The method as described in claim 1, characterized in that, The average transaction response time is calculated as follows: The average transaction response time of the payment channel is obtained by dividing the sum of the transaction response times of all orders in the second preset time period by the number of orders that initiated payment to the payment channel in the second preset time period.
4. The method as described in claim 1, characterized in that, The preset payment success rate weight a, the preset response time weight b, and the preset channel fee rate weight c are dynamically configured through preset weight adjustment rules, which include: The real-time number of customers in the store is detected according to the first preset cycle. The store's customer flow status is determined based on the real-time number of customers and the preset customer flow threshold, wherein the store's customer flow status is one of low customer flow status, medium customer flow status, and high customer flow status. If the store's customer flow status is low, set the preset channel fee rate weight c > the preset payment success rate weight a > the preset response time weight b; If the store's customer flow status is medium, set the preset payment success rate weight a > the preset response time weight b = the preset channel fee rate weight c; If the store's customer flow status is high, set the preset response time weight b > the preset payment success rate weight a > the preset channel fee rate weight c.
5. The method as described in claim 4, characterized in that, The preset weight adjustment rules also include: Determine whether the current date is a set holiday. If so, increase the preset payment success rate weight 'a' and the preset response time weight 'b'.
6. The method as described in claim 4, characterized in that, The preset weight adjustment rules also include: Determine whether the current average order value of the store is greater than or equal to the preset average order value threshold. If so, increase the preset channel fee rate weight c. If not, increase the preset payment success rate weight a.
7. The method according to any one of claims 4 to 6, characterized in that, The preset weight adjustment rules also include: According to the second preset cycle, the difference between the current channel evaluation index and the preset target value is calculated respectively to obtain the payment success rate difference, the average response time difference, and the channel fee rate difference; For the preset payment success rate weight a, the preset response time weight b, and the preset channel fee rate weight c, design an independent PID controller. Input the payment success rate difference, the average response time difference, and the channel fee rate difference into the three PID controllers respectively to obtain the payment success rate weight adjustment amount, the response time weight adjustment amount, and the channel fee rate weight adjustment amount. Based on the current preset payment success rate weight, the current preset response time weight, and the current preset channel fee rate weight, as well as the adjustment amount of the payment success rate weight, the adjustment amount of the response time weight, and the adjustment amount of the channel fee rate weight, the dynamically adjusted preset payment success rate weight, the dynamically adjusted preset response time weight, and the dynamically adjusted preset channel fee rate weight are calculated.
8. The method as described in claim 7, characterized in that, The calculation method for the payment success rate difference is as follows: E_s(t) = S_target - S_actual(t); In the formula, E_s(t) represents the payment success rate difference at the current time t, S_target represents the preset payment success rate target value, and S_actual(t) represents the payment success rate over N minutes at the current time t; The average response time difference is calculated as follows: E_t(t) = T_actual(t) - T_target; In the formula, E_t(t) represents the difference in average response time at the current time t, T_actual(t) represents the average transaction response time at the current time t, and T_target represents the preset target value for average response time; The formula for calculating the channel rate difference is as follows: E_c(t) = C_actual(t) - C_target; In the formula, E_c(t) represents the channel rate difference at the current time t, C_actual(t) represents the channel rate at the current time t, and C_target represents the preset channel rate target value.
9. The method as described in claim 8, characterized in that, The expression for the PID controller corresponding to the preset payment success rate weight 'a' is: ΔW_s(t)=Kp_s×E_s(t)+Ki_s×∫E_s(t)dt+Kd_s×dE_s(t) / dt; In the formula, Kp_s represents the first proportional coefficient, Ki_s represents the first integral coefficient, Kd_s represents the first differential coefficient, and ΔW_s(t) represents the payment success rate weight adjustment amount. The expression for the PID controller corresponding to the preset response time weight b is: ΔW_t(t)=Kp_t×E_t(t)+Ki_t×∫E_t(t)dt+Kd_t×dE_t(t) / dt; In the formula, Kp_t represents the second proportional coefficient, Ki_t represents the second integral coefficient, Kd_t represents the second differential coefficient, and ΔW_t(t) represents the response time weight adjustment amount; The expression for the PID controller corresponding to the preset channel rate weight c is: ΔW_c(t)=Kp_c×E_c(t)+Ki_c×∫E_c(t)dt+Kd_c×dE_c(t) / dt; In the formula, Kp_c represents the third proportional coefficient, Ki_c represents the third integral coefficient, Kd_c represents the third differential coefficient, and ΔW_c(t) represents the channel fee rate weight adjustment amount.
10. The method as described in claim 9, characterized in that, The step of calculating the dynamically adjusted preset payment success rate weight, the dynamically adjusted preset response time weight, and the dynamically adjusted preset channel fee rate weight based on the current preset payment success rate weight, the current preset response time weight, and the current preset channel fee rate weight, as well as the adjustment amounts of the payment success rate weight, the response time weight, and the channel fee rate weight, includes: The updated preset payment success rate weight, updated preset response time weight, and updated preset channel fee rate weight are calculated based on the current preset payment success rate weight, the current preset response time weight, and the current preset channel fee rate weight, as well as the adjustment amounts of the payment success rate weight, the response time weight, and the channel fee rate weight. The calculation formula is as follows: a_new=a'+ΔW_s(t); b_new=b'+ΔW_t(t); c_new=c'+ΔW_c(t); In the formula, a' represents the current preset payment success rate weight, b' represents the current preset response time weight, c' represents the current preset channel fee rate weight, a_new represents the updated preset payment success rate weight, b_new represents the updated preset response time weight, and c_new represents the updated preset channel fee rate weight. Based on the updated preset payment success rate weight, the updated preset response time weight, and the updated preset channel fee rate weight, normalization is performed to obtain the dynamically adjusted preset payment success rate weight, dynamically adjusted preset response time weight, and dynamically adjusted preset channel fee rate weight. The calculation formula is as follows: w_total = a_new + b_new + c_new; a_final = a_new / w_total; b_final = b_new / w_total; c_final = c_new / w_total; In the formula, w_total represents the weight sum, a_final represents the dynamically adjusted preset payment success rate weight, b_final represents the dynamically adjusted preset response time weight, and c_final represents the dynamically adjusted preset channel fee rate weight.
11. The method as described in claim 1, characterized in that, Also includes: A health check is performed on the merchant ID of the store's payment channel. Specifically, this includes requesting a pre-order from the store's payment channel according to a preset check cycle. If the pre-order is successful, the merchant ID of the payment channel is considered to be usable. If the pre-order fails, the merchant ID of the payment channel is considered to be unusable. To keep the payment channels available for a merchant account active, specifically, according to a preset active period, the store's current payment channel is switched to the payment channel available for the merchant account to be active, until the number of successfully paid orders through the payment channel available for the merchant account to be active reaches a preset number of orders.
12. The method as described in claim 11, characterized in that, Also includes: Based on preset constraints, determine whether each payment channel in the store's routing queue is available. If it is not available, remove the payment channel from the routing queue. The preset constraints include one or more of the following conditions: Determine if the merchant ID of the payment channel exists; if not, the payment channel is deemed unavailable. Determine if the merchant ID of the payment channel is available; if not, then the payment channel is deemed unavailable. Determine whether the payment channel supports the payment method of the current payment order; if not, the payment channel is deemed unavailable. Determine whether the current payment period is within the preset available period of the payment channel; if not, determine that the payment channel is unavailable. Determine whether the current payment period is within the preset maintenance period of the payment channel; if so, determine that the payment channel is unavailable. Determine whether the payment channel supports the store's preset fund settlement method. If not, the payment channel is deemed unavailable.
13. The method according to any one of claims 1 to 6, 11 and 12, characterized in that, The process of using the target payment channel for acquiring and settlement includes: The acquiring transaction is completed using the target payment channel, and the acquired funds are settled to the bank's internal account.
14. The method as described in claim 13, characterized in that, After completing the acquiring transaction using the target payment channel and settling the acquiring funds into the bank's internal account, the process further includes: The acquiring funds in the bank's internal account are reconciled and cleared with the channel bills to determine the balance of the store's internal account; Based on the store's withdrawal request and the store's internal account balance, the transaction funds are withdrawn to the store's bank account.
15. A store payment management system, characterized in that, include: The detection unit is used to detect the channel evaluation indicators of each payment channel in the store's routing queue when automatic routing is triggered. The channel evaluation indicators include the payment success rate in N minutes, the average transaction response time, and the channel fee rate. The calculation unit is used to perform weighted summation calculations based on the channel evaluation indicators of each payment channel to obtain the channel score of each payment channel. The specific calculation formula is as follows: Channel score = N-minute payment success rate × a + (maximum preset transaction response time - average transaction response time) × b + (preset industry standard fee rate - channel fee rate) × c; In the formula, a represents the preset payment success rate weight, b represents the preset response time weight, and c represents the preset channel fee rate weight. The payment unit is used to select the payment channel with the highest channel score as the target payment channel and use the target payment channel to perform acquiring and settlement.
Citation Information
Patent Citations
Payment channel selection method and device, and payment channel router
CN110852503A
Merchant information processing method and device
CN116012008A
Data processing method and system based on dynamic routing
CN119539795A
Disaster recovery data recovery method and system of disaster recovery system
CN120017608A
Cross-border payment fund routing optimization method and system
CN120598548A