Business risk processing method and device, equipment, storage medium and program product

Abstract

The invention provides a business risk processing method and device, equipment, a storage medium and a program product, and thorough decoupling and low-intrusion integration of business logic and risk control logic are realized by introducing a risk processing system. A business system only needs to initiate standardized calling and transmit business data at a key processing node, all risk control integration logics are automatically completed by a risk processing system, so that the business system does not need to embed any hard-coded risk control code, and therefore, when a risk control strategy is changed or an interface is adjusted, a business side does not need to modify the code and re-publish the code, and the risk control efficiency is improved. And the system coupling degree and the maintenance cost are obviously reduced. Meanwhile, due to a unified processing framework and an automatic expression mapping mechanism, repeated development of all service systems can be avoided, and the consistency of risk control behaviors is ensured.

Description

Technical Field

[0001] This application relates to the field of data processing, and more particularly to a business risk management method, apparatus, equipment, storage medium, and program product. Background Technology

[0002] With the rapid development of fintech and e-commerce, online transactions, fund transfers, and payment scenarios are becoming increasingly frequent, and transaction fraud risks are exhibiting diversified, concealed, and real-time characteristics. To safeguard fund security and user rights, various business systems generally need to integrate dedicated anti-fraud systems to identify and intercept transaction risks in real time.

[0003] Currently, business systems generally integrate risk control functions through hard coding: developers need to manually write data extraction, API call, and result processing logic in the business code. Specifically, the business system must extract fields from its own data structure and assemble requests according to the risk control interface specification, then initiate synchronous calls, and finally decide whether to block transactions based on the returned results.

[0004] However, this approach results in a high degree of coupling between the business system and the anti-fraud system. Any change to risk control strategies or interfaces requires modification of the business code and a redeployment, leading to poor system maintainability and flexibility. Therefore, an integration solution that reduces coupling and supports flexible configuration is needed. Summary of the Invention

[0005] This application provides a business risk handling method, apparatus, device, storage medium, and program product that can achieve efficient, flexible, and low-intrusion integration of business systems and anti-fraud systems in a configurable manner, effectively solving the problems of high coupling, difficult maintenance, and poor flexibility caused by traditional hard-coded integration methods.

[0006] In a first aspect, embodiments of this application provide a business risk handling method, applied to a risk handling system, the business risk handling method comprising:

[0007] Receive a call request from the business system. The call request includes the business information of the business to be processed. The business information includes the business identifier and business data of the business to be processed.

[0008] Based on the business identifier, determine the configuration information corresponding to the business to be processed. The configuration information includes the field assignment expressions corresponding to the business to be processed.

[0009] The anti-fraud system is invoked based on field assignment expressions to obtain the risk assessment results of the anti-fraud system for the business to be processed. The risk assessment results are used to indicate whether the business to be processed is a risky business.

[0010] Based on the risk assessment results, determine the target operations for the business to be processed.

[0011] In one possible implementation, the configuration information also includes the risk control service identifier corresponding to the business to be processed;

[0012] The anti-fraud system is invoked based on field assignment expressions to obtain the risk assessment results of the anti-fraud system for the business to be processed, including:

[0013] Based on the risk control service identifier, the target risk control service in the anti-fraud system is identified;

[0014] Based on field assignment expressions, business data is mapped to the interface fields of the target risk control service;

[0015] The anti-fraud system is invoked to judge the business to be processed based on the interface fields, and the risk assessment result of the business to be processed is obtained.

[0016] In one possible implementation, the configuration information also includes the data model identifier corresponding to the service to be processed;

[0017] Based on field assignment expressions, business data is mapped to the interface fields of the target risk control service, including:

[0018] Based on the data model identifier, determine the target data model corresponding to the business to be processed;

[0019] Based on the target data model, execute field assignment expressions to map business data to the interface fields of the target risk control service.

[0020] In one possible implementation, the anti-fraud system is invoked to assess the business to be processed based on interface fields, obtaining a risk assessment result for the business to be processed, including:

[0021] Based on the interface fields, generate a request message that conforms to the target risk control service;

[0022] Send a request message to the anti-fraud system and receive the risk assessment results of the anti-fraud system for the business to be processed based on the request message.

[0023] In one possible implementation, the configuration information also includes a processing mode identifier for the service to be processed, which is used to indicate whether the processing mode of the service to be processed is a first mode or a second mode.

[0024] When the processing mode of the pending business is the first mode, the anti-fraud system is invoked before the pending business is processed by the business system.

[0025] When the processing mode of the pending business is the second mode, the anti-fraud system is invoked after the pending business is processed by the business system.

[0026] In one possible implementation, when the processing mode of the service to be processed is the first mode, the target operation for the service to be processed is determined based on the risk assessment result, including:

[0027] If the risk assessment result indicates that the pending business is not a risky business, the target operation is to continue processing the pending business.

[0028] If the risk assessment result indicates that the pending business is a risky business, the target operation is to block the pending business.

[0029] In one possible implementation, when the processing mode of the service to be processed is the second mode, the target operation for the service to be processed is determined based on the risk assessment result, including:

[0030] If the risk assessment result indicates that the pending business is a risky business, the target operation is to reverse the pending business in the business system back to its state before it was processed.

[0031] In one possible implementation, the method further includes the following in the event that the pending business processing fails:

[0032] Obtain failure information for pending business processes;

[0033] Send a failure message to the anti-fraud system.

[0034] Secondly, embodiments of this application provide a business risk processing apparatus, comprising:

[0035] The receiving module is used to receive call requests from the business system. The call requests include business information of the business to be processed, and the business information includes the business identifier and business data of the business to be processed.

[0036] The determination module is used to determine the configuration information corresponding to the business to be processed based on the business identifier. The configuration information includes the field assignment expressions corresponding to the business to be processed.

[0037] The acquisition module is used to call the anti-fraud system based on field assignment expressions to obtain the risk assessment result of the anti-fraud system for the business to be processed. The risk assessment result is used to indicate whether the business to be processed is a risky business.

[0038] The determination module is also used to determine the target operation for the business to be processed based on the risk assessment results.

[0039] In one possible implementation, the configuration information also includes the risk control service identifier corresponding to the business to be processed;

[0040] The acquisition module is specifically used to: determine the target risk control service in the anti-fraud system based on the risk control service identifier;

[0041] Based on field assignment expressions, business data is mapped to the interface fields of the target risk control service;

[0042] The anti-fraud system is invoked to judge the business to be processed based on the interface fields, and the risk assessment result of the business to be processed is obtained.

[0043] In one possible implementation, the configuration information also includes the data model identifier corresponding to the service to be processed;

[0044] The acquisition module is specifically used to: determine the target data model corresponding to the business to be processed based on the data model identifier;

[0045] Based on the target data model, execute field assignment expressions to map business data to the interface fields of the target risk control service.

[0046] In one possible implementation, the acquisition module is specifically used to: generate a request message that conforms to the target risk control service based on the interface fields;

[0047] Send a request message to the anti-fraud system and receive the risk assessment results of the anti-fraud system for the business to be processed based on the request message.

[0048] In one possible implementation, the configuration information also includes a processing mode identifier for the service to be processed, which is used to indicate whether the processing mode of the service to be processed is a first mode or a second mode.

[0049] When the processing mode of the pending business is the first mode, the anti-fraud system is invoked before the pending business is processed by the business system.

[0050] When the processing mode of the pending business is the second mode, the anti-fraud system is invoked after the pending business is processed by the business system.

[0051] In one possible implementation, when the processing mode of the service to be processed is the first mode, the determining module is specifically used for:

[0052] If the risk assessment result indicates that the pending business is not a risky business, the target operation is to continue processing the pending business.

[0053] If the risk assessment result indicates that the pending business is a risky business, the target operation is to block the pending business.

[0054] In one possible implementation, when the processing mode of the service to be processed is the second mode, the determining module is specifically used for:

[0055] If the risk assessment result indicates that the pending business is a risky business, the target operation is to reverse the pending business in the business system back to its state before it was processed.

[0056] In one possible implementation, the business risk processing device further includes: a sending module;

[0057] The acquisition module is also used to: acquire failure information of pending business processing;

[0058] The sending module is used to send failure information to the anti-fraud system.

[0059] Thirdly, embodiments of this application provide a business risk processing system for performing the first aspect and / or various possible implementations of the first aspect.

[0060] Fourthly, embodiments of this application provide a risk processing system, including: a memory and a processor;

[0061] The memory stores the instructions that the computer executes;

[0062] The processor executes computer execution instructions stored in memory, causing the processor to perform the first aspect and / or various possible implementations of the first aspect as described above.

[0063] Fifthly, embodiments of this application provide a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the first aspect and / or various possible implementations of the first aspect.

[0064] In a sixth aspect, embodiments of this application provide a computer program product, including a computer program that, when executed by a processor, implements the first aspect and / or various possible implementations of the first aspect.

[0065] The business risk processing method, apparatus, device, storage medium, and program product provided in this application embodiment achieve complete decoupling and low-intrusion integration of business logic and risk control logic by introducing a configurable risk processing system. The core of this method is that the business system only needs to initiate standardized calls and transmit raw business data at key processing nodes, while all complex risk control integration logic—including dynamically obtaining configuration information based on business identifiers, automatically completing data conversion using field assignment expressions, and calling the anti-fraud system to obtain professional judgments—is automatically completed by the risk processing system. This design encapsulates risk control strategies and interface adaptation rules into dynamically modifiable configurations, eliminating the need for the business system to embed any hard-coded risk control code. Therefore, when risk control strategies change or interfaces are adjusted, the business side does not need to modify code or redeploy, significantly reducing system coupling and maintenance costs. Simultaneously, the unified processing framework and automated expression mapping mechanism not only avoid redundant development across business systems and ensure consistency in risk control behavior, but also significantly improve the adaptability, development efficiency, and overall architectural evolvability of the business system while guaranteeing the effectiveness of risk management. Attached Figure Description

[0066] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0067] Figure 1 A schematic diagram illustrating the application scenario of the business risk handling method provided in this application;

[0068] Figure 2 A flowchart illustrating the business risk handling method provided for this application. Figure 1 ;

[0069] Figure 3 A flowchart illustrating the business risk handling method provided for this application. Figure 2 ;

[0070] Figure 4 A flowchart illustrating the business risk handling method provided for this application. Figure 3 ;

[0071] Figure 5 A flowchart illustrating the business risk handling method provided for this application. Figure 4 ;

[0072] Figure 6 A schematic diagram of the business risk processing device provided in this application;

[0073] Figure 7 A schematic diagram of the structure of the electronic device provided in this application.

[0074] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0075] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0076] The collection, storage, use, processing, transmission, provision, and disclosure of financial data or user data involved in the technical solution of this application all comply with the provisions of relevant laws and regulations and do not violate public order and good morals.

[0077] It should be noted that in the embodiments of this application, certain software, components, models and other existing solutions in the industry may be mentioned. These should be regarded as exemplary and are only intended to illustrate the feasibility of implementing the technical solution of this application. However, it does not mean that the applicant has used or necessarily used the solution.

[0078] First, let me explain the terms used in this application:

[0079] Software Development Kit (SDK) is a set of integrated packages released by a platform or service provider that includes tools, libraries, documentation, and examples to help developers quickly and standardly integrate specific functionalities into their applications.

[0080] Application Programming Interface Gateway (API Gateway) is a middleware system that serves as the unified entry point for all external requests and the portal for backend services, responsible for core functions such as routing, authentication, rate limiting, and monitoring.

[0081] Microservices are a software architecture style that breaks down a large monolithic application into a set of small, independent services that can be deployed and scaled independently.

[0082] Rules Engine / Decision Engine Plugin: A software module that can be embedded or integrated to separate business decision logic (rules) from application code, enabling dynamic management and execution of strategies.

[0083] A message middleware processor is a logical processing unit that runs on a message middleware. It is responsible for subscribing to messages, performing business processing, and delivering new messages or updating status after processing.

[0084] Identifier (ID): A string or numeric code used to uniquely identify an entity (such as a user, transaction, or configuration) in a system.

[0085] Internet Protocol Address (IP) means: a unique address assigned to a network device, used to locate the device in the network, and is the basis for network communication and risk control geolocation analysis.

[0086] An Application Programming Interface (API) is a set of well-defined functions, protocols, and data structures that allow different software components or services to communicate and exchange data.

[0087] An HTTP Client / Remote Procedure Call Framework is a programming library or framework used to implement cross-network service calls.

[0088] A reversal occurs when, after a business transaction has been successfully processed, the system automatically or manually initiates a reverse transaction to cancel the original transaction and restore the system state to its state before the transaction, due to subsequent risk assessment or other reasons.

[0089] Rollback, in database or transaction processing, undoes all operations completed within the current transaction, restoring the data state to its state before the transaction began.

[0090] JSON (JavaScript Object Notation) is a lightweight data-interchange format that uses a text format that is completely independent of programming languages ​​to store and represent data. It is easy for humans to read and write, and also easy for machines to parse and generate.

[0091] XML (eXtensible Markup Language) is an extensible markup language used for storing and transmitting structured data. It uses custom tags to describe data and is widely used for configuration files and data exchange.

[0092] In related technologies, business systems typically need to directly call anti-fraud systems through hard-coding, meaning that business developers explicitly implement data field mapping, service calls, and result judgment logic in the code. This approach suffers from technical problems such as deep coupling between business logic and risk control logic, high system maintenance costs, and inflexible adjustment of risk control strategies.

[0093] Specifically, in related technologies, fraud detection and blocking are typically achieved through the following methods:

[0094] 1. Intrusive Business Logic Integration: Anti-fraud detection logic is directly embedded in the business system's code. For example, fraud risk assessment code is inserted at each key node of the transaction process (such as user authentication and account balance checks); if a risk is detected, the transaction is terminated. This approach requires developers to deeply modify the business logic, resulting in high coupling between the business code and the anti-fraud logic, and high maintenance costs.

[0095] 2. End-of-day batch processing: Existing systems typically rely on end-of-day batch processing tasks to collect transaction failure information (such as insufficient balance, account anomalies, etc.). For example, failed transaction records are periodically extracted from the transaction database and then fed back to the anti-fraud model for training or correction. This approach has significant latency, cannot support real-time risk response, and may lead to inefficient model optimization due to data lag.

[0096] 3. Redundant Development and Integration: When each business system integrates the anti-fraud function, the adaptation interface needs to be developed repeatedly. For example, for different transaction types (such as credit card payments and cross-border transfers), the calling logic of the anti-fraud rule engine needs to be written separately, resulting in long development cycles and serious code redundancy.

[0097] It is evident that while the above implementation methods can partially meet the anti-fraud requirements, they suffer from the following core problems: strong intrusion into business systems, delayed information collection, high access complexity, and difficulty in adapting to the real-time and flexibility requirements of high-frequency trading scenarios.

[0098] In view of this, embodiments of this application provide a business risk processing method, apparatus, device, storage medium, and program product. By introducing a configurable risk processing system, it achieves complete decoupling and low-intrusion integration of business logic and risk control logic. The business system only needs to initiate standardized calls and transmit raw business data at key processing nodes, while all complex risk control integration logic is automatically completed by the risk processing system. This design encapsulates risk control strategies and interface adaptation rules into dynamically modifiable configurations, eliminating the need for the business system to embed any hard-coded risk control code. Therefore, when risk control strategies change or interfaces are adjusted, the business side does not need to modify code or redeploy, significantly reducing system coupling and maintenance costs. Simultaneously, the unified processing framework and automated expression mapping mechanism not only avoid redundant development across business systems and ensure consistency in risk control behavior, but also significantly improve the adaptability, development efficiency, and overall architectural evolvability of the business system while guaranteeing effective risk management.

[0099] Figure 1 A schematic diagram illustrating the application scenario of the business risk handling method provided in this application. For example... Figure 1 As shown, the specific application scenarios of this application include: business systems, risk processing systems, and anti-fraud systems.

[0100] Users can initiate business requests (such as transfers and payments) to the business system via the client. At key processing nodes, the business system sends a business identifier (such as "transfer business 001") and the original business data to the risk processing system via a call request. The risk processing system, as a dedicated intermediate system, retrieves pre-configured rules (including field assignment expressions) based on the business identifier and automatically converts heterogeneous business data into standardized requests that the anti-fraud system can recognize. It then calls the anti-fraud system to perform real-time risk analysis. Correspondingly, after the anti-fraud system returns a risk assessment result (such as "high risk" or "low risk"), the risk processing system generates explicit control instructions (such as "block transaction" or "allow continue") and returns them to the business system, which then ultimately responds to the client.

[0101] In some embodiments, the risk processing system can be a logical unit with an independent execution environment, access to a configuration center, and the ability to initiate network calls. Its specific form can be flexibly selected based on the system architecture, deployment environment, and team technology stack; this application does not limit its specific form. For example, the risk processing system can be an independent service (microservice), SDK, rule engine, decision engine plugin, message middleware processor, or API gateway, etc.

[0102] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.

[0103] Figure 2 A flowchart illustrating the business risk handling method provided for this application. Figure 1 The execution entity of this application embodiment is the aforementioned risk handling system. For example... Figure 2 As shown, this risk management method includes the following steps:

[0104] S201, Receive the call request from the business system.

[0105] The call request includes the business information of the business to be processed, which includes the business identifier and business data of the business to be processed.

[0106] In some embodiments, pending business refers to a specific operation instance that the business system is currently executing. There is no limitation on the type of pending business. For example, pending business can be "user transfer transaction", "loan application submission" or "account registration request", etc.

[0107] In some embodiments, a business identifier is a code or keyword used to uniquely distinguish different types of businesses or different scenarios of the same business. For example, A0183A103 can represent "personal online banking large-amount transfer business".

[0108] In some embodiments, business data is the collection of all raw information generated alongside the business transaction to be processed and required for risk control judgment. For example, for a transfer, business data may include: user ID, account information, transaction amount, payee information, operation time, IP address, device fingerprint, geolocation, etc. This data is collected and assembled in real time by the business system from the context of its processing logic (such as user request parameters, session information, and database query results).

[0109] In this context, a call request refers to a structured service call initiated by a business system to a risk processing system (such as an SDK or intermediate service) when risk checks are required.

[0110] In one embodiment, the risk processing system can provide an API interface to the business system. When the business system reaches a node that requires risk assessment, the business system can actively call this API and generate a call request based on the aforementioned business identifier and business data, thereby requesting the risk processing system to execute the risk processing process.

[0111] S202. Determine the configuration information corresponding to the service to be processed based on the service identifier.

[0112] The configuration information includes the field assignment expressions corresponding to the business to be processed.

[0113] In some embodiments, configuration information is a predefined set of rules bound to a specific "business identifier" to guide how to perform risk control processing on this type of business. The configuration information can exist in the form of configuration files (such as XML or YAML) or database records; field assignment expressions are used to define the transformation relationship from "business data" (source) to "fields required by the anti-fraud system interface" (target).

[0114] In some embodiments, after receiving a call request from a business system, the risk processing system first extracts the business identifier from the business request, and uses the business identifier as an index to determine the configuration information corresponding to the business identifier, thereby obtaining the field assignment expressions in the configuration information.

[0115] S203. Call the anti-fraud system based on the field assignment expression to obtain the risk assessment results of the anti-fraud system for the business to be processed.

[0116] The risk assessment result is used to indicate whether the business to be processed is a risky business.

[0117] Specifically, an expression parsing engine can be set up within the risk processing system. After obtaining the field assignment expression, the expression engine uses the field assignment expression as a script to parse and calculate the business data, extract the specific value from the business data according to the path specified by the field assignment expression, and fill the extracted value into a blank request object that conforms to the anti-fraud system interface specification, thereby generating a request message that the anti-fraud system can fail to send.

[0118] Furthermore, the risk processing system can use microservices to call clients (such as HTTP Clients or RPC frameworks) to send the assembled request message to the corresponding interface pre-deployed by the anti-fraud system (the address is usually specified by configuration information). The anti-fraud system judges the business to be processed based on the request message and returns a structured risk judgment result after processing.

[0119] In some embodiments, the process by which an anti-fraud system assesses the risk of a request message and outputs the results mainly includes, but is not limited to, the following three aspects:

[0120] 1. Feature analysis and calculation: The anti-fraud system parses the key fields in the request message and combines them with its real-time or historical data context to calculate a series of risk feature indicators (such as transaction frequency, behavior sequence, and correlation network).

[0121] 2. Multi-dimensional risk assessment: Based on the above characteristics, the anti-fraud system uses its built-in rule engine (which executes predefined logical strategies) and risk model (such as machine learning scoring model) to conduct parallel assessments and obtain preliminary risk signals, scores, or probability parameters.

[0122] 3. Decision Synthesis and Result Output: The anti-fraud system can comprehensively analyze the outputs of rules and models based on preset decision-making strategies to generate a structured risk assessment result. This risk assessment result includes, but is not limited to, at least one of the following:

[0123] Final decision: approve, reject, or require manual review;

[0124] Risk score: A quantified risk value (e.g., 0-1000 points);

[0125] Risk levels: low, medium, high, severe, etc.

[0126] Risk cause: Which specific risk rules or characteristics were triggered;

[0127] Recommended actions: block, enhance verification, mark monitoring, etc.

[0128] Confidence level: The level of confidence in the judgment.

[0129] S204. Based on the risk assessment results, determine the target operation for the business to be processed.

[0130] The target operation refers to the subsequent actions that the business system should take after learning the risk assessment results.

[0131] Specifically, the risk management system can transform the core decision (such as "reject") from the risk assessment result and / or pre-configured strategies (such as "block if score is above 90") into a clear and simple operational instruction. Common instructions include, but are not limited to, at least one of the following:

[0132] "Block": requires the business system to immediately terminate the current business process.

[0133] "Release": This notifies the business system that it can continue executing the business.

[0134] "Reversal": After a transaction has been successfully completed, instruct the business system to initiate a reverse transaction to undo the original operation.

[0135] Ultimately, the risk processing system returns this "target operation" instruction to the business system that initially initiated the call, which then executes it, thus completing the entire risk control integration process.

[0136] The business risk assessment method, electronic device, storage medium, and program product provided in this application embodiment achieve structural decoupling between business processing and risk control systems by constructing a risk decision integration mechanism based on configuration-driven and expression mapping. This method retrieves pre-set configuration information using business identifiers as indexes, and automatically maps heterogeneous business data into standardized risk control service interface requests using declared field assignment expressions. This completes the risk assessment call and response processing, and dynamically controls the business execution process based on the assessment results. By externalizing interface adaptation, data conversion, service calls, and process control logic as configurable rules, this method eliminates the need for business systems to embed any risk control-related hard coding; they can access or adjust risk control capabilities solely through declarative configuration. This not only achieves a clear separation between business logic and risk control logic, significantly reducing system coupling and iterative maintenance costs, but also significantly improves the adaptability, development efficiency, and overall architectural evolvability of the business system while ensuring effective risk management.

[0137] In some embodiments, the processing mode of the pending business includes a first mode and a second mode. Specifically, when the processing mode of the pending business is the first mode, the anti-fraud system is invoked before the pending business is processed by the business system; when the processing mode of the pending business is the second mode, the anti-fraud system is invoked after the pending business is processed by the business system.

[0138] Next, combined Figure 3 The pending business in the first mode is explained. Figure 3 A flowchart illustrating the business risk handling method provided for this application. Figure 2 ,like Figure 3 As shown, the method includes:

[0139] S301, The business system sends a call request to the risk processing system.

[0140] The call request includes the business information of the business to be processed, which includes the business identifier and business data of the business to be processed.

[0141] Specifically, after receiving a user request (such as a transfer instruction), the business system executes step S301 before performing core business operations (such as deduction).

[0142] S302. The risk handling system determines the configuration information corresponding to the business to be processed based on the business identifier.

[0143] The configuration information includes the field assignment expressions corresponding to the business to be processed.

[0144] In some embodiments, the configuration information may further include a processing mode identifier for the service to be processed, which is used to indicate that the service to be processed is in a first mode.

[0145] Specifically, after receiving a request, the risk handling system first extracts the business identifier and then searches for matching rules in its internal configuration management center.

[0146] S303. The risk processing system calls the anti-fraud system based on field assignment expressions to obtain the risk assessment results of the anti-fraud system for the business to be processed.

[0147] The risk assessment result is used to indicate whether the business to be processed is a risky business.

[0148] S304. If the risk assessment result indicates that the pending business is not a risky business, the risk handling system determines the target operation to continue processing the pending business; if the risk assessment result indicates that the pending business is a risky business, the risk handling system determines the target operation to block the pending business.

[0149] S305. The risk handling system returns the target operation instruction to the business system.

[0150] Among them, the target operation instruction is used to instruct the business system to perform the target operation.

[0151] S306. If the pending business is not a risky business, the business system continues to process the pending business; if the pending business is a risky business, the business system blocks the pending business.

[0152] In some embodiments, if the business system receives a "continue processing" instruction, it will execute the previously suspended business operations; specifically, these include, but are not limited to, the following operations:

[0153] Database updates (such as deductions or status changes); invocation of downstream services; generation of business results; and return of a success response to the user.

[0154] In some embodiments, if a business system receives a "block" instruction, it immediately terminates the current business process. Specifically, this includes, but is not limited to, the following operations: returning a blocking prompt to the user (e.g., "Transaction is at risk and has been interrupted"); releasing occupied resources (e.g., database connections); logging the blocking event in detail for auditing and analysis; and, depending on the configuration, triggering enhanced verification or transferring the process to manual review.

[0155] S307. If the business processing fails, the risk handling system obtains the failure information of the pending business processing.

[0156] In some embodiments, the risk handling system can detect business system failures through callbacks or event listening mechanisms. The failure information includes, but is not limited to, at least one of the following:

[0157] Reasons for failure: such as "insufficient balance", "account frozen", "system error";

[0158] Failure time: Precise timestamp;

[0159] Business context: A snapshot of the business state at the time of failure;

[0160] Error details: Technical error code and description.

[0161] S308, The risk processing system sends a failure message to the anti-fraud system.

[0162] Specifically, the risk handling system can organize business failure information into a standard format and send it to the information collection interface of the anti-fraud system.

[0163] In some embodiments, failure information can be used for at least one of the following operations of the anti-fraud system:

[0164] Model training: Providing "negative samples" for the machine learning models of anti-fraud systems;

[0165] Rule optimization: Helping risk control experts understand which failures fall under normal user behavior;

[0166] System calibration: Avoid misjudging normal business failures as fraudulent features.

[0167] In a specific example, the business system calls the anti-fraud microservice (e.g., FraudService), which is the aforementioned risk handling system, and passes transaction context parameters (such as transaction time txnDt and account identifier crdInnrAccCgycd). Accordingly, the anti-fraud system determines the transaction risk level based on preset rules (such as blacklists and transaction frequency thresholds).

[0168] Furthermore, if a transaction is determined to be fraudulent, the anti-fraud system returns a blocking signal (e.g., isBlock=true), and the business system immediately terminates the transaction process; if a transaction is determined to be normal, the business system continues to execute the transaction process (such as deduction or transfer).

[0169] Furthermore, if the transaction is successful, the business system does not need to perform any additional operations; if the transaction fails (e.g., insufficient balance), the business system calls the anti-fraud information collection interface to feed back the reason for the failure (e.g., the srpTxnamt field) to the anti-fraud system for model optimization.

[0170] In the embodiments of this application, Figure 3The risk management method in the first mode (preemptive blocking) illustrates the core innovative value of this application in proactive prevention and system decoupling. This method constructs a proactive defense system of "test first, act later" by making risk control checks a mandatory pre-execution step in business processes. It can effectively identify and block high-risk businesses before losses occur, achieving the highest level of security control. This design completely decouples the traditional risk control logic embedded in business code, forming a standardized process centrally coordinated by an independent risk management system. This not only ensures the consistency and professionalism of risk decisions but also achieves deep decoupling between the business system and the risk control system through a configurable field mapping mechanism—the business system only needs to trigger checks and receive concise instructions without needing to be aware of risk control details. The resulting "zero business risk control code, zero risk control business adaptation" architecture significantly reduces the coupling between systems and maintenance costs, allowing adjustments to risk control strategies to take effect immediately through configuration modifications without requiring business system downtime for deployment. Meanwhile, the complete closed loop of abnormal information established by this method can feed back negative samples such as business execution failures to the risk control system in real time, providing continuous data nourishment for its model training and rule optimization, thus forming a proactive risk management framework with high security, high maintainability and continuous evolution capabilities.

[0171] In some embodiments, when the processing mode of the pending business is the second mode, the anti-fraud system is invoked through the risk processing system after the pending business has been processed by the business system. Next, combined with... Figure 4 The pending business in the second mode is explained as follows:

[0172] Figure 4 A flowchart illustrating the business risk handling method provided for this application. Figure 3 ,like Figure 4 As shown, the method includes:

[0173] Step S401: The business system executes the pending business.

[0174] Specifically, upon receiving a user request, the business system executes core business operations directly without waiting for any risk control checks.

[0175] For example, the content executed by the business system may include, but is not limited to, the following scenarios:

[0176] Payment scenarios: direct deduction, generation of transaction records;

[0177] Information changes: Directly update user information and modify settings;

[0178] Service processing: Directly create orders and activate services.

[0179] In some embodiments, the business system may record the execution information of this operation, including but not limited to at least one of the following:

[0180] Operation transaction ID; snapshot of the state before the operation; operation timestamp; execution result (success / failure).

[0181] S402. The business system sends a call request to the risk processing system.

[0182] The call request includes the business information of the business to be processed, which includes the business identifier and business data of the business to be processed.

[0183] Specifically, after the business system completes its business operation, it sends a call request to the risk handling system.

[0184] In some embodiments, in step S402, the aforementioned business data may also include, but is not limited to, the following:

[0185] Business execution results: reasons for success or failure, etc.;

[0186] Business execution evidence: transaction serial number, order number, operation voucher, etc.;

[0187] Reversibility information: Technical parameters on how to undo the operation;

[0188] S403. The risk handling system determines the configuration information corresponding to the business to be processed based on the business identifier.

[0189] The configuration information includes the field assignment expressions corresponding to the business to be processed.

[0190] In some embodiments, the configuration information may further include a processing mode identifier for the service to be processed, which is used to indicate that the service to be processed is in a second mode.

[0191] In some embodiments, after obtaining the processing mode identifier, the risk processing system can determine the following:

[0192] The business logic has been completed; the purpose of this call is verification and possible remediation; the logic related to reversal needs to be prepared.

[0193] In some embodiments, in addition to the basic field mapping, the configuration information may also include mapping rules for the fields required for reversal.

[0194] S404. The risk processing system calls the anti-fraud system based on field assignment expressions to obtain the risk assessment results of the anti-fraud system for the business to be processed.

[0195] The risk assessment result is used to indicate whether the business to be processed is a risky business.

[0196] In some embodiments, the risk processing system can convert business data (including execution results) into the verification request format required by the anti-fraud system.

[0197] In this model, the anti-fraud system focuses on at least one of the following:

[0198] Behavioral verification: Whether the completed business is consistent with the user's historical patterns;

[0199] Time correlation analysis: Are there any anomalies in the operation time points?

[0200] Result consistency check: Whether the business results match the expectations;

[0201] S405. If the risk assessment result indicates that the pending business is a risky business, the risk handling system determines the target operation as follows: revert the pending business in the business system to the state before the pending business was processed.

[0202] Specifically, if the result is "non-risk business": the target operation is determined to be "no operation" or "confirmed as completed", and the business ends normally.

[0203] If the result is "risky business": the target operation is determined to be "reverse", which means that the business system is required to undo the executed operation.

[0204] S406. The risk handling system returns the target operation instruction to the business system.

[0205] In some embodiments, the target operation indication includes, but is not limited to, at least one of the following: no operation indication; reversal indication.

[0206] Optionally, detailed reversal parameters can also be included. These parameters include the reversal method, reversal time window, and reversal voucher.

[0207] S407. If the risk assessment result indicates that the pending business is a risky business, the business system will reverse the pending business to its state before it was processed.

[0208] Specifically, after receiving a reversal instruction, the business system performs a reverse operation. The reversal methods include, but are not limited to, at least one of the following:

[0209] Financial reversal: For example, refunds or cancellations of deductions;

[0210] State rollback: For example, restoring the user's state to its original state;

[0211] Record invalidation: For example, mark the original record as invalid and generate a reversal record.

[0212] In some embodiments, the business system may also send a reversal notification to the user, such as "Your transaction has been reversed for security reasons".

[0213] S408, The risk handling system obtains failure information for pending business processes.

[0214] In some embodiments, whether the business execution fails or the reversal fails, the reasons for the failure and the context are recorded in detail.

[0215] S409. The risk handling system sends a failure message to the anti-fraud system.

[0216] In a specific example, regardless of whether the transaction is successful or not, the business system calls the risk processing service (i.e., the risk processing system) to transmit transaction result data (such as success status code and failure reason). If the transaction is marked as fraudulent, the risk processing system triggers the following reversal logic:

[0217] Call the predefined reversal service (e.g., outServiceID=A0991A001) to perform a rollback operation (e.g., cancel the transfer or restore the account balance); accordingly, the business system returns a transaction failure response based on the reversal result.

[0218] Furthermore, the risk processing system sends detailed information about successful or failed transactions (such as timestamps and account status) to the anti-fraud system to update the anti-fraud system's risk model in real time.

[0219] In the embodiments of this application, Figure 4 The risk handling method in the second mode (post-event reversal) demonstrates the core innovative value of this application in balancing user experience and risk control. This method prioritizes the smoothness and responsiveness of business processing by placing risk control checks after business execution, providing users with a seamless experience. Building upon this, the introduced intelligent reversal mechanism constitutes a crucial security baseline. When the anti-fraud system identifies a risk after the fact, it can automatically and accurately trigger a business rollback operation, restoring the system state to its state before business execution, thereby achieving timely remediation of the risk that has occurred. This design not only constructs a complete risk lifecycle management system covering "business execution, risk verification, and remediation execution," but also ensures through intelligent decision-making logic that reversal actions are only initiated when deemed necessary based on a comprehensive assessment of factors such as risk level, business reversibility, and cost-effectiveness. Furthermore, this method incorporates diverse information such as business execution failures and reversal operation failures into a feedback loop, continuously optimizing the risk control model and decision-making strategies, ultimately forming a dynamic risk control solution that balances user experience and inherent security in high-frequency business scenarios and possesses continuous learning and evolution capabilities.

[0220] Figure 5 A flowchart illustrating the business risk handling method provided for this application. Figure 4 In this embodiment Figure 2 , Figure 3 , Figure 4Based on the illustrated embodiment, the risk management method will be described in detail. Among them, Figure 5 The risk management method shown is implemented by a risk management system, such as... Figure 5 As shown, the method includes the following steps:

[0221] S501: Receive call requests from business systems.

[0222] The call request includes the business information of the business to be processed, which includes the business identifier and business data of the business to be processed.

[0223] S502. Determine the configuration information corresponding to the service to be processed based on the service identifier.

[0224] The configuration information includes the field assignment expressions corresponding to the business to be processed.

[0225] In some embodiments, the configuration information is a structured rule package that contains at least the following:

[0226] 1. Processing Mode Identifier: The processing mode identifier indicates the processing mode corresponding to the service to be processed. The processing modes include the following two types:

[0227] Mode 1: Represents a "preemptive blocking" strategy. Upon seeing this flag, the system will complete a risk control check before business operations are executed, and the business system must wait for the results.

[0228] The second mode represents a "post-event reversal" strategy. The system allows business operations to proceed first, followed by risk control verification in the background, triggering remediation if necessary.

[0229] 2. Field assignment expression list, which defines the rule statements for extracting and transforming the fields required for risk control from business data.

[0230] 3. Risk control service identifier, used to indicate the specific risk control service code that the business to be processed needs to call, such as "fraud detection service A" or "account security service B".

[0231] 4. Data model identifier, used to specify the technical class name corresponding to the request message format required by the risk control service.

[0232] In this embodiment, business logic and risk control strategies are decoupled. The risk control processing method for each business type is no longer hard-coded in the program, but is controlled through dynamically modifiable configurations, thus bringing great flexibility—to adjust the risk control strategy for a certain business, only the configuration needs to be modified, without changing the code or redeploying.

[0233] S503. Based on the risk control service identifier, determine the target risk control service in the anti-fraud system.

[0234] Specifically, based on the risk control service identifier, the corresponding service instance address is searched in the service registry, or the risk control service endpoint is obtained from the pre-configured mapping table.

[0235] This step enables the mapping from logical service names to physical service instances, allowing risk control services to be deployed, expanded, and upgraded independently, without the business system being aware of physical changes to the backend services. It also supports load balancing and fault tolerance.

[0236] S504. Based on field assignment expressions, map business data to the interface fields of the target risk control service.

[0237] Specifically, based on field assignment expressions, business data is mapped to the interface fields of the target risk control service, including the following steps S5041-S5042:

[0238] S5041. Based on the data model identifier, determine the target data model corresponding to the business to be processed.

[0239] The target data model is a complete classpath name specified in the configuration information, used to define the precise data structure expected by the risk control service—including field names, data types, whether they are required, format constraints, etc.

[0240] Specifically, the risk handling system creates an empty instance of this target data model class in memory, ready to populate it with data.

[0241] S5042. Based on the target data model, execute the field assignment expression to map the business data to the interface fields of the target risk control service.

[0242] Specifically, the risk processing system can have a built-in expression parsing and execution engine that supports a specific expression language. Each field assignment expression defines a data transformation rule. The engine reads each field assignment expression sequentially, navigates to and extracts values ​​from the business data according to the "source data path," and assigns the extracted values ​​to the model fields specified by the "target field path."

[0243] In this embodiment of the application, by replacing the hundreds of lines of data conversion code that originally needed to be written manually with declarative configuration statements, the problem of errors that are easy to make with manual coding is avoided, and the field mapping relationship is centrally managed, clear at a glance, and easy to modify.

[0244] S505. Call the anti-fraud system to judge the business to be processed based on the interface fields and obtain the risk judgment result of the business to be processed.

[0245] Specifically, the risk processing system serializes the data model instance built in S504 into a format accepted by the risk control service (such as JSON, XML, etc.), sends the request to the service endpoint determined by S503 through protocols such as HTTP and gRPC, receives the response from the risk control system, and deserializes it into an internal data structure.

[0246] In some embodiments, the risk handling system can also set a reasonable timeout period to avoid blocking business operations due to slow response from the anti-fraud system.

[0247] Optionally, after obtaining the risk assessment result, the result can be returned to the caller (business system). And according to the processing mode determined in S502:

[0248] First mode: The result is immediately returned to the business system to decide whether to continue the business process.

[0249] Second mode: The results are used to determine whether remedial measures such as reversal need to be triggered.

[0250] Figure 5 The core risk control processing method shown embodies the fundamental innovative value of this application in building a standardized, configurable risk control integration engine. This method defines a standardized processing pipeline from receiving business requests, parsing configurations, mapping data, to obtaining risk assessment results, abstracting and unifying the heterogeneous risk control logic traditionally scattered across various business systems into a professional risk processing system. Its core benefit lies in the fact that by introducing declarative configuration rules (especially field assignment expressions and processing mode identifiers), it achieves automated, zero-code mapping from business data to risk control interfaces, completely freeing business developers from understanding the details of risk control protocols and writing complex adaptation code. The resulting standardized "receive-configure-transform-call" process not only ensures a high degree of consistency and auditability of risk control behaviors across different businesses, but also, through the complete separation of configuration and code, allows adjustments to risk control strategies, switching of risk control services, and even changes in processing modes to take effect immediately by modifying external configurations, without requiring business system downtime for deployment, greatly improving the overall system's flexibility and maintainability. Ultimately, this process provides a framework for diverse upper-layer business risk control scenarios (such as...). Figure 3 Pre-emptive intervention Figure 4 Post-event reversal provides a stable, efficient, and scalable general-purpose technology foundation, enabling centralized management and on-demand configuration of risk control capabilities at the architectural level.

[0251] Figure 6 A schematic diagram of the business risk processing device provided in this application is shown below. Figure 6 As shown, the business risk processing device 60 provided in this embodiment includes:

[0252] The receiving module 601 is used to receive a call request from the business system. The call request includes business information of the business to be processed. The business information includes the business identifier and business data of the business to be processed.

[0253] The determination module 602 is used to determine the configuration information corresponding to the business to be processed based on the business identifier. The configuration information includes the field assignment expression corresponding to the business to be processed.

[0254] The acquisition module 603 is used to call the anti-fraud system based on the field assignment expression to obtain the risk assessment result of the anti-fraud system for the business to be processed. The risk assessment result is used to indicate whether the business to be processed is a risky business.

[0255] The determination module 602 is also used to determine the target operation for the business to be processed based on the risk assessment results.

[0256] In one possible implementation, the configuration information also includes the risk control service identifier corresponding to the business to be processed.

[0257] The acquisition module 603 is specifically used to: determine the target risk control service in the anti-fraud system based on the risk control service identifier;

[0258] Based on field assignment expressions, business data is mapped to the interface fields of the target risk control service;

[0259] The anti-fraud system is invoked to judge the business to be processed based on the interface fields, and the risk assessment result of the business to be processed is obtained.

[0260] In one possible implementation, the configuration information also includes the data model identifier corresponding to the service to be processed;

[0261] The acquisition module 603 is specifically used to: determine the target data model corresponding to the business to be processed based on the data model identifier;

[0262] Based on the target data model, execute field assignment expressions to map business data to the interface fields of the target risk control service.

[0263] In one possible implementation, the acquisition module 603 is specifically used to: generate a request message that conforms to the target risk control service based on the interface fields;

[0264] Send a request message to the anti-fraud system and receive the risk assessment results of the anti-fraud system for the business to be processed based on the request message.

[0265] In one possible implementation, the configuration information also includes a processing mode identifier for the service to be processed, which is used to indicate whether the processing mode of the service to be processed is a first mode or a second mode.

[0266] When the processing mode of the pending business is the first mode, the anti-fraud system is invoked before the pending business is processed by the business system.

[0267] When the processing mode of the pending business is the second mode, the anti-fraud system is invoked after the pending business is processed by the business system.

[0268] In one possible implementation, when the processing mode of the service to be processed is the first mode, the determining module 602 is specifically used for:

[0269] If the risk assessment result indicates that the pending business is not a risky business, the target operation is to continue processing the pending business.

[0270] If the risk assessment result indicates that the pending business is a risky business, the target operation is to block the pending business.

[0271] In one possible implementation, when the processing mode of the service to be processed is the second mode, the determining module 602 is specifically used for:

[0272] If the risk assessment result indicates that the pending business is a risky business, the target operation is to reverse the pending business in the business system back to its state before it was processed.

[0273] In one possible implementation, the business risk processing device further includes: a sending module 604;

[0274] The acquisition module 603 is also used to: acquire failure information of pending business processing;

[0275] The sending module 604 is used to send failure information to the anti-fraud system.

[0276] The business risk processing device provided in this embodiment can execute the method provided in the above method embodiment. Its implementation principle and technical effect are similar, and will not be described in detail here.

[0277] Figure 7 A schematic diagram of the structure of the electronic device provided in this application. Figure 7 As shown, the electronic device 70 provided in this embodiment includes at least one processor 701 and a memory 702. Optionally, the electronic device 70 further includes a communication component 703. The processor 701, memory 702, and communication component 703 are connected via a bus.

[0278] In a specific implementation, at least one processor 701 executes computer execution instructions stored in memory 702, causing at least one processor 701 to perform the above-described method.

[0279] The specific implementation process of processor 701 can be found in the above method embodiments, and its implementation principle and technical effect are similar. It will not be repeated here.

[0280] In the above embodiments, it should be understood that the processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in this invention can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules within the processor.

[0281] The memory may include random access memory (RAM) and may also include non-volatile memory (NVM), such as at least one disk storage device.

[0282] The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of illustration, the buses shown in the accompanying drawings are not limited to a single bus or a single type of bus.

[0283] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the above-described method.

[0284] This application also provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, implement the above-described method.

[0285] The aforementioned readable storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk. The readable storage medium can be any available medium accessible to a general-purpose or special-purpose computer.

[0286] An exemplary readable storage medium is coupled to a processor, enabling the processor to read information from and write information to the readable storage medium. Of course, the readable storage medium can also be a component of the processor. The processor and the readable storage medium can reside in an Application Specific Integrated Circuit (ASIC). Alternatively, the processor and the readable storage medium can exist as discrete components in the device.

[0287] The division of units is merely a logical functional division; in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be indirect coupling or communication connection through some interfaces, devices, or units, and may be electrical, mechanical, or other forms.

[0288] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment, depending on actual needs.

[0289] In addition, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0290] If a function is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this invention, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0291] Those skilled in the art will understand that all or part of the steps of the above-described method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When executed, the program performs the steps of the above-described method embodiments; and the aforementioned storage medium includes various media capable of storing program code, such as ROM, RAM, magnetic disks, or optical disks.

[0292] Finally, it should be noted that other embodiments of the invention will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This invention is intended to cover any variations, uses, or adaptations of the invention that follow the general principles of the invention and include common knowledge or customary techniques in the art not disclosed herein, and is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of the invention is limited only by the appended claims.

Claims

1. A business risk handling method, characterized in that, Applied to a risk management system, the method includes: Receive a call request from a business system, the call request including business information of the business to be processed, the business information including the business identifier and business data of the business to be processed; Based on the service identifier, the configuration information corresponding to the service to be processed is determined, and the configuration information includes the field assignment expression corresponding to the service to be processed; The anti-fraud system is invoked based on the field assignment expression to obtain the risk assessment result of the anti-fraud system on the pending business. The risk assessment result is used to indicate whether the pending business is a risky business. Based on the risk assessment results, the target operation for the pending business is determined.

2. The method according to claim 1, characterized in that, The configuration information also includes the risk control service identifier corresponding to the pending business; The step of invoking the anti-fraud system based on the field assignment expression to obtain the risk assessment result of the anti-fraud system for the pending business includes: Based on the risk control service identifier, the target risk control service in the anti-fraud system is determined; Based on the field assignment expression, the business data is mapped to the interface fields of the target risk control service; The anti-fraud system is invoked to judge the pending business based on the interface fields, and the risk judgment result of the pending business is obtained.

3. The method according to claim 2, characterized in that, The configuration information also includes the data model identifier corresponding to the service to be processed; The process of mapping the business data to the interface fields of the target risk control service based on the field assignment expression includes: Based on the data model identifier, the target data model corresponding to the service to be processed is determined; Based on the target data model, the field assignment expression is executed to map the business data to the interface fields of the target risk control service.

4. The method according to claim 2, characterized in that, The step of calling the anti-fraud system to judge the pending business based on the interface fields and obtaining the risk judgment result of the pending business includes: Based on the interface fields, generate a request message that conforms to the target risk control service; Send the request message to the anti-fraud system and receive the risk assessment result of the anti-fraud system on the pending business based on the request message.

5. The method according to any one of claims 1-4, characterized in that, The configuration information also includes a processing mode identifier for the service to be processed, which indicates whether the processing mode of the service to be processed is a first mode or a second mode. When the processing mode of the pending business is the first mode, the anti-fraud system is invoked before the pending business is processed by the business system. When the processing mode of the pending business is the second mode, the anti-fraud system is invoked after the pending business is processed by the business system.

6. The method according to claim 5, characterized in that, When the processing mode of the pending business is the first mode, determining the target operation for the pending business based on the risk assessment result includes: If the risk assessment result indicates that the pending business is not a risky business, then the target operation is determined to continue processing the pending business. If the risk assessment result indicates that the pending service is a risky service, the target operation is determined to be blocking the pending service.

7. The method according to claim 5, characterized in that, When the processing mode of the pending business is the second mode, determining the target operation for the pending business based on the risk assessment result includes: If the risk assessment result indicates that the pending business is a risky business, the target operation is determined to be: to reverse the pending business in the business system to the state before the pending business was processed.

8. The method according to claim 5, characterized in that, In the event that the pending service processing fails, the method further includes: Obtain the failure information of the pending business processing; The failure message is sent to the anti-fraud system.

9. A business risk processing device, characterized in that, include: A receiving module is used to receive a call request from a business system. The call request includes business information of the business to be processed, and the business information includes the business identifier and business data of the business to be processed. The determination module is used to determine the configuration information corresponding to the service to be processed based on the service identifier, wherein the configuration information includes the field assignment expression corresponding to the service to be processed; The acquisition module is used to call the anti-fraud system based on the field assignment expression to obtain the risk assessment result of the anti-fraud system on the business to be processed. The risk assessment result is used to indicate whether the business to be processed is a risky business. The determining module is further configured to determine the target operation for the pending business based on the risk assessment result.

10. A risk management system, characterized in that, The risk management system is used to perform the method as described in any one of claims 1-8.

11. An electronic device, characterized in that, include: Memory, processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory, causing the processor to perform the method as described in any one of claims 1-8.

12. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the method as described in any one of claims 1-8.

13. A computer program product, characterized in that, Includes a computer program that, when executed by a processor, implements the method described in any one of claims 1-8.

Images