A cross-border information payment system based on blockchain architecture

Abstract

The present invention relates to a cross-border information payment system based on a blockchain architecture, including a user terminal and a cloud server. The cloud server is configured with a cross-border processing subsystem, an information encryption subsystem, and an information collection subsystem. The cross-border processing subsystem includes a request response module, a request processing module, and a request execution module. The request response module is used to receive a transaction request from the user terminal and generate transaction data according to the content of the transaction request. The request execution module generates transaction information according to the transaction characteristics of the transaction data. The request execution module outputs the transaction information to an external remittance execution end to complete the transaction. It identifies whether the transaction request is cross-border. If so, it generates corresponding transaction information to a third party. It can ensure the clarity and efficiency of information for any user, while ensuring the data security on the other side of the transaction. At the same time, it also ensures that the user information cannot be modified, and the decentralized design ensures that the user information is not easily lost. At the same time, it saves most of the storage resources.

Description

Technical Field

[0001] The present invention relates to smart home devices, and more specifically, to a cross-border information payment system based on a blockchain architecture. Background Art

[0002] The electronic payment system refers to the intermediary institutions that provide payment services, the laws and regulations governing the transfer of money, and the electronic information technology means to achieve payment, which is used to repay the debts incurred by participants in economic activities when acquiring physical assets or financial assets. That is, the transaction information of new payment methods (including electronic cash, credit cards, debit cards, smart cards, etc.) is transmitted to banks or corresponding processing institutions through network security to achieve electronic payment. Therefore, the electronic payment system is one of the important social infrastructures for the smooth conduct of electronic transactions, and it is also the foundation and catalyst for the good operation of the social economy. The payment system refers to the intermediary institutions that provide payment services, the laws and regulations governing the transfer of money, and the technical means to achieve payment, which is used to repay the debts incurred by participants in economic activities when acquiring physical assets or financial assets. Therefore, the payment system is one of the important social infrastructures.

[0003] Different payment systems are usually associated with different economies. Economic societies have used various forms of money to transfer value in commodity exchanges. The development from the initial physical exchange to commodity money (such as precious metals) marks the progress of social productivity.

[0004] The payment system within each country is relatively simple. However, when it comes to cross-border payments, there is an exchange rate variable. Depending on the actual payment situation, the payment types include the payer's exchange rate, the real-time exchange rate, the recipient's exchange rate, the exchange rate at the time of goods delivery, etc., which makes the information environment more complicated. If it is necessary to take into account both data retention and modifiability, but cannot take into account data security, it will easily cause significant losses due to data leakage. Summary of the invention

[0005] In view of this, the purpose of the present invention is to provide a cross-border information payment system based on blockchain architecture.

[0006] In order to solve the above technical problems, the technical solution of the present invention is: a cross-border information payment system based on blockchain architecture, including a user terminal and a cloud server, wherein the cloud server is configured with a cross-border processing subsystem, an information encryption subsystem and an information collection subsystem;

[0007] The cross-border processing subsystem includes a first request-response module, a request processing module, and a request execution module. The first request-response module is used to receive a transaction request from a user terminal and generate transaction data according to the content of the transaction request. The request execution module generates transaction information based on the transaction characteristics of the transaction data. The request execution module outputs the transaction information to an external remittance execution end to complete the transaction; it identifies whether the transaction request is cross-border. If so, it generates corresponding transaction information to a third party;

[0008] The information encryption subsystem includes a data splitting module, a data encryption module, a data distribution module, a data association module, and a data decentralization module. The data splitting module includes splitting transaction information to generate two transaction sub-information, namely a payment terminal sub-information and a receiving terminal sub-information. The two transaction sub-information are respectively the payment terminal sub-information and the receiving terminal sub-information. The payment terminal sub-information includes a payment terminal code, a payment amount, and a payment time; the receiving terminal sub-information includes a receiving terminal code, a receiving amount, and a receiving time. The payment terminal code corresponds to the user terminal at the time of payment, and the receiving terminal code corresponds to the user terminal at the time of receipt. The payment amount reflects the actual expenditure amount of the currency in the country where the payment terminal is located, and the receiving amount reflects the actual received amount of the currency in the country where the receiving terminal is located; the data encryption module configures a first encryption algorithm to encrypt the transaction sub-information to generate corresponding transaction ciphertexts and transaction keys. The transaction ciphertexts include a payment terminal ciphertext and a receiving terminal ciphertext, and the transaction keys include a payment terminal key and a receiving terminal key; the data distribution module includes configuring a reference condition, screening eligible user terminals as payment storage terminals through a first reference condition, screening eligible user terminals as receiving storage terminals through a second reference condition, sending the payment terminal ciphertext to the payment storage terminal and the user terminal where the payment behavior occurs, sending the payment key to the user terminal where the payment behavior occurs, sending the receiving terminal ciphertext to the receiving storage terminal and the user terminal where the receiving behavior occurs; the data association module includes generating payment association information according to the payment terminal ciphertext and the receiving terminal sub-information, generating receiving association information according to the receiving terminal ciphertext and the payment terminal sub-information, and storing the association information in a pre-configured association database. The association database uses the association information as an index. The association information between the payment terminal ciphertext and the receiving terminal sub-information is generated according to the first reference condition, and the association information between the receiving terminal ciphertext and the payment terminal sub-information is generated according to the second reference condition; the data decentralization module includes deleting the transaction ciphertexts, transaction keys, and transaction sub-information;

[0009] The information collection subsystem includes an unlocking response module, an information addressing module, a second request response module, an information feedback module, and an information merging module; the unlocking response module includes obtaining a local transaction key according to an unlocking request generated by a user, and decrypting a corresponding transaction ciphertext with the transaction key and a first decryption algorithm to obtain a transaction sub-information; the information addressing module includes generating an association request according to the transaction sub-information and sending it to a cloud server, and the cloud server receives the association request and determines corresponding association information from the association database; the second request response module includes the cloud server generating an acquisition request according to the obtained association information and sending the acquisition request to each corresponding user terminal, the information feedback module includes when each user terminal receives the acquisition request, determining a corresponding transaction ciphertext according to the acquisition request, and decrypting the corresponding transaction ciphertext with the key of the user terminal and the first decryption algorithm, if a user terminal decrypts successfully to obtain the corresponding transaction sub-information, the information merging module includes the cloud server merging the transaction sub-information obtained in the unlocking response module and the information feedback module to generate transaction information.

[0010] Further: The transaction information further includes a transaction type. If the transaction type is a payment real-time exchange rate, the transaction amount in the transaction information is extracted, and this transaction amount is used as the payment amount, and the recipient currency exchange rate is determined from a preset exchange rate database according to the payment time to obtain the receiving amount.

[0011] Further: The transaction information further includes a transaction type. If the transaction type is a receiving real-time exchange rate, the transaction amount in the transaction information is extracted, and this transaction amount is used as the receiving amount, and the payer currency exchange rate is determined from a preset exchange rate database according to the receiving time to obtain the payment amount.

[0012] Further: The transaction information further includes a transaction type. If the transaction type is a receiving forward exchange rate, the transaction amount in the transaction information is extracted, and this transaction amount is used as the receiving amount, and the payer currency exchange rate is determined from a preset exchange rate database according to the forward time to obtain the payment amount, and the forward time is the agreed payment time.

[0013] Further: The transaction information further includes a transaction type. If the transaction type is a receiving real-time exchange rate, the transaction amount in the transaction information is extracted, and this transaction amount is used as the receiving amount, and the payer currency exchange rate is determined from a preset exchange rate database according to the forward time to obtain the payment amount, and the forward time is the agreed payment time.

[0014] Further: The first benchmark condition is configured as a randomly generated time range. If any user terminal has a transaction behavior within this time range, it is considered to meet the first benchmark condition; the second benchmark condition is a randomly generated address range. If the address range of any user terminal meets it, it is considered to meet the second benchmark condition.

[0015] Further: The second reference condition is configured as a randomly generated time range. If any user terminal has a transaction behavior within this time range, it is considered to meet the second reference condition; the first reference condition is a randomly generated address range. If the address range of any user terminal meets it, it is considered to meet the first reference condition.

[0016] Further: The first decryption algorithm is pre-stored in the cloud server.

[0017] Further: The cloud server includes an information verification subsystem. The information verification subsystem includes an association capture module, a number comparison module, and an anomaly analysis module. The association capture module includes obtaining two corresponding association information, and obtaining the corresponding terminal number group of the user terminal according to the two association information. Each association information has two corresponding terminal number groups, and each terminal number group includes several terminal numbers. The terminal number reflects the number of one of the terminals in the payment storage end, the payment behavior end, the receiving storage end, and the receiving behavior end. The number comparison module includes comparing whether there are the same terminal numbers in the corresponding terminal numbers included in the four terminal number groups; if there are no same terminal numbers, an anomaly result is output. If each terminal number group has only one same terminal number, a normal result is output.

[0018] Further: The information verification subsystem further includes a verification request module, a verification acquisition module, and a verification comparison module. The verification request module includes obtaining the corresponding association information according to the input verification request, and determining the corresponding terminal number group according to the association information. The verification acquisition module includes obtaining a target transaction ciphertext by sending an acquisition request from each user terminal corresponding to the terminal number group, and obtaining the corresponding transaction key from the verification request, and decrypting the transaction ciphertext through the transaction key and the first decryption algorithm to obtain several transaction sub-information. The verification comparison module includes comparing whether each transaction sub-information is the same. If there are different transaction sub-information, an anomaly result is output.

[0019] The technical effects of the present invention are mainly reflected in the following aspects: By setting like this, it can ensure the clarity and efficiency of information for any user, while ensuring the data security on the other side of the transaction, and at the same time ensuring that the user information cannot be modified. And the decentralized design ensures that the user information is not easily lost, and at the same time saves most of the storage resources. Description of the Drawings

[0020] Figure 1 : System architecture topology diagram of the present invention;

[0021] Figure 2 : Schematic diagram of the cross-border processing subsystem of the system of the present invention;

[0022] Figure 3 : Schematic diagram of the information encryption subsystem of the present invention;

[0023] Figure 4 : Schematic diagram of the information collection subsystem of the present invention;

[0024] Figure 5 : Schematic diagram of the information verification subsystem of the present invention.

[0025] Reference numerals: 100, user terminal; 200, cloud server; 210, cross-border processing subsystem; 211, first request response module; 212, request processing module; 213, request execution module; 220, information encryption subsystem; 221, data splitting module; 222, data encryption module; 223, data distribution module; 224, data association module; 225, data decentralization module; 230, information collection subsystem; 231, unlocking response module; 232, information addressing module; 233, second request response module; 234, information feedback module; 235, information merging module; 240, information verification subsystem; 2411, association capture module; 2412, number comparison module; 2413, anomaly analysis module; 2421, verification request module; 2422, verification acquisition module; 2423, verification comparison module. Detailed implementation manners

[0026] The following further details the specific implementation manners of the present invention in conjunction with the accompanying drawings, so that the technical solutions of the present invention are easier to understand and master.

[0027] A cross-border information payment system based on a blockchain architecture includes a user terminal 100 and a cloud server 200, and a cross-border processing subsystem 210, an information encryption subsystem 220, and an information collection subsystem 230 are configured in the cloud server 200;

[0028] The cross-border processing subsystem 210 includes a first request-response module 211, a request processing module 212, and a request execution module 213. The first request-response module 211 is used to receive a transaction request from the client 100 and generate transaction data according to the content of the transaction request. The request execution module 213 generates transaction information based on the transaction characteristics of the transaction data. The request execution module 213 outputs the transaction information to an external remittance execution end to complete the transaction; it identifies whether the transaction request is cross-border. If so, it generates corresponding transaction information to a third party. The transaction information further includes a transaction type. If the transaction type is paying the real-time exchange rate, the transaction amount in the transaction information is extracted, and this transaction amount is used as the payment amount. Then, according to the payment time, the recipient currency exchange rate is determined from a preset exchange rate database to obtain the receiving amount. The transaction information further includes a transaction type. If the transaction type is receiving the real-time exchange rate, the transaction amount in the transaction information is extracted, and this transaction amount is used as the receiving amount. Then, according to the receiving time, the payer currency exchange rate is determined from a preset exchange rate database to obtain the payment amount. The transaction information further includes a transaction type. If the transaction type is receiving the forward exchange rate, the transaction amount in the transaction information is extracted, and this transaction amount is used as the receiving amount. Then, according to the forward time (the forward time is the agreed payment time), the payer currency exchange rate is determined from a preset exchange rate database to obtain the payment amount. The transaction information further includes a transaction type. If the transaction type is receiving the real-time exchange rate, the transaction amount in the transaction information is extracted, and this transaction amount is used as the receiving amount. Then, according to the forward time (the forward time is the agreed payment time), the payer currency exchange rate is determined from a preset exchange rate database to obtain the payment amount. First, it is the cross-border processing subsystem 210. The key of the cross-border processing subsystem 210 lies in generating corresponding transaction data according to the user's transaction request. Generally, after formatting, the transaction data includes the transaction method. Due to the complexity of the cross-border system, generally, in addition to the payer and recipient of the transaction, the transaction time and transaction amount are different from non-cross-border payments, and the exchange rate situation needs to be considered. Therefore, the above four cases are listed on how to quantify the transaction information, and the corresponding payment amount or receiving amount is determined through the transaction database. Because the actual transaction information only includes the amount and currency, but due to the possible different results considering whether it is an immediate or forward transaction, the four cases are converted through the exchange rate database. The purpose of this conversion is to make the data of the payer and recipient independent and then output the corresponding results.

[0029] The information encryption subsystem 220 includes a data splitting module 221, a data encryption module 222, a data distribution module 223, a data association module 224, and a data decentralization module 225. The data splitting module 221 includes splitting transaction information to generate two transaction sub-informations, namely a payment terminal sub-information and a receiving terminal sub-information. The payment terminal sub-information includes a payment terminal code, a payment amount, and a payment time; the receiving terminal sub-information includes a receiving terminal code, a receiving amount, and a receiving time. The payment terminal code corresponds to the user terminal 100 at the time of payment, and the receiving terminal code corresponds to the user terminal 100 at the time of receipt. The payment amount reflects the actual currency expenditure amount of the country where the payment terminal is located, and the receiving amount reflects the actual currency receipt amount of the country where the receiving terminal is located; the data encryption module 222 configures a first encryption algorithm to encrypt the transaction sub-informations to generate corresponding transaction ciphertexts and transaction keys. The transaction ciphertexts include a payment terminal ciphertext and a receiving terminal ciphertext, and the transaction keys include a payment terminal key and a receiving terminal key; the data distribution module 223 includes configured benchmark conditions, screening eligible user terminals 100 as payment storage terminals through a first benchmark condition, screening eligible user terminals 100 as receiving storage terminals through a second benchmark condition, sending the payment terminal ciphertext to the payment storage terminal and the user terminal where the payment behavior occurs, sending the payment key to the user terminal where the payment behavior occurs, sending the receiving terminal ciphertext to the receiving storage terminal and the user terminal where the receiving behavior occurs; the data association module 224 includes generating payment association information based on the payment terminal ciphertext and the receiving terminal sub-information, generating receiving association information based on the receiving terminal ciphertext and the payment terminal sub-information, and storing the association information in a pre-configured association database. The association database uses the association information as an index. The association information between the payment terminal ciphertext and the receiving terminal sub-information is generated according to the first benchmark condition, and the association information between the receiving terminal ciphertext and the payment terminal sub-information is generated according to the second benchmark condition; the data decentralization module 225 includes deleting the transaction ciphertexts, transaction keys, and transaction sub-informations; the first benchmark condition is configured as a randomly generated time range. If any user terminal has a transaction behavior within this time range, it is considered to meet the first benchmark condition; the second benchmark condition is a randomly generated address range. If the address range of any user terminal meets it, it is considered to meet the second benchmark condition. The second benchmark condition is configured as a randomly generated time range. If any user terminal has a transaction behavior within this time range, it is considered to meet the second benchmark condition; the first benchmark condition is a randomly generated address range. If the address range of any user terminal meets it, it is considered to meet the first benchmark condition.A key aspect of the present invention lies in data splitting, where the information of the payer and the payee is split into two pieces of information. Even if there is some overlap in the data, it can ensure the clarity of the data. For example, the payer cannot obtain the payee's information about this transaction without making a request, but can clearly know the amount and time of their payment. This ensures independence while enhancing security. For the ciphertext and key generated through encryption, when distributing, a condition is used to determine a truly needed terminal, either the payer's or the payee's terminal. Additionally, the ciphertext is stored in several different user terminals, which ensures that the data is non-editable. At the same time, only the corresponding terminal receives the key. In this way, the terminal can not only store the ciphertext of other terminals but also locally view its own payment information or receiving information. The decentralization of data ensures the security and reliability of the data, such that there is no backup of all data on the cloud server 200.

[0030] The information collection subsystem 230 includes an unlocking response module 231, an information addressing module 232, a second request response module 233, an information feedback module 234, and an information merging module 235. The unlocking response module 231 includes obtaining the local transaction key according to the unlocking request generated by the user, and decrypting the corresponding transaction ciphertext with the transaction key and the first decryption algorithm to obtain a transaction sub-information. The information addressing module 232 includes generating an association request according to the transaction sub-information and sending it to the cloud server 200. The cloud server 200 receives the association request and determines the corresponding association information from the association database. The second request response module 233 includes the cloud server 200 generating an acquisition request according to the obtained association information and sending the acquisition request to each corresponding user terminal. The information feedback module 234 includes when each user terminal receives the acquisition request, determining the corresponding transaction ciphertext according to the acquisition request, and decrypting the corresponding transaction ciphertext with the key of this user terminal and the first decryption algorithm. If a user terminal decrypts successfully to obtain the corresponding transaction sub-information, the information merging module 235 includes the cloud server 200 merging the transaction sub-information obtained in the unlocking response module 231 and the information feedback module 234 to generate transaction information. The first decryption algorithm is pre-stored in the cloud server 200. Unlocking ensures that local information can be obtained, but the other corresponding piece of information missing from the transaction sub-information needs to be found through addressing to the corresponding user terminal (and the address of the fake storage terminal). The cloud server 200 sends the same request to these user terminals. The user terminal can judge whether it is the terminal of the transaction behavior at that time based on whether the unlocking is successful. The transaction sub-information with successful unlocking can be merged into transaction information, and the user can obtain the complete transaction information.

[0031] The principle of the entire system is as follows: First, after obtaining the transaction information, the transaction information is split into two transaction sub-information, and then encrypted respectively to obtain two transaction ciphertexts and two keys. According to the preset conditions, different user terminals 100 for storing the ciphertext are determined for each transaction ciphertext, and the ciphertext is stored in the user terminal 100 related to the transaction and the terminal related to the transaction. The user terminal as a storage function cannot open the corresponding ciphertext, and the key is sent to the terminal related to the transaction to ensure that the terminal can obtain its own transaction sub-information. The data association module 224 is for the case where if a trading party needs to obtain the entire complete transaction information, and since the ciphertext and the key will be deleted after the data is sent, a process is required to find the ciphertext through the transaction sub-information, which involves the way of association. The association is not to save its content, but to associate the characteristics of this content, as long as the uniqueness of the content is ensured. That is to say, the payment association information is to find the payment end ciphertext through the receiving end sub-information, and the association information is also related to the reference conditions. That is, if the cloud server 200 knows any one of the transaction sub-information, it can obtain the terminal storing the transaction ciphertext corresponding to the transaction sub-information according to the transaction sub-information, and then find the other transaction sub-information according to the known ciphertext. The logic of information collection is as follows: First, the local transaction sub-information is obtained by unlocking the local file, and then the association information can be found through the cloud server 200 according to the transaction sub-information, and the characteristics of the corresponding transaction ciphertext (the ciphertext cannot be obtained here) and all user terminals storing this transaction ciphertext can be determined. Then, a fetch request can be sent to each user terminal. When the user terminal receives this fetch request, it will try to unlock this ciphertext. If the unlocking is successful (only the user terminal corresponding to the transaction behavior has the key, so only it can unlock successfully), the corresponding transaction sub-information can be sent back to complete a cycle. It should be noted that the association information is the characteristics of the stored transaction sub-information and the transaction ciphertext, rather than the content of the specific transaction ciphertext, so there will be no data security problems.

[0032] The cloud server 200 includes an information verification subsystem 240. The information verification subsystem 240 includes an association capture module 2411, a number comparison module 2412, and an anomaly analysis module 2413. The association capture module 2411 includes obtaining two corresponding association information, obtaining a corresponding terminal number group of the user terminal according to the two association information. Each association information has two corresponding terminal number groups, and each terminal number group includes several terminal numbers. The terminal number reflects the number of one of the terminals in the payment storage end, the payment behavior end, the receiving storage end, and the receiving behavior end. The number comparison module 2412 includes comparing whether there are the same terminal numbers among the four terminal number groups corresponding to the terminal numbers; if there are no same terminal numbers, an abnormal result is output. If each terminal number group has only one same terminal number, a normal result is output. In this way, it can be verified whether the terminals in the association information have been modified and whether the association information is valid. The information verification subsystem 240 further includes a verification request module 2421, a verification acquisition module 2422, and a verification comparison module 2423. The verification request module 2421 includes obtaining corresponding association information according to the input verification request and determining the corresponding terminal number group according to the association information. The verification acquisition module 2422 includes sending an acquisition request from each user terminal corresponding to the terminal number group to obtain the target transaction ciphertext, and obtaining the corresponding transaction key from the verification request, and decrypting the transaction ciphertext through the transaction key and the first decryption algorithm to obtain several transaction sub-information. The verification comparison module 2423 includes comparing whether each transaction sub-information is the same. If there are different transaction sub-information, an abnormal result is output. In this way, the security of the transaction key can be verified. Of course, the above are only typical examples of the present invention. In addition, the present invention can also have many other specific implementation manners. All technical solutions formed by equivalent replacement or equivalent transformation fall within the scope of protection required by the present invention.

Claims

1. A cross-border information payment system based on a blockchain architecture, characterized in that: it includes a user terminal and a cloud server, and a cross-border processing subsystem, an information encryption subsystem, and an information collection subsystem are configured in the cloud server; The cross-border processing subsystem includes a first request response module, a request processing module, and a request execution module. The first request response module is used to receive a transaction request from the user terminal and generate transaction data according to the content of the transaction request. The request execution module generates transaction information according to the transaction characteristics of the transaction data, and the request execution module outputs the transaction information to an external remittance execution end to complete the transaction; it is to identify whether the transaction request is cross-border. If so, generate corresponding transaction information to a third party; The information encryption subsystem includes a data splitting module, a data encryption module, a data distribution module, a data association module, and a data decentralization module. The data splitting module includes splitting the transaction information to generate two transaction sub-information, and the two transaction sub-information are respectively a payment terminal sub-information and a receiving terminal sub-information. The payment terminal sub-information includes a payment terminal code, a payment amount, and a payment time; the receiving terminal sub-information includes a receiving terminal code, a receiving amount, and a receiving time. The payment terminal code corresponds to the user terminal at the time of payment, the receiving terminal code corresponds to the user terminal at the time of receipt, the payment amount reflects the actual expenditure amount of the currency in the country where the payment terminal is located, and the receiving amount reflects the actual received amount of the currency in the country where the receiving terminal is located; The data encryption module configures a first encryption algorithm to encrypt the transaction sub-information to generate corresponding transaction ciphertexts and transaction keys. The transaction ciphertexts include a payment terminal ciphertext and a receiving terminal ciphertext, and the transaction keys include a payment terminal key and a receiving terminal key; The data distribution module includes configuring benchmark conditions, screening eligible user terminals as payment storage terminals through the first benchmark condition, screening eligible user terminals as receiving storage terminals through the second benchmark condition, sending the payment terminal ciphertext to the payment storage terminal and the user terminal where the payment behavior occurs, sending the payment key to the user terminal where the payment behavior occurs, sending the receiving terminal ciphertext to the receiving storage terminal and the user terminal where the receiving behavior occurs; the data association module includes generating payment association information according to the payment terminal ciphertext and the receiving terminal sub-information, generating receiving association information according to the receiving terminal ciphertext and the payment terminal sub-information, and storing the association information in a pre-configured association database. The association database uses the association information as an index. The association information between the payment terminal ciphertext and the receiving terminal sub-information is generated according to the first benchmark condition, and the association information between the receiving terminal ciphertext and the payment terminal sub-information is generated according to the second benchmark condition; the data decentralization module includes deleting the transaction ciphertexts, transaction keys, and transaction sub-information; The information collection subsystem includes an unlocking response module, an information addressing module, a second request response module, an information feedback module, and an information merging module; the unlocking response module includes obtaining a local transaction key according to an unlocking request generated by a user, and decrypting a corresponding transaction ciphertext with the transaction key and a first decryption algorithm to obtain a transaction sub-information; the information addressing module includes generating an association request according to the transaction sub-information and sending it to a cloud server, and the cloud server receives the association request and determines corresponding association information from the association database; the second request response module includes the cloud server generating an acquisition request according to the obtained association information and sending the acquisition request to each corresponding user terminal, and the information feedback module includes when each user terminal receives the acquisition request, determining a corresponding transaction ciphertext according to the acquisition request, and decrypting the corresponding transaction ciphertext with the key of the user terminal and the first decryption algorithm. If a user terminal decrypts successfully to obtain the corresponding transaction sub-information, the information merging module includes the cloud server merging the transaction sub-information obtained in the unlocking response module and the information feedback module to generate transaction information; The cloud server includes an information verification subsystem, and the information verification subsystem includes an association capture module, a number comparison module, and an anomaly analysis module. The association capture module includes obtaining two corresponding association information, obtaining a corresponding terminal number group of the user terminal according to the two association information. Each association information has two corresponding terminal number groups, and each terminal number group includes several terminal numbers. The terminal number reflects the number of one of the terminals in the payment storage end, the payment behavior end, the receiving storage end, and the receiving behavior end. The number comparison module includes comparing whether there are the same terminal numbers in the four terminal number groups; if there are no same terminal numbers, an anomaly result is output. If each terminal number group has only one same terminal number, a normal result is output; The information verification subsystem further includes a verification request module, a verification acquisition module, and a verification comparison module. The verification request module includes obtaining corresponding association information according to an input verification request and determining a corresponding terminal number group according to the association information. The verification acquisition module includes obtaining a target transaction ciphertext by sending an acquisition request from each user terminal corresponding to the terminal number group, and obtaining a corresponding transaction key from the verification request, and decrypting the transaction ciphertext with the transaction key and the first decryption algorithm to obtain several transaction sub-information. The verification comparison module includes comparing whether each transaction sub-information is the same. If there are different transaction sub-information, an anomaly result is output.

2. The cross-border information payment system based on the blockchain architecture as described in claim 1, characterized in that: The transaction information further includes a transaction type. If the transaction type is the payment real-time exchange rate, the transaction amount in the transaction information is extracted, and this transaction amount is used as the payment amount, and the recipient currency exchange rate is determined from a preset exchange rate database according to the payment time to obtain the receiving amount.

3. The cross-border information payment system based on the blockchain architecture as described in claim 1, It is characterized in that: The transaction information further includes a transaction type. If the transaction type is receiving the real-time exchange rate, the transaction amount in the transaction information is extracted, and this transaction amount is used as the received amount. Then, the payor currency exchange rate is determined from a preset exchange rate database according to the receiving time to obtain the payment amount.

4. A cross-border information payment system based on a blockchain architecture as claimed in claim 1, It is characterized in that: The transaction information further includes a transaction type. If the transaction type is receiving the forward exchange rate, the transaction amount in the transaction information is extracted, and this transaction amount is used as the received amount. Then, the payor currency exchange rate is determined from a preset exchange rate database according to the forward time to obtain the payment amount, and the forward time is the agreed payment time.

5. A cross-border information payment system based on a blockchain architecture as claimed in claim 1, It is characterized in that: The transaction information further includes a transaction type. If the transaction type is receiving the real-time exchange rate, the transaction amount in the transaction information is extracted, and this transaction amount is used as the received amount. Then, the payor currency exchange rate is determined from a preset exchange rate database according to the forward time to obtain the payment amount, and the forward time is the agreed payment time.

6. A cross-border information payment system based on a blockchain architecture as claimed in claim 1, It is characterized in that: The first benchmark condition is configured as a randomly generated time range. If any user terminal has a transaction behavior within this time range, it is considered to meet the first benchmark condition; the second benchmark condition is a randomly generated address range. If the address range of any user terminal meets it, it is considered to meet the second benchmark condition.

7. A cross-border information payment system based on a blockchain architecture as claimed in claim 1, It is characterized in that: The second benchmark condition is configured as a randomly generated time range. If any user terminal has a transaction behavior within this time range, it is considered to meet the second benchmark condition; the first benchmark condition is a randomly generated address range. If the address range of any user terminal meets it, it is considered to meet the first benchmark condition.

Images