Balance checking method, device, equipment and system

Abstract

The invention provides a balance checking method, device, equipment and system, and is applied to the technical field of balance checking. The method comprises the steps of obtaining enterprise setting information of an enterprise account based on a charging order under the enterprise account; judging whether the enterprise setting information has a risk mark or not; if the enterprise setting information does not have the risk mark, balance verification is carried out on the enterprise account, and the risk mark of the enterprise setting information is determined according to the enterprise information. And if the enterprise setting information has the risk mark and the risk mark does not exist, continuously charging the charging order, and checking the risk-free mark of the enterprise setting information according to a preset checking period. According to the embodiment of the invention, if the enterprise setting information has the risk mark and the risk mark exists, balance verification is performed on the enterprise account, and the risk mark of the enterprise setting information is verified according to the preset verification period, account balance verification does not need to be performed on each charging order under the enterprise account, and the balance verification pressure of the charging platform can be reduced.

Description

Technical Field

[0001] The present application relates to the technical field of balance verification, and in particular to a balance verification method, device, equipment, and system. Background Art

[0002] In order to ensure the normal charging process and reduce problems such as bad debts, overcharging, and freeloading, charging operators use balance verification to check in real time during the charging process whether the charging user's account balance can pay the amount required for charging.

[0003] However, as the charging volume gradually increases and the number of corporate orders is huge, the charging platform still needs to verify the account balance of each order in the case of massive orders, which will cause excessive computing pressure on the charging platform.

[0004] Therefore, there is an urgent need for a balance verification method to reduce the balance verification pressure of the charging platform. Summary of the invention

[0005] The purpose of this application is to provide a balance verification method, device, equipment, and system to reduce the balance verification pressure of the charging platform.

[0006] In a first aspect, an embodiment of the present application provides a balance verification method, the method comprising: based on a charging order under a corporate account, obtaining corporate setting information of the enterprise to which the corporate account belongs; the corporate setting information is used to indicate whether the corporate information of the corporate account has a risk mark; judging whether the corporate setting information has a risk mark according to a preset detection period; the risk mark includes a no-risk mark and a risk mark; if the corporate setting information does not have the risk mark, performing a balance verification on the corporate account, and determining the risk mark of the corporate setting information based on the corporate information; or if the corporate setting information has a risk mark, and the risk mark is the no-risk mark, continuing to charge the charging order, and verifying the no-risk mark of the corporate setting information according to a preset verification period; the preset verification period is determined based on the corporate information; the charging process of continuing to execute the charging order does not require the balance verification of the corporate account; or if the corporate setting information has a risk mark, and the risk mark is the risk mark, performing a balance verification on the corporate account, and verifying the risk mark of the corporate setting information according to the preset verification period.

[0007] The balance verification method provided in the embodiment of the present application will continue to charge the charging order when there is a risk-free mark in the enterprise setting information. There is no need to verify the balance of the enterprise account. It only needs to verify the risk mark of the enterprise account within the validity period. There is no need to verify the account balance for each charging order under the enterprise account, which can reduce the pressure of balance verification on the charging platform and improve the processing efficiency of the charging platform. At the same time, by focusing on monitoring risky enterprises, potential risks can be better prevented and the security of corporate accounts can be guaranteed.

[0008] In a possible implementation, the enterprise information further includes: the amount of funds used and the total amount of unpaid orders. The risk mark also includes a no-risk mark. Determining the risk mark of the enterprise setting information according to the enterprise information includes: when the sum of the amount of funds used and the total amount of unpaid orders is less than or equal to a preset multiple of the account balance, determining that the enterprise setting information is the no-risk mark. When the sum of the amount of funds used and the total amount of unpaid orders is greater than a preset multiple of the account balance, determining that the enterprise setting information is the risk mark.

[0009] In a possible implementation, the enterprise information also includes: the scale information of the enterprise. The process of determining the amount of funds used includes: obtaining historical order information of the enterprise account in a preset time period. The historical order information includes: the number of historical orders and the amount of historical orders. Based on the number of historical orders and the amount of historical orders, determine the estimated flow rate of funds of the enterprise account in the preset time period. Based on the estimated flow rate of funds, determine the amount of funds used by the enterprise account at a preset level. The preset level corresponds to the scale information of the enterprise.

[0010] In a possible implementation, the preset level includes: a first level and a second level. The duration corresponding to the first level is shorter than the duration corresponding to the second level. The method further includes: calculating the historical highest capital flow rate of the enterprise account according to the historical order quantity and the historical order information. If the estimated capital flow rate is higher than the historical highest capital flow rate, the preset level corresponding to the enterprise account is adjusted to the first level. If the estimated capital flow rate is not higher than the historical highest capital flow rate, the preset level corresponding to the enterprise account is adjusted to the second level.

[0011] In a possible implementation, the balance verification method provided in the embodiment of the present application further includes: when the account balance is less than or equal to a preset minimum amount, adding the risk mark to the enterprise account and generating a reminder message. The reminder message is used to prompt that the account balance of the enterprise account is insufficient.

[0012] In a possible implementation, the enterprise information also includes the number of historical daily orders and the number of unpaid orders. The balance verification method provided in the embodiment of the present application also includes: when the number of unpaid orders exceeds a preset number of unpaid orders, adding the risk mark to the enterprise account. The preset number of unpaid orders is determined based on the number of historical daily orders.

[0013] In a possible implementation, the risk-free mark and the risky mark are used as target risk marks, and the target risk mark of the enterprise setting information is verified according to a preset period, including: obtaining the use period of the risk mark. According to the scale information of the enterprise in the enterprise information, determining the preset period corresponding to the preset level of the enterprise account. When the use period of the risk mark is the same as the preset verification period, determining the target risk mark of the enterprise setting information at the current moment according to the enterprise information.

[0014] In a possible implementation, the balance verification method provided in the embodiment of the present application further includes: when the verification time point of the preset verification period is reached, obtaining the number of all the target risk markers newly added at the verification time point. When the number of all the target risk markers does not belong to the preset number interval, generating abnormal information. The abnormal information is used to indicate that the balance verification is abnormal.

[0015] In a second aspect, an embodiment of the present application provides a balance verification device, which includes: an acquisition module, a judgment module, a verification module, and a charging module.

[0016] Among them, the acquisition module is used to obtain the enterprise setting information of the enterprise account based on the charging order under the enterprise account; the enterprise setting information is used to indicate whether there is a risk mark on the enterprise information of the enterprise account.

[0017] The judgment module is used to judge whether the enterprise setting information has a risk mark according to a preset detection period. The risk mark includes a no-risk mark and a risk mark.

[0018] A verification module is used to verify the balance of the enterprise account if the risk mark does not exist in the enterprise setting information, and determine the risk mark of the enterprise setting information based on the enterprise information.

[0019] The charging module is used for, if there is a risk mark in the enterprise setting information and the risk mark is the risk-free mark, continuing to charge the charging order and verifying the risk-free mark of the enterprise setting information according to a preset verification period; the preset verification period is determined according to the enterprise information. The charging process of continuing to execute the charging order does not require the balance verification of the enterprise account.

[0020] The verification module is also used to verify the balance of the enterprise account if there is a risk mark in the enterprise setting information and the risk mark is the risk mark, and verify the risk mark of the enterprise setting information according to the preset verification period.

[0021] In a third aspect, the present application provides a balance verification device, which has the function of implementing the balance verification method of the first aspect or any possible implementation method. The function can be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

[0022] In a fourth aspect, a computer-readable storage medium is provided, wherein instructions are stored in the computer-readable storage medium, and when the computer-readable storage medium is run on a computer, the computer can execute the balance verification method of the first aspect or any possible implementation manner.

[0023] In a fifth aspect, a computer program product comprising instructions is provided, which, when executed on a computer, enables the computer to execute the balance verification method of the first aspect or any possible implementation manner.

[0024] Among them, the technical effects brought about by any design method in the second to fifth aspects can refer to the technical effects brought about by different possible implementation methods in the first aspect, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] In order to more clearly illustrate the specific implementation methods of the present application or the technical solutions in the prior art, the drawings required for use in the specific implementation methods or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some implementation methods of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0026] Figure 1 A structural schematic diagram of a balance verification device provided in an embodiment of the present application;

[0027] Figure 2 A structural schematic diagram of a balance verification system provided in an embodiment of the present application;

[0028] Figure 3 A flow chart of a balance verification method provided in an embodiment of the present application;

[0029] Figure 4 A schematic diagram of a balance verification method provided in an embodiment of the present application;

[0030] Figure 5 A specific example diagram of a risk trend diagram provided in an embodiment of the present application;

[0031] Figure 6 A specific example diagram of a balance verification method provided in an embodiment of the present application;

[0032] Figure 7 A structural schematic diagram of a balance verification device provided in an embodiment of the present application;

[0033] Figure 8 Another structural schematic diagram of a balance verification system provided in an embodiment of the present application. DETAILED DESCRIPTION

[0034] In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all the embodiments. The components of the embodiments of the present application described and shown in the drawings here can be arranged and designed in various different configurations.

[0035] Therefore, the following detailed description of the embodiments of the present application provided in the accompanying drawings is not intended to limit the scope of the present application for which protection is sought, but merely represents selected embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in the field without creative work are within the scope of protection of the present application.

[0036] At present, when the charging platform verifies the balance of the enterprise account, it adopts the method of verification before the end of the service. That is, before each user charges, the charging platform will check whether the user's account balance can pay the required amount. When the number of enterprise orders is large, the charging platform still needs to verify the account balance of each order, which causes excessive calculation pressure on the charging platform.

[0037] Based on this, the embodiment of the present application provides a balance verification method, device, equipment, and system, the method comprising: based on the charging order under the enterprise account, obtaining the enterprise setting information of the enterprise to which the enterprise account belongs. The enterprise setting information is used to indicate whether the enterprise information of the enterprise account has a risk mark. It is determined whether the enterprise setting information has a risk mark according to the preset detection cycle. The risk mark includes a no-risk mark and a risk mark. If there is no risk mark in the enterprise setting information, the balance of the enterprise account is verified, and the risk mark of the enterprise setting information is determined according to the enterprise information. Or if there is a risk mark in the enterprise setting information, and the risk mark is a no-risk mark, the charging order continues to be charged, and the no-risk mark in the enterprise setting information is verified according to the preset verification cycle. The preset verification cycle is determined according to the enterprise information. There is no need to verify the balance of the enterprise account when continuing the charging process for the charging order. Or if there is a risk mark in the enterprise setting information, and the risk mark is a risk mark, the balance of the enterprise account is verified, and the risk mark in the enterprise setting information is verified according to the preset verification cycle.

[0038] The balance verification method provided in the embodiment of the present application will continue to charge the charging order when there is a risk-free mark in the enterprise setting information. There is no need to verify the balance of the enterprise account, and only the risk mark needs to be verified according to the preset verification cycle. There is no need to verify the account balance for each charging order under the enterprise account, which can reduce the pressure of balance verification on the charging platform and improve the processing efficiency of the charging platform. At the same time, by focusing on monitoring risky enterprises, potential risks can be better prevented and the security of corporate accounts can be guaranteed.

[0039] The implementation of the embodiments of the present application will be described in detail below with reference to the accompanying drawings.

[0040] On the one hand, a balance verification method provided in an embodiment of the present application can be executed by a balance verification device. Figure 1 As shown, the balance verification device 100 may include: a processor 101 and a memory 102. The memory 102 may be a memory in the processor 101.

[0041] The processor 101 may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor.

[0042] The memory 102 may be a volatile memory or a nonvolatile memory, or may include both volatile and nonvolatile memories. Among them, the nonvolatile memory may be a read-only memory (ROM), a programmable ROM (PROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example but not limitation, many forms of RAM are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM) and direct rambus RAM (DR RAM) or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer, but not limited thereto. The memory can be independent and connected to the processor 101 via a communication line. The memory 102 can also be integrated with the processor 101.

[0043] The memory 102 stores computer executable instructions for implementing the solution of the present application, and is executed under the control of the processor 101. The processor 101 is used to execute the computer executable instructions stored in the memory 102, thereby implementing the balance verification method provided in the following embodiment of the present application.

[0044] On the one hand, the balance verification method provided in the embodiment of the present application can be executed by a balance verification system. Figure 2 As shown, the balance verification system 200 may include: a balance verification device 100 and a cloud 201 .

[0045] The balance verification device 100 may be, but is not limited to, a mobile phone, a tablet computer, a laptop computer, an ultra-mobile personal computer (UMPC), a netbook, or a personal digital assistant (PDA), and other terminal devices, and no limitation is imposed on the specific type of the terminal device. The balance verification device 100 is used to support the balance verification method provided in the embodiment of the present application, based on the charging order under the enterprise account, obtain the enterprise setting information of the enterprise account, execute the risk mark acquisition request according to the preset detection cycle, and continue to charge the charging order if there is a no-risk mark in the enterprise setting information.

[0046] The balance verification device 100 can also be used to provide an interactive function for the user. The user can input data and information to the balance verification device 100 through the interactive interface of the balance verification device 100. For example, the user can manually input a charging order through the interactive interface.

[0047] The cloud 201 may be a resource cluster shared by multiple balance verification devices 100. The resource cluster can provide multiple algorithms for use by the balance verification device 100. The resource cluster may belong to a public cloud or a private cloud. In the case of a public cloud, the resource cluster may be used by different company users and individual users. In the case of a private cloud, the resource cluster generally only serves the company users described in the private cloud.

[0048] On the one hand, the present application embodiment discloses a balance verification method, which can be Figure 2 The balance verification system 200 shown in FIG. Figure 1 The balance checking device 100 shown in FIG. Figure 3 As shown, the method may include:

[0049] S301, based on the charging order under the enterprise account, obtain the enterprise setting information of the enterprise to which the enterprise account belongs.

[0050] Among them, the enterprise setting information is used to indicate whether there is a risk mark on the enterprise information of the enterprise account.

[0051] Among them, enterprise information includes account balance, capital usage, enterprise size information, historical daily order quantity, unpaid order quantity and total unpaid order amount.

[0052] For example, when a user needs to charge, he or she uses the enterprise account to submit a charging order through the interactive interface of the balance verification device. In response to the charging order submitted by the enterprise account, the balance verification device obtains the enterprise setting information of the enterprise to which the enterprise account belongs from the cloud.

[0053] Among them, Figure 4 As shown, users can submit charging orders using corporate accounts, which can include personal charging and corporate payment, corporate charging and corporate payment, and personal charging and corporate payment (limit).

[0054] In one possible implementation, when the balance verification device times out in obtaining the enterprise setting information of the enterprise to which the enterprise account belongs, the process of obtaining the enterprise setting information of the enterprise account will not be performed on the enterprise account this time. The balance of the enterprise account will be directly verified after the next charging order submitted by the enterprise account is received.

[0055] S302: Determine whether there is a risk mark in the enterprise setting information according to a preset detection cycle.

[0056] Exemplarily, a determination is made once every hour whether there is a risk mark in the enterprise setting information.

[0057] Among them, the risk mark includes a no-risk mark and a risk mark. A risk mark indicates that the account balance corresponding to the enterprise information is insufficient or there are other risks. A no-risk mark indicates that the account balance corresponding to the enterprise information is sufficient.

[0058] In one possible implementation, when the balance verification device times out when executing the risk tag acquisition request, the corporate account will not be verified to see whether it meets the preset conditions. The balance of the corporate account will be verified directly after the next charging order submitted by the corporate account is received.

[0059] S303: If the enterprise setting information does not contain the risk mark, perform a balance check on the enterprise account and determine the risk mark of the enterprise setting information based on the enterprise information.

[0060] Exemplarily, when the balance verification device detects that there is no risk mark in the enterprise setting information, it verifies the balance of the enterprise account by comparing the charging order with the account balance.

[0061] In one possible implementation, when there is no risk mark in the enterprise information, the balance verification device determines the risk mark of the enterprise setting information based on the enterprise information.

[0062] Specifically, the balance verification device can obtain the historical order information of the enterprise account in a preset time period. The historical order information includes: the number of historical orders and the amount of historical orders. According to the number of historical orders and the amount of historical orders, the estimated capital flow rate of the enterprise account in the preset time period is determined. According to the estimated capital flow rate, the capital usage of the enterprise account at the preset level is determined. The preset level corresponds to the scale information of the enterprise.

[0063] It should be noted that the preset level may include days, hours, minutes, etc., and this application does not limit this. The initial preset level is different for different enterprise sizes. For example, the initial preset level for a small enterprise may be minutes, that is, the enterprise's capital usage is calculated per minute based on the estimated capital flow rate.

[0064] The balance verification device adds a risk-free mark to the enterprise information when the sum of the fund usage and the total amount of unpaid orders is less than or equal to the account balance of a preset multiple.

[0065] The balance verification device adds the risk mark to the enterprise information when the sum of the fund usage and the total amount of unpaid orders is greater than the account balance of a preset multiple.

[0066] For example, if the sum of the amount of funds used and the total amount of unpaid orders is less than or equal to 2-3 times the account balance, a risk-free mark is added to the enterprise information. If the sum of the amount of funds used and the total amount of unpaid orders is greater than 2-3 times the account balance, a risky mark is added to the enterprise information.

[0067] In a possible implementation, the preset level may include a first level and a second level, and the duration corresponding to the first level is shorter than the duration corresponding to the second level. The balance verification device may calculate the highest historical capital flow rate of the enterprise account based on the number of historical orders and historical order information. If the estimated capital flow rate is higher than the highest historical capital flow rate, the preset level corresponding to the enterprise account is adjusted to the first level. If the estimated capital flow rate is not higher than the highest historical capital flow rate, the preset level corresponding to the enterprise account is adjusted to the second level.

[0068] In another possible implementation, the preset level may further include a third level, and the duration corresponding to the second level is shorter than the duration corresponding to the third level. The balance verification device may set the default level corresponding to the enterprise account to the third level.

[0069] Take the first level as minutes and the second level as hours as an example. The balance verification device calculates the total amount of historical orders based on the number of historical orders and the amount of historical orders in the order information. The highest historical capital flow rate of the enterprise account in the past 7 days is calculated based on the highest historical order volume and the highest historical total order amount in the past 7 days. The highest historical order volume and the highest historical total order amount can be the corresponding information in the same time, or any highest order volume and any highest total order amount in 7 days. If the estimated capital flow rate is higher than the highest historical capital flow rate, the preset level corresponding to the enterprise account is adjusted to perform balance verification by minute. If the estimated capital flow rate is not higher than the highest historical capital flow rate, the preset level corresponding to the enterprise account is adjusted to perform balance verification by hour. In special cases, if it is determined that the system has no risk issues, the system can be manually set to perform balance verification on a daily basis.

[0070] One possible implementation method is that when the account balance is less than or equal to a preset minimum amount, a risk mark is added to the corporate account and a reminder message is generated. The balance verification device sends the reminder message to the cloud, and the cloud displays the reminder message to the user to remind the user that the account balance of the corporate account is insufficient.

[0071] Exemplarily, when the account balance is less than or equal to twice the preset minimum amount, a risk mark is added to the business account to remind the user that the business account is about to have insufficient account balance.

[0072] In one possible implementation, when the number of unpaid orders exceeds a preset number of unpaid orders, a risk mark is added to the enterprise account. The preset number of unpaid orders is determined based on the number of historical daily orders.

[0073] Exemplarily, the balance verification device calculates the proportion of the historical daily order quantity to obtain the allowed number of unpaid orders, which may be 5-10%. When the number of unpaid orders exceeds the historical daily order quantity at a proportion of 5-10%, a risk mark is added to the corporate account.

[0074] In one possible implementation, the balance verification device can set a fixed minimum amount. When the balance verification device detects that the account balance is less than the fixed minimum amount, a risk mark is added to the enterprise account. The fixed minimum amount can be calculated as the minimum amount based on the ratio of the user's highest consumption amount in the historical time, and the default is the consumption amount of one day.

[0075] In one possible implementation, when the balance verification device determines that the user submits a charging order using a corporate account for personal charging and corporate payment (limit), the personal charging and corporate payment is limited according to the preset limit. When the personal charging and corporate payment reaches the preset limit, a risk mark is added to the corporate account.

[0076] In one possible implementation, the balance verification method provided in the embodiment of the present application will also add monitoring reporting for risky enterprises after adding a risky mark to the enterprise account, and report the enterprise internal code and the risky type of the enterprise account with the risky mark to the cloud.

[0077] It should be noted that the risk tags in the enterprise information are updated according to a preset frequency, and the preset frequency can be set to hours or days, etc., which is not limited in this application.

[0078] S304: If the enterprise setting information has a risk mark, and the risk mark is a risk-free mark, continue to charge the charging order, and verify the risk-free mark of the enterprise setting information according to a preset verification cycle.

[0079] Among them, there is no need to check the balance of the enterprise account to continue the charging process for the charging order. In this process, there is no need to check the account balance of each charging order under the enterprise account, which can reduce the pressure of balance verification on the charging platform and improve the processing efficiency of the charging platform. At the same time, by focusing on monitoring risky enterprises, potential risks can be better prevented and the security of corporate accounts can be guaranteed.

[0080] Furthermore, the preset verification cycle is determined based on the enterprise information. Specifically, when the target risk mark is a no-risk mark, the use cycle of the risk mark is obtained, and the preset cycle corresponding to the preset level of the enterprise account is determined based on the scale information of the enterprise in the enterprise information. When the use cycle of the risk mark is the same as the preset verification cycle, the risk mark of the enterprise setting information at the current moment is determined based on the enterprise information.

[0081] Exemplarily, the preset verification period may include days, hours, minutes, etc., which is not limited in the present application. The preset verification period may also be a preset verification period that is individually set in combination with specific enterprise information. The initial preset verification period is different for different enterprise sizes. For example, the initial verification period for a small enterprise may be minutes, that is, the risk mark of the small enterprise is recalculated every minute, and the risk-free mark of the small enterprise at the current moment is determined based on the enterprise information of the small enterprise, so as to realize dynamic monitoring of the small enterprise.

[0082] S305: If there is a risk mark in the enterprise setting information, and the risk mark is a risk mark, the balance of the enterprise account is checked, and the risk mark of the enterprise setting information is checked according to a preset check cycle.

[0083] Exemplarily, when the balance verification device detects that there is a risk mark in the enterprise information and the risk mark is a risk mark, the balance verification device compares the charging order with the account balance.

[0084] Furthermore, the preset verification period is determined based on the enterprise information. Specifically, when the target risk mark is a risk mark, the use period of the risk mark is obtained, and the preset period corresponding to the preset level of the enterprise account is determined based on the scale information of the enterprise in the enterprise information. When the use period of the risk mark is the same as the preset verification period, the risk mark of the enterprise setting information at the current moment is determined based on the enterprise information.

[0085] Furthermore, when the verification time point of the preset verification cycle is reached, the number of all target risk markers added at the verification time point is obtained, and when the number of all target risk markers does not belong to the preset number range, an abnormal information is generated. The abnormal information is used to indicate that the balance verification is abnormal at this time.

[0086] It should be noted that after obtaining the number of all newly added target risk markers at the verification time point, it is also possible to determine whether to generate the abnormal information by combining the risk trend of the target risk marker. For example, if the risk trend at the current verification time point changes too much compared to the risk area at the previous verification time point, abnormal information is generated.

[0087] For example, Figure 5 A specific example diagram of a risk trend graph provided in an embodiment of the present application is illustrated, in which the horizontal axis represents time and the vertical axis represents the number of risk marks. When the preset verification period is 10 seconds, the number of all newly added target risk marks under all enterprises is obtained every 10 seconds, and the average newly added risk mark of each enterprise is calculated, and the risk trend graph is generated using the average risk mark. The risk trend graph shows the number of all risk marks reported by the newly added enterprises at each time point, the number of risk marks and the number of non-risk marks. By comparing the number of risk marks at each time point, when the number of risk marks or non-risk marks is deployed in the preset number interval, an abnormal information is generated to remind that an abnormality has occurred in the balance verification at this time. Users can check the abnormal situation of the enterprise and take measures.

[0088] When there are too many risk tags, users can check whether there are any problems with the data synchronization process of the enterprise information, whether there are any abnormalities in the enterprise's account balance, whether there are any abnormalities in the enterprise information, and other factors that may affect the enterprise's setting information. When there are too many risk tags, it means that the system pressure is rising. Users can check whether the balance of the enterprise account is sufficient. If the balance is insufficient, you can remind the enterprise to recharge, and check whether there are other problems in the enterprise information. If the amount of business data is too large and affects the normal operation of the system, you can increase the system server buffer.

[0089] When the number of risk-free marks is too large, users can check whether there are any abnormalities in the system, such as delays in data synchronization, historical order data or unpaid orders not being synchronized in time.

[0090] The balance verification method provided in the embodiment of the present application will be described in detail below with reference to specific examples.

[0091] like Figure 6 As shown, during the charging process, the user uses the enterprise account to submit a charging order through the interactive interface of the balance verification device. In response to the charging order submitted by the enterprise account, the balance verification device obtains the enterprise information of the enterprise account from the cloud.

[0092] The balance verification device executes the risk tag acquisition request according to the preset period to obtain the risk tag from the data structure server (Redis) corresponding to the enterprise information. Determine whether there is a value in Redis. When there is a value in Redis, determine whether the enterprise account indicated by the value is at risk. If there is no value in Redis, the enterprise account is at risk, and a balance check is performed on the enterprise account. If the value in Redis indicates that the enterprise account is not risky, the charging authority continues to be executed for the charging order. If the value in Redis indicates that the enterprise account is at risk, a balance check is performed on the enterprise account.

[0093] At the same time, if there is no value in Redis, a risk tagging judgment is initiated for the enterprise account. Obtain the enterprise's historical 7-day transaction orders, the highest historical order quantity and historical order amount within 7 days. Calculate the highest historical capital flow rate of the enterprise account within 7 days based on the highest historical order quantity and the highest historical total order amount within 7 days. According to the estimated capital flow rate, determine the capital usage of the enterprise account at three levels corresponding to each day, hour and minute. Based on the capital usage, the total amount of payment orders of the enterprise account and the account balance of the enterprise account, a comparison is made. If the sum of the capital usage and the total amount of unpaid orders is less than or equal to 2-3 times the account balance, add a risk-free tag to the enterprise information. If the sum of the capital usage and the total amount of unpaid orders is greater than 2-3 times the account balance, add a risk tag to the enterprise information.

[0094] When the sum of the amount of funds used and the total amount of unpaid orders is less than or equal to 2-3 times the account balance, a risk-free mark is added to the enterprise information. When the sum of the amount of funds used and the total amount of unpaid orders is greater than 2-3 times the account balance, a risk mark is added to the enterprise information. When the account balance is less than or equal to twice the preset minimum amount, a risk mark is added to the enterprise account to remind the user that the enterprise account is about to have insufficient account balance. The proportion calculated according to the historical daily order quantity is used to obtain the allowed number of unpaid orders, which can be 5-10%. When the number of unpaid orders exceeds the historical daily order quantity at a ratio of 5-10%, a risk mark is added to the enterprise account.

[0095] The above mainly introduces the solution provided by the embodiment of the present application from the perspective of the working principle of the device. It can be understood that in order to realize the above functions, the balance verification device includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should easily realize that, in combination with the algorithm steps of each example described in the embodiments disclosed in this article, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0096] The embodiment of the present application can divide the functional modules of the balance verification device according to the above method example. For example, each functional module can be divided according to each function, or two or more functions can be integrated into one processing module. The above integrated module can be implemented in the form of hardware or software functional module.

[0097] It should be noted that the division of modules in the embodiments of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation. Figure 7 A possible schematic diagram of the balance checking device involved in the above-mentioned embodiment is shown. Figure 7 As shown, the balance verification device 700 may include: an acquisition module 701, a judgment module 702, a verification module 703, and a charging module 704.

[0098] Among them, the acquisition module 701 is used to support the balance verification device 700 to execute Figure 3 S301 of the illustrated balance verification method.

[0099] The judgment module 702 is used to support the balance verification device 700 to execute Figure 3S302 of the illustrated balance verification method.

[0100] Verification module 703, used to support the balance verification device 700 to execute Figure 3 S303 or S305 of the illustrated balance verification method.

[0101] Charging module 704, used to support the balance verification device 700 to execute Figure 3 S304 of the illustrated balance verification method.

[0102] It should be noted that all relevant contents of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional module and will not be repeated here.

[0103] The balance verification device 700 provided in the embodiment of the present application is used to perform the above Figure 3 The balance verification method shown can therefore achieve the same effect as the above-mentioned balance verification method.

[0104] The present application also provides a balance verification device, which can be the balance verification device described in the above embodiment. Figure 1 The balance verification device 100 shown can execute the balance verification method and related steps in the above method embodiment.

[0105] An embodiment of the present application also provides a computer-readable storage medium on which instructions are stored. When the instructions are executed, the balance verification method and related steps in the above method embodiment are executed.

[0106] The embodiment of the present application also provides a computer program product. When the computer program product is run on a computer, the computer executes the balance verification method and related steps in the above method embodiment.

[0107] In some embodiments, the methods described herein may be implemented as computer program instructions encoded in a machine-readable format on a computer-readable storage medium or encoded on other non-transitory media or articles of manufacture.

[0108] The present application embodiment also provides a balance verification system 800, such as Figure 8 As shown, the balance verification system 800 includes at least one processor 801 and at least one interface circuit 802 .

[0109] As an example, when the balance verification system 800 includes a processor and an interface circuit, the processor may be Figure 8 The processor 801 shown in the solid line frame (or the processor 801 shown in the dotted line frame) may be Figure 8The interface circuit 802 shown in the solid line frame (or the interface circuit 802 shown in the dotted line frame). When the chip system 800 includes two processors and two interface circuits, the two processors include Figure 8 The processor 801 shown in the solid line frame and the processor 801 shown in the dotted line frame, the two interface circuits include Figure 8 The interface circuit 802 shown in the solid line frame and the interface circuit 802 shown in the dotted line frame are not limited to this.

[0110] The processor 801 and the interface circuit 802 may be interconnected via a line. For example, the interface circuit 802 may be used to receive a signal. In another example, the interface circuit 802 may be used to send a signal to another device (e.g., the processor 801). For example, the interface circuit 802 may read a computer instruction stored in a memory and send the computer instruction to the processor 801. The processor 801 executes the instruction and implements the various steps in the above embodiments in combination with the input and output devices, such as implementing Figure 3-Figure 6 Of course, the chip system may also include other discrete devices, which are not specifically limited in the embodiments of the present application.

[0111] Through the description of the above implementation methods, technical personnel in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional modules is used as an example. In actual applications, the above-mentioned functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0112] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the modules or units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another device, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0113] The units described as separate components may or may not be physically separated, and the components shown as units may be one physical unit or multiple physical units, that is, they may be located in one place or distributed in multiple different places. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0114] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0115] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application is essentially or the part that contributes or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium, including several instructions to enable a device (which can be a single-chip microcomputer, chip, etc.) or a processor (processor) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read only memory (ROM), random access memory (RAM), disk or optical disk and other media that can store program code.

[0116] The above contents are only specific implementation methods of the present application, but the protection scope of the present application is not limited thereto. Any changes or substitutions within the technical scope disclosed in the present application shall be included in the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A balance verification method, characterized in that: The method comprises: Based on the charging order under the enterprise account, obtain the enterprise setting information of the enterprise to which the enterprise account belongs; the enterprise setting information is used to indicate whether there is a risk mark on the enterprise information of the enterprise account; Determine whether the enterprise setting information has a risk mark according to a preset detection cycle; the risk mark includes a no-risk mark and a risk mark; If the enterprise setting information does not contain the risk mark, perform a balance check on the enterprise account, and determine the risk mark of the enterprise setting information based on the enterprise information; Or, if there is a risk mark in the enterprise setting information, and the risk mark is the risk-free mark, the charging order continues to be charged, and the risk-free mark of the enterprise setting information is verified according to a preset verification period; the preset verification period is determined according to the enterprise information; the charging process of continuing to execute the charging order does not require the balance verification of the enterprise account; Or, if there is a risk mark in the enterprise setting information, and the risk mark is the risky mark, the balance of the enterprise account is checked, and the risky mark of the enterprise setting information is checked according to the preset verification period.

2. The method according to claim 1, characterized in that The enterprise information also includes: the amount of funds used and the total amount of unpaid orders; the risk mark also includes a no-risk mark; the risk mark of the enterprise setting information is determined based on the enterprise information, including: In the case where the sum of the capital usage amount and the total amount of the unpaid orders is less than or equal to the account balance of a preset multiple, determining that the enterprise setting information is the risk-free mark; In the case where the sum of the fund usage amount and the total amount of the unpaid orders is greater than a preset multiple of the account balance, the enterprise setting information is determined to be the risky mark.

3. The method according to claim 2, characterized in that The enterprise information also includes: the scale information of the enterprise; the process of determining the amount of funds used includes: Obtaining historical order information of the enterprise account in a preset time period; the historical order information includes: historical order quantity and historical order amount; Determine the estimated capital flow rate of the enterprise account in the preset time period according to the historical order quantity and the historical order amount; According to the estimated fund flow rate, the fund usage of the enterprise account at a preset level is determined; the preset level corresponds to the scale information of the enterprise.

4. The method according to claim 3, characterized in that: The preset levels include: a first level and a second level; the duration corresponding to the first level is shorter than the duration corresponding to the second level; the method further includes: Calculate the historical maximum capital flow rate of the enterprise account according to the historical order quantity and the historical order information; If the estimated capital flow rate is higher than the historical highest capital flow rate, adjusting the preset level corresponding to the enterprise account to the first level; If the estimated funds flow rate is not higher than the historical highest funds flow rate, the preset level corresponding to the corporate account is adjusted to the second level.

5. The method according to claim 2, characterized in that: The method further comprises: When the account balance is less than or equal to a preset minimum amount, the enterprise setting information is determined to be the risky mark, and a reminder message is generated; the reminder message is used to prompt that the account balance of the enterprise account is insufficient.

6. The method according to claim 2, characterized in that The enterprise information also includes the number of historical daily orders and the number of unpaid orders; the method also includes: When the number of unpaid orders exceeds a preset number of unpaid orders, the enterprise setting information is determined to be the risky mark; the preset number of unpaid orders is determined based on the historical daily order number.

7. The method according to claim 1, characterized in that Using the risk-free mark and the risky mark as target risk marks; Verify the target risk markers of the enterprise setting information according to the preset period, including: Obtaining a usage period of the target risk marker; Determining a preset period corresponding to a preset level of the enterprise account according to the scale information of the enterprise in the enterprise information; When the use period of the target risk mark is the same as the preset verification period, the verification risk mark of the enterprise setting information at the current moment is determined according to the enterprise information.

8. The method according to claim 7, characterized in that The method further comprises: When the verification time point of the preset verification period is reached, the number of all the target risk marks newly added at the verification time point is obtained; When the quantity of all the target risk markers does not belong to the preset quantity interval, abnormal information is generated; the abnormal information is used to indicate that the balance check is abnormal.

9. A balance verification device, characterized in that: The device comprises: An acquisition module, configured to acquire enterprise setting information of the enterprise account based on a charging order placed under the enterprise account; the enterprise setting information is used to indicate whether there is a risk mark on the enterprise information of the enterprise account; A judgment module, used to judge whether the enterprise setting information has a risk mark according to a preset detection cycle; the risk mark includes a no-risk mark and a risk mark; A verification module, configured to verify the balance of the enterprise account if the enterprise setting information does not contain the risk mark, and determine the risk mark of the enterprise setting information according to the enterprise information; A charging module, for continuing to charge the charging order if there is a risk mark in the enterprise setting information and the risk mark is the risk-free mark, and verifying the risk-free mark of the enterprise setting information according to a preset verification period; the preset verification period is determined according to the enterprise information; the charging process of continuing to charge the charging order does not require a balance check on the enterprise account; The verification module is also used to verify the balance of the enterprise account if there is a risk mark in the enterprise setting information and the risk mark is the risky mark, and verify the risky mark of the enterprise setting information according to the preset verification period.

10. A balance verification device, characterized in that: The balance verification device comprises a processor and a memory, wherein the memory stores machine executable instructions that can be executed by the processor, and the processor executes the machine executable instructions to implement the balance verification method according to any one of claims 1 to 8.

11. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores machine-executable instructions. When the computer-executable instructions are called and executed by a processor, the computer-executable instructions prompt the processor to implement the balance verification method according to any one of claims 1 to 8.

12. A computer program product comprising a computer program / instructions, characterized in that When the computer program product / instructions are executed by a processor, the steps of the balance verification method according to any one of claims 1 to 8 are implemented.

Images