Managing blockchain-based trusted transaction services

Abstract

Disclosed herein are methods, systems, and apparatus, including computer programs encoded on computer storage media, for managing a blockchain-based trusted transaction service. One of the methods includes storing order data for an order between a buyer and a seller on a blockchain of a blockchain network, the order data including one or more payment conditions and data for a trusted underwriting (TU) service, generating a trusted underwriting instrument for the order based on the order data, storing the trusted underwriting instrument on the blockchain, and transmitting the trusted underwriting instrument to a seller financial institution to determine whether to approve a financing request of the seller based on the trusted underwriting instrument. The trusted underwriting service is guaranteed by a buyer financial institution that automatically makes a payment based on credit of the buyer in response to conditions specified in a smart contract deployed on the blockchain being satisfied.

Description

Technical Field

[0001] This article relates to the management of trusted transaction services based on blockchain technology. Background Technology

[0002] Distributed ledger systems (DLS), also known as consensus networks and / or blockchain networks, enable participating entities to store data securely and immutably. Without referencing any specific use case, distributed ledger systems are generally referred to as blockchain networks. Examples of blockchain network types can include public blockchain networks, private blockchain networks, and consortium blockchain networks. Consortium blockchain networks are provided for a selected group of entities that control the consensus process, and these networks include an access control layer.

[0003] Digital networks enable people around the world to easily and efficiently find information and communicate with each other, which has also driven the booming development of trade, including international trade and cross-border trade. However, in traditional transactions, the parties often lack mutual trust, especially in international or cross-border transactions where the parties are geographically distant and have little prior trading history. Although the parties may agree on transaction terms such as payment terms in contracts or orders, it is difficult to ensure that these terms are met. For example, payment is often controlled by the buyer. Even if the buyer agrees to pay the seller, the timing of payment remains under the buyer's control. Whether the buyer has made payment is opaque or not immediately available to the seller, especially when the payment involves international or cross-border remittances between financial institutions in different countries or regions. In some cases, the seller can only confirm that the buyer has paid after actually receiving the payment. Before that, the seller may have to manually or even repeatedly request payment or payment status. In some cases, trust and reliable services have been implemented based on escrow systems provided by the trading platforms of the trading parties. However, these implementations require the trading parties to open escrow accounts on the escrow system and cannot use their own financial accounts in their own financial institutions, which may lead to a lack of trust and security. The trading platform, acting as a guarantor for the escrow account, also bears significant risks.

[0004] Furthermore, despite having trade orders and payment commitments from buyers, sellers are unable to use these trade orders to obtain financing from financial institutions because of a lack of reliable technology to enable financial institutions to verify the authenticity of the trade orders.

[0005] Therefore, there is a desire to develop new digital trust technologies and systems that can establish trust and provide trusted transaction services to multiple participants, including trading parties and financial institutions, for example, in international or cross-border trade. Summary of the Invention

[0006] Implementations of the described subject matter may include one or more features, individually or in combination.

[0007] For example, in one embodiment, a system for managing blockchain-based trusted transaction services includes: a blockchain network of multiple trusted nodes, comprising: a trade platform node corresponding to a trade platform for providing blockchain-based trusted trade services between a buyer and a seller, wherein the buyer is verified to have a trusted automatic payment service guaranteed by a buyer's financial institution, and the buyer's financial institution automatically makes payment on behalf of the buyer in response to the satisfaction of conditions specified in a smart contract deployed on a blockchain of the blockchain network; and a buyer's financial institution node corresponding to the buyer's financial institution. The trade platform node is configured to: after the buyer and the seller confirm an order on the trade platform, store the order data of the order on a corresponding blockchain of the blockchain network for the order, the order data including one or more payment conditions for the order; and generate a corresponding smart contract for the order based on the order data, wherein the corresponding smart contract includes an automatic function that, in response to determining that the corresponding payment conditions for the order payment are satisfied, automatically instructs the buyer's financial institution to make order payment to the seller for the order. The buyer's financial institution node is configured to communicate with the buyer's financial institution's computing device to verify that the buyer has a trusted automatic payment service guaranteed by the buyer's financial institution, and to execute the corresponding smart contract, wherein executing the corresponding smart contract includes automatically instructing the buyer's financial institution's computing device to make order payment to the seller in response to determining that the corresponding payment conditions for the order payment are met.

[0008] In some embodiments, one or more of these general and specific embodiments may be implemented using a device, system, method, or computer-readable medium, or any combination of a device, system, method, and computer-readable medium. The foregoing and other described embodiments may each optionally include one or more of the following embodiments:

[0009] In some embodiments, the buyer financial institution node is configured to: receive order payment data confirming that the buyer financial institution has made order payment to the seller; and store the order payment data on the corresponding blockchain.

[0010] In some embodiments, the trading platform is configured to: receive the order payment data from the corresponding blockchain; and provide feedback on the payment status to the buyer and the seller based on the order payment data.

[0011] In some embodiments, the buyer financial institution node is configured to: in response to determining that a predetermined time has been reached or a predetermined time period has elapsed after the corresponding payment conditions for the order payment have been met, execute the corresponding smart contract to automatically instruct the buyer financial institution's computing device to make order payment to the seller.

[0012] In some embodiments, the buyer financial institution node is configured to: in response to determining that the corresponding payment conditions for the order payment are met, execute the corresponding smart contract to generate an automatic payment command; and send the automatic payment command to the computing device of the buyer financial institution, the automatic payment command instructing the computing device of the buyer financial institution to make order payment to the seller in accordance with the trusted automatic payment service.

[0013] In some embodiments, the buyer's financial institution node is configured to store the order payment data on the corresponding blockchain, which confirms that the buyer's financial institution has made order payment to the seller.

[0014] In some embodiments, the buyer has a buyer financial account in the buyer's financial institution, the seller has a seller financial account in the seller's financial institution, and the buyer's financial institution node is configured to execute the corresponding smart contract in response to determining that the corresponding payment conditions for the order payment are met, to automatically instruct the computing device of the buyer's financial institution to make the order payment directly to the seller's financial account in the seller's financial institution without going through the trading platform.

[0015] In some embodiments, the blockchain network of the plurality of trusted nodes further includes a seller financial institution node corresponding to the seller financial institution.

[0016] In some embodiments, one of the buyer financial institution and the seller financial institution is an offshore entity, and the other is an onshore entity. The offshore entity and the onshore entity are subject to different financial regulations, and the buyer financial institution node corresponding to the buyer financial institution and the seller financial institution node corresponding to the seller financial institution belong to the same blockchain network of the plurality of trusted nodes.

[0017] In some embodiments, the buyer financial institution node is configured to transfer the digital value corresponding to the order payment to the seller financial institution node in response to the automatic payment command.

[0018] In some embodiments, the seller financial institution node is configured to store payment receipt data on the corresponding blockchain, the payment receipt data confirming that the seller financial account in the seller financial institution has received the order payment for the order from the buyer financial institution.

[0019] In some embodiments, the trade platform node is configured to communicate with the buyer financial institution node after the buyer logs into the buyer trade account on the trade platform to verify whether the buyer's buyer financial account in the buyer financial institution is eligible for the trusted automatic payment service on the trade platform, wherein the buyer trade account includes information about the buyer financial account.

[0020] In some embodiments, the trading platform is configured to allow the buyer to draft or view orders on the trading platform in response to determining that the buyer's financial account is eligible for the trusted automatic payment service.

[0021] In some embodiments, the corresponding smart contract further includes: an order status update function that automatically updates the order status in response to determining, based on order status data uploaded to the corresponding blockchain, that the order status has been changed.

[0022] In some embodiments, the order status data includes at least one of logistics data, supply chain data, customs data, bill of lading data, or payment data.

[0023] In some embodiments, the status of the order indicates at least one of the following: the product associated with the order has been prepared or shipped by the seller; the product has been inspected by customs; the product is being transported by at least one logistics provider; the bill of lading associated with the order has been submitted by the seller on a trading platform; the submitted bill of lading has been confirmed by the buyer on the trading platform; the invoice associated with the order has been generated by the blockchain network; the generated invoice has been confirmed by the buyer; the buyer and the seller have reached a consensus on the order; the buyer's financial institution has made the automatic payment; the seller's financial institution has received the automatic payment; or the buyer has received the product.

[0024] In some embodiments, the blockchain network of the plurality of trusted nodes further includes at least one of the following: a customs node corresponding to the customs, wherein the order status data includes customs data uploaded by the customs node to the corresponding blockchain; or a logistics provider node corresponding to the at least one logistics provider, wherein the order status data includes logistics data uploaded by the logistics provider node to the corresponding blockchain.

[0025] In some embodiments, one or more payment conditions include a first payment condition for a first payment of the order and a second payment condition for a second payment of the order. The buyer financial institution node is configured to: in response to determining that the first payment condition for the first payment is satisfied, execute the corresponding smart contract to automatically instruct the buyer financial institution's computing device to make the first payment to the seller; and in response to determining that the second payment condition for the second payment is satisfied, execute the corresponding smart contract to automatically instruct the buyer financial institution's computing device to make the second payment to the seller.

[0026] In some embodiments, the first payment is an advance payment for the order, and the first payment condition includes that the order has been verified on the trading platform; the second payment is the final payment for the order, and the second payment condition includes at least one of the following: the bill of lading associated with the order has been submitted by the seller on the trading platform; the submitted bill of lading has been confirmed by the buyer on the trading platform; the invoice associated with the order has been generated by the blockchain network; the generated invoice has been confirmed by the buyer; or the buyer and the seller have reached a consensus on the order.

[0027] In some embodiments, the system includes the trading platform.

[0028] In some embodiments, the trade platform node is configured to generate a corresponding smart contract for the order based on the order data according to a smart contract template. The smart contract template includes multiple functions for trusted trade services. When generating the corresponding smart contract for the order, the trade platform node is configured to call one or more functions in the smart contract template and use the order data as input to one or more functions in the smart contract template.

[0029] For example, in another embodiment, a system for managing blockchain-based trusted transaction services includes: a blockchain network of multiple trusted nodes, comprising: a trade platform node corresponding to a trade platform for providing blockchain-based trusted trade services between a buyer and a seller, wherein the buyer is verified to have a trusted undertaking (TU) service guaranteed by the buyer's financial institution, and in response to the satisfaction of conditions specified in a smart contract deployed on the blockchain network, the buyer's financial institution automatically makes payment to the seller for the buyer based on the buyer's credit with the buyer's financial institution; and a buyer financial institution node corresponding to the buyer's financial institution. The trade platform node is configured to: after the buyer and the seller confirm an order on the trade platform, store the order data on the blockchain network of the order on the corresponding blockchain of the order, the order data including one or more payment conditions of the order and trusted undertaking service data representing the corresponding trusted undertaking service of the order, and generate a corresponding smart contract for the order based on the order data, wherein the corresponding smart contract includes an automatic function that, in response to determining that the corresponding payment conditions for the order payment are satisfied, automatically instructs the buyer's financial institution to make order payment to the seller for the order. The buyer's financial institution node is configured to: communicate with the buyer's financial institution's computing device to verify that the buyer has the corresponding trusted credit service guaranteed by the buyer's financial institution for the order, and to execute the corresponding smart contract, wherein executing the corresponding smart contract includes automatically instructing the buyer's financial institution's computing device to make the order payment to the seller in response to determining that the corresponding payment conditions for the order payment have been met.

[0030] In some embodiments, one or more of these general and specific embodiments may be implemented using a device, system, method, or computer-readable medium, or any combination of a device, system, method, and computer-readable medium. The foregoing and other described embodiments may each optionally include one or more of the following embodiments:

[0031] In some embodiments, the buyer financial institution node is configured to: receive order payment data confirming that the buyer financial institution has successfully made order payment to the seller based on the trusted credit service for the order; and store the order payment data on the blockchain.

[0032] In some embodiments, the blockchain network of the plurality of trusted nodes further includes a seller financial institution node corresponding to the seller financial institution. The seller has a seller financial account in the seller financial institution, and the seller financial institution node is configured to store the payment receipt data on the corresponding blockchain, the payment receipt data confirming that the seller financial account in the seller financial institution has received order payment for the order from the buyer financial institution.

[0033] In some embodiments, the trade platform node is configured to: determine, based on the trusted credit service data, that the buyer has chosen to use the corresponding trusted credit service for the order on the trade platform, and send a request to the computing device of the buyer financial institution through the buyer financial institution node, the request requesting the buyer financial institution to verify whether the buyer is eligible for the corresponding trusted credit service for the order guaranteed by the buyer financial institution.

[0034] In some embodiments, the trading platform is configured to provide a user interface for receiving user input of the order data, and the user interface includes the selection of a corresponding trusted credit service using the order.

[0035] In some embodiments, the buyer financial institution node is configured to: receive verification data from the buyer financial institution's computing device, the verification data confirming that the buyer has a corresponding trusted credit service guaranteed by the buyer financial institution for the order, and to store the verification data on the corresponding blockchain.

[0036] In some embodiments, the trading platform is configured to: determine, based on verification data stored on the corresponding blockchain, that the buyer has a corresponding trusted credit service for the order guaranteed by the buyer's financial institution, and verify the order after determining that the buyer has a corresponding trusted credit service for the order guaranteed by the buyer's financial institution.

[0037] In some embodiments, the trading platform node is configured to send a request after storing the order data of the order on the corresponding blockchain.

[0038] In some embodiments, the payment terms for the order are determined based on the corresponding trusted credit service for that order.

[0039] In some embodiments, the buyer financial institution node is configured to execute the corresponding smart contract in response to determining that a predetermined time has elapsed or a predetermined period has elapsed after the corresponding payment conditions for the order payment have been met, so as to automatically instruct the computing device of the buyer financial institution to make order payment to the seller in accordance with the corresponding trusted credit service for the order.

[0040] In some embodiments, the scheduled time or scheduled time period is determined based on the corresponding trusted credit service of the order.

[0041] In some embodiments, the one or more payment conditions include a first payment condition for a first payment of the order and a second payment condition for a second payment of the order. The second payment is an order payment made according to the corresponding trusted credit service, and the second payment condition includes the corresponding payment terms. The buyer financial institution node is configured to: in response to determining that the second payment condition for the second payment is met, execute the corresponding smart contract to automatically instruct the buyer financial institution's computing device to make the second payment to the seller according to the corresponding trusted credit service for the order.

[0042] In some embodiments, the buyer financial institution node is configured to: in response to determining that a first payment condition for the first payment is met, execute the corresponding smart contract to automatically instruct the buyer financial institution's computing device to make the first payment to the seller based on the buyer's trusted automatic payment service provided by the buyer financial institution.

[0043] In some embodiments, the trade platform node is configured to: after the buyer logs into the buyer trade account on the trade platform, communicate with the computing device of the buyer financial institution through the buyer financial institution node to verify whether the buyer's buyer financial account in the buyer financial institution is eligible for trusted automatic payment services, wherein the buyer trade account includes information of the buyer financial account.

[0044] In some embodiments, the first payment is a prepayment for the order, and the first payment condition includes verification of the order. The second payment is the final payment for the order, and the second payment condition may include at least one of the following: the bill of lading associated with the order has been submitted by the seller on the trading platform; the submitted bill of lading has been confirmed by the buyer on the trading platform; the invoice associated with the order has been generated by the blockchain network; the generated invoice has been confirmed by the buyer; or the buyer and the seller have reached a consensus on the order.

[0045] In some embodiments, the corresponding smart contract further includes an order status update function that automatically updates the order status in response to determining that the order status has been changed based on order status data uploaded to the corresponding blockchain.

[0046] In some embodiments, the status of the order indicates at least one of the following: the product associated with the order has been prepared or shipped by the seller; the product has been inspected by customs; the product is being transported by at least one logistics provider; the bill of lading associated with the order has been submitted by the seller on the trading platform; the submitted bill of lading has been confirmed by the buyer on the trading platform; the invoice associated with the order has been generated by the blockchain network; the generated invoice has been confirmed by the buyer; the buyer and the seller have reached a consensus on the order; the buyer's financial institution has made the automatic payment; the seller's financial institution has received the automatic payment; or the buyer has received the product.

[0047] In some embodiments, the blockchain network of the plurality of trusted nodes further includes at least one of the following: a customs node corresponding to the customs, wherein the order status data includes customs data uploaded by the customs node to the corresponding blockchain; or a logistics provider node corresponding to the at least one logistics provider, wherein the order status data includes logistics data uploaded by the logistics provider node to the corresponding blockchain.

[0048] In some embodiments, the order status data includes at least one of logistics data, supply chain data, customs data, bill of lading data, or payment data.

[0049] In some embodiments, the system includes the trading platform.

[0050] For example, in another embodiment, a system for managing blockchain-based trusted transaction services includes: a blockchain network of multiple trusted nodes, comprising: a trade platform node corresponding to a trade platform for providing blockchain-based trusted trade services between a buyer and a seller, wherein the buyer has a buyer financial account in a buyer financial institution, the seller has a seller financial account in a seller financial institution, the buyer is verified to have a trusted credit (TU) service guaranteed by the buyer financial institution, and in response to the fulfillment of conditions specified in a smart contract deployed on the blockchain of the blockchain network, the buyer financial institution automatically makes payments for the buyer based on the buyer's credit in the buyer financial institution; a buyer financial institution node corresponding to the buyer financial institution; and a seller financial institution node corresponding to the seller financial institution. The trade platform node is configured to: after the buyer and the seller confirm an order on the trade platform, store the order data of the order on a corresponding blockchain of the blockchain network for the order, the order data including one or more payment terms of the order and data representing the corresponding trusted credit service of the order; generate a trusted credit certificate for the order based on the trusted credit service data, the trusted credit certificate including the order payment amount, and store the trusted credit certificate for the order on the blockchain. The buyer's financial institution node is configured to send the trusted credit certificate to the seller's financial institution's computing device to determine whether to approve the seller's financing request based on the trusted credit certificate.

[0051] In some embodiments, one or more of these general and specific embodiments may be implemented using a device, system, method, or computer-readable medium, or any combination of a device, system, method, and computer-readable medium. The foregoing and other described embodiments may each optionally include one or more of the following embodiments:

[0052] In some embodiments, one of the buyer financial institution and the seller financial institution is an offshore entity, and the other is an onshore entity. The offshore entity and the onshore entity are subject to different financial regulations, and the buyer financial institution node corresponding to the buyer financial institution and the seller financial institution node corresponding to the seller financial institution belong to the same blockchain network of the plurality of trusted nodes.

[0053] In some embodiments, the seller financial institution node is configured to: receive approval data from the seller financial institution's computing device, the approval data indicating that the seller financial institution has approved the seller's financing request for the financing amount based on the trusted credit certificate, and store the approval data on a blockchain, wherein the approval data references the trusted credit certificate.

[0054] In some embodiments, the seller financial institution node is configured to: receive financing payment data from the seller financial institution's computing device, the financing payment data confirming that the financing amount associated with the financing request has been paid by the seller financial account of the seller financial institution, and store the financing payment data on a blockchain.

[0055] In some embodiments, the trusted credit credential includes at least one of the following: an identifier of the trusted credit credential; the validity period of the trusted credit credential; the corresponding payment terms for the order; information about the order, including at least one of the following: order identifier, total cost of the order, or product information; logistics information about the order, including at least one of the following: transportation method, trade terms, transportation cost, or transportation insurance cost; information about the buyer and the seller; information about the buyer's financial institution and the seller's financial institution; or information about the buyer's financial account in the buyer's financial institution and information about the seller's financial account in the seller's financial institution.

[0056] In some embodiments, the seller financial institution node is configured to: receive payment receipt data from the seller financial institution's computing device, the payment receipt data confirming that the seller financial account in the seller financial institution has received the order payment for the order from the buyer financial institution, and store the payment receipt data on the blockchain.

[0057] In some embodiments, the trade platform node is configured to generate a corresponding smart contract for the order based on the order data. The corresponding smart contract includes an automatic function that, in response to determining that the corresponding payment conditions for the order payment have been met, automatically instructs the buyer's financial institution to make order payment to the seller for the order based on the corresponding trusted credit service.

[0058] In some embodiments, the trade platform node is configured to: verify, via the buyer financial institution node, using the buyer financial institution's computing equipment, whether the buyer has authorization for the corresponding trusted credit service for the order on the trade platform.

[0059] In some embodiments, in response to verifying that the buyer has authorization for a corresponding trusted credit service for the order guaranteed by the buyer's financial institution, a trusted credit certificate for the order is generated on the blockchain.

[0060] In some embodiments, the trade platform node is configured to submit a verification request with the trusted credit certificate to the computing device of the buyer financial institution via the buyer financial institution node, and the buyer financial institution is configured to verify, based on the trusted credit certificate, whether the buyer has authorization for the corresponding trusted credit service for the order.

[0061] In some embodiments, the trading platform node is configured to send a verification message to the trading platform confirming that the buyer has authorization for the corresponding trusted credit service for the order, guaranteed by the buyer's financial institution, in response to verifying that the buyer has authorization for the corresponding trusted credit service for the order.

[0062] In some embodiments, the trading platform is configured to verify the order after receiving the verification message from the trading platform node.

[0063] In some embodiments, the trading platform node is configured to send a verification request after storing the order data of the order on the blockchain.

[0064] In some embodiments, the corresponding payment terms are determined based on the corresponding trusted credit service for the order.

[0065] In some embodiments, the buyer financial institution node is configured to: in response to determining that the corresponding payment conditions for the order payment are met, execute the corresponding smart contract, wherein executing the corresponding smart contract includes automatically instructing the buyer financial institution's computing device to make order payment to the seller in accordance with the corresponding trusted credit service.

[0066] In some embodiments, the buyer financial institution node is configured to: in response to determining that the corresponding payment conditions for the order payment are met, execute a corresponding smart contract to generate an automatic payment command, the automatic payment command instructing the buyer financial institution's computing device to make order payment to the seller based on the corresponding trusted credit service for the order; and send the automatic payment command to the buyer financial institution's computing device.

[0067] In some embodiments, the blockchain network is configured to: in response to determining that a predetermined time has been reached or a predetermined time period has elapsed after the corresponding payment conditions have been met, execute the corresponding smart contract to automatically instruct the computing device of the buyer's financial institution to make order payment to the seller based on the corresponding trusted credit service of the order.

[0068] In some embodiments, the scheduled time or scheduled time period is determined based on the corresponding trusted credit service of the order.

[0069] In some embodiments, the one or more payment terms include a first payment term for a first payment of the order and a second payment term for a second payment of the order. The second payment is an order payment made under a trusted credit service for the order, and the second payment terms include the corresponding payment terms.

[0070] In some embodiments, the buyer financial institution node is configured to: in response to determining that a first payment condition for the first payment is met, execute the corresponding smart contract to automatically instruct the buyer financial institution's computing device to make a first payment to the seller based on the buyer's trusted automatic payment service provided by the buyer financial institution; and in response to determining that a second payment condition for the second payment is met, execute the corresponding smart contract to automatically instruct the buyer financial institution's computing device to make a second payment to the seller based on the corresponding trusted credit service for the order.

[0071] In some embodiments, the first payment is an advance payment for the order, and the first payment condition includes verification of the order. The second payment is the final payment for the order, and the second payment condition includes at least one of the following: the bill of lading associated with the order has been submitted by the seller on the trading platform; the submitted bill of lading has been confirmed by the buyer on the trading platform; the invoice associated with the order has been generated by the blockchain network; the generated invoice has been confirmed by the buyer; or the buyer and the seller have reached a consensus on the order.

[0072] In some embodiments, the trade platform node is configured to: after the buyer logs into the buyer trade account on the trade platform, communicate with the computing device of the buyer financial institution through the buyer financial institution node to verify whether the buyer's buyer financial account in the buyer financial institution is eligible for trusted automatic payment services, wherein the buyer trade account includes information of the buyer financial account.

[0073] In some embodiments, the corresponding smart contract further includes an order status update function that automatically updates the order status in response to determining that the order status has been changed based on order status data uploaded to the corresponding blockchain.

[0074] In some embodiments, the status of the order indicates at least one of the following: the product associated with the order has been prepared or shipped by the seller; the product has been inspected by customs; the product is being transported by at least one logistics provider; the bill of lading associated with the order has been submitted by the seller on the trading platform; the submitted bill of lading has been confirmed by the buyer on the trading platform; the invoice associated with the order has been generated by the blockchain network; the generated invoice has been confirmed by the buyer; the buyer and the seller have reached a consensus on the order; the buyer's financial institution has made the automatic payment; the seller's financial institution has received the automatic payment; or the buyer has received the product.

[0075] In some embodiments, the blockchain network of the plurality of trusted nodes further includes at least one of the following: a customs node corresponding to the customs, wherein the order status data includes customs data uploaded by the customs node to the corresponding blockchain; or a logistics provider node corresponding to the at least one logistics provider, wherein the order status data includes logistics data uploaded by the logistics provider node to the corresponding blockchain.

[0076] In some embodiments, the order status data includes at least one of logistics data, supply chain data, customs data, bill of lading data, or payment data.

[0077] In some embodiments, the system includes the trading platform.

[0078] It should be understood that the methods according to this document may include any combination of the embodiments described herein. That is, the methods according to this document are not limited to the combinations of the embodiments specifically described herein, but also include any combination of the provided embodiments.

[0079] Details of one or more embodiments herein will be set forth in the accompanying drawings and the following description. Further embodiments and advantages herein will become apparent from the description, drawings, and claims. Attached Figure Description

[0080] Figure 1 This is a diagram illustrating an example of an environment that can be used to perform the embodiments described herein.

[0081] Figure 2 This is a diagram illustrating an example of an architecture according to embodiments of this document.

[0082] Figure 3 This is a diagram illustrating an example of a blockchain-based trusted trading system that implements a blockchain-based trusted transaction service according to embodiments of this document.

[0083] Figure 4 This is a diagram illustrating an example of a user interface for a trade platform used to implement trusted trade services according to embodiments of this document.

[0084] Figure 5 This is a flowchart illustrating an example of a process for implementing a blockchain-based trusted transaction service, which can be performed according to embodiments herein.

[0085] Figure 6 This is a flowchart illustrating an example of a process for implementing a blockchain-based trusted transaction service, which can be performed according to embodiments herein.

[0086] Figure 7 This is a flowchart illustrating an example of a process for implementing a blockchain-based trusted transaction service, which can be performed according to embodiments herein.

[0087] Figure 8 This is a diagram illustrating an example of a blockchain trade invoice according to embodiments of this document.

[0088] Figure 9 This is a diagram illustrating an example of a trusted credential according to embodiments of this document.

[0089] Figure 10 This is a flowchart illustrating an example of a process for implementing a blockchain-based trusted transaction service with different payment conditions, which can be performed according to embodiments herein.

[0090] Figure 11 This is a flowchart illustrating an example of a process for implementing a blockchain-based trusted transaction service with consensus payment conditions, which can be performed according to embodiments herein.

[0091] Figure 12 An embodiment according to this article is shown. Figure 10 or Figure 11 A diagram showing the steps involved in the processing.

[0092] Figure 13A This is a flowchart illustrating an example of a process according to embodiments of this document.

[0093] Figure 13B This is a flowchart illustrating an example of a process according to embodiments of this document.

[0094] Figure 13C This is a flowchart illustrating an example of a process according to embodiments of this document.

[0095] Figure 14A Examples of modules of a device according to embodiments herein are depicted.

[0096] Figure 14B An example of a module of another apparatus according to embodiments herein is depicted.

[0097] Figure 14C An example of a module of another apparatus according to embodiments herein is depicted.

[0098] The same reference numerals and names in the various figures denote the same elements. Detailed Implementation

[0099] This paper describes technologies for managing trusted transaction services based on a novel blockchain architecture that enhances multiple aspects of data exchange between potentially unrelated entities. Trusted transaction services can include trade services, payment services, financial services, data exchange services, or any other transaction services. These technologies can enable new trusted transaction (e.g., trade and finance) service systems by integrating multiple trusted nodes into a blockchain network to provide trusted transaction services to transaction entities (e.g., trading parties), particularly for international orders or cross-border trade. These technologies can create a trusted transaction platform that allows potentially unrelated and previously untrusted or weakly trusted trading parties (e.g., small and medium-sized enterprises (SMEs)) to communicate and conduct business with each other in a reliable and efficient manner. These technologies can bridge the trust gap between trading parties and connect them through the transaction platform. The technology can integrate transaction platforms, financial institutions (e.g., offshore and onshore banks, customs, logistics providers, and / or any other relevant entities) as network nodes in a blockchain network to create a new ecosystem, for example, for providing trusted digital international or cross-border trade. The new ecosystem improves upon previous transaction systems in several ways. For example, the implementation of the technologies described herein can provide more secure, reliable, efficient, convenient, diversified, inclusive, and transparent transaction services. The new ecosystem also enables systems that enhance trust between trading parties and between businesses and financial institutions. The new ecosystem can make transactions more secure and reliable, financial lending more transparent, credible, or efficient, and services more efficient, convenient, or effective. For illustrative purposes, in this document, trade services (which may also include financial services such as payment services) are described as examples of transaction services; trade platforms or systems are described as examples of transaction platforms or systems; orders (e.g., purchase orders or other trade orders) are described as examples of transactions between trading entities; and buyers and sellers are described as examples of a pair of trading entities. The described technologies can be applied to additional or different examples of transaction services.

[0100] This technology can overcome well-known problems in traditional transaction systems (such as trade systems), such as low or insufficient trust among participants, inefficiency, low digitalization, high transaction costs, long payment turnaround times, heavy financing pressures on SMEs, and a lack of transparency. For example, the technology implemented in this paper can avoid complex offline processing and viewing, and can reduce transaction costs, automate settlement, facilitate access to corporate credit, and ensure verified orders and counterparties in trade, especially international or cross-border trade. These technologies can mitigate trade risks, such as reducing uncertainty (e.g., when shipping products and making payments), and help provide inclusive and efficient financial services by using traceable trade data and trusted automated payment services. These technologies can create next-generation global transaction systems to serve global entities, including SMEs.

[0101] The technology described herein produces several technical effects. In some embodiments, the technology can leverage hardware and software to establish new blockchain-based trading systems that integrate multiple selected groups of network nodes to construct a blockchain network. The selected group of network nodes may include, for example, computer systems of one or more trading platforms, financial institutions of trading parties, and one or more customs and logistics providers. The selected network nodes are trusted nodes, ensuring enhanced trust within the established blockchain network through consensus processing and the immutability, reliability, transparency, traceability, and verifiability of data. In some embodiments, for example, the blockchain network may be a consortium blockchain network, with additional safeguards regarding whether an entity can join as a network node in the blockchain network to provide trusted transaction services. In some embodiments, the technology can establish enhanced data security, provide more secure and reliable communication channels, reduce latency in data transmission, trigger order operations, and confirm receipt to provide trusted trading services. In some embodiments, the technology can define and deploy one or more smart contracts on the blockchain of the blockchain network to automatically trigger payments and other trading operations and enable trusted trading services. For example, once a buyer or seller (or supplier) generates (or confirms) a trade order on a trading platform, the order can be automatically uploaded and recorded on the blockchain of a blockchain network, making it traceable and tamper-proof. The order can include order details such as order terms, one or more payment conditions, and payment time. Once the order is recorded on the blockchain, a corresponding smart contract can be generated. As the order is executed, the smart contract can automatically execute to track and update order status data transmitted by trusted nodes in the blockchain network. Order status data can include, for example, order data, logistics data, customs data, payment data, and tax refund option information. Using blockchain, buyer's and seller's financial institutions can automatically process payment settlements through smart contracts. For example, a smart contract can include an automatic function that, in response to determining that the corresponding payment conditions for payment have been met, automatically instructs the buyer's financial institution to make payment to the seller for the order. The automatic triggering and immutability of smart contracts can enhance seller trust and assurance in order payment, making sellers more willing to do business with the seller.

[0102] In some embodiments, the buyer's payment may be backed or guaranteed by the buyer's financial institution to further enhance trust. In some cases, the buyer has been verified to have a trusted automatic payment (AP) service guaranteed by the buyer's financial institution, in which the financial institution automatically makes payment on behalf of the buyer upon the fulfillment of payment conditions specified in a smart contract on the blockchain. Under the trusted automatic payment service, the buyer's financial institution's computing device automatically executes the payment transaction without receiving authorization or confirmation from the buyer upon the fulfillment of payment conditions specified in a smart contract on the blockchain. In some cases, the buyer has been verified to have a trusted undertaking (TU) service guaranteed by the buyer's financial institution, such as a bank payment undertaking (BPU) service, in which the financial institution automatically makes payment to the seller on behalf of the buyer based on the buyer's credit within the financial institution upon the fulfillment of conditions specified in a smart contract on the blockchain. Under the trusted undertaking service, the buyer's financial institution's computing device executes the payment transaction without receiving authorization or confirmation from the buyer, regardless of whether the buyer's financial account has sufficient funds or money within the financial institution.

[0103] In some embodiments, this technology can improve efficiency and reduce waiting times in a series of operations within a trade order, including product transportation, different payment stages, payment confirmation, etc. In some embodiments, a series of operations within a specific trade order can be written into a smart contract tailored to that trade order, with defined trigger conditions. Once the trigger conditions are met, the smart contract can automatically trigger the next operation, thereby reducing processing delays and ensuring the orderly execution of the transaction process. Furthermore, during the actual execution of a trade order, data related to the trade order (e.g., logistics data and payment data) can be uploaded and stored on the blockchain, for example, by trusted nodes in real-time or near real-time. The smart contract can receive data (as input to trigger further operations) and track and update the status of the trade order based on the received data. Each trusted node in the blockchain network can have transparency and trust in the order status and order data stored on the blockchain. For example, payment confirmation data from the buyer's financial institution and / or payment receipt data from the seller's financial institution can be promptly returned and recorded on the blockchain, and made available to other trusted nodes in the blockchain network. For example, a trading platform can immediately receive payment confirmation data and / or payment receipt data and provide feedback on the payment status to both the buyer and seller. This ensures order payment, reduces payment confirmation waiting time, and makes payments more efficient and transparent. Trust between buyers and sellers can be established and increased. On-chain trust between buyers and suppliers can be continuously accumulated.

[0104] In some embodiments, this technology can enable trusted financial services for buyers. For example, a buyer can apply for a corresponding trusted credit line from a buyer's financial institution to place an order with a seller. The buyer's financial institution can verify, for example, the buyer's eligibility for the trusted credit line based on the buyer's credit history within the buyer's financial institution. If the buyer is verified to be eligible for the trusted credit line, the buyer's financial institution can make a payment commitment and guarantee (or promise) to make payment for the order to the seller once the payment conditions are met. In this way, the trusted credit line can convert the buyer's credit history within the buyer's financial institution into credit within the buyer's financial institution, which can enhance the buyer's reputation and leverage in trade. Therefore, the buyer can use the trusted credit line to negotiate better order terms, such as payment terms with longer payment periods. The trusted credit line can capitalize the buyer's credit history within the buyer's financial institution and can use the buyer's financial institution's guarantee to increase the buyer's credit in trade. For example, a blockchain network can generate a trusted credit certificate for the order based on, for example, order data, logistics data, customs data, and / or invoice data. The generated trusted credit certificate can be stored, transferred, and traded on the blockchain like an asset. The buyer can request the trusted credit line from the buyer's financial institution for the order based on the trusted credit certificate.

[0105] In some embodiments, these technologies can enable trusted financial services for sellers. For example, with a trusted credit line guaranteed by the buyer's financial institution, the seller does not need to worry about whether the buyer will make payment after the seller ships the products, and can be certain that the payment will be made by the buyer's financial institution, ensuring the seller's liquidity and security. Trusted financial services for trade orders supported by trusted credit lines can also help sellers obtain more financing. As an example, when a seller has financing needs, the seller can submit a financial request, such as a loan, to the seller's financial institution. The seller's financial institution can verify the seller's eligibility for a loan based on the on-chain trust between the trading parties (e.g., a trusted credit certificate generated on the blockchain). In some embodiments, the trusted credit certificate can be used as the seller's receivables and is considered any other type of asset of the seller that can be transferred or used for financing. In some embodiments, the seller's financial institution can submit a verification request to the blockchain network to check trusted trade data on the blockchain and obtain a trusted credit certificate, or the seller can submit a financing request along with a trusted credit certificate. If the seller's financial institution confirms the seller's eligibility for a loan, the seller can obtain the loan they need. The seller can repay the loan, for example, with the payment received from the buyer's financial institution based on the trusted credit line for the order.

[0106] In some embodiments, this technology can provide trusted trading services to a large number of trading parties through a unified, more user-friendly interface, while reducing the infrastructure and operational costs of trading entities. In some embodiments, buyers and sellers do not join the blockchain network as trusted nodes. Instead, the trading platform, as a trusted node in the blockchain network, can act as a common interface between buyers and sellers, providing secure and trusted trading services between them. However, in some embodiments, the trading platform does not need to act as a custodian system between buyers and sellers, and buyers and sellers do not need to open their own financial or monetary accounts on the trading platform for payments. Instead, buyers and sellers can use their own bank accounts to conduct end-to-end currency exchange or payments with their respective banks without channeling the money through the trading platform or other types of payments, which can be more efficient and reliable. In this way, the trading platform can be scaled to accommodate a large number of buyers and sellers, saving buyers and sellers operating expenses (OPEX) while continuing their respective financial instructions without opening new financial or monetary accounts. On the other hand, a large number of buyers and sellers can enjoy blockchain-based trusted trading services without having to join the blockchain network themselves as network nodes. This saves infrastructure costs by limiting trusted nodes to trading platforms, financial institutions, logistics providers, customs, and / or any relevant parties that can provide services to multiple buyers and sellers. This structure of blockchain-based trading platforms can also improve the operational efficiency of blockchain networks by reducing network traffic and computational load through consensus-building before data is stored on the blockchain. These technologies can provide more opportunities for trading platforms or trading markets, trading parties, financial institutions, logistics providers, customs, and / or any relevant parties.

[0107] In some embodiments, these technologies provide additional functions for establishing trusted connections between potentially unrelated entities. For example, these technologies can link trading platforms with buyer financial institutions, seller financial institutions, logistics providers, or companies or supply chain companies to build a trusted trading network in the form of a blockchain consortium to provide guaranteed trading services. This technology enables functions that provide traceability, decentralization, immutability, and transparency for trade and financial services, which can be used by all participants (or parties) on the blockchain to build a better trust system. A trust system enables trade to proceed, and the transfer of assets or credit to become more reliable and efficient.

[0108] In some embodiments, these technologies can enhance the security and convenience of executing electronic transactions. For example, they can provide secure and convenient transactions, smart and inclusive finance, and efficient and digital order management. In some embodiments, data on the blockchain can be made a source of authenticity by fairly distributing control to the parties using the system through the transparency of transaction history. Uploading source data to the blockchain through upstream and downstream cross-verification and the blockchain consensus mechanism ensures the authenticity of data on the blockchain, enabling trade participants to efficiently obtain authentic trade data from the blockchain and improve collaboration efficiency. In some embodiments, the blockchain network can generate blockchain trade invoices, which can integrate authentic trade data on the blockchain to form vouchers. These vouchers can serve as the basis for participants to verify the authenticity of trade, as transaction vouchers for buyers and sellers, and even as the basis for payments. Blockchain trade invoices can be used to verify the authenticity of trade without the need for complex offline processing and the requirements of various certification materials and documents.

[0109] To provide further background for the embodiments described herein, as mentioned above, a distributed ledger system (DLS), also known as a consensus network (e.g., composed of peer-to-peer nodes) and a blockchain network, enables participating entities to securely and immutably transact and store data. While the term blockchain is often associated with specific networks and / or use cases, in this document, blockchain generally refers to DLS without reference to any particular use case.

[0110] A blockchain is a data structure that stores transactions in an immutable manner. Therefore, transactions recorded on a blockchain are reliable and trustworthy. A blockchain consists of one or more blocks. Each block in the chain is linked to the preceding block by including the hash of its immediate predecessor in the chain. Each block also includes a local timestamp (e.g., provided by the computing device that generated the block or the computing system that manages the blockchain), its own hash, and one or more transactions. For example, a block may include a block header and a block body. The block header may include a local timestamp, its own hash, and the hash of the preceding block. The block body may include payload information, such as one or more transactions (or transaction data). Transactions verified by nodes in the blockchain network are hashed and encoded into a Merkle tree. A Merkle tree is a data structure in which data at the leaf nodes of a tree is hashed, and all hashes in each branch of the tree are concatenated at the root of the branch. This process continues along the tree to the root, where hashes representing all data in the tree are stored. A hash value can be quickly verified by determining whether the hash value of a transaction that claims to be stored in the tree is consistent with the structure of the tree.

[0111] A blockchain is a decentralized or at least partially decentralized data structure used to store transactions, while a blockchain network is a network of computing nodes that manage, update, and maintain one or more blockchains through activities such as broadcasting, verifying, and confirming transactions. As mentioned above, blockchain networks can be provided as public, private, or consortium blockchain networks.

[0112] Typically, consortium blockchain networks are private among the participating entities. In a consortium blockchain network, consensus processing is controlled by an authorized set of nodes, often referred to as consensus nodes, which are operated by their respective entities (e.g., financial institutions, insurance companies). For example, a consortium of ten (10) entities (e.g., financial institutions, insurance companies) can operate a consortium blockchain network, with each entity operating at least one node within the network. In some examples, a global blockchain is provided in a consortium blockchain network as a blockchain replicated across all nodes. That is, all consensus nodes are in a state of full consensus relative to the global blockchain. To achieve consensus (e.g., agreeing to add a block to the blockchain), a consensus protocol is implemented within the consortium blockchain network. For example, a consortium blockchain network can implement Practical Byzantine Fault Tolerance (PBFT) consensus, which will be described in further detail below.

[0113] In some embodiments, centralized ledger systems may also employ a blockchain data structure to leverage the immutability, reliability, and trustworthiness of data stored on the blockchain. In some embodiments, such a centralized ledger system may be referred to as a blockchain-based centralized ledger system or a general auditable ledger service system. In some embodiments, a blockchain-based centralized ledger system may include a central trusted authority that provides transparent, immutable, and cryptographically verifiable data stored in blocks within the blockchain data structure. The stored data may be in a log format, including not only transaction logs but also other transaction data and block data. Due to the presence of the central trusted authority, a blockchain-based centralized ledger system can establish trust without performing consensus processing. In some embodiments, a blockchain-based centralized ledger system can be more efficient than a typical blockchain-based distributed or decentralized ledger system. In some embodiments, a blockchain-based centralized ledger system can provide enhanced trust, efficiency, and storage performance for cloud-based storage services.

[0114] In some embodiments, a centralized ledger system can be a node in a blockchain network. For example, a centralized ledger system can be a non-consensus node in a blockchain network and can provide highly reliable and high-performance auditable streaming ledger services to consensus nodes or other non-consensus nodes in the blockchain network or entities outside the blockchain network.

[0115] Figure 1This diagram illustrates an example of an environment 100 that can be used to perform embodiments of this document. In some examples, environment 100 enables entities to participate in a consortium blockchain network 102. Environment 100 includes computing systems 106, 108 and a network 110. In some examples, network 110 includes a local area network (LAN), a wide area network (WAN), the Internet, or a combination thereof, and connects websites, user devices (e.g., computing devices), and backend systems. In some examples, network 110 can be accessed via wired and / or wireless communication links. In some examples, network 110 enables communication with and within the consortium blockchain network 102. Typically, network 110 represents one or more communication networks. In some cases, computing systems 106, 108 may be nodes of a cloud computing system (not shown), or each computing system 106, 108 may be a separate cloud computing system comprising multiple computers interconnected via a network and functioning as a distributed processing system.

[0116] In the described examples, computing systems 106 and 108 may each include any suitable computing system capable of participating as a node in the consortium blockchain network 102. Examples of computing devices include, but are not limited to, servers, desktop computers, laptop computers, tablet computing devices, and smartphones. In some examples, computing systems 106 and 108 host one or more computer-implemented services for interacting with the consortium blockchain network 102. For example, computing system 106 may host computer-implemented services for a first entity (e.g., user A), such as a transaction management system used by the first entity to manage its transactions with one or more other entities (e.g., other users). Computing system 108 may host computer-implemented services for a second entity (e.g., user B), such as a transaction management system used by the second entity to manage its transactions with one or more other entities (e.g., other users). Figure 1 In the example, the consortium blockchain network 102 is represented as a peer-to-peer network of nodes, and computing systems 106 and 108 provide nodes for the first and second entities participating in the consortium blockchain network 102, respectively.

[0117] Figure 2This is a diagram illustrating an example of architecture 200 according to embodiments of this document. The exemplary conceptual architecture 200 includes participant systems 202, 204, and 206, respectively corresponding to participant A, participant B, and participant C. Each participant (e.g., a user, enterprise) participates in a blockchain network 212 comprising a peer-to-peer network of nodes 214, wherein at least some nodes immutably record information in blockchain 216. As further described in detail herein, although a single blockchain 216 is schematically depicted within blockchain network 212, multiple copies of blockchain 216 are provided and maintained on blockchain network 212.

[0118] In the illustrated example, each participant system 202, 204, 206 is provided by or represents participants A, B, and C, respectively, and functions as their respective node 214 in the blockchain network. As used herein, a node typically refers to an individual system (e.g., a computer, server) connected to the blockchain network 212 and enabling the corresponding participant to participate in the blockchain network. In the example of the diagram, 2, each participant corresponds to a node 214. However, it should be anticipated that a participant can operate multiple nodes 214 within the blockchain network 212, and / or multiple participants can share a single node 214. In some examples, participant systems 202, 204, 206 communicate with or through the blockchain network 212 using protocols (e.g., Hypertext Transfer Protocol Security (HTTPS)) and / or using Remote Procedure Calls (RPC).

[0119] Node 214 can have different levels of participation within the blockchain network 212. For example, some nodes 214 may participate in consensus processing (e.g., as mining nodes adding blocks to blockchain 216), while other nodes 214 may not participate in this consensus processing. As another example, some nodes 214 may store a complete copy of blockchain 216, while other nodes 214 may store only a partial copy of blockchain 216. For example, data access privileges can restrict the amount of blockchain data that a given participant can store within their respective system. Figure 2 In the example, participant systems 202, 204 and 206 store complete copies 216', 216” and 216”' of blockchain 216, respectively.

[0120] Blockchain (e.g., Figure 2A blockchain (216) comprises a chain of blocks, each storing data. Examples of data include transaction data representing transactions between two or more participants. Transaction data is used as an example of data stored in the blockchain. Examples of transactions may include, but are not limited to, the exchange of valuables (e.g., assets, products, services, currencies). In some embodiments, one or more operations performed in the ledger system may be stored as transaction data in the blockchain. For example, transaction data may include one or more operations or manipulations on data stored in the blockchain, information obtained from external resources (e.g., timestamp information) or any suitable data (e.g., documents, images, videos, audio) may be stored in the blockchain. Transaction data is stored immutably in the blockchain. That is, the transaction data cannot be changed.

[0121] Before transaction data is stored in a block, it is hashed. Hashing is the process of converting transaction data (provided as string data) into a fixed-length hash value (also provided as string data). It is impossible to dehash the hash value to obtain the transaction data. Hashing ensures that even slight changes to the transaction data will result in a completely different hash value. Furthermore, as mentioned above, the hash value has a fixed length. That is, the length of the hash value is fixed regardless of the size of the transaction data. Hashing involves processing the transaction data using a hash function to generate a hash value. Examples of hash functions include, but are not limited to, the Secure Hash Algorithm (SHA)-256, which outputs a 256-bit hash value.

[0122] Transaction data from multiple transactions is hashed and stored in a block. For example, two transactions are provided with hashes, and then they are hashed themselves to provide another hash. This process is repeated until a single hash is provided for all transactions to be stored in the block. This hash is called the Merkle root hash and is stored in the block header. Any change in a transaction will cause its hash to change, and ultimately, the Merkle root hash will change.

[0123] Blocks are added to the blockchain via a consensus protocol. Multiple nodes in the blockchain network participate in the consensus protocol and perform work to add blocks to the blockchain. Such nodes are called consensus nodes. PBFT, as described above, serves as a non-restricted example of a consensus protocol. Consensus nodes execute the consensus protocol to add transactions to the blockchain and update the overall state of the blockchain network.

[0124] In more detail, consensus nodes generate block headers, hash all transactions within a block, and combine these hashes in pairs to generate further hashes until a single hash (the Merkle root hash) is provided for all transactions in the block. This hash is then added to the block header. Consensus nodes also determine the hash of the most recent block in the blockchain (i.e., the last block added to the blockchain). Consensus nodes also add a nonce value and a timestamp to the block header.

[0125] Typically, PBFT provides a practical Byzantine state machine replication that tolerates Byzantine errors (e.g., faulty nodes, malicious nodes). This is achieved by assuming failures will occur in PBFT (e.g., assuming independent node failures and / or manipulated messages sent by consensus nodes). In PBFT, consensus nodes are provided in a sequence including a primary consensus node and backup consensus nodes. The primary consensus node is changed periodically. Transactions are added to the blockchain by reaching consensus on the world state of the blockchain network among all consensus nodes within the blockchain network. In this process, messages are transmitted between consensus nodes, and each consensus node proves that the message was received from a designated peer node and verifies that the message has not been modified during transmission.

[0126] In PBFT, the consensus protocol is provided in multiple phases, assuming all consensus nodes start in the same state. First, the client sends a request to the primary consensus node to invoke a service operation (e.g., execute a transaction within the blockchain network). Upon receiving the request, the primary consensus node multicasts the request to backup consensus nodes. The backup consensus nodes execute the request, and each node sends a response to the client. The client waits until it receives a threshold number of responses. In some examples, the client waits until it receives f+1 responses, where f is the maximum number of faulty consensus nodes that the blockchain network can tolerate. The end result is that a sufficient number of consensus nodes agree on the order in which records are added to the blockchain, and the record is either accepted or rejected.

[0127] In some blockchain networks, cryptography is used to maintain transaction privacy. For example, if two nodes want to keep transaction privacy so that other nodes in the blockchain network cannot see the details of the transaction, these two nodes can encrypt the transaction data. Examples of encryption include, but are not limited to, symmetric and asymmetric encryption. Symmetric encryption refers to encryption that uses a single key for both encryption (generating ciphertext from plaintext) and decryption (generating plaintext from ciphertext). In symmetric encryption, the same key can be used by multiple nodes, so each node can encrypt / decrypt the transaction data.

[0128] Asymmetric encryption uses key pairs, each consisting of a private key and a public key. The private key is known only to the corresponding node, while the public key is known to any or all other nodes in the blockchain network. A node can encrypt data using another node's public key, and that encrypted data can be decrypted using another node's private key. For example, refer again... Figure 2 Participant A can use Participant B's public key to encrypt data and send the encrypted data to Participant B. Participant B can use their public key to decrypt the encrypted data (ciphertext) and extract the original data (plaintext). Messages encrypted using a node's public key can only be decrypted using that node's private key.

[0129] Asymmetric encryption is used to provide digital signatures, which allows participants in a transaction to verify the other participants and the validity of the transaction. For example, a node can digitally sign a message, and another node can verify that the message was sent by participant A based on A's digital signature. Digital signatures can also be used to ensure that messages are not tampered with during transmission. For example, see again... Figure 2 Participant A will send a message to Participant B. Participant A generates a hash value for the message and then encrypts the hash value using its private key to provide a digital signature for the encrypted hash value. Participant A appends this digital signature to the message and sends the digitally signed message to Participant B. Participant B decrypts the digital signature using Participant A's public key and extracts the hash value. Participant B hashes the message and compares the hash values. If the hash values ​​are the same, Participant B can confirm that the message did indeed originate from Participant A and has not been tampered with.

[0130] Figure 3 This is a diagram illustrating an example of a blockchain-based transaction system (e.g., a trade and financial system) 300 according to embodiments of this document. The blockchain-based trusted transaction system 300 uses a blockchain network 320 to implement blockchain-based trusted trade, financing, and other data exchange services. The blockchain network 320 may be... Figure 1 Blockchain network 102 or Figure 2 Blockchain network 212. For illustrative purposes, a consortium blockchain network is described as an example of blockchain network 320, and blockchain network 320 can also be a public blockchain network or a private blockchain network. Blockchain network 320 may include multiple trusted nodes (e.g., nodes 321, 322, 324, 326, 328) of a selected group of participants (e.g., entities 310, 330, 340, 350, 360). Although Figure 3The diagram illustrates separate, annotated nodes 321, 322, 324, 326, and 328, and their respective entities 310, 330, 340, 350, and 360. However, those skilled in the art will understand that in some embodiments, nodes 321, 322, 324, 326, and 328 may integrate one or more computing devices of their respective entities 310, 330, 340, 350, and 360 into a single device or system, and vice versa. In some embodiments, the plurality of trusted nodes may be consensus nodes that control the consensus processing of the blockchain network 320. Each of the plurality of trusted nodes may be, for example, Figure 1 Nodes 106 or 108, or Figure 2 Node 214. Blockchain network 320 can connect participants (such as trading platforms, buyer's financial institutions, seller's financial institutions, logistics providers or companies, customs and / or supply chain companies) to establish a trusted trade network in the form of a blockchain consortium to provide guaranteed trade services. Blockchain technology can make trade and financial services traceable, decentralized, immutable and transparent, allowing all participants on the blockchain to build a better trust system. A trust system can allow value to be transferred efficiently.

[0131] Participants may include one or more financial institutions, such as buyer bank 330 and seller bank 340. Financial institutions can be companies engaged in financial and monetary transactions such as deposits, loans, investments, and currency exchange. Financial institutions may provide customers with one or more financial services, such as payments, loans, and currency exchange. Financial institutions may include, for example, banks, trust companies, insurance companies, brokerage firms, or investment companies. For illustrative purposes, banks are used as an example of financial institutions in this disclosure, and the described techniques can be applied to any other type of financial institution.

[0132] In some embodiments, such as Figure 3 As shown, the blockchain network 320 includes a trusted trading platform node 321 corresponding to the trading platform 310. In some embodiments, the trusted trading platform node 321 and the trading platform 310 are communicatively connected. In some embodiments, the trusted trading platform node 321 and the trading platform 310 may be implemented as a single computing device or system. In some embodiments, the trusted trading system may include the blockchain network 320 and the trading platform 310.

[0133] In some embodiments, the blockchain network 320 includes multiple trusted trading platform nodes for multiple different trading platforms. A trusted trading system may include the blockchain network 320 and multiple different trading platforms 310.

[0134] Trade platform 310 can provide trade services to trading parties such as buyer 302 and seller 304. Trading parties can be individuals or businesses, such as small and medium-sized enterprises (SMEs). Seller 304 can be a supplier providing products (including services). Trade platform 310 can be an international or cross-border trade platform that provides trade services to buyers and sellers in different countries or regions. In some embodiments, each buyer has a buyer trade account on trade platform 310, and each seller has a seller trade account on trade platform 310.

[0135] Buyer 302 can log in to and be verified on the trade platform 310 using a buyer client device (e.g., a mobile device, laptop, desktop, or any other type of computing device) with appropriate credentials to trade with one or more sellers on the trade platform 310. Seller 304 can log in to and be verified on the trade platform 310 using a seller client device (e.g., a mobile device, laptop, desktop, or any other type of computing device) with appropriate credentials to trade with one or more buyers on the trade platform 310. One or both of Buyer 302 and Seller 304 can draft an order on the trade platform 310 and send it to the other party for review. The other party can modify or confirm the order until an agreement is reached between Buyer 302 and Seller 304. After both Buyer 302 and Seller 304 confirm the order, the trade platform 310 can upload the order data to the trade platform node 321. The order data may include, for example, information about Buyer 302, information about Seller 304, product information, and / or logistics information (e.g., shipping information). Order data may also include one or more order payments associated with one or more corresponding payment terms and corresponding payment times. In some embodiments, each order payment may have a corresponding payment service.

[0136] Trade platform 310 can upload order data to blockchain network 320 through corresponding trade platform node 321. Trade platform node 321 can be configured to store order data on the blockchain of blockchain network 320. The blockchain can store order-related information, including order data, logistics data, payment data, customs data, supply chain data, invoice data, or any data related to the order. This blockchain can be accessed by every network node in the blockchain network. The blockchain can be... Figure 2Blockchain 216. In some embodiments, each node in the blockchain network can store a local copy of the blockchain in its own storage space. In some embodiments, each node in the blockchain network 320 can receive corresponding order status data uploaded to the blockchain by the corresponding participant and store the corresponding order status data on the blockchain. For example, order status data may include logistics data uploaded by the logistics provider 350 via the corresponding logistics provider node 326, supply chain data from the supply chain service company, customs data uploaded by the customs 360 via the customs node 328, bill of lading data from the trading platform to the trading platform node, or payment confirmation data uploaded by the buyer's bank 330 via the buyer's bank node 322 and / or payment receipt data uploaded by the seller's bank 340 via the seller's bank node 324. In this way, the blockchain network 320 can provide secure and convenient transactions, intelligent and inclusive finance, and efficient and digital order management, which can make the data on the blockchain a source of authenticity and provide transparent transaction history to users of the blockchain-based trusted trade and finance system 300. By cross-verifying upstream and downstream data, uploading source data to the blockchain, and using the blockchain consensus mechanism, the authenticity of data on the blockchain can be ensured. This allows participants in the blockchain network 320, such as trading platforms 310, buyer banks 330, seller banks 340, logistics providers 350, and customs 360, to efficiently obtain authentic trade data from the blockchain and improve collaboration efficiency.

[0137] In some embodiments, blockchain network 320 can generate blockchain trade invoices that integrate real trade data on the blockchain to form vouchers. These vouchers can serve as the basis for participants to verify the authenticity of trade, as transaction vouchers for buyers and sellers, and even as payment confirmations. Blockchain trade invoices can be used to verify the authenticity of trade without requiring complex offline processing and various certification materials and documents.

[0138] Figure 8 This is a diagram illustrating an example of a blockchain trade invoice 800 according to embodiments of this document. The blockchain trade invoice 800 can be generated by a blockchain network 320 (e.g., a trade platform node 321) based on order data. Based on the order status data corresponding to the order, the invoice 800 can be updated, for example dynamically or in real-time, such as updating customs or logistics information as the order status changes. In some embodiments, the invoice 800 includes invoice information 802, buyer / seller information 804, logistics information 806, product information 808, and summary information 810.

[0139] As Figure 8In the example shown, invoice information may include an invoice number (or invoice identifier), order number, invoice date, and buyer's bank name. Buyer / seller information 804 may include seller information (e.g., seller name, registered address, email, or other contact information) and buyer information (e.g., buyer name, registered address, email, or other contact information). Logistics information 806 may include the mode of transport (e.g., ocean freight), shipping terms (e.g., FOB), and transport costs. Logistics information 806 may also include customs status (e.g., transit) and customs number, which can be updated using customs data provided by Customs 360. Logistics information 806 may also include transport status (e.g., en route), which can be updated using logistics data uploaded by logistics provider 350. Product information 808 may include product images, product name, specifications, remarks, quantity, and cost. Summary information 810 may include total order amount, transport costs, transport insurance premiums, and total order cost.

[0140] Return to reference Figure 3 Trade platform node 321 can generate smart contracts corresponding to orders on the blockchain. Smart contracts can include one or more computer-executable logic, instructions, scripts, or lines of code, which can be stored on the blockchain and automatically executed when one or more predetermined conditions are met. Because smart contracts are stored on the blockchain of blockchain network 320, they are executed by trusted nodes of blockchain network 320, and the execution result of the smart contract occurs through consensus processing among nodes. Smart contracts can enforce protocols, allowing participants to determine the outcome without the involvement of intermediaries. For example, smart contracts can include functions written in the form of computer-executable code, such as "if / when...then...". Smart contracts can be deployed on the blockchain network, for example, by having a contract account corresponding to the smart contract on the blockchain, and this contract account having a specific address (also called a smart contract address). For example, a smart contract can be invoked via a transaction on the blockchain transmitted from network nodes (e.g., nodes 321, 322, 324, 326, or 328 of blockchain network 320). When the predetermined conditions are met and verified, the network node can execute the smart contract. In some embodiments, smart contracts can be executed independently on each node in the blockchain network.

[0141] In some embodiments, the trading platform node 321 can generate a smart contract template that includes multiple logic or functions related to trusted trading services and deploy the smart contract template in the blockchain network 320. For each order, a transaction corresponding to the order can be generated based on the order data. For example, the trading platform node 321 can generate a transaction to invoke or call one or more functions in the smart contract template, using the order data as input to one or more functions in the smart contract template. The trading platform node 321 can then submit the transaction corresponding to the order to the blockchain for storage and execution.

[0142] In some embodiments, the trading platform node 321 can generate a smart contract corresponding to each order and deploy each smart contract on the blockchain network 320. Each smart contract is generated based on the order data of the corresponding order and includes functions for the trusted trading services of the corresponding order.

[0143] In some embodiments, the transaction corresponding to the order in the foregoing implementation can also be referred to as the smart contract corresponding to the order, because the transaction also includes instructions or code for calling functions defined in the smart contract template. In some embodiments, in exemplary implementations or other possible implementations, it is commonly described that a smart contract corresponding to the order can be generated based on the order data of the order. Those skilled in the art will understand that the smart contract corresponding to the order can be implemented in different ways, including logic or functions, to realize a trusted trading service for the corresponding order. For example, the trading platform node 321 is configured to generate the smart contract for the order from scratch, or the trading platform node 321 is configured to generate the smart contract for the order based on the order data according to a smart contract template, the smart contract template may include multiple functions for trusted trading services. In the latter case, when generating the corresponding smart contract for the order, the trading platform node 321 may be configured to call one or more functions of multiple functions in the smart contract template, and use the order data as input to one or more functions of multiple functions in the smart contract template to generate the smart contract for the order as output.

[0144] In some embodiments, the corresponding smart contract further includes an order status update function that automatically updates the order status in response to a determination based on order status data uploaded to the corresponding blockchain that the order status has been changed. For example, the order status may indicate that the product associated with the order has been prepared or shipped by the seller, the product has been inspected by customs 360, the product is being transported by the logistics provider 350, the bill of lading associated with the order has been submitted by the seller 304 on the trading platform 310, the submitted bill of lading has been confirmed by the buyer 302 on the trading platform 310, the invoice associated with the order has been generated by the blockchain network 320, the generated invoice has been confirmed by the buyer 302, a consensus has been reached between the buyer 302 and the seller 304 regarding the order, the buyer's bank 330 has completed order payment, the seller's bank 340 has received order payment, the buyer 302 has received the product, or any other order status information.

[0145] In some embodiments, buyer 302 has a buyer financial account in buyer bank 330, which provides one or more financial services, such as payment services, to the buyer. The buyer's trading account on trading platform 310 may include information about the buyer's financial account, such as the name of buyer bank 330, account number, and the name of the buyer. In some embodiments, seller 304 has a seller financial account in seller bank 340, which provides one or more financial services, such as deposit services and / or financial lending services, to seller 304. The seller's trading account on trading platform 310 may include information about the seller's financial account, such as the name of seller bank 340, account number, and the name of the seller. In some embodiments, order payments for orders between the buyer and seller can be made between buyer bank 330 and seller bank 340 without going through trading platform 310. Therefore, trading platform 310 does not need to act as an escrow system between the buyer and seller, which mitigates the risk of trading platform 310 acting as a guarantor. Buyer 302 and seller 304 do not need to open their own financing or currency accounts on trading platform 310 for payments. Instead, buyers and sellers can use their own bank accounts to exchange or make payments with their respective banks, without going through a trading platform. This is more reliable and efficient, saving them costs and effort, and reducing their concerns about the security of their financial accounts.

[0146] In some embodiments, buyer 302 and seller 304 may be located or registered in different countries or regions, thus their trade is international or cross-border trade. Similarly, buyer bank 330 and seller bank 340 may be located or registered in different countries or regions and are subject to different financial regulations. Payments or other asset transfers between buyer bank 330 and seller bank 340 may be international transactions or cross-border trade. For example, relative to trade platform 310, one of buyer bank 330 and seller bank 340 is an offshore bank, and the other is an onshore bank. Offshore and onshore banks can handle incompatible currencies. Blockchain-based trusted trade and finance system 300 creates a reliable and secure platform that can make unrelated or incompatible entities compatible, for example, by integrating buyer bank node 322 of buyer bank 330 and seller bank node 324 of seller bank 340 into blockchain network 320, enabling buyer bank 330 and seller bank 340 to transact.

[0147] In some embodiments, order payments between buyer 302 and seller 304 from buyer bank 330 to seller bank 340 are made via wire transfer. The wire transfer can be, for example, a whale transfer or a SWIFT transfer. In some embodiments, order payments can be made between buyer bank 330 and seller bank 340 in digital currency. In response to receiving a payment order, buyer bank 330 can transfer the digital value corresponding to the order payment to seller bank 340, for example, through buyer bank node 322 and seller bank node 324 in blockchain network 320 or any other blockchain network.

[0148] As discussed in further detail below, in some embodiments, buyer bank 330 may provide buyer 302 with a trusted automatic payment (AP) service to conduct trade on trading platform 310. Buyer bank 330 guarantees the trusted automatic payment service, automatically making payment on behalf of buyer 302 in response to the fulfillment of payment conditions specified in a corresponding smart contract deployed on the corresponding blockchain of blockchain network 320. Under the trusted automatic payment service, buyer bank 330 can automatically make payments without authorization or confirmation from buyer 302. In this way, payment for orders can be guaranteed, and payments can be made efficiently, effectively, and transparently. Trust between buyer 302 and seller 304 can be established or enhanced.

[0149] In some embodiments, when drafting an order or viewing an order from seller 304, buyer 302 may choose to use the appropriate trusted automatic payment service for the order on trading platform 310. After buyer 302 and seller 304 confirm the order, trading platform 310 sends the order data to trading platform node 321, which stores the order data in the corresponding blockchain. The order data may include one or more order payments with one or more corresponding payment conditions and data on the trusted automatic payment service for the order. The trusted automatic payment service data may include the order payment using the trusted automatic payment service. Trading platform node 321 may send a request to the computing device of buyer bank 330 via buyer bank node 322 to verify whether buyer 302 or buyer financial account is eligible for the trusted automatic payment service for the order payment. Buyer bank 330 may determine the eligibility of buyer 302 or buyer financial account based on, for example, the credit limit of buyer 302 or buyer financial account. If buyer bank 330 determines that buyer 302 or buyer's financial account is eligible for the trusted automatic payment service for the order, buyer bank 330's computing device can send verification data to buyer bank node 322, which stores the verification data for the order on the blockchain. Therefore, trading platform node 321 can send a verification message corresponding to the verification data to trading platform 310. Based on the verification message, trading platform 310 can confirm that buyer 302 can use the trusted automatic payment service for the order and subsequently verify the order. The order verification can be uploaded to the blockchain by trading platform 310 via trading platform node 321. Trading platform node 321 can generate a corresponding smart contract for the order. In response to the determination that the corresponding payment conditions for the order payment are met, the corresponding smart contract can be executed to automatically instruct buyer bank 330's computing device to make order payment to the seller according to the trusted automatic payment service.

[0150] In some embodiments, having access to a trusted automatic payment service may be a basic requirement or the default payment service for conducting trade on the trading platform 310. After buyer 302 logs into their buyer trading account on the trading platform 310, the trading platform node 321 may communicate with the buyer's bank 330 to verify whether buyer 302's buyer financial account or the buyer in buyer's bank 330 is eligible for the trusted automatic payment service on the trading platform 310. The trading platform 310 may be configured to allow buyer 302 to draft an order or view an order prepared by seller 304 on the trading platform 310 in response to determining that buyer 302 or the buyer financial account associated with the buyer's trading account is eligible for the trusted automatic payment service. If the trading platform 310 determines that buyer 302 or the buyer financial account is not eligible for the trusted automatic payment service, the trading platform 310 may warn buyer 302 and refuse to allow buyer 302 to process the order.

[0151] As discussed in further detail below, in some embodiments, the buyer bank 330 may also provide a Trusted Credit (TU) service, such as a Trusted Bank Payment Credit (BPU) service. The Trusted Credit Payment Service is guaranteed by the buyer bank 330, and in response to the fulfillment of payment conditions specified in a corresponding smart contract deployed on the corresponding blockchain, the buyer bank 330 automatically makes payment for the buyer 302 based on the buyer 302's credit in the buyer bank 330. According to the Trusted Credit Service, the buyer bank 330 guarantees payment regardless of whether the buyer 302 has sufficient funds or money in the buyer bank 330, which can significantly increase the certainty of payment and improve trust between the buyer and seller of the order. For illustrative purposes, the Trusted Bank Payment Credit Service is used as an example of a Trusted Credit Service in this disclosure, and the described techniques can be applied to any other type of Trusted Credit Service.

[0152] In some embodiments, the trading platform 310 provides a user interface (e.g., ...). Figure 4 The user interface (400) is provided, for example, to the buyer 302 and / or the seller 304 for receiving user input of order data. In some embodiments, the user interface may include the use of a corresponding trusted bank payment credit service for at least one payment option for an order with corresponding payment terms and / or corresponding payment times. Payment time is represented, for example, as the period after the payment terms are met and before the trusted bank payment credit service is used to execute the payment. Since the trusted bank payment credit service can be guaranteed by the buyer's bank 330, the buyer 302 can negotiate the payment time with the seller 304 based on the selection of the trusted bank payment credit service for order payment.

[0153] In some embodiments, if the trading platform 310 determines that the buyer 302 has chosen to use the trusted bank payment credit service for an order confirmed by the buyer 302 and the seller 304, the trading platform 310 may request verification of whether the buyer's bank 330 has approved the buyer 302 to use the trusted bank payment credit service for the order through the trading platform node 321 and the buyer's bank node 322. The buyer's bank 330 may determine the eligibility of the buyer 302 or the buyer's financial account, for example, based on the creditworthiness of the buyer 302 or the buyer's financial account in the buyer's bank 330. If the buyer's bank 330 determines that the buyer 302 or the buyer's financial account is eligible for the trusted bank payment credit service for the order, the computing device of the buyer's bank 330 may send the verification data to the buyer's bank node 322. The buyer's bank node 322 may store the verification data of the order on the blockchain. Therefore, the trading platform node 321 may receive the verification data of the order from the blockchain and send a verification message corresponding to the verification data to the trading platform 310. Trade platform 310 can confirm that buyer 302 is eligible for the trusted bank payment credit service for the order based on the verification message, and then verify the order. Order verification can be uploaded to the blockchain by trade platform 310 via trade platform node 321. Trade platform node 321 can generate a corresponding smart contract for the order. In response to the determination that the corresponding payment conditions for order payment are met, the corresponding smart contract can be executed to automatically instruct the computing device of buyer bank 330 to make order payment to seller 304 according to the trusted bank payment credit service. Buyer bank 330 can make a payment commitment and guarantee to make order payment to seller 304 for the order. In this way, the trusted bank payment credit service can convert the credit of buyer bank 330 into the credit of the buyer within buyer bank 330, which can increase the credit of buyer 302 in the trade. Therefore, buyer 302 can use the trusted bank payment credit service to negotiate better order terms, such as payment terms like longer payment terms and / or lower prepayment amounts. Trusted bank payment credit services can capitalize buyer credit in buyer bank 330 and can use buyer bank 330's guarantees to increase buyer credit in trade.

[0154] In some embodiments, a trusted credit credential, such as a trusted bank payment credit credential, can be generated based on order data. Order data may include information about the buyer (302), the seller (304), product information, logistics information, and at least one payment using trusted bank payment credit services and corresponding payment terms.

[0155] Figure 9An exemplary trusted credit credential is illustrated according to embodiments herein, such as a bank payment credit credential 900 generated based on order data of a corresponding order. The bank payment credit credential 900 includes bank payment credit information 902, bank payment credit data 904, bank account information 906, shipping information 908, and product information 910. In some embodiments, the bank payment credit information 902 includes a bank payment credit credential number (or an identifier of the bank payment credit credential), an order number, a buyer's name, a seller's name, and a buyer's bank. The bank payment credit data 904 may include the corresponding payment amount or bank payment credit amount, the effective date of the bank payment credit, the total cost of the order, and corresponding payment terms, such as payment 30 days after the seller submits the bill of lading. The bank account information 906 may include information about the buyer's bank account (e.g., buyer's name, account number, and buyer's bank name) and information about the seller's bank account (e.g., seller's name, account number, and seller's bank name). The shipping information 908 may include, for example, a mode of transport by sea and, for example, FOB terms of shipment (or trade terms). Product information 910 may include product images, name, specifications, remarks, quantity, and cost. Bank payment credit voucher 900 may also include summary information 912, which includes transportation costs, transportation insurance premiums, the total order amount, and the total cost of the order.

[0156] Return to reference Figure 3 Trusted credentials can be generated through a trusted node in the trading platform 310 or the blockchain network 320. The generated trusted credentials can be stored, transferred, and traded on the blockchain like assets. Buyers 302 and / or sellers 304 can use the trusted credentials.

[0157] In some embodiments, after buyer 302 and seller 304 confirm the order, trading platform 310 determines that buyer 302 has selected a trusted bank payment credit service for at least one payment of the order. Trading platform 310 can generate a corresponding trusted credit certificate based on the order data, such as a trusted bank payment credit certificate (e.g., bank payment credit certificate 900). Trading platform 310 can submit the trusted credit certificate and order data to trading platform node 321 for storage on the corresponding blockchain of blockchain network 320. Buyer 302 can request buyer bank 330 to provide trusted bank payment credit service to pay for the order based on the trusted credit certificate. The trusted credit certificate can be proof of order authentication. Buyer bank 330 can verify whether buyer 302 is eligible for trusted bank payment credit service for order payment based on buyer 302's credit in buyer bank 330.

[0158] In some embodiments, trade platform node 321 can receive order data from trade platform 310. In some embodiments, the order data includes user input data instructing buyer 302 to select a trusted bank payment credit service for payment of the order. Trade platform node 321 can determine that buyer 302 has selected a trusted bank payment credit service for payment of the order and can generate a corresponding trusted credit credential based on the order data. Trade platform node 321 can store the trusted credit credential along with the order data on the blockchain. Trade platform node 321 can provide the trusted credit credential to trade platform 310, which can then forward it to buyer 302's client device. Buyer 302 can request buyer's bank 330 to provide bank payment credit service for order payment. Buyer's bank 330 can obtain the trusted credit credential from the blockchain through buyer's bank node 322 and verify the order's authentication and buyer 302's eligibility.

[0159] In some embodiments, as described above, after the buyer 302 and seller 304 confirm the order, the trading platform 310 determines that the buyer 302 has selected a trusted bank payment credit service for at least one payment of the order. The trading platform 310 can submit a request to the buyer's bank 330 through the trading platform node 321 and the buyer's bank node 322 to verify whether the buyer's bank 330 will provide the buyer 302 with the trusted bank payment credit service for the order payment, or to verify whether the buyer 302 is eligible for the trusted bank payment credit service for the order payment guaranteed by the buyer's bank 330. If the buyer 302 is eligible for the trusted bank payment credit service, the buyer's bank 330 can submit the verification data to the buyer's bank node 322. The buyer's bank node 322 stores the verification data on the blockchain. For example, in response to determining that the buyer is eligible for the trusted bank payment credit service for the order payment guaranteed by the buyer's bank 330, the buyer's bank node 322 or the trading platform node 321 can generate a corresponding trusted credit certificate for the order based on the verification data.

[0160] In some embodiments, where the buyer's bank 330 guarantees the trusted bank payment credit service, the seller 304 does not need to be concerned about payments from the buyer 302 and can have order payment certainty to ensure the seller 304's liquidity and security. When the seller 304 has financing needs, for example, needing more funds to manufacture the products in the order, the seller 304 can submit a financial request, such as a loan, to the seller's bank 340. The seller's bank 340 can verify the seller 304's eligibility for a loan based on the seller 304's credit and / or on-chain trust (e.g., a trusted credit certificate generated on the blockchain). The seller's bank 340 can submit a verification request to the seller's bank node 324 to check trusted trade data on the blockchain and obtain a trusted credit certificate, or the seller 304 can submit a financial request with a trusted credit certificate to the seller's bank 340. If the seller's bank 340 verifies that the seller 304 is eligible for a loan, the seller 304 can obtain a loan according to their financial needs. Seller 304 may, for example, use the payment received from buyer's bank 330 to repay the financial loan under the trusted bank payment credit service of the order.

[0161] An order may include one or more order payments corresponding to one or more payment terms. For example, the order may include an initial payment or prepayment and its corresponding payment terms, as well as a remaining payment or balance payment and its corresponding payment terms. In some embodiments, all order payments for an order may be made using the same payment service (e.g., a Trusted Automatic Payment (AP) service or a Trusted Credit (TU) service such as a Trusted Bank Payment Credit Service). In some embodiments, order payments for the order may be made using a combination of a Trusted Automatic Payment Service and a Trusted Bank Payment Credit Service; for example, different payment services may be used for different order payments. Buyer 302 or seller 304 may select the appropriate payment service for different order payments on the trading platform 310, for example, through a user interface.

[0162] Figure 4 It shows the result of Figure 3 An example of the user interface 400 provided by the trading platform 310. The trading platform 310 may have a default payment service, such as a trusted automatic payment service. As described above, the trading platform 310 may first verify whether the buyer is eligible for a trusted automatic payment service with buyer bank guarantee, and after successful verification, provide the buyer with the user interface 400 for drafting an order.

[0163] Payment for an order can include one or more payments. The sum of these payments is the total amount of the order. For example, payment for an order can be divided into a prepayment and a final payment. The sum of the prepayment and the final payment is the total amount of the order. In some examples, the prepayment is 30% of the total order amount, and the final payment is 70% of the total order amount. Figure 4 As shown, the user interface 400 includes a prepayment section 410 for advance payments and a final payment section 420 for final payments. The buyer can set the prepayment amount 412, for example, $3000. Label 414 indicates the payment conditions that automatically trigger the prepayment payment after a predetermined time has elapsed following the fulfillment of certain conditions. The buyer can select payment conditions 416, such as order verification, and set the payment time 418, such as entering the number of days or selecting a specific date as the Pre-Delivery Time (PDT). There is no option to select a trusted automatic payment service in the prepayment section 410, meaning the prepayment is made according to the default trusted automatic payment service.

[0164] In the final payment section 420, the final payment amount 422 is displayed, for example, automatically determined after selecting a prepayment. Label 424 indicates payment conditions that automatically trigger the final payment after a predetermined time has elapsed following the fulfillment of the following conditions. The buyer can select payment conditions 426. A pop-up window 430 displays a list of payment conditions, such as seller submitting the bill of lading, buyer confirming the bill of lading, system-generated conditions, etc. Figure 8 The invoice can be an 800-type invoice, a buyer-confirmed invoice, or an agreement reached between the buyer and seller. The selected payment terms can be highlighted, for example, in bold. The buyer can also select the payment time 428, such as entering the number of days or selecting a specific date as the scheduled time (PDT). Unlike the prepayment portion 410, the final payment portion 420 includes the option 429 to select a bank payment credit service. If the buyer does not select a bank payment credit service, it is assumed that the final payment will be made according to the default payment service (e.g., a trusted automatic payment service). If the buyer selects a bank payment credit service, it is assumed that the final payment is made according to the bank payment credit service. The buyer can negotiate additional payment times with the seller by selecting a bank payment credit service. As mentioned above, for example... Figure 9 A trusted bank payment credit certificate (900) can be generated accordingly. The trading platform can submit a verification request to verify whether the buyer is eligible for the bank payment credit service for the order.

[0165] To illustrate, the attached diagram... Figure 5 , Figure 6 , Figure 7 This is a flowchart illustrating examples of processes for implementing a blockchain-based trusted trade service, which can be performed according to the embodiments herein. Each process includes operations related to a Trusted Automatic Payment (AP) service and a Trusted Bank Payment Pricing (BPU) service. The process can, for example... Figure 3 Implemented in an environment or system of blockchain-based trusted trade and finance system 300, the environment or system including, for example Figure 3 The blockchain network 320 and multiple participants, including, for example, Figure 3 310 trade platforms, for example Figure 3 Buyer bank 330, for example Figure 3 The seller's bank 340, for example Figure 3 Logistics providers of 350, such as Figure 3 Customs 360. A blockchain network can include multiple trusted nodes corresponding to multiple participants. Trading platforms, for example... Figure 3 Buyer 302 and, for example Figure 3 The seller's bank provides trusted trading services between sellers (those with a 304 error). The buyer's bank provides financial services to the buyer, such as payment services. The seller's bank provides financial services to the seller, such as loans and deposits. Trusted Automatic Payment (AP) service can be the default payment service on the trading platform. Bank payment credit services can be selected and verified.

[0166] Reference Figure 5 In processing 500, line 510 includes logistics-related steps performed by customs and logistics providers; line 520 includes steps related to information flows performed on the trade platform; line 530 includes steps related to AP / BPU services; and line 540 includes steps related to fund flows performed by the buyer's bank and the seller's bank.

[0167] At step 521, process 500 begins. The buyer or seller can log in to their buyer's trading account or seller's trading account on the trading platform. The buyer's trading account may include information about their financial account at their bank. In some embodiments, after the buyer logs in to their trading account, the trading platform may submit a request to the blockchain network to verify with the buyer's bank whether the buyer is eligible for a trusted automated payment service guaranteed by the buyer's bank. If the trading platform receives successful verification from the buyer's bank, process 500 continues.

[0168] At 522, draft an order on the trading platform. The trading platform can present a user interface, for example, Figure 4 The user interface 400 allows the buyer to select the prepayment amount or the final payment amount, as well as the corresponding payment terms and timing. In 532, the buyer, for example, selects a bank payment credit service in the user interface. After completing the order, the buyer can send the order to the seller for review. The seller can modify the order and send the modified order back to the buyer for review.

[0169] At step 523, the buyer and seller confirm the order on the trading platform. At step 533, after order confirmation, the trading platform submits the order data (or order information) to the corresponding trading platform node on the blockchain network, for example... Figure 3 Node 321. Order data 531 may include the corresponding payment terms for one or more payments (e.g., prepayment and final payment) and bank payment credit information for a bank payment credit service. The bank payment credit information may indicate that a bank payment credit service has been selected for the final payment.

[0170] At 534, the trading platform node stores order data 531 on the blockchain of the blockchain network. Order data 531 includes payment terms for prepayment, such as... Figure 4 The prepayment terms 416, and the final payment terms, for example... Figure 4 The final payment condition is 426. Trade platform nodes can generate blockchain trade invoices based on order data, for example... Figure 8 The invoice (800) is generated and stored on the blockchain. The trading platform node can then determine that the buyer has selected a bank payment credit service for the final payment of the order. In some embodiments, the trading platform node can generate a trusted bank payment credit certificate based on the order data, for example... Figure 9 Bank payment credit certificate 900.

[0171] In 541, through the buyer's bank node (e.g., Figure 3 The buyer's bank node (322) submits a verification request to the buyer's bank, and the trading platform node initiates a bank payment credit application for the final payment. At 542, the buyer's bank performs bank payment credit verification to determine whether the buyer is eligible for the final payment's bank payment credit service based on the buyer's credit, invoice, and / or bank payment credit certificate in the buyer's bank records. If the buyer's bank determines that the buyer is eligible for the final payment's bank payment credit service, the buyer's bank can submit the corresponding verification data to the buyer's bank node that stores the verification data on the blockchain. The trading platform node can then send the verification data to the trading platform. At 535, in response to receiving the verification data, the trading platform verifies the order. The trading platform uploads the order's verification data to the trading platform node on the blockchain network.

[0172] In 536, the trading platform node generates smart contract 502 on the blockchain based on order data. Smart contract 502 includes an automatic function that, in response to determining that the prepayment payment conditions are met, automatically instructs the buyer's bank to pay the prepayment for the order to the seller via a trusted automatic payment service, and, in response to determining that the final payment payment conditions are met, pays the final payment for the order to the seller via a trusted bank payment credit service. Smart contract 502 also includes an order status update function that automatically updates the order status in response to determining that the order status has been changed based on order status data uploaded to the blockchain by participants (e.g., the trading platform, buyer's bank, seller's bank, customs, and logistics providers).

[0173] In step 543, in response to determining that the payment conditions for the prepayment have been met, the smart contract automatically triggers an automatic payment command. The payment conditions for the prepayment may be that the order has been verified by the trading platform. In some embodiments, the automatic payment command is triggered in response to determining that a predetermined time has elapsed or a predetermined period has passed since the payment conditions for the prepayment have been met. The buyer's financial institution node sends the automatic payment command to the buyer's bank's computing device, which instructs the buyer's financial institution's computing device to pay the prepayment to the seller according to the trusted automatic payment service.

[0174] At step 544, the buyer's bank makes the advance payment according to the trusted automatic payment service and submits payment data 545 to the buyer's bank node. Payment data 545 confirms that the buyer's bank has made the advance payment to the seller. The buyer's bank node stores payment data 545 on the blockchain. At step 546, the seller's bank receives the advance payment from the buyer's bank and can submit payment receipt data to the seller's bank node that stores the payment receipt data on the blockchain. Payment receipt data confirms that the seller's financial account has received the advance payment. The trading platform can be configured to receive payment data (and / or payment receipt data) from the blockchain through the trading platform node and provide payment status feedback to the buyer and seller based on the payment data (and / or payment receipt data).

[0175] At step 525, the seller ships the ordered products. Following step 524, i.e., after the order is verified on the trading platform, or after receiving payment data and / or payment receipt data, the seller can ship the products. At step 512, customs inspects the products and generates customs data 511. At step 514, the logistics provider ships the products and generates logistics data 513. At step 537, customs data 511 is submitted to the blockchain, e.g., from customs to a customs node, and logistics data 513 is submitted to the blockchain, e.g., from the logistics provider to a logistics provider node.

[0176] In section 526, after the seller ships the products, the seller submits a bill of lading (B / L or BOL) to the trading platform, which can be a condition for final payment. The bill of lading can be an electronic bill of lading (eBOL). The trading platform submits the B / L to its nodes to store it on the blockchain.

[0177] At 539, the final payment conditions are met, which can be detected by the smart contract based on order status data. In response to determining that the final payment conditions are met, the smart contract triggers an automatic payment command to instruct the buyer's bank to make the final payment for the order to the seller. In some cases, if the buyer has not selected a bank payment credit service or the buyer's bank has rejected the bank payment credit application, at 538, the smart contract triggers an automatic AP command from the buyer's bank to make the final payment according to the trusted automatic payment service. In some cases, if the buyer's bank has approved the bank payment credit application, at 547, the smart contract triggers an automatic bank payment credit command to automatically instruct the buyer's bank to make the final payment for the order to the seller according to the trusted bank payment credit service.

[0178] At step 548, the buyer's bank pays the final payment according to the bank's payment credit service and submits the payment data at step 549 to the buyer's bank node that stores the payment data on the blockchain. At step 546, the seller's bank receives the final payment from the buyer's bank according to the bank's payment credit service and can submit the payment receipt data to the seller's bank node that stores the payment receipt data on the blockchain.

[0179] At 550, the buyer's bank can, for example, submit a payment success message to the trading platform via the buyer's bank node and the trading platform node. Alternatively, the trading platform node can generate a payment success message based on payment data and / or payment receipt data. At 527, the buyer confirms the delivery of the product on the trading platform. Thus, the buyer receives the product, and the seller receives payment. Processing 500 ends at 528.

[0180] Reference Figure 6 This illustrates another process 600 for implementing blockchain-based trusted trade services. In addition... Figure 5 In addition to the trusted automatic payment service and trusted bank payment credit service shown in process 500, process 600 shows the generation of trusted bank payment credit credentials and trusted bank payment credit financial services.

[0181] Processing 600 may include steps along line 630 related to order processing, steps along line 602 related to bank payment credit services, steps along line 604 related to the activities of the buyer's bank, and steps along line 606 related to the activities of the seller's bank.

[0182] At 631, processing begins at 600. For example, the buyer logs into their trade account on the trading platform. At 632, the buyer drafts an order to trade with the seller on the trading platform. At 610, the buyer selects a trusted bank payment credit service for at least one payment (e.g., the final payment of the order). At 633, the trading platform verifies the order, for example, after the buyer and seller confirm the order and the trading platform verifies that the buyer is eligible for a trusted automatic payment service guaranteed by the buyer's bank. In response to determining that the order is valid and the prepayment conditions are met, the smart contract automatically triggers the automatic payment request at 634 to instruct the buyer's bank to make the prepayment.

[0183] At 612, the trading platform initiates a bank payment credit application to the buyer's bank via a blockchain network (e.g., through trading platform nodes and buyer's bank nodes). At 614, the buyer's bank verifies, based on the buyer's credit and order data, whether the buyer is eligible for a trusted bank payment credit service for the order.

[0184] At step 616, the buyer's bank confirms that the buyer has passed the bank's payment credit verification and submits the verification data to the blockchain network, for example, to the buyer's bank node. The buyer's bank node then stores the verification data on the blockchain network's blockchain.

[0185] During the 618 shopping festival, buyer bank nodes or trading platform nodes generate trusted bank payment credit credentials, for example... Figure 9 The bank payment credit certificate 900. The bank payment credit certificate includes a payment amount guaranteed by the buyer's bank, and in response to the fulfillment of payment conditions specified in a smart contract deployed on the blockchain, the buyer's bank automatically makes the payment on behalf of the buyer. At 620, the seller submits a financing request, such as a loan, to the seller's bank 606 using the trusted bank payment credit certificate. At 622, the seller's bank approves the seller's financing request.

[0186] In section 635, the seller ships the ordered products. After the seller ships the ordered products, in section 636, the seller submits an invoice, for example, Figure 8 Invoice 800. On the trading platform, it can be a condition for final payment. The trading platform can submit the invoice to a trading platform node, which stores the invoice and associated order status data on the blockchain. At 637, a smart contract is executed to determine if the final payment condition has been met. At 624, an automatic command is automatically triggered, instructing the buyer's bank to pay the final payment according to the trusted bank's payment credit service.

[0187] At 626, based on the trusted bank payment credit service, the buyer's bank pays the final payment to the seller's financial account in the seller's bank. At 628, the seller or seller's bank can, for example, use the final payment received from the buyer's bank to repay financing. After paying the final payment based on the trusted bank payment credit service, the buyer's bank submits the payment data to the trading platform, for example, through the buyer's bank node and the trading platform node. At 629, the payment data confirms that the final payment has been successfully made to the seller. At 638, after the buyer confirms product delivery, processing 600 is completed at 640.

[0188] Reference Figure 7 This illustrates another process 700 for implementing blockchain-based trusted trade services. Similar to... Figure 5 For processing 500 and 700 transactions, trusted automatic payment services and trusted bank payment credit services can be applied. Trusted automatic payment services are a fundamental service of the trade platform, while bank payment credit services are optional. For example... Figure 7 As shown, the basic processing 710 is indicated by solid lines and includes steps shared by the automatic payment service and the bank payment credit service. The bank payment credit-only processing 750 is indicated by dashed lines and includes steps specific to the bank payment credit service.

[0189] Processing 700 may include steps along line 702 relating to the activities of the buyer, steps along line 704 relating to the activities of the buyer's bank, steps along line 706 relating to the activities of the seller, and steps along line 708 relating to the activities of the seller's bank.

[0190] At 712, the buyer logs into their trade account on the trading platform using a client device. At 714, the trading platform submits a verification request to the buyer's bank, for example, through the trading platform node and the buyer's bank node on the blockchain network. The verification request will ask the buyer's bank to verify whether the buyer is authorized to use the Trusted Automatic Payment Service and / or Know Your Customer (KYC) service. At 716, the buyer's bank performs verification based on the buyer's credit. At 720, the seller logs into their trade account on the trading platform and is verified by the trading platform using credential information. In some embodiments, the seller's trade account includes information about the seller's financial account in the seller's bank. At 722, the trading platform can verify whether the seller's financial account is valid.

[0191] After verifying the buyer's authorization to use the trusted automated payment service on the trading platform, at step 718, the trading platform allows the buyer to draft an order to trade with the seller. At step 724, the seller reviews and confirms the order. At step 752, after the buyer and seller confirm the order, the trading platform can determine that the buyer has selected a trusted bank payment credit service for the final payment of the order. The trading platform can submit the bank payment credit application to the buyer's bank through the trading platform node and the buyer's bank node. At step 752, the buyer's bank determines whether the buyer is eligible for the trusted bank payment credit service based on the buyer's creditworthiness. If the buyer is eligible, the bank payment credit service is approved. The buyer's bank can submit verification data to the blockchain network (e.g., the buyer's bank node). The buyer's bank node stores the verification data on the blockchain network's blockchain.

[0192] In 726, for example, in response to receiving an automated payment command generated by a smart contract on the blockchain, the buyer's bank pays an advance payment according to a trusted automated payment service. The smart contract triggers the automated payment command in response to determining that the advance payment conditions corresponding to the advance payment have been met.

[0193] At 728, the seller's bank receives the advance payment from the buyer's bank. If the seller's bank and the buyer's bank are offshore and domestic banks, respectively, the seller's bank receives foreign currency. After receiving the advance payment, at 730, the seller ships the ordered products. At 732, the buyer confirms the delivery of the products, which may be a condition for the final payment. At 754 and 756, the final payment may be made by a trusted automatic payment service or a trusted bank payment credit service.

[0194] In some cases, if the buyer does not select the bank payment credit service or the buyer's bank rejects the bank payment credit application, then at 734, the smart contract on the blockchain will trigger an automatic AP command from the buyer's bank to pay the final payment according to the trusted automatic payment service. In some cases, if the bank payment credit application is approved by the buyer's bank, then at 758, the smart contract will trigger an automatic bank payment credit command to automatically instruct the buyer's bank to pay the final payment of the order to the seller according to the trusted bank payment credit service.

[0195] At step 738, the seller's bank receives the final payment from the buyer's bank and collects the foreign currency. Processing step 700 ends after the seller's bank confirms receipt of the final payment.

[0196] Figure 10 , Figure 11 , Figure 12Examples of processes for implementing a blockchain-based trusted trading service, which can be executed according to the embodiments herein, are shown. Each process illustrates a complete order flow from start to finish. Orders are paid with an advance payment and a final payment with corresponding payment terms. The advance payment can be made via automatic initial payment (AIP) or manual initial payment (MIP) (if automatic initial payment fails). The final payment can be made via automatic remaining payment (ARP) or manual remaining payment (MRP) (if automatic remaining payment fails). Figure 5-7 As shown, automatic prepayment can be achieved through trusted automatic payment services, and automatic final payment can be achieved through trusted automatic payment services or trusted bank payment credit services.

[0197] Figure 10 , Figure 11 and Figure 12 The processing in can be, for example Figure 3 Implemented in an environment or system of a blockchain-based trusted trade and finance system 300, said environment or system including, for example... Figure 3 The blockchain network 320 and multiple participants, including, for example, Figure 3 310 trade platforms, for example Figure 3 Buyer bank 330, for example Figure 3 The seller's bank 340, for example Figure 3 Logistics providers of 350, such as Figure 3 Customs 360. A blockchain network can include multiple trusted nodes corresponding to multiple participants. Trading platforms, for example... Figure 3 Buyer 302 and, for example Figure 3 The trusted trading system provides trusted trading services between sellers 304. The buyer's bank provides financial services to the buyer, such as payment services. The seller's bank provides financial services to the seller, such as loans and deposits. In some embodiments, the trusted trading system includes a blockchain network 320 that can be coupled to different trading platforms. In some embodiments, the trusted trading system includes a blockchain network 320 and a trading platform.

[0198] Figure 10 This is a flowchart illustrating an example of a process 1000 for implementing a blockchain-based trusted trade service using various payment terms, which can be performed according to embodiments herein.

[0199] At 1002, processing begins at 1000. For example, the buyer can log into their trade account on the trading system using their client device. At 1004, the buyer drafts an order, for example, similar to... Figure 5 Step 522 Figure 6 632, or Figure 7 718. An order can include order terms and payment conditions. At 1006, after the buyer completes the order, the trading platform awaits order confirmation from the seller. At 1008, the trading platform sends a notification message as a seller event to the seller's client device to confirm the order.

[0200] In some cases, if the seller cancels the order at step 1016, the order is closed at step 1018. In some cases, if the trading platform does not receive confirmation from the seller after a predetermined period, the order is canceled at step 1016 and closed at step 1018. In some cases, at step 1010, the seller modifies the order and sends it to the trading system. At step 1012, the trading platform awaits confirmation of the modified order from the buyer. At step 1014, the trading platform sends a notification message to the buyer's client device as a buyer event to accept the modification. In some cases, at step 1016, if the buyer cancels the seller's modified order, the order is closed at step 1018. In some cases, at step 1020, if the buyer confirms the modified order, it indicates that the modified order has been confirmed by both the buyer and seller. At step 1022, if the seller confirms the order drafted by the buyer, it indicates that the order has been confirmed by both the buyer and seller. At step 1024, the trading platform records the confirmed order. The trading platform can, for example, submit the order data of the confirmed order on the blockchain of a blockchain network, similar to... Figure 5 Step 533.

[0201] Smart contracts can generate orders on the blockchain based on order data. These smart contracts may include automated functions that, in response to determining that payment conditions for the order have been met, automatically instruct the buyer's bank to make payment to the seller for the order using a payment service. The smart contract may also include order status update functions that automatically update the order status in response to determining that the order status has been changed based on order status data uploaded to the corresponding blockchain.

[0202] At 1026, the seller (or seller's bank) is awaiting prepayment from the buyer (or buyer's bank). At 1028, the seller can send a notification message as a buyer event to the buyer's client device to initiate Automatic Prepayment (AIP). In some cases, in response to determining that payment conditions deployed on the smart contract are met, the buyer's bank node can execute the smart contract to automatically instruct the buyer's bank to make a prepayment to the seller (or seller's bank) according to the AIP. At 1030, if the AIP fails, the order can be cancelled at 1034 and closed at 1018, or at 1032, the trading platform sends a notification message as a buyer event to the buyer's client device to make payment according to the manual prepayment service. In some cases, the buyer can request modifications to the order terms or conditions, which the seller can modify, and the buyer can agree again at 1036.

[0203] If the automatic prepayment is successful at step 1038, or if the automatic prepayment fails but the manual prepayment is successful, then at step 1040, the trading system is waiting for the seller to ship the ordered products. At step 1042, the trading system can send a notification message as a seller event to the seller's client device to arrange shipment. At step 1044, the products are shipped by the seller, and logistics and customs information can be uploaded to the blockchain by the relevant logistics provider and customs.

[0204] At 1046, the trade system records the shipment data – “Shipment has begun” – on the blockchain and sends a notification message 1048 to the buyer's client device as a buyer event. At 1050, the logistics provider can submit the shipment completion data to the blockchain, or customs can submit customs data indicating that the product has passed inspection.

[0205] The final payment can have various payment terms. If the payment term is an invoice type, and the buyer needs to confirm at step 1056, then at step 1058, the trading system is waiting for the buyer to confirm the invoice. The trading system can send a notification message 1060, as a buyer event, to the buyer's client device to confirm the invoice. After the buyer confirms the invoice at step 1062, at step 1054, the trading system waits for the buyer's bank to pay the final payment, for example, by executing a smart contract to automatically instruct the buyer's bank to pay the final payment according to the automatic final payment service.

[0206] In some embodiments, the payment terms for the final payment are of the electronic bill of lading (eBOL) type (1064). At 1066, the trading system waits for the seller to upload the eBOL and may send a notification message 1068 to the seller's seller client device. If the payment terms are that the seller has submitted the eBOL but there has been no buyer confirmation (1070), then process 1000 proceeds to step 1054. If the payment terms are that the eBOL is submitted along with buyer confirmation (1072), then at 1074 the trading system waits for buyer confirmation of the eBOL and sends a notification message 1076 requesting buyer confirmation of the eBOL. At 1078, after the buyer confirms the eBOL, process 1000 proceeds to step 1054.

[0207] In some embodiments, the payment terms for the final payment are an invoice type that does not require buyer confirmation (1052), and processing 1000 proceeds directly from 1050 to 1054, i.e., waiting for the final payment.

[0208] The trading system can send a notification message 1080, as a buyer event, to the buyer's bank or the buyer's client device to request final payment according to the automatic final payment. At 1082, if the automatic final payment fails, the trading system can send a notification message 1084 to the buyer's bank or the buyer's client device to request final payment according to the manual final payment. At 1086, if the automatic final payment succeeds, or if the automatic final payment fails but the manual final payment succeeds, at 1088, the trading system awaits delivery confirmation. The trading system can send a notification message 1090, as a buyer event, to the buyer's client device to confirm product delivery. At 1092, after the buyer confirms delivery, the order is completed at 1094.

[0209] Figure 11 This is a flowchart illustrating an example of a process 1100 for implementing a blockchain-based trusted trade service using consensus payment conditions, which can be performed according to embodiments herein.

[0210] At 11:02, processing begins at 11:00. At 11:04, the buyer drafts an order on the trading platform. After the order is completed, at 11:06, the trading system waits for the seller's confirmation and sends a notification message at 11:08 requesting the seller's confirmation. At 11:22, if the seller confirms the order, it indicates that the order has been confirmed by both the buyer and seller, and at 11:24, the order is recorded.

[0211] If the seller cancels the order at 11:16, the order is closed at 11:18. If the seller modifies the order at 11:10, the trading platform waits for the buyer's confirmation of the modified order at 11:12 and can send a notification message at 11:14 requesting the buyer to accept the modification. If the buyer cancels the modified order at 11:16, the order is closed at 11:18. If the buyer confirms the modified order at 11:20, it indicates that the modified order has been confirmed by both the buyer and the seller, and the modified order is recorded at 11:24.

[0212] The prepayment is conditional upon the recording of the order. For example, after the order is recorded on the blockchain of the blockchain network, the trading system awaits the prepayment at 1126. If the automatic prepayment fails at 1130, the prepayment can be modified at 1128, and the trading system can notify the buyer to pay the prepayment according to the manual prepayment. If the automatic prepayment succeeds at 1132, or if the automatic prepayment fails but the manual prepayment succeeds, the trading system awaits the buyer's bank or the buyer's final payment at 1134.

[0213] If the payment terms are agreed upon by the buyer and seller (1136), and both automatic and manual final payments are successful, the trade system waits for the seller to ship the products at 1138. At 1144, the products are shipped, and logistics and customs information can be uploaded to the trade system by the logistics provider and customs. At 1146, the trade system can determine the start of shipment based on the order status data. At 1148, after shipment is completed and cleared through customs, the trade system waits for delivery confirmation at 1150. At 1152, the trade system receives delivery confirmation from the buyer, and at 1154, the order is completed.

[0214] Figure 12 An embodiment according to this article is shown. Figure 10 and Figure 11 Figure 1200 shows the steps in the processing. Box 1210 shows different icons representing different meanings. Icon 1212 represents the initial condition, icon 1214 represents the external condition of the blockchain, icon 1216 represents the condition on the blockchain, icon 1218 represents the ending condition, icon 1220 represents the notification message as a buyer event, and icon 1222 represents the notification message as a seller event.

[0215] Box 1230 illustrates how conditions are modified. At 1232, the trading system allows modification of the conditions. At 1234, the buyer submits a modification request, and at 1236 the trading system awaits the seller's modification, sending a notification message to the seller in 1238. If this condition is not needed, the trading system can still display the previous conditions. At 1240, the seller makes the modification, and at 1242 the trading system awaits the buyer's confirmation of the modified order. At 1248, the trading system sends a notification message as a buyer event, requesting the buyer to accept the modification. At 1244, if the buyer refuses to confirm the modified order, processing returns to step 1232. At 1246, if the buyer confirms the modified order, processing returns to step 1232.

[0216] Box 1250 illustrates the status change used to notify of successful payment. At 1252, the payment status is in status 1. At 1256, after successful payment of the prepayment under automatic or manual prepayment, or the balance under automatic or manual balance, the payment status changes to status 2 (1254). The trading system sends notification message 1258 as a seller event to notify the seller of successful payment, and sends notification message 1260 as a buyer event to notify the buyer of successful payment.

[0217] Figure 13A This is a flowchart illustrating an example of a process 1300 for managing a blockchain-based trusted transaction service according to embodiments of this document. This blockchain-based trusted trading service can be provided by a blockchain-based trusted trading and financial system (e.g., Figure 3 The blockchain-based trusted trading and financial system (300) is executed. The blockchain-based trusted trading and financial system may include a blockchain network. The blockchain network may be a public blockchain network, a private blockchain network, or a consortium blockchain network. In some embodiments, the blockchain network may be... Figure 1 Blockchain network 102, Figure 2 Blockchain network 212, or Figure 3A blockchain network 320. The blockchain network may include multiple trusted nodes. Each trusted node may correspond to a corresponding participant in a trade within a blockchain-based trusted trading and financial system. In some embodiments, one or more steps of process 1300 may be performed by trusted network nodes of the blockchain network (e.g., trading platform node 321, buyer bank node 322, or seller bank node 324). In some embodiments, one or more steps of process 1300 may be performed by computing devices connected to trusted network nodes of the blockchain network (e.g., the computing devices of trading platform 310, buyer bank 330, or seller bank node 324). In some embodiments, one or more steps of process 1300 may be performed by a combination or integration of trusted network nodes of the blockchain network (e.g., trading platform node 321) and computing devices connected to trusted network nodes of the blockchain network (e.g., trading platform 310). In some embodiments, one or more steps of process 1300 may be performed according to the techniques described with respect to processes 500, 600, 700, 1000, 1100, and / or 1200.

[0218] In 1302, the buyer (e.g., Figure 3 Buyer 302) and seller (e.g., Figure 3 The order data for orders between sellers (304) is stored on the blockchain of the blockchain network for that order. The order data includes one or more payment terms for the order. The order data may be generated by a platform corresponding to the trading platform (e.g., [the platform]). Figure 3 Trusted trading platform nodes (e.g., trading platform 310) Figure 3 Node 321) storage. The trading platform is configured to provide trusted blockchain-based trading services between buyers and sellers. After buyers and sellers confirm orders on the trading platform, the order data can be stored on the blockchain.

[0219] In 1304, it is verified that the buyer has a financial institution (e.g., the buyer's financial institution) Figure 3 The Trusted Automatic Payment (AP) service is guaranteed by the buyer's financial institution (330). The Trusted Automatic Payment service is guaranteed by the buyer's financial institution and automatically makes payments on behalf of the buyer in response to the fulfillment of conditions specified in a smart contract deployed on a blockchain network. Each order can correspond to a specific smart contract. Each order can have one or more payment orders with one or more corresponding payment conditions. Each order can correspond to a specific blockchain within the blockchain network.

[0220] Having a reliable automated payment service can be a basic requirement for using a trading platform. After the buyer logs into their trading account on the trading platform, the trading platform node can connect with the buyer's financial institution node corresponding to the buyer's financial institution (e.g., Figure 3The trading platform communicates with node 322 to verify whether the buyer's financial account within the buyer's financial institution is eligible for the trusted automatic payment service on the trading platform. The buyer's financial institution node can communicate with the computing device of the buyer's financial institution to verify that the buyer has the trusted automatic payment service guaranteed by the buyer's financial institution. The buyer's trading account may include information such as the buyer's financial account number, buyer's name, and the name of the buyer's financial institution. The trading platform can be configured to allow the buyer to draft orders or view orders prepared by the seller on the trading platform in response to determining that the buyer's financial account is eligible for the trusted automatic payment service.

[0221] The seller also has a seller trading account on the trading platform and a seller financial account in the seller's financial institution. The blockchain network may include seller financial institution nodes corresponding to the seller's financial institution. The buyer's financial institution can make payments to the seller's financial account in the seller's financial institution on behalf of the buyer. In some embodiments, one of the buyer's financial institution and the seller's financial institution is an offshore entity, and the other is an onshore entity. The offshore and onshore entities are subject to different financial regulations, and the buyer's financial institution node corresponding to the buyer's financial institution and the seller's financial institution node corresponding to the seller's financial institution belong to the same blockchain network of multiple trusted nodes.

[0222] In step 1306, a corresponding smart contract for the order is generated on the blockchain based on order data. The corresponding smart contract may include an automated function that, in response to determining that the corresponding payment conditions for the order payment are met, automatically instructs the buyer's financial institution to make order payment to the seller for the order according to a trusted automated payment service. In some embodiments, a trading platform node is configured to generate the corresponding smart contract for the order based on order data according to a smart contract template, which includes multiple functions for trusted trading services. When generating the corresponding smart contract for the order, the trading platform node may be configured to call one or more functions from the multiple functions in the smart contract template, using the order data as input to one or more of the multiple functions in the smart contract template.

[0223] At 1308, order status data is received and uploaded to the blockchain. Each node in the blockchain network can receive corresponding order status data uploaded by the relevant participants. Order status data may include at least one of the following: from, for example... Figure 3 Logistics data sent from 350 logistics providers to logistics provider nodes, supply chain data from supply chain service companies, and data from sources such as... Figure 3 Customs 360 sends to such Figure 3Customs data from node 328, bill of lading data sent from the trade platform to the trade platform node, or payment data sent from the buyer's financial institution to the buyer's financial institution node and / or payment data sent from the seller's financial institution to the seller's financial institution node.

[0224] The corresponding smart contract also includes an order status update function, which automatically updates the order status in response to a change in the order status determined based on order status data uploaded to the corresponding blockchain. The order status can indicate at least one of the following: the product associated with the order has been prepared or shipped by the seller; the product has been inspected by customs; the product is being transported by a logistics provider; the bill of lading associated with the order has been submitted by the seller on a trading platform; the submitted bill of lading has been confirmed by the buyer on a trading platform; the invoice associated with the order has been generated by the blockchain network; the generated invoice has been confirmed by the buyer; the buyer and seller have reached a consensus on the order; the buyer's financial institution has made the automatic payment; the seller's financial institution has received the automatic payment; or the buyer has received the product.

[0225] At 1310, in response to determining that the corresponding payment conditions for order payment have been met based on order status data, the corresponding smart contract is executed to automatically instruct the buyer's financial institution's computing device to make order payment to the seller according to the trusted automatic payment service. In response to determining that the corresponding payment conditions for order payment have been met, the corresponding smart contract can automatically generate or trigger an automatic payment command. The buyer's financial institution node can send the automatic payment command to the buyer's financial institution's computing device, which instructs the buyer's financial institution's computing device to make order payment to the seller according to the trusted automatic payment service. In some embodiments, in response to determining that a predetermined time has elapsed or a predetermined time period has passed after the corresponding payment conditions for order payment have been met, the corresponding smart contract generates the automatic payment command.

[0226] The buyer's financial institution node can be configured to execute a smart contract in response to the determination that the corresponding payment conditions for order payment have been met, so as to automatically instruct the buyer's financial institution's computing device to make order payment directly to the seller's financial account in the seller's financial institution without going through the trading platform.

[0227] In some embodiments, one or more payment conditions include a first payment condition for a first payment of the order and a second payment condition for a second payment of the order. The buyer's financial institution node can be configured to: in response to determining that the first payment condition for the first payment is met, execute a corresponding smart contract to automatically instruct the buyer's financial institution's computing device to make a first payment to the seller; and in response to determining that the second payment condition for the second payment is met, execute a corresponding smart contract to automatically instruct the buyer's financial institution's computing device to make a second payment to the seller.

[0228] In some embodiments, the first payment is an advance payment for the order, and the first payment condition includes that the order has been verified on the trading platform. The second payment is the final payment for the order, and the second payment condition may include at least one of the following: the bill of lading associated with the order has been submitted by the seller on the trading platform; the submitted bill of lading has been confirmed by the buyer on the trading platform; the invoice associated with the order has been generated by the blockchain network; the generated invoice has been confirmed by the buyer; or the buyer and seller have reached a consensus on the order.

[0229] In some embodiments, order payments can be made via wire transfer between the buyer's financial institution and the seller's financial institution. The wire transfer can be a whale transfer or a SWIFT transfer. In some embodiments, order payments can be made in digital currency. In response to receiving an automatic payment command, the buyer's financial institution can, for example, transfer the digital value corresponding to the order payment to the seller's financial institution through buyer's financial institution nodes and seller's financial institution nodes or any other blockchain network.

[0230] Buyer financial institution nodes can be configured to receive order payment data, confirming that the buyer financial institution has made payment to the seller, and store this order payment data on the blockchain. Seller financial institution nodes can be configured to store payment receipt data on the corresponding blockchain, confirming that the seller's financial account in the seller financial institution has received the order payment from the buyer financial institution. The trading platform can be configured to receive order payment data from the corresponding blockchain through trading platform nodes and, based on this order payment data, provide payment status feedback to both the buyer and seller.

[0231] Figure 13B This is a flowchart illustrating an example of a process 1330 for managing a blockchain-based trusted transaction service executed according to embodiments of this document. This blockchain-based trusted trading service can be provided by a blockchain-based trusted trading and financial system (e.g., Figure 3 The blockchain-based trusted trading and financial system (300) is executed. The blockchain-based trusted trading and financial system may include a blockchain network. This blockchain network may be a public blockchain network, a private blockchain network, or a consortium blockchain network. In some embodiments, the blockchain network may be... Figure 1 Blockchain network 102, Figure 2 Blockchain network 212, or Figure 3A blockchain network 320. The blockchain network may include multiple trusted nodes. Each trusted node may correspond to a corresponding participant in a trade within a blockchain-based trusted trading and financial system. In some embodiments, one or more steps of process 1330 may be performed by trusted network nodes of the blockchain network (e.g., trading platform node 321, buyer bank node 322, or seller bank node 324). In some embodiments, one or more steps of process 1330 may be performed by computing devices connected to trusted network nodes of the blockchain network (e.g., the computing devices of trading platform 310, buyer bank 330, or seller bank node 324). In some embodiments, one or more steps of process 1330 may be performed by a combination or integration of trusted network nodes of the blockchain network (e.g., trading platform node 321) and computing devices connected to trusted network nodes of the blockchain network (e.g., trading platform 310). In some embodiments, one or more steps of process 1330 may be performed according to the techniques described with respect to processes 500, 600, 700, 1000, 1100, and / or 1200.

[0232] In 1332, order data for an order between a buyer and seller is stored on the blockchain of the blockchain network for that order. Order data includes one or more payment terms for the order, as well as data regarding the Trusted Trade Provider (TU) service for that order. Order data can be stored by a Trusted Trade Platform node corresponding to the trade platform. The trade platform is configured to provide blockchain-based trusted trade services between buyers and sellers. After the buyer and seller confirm the order on the trade platform, the order data can be stored on the blockchain.

[0233] In 1334, it is verified that the buyer has a Trusted Credit (TU) service for the order guaranteed by the buyer's financial institution. In response to the fulfillment of the conditions specified in the smart contract deployed on the blockchain, the Trusted Credit (TU) service for the order automatically makes payment to the seller for the order on behalf of the buyer based on the buyer's credit in the buyer's financial institution.

[0234] In some embodiments, the trade platform node is configured to: determine, based on trusted credit data, that the buyer has chosen to use the trusted credit service for an order on the trade platform, and send a request to the buyer's financial institution's computing device via the buyer's financial institution node, the request requesting the buyer's financial institution to verify whether the buyer is eligible for the trusted credit service guaranteed by the buyer's financial institution for the order.

[0235] In some embodiments, the trading platform is configured to provide a user interface for receiving user input for order data, and the user interface includes the option to use the corresponding trusted credit service for the order.

[0236] In some embodiments, the trading platform node is configured to send a request after the order data of the order is stored on the blockchain.

[0237] In some embodiments, the blockchain network includes a buyer financial institution node corresponding to the buyer's financial institution. The buyer financial institution node is configured to: receive verification data from the buyer financial institution's computing device, confirming that the buyer has trusted credit services for the order guaranteed by the buyer financial institution, and store the verification data on the corresponding blockchain.

[0238] In some embodiments, the trading platform is configured to: determine, based on verification data stored on a blockchain, that the buyer has a trusted credit line for the order guaranteed by the buyer's financial institution, and verify the order after determining that the buyer has a trusted credit line for the order guaranteed by the buyer's financial institution.

[0239] In some embodiments, the appropriate payment terms for order payment are determined based on the trusted credit service of the order.

[0240] In 1336, a smart contract for the order is generated based on the order data, and the smart contract includes an automatic function that, in response to determining that the corresponding payment conditions for order payment are met, automatically instructs the buyer's financial institution to make order payment to the seller for the order based on the order's trusted credit service. In some embodiments, a trading platform node is configured to generate a corresponding smart contract for the order based on the order data according to a smart contract template, the smart contract template including multiple functions for trusted trading services. When generating the corresponding smart contract for the order, the trading platform node can be configured to call one or more functions of the multiple functions in the smart contract template, using the order data as input to one or more functions of the multiple functions in the smart contract template.

[0241] At 1338, order status data of orders uploaded to the blockchain is received. In some embodiments, the smart contract also includes an order status update function that automatically updates the order status in response to determining, based on the order status data uploaded to the corresponding blockchain, that the order status has been changed.

[0242] In some embodiments, the status of an order indicates at least one of the following: the product associated with the order has been prepared or shipped by the seller; the product has been inspected by customs; the product is being transported by a logistics provider; the bill of lading associated with the order has been submitted by the seller on a trading platform; the submitted bill of lading has been confirmed by the buyer on a trading platform; the invoice associated with the order has been generated by a blockchain network; the generated invoice has been confirmed by the buyer; the buyer and seller have reached a consensus on the order; the buyer's financial institution has made the automatic payment; the seller's financial institution has received the automatic payment; or the buyer has received the product.

[0243] In some embodiments, the blockchain network of the plurality of trusted nodes further includes at least one of the following: a customs node corresponding to customs, wherein the order status data includes customs data uploaded by the customs node to the corresponding blockchain; or a logistics provider node corresponding to at least one logistics provider, wherein the order status data includes logistics data uploaded by the logistics provider node to the corresponding blockchain.

[0244] In some embodiments, order status data includes at least one of logistics data, supply chain data, customs data, bill of lading data, or payment data.

[0245] At 1340, in response to the determination based on order status data that the corresponding payment conditions for order payment have been met, a smart contract is executed to automatically instruct the buyer's financial institution's computing device to make payment for the order to the seller based on a trusted credit service.

[0246] In some embodiments, the blockchain network includes a buyer financial institution node corresponding to the buyer's financial institution. The buyer financial institution node is configured to: receive order payment data confirming that the buyer financial institution has successfully made order payment to the seller based on the order's trusted credit service, and store the order payment data on the blockchain.

[0247] In some embodiments, the blockchain network includes a seller financial institution node corresponding to the seller's financial institution. The seller has a seller financial account in the seller financial institution, and the seller financial institution node is configured to store payment receipt data on the corresponding blockchain, the payment receipt data confirming that the seller financial institution has received order payment for the order from the buyer's financial institution.

[0248] In some embodiments, the buyer's financial institution node is configured to execute a smart contract in response to determining that a predetermined time has been reached or a predetermined time period has elapsed after the corresponding payment conditions for order payment have been met, to automatically instruct the buyer's financial institution's computing device to make order payment to the seller based on the order's trusted credit service.

[0249] In some embodiments, the scheduled time or scheduled time period is determined based on the corresponding trusted credit service of the order.

[0250] In some embodiments, one or more payment terms include first payment terms for a first payment of the order and second payment terms for a second payment of the order. The second payment is an order payment made under the trusted credit service of the order, and the second payment terms include corresponding payment conditions. The buyer's financial institution node is configured to: in response to determining that the second payment terms for the second payment are met, execute a smart contract to automatically instruct the buyer's financial institution's computing device to make the second payment to the seller under the trusted credit service of the order.

[0251] In some embodiments, the buyer financial institution node is configured to: in response to determining that the first payment conditions for the first payment are met, execute a smart contract to automatically instruct the buyer financial institution's computing device to make the first payment to the seller based on the buyer's trusted automatic payment service provided by the buyer financial institution.

[0252] In some embodiments, the trade platform node is configured to: after the buyer logs into the buyer's trade account on the trade platform, communicate with the computing device of the buyer's financial institution through the buyer's financial institution node to verify whether the buyer's financial account in the buyer's financial institution is eligible for trusted automatic payment services, wherein the buyer's trade account includes information about the buyer's financial account.

[0253] In some embodiments, the first payment is an advance payment for the order, and the first payment condition includes verification of the order. The second payment is the final payment for the order, and the second payment condition may include at least one of the following: the bill of lading associated with the order has been submitted by the seller on the trading platform; the submitted bill of lading has been confirmed by the buyer on the trading platform; the invoice associated with the order has been generated by the blockchain network; the generated invoice has been confirmed by the buyer; or the buyer and seller have reached a consensus on the order.

[0254] Figure 13C This is a flowchart illustrating an example of a process 1350 for managing a blockchain-based transaction service executed according to embodiments of this document. This blockchain-based trading service can be provided by a blockchain-based trusted trading and financial system (e.g., Figure 3 The blockchain-based trusted trading and financial system (300) is executed. The blockchain-based trusted trading and financial system may include a blockchain network. This blockchain network may be a public blockchain network, a private blockchain network, or a consortium blockchain network. In some embodiments, the blockchain network may be... Figure 1 Blockchain network 102, Figure 2 Blockchain network 212, or Figure 3A blockchain network 320. The blockchain network may include multiple trusted nodes. Each trusted node may correspond to a corresponding participant in a trade within a blockchain-based trusted trading and financial system. In some embodiments, one or more steps of process 1350 may be performed by trusted network nodes of the blockchain network (e.g., trading platform node 321, buyer bank node 322, or seller bank node 324). In some embodiments, one or more steps of process 1350 may be performed by computing devices connected to trusted network nodes of the blockchain network (e.g., the computing devices of trading platform 310, buyer bank 330, or seller bank node 324). In some embodiments, one or more steps of process 1350 may be performed by a combination or integration of trusted network nodes of the blockchain network (e.g., trading platform node 321) and computing devices connected to trusted network nodes of the blockchain network (e.g., trading platform 310). In some embodiments, one or more steps of process 1350 may be performed according to the techniques described with respect to processes 500, 600, 700, 1000, 1100, and / or 1200.

[0255] In 1352, order data for an order between a buyer and seller is stored on the blockchain of the blockchain network for that order. Order data includes one or more payment terms for the order, as well as data regarding the Trusted Trust (TU) service for the order. Order data can be stored by Trusted Trade Platform nodes corresponding to the trading platform. The trading platform is configured to provide blockchain-based Trusted Trade services between buyers and sellers. After the buyer and seller confirm the order on the trading platform, the order data can be stored on the blockchain. The Trusted Trust service for the order is guaranteed by the buyer's financial institution. In response to the fulfillment of conditions specified in a smart contract deployed on the blockchain, the buyer's financial institution automatically makes payments on behalf of the buyer to the seller's associated financial institution based on the buyer's credit within the buyer's financial institution.

[0256] Multiple trusted nodes can include trade platform nodes corresponding to a trade platform. Multiple trusted nodes can include buyer financial institution nodes corresponding to buyer financial institutions. Multiple trusted nodes can include seller financial institution nodes corresponding to seller financial institutions.

[0257] In some embodiments, one of the buyer's financial institution and the seller's financial institution is an offshore entity, and the other is an onshore entity. The offshore and onshore entities are subject to different financial regulations, and the buyer's financial institution node corresponding to the buyer's financial institution and the seller's financial institution node corresponding to the seller's financial institution belong to the same blockchain network of multiple trusted nodes.

[0258] In step 1354, a trusted credit credential is generated based on order data including trusted credit data. In some embodiments, the trusted credit credential includes at least one of the following: an identifier of the trusted credit credential; the validity period of the trusted credit credential; the corresponding payment terms for the order payment; order information, including at least one of order identifier, total order cost, or product information; order logistics information, including at least one of transportation method, trade terms, transportation cost, or transportation insurance cost; buyer and seller information; buyer's financial institution and seller's financial institution information; or information of the buyer's financial account in the buyer's financial institution and information of the seller's financial account in the seller's financial institution.

[0259] In 1356, the trusted credentials for the order are stored on the blockchain.

[0260] In some embodiments, the trading platform node is configured to: verify, via the buyer's financial institution node and utilizing the buyer's financial institution's computing equipment, whether the buyer has authorization for a trusted credit service for the order on the trading platform. In some embodiments, in response to verifying that the buyer has authorization for a corresponding trusted credit service for the order guaranteed by the buyer's financial institution, a trusted credit certificate for the order is generated on the blockchain.

[0261] In some embodiments, the trade platform node is configured to submit a verification request with a trusted credit credential to the buyer financial institution's computing device via the buyer financial institution node, and the buyer financial institution is configured to verify, based on the trusted credit credential, whether the buyer has authorization for the corresponding trusted credit service for the order.

[0262] In some embodiments, a trade platform node is configured to send a verification message to the trade platform confirming that the buyer has authorization for the corresponding trusted credit service for the order, in response to verifying that the buyer has authorization for the corresponding trusted credit service for the order guaranteed by the buyer's financial institution.

[0263] In some embodiments, the trading platform is configured to verify an order after receiving a verification message from a trading platform node.

[0264] In some embodiments, a trading platform node is configured to send a verification request after storing the order data of an order on the blockchain.

[0265] In some embodiments, the corresponding payment terms are determined based on the corresponding trusted credit service of the order.

[0266] At 1358, a trusted credit credential is sent to the seller's financial institution's computing device to determine whether to approve the seller's financing request based on the trusted credit credential.

[0267] In some embodiments, the seller financial institution node is configured to: receive approval data from the seller financial institution's computing device, the approval data indicating that the seller financial institution has approved the seller's financing request for the financing amount based on the trusted credit certificate, and store the approval data on a blockchain, wherein the approval data references the trusted credit certificate.

[0268] In some embodiments, the seller financial institution node is configured to: receive financing payment data from the seller financial institution's computing device, the financing payment data confirming that the financing amount associated with the financing request has been paid by the seller financial account of the seller financial institution, and store the financing payment data on a blockchain.

[0269] In some embodiments, the seller financial institution node is configured to: receive payment receipt data from the seller financial institution's computing device, the payment receipt data confirming that the seller financial account in the seller financial institution has received the order payment for the order from the buyer financial institution, and store the payment receipt data on a blockchain.

[0270] In some embodiments, the trade platform node is configured to generate a corresponding smart contract for the order based on the order data. This corresponding smart contract includes an automatic function that, in response to determining that the corresponding payment conditions for the order payment have been met, automatically instructs the buyer's financial institution to make order payment to the seller for the order based on the order's trusted credit service.

[0271] In some embodiments, the buyer's financial institution node is configured to: in response to determining that the corresponding payment conditions for order payment have been met, execute the corresponding smart contract to automatically instruct the buyer's financial institution's computing device to make order payment to the seller based on the order's trusted credit service.

[0272] In some embodiments, the buyer financial institution node is configured to: in response to determining that the corresponding payment conditions for order payment are met, execute a corresponding smart contract to generate an automatic payment command, which instructs the buyer financial institution's computing device to make order payment to the seller based on the corresponding trusted credit service of the order; and send the automatic payment command to the buyer financial institution's computing device.

[0273] In some embodiments, the blockchain network is configured to: in response to determining that a predetermined time has been reached or a predetermined time period has elapsed after the corresponding payment conditions have been met, execute the corresponding smart contract to automatically instruct the buyer's financial institution's computing device to make order payment to the seller based on the corresponding trusted credit service of the order.

[0274] In some embodiments, the scheduled time or scheduled time period is determined based on the trusted credit service of the order.

[0275] In some embodiments, one or more payment terms include first payment terms for a first payment of the order and second payment terms for a second payment of the order. The second payment is an order payment made under a trusted credit service for the order, and the second payment terms include corresponding payment conditions.

[0276] In some embodiments, the buyer's financial institution node is configured to: in response to determining that the first payment condition for the first payment is met, execute a corresponding smart contract to automatically instruct the buyer's financial institution's computing device to make a first payment to the seller based on the buyer's trusted automatic payment service provided by the buyer's financial institution; and in response to determining that the second payment condition for the second payment is met, execute a corresponding smart contract to automatically instruct the buyer's financial institution's computing device to make a second payment to the seller based on the corresponding trusted credit service of the order.

[0277] In some embodiments, the first payment is an advance payment for the order, and the first payment condition includes verification of the order. The second payment is the final payment for the order, and the second payment condition may include at least one of the following: the bill of lading associated with the order has been submitted by the seller on the trading platform; the submitted bill of lading has been confirmed by the buyer on the trading platform; the invoice associated with the order has been generated by the blockchain network; the generated invoice has been confirmed by the buyer; or the buyer and seller have reached a consensus on the order.

[0278] In some embodiments, the trade platform node is configured to: after the buyer logs into the buyer's trade account on the trade platform, communicate with the computing device of the buyer's financial institution through the buyer's financial institution node to verify whether the buyer's financial account in the buyer's financial institution is eligible for trusted automatic payment services, wherein the buyer's trade account includes information about the buyer's financial account.

[0279] In some embodiments, the corresponding smart contract further includes an order status update function that automatically updates the order status in response to determining that the order status has been changed based on order status data uploaded to the corresponding blockchain.

[0280] In some embodiments, the status of an order indicates at least one of the following: the product associated with the order has been prepared or shipped by the seller; the product has been inspected by customs; the product is being transported by at least one logistics provider; the bill of lading associated with the order has been submitted by the seller on a trading platform; the submitted bill of lading has been confirmed by the buyer on a trading platform; the invoice associated with the order has been generated by a blockchain network; the generated invoice has been confirmed by the buyer; the buyer and seller have reached a consensus on the order; the buyer's financial institution has made the automatic payment; the seller's financial institution has received the automatic payment; or the buyer has received the product.

[0281] In some embodiments, the blockchain network of the plurality of trusted nodes further includes at least one of the following: a customs node corresponding to customs, wherein the order status data includes customs data uploaded by the customs node to the corresponding blockchain; or a logistics provider node corresponding to at least one logistics provider, wherein the order status data includes logistics data uploaded by the logistics provider node to the corresponding blockchain.

[0282] In some embodiments, order status data includes at least one of logistics data, supply chain data, customs data, bill of lading data, or payment data.

[0283] Figure 14A An example of a module of apparatus 1400 according to an embodiment of this document is shown. Apparatus 1400 may be an example of an embodiment configured to manage a blockchain-based trusted trading service. The apparatus 1400 may correspond to the foregoing embodiments, and the apparatus 1400 includes the following: a storage module 1402, which stores the order data of the order between the buyer and seller on a blockchain network for the order after the buyer and seller confirm the order on the trading platform, the order data including one or more payment terms of the order; a verification module 1404, which verifies that the buyer has a trusted automatic payment service guaranteed by the buyer's financial institution, and automatically makes payment on behalf of the buyer in response to the satisfaction of the conditions specified in the smart contract deployed on the blockchain network; a generation module 1406, which generates a corresponding smart contract for the order based on the order data, the corresponding smart contract including an automatic function that automatically instructs the buyer's financial institution to make order payment to the seller for the order in response to determining that the corresponding payment conditions for order payment are satisfied; a receiving module 1408, which receives the order status data of the order uploaded to the blockchain; and an execution module 1410, which executes the corresponding smart contract in response to determining that the corresponding payment conditions for order payment are satisfied based on the order status data, to automatically instruct the computing device of the buyer's financial institution to make order payment to the seller according to the trusted automatic payment service.

[0284] In some embodiments, the apparatus 1400 includes a buyer financial institution node corresponding to the buyer financial institution. The buyer financial institution node is configured to communicate with the computing device of the buyer financial institution to verify that the buyer has a trusted automated payment service guaranteed by the buyer financial institution, and to execute the corresponding smart contract.

[0285] In some embodiments, the buyer's financial institution node is configured to: receive order payment data that confirms the buyer's financial institution has made order payment to the seller, and store the order payment data on the blockchain.

[0286] In some embodiments, the trading platform is configured to: receive order payment data from the corresponding blockchain; and provide feedback on the payment status to the buyer and seller based on the order payment data.

[0287] In some embodiments, the buyer's financial institution node is configured to: in response to determining that a predetermined time has been reached or a predetermined time period has elapsed after the corresponding payment conditions for order payment have been met, execute the corresponding smart contract to automatically instruct the buyer's financial institution's computing device to make order payment to the seller.

[0288] In some embodiments, the buyer financial institution node is configured to: in response to determining that the corresponding payment conditions for order payment are met, execute a corresponding smart contract to generate an automatic payment command; and send the automatic payment command to the buyer financial institution's computing device, which instructs the buyer financial institution's computing device to make order payment to the seller in accordance with a trusted payment service.

[0289] In some embodiments, the buyer's financial institution node is configured to store order payment data on the corresponding blockchain, which confirms that the buyer's financial institution has made order payment to the seller.

[0290] In some embodiments, the buyer has a buyer financial account in a buyer's financial institution, and the seller has a seller financial account in a seller's financial institution. The buyer's financial institution node is configured to: in response to determining that the corresponding payment conditions for order payment have been met, execute the corresponding smart contract to automatically instruct the buyer's financial institution's computing device to make order payment directly to the seller's financial account in the seller's financial institution without going through the trading platform.

[0291] In some embodiments, the apparatus 1400 includes a seller financial institution node corresponding to the seller financial institution.

[0292] In some embodiments, one of the buyer's financial institution and the seller's financial institution is an offshore entity, and the other is an onshore entity. The offshore and onshore entities are subject to different financial regulations, and the buyer's financial institution node corresponding to the buyer's financial institution and the seller's financial institution node corresponding to the seller's financial institution belong to the same blockchain network of multiple trusted nodes.

[0293] In some embodiments, the buyer financial institution is configured to transfer the digital value corresponding to the order payment to the seller financial institution in response to an automatic payment command.

[0294] In some embodiments, the seller financial institution node is configured to store payment receipt data on a corresponding blockchain, the payment receipt data confirming that the seller financial account in the seller financial institution has received the order payment for the order from the buyer financial institution.

[0295] In some embodiments, the apparatus 1400 includes a trade platform node corresponding to a trade platform.

[0296] In some embodiments, a trading platform node is configured to generate a corresponding smart contract for an order based on order data according to a smart contract template, the smart contract template including multiple functions for trusted trading services, and when generating the corresponding smart contract for an order, the trading platform node can be configured to call one or more of the multiple functions in the smart contract template and use the order data as input to one or more of the multiple functions in the smart contract template.

[0297] In some embodiments, the trade platform node is configured to communicate with the node of the buyer's financial institution after the buyer logs into the buyer's trade account on the trade platform to verify whether the buyer's buyer financial account in the buyer's financial institution is eligible for the trusted automatic payment service on the trade platform, wherein the buyer's trade account includes information about the buyer's financial account.

[0298] In some embodiments, the trading platform is configured to allow the buyer to draft or view orders on the trading platform in response to determining that the buyer's financial account is qualified for a trusted automatic payment service.

[0299] In some embodiments, the corresponding smart contract further includes: an order status update function that automatically updates the order status in response to determining, based on order status data uploaded to the corresponding blockchain, that the order status has been changed.

[0300] In some embodiments, order status data includes at least one of logistics data, supply chain data, customs data, bill of lading data, or payment data.

[0301] In some embodiments, the status of an order indicates at least one of the following: the product associated with the order has been prepared or shipped by the seller; the product has been inspected by customs; the product is being transported by at least one logistics provider; the bill of lading associated with the order has been submitted by the seller on a trading platform; the submitted bill of lading has been confirmed by the buyer on a trading platform; the invoice associated with the order has been generated by a blockchain network; the generated invoice has been confirmed by the buyer; the buyer and seller have reached a consensus on the order; the buyer's financial institution has made the automatic payment; the seller's financial institution has received the automatic payment; or the buyer has received the product.

[0302] In some embodiments, the apparatus 1400 further includes at least one of the following: a customs node corresponding to customs, wherein the order status data includes customs data uploaded by the customs node to the corresponding blockchain; or a logistics provider node corresponding to at least one logistics provider, wherein the order status data includes logistics data uploaded by the logistics provider node to the corresponding blockchain.

[0303] In some embodiments, one or more payment conditions include a first payment condition for a first payment of the order and a second payment condition for a second payment of the order. The buyer's financial institution node is configured to: in response to determining that the first payment condition for the first payment is met, execute a corresponding smart contract to automatically instruct the buyer's financial institution's computing device to make a first payment to the seller; and in response to determining that the second payment condition for the second payment is met, execute a corresponding smart contract to automatically instruct the buyer's financial institution's computing device to make a second payment to the seller.

[0304] In some embodiments, the first payment is an advance payment for the order, and the first payment condition includes that the order has been verified on the trading platform. The second payment is the final payment for the order, and the second payment condition may include at least one of the following: the bill of lading associated with the order has been submitted by the seller on the trading platform; the submitted bill of lading has been confirmed by the buyer on the trading platform; the invoice associated with the order has been generated by the blockchain network; the generated invoice has been confirmed by the buyer; or the buyer and seller have reached a consensus on the order.

[0305] Figure 14BAn example of modules of apparatus 1430 according to embodiments herein is shown. Apparatus 1430 may be an example of an embodiment of a blockchain network configured to manage a blockchain-based trusted trading service. Apparatus 1430 may correspond to the foregoing embodiments, and apparatus 1430 includes: a storage module 1432, which stores order data of the order between the buyer and seller on a blockchain network for the order after the buyer and seller confirm the order on the trading platform; the order data includes one or more payment terms of the order and trusted credit service (TUS) data of the order; a verification module 1434, which verifies that the buyer has a trusted credit service guaranteed by the buyer's financial institution; in response to the satisfaction of conditions specified in a smart contract deployed on the blockchain, the buyer's financial institution automatically makes payment on behalf of the buyer; and a generation module 1. 436, generating a corresponding smart contract for the order based on the order data, the corresponding smart contract including an automatic function that, in response to determining that the corresponding payment conditions for order payment are met, automatically instructs the buyer's financial institution to make order payment to the seller for the order based on the trusted credit service of the order; receiving module 1438, used to receive order status data of the order uploaded to the blockchain; execution module 1440, in response to determining that the corresponding payment conditions for order payment are met based on the order status data, executing the corresponding smart contract to automatically instruct the buyer's financial institution's computing device to make order payment to the seller based on the trusted credit service.

[0306] In some embodiments, the apparatus 1430 includes a buyer financial institution node corresponding to the buyer's financial institution. The buyer financial institution node is configured to: receive order payment data confirming that the buyer financial institution has successfully made order payment to the seller based on the order's trusted credit service; and store the order payment data on a blockchain.

[0307] In some embodiments, apparatus 1430 includes a seller financial institution node corresponding to the seller's financial institution. The seller has a seller financial account in the seller financial institution, and the seller financial institution node is configured to store payment receipt data on a corresponding blockchain, the payment receipt data confirming that the seller financial account in the seller financial institution has received order payment for the order from the buyer's financial institution.

[0308] In some embodiments, apparatus 1430 includes a trade platform node corresponding to a trade platform. The trade platform node is configured to: determine, based on trusted credit data, that the buyer has chosen to use the corresponding trusted credit service for an order on the trade platform, and send a request to the computing device of the buyer's financial institution via a buyer's financial institution node, the request requesting the buyer's financial institution to verify whether the buyer is eligible for trusted credit services guaranteed by the buyer's financial institution for the order.

[0309] In some embodiments, the trading platform is configured to provide a user interface for receiving user input for order data, and the user interface includes the option to use the corresponding trusted credit service for the order.

[0310] In some embodiments, the buyer's financial institution node is configured to: receive verification data from the buyer's financial institution's computing device, the verification data confirming that the buyer has a corresponding trusted credit service for the order guaranteed by the buyer's financial institution, and store the verification data on the corresponding blockchain.

[0311] In some embodiments, the trading platform is configured to: determine, based on verification data stored on the corresponding blockchain, that the buyer has a corresponding trusted credit line for the order guaranteed by the buyer's financial institution, and verify the order after determining that the buyer has a corresponding trusted credit line for the order guaranteed by the buyer's financial institution.

[0312] In some embodiments, the trading platform node is configured to send a request after storing the order data of the order on the corresponding blockchain.

[0313] In some embodiments, the corresponding payment terms for order payment are determined based on the order's corresponding trusted credit service.

[0314] In some embodiments, the buyer's financial institution node is configured to execute a corresponding smart contract in response to determining that a predetermined time has been reached or a predetermined time period has elapsed after the corresponding payment conditions for order payment have been met, so as to automatically instruct the buyer's financial institution's computing device to make order payment to the seller in accordance with the corresponding trusted credit service of the order.

[0315] In some embodiments, the scheduled time or scheduled time period is determined based on the corresponding trusted credit service of the order.

[0316] In some embodiments, one or more payment terms include first payment terms for a first payment of the order and second payment terms for a second payment of the order. The second payment is an order payment made according to a corresponding trusted credit service, and the second payment terms include the corresponding payment conditions. The buyer's financial institution node is configured to: in response to determining that the second payment terms for the second payment are met, execute a corresponding smart contract to automatically instruct the buyer's financial institution's computing device to make the second payment to the seller according to the corresponding trusted credit service of the order.

[0317] In some embodiments, the buyer financial institution node is configured to: in response to determining that the first payment conditions for the first payment are met, execute a corresponding smart contract to automatically instruct the buyer financial institution's computing device to make the first payment to the seller based on the buyer's trusted automatic payment service provided by the buyer financial institution.

[0318] In some embodiments, the trade platform node is configured to: after the buyer logs into the buyer's trade account on the trade platform, communicate with the computing device of the buyer's financial institution through the buyer's financial institution node to verify whether the buyer's financial account in the buyer's financial institution is eligible for trusted automatic payment services, wherein the buyer's trade account includes information about the buyer's financial account.

[0319] In some embodiments, the first payment is an advance payment for the order, and the first payment condition includes verification of the order. The second payment is the final payment for the order, and the second payment condition may include at least one of the following: the bill of lading associated with the order has been submitted by the seller on the trading platform; the submitted bill of lading has been confirmed by the buyer on the trading platform; the invoice associated with the order has been generated by the blockchain network; the generated invoice has been confirmed by the buyer; or the buyer and seller have reached a consensus on the order.

[0320] In some embodiments, the corresponding smart contract further includes an order status update function that automatically updates the order status in response to determining, based on order status data uploaded to the corresponding blockchain, that the order status has been changed.

[0321] In some embodiments, the status of an order indicates at least one of the following: the product associated with the order has been prepared or shipped by the seller; the product has been inspected by customs; the product is being transported by at least one logistics provider; the bill of lading associated with the order has been submitted by the seller on a trading platform; the submitted bill of lading has been confirmed by the buyer on a trading platform; the invoice associated with the order has been generated by a blockchain network; the generated invoice has been confirmed by the buyer; the buyer and seller have reached a consensus on the order; the buyer's financial institution has made the automatic payment; the seller's financial institution has received the automatic payment; or the buyer has received the product.

[0322] In some embodiments, the blockchain network of the plurality of trusted nodes further includes at least one of the following: a customs node corresponding to customs, wherein the order status data includes customs data uploaded by the customs node to the corresponding blockchain; or a logistics provider node corresponding to at least one logistics provider, wherein the order status data includes logistics data uploaded by the logistics provider node to the corresponding blockchain.

[0323] In some embodiments, order status data includes at least one of logistics data, supply chain data, customs data, bill of lading data, or payment data.

[0324] Figure 14CAn example of the modules of apparatus 1450 according to embodiments herein is shown. Apparatus 1450 may be an example of an embodiment of a blockchain network configured to manage a blockchain-based trusted trading service. Apparatus 1450 may correspond to the foregoing embodiments, and apparatus 1450 includes: a first storage module 1452, which stores order data of the order between the buyer and seller on a blockchain network for the order after the buyer and seller confirm the order on a trading platform, the order data including one or more payment terms of the order and trusted tranche (TU) service data of the order, the trusted tranche service being guaranteed by the buyer's financial institution, the buyer's financial institution automatically making payment on behalf of the buyer in response to the fulfillment of conditions specified in a smart contract deployed on the blockchain; a generation module 1454, which generates a trusted tranche certificate for the order based on the order data including the trusted tranche data; a second storage module 1456, which stores the trusted tranche certificate of the order on the blockchain; and a sending module 1458, which sends the trusted tranche certificate to the computing device of the seller's financial institution to determine whether to approve the seller's financing request based on the trusted tranche certificate.

[0325] The apparatus 1450 includes a plurality of trusted nodes. In some embodiments, the apparatus 1450 includes a trade platform node corresponding to a trade platform. In some embodiments, the apparatus 1450 includes a buyer financial institution node corresponding to a buyer financial institution. In some embodiments, the apparatus 1450 includes a seller financial institution node corresponding to a seller financial institution.

[0326] In some embodiments, one of the buyer's financial institution and the seller's financial institution is an offshore entity, and the other is an onshore entity. The offshore and onshore entities are subject to different financial regulations, and the buyer's financial institution node corresponding to the buyer's financial institution and the seller's financial institution node corresponding to the seller's financial institution belong to the same blockchain network of multiple trusted nodes.

[0327] In some embodiments, the seller financial institution node is configured to: receive approval data from the seller financial institution's computing device, the approval data indicating that the seller financial institution has approved the seller's financing request for a financing amount based on a trusted credit credential, and store the approval data on a blockchain, wherein the approval data references the trusted credit credential.

[0328] In some embodiments, the seller financial institution node is configured to: receive financing payment data from the seller financial institution's computing device, the financing payment data confirming that the financing amount associated with the financing request has been paid by the seller financial account of the seller financial institution, and store the financing payment data on a blockchain.

[0329] In some embodiments, a trusted credit credential includes at least one of the following: an identifier of the trusted credit credential; the validity period of the trusted credit credential; the corresponding payment terms for the order payment; order information, including at least one of order identifier, total order cost, or product information; order logistics information, including at least one of transportation method, trade terms, transportation cost, or transportation insurance cost; buyer and seller information; buyer's financial institution and seller's financial institution information; or buyer's financial account information in buyer's financial institution and seller's financial account information in seller's financial institution.

[0330] In some embodiments, the seller financial institution node is configured to: receive payment receipt data from the seller financial institution's computing device, the payment receipt data confirming that the seller financial account in the seller financial institution has received the order payment for the order from the buyer financial institution, and store the payment receipt data on a blockchain.

[0331] In some embodiments, the trading platform node is configured to generate a corresponding smart contract for the order based on the order data. This corresponding smart contract includes an automatic function that, in response to determining that the corresponding payment conditions for the order payment have been met, automatically instructs the buyer's financial institution to make order payment to the seller for the order based on the corresponding trusted credit service.

[0332] In some embodiments, the trade platform node is configured to: verify, via the buyer's financial institution node, using the buyer's financial institution's computing equipment, whether the buyer has authorization for the corresponding trusted credit service for the order on the trade platform.

[0333] In some embodiments, in response to verifying the buyer's authorization to have a corresponding trusted credit service for the order guaranteed by the buyer's financial institution, a trusted credit certificate for the order is generated on the blockchain.

[0334] In some embodiments, the trade platform node is configured to submit a verification request with a trusted credit credential to the buyer financial institution's computing device via the buyer financial institution node, and the buyer financial institution is configured to verify, based on the trusted credit credential, whether the buyer has authorization for the corresponding trusted credit service for the order.

[0335] In some embodiments, a trading platform node is configured to send a verification message to the trading platform confirming that the buyer has authorization for the corresponding trusted credit service for the order, in response to verifying that the buyer has authorization for the corresponding trusted credit service for the order guaranteed by the buyer's financial institution.

[0336] In some embodiments, the trading platform is configured to verify an order after receiving a verification message from a trading platform node.

[0337] In some embodiments, a trading platform node is configured to send a verification request after storing the order data of an order on the blockchain.

[0338] In some embodiments, the corresponding payment terms are determined based on the corresponding trusted credit service of the order.

[0339] In some embodiments, the buyer financial institution node is configured to: in response to determining that the corresponding payment conditions for order payment are met, execute the corresponding smart contract, wherein executing the corresponding smart contract includes automatically instructing the buyer financial institution's computing device to make order payment to the seller based on the corresponding trusted credit service.

[0340] In some embodiments, the buyer financial institution node is configured to: in response to determining that the corresponding payment conditions for order payment are met, execute a corresponding smart contract to generate an automatic payment command, which instructs the buyer financial institution's computing device to make order payment to the seller based on the corresponding trusted credit service of the order; and send the automatic payment command to the buyer financial institution's computing device.

[0341] In some embodiments, the blockchain network is configured to: in response to determining that a predetermined time has been reached or a predetermined time period has elapsed after the corresponding payment conditions have been met, execute the corresponding smart contract to automatically instruct the buyer's financial institution's computing device to make order payment to the seller based on the corresponding trusted credit service of the order.

[0342] In some embodiments, the scheduled time or scheduled time period is determined based on the trusted credit service of the order.

[0343] In some embodiments, one or more payment terms include first payment terms for a first payment of the order and second payment terms for a second payment of the order. The second payment is an order payment made under a trusted credit service for the order, and the second payment terms include corresponding payment conditions.

[0344] In some embodiments, the buyer's financial institution node is configured to: in response to determining that the first payment condition for the first payment is met, execute a corresponding smart contract to automatically instruct the buyer's financial institution's computing device to make a first payment to the seller based on the buyer's trusted automatic payment service provided by the buyer's financial institution; and in response to determining that the second payment condition for the second payment is met, execute a corresponding smart contract to automatically instruct the buyer's financial institution's computing device to make a second payment to the seller based on the corresponding trusted credit service of the order.

[0345] In some embodiments, the first payment is an advance payment for the order, and the first payment condition includes verification of the order. The second payment is the final payment for the order, and the second payment condition includes at least one of the following: the bill of lading associated with the order has been submitted by the seller on the trading platform; the submitted bill of lading has been confirmed by the buyer on the trading platform; the invoice associated with the order has been generated by the blockchain network; the generated invoice has been confirmed by the buyer; or the buyer and seller have reached a consensus on the order.

[0346] In some embodiments, the trade platform node is configured to: after the buyer logs into the buyer's trade account on the trade platform, communicate with the computing device of the buyer's financial institution through the buyer's financial institution node to verify whether the buyer's financial account in the buyer's financial institution is eligible for trusted automatic payment services, wherein the buyer's trade account includes information about the buyer's financial account.

[0347] In some embodiments, the corresponding smart contract further includes an order status update function that automatically updates the order status in response to determining, based on order status data uploaded to the corresponding blockchain, that the order status has been changed.

[0348] In some embodiments, the status of an order indicates at least one of the following: the product associated with the order has been prepared or shipped by the seller; the product has been inspected by customs; the product is being transported by at least one logistics provider; the bill of lading associated with the order has been submitted by the seller on a trading platform; the submitted bill of lading has been confirmed by the buyer on a trading platform; the invoice associated with the order has been generated by a blockchain network; the generated invoice has been confirmed by the buyer; the buyer and seller have reached a consensus on the order; the buyer's financial institution has made the automatic payment; the seller's financial institution has received the automatic payment; or the buyer has received the product.

[0349] In some embodiments, the blockchain network of the plurality of trusted nodes further includes at least one of the following: a customs node corresponding to customs, wherein the order status data includes customs data uploaded by the customs node to the corresponding blockchain; or a logistics provider node corresponding to at least one logistics provider, wherein the order status data includes logistics data uploaded by the logistics provider node to the corresponding blockchain.

[0350] In some embodiments, order status data includes at least one of logistics data, supply chain data, customs data, bill of lading data, or payment data.

[0351] The systems, devices, modules, or units shown in the foregoing embodiments can be implemented using computer chips or entities, or can be implemented using products with specific functions. Typical embodiment devices are computers (which may be personal computers), laptop computers, cellular phones, camera phones, smartphones, personal digital assistants, media players, navigation devices, email sending and receiving devices, game consoles, tablet computers, wearable devices, or any combination of these devices.

[0352] For the implementation process of the functions and roles of each module in the device, please refer to the implementation process of the corresponding steps in the aforementioned method. Details are omitted here for simplicity.

[0353] Since the apparatus embodiments largely correspond to the method embodiments, the relevant descriptions in the method embodiments can be referred to for related components. The apparatus implementation described above is merely an example. Modules described as individual components may or may not be physically separate, and components shown as modules may or may not be physical modules, may be located in one location, or may be distributed across multiple network modules. Some or all modules can be selected based on actual needs to achieve the purpose of the solutions herein. Those skilled in the art can understand and implement the embodiments of this application without inventive effort.

[0354] Refer again Figure 14A , Figure 14B or Figure 14C This can be interpreted as illustrating the internal function modules and structure of a blockchain network implementation device. Essentially, the execution entity can be an electronic device comprising: one or more processors; and one or more computer-readable storage media configured to store executable instructions of the one or more processors. In some embodiments, the one or more computer-readable storage media are coupled to the one or more processors and have programming instructions stored thereon, which can be executed by the one or more processors to perform the algorithms, methods, functions, processes, flows, and programs described herein. This document also provides one or more non-transitory computer-readable storage media coupled to one or more processors and having instructions stored thereon, which, when executed by the one or more processors, cause the one or more processors to perform operations according to embodiments of the methods provided herein.

[0355] This document also provides a system for implementing the methods provided herein. The system includes one or more processors and a computer-readable storage medium coupled to and having instructions stored thereon on the one or more processors, the instructions, when executed by the one or more processors, causing the one or more processors to perform the operations described in embodiments of the methods provided herein.

[0356] The embodiments of the subject matter, actions, and operations described herein can be implemented in digital electronic circuits, tangibly embodied computer software or firmware, computer hardware, including the structures disclosed herein and their structural equivalents, or combinations thereof. Embodiments of the subject matter described herein can be implemented as one or more computer programs, such as one or more modules of computer program instructions encoded on a computer program carrier for execution by a data processing apparatus or for controlling the operation of a data processing apparatus. For example, a computer program carrier may include one or more computer-readable storage media on which instructions are encoded or stored. The carrier may be a tangible, non-transitory computer-readable medium, such as a magnetic disk, magneto-optical disk or optical disk, a solid-state drive, random access memory (RAM), read-only memory (ROM), or other media types. Optionally or additionally, the carrier may be an artificially generated propagation signal, such as a machine-generated electrical signal, optical signal, or electromagnetic signal, generated to encode information for transmission to a suitable receiver device for execution by a data processing apparatus. A computer storage medium may be, or in part, a machine-readable storage device, a machine-readable storage substrate, a random or serial access memory device, or a combination thereof. A computer storage medium is not a propagation signal.

[0357] A computer program may also be called or described as a program, software, software application, app, module, software module, engine, script, or code, and may be written in any form of programming language, including compiled or interpreted languages, or declarative or procedural languages; it may be deployed in any form, including as a standalone program or as a module, component, engine, subroutine, or other unit suitable for execution in a computing environment, which may include one or more computers interconnected by a data communication network in one or more locations.

[0358] A computer program may, but is not required to, correspond to a file in a file system. A computer program may be stored as: a portion of a file that holds other programs or data, for example, one or more scripts stored in a markup language document; a single file dedicated to the program in question; or multiple coordination files, for example, multiple files storing one or more modules, subroutines, or code sections.

[0359] Processors used to execute computer programs include, for example, general-purpose and special-purpose microprocessors, as well as any one or more processors of any kind of digital computer. Typically, the processor receives instructions and data for executing the computer program from a non-transitory computer-readable medium coupled to the processor.

[0360] The term "data processing apparatus" encompasses all types of devices, apparatuses, and machines used for processing data, including programmable processors, computers, or multiple processors or computers. Data processing apparatuses may include dedicated logic circuitry such as FPGAs (Field-Programmable Gate Arrays), ASICs (Application-Specific Integrated Circuits), or GPUs (Graphics Processing Units). In addition to hardware, the apparatus may also include code that creates an execution environment for computer programs, such as code constituting processor firmware, protocol stacks, database management systems, operating systems, or combinations thereof.

[0361] The processing and logic flow described herein can be executed by one or more computers or processors executing one or more computer programs to perform operations by manipulating input data and generating output. This processing and logic flow can also be executed by dedicated logic circuitry, such as FPGAs, ASICs, or GPUs, or by a combination of dedicated logic circuitry and one or more programmed computers.

[0362] A computer suitable for executing computer programs can be based on a general-purpose and / or special-purpose microprocessor, or any other type of central processing unit (CPU). Typically, the CPU receives instructions and data from read-only memory and / or random access memory. The components of a computer may include a CPU for executing instructions and one or more storage devices for storing instructions and data. The CPU and memory may be supplemented with or integrated into special-purpose logic circuitry.

[0363] Typically, a computer also includes, or is operatively coupled to, one or more storage devices to receive data or transfer data to one or more storage devices. Storage devices can be, for example, disks, magneto-optical or optical disks, solid-state drives, or any other type of non-transitory computer-readable media. However, a computer is not required to have such devices. Thus, a computer can be coupled to one or more storage devices, such as one or more local and / or remote memories. For example, a computer may include one or more local memories as an integrated component of the computer, or the computer may be coupled to one or more remote memories located in a cloud network. Furthermore, a computer may be embedded in another device, such as a mobile phone, a personal digital assistant (PDA), a mobile audio or video player, a game console, a global positioning system (GPS) receiver, or a portable storage device such as a universal serial bus (USB) flash drive, to name just a few.

[0364] Components can be "coupled" to each other by communicating directly or via one or more intermediate components, such as electrical or optical connections. Components can also be "coupled" to each other if one component is integrated into another. For example, a memory component integrated into a processor (e.g., an L2 cache component) can be "coupled" to the processor.

[0365] To provide interaction with the user, embodiments of the subject matter described herein can be implemented on, or configured to communicate with, a computer having a display device and an input device, such as an LCD (liquid crystal display) monitor for displaying information to the user, and an input device such as a keyboard and a pointing device through which the user provides input to the computer, such as a mouse, trackball, or touchpad. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback, such as visual, auditory, or tactile feedback; and any form of input from the user can be received, including sound, speech, or tactile input. Furthermore, the computer can interact with the user by sending and receiving documents from the device used by the user; for example, by sending a web page to a web browser on the user's device in response to a request received from the web browser, or by interacting with an application (app) running on the user's device, such as a smartphone or tablet. The computer can also interact with the user by sending text messages or other forms of messages to a personal device, such as a smartphone running a messaging application, and receiving response messages from the user.

[0366] This document uses the term "configured as" in relation to systems, devices, and computer program components. For a system of one or more computers configured to perform a specific operation or action, this means that the system has software, firmware, hardware, or a combination thereof installed thereon that causes the system to perform said operation or action during operation. For one or more computer programs configured to perform a specific operation or action, this means that the one or more programs include instructions that, when executed by a data processing device, cause that device to perform said operation or action. For a dedicated logic circuit configured to perform a specific operation or action, this means that the circuit has electronic logic for performing said operation or action.

[0367] While this document contains many specific implementation details, these should not be construed as limiting the scope of the claims, but rather as descriptions of features of particular embodiments, the scope of which is defined by the claims themselves. Certain features described herein in the context of individual embodiments may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented individually in multiple embodiments or in any suitable sub-combination. Moreover, although the features described above may function in certain combinations, and even were initially claimed as such, in some cases one or more features may be removed from the claimed combination, and the claims may also be directed to sub-combinations or variations thereof.

[0368] Similarly, although the operations are depicted in a specific order in the accompanying drawings and recited in the claims, this should not be construed as requiring the operations to be performed in the specific order shown or sequentially, or requiring all of the shown operations to be performed, in order to achieve the desired result. In some cases, multitasking and parallel processing may be advantageous. Furthermore, the separation of the various system modules and components in the above embodiments should not be construed as requiring such separation in all embodiments, and it should be understood that the described program components and systems can generally be integrated into a single software product or packaged into multiple software products.

[0369] Specific embodiments of this subject matter have been described. Other embodiments also fall within the scope of the following claims. For example, the actions recited in the claims can be performed in a different order and still achieve the desired result. As an example, the processing depicted in the drawings does not require a specific order or sequence to achieve the desired result. In some cases, multitasking in parallel may be advantageous.

Claims

1. A system for managing blockchain-based trusted transaction services, comprising: A blockchain network with multiple trusted nodes, including: The trade platform node, corresponding to the trade platform, is used to provide blockchain-based trusted trade services between buyers and sellers, wherein the buyer has a buyer financial account in a buyer financial institution, the seller has a seller financial account in a seller financial institution, the buyer is verified to have trusted credit services guaranteed by the buyer financial institution, and in response to the fulfillment of conditions specified in a smart contract deployed on the blockchain of the blockchain network, the buyer financial institution automatically makes payments for the buyer based on the buyer's credit in the buyer financial institution; The buyer financial institution node corresponding to the buyer financial institution; and The seller financial institution node corresponding to the seller financial institution. The trade platform node is configured as follows: After the buyer and seller confirm the order on the trading platform, the order data is stored on the corresponding blockchain of the blockchain network for that order. The order data includes one or more payment terms for the order and trusted credit service data representing the corresponding trusted credit service for the order. Based on the trusted credit service data, a trusted credit certificate is generated for the order. The trusted credit certificate includes the order payment amount and... The trusted authorization certificate for the order is stored on the blockchain, and The seller financial institution node is configured as follows: The trusted credit certificate is sent to the seller's financial institution's computing device to determine whether to approve the seller's financing request based on the trusted credit certificate.

2. The system according to claim 1, wherein, One of the buyer's financial institution and the seller's financial institution is an offshore entity, and the other of the buyer's financial institution and the seller's financial institution is an onshore entity. The offshore entity and the onshore entity are subject to different financial regulations, and The buyer financial institution node corresponding to the buyer financial institution and the seller financial institution node corresponding to the seller financial institution belong to the same blockchain network of the multiple trusted nodes.

3. The system according to claim 1 or 2, wherein, The seller financial institution node is configured as follows: The system receives approval data from the seller's financial institution's computing device, indicating that the seller's financial institution has approved the seller's financing request for the financing amount based on the credible credit certificate. The approval data is stored on the blockchain, wherein the approval data references the trusted authorization credential.

4. The system according to claim 1 or 2, wherein, The seller financial institution node is configured as follows: The system receives financing payment data from the seller's financial institution's computing device, the financing payment data confirming that the financing amount associated with the financing request has been paid from the seller's financial account within the seller's financial institution. The financing payment data is stored on the blockchain.

5. The system according to claim 1 or 2, wherein, The trusted authorization credential includes at least one of the following: The identifier of the trusted credit credential. The validity period of the trusted credit certificate. The corresponding payment terms for the order payment, The order information includes at least one of the following: order identifier, total order cost, or product information. The logistics information for the order includes at least one of the following: transportation method, trade terms, transportation cost, or transportation insurance cost. The buyer's information and the seller's information, The information of the buyer's financial institution and the information of the seller's financial institution, or Information on the buyer's financial account in the buyer's financial institution and information on the seller's financial account in the seller's financial institution.

6. The system according to claim 1 or 2, wherein, The seller financial institution node is configured as follows: Payment receipt data is received from the seller's financial institution's computing device, confirming that the seller's financial account in the seller's financial institution has received the order payment for the order from the buyer's financial institution. The payment receipt data is stored on the blockchain.

7. The system according to claim 1 or 2, wherein, The trade platform node is configured as follows: Based on the order data of the order, a corresponding smart contract for the order is generated. The corresponding smart contract includes an automatic function that, in response to determining that the corresponding payment conditions for the order payment are met, automatically instructs the buyer's financial institution to make order payment to the seller for the order based on the corresponding trusted credit service for the order.

8. The system according to claim 7, wherein, The trade platform node is configured as follows: Through the buyer's financial institution node, using the computing equipment of the buyer's financial institution, it is verified whether the buyer has authorization for the corresponding trusted credit service for the order on the trading platform.

9. The system according to claim 7, wherein, The buyer financial institution node is configured as follows: Executing the corresponding smart contract includes: in response to determining that the corresponding payment conditions for the order payment are met, automatically instructing the computing device of the buyer's financial institution to make the order payment to the seller based on the corresponding trusted credit service for the order.

10. The system according to claim 9, wherein, The blockchain network is configured as follows: In response to determining that after the corresponding payment conditions are met, a predetermined time has elapsed or a predetermined time period has elapsed, the corresponding smart contract is executed to automatically instruct the buyer's financial institution's computing device to make payment for the order to the seller based on the corresponding trusted credit service for the order.

11. The system according to claim 9, wherein, The one or more payment terms include the first payment terms for the first payment of the order and the second payment terms for the second payment of the order. Wherein, the second payment is the order payment made based on the trusted credit service of the order, and the second payment conditions include the corresponding payment conditions. The buyer financial institution node is configured as follows: In response to determining that the first payment condition for the first payment is met, the corresponding smart contract is executed to automatically instruct the computing device of the buyer's financial institution to make the first payment to the seller based on the buyer's trusted automatic payment service provided by the buyer's financial institution. In response to the determination that the second payment conditions for the second payment are met, the corresponding smart contract is executed to automatically instruct the computing device of the buyer's financial institution to make the second payment to the seller in accordance with the corresponding trusted credit service of the order.

12. The system according to claim 11, wherein, The first payment is a prepayment for the order, and the first payment conditions include verification of the order, and The second payment is the final payment for the order, and the second payment terms include at least one of the following: The bill of lading associated with this order has been submitted by the seller on the trading platform. The submitted bill of lading has been confirmed by the buyer on the trading platform. The invoice associated with this order has been generated by the blockchain network. The generated invoice has been confirmed by the buyer, or The buyer and the seller have reached an agreement on the order.

13. The system according to claim 7, wherein, The corresponding smart contract also includes an order status update function, which automatically updates the order status in response to a determination based on order status data uploaded to the corresponding blockchain that the order status has been changed. The status of the order indicates at least one of the following: The products associated with this order have already been prepared or shipped by the seller. The product has been inspected by customs. The product is being transported by at least one logistics provider. The bill of lading associated with this order has been submitted by the seller on the trading platform. The submitted bill of lading has been confirmed by the buyer on the trading platform. The invoice associated with this order has been generated by the blockchain network. The generated invoice has been confirmed by the buyer. The buyer and the seller have reached a consensus on the order. The buyer's financial institution has made automatic payments. The seller has received automatic payment, or The buyer has received the product.

14. A computer-implemented method, performed by the system according to any one of claims 1 to 13.

15. An apparatus for managing a blockchain-based trusted transaction service, the apparatus comprising a plurality of modules for performing the computer-implemented method of claim 14.

Images