CN108961039B - Transaction processing method, device and system - Google Patents
Transaction processing method, device and system Download PDFInfo
- Publication number
- CN108961039B CN108961039B CN201810709167.3A CN201810709167A CN108961039B CN 108961039 B CN108961039 B CN 108961039B CN 201810709167 A CN201810709167 A CN 201810709167A CN 108961039 B CN108961039 B CN 108961039B
- Authority
- CN
- China
- Prior art keywords
- service
- transaction request
- transaction
- operation code
- preprocessing
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/02—Banking, e.g. interest calculation or account maintenance
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/03—Credit; Loans; Processing thereof
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/06—Asset management; Financial planning or analysis
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/08—Insurance
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/30—Computing systems specially adapted for manufacturing
Landscapes
- Business, Economics & Management (AREA)
- Engineering & Computer Science (AREA)
- Accounting & Taxation (AREA)
- Finance (AREA)
- Development Economics (AREA)
- Technology Law (AREA)
- Marketing (AREA)
- Strategic Management (AREA)
- Economics (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Entrepreneurship & Innovation (AREA)
- Game Theory and Decision Science (AREA)
- Human Resources & Organizations (AREA)
- Operations Research (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
The embodiment of the present specification provides a transaction processing method, which may be used to process transaction requests of multiple products in a product layer, perform service preprocessing on the transaction request after the transaction request of a product layer is obtained, and search a target service processing process corresponding to a service identifier in a preconfigured information base based on the service identifier of the transaction request subjected to service preprocessing, so that the transaction request subjected to service preprocessing is sent to the target service processing process to perform corresponding service processing, so as to complete a current transaction.
Description
Technical Field
The embodiment of the specification relates to the technical field of data processing, in particular to a transaction processing method, a transaction processing device and a transaction processing system.
Background
Along with the higher financial informatization degree of banks, the types of products provided by banks are more and more, the business service is more and more complex, and the maintainability of a bank core system becomes one of the important indexes of system design. Therefore, there is a need to provide a system design that is more maintainable.
Disclosure of Invention
The embodiment of the specification provides a transaction processing method, a transaction processing device and a transaction processing system.
In a first aspect, an embodiment of the present specification provides a transaction processing method, including: acquiring a transaction request of a product in a product layer, wherein the transaction request comprises a service identifier, and the product layer comprises a plurality of products; performing service preprocessing on the transaction request; searching a target service processing process corresponding to the service identifier in a pre-configured information base based on the service identifier of the transaction request subjected to service preprocessing, wherein the information base comprises corresponding relation information between various service identifiers and corresponding service processing processes; and sending the transaction request subjected to service preprocessing to the target service processing process for corresponding service processing.
In a second aspect, an embodiment of the present specification provides a transaction processing apparatus, including: the system comprises a first acquisition unit, a second acquisition unit and a third acquisition unit, wherein the first acquisition unit is used for acquiring a transaction request of a product in a product layer, the transaction request comprises a service identifier, and the product layer comprises a plurality of products; the preprocessing unit is used for preprocessing the business of the transaction request; a determining unit, configured to search, based on a service identifier of the transaction request subjected to service preprocessing, a pre-configured information base for a target service processing procedure corresponding to the service identifier, where the information base includes correspondence information between multiple service identifiers and corresponding service processing procedures; and the sending unit is used for sending the transaction request subjected to the service preprocessing to the target service processing process for corresponding service processing.
In a third aspect, an embodiment of the present specification provides a transaction processing system, including: a transaction processing device and one or more business processing devices. The transaction processing device is used for acquiring a transaction request of a product in a product layer, wherein the transaction request comprises a service identifier, and the product layer comprises a plurality of products; performing service preprocessing on the transaction request; searching a target service processing device corresponding to the service identifier in a pre-configured information base based on the service identifier of the transaction request subjected to service preprocessing, wherein the information base comprises corresponding relation information between various service identifiers and corresponding service processing devices; and sending the transaction request processed by the service preprocessing to the target service processing device. Each service processing device is used for performing core service processing on the received transaction request so as to complete the current transaction.
In a fourth aspect, an embodiment of the present specification provides an electronic device, including: a memory; one or more processors; and the transaction processing device described above, stored in the memory and configured to be executed by one or more processors.
In a fifth aspect, the present specification provides a computer-readable storage medium, on which a computer program is stored, and the computer program, when executed by a processor, implements the steps of the transaction processing method.
The embodiment of the specification has the following beneficial effects:
in the transaction processing method provided in the embodiment of the present specification, a transaction request of a product in a product layer is obtained, then a service preprocessing is performed on the transaction request, and based on a service identifier of the transaction request subjected to the service preprocessing, a target service processing procedure corresponding to the service identifier is searched in a preconfigured information base, so that the transaction request subjected to the service preprocessing is distributed to the target service processing procedure, so as to perform corresponding core service processing on the transaction request, thereby completing a current transaction. When the product layer comprises a plurality of different products, the embodiment of the specification can process transaction requests of the products, can be suitable for various bank core systems, realizes the decoupling of the business preprocessing process and the core business processing process of the transaction requests, and effectively improves the maintainability of the system.
Drawings
Fig. 1 is a schematic diagram of an application scenario according to an embodiment of the present disclosure;
FIG. 2 is a flow chart of a transaction processing method provided in the first aspect of the embodiments of the present disclosure;
fig. 3 is a schematic structural diagram of a transaction processing device provided in a second aspect of the embodiments of the present disclosure;
FIG. 4 is a schematic diagram of a transaction processing system provided in a third aspect of an embodiment of the present specification;
fig. 5 is a schematic structural diagram of an electronic device provided in the fourth aspect of the embodiments of the present description.
Detailed Description
In order to better understand the technical solutions of the embodiments of the present specification, the technical solutions of the embodiments of the present specification are described in detail below with reference to the accompanying drawings and specific embodiments, and it should be understood that the specific features of the embodiments and examples of the present specification are detailed descriptions of the technical solutions of the embodiments of the present specification, and are not limitations of the technical solutions of the embodiments and examples of the present specification, and the technical features of the embodiments and examples of the present specification may be combined with each other without conflict.
In the embodiment of the present specification, the bank core system refers to the core business logic for processing products such as deposit, loan, financing, and the like, and includes account opening, account entry, account counting, and the like. In addition, it can be understood that in the banking system, the business operation performed by the user for each product in the product layer is converted into a single transaction, for example: the transaction of the deposit includes a deposit transaction and a withdrawal transaction, and the transaction of the loan includes a put transaction and a repayment transaction.
Please refer to fig. 1, which is a schematic diagram of an application scenario according to an embodiment of the present disclosure. The bank core system 12 is configured to perform data interaction with the product layer 11 in the banking system, so as to complete processing of a transaction request issued by the product layer 11. The product layer 11 is configured to manage various products, detect a business operation triggered by a user for each product, and send a transaction request corresponding to the business operation to the bank core system 12 for processing. The product layer 11 includes a plurality of products, each of which has one or more transaction requests. It should be noted that the first product, the second product and the third product shown in fig. 1 are only used to illustrate that a plurality of different types of products are included in the product layer 11, and the specific number of products in the product layer 11 is not limited. For example, the product layer 11 may include, but is not limited to, a variety of products among deposit products, investment financing products, consumer products, loan products, insurance products, and the like.
As shown in fig. 1, the bank core system 12 may include a transaction processing device 121 and one or more business processing devices. It should be noted that the first service processing device 122, the second service processing device 123, and the third service processing device 124 shown in fig. 1 are only examples, and do not limit the specific number of service processing devices in the embodiments of the present specification. The transaction processing device 121 is configured to perform service preprocessing on a transaction request issued by the product layer 11, determine a service processing device corresponding to the transaction request, and send the transaction request to the corresponding service processing device. Each service processing device is used for carrying out corresponding core service processing on the received transaction request so as to complete the current transaction. For example, the deposit corresponds to a deposit transaction processing device for performing deposit transaction processing according to the received transaction request, and a withdrawal transaction processing device for performing deposit withdrawal processing according to the received transaction request. For another example, the loan is associated with a borrowing transaction processing device for performing borrowing processing in accordance with the received transaction request and a repayment transaction processing device for performing repayment processing in accordance with the received transaction request.
In a first aspect, an embodiment of the present disclosure provides a transaction processing method, configured to process transaction requests of multiple products in a product layer, for example, a transaction request corresponding to a deposit operation and a withdrawal operation included in a deposit product, a transaction request corresponding to a borrowing operation and a repayment operation included in a loan product, a transaction request corresponding to a purchase applying operation and a redemption operation included in a financing product, and the like. Referring to FIG. 2, the method includes steps S200-S206.
Step S200, a transaction request of a product in a product layer is obtained, wherein the transaction request comprises a service identifier.
The product layer comprises various products, such as deposit products, investment and financing products, consumer products, loan products, insurance products and the like, and can be determined according to actual application scenes. Each product comprises one or more business operations, and after a user triggers a certain business operation on a certain product at the product layer, the product layer converts the business operation into a transaction request. That is, each product may have one or more transaction requests. Each transaction request comprises a service identifier which can be used for uniquely identifying the service operation corresponding to the transaction request, and the service identifiers for the service operations of different products are different. After the transaction request of a certain product is obtained, the transaction request is analyzed, and then the service identifier included in the transaction request can be obtained. In a specific application scenario, the transaction request obtained in step S200 may be a transaction request corresponding to each business operation in products such as deposit, investment, financing, consumption, loan, or insurance.
In an alternative embodiment, the service identification may include product information and event information. The product information is used for representing a product to which the transaction request belongs, and the event information is used for representing business operation corresponding to the transaction request. For example, the transaction request is a transaction request formed after a user performs a 3-year periodic deposit operation on a product layer, the product information may be a 3-year periodic deposit, and the event information may be a deposit; or, the transaction request is a transaction request formed after the user performs a time-out operation on the product layer, the product information may be time-out, and the event information may be time-out.
In other alternative embodiments, the service identifier may be other information that can be used to uniquely identify the service operation corresponding to the transaction request, for example, the service identifier may be an identification code configured in advance for each service operation included in each product, the identification codes of different service operations are different, and the product layer may have the identification code in the transaction request when converting the service operation triggered by the user into the corresponding transaction request.
Step S202, the transaction request is processed by service preprocessing.
In the embodiment of the present specification, the service preprocessing process may be set according to the service processing requirement of each product. In an alternative embodiment, the business preprocessing process for the transaction request may include: checking and/or information complementing the transaction request; and obtaining the transaction request subjected to service preprocessing based on the transaction request supplemented by the verification and/or the information.
Specifically, verifying the transaction request may include at least: one or more of a status check of the account, a status check of the contract, and a control check of the transaction activity.
It will be appreciated that the transaction request may also include account information for the user. The status check of the account may include: and checking whether the state of the account is abnormal or not. For example, if an account is in a account-canceling state, it is determined that the account is in an abnormal state. In addition, when the account corresponds to the account level, the checking of the status of the account may further include: and checking the account grade and judging whether the account grade is authentic.
It will be appreciated that each bank making a transaction will enter into a corresponding contract with the customer. The contract state check is to check whether the contract state corresponding to the transaction request is abnormal. The method specifically comprises the following steps: and judging whether the contract corresponding to the transaction request is in an abnormal state, if so, indicating that the verification is not passed, and if so, indicating that the verification is passed.
The control verification of the transaction behavior is to verify whether the transaction behavior corresponding to the transaction request is within a preset authority range. The method specifically comprises the following steps: acquiring account information corresponding to the transaction request, and accordingly determining a transaction authority range corresponding to the account information; and judging whether the transaction behavior corresponding to the transaction request is in the transaction authority range, if so, passing the verification, and if not, failing to pass the verification. The transaction behavior corresponding to the transaction request can be determined by the service identifier of the transaction request. For example, the current account state is a frozen state, the transaction authority range of the current account only includes deposit and repayment, and if the transaction behavior corresponding to the transaction request is to perform deposit payment operation on the current account, it is determined that the transaction behavior corresponding to the transaction request is not in the transaction authority range, and the verification fails.
It should be noted that, when the transaction request is subjected to the service preprocessing, including the verification of the transaction request, and the transaction request which is not verified passes, it is indicated that the transaction request does not pass the service preprocessing, corresponding abnormal information is returned to the product layer, the subsequent processing of the transaction request is not continued, and the current transaction is ended. And for the transaction request passing the verification, obtaining the transaction request passing the service preprocessing based on the transaction request.
Specifically, the process of supplementing the transaction request may specifically include: and supplementing the product information in the transaction request and/or adding preset parameters into the transaction request. For example, the product information in the transaction request is 3-year-old period, and the related detailed information of the 3-year-old period may be supplemented to the transaction request. In specific application, the preset parameters may be set according to the service processing requirements of each product in the product layer, for example, the preset parameters may include interest rates, and the like. Of course, in addition to the above information, other information of the transaction request may be supplemented as necessary.
After the transaction request is checked and/or supplemented with information, the transaction request processed through the service preprocessing may be obtained based on the transaction request after the information supplementation is completed through the check and/or the information supplementation, so as to continue to perform the following step S204 on the transaction request processed through the service preprocessing. In an optional implementation manner, based on the transaction request after passing the verification and/or completing information completion, a specific process of obtaining the transaction request passing service preprocessing may be: and based on a pre-configured bill template, assembling the transaction requests which are completed through the verification and/or the information into a bill with a uniform format, wherein the bill still comprises the service identifier in the transaction request, and the bill is used as the transaction request preprocessed through the service. It should be noted that the document may be used as a transaction record or a bill specification for the user to inquire or reconcile.
The document template can be configured according to the business processing requirements of products in the actual product layer. The document template comprises a plurality of project names, and the process of assembling the document of the transaction request is as follows: and acquiring information corresponding to each item name from the transaction request, filling the information into the bill template, and generating the bill with a uniform format. For example, the item names in the document template may include: account, product, event, and transaction details, etc.
Of course, in other embodiments of the present specification, the transaction request after passing the verification and/or completing the information completion may also be directly used as the transaction request processed by the service preprocessing.
In an optional embodiment, before the verifying and/or the information completing the transaction request, the service preprocessing process may further include: determining the product type to which the service identifier of the transaction request belongs; and converting the message format of the transaction request into a pre-configured format corresponding to the product type so as to facilitate the subsequent processing of the transaction request. Specifically, the message format corresponding to each product type may be set in advance. For example, the product type may include deposit, loan, financing, consumption, insurance, and the like. In an alternative, a corresponding relationship between the service identifier and the product type may be configured in advance, and based on the corresponding relationship, the product type to which the service identifier of the transaction request belongs may be determined.
By executing the above step S202, the business preprocessing of transaction requests of various products can be completed. And then, the following steps S204 and S206 are further executed to respectively issue the transaction requests which are processed through the service preprocessing to the corresponding service processing processes for core service processing, so that the reduction of program redundancy is facilitated, and the design of a bank core system is simplified.
Step S204, based on the service identification of the transaction request through service preprocessing, searching a target service processing process corresponding to the service identification in a pre-configured information base, wherein the information base comprises corresponding relation information between various service identifications and corresponding service processing processes.
It should be noted that, in this embodiment of the present specification, a corresponding service processing process needs to be set in advance for a service processing requirement of each product, and the service processing process corresponding to each product may be one or multiple. Furthermore, for each product, the transaction types of the product may be divided according to the core service processing capability of each service processing process, so that one transaction type corresponds to one service processing process. The classification of transaction types may specifically be: and respectively aiming at each product, dividing the transaction request corresponding to one or more service operations of the product into one transaction type. For example, a business processing process for performing a periodic deposit operation corresponding to a deposit product may process periodic deposit operations of different time limits, and periodic deposit transactions of various time limits are classified into the same transaction type, but due to different specific business operations, business identifiers of corresponding transaction requests are different, but the two transaction requests are different only in parameters such as fixed interest rates and time limits, and may be subjected to deposit processing by the same business processing process. That is, each product may correspond to one or more transaction types, each transaction type corresponding to one or more business operations directed to the product, i.e., each transaction type corresponding to one or more business identifications.
After the corresponding relation between the service identification and the transaction type and the corresponding relation between the transaction type and the service processing progress are determined for each product, the information base can be configured in advance based on the two corresponding relations.
In an optional implementation manner, the information base may include correspondence information between a plurality of service identifications and corresponding service processing processes. One service processing process can correspond to one or more service identifications. Specifically, the preconfigured information base includes service processing procedures corresponding to a plurality of products and service identifiers corresponding to the products, and among the service identifiers, the service identifier corresponding to the same transaction type corresponds to the corresponding service processing procedure. For example, when a certain transaction type of a certain product corresponds to the service identifier F1, the service identifier F2, and the service identifier F3, and transaction requests belonging to the transaction type are all processed by the service processing process Q, the service identifier F1, the service identifier F2, and the service identifier F3 may be corresponding to the service processing process Q when configuring the information base.
Based on the configuration, after the service identifier of the transaction request preprocessed by the service is acquired, the service processing process corresponding to the service identifier can be searched in the information base, and the searched service processing process is used as a target processing process.
For convenience of configuration, in another optional implementation manner, an operation code may be defined in advance according to the service processing capability of each service processing process of each product, that is, one service processing process corresponds to one operation code, and then, a corresponding relationship between the service identifier and the service processing process is constructed based on the operation code. At this time, the preconfigured information base includes a first mapping relationship between the multiple service identifiers and the preconfigured multiple operation codes and a second mapping relationship between the multiple operation codes and the corresponding service processing processes.
For example, taking a deposit product as an example, the deposit product includes a deposit service operation and a withdrawal service operation, the deposit service operation includes a periodic deposit service operation and a current deposit service operation, and the withdrawal service operation correspondingly includes a periodic withdrawal service operation and a current withdrawal service operation. Suppose that the business process corresponding to the deposit product includes: a service processing process A1, a service processing process A2, a service processing process A3 and a service processing process A4. The service processing process A1 is used for executing the periodic deposit processing, the service processing process A2 is used for executing the live deposit processing, the service processing process A3 is used for executing the periodic withdrawal processing, and the service processing process A4 is used for executing the live withdrawal processing. Corresponding to the service processing process A1, the configured operation code may be CREDIT _ TIME, which indicates that the operation code is stored periodically; corresponding to the service processing process A2, the configured operation code may be CREDIT _ DEMAND, which indicates a live-in; corresponding to the service processing process A3, the configured operation code may be debug _ TIME, which indicates periodic fetching; corresponding to the service processing process A4, the configured operation code may be deep _ DEMAND, which indicates live fetch. The second mapping relationship of the specific configuration may be as shown in table 1.
TABLE 1
Further, a first mapping relationship between each operation code and each service identifier is configured based on table 1. It is assumed that the deposit product specifically includes a 3-year fixed deposit, a 1-year fixed deposit, and a demand deposit, and the deposit event includes deposit and withdrawal. Specifically, when the service identification includes product information and event information, a first mapping relationship between the service identification and the operation code of the transaction request related to the deposit product may be as shown in table 2.
TABLE 2
Since the 3-year periodic deposit operation and the 1-year periodic deposit operation are different only in parameters such as fixed interest rate, time limit and the like, the deposit processing can be executed by the same business processing process. Thus, as shown in Table 2, the service identification of both the 3-year periodic deposit operation and the 1-year periodic deposit operation may be associated with the operation code CREDIT _ TIME. Similarly, the service identifiers of the 3-year periodic drawing operation and the 1-year periodic drawing operation can be associated with the operation code DEBIT _ TIME. And associating the service identification of the current storage operation with the operation code CREDIT _ DEMAND, and associating the service identification of the current drawing operation with the operation code DEBIT _ DEMAND.
Based on the above configuration, the process of determining the target business process may include: based on the service identifier of the transaction request preprocessed by the service, searching a first operation code corresponding to the service identifier in the first mapping relation; based on the first operation code, searching a business processing process corresponding to the first operation code in the second mapping relation, and taking the business processing process as the target business processing process.
It can be understood that, in this embodiment of the present specification, the information base specifically includes feature identifiers of stored service processing processes, the second mapping relationship specifically includes a one-to-one correspondence relationship between each operation code and a feature identifier of each service processing process, the feature identifiers of different service processing processes are different, and the service processing process can be called through the feature identifier of the service processing process.
Therefore, the transaction processing process of the transaction requests of different products issued by the product layer can be decoupled from the core service processing process, so that the transaction processing process or the core service processing process can be independently modified or configured, and the maintainability of the system is effectively improved.
In an alternative embodiment, the first mapping relationship and the second mapping relationship are configurable, considering that there may be a new addition of business operations. In order to facilitate the configuration of the operation of the new service, the transaction processing method provided in the embodiment of the present specification may further include: when a newly added service configuration instruction is detected, acquiring a service identifier of a newly added service operation, and determining a second operation code corresponding to the service identifier of the newly added service operation; and adding the service identifier of the newly added service operation and the second operation code into the first mapping relation.
It can be understood that, for a newly added service operation that does not belong to an existing transaction type, a service processing process for performing core service processing on the newly added service operation needs to be correspondingly additionally added. And for the newly added service operation belonging to the existing transaction type, the service processing process does not need to be additionally arranged, and the core service processing is carried out on the newly added service operation by the service processing process corresponding to the transaction type. Therefore, when a service processing process for performing core service processing on the newly added service operation needs to be correspondingly additionally added, that is, when a service processing process associated with the second operation code does not exist in the second mapping relationship, the service processing process corresponding to the second operation code needs to be determined, and the second operation code and the service processing process corresponding to the second operation code need to be added to the second mapping relationship.
For example, the product layer comprises a deposit product, a 2-year periodic deposit business operation and a 2-year periodic withdrawal business operation are added on the basis of the existing 1-year periodic deposit and 3-year periodic deposit, and a business identifier of the added business operation is configured. At this time, the service identifier of the newly added service operation includes a service identifier of a 2-year periodic deposit operation and a service identifier of a 2-year periodic withdrawal operation. The newly added transaction requests corresponding to the 2-year periodic deposit and deposit operation and the 2-year periodic withdrawal operation belong to the existing transaction types corresponding to the deposit products, namely the transaction request corresponding to the 2-year periodic deposit and deposit operation belongs to a periodic deposit transaction, and the transaction request corresponding to the 2-year periodic withdrawal operation belongs to a periodic withdrawal transaction. Therefore, the service identifier M1 corresponding to the 2-year periodic operation may be associated with the operation code CREDIT _ TIME in table 2, and the service identifier M2 corresponding to the 2-year periodic operation may be associated with the operation code DEBIT _ TIME in table 2. That is to say, the operation code CREDIT _ TIME is the second operation code P1 corresponding to the service identifier M1, and the operation code DEBIT _ TIME is the second operation code P2 corresponding to the service identifier M2. Then, the corresponding relation between the service identifier M1 and the second operation code P1 and the corresponding relation between the service identifier M2 and the second operation code P2 are added in the pre-configured first mapping relation.
For another example, the product layer includes a financial product, a financial service operation is added on the basis of the existing financial service operation, and a service identifier of the financial service operation is configured. If the transaction request corresponding to the financial management service operation does not belong to the existing transaction type corresponding to the financial product, a service processing process B for performing core service processing on the transaction request corresponding to the newly added financial management service operation needs to be additionally added, and a second operation code P3 associated with the service processing process B is configured. And associating the second operation code P3 with the service identification M3 of the new financial service. At this time, in addition to the corresponding relationship between the service identifier M3 and the second operation code P3, which needs to be added in the preconfigured first mapping relationship, the corresponding relationship between the second operation code P3 and the service processing process B needs to be added in the preconfigured second mapping relationship, so that after the transaction request corresponding to the newly added financing service operation is subjected to service preprocessing according to the above step 202, the corresponding service processing process B can be found based on the first mapping relationship and the second mapping relationship, and further the core service processing of the transaction request is completed.
Specifically, in an optional implementation manner, the process of acquiring the service identifier of the newly added service operation and determining the second operation code corresponding to the service identifier of the newly added service operation may be: detecting whether a trigger operation for configuring a newly added service exists; when the triggering operation is detected, a newly added service configuration instruction is triggered, so that a newly added service configuration interface is popped up. An operator with configuration authority can input the service identifier of the newly added service operation in the configuration interface, and select the existing operation code or input a new operation code as a second operation code corresponding to the service identifier, so that the service identifier of the newly added service operation and the second operation code corresponding to the service identifier can be obtained. It should be noted that the existing operation code is an operation code in the preconfigured first mapping relationship, and for example, the existing operation code may be presented in a form of a drop-down list for an operator to select.
Further, when it is detected that the operator inputs a new operation code as a second operation code corresponding to the service identifier of the newly added service operation, it is determined that a service processing procedure associated with the second operation code does not exist in the second mapping relationship, and at this time, a feature identifier of the service processing procedure corresponding to the second operation code, which is input by the operator, needs to be further obtained, so that the second operation code and the service processing procedure corresponding to the second operation code are added to the second mapping relationship.
In another optional implementation, when a new service operation is added to the product layer, the product layer generates a new service configuration instruction according to the added new service operation. The new service configuration instruction comprises a service identifier of the new service operation, a second operation code corresponding to the service identifier and a service processing process corresponding to the second operation code. At this time, the process of obtaining the service identifier of the newly added service operation and determining the second operation code corresponding to the service identifier of the newly added service operation may be: when a newly added service configuration instruction issued by any product layer is received, acquiring a service identifier of a newly added service operation, a second operation code corresponding to the service identifier and a service processing process corresponding to the second operation code from the newly added service configuration instruction.
Adding a service identifier of the newly added service operation and a second operation code corresponding to the service identifier into a first mapping relation configured in advance, and detecting whether a service processing process associated with the second operation code exists in the second mapping relation configured in advance; when the second mapping relation does not have the service processing process associated with the second operation code, adding the second operation code and the service processing process corresponding to the second operation code into the second mapping relation; and when the second mapping relation has the service processing progress corresponding to the second operation code, ending the configuration.
Therefore, in the transaction processing method provided in the embodiment of the present specification, when a service operation is newly added in a product layer, only mapping configuration needs to be performed based on relevant information of the newly added service operation, and thus the method has very good extensibility.
Step S206, the transaction request which passes through the service preprocessing is sent to a target service processing process for corresponding service processing.
After determining the target service processing process corresponding to the transaction request subjected to the service preprocessing according to the step S204, the target service processing process may be invoked to continue performing core service processing on the transaction request, thereby completing the current transaction. For example, when the transaction request processed through the service preprocessing is a transaction request corresponding to a periodic deposit operation, the corresponding target service processing process may be configured to read information of an account, an amount of money, a fixed interest rate, a term and the like in the transaction request, and deposit a corresponding amount of money in the account based on the fixed interest rate and the term, that is, complete the periodic deposit transaction.
In a specific application scenario of the embodiment of the present specification, the transaction processing process may specifically be: after a transaction request of a product in a product layer is obtained, the product type to which a service identifier in the transaction request belongs can be determined, the message format of the transaction request is converted into a pre-configured format corresponding to the product type, then the transaction request subjected to the message conversion is verified and/or information is supplemented, and then the transaction request subjected to the verification and/or information supplementation is assembled into a receipt with a uniform format based on a pre-configured receipt template to serve as a transaction record or bill detail for a user to inquire or reconcile; wherein, the receipt still comprises the service identifier in the transaction request; then, based on a first mapping relation configured in advance, a first operation code corresponding to the service identifier is determined, and the first operation code is also added to the bill; and then, based on a second mapping relation configured in advance, finding a target business processing process corresponding to the first operation code in the bill, and calling the target business processing process to continue to perform core business processing on the bill so as to complete the current transaction.
The transaction processing method provided by the embodiment of the invention can be suitable for various bank core systems such as deposit, investment and financing, consumption, loan and insurance, and has better universality. Meanwhile, the transaction preprocessing process of the transaction request of each product issued by the product layer is decoupled from the core service processing process, and the maintainability of the system is effectively improved.
In a second aspect, based on the same inventive concept, an embodiment of the present specification further provides a transaction processing apparatus, please refer to fig. 3, including:
a first obtaining unit 31, configured to obtain a transaction request for a product in a product layer, where the transaction request includes a service identifier, and the product layer includes multiple products;
a preprocessing unit 32, configured to perform service preprocessing on the transaction request;
a determining unit 33, configured to search, based on a service identifier of the transaction request subjected to service preprocessing, a pre-configured information base for a target service processing procedure corresponding to the service identifier, where the information base includes information about correspondence between multiple service identifiers and corresponding service processing procedures;
a sending unit 34, configured to send the transaction request subjected to service preprocessing to the target service processing process for performing corresponding service processing.
In an optional implementation manner, the information base includes a first mapping relationship between a plurality of service identifications and a plurality of preconfigured operation codes and a second mapping relationship between the plurality of operation codes and corresponding service processing processes. At this time, the determining unit 33 includes:
a first determining subunit 331, configured to search, based on a service identifier of the transaction request preprocessed by a service, a first operation code corresponding to the service identifier in the first mapping relationship;
a second determining subunit 332, configured to search, based on the first operation code, a service processing procedure corresponding to the first operation code in the second mapping relationship, and use the service processing procedure as the target service processing procedure.
In an alternative embodiment, the transaction processing device further comprises:
a second obtaining unit 35, configured to obtain, when a new service configuration instruction is detected, a service identifier of a new service operation, and determine a second operation code corresponding to the service identifier of the new service operation;
a first adding unit 36, configured to add the service identifier of the newly added service operation and the second operation code to the first mapping relationship.
In an alternative embodiment, the transaction processing device further comprises:
a second adding unit 37, configured to determine, when there is no service processing process associated with the second operation code in the second mapping relationship, a service processing process corresponding to the second operation code, and add the second operation code and the service processing process corresponding to the second operation code to the second mapping relationship.
In an alternative embodiment, the preprocessing unit 32 comprises:
a first processing subunit 321, configured to perform verification and/or information completion on the transaction request;
a second processing subunit 322, configured to obtain the transaction request preprocessed by the service based on the transaction request completed by the checksum and/or the information.
In an optional implementation manner, the second processing subunit 322 is specifically configured to: based on a pre-configured bill template, assembling the transaction requests which pass the verification and/or the information completion into bills with uniform formats, wherein the bills comprise service identifiers in the transaction requests; and using the receipt as the transaction request preprocessed through the service.
In an alternative embodiment, the preprocessing unit 32 further comprises:
a format conversion subunit 323, configured to determine a product type to which the service identifier of the transaction request belongs; and converting the message format of the transaction request into a preset format corresponding to the product type.
It should be noted that, the transaction processing apparatus provided in the embodiments of the present specification, the specific manner in which each unit performs the operation has been described in detail in the above method embodiments, and will not be described in detail here.
In practical application, the transaction processing device provided in the embodiment of the present specification may be provided in the form of middleware, and is applied to various banking core business systems to implement business preprocessing of transaction requests of products in a product layer. Especially when a bank core business system needs to be newly built, only the middleware of the transaction processing device needs to be introduced and a corresponding business processing process needs to be designed, so that the design difficulty of the system is simplified.
In a third aspect, based on the same inventive concept, the embodiment of the present specification further provides a transaction processing system. As shown in fig. 4, the system includes: a transaction processing device 41 and one or more service processing devices 42. It should be noted that the number of the service processing devices 42 shown in fig. 4 is only an example, and does not limit the specific number of the service processing devices 42 in the embodiment of the present specification.
The transaction processing device 41 is configured to obtain a transaction request of a product in a product layer, where the transaction request includes a service identifier, and the product layer includes multiple products; performing service preprocessing on the transaction request; searching a target service processing device corresponding to the service identifier in a pre-configured information base based on the service identifier of the transaction request subjected to service preprocessing, wherein the information base comprises corresponding relation information between various service identifiers and corresponding service processing devices; and sending the transaction request subjected to service preprocessing to the target service processing device.
Each of the service processing devices 42 is configured to perform core service processing on the received transaction request to complete the current transaction.
It should be noted that, in the transaction processing system provided in the embodiments of the present specification, the specific implementation of the transaction processing apparatus has been described in detail in the above method embodiments, and will not be described in detail here.
In a fourth aspect, based on the same inventive concept as the transaction processing method in the foregoing embodiment, the present invention further provides an electronic device, as shown in fig. 5, including a memory 504, one or more processors 502, and a computer program stored on the memory 504 and executable on the processor 502, wherein the processor 502 implements the steps of the foregoing transaction processing method when executing the program.
Where in fig. 5 a bus architecture (represented by bus 500) is shown, bus 500 may include any number of interconnected buses and bridges, and bus 500 links together various circuits including one or more processors, represented by processor 502, and memory, represented by memory 504. The bus 500 may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. A bus interface 506 provides an interface between the bus 500 and the receiver 501 and transmitter 503. The receiver 501 and the transmitter 503 may be the same element, i.e. a transceiver, providing a means for communicating with various other apparatus over a transmission medium. The processor 502 is responsible for managing the bus 500 and general processing, and the memory 504 may be used for storing data used by the processor 502 in performing operations.
In a fifth aspect, based on the inventive concept of the transaction processing method in the foregoing embodiments, the present invention further provides a computer-readable storage medium, on which a computer program is stored, which when executed by a processor, implements the steps of any one of the foregoing transaction processing methods.
The description has been presented with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the description. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
While the preferred embodiments of the present specification have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all changes and modifications that fall within the scope of the specification.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present specification without departing from the spirit and scope of the specification. Thus, if such modifications and variations of the present specification fall within the scope of the claims of the present specification and their equivalents, the specification is intended to include such modifications and variations.
Claims (11)
1. A transaction processing method, comprising:
acquiring a transaction request of a product in a product layer, wherein the transaction request comprises a service identifier, and the product layer comprises a plurality of products;
the transaction request is subjected to business preprocessing through an introduced middleware, and the middleware is applied to various banking core business systems and is used for preprocessing the business of the transaction request of each product in a product layer;
based on the service identifier of the transaction request processed by the service preprocessing, searching a target service processing process corresponding to the service identifier in a pre-configured information base, comprising: the information base comprises a first mapping relation between various service identifications and a plurality of preconfigured operation codes and a second mapping relation between the plurality of operation codes and corresponding service processing processes, the operation codes are defined in advance according to the service processing capacity of each service processing process of each product, and the first operation codes corresponding to the service identifications are searched in the first mapping relation based on the service identifications of the transaction requests subjected to service preprocessing; based on the first operation code, searching a business processing process corresponding to the first operation code in the second mapping relation, and taking the business processing process as the target business processing process;
when a new service configuration instruction is detected, acquiring a service identifier of a new service operation, and determining a second operation code corresponding to the service identifier of the new service operation; adding the service identifier of the newly added service operation and the second operation code into the first mapping relation; when the second mapping relation does not have the service processing process associated with the second operation code, determining the service processing process corresponding to the second operation code, and adding the second operation code and the service processing process corresponding to the second operation code into the second mapping relation;
and sending the transaction request subjected to service preprocessing to the target service processing process for corresponding service processing.
2. The method of claim 1, the business preprocessing the transaction request, comprising:
checking and/or information complementing the transaction request;
and obtaining the transaction request which passes the service preprocessing based on the transaction request which passes the verification and/or information completion.
3. The method of claim 2, said deriving said transaction request preprocessed by traffic based on said transaction request complemented by said checksum/or information, comprising:
based on a pre-configured bill template, assembling the transaction requests completed through the verification and/or the information into bills with uniform formats, wherein the bills comprise service identifiers in the transaction requests;
and using the receipt as the transaction request preprocessed through the service.
4. The method of claim 2, prior to said verifying and/or supplementing information with said transaction request, further comprising:
determining the product type to which the service identifier of the transaction request belongs;
and converting the message format of the transaction request into a pre-configured format corresponding to the product type.
5. A transaction processing device comprising:
the system comprises a first acquisition unit, a second acquisition unit and a third acquisition unit, wherein the first acquisition unit is used for acquiring a transaction request of a product in a product layer, the transaction request comprises a service identifier, and the product layer comprises a plurality of products;
the preprocessing unit is used for preprocessing the business of the transaction request through introduced middleware, and the middleware is applied to various bank core business systems and is used for preprocessing the business of the transaction request of each product in a product layer;
a determining unit, configured to search, based on a service identifier of the transaction request subjected to service preprocessing, a target service processing process corresponding to the service identifier in a preconfigured information base, where the information base includes a first mapping relationship between multiple service identifiers and preconfigured multiple operation codes and a second mapping relationship between the multiple operation codes and corresponding service processing processes, and an operation code is defined in advance according to a service processing capability of each service processing process of each product, and the determining unit includes: a first determining subunit, configured to search, based on a service identifier of the transaction request preprocessed by a service, a first operation code corresponding to the service identifier in the first mapping relationship; a second determining subunit, configured to search, based on the first operation code, a service processing procedure corresponding to the first operation code in the second mapping relationship, and use the service processing procedure as the target service processing procedure;
the second obtaining unit is used for obtaining the service identifier of the newly added service operation when the newly added service configuration instruction is detected, and determining a second operation code corresponding to the service identifier of the newly added service operation;
a first adding unit, configured to add the service identifier of the newly added service operation and the second operation code to the first mapping relationship;
a second adding unit, configured to determine, when a service processing process associated with the second operation code does not exist in the second mapping relationship, a service processing process corresponding to the second operation code, and add the second operation code and the service processing process corresponding to the second operation code to the second mapping relationship;
and the sending unit is used for sending the transaction request subjected to service preprocessing to the target service processing process for corresponding service processing.
6. The apparatus of claim 5, the pre-processing unit comprising:
the first processing subunit is used for verifying and/or supplementing information to the transaction request;
and the second processing subunit is used for obtaining the transaction request which passes through the service preprocessing based on the transaction request which passes through the verification and/or information complementation.
7. The apparatus of claim 6, the second processing subunit being specifically configured to: based on a pre-configured bill template, assembling the transaction requests which pass the verification and/or the information completion into bills with uniform formats, wherein the bills comprise service identifiers in the transaction requests; and using the receipt as the transaction request preprocessed through the service.
8. The apparatus of claim 6, the pre-processing unit further comprising:
the format conversion subunit is used for determining the product type to which the service identifier of the transaction request belongs; and converting the message format of the transaction request into a preset format corresponding to the product type.
9. A transaction processing system comprising: transaction processing means and one or more transaction processing means,
the transaction processing device is used for acquiring a transaction request of a product in a product layer, wherein the transaction request comprises a service identifier, and the product layer comprises a plurality of products; the transaction request is subjected to business preprocessing through an introduced middleware, and the middleware is applied to various banking core business systems and is used for preprocessing the business of the transaction request of each product in a product layer; based on the service identifier of the transaction request processed by the service preprocessing, searching a target service processing device corresponding to the service identifier in a pre-configured information base, comprising: the information base comprises a first mapping relation between various service identifications and a plurality of preconfigured operation codes and a second mapping relation between the plurality of operation codes and corresponding service processing processes, the operation codes are defined in advance according to the service processing capacity of each service processing process of each product, and the first operation codes corresponding to the service identifications are searched in the first mapping relation based on the service identifications of the transaction requests preprocessed by the services; based on the first operation code, searching a business processing process corresponding to the first operation code in the second mapping relation, and taking the business processing process as a target business processing process; sending the transaction request subjected to service preprocessing to the target service processing device, acquiring a service identifier of a newly added service operation when a newly added service configuration instruction is detected, and determining a second operation code corresponding to the service identifier of the newly added service operation; adding the service identifier of the newly added service operation and the second operation code into the first mapping relation; when the second mapping relation does not have the service processing process associated with the second operation code, determining the service processing process corresponding to the second operation code, and adding the second operation code and the service processing process corresponding to the second operation code into the second mapping relation;
each service processing device is used for performing core service processing on the received transaction request so as to complete the current transaction.
10. An electronic device, comprising:
a memory;
one or more processors; and
the transaction processing device of any of claims 5-8, stored in the memory and configured to be executed by one or more processors.
11. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810709167.3A CN108961039B (en) | 2018-07-02 | 2018-07-02 | Transaction processing method, device and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810709167.3A CN108961039B (en) | 2018-07-02 | 2018-07-02 | Transaction processing method, device and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108961039A CN108961039A (en) | 2018-12-07 |
| CN108961039B true CN108961039B (en) | 2023-03-31 |
Family
ID=64484695
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810709167.3A Active CN108961039B (en) | 2018-07-02 | 2018-07-02 | Transaction processing method, device and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108961039B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112330452B (en) * | 2020-11-17 | 2024-04-23 | 杭州大搜车汽车服务有限公司 | Transaction data processing method, device, computer equipment and storage medium |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102831499A (en) * | 2012-08-06 | 2012-12-19 | 北京亿速码数据处理有限责任公司 | Nationwide city smart-card interconnection and intercommunication system and method utilizing same |
| CN103338230A (en) * | 2013-06-03 | 2013-10-02 | 广州天宁信息技术有限公司 | A method and a system both for processing business data |
| CN104951481A (en) * | 2014-03-31 | 2015-09-30 | 中国移动通信集团云南有限公司 | Method and device for managing database connection |
| CN105205717A (en) * | 2015-11-10 | 2015-12-30 | 中国建设银行股份有限公司 | Bank system transaction information management method, system and general account transfer system |
| CN106330769A (en) * | 2016-11-15 | 2017-01-11 | 腾讯科技（深圳）有限公司 | Business processing method and server |
| CN106875170A (en) * | 2016-07-22 | 2017-06-20 | 阿里巴巴集团控股有限公司 | A kind of method and device for business processing of intermediate business system |
| CN107832134A (en) * | 2017-11-24 | 2018-03-23 | 平安科技（深圳）有限公司 | multi-task processing method, application server and storage medium |
Family Cites Families (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2002101510A2 (en) * | 2001-06-13 | 2002-12-19 | Caminus Corporation | System architecture and method for energy industry trading and transaction management |
| CN100411367C (en) * | 2002-11-19 | 2008-08-13 | 华为技术有限公司 | Method and apparatus for implementing simultaneous processing of multiple service logic on server |
| CN100498719C (en) * | 2006-12-30 | 2009-06-10 | 中国建设银行股份有限公司 | Method and device for executing batch processing job |
| CN100507922C (en) * | 2007-11-21 | 2009-07-01 | 金蝶软件（中国）有限公司 | Method and system for processing multiple services bills data |
| CN101877158A (en) * | 2010-03-23 | 2010-11-03 | 苏州德融嘉信信用管理技术有限公司 | Front service platform of bank and operation processing method thereof |
| CN103679530A (en) * | 2012-09-07 | 2014-03-26 | 中国银联股份有限公司 | Intelligent service database generation system and method as well as service processing system and method |
| CN103501326A (en) * | 2013-09-26 | 2014-01-08 | 中国银行股份有限公司 | Data processing method and system based on middleware |
| US10372701B2 (en) * | 2016-02-01 | 2019-08-06 | International Business Machines Corporation | Transaction processor |
| CN107911331B (en) * | 2016-12-24 | 2021-04-06 | 深圳壹账通智能科技有限公司 | Data verification method and server |
| CN106973078B (en) * | 2017-01-16 | 2018-08-03 | 平安银行股份有限公司 | The method and information exchange control system of business data processing |
| CN107025559B (en) * | 2017-01-26 | 2020-09-18 | 创新先进技术有限公司 | Service processing method and device |
| CN107516272A (en) * | 2017-06-29 | 2017-12-26 | 中国建设银行股份有限公司 | Transaction processing method, system, device and storage medium based on unified message |
| CN107369088B (en) * | 2017-07-19 | 2021-05-07 | 中国银行股份有限公司 | Method and device for processing account transaction |
| CN108132923A (en) * | 2017-12-06 | 2018-06-08 | 口碑(上海)信息技术有限公司 | The generation method and system of business paper |
| CN108156236B (en) * | 2017-12-22 | 2021-05-25 | 平安养老保险股份有限公司 | Service request processing method and device, computer equipment and storage medium |
-
2018
- 2018-07-02 CN CN201810709167.3A patent/CN108961039B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102831499A (en) * | 2012-08-06 | 2012-12-19 | 北京亿速码数据处理有限责任公司 | Nationwide city smart-card interconnection and intercommunication system and method utilizing same |
| CN103338230A (en) * | 2013-06-03 | 2013-10-02 | 广州天宁信息技术有限公司 | A method and a system both for processing business data |
| CN104951481A (en) * | 2014-03-31 | 2015-09-30 | 中国移动通信集团云南有限公司 | Method and device for managing database connection |
| CN105205717A (en) * | 2015-11-10 | 2015-12-30 | 中国建设银行股份有限公司 | Bank system transaction information management method, system and general account transfer system |
| CN106875170A (en) * | 2016-07-22 | 2017-06-20 | 阿里巴巴集团控股有限公司 | A kind of method and device for business processing of intermediate business system |
| CN106330769A (en) * | 2016-11-15 | 2017-01-11 | 腾讯科技（深圳）有限公司 | Business processing method and server |
| CN107832134A (en) * | 2017-11-24 | 2018-03-23 | 平安科技（深圳）有限公司 | multi-task processing method, application server and storage medium |
Non-Patent Citations (1)
| Title |
|---|
| 商业银行中间业务平台业务交易的定制与实现;张茹;《华南金融电脑》;20081110(第11期);37-40 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108961039A (en) | 2018-12-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110263024B (en) | Data processing method, terminal device and computer storage medium | |
| US10698795B2 (en) | Virtual payments environment | |
| CN110782240B (en) | Business data processing method and device, computer equipment and storage medium | |
| CN110458562B (en) | Bill reimbursement method, device and equipment and computer storage medium | |
| US11087371B2 (en) | Blockchain-based invoice creation method apparatus, and electronic device | |
| CN109285069B (en) | Resource transfer method, device and server | |
| CN111091358B (en) | Unified processing method and system for multiple payment channels | |
| CN110163691B (en) | Invoice creating method and device based on block chain and electronic equipment | |
| CN110060139B (en) | Accounting processing method and device | |
| CN104376452A (en) | System and method for managing payment success rate on basis of international card payment channel | |
| CN107665463A (en) | Method for processing resource, device, storage medium and the computer equipment of investment product | |
| CN112907244A (en) | Data processing method, device and equipment based on block chain and readable storage medium | |
| US20140229368A1 (en) | Method and system for merchant debit routing table change detection | |
| CN110781134A (en) | Data processing method and device, computer storage medium and electronic equipment | |
| CN108961039B (en) | Transaction processing method, device and system | |
| US20230385891A1 (en) | Prototype message service | |
| CN113159733A (en) | Online processing method, device and equipment for accumulation fund extraction service and storage medium | |
| CN117036115A (en) | Contract data verification method, device and server | |
| CN112181628A (en) | Resource transfer method, device and system and electronic equipment | |
| CN113034275A (en) | Management system and method based on block chain network and terminal equipment | |
| CN111367776A (en) | Recording method, device, equipment and storage medium of resource transfer service | |
| CN112967049B (en) | Method and device for issuing receivable through block chain | |
| CN110648090A (en) | Logistics process node management method and system | |
| CN113450096A (en) | Resource transfer data processing method and device, electronic equipment and medium | |
| CN106569791A (en) | Method and device for processing data objects |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20200925 Address after: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Applicant after: Innovative advanced technology Co.,Ltd. Address before: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Applicant before: Advanced innovation technology Co.,Ltd. Effective date of registration: 20200925 Address after: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Applicant after: Advanced innovation technology Co.,Ltd. Address before: A four-storey 847 mailbox in Grand Cayman Capital Building, British Cayman Islands Applicant before: Alibaba Group Holding Ltd. |
|
| TA01 | Transfer of patent application right | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |