A payment system switching method and device

Abstract

The embodiment of the present application provides a payment system switching method and device, which can be applied to the field of computer technology. In the method, multiple non-account requests received are diverted to an original transaction component and a target transaction component for processing, and multiple real-time account requests received are allocated to a target transaction component for processing; after a first performance evaluation value of a target transaction component obtained based on a processing result of the target transaction component on the non-account request is greater than a preset threshold, the multiple real-time account requests received are diverted to the original transaction component and the target transaction component for processing; when a second performance evaluation value of the target transaction component obtained based on a processing result of the target transaction component on the real-time account request is greater than a preset threshold, the original transaction component is closed, and the real-time and security of the transaction requests during the switching process are improved without affecting the real-time transactions of the payment system.

Description

Technical Field

[0001] The embodiments of the present application relate to the fields of information technology and data processing, and in particular, to a payment system switching method and device. Background Art

[0002] The full name of the xinchuang industry is information technology application innovation, which is a technological innovation based on domestic chips and operating systems, servers, databases, middleware and other infrastructure. In the past, the information technology field mostly used foreign information infrastructure. However, with the development of the domestic xinchuang industry, the deployment of domestic infrastructure has become a trend, so the switching task of various payment systems cannot be delayed.

[0003] However, when switching the payment system, the related technologies mostly adopt a direct copy method or a one-time switching method. When the payment system is switched by adopting this solution, the real-time transaction of the payment system needs to be stopped, thereby affecting the real-time and security of the transaction request processing. Summary of the invention

[0004] The embodiment of the present invention provides a payment system switching method and device, which are used to improve the real-time performance and security of transaction requests during the payment system switching process.

[0005] On the one hand, an embodiment of the present application provides a payment system switching method, the method comprising:

[0006] Dividing the received multiple non-account requests to the original transaction component and the target transaction component for processing; allocating the received multiple real-time account requests to the target transaction component for processing;

[0007] Obtaining a first performance evaluation value of the target transaction component based on a processing result of the target transaction component on the non-account request;

[0008] After determining that the first performance evaluation value is greater than a preset threshold, the received multiple real-time account requests are diverted to the original transaction component and the target transaction component for processing;

[0009] Based on the processing result of the target transaction component on the real-time account request, obtaining a second performance evaluation value of the target transaction component;

[0010] When the second performance evaluation value is greater than a preset threshold, the original transaction component is closed.

[0011] Optionally, when the second performance evaluation value is greater than a preset threshold, after closing the original transaction component, the method further includes:

[0012] Sending the received non-account requests, real-time account requests and batch account requests to the target transaction component for processing;

[0013] The stock data in the original transaction component is synchronized to the target transaction component, and the original transaction component is removed.

[0014] Optionally, before the received multiple non-account requests are diverted to the original transaction component and the target transaction component for processing, the method further includes:

[0015] Load the historical transaction line data of the original transaction component on the previous T-1 day into the target transaction component, and generate the target transaction line data of the Tth day based on the historical transaction line data on the previous T-1 day through the target transaction component, where T is a positive integer greater than 1;

[0016] When the target transaction line data on the Tth day is consistent with the transaction line historical data on the Tth day of the original transaction component, the payment system is triggered to be switched.

[0017] Optionally, the step of diverting the received multiple non-account requests to the original transaction component and the target transaction component for processing includes:

[0018] Sending the plurality of non-account requests to the original transaction component;

[0019] forwarding, by the original transaction component, at least one of the multiple non-account requests to the target transaction component for processing based on identification information carried by the multiple non-account requests;

[0020] Other non-account requests among the multiple non-account requests are processed through the original transaction component.

[0021] Optionally, the forwarding, by the original transaction component, at least one of the multiple non-account requests to the target transaction component for processing based on identification information carried by the multiple non-account requests, includes:

[0022] For the multiple non-accounting requests, the following operations are performed respectively:

[0023] If the identification information carried by a non-account request does not match the first flow control parameter configured in the original transaction component, the non-account request is forwarded to the target transaction component for processing.

[0024] Optionally, the receiving multiple real-time account requests are diverted to the original transaction component and the target transaction component for processing, including:

[0025] For the multiple real-time account requests, the following operations are performed respectively:

[0026] Based on identification information carried by a real-time account request and a second flow control parameter configured in the control component, obtaining a transaction component type for processing the real-time account request;

[0027] If the transaction component type is the target transaction component, forwarding the one real-time account request to the target transaction component for processing through the control component;

[0028] If the transaction component type is the original transaction component, the real-time account request is forwarded to the original transaction component for processing through the control component.

[0029] Optionally, forwarding the real-time account request to the target transaction component for processing by the control component includes:

[0030] Synchronizing a basic parameter file for processing real-time account requests in the original transaction component to the target transaction component;

[0031] The real-time account request is forwarded to the target transaction component through the control component, so that the real-time account request is processed by the target transaction component based on the basic parameter file.

[0032] Optionally, after forwarding the real-time account request to the target transaction component for processing by the control component, the method further includes:

[0033] Synchronizing the processing result of the one real-time account request from the target transaction component to the original transaction component;

[0034] The processing result of the one real-time account request is saved in a database through the original transaction component.

[0035] On the one hand, an embodiment of the present application provides a payment system switching device, the device comprising:

[0036] The allocation module is used to distribute the received multiple non-account requests to the original transaction component and the target transaction component for processing; and allocate the received multiple real-time account requests to the target transaction component for processing.

[0037] A processing module, configured to obtain a first performance evaluation value of the target transaction component based on a processing result of the target transaction component on the non-account request;

[0038] After determining that the first performance evaluation value is greater than a preset threshold, the received multiple real-time account requests are diverted to the original transaction component and the target transaction component for processing;

[0039] Based on the processing result of the target transaction component on the real-time account request, obtaining a second performance evaluation value of the target transaction component;

[0040] When the second performance evaluation value is greater than a preset threshold, the original transaction component is closed.

[0041] Optionally, the processing module is further used for:

[0042] Sending the received non-account requests, real-time account requests and batch account requests to the target transaction component for processing;

[0043] The stock data in the original transaction component is synchronized to the target transaction component, and the original transaction component is removed.

[0044] Optionally, the processing module is further used for:

[0045] Load the historical transaction line data of the original transaction component on the previous T-1 day into the target transaction component, and generate the target transaction line data of the Tth day based on the historical transaction line data on the previous T-1 day through the target transaction component, where T is a positive integer greater than 1;

[0046] When the target transaction line data on the Tth day is consistent with the transaction line historical data on the Tth day of the original transaction component, the payment system is triggered to be switched.

[0047] Optionally, the processing module is specifically used for:

[0048] Sending the plurality of non-account requests to the original transaction component;

[0049] forwarding, by the original transaction component, at least one of the multiple non-account requests to the target transaction component for processing based on identification information carried by the multiple non-account requests;

[0050] Other non-account requests among the multiple non-account requests are processed through the original transaction component.

[0051] Optionally, the processing module is specifically used for:

[0052] For the multiple non-accounting requests, the following operations are performed respectively:

[0053] If the identification information carried by a non-account request does not match the first flow control parameter configured in the original transaction component, the non-account request is forwarded to the target transaction component for processing.

[0054] Optionally, the processing module is specifically used for:

[0055] For the multiple real-time account requests, the following operations are performed respectively:

[0056] Based on identification information carried by a real-time account request and a second flow control parameter configured in the control component, obtaining a transaction component type for processing the real-time account request;

[0057] If the transaction component type is the target transaction component, forwarding the one real-time account request to the target transaction component for processing through the control component;

[0058] If the transaction component type is the original transaction component, the real-time account request is forwarded to the original transaction component for processing through the control component.

[0059] Optionally, the processing module is specifically used for:

[0060] Synchronizing a basic parameter file for processing real-time account requests in the original transaction component to the target transaction component;

[0061] The real-time account request is forwarded to the target transaction component through the control component, so that the real-time account request is processed by the target transaction component based on the basic parameter file.

[0062] Optionally, the processing module is further used for:

[0063] Synchronizing the processing result of the one real-time account request from the target transaction component to the original transaction component;

[0064] The processing result of the one real-time account request is saved in a database through the original transaction component.

[0065] In one aspect, an embodiment of the present application provides a computer device, including:

[0066] A memory for storing program instructions;

[0067] The processor is used to call the program instructions stored in the memory and execute the steps of the payment system switching method according to the obtained program.

[0068] On the one hand, an embodiment of the present application provides a computer-readable storage medium storing a computer program executable by a computer device, and when the program is run on the computer device, the computer executes the steps of the above-mentioned payment system switching method.

[0069] On the one hand, an embodiment of the present application provides a computer program product, including a computer program stored on a computer-readable storage medium, wherein the computer program includes program instructions, and when the program instructions are executed by a computer device, the computer device executes the steps of the above-mentioned payment system switching method.

[0070] In an embodiment of the present application, first, multiple non-account requests are diverted and sent to the original transaction component and the target transaction component for processing, and multiple real-time account requests are diverted and sent to the target transaction component and the original transaction component for processing. During the payment system switching process, non-account requests and real-time account requests are processed in batches and in parallel in dual databases, so that the upstream customers have an imperceptible experience, the timeliness of transaction request switching is effectively improved, and the user experience is enhanced; secondly, when the first performance evaluation value of the processing result of the non-account request is greater than the preset threshold, the real-time account request is diverted to ensure the security of the transaction request. The entire payment system switching process realizes the smooth switching of transaction requests from the original transaction component to the target transaction component without affecting the real-time business transactions. BRIEF DESCRIPTION OF THE DRAWINGS

[0071] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

[0072] Figure 1 A schematic diagram of a system architecture provided in an embodiment of the present application;

[0073] Figure 2 A schematic diagram of a payment system switching method provided in an embodiment of the present application;

[0074] Figure 3 A schematic diagram of the structure of a payment system switching method provided in an embodiment of the present application;

[0075] Figure 4A A schematic diagram of the structure of a payment system switching method provided in an embodiment of the present application;

[0076] Figure 4B A schematic diagram of the structure of a payment system switching method provided in an embodiment of the present application;

[0077] Figure 5 A schematic diagram of the structure of a payment system switching method provided in an embodiment of the present application;

[0078] Figure 6A schematic diagram of the structure of a payment system switching method provided in an embodiment of the present application;

[0079] Figure 7 A schematic diagram of a payment system switching method provided in an embodiment of the present application;

[0080] Figure 8 A schematic diagram of the structure of a payment system switching device provided in an embodiment of the present application;

[0081] Fig. 9 A schematic diagram of the structure of a computer device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0082] In order to make the purpose, technical scheme and beneficial effects of the present invention more clear, the present invention is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not intended to limit the present invention. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present invention.

[0083] The following is a brief introduction to the system architecture diagram applicable to the technical solution of the embodiment of the present application. It should be noted that the process introduced below is only used to illustrate the embodiment of the present application and is not a limitation.

[0084] refer to Figure 1 , which is a system architecture diagram applicable to an embodiment of the present application. The system architecture at least includes a terminal device 101 and a server 102. The number of terminal devices 101 can be one or more, and the number of server 102 can also be one or more. The present application does not specifically limit the number of terminal devices 101 and server 102.

[0085] The terminal device 101 is pre-installed with an application with a payment function, which is a client application, a web application, a small program application, etc. The terminal device 101 can be a smart phone, a tablet computer, a laptop computer, a desktop computer, a smart home appliance, a smart voice interaction device, a smart car device, etc., but is not limited thereto.

[0086] The server 102 is the background server of the application, which is used to process the transaction request sent by the terminal device 101. The server 102 can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content delivery networks (CDN), and big data and artificial intelligence platforms, but is not limited to these.

[0087] In some embodiments, the server 102 includes: a basic component layer, a channel layer, a user service integration layer, an application integration layer, an external connection layer, a settlement system, a service layer, a data layer, and a management and analysis layer.

[0088] Among them, the channel layer includes user channels and employee channels. The employee channel is a channel specially set up for the staff of the bank where the payment system is located, and the user channel is a channel set up for users that is different from the staff. The application integration layer includes: service publishing. All requests initiated by users and staff through any device or application are passed to relevant components for processing through service publishing.

[0089] The service layer includes original transaction components and target transaction components; the data layer includes standard data areas, historical archive data storage and cloud data warehouses; the management and analysis layer includes: management and analysis services-component library; the basic component layer includes: security, message center, file transfer and other basic components.

[0090] The purpose of this application is to switch from processing the transaction request from the original transaction component to processing the transaction request from the target transaction component, thereby achieving the switching of the payment system.

[0091] It should be noted that the method in the embodiment of the present application can be executed by the terminal device 101 or the server 102 alone, or can be executed by the terminal device 101 and the server 102 together.

[0092] In the embodiment of the present application, the terminal device 101 and the server 102 can be directly or indirectly connected to each other through one or more networks. The network can be a wired network or a wireless network, for example, the wireless network can be a mobile cellular network, or a wireless fidelity (Wireless-Fidelity, WIFI) network, and of course, it can be other possible networks, which are not limited in the embodiment of the present application.

[0093] The following is a description of exemplary embodiments of the present application in conjunction with the accompanying drawings, including various details of the embodiments of the present application to facilitate understanding, which should be considered as merely exemplary. Therefore, those of ordinary skill in the art should recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope of the present application. Similarly, for the sake of clarity and conciseness, the description of well-known functions and structures is omitted in the following description. It should be noted that in the embodiments of the present application, certain software, components, models and other existing solutions in the industry may be mentioned, which should be considered as exemplary, and their purpose is only to illustrate the feasibility of the implementation of the technical solution of the present application, but it does not mean that the applicant has or will necessarily use the solution.

[0094] It should be noted that the acquisition, transmission, storage, and use of data in the technical solution of this application are in compliance with the relevant provisions of national laws and regulations.

[0095] The following is based on Figure 1 The system architecture diagram shown in FIG. 1 shows a flow chart of a payment system switching method provided in an embodiment of the present application. The flow chart of the method can be Figure 1 The server 102 shown in FIG. 104 may also be executed by the terminal device 101 interacting with the server 102, such as Figure 2 As shown, the following steps are included:

[0096] Step 201: Divide the received multiple non-account requests into the original transaction component and the target transaction component for processing; distribute the received multiple real-time account requests into the target transaction component for processing.

[0097] Specifically, non-account requests are non-account online transactions involving the signing of the overseas quick payment EDDA agreement and the calculation of fees for overseas payment transactions. The EDDA protocol is an electronic direct debit authorization system that allows customers to authorize merchants or service providers to directly deduct funds from the customer's bank account to pay bills or regular expenses, such as water, electricity, telephone bills, mortgages or rent, etc.; real-time account requests are account online transactions involving the signing of the overseas quick payment Addressing protocol, real-time credit, real-time debit, refund, etc. The Addressing protocol is used to identify the account information of the payee and payer to ensure that payment instructions can be accurately delivered and prevent payment errors and abnormal transaction behaviors.

[0098] In some embodiments, before the received multiple non-account requests are diverted to the original transaction component and the target transaction component for processing, the historical transaction line data of the original transaction component in the previous T-1 day is loaded into the target transaction component, and the target transaction line data of the Tth day is generated based on the historical transaction line data of the previous T-1 day through the target transaction component, where T is a positive integer greater than 1; when the target transaction line data of the Tth day is consistent with the historical transaction line data of the original transaction component on the Tth day, the payment system is triggered to switch.

[0099] Specifically, transaction line data refers to transaction data for credit cards, personal loans, and acquiring. Among them, credit cards refer to credit cards issued by banks or credit card companies based on the user's credit and financial resources. Cardholders can use credit cards for consumption and repay on the checkout date. Personal loans refer to loans applied for by individuals from banks, which usually require certain collateral or credit guarantees; acquiring refers to institutions with bank card acquiring qualifications providing acceptance debit cards to special customers through acceptance terminals and completing related fund settlements, including: installation, maintenance and management of acceptance terminals, transaction monitoring, risk management, transaction error handling and other services.

[0100] For example, refer to Figure 3 In the service layer, the original transaction component and the target transaction component were originally independent of each other. The transaction line data of the original transaction component in the previous T-1 day, including the relevant data of credit cards, personal loans, and acquiring, and the supply data of the original transaction component in the previous T-1 day (that is, the data stored in the database of the standard data area), are obtained, and these transaction line data are imported into the target transaction component, so that the target transaction component generates the target transaction line data of the Tth day based on the transaction line data of the previous T-1, including the credit card repayment file, personal loan repayment file, acquiring reconciliation file and supply data of the Tth day, and compares and verifies the target transaction line data with the credit card repayment file, personal loan repayment file, acquiring reconciliation file and supply data of the original transaction component on the Tth day. If the two are consistent, it means that the target transaction component has the performance to process similar transaction requests, and then triggers the subsequent payment system switch.

[0101] In the embodiment of the present application, the transaction line data of the original transaction component and the target transaction component are compared and verified in parallel, which provides a basis for the subsequent parallel operation of the two components and ensures the stable operation of the system.

[0102] In some embodiments, multiple non-account requests are sent to an original transaction component, and at least one of the multiple non-account requests is forwarded to a target transaction component for processing through the original transaction component based on identification information carried by the multiple non-account requests; and other non-account requests among the multiple non-account requests are processed through the original transaction component.

[0103] Specifically, the non-account request carries the address identifier of the transaction component, and the original transaction component can address the transaction component that can process the non-account request according to the address identifier.

[0104] For example, refer to Figure 4A Before switching the payment system, the service release sends the transaction request to the original transaction component. The original transaction component can handle transaction line tasks such as deposit and debit card business, credit card, personal loan, and acquiring. For ordinary payment business (including transaction line tasks), such as cash on delivery, credit card payment and other consumer scenarios, the original transaction component can directly process and save the processing results to the database in the standard data area. For settlement business, such as bank drafts, commercial drafts, bank promissory notes, checks, remittances, and cross-regional collection and payment settlement, the processing results are sent to the external connection layer after being processed by the original transaction component. The external connection layer forwards the processing results of the original transaction component to the settlement system in the form of a message. The settlement is completed by the settlement system, and the settlement results are returned to the original transaction component through the external connection layer. The original transaction component saves the settlement results to the database in the standard data area.

[0105] For non-accounting requests, refer to Figure 4B ,exist Figure 4A On this basis, the target transaction component can receive and process non-account requests, and for non-account requests related to settlement business, the processing results can be directly sent to the external layer, and the external layer forwards the processing results of the target transaction component to the settlement system in the form of a message. The settlement system completes the settlement and returns the settlement results to the original transaction component through the external layer, and the original transaction component saves the settlement results to the database in the standard data area.

[0106] For non-accounting requests other than settlement services, the target transaction component sends the processing results to the original transaction component, and the original transaction component saves the processing results of the target transaction component into the database.

[0107] In some embodiments, for multiple non-account requests, the following operations are performed respectively: if the identification information carried by a non-account request does not match the first flow control parameter configured in the original transaction component, the non-account request is forwarded to the target transaction component for processing.

[0108] Specifically, each non-account request carries an address identifier. When the first flow control parameter configured in the original transaction component matches the address identifier of the non-account request, the non-account request is processed in the original transaction component; when the address identifier of the non-account request does not match the first flow control parameter of the original transaction component, the original transaction component allocates the corresponding non-account request to the transaction component with the matching address identifier for processing based on the address identifier.

[0109] In addition, when a query request for a processing result of a non-account request for a settlement service occurs, a synchronous query can be implemented by the original transaction component or the target transaction component.

[0110] Step 202, based on the processing result of the target transaction component on the non-account request, obtain a first performance evaluation value of the target transaction component; after determining that the first performance evaluation value is greater than a preset threshold, the received multiple real-time account requests are diverted to the original transaction component and the target transaction component for processing.

[0111] Specifically, the first performance evaluation value of the target transaction component refers to the processing success rate of the target transaction component for non-account requests. When the processing success rate of non-account requests is greater than the preset threshold value of 95%, it means that the target transaction component can process non-account requests normally. Therefore, the next batch of switching can be carried out, that is, the switching for real-time account requests, and the real-time account requests originally processed by the original transaction component are diverted to the original transaction component and the target transaction component for processing.

[0112] In some embodiments, for multiple real-time account requests, the following operations are performed respectively: based on the identification information carried by a real-time account request and the second flow control parameter configured in the management and control component, a transaction component type for processing a real-time account request is obtained; if the transaction component type is a target transaction component, the real-time account request is forwarded to the target transaction component for processing through the management and control component; if the transaction component type is an original transaction component, the real-time account request is forwarded to the original transaction component for processing through the management and control component.

[0113] Specifically, refer to Figure 5 The control component is deployed in the service release of the application integration layer. The second flow control parameter configured in the control component can identify the processing identifier of the real-time account request, and determine the type of transaction component that processes the real-time account request based on the processing identifier. The service release directly sends the real-time account request to the transaction component corresponding to the transaction component type; if the transaction component type is a target transaction component, a real-time account request is forwarded to the target transaction component for processing through the control component, and does not need to be forwarded by the original transaction component; if the transaction component type is an original transaction component, a real-time account request is forwarded to the original transaction component for processing through the control component.

[0114] The processing identifier carried by the real-time account request can be set according to the user's special requirements; if the user has no special requirements, multiple real-time account requests within a preset time period will be evenly distributed with processing identifiers corresponding to different transaction component types, so as to evenly distribute multiple real-time account requests to the original transaction component and the target transaction component.

[0115] In some embodiments, a basic parameter file for processing real-time account requests in an original transaction component is synchronized to a target transaction component; a real-time account request is forwarded to a target transaction component through a management and control component, so that the target transaction component processes the real-time account request based on the basic parameter file.

[0116] Specifically, the basic parameter files include: Faster Payment System (FPS) participating bank status notification, Stored Value Facility (SVF) rule maintenance, new and old whitelist account maintenance, account name check matching rate switch, account name check matching rate maintenance, whitelist maintenance, virtual account maintenance, host account cancellation file and receiving bank number file, etc.

[0117] For example, refer to Figure 5 Before the target transaction component receives and processes the real-time account request, the basic parameters used to process the real-time account request in the original transaction component are organized into a basic parameter file, and the basic parameter file is synchronized to the target transaction component through the original transaction component, so that the basic parameters used to process the real-time account request in the original transaction component and the target transaction component are synchronized. In addition, when the settlement system initiates a basic parameter change for the processing method of the real-time account request, the settlement system sends the updated basic parameter file to the original transaction component. After the original transaction component successfully processes the real-time account request based on the updated basic parameter file, the updated basic parameter file is forwarded to the target transaction component, and the updated basic parameter file is parsed and stored in the database through the target transaction component.

[0118] In an embodiment of the present application, after the basic parameter file in the original transaction component is synchronized to the target transaction component, the target transaction component can process the received real-time account request, so that the basic parameters in the original transaction component and the target transaction component are consistent, thereby ensuring the operational stability during the payment system switching process and improving the security of the transaction request.

[0119] In some embodiments, after a real-time account request is forwarded to a target transaction component for processing through a management and control component, the processing result of the real-time account request is synchronized from the target transaction component to the original transaction component; and the processing result of the real-time account request is saved in a database through the original transaction component.

[0120] Specifically, since multiple real-time account requests are diverted, the business data (i.e., processing results) in the original transaction component and the target transaction component are different, and processing user query requests is more complicated. Therefore, the processing result of a real-time account request is synchronized to the original transaction component through the target transaction component, and the processing result of the target transaction component and its own processing result are saved in the database in the form of sub-files through the original transaction component, or the processing results are returned to the application end together, so that the processing results are not missing or omitted, which is conducive to users initiating result query requests.

[0121] The business data sent to the original transaction component through the target transaction component includes: FPS transaction details, FPS transaction details, FPS transaction details connection report, FPS transaction payment record, FPS participating line list, FPS abnormal message, etc.

[0122] Step 203, based on the processing result of the target transaction component on the real-time account request, obtain a second performance evaluation value of the target transaction component; when the second performance evaluation value is greater than a preset threshold, close the original transaction component.

[0123] Specifically, the second performance evaluation value of the target transaction component refers to the processing success rate of the target transaction component for real-time account requests. When the processing success rate of real-time account requests is greater than the preset threshold of 95%, it means that the target transaction component can process real-time account requests normally, and therefore the next batch can be switched.

[0124] In some embodiments, after closing the original transaction component, the received non-account requests, real-time account requests, and batch account requests are sent to the target transaction component for processing; the stock data in the original transaction component is synchronized to the target transaction component, and the original transaction component is removed.

[0125] Specifically, the batch account request is a batch account transaction involving overseas fast payment batch debit, settlement system electronic exchange, overseas batch clearing, etc.

[0126] Closing the original transaction component means closing the non-fungible token (NFT) in the original transaction component and migrating the NFT function of the original transaction component from the original transaction component to the target transaction component. NFT uses smart contracts to transfer files across servers, which is unique, irreplaceable and programmable, and can ensure the permanence and transparency of transaction records. After the target transaction component obtains the NFT function of the original transaction component, the service release directly sends non-account requests, real-time account requests and batch account requests to the target transaction component for processing, realizing the switching of various types of transaction requests from the original transaction component to the target transaction component.

[0127] Stock data refers to the balance data of products, reserves, assets and liabilities produced and accumulated in the past within a specific period of time. Specifically, it may include: total assets of a company, government bonds, foreign exchange reserves of a country, personal bank deposits and real estate stocks, etc.

[0128] For example, refer to Figure 6 After the original transaction component is removed, the target transaction component is fully responsible for processing various transaction requests. The target transaction component directly receives non-account requests, real-time account requests and batch account requests issued by the service. The target transaction component can handle deposit debit card business, as well as credit card, personal loan, acquiring and other transaction line tasks; the target transaction component directly interacts with the external connection layer, and forwards the non-account requests, real-time account requests and batch account requests related to the settlement business to the settlement system for settlement through the external connection layer. The settlement system then returns the processing results related to the settlement business to the target transaction component through the external connection layer, and the target transaction component saves the processing results of non-account requests, real-time account requests and batch account requests to the database in the standard data area.

[0129] In an embodiment of the present application, first, multiple non-account requests are diverted and sent to the original transaction component and the target transaction component for processing, and multiple real-time account requests are diverted and sent to the target transaction component and the original transaction component for processing. During the payment system switching process, the non-account requests and the real-time account requests are processed in batches and in parallel by dual databases, so that the upstream customers have an imperceptible experience, the timeliness of transaction request switching is effectively improved, and the user experience is enhanced; secondly, when the first performance evaluation value of the processing result of the non-account request is greater than the preset threshold, the real-time account request is diverted to ensure the security of the transaction request. The entire payment system switching process realizes the smooth switching of the transaction request from the original transaction component to the target transaction component without affecting the real-time business transactions.

[0130] In order to better explain the embodiment of the present application, a method for switching a payment system provided by the embodiment of the present application is introduced below in combination with an actual scenario. The process of the method is as follows: Figure 1 The server execution shown in FIG. 1 includes the following steps: Figure 7 As shown:

[0131] Step 701, prepare batches: based on the historical transaction line data of the original transaction component, verify the consistency of the transaction line of the target transaction component, and execute the payment system switching operation if the verification is successful.

[0132] Specifically, if the verification fails, the target transaction component is manually checked and repaired.

[0133] Step 702, the first batch: multiple non-account requests are diverted to the original transaction component and the target component for processing, multiple real-time account requests and batch account requests are allocated to the original transaction component for processing, and after determining that the first performance evaluation value of the target transaction component's processing result for the non-account request is greater than a preset threshold, the second batch switching is performed.

[0134] Step 703, second batch: multiple non-account requests and real-time account requests are diverted to the original transaction component and the target transaction component for processing, multiple batch account requests are allocated to the original transaction component for processing, and after determining that the second performance evaluation value of the target transaction component's processing result of the real-time account request is greater than a preset threshold, execute the third batch switching.

[0135] Specifically, during the switching process between the first batch and the second batch, the processing results of non-account requests and real-time account requests by the target transaction component are sent to the original transaction component, so that the original transaction component saves the processing results of the target transaction component and its own processing results of non-account requests, real-time account requests, and batch account requests into the database.

[0136] Step 704, the third batch: close the NFT in the original transaction component, send multiple non-account requests, real-time account requests and batch account requests to the target transaction component for processing, obtain the processing results, and save the processing results to the database through the target transaction component.

[0137] Step 705, fourth batch: migrate the stock data in the original transaction component to the target transaction component, and remove the original transaction component.

[0138] In the embodiment of the present application, the payment system is switched by diverting in batches, which can smoothly transition from the application container environment deployed by foreign infrastructure to the transformation of a full set of domestically-produced trust-based infrastructure plus applications, so that the stability and security of the financial system can be guaranteed; secondly, in the diversion and switching process, 7*24h non-stop transition is achieved, reducing the risks brought by the system's full switch from the original commercial technology stack to the trust-based environment. At the same time, transactions are gradually transitioned and dual databases are run in parallel, which makes it imperceptible to upstream and downstream related parties, saves financial costs, and realizes financial speed and convenience; in the switching process of each batch, data storage at all stages of the entire process and query of the dual database merged result set are realized, which not only ensures the high security of the data, but also completely isolates the data of the two databases, ensuring that data scanning and accounting are completely independent.

[0139] Based on the same technical concept, the present application embodiment provides a structural diagram of a payment system switching device, such as Figure 8 As shown, the payment system switching device 800 includes:

[0140] The allocation module 801 is used to distribute the received multiple non-account requests to the original transaction component and the target transaction component for processing; and allocate the received multiple real-time account requests to the target transaction component for processing.

[0141] A processing module 802, configured to obtain a first performance evaluation value of the target transaction component based on a processing result of the target transaction component on the non-account request;

[0142] After determining that the first performance evaluation value is greater than a preset threshold, the received multiple real-time account requests are diverted to the original transaction component and the target transaction component for processing;

[0143] Based on the processing result of the target transaction component on the real-time account request, obtaining a second performance evaluation value of the target transaction component;

[0144] When the second performance evaluation value is greater than a preset threshold, the original transaction component is closed.

[0145] Optionally, the processing module 802 is further configured to:

[0146] Sending the received non-account requests, real-time account requests and batch account requests to the target transaction component for processing;

[0147] The stock data in the original transaction component is synchronized to the target transaction component, and the original transaction component is removed.

[0148] Optionally, the processing module 802 is further configured to:

[0149] Load the historical transaction line data of the original transaction component on the previous T-1 day into the target transaction component, and generate the target transaction line data of the Tth day based on the historical transaction line data on the previous T-1 day through the target transaction component, where T is a positive integer greater than 1;

[0150] When the target transaction line data on the Tth day is consistent with the transaction line historical data on the Tth day of the original transaction component, the payment system is triggered to be switched.

[0151] Optionally, the processing module 802 is specifically configured to:

[0152] Sending the plurality of non-account requests to the original transaction component;

[0153] forwarding, by the original transaction component, at least one of the multiple non-account requests to the target transaction component for processing based on identification information carried by the multiple non-account requests;

[0154] Other non-account requests among the multiple non-account requests are processed through the original transaction component.

[0155] Optionally, the processing module 802 is specifically configured to:

[0156] For the multiple non-accounting requests, the following operations are performed respectively:

[0157] If the identification information carried by a non-account request does not match the first flow control parameter configured in the original transaction component, the non-account request is forwarded to the target transaction component for processing.

[0158] Optionally, the processing module 802 is specifically configured to:

[0159] For the multiple real-time account requests, the following operations are performed respectively:

[0160] Based on identification information carried by a real-time account request and a second flow control parameter configured in the control component, obtaining a transaction component type for processing the real-time account request;

[0161] If the transaction component type is the target transaction component, forwarding the one real-time account request to the target transaction component for processing through the control component;

[0162] If the transaction component type is the original transaction component, the real-time account request is forwarded to the original transaction component for processing through the control component.

[0163] Optionally, the processing module 802 is specifically configured to:

[0164] Synchronizing a basic parameter file for processing real-time account requests in the original transaction component to the target transaction component;

[0165] The real-time account request is forwarded to the target transaction component through the control component, so that the real-time account request is processed by the target transaction component based on the basic parameter file.

[0166] Optionally, the processing module 802 is further configured to:

[0167] Synchronizing the processing result of the one real-time account request from the target transaction component to the original transaction component;

[0168] The processing result of the one real-time account request is saved in a database through the original transaction component.

[0169] In the embodiment of the present application, the payment system is switched by diverting in batches, which can smoothly transition from the application container environment deployed by foreign infrastructure to the transformation of a full set of domestically-produced infrastructure plus applications, so that the stability and security of the financial system can be guaranteed; secondly, in the diversion and switching process, 7*24h non-stop transition is achieved, reducing the risks brought by the payment system's full switch from the original commercial technology stack to the trusted innovation environment. At the same time, transactions are gradually transitioned and dual databases are run in parallel, which makes it imperceptible to upstream and downstream related parties, saves transaction costs, and realizes financial convenience; in the switching process of each batch, data storage and dual database merge result set query are realized at all stages of the whole process, which not only ensures the high security of the data, but also completely isolates the data of the two databases, ensuring that data scanning and accounting are completely independent.

[0170] Based on the same technical concept, the embodiment of the present application provides a computer device, which can be Figure 1 The server shown in Fig. 9 As shown, it includes at least one processor 901 and a memory 902 connected to the at least one processor. The specific link medium between the processor 901 and the memory 902 is not limited in the embodiment of the present application. Fig. 9 For example, the processor 901 and the memory 902 are connected via a bus. The bus can be divided into an address bus, a data bus, a control bus, etc.

[0171] In the embodiment of the present application, the memory 902 stores instructions executed by at least one processor 901, and the at least one processor 901 can perform the steps of the above-mentioned payment system switching method by executing the instructions stored in the memory 902.

[0172] Among them, the processor 901 is the control center of the computer device, and can use various interfaces and lines to connect various parts of the computer device, and realize the payment system switching by running or executing instructions stored in the memory 902 and calling data stored in the memory 902. Optionally, the processor 901 may include one or more processing modules, and the processor 901 may integrate an application processor and a modem processor, wherein the application processor mainly processes the operating system, user interface, and application programs, etc., and the modem processor mainly processes wireless communication. It is understandable that the above-mentioned modem processor may not be integrated into the processor 901. In some embodiments, the processor 901 and the memory 902 may be implemented on the same chip, and in some embodiments, they may also be implemented separately on independent chips.

[0173] Processor 901 can be a general-purpose processor, such as a central processing unit (CPU), a digital signal processor, an application-specific integrated circuit (ASIC), a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, and can implement or execute the methods, steps and logic block diagrams disclosed in the embodiments of the present application. A general-purpose processor can be a microprocessor or any conventional processor, etc. The steps of the method disclosed in the embodiments of the present application can be directly embodied as a hardware processor for execution, or can be executed by a combination of hardware and software modules in the processor.

[0174] The memory 902 is a non-volatile computer-readable storage medium that can be used to store non-volatile software programs, non-volatile computer executable programs and modules. The memory 902 may include at least one type of storage medium, such as a flash memory, a hard disk, a multimedia card, a card-type memory, a random access memory (Random Access Memory, RAM), a static random access memory (Static Random Access Memory, SRAM), a programmable read-only memory (Programmable Read Only Memory, PROM), a read-only memory (Read Only Memory, ROM), an electrically erasable programmable read-only memory (Electrically Erasable Programmable Read-Only Memory, EEPROM), a magnetic memory, a disk, an optical disk, etc. The memory 902 is any other medium that can be used to carry or store a desired program code in the form of an instruction or data structure and can be accessed by a computer device, but is not limited thereto. The memory 902 in the embodiment of the present application can also be a circuit or any other device that can realize a storage function, for storing program instructions and / or data.

[0175] Based on the same inventive concept, an embodiment of the present application provides a computer-readable storage medium storing a computer program executable by a computer device. When the program runs on the computer device, the computer device executes the steps of the above-mentioned payment system switching method.

[0176] Based on the same inventive concept, an embodiment of the present application provides a computer program product, including a computer program stored on a computer-readable storage medium, wherein the computer program includes program instructions, and when the program instructions are executed by a computer device, the computer device executes the steps of the above-mentioned payment system switching method.

[0177] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that include computer-usable program code.

[0178] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0179] These computer program instructions may also be stored in a computer readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0180] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0181] Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.

Claims

1. A payment system switching method, characterized in that: include: Diverting multiple non-accounting requests received to the original transaction component and the target transaction component for processing; Allocating the received multiple real-time account requests to the target transaction component for processing; Obtaining a first performance evaluation value of the target transaction component based on a processing result of the target transaction component on the non-account request; After determining that the first performance evaluation value is greater than a preset threshold, the received multiple real-time account requests are diverted to the original transaction component and the target transaction component for processing; Based on the processing result of the target transaction component on the real-time account request, obtaining a second performance evaluation value of the target transaction component; When the second performance evaluation value is greater than a preset threshold, the original transaction component is closed.

2. The method according to claim 1, characterized in that When the second performance evaluation value is greater than a preset threshold, after closing the original transaction component, the method further includes: Sending the received non-account requests, real-time account requests and batch account requests to the target transaction component for processing; The stock data in the original transaction component is synchronized to the target transaction component, and the original transaction component is removed.

3. The method according to claim 1, characterized in that Before the received multiple non-account requests are diverted to the original transaction component and the target transaction component for processing, the method further includes: Load the historical transaction line data of the original transaction component on the previous T-1 day into the target transaction component, and generate the target transaction line data of the Tth day based on the historical transaction line data on the previous T-1 day through the target transaction component, where T is a positive integer greater than 1; When the target transaction line data on the Tth day is consistent with the transaction line historical data on the Tth day of the original transaction component, the payment system is triggered to be switched.

4. The method according to claim 1, characterized in that The step of diverting the received multiple non-account requests to the original transaction component and the target transaction component for processing includes: Sending the plurality of non-account requests to the original transaction component; forwarding, by the original transaction component, at least one of the multiple non-account requests to the target transaction component for processing based on identification information carried by the multiple non-account requests; Other non-account requests among the multiple non-account requests are processed through the original transaction component.

5. The method according to claim 4, characterized in that The forwarding, by the original transaction component, at least one of the multiple non-account requests to the target transaction component for processing based on the identification information carried by the multiple non-account requests, includes: For the multiple non-accounting requests, the following operations are performed respectively: If the identification information carried by a non-account request does not match the first flow control parameter configured in the original transaction component, the non-account request is forwarded to the target transaction component for processing.

6. The method according to any one of claims 1 to 5, characterized in that: The receiving multiple real-time account requests are divided into the original transaction component and the target transaction component for processing, including: For the multiple real-time account requests, the following operations are performed respectively: Obtaining a transaction component type for processing a real-time account request based on identification information carried by the real-time account request and a second flow control parameter configured in the control component; If the transaction component type is the target transaction component, forwarding the one real-time account request to the target transaction component for processing through the control component; If the transaction component type is the original transaction component, the real-time account request is forwarded to the original transaction component for processing through the control component.

7. The method according to claim 6, characterized in that The forwarding of the real-time account request to the target transaction component for processing by the control component includes: Synchronizing a basic parameter file for processing real-time account requests in the original transaction component to the target transaction component; The real-time account request is forwarded to the target transaction component through the control component, so that the real-time account request is processed by the target transaction component based on the basic parameter file.

8. The method according to claim 6, characterized in that After forwarding the real-time account request to the target transaction component for processing by the control component, the method further includes: Synchronizing the processing result of the one real-time account request from the target transaction component to the original transaction component; The processing result of the one real-time account request is saved in a database through the original transaction component.

9. A device for switching a payment system, characterized in that: include: A distribution module, used for distributing multiple non-account requests received to an original transaction component and a target transaction component for processing; Allocating the received multiple real-time account requests to the target transaction component for processing; A processing module, configured to obtain a first performance evaluation value of the target transaction component based on a processing result of the target transaction component on the non-account request; After determining that the first performance evaluation value is greater than a preset threshold, the received multiple real-time account requests are diverted to the original transaction component and the target transaction component for processing; Based on the processing result of the target transaction component on the real-time account request, obtaining a second performance evaluation value of the target transaction component; When the second performance evaluation value is greater than a preset threshold, the original transaction component is closed.

10. A computer device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the program, the steps of any one of the methods of claims 1 to 8 are implemented.

11. A computer-readable storage medium, characterized in that: It stores a computer program executable by a computer device. When the program is run on the computer device, the computer device executes the steps of any method described in claims 1 to 8.

12. A computer program product, characterized in that The computer program product comprises a computer program stored on a computer-readable storage medium, wherein the computer program comprises program instructions, and when the program instructions are executed by a computer device, the computer device is caused to execute the steps of the method according to any one of claims 1 to 8.

Images