CN115271908A

CN115271908A - Method and device for realizing multi-party on-site transaction based on contract and electronic equipment

Info

Publication number: CN115271908A
Application number: CN202210770956.4A
Authority: CN
Inventors: 李静; 黄海明
Original assignee: Guangzhou Yuntong Shuda Technology Co ltd
Current assignee: Guangzhou Yuntong Shuda Technology Co ltd
Priority date: 2022-06-30
Filing date: 2022-06-30
Publication date: 2022-11-01

Abstract

The present disclosure relates to a method for realizing multi-party to point transaction based on contracts, which comprises: the method comprises the steps of obtaining transaction information aiming at a type of product among a plurality of transaction parties, inquiring contract information corresponding to the identification of each transaction party according to the identification of each transaction party in the transaction information, and verifying the contract information of each transaction party, so that the transaction safety can be ensured. When the verification is passed, the contract information and the transaction information of each transaction party are sent to the bank digital currency system, so that the bank digital currency system completes multiple transactions among a plurality of transaction parties through the digital wallet of each transaction party according to the contract information and the transaction information of each transaction party, and multiple transactions among a plurality of transaction parties can be realized for one product based on the contract signed among the transaction parties in the mode, so that the business requirements are met, convenience is brought to the transaction parties, and the experience of the transaction parties is improved.

Description

Method and device for realizing multi-party on-site transaction based on contract and electronic equipment

Technical Field

The disclosure relates to the field of transaction data processing, and in particular, to a method, an apparatus, an electronic device, and a computer-readable medium for implementing a multiparty point-to-point transaction based on a contract.

Background

With the rapid development of the internet, electronic payment is more and more favored by users, and brings convenience to the life of the users. For example, transactions such as payments, transfers, etc. may be made through electronic payment. In addition, digital currency payment that has emerged in recent years is also one type of electronic payment. At present, the transaction process of a product in a service platform by adopting a digital currency payment mode only comprises one point transaction, such as payment or transfer of C2C or C2B. However, since the transaction process for a product in the service platform involves multiple objects, e.g., a user, a merchant, a service platform, or a user, a service platform. If only one point-to-point transaction is involved in the transaction process, the service requirement cannot be met. In addition, a verification link is lacked in the transaction process, so that the transaction process has a safety problem.

The above information disclosed in this background section is only for enhancement of understanding of the background of the disclosure and therefore it may contain information that does not form the prior art that is already known to a person of ordinary skill in the art.

Disclosure of Invention

In view of the above, the present disclosure provides a method, an apparatus, an electronic device, and a computer-readable medium for implementing a multi-party to-point transaction based on a contract, which can implement multiple transactions among multiple transaction parties for a product based on a contract signed among the multiple transaction parties, thereby satisfying business requirements. In addition, in the transaction process, the contract information of the transaction party is verified, and the security of the transaction is guaranteed.

Additional features and advantages of the disclosure will be set forth in the detailed description which follows, or in part will be obvious from the description, or may be learned by practice of the disclosure.

According to an aspect of the present disclosure, a method for implementing a multi-party to point transaction based on a contract is provided, including: acquiring a transaction request, wherein the transaction request comprises transaction information aiming at a type of product among a plurality of transaction parties; inquiring contract information corresponding to the identification of each trading party according to the identification of each trading party in the trading information, wherein the contract information of each trading party is generated based on the signing information of each trading party for one type of product; and verifying contract information of each transaction party, and when the verification is passed, sending the contract information and the transaction information of each transaction party to a bank digital currency system, so that the bank digital currency system completes multiple transactions among a plurality of transaction parties through a digital wallet of each transaction party according to the contract information and the transaction information of each transaction party.

Optionally, before obtaining the transaction request, the method further comprises: acquiring signing information signed by a digital certificate in a digital wallet of each transaction party aiming at various types of products, wherein the signing information comprises identifications of the transaction parties having transaction relations aiming at various types of products, identifications of the digital wallet and transaction detail information among the transaction parties; and verifying the digital certificate of the digital wallet of each transaction party, and generating corresponding contract information based on the signing information of the digital certificate signature in the digital wallet of each transaction party when the verification is passed.

Optionally, the method further comprises: setting an expiration date for contract information of each transaction party; contract information for each counterparty is stored in a contract list according to the validity period.

Optionally, querying, according to the identifier of each transaction party in the transaction information, contract information corresponding to the identifier of each transaction party includes: judging whether each trading party identifier exists in the contract list or not; and if so, inquiring contract information corresponding to the identification of each trading party from the contract list based on the identification of each trading party.

Optionally, verifying the contract information of each transaction part, and when the verification is passed, sending the contract information of each transaction part and the transaction information to the bank digital currency system comprises: verifying whether the validity period in the contract information of each transaction party is invalid; and when the validity period in the contract information of each transaction party is not expired, transmitting the identification of the transaction party, the identification of the digital wallet and the transaction details in the contract to the bank digital currency system.

Optionally, the method further comprises: receiving a plurality of transaction results returned by the bank digital currency system; according to the identification of the transaction party in the transaction results, sending the corresponding transaction result to the transaction party; storing the plurality of transaction results in a transaction list.

According to an aspect of the present disclosure, there is provided an apparatus for implementing a multi-party to point transaction based on a contract, the apparatus comprising: the system comprises a first acquisition module, a second acquisition module and a third acquisition module, wherein the first acquisition module is used for acquiring a transaction request which comprises transaction information aiming at a type of product among a plurality of transaction parties; the inquiry module is used for inquiring contract information corresponding to the identification of each trading party according to the identification of each trading party in the trading information, and the contract information of each trading party is generated based on the signing information of each trading party for one type of product; and the verification module is used for verifying the contract information of each transaction party, and sending the contract information and the transaction information of each transaction party to the bank digital currency system when the verification is passed, so that the bank digital currency system completes multiple transactions among a plurality of transaction parties through the digital wallet of each transaction party according to the contract information and the transaction information of each transaction party.

Optionally, before obtaining the transaction request, the apparatus further comprises: the second acquisition module is used for acquiring signing information signed by the digital certificate in the digital wallet of each transaction party aiming at various products, wherein the signing information comprises the identification of the transaction party having transaction relation aiming at various products, the identification of the digital wallet and transaction detail information between the transaction parties; and the second verification module is used for verifying the digital certificate of the digital wallet of each transaction party, and generating corresponding contract information based on the signing information of the digital certificate signature in the digital wallet of each transaction party when the verification is passed.

Optionally, the apparatus further comprises: the setting module is used for setting an expiration date aiming at the contract information of each transaction party; the first storage module is used for storing the contract information of each trading party in a contract list according to the validity period.

Optionally, the query module is configured to: judging whether each trading party identifier exists in the contract list or not; and if so, inquiring contract information corresponding to the identification of each trading party from the contract list based on the identification of each trading party.

Optionally, the first authentication module is configured to: verifying whether the validity period in the contract information of each transaction party is invalid; when the validity period in the contract information of each transaction party is not expired, transmitting the identification of the transaction party, the identification of the digital wallet and the transaction details in the contract to the bank digital currency system.

Optionally, the apparatus further comprises: the receiving module is used for receiving a plurality of transaction results returned by the bank digital currency system; the sending module is used for sending the corresponding transaction result to the transaction party according to the identification of the transaction party in the transaction results; and the second storage module is used for storing the transaction results into a transaction list.

According to one aspect of the present disclosure, a contract-based multi-party to point transaction system is provided, wherein the transaction system comprises: a digital currency operation platform and a bank digital currency system; the digital currency operation platform is used for acquiring a transaction request, wherein the transaction request comprises transaction information aiming at a type of product among a plurality of transaction parties; inquiring contract information corresponding to the identification of each trading party according to the identification of each trading party in the trading information, wherein the contract information of each trading party is generated based on the signing information of each trading party for one type of products; verifying contract information of each transaction party, and sending the contract information and the transaction information of each transaction party to the bank digital currency system when the verification is passed; and the bank digital currency system is used for receiving contract information and the transaction information of each transaction party, verifying the digital wallets of the transaction parties, and completing multiple transactions among a plurality of transaction parties through the digital wallets of the transaction parties according to the transaction division proportion and the transaction information among the transaction parties in each contract when the verification is passed.

According to an aspect of the present disclosure, an electronic device is provided, the electronic device including: one or more processors; storage means for storing one or more programs; when executed by one or more processors, cause the one or more processors to implement a method as above.

According to an aspect of the disclosure, a computer-readable medium is proposed, on which a computer program is stored, which program, when being executed by a processor, carries out the method as above.

According to the contract-based multi-party-to-point transaction method, the contract-based multi-party-to-point transaction device, the electronic equipment and the computer readable medium, transaction information for one type of product among a plurality of transaction parties is obtained, contract information corresponding to the identification of each transaction party is inquired according to the identification of each transaction party in the transaction information, and the contract information of each transaction party is verified, so that the transaction safety can be ensured. When the verification is passed, the contract information and the transaction information of each transaction party are sent to the bank digital currency system, so that the bank digital currency system completes multiple transactions among a plurality of transaction parties through the digital wallet of each transaction party according to the contract information and the transaction information of each transaction party, and multiple transactions among a plurality of transaction parties can be realized for one product based on the contract signed among the transaction parties in the mode, so that the business requirements are met, convenience is brought to the transaction parties, and the experience of the transaction parties is improved.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.

Drawings

The above and other objects, features and advantages of the present disclosure will become more apparent by describing in detail exemplary embodiments thereof with reference to the attached drawings. The drawings described below are merely some embodiments of the present disclosure, and other drawings may be derived from those drawings by those of ordinary skill in the art without inventive effort.

FIG. 1A is a block diagram illustrating a contract-based implementation of a multi-party to point transaction system in accordance with an exemplary embodiment.

FIG. 1B is a diagram illustrating an application scenario for implementing a multi-party to point trading system based on contracts, according to an illustrative embodiment.

FIG. 1C is a schematic illustration of a trading partner contract generation shown in accordance with an exemplary embodiment.

FIG. 1D is a schematic diagram illustrating the use of a counterparty contract, according to an exemplary embodiment.

FIG. 2 is a flow diagram illustrating a method for implementing a multi-party to point transaction based on a contract, according to an exemplary embodiment.

FIG. 3 is a flow diagram illustrating a method for implementing a multi-party to point transaction based on a contract, according to another illustrative embodiment.

FIG. 4 is a flow diagram illustrating a method for implementing a multi-party to point transaction based on a contract, according to another illustrative embodiment.

FIG. 5 is a flowchart illustrating a method for implementing a multi-party to point transaction based on a contract, according to another illustrative embodiment.

FIG. 6 is a flowchart illustrating a method for implementing a multi-party to point transaction based on a contract, according to another illustrative embodiment.

FIG. 7 is a flowchart illustrating a method for implementing a multi-party to point transaction based on a contract, according to another illustrative embodiment.

FIG. 8 is a block diagram illustrating a contract-based implementation of a multi-party to point transaction device according to an exemplary embodiment.

FIG. 9 is a block diagram illustrating a contract-based implementation of a multi-party to point transaction device according to another exemplary embodiment.

FIG. 10 is a block diagram illustrating a contract-based implementation of a multi-party to point transaction device according to another illustrative embodiment.

FIG. 11 is a block diagram illustrating a contract-based implementation of a multi-party to point transaction device according to another illustrative embodiment.

FIG. 12 is a block diagram illustrating an electronic device in accordance with an example embodiment.

FIG. 13 is a block diagram illustrating a computer-readable medium in accordance with an example embodiment.

Detailed Description

Example embodiments will now be described more fully with reference to the accompanying drawings. Example embodiments may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of example embodiments to those skilled in the art. The same reference numerals denote the same or similar parts in the drawings, and thus, a repetitive description thereof will be omitted.

Furthermore, the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a thorough understanding of embodiments of the disclosure. One skilled in the relevant art will recognize, however, that the subject matter of the present disclosure can be practiced without one or more of the specific details, or with other methods, components, devices, steps, and so forth. In other instances, well-known methods, devices, implementations, or operations have not been shown or described in detail to avoid obscuring aspects of the disclosure.

The block diagrams shown in the figures are functional entities only and do not necessarily correspond to physically separate entities. I.e. these functional entities may be implemented in the form of software, or in one or more hardware modules or integrated circuits, or in different networks and/or processor means and/or microcontroller means.

The flow charts shown in the drawings are merely illustrative and do not necessarily include all of the contents and operations/steps, nor do they necessarily have to be performed in the order described. For example, some operations/steps may be decomposed, and some operations/steps may be combined or partially combined, so that the actual execution sequence may be changed according to the actual situation.

It will be understood that, although the terms first, second, third, etc. may be used herein to describe various components, these components should not be limited by these terms. These terms are used to distinguish one element from another. Thus, a first component discussed below could be termed a second component without departing from the teachings of the disclosed concepts. As used herein, the term "and/or" includes any and all combinations of one or more of the associated listed items.

It is to be understood by those skilled in the art that the drawings are merely schematic representations of exemplary embodiments, and that the blocks or processes shown in the drawings are not necessarily required to practice the present disclosure and are, therefore, not intended to limit the scope of the present disclosure.

As shown in fig. 1A, system architecture 100 may include a server 101 and a server 103, and a network 102. Network 102 is the medium used to provide communications links between server 101 and server 103. Network 102 may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others.

It should be understood that the number of networks and servers in fig. 1 is merely illustrative. There may be any number of networks and servers, as desired for an implementation. For example, server 101 and server 103 may be a server cluster composed of a plurality of servers, and the like.

A user may use server 101 to interact with server 103 over network 102 to receive or transmit information related to a transaction. In this embodiment, the server 101 may be a digital money operation platform, and the server 103 may be a bank digital money system. For example, the digital currency operating platform may receive signing information of a plurality of transaction parties for a type of product, generate contract information corresponding to each transaction party based on the signing information of the plurality of transaction parties for the type of product, then store the contract information corresponding to each transaction party, and send the contract information corresponding to each transaction party to a bank digital currency system, where the bank digital currency system verifies the contract information corresponding to each transaction party, and after the verification is passed, store the contract information corresponding to each transaction party.

In an embodiment of the present invention, the digital currency operation platform may be configured to obtain a transaction request, where the transaction request includes transaction information for a type of product among a plurality of transaction parties, and query, according to an identifier of each transaction party in the transaction information, contract information corresponding to the identifier of each transaction party, where the contract information of each transaction party is generated based on signing information of each transaction party for a type of product, and verifies the contract information of each transaction party, so as to ensure security of a transaction. And when the verification is passed, transmitting contract information of each transaction party and the transaction information to the bank digital currency system.

In an embodiment of the present invention, the bank digital currency system is configured to receive contract information and the transaction information of each transaction party, and verify a digital wallet of each transaction party, so as to further ensure security of the transaction. When the verification is passed, according to the transaction division proportion between transaction parties in each contract and the transaction information, multiple transactions among a plurality of transaction parties are completed through the digital wallets of the transaction parties, so that the business requirements are met, convenience is brought to the transaction parties, and the experience of the transaction parties is improved.

As shown in fig. 1B, the system 100 requires obtaining contract-related information from other trading parties when signing and using the contract. For example, when signing a contract, the server 101 (digital currency operation platform) needs to acquire signing information for a type of product corresponding thereto from other transaction parties (e.g., the user terminal 105, the service platform 106, and the merchant terminal 107) through the network 104. In addition, the server 101 (digital currency operation platform) belongs to a trading party in the trading process when signing a contract or using a contract. Specifically, in the transaction process for one type of product, the transaction parties are the user terminal 105, the service platform 106, the merchant terminal 107, and the server 101 (digital currency operation platform), respectively. The user terminal 105 is a payer, and the service platform 106, the merchant terminal 107, and the server 101 (digital currency operation platform) are respectively a payee.

Referring to FIG. 1C, signing a contract between multiple transaction parties may include the steps of:

s1: the user using the user terminal 105 can sign the transaction information of various types of products in the service platform 106 by using the digital certificate in the digital wallet of the user, obtain the signing information of the user terminal 105 for various types of products, and then send the signing information to the service platform 106. The signed information characterizes that the user using the user terminal 105 agrees to sign with the service platform 106 that payment can be made for various types of products at the time of payment according to the respective payee proportions in the signed information.

S3: the merchant terminal 107 used by the merchant can sign transaction information of various products in the service platform 106 by using a digital certificate in the digital wallet of the merchant, obtain signing information of various products by the merchant terminal 107, and then send the signing information to the service platform 106. The signing information characterizes the merchant's consent to use the merchant terminal 107 to sign with the service platform 106 that payment can be collected at each payee in the signing information for various types of products at the time of payment.

S5: the service platform 106 receives the signing information of the user terminal 105 for various types of products and the signing information of the merchant terminal 107 for various types of products, the service platform 106 can respectively sign the signing information of the user terminal 105 for various types of products and the signing information of the merchant terminal 107 for various types of products by using a digital certificate in a digital wallet to obtain the signing information of the service platform 106 for various types of products, the signing information represents service fees which the service platform 106 agrees to pay to the service platform 106 by the user terminal 105 for various types of products during payment, and the signing information can also represent a payment receiving proportion which the merchant terminal 107 agrees to set by the service platform 106 for various types of products. The service platform 106 can transmit the signing information of the user terminal 105, the service platform 106, and the merchant terminal 107 for various types of products to the server 101 (digital money operation platform).

S7: the server 101 (digital currency operation platform) receives the signing information of the user terminal 105, the service platform 106 and the merchant terminal 107 for various types of products, and generates contract information of the user terminal 105 and the service platform 106, contract information of the user terminal 105 and the merchant terminal 107 and contract information of the service platform 106 and the merchant terminal 107, respectively, based on the signing information of the user terminal 105, the service platform 106 and the merchant terminal 107 for various types of products. In addition, the digital money operation platform signs the signing information of the user terminal 105 for various types of products and the signing information of the merchant terminal 107 for various types of products by using the digital certificate of the digital wallet to obtain the signing information of the digital money operation platform, wherein the signing information indicates that the digital money operation platform agrees that the user terminal 105 can pay for various types of products according to the payment proportion in the signing information when paying, and also indicates that the digital money operation platform agrees that the merchant terminal 107 agrees to the collection proportion set for various types of products. Based on the signing information, the digital currency operation platform generates contract information of the user terminal 105 and the digital currency operation platform, and contract information of the merchant terminal 107 and the digital currency operation platform, respectively. And transmits the above-mentioned each contract information to the server 103 (bank digital money system).

S9: the server 101 (digital money operation platform) transmits the contract information to the server 103 (bank digital money system).

S11: the server 103 (bank digital currency system) receives the contract information, verifies the contract information, and stores the contract information.

S13: the server 103 (bank digital money system) transmits the verified contract information to the digital money operation platform.

S15: the server 101 (digital money operation platform) receives the validated contract information sent by the server 103 (bank digital money system) and stores the contract information.

S17: the server 101 (digital money operation platform) transmits information that is verified by the bank digital money system for each piece of contract information described above to the service platform 106.

S19: the service platform 106 receives information that the bank digital currency system verifies for each contract information described above, and sends the information to the merchant 107.

S21: the service platform 106 receives the information that the contract information passes the verification of the bank digital currency system, and sends the information to the user terminal 105.

Through the steps S1 to S21, contract information related to a plurality of transaction parties can be generated for any type of product in the service platform 106, so that the subsequent user side 101 can pay for other transaction parties according to the contract information, and multiple transactions for a product are realized.

Referring to FIG. 1D, signing a contract between multiple transaction parties may include the steps of:

s2: a user using the user terminal 101 can purchase a product on the service platform 106. When a user purchases a product, the user terminal 101 is used to send order information to the service platform 106, wherein the order information includes details of the product to be purchased by the user.

S4: when a user purchases a product at the service platform 106 using the user terminal 101, the service platform 106 may receive order information sent by the user terminal 101, and based on the order information, a trading request may be generated, which may be trading information for a type of product between multiple trading parties. The transaction information of one payer and the transaction information of at least two payees are contained in the transaction parties. In this step, the payer is the user side 101, and at least two payees are the service platform 106, the merchant side 107, and the server 1 (digital currency operation platform).

S6: the server 1 (digital money operation platform) receives a transaction request, inquires about contract information of each transaction party according to transaction information of a plurality of transaction parties in the transaction request, and then generates contract transfer transaction information of each transaction party based on the contract information of each transaction party.

S8: the server 1 (digital money operation platform) transmits the contract transfer transaction information of each transaction party to the service platform 106.

S10: service platform 106 receives contract transfer transaction information for each counterparty and forwards it to user side 101.

S12: the user terminal 101 receives contract transfer transaction information of each transaction party so that the user can know a specific amount paid to each receiver party and a ratio of the amount to the price of the purchased product. And then sends a payment request to the digital currency operation platform.

S14: the server 101 receives the payment request, and then transmits the payment request and contract information of each transaction party to the server 103 (bank digital money system).

S16: the server 103 (bank digital money system) receives the payment request and the contract information of each transaction party, and verifies the contract information of each transaction party.

S18 to S22: after the verification of the contract information of each transaction party is passed, the server 103 (the bank digital money system completes a plurality of transactions between a plurality of transaction parties by the digital wallets of each transaction party according to the transaction division ratio and the transaction information between the transaction parties in each contract, for example, pays a service fee to the digital wallet of the service platform 106 according to the transaction division ratio in the contract by the digital wallet of the user terminal 101. Pays a fee for a product to the digital wallet of the merchant terminal 107 according to the transaction division ratio in the contract by the digital wallet of the user terminal 101. Pays a service fee to the digital wallet of the server 1 (digital money operation platform) according to the transaction division ratio in the contract by the digital wallet of the user terminal 101.

S24: the server 103 (bank digital money system) returns a payment result including payment details of a plurality of transactions to the server 1 (digital money operation platform)

S26: the server 1 (digital money operation platform) receives the above payment result. And stores the payment result.

S28: the server 1 (digital money operation platform) returns the above payment result to the service platform 106.

S30: the service platform 106 receives the payment result and returns it to the user terminal 101 so that the user is informed of the details of the multiple payments.

Through the steps S2 to S30, multiple transactions among multiple transaction parties aiming at one type of product can be realized based on contracts signed among the transaction parties, so that the business requirements are met, convenience is brought to the transaction parties, and the experience of the transaction parties is improved.

FIG. 2 is a flow diagram illustrating a method for implementing a multi-party to point transaction based on a contract, according to an exemplary embodiment. In this implementation, the method may be applied to the above-described digital currency operating platform.

As shown in FIG. 2, the contract-based method for implementing multi-party to point transactions includes steps S210-S230.

In step S210, a transaction request is obtained, where the transaction request includes transaction information for a type of product between multiple transaction parties.

In step S220, according to the identifier of each transaction party in the transaction information, contract information corresponding to the identifier of each transaction party is queried, and the contract information of each transaction party is generated based on the signing information of each transaction party for a type of product.

In step S230, the contract information of each transaction part is verified, and when the verification is passed, the contract information and the transaction information of each transaction part are transmitted to the bank digital currency system, so that the bank digital currency system completes a plurality of transactions among a plurality of transaction parts through the digital wallets of each transaction part according to the contract information and the transaction information of each transaction part.

The method can acquire the transaction information of a type of product among a plurality of transaction parties, inquire contract information corresponding to the identification of each transaction party according to the identification of each transaction party in the transaction information, and verify the contract information of each transaction party, so that the transaction safety can be ensured. When the verification is passed, the contract information and the transaction information of each transaction party are sent to the bank digital currency system, so that the bank digital currency system completes multiple transactions among a plurality of transaction parties through the digital wallet of each transaction party according to the contract information and the transaction information of each transaction party, and multiple transactions among a plurality of transaction parties can be realized for one product based on the contract signed among the transaction parties in the mode, so that the business requirements are met, convenience is brought to the transaction parties, and the experience of the transaction parties is improved.

In one embodiment, the product may be a physical product or a virtual product. For example, a physical product may refer to a product generated by a manufacturing line. The virtual product may be an internet service product derived through internet technology.

In one embodiment, the transaction request may be transaction information between a plurality of transaction parties for a type of product. The transaction information of one payer and the transaction information of at least two payees are contained in the transaction parties. Referring to fig. 1D, the payer is a user terminal 101, and the at least two payees are a service platform 106, a merchant terminal 107, and a server 1 (digital currency operation platform).

In one embodiment, the transaction information of the payer may include, but is not limited to, payer id, product type, product cost, and the like.

In one embodiment, the transaction information of the payee may include, but is not limited to, id of each payee, and transaction relationship between each payee and payer for a product.

In one embodiment, according to the identifier of each transaction party in the transaction information, contract information corresponding to the identifier of each transaction party is queried. For example, according to the trading party id in the trading information, the contract information corresponding to the trading party id is inquired from a contract mapping table between the trading parties.

In one embodiment, the contract information may include, but is not limited to, transaction party id, digital wallet id of transaction party, transaction share ratio between transaction parties.

In one embodiment, the digital currency operating platform may verify the contract information after querying the contract information based on the counterparty id. For example, the digital currency operation platform may verify whether the contract information is valid, verify whether the identifier of the digital wallet of each transaction party in the contract information is revoked or is authentic, and the like, so that invalid contract information may be effectively prevented from being sent to the bank digital currency system, and further, the bank digital currency system may be prevented from conducting transactions based on the invalid contract information.

In one embodiment, after the bank digital currency system receives the contract information and the transaction information of each transaction party, the transaction between the transaction parties can be completed through the digital wallets of the transaction parties based on the contract information and the transaction information of the transaction parties. For example, when a payer initiates a payment request, the bank digital money system may pay various fees in the contract to the digital wallets of each payee through the digital wallets of the payer, for example, pay a service fee to the service platform 106, pay a product fee to a merchant, pay a service fee to the digital money operating platform, based on the transaction share ratio and the fee of the product in the contract information of each transaction party, and the digital wallet id of the payer and the digital wallet id of each payer in the contract information. In this way, multiple transactions among multiple transaction parties can be realized for one product based on the contracts signed among the multiple transaction parties, so that the business requirements are met, convenience is brought to the transaction parties, and the experience of the transaction parties is improved.

As shown in fig. 3, before the step S210, the method may further include a step S310 to a step S320.

In step S310, for various types of products, signing information signed by a digital certificate in a digital wallet of each transaction party is acquired, the signing information including an identification of the transaction party having a transaction relationship for the various types of products, an identification of the digital wallet, and transaction detail information between the transaction parties.

In step S320, the digital certificate of the digital wallet of each transaction party is verified, and when the verification is passed, corresponding contract information is generated based on the signing information of the digital certificate signature in the digital wallet of each transaction party.

The method can verify the digital certificate of the digital wallet of each transaction party, thus ensuring the validity of contracts and protecting the safety of information of the transaction parties. When the verification is passed, corresponding contract information is generated based on the signing information of the digital certificate signature in the digital wallet of each transaction party, and invalid contract information is effectively prevented from being generated.

In one embodiment, the signing information may be obtained by signing the transaction information about a product with a digital certificate of a respective digital wallet by each transaction party. For example, the signing information may include, but is not limited to, identification of the transaction parties that have a transaction relationship for various types of products, digital wallet identification, and transaction detail information between the transaction parties. Specific contract signing and generation may refer to steps S1-S21 of fig. 1C.

As shown in fig. 4, the method may further include steps S410 to S420.

In step S410, an expiration date is set for contract information of each transaction party.

In step S420, the contract information of each trading party is stored in the contract list according to the validity period.

The method can set the validity period aiming at the contract information of each trading party, and the contract information of each trading party is stored in the contract list according to the validity period, so that the newly generated contract is quickly stored in the contract list corresponding to the newly generated contract according to the duration of the validity period.

In one embodiment, the validity period of the contract information of each transaction party may be set according to actual business conditions.

In one embodiment, the digital currency operation platform can regularly monitor the validity period of each contract in the contract list, and can regularly delete the contract information exceeding the validity period, so that new storage space can be added, and the operation speed of the digital currency operation platform is increased.

As shown in fig. 5, the step S220 may specifically include steps S510 to S520.

In step S510, it is determined whether or not each trading party identifier exists in the contract list.

In step S520, contract information corresponding to the identification of each trading party, if any, is queried from the contract list based on the identification of each trading party.

The method can judge whether each trading party identification exists in the contract list, if so, based on the identification of each trading party, the contract information corresponding to the identification of each trading party is inquired from the contract list, so that the contract information of each trading party can be acquired quickly and conveniently.

FIG. 6 is a flowchart illustrating a method for implementing a multi-party to point transaction based on a contract, according to another exemplary embodiment.

As shown in fig. 6, the step S230 may specifically include steps S610 to S620.

In step S610, it is verified whether the validity period in the contract information of each transaction party is expired.

In step S620, when the validity period in the contract information of each transaction party is not expired, the identification of the transaction party in the contract, the digital wallet identification, and the transaction details are transmitted to the bank digital money system.

The method can verify whether the validity period in the contract information of each transaction party is invalid or not, so that invalid contract information can be effectively prevented from being sent to a bank digital currency system. When the validity period in the contract information of each transaction party is not invalid, the identification of the transaction party, the digital wallet identification and the transaction details in the contract are sent to the bank digital currency system, so that the bank digital currency system can be effectively prevented from conducting transaction based on invalid contract information.

In one embodiment, the digital currency operation platform can also verify whether the identification of the digital wallet of each transaction party in the contract information is cancelled or true, and the like, so that the authenticity of the contract can be further ensured.

As shown in fig. 7, the method may further include steps S710 to S730.

In step S710, a plurality of transaction results returned by the bank digital currency system are received.

In step S720, according to the identifier of the transaction party in the transaction results, the transaction result corresponding to the identifier is sent to the transaction party.

In step S730, the transaction results are stored in a transaction list.

The method can send the corresponding transaction result to the transaction party according to the identification of the transaction party in the transaction results, and store the transaction results into the transaction list, so that the service requirement is further met.

Those skilled in the art will appreciate that all or part of the steps implementing the above embodiments are implemented as computer programs executed by a CPU. When executed by the CPU, performs the functions defined by the above-described methods provided by the present disclosure. The program may be stored in a computer readable storage medium, which may be a read-only memory, a magnetic or optical disk, or the like.

Furthermore, it should be noted that the above-mentioned figures are only schematic illustrations of the processes involved in the methods according to exemplary embodiments of the disclosure, and are not intended to be limiting. It will be readily understood that the processes shown in the above figures are not intended to indicate or limit the chronological order of the processes. In addition, it is also readily understood that these processes may be performed, for example, synchronously or asynchronously in multiple modules.

The following are embodiments of the disclosed apparatus that may be used to perform embodiments of the disclosed methods. For details not disclosed in the embodiments of the apparatus of the present disclosure, refer to the embodiments of the method of the present disclosure.

FIG. 8 is a block diagram illustrating a contract-based implementation of a multi-party to point transaction device according to another illustrative embodiment.

As shown in fig. 8, the contract-based multi-party to point transaction apparatus 800 includes: a first acquisition module 801, a query module 802 and a verification module 803.

Specifically, the first obtaining module 801 is configured to obtain a transaction request, where the transaction request includes transaction information for a type of product between multiple transaction parties.

The query module 802 is configured to query, according to the identifier of each transaction party in the transaction information, contract information corresponding to the identifier of each transaction party, where the contract information of each transaction party is generated based on the signing information of each transaction party for one type of product.

And the verification module 803 is configured to verify contract information of each transaction party, and when the verification is passed, send the contract information and the transaction information of each transaction party to the bank digital currency system, so that the bank digital currency system completes multiple transactions among multiple transaction parties through the digital wallets of each transaction party according to the contract information and the transaction information of each transaction party.

The contract-based multi-party to point transaction device 800 can acquire transaction information for one type of product among a plurality of transaction parties, inquire contract information corresponding to the identification of each transaction party according to the identification of each transaction party in the transaction information, and verify the contract information of each transaction party, so that the transaction safety can be ensured. When the verification is passed, the contract information and the transaction information of each transaction party are sent to the bank digital currency system, so that the bank digital currency system completes multiple transactions among a plurality of transaction parties through the digital wallet of each transaction party according to the contract information and the transaction information of each transaction party, and multiple transactions among a plurality of transaction parties can be realized for one product based on the contract signed among the transaction parties in the mode, so that the business requirement is met, convenience is brought to the transaction parties, and the experience of the transaction parties is improved

According to an embodiment of the present invention, the contract-based multi-party to point transaction apparatus 800 may be used to implement the contract-based multi-party to point transaction method described in the embodiment of FIG. 2.

Optionally, the query module 802 is configured to: judging whether each trading party identifier exists in the contract list or not; and if so, inquiring contract information corresponding to the identification of each trading party from the contract list based on the identification of each trading party.

Optionally, the first verification module 803 is configured to: verifying whether the validity period in the contract information of each transaction party is invalid; and when the validity period in the contract information of each transaction party is not expired, transmitting the identification of the transaction party, the identification of the digital wallet and the transaction details in the contract to the bank digital currency system.

As shown in fig. 9, the contract-based multi-party to point transaction apparatus 800 may further include: a second acquisition module 804 and a second verification module 805.

Specifically, the second obtaining module 804 is configured to obtain, for various types of products, signing information signed by the digital certificate in the digital wallet of each transaction party, where the signing information includes an identifier of the transaction party having a transaction relationship with the various types of products, an identifier of the digital wallet, and transaction detail information between the transaction parties.

And a second verification module 805 configured to verify the digital certificate of the digital wallet of each transaction party, and generate corresponding contract information based on signing information of the digital certificate signature in the digital wallet of each transaction party when the verification is passed.

The contract-based multi-party to point transaction apparatus 800 can verify the digital certificate of the digital wallet of each transaction party, thus ensuring the validity of the contract and protecting the security of the information of the transaction parties. When the verification is passed, corresponding contract information is generated based on the signing information of the digital certificate signature in the digital wallet of each transaction party, and invalid contract information is effectively prevented from being generated.

According to an embodiment of the present invention, the contract-based multi-party to point transaction apparatus 800 may be used to implement the contract-based multi-party to point transaction method described in the embodiment of FIG. 3.

As shown in fig. 10, the contract-based multi-party to point transaction apparatus 800 may further include: a setup module 806 and a first storage module 807.

Specifically, the setting module 806 is configured to set an expiration date for contract information of each transaction party.

A first storage module 807 for storing the contract information of each transaction party in a contract list according to the validity period.

The contract-based multi-party to point transaction device 800 can set the effective period for the contract information of each transaction party, and store the contract information of each transaction party in the contract list according to the effective period, so that the newly generated contract is quickly stored in the contract list corresponding to the contract list according to the effective period.

According to an embodiment of the present invention, the contract-based multi-party to point transaction apparatus 800 may be used to implement the contract-based multi-party to point transaction method described in the embodiment of FIG. 4.

FIG. 11 is a block diagram illustrating a contract-based implementation of a multi-party to point transaction device according to another exemplary embodiment.

As shown in fig. 11, the contract-based multi-party to point transaction apparatus 800 may further include: a receiving module 808, a sending module 809, and a second storing module 810.

In particular, the receiving module 808 is configured to receive a plurality of transaction results returned by the bank digital currency system.

The sending module 809 is configured to send the transaction result corresponding to the identifier of the transaction party in the multiple transaction results to the transaction party.

A second storing module 810, configured to store the transaction results into a transaction list.

The contract-based multi-party to point transaction apparatus 800 may send the transaction result corresponding to the identifier of the transaction party in the transaction results to the transaction party, and store the transaction results in the transaction list, so as to further satisfy the business requirement, for example, the transaction parties may approve based on the transaction result to ensure the accuracy of each transaction.

According to an embodiment of the present invention, the contract-based multi-party to point transaction apparatus 800 may be used to implement the contract-based multi-party to point transaction method described in the embodiment of FIG. 7.

An electronic device 900 according to this embodiment of the disclosure is described below with reference to fig. 12. The electronic device 900 shown in fig. 12 is only an example and should not bring any limitations to the functionality or scope of use of the embodiments of the present disclosure.

As shown in fig. 12, the electronic device 900 is embodied in the form of a general purpose computing device. Components of electronic device 900 may include, but are not limited to: at least one processing unit 910, at least one storage unit 920, a bus 930 that couples various system components including the storage unit 920 and the processing unit 910, a display unit 940, and the like.

Wherein the storage unit stores program code that can be executed by the processing unit 910 to cause the processing unit 910 to perform the steps according to various exemplary embodiments of the present disclosure in the specification. For example, the processing unit 910 may perform the steps as shown in fig. 2 to 7.

The storage unit 920 may include a readable medium in the form of a volatile storage unit, such as a random access storage unit (RAM) 9201 and/or a cache storage unit 9202, and may further include a read only storage unit (ROM) 9203.

The memory unit 920 may also include a program/utility 9204 having a set (at least one) of program modules 9205, such program modules 9205 including but not limited to: an operating system, one or more application programs, other program modules, and program data, each of which, or some combination thereof, may comprise an implementation of a network environment.

Bus 930 can be any type representing one or more of several types of bus structures, including a memory unit bus or memory unit controller, a peripheral bus, an accelerated graphics port, a processing unit, or a local bus using any of a variety of bus architectures.

The electronic device 900 can also communicate with one or more external devices 900 (e.g., keyboard, pointing device, bluetooth device, etc.), such that a user can communicate with the devices with which the electronic device 900 interacts, and/or any device (e.g., router, modem, etc.) with which the electronic device 900 can communicate with one or more other computing devices. Such communication may occur via input/output (I/O) interface 950. Also, the electronic device 900 may communicate with one or more networks (e.g., a Local Area Network (LAN), a Wide Area Network (WAN) and/or a public network, such as the Internet) via the network adapter 960. The network adapter 960 may communicate with other modules of the electronic device 900 via the bus 930. It should be appreciated that although not shown, other hardware and/or software modules may be used in conjunction with the electronic device 900, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, among others.

Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein may be implemented by software, and may also be implemented by software in combination with necessary hardware. Therefore, as shown in fig. 13, the technical solution according to the embodiment of the present disclosure may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (which may be a CD-ROM, a usb disk, a removable hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which may be a personal computer, a server, or a network device, etc.) to execute the above method according to the embodiment of the present disclosure.

The software product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium include: an electrical connection having one or more wires, a portable diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

The computer readable storage medium may include a propagated data signal with readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A readable storage medium may also be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a readable storage medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

Program code for carrying out operations of the present disclosure may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device and partly on a remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., through the internet using an internet service provider).

The computer readable medium carries one or more programs which, when executed by a device, cause the computer readable medium to perform the functions of: acquiring a transaction request, wherein the transaction request comprises transaction information of a plurality of transaction parties for a type of product; inquiring contract information corresponding to the identification of each trading party according to the identification of each trading party in the trading information, wherein the contract information of each trading party is generated based on the signing information of each trading party for one type of product; and verifying contract information of each transaction party, and when the verification is passed, sending the contract information and the transaction information of each transaction party to a bank digital currency system, so that the bank digital currency system completes multiple transactions among a plurality of transaction parties through a digital wallet of each transaction party according to the contract information and the transaction information of each transaction party.

Those skilled in the art will appreciate that the modules described above may be distributed in the apparatus according to the description of the embodiments, or may be modified accordingly in one or more apparatuses unique from the embodiments. The modules of the above embodiments may be combined into one module, or further split into multiple sub-modules.

Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein may be implemented by software, or by software in combination with necessary hardware. Therefore, the technical solution according to the embodiments of the present disclosure may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (which may be a CD-ROM, a usb disk, a removable hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which may be a personal computer, a server, a mobile terminal, or a network device, etc.) to execute the method according to the embodiments of the present disclosure.

Exemplary embodiments of the present disclosure are specifically illustrated and described above. It is to be understood that the present disclosure is not limited to the precise arrangements, instrumentalities, or instrumentalities described herein; on the contrary, the disclosure is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims.

Claims

1. A method for implementing a multi-party to point transaction based on a contract, the method comprising:

acquiring a transaction request, wherein the transaction request comprises transaction information aiming at a type of product among a plurality of transaction parties;

inquiring contract information corresponding to the identification of each trading party according to the identification of each trading party in the trading information, wherein the contract information of each trading party is generated based on the signing information of each trading party for one type of product;

and verifying the contract information of each transaction party, and when the verification is passed, sending the contract information and the transaction information of each transaction party to a bank digital currency system, so that the bank digital currency system completes multiple transactions among a plurality of transaction parties through the digital wallets of each transaction party according to the contract information and the transaction information of each transaction party.

2. A contract-based method of implementing a multi-party to point transaction according to claim 1, wherein prior to obtaining the transaction request, the method further comprises:

acquiring signing information signed by a digital certificate in a digital wallet of each transaction party aiming at various types of products, wherein the signing information comprises identification of the transaction parties having transaction relations aiming at various types of products, identification of the digital wallet and transaction detail information among the transaction parties;

and verifying the digital certificate of the digital wallet of each transaction party, and generating corresponding contract information based on the signing information of the digital certificate signature in the digital wallet of each transaction party when the verification is passed.

3. A method for contract-based implementation of a multi-party to point transaction according to claim 2, the method further comprising:

setting an expiry date aiming at contract information of each transaction party;

the contract information of each transaction party is stored in a contract list according to the validity period.

4. A method for implementing multi-party to point transactions according to claim 1, wherein querying the contract information corresponding to the identity of each trading party according to the identity of each trading party in the transaction information comprises:

judging whether each trading party identifier exists in the contract list or not;

and if so, inquiring contract information corresponding to the identification of each trading party from the contract list based on the identification of each trading party.

5. A method of effecting a multi-party to point transaction based on a contract as claimed in claim 1 wherein verifying contract information of each transaction party and, when the verification is passed, sending the contract information and the transaction information of each transaction party to a bank digital currency system comprises:

verifying whether the validity period in the contract information of each transaction party is invalid;

when the validity period in the contract information of each transaction party is not expired, transmitting the identification of the transaction party, the identification of the digital wallet and the transaction details in the contract to the bank digital currency system.

6. A method for contract-based implementation of a multi-party to point transaction as recited in claim 1, the method further comprising:

receiving a plurality of transaction results returned by the bank digital currency system;

according to the identification of the transaction party in the transaction results, sending the corresponding transaction result to the transaction party;

storing the plurality of transaction results in a transaction list.

7. An apparatus for implementing a multi-party to point transaction based on a contract, the apparatus comprising:

the system comprises a first acquisition module, a second acquisition module and a third acquisition module, wherein the first acquisition module is used for acquiring a transaction request which comprises transaction information aiming at a type of product among a plurality of transaction parties;

the inquiry module is used for inquiring contract information corresponding to the identification of each trading party according to the identification of each trading party in the trading information, and the contract information of each trading party is generated on the basis of the signing information of each trading party for one type of products;

the first verification module is used for verifying contract information of each transaction party, and when the contract information and the transaction information of each transaction party pass the verification, the contract information and the transaction information of each transaction party are sent to the bank digital currency system, so that the bank digital currency system completes multiple transactions among multiple transaction parties through the digital wallets of each transaction party according to the contract information and the transaction information of each transaction party.

8. A contract-based multi-party to point trading system, the trading system comprising: a digital currency operation platform and a bank digital currency system;

the digital currency operation platform is used for acquiring a transaction request, wherein the transaction request comprises transaction information aiming at a type of product among a plurality of transaction parties; inquiring contract information corresponding to the identification of each trading party according to the identification of each trading party in the trading information, wherein the contract information of each trading party is generated based on the signing information of each trading party for one type of product; the contract information of each transaction party is verified, and when the contract information and the transaction information of each transaction party pass the verification, the contract information and the transaction information of each transaction party are sent to the bank digital currency system;

and the bank digital currency system is used for receiving contract information and the transaction information of each transaction party, verifying the digital wallets of the transaction parties, and completing multiple transactions among a plurality of transaction parties through the digital wallets of the transaction parties according to the transaction division proportion and the transaction information among the transaction parties in each contract when the verification is passed.

9. An electronic device, comprising:

one or more processors;

storage means for storing one or more programs;

the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the method recited in any of claims 1-67.

10. A computer-readable medium, on which a computer program is stored, which, when being executed by a processor, carries out the method according to any one of claims 1-6.