Payment and clearing method, device and system and electronic equipment

Abstract

The invention discloses a payment liquidation method, device and system and electronic equipment, and the method comprises the steps: obtaining the liquidation result of summarized liquidation data sent by each service layer main body for a switching layer, and the summarized liquidation data comprises the liquidation data corresponding to each service layer main body; selecting one of the service layer main bodies as a target service layer main body; controlling the target service layer main body to sign the summarized clearing data and the clearing result obtained by the current clearing and the stored last signature data obtained by the last clearing, and storing the obtained current signature data; and controlling the target service layer main body to send a liquidation result obtained by this liquidation and this signature data to a transfer layer. According to the invention, the disaster recovery scheme of payment and settlement is constructed, so that the normal operation of payment and settlement services can still be ensured when the original settlement system cannot operate normally, and the continuity, effectiveness and reliability in the payment and settlement process are ensured.

Description

Technical Field

[0001] This application relates to the technical field of clearing, and in particular, to a payment clearing method, device, system, and electronic device. Background Art

[0002] In the related art, the process of payment clearing mainly relies on the cooperation of the client layer, service layer, transfer layer, and clearing layer to achieve the settlement of the creditor's rights and debts between traders. However, in the related art, since the clearing stage highly depends on the clearing system of the clearing layer, if the clearing system becomes unavailable, it may lead to the abnormal operation of the clearing business. Therefore, how to construct a disaster tolerance solution to ensure the normal operation of the payment clearing business when the original clearing system fails has become an urgent problem to be solved. Summary of the Invention

[0003] This application aims to solve at least one of the technical problems in the related art to some extent.

[0004] To this end, the first object of this application is to propose a payment clearing method, which is used to solve the technical problem that in the existing payment clearing method, when the original clearing system fails, the normal operation of the payment clearing business can still be ensured through the constructed disaster tolerance solution for payment clearing.

[0005] The second object of the present invention is to propose a payment clearing device.

[0006] The third object of the present invention is to propose a payment clearing system.

[0007] The fourth object of the present invention is to propose an electronic device.

[0008] The fifth object of the present invention is to propose a computer-readable storage medium.

[0009] To achieve the above object, the first aspect embodiment of this application provides a payment clearing method, and the method includes the following steps: obtaining the clearing results of the summary clearing data sent by each service layer entity to the transfer layer, where the summary clearing data includes the clearing data corresponding to each service layer entity; selecting one of each service layer entity as the target service layer entity; controlling the target service layer entity to sign the summary clearing data, the clearing results, and the previous signature data obtained from the previous clearing stored during the current clearing, and storing the obtained current signature data; controlling the target service layer entity to send the clearing results and the current signature data obtained during the current clearing to the transfer layer.

[0010] In addition, the payment clearing method according to the above embodiment of this application may further have the following additional technical features:

[0011] Before obtaining the settlement result of the summary settlement data sent by each service layer entity to the transfer layer according to an embodiment of the present application, the method further includes: receiving the summary settlement data sent by the transfer layer; distributing the summary settlement data to each service layer entity; and controlling each service layer entity to perform settlement on the summary settlement data to obtain the settlement result.

[0012] According to an embodiment of the present application, the method further includes: storing the summary settlement data and the settlement result obtained in this settlement.

[0013] According to an embodiment of the present application, controlling the target service layer entity to sign the summary settlement data, the settlement result obtained in this settlement, and the previous signature data obtained in the previous settlement stored, includes: controlling the target service layer entity to use its own private key to sign the summary settlement data, the settlement result obtained in this settlement, and the previous signature data.

[0014] According to an embodiment of the present application, selecting one of the service layer entities as the target service layer entity includes: if the settlement results of all service layer entities are consistent, selecting one of the service layer entities as the target service layer entity.

[0015] According to an embodiment of the present application, selecting one of the service layer entities as the target service layer entity includes: randomly selecting one of the service layer entities as the target service layer entity.

[0016] The payment settlement method provided by the first aspect embodiment of the present application can, based on the constructed disaster recovery solution for payment settlement, that is, by using the service layer as the execution entity, obtain the settlement result, control the selected target service layer entity to sign the summary settlement data, the settlement result obtained in this settlement, and the previous signature data obtained in the previous settlement stored, and store the signature data of this time, and then control the target service layer entity to send the settlement result and the signature data of this time obtained in this settlement to the transfer layer to implement payment settlement. When the original settlement system cannot operate normally, based on the payment settlement method provided by the present application, it can continue to ensure the normal progress of the payment settlement service, and ensure the continuity, effectiveness, and reliability in the payment settlement process.

[0017] To achieve the above object, an embodiment of the second aspect of the present application provides a payment and settlement device. The payment and settlement device includes: an acquisition module, configured to acquire the settlement results of the summary settlement data sent by each service layer entity to the transfer layer, where the summary settlement data includes the settlement data corresponding to each service layer entity; a selection module, configured to select one of each service layer entity as the target service layer entity; a first control module, configured to control the target service layer entity to sign the summary settlement data, the settlement results obtained in this settlement, and the previous signature data obtained in the previous settlement stored, and store the obtained current signature data; a second control module, configured to control the target service layer entity to send the settlement results and the current signature data obtained in this settlement to the transfer layer.

[0018] In addition, the payment and settlement device according to the above embodiment of the present application may further have the following additional technical features:

[0019] According to an embodiment of the present application, the payment and settlement device proposed by the present application further includes: a third control module, configured to receive the summary settlement data sent by the transfer layer; distribute the summary settlement data to each service layer entity; and control each service layer entity to perform settlement on the summary settlement data to obtain the settlement results.

[0020] According to an embodiment of the present application, the third control module is further configured to store the summary settlement data and the settlement results obtained in this settlement.

[0021] According to an embodiment of the present application, the first control module is specifically configured to control the target service layer entity to sign the summary settlement data, the settlement results obtained in this settlement, and the previous signature data with its own private key.

[0022] According to an embodiment of the present application, the selection module is specifically configured to, if the settlement results of each service layer entity are the same, select one of each service layer entity as the target service layer entity.

[0023] According to an embodiment of the present application, the selection module is specifically configured to randomly select one of each service layer entity as the target service layer entity.

[0024] In the second aspect of the embodiments of the present application, a payment and clearing device is provided. Based on the constructed disaster recovery solution for payment and clearing, that is, by taking the service layer as the execution entity, the clearing result can be obtained, and it is controlled that the selected target service layer entity signs the summary clearing data, clearing result obtained from this clearing, and the previous signature data obtained from the previous clearing stored, and the current signature data is stored. Furthermore, it is controlled that the target service layer entity sends the clearing result and the current signature data obtained from this clearing to the transfer layer to achieve payment and clearing. When the original clearing system cannot operate normally, based on the payment and clearing method provided in the present application, the normal progress of payment and clearing services can be continuously guaranteed, ensuring the continuity, effectiveness, and reliability in the payment and clearing process.

[0025] To achieve the above object, in the third aspect of the embodiments of the present application, a payment and clearing system is provided. The system includes: a transfer layer, a customer layer, and a payment and clearing device as described in the second aspect of the embodiments of the present application.

[0026] To achieve the above object, in the fourth aspect of the embodiments of the present application, an electronic device is provided, including: a memory, a processor, and a computer program stored on the memory and executable on the processor. When the processor executes the program, the payment and clearing method as described in any one of the first aspect of the embodiments of the present application is implemented.

[0027] To achieve the above object, in the fifth aspect of the embodiments of the present application, a computer-readable storage medium is provided. When the program is executed by the processor, the payment and clearing method as described in any one of the first aspect of the embodiments of the present application is implemented. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] Figure 1 It is a schematic flowchart of the payment and clearing method disclosed in an embodiment of the present application;

[0029] Figure 2 It is a schematic flowchart of the payment and clearing method disclosed in another embodiment of the present application;

[0030] Figure 3 It is a schematic flowchart of the payment and clearing method disclosed in yet another embodiment of the present application;

[0031] Figure 4 It is a schematic flowchart of the payment and clearing method disclosed in still another embodiment of the present application;

[0032] Figure 5 It is a schematic structural diagram of the payment and clearing device disclosed in an embodiment of the present application;

[0033] Figure 6 It is a schematic structural diagram of the payment and clearing device disclosed in another embodiment of the present application;

[0034] Figure 7 Schematic structural diagram of a payment and clearing system disclosed in an embodiment of the present application;

[0035] Figure 8 Schematic structural diagram of a payment and clearing system disclosed in another embodiment of the present application;

[0036] Figure 9 Schematic structural diagram of an existing payment and clearing system disclosed in an embodiment of the present application;

[0037] Figure 10 Schematic structural diagram of an electronic device provided in an embodiment of the present application. Detailed implementation manners

[0038] In order to better understand the above technical solutions, exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although the exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure can be implemented in various forms and should not be limited by the embodiments set forth herein. On the contrary, these embodiments are provided so that the present disclosure can be more thoroughly understood and the scope of the present disclosure can be fully conveyed to those skilled in the art.

[0039] The payment and clearing method, device, system and electronic device proposed according to the embodiments of the present application will be described below with reference to the accompanying drawings.

[0040] Figure 1 Flow schematic diagram of a payment and clearing method disclosed in an embodiment of the present application. It should be noted that the payment and clearing method in this embodiment is a disaster recovery solution for the existing payment and clearing method, and the execution entity is the service layer.

[0041] As Figure 1 shown, taking the service layer as the execution entity, the payment and clearing method proposed in the embodiment of the present application will be explained, which specifically includes the following steps:

[0042] S101. Obtain the clearing results of the aggregated clearing data sent by each service layer entity to the transfer layer, where the aggregated clearing data includes the clearing data corresponding to each service layer entity.

[0043] In the embodiment of the present application, each service layer entity can perform clearing on the aggregated clearing data sent by the transfer layer and send the obtained clearing results to the service layer. Correspondingly, the service layer can obtain the clearing results of the aggregated clearing data sent by each service layer entity to the transfer layer.

[0044] Among them, the aggregated clearing data includes the clearing data corresponding to each service layer entity.

[0045] It should be noted that in this application, when each service layer entity attempts to send the settlement result of the aggregated settlement data obtained to the service layer, it can be sent according to a preset time or a preset time interval. Among them, this application does not limit the preset time and the preset time interval, and can be set according to the actual situation. For example, it can be set that each service layer entity sends the settlement result of the aggregated settlement data to the service layer at 8:00, 12:00, 15:00, and 21:00 every day; for another example, it can be set that each service layer entity sends the settlement result of the aggregated settlement data to the service layer with a preset time interval of 3 hours.

[0046] S103. Select one of the service layer entities as the target service layer entity.

[0047] In an embodiment of this application, one of the service layer entities can be randomly selected as the target service layer entity.

[0048] For example, there are a total of 10 service layer entities from service layer entity 1 to service layer entity 10. At this time, any service layer entity between service layer entity 1 and service layer entity 10 can be selected as the target service layer entity. For example, service layer entity 1, service layer entity 5, or service layer entity 9 can be selected as the target service layer entity.

[0049] S105. Control the target service layer entity to sign the aggregated settlement data, settlement result obtained from this settlement, and the previous signature data obtained from the previous settlement stored, and store the obtained current signature data.

[0050] In an embodiment of this application, in order to ensure the security during the data interaction process and avoid data information being tampered with, each service layer entity can first generate a key pair, including a private key and a public key. Then each service layer entity stores the private key locally and sends the public key to the transfer layer. Further, the target service layer entity can be controlled to use the private key stored locally to sign the aggregated settlement data, settlement result obtained from this settlement, and the previous signature data obtained from the previous settlement stored, and store the obtained current signature data.

[0051] Among them, signing means that the target service layer entity (information sender) uses its own private key to perform RSA algorithm (RSA Algorithm) operations on the aggregated settlement data, settlement result obtained from this settlement, and the previous signature data, so as to ensure that the target service layer entity cannot deny having sent this information (i.e., non-repudiation), and at the same time ensure that this information has not been tampered with after being signed (i.e., integrity). When the transfer layer (information receiver) receives this information, it can verify the signature through the public key received from the target service layer entity.

[0052] Further, the signature data of this time can be stored, that is, the summary liquidation data, liquidation result obtained through this signature, and the previous signature data obtained from the previous liquidation stored, and the signature data of this time is incorporated into the data to be signed next time to further ensure that the data in the delivery liquidation process is not tampered with.

[0053] S107. Control the main body of the target service layer to send the liquidation result and the signature data of this time obtained from this liquidation to the transfer layer.

[0054] In the embodiment of the present application, after the main body of the target service layer signs and stores the obtained signature data of this time, the main body of the target service layer can be controlled to send the liquidation result and the signature data of this time obtained from this liquidation to the transfer layer to request liquidation.

[0055] Optionally, after obtaining the liquidation result, the disaster recovery plan for payment liquidation can be switched to the normal payment liquidation method, and the liquidation result can be synchronized to continue the subsequent payment liquidation process.

[0056] The technical solutions in the above embodiments of the present application at least have the following technical effects or advantages:

[0057] Since the present application can, when the existing liquidation system fails and cannot operate normally, take the service layer as the execution main body, obtain the liquidation result, control the selected main body of the target service layer to sign the summary liquidation data, liquidation result obtained from this liquidation, and the previous signature data obtained from the previous liquidation stored, and store the signature data of this time, and then control the main body of the target service layer to send the liquidation result and the signature data of this time obtained from this liquidation to the transfer layer to implement payment liquidation, so that payment liquidation can be realized based on the payment liquidation method provided by the present application when the liquidation layer is unavailable, avoiding the technical problem that payment liquidation cannot be completed due to the unavailability of the liquidation layer, and ensuring the continuity, effectiveness and reliability in the payment liquidation process.

[0058] It should be noted that before attempting to obtain the liquidation results of the summary liquidation data sent by the transfer layer for each service layer main body, the main bodies of each service layer can also be controlled to obtain the liquidation results.

[0059] As a possible implementation manner, as Figure 2 shown, on the basis of the above embodiment, before step S101 of obtaining the liquidation results of the summary liquidation data sent by the transfer layer for each service layer main body, the process of obtaining the liquidation results specifically includes the following steps:

[0060] S201. Receive the summary liquidation data sent by the transfer layer.

[0061] In an embodiment of the present application, the transfer layer can summarize the payment results within the agreed time range to form the data to be cleared, and calculate the receivable or payable clearing data of each service layer entity as the summarized clearing data. Further, the transfer layer can send the summarized clearing data of each service layer entity to the service layer. Correspondingly, the service layer can receive the summarized clearing data sent by the transfer layer.

[0062] It should be noted that when the transfer layer attempts to send the summary settlement data of each service layer entity to the service layer, it can be sent at one time. In other words, during the payment settlement process, the transfer layer only needs to submit data once to complete the current settlement. Accordingly, the service layer can receive the summary settlement data at one time, which greatly simplifies the settlement logic, reduces the complexity of the interaction logic, and improves the timeliness of the payment settlement process.

[0063] S203: Distribute the aggregated settlement data to each service layer entity.

[0064] In an embodiment of the present application, after the service layer receives the summary settlement data sent by the switching layer, the summary settlement data can be distributed to each service layer subject, wherein the summary settlement data received by each service layer subject is synchronous.

[0065] It should be noted that in this application, the aggregated clearing data can be shared in clearing networks located in different geographical locations or composed of multiple institutions. In a clearing network, each service layer entity can obtain a unique and authentic aggregated clearing data. Any changes in the aggregated clearing data will be quickly and truthfully reflected in the aggregated clearing data received by each service layer entity, ensuring the transparency, openness and immutability of the aggregated clearing data.

[0066] S205. Control each service layer entity to perform liquidation on the aggregated liquidation data to obtain a liquidation result.

[0067] Among them, the liquidation result obtained by each service layer entity is the liquidation result of all service layer entities; the liquidation result may be the amount of the liquidation account.

[0068] In an embodiment of the present application, after the service layer distributes the aggregated settlement data to each service layer entity, each service layer entity can be controlled to settle the aggregated settlement data according to an agreed calculation method to obtain a settlement result.

[0069] It should be noted that in this application, when attempting to control each service layer entity to conduct liquidation, each service layer entity can conduct liquidation according to the digital-form agreed calculation method stored in its own storage area, and the liquidation result obtained through this agreed calculation method is reliable. The process of conducting liquidation is equivalent to the application of a smart contract. Each service layer entity, as a participant in the contract, conducts liquidation according to the promised calculation method.

[0070] Furthermore, after obtaining the liquidation result, the aggregated liquidation data and the liquidation result obtained from this liquidation can be stored.

[0071] It should be noted that in the aforementioned step S105, the service layer controls the target service layer entity to sign and stores the obtained signature data for this time. Thus, in this application, the aggregated liquidation data, the liquidation result, and the signature data for this time of the target service layer are stored at multiple points in the service layer to achieve the multi-point provision of liquidation services and the multi-point storage of account data.

[0072] The technical solutions in the embodiments of this application described above have at least the following technical effects or advantages: Through the disaster tolerance solution for payment liquidation constructed by this application, the normal operation of payment liquidation services can still be guaranteed when the original liquidation system cannot operate normally, ensuring the continuity, effectiveness, and reliability in the payment liquidation process.

[0073] It should be noted that when attempting to select one of the service layer entities as the target service layer entity, it is possible to first judge whether the liquidation results of each service layer entity are consistent, and determine the matching target service layer entity selection strategy according to the recognition result.

[0074] As a possible implementation method, as Figure 3 shown, on the basis of the above embodiment, in the above step S103, the process of selecting one of the service layer entities as the target service layer entity specifically includes the following steps:

[0075] S301. Judge whether the liquidation results of each service layer entity are consistent.

[0076] Optionally, the liquidation results of each service layer entity can be compared. If it is recognized that the liquidation results of each service layer entity are consistent, it indicates that the process of obtaining the liquidation results of each service layer entity is effective and reliable, and then step S303 can be executed.

[0077] S303. Select one of the service layer entities as the target service layer entity.

[0078] Optionally, one of the service layer entities can be randomly selected as the target service layer entity.

[0079] The technical solutions in the embodiments of the present application at least have the following technical effects or advantages:

[0080] Since the present application can judge whether the liquidation results of each service layer entity are consistent when attempting to select one of the service layer entities as the target service layer entity, and randomly select one of the service layer entities as the target service layer entity when it is recognized that the liquidation results of each service layer entity are consistent, it can confirm that the process of obtaining the liquidation results of each service layer entity is effective and reliable, further ensuring the continuity, effectiveness, and reliability in the payment and settlement process.

[0081] Figure 4 It is a schematic flowchart of the payment and settlement method disclosed in another embodiment of the present application. As Figure 4 shown, the process of payment and settlement is explained as follows, which specifically includes the following steps:

[0082] S401. Receive the payment request submitted by the customer layer.

[0083] Optionally, the customer layer can use an uninterrupted payment service to submit a payment request to the service layer. Correspondingly, the service layer can receive the payment request submitted by the customer layer.

[0084] Among them, the payment request can be any payment request of a customer with a payment need, such as a collection request, a payment request, etc.

[0085] S403. Forward the payment request to the transfer layer.

[0086] S405. Receive the processing result obtained by the transfer layer based on the feedback information of the service layer.

[0087] Optionally, the transfer layer accepts the payment request transferred by the service layer, forwards the payment request to the participating party (service layer) of this payment, and arbitrates the transaction result by integrating the feedback information of the participating party.

[0088] S407. Feedback the processing result to the customer layer.

[0089] Optionally, the service layer can feedback the processing result to the customer layer so that the customer can learn about the processing result.

[0090] In summary, the process of payment and settlement can be divided into the following two stages: the payment stage and the settlement stage. Optionally, in the payment stage, the customer layer can submit a payment request to the service layer. After receiving the request, the service layer can forward the request to the transfer layer. The transfer layer accepts the payment request and forwards it to the participating party (service layer) of this transaction, and arbitrates the transaction result by integrating the feedback opinions of the participating party. Further, the transfer layer can feedback the processing result to the service layer, and the service layer then feedbacks the processing result to the customer layer.

[0091] S409. Receive the summary settlement data sent by the transfer layer.

[0092] S411. Distribute the summary settlement data to the main bodies of each service layer.

[0093] S413. Control the main bodies of each service layer to settle the summary settlement data to obtain a settlement result.

[0094] S415. Obtain the settlement results of the main bodies of each service layer for the summary settlement data sent by the transfer layer, where the summary settlement data includes the settlement data corresponding to the main bodies of each service layer.

[0095] S417. Determine whether the settlement results of the main bodies of each service layer are consistent.

[0096] Optionally, when it is recognized that the settlement results of the main bodies of each service layer are consistent, step S421 can be executed.

[0097] S419. Randomly select one of the main bodies of each service layer as the target service layer main body.

[0098] S421. Control the target service layer main body to sign the summary settlement data, settlement result, and the previous signature data obtained from the previous settlement stored for the current settlement, and store the obtained current signature data.

[0099] S423. Control the target service layer main body to send the settlement result and the current signature data obtained from the current settlement to the transfer layer.

[0100] It should be noted that for the introduction of the settlement stage in steps S409 to S423, reference can be made to the relevant records in the above embodiments, which will not be elaborated here.

[0101] The technical solutions in the embodiments of the present application at least have the following technical effects or advantages: Through the disaster tolerance solution for payment settlement constructed by the present application, the normal operation of payment settlement services can still be guaranteed when the original settlement system fails to operate properly, ensuring the continuity, effectiveness, and reliability in the payment settlement process.

[0102] Based on the same inventive concept, the embodiments of the present application also provide a payment settlement device.

[0103] Figures 5 - 6 For the structural schematic diagram of the payment settlement device provided in the embodiments of the present application. As Figure 5 shown, the payment settlement device 100 includes: an acquisition module 11, a selection module 13, a first control module 15, and a second control module 17.

[0104] Among them, an acquisition module 11 is configured to acquire the settlement results of the summary settlement data sent by each service layer entity to the transfer layer, where the summary settlement data includes the settlement data corresponding to each service layer entity; a selection module 13 is configured to select one of each service layer entity as a target service layer entity; a first control module 15 is configured to control the target service layer entity to sign the summary settlement data, the settlement results obtained in this settlement, and the previous signature data obtained in the previous settlement stored, and store the obtained current signature data; a second control module 17 is configured to control the target service layer entity to send the settlement results and the current signature data obtained in this settlement to the transfer layer.

[0105] According to an embodiment of the present application, as Figure 6 shown, the payment settlement device 100 proposed by the present application further includes: a third control module 19, configured to: receive the summary settlement data sent by the transfer layer; distribute the summary settlement data to each service layer entity; control each service layer entity to settle the summary settlement data to obtain the settlement results.

[0106] According to an embodiment of the present application, Figure 6 the third control module 19 in

[0107] According to an embodiment of the present application, Figure 5 the first control module 15 in

[0108] According to an embodiment of the present application, Figure 5 the selection module 13 in

[0109] According to an embodiment of the present application, Figure 5 the selection module 13 in

[0110] Based on the same inventive concept, an embodiment of the present application further provides a payment settlement system.

[0111] Figure 7 is a schematic structural diagram of the payment settlement system provided by an embodiment of the present application. As Figure 7 shown, the payment settlement system 300 includes a transfer layer 31, a client layer 33, and a payment settlement device 100.

[0112] It should be noted that the payment and settlement system proposed in this application can be applied to various payment and settlement scenarios. Taking the retail payment and settlement scenario as an example below, the payment and settlement system proposed in this application will be explained.

[0113] As Figure 8 shown, the customer layer in the payment and settlement system 300 includes customers 1 to k with payment needs, such as the paying individuals and receiving merchants in the consumption scenario, the payers and payees in the transfer scenario, etc. Customers open their own accounts in the customer service systems 1 to j in the service layer and entrust the customer service systems to hold their funds. In the actual application of the payment and settlement scenario, customers can submit their payment requests to the customers in the customer layer through online, offline (counter), etc.

[0114] In the service layer, it mainly includes entities that provide account management and payment services to customers, such as commercial banks, third-party payment institutions, etc. The service layer accepts the payment requests of customers and provides real-time or near-real-time payment and settlement services to customers. Each entity in the service layer opens a settlement account and performs operations such as settlement, fund transfer, and account registration.

[0115] In the transfer layer, it mainly includes retail transfer entities. Facing the service layer, the transfer layer provides real-time or near-real-time information transfer services and arbitrates retail transaction results. Since the retail transfer systems 1 to i can directly accept retail transactions of each customer service system, the system needs to have the ability to support high concurrency. In addition, facing the service layer, the transfer layer aggregates transaction data within a specified time range and submits it to the service layer at a specified point in time for settlement by the service layer.

[0116] It should be noted that in the case where a similar Figure 9 payment and settlement system is unavailable, the solution proposed in this application is that the service layer simultaneously undertakes the functions of the service layer and the settlement layer in the existing payment and settlement system.

[0117] That is to say, in this application, by constructing a disaster tolerance solution for payment and settlement, it is possible to ensure the normal progress of payment and settlement services when the original settlement system cannot operate normally, not only avoiding the technical problem of being unable to complete payment and settlement due to the unavailability of the settlement layer, but also ensuring the continuity, effectiveness, and reliability in the payment and settlement process.

[0118] Based on the same inventive concept, the embodiment of this application also provides an electronic device.

[0119] Figure 10 It is a schematic structural diagram of the electronic device provided by the embodiment of this application. As Figure 10As shown, the electronic device 2000 includes a memory 210, a processor 220, and a computer program stored on the memory 210 and executable on the processor 220. When the processor executes the program, the foregoing payment and settlement method is implemented.

[0120] Those skilled in the art should understand that the embodiments of the present application can be provided as a method, a system, or a computer program product. Therefore, the present application can take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present application can take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0121] The present application is described with reference to the flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each flow and / or block in the flowchart and / or block diagram can be implemented by computer program instructions, and the combination of the flows and / or blocks in the flowchart and / or block diagram can also be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing devices to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing devices generate means for implementing the specified functions in one Figure 1 flow or multiple flows and / or blocks Figure 1 block or multiple blocks.

[0122] These computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer-readable memory generate a manufactured article including instruction means, and the instruction means implement the specified functions in one Figure 1 flow or multiple flows and / or blocks Figure 1 block or multiple blocks.

[0123] These computer program instructions can also be loaded onto a computer or other programmable data processing device, so that a series of operation steps are executed on the computer or other programmable device to generate a computer-implemented process. Therefore, the instructions executed on the computer or other programmable device provide steps for implementing the specified functions in one Figure 1 flow or multiple flows and / or blocks Figure 1 block or multiple blocks.

[0124] It should be noted that in the claims, any reference signs placed between parentheses shall not be construed as limiting the claim. The word "comprising" does not exclude the presence of elements or steps not listed in the claim. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. The present application can be implemented by means of hardware including several different elements and by means of a suitably programmed computer. In a unit claim listing several devices, several of these devices may be embodied by the same item of hardware. The use of the words first, second, and third, etc. does not denote any order. These words may be interpreted as names.

[0125] Although the preferred embodiments of the present application have been described, additional changes and modifications can be made by those skilled in the art once they learn the basic inventive concept. Therefore, the appended claims are intended to be construed to cover the preferred embodiments as well as all changes and modifications falling within the scope of the present application.

[0126] 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 invention. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalent technologies, the present application is also intended to include these modifications and variations.

Claims

1. A payment and settlement method, characterized in that, Including: Obtaining the settlement result of the summary settlement data sent by each service layer entity to the transfer layer, where the summary settlement data includes the settlement data corresponding to each service layer entity; Selecting one of each of the service layer entities as the target service layer entity; Controlling the target service layer entity to sign the summary settlement data, the settlement result obtained in this settlement, and the previous signature data obtained in the previous settlement stored, and storing the obtained current signature data; Controlling the target service layer entity to send the settlement result and the current signature data obtained in this settlement to the transfer layer.

2. The payment and settlement method according to claim 1, characterized in that, Before obtaining the settlement result of the summary settlement data sent by each service layer entity to the transfer layer, further including: Receiving the summary settlement data sent by the transfer layer; Distributing the summary settlement data to each service layer entity; Controlling each service layer entity to settle the summary settlement data to obtain the settlement result.

3. The payment and settlement method according to claim 1, characterized in that, Further including: Storing the summary settlement data and the settlement result obtained in this settlement.

4. The payment and settlement method according to claim 1, characterized in that, The controlling the target service layer entity to sign the summary settlement data, the settlement result obtained in this settlement, and the previous signature data obtained in the previous settlement stored includes: Controlling the target service layer entity to use its own private key to sign the summary settlement data, the settlement result obtained in this settlement, and the previous signature data.

5. The payment and settlement method according to claim 1, characterized in that, The selecting one of each of the service layer entities as the target service layer entity includes: If the settlement results of each service layer entity are the same, selecting one of each of the service layer entities as the target service layer entity.

6. The payment and settlement method according to claim 1, characterized in that, The selecting one of each of the service layer entities as the target service layer entity includes: Randomly selecting one of each of the service layer entities as the target service layer entity.

7. A payment and settlement device, characterized in that, Including: An obtaining module, configured to obtain the settlement result of the summary settlement data sent by each service layer entity to the transfer layer, where the summary settlement data includes the settlement data corresponding to each service layer entity; A selecting module, configured to select one of each of the service layer entities as the target service layer entity; A first control module, configured to control the target service layer entity to sign the summary settlement data, the settlement result obtained in this settlement, and the previous signature data obtained in the previous settlement stored, and store the obtained current signature data; A second control module, configured to control the target service layer entity to send the settlement result and the current signature data obtained in this settlement to the transfer layer.

8. A payment and settlement system, characterized in that, Including: A transfer layer, a customer layer, and the payment settlement device as claimed in claim 7.

9. An electronic device, characterized in that, Including: A memory, a processor, and a computer program stored on the memory and executable on the processor, where when the processor executes the program, the payment settlement method as claimed in any one of claims 1-6 is implemented.

10. A computer-readable storage medium, on which a computer program is stored, characterized in that, When the program is executed by the processor, the payment settlement method as claimed in any one of claims 1-6 is implemented.

Images