CN117952733A - Method and system for processing bank product transaction based on request order model - Google Patents

Abstract

The invention relates to a method and a system for processing a bank product transaction based on a request order model. According to the method, the order model of the e-commerce platform is transformed into the financial order model which can be used for a transaction scene of a bank for a customer, the transaction flow control of the original system is unified by using the request order model, the product transaction scene is combined with the request order, and the scene related system business flow instance is converted into the request order flow by the configuration method. In addition, the invention can extract transaction information from the service system without perception and record the transaction information into the order model of the transaction center, thereby realizing the unified management of the transaction center on the scattered product transaction scene of the bank system.

Description

Method and system for processing bank product transaction based on request order model

Technical Field

The invention belongs to the technical field of a bank product transaction processing method, and particularly relates to a method and a system for processing bank product transaction based on a request order model.

Background

The digitalized transformation of banks is entering into intelligent banks bank4.0 age of production and life by reconstructing banking business through financial science and technology and embedding the capabilities thereof in bank1.0 age of services with physical network points, bank2.0 age of providing self-service such as ATM machine, bank3.0 age of providing services through mobile entrance such as APP. In this process, the system architecture of the bank is also evolving continuously, but the evolution of the system architecture is not to directly replace the old architecture system with the new architecture system, so that in order to ensure the stability and the integrity of the service, a bypass architecture is usually added on the basis of the original architecture, and then smooth transition is performed through data migration, and meanwhile, the new system is synchronously constructed by other manufacturers. However, a result of the process appears, a huge IT system of the bank is continuously evolved forward in a macroscopic scale, but the microscopic IT system level is difficult and heavy in the evolution process and the cost is higher and higher due to the fact that the architecture is too complex and a system vertical shaft stands.

In the traditional period of taking the product as the center, because the product is the leading party of the bank, the customer is the party of receiving the product passively, the obstruction is not obvious at this time, but after the customer is online through the mobile internet, the past product-centered is turned to the customer-centered, the core concept of taking the customer as the center is that the demand of the customer diversification is met through more humanized product and more agile service, the control right of the demand is reversed, the bank must promote the service efficiency in order to obtain more customers, the customer experience is improved, and the traditional IT construction scheme can not meet the current customer demand completely.

Specifically, the bank product system needs to make the customer use corresponding product service through transaction actions with the customer, for example, the customer needs to deposit funds into the bank through deposit operation, use transfer service through transfer operation and purchase and hold financial products through financial operation, but these operations are all self-series transaction processes in the respective systems, the internal systems of the bank are generally not uniformly considered and designed during construction, so that channel display modes, calling interfaces and service logic required by various types of services of the bank when the services are executed on the system are very complex, and for example, deposit in the prior art, the demand deposit and the regular deposit in many traditional bank systems are designed into two sets of mutually independent functional modules on the operation interfaces, interface processing and transaction control.

In addition, when banks realize various business processes on application architecture, all transaction process control logic is usually realized directly on a product system.

A. Taking the cross-bank transfer transaction as an example, the channel system initiates the transaction, calls the secondary payment system, and the secondary payment system firstly calls the core service system to deduct the balance of the customer account, and then calls the pedestrian payment system to conduct cross-bank clearing, and at the moment, the transaction flow control logic is located in the secondary payment system, as shown in fig. 1.

B. taking cash deposit transaction as an example, the channel system initiates transaction, and invokes the core business system, wherein the cash module accepts cash deposit, the account module accepts account deposit, and the transaction flow control logic falls into the core business system at this time, as shown in fig. 2.

C. Taking financial purchase transaction as an example, the channel system initiates transaction, invokes the financial system, invokes the core business system to complete customer account deduction, and then executes own financial accounting, as shown in fig. 3.

Through the above three examples, it is shown that when designing the control logic of the non-transaction flow, the control of the whole transaction logic is usually realized by the product system at the back end, so that the transaction flows of different services can fall on different systems, and the corresponding processing flow logics are also designed independently. Although the system accords with the common habit of people, the system is simpler to design in a single system, and with the increase of the complexity of product business, the system needs to be expanded in the original system or be connected with other product business systems for assistance. The example of C financial management is expanded to enable the financial management system to support the purchasing behavior of the I and II accounts at the same time, so that the financial management system can be completed by docking with the mutual-gold core system, as shown in fig. 4.

Based on the design structure, the product transaction rules are scattered in each product business system, and the flow is independently controlled by each system.

The above-mentioned various use cases are simple in design in a certain vertical product business field, but the drawbacks are also quite obvious:

(1) The product business independently designs the transaction flow, has no unified transaction mode, and is not beneficial to the rapid design and landing of new business;

(2) Transaction control is distributed in each product system, logic capable of guaranteeing data consistency needs to be repeatedly developed, and the cost is high and the landing is slow;

(3) When the product transaction logic of the current system needs to be newly added or changed, the corresponding system needs to be transformed or docked, and the decoupling is difficult;

(4) The channel system needs to be docked with various product systems to realize the logic of transaction processing, the newly built product system needs to be transformed to be docked, and the whole transaction link is gradually complex, as shown in fig. 5.

Disclosure of Invention

In order to overcome the defects of the conventional banking product transaction processing method, the invention provides a novel method for processing banking product transaction based on a request order model.

Analyzing the problems of the existing bank product transaction processing method, we find that: the core of the problem is that the rules of the product are tightly coupled to the flow of the transaction, and if both can be decoupled, the above problem will be solved.

Based on the above conception, the invention uses the request order model to complete decoupling of the product rule and the transaction flow, while the entity product and the virtual service use the order transaction model to complete unification of the transaction flow in the electronic commerce platform at present, banking business and electronic commerce have essential differences, namely the exchange behavior of the entity product or the virtual service and funds between the electronic commerce platform and a client, and for banking business, the transaction between the bank and the client is essentially the flow of the funds of the client, for example, the client flows the funds to (pays) the bank when deposit business occurs, and the bank generates liabilities (delivery); the customer transfers funds out (pays) and transfers funds to the target user (deliveries) when the transfer transaction occurs; the customer flows funds to (pays) the bank at the time of financial product purchase, and the bank provides (delivers) product shares as shown in the following table:

Through the above case analysis, the present invention anchors two defined points for stability of the model:

1. the one-way mode of payment by the customer and delivery by the bank is used, and the reverse mode of payment by the bank and delivery by the customer is not adopted.

2. Instead of using a product transaction scenario to determine the flow of funds, funds in an e-commerce platform order can only be represented by payment.

After determining the model definition of the order, the pretreatment work before the generation of the order is needed, the part of banking business comprises a plurality of businesses which do not relate to fund flow, such as price inquiring, credit giving, application evaluating and other product services, and the part of banking business is completed by using the request quotation model in the invention, so that a complete banking product business transaction flow can be constructed, and the flow has certain universality, and the online credit loan is used for simply requesting the separation of the order model, as shown in fig. 6.

In the whole, the invention decouples the product service rule from the transaction flow control, and unifies the transaction flow control of the original system by using the request order model, so as to reduce the butting workload of the channel end, and the decoupled effect is more beneficial to new product establishment and quick exhibition. Taking account of transfer transaction as an example, when the account transfer needs to be charged, or multi-account deduction is needed to be provided, or digital currency is used for supporting funds, the traditional mode needs to be reconstructed to complete a new product business scene, but a large amount of docking cost can be saved by using the method.

The invention takes the transaction center as an IT system, and the transaction center realizes the unified management of the transaction operation of the customer products by the bank through decoupling the product service rules and the transaction flow control.

Specifically, the present invention provides a method for processing a transaction of a banking product based on a request order model, as shown in fig. 18, the method includes:

S1, collecting bank involves customer scenes of product transaction and carries out classification management on the customer scenes, basic service information of various scenes and each transaction stage are defined, the defined transaction scenes are started, the transaction scenes are butted through scene access functions provided by a transaction center, after the transaction scenes are started to be executed, the transaction center carries out circulation on each transaction stage of the scenes, data of a request order are saved, abnormal events occurring in the circulation process are processed, and the customer is guided to complete the transaction;

s2, constructing a request order model based on request order data of each transaction stage of various transaction scenes, when new product transaction is carried out, firstly inputting product transaction information into the request order model to generate a request order, confirming the stage state of the request order in the request order model, and then controlling circulation of each transaction stage of the request order to ensure that the execution flow of the request order is carried out according to an execution rule;

S3, the channel end definitely needs to call a transaction scene, the transaction scene is transmitted into the participation of different stages through HTTP, the transaction center completes each request order stage specified by the scene, the product transaction is integrated into a request order model of the transaction center, and the transaction center uses the request order model to uniformly control various product transaction flows.

Further, the method for processing the bank product transaction based on the request order model in the invention comprises the following steps of:

s11, collecting bank relates to customer scenes of product transaction, and classifying and managing the customer scenes to realize starting and stopping, and defining basic service information of various scenes;

s12, defining each trading stage of a scene, wherein the trading stages represent each stage of requesting orders;

s13, after the customer transaction scene is defined completely, starting the defined scene, and docking the transaction scene through a scene access function provided by a transaction center;

s14, after the transaction scene starts to be executed, the transaction center flows all transaction stages of the scene, the request order data are stored, abnormal events occurring in the flowing process are processed, and finally the clients are guided to complete the transaction.

Further, the transaction stage of the scenario described in the step S12 of the method of processing a transaction of a banking product based on a request order model of the present invention comprises: request response, order creation, order approval, order payment, order delivery, order notification, order completion.

Further, the uniqueness of the transaction scene in the step S1 of the method for processing the transaction of the bank product based on the request order model is represented by the transaction scene number, an execution interface of a transaction center is called when the channel end initiates the HTTP request, the transaction scene number is carried in the message header, the transaction center searches for a corresponding scene execution rule through a routing mechanism, and the scene execution rule is determined by each transaction stage.

Further, the request order model in the method step S2 for processing the transaction of the bank product based on the request order model provides two states for execution and completion in each stage, and when a forward operation or a reverse operation is performed in a certain stage, it is required to determine whether the current state in the stage can perform the corresponding operation.

Further, the method for processing the bank product transaction based on the request order model in the invention in step S2 includes the following steps:

Request response phase: recording the demand information of a customer on a product, and providing corresponding service or quotation after the customer demand responds to a customer; the customer demand information for the product includes: the expected amount of the customer, the product number, the number of products, and the net value of the unit;

order creation phase: recording a customer's product transaction record and other transaction additional attributes; the customer's product transaction record includes: information of the transaction product, amount information, order adjustment items, and related user roles of order execution;

an order approval stage: recording information whether the order is compliant or not and whether the order can be controlled through wind;

Order payment stage: recording customer payment information; the customer payment information includes: transaction party and transacted party of order payment, account information, currency information;

order delivery phase: recording the information of the liability products of the delivered line side assets;

order notification phase: notifying the order execution condition;

order completion stage: and finally, confirming the completion state change of the product transaction.

Further, the invention provides a method for processing a transaction of a banking product based on a request order model, wherein the request order model comprises a request response data model and an order data model.

In another aspect, the present invention also provides a system for processing a transaction of a banking product based on a request order model, the system comprising:

A. Transaction scene flow control module: the module is responsible for management of a transaction scene, configuration of each stage in the transaction scene and configuration work of other systems; the main function of the module is to define a template for a transaction scene; the transaction scene flow control module performs stage control on the transaction scene execution module;

B. The transaction scene execution module and the transaction exception processing module: the transaction scene execution module is responsible for calling routing work of the transaction scene and forwarding all stages of the request order; the transaction exception handling module is responsible for handling exceptions occurring in the execution process according to the execution rules; the main functions of the transaction scene execution module and the transaction exception processing module are the execution of the transaction scene execution rule;

C. transaction standard data management module: the module is responsible for storing the transaction records according to different request order stages, and forming the transaction records of different transaction scenes into request order data of a unified model; the transaction standard data management module provides data support for the transaction scenario execution module.

Further, in the system for processing the transaction of the bank product based on the request order model, the invention comprises the following steps:

A. The transaction scene flow control module comprises:

(1) And a customization module: responsible for pre-processing management and post-processing management;

(2) A transaction scene configuration module: responsible for scene type management, scene stage management, scene parameter mapping, stage information management and abnormal configuration management;

(3) The flow processing module: responsible for calling type management, calling method management and calling exception management;

B. the system comprises a transaction scene execution module and a transaction exception processing module, wherein:

(1) A transaction scenario execution module: is responsible for invoking transaction scenario routing, request response, order creation, order approval, order payment, order delivery, order completion, order notification, transaction record;

(2) Transaction exception handling module: responsible for order retrying, order compensation, order cancellation, order alignment;

C. the transaction standard data management module comprises:

(1) And a request response module: the method is responsible for requesting main body information management, request item information management, request association relation management, request type management, response content management, response call questionnaires and response type management;

(2) Standard order module: is responsible for order head management, order item management, order type management, order role management, order payment information management, order delivery information management, order role information management, order association management and order state management.

Further, the system for processing the bank product transaction based on the request order model further comprises:

request quotation module: for performing a preprocessing operation on associated banking prior to generation of a banking order, said preprocessing operation comprising: price polling, credit granting, application assessment.

In addition, the invention also provides a computer readable storage medium, wherein the storage medium is stored with a computer program, and the program is executed by a processor to realize the steps of the method for processing the bank product transaction based on the request order model.

In summary, the method for processing the transaction of the bank product based on the request order model of the invention transforms the order model of the electronic commerce platform into the financial order model which can be used for the transaction scene of the bank for the customer, unifies the transaction flow control of the original system by using the request order model, combines the product transaction scene with the request order, and converts the service flow instance of the scene-related system into the request order flow by the configuration method. In addition, the invention can extract transaction information from the service system without perception and record the transaction information into the order model of the transaction center, thereby realizing the unified management of the transaction center on the scattered product transaction scene of the bank system.

Drawings

For a clearer description of the background art and of the technical solutions of the embodiments of the present invention, the following brief description of the drawings that are needed in the description of the background art and of the embodiments of the present invention will be obvious to those skilled in the art, but the following drawings are merely examples of embodiments described in the present invention, and other drawings can be obtained according to these drawings without inventive effort.

Fig. 1 is a schematic diagram of an implementation flow of a cross-bank transfer transaction service on a bank existing application architecture.

Fig. 2 is a schematic diagram of a cash deposit transaction service implementation flow on a bank existing application architecture.

Fig. 3 is a schematic diagram of an implementation flow of a financial purchasing transaction service on a bank existing application architecture.

Fig. 4 is a schematic implementation flow diagram of the financial purchasing transaction service (the financial system supports the purchasing behavior of the class i and class ii accounts at the same time) expanded on the existing application architecture of the bank.

Fig. 5 is a schematic diagram showing the gradual complexity of the overall transaction link for the logic of the channel system on the bank's existing application architecture required to interface with various product systems to effect transaction processing.

FIG. 6 is a schematic diagram of an online credit loan transaction flow based on a request order model.

FIG. 7 is a schematic diagram of the overall design architecture of the present invention.

Fig. 8 is a schematic diagram of the composition of the system of the present invention.

FIG. 9 is a state matrix diagram of a request order according to an embodiment of the present invention.

FIG. 10 is a diagram of a request response data model according to an embodiment of the present invention.

FIG. 11 is a schematic diagram of an order data model according to an embodiment of the present invention.

Fig. 12 is a view showing the effect of scene classification and transaction scene list on a management end page according to an embodiment of the present invention.

Fig. 13 is a schematic diagram of various stages of a transaction of a debit card Shen Ka according to an embodiment of the present invention.

Fig. 14 is an operation example diagram of a scenario of a debit card Shen Ka of an embodiment of the present invention.

Fig. 15 is a flow chart of a transaction scenario rule configuration according to an embodiment of the present invention.

Fig. 16 is a diagram of the resulting order effect after execution of the debit card Shen Ka scenario of an embodiment of the present invention.

FIG. 17 is a control diagram illustrating the prior art system decoupling by the transaction center and unified transaction flow using the request order model according to an embodiment of the present invention.

FIG. 18 is a schematic flow chart of the method of the present invention.

Detailed Description

In order to make the objects, technical solutions and advantages of the present invention more apparent, the technical solutions of the present invention will be clearly and completely described below with reference to specific embodiments and corresponding drawings. It is apparent that the described embodiments are only some embodiments of the present invention, but not all embodiments, and the present invention may be implemented or applied by different specific embodiments, and that various modifications or changes may be made in the details of the present description based on different points of view and applications without departing from the spirit of the present invention.

Meanwhile, it should be understood that the scope of the present invention is not limited to the following specific embodiments; it is also to be understood that the terminology used in the examples of the invention is for the purpose of describing particular embodiments only, and is not intended to limit the scope of the invention.

Examples: method for processing bank product transaction based on request order model

The system structure, the functional design module, and the operation mechanism of the present invention will be described in detail below.

The invention takes the transaction center as an IT system, and the transaction center realizes the unified management of the transaction operation of the customer product by the bank through decoupling the product service rule and the transaction flow control, and the whole design framework of the invention is shown in figure 7.

Architecture module design

Firstly, a customer scene related to product transaction is collected by a bank, classified management is carried out on the customer scene, activation and deactivation are realized, and basic service information of various scenes is defined.

After the basic service information of the scenario is defined, each stage of the scenario needs to be defined, and one scenario must be composed of a plurality of transaction stages, wherein the transaction stages represent each stage of requesting an order, including request response, order creation, order approval, order payment, order delivery, order notification and order completion.

After the customer transaction scene is defined completely, the defined scene is started. The channel end only needs to dock the transaction scene according to the calling rule of the transaction scene.

After the transaction scene is executed, the transaction center flows each stage of the scene, saves the request order data, processes the abnormal event occurring in the process, and finally guides the customer to complete the transaction.

In summary, the system of the present invention can be split into the following three parts according to the module responsibilities, as shown in fig. 8:

A. transaction scene flow control module: the module is responsible for management of a transaction scene, configuration of each stage in the transaction scene and configuration work of other systems, and the main function of the module is to define a template for the transaction scene. The transaction scene flow control module specifically comprises: a customization module (responsible for pre-processing management and post-processing management); transaction scene configuration module (responsible for scene type management, scene stage management, scene parameter mapping, stage information management, exception configuration management); the flow processing module (responsible for calling type management, calling method management and calling exception management). The transaction scene flow control module performs stage control on the transaction scene execution module.

B. The transaction scene execution module and the transaction exception processing module: the module is responsible for the call routing work of the transaction scene, flows through each stage of the request order, processes the abnormality generated in the execution process according to the rule, and has the main function of executing the rule of the transaction scene. Specifically, the transaction scenario execution module is responsible for invoking transaction scenario routing, request response, order creation, order approval, order payment, order delivery, order completion, order notification, transaction record; the transaction exception handling module is responsible for order retries, order compensation, order cancellation, order correction.

C. Transaction standard data management module: the module is responsible for storing the transaction records according to different request order stages, and forming the transaction records of different transaction scenes into request order data of a unified model. The transaction standard data management module specifically comprises: a request response module (responsible for request subject information management, request item information management, request association relation management, request type management, response content management, response call questionnaire, response type management); standard order modules (responsible for order header management, order item management, order type management, order role management, order payment information management, order delivery information management, order role information management, order association management, order status management). The transaction standard data management module provides data support for the transaction scenario execution module.

(II) Programming

1. Request order model

The invention firstly needs to make clear the phase state of the request order model, and each phase provides two states of execution neutralization completion. In the forward operation and the reverse operation of the stage, it is also required to determine whether the current state can perform the corresponding operation, and the state matrix diagram of the request order is shown in fig. 9.

After confirming the state change, control can be made on circulation of the order requesting stage, and the order requesting flow is ensured to be carried out according to the execution rule.

The requested order data operations that need to be performed at each stage are also different:

Request response phase: and recording the information of the demand of the customer on the product, such as the expected amount, the product number, the product quantity, the net value of the unit and the like of the customer, and providing corresponding service or quotation after the customer demand responds on the line side.

Order creation phase: a product transaction record for the customer is recorded, such as information on the product being transacted, monetary information, order adjustments (adjustments such as commissions), relevant user roles for order execution (customer, customer manager, authorization manager, etc.), and other transaction additional attributes.

An order approval stage: and recording information about whether the order is compliant, whether the order can be controlled by wind and the like.

Order payment stage: and recording the transaction party and the customer payment information such as the transacted party, account information, currency information and the like of order payment.

Order delivery phase: record the line side asset liability product information of delivery.

Order completion stage: and finally, confirming the completion state change of the product transaction.

The request model (request response data model) and the order (data) model are designed by the above contents, as shown in fig. 10 and 11.

2. Scene mechanism

The other functional key point of the invention is to reduce the access of the channel end, and the channel end in the existing system is usually required to be in butt joint with a core service system and a product service system, and the butt joint process is tedious and can not be reused. In the invention, a transaction center provides a scene access function.

Firstly, corresponding collection is carried out on transaction scenes through scene classification, and finally, the transaction scenes are displayed in a management end page, as shown in fig. 12, the left side in fig. 12 is the scene classification, and the right side is a transaction scene list under the classification.

The transaction scene is represented by the uniqueness through the transaction scene number, an execution interface of the transaction center is called when the channel end initiates the HTTP request, the transaction scene number is carried in the message header, and the transaction center can search the corresponding scene execution rule through the routing mechanism.

The rules of the trade scenario are defined by the trade phase, i.e. the request order phase mentioned above.

Requiring a third party to perform a function in part of the order stage, such as requiring a core system or a unified payment system to be invoked for each transaction stage of the debit card Shen Ka in fig. 13, requires a third party system to be invoked in addition to the order information to complete the function of the stage at each stage of the order.

Thus providing a flow handling mechanism for each phase of requesting an order, the third party system may be configured to be invoked via an HTTP request, an example of which is shown in FIG. 14, with the debit card Shen Ka scenario depicted in FIG. 14, requesting that the quote phase select the third party system interface as the operation to invoke the rules.

Through the configuration page of the management end, we can associate the unique identification of the financial product with the scene, so as to complete the rule configuration of the whole transaction scene, as shown in fig. 15.

3. Scene call and order record

After the channel end has defined the scene to be called, the channel end can enter the parameters of different stages through HTTP to complete each request order stage specified by the scene, and finally, various financial product transactions are unified in the request order model of the transaction center. Fig. 16 shows the debit card Shen Ka transaction scenario, with the final order effect after the scenario is executed.

4. Summary of the design

The decoupling between the original systems is formed by the transaction center, and the control of the transaction flow is unified by using the request order model, as shown in fig. 17.

The present invention is not limited to the preferred embodiments, and any equivalent modifications and variations in light thereof can be made by those skilled in the art without departing from the scope of the present invention, but are intended to be encompassed by the following claims.

Claims (10)

1. A method of processing a transaction for a banking product based on a request order model, the method comprising:

S1, collecting bank involves customer scenes of product transaction and carries out classification management on the customer scenes, basic service information of various scenes and each transaction stage are defined, the defined transaction scenes are started, the transaction scenes are docked through a scene access function provided by a transaction center, after the transaction scenes are started to be executed, the transaction center carries out circulation on each transaction stage of the scenes, order data are saved, and abnormal events occurring in the circulation process are processed;

s2, constructing a request order model based on request order data of each transaction stage of various transaction scenes, when new product transaction is carried out, firstly inputting product transaction information into the request order model to generate a request order, confirming the stage state of the request order in the request order model, and then controlling circulation of each transaction stage of the request order to ensure that the execution flow of the request order is carried out according to an execution rule;

S3, the channel end definitely needs to call a transaction scene, the transaction scene is transmitted into the participation of different stages through HTTP, the transaction center completes each request order stage specified by the scene, the product transaction is integrated into a request order model of the transaction center, and the transaction center uses the request order model to uniformly control various product transaction flows.

2. The method of claim 1, wherein step S1 includes:

S11, collecting bank relates to customer scenes of product transaction, classifying and managing the customer scenes, and defining basic service information of various scenes;

s12, defining each trading stage of a scene, wherein the trading stages represent each stage of requesting orders;

s13, after the customer transaction scene is defined completely, starting the defined scene, and docking the transaction scene through a scene access function provided by a transaction center;

s14, after the transaction scene starts to be executed, the transaction center flows all transaction stages of the scene, the request order data are stored, abnormal events occurring in the flowing process are processed, and finally the clients are guided to complete the transaction.

3. The method of claim 2, wherein the transaction phase of the scenario in step S12 comprises: request response, order creation, order approval, order payment, order delivery, order notification, order completion.

4. A method for processing a transaction of a banking product based on a request order model as claimed in claim 3, wherein the transaction scenario in step S1 is represented by a transaction scenario number, the execution interface of the transaction center is invoked when the channel side initiates an HTTP request, and the transaction scenario number is carried in the header, and the transaction center finds a corresponding scenario execution rule by a routing mechanism, and the scenario execution rule is determined by each transaction stage.

5. A method for processing a transaction of a banking product based on a request order model as claimed in claim 3, wherein the request order model in step S2 provides two states of execution and completion in each stage, and when a forward operation or a reverse operation is performed in a certain stage, it is required to determine whether the current state of the stage can perform the corresponding operation.

6. A method for processing a banking transaction based on a request order model as claimed in claim 3 wherein the request order data operations performed by the request order model in each stage in step S2 are respectively:

Request response phase: recording the demand information of a customer on a product, and providing corresponding service or quotation after the customer demand responds to a customer; the customer demand information for the product includes: the expected amount of the customer, the product number, the number of products, and the net value of the unit;

order creation phase: recording a customer's product transaction record and other transaction additional attributes; the customer's product transaction record includes: information of the transaction product, amount information, order adjustment items, and related user roles of order execution;

an order approval stage: recording information whether the order is compliant or not and whether the order can be controlled through wind;

Order payment stage: recording customer payment information; the customer payment information includes: transaction party and transacted party of order payment, account information, currency information;

order delivery phase: recording the information of the liability products of the delivered line side assets;

order notification phase: notifying the order execution condition;

order completion stage: and finally, confirming the completion state change of the product transaction.

7. A method of processing a transaction of a banking product based on a request order model as claimed in claim 3, wherein the request order model in step S2 includes a request response data model and an order data model.

8. A system for processing a transaction for a banking product based on a request order model, the system comprising:

A. Transaction scene flow control module: the module is responsible for management of a transaction scene, configuration of each stage in the transaction scene and configuration work of other systems; the main function of the module is to define a template for a transaction scene; the transaction scene flow control module performs stage control on the transaction scene execution module;

B. The transaction scene execution module and the transaction exception processing module: the transaction scene execution module is responsible for calling routing work of the transaction scene and forwarding all stages of the request order; the transaction exception handling module is responsible for handling exceptions occurring in the execution process according to the execution rules; the main functions of the transaction scene execution module and the transaction exception processing module are the execution of the transaction scene execution rule;

C. transaction standard data management module: the module is responsible for storing the transaction records according to different request order stages, and forming the transaction records of different transaction scenes into request order data of a unified model; the transaction standard data management module provides data support for the transaction scenario execution module.

9. The system for processing banking product transactions based on request order model as recited in claim 8, wherein said system is configured to:

A. The transaction scene flow control module comprises:

(1) And a customization module: responsible for pre-processing management and post-processing management;

(2) A transaction scene configuration module: responsible for scene type management, scene stage management, scene parameter mapping, stage information management and abnormal configuration management;

(3) The flow processing module: responsible for calling type management, calling method management and calling exception management;

B. the system comprises a transaction scene execution module and a transaction exception processing module, wherein:

(1) A transaction scenario execution module: is responsible for invoking transaction scenario routing, request response, order creation, order approval, order payment, order delivery, order completion, order notification, transaction record;

(2) Transaction exception handling module: responsible for order retrying, order compensation, order cancellation, order alignment;

C. the transaction standard data management module comprises:

(1) And a request response module: the method is responsible for requesting main body information management, request item information management, request association relation management, request type management, response content management, response call questionnaires and response type management;

(2) Standard order module: is responsible for order head management, order item management, order type management, order role management, order payment information management, order delivery information management, order role information management, order association management and order state management.

10. The system for processing banking product transactions based on request order model as recited in claim 8, further including:

request quotation module: for performing a preprocessing operation on associated banking prior to generation of a banking order, said preprocessing operation comprising: price polling, credit granting, application assessment.