CN112529692A - Merchant risk auditing method, device and equipment and readable storage medium - Google Patents
Merchant risk auditing method, device and equipment and readable storage medium Download PDFInfo
- Publication number
- CN112529692A CN112529692A CN202011493469.5A CN202011493469A CN112529692A CN 112529692 A CN112529692 A CN 112529692A CN 202011493469 A CN202011493469 A CN 202011493469A CN 112529692 A CN112529692 A CN 112529692A
- Authority
- CN
- China
- Prior art keywords
- risk
- merchant
- preset
- key information
- information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 65
- 230000008569 process Effects 0.000 claims abstract description 23
- 238000012502 risk assessment Methods 0.000 claims description 45
- 238000012550 audit Methods 0.000 claims description 22
- 238000012216 screening Methods 0.000 claims description 18
- 230000014509 gene expression Effects 0.000 claims description 11
- 238000012795 verification Methods 0.000 claims description 9
- 238000004590 computer program Methods 0.000 claims description 7
- 238000000605 extraction Methods 0.000 claims description 3
- 238000012545 processing Methods 0.000 description 8
- 230000008901 benefit Effects 0.000 description 4
- 238000011161 development Methods 0.000 description 3
- 238000010586 diagram Methods 0.000 description 3
- 238000007726 management method Methods 0.000 description 3
- 238000012546 transfer Methods 0.000 description 3
- 230000006399 behavior Effects 0.000 description 2
- 230000008878 coupling Effects 0.000 description 2
- 238000010168 coupling process Methods 0.000 description 2
- 238000005859 coupling reaction Methods 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 238000003032 molecular docking Methods 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 238000004458 analytical method Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/03—Credit; Loans; Processing thereof
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/103—Workflow collaboration or project management
Landscapes
- Business, Economics & Management (AREA)
- Engineering & Computer Science (AREA)
- Strategic Management (AREA)
- Human Resources & Organizations (AREA)
- General Business, Economics & Management (AREA)
- Accounting & Taxation (AREA)
- Marketing (AREA)
- Entrepreneurship & Innovation (AREA)
- Economics (AREA)
- Physics & Mathematics (AREA)
- Finance (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Technology Law (AREA)
- Data Mining & Analysis (AREA)
- Development Economics (AREA)
- Operations Research (AREA)
- Quality & Reliability (AREA)
- Tourism & Hospitality (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention discloses a method, a device, equipment and a storage medium for verifying the risk of a merchant, wherein the method comprises the following steps: receiving a merchant risk auditing request submitted by a terminal, wherein the merchant risk auditing request comprises merchant information; extracting preset key information in the merchant information; calling a preset interface for verifying the authenticity of preset key information, and verifying the authenticity of the extracted preset key information; if the preset key information is real, judging whether the preset key information meets a preset circulation condition; and if the preset circulation condition is met, auditing the preset key information based on a preset auditing rule to determine the risk condition of the merchant. The method and the system can reduce manpower and error rate in the merchant risk auditing process, thereby improving auditing efficiency and accuracy and realizing more effective management and control on the merchant risk.
Description
Technical Field
The invention relates to the technical field of computers, in particular to a method, a device and equipment for verifying merchant risk and a readable storage medium.
Background
In the existing financial industry, taking a bank as an example, when a merchant needs to be expanded due to some business requirements, for example, when more merchants need to be expanded to use a POS machine or a two-dimensional code of a bank to collect money, merchant data (such as registration information, activated financial services, an existing money collection mode, and other information) needs to be collected and checked to determine potential risks of the merchant, and transaction behaviors of the merchant using the POS machine or the two-dimensional code of the bank are controlled.
The existing auditing method for the potential risk of the merchant mainly includes the steps of acquiring merchant information on line, logging in each external related system (such as a website for inquiring registration information) by business personnel to collect merchant information, and auditing the collected merchant information based on a preset auditing logic to determine the potential risk of the merchant. In the above manner, the whole process requires a large labor cost, low efficiency and a high error rate. In addition, the audit logic usually needs to be implemented by developers in a background hard coding manner, and under the condition that the audit logic needs to be adjusted or added, the developers need to modify or rewrite the codes to generate a new version. In addition, the auditing logic is easily exposed in the code, so that sensitive information of certain businesses is easily exposed, and certain safety hazards also exist.
Disclosure of Invention
The invention aims to provide a merchant risk auditing method, a merchant risk auditing device, merchant risk auditing equipment and a storage medium, which can reduce the labor cost and the error rate of a merchant risk auditing process, thereby improving the auditing efficiency and the accuracy rate and realizing more effective management and control on merchant risks.
According to an aspect of the present invention, there is provided a merchant risk auditing method, including:
receiving a merchant risk auditing request submitted by a terminal, wherein the merchant risk auditing request comprises merchant information;
extracting preset key information in the merchant information;
calling a preset interface for verifying the authenticity of preset key information, and verifying the authenticity of the extracted preset key information;
if the preset key information is real, judging whether the preset key information meets a preset circulation condition;
and if the preset circulation condition is met, auditing the preset key information based on a preset auditing rule to determine the risk condition of the merchant.
Optionally, the method further includes:
if the preset circulation condition is not met, the process is terminated and the information of stopping the audit is returned.
Optionally, the method further includes:
receiving a new request of an interface which is submitted by a terminal and related to a service requirement;
and establishing the connection of the interface related to the service requirement according to the new request so as to realize the calling of the interface after receiving the request related to the calling of the interface.
Optionally, the method further includes:
receiving a risk analysis rule which is submitted by a terminal and set according to the service requirement, wherein the risk analysis rule comprises screening condition information and corresponding risk result information;
after receiving a risk analysis request for data corresponding to an interface related to the business requirement, calling the interface related to the business requirement;
and screening the called data based on the screening conditions to obtain a corresponding risk result.
Optionally, the method further includes:
providing an operation interface for inputting risk analysis rules;
based on this, the risk analysis rule set according to the business requirement submitted by the receiving terminal includes:
and receiving a risk analysis rule written in a pseudo code mode through the operation interface.
Optionally, the method further includes: and storing the risk condition of the merchant in a preset database in real time or at regular time.
Optionally, the expression form of the risk condition of the merchant includes a score, an amount limit, a preset risk level and/or a preset merchant level.
In order to achieve the above object, the present invention further provides a merchant risk auditing apparatus, where the apparatus includes:
the request receiving module is used for receiving a merchant risk auditing request submitted by a terminal, wherein the merchant risk auditing request comprises merchant information;
the information extraction module is used for extracting preset key information in the merchant information;
the information verification module is used for calling a preset interface for verifying the authenticity of preset key information and verifying the authenticity of the extracted preset key information;
the judging module is used for judging whether the preset key information meets preset circulation conditions or not under the condition that the preset key information is real;
and the risk determining module is used for auditing the preset key information based on a preset auditing rule to determine the risk condition of the merchant under the condition of meeting the preset circulation condition.
In order to achieve the above object, the present invention further provides a computer device, which specifically includes: a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the steps of the above-described merchant risk auditing method when executing the computer program.
In order to achieve the above object, the present invention further provides a computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, implements the steps of the above-described merchant risk auditing method.
The method, the device, the equipment and the storage medium for verifying the risk of the merchant can extract preset key information from a received merchant risk verification request which is submitted by a terminal and comprises merchant information, then directly call a preset interface which is butted in advance and used for verifying the authenticity of the preset key information, verify the authenticity of the extracted preset key information, continuously judge whether the preset key information meets preset circulation conditions or not under the condition that the preset key information is real, and verify the preset key information based on preset verification rules to determine the risk condition of the merchant under the condition that the preset key information meets the preset circulation conditions. Compared with the existing scheme that the merchant risk auditing process mainly depends on manual operation of business personnel, the merchant risk auditing method can audit the merchant risk more automatically by means of pre-docking with related interfaces, pre-setting auditing rules and the like, so that the manpower cost and the auditing error rate of the merchant risk auditing process can be reduced, the auditing efficiency and accuracy are improved, and the merchant risk is more effectively controlled.
Drawings
Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the invention. Also, like reference numerals are used to refer to like parts throughout the drawings. In the drawings:
fig. 1 is an alternative flow diagram of a merchant risk auditing method according to an embodiment;
fig. 2 is a schematic diagram of an optional component structure of the merchant risk auditing apparatus according to the second embodiment;
fig. 3 is a schematic diagram of an alternative hardware architecture of the computer device according to the third embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Example one
The embodiment of the invention provides a merchant risk auditing method, which specifically comprises the following steps of:
step S101: receiving a merchant risk auditing request submitted by a terminal, wherein the merchant risk auditing request comprises merchant information.
In this embodiment, the present scheme may be applied to an application program (APP) related to verifying a merchant risk in a financial system, such as an information approval system for a special business agreement for receipt used by an existing secure bank, where the APP may be installed in a terminal used by a business person related to business expansion in a row. Under the condition that the risk of the merchant needs to be checked, merchant information which is provided by the merchant and is relevant to the risk of the merchant is input through the APP, a merchant risk checking request is submitted and sent, and the like, and a server corresponding to the APP can receive the relevant information, the request and the like and can correspondingly process the received relevant information, the request and the like. The merchant mentioned in the scheme may be, for example, a mall, a supermarket, a flower shop, a pet shop, and the like, and the terminal may be a terminal used by a business person related to business development in a bank.
In a specific implementation, the APP may provide an information input interface for inputting merchant information, where the information input interface may include an input box and a "submit" button for sending an information submission request, and for example, the merchant submits the merchant information related to the information input interface to business personnel, and the business personnel inputs the merchant information into the information input interface and triggers the "submit" button to submit the merchant information. In this embodiment, the merchant information may include information related to the merchant registration information (such as a merchant name, an address, an affiliated industry, registered funds, an operating range, a legal person, a shareholder, a staff number, and the like), and may further include information about a transaction type of the merchant, a settlement account, a collection mode, an opened financial service (such as an internal card, an external card, and the like), whether a loan exists, a loan installment age, whether a credit card payment is not timely paid, whether a loan payment is not timely paid, whether the loan payment is present in a blacklist of a unionpay association, an operating site area of the merchant, whether the operating site is leased or owned, and the like.
After the merchant information is obtained, authenticity judgment can be carried out on the merchant information in subsequent steps so as to further understand the merchant situation, and then potential risk verification can be carried out on the merchant information based on the actual merchant information so as to obtain a relatively objective and accurate merchant risk situation.
Step S102: and extracting preset key information in the merchant information.
In this embodiment, the key information may be set in advance according to actual requirements, for example, in the case that the scale of the merchant tends to be verified, the preset key information may be registered funds, the area of the business site of the merchant, the number of employees of the merchant, and the like; for example, in the case that the comparison tends to verify the credit of the merchant, the preset key information may be the settlement account, the loan installment age, whether the repayment of the credit card is not in time, whether the repayment of the loan is in the blacklist of the Unionpay association, or the like; for example, in the case of verifying the scale and credit of the merchant, the preset key information may be registered funds, the area of the operating site of the merchant, the number of employees of the merchant, a settlement account, the loan installment age, whether the credit card is not paid in time, whether the loan is not paid in time, whether the credit card is on a blacklist of the Unionpay association, or the like; of course, in the case that the merchant tends to be more comprehensively known, more information items may be selected from the information items of the merchant information as the preset key information. That is, the preset key information can select an appropriate information item from the information items of the customer information according to the business requirements, so that the preset key information can be more flexibly and preferentially applied to the operation of verifying the authenticity of the customer information in the subsequent step, and the verification process is more accurate and efficient.
Step S103: and calling a preset interface for verifying the authenticity of the preset key information, and verifying the authenticity of the extracted preset key information.
In this embodiment, the connection may be performed in advance with each relevant interface (for example, a website for querying enterprise registration information, a website for querying a blacklist of a unionpay association, a banking system for querying a credit record, a banking system for querying a settlement account, a collection account, and a collection mode of a merchant, and the like), so that, when data in the relevant interface is needed, the relevant interface is directly called, and operations such as querying and collecting data in the interface are performed more quickly and efficiently.
For example, when the extracted preset key information is the registered fund, the operating site area of the merchant and the number of the staff members of the merchant, the website for inquiring the enterprise registration information can be called to verify the registered fund, the operating site area of the merchant and the number of the staff members of the merchant in the preset key information so as to determine whether the registered fund, the operating site area of the merchant and the number of the staff members of the merchant provided by the merchant are real or not; for example, when the extracted preset key information is a settlement account, the loan installment age, whether a credit card is not timely paid, whether a loan is not timely paid, and whether the loan is not timely paid, or whether the loan is in a blacklist of the unionpay association, a relevant system or website for inquiring account information, loan information, unionpay association, and the like can be called to verify the content of the preset key information so as to determine that the content of the preset key information provided by the merchant is real. If the preset key information contained in the merchant information provided by the merchant is determined to be not true, the process can be directly terminated and the information for terminating the audit can be returned, for example, a dialog box including 'terminating audit' can be provided to inform business personnel that the preset key information is not true and the process is not continued any more. That is, on one hand, the trend of the flow can be determined according to the verification result of the preset key information, so as to improve the processing efficiency of the system; on the other hand, compared with the existing mode that business personnel need to log in each relevant website (such as a website relevant to inquiring enterprise registration information, a certain bank system and the like) to collect relevant information so as to determine whether the preset key information contained in the merchant information is true or not, the processing efficiency and accuracy of the system can be improved.
Step S104: and if the preset key information is real, judging whether the preset key information meets a preset circulation condition.
In this embodiment, the circulation condition may be set in advance according to the preset key information, for example, if the preset key information is the registered fund, the preset circulation condition may be set to be not lower than a certain value (for example, 10 ten thousand yuan renowned folk money, etc., that is, the registered fund of the merchant is not lower than 10 ten thousand yuan renowned folk money, the preset circulation condition is satisfied, otherwise, the preset circulation condition is not satisfied); for example, if the preset key information is that the preset key information exists in the blacklist of the union pay association, the preset circulation condition can be set to be no (that is, the merchant does not exist in the blacklist of the union pay association, the preset circulation condition is met, otherwise, the merchant does not exist in the blacklist of the union pay association, and the preset circulation condition is not met); for example, if the preset key information indicates whether loan repayment is not in time, the preset transfer condition may be set to no (that is, if the loan repayment is not in time, the preset transfer condition is satisfied, otherwise, the preset transfer condition is not satisfied) and the like. And if the judgment result is that the preset key information does not meet the preset circulation condition, directly terminating the process and returning the information for terminating the audit, for example, providing a dialog box including 'terminating the audit' to inform service personnel that the preset key information does not meet the preset circulation condition and the process is not continued any more. That is to say, the trend of the flow can be determined according to whether the preset key information meets the preset circulation condition, and the flow is terminated in time under the condition that the preset key information does not meet the preset circulation condition, so that the processing efficiency of the system can be improved.
Step S105: and if the preset circulation condition is met, auditing the preset key information based on a preset auditing rule to determine the risk condition of the merchant.
In this embodiment, the audit rule may be set in advance according to an actual requirement, for example, the audit rule may be set based on preset key information (the expression form of the risk condition of the merchant is high risk, general risk, and low risk is taken as an example for explanation), and for example, the preset audit rule may include: registered funds below 5 million (including 5 million) are high risk, between 5 million and 15 million are general risk, and above 15 million (not including 15 million) are low risk; the number of staff is lower than 10 (including 10) for high risk, between 10 and 30 for general risk, and higher than 30 (not including 30) for low risk; the condition that the payment of the credit card is not in time is low risk, the condition that the payment of the credit card is not in time within two times (including two times) is general risk, and the condition that the payment of the credit card is not in time more than two times is high risk; the condition that loan repayment is not timely is low risk, the condition that loan repayment is not timely within two times (including two times) is general risk, and the condition that loan repayment is not timely more than two times is high risk; the low risk is not present in the blacklist of the Unionpay Association, and the high risk is present in the blacklist of the Unionpay Association; businesses operating below 50 square meters (including 50 square meters) are at high risk, between 50 and 100 square meters are at general risk, above 100 square meters (not including 100 square meters) are at low risk, and so on.
Wherein the manifestation of the risk condition of the merchant may include a score (e.g., a score from 1 to 3, where 1 is low risk, 2 is general risk, and 3 is high risk); amount (e.g., the amount of money for limiting card swiping each day may be used, a lower risk client may set a relatively higher amount (e.g., 5 ten thousand), a higher risk client may set a relatively lower amount (e.g., 1 ten thousand), etc.); preset risk levels (e.g., low risk, general risk, high risk, etc.); and presetting a merchant level (such as a first-level merchant, a second-level merchant and a third-level merchant with low risk to high risk). In practical application, at least one of the above expressions can be selected according to business requirements to express the risk condition of the merchant.
For example, in the case that the preset key information is the registered fund, the area of the business site of the merchant, and the number of employees of the merchant, the preset key information included in the merchant information provided by the merchant is verified to be true, where the registered fund is 100 ten thousand renminbi, the area of the business site of the merchant is 100 square meters, the number of employees of the merchant is 35, and the preset circulation condition is satisfied (for example, the preset circulation condition is that the registered fund is not less than 10 ten thousand renminbi, the area of the business site of the merchant is not less than 50 square meters, the preset circulation condition is satisfied, the number of employees of the merchant is not less than 10, and the like), the preset key information may be audited based on the preset circulation rule to determine the risk condition of the merchant.
For example, in the preset audit rules, the registered fund is high risk when the registered fund is less than 5 ten thousand (including 5 ten thousand), general risk when the registered fund is between 5 ten thousand and 15 ten thousand, and low risk when the registered fund is more than 15 ten thousand (without 15 ten thousand); the number of staff is lower than 10 (including 10) for high risk, between 10 and 30 for general risk, and higher than 30 (not including 30) for low risk; the business area of the merchant is lower than 50 square meters (including 50 square meters) to be high risk, between 50 and 100 square meters to be general risk, and higher than 100 square meters (not including 100 square meters) to be low risk, and it can be known through comparison that each item in the preset key information conforms to a low risk item in the preset auditing rule, and has a relatively obvious advantage, so that the risk condition of the merchant can be determined as low risk or primary merchant (other expression modes of risk conditions can also be selected according to requirements).
For example, in the case that the preset key information is the loan installment year, whether the repayment of the credit card is not in time exists, whether the repayment of the loan is in time exists in the blacklist of the union of bank, the preset key information included in the merchant information provided by the merchant through verification is true, wherein the loan installment year is 15 years, the repayment of the credit card is not in time once, the repayment of the loan is not in time, the loan repayment is not in time, the preset circulation condition is satisfied when the loan installment year is not more than 20 years, the preset circulation condition is satisfied when the repayment of the credit card is not in time within two times (including two times), the preset circulation condition is satisfied when the repayment of the loan is not in time, the preset circulation condition is satisfied when the loan repayment is not in time, the blacklist of the union of bank is not present, and the like), the preset key information is audited based on preset audit rules to determine the risk condition of the merchant.
For example, in the preset auditing rule, the loan staging age is low risk when the loan staging age is less than 5 years (including 5 years), general risk when the loan staging age is 5-10 years, and high risk when the loan staging age is more than 10 years (not including 10 years); the condition that the payment of the credit card is not in time is low risk, the condition that the payment of the credit card is not in time within two times (including two times) is general risk, and the condition that the payment of the credit card is not in time more than two times is high risk; the condition that loan repayment is not timely is low risk, the condition that loan repayment is not timely within two times (including two times) is general risk, and the condition that loan repayment is not timely more than two times is high risk; the business risk condition is determined as a general risk business or a score of "2" (or other expression modes of other risk conditions can be selected according to requirements) by combining the comparison results of the four items.
Therefore, equivalently, the merchant is labeled according to the risk condition of the merchant, the merchant risk condition can be known more visually based on the merchant label, and the transaction behavior (such as daily card swiping amount) of the merchant can be controlled according to the merchant label, so that the merchant risk is controlled more effectively.
In addition, in this embodiment, after determining the risk condition of the merchant, the risk condition of the merchant may be stored in a preset database in real time or at regular time according to actual needs. Therefore, compared with the mode that the risk conditions of the merchants are dispersedly managed by business personnel (such as being stored in computers used by the business personnel, etc.), the method can more conveniently carry out centralized management on the risk conditions of all the merchants, and is more convenient to analyze, count, backtrack, etc. the risk conditions of all the merchants, thereby more effectively managing and controlling the risk of the merchants.
In specific implementation, the method may further include receiving a new request of an interface related to the service requirement, which is submitted by the terminal, and establishing a connection with the interface related to the service requirement according to the new request, so as to implement the call of the interface after receiving the request related to the call of the interface.
Specifically, an operation interface (in this embodiment, may be referred to as a first operation interface) for receiving a new addition request of the interface related to the service requirement may be provided, the first operation interface may include, for example, an input box for inputting interface description information (the input box may be referred to as a first input box, where the interface description information is, for example, a website name or a website link, etc.), an "add" button for issuing an interface corresponding to the interface information input in the first input box, when the service person inputs a website link in the first input box and triggers the "add" button, namely, a new request of a relevant interface is sent out, the server corresponding to the APP can receive the new request, and corresponding processing can be carried out on the new request, namely, the connection with a related interface (such as a website link) is established according to the new request.
Therefore, service personnel can flexibly submit a request of a newly added calling interface according to service requirements so as to realize more convenient and efficient application of data called from the interface, and the newly added interface can be regarded as an independent interface and is not in conflict with other services or functions, so that the flexibility and the expandability of the system can be improved. Compared with the existing mode that developers need to generate new versions in a hard coding mode under the conditions of system function adjustment or addition and the like, on one hand, the processing efficiency can be improved, and on the other hand, the code coupling degree and the development and maintenance cost can be reduced.
Further, after the interface related to the service requirement is connected according to the new request, a risk analysis rule set according to the service requirement and submitted by a terminal may be received, where the risk analysis rule may include screening condition information and corresponding risk result information. Next, after receiving a risk analysis request for data corresponding to the interface related to the business demand, the interface related to the business demand may be invoked, and the invoked data may be screened based on the screening condition to obtain a corresponding risk result.
In particular implementation, an operation interface (in this embodiment, may be referred to as a second operation interface) for inputting risk analysis rules may be provided, an input box for inputting the risk analysis rule (which may be referred to as a second input box) and a "submit" button for sending a submit request for the risk analysis rule input in the second input box may be included in the second operation interface, wherein, the risk analysis rule can be written in a pseudo code mode (of course, other writing modes can be set according to actual requirements), when the business personnel writes the risk analysis rule in the second input box through the pseudo code, the business personnel triggers a 'submit' button, namely submitting the risk analysis rule, the server corresponding to the APP can receive the risk analysis rule submitted by the terminal, and the risk analysis rule can be saved so as to apply the risk analysis rule to process data when needed. Therefore, compared with the mode that developers need to generate new versions through hard coding under the conditions of adjustment or addition of the existing audit logic, on one hand, the processing efficiency can be improved, on the other hand, the code coupling degree and the development and maintenance cost can be reduced, and in addition, because the audit logic is not exposed in the codes, the confidentiality of the audit logic can be improved, and the safety of the system can be improved.
In this embodiment, in the second operation interface, a "risk analysis" button for sending a risk analysis request may be further included, and when a business person triggers the "risk analysis" button, that is, the business person submits a risk analysis request for data corresponding to the interface related to the business demand, the server corresponding to the APP may receive the risk analysis request submitted by the terminal, and may process the risk analysis request. Specifically, an interface related to the service requirement may be called first to obtain data corresponding to the interface related to the service requirement, and in this embodiment, the obtained data is generally data such as merchant information related to the service requirement, and is mainly used to perform risk analysis on the obtained merchant information related to the service requirement.
In a specific implementation, the screening condition may be set according to actual needs based on preset key information, for example, the screening condition may be set to be a merchant existing in a blacklist of the union of bank, a merchant with registered funds between 5 to 15 ten thousand, a merchant without a situation that loan repayment is not in time and a situation that credit card repayment is not in time, and then a corresponding risk result may be set according to the screening condition.
The risk result may also be set with reference to the risk condition of the merchant, for example, the expression form of the risk result may include a score (for example, a score is given from 1 to 3, where 1 is a low risk, 2 is a general risk, and 3 is a high risk), an amount (for example, an amount that a card is swiped for each day may be limited, for example, a lower-risk customer may set a relatively higher amount, a higher-risk customer may set a relatively lower amount, and the like), a preset risk level (for example, a low risk, a general risk, a high risk, and the like), and a preset merchant level (for example, a first-level merchant, a second-level merchant, a third-level merchant, and the like, whose risk is from. In practical application, at least one of the above expressions can be selected according to business requirements to express risk results.
In this embodiment, for example, the screening condition is that the merchant exists in the blacklist of the union pay association, and the corresponding risk result is a high risk (taking this risk expression as an example for explanation, it is needless to say that other risk expression may be selected according to the requirement); the screening condition is that merchants with registered funds of 5 to 15 ten thousand have intermediate risks; the screening condition is that no commercial tenant with untimely loan repayment and untimely credit card repayment exists, and the corresponding risk result is low risk.
Therefore, the risk analysis rule can be set more flexibly according to the business requirement, and the risk analysis can be carried out on the merchants related to the business requirement based on the risk rule, so that the risk analysis efficiency can be improved, and the risk result which is more targeted and can meet the business requirement can be obtained, so that the risk result can be more accurately applied to the related business.
In addition, after the risk result of the merchant is obtained, the risk result can be stored in a preset database in real time or at regular time according to actual needs. Therefore, centralized management can be more conveniently carried out on the risk results of the commercial tenants related to the business requirements, analysis, statistics, backtracking and the like can be more conveniently carried out on the risk results of the commercial tenants, and therefore the risk of the commercial tenants can be more effectively controlled.
The merchant risk auditing method provided by this embodiment may extract preset key information from a merchant risk auditing request including merchant information submitted by a received terminal, then directly invoke a preset interface that is docked in advance and used for verifying the authenticity of the preset key information, verify the authenticity of the extracted preset key information, continue to judge whether the preset key information satisfies preset circulation conditions when the preset key information is authentic, and audit the preset key information based on preset auditing rules to determine the risk condition of the merchant when the preset key information satisfies the preset circulation conditions. Compared with the existing scheme that the merchant risk auditing process mainly depends on manual operation of business personnel, the merchant risk auditing method can audit the merchant risk more automatically by means of pre-docking with related interfaces, pre-setting auditing rules and the like, so that the manpower cost and the auditing error rate of the merchant risk auditing process can be reduced, the auditing efficiency and accuracy are improved, and the merchant risk is more effectively controlled.
Example two
The embodiment of the invention provides a merchant risk analysis device, which specifically comprises the following components as shown in fig. 2:
a request receiving module 201, configured to receive a merchant risk auditing request submitted by a terminal, where the merchant risk auditing request includes merchant information;
an information extraction module 202, configured to extract preset key information in the merchant information;
the information verification module 203 is used for calling a preset interface for verifying the authenticity of preset key information and verifying the authenticity of the extracted preset key information;
a judging module 204, configured to judge whether the preset key information meets a preset circulation condition when the preset key information is true;
and the risk determining module 205 is configured to, when the preset circulation condition is met, audit the preset key information based on a preset audit rule to determine a risk condition of the merchant.
Specifically, the expression form of the risk condition of the merchant includes a score, an amount limit, a preset risk level and/or a preset merchant level.
Further, the risk determining module 205 may be further configured to terminate the flow and return to the information of terminating the audit when the preset circulation condition is not satisfied.
In a specific implementation, the apparatus may further include:
the interface newly-increased request receiving module is used for receiving a newly-increased request of an interface which is submitted by a terminal and is related to the service requirement;
and the interface connection module is used for establishing the connection of the interface related to the service requirement according to the new request so as to realize the calling of the interface after receiving the request related to the calling of the interface.
Further, the device may further include:
the risk analysis rule receiving module is used for receiving a risk analysis rule which is submitted by a terminal and set according to the business requirement, wherein the risk analysis rule comprises screening condition information and corresponding risk result information;
the risk analysis request receiving module is used for calling the interface related to the business requirement after receiving a risk analysis request for the data corresponding to the interface related to the business requirement;
and the screening module can be used for screening the called data based on the screening conditions to obtain a corresponding risk result.
In a specific implementation, the apparatus may further include:
the operation interface providing module can be used for providing an operation interface for inputting risk analysis rules;
based on this, the risk analysis rule receiving module may be specifically configured to: and receiving a risk analysis rule written in a pseudo code mode through the operation interface.
Further, the device may further include:
and the storage module can be used for storing the risk condition of the merchant in a preset database in real time or at regular time.
EXAMPLE III
The embodiment also provides a computer device, such as a smart phone, a tablet computer, a notebook computer, a desktop computer, a rack server, a blade server, a tower server or a rack server (including an independent server or a server cluster composed of a plurality of servers) capable of executing programs, and the like. As shown in fig. 3, the computer device 30 of the present embodiment includes at least but is not limited to: a memory 301, a processor 302 communicatively coupled to each other via a system bus. It is noted that FIG. 3 only shows the computer device 30 having components 301 and 302, but it is understood that not all of the shown components are required and that more or fewer components may be implemented instead.
In this embodiment, the memory 301 (i.e., the readable storage medium) includes a flash memory, a hard disk, a multimedia card, a card-type memory (e.g., SD or DX memory, etc.), a Random Access Memory (RAM), a Static Random Access Memory (SRAM), a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), a programmable read-only memory (PROM), a magnetic memory, a magnetic disk, an optical disk, and the like. In some embodiments, the storage 301 may be an internal storage unit of the computer device 30, such as a hard disk or a memory of the computer device 30. In other embodiments, the memory 301 may also be an external storage device of the computer device 30, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), or the like, provided on the computer device 30. Of course, the memory 301 may also include both internal and external storage devices for the computer device 30. In the present embodiment, the memory 301 is generally used for storing an operating system and various types of application software installed in the computer device 30. In addition, the memory 301 may also be used to temporarily store various types of data that have been output or are to be output.
Processor 302 may be a Central Processing Unit (CPU), controller, microcontroller, microprocessor, or other data Processing chip in some embodiments. The processor 302 generally serves to control the overall operation of the computer device 30.
Specifically, in this embodiment, the processor 302 is configured to execute a program of the merchant risk analysis method stored in the processor 302, and when executed, the program of the merchant risk analysis method implements the following steps:
receiving a merchant risk auditing request submitted by a terminal, wherein the merchant risk auditing request comprises merchant information;
extracting preset key information in the merchant information;
calling a preset interface for verifying the authenticity of preset key information, and verifying the authenticity of the extracted preset key information;
if the preset key information is real, judging whether the preset key information meets a preset circulation condition;
and if the preset circulation condition is met, auditing the preset key information based on a preset auditing rule to determine the risk condition of the merchant.
The specific embodiment process of the above method steps can be referred to in the first embodiment, and the detailed description of this embodiment is not repeated here.
Example four
The present embodiments also provide a computer readable storage medium, such as a flash memory, a hard disk, a multimedia card, a card type memory (e.g., SD or DX memory, etc.), a Random Access Memory (RAM), a Static Random Access Memory (SRAM), a Read Only Memory (ROM), an Electrically Erasable Programmable Read Only Memory (EEPROM), a Programmable Read Only Memory (PROM), a magnetic memory, a magnetic disk, an optical disk, a server, an App application mall, etc., having stored thereon a computer program that when executed by a processor implements the method steps of:
receiving a merchant risk auditing request submitted by a terminal, wherein the merchant risk auditing request comprises merchant information;
extracting preset key information in the merchant information;
calling a preset interface for verifying the authenticity of preset key information, and verifying the authenticity of the extracted preset key information;
if the preset key information is real, judging whether the preset key information meets a preset circulation condition;
and if the preset circulation condition is met, auditing the preset key information based on a preset auditing rule to determine the risk condition of the merchant.
The specific embodiment process of the above method steps can be referred to in the first embodiment, and the detailed description of this embodiment is not repeated here.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner.
The above description is only a preferred embodiment of the present invention, and not intended to limit the scope of the present invention, and all modifications of equivalent structures and equivalent processes, which are made by using the contents of the present specification and the accompanying drawings, or directly or indirectly applied to other related technical fields, are included in the scope of the present invention.
Claims (10)
1. A merchant risk auditing method is characterized by comprising the following steps:
receiving a merchant risk auditing request submitted by a terminal, wherein the merchant risk auditing request comprises merchant information;
extracting preset key information in the merchant information;
calling a preset interface for verifying the authenticity of preset key information, and verifying the authenticity of the extracted preset key information;
if the preset key information is real, judging whether the preset key information meets a preset circulation condition;
and if the preset circulation condition is met, auditing the preset key information based on a preset auditing rule to determine the risk condition of the merchant.
2. The method of claim 1, further comprising:
if the preset circulation condition is not met, the process is terminated and the information of stopping the audit is returned.
3. The method of claim 1, further comprising:
receiving a new request of an interface which is submitted by a terminal and related to a service requirement;
and establishing the connection of the interface related to the service requirement according to the new request so as to realize the calling of the interface after receiving the request related to the calling of the interface.
4. The method of claim 3, further comprising:
receiving a risk analysis rule which is submitted by a terminal and set according to the service requirement, wherein the risk analysis rule comprises screening condition information and corresponding risk result information;
after receiving a risk analysis request for data corresponding to an interface related to the business requirement, calling the interface related to the business requirement;
and screening the called data based on the screening conditions to obtain a corresponding risk result.
5. The method of claim 4, further comprising:
providing an operation interface for inputting risk analysis rules;
the risk analysis rule which is submitted by the receiving terminal and set according to the business requirement comprises the following steps:
and receiving a risk analysis rule written in a pseudo code mode through the operation interface.
6. The method of claim 1, further comprising: and storing the risk condition of the merchant in a preset database in real time or at regular time.
7. The method of claim 1, further comprising:
the expression form of the risk condition of the merchant comprises scores, money amount, preset risk level and/or preset merchant level.
8. A merchant risk auditing apparatus, the apparatus comprising:
the request receiving module is used for receiving a merchant risk auditing request submitted by a terminal, wherein the merchant risk auditing request comprises merchant information;
the information extraction module is used for extracting preset key information in the merchant information;
the information verification module is used for calling a preset interface for verifying the authenticity of preset key information and verifying the authenticity of the extracted preset key information;
the judging module is used for judging whether the preset key information meets preset circulation conditions or not under the condition that the preset key information is real;
and the risk determining module is used for auditing the preset key information based on a preset auditing rule to determine the risk condition of the merchant under the condition of meeting the preset circulation condition.
9. A computer device, the computer device comprising: memory, processor and computer program stored on the memory and executable on the processor, characterized in that the processor implements the steps of the method of any of claims 1 to 7 when executing the computer program.
10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011493469.5A CN112529692A (en) | 2020-12-16 | 2020-12-16 | Merchant risk auditing method, device and equipment and readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011493469.5A CN112529692A (en) | 2020-12-16 | 2020-12-16 | Merchant risk auditing method, device and equipment and readable storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112529692A true CN112529692A (en) | 2021-03-19 |
Family
ID=75001284
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011493469.5A Pending CN112529692A (en) | 2020-12-16 | 2020-12-16 | Merchant risk auditing method, device and equipment and readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112529692A (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109389457A (en) * | 2018-08-20 | 2019-02-26 | 深圳壹账通智能科技有限公司 | Method of network entry, device, equipment and the readable storage medium storing program for executing of application gathering permission |
| CN110162560A (en) * | 2019-04-16 | 2019-08-23 | 深圳壹账通智能科技有限公司 | Finance data interface butt joint method, device, computer equipment and storage medium |
| CN110288462A (en) * | 2019-05-31 | 2019-09-27 | 北京随信云链科技有限公司 | Air control system, air control method, computer readable storage medium and calculating equipment |
-
2020
- 2020-12-16 CN CN202011493469.5A patent/CN112529692A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109389457A (en) * | 2018-08-20 | 2019-02-26 | 深圳壹账通智能科技有限公司 | Method of network entry, device, equipment and the readable storage medium storing program for executing of application gathering permission |
| CN110162560A (en) * | 2019-04-16 | 2019-08-23 | 深圳壹账通智能科技有限公司 | Finance data interface butt joint method, device, computer equipment and storage medium |
| CN110288462A (en) * | 2019-05-31 | 2019-09-27 | 北京随信云链科技有限公司 | Air control system, air control method, computer readable storage medium and calculating equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110782329A (en) | Financial invoice authentication management method and system | |
| US20100250431A1 (en) | Systems, methods, and machine-readable mediums for providing real-time data of commercial and financial activity of a business to a financial institution to guide credit operations and risk management | |
| CN109584031A (en) | Account checking method, device, electronic equipment and computer-readable medium | |
| CN112001795B (en) | Cross-border service declaration file verification method, device and equipment | |
| JP2011170490A (en) | SaaS GENERAL ACCOUNTING SYSTEM | |
| CN111144697A (en) | Data processing method, data processing device, storage medium and electronic equipment | |
| KR102069551B1 (en) | Accounting and management system using artificial intelligence | |
| US20130144782A1 (en) | Electronic invoice payment prediction system and method | |
| WO2020233402A1 (en) | Accounts payable order validation method, apparatus and device, and storage medium | |
| CN113205402A (en) | Account checking method and device, electronic equipment and computer readable medium | |
| US7970673B2 (en) | Method, apparatus, and computer program product for repository data maximization | |
| KR20160118399A (en) | System and method for examining tax affairs report | |
| CN113935818A (en) | Order settlement method, system and electronic equipment | |
| CN114862110A (en) | Method and device for building middle platform of commercial banking business, electronic equipment and storage medium | |
| CN110020795A (en) | The method and device of risk control is provided for mutual fund earnings | |
| US20130339237A1 (en) | Methods and systems for investigating fraudulent transactions | |
| CN115423619A (en) | Data processing method, device, system, storage medium and program product | |
| CN115545858A (en) | RPA-based automatic account checking method, device, equipment and storage medium | |
| CN112529692A (en) | Merchant risk auditing method, device and equipment and readable storage medium | |
| CN114331105A (en) | Electronic draft processing system, method, electronic device and storage medium | |
| KR102387046B1 (en) | Method and system for pawnshop automation of nonstorage pledge | |
| Oliverio et al. | A hybrid model for fraud detection on purchase orders | |
| CN114187116A (en) | Method and apparatus for managing account information | |
| CN114240652A (en) | Rule generation method and device for business system | |
| CN113313573A (en) | Configuration-based credit granting business processing method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |