Business processing method and apparatus, electronic device, and readable medium

Abstract

The application provides a business processing method and device, electronic equipment and readable medium. The method comprises: receiving a first business processing request, the business processing request comprising a first business type identifier and a business amount; calling a business processing logic corresponding to the first business type identifier to create a control sheet information corresponding to the business amount, the control sheet information being used to control the flow direction of the business amount; receiving a second business processing request for the control sheet information, the second business processing request comprising a second business type identifier and a business amount; calling a business processing logic corresponding to the second business type identifier to create a release control sheet information corresponding to the business amount, the release control sheet information being used to release the control of the flow direction of the business amount; and feeding back a business processing result according to the control sheet information and the release control sheet information. The method uniformly controls the fund, avoids competition of various business modules for the same fund management, and improves the operation efficiency of the fund management process.

Description

Technical Field

[0001] This application relates to the field of computer technology, and more particularly to a business processing method, apparatus, electronic device, and readable medium. Background Technology

[0002] In payment scenarios, after the payer's funds enter the transaction system, they will face multiple fund flows, such as settlement business, account splitting business, and cash withdrawal business. At the same time, there is also a refund business with the opposite flow. The funds available in these multiple fund flows are mutually exclusive, so it is necessary to control the flow of various funds.

[0003] Currently, in management systems in related fields, each business module typically manages its own fund inflows and outflows based on overall fund control information.

[0004] However, in such schemes, each business module is responsible for business logic and fund management. As a result, multiple business modules compete for the same funds, which affects the efficiency of the fund management process. Summary of the Invention

[0005] In view of the above-mentioned technical problems, this application provides a business processing method, apparatus, electronic device and readable medium to uniformly manage funds, avoid competition among various business modules for the same fund management, and thus improve the operational efficiency of the fund management process.

[0006] Other features and advantages of this application will become apparent from the following detailed description, or may be learned in part from practice of this application.

[0007] According to one aspect of the embodiments of this application, a business processing method is provided, including:

[0008] Receive a first service processing request, wherein the service processing request includes a first service type identifier and a service amount;

[0009] Invoke the business processing logic corresponding to the first business type identifier to create control order information corresponding to the business amount, wherein the control order information is used to control the flow of the business amount;

[0010] Receive a second business processing request for the control order information, wherein the second business processing request includes a second business type identifier and the business amount;

[0011] Invoke the business processing logic corresponding to the second business type identifier to create a release order information corresponding to the business amount, wherein the release order information is used to release the flow of the business amount;

[0012] The business processing results are fed back based on the control order information and the decontrol order information.

[0013] According to one aspect of the embodiments of this application, a business processing apparatus is provided, comprising:

[0014] The first request receiving module is used to receive a first business processing request, wherein the first business processing request includes a business type identifier and a business amount;

[0015] The first logic call module is used to call the business processing logic corresponding to the first business type identifier to create control order information corresponding to the business amount, wherein the control order information is used to control the flow of the business amount;

[0016] The second request receiving module is used to receive a second business processing request for the control order information, wherein the second business processing request includes a second business type identifier and the business amount;

[0017] The second logic call module is used to call the business processing logic corresponding to the second business type identifier to create a release order information corresponding to the business amount, wherein the release order information is used to release the flow of the business amount;

[0018] The result feedback module is used to provide feedback on the business processing results based on the control order information and the decontrol order information.

[0019] In some embodiments of this application, based on the above technical solutions, the request receiving module includes:

[0020] A payment control receiving unit is used to receive a payment control request when a payment request is completed, wherein the payment control request carries a business payment identifier and the business amount, and the business amount is the amount in response to the payment request;

[0021] The first logical call module includes:

[0022] The payment logic invocation unit is used to invoke the business processing logic corresponding to the business payment identifier to create a payment control order, wherein the payment control order includes a payment document identifier and the business amount.

[0023] In some embodiments of this application, based on the above technical solutions, the first logic call module further includes:

[0024] A payment release receiving unit is used to receive a payment release request sent by a target device, wherein the payment release request carries the payment document identifier and the release amount;

[0025] The release control unit is used to release control over the release amount or the transaction amount in the payment control order according to the payment release request;

[0026] The amount sending unit is used to send the unlocked amount or the service amount to the target device.

[0027] In some embodiments of this application, based on the above technical solutions, deactivating the control unit includes:

[0028] The first payment decontrol subunit is used to release control of the decontrol amount in the payment control order if the decontrol amount carried in the payment decontrol request is less than or equal to the business amount in the payment control order;

[0029] The second payment decontrol subunit is used to release control over the transaction amount in the payment control order if the decontrol amount carried in the payment decontrol request is greater than the transaction amount in the payment control order.

[0030] In some embodiments of this application, based on the above technical solutions, the second request receiving module includes:

[0031] The settlement release request receiving unit is used to receive a settlement release request sent by the business module when a settlement request for the control order information is completed, wherein the settlement release request carries a business settlement identifier and a settlement release amount, and the settlement release amount is the amount in response to the settlement request;

[0032] The second logic call module includes:

[0033] The settlement logic invocation unit is used to invoke the business processing logic corresponding to the business settlement identifier to create a settlement release order, wherein the settlement release order includes a settlement document identifier and the settlement release amount.

[0034] In some embodiments of this application, based on the above technical solutions, the control order information includes control amount, control type, and control status; the second logic call module further includes:

[0035] Settlement control order acquisition unit, used to acquire control order information for the settlement request;

[0036] The settlement type update unit is used to update the control type of the control order information to the settlement type according to the settlement release control order;

[0037] The control status update unit is used to update the control status to the control completion status if the settlement release amount is equal to the control amount.

[0038] In some embodiments of this application, based on the above technical solutions, the second request receiving module includes:

[0039] The first revenue sharing and decontrollability request receiving unit is configured to receive a first revenue sharing and decontrollability request when a revenue sharing request for the control order information is completed, wherein the first revenue sharing and decontrollability request carries a business revenue sharing identifier and the business amount, and the business amount is the amount in response to the revenue sharing request;

[0040] The second logic call module includes:

[0041] The revenue sharing logic invocation unit is used to invoke the business processing logic corresponding to the business revenue sharing identifier to create a revenue sharing release order, wherein the revenue sharing release order includes a revenue sharing document identifier and the business amount.

[0042] In some embodiments of this application, based on the above technical solutions, the control order information includes the control amount; the second logic call module further includes:

[0043] The second revenue sharing release request receiving unit is used to receive a second revenue sharing release request sent by the target device, wherein the second revenue sharing release request carries the revenue sharing document identifier and the revenue sharing amount;

[0044] The split account release control unit is used to release control over the split account amount in the control order information according to the second split account release request;

[0045] The revenue sharing amount sending unit is used to send the revenue sharing amount to the target device.

[0046] In some embodiments of this application, based on the above technical solutions, the revenue splitting and release control unit includes:

[0047] The first revenue sharing decontrol subunit is used to release control on the revenue sharing amount in the control order information if the sum of the revenue sharing amount carried in the second revenue sharing decontrol request and the business amount in the first revenue sharing decontrol request is less than or equal to the control amount in the control order information.

[0048] The second revenue sharing decontrol subunit is used to release the control over the control amount in the revenue sharing decontrol request if the sum of the revenue sharing amount carried in the second revenue sharing decontrol request and the business amount in the first revenue sharing decontrol request is greater than the control amount in the control order information.

[0049] In some embodiments of this application, based on the above technical solutions, the second request receiving module includes:

[0050] A refund release request receiving unit is used to receive a refund release request when a refund request for the control order information is completed, wherein the refund release request carries a business refund identifier and a refund release amount, and the refund release amount is the amount in response to the refund request;

[0051] The second logic call module includes:

[0052] The refund logic invocation unit is used to invoke the business processing logic corresponding to the business refund identifier to create a refund release order, wherein the refund release order includes a refund document identifier and the refund release amount.

[0053] In some embodiments of this application, based on the above technical solutions, the control order information includes the amount under control; the second logic call module further includes:

[0054] The refund control order acquisition unit is used to acquire the control order information corresponding to the refund request;

[0055] The refund amount update unit is used to update the amount under control in the control order information according to the refund release amount.

[0056] In some embodiments of this application, based on the above technical solutions, the control order information further includes the amount already released; the refund release order further includes the release status; the second logic call module further includes:

[0057] A refund result receiving unit is used to receive a refund result notification sent by the target device, wherein the refund result notification carries the refund document identifier and the refund amount;

[0058] The refund status update unit is used to update the release status in the refund release form to the release success status if the refund result notification indicates that the refund was successful.

[0059] The refund amount update unit is used to record the refund amount in the refund release order and update the amount under release and the amount already released in the control order information according to the refund amount.

[0060] In some embodiments of this application, based on the above technical solutions, the second request receiving module includes:

[0061] A withdrawal release request receiving unit is configured to receive a withdrawal release request when a withdrawal request for the control order information is completed, wherein the withdrawal release request carries a business withdrawal identifier and a withdrawal release amount, and the withdrawal release amount is the amount in response to the withdrawal request;

[0062] The second logic call module includes:

[0063] The withdrawal logic invocation unit is used to invoke the business processing logic corresponding to the business withdrawal identifier to create a withdrawal release order, wherein the withdrawal release order includes a withdrawal document identifier and the withdrawal release amount.

[0064] According to one aspect of the embodiments of this application, an electronic device is provided, the electronic device including: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to perform the business processing method as described above by executing the executable instructions.

[0065] According to one aspect of the embodiments of this application, a computer-readable storage medium is provided, on which a computer program is stored, which, when executed by a processor, implements the business processing method as described in the above technical solutions.

[0066] According to one aspect of the embodiments of this application, a computer program product or computer program is provided, which includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the business processing methods provided in the various optional implementations described above.

[0067] In the embodiments of this application, a first business processing request sent by a business module is first received. This request includes a first business type identifier and a business amount. Then, the business processing logic corresponding to the first business type identifier is invoked to create control order information corresponding to the business amount. Next, a second business request for the control order information is received, and the corresponding logic is invoked to create decontrol order information to decontrol the business amount. Finally, the business processing result is fed back to the business module based on the control order information and the decontrol order information. Through this method, when a business module needs to manage funds, it requests the management service module, which then generates control order information and decontrol order information to control and decontrol the flow of funds. This enables unified management of funds, avoids competition among different business modules for the same fund management, and improves the operational efficiency of the fund management process.

[0068] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and do not limit this application. Attached Figure Description

[0069] 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. It is obvious that the drawings described below are merely some embodiments of this application, and those skilled in the art can obtain other drawings based on these drawings without any inventive effort. In the drawings:

[0070] Figure 1 The schematic diagram illustrates an exemplary system architecture of the technical solution of this application in an application scenario;

[0071] Figure 2 This is a schematic diagram of the overall architecture of the fund management system in the embodiments of this application;

[0072] Figure 3 This is a schematic flowchart of the business processing method in the embodiments of this application;

[0073] Figure 4 This is a schematic flowchart illustrating the payment control process in the embodiments of this application;

[0074] Figure 5 This is a schematic flowchart illustrating the settlement control process in the embodiments of this application;

[0075] Figure 6 This is a schematic flowchart illustrating the revenue sharing control process in the embodiments of this application;

[0076] Figure 7 This is a schematic flowchart illustrating the refund control process in the embodiments of this application;

[0077] Figure 8 This is a schematic flowchart illustrating the withdrawal control process in the embodiments of this application;

[0078] Figure 9 A schematic block diagram of the service processing apparatus in an embodiment of this application is shown.

[0079] Figure 10 A schematic diagram of the structure of a computer system suitable for implementing the electronic device of the present application is shown. Detailed Implementation

[0080] Exemplary embodiments will now be described more fully with reference to the accompanying drawings. However, these exemplary embodiments can be implemented in many forms and should not be construed as limited to the examples set forth herein; rather, they are provided to make this application more comprehensive and complete, and to fully convey the concept of the exemplary embodiments to those skilled in the art.

[0081] Furthermore, the described features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. Numerous specific details are provided in the following description to give a thorough understanding of embodiments of this application. However, those skilled in the art will recognize that the technical solutions of this application can be practiced without one or more of the specific details, or other methods, components, apparatuses, steps, etc., can be employed. In other instances, well-known methods, apparatuses, implementations, or operations are not shown or described in detail to avoid obscuring various aspects of this application.

[0082] The block diagrams shown in the accompanying drawings are merely functional entities and do not necessarily correspond to physically independent entities. That is, these functional entities can be implemented in software, in one or more hardware modules or integrated circuits, or in different network and / or processor devices and / or microcontroller devices.

[0083] The flowcharts shown in the accompanying drawings are merely illustrative and do not necessarily include all content and operations / steps, nor do they necessarily have to be performed in the described order. For example, some operations / steps can be broken down, while others can be combined or partially combined; therefore, the actual execution order may change depending on the specific circumstances.

[0084] It should be understood that the solution presented in this application can be applied in the computer field, specifically in payment scenarios for enterprises or merchants. Specifically, in such scenarios, after the payer's funds enter the transaction system, there are multiple fund flows. For example, settlement, allocation, and withdrawal will cause funds to flow into the enterprise or merchant's account, while a refund will cause funds to flow into the user's account that made the payment. The funds available for each of these fund flows are mutually exclusive. For instance, for a single fund, the processes of settlement and allocation are mutually exclusive. If settlement is performed first, the allocation process requires competing for management rights over that fund. Only after gaining management rights can the funds be allocated. The solution presented in this application uses a management service module to uniformly manage funds based on requests from various business modules. This eliminates the need for competition among business modules for funds, saving system resources consumed by fund competition and improving the operational efficiency of the fund management process. It is understood that the solution proposed in this application can also be used in other scenarios, such as the transaction process or simulated transaction process of various virtual resources. As long as multiple businesses are involved in controlling the flow of the same resource, the solution proposed in this application can be applied.

[0085] To achieve more efficient fund management in the aforementioned scenarios, this application proposes a business processing method, which is applied to... Figure 1 Please refer to the business processing system shown. Figure 1 , Figure 1 The diagram illustrates an exemplary system architecture of the technical solution of this application in an application scenario. This business processing system includes a server and terminal devices. The aforementioned business processing method can be executed by a business processing device or service on the server, or by a terminal device with strong computing power.

[0086] Among them, such as Figure 1 As shown, the aforementioned terminal devices include, but are not limited to, tablets, laptops, PDAs, mobile phones, voice interaction devices, and personal computers (PCs), etc., without limitation here. Among them, voice interaction devices include, but are not limited to, smart speakers and smart home appliances. In some implementations, the client can be a web client or an application-type client, deployed on the aforementioned terminal devices. Figure 1 The server mentioned can be a single server, a server cluster consisting of multiple servers, or a cloud computing center, etc., and there are no specific restrictions here.

[0087] Although Figure 1 Only five terminal devices and one server are shown, but it should be understood that... Figure 1 The examples provided are for understanding this solution only; the actual number of terminal devices and servers should be determined flexibly based on the specific circumstances.

[0088] This application introduces a business processing method to solve the problem of competition among multiple business modules during fund management. For details, please refer to the overall architecture of the fund management system. Figure 2 , Figure 2 This is a schematic diagram of the overall architecture of the funds management system in an embodiment of this application. Figure 2 As shown, the funds management system includes a management service module and five business modules: payment, settlement, account splitting, withdrawal, and refund. Each business module handles different transactions during the payment process, while the management service module provides fund management functionality. The management service module creates fund control orders or fund release orders based on requests from the business modules. Fund control orders manage scenarios where funds flow into the account, such as payments or settlements. Fund release orders manage scenarios where funds flow out of the account, such as account splitting, withdrawals, or refunds. For each control order, when funds flow out concurrently, the management service module must also ensure that the total funds flowing out of the account do not exceed the control limit for that control order.

[0089] During business operations, when various business modules need to manage funds, they send management requests to the management service module based on their respective business documents. The management service module then creates corresponding management and release orders based on the needs of the business modules to manage the funds. Specifically, for example... Figure 2 As shown, during the payment process, the payment module assigns a core payment order to each payment order, while the management service module creates a fund control order for each core payment order to manage funds. Each fund control order can correspond to multiple release orders. The settlement module creates a core settlement order or a core reverse settlement order based on whether the payment funds are for forward or reverse settlement. The management service module creates corresponding forward or reverse settlement release orders based on the settlement module's request to release the requested funds. The revenue sharing module creates a master revenue sharing control order for each payment order, which controls that the cumulative revenue sharing amount for the same payment order cannot exceed the payment order amount. A payment order can be shared multiple times; for each revenue sharing request, the revenue sharing module creates a corresponding revenue sharing instruction order. A revenue sharing instruction order can include multiple revenue sharing detail orders. The management service module creates a revenue sharing release order for each revenue sharing detail order to release the funds. The refund module creates a master refund control order for each payment order, and each refund request corresponds to a core refund order. A single payment can be refunded multiple times. A master refund control order is used to ensure that the total refund amount for the same payment order does not exceed the order amount. The management service module creates a refund release order for each core refund order based on requests from the refund module, releasing the requested refund amount. The withdrawal module creates a core withdrawal order for each withdrawal request. The management service module then releases the funds based on the corresponding withdrawal release order for each core withdrawal order.

[0090] More specifically, the service processing device can be a client deployed on a terminal device, such as all the clients shown in the examples of the application scenarios described above. In this case, the server can send the service processing device to the terminal device via a wireless network. The service processing device can also be a terminal device specifically designed for service processing. In this case, the server can configure the service processing device on the terminal device via a wired network or mobile storage medium after generating the service processing device. Alternatively, the service processing device can be deployed on a server. In this case, after the terminal device receives a service request, it sends the request to the server, which then performs the service processing operation and sends it back to the terminal device. This application uses the example of a service processing device deployed on a server for illustration, but this should not be construed as a limitation of this application. Furthermore, the aforementioned wireless network uses standard communication technologies and / or protocols. The wireless network is typically the Internet, but can also be any network, including but not limited to Bluetooth, a Local Area Network (LAN), a Metropolitan Area Network (MAN), a Wide Area Network (WAN), mobile, private networks, or any combination of virtual private networks. In some embodiments, custom or dedicated data communication technologies may be used to replace or supplement the aforementioned data communication technologies.

[0091] Based on the above description, the technical solution provided in this application will be described in detail below with reference to specific embodiments. Please refer to [link / reference]. Figure 3 , Figure 3 This is a schematic flowchart illustrating the business processing method in an embodiment of this application. The business processing method in this embodiment is applied to a business processing system, which includes a management service module and at least two business modules. The business processing method specifically includes the following steps:

[0092] Step S310: Receive a first service processing request, wherein the service processing request includes a first service type identifier and a service amount;

[0093] The first business processing request is a request to initiate a corresponding business transaction. This request can be generated by a business module after performing corresponding logical or communication processes according to the business flow, and is used to notify the management service module to control the corresponding fund flow. Alternatively, the first business processing request can be a request sent by a business module to initiate the payment system's business process. After receiving the first business processing request, the system first provides the business module with the business logic processing, and then the business module cooperates with the management service module to control the fund flow. The first business processing request includes a first business type identifier and a business amount. The first business type identifier indicates the specific type of business involved, such as identifying payment and settlement transactions. The business amount is the amount involved in the first business processing request, such as the payment amount or settlement amount. It is understood that the business modules originate from at least two business modules within the business processing system.

[0094] Step S320: Invoke the business processing logic corresponding to the first business type identifier to create control order information corresponding to the business amount, wherein the control order information is used to control the flow of the business amount.

[0095] Depending on the business type identifier, the corresponding business processing logic can be invoked. The business processing logic defines how the business processing system or management service module handles business processing requests, thereby creating control order information corresponding to the business amount. This control order information is used to control the flow of business funds. Specifically, control order information includes control information used to lock the business amount transferred into the system. Control information is typically created during each payment process, with one control order created for each payment. Control information is used to restrict the flow of funds to either party's account in the transaction. A single fund is typically locked by one control order, even if the corresponding transaction consists of multiple transactions. For example, a transaction that includes different goods purchased from multiple merchants can also be locked by a single control order during the payment process.

[0096] Step S330: Receive a second business processing request for the control order information, wherein the second business processing request includes a second business type identifier and the business amount.

[0097] The second business processing request serves the same purpose as the first business data request; it is also a request to initiate the corresponding business transaction. This second business processing request can be generated by a business module after performing corresponding logical or communication processes according to the business flow, and is used to notify the management service module to release control over the corresponding fund flow. Alternatively, the second business processing request can be a request sent by a business module to initiate the payment system's business process. After receiving the second business processing request, the system first provides the business module with the business logic processing, and then, through cooperation between the business module and the management service module, releases control over the fund flow. The second business processing request includes a second business type identifier and a business amount. The second business type identifier indicates the specific type of business involved, such as settlement, splitting accounts, withdrawal, or refund. The business amount is the amount involved in the second business processing request, such as the settlement amount or withdrawal amount. It is understood that the business modules originate from at least two business modules within the business processing system.

[0098] Step S340: Invoke the business processing logic corresponding to the second business type identifier to create a release order information corresponding to the business amount, wherein the release order information is used to release the flow of the business amount.

[0099] Based on the different business type identifiers, corresponding business processing logic can be invoked. Business processing logic defines the processing procedure of the business processing system or management service module for business processing requests, thereby creating release control order information corresponding to the business amount. Release control order information is used to release control over the flow of business funds. Specifically, release control order information includes release control information used to unlock business funds transferred into the system, allowing them to be transferred out to the user's account. Release control information is typically created during each settlement, refund, or withdrawal process, with one release control order created for each settlement. Release control information can be used to transfer funds to the account of either party in the transaction; for example, settlement transactions transfer funds to the payee's account, while refunds transfer transaction funds to the payer's account. A single fund is typically locked by one control order, but can be released in batches by multiple release control orders. For example, if only a portion of the goods in a transaction are sold, the settlement process for the sold portion will generate a control order containing release information to release the amount of the sold goods, which will then be transferred to the payee's account. For the unsold goods, the refund process will generate a processing order containing release information to release the amount of the unsold goods, which will then be refunded to the payer's account.

[0100] Step S350: Feedback the business processing result based on the control order information and the decontrol order information.

[0101] Specifically, funds can be controlled or released based on control and release order information, and the results are sent to the business module. This includes information such as whether the control or release was successful or failed, and the relevant amounts. Further processing is then performed according to the business logic. For example, the system can release funds based on the release order information, update the relevant status and records of the control and release order information, transfer the released funds to the payee's account, and feed the transfer result back to the business module as the business processing result.

[0102] In the embodiments of this application, a first business processing request sent by a business module is first received. This request includes a first business type identifier and a business amount. Then, the business processing logic corresponding to the first business type identifier is invoked to create control order information corresponding to the business amount. Next, a second business request for the control order information is received, and the corresponding logic is invoked to create decontrol order information to decontrol the business amount. Finally, the business processing result is fed back to the business module based on the control order information and the decontrol order information. Through this method, when a business module needs to manage funds, it requests the management service module, which then generates control order information and decontrol order information to control and decontrol the flow of funds. This enables unified management of funds, avoids competition among different business modules for the same fund management, and improves the operational efficiency of the fund management process.

[0103] In the embodiments of this application, based on the above technical solution, step S310, receiving the first service processing request, specifically includes the following steps:

[0104] When a payment request is completed, a payment control request is received, wherein the payment control request carries a business payment identifier and the business amount, and the business amount is the amount in response to the payment request;

[0105] Step S320 above involves invoking the business processing logic corresponding to the business type identifier to create control order information corresponding to the business amount, including:

[0106] The business processing logic corresponding to the business payment identifier is invoked to create a payment control order, wherein the payment control order includes a payment document identifier and the business amount.

[0107] This embodiment describes the specific control method for the payment process, with the payment module being the specific business module. Upon receiving a payment request, the payment module processes it according to the payment business logic. For a clearer explanation, please refer to [link to documentation]. Figure 4 , Figure 4 This is a schematic flowchart illustrating the payment control process in an embodiment of this application. Figure 4As shown, in step 401, the payment module first makes payment based on the payment request. After payment, in step 402, it sends information to the channel integration service to trigger the channel payment and settlement process. After the channel payment process, in step 403, the channel integration service initiates a payment completion request to the payment module. At this time, the business module completes the payment request and sends a payment control request to the service management module in step 404. The payment control request carries a business payment identifier and the business amount. The business amount is the amount in response to the payment request. Specifically, the business payment identifier is used to identify the payment business, such as characters or specific numbers. The business amount is the amount to be paid in this payment process. For example, if the purchase of goods requires a payment of 500 yuan, then the business amount is 500 yuan. Then, in step 405, the service management module calls the business processing logic corresponding to the business payment identifier to create a payment control order. Specifically, the payment control order includes a document identifier and a business amount. The document identifier is used to identify the payment control order. For example, the content of the payment control order may include the fields in the following table.

[0108] Table 1 Control Order

[0109]

[0110]

[0111] The control order ID is the document identifier for a control order, used to uniquely identify a control order; the total control amount represents the total amount of the payment; the control rule indicates the control method executed on this amount, where different decontrol processes correspond to different control methods; the original transaction ID corresponding to the control order represents the identification information of the payment request corresponding to the payment control order; the original transaction type corresponding to the control order represents the transaction type of the payment request corresponding to the payment control order, usually payment or calculation; the current control type is the type of the ongoing decontrol process, such as settlement, splitting accounts, and withdrawal; the decontrolled amount represents the amount that has been decontrolled in this payment control order, which has usually been transferred to the target account; the amount under decontrol represents the amount that is being decontrolled, which has usually not yet been transferred to the user's account; the control order status represents the overall status of the control order, which will be updated to decontrol completed when all amounts have been decontrolled. It is understood that a payment control order does not necessarily need to include all the fields in the above table, and the content of the payment control order can vary depending on specific requirements. In step 405, the service management module has already locked the business funds based on the payment control order. Afterwards, the service management module waits for the locked funds to be released and further transferred out in other business scenarios or processes.

[0112] In the embodiments of this application, a specific method is provided to call business logic in a payment scenario to create a payment control order, thereby controlling the amount of business involved in the payment process. By using the payment control order, the information on locking the amount of business can be made independent from the business information, and the fund control information can be managed separately, thereby improving the overall management efficiency.

[0113] In the embodiments of this application, based on the above technical solution and the above steps, after calling the business processing logic corresponding to the business payment identifier to create a payment control order, the method further includes:

[0114] Receive a payment release request sent by the target device, wherein the payment release request carries the payment document identifier and the release amount;

[0115] According to the payment release request, the control over the release amount or the transaction amount in the payment control order is released.

[0116] The amount to be released or the amount of the service will be sent to the target device.

[0117] Specifically, after a transaction amount is locked based on a payment control order, other devices can unlock that locked amount in other scenarios. Specifically, the user can send a payment unlock request to the system through the target device. This request carries a document identifier and the unlock amount. Specifically, payment unlock requests are typically triggered in other business scenarios; for example, after a user confirms receipt of goods, a continued payment process or a separate settlement process is triggered. Taking settlement as an example, the target device triggers a settlement process for the payment transaction. During settlement, the settlement module generates a payment unlock request based on the document identifier of the payment control order and the unlock amount involved in the settlement process, and sends it to the management service module. It is understood that the unlock amount must be less than or equal to the transaction amount; that is, the amount to be unlocked cannot exceed the amount locked in the payment control order. The management service module will release control on the unlock amount or transaction amount in the payment control order based on the payment unlock request. Specifically, the release method can include recording the relevant unlock amount in the payment control order. Afterwards, the management service module will send the unlock amount or transaction amount to the target device. The target device can then perform further operations based on the received release amount or transaction amount. In one embodiment, the management service module can also directly transfer the release amount or transaction amount based on the payment release request, and the release amount or transaction amount is included in the transfer result notification information sent to the target device.

[0118] In the solution proposed in this application, the target device can submit a payment release request to the payment control order to release the funds of the release amount. This allows different business processes to control the same fund separately based on information from the same source, unifying the data source of the same fund, avoiding data conflicts and maintenance difficulties caused by data from different sources, and reducing the error rate of system operation.

[0119] In the embodiments of this application, based on the above technical solution, the above steps, according to the payment release request, to release the control over the release amount or the transaction amount in the payment control order, specifically include the following steps:

[0120] If the amount to be released in the payment release request is less than or equal to the transaction amount in the payment control order, then the control on the amount to be released in the payment control order is lifted.

[0121] If the amount to be released in the payment release request is greater than the transaction amount in the payment control order, then the transaction amount in the payment control order will be released from control.

[0122] Specifically, if the amount to be released in the payment release request is less than or equal to the business amount in the payment control order, it indicates that the amount requested for release in the payment release request is reasonable and can be released. The service management module will then release the control on the amount to be released in the payment control order. Specifically, if the amount to be released is less than the business amount, further verification can be performed on the amount to be released and the business amount based on payment verification conditions. For example, the amount to be released and the business amount need to meet a specific ratio, or the amount remaining after subtracting the amount to be released from the business amount needs to be greater than a certain preset amount. Only after verification is passed will the amount to be released be released. If the amount to be released in the payment release request is greater than the business amount in the payment control order, it indicates that the amount to be released in the payment release request is incorrect. In this case, the control on the business amount in the payment control order will be released. In one embodiment, the business amount in the payment control order will first be calculated, i.e., it will be verified whether the payment control order has been released before. If a portion of the amount has already been released, the portion that has already been released will first be subtracted from the business amount before being compared with the current amount to be released.

[0123] In the embodiments of this application, a specific implementation method is provided for unlocking the amount or business amount in the payment control order according to the payment unlocking request. The amount is unlocked according to the relationship between the amount to be unlocked and the locked business amount, allowing only a portion of the amount to be unlocked, thereby enabling two unlockings of a locked amount, increasing the flexibility of fund control and unlocking process.

[0124] In the embodiments of this application, based on the above technical solution, step S330, receiving a second service processing request for the control order information, specifically includes the following steps:

[0125] When a settlement request for the control order information is completed, a settlement release request is received, wherein the settlement release request carries a business settlement identifier and a settlement release amount, and the settlement release amount is the amount in response to the settlement request;

[0126] Step S340 above involves invoking the business processing logic corresponding to the second business type identifier to create release order information corresponding to the business amount, including:

[0127] The business processing logic corresponding to the business settlement identifier is invoked to create a settlement release order, wherein the settlement release order includes a settlement document identifier and the settlement release amount.

[0128] This embodiment describes the specific control method for the settlement process, with the business module specifically being the settlement module. Upon receiving a settlement request, the settlement module processes the request according to the settlement business logic. For a clearer explanation, please refer to [link to documentation]. Figure 5 , Figure 5 This is a schematic flowchart illustrating the settlement control process in an embodiment of this application. Figure 5 As shown, in step 501, the channel integration service sends a settlement completion notification to the settlement module after a payment process is completed. Subsequently, in step 502, the settlement module updates the status of the payment process to settlement completion. At this point, the business module completes the settlement request and then, in step 503, directly sends a settlement release request to the service management module for settlement release. The settlement release request carries a business settlement identifier and a settlement release amount, where the business settlement identifier represents the settlement business. The settlement release amount is the amount requested to be released in the settlement release request. In step 504, the service management module creates a settlement release order based on the settlement release request. The settlement release order includes a document identifier and a settlement release amount. Specifically, the document identifier is used to identify the settlement release order. For example, the content of the release order may include the fields in the table below.

[0129] Table 2 Release Form

[0130]

[0131]

[0132] Among them, the release control order ID is the document identifier of the release control order; the release control order type indicates the business type that created the release control order; the corresponding control order ID represents the document identifier of the control order to which the release control order is targeted; the business order ID of the corresponding type that initiated the release control indicates the identifier information of the release control request corresponding to the release control order; the business order amount that initiated the release control indicates the amount requested to be released in the release control request; the actual release control amount of the release control system represents the amount actually unlocked after the release control process. It can be understood that this amount is not necessarily equal to the amount of the business order that initiated the release control; the release control order status is determined according to the release control order. It can be understood that the settlement release control order does not necessarily have to include all the fields in the above table, and the content of the settlement release control order can vary depending on specific needs. In step 504, the service management module has already unlocked the released funds according to the settlement release control order. Afterwards, the service management module can further process the subsequent transfer of the released funds, or notify the business module to perform the corresponding transfer operation.

[0133] In the embodiments of this application, a specific method is provided to call business logic in the settlement scenario to create a settlement release order, thereby releasing the business amount involved in the settlement process. In this way, the release process of funds can leave independent record information without being bound to transaction information, so that the release history of funds can be traced separately and the flexibility of system management can be improved.

[0134] In the embodiments of this application, based on the above technical solution, the control order information includes the control amount, control type, and control status; after the above steps of calling the business processing logic corresponding to the business settlement identifier to create a settlement release order, the method further includes the following steps:

[0135] Obtain the control order information targeted by the settlement request;

[0136] Based on the settlement release order, update the control type of the control order information to the settlement type;

[0137] If the settlement release amount equals the control amount, the control status is updated to release completed.

[0138] The control order information can be established by referring to the above-described payment control order example. When the settlement module makes a settlement request, the settlement request will include information about the control order information targeted by the settlement, such as the document identifier of the control order information. The control type is used to indicate the type of business currently being decontrolled, and the control status is used to indicate whether the control order information has been decontrolled. After calling the business processing logic corresponding to the business settlement identifier to create a settlement decontrol order, the service management module obtains the control order information targeted by the settlement request. Specifically, the settlement request is made for control order information, which usually includes the identification information of the control order information, such as the document identifier. The service management module obtains the control order information targeted by the settlement operation based on the document identifier of the control order information. Based on the settlement decontrol order, the service management module updates the control type of the control order information to the settlement type. The control type varies depending on the specific business; for example, the control type corresponding to the refund process is the refund type. The service management module compares the settlement decontrol amount with the control amount. If the settlement release amount equals the control amount, it means that all amounts in the control order information have been released. In this case, the control status of the control order information is updated to "release completed". Otherwise, the current status of the control order information can be maintained, or the control status can be updated to "controlling". It's understandable that the control amount is the amount currently still under control in the control order information. This amount will change based on the amount released. For example, in a control order information with a total amount of 500 yuan, after 300 yuan is released, the control amount will be 200 yuan.

[0139] In the embodiments of this application, after the decontrol process, the control type and control status of the corresponding control order information are updated, thereby enabling information exchange between the decontrol process and the control process. The current decontrol status can be directly determined through the information in the control order information, saving the amount of query calculation for the decontrol status and improving the system operating efficiency.

[0140] In the embodiments of this application, based on the above technical solution, step S330, receiving a second service processing request for the control order information, specifically includes the following steps:

[0141] When a splitting request for the control order information is completed, a first splitting release request is received, wherein the first splitting release request carries a business splitting identifier and the business amount, and the business amount is the amount in response to the splitting request;

[0142] Step S320 above involves invoking the business processing logic corresponding to the second business type identifier to create release order information corresponding to the business amount, including:

[0143] Invoke the business processing logic corresponding to the business accounting identifier to create an accounting control release order, wherein the accounting control release order includes the accounting document identifier and the business amount.

[0144] This embodiment describes the specific control method for the revenue sharing process, with the revenue sharing module being the business module. Upon receiving a revenue sharing request, the revenue sharing module processes the data according to the revenue sharing business logic. For a clearer explanation, please refer to [link to documentation / reference]. Figure 6 , Figure 6 This is a schematic flowchart illustrating the revenue sharing control process in an embodiment of this application. Figure 6 As shown, in step 601, the revenue sharing module first adds a revenue sharing instruction form and a revenue sharing detail form, and checks and updates the revenue sharing master control form. If the check passes, the revenue sharing module completes the revenue sharing request. In step 602, the revenue sharing module sends a first revenue sharing decontrol request to the service management module. At this time, the service management module receives the revenue sharing decontrol request sent by the revenue sharing module. The first revenue sharing decontrol request carries a business revenue sharing identifier and a business amount. The business revenue sharing identifier is used to mark the revenue sharing business, and the business amount is the amount requested in the revenue sharing request, that is, the amount to be shared in the revenue sharing request. For example, if the revenue sharing request requests a revenue sharing of 300 yuan for a payment of 500 yuan, then the business amount is 300 yuan. In step 603, the service management module calls the business processing logic corresponding to the business revenue sharing identifier to create a revenue sharing decontrol form. Specifically, the revenue sharing decontrol form is created through a transaction, and the content of the revenue sharing decontrol form can include some or all of the fields in the decontrol form table mentioned above. A deregulation release order and a deregulation request are typically issued for a single payment. In step 603, the service management module updates the deregulation amount in the deregulation control order information for that payment. Subsequently, the service management module notifies the deregulation module to process the deregulated funds. In step 604, the deregulation module calls the channel transfer interface to process the funds through the channel transfer service. In step 605, after the channel transfer service performs the transfer operation, the deregulation service sends a callback with the channel transfer result. In step 606, the deregulation module determines whether to submit or cancel the deregulation based on the transfer result. Submission confirms a successful transfer, while cancellation indicates a failed transfer. In step 607, the management service module updates the status of the deregulation release order and the deregulated amount in the transaction, and also updates the deregulation amount in the deregulation control order information for the deregulation request. Specifically, if the transfer is successful, the status of the account uncontrollability release order is updated to "uncontrollability successful," and the actual uncontrollable amount in the uncontrollability release system is updated to the requested account uncontrollability amount. Correspondingly, the amount under uncontrollability in the control order information is updated to 0, while the uncontrollable amount is added to the already uncontrollable amount. If the transfer fails, the status of the account uncontrollability release order is updated to "uncontrollability failed," and the actual uncontrollable amount in the uncontrollability release system is updated to 0. Correspondingly, the amount under uncontrollability in the control order information is updated to 0, while the already uncontrollable amount remains unchanged.

[0145] In the embodiments of this application, the fund release process in the splitting process is managed by creating a splitting release order, which improves the traceability of the release process in the splitting business and allows the release of only the amount to be split, thereby avoiding conflicts with other businesses and improving system operating efficiency.

[0146] In the embodiments of this application, the control order information based on the above technical solution includes the control amount; after the above steps, which involve calling the business processing logic corresponding to the business account identifier to create an account release control order, the method further includes:

[0147] Receive a second split account release request sent by the target device, wherein the second split account release request carries a split account document identifier and a split account amount;

[0148] Based on the second request to release control of the sub-account, control is released on the sub-account amount in the control order information;

[0149] Send the revenue share to the target device.

[0150] In this embodiment, the revenue sharing request targets the control order information, and multiple revenue sharing requests can be made for the same control order information. Specifically, the target device can make a second revenue sharing release request for the control order information. The second revenue sharing release request carries a document identifier and a revenue sharing amount. The document identifier identifies the second revenue sharing release request, and the revenue sharing amount is the amount of the second revenue sharing. For example, for a control order information of 500 yuan, where 300 yuan has already been shared, the revenue sharing amount carried in the second revenue sharing release request will be 200 yuan or less. The service management module releases control over the revenue sharing amount in the control order information based on the second revenue sharing request. Specifically, the release method is the same as the release method using a revenue sharing release request in the above embodiment, and will not be repeated here. After the release is completed, the revenue sharing amount is sent to the target device, which then performs subsequent transfer operations and result updates.

[0151] In the embodiments of this application, a specific implementation process for splitting the same funds is provided. By making multiple splitting and decontrolling requests, multiple splitting and decontrolling orders are established to split the same funds, so that multiple splitting requests can be processed in parallel, increasing the flexibility of the splitting business.

[0152] In the embodiments of this application, based on the above technical solution, the above steps, according to the second account release request, to release control on the account amount in the control order information, include:

[0153] If the sum of the revenue amount carried in the second revenue release request and the business amount in the first revenue release request is less than or equal to the control amount in the control order information, then the control on the revenue amount in the control order information is lifted.

[0154] If the sum of the revenue amount carried in the second revenue release request and the business amount in the first revenue release request is greater than the control amount in the control order information, then the control amount in the revenue release order is released from control.

[0155] Specifically, if the amount requested for deregulation in the second deregulation request is less than or equal to the control amount in the control order information compared to the business amount in the first deregulation request, it indicates that the amount requested for deregulation in the second deregulation request is reasonable and eligible for deregulation. The service management module will then release the control on the amount in the control order information. Specifically, the control amount in the control order information is the total control amount in the control order information. If the amount is less than the control amount, further verification can be performed on the amount and control amount based on payment verification conditions. For example, the amount and control amount may need to meet a specific ratio, or the remaining amount after subtracting the amount from the control amount may need to be greater than a certain preset amount. Only after successful verification will the control on the amount be released. If the sum of the amount requested for deregulation in the second deregulation request and the business amount in the first deregulation request is greater than the control amount in the control order information, it indicates that the amount requested for deregulation in the second deregulation request is incorrect. In this case, the control on the amount in the control order information will be released. Understandably, if the control order information targeted by the splitting request has been split multiple times before, the release of control will be checked based on the results of the multiple splitting requests. That is, the sum of the splitting amount proposed in this splitting request and the amounts of the previous splitting requests must be less than or equal to the control amount in the control order information before control can be released.

[0156] In the embodiments of this application, specific access control methods for multiple account splitting and decontrolling requests are provided, which improves the operability of the solution.

[0157] In the embodiments of this application, based on the above technical solution, step S330, receiving a second service processing request for the control order information, specifically includes the following steps:

[0158] When a refund request for the aforementioned control order information is completed, a refund release request is received, wherein the refund release request carries a business refund identifier and a refund release amount, and the refund release amount is the amount responded to in the refund request;

[0159] Step S340 above involves invoking the business processing logic corresponding to the second business type identifier to create release order information corresponding to the business amount, including:

[0160] Invoke the business processing logic corresponding to the business refund identifier to create a refund release order, wherein the refund release order includes a refund document identifier and the refund release amount.

[0161] This embodiment describes the specific control method for the refund process, with the business module specifically being the refund module. Upon receiving a refund request, the refund module processes it according to the refund business logic. For clarity, please refer to [link to relevant documentation]. Figure 7 , Figure 7 This is a schematic flowchart illustrating the refund control process in an embodiment of this application. Figure 7 As shown, in step 701, the refund module submits a refund release request directly to the management service module based on the refund request. In step 702, the service management module receives the refund release request sent by the business module, which carries a business refund identifier and a refund release amount. The business refund identifier is used to mark the refund business, and the business amount is the amount requested in the refund request, i.e., the amount to be refunded in the refund request. For example, if a refund request requests a refund of 300 yuan for a payment of 500 yuan, the business amount is 300 yuan. The service management module also updates the release amount in the payment control order for this payment. Subsequently, the service management module notifies the refund module to process the released funds. In step 703, the refund module prepares the refund funds and performs operations such as settlement of handling fees based on the control type returned by the service management module. After the calculation is completed, in step 704, the refund module triggers a channel refund to the channel integration service. In step 705, after the channel refund service performs the refund operation, the refund service will call back the channel refund result. In step 706, the refund module determines whether to submit or cancel the decontrol request based on the refund result. Submission confirms a successful refund, while cancellation indicates a failed refund. In step 707, the management service module updates the status of the refund decontrol order and the amount decontrolled in the transaction, and also updates the amount under decontrol and the amount decontrolled in the payment control order targeted by the refund request. Specifically, if the refund is successful, the status of the refund decontrol order is updated to "Decontrol Successful," the actual decontrolled amount in the decontrol system is updated to the requested refund amount, and correspondingly, the amount under decontrolled in the payment control order is updated to 0, while the refund amount is added to the amount decontrolled. If the refund fails, the status of the refund decontrol order is updated to "Decontrol Failed," the actual decontrolled amount in the decontrol system is updated to 0, and correspondingly, the amount under decontrolled in the payment control order is updated to 0, while the amount decontrolled remains unchanged.

[0162] In the embodiments of this application, the fund release process during the refund is managed by creating a refund release order, which improves the traceability of the release process in the refund business and allows the release of only the amount to be distributed, thereby avoiding conflicts with other businesses and improving system operating efficiency.

[0163] In the embodiments of this application, the information on the control order based on the above-mentioned technical solution includes the amount under control; after calling the business processing logic corresponding to the business refund identifier to create a refund release order, the method further includes:

[0164] Obtain the control order information for the refund request;

[0165] Update the amount under control in the control order information based on the amount of the refund released.

[0166] Specifically, the control order information also includes management order information. The refund request is made in response to the management order information, which includes the amount being released from control. As mentioned above... Figure 7 As described, the service management module updates the information in the corresponding control order after creating a refund release order. Specifically, the refund request is made for control order information; when a user requests a refund, they select a payment order, which is associated with the control order information. Therefore, the business module adds an identifier for the control order information, such as a document identifier, to the refund request. Based on the document identifier, the service management module can obtain the control order information targeted by the refund request. Subsequently, the service management module updates the release amount in the control order information according to the refund release amount. At this point, the funds for the refund release have been unlocked, but the business module has not yet performed any related fund operations.

[0167] In this embodiment, during the refund process, the relevant data on the release of control is updated in the data of the payment process, so that the release status of funds can be found more conveniently based on the payment data, saving data search time and thus improving the maintenance efficiency of the system.

[0168] In the embodiments of this application, based on the above technical solution, the control order information also includes the amount already released; the refund release order also includes the release status; after updating the amount under release in the control order information according to the refund release amount, the method further includes:

[0169] Receive a refund result notification sent by the target device, wherein the refund result notification carries a refund document identifier and a refund amount;

[0170] If the refund result notification indicates that the refund was successful, the release status in the refund release form will be updated to the release success status;

[0171] Record the refund amount in the refund release order, and update the amount under release and the amount already released in the control order information based on the refund amount.

[0172] Specifically, as mentioned above... Figure 7 As described, after the refund amount is released from control, the information in the refund release order and control order will be further updated. Specifically, after release, the target device performs a refund operation through the channel integration service based on the release result and sends a refund result notification to the service management module. The refund result notification carries the document identifier and the refund amount. The document identifier is the identifier of the refund release order, while the refund amount is the actual amount in the refund process. If the refund result notification indicates that the refund is successful, the service management module updates the release status in the refund release order to a successful release status. If the refund result notification indicates that the refund fails, the service management module updates the release status in the refund release order to a failed release status. Subsequently, the refund amount is recorded in the refund release order, and the amount under release and the amount already released in the control order information are updated according to the refund amount. Specifically, if the refund is successful, the refund amount is recorded in the actual released amount, the amount under release in the corresponding control order information is updated to 0, and the refund amount is added to the amount already released. If the refund fails, the actual amount released will be updated to 0, the amount in the corresponding control order information will be updated to 0, and the existing amount of the released amount will be maintained.

[0173] In the embodiments of this application, a scheme is provided for updating relevant status information and amount records in the release order status and control order status, thereby improving the operability of the scheme.

[0174] In the embodiments of this application, based on the above technical solution, step S330, receiving a second service processing request for the control order information, specifically includes the following steps:

[0175] When a withdrawal request for the aforementioned control order information is completed, a withdrawal release request is received, wherein the withdrawal release request carries a business withdrawal identifier and a withdrawal release amount, and the withdrawal release amount is the amount in response to the withdrawal request;

[0176] Step S340 above involves invoking the business processing logic corresponding to the second business type identifier to create control order information corresponding to the business amount, including:

[0177] The business processing logic corresponding to the business withdrawal identifier is invoked to create a withdrawal release order, wherein the withdrawal release order includes a withdrawal document identifier and the withdrawal release amount.

[0178] This embodiment describes the specific control method for the withdrawal process, with the withdrawal module being the specific business module. Upon receiving a withdrawal request, the withdrawal module processes it according to the withdrawal business logic. For clarity, please refer to [link to relevant documentation]. Figure 8 , Figure 8 This is a schematic flowchart illustrating the withdrawal control process in an embodiment of this application. Figure 8 As shown, in step 801, the withdrawal module submits a withdrawal release request directly to the management service module based on the withdrawal request. In step 802, the service management module receives the withdrawal release request sent by the business module, which carries a business withdrawal identifier and a release amount. The business withdrawal identifier is used to mark the withdrawal business, and the business amount is the amount requested in the withdrawal request, i.e., the amount to be withdrawn. The service management module also updates the release amount in the payment control order for this payment. Subsequently, the service management module notifies the withdrawal module to process the released funds. In step 803, the withdrawal module prepares the withdrawal funds and settles transaction fees according to the control type returned by the service management module. After the calculation is completed, in step 804, the withdrawal module triggers channel withdrawal to the channel integration service. In step 805, after the channel withdrawal service performs the withdrawal operation, the withdrawal service will call back the channel withdrawal result. In step 806, the withdrawal module determines whether to submit or cancel the decontrol order based on the withdrawal result. Submission confirms successful withdrawal, while cancellation indicates withdrawal failure. In step 807, the management service module updates the status of the withdrawal decontrol order and the amount decontrolled in the transaction, and also updates the amount under decontrol and the amount decontrolled in the payment control order targeted by the withdrawal request. Specifically, if the withdrawal is successful, the status of the withdrawal decontrol order is updated to "Decontrol Successful," the actual decontrolled amount in the decontrol system is updated to the requested withdrawal amount, and correspondingly, the amount under decontrol in the payment control order is updated to 0, while the withdrawal amount is added to the amount decontrolled. If the withdrawal fails, the status of the withdrawal decontrol order is updated to "Decontrol Failed," the actual decontrolled amount in the decontrol system is updated to 0, and correspondingly, the amount under decontrol in the payment control order is updated to 0, while the amount decontrolled remains unchanged.

[0179] In the embodiments of this application, the release of funds during the withdrawal process is managed by creating a withdrawal release order, thereby allowing the same funds to be managed in parallel with other processes during the withdrawal process, thus improving system operating efficiency.

[0180] It should be noted that although the steps of the method in this application are described in a specific order in the accompanying drawings, this does not require or imply that the steps must be performed in that specific order, or that all the steps shown must be performed to achieve the desired result. Additional or alternative steps may be omitted, multiple steps may be combined into one step, and / or one step may be broken down into multiple steps.

[0181] The following describes the implementation of the apparatus of this application, which can be used to execute the business processing methods in the above embodiments of this application. Figure 9 A schematic block diagram illustrating the composition of the service processing apparatus in an embodiment of this application is shown. For example... Figure 9 As shown, the service processing device 900 mainly includes:

[0182] The first request receiving module 910 is used to receive a first service processing request, wherein the first service processing request includes a service type identifier and a service amount;

[0183] The first logic call module 920 is used to call the business processing logic corresponding to the first business type identifier to create control order information corresponding to the business amount, wherein the control order information is used to control the flow of the business amount;

[0184] The second request receiving module 930 is used to receive a second business processing request for the control order information, wherein the second business processing request includes a second business type identifier and the business amount;

[0185] The second logic call module 940 is used to call the business processing logic corresponding to the second business type identifier to create a release order information corresponding to the business amount, wherein the release order information is used to release the flow of the business amount;

[0186] The result feedback module 950 is used to provide feedback on the business processing results based on the control order information and the decontrol order information.

[0187] In some embodiments of this application, based on the above technical solutions, the first request receiving module 910 includes:

[0188] A payment control receiving unit is configured to receive a payment control request when the payment request is completed, wherein the payment control request carries a business payment identifier and the business amount, and the business amount is the amount in response to the payment request;

[0189] The first logic call module 920 includes:

[0190] The payment logic invocation unit is used to invoke the business processing logic corresponding to the business payment identifier to create a payment control order, wherein the payment control order includes a payment document identifier and the business amount.

[0191] In some embodiments of this application, based on the above technical solutions, the first logic call module 920 further includes:

[0192] A payment release receiving unit is used to receive a payment release request sent by a target device, wherein the payment release request carries the payment document identifier and the release amount;

[0193] The release control unit is used to release control over the release amount or the transaction amount in the payment control order according to the payment release request;

[0194] The amount sending unit is used to send the unlocked amount or the service amount to the target device.

[0195] In some embodiments of this application, based on the above technical solutions, deactivating the control unit includes:

[0196] The first payment decontrol subunit is used to release control of the decontrol amount in the payment control order if the decontrol amount carried in the payment decontrol request is less than or equal to the business amount in the payment control order;

[0197] The second payment decontrol subunit is used to release control over the transaction amount in the payment control order if the decontrol amount carried in the payment decontrol request is greater than the transaction amount in the payment control order.

[0198] In some embodiments of this application, based on the above technical solutions, the second request receiving module 930 includes:

[0199] A settlement release request receiving unit is configured to receive a settlement release request when a settlement request for the control order information is completed, wherein the settlement release request carries a business settlement identifier and a settlement release amount, and the settlement release amount is the amount in response to the settlement request;

[0200] The second logic call module 940 includes:

[0201] The settlement logic invocation unit is used to invoke the business processing logic corresponding to the business settlement identifier to create a settlement release order, wherein the settlement release order includes a settlement document identifier and the settlement release amount.

[0202] In some embodiments of this application, based on the above technical solutions, the control order information includes control amount, control type, and control status; the second logic call module 940 further includes:

[0203] Settlement control order acquisition unit, used to acquire control order information for the settlement request;

[0204] The settlement type update unit is used to update the control type of the control order information to the settlement type according to the settlement release control order;

[0205] The control status update unit is used to update the control status to the control completion status if the settlement release amount is equal to the control amount.

[0206] In some embodiments of this application, based on the above technical solutions, the second request receiving module 930 includes:

[0207] The first revenue sharing and decontrollability request receiving unit is configured to receive a first revenue sharing and decontrollability request when a revenue sharing request for the control order information is completed, wherein the first revenue sharing and decontrollability request carries a business revenue sharing identifier and the business amount, and the business amount is the amount in response to the revenue sharing request;

[0208] The second logic call module 940 includes:

[0209] The revenue sharing logic invocation unit is used to invoke the business processing logic corresponding to the business revenue sharing identifier to create a revenue sharing release order, wherein the revenue sharing release order includes a revenue sharing document identifier and the business amount.

[0210] In some embodiments of this application, based on the above technical solutions, the control order information includes the control amount; the second logic call module 940 further includes:

[0211] The second revenue sharing release request receiving unit is used to receive a second revenue sharing release request sent by the target device, wherein the second revenue sharing release request carries the revenue sharing document identifier and the revenue sharing amount;

[0212] The split account release control unit is used to release control over the split account amount in the control order information according to the second split account release request;

[0213] The revenue sharing amount sending unit is used to send the revenue sharing amount to the target device.

[0214] In some embodiments of this application, based on the above technical solutions, the revenue splitting and release control unit includes:

[0215] The first revenue sharing decontrol subunit is used to release control on the revenue sharing amount in the control order information if the sum of the revenue sharing amount carried in the second revenue sharing decontrol request and the business amount in the first revenue sharing decontrol request is less than or equal to the control amount in the control order information.

[0216] The second revenue sharing decontrol subunit is used to release the control over the control amount in the revenue sharing decontrol request if the sum of the revenue sharing amount carried in the second revenue sharing decontrol request and the business amount in the first revenue sharing decontrol request is greater than the control amount in the control order information.

[0217] In some embodiments of this application, based on the above technical solutions, the second request receiving module 930 includes:

[0218] A refund release request receiving unit is used to receive a refund release request when a refund request for the control order information is completed, wherein the refund release request carries a business refund identifier and a refund release amount, and the refund release amount is the amount in response to the refund request;

[0219] The second logic call module 940 includes:

[0220] The refund logic invocation unit is used to invoke the business processing logic corresponding to the business refund identifier to create a refund release order, wherein the refund release order includes a refund document identifier and the refund release amount.

[0221] In some embodiments of this application, based on the above technical solutions, the control order information includes the amount being released from control; the second logic call module 940 further includes:

[0222] The refund control order acquisition unit is used to acquire the payment control order to which the refund request is targeted;

[0223] The refund amount update unit is used to update the amount in the control release information according to the refund release amount.

[0224] In some embodiments of this application, based on the above technical solutions, the control order information further includes the amount already released; the refund release order further includes the release status; the second logic call module 940 further includes:

[0225] A refund result receiving unit is used to receive a refund result notification sent by the target device, wherein the refund result notification carries the refund document identifier and the refund amount;

[0226] The refund status update unit is used to update the release status in the refund release form to the release success status if the refund result notification indicates that the refund was successful.

[0227] The refund amount update unit is used to record the refund amount in the refund release order and update the amount under release and the amount already released in the control order information according to the refund amount.

[0228] In some embodiments of this application, based on the above technical solutions, the second request receiving module 930 includes:

[0229] A withdrawal release request receiving unit is configured to receive a withdrawal release request when a withdrawal request for the control order information is completed, wherein the withdrawal release request carries a business withdrawal identifier and a withdrawal release amount, and the withdrawal release amount is the amount in response to the withdrawal request;

[0230] The second logic call module 940 includes:

[0231] The withdrawal logic invocation unit is used to invoke the business processing logic corresponding to the business withdrawal identifier to create a withdrawal release order, wherein the withdrawal release order includes a withdrawal document identifier and the withdrawal release amount.

[0232] It should be noted that the apparatus provided in the above embodiments and the method provided in the above embodiments belong to the same concept, and the specific way in which each module performs the operation has been described in detail in the method embodiments, and will not be repeated here.

[0233] Figure 10 A schematic diagram of the structure of a computer system suitable for implementing the electronic device of the present application is shown.

[0234] It should be noted that, Figure 10 The computer system 1000 of the electronic device shown is merely an example and should not impose any limitation on the functionality and scope of use of the embodiments of this application.

[0235] like Figure 10 As shown, the computer system 1000 includes a Central Processing Unit (CPU) 1001, which can perform various appropriate actions and processes based on programs stored in Read-Only Memory (ROM) 1002 or programs loaded from storage section 1008 into Random Access Memory (RAM) 1003. The RAM 1003 also stores various programs and data required for system operation. The CPU 1001, ROM 1002, and RAM 1003 are interconnected via a bus 1004. An Input / Output (I / O) interface 1005 is also connected to the bus 1004.

[0236] The following components are connected to I / O interface 1005: an input section 1006 including a keyboard, mouse, etc.; an output section 1007 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and speakers, etc.; a storage section 1008 including a hard disk, etc.; and a communication section 1009 including a network interface card such as a LAN (Local Area Network) card, modem, etc. The communication section 1009 performs communication processing via a network such as the Internet. A drive 1010 is also connected to I / O interface 1005 as needed. Removable media 1011, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., are installed on drive 1010 as needed so that computer programs read from them can be installed into storage section 1008 as needed.

[0237] Specifically, according to embodiments of this application, the processes described in the various method flowcharts can be implemented as computer software programs. For example, embodiments of this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication section 1009, and / or installed from removable medium 1011. When the computer program is executed by central processing unit (CPU) 1001, it performs various functions defined in the system of this application.

[0238] It should be noted that the computer-readable medium shown in the embodiments of this application can be a computer-readable signal medium or a computer-readable storage medium, or any combination of the two. A computer-readable storage medium can be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), flash memory, optical fiber, portable compact disc read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this application, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In this application, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such transmitted data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. The computer-readable signal medium can also be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to wireless, wired, etc., or any suitable combination thereof.

[0239] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0240] It should be noted that although several modules or units for the device used to perform actions have been mentioned in the detailed description above, this division is not mandatory. In fact, according to the embodiments of this application, the features and functions of two or more modules or units described above can be embodied in one module or unit. Conversely, the features and functions of one module or unit described above can be further divided and embodied by multiple modules or units.

[0241] Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein can be implemented by software or by combining software with necessary hardware. Therefore, the technical solutions according to the embodiments of this application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (such as a CD-ROM, USB flash drive, external hard drive, etc.) or on a network, including several instructions to cause a computing device (such as a personal computer, server, touch terminal, or network device, etc.) to execute the method according to the embodiments of this application.

[0242] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein.

[0243] It should be understood that this application is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this application is limited only by the appended claims.

Claims

1. A business processing method, characterized in that, The business processing method includes: When a payment request is completed, a payment control request is received, wherein the payment control request carries a business payment identifier and a business amount, and the business amount is the amount in response to the payment request; The business processing logic corresponding to the business payment identifier is invoked to create a payment control order, wherein the payment control order includes a payment document identifier and the business amount, and the control order information of the payment control order is used to control the flow of the business amount; When a settlement request for the control order information is completed, a settlement release request is received, wherein the settlement release request carries a business settlement identifier and a settlement release amount, and the settlement release amount is the amount in response to the settlement request; Invoke the business processing logic corresponding to the business settlement identifier to create a settlement release order, wherein the settlement release order includes a settlement document identifier and the settlement release amount, and the release order information of the settlement release order is used to release the flow of the business amount; The business processing results are fed back based on the control order information and the decontrol order information.

2. The business processing method according to claim 1, characterized in that, After invoking the business processing logic corresponding to the business payment identifier to create a payment control order, the method further includes: Receive a payment release request sent by the target device, wherein the payment release request carries the payment document identifier and the release amount; According to the payment release request, the control over the release amount or the transaction amount in the payment control order is released. The amount to be released or the amount of the service will be sent to the target device.

3. The business processing method according to claim 2, characterized in that, The step of releasing control over the amount to be released or the transaction amount in the payment control order according to the payment release request includes: If the amount to be released in the payment release request is less than or equal to the transaction amount in the payment control order, then the control on the amount to be released in the payment control order is lifted. If the amount to be released in the payment release request is greater than the transaction amount in the payment control order, then the transaction amount in the payment control order will be released from control.

4. The business processing method according to claim 1, characterized in that, The control order information includes the control amount, control type, and control status; after invoking the business processing logic corresponding to the business settlement identifier to create a settlement release order, the method further includes: Obtain the control order information targeted by the settlement request; Based on the settlement release order, update the control type of the control order information to the settlement type; If the settlement release amount equals the control amount, the control status is updated to release completed.

5. The business processing method according to claim 1, characterized in that, The method further includes: When a splitting request for the control order information is completed, a first splitting release request is received, wherein the first splitting release request carries a business splitting identifier and the business amount, and the business amount is the amount in response to the splitting request; Invoke the business processing logic corresponding to the business accounting identifier to create an accounting control release order, wherein the accounting control release order includes the accounting document identifier and the business amount.

6. The business processing method according to claim 5, characterized in that, The control order information includes the control amount; After invoking the business processing logic corresponding to the business revenue sharing identifier to create a revenue sharing release order, the method further includes: Receive a second split billing release request sent by the target device, wherein the second split billing release request carries the split billing document identifier and the split billing amount; According to the second account release request, the account amount in the control order information is released from control. The revenue share is sent to the target device.

7. The business processing method according to claim 6, characterized in that, The step of releasing control over the account amount in the control order information according to the second account release request includes: If the sum of the revenue amount carried in the second revenue release request and the business amount in the first revenue release request is less than or equal to the control amount in the control order information, then the control on the revenue amount in the control order information is lifted. If the sum of the revenue amount carried in the second revenue release request and the business amount in the first revenue release request is greater than the control amount in the control order information, then the control amount in the revenue release order is released from control.

8. The method according to claim 1, characterized in that, The method further includes: When a refund request for the aforementioned control order information is completed, a refund release request is received, wherein the refund release request carries a business refund identifier and a refund release amount, and the refund release amount is the amount responded to in the refund request; Invoke the business processing logic corresponding to the business refund identifier to create a refund release order, wherein the refund release order includes a refund document identifier and the refund release amount.

9. The method according to claim 8, characterized in that, The control order information includes the amount being released from control; after invoking the business processing logic corresponding to the business refund identifier to create a refund release order, the method further includes: Obtain the control order information to which the refund request is targeted; Update the amount under control in the control order information according to the amount of the refund release.

10. The method according to claim 9, characterized in that, The control order information also includes the amount that has been released from control; the refund release order also includes the release status; after updating the amount under release in the control order information according to the refund release amount, the method further includes: Receive a refund result notification sent by the target device, wherein the refund result notification carries the refund document identifier and the refund amount; If the refund result notification indicates that the refund was successful, the release status in the refund release form will be updated to the release success status; The refund amount is recorded in the refund release order, and the amount under release and the amount already released in the control order information are updated according to the refund amount.

11. The method according to claim 1, characterized in that, The method further includes: When a withdrawal request for the aforementioned control order information is completed, a withdrawal release request is received, wherein the withdrawal release request carries a business withdrawal identifier and a withdrawal release amount, and the withdrawal release amount is the amount in response to the withdrawal request; The business processing logic corresponding to the business withdrawal identifier is invoked to create a withdrawal release order, wherein the withdrawal release order includes a withdrawal document identifier and the withdrawal release amount.

12. A business processing apparatus, characterized in that, include: A payment control receiving unit is used to receive a payment control request when a payment request is completed, wherein the payment control request carries a business payment identifier and a business amount, and the business amount is the amount in response to the payment request; The payment logic invocation unit is used to invoke the business processing logic corresponding to the business payment identifier to create a payment control order. The payment control order includes a payment document identifier and the business amount. The control order information of the payment control order is used to control the flow of the business amount. A settlement release request receiving unit is configured to receive a settlement release request when a settlement request for the control order information is completed, wherein the settlement release request carries a business settlement identifier and a settlement release amount, and the settlement release amount is the amount in response to the settlement request; The settlement logic invocation unit is used to invoke the business processing logic corresponding to the business settlement identifier to create a settlement release order. The settlement release order includes a settlement document identifier and the settlement release amount. The release order information of the settlement release order is used to release the flow of the business amount. The result feedback module is used to provide feedback on the business processing results based on the control order information and the decontrol order information.

13. An electronic device, characterized in that, include: processor; Memory for storing the executable instructions of the processor; The processor is configured to execute the business processing method of any one of claims 1 to 11 by executing the executable instructions.

14. A computer-readable medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the business processing method as described in any one of claims 1 to 11.

15. A computer program product, characterized in that, The computer program product includes computer instructions stored in a computer-readable storage medium, and a processor of a computer device reads and executes the computer instructions from the computer-readable storage medium, causing the computer device to perform the business processing method as described in any one of claims 1 to 11.

Images