CN116934318A

CN116934318A - General method, device, equipment and storage medium for processing online banking flow

Info

Publication number: CN116934318A
Application number: CN202310970164.6A
Authority: CN
Inventors: 高子轩
Original assignee: China Merchants Bank Co Ltd
Current assignee: China Merchants Bank Co Ltd
Priority date: 2023-08-02
Filing date: 2023-08-02
Publication date: 2023-10-24

Abstract

The invention discloses a general method, a device, equipment and a storage medium for processing an online banking process, wherein the method comprises the following steps: checking whether transaction elements of the transaction are correct based on a standard preset format; when the transaction element accords with the standard preset format, judging whether the transaction element accords with the transaction logic; when the transaction elements are verified to be in accordance with the transaction logic, approval stream processing is carried out; after approval flows are approved, the transaction is sent to a core system of a bank for processing at preset expected time; when the transaction is processed at the core system, the transaction is completed. And abstracting the business flow of the online banking transaction, so that the business flow is solidified, and an enterprise online banking transaction framework is formed. When a developer develops a service, the developer does not need to pay attention to the flow operation of the transaction, only needs to pay attention to different details of different services, other functions are realized through a transaction framework and a plurality of configuration items, the development efficiency can be effectively improved, and the lead time is reduced.

Description

General method, device, equipment and storage medium for processing online banking flow

Technical Field

The present invention relates to the field of data processing technologies, and in particular, to a general method, an apparatus, a device, and a storage medium for online banking process processing.

Background

Overseas branch business of banks refers to branches or subsidiaries established by banks abroad to provide various financial products and services for cross-border customers. These branches are set up abroad, but still are under the supervision and control of the parent. Overseas traffic generally includes the following aspects: the fund storage and management are carried out by the overseas branches to provide services such as cross-border deposit, settlement and fund management for clients, ensure the fund safety of the clients and provide an efficient fund management tool. Loan and financing, the overseas branches provide services such as loan, financing and credit support for customers, helping customers meet the fund demands of cross-border business expansion and development. Foreign exchange transaction and risk management, foreign exchange, long-term transaction, foreign exchange risk hedging and other services are provided by the foreign exchange, and clients are helped to manage foreign exchange risks in cross-border transactions. Capital market services, overseas branches provide investment banking and capital market services, support for stock issuance, bond issuance, and parallel purchase transactions of customers, and the like. For example, a national bank establishes a branch in the united states that can provide cross-border loan and financing services for chinese businesses in the united states. The chinese business may apply for loans through the branch for expanding business or performing union transactions in the united states.

With the continuous expansion of the business of the overseas branches of the banks, the variety and the quantity of the enterprise internet banking business can show explosive growth. The same service of different overseas branches and different service logics of the same overseas branches are different, which is a great challenge for development, test and operation of the internet banking service. The developer needs to cooperate with business personnel of different business departments of different branches to confirm each detail on a transaction link, and although the transaction main flows are similar, flow nodes such as a management, approval, revocation, timing task pushing core system and the like exist, the specific details are quite different. Therefore, a set of corresponding codes needs to be developed for each service, the development efficiency is low, and the lead time is prolonged.

The foregoing is provided merely for the purpose of facilitating understanding of the technical solutions of the present invention and is not intended to represent an admission that the foregoing is prior art.

Disclosure of Invention

The invention mainly aims to provide a general method, device, equipment and storage medium for processing an online banking process, and aims to solve the technical problems of low development efficiency and long delivery cycle of the existing online banking process processing method.

In order to achieve the above object, the present invention provides a general method for processing an online banking process, the method comprising the steps of:

Checking whether transaction elements of the transaction are correct based on a standard preset format;

when the transaction element accords with a standard preset format, judging whether the transaction element accords with transaction logic or not;

when the verification transaction element accords with the transaction logic, performing approval stream processing;

after the approval flow is approval, the transaction is sent to a core system of a bank for processing at preset expected time;

when a transaction is completed at the core system, the transaction is completed.

Optionally, the step of verifying whether the transaction element of the transaction is correct based on the standard preset format includes:

based on a standard preset format, carrying out general verification on general transaction elements;

when the general transaction element accords with a standard preset format, judging whether personalized verification is required according to the transaction type of the transaction;

when the personalized verification is needed, acquiring a personalized preset format, and carrying out personalized verification on the transaction elements.

Optionally, after the step of performing approval stream processing when the verification transaction element accords with the transaction logic, the method further includes:

storing the transaction state into an online banking platform database;

Correspondingly, after the step of sending the transaction to the core system of the bank for processing at a preset expected time after the approval flow is approval, the method further comprises the following steps:

updating the transaction state and storing the transaction state into an online banking platform database.

Optionally, after the step of saving the transaction state in the internet banking platform database, the method further includes:

a corresponding approval expansion step is obtained according to the transaction type of the transaction;

and updating the transaction according to the approval extension step.

Optionally, when the transaction is completed by the core system, before the step of completing the transaction, the method further includes:

receiving a revocation request, and checking the revocation request;

when the revocation request passes the verification, performing revocation approval stream processing;

Optionally, the step of sending the transaction to a core system of a bank for processing at a preset expected time after the approval stream is approval, includes:

locking the transaction after the approval stream is approval;

judging the transaction state of the transaction;

When the transaction state accords with a preset condition, the transaction is sent to a core system of a bank for processing at a preset expected time, and the locking of the transaction is released;

sending a transaction state query request to a core system and receiving update information;

updating the transaction state according to the updating information, and storing the transaction state into an online banking platform database.

In addition, in order to achieve the above object, the present invention also provides a general device for processing an internet banking process, the general device for processing an internet banking process comprising:

the format verification module is used for verifying whether the transaction elements of the transaction are correct based on a standard preset format;

the logic verification module is used for judging whether the transaction element accords with transaction logic or not when the transaction element accords with a standard preset format;

the approval processing module is used for carrying out approval stream processing when the verification transaction element accords with the transaction logic;

the transaction sending module is used for sending the transaction to a core system of a bank for processing at preset expected time after the approval flow is approval;

And the state updating module is used for updating the transaction state when the transaction is processed and completed in the core system, and completing the transaction.

In addition, in order to achieve the above object, the present invention also provides a general device for processing an online banking process, the device comprising: the system comprises a memory, a processor and an online banking process general-purpose program stored on the memory and capable of running on the processor, wherein the online banking process general-purpose program is configured to realize the steps of the online banking process general-purpose method.

In addition, in order to achieve the above object, the present invention also proposes a storage medium having stored thereon an internet banking process general-purpose program which, when executed by a processor, implements the steps of the internet banking process general-purpose method as described above.

The invention verifies whether the transaction elements of the transaction are correct or not based on a standard preset format; when the transaction element accords with a standard preset format, judging whether the transaction element accords with transaction logic or not; when the verification transaction element accords with the transaction logic, performing approval stream processing; after the approval flow is approval, the transaction is sent to a core system of a bank for processing at preset expected time; when a transaction is completed at the core system, the transaction is completed. And abstracting the business flow of the online banking transaction, so that the business flow is solidified, and an enterprise online banking transaction framework is formed. When a developer develops a service, the developer does not need to pay attention to the flow operation of the transaction, only needs to pay attention to different details of different services, other functions are realized through a transaction framework and a plurality of configuration items, the development efficiency can be effectively improved, and the lead time is reduced.

Drawings

Fig. 1 is a schematic diagram of a general device structure for processing an internet banking process in a hardware operation environment according to an embodiment of the present invention;

FIG. 2 is a flow chart of a first embodiment of a general method for online banking flow treatment according to the present invention;

FIG. 3 is a flow chart of a third embodiment of the general method for online banking flow treatment of the present invention;

FIG. 4 is a schematic diagram of a general method for processing an online banking process according to the present invention;

fig. 5 is a schematic block diagram of a general device for processing internet banking flow.

The achievement of the objects, functional features and advantages of the present invention will be further described with reference to the accompanying drawings, in conjunction with the embodiments.

Detailed Description

It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the invention.

Referring to fig. 1, fig. 1 is a schematic diagram of an internet banking process general device structure of a hardware running environment according to an embodiment of the present invention.

As shown in fig. 1, the general device for processing the internet banking flow process may include: a processor 1001, such as a central processing unit (Central Processing Unit, CPU), a communication bus 1002, a user interface 1003, a network interface 1004, a memory 1005. Wherein the communication bus 1002 is used to enable connected communication between these components. The user interface 1003 may include a Display, an input unit such as a Keyboard (Keyboard), and the optional user interface 1003 may further include a standard wired interface, a wireless interface. The network interface 1004 may optionally include a standard wired interface, a WIreless interface (e.g., a WIreless-FIdelity (WI-FI) interface). The Memory 1005 may be a high-speed random access Memory (Random Access Memory, RAM) Memory or a stable nonvolatile Memory (NVM), such as a disk Memory. The memory 1005 may also optionally be a storage device separate from the processor 1001 described above.

Those skilled in the art will appreciate that the architecture shown in fig. 1 is not limiting of the general purpose device for internet banking processes, and may include more or fewer components than shown, or may combine certain components, or may be a different arrangement of components.

As shown in fig. 1, an operating system, a network communication module, a user interface module, and an internet banking process general program may be included in the memory 1005 as one type of storage medium.

In the general device for internet banking process shown in fig. 1, the network interface 1004 is mainly used for data communication with a network server; the user interface 1003 is mainly used for data interaction with a user; the processor 1001 and the memory 1005 in the general device for processing internet banking process according to the present invention may be disposed in the general device for processing internet banking process, where the general device for processing internet banking process calls the general program for processing internet banking process stored in the memory 1005 through the processor 1001, and executes the general method for processing internet banking process provided by the embodiment of the present invention.

An embodiment of the present invention provides a general method for processing an online banking process, and referring to fig. 2, fig. 2 is a flow diagram of a first embodiment of the general method for processing an online banking process of the present invention.

In this embodiment, the general method for processing the online banking process includes the following steps:

step S10: based on the standard preset format, checking whether the transaction element of the transaction is correct.

It should be noted that the standard preset format may be a predefined structure and specification of transaction data, which is used for verifying and verifying the correctness of the transaction, and specifying the position, length, format requirement, value range, and other contents of each element in the transaction information. It will be appreciated that in an internet banking system, data in a transaction may have certain data format requirements, for example, an account number should be a number of a specific length, an amount should be two digits after a decimal point, and so on. These specifications can be used as standard preset formats. For transfer transactions, the standard pre-set format may require that the transaction amount must be digital and greater than zero and that the account number must meet specific length and format requirements. Only if the transaction elements meet the standard preset formats, the next transaction logic judgment can be performed.

It should be noted that the transaction element may be a basic information or data element necessary for constituting a complete transaction. Including but not limited to account number, amount, currency, payee information, etc., to complete a complete transaction. For example, in a transfer transaction, account number, transfer amount, currency, payee account number, etc., are the transaction elements. The specific content and requirements of the transaction elements depend on the different transaction types and bank specifications.

In a specific implementation, the received transaction elements are checked according to a standard preset format, and whether the format is correct is judged. For example, if the transaction element includes an account number, a transaction amount, a currency, and the like, it is checked whether the account number conforms to a prescribed format, whether the transaction amount is within a valid range, whether the annex character conforms to a requirement, and the like.

Step S20: and when the transaction element accords with a standard preset format, judging whether the transaction element accords with transaction logic.

It is to be appreciated that the transaction logic can be a process of associating and logically determining data in transaction elements based on business rules and specifications. As a specified or preset logic relationship, the method is used for judging whether the transaction elements meet the legitimacy and compliance of the service. For example, in a transfer transaction, transaction logic may require that the available balance of the transfer-out account must be greater than the transfer amount, that the collection account must be present and permitted to receive, etc. Only if the transaction components meet the specifications of these transaction logics, the transaction can be considered legal and can go to the next approval process.

In a specific implementation, after the transaction element accords with a standard preset format, the transaction logic is judged. And judging whether the association relationship between transaction elements is correct or not according to a preset transaction logic rule. For example, if the transaction element includes a transfer amount and a collection account, then whether the corresponding transfer account balance is sufficient, whether a collection account exists, and so forth.

Step S30: and when the verification transaction element accords with the transaction logic, performing approval stream processing.

It should be noted that, the approval flow may be a flow for transferring the transaction to the corresponding approver for processing according to a preset flow and rule after the transaction element check and the transaction logic are judged to pass. As a series of approval procedures and flows set up inside an organization or institution to ensure the security and compliance of transactions, for monitoring, auditing and decision making of transactions. For example, in a high money transfer transaction, the approval stream may include multiple levels of approvers, such as primary approvers, secondary approvers, and advanced approvers. After the transaction elements are judged through the checksum transaction logic, the transaction elements are sequentially submitted to the approvers for approval, and each approver needs to carry out auditing and decision making according to a specified flow.

In a specific implementation, after the transaction element accords with the transaction logic, an approval process is entered. And submitting the transaction to corresponding approvers for processing according to a preset approval process rule. For example, the transaction needs to be subjected to multi-level approval, and each level of approval personnel needs to perform approval step by step according to a specified flow.

Step S40: and after the approval flow is approval, the transaction is sent to a core system of a bank for processing at preset expected time.

It may be understood that the preset expected time may refer to a time point or a time range at which a preset expected transaction is sent to a bank core system for processing according to a business requirement or a rule in an approval process. For a particular transfer transaction, the preset expected time may be a particular point in time for the next workday after the transaction is finally approved, or within a particular time period of the day.

It will be appreciated that the core system may be a centralized computer system used by banks to handle core business, manage account information, conduct transaction processing and funds settlement, among other critical functions. A core system of a bank may include an account management module, a transaction processing module, a risk control module, etc., and may support various types of transaction processing such as transfer, money transfer, deposit, loan, etc.

In a specific implementation, when the approval process passes through all, and the transaction meets the preset expected time requirement, the transaction is sent to a core system of the bank for processing. The core system is responsible for processing and recording the transaction, and ensures timeliness and safety of the transaction.

Step S50: when a transaction is completed at the core system, the transaction is completed.

In a specific implementation, when the transaction is completed at the core system, the entire transaction process is completed. The transaction results can be displayed by informing the user through an online banking system or providing transaction details.

In the embodiment, whether the transaction element of the transaction is correct or not is checked based on a standard preset format; when the transaction element accords with a standard preset format, judging whether the transaction element accords with transaction logic or not; when the verification transaction element accords with the transaction logic, performing approval stream processing; after the approval flow is approval, the transaction is sent to a core system of a bank for processing at preset expected time; when a transaction is completed at the core system, the transaction is completed. And abstracting the business flow of the online banking transaction, so that the business flow is solidified, and an enterprise online banking transaction framework is formed. When a developer develops a service, the developer does not need to pay attention to the flow operation of the transaction, only needs to pay attention to different details of different services, other functions are realized through a transaction framework and a plurality of configuration items, the development efficiency can be effectively improved, and the lead time is reduced. The universality and the automation of the online banking flow process are realized, and the efficiency and the accuracy of transaction processing are improved. Meanwhile, the method can be flexibly configured and customized according to the requirements of different banks, and is suitable for various complex transaction scenes and business requirements.

Further, in order to flexibly perform general and personalized verification on the transaction elements according to the transaction type, the step S10 includes:

step S101: and carrying out general verification on the general transaction elements based on a standard preset format.

It is understood that the generic transaction element may refer to those necessary information or data elements that are applicable to most transactions. For example, in a transfer transaction, the general transaction element may include an account number, a collection account number, a transaction amount, a transaction currency, and the like. These general transaction elements are necessary in most transfer transactions.

In a specific implementation, according to a preset standard format, the transaction elements are subjected to general verification so as to ensure the correctness and integrity of the format. The general transaction elements refer to those necessary information applicable to most transactions, such as account numbers, transaction amounts, and currencies.

Step S102: when the general transaction element accords with a standard preset format, judging whether personalized verification is needed according to the transaction type of the transaction.

It will be appreciated that the transaction types may be classifications and identifications of transactions for distinguishing between different transaction categories for corresponding processing in accordance with the different transaction types. For example, in an online banking system, common transaction types include transfer, remittance, deposit, loan, and the like. Each transaction type has specific transaction elements and requirements and requires corresponding checksum processing.

It should be noted that, the personalized verification may be a verification performed on a specific field, rule or flow required in a specific transaction type or a specific transaction scenario, so as to meet a specific business requirement and a risk management requirement. For specific transaction types or special transaction scenarios, additional verification is performed on the transaction elements to ensure the accuracy and compliance of the transaction. For example, for an international money transfer transaction, personalized verification may require further review and verification of the paymate type, paymate information, payee name and address, and the like. In this case, the personalized verification may ensure that the money transfer complies with relevant regulations and policies.

In a specific implementation, a transaction type verification rule table is set in the system, and the table contains personalized verification steps and rules required to be carried out by different transaction types. For example, for the transfer transaction type, a personalized verification step that requires identity verification of the payee account number is set in the transaction type verification rule table. After the general transaction elements in the standard preset format pass the verification, the system judges whether the transaction belongs to the transfer transaction type according to the setting in the transaction type verification rule table, and obtains corresponding personalized verification steps and rules, for example, the collection account is required to be the internal account of the branch. If the transaction type is of another type, such as a deposit type, the system will not require an additional personalized verification step.

Step S103: when the personalized verification is needed, acquiring a personalized preset format, and carrying out personalized verification on the transaction elements.

It will be appreciated that the personalized preset format may be defined according to a particular transaction type or particular transaction scenario, a set of format specifications or requirements for verifying and verifying transaction elements. The specification, format or requirements required to represent a particular transaction type or particular transaction scenario are used to personalize the transaction elements. For example, for a deposit transaction type, the personalized preset format may require that the deposit amount in the transaction element must be greater than a certain threshold, or that the deposit duration be selected only for a certain time.

In a specific implementation, a personalized verification rule table can be set in the system, and the table contains personalized preset formats required under different transaction types or special transaction scenes. For example, for cross-border money transfer transactions, a personalized preset format for association verification of the paymate type, paymate information, payee name and address is set in a personalized verification rule table. When the system judges that personalized verification is needed, a corresponding personalized preset format is obtained from a personalized verification rule table according to the transaction type or the specific scene, for example, a user is required to fill in the complete collection line type, collection line information, the name and address of a payee and the like, and whether the collection line type, the collection line information, the name and address and the like accord with preset association rules or not is required.

In general, for example, for a transfer transaction, the general transaction element may include an account number, a transaction amount, a currency, and the like. For these general transaction elements, general verification is performed according to a standard preset format, for example, the account number must be a number with a specific length, and the transaction amount must be a positive number. And then judging whether personalized verification is needed according to the transaction type. In the case of a particular type of cross-border transfer, a SWIFT format check may be required for the payline information. In this case, a personalized preset format will be obtained for personalized verification of the payee account number.

The above manner of the embodiment is based on a standard preset format to perform general verification on general transaction elements; when the general transaction element accords with a standard preset format, judging whether personalized verification is required according to the transaction type of the transaction; when the personalized verification is needed, acquiring a personalized preset format, and carrying out personalized verification on the transaction elements. Through the steps, the transaction elements can be flexibly checked in a universal and personalized way according to the transaction types, and the accuracy, the integrity and the standardization of the transaction are ensured.

Based on the above embodiment, a second embodiment of the present invention is provided, and in this embodiment, after the step S30, the method further includes:

step S31: storing the transaction state into an online banking platform database;

it should be noted that the transaction status may refer to different states of the transaction at different processing stages or conditions, and is used to represent and track progress and result of the transaction. The transaction status can be categorized into a variety of types, such as waiting for approval, finishing, in-process of a bank, completion (success), completion (failure). In the online banking system, a state of a transfer transaction may be pending, and when the transaction passes the approval, the transaction state becomes finished, and when the transaction is sent to the core system, the state becomes in the banking process, and after the core system finishes the process, the state may become successful or failed.

It will be appreciated that the web farm platform database may be a centralized data storage system for storing, managing, and maintaining data required by the web farm system, including transaction information, user information, system configuration, and the like. In the internet banking platform database, user account information, transaction records, approval stream information, transaction states and the like are stored. The data can be queried, updated, deleted and the like through the database so as to support the normal operation and management of the internet banking system.

In particular implementations, a comprehensive transaction table may be created in the online banking platform database that stores summary information of transactions and transaction status. Each time a transaction passes a certain stage or state transition, the corresponding state information is updated into the integrated transaction table. For example, in a transfer transaction, after the transaction passes approval, the implementation manner of saving the transaction status to the internet banking platform database may be to update the status field of the corresponding transaction in the integrated transaction table to "finish. Thus, by querying the comprehensive transaction table, the latest state of the transaction can be obtained at any time.

step S41: updating the transaction state and storing the transaction state into an online banking platform database.

In a specific implementation, after the transaction is sent to a bank core system for processing, a processing result returned by the core system is obtained, corresponding transaction state information is updated according to the processing result, and the updated transaction state is stored in a database of an online banking platform. Thus, tracking and updating of the transaction state can be realized, and the transaction state is ensured to be consistent with the processing result of the core system.

The embodiment saves the transaction state into an internet banking platform database; correspondingly, after the step of sending the transaction to the core system of the bank for processing at a preset expected time after the approval flow is approval, the method further comprises the following steps: updating the transaction state and storing the transaction state into an online banking platform database. The state information of the transaction can be timely stored in a database of the online banking platform, and the integrity and consistency of the data are maintained. Meanwhile, subsequent inquiry, statistics and monitoring are facilitated, and manageability and traceability of the online banking flow process are improved.

Further, in order to improve the adaptability and flexibility of the online banking process, after the step S31, the method further includes:

step S32: and acquiring a corresponding approval expansion step according to the transaction type of the transaction.

It will be appreciated that the approval extension step may be defined for certain transaction types or specific business scenarios, as opposed to a standard approval process, as a set of additional operations, verification or approval steps to meet the specific approval and processing requirements of a particular transaction type. For example, for high risk transaction types, the approval extension step may include additional verification or security checks, such as requiring user quota verification. As another example, for a particular type of batch payment transaction, the approval extension step may involve additional steps of verification and validation.

In a specific implementation, a mapping table of transaction types and approval extension steps may be set in the system. The table records the approval extension steps corresponding to each transaction type. For example, for a transfer transaction type, a set of approval extension steps associated with the transfer transaction, such as risk assessment, double verification, etc., are defined in the mapping table. When the system receives the transfer transaction, the corresponding approval expansion step is searched in the mapping table according to the transaction type, and additional operation or verification to be performed is obtained.

Step S33: and updating the transaction according to the approval extension step.

In a specific implementation, after the approval extension step is obtained, the transaction can be updated or processed correspondingly according to the definition and the requirement of each step. These approval extension steps may include requiring additional material to be entered, specific verification to be made, sending notifications, triggering other system operations, etc.

The above manner of this embodiment obtains the corresponding approval expansion step according to the transaction type of the transaction; and updating the transaction according to the approval extension step. Therefore, corresponding approval expansion steps are obtained according to the transaction types, and targeted processing and auditing are further carried out on the transaction. Thus, special processing requirements and approval flows of different transaction types can be met, and the adaptability and flexibility of online banking flow processing are improved.

Further, in order to improve traceability and manageability of the online banking process, before step S50, the method further includes:

step S42: and receiving a revocation request, and checking the revocation request.

It will be appreciated that the revocation request may refer to a request by a user or party of interest to the network banking system via an appropriate channel to cancel an already submitted transaction or to conduct a revocation operation of the transaction. For example, in a transfer transaction, if a user is aware of a wrong account number or amount after submitting a transfer request, they may initiate a withdrawal request in hopes of canceling or withdrawing the transfer transaction.

In particular implementations, the system may receive a revocation request submitted by a user, which may be received through a module, an API interface, or other channels of the internet banking system. In this way, the system is able to obtain the revocation request that needs to be processed. And then the system checks the received revocation request to ensure the validity and validity of the request. Verification may include verifying the validity of the source of the request, verifying whether the revocation request meets the revocation condition, and so forth. The user may also be required to provide authentication information, such as a password or other authentication factor, for the revocation request to ensure that the source of the revocation request is legitimate. The revocation request may also be restricted based on specific revocation conditions, such as whether the revocation request was sent ahead of the transaction process completion.

Step S43: and when the revocation request passes the verification, performing revocation approval streaming processing.

It is understood that the revocation approval stream refers to a step of submitting a revocation operation to an approval stream. In a specific implementation, when the verification of the revocation request is passed, a request for revoking the approval stream can be submitted to the middle platform, and when the request is processed, the approval stream of the transaction is ended.

Step S44: updating the transaction state and storing the transaction state into an online banking platform database.

In a specific implementation, after the approval flow process is finished, updating the transaction state according to the final result of the approval flow, and storing the updated transaction state into an online banking platform database. Thus, timeliness and accuracy of the transaction state and the revocation state can be ensured.

The above manner of this embodiment verifies the revocation request by receiving the revocation request; when the revocation request passes the verification, performing revocation approval stream processing; updating the transaction state and storing the transaction state into an online banking platform database. Furthermore, the method can check and process the revocation of the request and update the transaction state, so that the system can timely reflect the revocation state and the latest transaction state of the transaction. Thus, the subsequent inquiry, statistics and management are convenient, and the traceability and manageability of the internet banking flow process are improved.

Based on the above embodiments, a third embodiment of the present application is provided, referring to fig. 3, and fig. 3 is a flow chart of a third embodiment of the general method for processing internet banking flow.

In this embodiment, the step S40 includes:

step S401: locking the transaction after the approval stream is approval.

In particular implementations, when the end result of the approval process is approval, the transaction is locked to prevent other operations from interfering with or modifying the transaction. This may be accomplished by setting a lock identifier on the transaction status or related data fields.

Step S402: and judging the transaction state of the transaction.

In a specific implementation, the locked transaction is subjected to state judgment so as to ensure that the transaction state meets preset conditions. The determination may be made based on predetermined conditions, such as whether the transaction status is pending or otherwise specified.

Step S403: when the transaction state accords with a preset condition, the transaction is sent to a core system of a bank for processing at a preset expected time, and the locking of the transaction is released.

In a specific implementation, if the transaction state meets the preset condition, the transaction is sent to a core system of the bank for processing according to the preset expected time. Once the core system processing is complete, subsequent updates and operations may be performed based on the processing results.

In the embodiment, after the approval flow is approval, the transaction is locked; judging the transaction state of the transaction; when the transaction state accords with a preset condition, the transaction is sent to a core system of a bank for processing at a preset expected time, and the locking of the transaction is released. The transaction may be locked and sent to the core system for processing at a preset desired time after the final approval is obtained by the approval process. Thus, the correctness and timeliness of transaction transmission can be ensured, and the locking state of the transaction is released, so that the transaction can be continuously processed and updated. Therefore, the efficiency and the accuracy of the online silver treatment process can be improved.

Further, before the step S50, the method further includes:

step S45: and sending a transaction state query request to the core system and receiving update information.

It should be noted that the transaction state query request may be a request sent to the core system through an appropriate channel, for querying the processing state and the result of a specific transaction in the core system. For example, in a transfer transaction, the internet banking system sends a query request to the core system to obtain the current status of the transfer transaction, such as in progress, completed or in error.

It will be appreciated that the updated information may refer to data about the results and the latest status of the transaction process returned by the core system to the internet banking system. For example, the updated information returned by the core system may include the final state of the transaction, the results of the processing, the time of completion of the transaction, etc.

In a specific implementation, before the transaction processing is completed, the online banking system sends a query request to the core system to request to acquire the latest state of a specific transaction in the core system. The request may be sent through an associated interface or API. After receiving the inquiry request, the core system processes the request and returns corresponding update information. The online banking system receives and analyzes the updated information returned by the core system through the interface or the API so as to obtain the latest transaction state and related results. In addition, standard Web services or RESTful APIs can also be used to establish data exchanges and communications between the internet banking system and the core system.

Step S46: updating the transaction state according to the updating information, and storing the transaction state into an online banking platform database.

In a specific implementation, according to the update information received from the core system, corresponding update operation is performed on the transaction state, and the updated transaction state is stored in a database of the internet banking platform, so that the accuracy and timeliness of the transaction state are ensured.

In a further embodiment, the method includes sending a transaction state query request to a core system and receiving update information; updating the transaction state according to the updating information, and storing the transaction state into an online banking platform database. The core system may be sent a query request to obtain the latest transaction state information, and update the transaction state according to the returned update information. Therefore, the transaction state can be ensured to be consistent with the processing result of the core system, and the updated transaction state is stored in the internet banking platform database, so that the subsequent inquiry, statistics and management are convenient. Thus, traceability of the online banking flow process and consistency of data are improved.

Based on the above embodiments, a fourth embodiment of the present application is presented. In this embodiment, a general transaction framework based on an external internet banking transaction process is provided.

Referring to fig. 4, fig. 4 is a schematic diagram of a general method frame for processing an internet banking process according to the present application, and it can be understood that an overseas internet banking transaction process is generally divided into a pre-sponsored, approved, cancelled, sent transaction, and synchronized state. For transactions, each process has the same approval flow processing steps and business logic of different details corresponding to different transactions. The framework forms a series of general templates of the transaction flow by extracting similar steps in the business flow so as to be convenient for development and use. The application solves the problem of repeated development of similar transaction codes, provides a nonfunctional function, ensures that the development only needs to pay attention to business details, improves the development efficiency, reduces the learning cost and reduces the workload.

The transaction framework of the invention is divided into a basic functional module, a pre-sponsor module, a sponsor module, an approval module, a revocation module, a transaction sending module and a synchronous state module.

Basic functional module: providing basic service capability for the transaction framework; specifically, the basic function module comprises a notification sending function, a transaction state pushing function and a transaction duplicate prevention function.

A pre-manager module: providing a pre-manager function for the transaction flow; specifically, whether a part of transaction elements are correct or not can be checked in advance through the pre-sponsor module, and information such as the cost and interest rate of the transaction can be obtained through the pre-sponsor.

And (5) a management module: providing a transaction process with a sponsoring function; specifically, the client-side business process including approval stream processing, core system verification, business data list falling and the like can be completed through the business module.

And an approval module: providing approval function for transaction flow; specifically, the approval process of the client can be completed through the approval module, and approval functions such as approval stream processing, multi-stage approval, approval operation, approval rejection operation, approval after working time and the like are provided.

And (3) a revocation module: providing a revocation function for the transaction flow; specifically, the revocation process of the client can be completed through a revocation module, including functions of approving stream processing, concurrently revoking consistency and the like.

And (3) a transmission transaction module: providing a function of transmitting the transaction to the core system for the transaction flow; specifically, the transaction may be sent to the bank's core system for processing by the sending module on the day of the customer's specified desire.

A synchronization status module: the transaction flow provides a function of synchronizing transaction states; specifically, when the transaction is processed and completed in the core system, the transaction state of the internet banking end can be updated through the synchronous state module, and the transaction is completed.

Further, the basic functional module includes: the transaction system comprises a distributed transaction framework unit, a transaction duplicate prevention unit and a transaction state updating unit;

distributed transaction framework unit: the transaction arrangement of each flow based on the saga mode of the seata comprises a start state of the transaction, a method of each node, input and output parameters of each node, a transaction compensation method of each node and the like. And finally, the arranged and completed transaction is delivered to a saga state machine for executing the transaction. For example, the transaction flow needs to write a transinput. Json file, in which the name "trans_input" of the transaction, the start state "basic stateinput" of the transaction, the next state of each node, and transaction information such as the compensation method of each node are described.

Transaction duplicate prevention unit: the double locking mechanism based on redis lock and database lock ensures that the transaction will not be repeated. Specifically, the redis is called for locking, and if the redis fails to lock, a database locking mode is further adopted.

Transaction state updating unit: after each flow of the transaction is completed, the transaction status is synchronized to the operator by the code of the unit. Specifically, the synchronization of the transaction state is accomplished by asynchronously pushing the transaction state to the message middleware kafka of the corresponding topic.

When carrying out transaction pre-processing, firstly, checking all transactions such as account number format, date format, amount format and the like through general checking, and the checking logic is required to be involved. And then, the verification is carried out through the expanded personalized verification, wherein the personalized verification is used for expansion, so that the aim of solving the differentiated verification logic of different transaction types is to develop the focus of attention. For example, for the pre-manager of the swift money transfer service, it is necessary to check in the unit whether the expected day, the amount in the account is sufficient to pay the transaction amount, whether the state of the account is normal, whether the format of the swift code is correct, etc.

In the transaction sponsorship process, the general sponsorship verification and the personalized sponsorship verification are performed first, after the verification is passed, the database is saved after the sponsorship of the base center, and the sponsorship expansion step can be performed. The distributed transaction framework in the basic functional module is used in the process of management extension to ensure the consistency of the transaction in the step. Specifically, the general manager check is responsible for checking functions of some general logics, such as format check of transaction elements, status availability of transaction account numbers, expected date expiration and the like, before the formal manager. Personalized parity is used for expansion, and is aimed at solving the differentiation verification logic of different transaction types, and is an important point of attention for development. The base center office provides an approval flow interface for the transaction flow, and writes the office approval flow of the transaction into the base center. The data storage is to store the transaction information of the client to an internet banking platform database, and specifically comprises a transaction detail table and a comprehensive transaction table. The sponsor expansion module is an expansion of the sponsor function to provide additional sponsor functions for some non-standardized transactions, e.g., the generation of the deduction service requires synchronization of transaction data by the sponsor expansion step to the retail host.

When the approval is carried out, firstly, general approval verification is carried out, and then personalized approval verification is carried out. After the verification is passed, the base center is approved, the database is updated, and then the approval expansion step is carried out. The distributed transaction framework in the basic functional module is used for ensuring the transaction consistency of the 3 steps. Specifically, the general approval check is responsible for performing some general logic check functions, such as format check of transaction elements, and whether the approval request elements are legal or not, before formal approval. Personalized approval verification is used for expansion, and aims to solve the problem of differentiated verification logic of different transaction types, and is an important point of development and attention. The base center station approves an approval flow interface for the approval flow, and an approval (approval/rejection) approval flow of the transaction is written into the base center station. The updating data is to store the change state of the transaction information of the client to an internet banking platform database (if the transaction state is modified by the completion of the final examination), and specifically comprises a transaction detail table and a comprehensive transaction table. The approval extension module is an extension of the approval function and provides additional approval functions for some non-standardized transactions, for example, the cross-currency money transfer business needs to update the exchange rate information of the transaction through the approval extension step, etc.

And in the revocation process, general revocation verification and personalized verification are carried out, and after the verification is passed. Updating the database after the base center station is withdrawn, and carrying out a withdrawal and expansion step. Wherein, the basic middle station withdraws, updates the database and withdraws and expands the distributed transaction framework in the basic functional module to ensure the transaction consistency of the 3 steps. Specifically, the general revocation checking is responsible for performing some general logical checking functions, such as format checking of revoked transaction elements, before formal revocation. The personalized revocation checking is used for expansion, and aims to know differentiated checking logic of different transaction types, and is an important point of development and attention. The basic center station revocation provides an approval flow interface for the revocation flow, and the revocation approval flow of the transaction is written into the basic center station. The updating data is to store the change state of the transaction information to the database of the internet banking platform after the withdrawal is completed, and specifically comprises a transaction detail table and a comprehensive transaction table. The revocation extension module is an extension of the revocation function, providing additional revocation functions for some non-standardized transactions.

In the process of transmitting the transaction, the transaction locking anti-duplication is firstly carried out, and then the transaction state is judged. After judging that the transaction state accords with the core transaction, updating the database state, then sending the transaction to the core transaction, and finally releasing the lock. The local transaction provided by the spring framework when releasing the lock completes the control of the transaction. Specifically, the transaction anti-replay lock uses the transaction anti-replay in the basic functional module to prevent the transaction from being repeatedly transmitted. The transaction status is determined to ensure the correctness of the transaction currently requiring the sending core system. Updating the database state modifies the state of the transaction to "in-process of the bank" and saves it to the online banking platform database. And sending the transaction to the core system, sending the transaction on the expected date to the core system for processing, and updating the transaction information of the internet banking terminal according to the information returned by the core system. The last release of the lock is to release the lock added in the first step, preventing the transaction from blocking the program when the intermediate step is abnormal.

In the synchronous state process, firstly inquiring the transaction state, then calling back the base center station, updating the database, and performing the expansion step. The callback base center updates the database, and the expansion step uses the distributed transaction framework in the base function module to ensure the transaction consistency of the 3 steps. Specifically, querying the transaction status is mainly responsible for querying transactions whose transaction status is "in bank processing", and querying the core system for the status of these transactions. The callback base center is the approval stream that aims to settle the transaction. The updated data is the final state of the transaction and is stored in an internet banking platform database, and specifically comprises a transaction detail table and a comprehensive transaction table. The expansion step provides an expansion for some branch personalization requirements, e.g., branch needs to delete transaction operations after some transactions return to a "fail" state, etc.

Aiming at the situation that different transaction flows of different branches are complex and changeable and a plurality of sets of codes need to be written, the invention solidifies the transaction flow through a business flow model of abstract internet banking transaction, such as a management, approval, withdrawal and sending core system model, so as to form an enterprise internet banking transaction framework. When a developer develops a service, the developer does not need to pay attention to the flow operation of the transaction, only needs to pay attention to different details of different services, other functions are realized through a transaction framework and a plurality of configuration items, and the development efficiency can be effectively improved.

Aiming at some nonfunctional requirements, such as control of distributed transactions and anti-duplication control of transactions, the invention provides basic services of the nonfunctional requirements in a framework, and developers do not need to care about specific logic and can be used after unpacking. Meanwhile, due to the standardized function provided by the framework, subsequent upgrading iteration is more convenient, and the system is noninductive to a user of the framework.

Aiming at the new internet banking service demand, the invention provides a set of standardized internet banking service flow, and the service can be agreed with development on the new service rapidly only by following the flow of a transaction framework, thereby reducing the communication cost and improving the delivery efficiency.

In addition, to achieve the above objective, an embodiment of the present invention further provides a general device for processing an online banking process, referring to fig. 5, fig. 5 is a schematic block diagram of the general device for processing an online banking process, where the general device for processing an online banking process includes:

In addition, in order to achieve the above object, the present invention further provides a storage medium, wherein the storage medium stores an internet banking process general-purpose program, and the internet banking process general-purpose program when executed by a processor implements the steps of the internet banking process general-purpose method as described above.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or system that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or system. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or system that comprises the element.

The foregoing embodiment numbers of the present invention are merely for the purpose of description, and do not represent the advantages or disadvantages of the embodiments.

From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present invention may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium (e.g. ROM/RAM, magnetic disk, optical disk) comprising instructions for causing a terminal device (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to perform the method according to the embodiments of the present invention.

The foregoing description is only of the preferred embodiments of the present invention, and is not intended to limit the scope of the invention, but rather is intended to cover any equivalents of the structures or equivalent processes disclosed herein or in the alternative, which may be employed directly or indirectly in other related arts.

Claims

1. The general method for processing the online banking process is characterized by comprising the following steps of:

2. The general method for online banking process according to claim 1, wherein the step of verifying whether the transaction element of the transaction is correct based on the standard preset format comprises:

3. The general method for online banking process according to claim 1, wherein after the step of performing approval stream processing when the verification transaction element conforms to transaction logic, further comprising:

storing the transaction state into an online banking platform database;

4. The general method for online banking process according to claim 3, wherein after the step of saving the transaction status in the online banking platform database, further comprising:

and updating the transaction according to the approval extension step.

5. The general method for online banking process according to claim 3, wherein when a transaction is completed at the core system, before the step of completing the transaction, further comprising:

Receiving a revocation request, and checking the revocation request;

6. The general method for processing an online banking process according to claim 1, wherein the step of sending the transaction to a core system of a bank for processing at a preset expected time after the approval flow is approval, comprises:

locking the transaction after the approval stream is approval;

judging the transaction state of the transaction;

when the transaction state accords with a preset condition, the transaction is sent to a core system of a bank for processing at a preset expected time, and the locking of the transaction is released.

7. The general method for online banking process according to claim 1, wherein when a transaction is completed at the core system, before the step of completing the transaction, further comprising:

8. An online banking process general device, characterized in that the online banking process general device comprises:

9. An on-line silver flow processing general purpose device, the device comprising: a memory, a processor, and an online banking process general program stored on the memory and executable on the processor, the online banking process general program configured to implement the steps of the online banking process general method of any one of claims 1 to 7.

10. A storage medium, wherein the storage medium has stored thereon an internet banking process general-purpose program, which when executed by a processor, implements the steps of the internet banking process general-purpose method according to any one of claims 1 to 7.