Cross-border payment method and related device

Abstract

The embodiment of the invention provides a cross-border payment method and a related device, and relates to the field of financial science and technology or other related fields, and the method comprises the steps: responding to a payment request, generating transaction data, and storing the transaction data in a distributed block chain; analyzing the transaction data through an intelligent contract, and determining whether to perform collaborative security assessment on the transaction data based on a preset compliance rule; if the collaborative security assessment is determined to be carried out, carrying out joint calculation based on encrypted data provided by a participant of the transaction data, and generating a risk score of the transaction data; and performing payment processing on the transaction data according to the risk score. According to the scheme, automation, global risk control and real-time supervision of a cross-border payment process can be realized on the premise of ensuring privacy.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of financial technology or other related fields, in particular to a cross-border payment method and related device. BACKGROUND

[0002] The existing bank cross-border payment mainly relies on the international funds clearing system, and adopts the technical architecture of "proxy mode + decentralized risk control". When the payer bank cannot be directly connected to the payee bank, multi-level proxy banks are used to complete the clearing.

[0003] In this process, the payer bank, the payee bank and the intermediate agent institution need to independently perform customer identity verification and suspicious fund review. However, due to the lack of trust mechanism between institutions, the external verification results cannot be directly adopted, resulting in the need for multiple manual audits for the same transaction, and high compliance costs. In addition, banks cannot share sensitive risk data due to privacy compliance requirements, resulting in a lack of global risk control capability based on local data. SUMMARY

[0004] Embodiments of the present application provide a cross-border payment method and related device to reduce compliance costs and improve global risk control capabilities.

[0005] In a first aspect, embodiments of the present application provide a cross-border payment method, comprising:

[0006] In response to a payment request, transaction data is generated and stored in a distributed blockchain;

[0007] The transaction data is parsed by a smart contract, and it is determined whether to perform a collaborative security assessment on the transaction data based on a preset compliance rule;

[0008] If it is determined to perform the collaborative security assessment, joint calculation is performed based on the encrypted data provided by the participants of the transaction data to generate a risk score of the transaction data;

[0009] The transaction data is processed according to the risk score.

[0010] In some embodiments, the processing of the transaction data according to the risk score comprises:

[0011] If the risk score is less than a preset threshold, the transaction data is cleared and settled;

[0012] If the risk score is greater than or equal to the preset threshold, the transaction data is frozen, and a warning information is output.

[0013] In some embodiments, the generation of transaction data in response to a payment request comprises:

[0014] In response to the payment request, performing compliance verification on the payment request to generate a compliance verification result;

[0015] In a case where the compliance verification result passes, generating initial transaction data based on the compliance verification result;

[0016] Performing encryption signature on the initial transaction data to obtain the transaction data.

[0017] In some embodiments, the smart contract parses the transaction data and determines whether to perform collaborative security assessment on the transaction data based on preset compliance rules, including:

[0018] The smart contract parses the transaction data and determines the key fields of the transaction data;

[0019] If it is determined that the key fields meet the risk control conditions based on the preset compliance rules, the transaction data is subjected to collaborative security assessment.

[0020] In some embodiments, the risk score of the transaction data is generated based on encrypted data provided by a participant of the transaction data through joint calculation, including:

[0021] Sending a joint calculation request to the participant;

[0022] Obtaining encrypted data provided by the participant; the encrypted data is provided by the participant based on a secret sharing strategy or a homomorphic encryption strategy;

[0023] Using a preset calculation strategy to perform joint calculation on the encrypted data to obtain the risk score; the risk score is plaintext data.

[0024] In some embodiments, the compliance verification on the payment request to generate a compliance verification result includes:

[0025] Performing compliance verification on the payment request based on zero-knowledge proof to generate a compliance verification result;

[0026] Or,

[0027] Performing compliance verification on the payment request based on local customer identity verification to generate a compliance verification result.

[0028] In some embodiments, the method further includes:

[0029] Receiving a rule change request submitted by a regulatory authority;

[0030] Verifying the rule change request through a consensus mechanism of a blockchain;

[0031] If the verification is passed, the preset compliance rule is updated based on the rule change request.

[0032] In some embodiments, the method further comprises:

[0033] storing full-process data in the distributed block chain during processing of the transaction data;

[0034] The full-process data includes a payment request, a digital signature of a paying bank, joint calculation tasks and participant identification, risk score and payment processing results, clearing and settlement transaction identification and timestamp, and execution logs of a smart contract.

[0035] In a second aspect, the embodiments of the present application provide a cross-border payment device, comprising:

[0036] a response module configured to generate transaction data in response to a payment request and store the transaction data in a distributed block chain; the transaction data includes transaction identification and an encrypted signature;

[0037] a processing module configured to analyze the transaction data through a smart contract and determine whether to perform a collaborative security evaluation on the transaction data based on preset compliance rules;

[0038] a calculation module configured to perform joint calculation on encrypted data provided by other participants to generate a risk score of the transaction data if it is determined to perform the collaborative security evaluation;

[0039] a payment module configured to perform payment processing on the transaction data according to the risk score.

[0040] In a third aspect, the present application provides an electronic device, comprising a memory and a processor.

[0041] The memory is configured to store computer instructions; and the processor is configured to run the computer instructions stored in the memory to implement the method of any one of the first aspect.

[0042] In a fourth aspect, the present application provides a computer readable storage medium having a computer program stored thereon, the computer program being executed by a processor to implement the method of any one of the first aspect.

[0043] In a fifth aspect, the present application provides a computer program product comprising a computer program, the computer program being executed by a processor to implement the method of any one of the first aspect.

[0044] The cross-border payment method and related apparatus provided in this application generate transaction data in response to a payment request and store the transaction data in a distributed blockchain. The transaction data is parsed via a smart contract, and a collaborative security assessment is determined based on preset compliance rules. If the collaborative security assessment is determined, joint calculations are performed based on encrypted data provided by the participants in the transaction data to generate a risk score for the transaction data. Payment is then processed based on the risk score. This solution utilizes smart contracts to automatically parse transaction data and execute compliance rule judgments, replacing the traditional manual review process and significantly shortening transaction verification time. Multi-party secure joint calculations are performed on encrypted data to ensure that the original data of each participant does not leave their local machine, enabling collaborative generation of risk scores across institutions. Payment processing based on the risk score ensures that high-risk transactions are blocked before settlement, avoiding post-event risk tracing. This allows for the automation, global risk control, and real-time monitoring of the cross-border payment process while protecting privacy. Attached Figure Description

[0045] Figure 1 A scenario diagram provided for an embodiment of this application;

[0046] Figure 2 A flowchart illustrating a cross-border payment method provided in this application embodiment. Figure 1 ;

[0047] Figure 3 A flowchart illustrating a cross-border payment method provided in this application embodiment. Figure 2 ;

[0048] Figure 4 This is a schematic diagram of the structure of a cross-border payment device provided in an embodiment of this application;

[0049] Figure 5 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0050] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0051] In the embodiments of the present application, the same or similar items with substantially the same functions and effects are distinguished by using "first", "second", and the like, without limiting the sequence. Those skilled in the art can understand that "first", "second", and the like do not limit the quantity and execution sequence, and "first", "second", and the like do not necessarily mean different.

[0052] It should be noted that in the embodiments of the present application, the words "exemplary" or "for example" are used to mean example, illustration, or description. Any embodiment or design scheme described as "exemplary" or "for example" in the present application should not be interpreted as more preferred or more advantageous than other embodiments or design schemes. Rather, the words "exemplary" or "for example" are used in the specific manner to present the relevant concept.

[0053] It should be noted that the user information (including but not limited to user equipment information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, displayed data, etc.) involved in the present application are all information and data authorized by the user or authorized by all parties, and the collection, storage, use, processing, transmission, provision, disclosure, and application of the relevant data comply with the relevant laws, regulations, and standards of the relevant countries and regions, take necessary security measures, do not violate public order and good customs, and provide corresponding operation portals for users to choose authorization or refusal.

[0054] And the present application involves big data analysis of user information (including but not limited to personal biological characteristics, identity data, consumption data, asset data, electronic terminal operation data, etc.), and uses artificial intelligence technology for automatic decision-making, and makes technical solutions based on the automatic decision-making results that have a significant impact on personal rights and interests, provides corresponding operation portals for users to choose to agree or refuse the automatic decision-making results; if the user chooses to refuse, the expert decision-making process is entered.

[0055] It should be noted that the cross-border payment method and related device provided by the present application can be used in the field of financial technology or other related fields, and can also be used in any field other than the field of financial technology or other related fields. The application of the cross-border payment method and related device is not limited by the present application.

[0056] Cross-border payment is the core link of international financial transactions, involving the collaborative operation of banks, agents, and regulatory agencies in multiple countries.

[0057] Taking the payment of dollars by A bank to customers in B country as an example, the traditional process needs to be completed by relay through the international funds clearing system (SWIFT system) by the dollar clearing bank and the local agent bank in B country, and on average needs to pass through 2.6 levels of agent banks.

[0058] In this process, the paying bank, the receiving bank and the intermediary agency need to independently perform the Know Your Customer (KYC) verification and suspicious fund review, but due to the lack of trust mechanism between agencies, the external verification results cannot be directly accepted, resulting in more than 60% of the same transaction needing to be manually reviewed for more than 60 hours or even days.

[0059] At the same time, the regulatory agency relies on post-reporting audit and cannot monitor the transaction link in real time, and high-risk transactions are often discovered after clearing and settlement, which has a serious fund safety loophole. In addition, banks cannot share risk data (such as preset suspicious list and suspicious transaction model) due to privacy restrictions, resulting in a single agency being able to determine risk based on local data only, with high false negative and false positive rates, and a decrease in overall risk control accuracy of more than 40%. The existing technology cannot meet the collaborative needs of real-time payment, global risk control and privacy protection, and a new technical solution that combines privacy computing and blockchain is urgently needed.

[0060] Therefore, the embodiments of the present application provide a cross-border payment method and related device, which uses the distributed ledger and smart contract technology of the blockchain to solve the problems of trusted storage of transaction data and automatic execution of rules, and completes cross-agency risk calculation through multi-party secure calculation (MPC) technology under the premise of data invisibility, and finally forms a closed-loop process of "compliance verification-risk determination-supervision response". The core of this technical concept is to break the contradiction between data silos and repeated verification in traditional cross-border payments, while meeting the needs of privacy protection and real-time risk control.

[0061] The technical solutions of the present application and how the technical solutions of the present application solve the above technical problems will be described in detail below with specific embodiments. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of the present application will be described below with reference to the drawings.

[0062] Figure 1 A cross-border payment scenario provided by the embodiments of the present application is shown in FIG. 1, which includes a paying bank system, a receiving bank system, a blockchain network and a regulatory agency system. Figure 1

[0063] When the paying bank system receives a payment request initiated by a customer, it generates transaction data and submits the transaction data to the blockchain for storage.

[0064] The smart contract deployed in the blockchain parses the transaction data and determines whether the transaction data needs to trigger collaborative risk control. If not, it directly performs clearing and settlement to complete the payment.

[0065] ​If the risk control needs to be coordinated, the integrated multi-party secure computing engine is called to perform privacy collaborative calculation using the private data of the payer system, the payee system and the regulatory authority system to determine whether the transaction is compliant.

[0066] If the transaction is determined to be compliant, the clearing and settlement is directly performed to complete the payment. If the transaction is determined to be non-compliant, the transaction is frozen, and the reason for the transaction freezing is recorded in the blockchain.

[0067] The payee system obtains the payment result (success / failure) from the blockchain, updates the payee account state, and feeds back the final state of the transaction to the payer and the customer.

[0068] In the scenario shown in FIG. 1, the cross-border payment method provided by the embodiments of the present application is described below. Figure 1 Figure 2

[0069] Figure 2 A flowchart of a cross-border payment method provided by the embodiments of the present application is shown in FIG. 2, which includes the following steps. Figure 2

[0070] S201, in response to a payment request, transaction data is generated and stored in a distributed blockchain.

[0071] In some embodiments, the transaction data can include transaction identification (such as a transaction unique ID), transaction amount, payer information, payee information, timestamp, etc.

[0072] Optionally, in order to protect the information of the payer and the payee, the payer information and the payee information can be encrypted using an encryption algorithm. For example, the payer information and the payee information are encrypted using an encryption hash algorithm. Correspondingly, the payer information and the payee information can be payer hash and payee hash.

[0073] In some embodiments, when the payer receives a payment request from the customer, the payer can perform compliance verification on the payment request and generate transaction data if the compliance verification is passed.

[0074] In some embodiments, after the transaction data is generated, the transaction data can be uploaded to the blockchain for storage. The blockchain can be a consortium chain or a private chain, and the type of the blockchain is not limited by the embodiments of the present application.

[0075] S202, the transaction data is parsed by a smart contract, and whether to perform collaborative security evaluation on the transaction data is determined based on a preset compliance rule.

[0076] ​​​In some embodiments, after uploading the transaction data to the blockchain, the smart contract deployed in the blockchain can parse the transaction data, further confirm the parsing result of the transaction data based on the preset compliance rules, and determine whether to further perform security assessment on the transaction data.

[0077] The smart contract refers to an automated program deployed on the blockchain, which performs transaction and business logic processing according to preset rules without human intervention.

[0078] For example, the transaction amount and the hash of the two parties of the transaction are extracted from the transaction data. If it is determined that the transaction data is a regular transaction (such as a small payment) by using the preset compliance rules, it is determined that the transaction data is compliant and does not need to be further security assessed. If it is determined that the transaction data is an irregular transaction (such as a large payment or a transaction target object) by using the preset compliance rules, it is determined that the transaction data needs to be further security assessed.

[0079] S203, if it is determined to perform collaborative security assessment, joint calculation is performed based on the encrypted data provided by the parties involved in the transaction data to generate a risk score of the transaction data.

[0080] In some embodiments, the parties involved in the transaction data can include a payer system, a payee system, and a regulatory authority system.

[0081] The encrypted data provided by the parties can include KYC lists, suspicious transaction patterns, and other data provided by the parties.

[0082] In some embodiments, the parties can encrypt the KYC lists, suspicious transaction patterns, and other data through homomorphic encryption, zero-knowledge proof, and other methods and upload them to the blockchain. The smart contract deployed in the blockchain can call the multi-party secure computing engine to perform joint calculation on the received encrypted data and output the risk score of the transaction data.

[0083] S204, performing payment processing on the transaction data according to the risk score.

[0084] In some embodiments, after determining the risk score, it can be determined whether the transaction data is compliant based on the size relationship of the preset threshold of the risk score. The risk score is in plaintext data, for example, 75 points. The preset threshold can be set based on actual needs, for example, 60 points, and the specific size of the preset threshold is not limited in the embodiments of the present application.

[0085] In some embodiments, if the risk score is less than the preset threshold, it is determined that the transaction data is compliant, and the transaction data is cleared and settled.

[0086] In some embodiments, if the risk score is greater than or equal to a preset threshold, it is determined that the transaction data is compliant, and the transaction data is frozen.

[0087] In some embodiments, after freezing the transaction data, a warning message can be sent to the regulatory agency system. The warning message can include transaction identification and information of the transaction parties.

[0088] The cross-border payment method provided by the embodiments of the present application generates transaction data in response to a payment request and stores the transaction data in a distributed blockchain. The transaction data is parsed by a smart contract, and it is determined whether to perform collaborative security assessment on the transaction data based on preset compliance rules. If it is determined to perform collaborative security assessment, joint calculation is performed based on the encryption data provided by the parties involved in the transaction data to generate a risk score of the transaction data. The transaction data is processed for payment according to the risk score. The smart contract automatically parses the transaction data and executes the compliance rule judgment, replacing the traditional manual audit process, significantly shortening the transaction verification time. Multi-party secure joint calculation is performed on the encryption data to ensure that the original data of each party does not leave the local, realizing the collaborative generation of cross-institution risk scores. The transaction data is processed for payment based on the risk score, ensuring that high-risk transactions are blocked before clearing, avoiding post-trace risks. The cross-border payment process can be automated, globally risk-controlled and real-time supervised under the premise of protecting privacy.

[0089] Based on the above embodiments, the cross-border payment method provided by the embodiments of the present application will be further described below. Figure 3

[0090] Figure 3 The flowchart of the cross-border payment method provided by the embodiments of the present application is shown in Figure 2 As shown in Figure 3 , it includes:

[0091] S301, in response to a payment request, performing compliance verification on the payment request.

[0092] In some embodiments, when the payment request is received, the payment request can be verified for compliance based on a preset compliance verification strategy.

[0093] In one possible implementation, zero-knowledge proof can be used to verify the payment request for compliance.

[0094] For example, the transaction amount, transaction parties and other information in the payment request can be extracted, and the corresponding mathematical proof can be generated using a zero-knowledge proof algorithm. The payee bank system can call the internal verification system to verify whether the mathematical proof is valid. If it is valid, it is determined that the transaction data is compliant.

[0095] ​In a possible implementation, the payment request can be verified for compliance by local customer authentication.

[0096] For example, the payment line system invokes an internal verification system to verify the customer identity, account balance, and transaction authority, and perform KYC checks to check whether the customer is on an internal exception list, whether the transaction behavior is abnormal, and the like, to verify the payment request for compliance.

[0097] S302, if the compliance verification is passed, transaction data is generated based on the compliance verification result, and the transaction data is stored in the distributed block chain.

[0098] In some embodiments, the compliance verification result, transaction identification, transaction amount, payee information, payee information, timestamp, and the like can be associated and packaged in a predefined association or assembly rule to generate initial transaction data.

[0099] After obtaining the initial transaction data, the payment line uses its private key to encrypt and sign the initial transaction data to obtain transaction data. The transaction data is broadcast to the alliance block chain network.

[0100] S303, the transaction data is parsed by the smart contract to determine the key fields of the transaction data.

[0101] In some embodiments, the key fields of the transaction data can include the transaction amount and the hash of the transaction participants.

[0102] For example, the transaction data can be parsed by using function parameters or assembly to extract the key fields of the transaction data.

[0103] S304, if it is determined that the key fields meet the risk control conditions based on the preset compliance rules, the transaction data is subjected to collaborative security assessment.

[0104] In some embodiments, after obtaining the key fields, the key fields can be compared with the preset compliance rules to determine whether the key fields meet the risk control conditions.

[0105] For example, if the transaction amount is less than the preset amount and the hash of the payee and the payee is not in the preset list, it is determined that the key fields do not meet the risk control conditions, which is a regular transaction and does not need to be subjected to collaborative security assessment, and can be directly subjected to clearing and settlement.

[0106] If the transaction amount is greater than or equal to the preset amount, and the hash of the payee and the payee is in the preset list, it is determined that the key fields meet the risk control conditions, and need to be subjected to collaborative risk control.

[0107] In some embodiments, to further improve the accuracy of determining that the key fields meet the risk control conditions, the preset compliance rules can also be updated.

[0108] For example, receiving a rule change request submitted by a regulatory authority; verifying the rule change request through a consensus mechanism of the blockchain; if the verification is passed, updating the preset compliance rules based on the rule change request.

[0109] The consensus mechanism of the blockchain can refer to a technology by which nodes of the blockchain reach an agreement through a preset algorithm (such as PBFT), for example, the nodes vote to pass the rule change.

[0110] For example, the smart contract receives a rule change request (such as adjusting the risk threshold) submitted by a regulatory authority, and verifies the request legality through the consensus mechanism of the alliance chain. If the verification is passed, the smart contract automatically updates the preset compliance rules to ensure that the new rules take effect immediately. Through the dynamic rule updating mechanism, the real-time and global consistency of the compliance rules are ensured, the delay of manual approval is avoided, and the accuracy of determining that the key fields meet the risk control conditions based on the preset compliance rules is improved

[0111] S305, based on the encrypted data provided by the participants of the transaction data, joint calculation is performed to generate a risk score of the transaction data.

[0112] In some embodiments, when it is determined that collaborative risk control is needed, the smart contract can call the multi-party secure computing engine to jointly calculate the participants of the transaction data.

[0113] For example, a joint calculation request is sent to the participants; encrypted data provided by the participants is obtained; the encrypted data is provided by the participants based on a secret sharing strategy or a homomorphic encryption strategy; the encrypted data is jointly calculated using a preset calculation strategy to obtain a risk score; and the risk score is clear text data.

[0114] For example, each participant inputs local private KYC list, suspicious transaction pattern and other data through secret sharing or homomorphic encryption into the multi-party secure computing engine without revealing the original data.

[0115] After receiving the data input by each participant, the multi-party secure computing engine executes a preset algorithm to calculate the risk score of the transaction data.

[0116] For example, the risk score calculation can be performed in the following manner:

[0117] Risk score = (number of times of hitting abnormal payee list x weight A) + (number of times of hitting high-risk area list of payee x weight B) + (transaction amount anomaly index x weight C) +...

[0118] In some embodiments, after obtaining the risk score, the multi-party secure computing engine can return the risk score to the smart contract.

[0119] S306, performing payment processing on the transaction data according to the risk score.

[0120] In some embodiments, the specific implementation of the step S306 shown in the embodiments of the present application is similar to the specific implementation of the step S204 shown in the embodiments Figure 2 The specific implementation of the step S204 shown in the embodiments is similar, and will not be described here.

[0121] In some embodiments, a pre-trained machine learning model (such as federated learning) can also be used to process the data provided by each participant, and output whether the transaction data is high-risk. If it is high-risk transaction data, it is frozen, and if it is low-risk transaction data, it triggers clearing and settlement.

[0122] In some embodiments, for transaction data that can perform clearing and settlement, the smart contract automatically generates settlement instructions and completes fund transfer through the currency system or settlement system on the chain.

[0123] In some embodiments, the payee bank system can listen to events on the blockchain, capture settlement successful transaction data, verify the digital signature of the transaction data, automatically update the corresponding payee account balance, and send a credit notice to the payee.

[0124] In some embodiments, if the transaction is frozen, the payer bank system can obtain the corresponding freezing reason from the blockchain and send a notification to the customer.

[0125] In some embodiments, during the process of processing transaction data, the whole process data in the transaction data process can also be stored in a distributed blockchain.

[0126] The whole process data includes payment request, payer bank digital signature, joint computing task and participant identifier, risk score and payment processing result, clearing and settlement transaction identifier and timestamp, and execution log of the smart contract.

[0127] In summary, the cross-border payment method provided by the embodiments of the present application uses smart contracts to replace manual review, shortens the traditional hour-level compliance process to minutes, for example, transaction verification and risk determination are completed synchronously on the chain without the need for cross-institutional manual collaboration; multi-party secure computation technology realizes cross-institutional risk score calculation under the premise of data invisibility, without sharing the original KYC list, breaking the data silos; high-risk transactions are blocked immediately before clearing, for example, if the risk score exceeds the threshold, the transaction is automatically frozen and a regulatory alert is triggered, avoiding illegal fund transfer. The transaction party identity is stored in the form of hash, only authorized nodes can apply for decryption; the regulatory rules are updated in real time through the alliance chain consensus mechanism to ensure the timeliness of the risk control strategy. The technical solution of the embodiments of the present application realizes efficient compliance, global risk control and real-time supervision of the cross-border payment process on the premise of protecting privacy, significantly reducing compliance costs and systemic risks.

[0128] On the basis of the above-mentioned embodiments, the application further provides a cross-border payment device.

[0129] Figure 4 The structural schematic diagram of the cross-border payment device 40 provided by the embodiments of the application is shown in Figure 4 , which comprises:

[0130] The response module 401 is configured to generate transaction data in response to a payment request and store the transaction data in a distributed block chain; the transaction data comprises a transaction identifier and an encrypted signature.

[0131] The processing module 402 is configured to parse the transaction data through a smart contract and determine whether to perform collaborative security assessment on the transaction data based on preset compliance rules.

[0132] The calculation module 403 is configured to perform joint calculation on encrypted data provided by other participants to generate a risk score of the transaction data if it is determined to perform collaborative security assessment.

[0133] The payment module 404 is configured to perform payment processing on the transaction data according to the risk score.

[0134] In some embodiments, the payment module 404 is configured to perform clearing and settlement on the transaction data if the risk score is less than a preset threshold, and freeze the transaction data and output a warning information if the risk score is greater than or equal to the preset threshold.

[0135] In some embodiments, the response module 401 is configured to perform compliance verification on the payment request in response to the payment request, generate a compliance verification result, generate initial transaction data based on the compliance verification result if the compliance verification result passes, and obtain the transaction data by encrypting and signing the initial transaction data.

[0136] In some embodiments, the processing module 402 is configured to parse the transaction data through a smart contract and determine a key field of the transaction data; and perform collaborative security assessment on the transaction data if it is determined that the key field meets a risk control condition based on preset compliance rules.

[0137] In some embodiments, the calculation module 403 is configured to send a joint calculation request to a participant, obtain encrypted data provided by the participant, perform joint calculation on the encrypted data using a preset calculation strategy to obtain a risk score, and output the risk score as plaintext data; the encrypted data is provided by the participant based on a secret sharing strategy or a homomorphic encryption strategy.

[0138] In some embodiments, the response module 401 is configured to perform compliance verification on the payment request based on a zero-knowledge proof to generate a compliance verification result, or perform compliance verification on the payment request based on local customer identity verification to generate a compliance verification result.

[0139] In some embodiments, the processing module 402 is configured to receive a rule change request submitted by a regulatory authority, verify the rule change request through a consensus mechanism of the blockchain, and if the verification is passed, update the preset compliance rules based on the rule change request.

[0140] In some embodiments, the processing module 402 is configured to store full-process data in the process of processing transaction data in the distributed blockchain, wherein the full-process data includes a payment request, a digital signature of a paying bank, joint computing tasks and participant identities, risk scores and payment processing results, clearing and settlement transaction identities and timestamps, and execution logs of smart contracts.

[0141] The cross-border payment device provided by the embodiments of the present application can perform the cross-border payment method shown in any of the above embodiments, and has similar principles and technical effects, which will not be described here.

[0142] The embodiments of the present application further provide an electronic device.

[0143] Figure 5 As shown in the structural schematic diagram of the electronic device 50 provided by the embodiments of the present application, Figure 5 The electronic device can include a transceiver 501, a processor 502, and a memory 503.

[0144] The processor 502 executes computer execution instructions stored in the memory, so that the processor 502 performs the schemes in the above embodiments. The processor 502 can be a general-purpose processor, including a central processing unit CPU, a network processor NP, etc.; it can also be a digital signal processor DSP, an application-specific integrated circuit ASIC, a field programmable gate array FPGA or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components.

[0145] The memory 503 is connected with the processor 502 through a system bus and completes mutual communication, and the memory 503 is used for storing computer program instructions.

[0146] The transceiver 501 can perform receiving and sending data and instructions.

[0147] Optionally, the electronic device 50 can further include a communication interface 504, so as to communicate with external or internal devices through the communication interface 503, the external device can be a client (for example, a mobile phone, a tablet) for example. In a specific implementation, if the communication interface 504, the memory 503 and the processor 502 are independently implemented, the communication interface 504, the memory 503 and the processor 502 can be connected with each other through a bus and complete communication between each other.

[0148] The system bus can be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. The system bus can be divided into an address bus, a data bus, a control bus, etc. For the convenience of representation, only one thick line is used in the figure, but it does not mean that there is only one bus or only one type of bus. The transceiver is used to realize the communication between the database access device and other computers (for example, a client, a read-write library and a read-only library). The memory can include random access memory (RAM), and can also include non-volatile memory.

[0149] Optionally, in a specific implementation, if the communication interface 504, the memory 503 and the processor 502 are integrated on a chip, the communication interface 504, the memory 503 and the processor 502 can complete communication through an internal interface.

[0150] The embodiment of the application further provides a chip for running instructions, which is used for executing the technical solutions of the monitoring method in the above-mentioned embodiments.

[0151] In the embodiment of the application, a computer readable storage medium is further provided, and the computer readable storage medium stores a computer program. The computer program is executed by a processor to implement the technical solutions of the monitoring method embodiments, and the implementation principle and technical effects are similar, and details are not repeated here.

[0152] In a possible implementation, the computer readable medium can include a Random Access Memory (RAM), a Read-Only Memory (ROM), a compact disc read-only memory (CD-ROM) or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that is suitable for storing desired program code in the form of instructions or data structures and that can be accessed by a computer. Also, any connection is properly termed a computer readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. Disk and disc, as used herein, include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray® disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer readable media.

[0153] The application also provides a computer program product comprising a computer program which, when executed by a processor, implements the technical solutions of the API gateway commissioning verification method embodiments described above, and has similar implementation principles and technical effects, which will not be described here.

[0154] In the specific implementation of the terminal device or the server described above, it should be understood that the processor can be a central processing unit (CPU), and can also be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. The general-purpose processor can be a microprocessor or any conventional processor, etc. The steps of the method disclosed in the embodiments of the application can be directly embodied as being executed by a hardware processor, or executed by a combination of hardware and software modules in the processor.

[0155] Those skilled in the art can understand that all or part of the steps of any of the method embodiments described above can be completed by hardware related to program instructions. The foregoing program can be stored in a computer readable storage medium, and when the program is executed, all or part of the steps of the foregoing method embodiments are executed.

[0156] If the technical solutions of the present application are realized in the form of software and sold or used as products, they can be stored in a computer readable storage medium. Based on this understanding, all or part of the technical solutions of the present application can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes a computer program or a plurality of instructions. The computer software product makes a computer device (which can be a personal computer, a server, a network device or similar electronic equipment) execute all or part of the steps of the method embodiments of the present application.

[0157] It should be noted that, for the foregoing method embodiments, in order to simply describe, they are all described as a combination of a series of actions, but those skilled in the art should know that the present application is not limited to the order of the actions described, because according to the present application, certain steps can be performed in other order or simultaneously. Secondly, those skilled in the art should know that the embodiments described in the specification all belong to optional embodiments, and the actions and modules involved are not necessarily required by the present application.

[0158] It should be further noted that, although each step in the flowchart is displayed in sequence according to the arrow, these steps are not necessarily executed in sequence according to the arrow. Unless otherwise stated in this document, the execution of these steps has no strict order limitation, and these steps can be executed in other order. Moreover, at least part of the steps in the flowchart can include multiple sub-steps or multiple stages, which are not necessarily executed at the same time, but can be executed at different times, and the execution order of these sub-steps or stages is not necessarily sequential, but can be executed in rotation or alternation with other steps or sub-steps or stages of other steps.

[0159] It should be understood that the device embodiments described above are only schematic, and the device of the present application can also be realized in other ways. For example, the division of units / modules in the above embodiments is only a logical function division, and actual implementation can have another division manner. For example, a plurality of units, modules or components can be combined, or can be integrated into another system, or some features can be ignored or not executed.

[0160] In addition, each functional unit / module in the embodiments of the present application can be integrated in one unit / module, or each unit / module can exist physically, or two or more units / modules can be integrated together. The integrated unit / module can be realized in the form of hardware or in the form of a software program module.

[0161] The integrated unit / module, if realized in the form of hardware, can be a digital circuit, an analog circuit, etc. The physical realization of the hardware structure includes but is not limited to transistors, memristors, etc. Unless otherwise specified, the processor can be any appropriate hardware processor, such as a CPU, a GPU, an FPGA, a DSP, an ASIC, etc. Unless otherwise specified, the storage unit can be any appropriate magnetic storage medium or magneto-optical storage medium, such as a resistive random access memory (RRAM), a dynamic random access memory (DRAM), a static random access memory (SRAM), an enhanced dynamic random access memory (EDRAM), a high-bandwidth memory (HBM), a hybrid memory cube (HMC), etc.

[0162] The integrated unit / module, if realized in the form of a software program module and sold or used as an independent product, can be stored in a computer readable storage medium. Based on this understanding, the technical solutions of the present application, essentially or the part that makes a contribution to the prior art, or the whole or part of the technical solutions can be embodied in the form of a software product. The computer software product is stored in a storage medium, and includes a number of instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the embodiments of the method of the present application. The aforementioned storage medium includes: a U disk, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk or an optical disk, and various other media capable of storing program codes.

[0163] In the above embodiments, the description of each embodiment has its own focus, and the parts not described in detail in a certain embodiment can be referred to the relevant description of other embodiments. The technical features of the above embodiments can be combined in any manner. In order to make the description simple, not all possible combinations of the technical features in the above embodiments are described, but as long as the combinations of the technical features do not exist contradictory, it should be considered as the scope of the present application.

[0164] Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present application, and not to limit them; although the present application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand: they can still modify the technical solutions recorded in the foregoing embodiments, or make equivalent replacement for part or all of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the scope of the technical solutions of the embodiments of the present application.

Claims

1. A cross-border payment method, characterized in that, The method comprises: generating transaction data in response to a payment request and storing the transaction data in a distributed blockchain; analyzing the transaction data through a smart contract and determining whether to perform collaborative security assessment on the transaction data based on preset compliance rules; if it is determined to perform the collaborative security assessment, performing joint calculation based on encrypted data provided by parties involved in the transaction data to generate a risk score of the transaction data; performing payment processing on the transaction data according to the risk score.

2. The method of claim 1, wherein, The payment processing on the transaction data according to the risk score comprises: if the risk score is less than a preset threshold, clearing and settling the transaction data; if the risk score is greater than or equal to the preset threshold, freezing the transaction data and outputting a warning information.

3. The method of claim 2, wherein, The generating of the transaction data in response to the payment request comprises: performing compliance verification on the payment request to generate a compliance verification result; generating initial transaction data based on the compliance verification result if the compliance verification result is passed; encrypting and signing the initial transaction data to obtain the transaction data.

4. The method of claim 1, wherein, The analyzing of the transaction data through the smart contract and the determining of whether to perform the collaborative security assessment on the transaction data based on the preset compliance rules comprise: analyzing the transaction data through the smart contract to determine key fields of the transaction data; if it is determined that the key fields meet risk control conditions based on the preset compliance rules, performing the collaborative security assessment on the transaction data.

5. The method according to claim 1 or 4, characterized in that, The joint calculation based on the encrypted data provided by the parties involved in the transaction data to generate the risk score of the transaction data comprises: sending a joint calculation request to the parties involved; obtaining encrypted data provided by the parties involved; the encrypted data is provided by the parties involved based on a secret sharing strategy or a homomorphic encryption strategy; performing joint calculation on the encrypted data by using a preset calculation strategy to obtain the risk score; the risk score is plaintext data.

6. The method of claim 3, wherein, The compliance verification on the payment request to generate the compliance verification result comprises: performing compliance verification on the payment request based on zero-knowledge proof to generate the compliance verification result; or performing compliance verification on the payment request based on local customer identity verification to generate the compliance verification result. The method further comprises:

7. The method according to claims 1-6, characterized in that, receiving a rule change request submitted by a regulatory authority; verifying the rule change request through a consensus mechanism of the blockchain; if the verification is passed, updating the preset compliance rules based on the rule change request. The method further comprises:

8. The method according to any one of claims 1 to 6, characterized in that, storing whole-process data in the process of processing the transaction data in the distributed blockchain; wherein the whole-process data comprises a payment request, a digital signature of a paying bank, joint calculation tasks and party identifiers, a risk score and a payment processing result, a clearing and settlement transaction identifier and a timestamp, and an execution log of a smart contract. The method comprises:

9. A cross-border payment device, characterized by, a response module configured to generate transaction data in response to a payment request and store the transaction data in a distributed blockchain; the transaction data comprises a transaction identifier and an encrypted signature. ​ The processing module is configured to parse the transaction data by using the smart contract, and determine whether to perform the collaborative security assessment on the transaction data based on preset compliance rules. The computing module is configured to, if it is determined to perform the collaborative security assessment, perform joint calculation on the encrypted data provided by the other participants to generate a risk score of the transaction data. The payment module is configured to perform payment processing on the transaction data according to the risk score.

10. An electronic device, comprising: The computer program is stored in the memory and executed by the processor to implement the method in any one of claims 1-8. The computer program is stored in the memory and executed by the processor to implement the method in any one of claims 1-8. The computer program is stored in the memory and executed by the processor to implement the method in any one of claims 1-8.

11. A computer readable storage medium, characterized in that, ​ 12. A computer program product, characterised in that, ​

Images