A service processing method and device, electronic equipment and computer readable medium

Abstract

The application discloses a business processing method and device, electronic equipment and computer readable medium, relates to the technical field of big data data processing, and a specific embodiment comprises the following steps: in response to a business change request, obtaining a corresponding user identifier and a change business type identifier, calling a pre-advance interface to generate a corresponding change order identifier based on the change business type identifier; based on the user identifier, the change order identifiers are summarized to obtain a change order identifier set; each change order identifier in the change order identifier set is bound to generate a bound change order identifier, and then a pre-advance interface is called to generate advance information based on the bound change order identifier; and based on the advance information, corresponding payment is performed. Thus, when a product needs to be changed or added during business handling, a new order number does not need to be applied again, and the business processing efficiency is improved.

Description

Technical Field

[0001] This application relates to the field of big data processing technology, and in particular to a business processing method, apparatus, electronic device and computer-readable medium. Background Technology

[0002] Currently, banks and various car manufacturers offer credit services for a wide range of products. Once a user selects a product and submits an application, the manufacturer provides a financial order number. Subsequent cross-processing, approval, disbursement, and loan disbursement processes are all tied to this order number. If a user wants to change or add a product midway through the process, they need to submit a new application for a new financial order number, which is inefficient and makes users prone to abandoning their credit applications. Summary of the Invention

[0003] In view of this, embodiments of this application provide a business processing method, apparatus, electronic device, and computer-readable medium, which can solve the problem of low business processing efficiency caused by the need to apply for a new order number when changing or adding products during the business process.

[0004] To achieve the above objectives, according to one aspect of an embodiment of this application, a business processing method is provided, comprising:

[0005] In response to a business change request, obtain the corresponding user identifier and change business type identifier, and call the pre-submission interface to generate the corresponding change order identifier based on the change business type identifier;

[0006] Based on the user identifier, the change order identifiers are aggregated to obtain a set of change order identifiers;

[0007] Bind each change order identifier in the change order identifier set to generate a bound change order identifier, and then call the advance payment request interface to generate payment request information based on the bound change order identifier;

[0008] Based on the payment request information, execute the corresponding payment.

[0009] Optionally, a corresponding change order identifier is generated, including:

[0010] Retrieve the existing change order identifier corresponding to the business type identifier;

[0011] Generate the corresponding change order identifier based on the business type identifier and the existing change order identifier.

[0012] Optionally, based on the business type identifier and the existing change order identifier, a corresponding change order identifier is generated, including:

[0013] Identify the number corresponding to the existing change order identifier;

[0014] Call the change order identifier generation program to generate the corresponding change order identifier based on the business type identifier and number.

[0015] Optionally, change order identifiers are aggregated based on user identifiers to obtain a set of change order identifiers, including:

[0016] The various change order identifiers associated with the user identifier are aggregated to obtain a change order identifier set.

[0017] Optionally, each change order identifier in the change order identifier set is bound to generate a bound change order identifier, including:

[0018] Extract the preset dimension fields from the user identifier and the change business type identifier;

[0019] Generate binding change order identifiers based on preset dimension fields and each change order identifier.

[0020] Optionally, payment request information is generated based on the bound change order identifier, including:

[0021] Based on the bound change order identifier, obtain the corresponding amount for each payment request;

[0022] Based on each requested amount and user identifier, request information is generated.

[0023] Optionally, based on each requested amount and user identifier, request information is generated, including:

[0024] Based on the user identifier, determine the corresponding payment account identifier;

[0025] The request information is generated based on each request amount and the requesting account identifier.

[0026] In addition, this application also provides a business processing apparatus, including:

[0027] The acquisition unit is configured to respond to a business change request by acquiring the corresponding user identifier and change business type identifier, and calling the pre-submission interface to generate the corresponding change order identifier based on the change business type identifier;

[0028] The aggregation unit is configured to aggregate change order identifiers based on user identifiers to obtain a set of change order identifiers;

[0029] The payment request information generation unit is configured to bind each change order identifier in the change order identifier set to generate a bound change order identifier, and then call the pre-payment request interface to generate payment request information based on the bound change order identifier;

[0030] The execution unit is configured to execute the corresponding payment based on the payment request information.

[0031] Optionally, the acquisition unit is further configured to:

[0032] Retrieve the existing change order identifier corresponding to the business type identifier;

[0033] Generate the corresponding change order identifier based on the business type identifier and the existing change order identifier.

[0034] Optionally, the acquisition unit is further configured to:

[0035] Identify the number corresponding to the existing change order identifier;

[0036] Call the change order identifier generation program to generate the corresponding change order identifier based on the business type identifier and number.

[0037] Optionally, the summary unit is further configured as follows:

[0038] The various change order identifiers associated with the user identifier are aggregated to obtain a change order identifier set.

[0039] Optionally, the device further includes a reimbursement information generation unit, configured to:

[0040] Extract the preset dimension fields from the user identifier and the change business type identifier;

[0041] Generate binding change order identifiers based on preset dimension fields and each change order identifier.

[0042] Optionally, the device further includes a reimbursement information generation unit, configured to:

[0043] Based on the bound change order identifier, obtain the corresponding amount for each payment request;

[0044] Based on each requested amount and user identifier, request information is generated.

[0045] Optionally, the payment request information generation unit is further configured to:

[0046] Based on the user identifier, determine the corresponding payment account identifier;

[0047] The request information is generated based on each request amount and the requesting account identifier.

[0048] In addition, this application also provides a business processing electronic device, including: one or more processors; and a storage device for storing one or more programs, which, when executed by one or more processors, enable the one or more processors to implement the business processing method described above.

[0049] In addition, this application also provides a computer-readable medium having a computer program stored thereon, which, when executed by a processor, implements the business processing method described above.

[0050] To achieve the above objectives, according to another aspect of the embodiments of this application, a computer program product is provided.

[0051] A computer program product according to an embodiment of this application includes a computer program that, when executed by a processor, implements the business processing method provided in the embodiment of this application.

[0052] One embodiment of the above invention has the following advantages or beneficial effects: In response to a business change request, this application obtains the corresponding user identifier and change business type identifier, calls the pre-submission interface to generate a corresponding change order identifier based on the change business type identifier; it then aggregates the change order identifiers based on the user identifier to obtain a change order identifier set; it binds each change order identifier in the change order identifier set to generate a bound change order identifier, and then calls the pre-payment interface to generate payment request information based on the bound change order identifier; finally, it executes the corresponding payment based on the payment request information. This eliminates the need to apply for a new order number when changes or additions are needed during business processing, improving business processing efficiency.

[0053] The further effects of the aforementioned unconventional alternative methods will be explained below in conjunction with specific implementation methods. Attached Figure Description

[0054] The accompanying drawings are provided to better understand this application and do not constitute an undue limitation thereof. Wherein:

[0055] Figure 1 This is a schematic diagram of the main flow of a business processing method according to an embodiment of this application;

[0056] Figure 2 This is a schematic diagram of the main flow of a business processing method according to an embodiment of this application;

[0057] Figure 3 This is a schematic diagram of the main flow of a business processing method according to an embodiment of this application;

[0058] Figure 4 This is a schematic diagram of the main units of a service processing apparatus according to an embodiment of this application;

[0059] Figure 5 This is an exemplary system architecture diagram to which embodiments of this application can be applied;

[0060] Figure 6 This is a schematic diagram of the structure of a computer system suitable for implementing terminal devices or servers in the embodiments of this application. Detailed Implementation

[0061] The following description, in conjunction with the accompanying drawings, illustrates exemplary embodiments of this application, including various details to aid understanding. These embodiments should be considered merely exemplary. Therefore, those skilled in the art should recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of this application. Similarly, for clarity and brevity, descriptions of well-known functions and structures are omitted in the following description. It should be noted that the collection, analysis, use, transmission, and storage of user personal information involved in the technical solutions of this application comply with relevant laws and regulations, are used for legitimate and reasonable purposes, are not shared, disclosed, or sold outside of these legitimate uses, and are subject to supervision and management by regulatory authorities. Necessary measures should be taken to prevent unauthorized access to such personal information data, ensure that personnel authorized to access personal information data comply with relevant laws and regulations, and ensure the security of user personal information. Once this user personal information data is no longer needed, the risk should be minimized by restricting or even prohibiting data collection and / or deleting the data.

[0062] When used, including in certain relevant applications, data is deidentified to protect user privacy, for example by removing specific identifiers, controlling the amount or specificity of stored data, controlling how data is stored, and / or other methods.

[0063] Figure 1 This is a schematic diagram of the main flow of a business processing method according to an embodiment of this application, as shown below. Figure 1 As shown, the business processing methods include:

[0064] Step S101: In response to the business change request, obtain the corresponding user identifier and change business type identifier, call the pre-submission interface, and generate the corresponding change order identifier based on the change business type identifier.

[0065] In this embodiment, the execution entity of the business processing method (e.g., a server) can receive business change requests via wired or wireless connections. Upon receiving the business change request, the execution entity can obtain the user identifier and the change business type identifier carried in the request. The user identifier can be used to represent the nickname, ID, etc., of the user initiating the business change request; this embodiment does not specifically limit the content of the user identifier. The change business type identifier can be used to represent the type of business to be added, such as main loan fee, surcharge, purchase tax, registration fee, insurance fee, etc.; this embodiment does not specifically limit the business type represented by the change business type identifier. The execution entity can call the pre-submission interface to generate a corresponding change order identifier based on the change business type identifier. Specifically, it can call the order identifier generation template to place the change business type identifier into the corresponding position in the order identifier generation template to generate a change order identifier corresponding to the change business type identifier.

[0066] Step S102: Summarize the change order identifiers based on the user identifiers to obtain a set of change order identifiers.

[0067] Specifically, the change order identifiers are aggregated based on the user identifiers to obtain a set of change order identifiers, including: aggregating the various change order identifiers associated with the user identifiers to obtain a set of change order identifiers.

[0068] One or more change order identifiers corresponding to the same user identifier are aggregated to obtain a change order identifier set.

[0069] Step S103: Bind each change order identifier in the change order identifier set to generate a bound change order identifier, and then call the pre-payment interface to generate payment request information based on the bound change order identifier.

[0070] Specifically, each change order identifier in the change order identifier set is bound to generate a bound change order identifier, including: extracting preset dimension fields from the user identifier and the change business type identifier; and generating a bound change order identifier based on the preset dimension fields and each change order identifier.

[0071] A preset dimension field can be a field common to both the user identifier (e.g., 0100) and various change business type identifiers (e.g., 01001, 01002, 01003, 01004). For example, it could be 0100. The executing entity can then bind the preset dimension field to the identifiers obtained from each change business type identifier after removing the preset dimension field, such as 1, 2, 3, and 4, to obtain a bound change order identifier, such as 01001234. This means that the user identifier 0100 is bound to each change business type identifier 01001, 01002, 01003, and 01004. Obtaining the bound change order identifier makes the business processing simpler, more accurate, more scalable, and more efficient.

[0072] Call the pre-payment request interface to generate payment request information based on the bound change order identifier.

[0073] Specifically, generating payment request information based on the bound change order identifier includes: obtaining the corresponding payment amounts based on the bound change order identifier; and generating payment request information based on each payment amount and the user identifier.

[0074] After obtaining the bound change order identifier, the executing entity can separate each change order identifier. Then, the executing entity can obtain the request amount for each change order identifier. The request amounts are added together and combined with the user identifier to generate a request information, which includes the user identifier and the total request amount. Based on the user identifier, the requesting account can be obtained, and the total request amount can be disbursed to the requesting account to complete the business processing.

[0075] Specifically, based on each requested amount and user identifier, request information is generated, including: determining the corresponding request account identifier based on the user identifier; and generating request information based on each requested amount and request account identifier.

[0076] The executing entity can obtain the default request account identifier corresponding to the user identifier and determine the default request account identifier as the corresponding request account identifier.

[0077] The executing entity can also obtain configuration information corresponding to the user identifier, and determine the corresponding requesting account identifier based on the configuration information. The number of requesting account identifiers can be one or multiple; this embodiment does not specifically limit the number of requesting account identifiers. Based on the configuration information, the entity can also obtain the correspondence between the requested amount and the requesting account identifier, and generate request information based on this correspondence.

[0078] Step S104: Based on the payment request information, execute the corresponding payment.

[0079] The payment procedure is invoked to execute the corresponding payment based on the correspondence between the requested amount and the requested account identifier in the payment request information, and the payment result can be returned.

[0080] In this embodiment, in response to a business change request, the corresponding user identifier and change business type identifier are obtained. The pre-submission interface is called to generate a corresponding change order identifier based on the change business type identifier. The change order identifiers are then aggregated based on the user identifier to obtain a set of change order identifiers. Each change order identifier in the set is bound to generate a bound change order identifier. Subsequently, the pre-payment interface is called to generate payment request information based on the bound change order identifiers. Based on the payment request information, the corresponding payment is executed. This eliminates the need to apply for a new order number when changes or additions are needed during business processing, improving business processing efficiency.

[0081] Figure 2 This is a schematic diagram of the main flow of a business processing method according to an embodiment of this application, such as... Figure 2 As shown, the business processing methods include:

[0082] Step S201: In response to the business change request, obtain the corresponding user identifier and the change business type identifier.

[0083] Step S202: Obtain the existing change order identifier corresponding to the business type identifier.

[0084] Each business type identifier can correspond to one or more existing change order identifiers. Existing change order identifiers can be the numbers corresponding to the business that needs to be changed, generated based on the business type identifiers.

[0085] Step S203: Generate the corresponding change order identifier based on the business type identifier and the existing change order identifier.

[0086] Specifically, based on the business type identifier and the existing change order identifier, a corresponding change order identifier is generated, including: determining the number corresponding to the existing change order identifier; and calling the change order identifier generation program to generate the corresponding change order identifier according to the business type identifier and the number.

[0087] The executing entity can call the change order identifier generation program to add the number corresponding to the existing change order identifier to the corresponding position in the template corresponding to the change order identifier, so as to generate the change order identifier.

[0088] Step S204: Summarize the change order identifiers based on the user identifiers to obtain a set of change order identifiers.

[0089] Obtain the generated change order identifiers corresponding to the user identifiers to obtain a set of change order identifiers.

[0090] Step S205: Bind each change order identifier in the change order identifier set to generate a bound change order identifier, and then call the pre-payment interface to generate payment request information based on the bound change order identifier.

[0091] Specifically, the change order identifier selected by the user can be bound to the order identifier set to generate a bound change order identifier. This, in turn, calls the execution logic in the pre-payment interface to generate payment request information based on the bound change order identifier. This improves business processing efficiency.

[0092] Step S206: Based on the payment request information, execute the corresponding payment.

[0093] This application embodiment enables businesses to apply for a new order number without interrupting the business processing process when they need to change or add products during the business process, thereby improving business processing efficiency.

[0094] Figure 3 This is a schematic diagram illustrating an application scenario of a business processing method according to an embodiment of this application. The business processing method of this embodiment is applied to scenarios where new business needs to be added during business processing. Figure 3 As shown, the main business processing flow can be as follows: the executing entity receives an application, obtains the corresponding order number, executes the application based on the order number, and after multiple approvals, performs a credit check. If the credit check passes, a payment request is made, and then subsequent processes are executed. Specifically, when a user calls the pre-application interface to perform multiple pre-applications, a new order number corresponding to each pre-application is generated and updated in the main business processing flow as the basis for application. The executing entity can generate multiple application information entries based on the new order numbers generated from multiple pre-applications. The user can select from these multiple application information entries, and the executing entity can bind one or more application / payment request information entries based on the user's selection. Specifically, users can also generate new order numbers by uploading images and making multiple pre-payment requests, thereby generating multiple payment request information entries. Specifically, through pre-application transactions, users can add various types of business products at any time, including main loan fees, surcharges, vehicle purchase tax, registration fees, insurance premiums, etc. By uploading images for transactions, necessary information can be supplemented by uploading images after product changes; by submitting pre-payment transactions, product types can be further adjusted before loan disbursement, allowing for more flexible combinations of required product types. Furthermore, if multiple payment requests are needed, multiple pre-payment requests can be submitted at once. This application embodiment enables the addition or modification of product types before application submission, the modification of some product attributes before payment requests, the completion of multiple payment requests through a single transaction, and the flexible combination of product types throughout the process.

[0095] For example, when the same user is required to apply for car loan services from the same manufacturer, if they want to change / add other types of the product or apply for other services related to the same product midway through the process, they do not need to resubmit the application; the process can continue, improving efficiency and system scalability. A pre-application interface is provided, allowing changes to be made before formal application, meeting the user's need to change product types in the early stages. A pre-disbursement interface is also provided, allowing pre-disbursement requests after cross-checking, three-stage approval, and manual credit investigation, meeting the user's need to change / add product attributes later and for multiple disbursement requests. Image upload transactions are provided; after changing product types, users can upload images to the transaction, storing the new necessary images. Order numbers generated from multiple applications are uniquely bound. This enhances horizontal scalability, allowing for intervention at different process nodes, providing high flexibility.

[0096] Figure 4 This is a schematic diagram of the main units of a service processing apparatus according to an embodiment of this application. Figure 4 As shown, the business processing device 400 includes an acquisition unit 401, a summarization unit 402, a payment request information generation unit 403, and an execution unit 404.

[0097] The acquisition unit 401 is configured to respond to a business change request by acquiring the corresponding user identifier and change business type identifier, and calling the pre-submission interface to generate the corresponding change order identifier based on the change business type identifier.

[0098] The aggregation unit 402 is configured to aggregate change order identifiers based on user identifiers to obtain a set of change order identifiers.

[0099] The payment request information generation unit 403 is configured to bind each change order identifier in the change order identifier set to generate a bound change order identifier, and then call the pre-payment interface to generate payment request information based on the bound change order identifier.

[0100] Execution unit 404 is configured to execute the corresponding payment based on the payment request information.

[0101] In some embodiments, the acquisition unit 401 is further configured to: acquire the existing change order identifier corresponding to the business type identifier; and generate the corresponding change order identifier based on the business type identifier and the existing change order identifier.

[0102] In some embodiments, the acquisition unit 401 is further configured to: determine the number corresponding to an existing change order identifier; and call a change order identifier generation program to generate a corresponding change order identifier based on the business type identifier and the number.

[0103] In some embodiments, the aggregation unit 402 is further configured to aggregate the various change order identifiers associated with the user identifier to obtain a change order identifier set.

[0104] In some embodiments, the business processing apparatus further includes Figure 4 The payment request information generation unit (not shown) is configured to: extract preset dimension fields from the user identifier and the change business type identifier; and generate a binding change order identifier based on the preset dimension fields and each change order identifier.

[0105] In some embodiments, the business processing apparatus further includes Figure 4 The payment request information generation unit (not shown) is configured to: obtain the corresponding payment amounts based on the bound change order identifier; and generate payment request information based on each payment amount and the user identifier.

[0106] In some embodiments, the reimbursement information generation unit is further configured to: determine the corresponding reimbursement account identifier based on the user identifier; and generate reimbursement information based on each reimbursement amount and the reimbursement account identifier.

[0107] It should be noted that the business processing method and business processing device in this application are related in terms of specific implementation content, so repeated content will not be described again.

[0108] Figure 5 An exemplary system architecture 500 is shown that can be applied to the business processing method or business processing apparatus of the embodiments of this application.

[0109] like Figure 5 As shown, system architecture 500 may include terminal devices 501, 502, and 503, a network 504, and a server 505. Network 504 serves as the medium for providing communication links between terminal devices 501, 502, and 503 and server 505. Network 504 may include various connection types, such as wired or wireless communication links, or fiber optic cables, etc.

[0110] Users can use terminal devices 501, 502, and 503 to interact with server 505 via network 504 to receive or send messages, etc. Various communication client applications can be installed on terminal devices 501, 502, and 503, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social media platform software, etc. (for example only).

[0111] Terminal devices 501, 502, and 503 can be various electronic devices with business processing screens and support web browsing, including but not limited to smartphones, tablets, laptops, and desktop computers.

[0112] Server 505 can be a server providing various services, such as a backend management server supporting business change requests submitted by users using terminal devices 501, 502, and 503 (this is just an example). The backend management server can respond to a business change request by obtaining the corresponding user identifier and change business type identifier, calling the pre-submission interface to generate a corresponding change order identifier based on the change business type identifier; aggregating change order identifiers based on the user identifier to obtain a change order identifier set; binding each change order identifier in the change order identifier set to generate a bound change order identifier; then calling the pre-payment interface to generate payment request information based on the bound change order identifier; and finally, executing the corresponding payment based on the payment request information. This eliminates the need to apply for a new order number when changes or additions are needed during business processing, improving business processing efficiency.

[0113] It should be noted that the business processing method provided in this application embodiment is generally executed by server 505, and correspondingly, the business processing device is generally set in server 505.

[0114] It should be understood that Figure 5 The number of terminal devices, networks, and servers shown is merely illustrative. Depending on implementation needs, any number of terminal devices, networks, and servers can be included.

[0115] The following is for reference. Figure 6 It shows a schematic diagram of the structure of a computer system 600 suitable for implementing a terminal device according to the embodiments of this application. Figure 6 The terminal device shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of this application.

[0116] like Figure 6 As shown, the computer system 600 includes a central processing unit (CPU) 601, which can perform various appropriate actions and processes based on programs stored in read-only memory (ROM) 602 or programs loaded from storage section 608 into random access memory (RAM) 603. The RAM 603 also stores various programs and data required for the operation of the computer system 600. The CPU 601, ROM 602, and RAM 603 are interconnected via a bus 604. An input / output (I / O) interface 605 is also connected to the bus 604.

[0117] The following components are connected to I / O interface 605: an input section 606 including a keyboard, mouse, etc.; an output section 607 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and speakers, etc.; a storage section 608 including a hard disk, etc.; and a communication section 609 including a network interface card such as a LAN card, modem, etc. The communication section 609 performs communication processing via a network such as the Internet. A drive 610 is also connected to I / O interface 605 as needed. A removable medium 611, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on drive 610 as needed so that computer programs read from it can be installed into storage section 608 as needed.

[0118] Specifically, according to the embodiments disclosed in this application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments disclosed in 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 609, and / or installed from removable medium 611. When the computer program is executed by central processing unit (CPU) 601, it performs the functions defined above in the system of this application.

[0119] It should be noted that the computer-readable medium shown in this application can be a computer-readable signal medium or a computer-readable storage medium, or any combination of the two. Computer-readable storage media can be, for example, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to: electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, 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 propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media can also be any computer-readable medium other than computer-readable storage media, 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, wire, optical fiber, RF, etc., or any suitable combination thereof.

[0120] 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.

[0121] The units described in the embodiments of this application can be implemented in software or hardware. The described units can also be housed in a processor; for example, a processor can be described as including an acquisition unit, a summarization unit, a reimbursement information generation unit, and an execution unit. The names of these units do not necessarily limit the specific unit itself.

[0122] In another aspect, this application also provides a computer-readable medium, which may be included in the device described in the above embodiments; or it may exist independently and not assembled into the device. The computer-readable medium carries one or more programs. When the one or more programs are executed by the device, the device responds to a business change request by obtaining the corresponding user identifier and change business type identifier, calling the pre-submission interface to generate a corresponding change order identifier based on the change business type identifier; aggregating change order identifiers based on the user identifier to obtain a change order identifier set; binding each change order identifier in the change order identifier set to generate a bound change order identifier; then calling the pre-payment interface to generate payment request information based on the bound change order identifier; and executing the corresponding payment based on the payment request information.

[0123] The computer program product of this application includes a computer program that, when executed by a processor, implements the business processing method in the embodiments of this application.

[0124] According to the technical solution of this application embodiment, it is possible to realize that when it is necessary to change or add products during the business process, there is no need to apply for a new order number again, thereby improving the efficiency of business processing.

[0125] The specific embodiments described above do not constitute a limitation on the scope of protection of this application. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can occur depending on design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this application should be included within the scope of protection of this application.

Claims

1. A business processing method, characterized in that, include: In response to a business change request, the system obtains the corresponding user identifier and change business type identifier, and calls the pre-submission interface to generate a corresponding change order identifier based on the change business type identifier. The change order identifiers are aggregated based on the user identifiers to obtain a set of change order identifiers; Bind each change order identifier in the change order identifier set to generate a bound change order identifier, and then call the pre-payment interface to generate payment request information based on the bound change order identifier; Based on the aforementioned payment request information, execute the corresponding payment. The step of binding each change order identifier in the change order identifier set to generate a bound change order identifier includes: extracting a preset dimension field from the user identifier and the change business type identifier; and generating a bound change order identifier based on the preset dimension field and each change order identifier. The step of generating the corresponding change order identifier includes: obtaining the existing change order identifier corresponding to the business type identifier; generating the corresponding change order identifier based on the business type identifier and the existing change order identifier, including: determining the number corresponding to the existing change order identifier; and calling the change order identifier generation program to generate the corresponding change order identifier according to the business type identifier and the number. It also includes: obtaining configuration information corresponding to the user identifier, determining the corresponding request account identifier based on the configuration information, wherein the number of request account identifiers is one or more, obtaining the correspondence between the request amount and the request account identifier based on the configuration information, and generating request information based on the correspondence.

2. The method according to claim 1, characterized in that, The step of aggregating the change order identifiers based on the user identifier to obtain a change order identifier set includes: The various change order identifiers associated with the user identifier are aggregated to obtain a change order identifier set.

3. The method according to claim 1, characterized in that, The generation of payment request information based on the bound change order identifier includes: Based on the bound change order identifier, obtain the corresponding payment amounts for each request; Based on the respective reimbursement amounts and the user identifier, reimbursement information is generated.

4. The method according to claim 3, characterized in that, The process of generating payment request information based on the respective payment amounts and the user identifier includes: Based on the user identifier, determine the corresponding payment request account identifier; Based on each requested amount and the requested account identifier, request information is generated.

5. A business processing device, characterized in that, include: The acquisition unit is configured to, in response to a business change request, acquire the corresponding user identifier and change business type identifier, and call the pre-submission interface to generate a corresponding change order identifier based on the change business type identifier; The aggregation unit is configured to aggregate the change order identifiers based on the user identifier to obtain a set of change order identifiers; The payment request information generation unit is configured to bind each change order identifier in the change order identifier set to generate a bound change order identifier, and then call the pre-payment request interface to generate payment request information based on the bound change order identifier; The execution unit is configured to execute the corresponding payment based on the payment request information; The acquisition unit is configured to: acquire the existing change order identifier corresponding to the business type identifier; Based on the business type identifier and the existing change order identifier, a corresponding change order identifier is generated; Determine the number corresponding to the existing change order identifier; Invoke the change order identifier generation program to generate a corresponding change order identifier based on the business type identifier and the number; The device further includes a payment request information generation unit, configured to: extract preset dimension fields from the user identifier and the change business type identifier; and generate a binding change order identifier based on the preset dimension fields and each change order identifier. The reimbursement information generation unit is configured to: obtain configuration information corresponding to the user identifier; determine the corresponding reimbursement account identifier based on the configuration information (the number of reimbursement account identifiers may be one or more); obtain the correspondence between the reimbursement amount and the reimbursement account identifier based on the configuration information; and generate reimbursement information based on the correspondence.

6. The apparatus according to claim 5, characterized in that, The aggregation unit is configured to: The various change order identifiers associated with the user identifier are aggregated to obtain a change order identifier set.

7. The apparatus according to claim 5, characterized in that, The device further includes a reimbursement information generation unit, configured to: Based on the bound change order identifier, obtain the corresponding payment amounts for each request; Based on the respective reimbursement amounts and the user identifier, reimbursement information is generated.

8. A business processing electronic device, characterized in that, include: One or more processors; Storage device for storing one or more programs. When the one or more programs are executed by the one or more processors, the one or more processors implement the method as described in any one of claims 1-4.

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

10. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the method as described in any one of claims 1-4.

Images