Wind control strategy configuration process and system used in accounting information system

Abstract

The invention relates to a wind control strategy configuration process used in an accounting information system, which comprises the following steps: (1) the background personnel maintain the information of the commodity itself, the advanced information, the additional information and the market information; (2) a transaction request of a user is responded, and a process of risk control of the sales system is started; (3) the transaction risk type is judged, and the transaction amount threshold m is set; and the risk control process is selected to be a strong consistency risk control process or a high concurrency risk control process.

Description

technical field [0001] The invention belongs to the field of information technology, in particular to the field of risk strategy configuration and control under an accounting information system. Background technique [0002] The current query function in the sales accounting information system usually adopts a single-table data structure design. By setting simple query conditions such as product name and product number, the relevant merchant sales information is queried from the merchant sales information database, and through the front-end interface. displayed to the user. There are often some problems in the traditional sales information query. 1. The display form of sales information is single, especially for the lack of display of the commodity category level and its superior-subordinate relationship. 2. The display dimension of product sales information is simple. Generally, it can only display some traditional information of the product itself (such as product name, p...

AI Technical Summary

Problems solved by technology

Traditional sales information query often has the following problems: 1. The display form of sales information is single, especially for the lack of display of commodity category levels and their superior-subordinate relationships

2. The display dimension of product sales information is simple. Generally, it can only display some traditional information of the product itself (such as product name, price, etc.). It cannot display and maintain multi-dimensional information from channels, content providers, applications, etc., and is not suitable for the current Internet. development requirements

[0003] In addition, after adopting multi-dimensional information display, a large number of customer flows have been brought in, and a new problem has arisen at the same time: the volume of customer transactions has increased significantly, especially the increase in concurrent transactions

Such a processing method is beneficial to effectively prevent and control transaction risks. However, with the increasing variety of online transaction scenarios, the number of online sales transactions has increased sharply, and users’ requirements for customer experience have increased. Traditional solutions will bring Here are the following questions: 1. Because the risk inspection needs to calculate and store relevant data, it usually takes at least 100ms or more, which prolongs the overall processing time of the entire transaction and affects the customer's transaction experience.

2. Due to the significant increase in offline transaction volume, the concurrent requests for back-end sales information have increased exponentially. The old database-based risk control model is difficult to undertake data calculation under such a large concurrent volume, and dirty data problems may occur , leading to failure of risk control

When the second transaction occurs, the previous transaction amount is 500 plus the current transaction amount, and the daily cumulative transaction amount is 500+600=1100, which will trigger risk control due to exceeding the daily cumulative transaction limit

When the second transaction occurs, since the calculation of the previous risk limit has not been completed, the cumulative value of the daily transaction at this time is still calculated from 0, and the cumulative value of the transaction at this time is 0+600=600, which is also less than the daily cumulative limit of 1000 , the second transaction will proceed normally without triggering the risk control, which leads to the failure of the risk control strategy

3. Due to the limitations of the database, the traditional database-based risk control cannot dynamically expand the cluster

There is no hierarchical relationship between risk strategies, no cascading relationship, and it cannot meet the needs of diversified risk control strategy configuration

5. If the security setting is too high, it will affect the convenience of transactions, but if the setting is too low, there is a huge risk

Images