Data processing method and device based on payment, equipment, medium and program product

Abstract

The invention provides a payment-based data processing method and device, equipment, a medium and a program product, and relates to the technical field of block chains. The method comprises the following steps: receiving a target project payment request sent by client equipment, and obtaining initial payment information of a target project; the target project payment request is triggered by the target user through a payment management interface of the client device; verifying the initial payment information by adopting a preset smart contract, and storing the verified initial payment information in a block chain; in response to the received target project payment request, target payment information is obtained, a target payment list is generated based on the target payment information, and the target payment information is payment information used for payment and determined when the target project payment request is received; matching the initial payment information read from the block chain with the target payment information to obtain a matching result; and if it is determined that the matching result is successful, payment operation is executed.

Description

Technical Field

[0001] The present application relates to the field of blockchain technology, and in particular to a payment-based data processing method, device, equipment, medium and program product. Background Art

[0002] With the rapid development of information technology, the payment system has become an indispensable part of daily life. The payment system connects banks, payment platforms and service providers through the Internet. Users can conveniently pay for water, electricity, gas, tuition, property fees and other fees by entering the corresponding payment information.

[0003] Currently, after the user enters the payment information and sends a payment request for online payment, the system will directly jump to the payment interface to allow the user to make the payment. This results in poor security of the corresponding payment information used by the user for payment, which in turn affects the user experience. Summary of the invention

[0004] The present application provides a payment-based data processing method, device, equipment, medium and program product, which are used to solve the problem in the prior art that after the user enters the payment information and sends a payment request for online payment, the user will be directly redirected to the payment interface to make the payment, which causes the payment information corresponding to the user's payment to be less secure, thereby affecting the user experience.

[0005] In a first aspect, the present application provides a payment-based data processing method, comprising:

[0006] Receive a payment request for a target item sent by a client device, and obtain initial payment information for the target item; the payment request for the target item is triggered by the target user through a payment management interface of the client device;

[0007] The initial payment information is verified using a preset smart contract, and the verified initial payment information is stored in the blockchain;

[0008] In response to receiving the payment request for the target item, obtaining target payment information and generating a target payment list based on the target payment information, wherein the target payment information is payment information for payment determined when the payment request for the target item is received;

[0009] Matching the initial payment information read from the blockchain with the target payment information to obtain a matching result;

[0010] If the matching result is determined to be successful, the payment operation is performed.

[0011] In a possible design, the target item payment request includes target user information;

[0012] The obtaining of the initial payment information of the target project includes:

[0013] Determining whether the target user has a payment record for the target item based on the target user information;

[0014] If it exists, obtaining the most recent payment record of the target project from the blockchain, sending the preset payment information in the most recent payment record to the client device for display on the payment management interface, and receiving the initial payment information of the target project sent by the client device, where the initial payment information is determined based on the preset payment information;

[0015] If not, initial payment information of the target item sent by the client device is received, where the initial payment information is input by the user in the payment management interface.

[0016] In a possible design, the verification of the initial payment information by using a preset smart contract includes:

[0017] Verifying the initial payment information using the verification rules in the preset smart contract;

[0018] If it is determined that the initial payment information satisfies the verification rule, then the verification result is determined to be passed;

[0019] If it is determined that the initial payment information does not satisfy the verification rule, the verification result is determined to be failed.

[0020] In a possible design, the verification rules of the preset smart contract include format verification rules and amount verification rules;

[0021] The verifying the initial payment information by using the verification rules in the preset smart contract includes:

[0022] Using the format verification rules to verify the format of each payment information in the initial payment information;

[0023] The payment amount in the initial payment information is verified using the amount verification rule.

[0024] In a possible design, the initial payment information read from the blockchain is matched with the target payment information to obtain a matching result, including:

[0025] Matching the initial payment information read from the blockchain with the target payment information to determine whether the initial payment information read from the blockchain is completely consistent with the corresponding payment information in the target payment information;

[0026] In response to the corresponding payment information being completely consistent, determining that the matching result is a successful match;

[0027] In response to the corresponding payment information being not completely consistent, it is determined that the matching result is a matching failure.

[0028] In a possible design, after generating a target payment list based on the target payment information, the method further includes:

[0029] Storing the target payment list in the blockchain;

[0030] After the payment operation is performed, the method further includes:

[0031] Determine the payment status of the target project and use the preset smart contract to update the payment status in the target payment list in the blockchain.

[0032] In a possible design, after determining the payment status of the target project, the method further includes:

[0033] If it is determined that the payment status of the target item is successfully paid, a preset smart contract is used to send multiple candidate payment notification methods to the client device;

[0034] Receiving a preset payment notification method triggered by a client device through a target user;

[0035] The payment result of the target item is sent to the client device according to the preset payment notification method.

[0036] In a second aspect, the present application provides a payment-based data processing device, comprising: a receiving module, configured to receive a payment request for a target item sent by a client device;

[0037] An acquisition module is used to obtain the initial payment information of the target project;

[0038] A verification module, used to verify the initial payment information using a preset smart contract;

[0039] A storage module, used to store the verified initial payment information in the blockchain;

[0040] The acquisition module is further used to, in response to receiving the payment request for the target item, acquire the target payment information and generate a target payment list based on the target payment information;

[0041] A matching module, used to match the initial payment information read from the blockchain with the target payment information to obtain a matching result;

[0042] The execution module is used to execute the payment operation if the matching result is determined to be a successful match.

[0043] In a third aspect, an embodiment of the present application provides an electronic device, comprising: at least one processor and a memory; the memory stores computer execution instructions; the at least one processor executes the computer execution instructions stored in the memory, so that the at least one processor executes the payment-based data processing method described in the first aspect and various possible designs of the first aspect.

[0044] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, in which computer execution instructions are stored. When a processor executes the computer execution instructions, the payment-based data processing method described in the first aspect and various possible designs of the first aspect is implemented.

[0045] In a fifth aspect, an embodiment of the present application provides a computer program product, including a computer program. When the computer program is executed by a processor, it implements the payment-based data processing method described in the first aspect and various possible designs of the first aspect.

[0046] The payment-based data processing method, device, equipment, medium and program product provided by the present application receive a payment request for a target project sent by a client device and obtain the initial payment information of the target project; the payment request for the target project is triggered by the target user through the payment management interface of the client device; the initial payment information is verified by a preset smart contract, and the verified initial payment information is stored in the blockchain; in response to receiving the payment request for the target project, the target payment information is obtained and a target payment list is generated based on the target payment information, the target payment information is the payment information for payment determined when the payment request for the target project is received; the initial payment information read from the blockchain is matched with the target payment information to obtain a matching result; if the matching result is determined to be a successful match, the payment operation is executed. Since the payment request for the target project triggered by the target user through the payment management interface of the client device is received, the initial payment information of the target project is obtained, and the initial payment information includes the information required for payment of the target project. In order to ensure the standardization and rationality of the payment information, the initial payment information is verified through a preset smart contract, and the initial payment information after verification is saved in the blockchain. When the payment request for the target project is received, the target payment information is obtained, and a target payment list is generated based on the target payment information. The target payment information is the payment information used for payment determined when the payment request for the target project is received. In order to prevent the target payment information from being tampered with during payment, the initial payment information is read from the blockchain and matched with the target payment information. When the matching result is determined to be a successful match, the payment operation is performed. Compared with directly jumping to the payment interface for payment after receiving the payment request, by matching the initial payment information with the target payment information, the consistency of the target payment information and the initial payment information can be guaranteed, and the target payment information can be prevented from being tampered with during the payment process, thereby enhancing the security of the target payment information corresponding to the target project, thereby improving the user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0047] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0048] Figure 1 This is an application scenario diagram of the payment-based data processing method applicable to the embodiment of the present application;

[0049] Figure 2 A flowchart of a payment-based data processing method provided in one embodiment of the present application;

[0050] Figure 3 A flowchart of a payment-based data processing method provided in another embodiment of the present application;

[0051] Figure 4 A schematic diagram of the structure of a payment-based data processing device provided in one embodiment of the present application;

[0052] Figure 5 A schematic diagram of the structure of an electronic device provided in one embodiment of the present application.

[0053] The above drawings have shown clear embodiments of the present application, which will be described in more detail later. These drawings and text descriptions are not intended to limit the scope of the present application in any way, but to illustrate the concept of the present application to those skilled in the art by referring to specific embodiments. DETAILED DESCRIPTION

[0054] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.

[0055] In the technical solution of this application, the collection, storage, use, processing, transmission, provision and disclosure of information such as financial data or user data involved shall comply with the provisions of relevant laws and regulations and shall not violate public order and good morals.

[0056] It should be noted that in the embodiments of the present application, certain software, components, models and other existing solutions in the industry may be mentioned, and they should be regarded as exemplary. Their purpose is only to illustrate the feasibility of implementing the technical solution of the present application, but it does not mean that the applicant has or will necessarily use the solution.

[0057] In order to clearly understand the technical solution of the present application, the solution of the prior art is first introduced in detail.

[0058] Currently, for online payment, users generally enter payment information on the payment page of the client device, and after triggering the payment request, they will directly jump to the payment page for payment. Therefore, it is impossible to ensure that the payment information corresponding to the user when making the payment is consistent with the payment information before the payment is made, resulting in poor security of the corresponding payment information of the user when making the payment, which in turn affects the user experience.

[0059] In response to the above technical problems, the present application proposes the following technical concept: instead of directly jumping to the payment page for payment after triggering payment, the payment information to be paid is verified with the payment information before the payment is triggered, and then jumping to the payment page for payment after the verification is passed. Specifically, a payment request for a target project triggered by a target user through the payment management interface of a client device is received, and the initial payment information of the target project is obtained. In order to ensure the standardization of the initial payment information, the initial payment information is verified through a preset smart contract, and the verified information is saved in the blockchain. Since the blockchain is tamper-proof, it can be ensured that the initial payment information is not maliciously tampered with. It is understandable that before the target user triggers the target payment request, the server-side device will continuously obtain the latest initial payment information and update the initial payment information saved in the blockchain. When a payment request for a target project is received, the target payment information is obtained and a target payment list is generated based on the target payment information. It is understandable that the target payment information is the payment information used for payment determined when the payment request for the target project is received. In order to ensure that the target payment information has not been maliciously tampered with when making a payment, the initial payment information will be read from the blockchain and matched with the target payment information. When the matching result is a successful match, it means that the target payment information is the payment information that the user wants to pay and has not been maliciously tampered with, so the payment operation can be performed. Therefore, by ensuring the consistency of the payment information corresponding to the user when making a payment and the payment information before the payment, the corresponding payment information of the user when making a payment is ensured to be secure, thereby improving the user experience.

[0060] The technical solution of the present application and how the technical solution of the present application solves the above-mentioned technical problems are 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 repeated in some embodiments. The embodiments of the present application will be described below in conjunction with the accompanying drawings.

[0061] Figure 1 FIG. 1 is an application scenario diagram of the payment-based data processing method applicable to an embodiment of the present application, such as Figure 1As shown. The system corresponding to the payment-based data processing method in the embodiment of the present application may include: a client device 11 and a server device 12. The user triggers a payment request for the target project through the payment management interface of the client device 11, and the client device 11 sends the payment request for the target project to the server device 12. In response to receiving the payment request for the target project, the server device 12 obtains the initial payment information of the target project, verifies the initial payment information using a preset smart contract, and stores the verified initial payment information in the blockchain. When the server receives the payment request for the target project, the target payment information is obtained and a target payment list is generated based on the target payment information. It can be understood that the target payment information is the payment information for payment determined when the payment request for the target project is received. The server device 12 reads the initial payment information from the blockchain and matches it with the target payment information to obtain a matching result. When the server device 12 determines that the match is successful, the payment operation is performed.

[0062] Figure 2 A flowchart of a payment-based data processing method provided in an embodiment of the present application, such as Figure 2 As shown, the execution subject of this embodiment is a payment-based data processing device, which can be implemented by a computer program or a medium storing relevant computer programs, such as a USB flash drive and / or a CD, etc.; or, it can also be implemented by a physical device integrated or installed with relevant computer programs, such as a chip, an electronic device, etc. The payment-based data processing method provided in this embodiment includes the following steps:

[0063] S201, receiving a payment request for a target item sent by a client device, and obtaining initial payment information for the target item.

[0064] The target item payment request is triggered by the target user through the payment management interface of the client device. The target user is the user who triggers the payment request. The target item is the item to be paid. The initial payment information is the various payment information required for the target item to be paid before the payment is triggered. Exemplarily, if the target item is a water fee, the initial payment information may include the target user's account number, payment amount, etc. The payment management interface is an interface for managing payment.

[0065] It is understandable that each target project has a corresponding payment management interface, and different target projects have different corresponding payment management interfaces.

[0066] It is understandable that the corresponding payment information in the initial payment information varies depending on the target project.

[0067] Optionally, the target project can be set according to actual needs and is not limited in this embodiment.

[0068] Specifically, in this embodiment, the target user triggers payment for the target item through the payment management interface of the client device, and the client device sends a payment request for the target item to the server device. Further, the client device obtains the initial payment information of the payment management interface and sends it to the server device.

[0069] The initial payment information may be obtained by using a payment information collection module, which may be used to collect the payment information of the target user.

[0070] S202, using a preset smart contract to verify the initial payment information, and storing the verified initial payment information in the blockchain.

[0071] Among them, smart contracts are programs running on blockchains that can automatically execute contract terms and trigger corresponding actions when certain conditions are met. The preset smart contract has preset logic for verifying the initial payment information. Blockchain is a decentralized database technology that records and verifies transactions by dividing data into a series of blocks and linking them into a growing chain.

[0072] Specifically, in this embodiment, after the server device obtains the initial payment information, it uses the verification logic corresponding to the target item preset in the preset smart contract to verify the various payment information in the initial payment information. If the verification fails, a prompt message is sent to the client device. If the verification passes, the verified initial payment information is saved in the blockchain.

[0073] Among them, before the target user triggers payment, if the target user modifies the payment information of any item in the initial payment information, the server-side device will use the preset smart contract to re-verify the modified initial payment information, and will save the modified initial payment information that has passed the re-verification in the blockchain to update the previously saved initial payment information.

[0074] Optionally, the preset verification logic may be to verify the format of payment information, etc., which is not limited in this embodiment.

[0075] S203, in response to receiving the target project payment request, obtaining target payment information and generating a target payment list based on the target payment information.

[0076] The target payment information is the payment information used for payment determined when receiving the payment request for the target item. The target payment list is a list generated based on the target payment information and used to record the payment information of the target item, which can be in a list format.

[0077] It is understandable that the target payment list may include payment time, target user information, target items and target payment information corresponding to the target items, etc.

[0078] Specifically, in this embodiment, the target user triggers a target project payment request on the payment management interface corresponding to the target project of the client device. When the server device receives the target project payment request, it obtains the target payment information for payment determined by the target user when receiving the target project payment request, and generates a corresponding target payment list based on the obtained target payment information.

[0079] Among them, the payment information collection module can also execute to obtain target payment information.

[0080] S204, matching the initial payment information read from the blockchain with the target payment information to obtain a matching result.

[0081] Specifically, in this embodiment, the server-side device reads the previously saved initial payment information from the blockchain, and matches each item of payment information in the initial payment information with each item of payment information in the target payment information, thereby obtaining a matching result of the initial payment information and the target payment information.

[0082] S205: If the matching result is determined to be successful, the payment operation is performed.

[0083] Specifically, in this embodiment, if the server-side device determines that the initial payment information and the target payment information match successfully, then the payment operation is further performed.

[0084] It is understandable that the payment operation may include confirming the identity of the target user, payment authorization, and payment execution, etc., which is not limited in this embodiment.

[0085] The payment operation may also be performed by using a payment processing module, which can be used to perform corresponding payment operations according to target payment information.

[0086] The payment-based data processing method provided by the present application includes: receiving a payment request for a target project sent by a client device, and obtaining initial payment information of the target project; the payment request for the target project is triggered by the target user through the payment management interface of the client device; using a preset smart contract to verify the initial payment information, and storing the verified initial payment information in a blockchain; in response to receiving a payment request for a target project, obtaining target payment information and generating a target payment list based on the target payment information, the target payment information being the payment information for payment determined when the payment request for the target project is received; matching the initial payment information read from the blockchain with the target payment information to obtain a matching result; if it is determined that the matching result is a successful match, executing a payment operation. Since the payment request for the target project is triggered by the payment management interface of the client device, the initial payment information of the target project is obtained, and the initial payment information includes the information required for the payment of the target project. In order to ensure the standardization and rationality of the payment information, the initial payment information is verified by a preset smart contract, and the initial payment information after verification is stored in the blockchain. After receiving the payment request for the target project, the target payment information is obtained, and a target payment list is generated based on the target payment information. The target payment information is the payment information used for payment determined when the payment request for the target project is received. In order to prevent the target payment information from being tampered with during payment, the initial payment information is read from the blockchain and matched with the target payment information. When the match result is determined to be a successful match, the payment operation is performed. Compared to directly jumping to the payment interface to perform the payment operation after receiving the payment request, by matching the initial payment information with the target payment information, the consistency of the target payment information and the initial payment information can be guaranteed, and the target payment information can be prevented from being tampered with during the payment process, thereby enhancing the security of the target payment information corresponding to the target project, thereby improving the user experience.

[0087] As an optional implementation mode, based on the above embodiment, the target item payment request includes target user information;

[0088] Obtain the initial payment information of the target project, including:

[0089] Determine whether the target user has a payment record for the target project based on the target user information;

[0090] If it exists, the latest payment record of the target project is obtained from the blockchain, the preset payment information in the latest payment record is sent to the client device for display on the payment management interface, and the initial payment information of the target project sent by the client device is received, and the initial payment information is determined based on the preset payment information;

[0091] If it does not exist, the initial payment information of the target item sent by the client device is received, and the initial payment information is input by the user in the payment management interface.

[0092] The target user information is user information of the target user, which can be used to uniquely identify the target user, and can be identity information of the target user, a target user identification code, etc.

[0093] Specifically, in this embodiment, the server device receives the payment request for the target project, reads the target user information contained therein, and searches the blockchain for whether the target user corresponding to the target user information has a payment record for the target project. If the target user has a payment record for the target project, the latest payment information for the target project is obtained, and the preset payment information in the latest payment record is sent to the client device. The client device displays the received preset payment information on the payment management interface corresponding to the target project. The target user can complete the payment information based on the displayed preset payment information, or modify the preset payment information. When the payment information corresponding to the target project is completed and verified, the client device sends the initial payment information to the server device. If the target user does not have a payment record for the target project, wait for the user to enter it in the payment management interface corresponding to the target project. When the user completes the payment information corresponding to the target project and verifies it, the client device sends the initial payment information to the server device.

[0094] It is understandable that when a user enters payment information in the payment management interface, the user may enter the information for a target user or a non-target user, but the information is entered in the payment management interface of the target user's client device.

[0095] The payment-based data processing method provided by the present application includes target user information in the payment request of the target project; obtaining the initial payment information of the target project includes: determining whether the target user has a payment record of the target project based on the target user information; if so, obtaining the latest payment record of the target project from the blockchain, sending the preset payment information in the latest payment record to the client device for display in the payment management interface, and receiving the initial payment information of the target project sent by the client device, the initial payment information is determined based on the preset payment information; if not, receiving the initial payment information of the target project sent by the client device, the initial payment information is input by the user in the payment management interface. Since after obtaining the payment request of the target project, it is determined whether the target user has a payment record of the target project according to the target user information included in the payment request of the target project, when the target user has a payment record of the target project, the preset payment information of the latest payment record of the target project can be sent to the client device and displayed in the payment management interface, thereby reducing the number of manual inputs by the user, and further reducing the probability of errors caused by manual input.

[0096] As an optional implementation, based on the above embodiment, a preset smart contract is used to verify the initial payment information, including:

[0097] Use the verification rules in the preset smart contract to verify the initial payment information;

[0098] If it is determined that the initial payment information meets the verification rules, the verification result is determined to be passed;

[0099] If it is determined that the initial payment information does not meet the verification rules, the verification result is determined to be failed.

[0100] Specifically, in this embodiment, the verification rules in the preset smart contract are used to verify each item of payment information in the initial payment information. Each item of payment information may correspond to different verification rules. If each item of payment information satisfies the corresponding verification rules, the verification result is determined to be passed. If any item of payment information does not satisfy the corresponding verification rules, the verification result is determined to be failed.

[0101] Furthermore, if the verification fails, the server device will send the verification result to the client device, and the client device will display an error prompt on the payment management page for the payment information that failed the verification.

[0102] Optionally, the verification rules may include payment information format verification, integrity verification, external data verification, etc., which can be independently limited according to actual applications and are not limited in this embodiment.

[0103] It is understandable that the verification rules in the preset smart contract may include multiple verification types. The preset smart contract may perform multiple types of verification on the initial payment information.

[0104] The payment-based data processing method provided by the present application uses a preset smart contract to verify the initial payment information, including: using the verification rules in the preset smart contract to verify the initial payment information; if it is determined that the initial payment information meets the verification rules, then the verification result is determined to be passed; if it is determined that the initial payment information does not meet the verification rules, then the verification result is determined to be failed. Since the verification rules in the preset smart contract are used to verify the initial payment information and determine the verification result, the security, accuracy and integrity of the data can be guaranteed, and automated verification can reduce the time of manual review and improve the efficiency of payment processing.

[0105] As an optional implementation, based on the above embodiment, the verification rules of the preset smart contract include format verification rules and amount verification rules;

[0106] The initial payment information is verified using the verification rules in the preset smart contract, including:

[0107] The format validation rules are used to validate the formats of various payment information in the initial payment information; the amount validation rules are used to validate the payment amounts in the initial payment information.

[0108] Among them, the format validation rule is used to check whether the payment information corresponding to the target project conforms to the expected format. The amount validation rule is used to ensure the rationality and correctness of the payment amount.

[0109] Optionally, the format validation rules may include field non-empty validation, data type validation, format matching, and length restriction, etc., which are not limited in this embodiment.

[0110] The fields can be the payment information in the initial payment information. Field non-empty validation is used to ensure that the required fields are not empty. Data type validation is used to confirm whether the data type of the field is correct. Format matching is used to check whether the string conforms to a specific format and perform regular expression matching on the numeric field to ensure that its format is correct. Length restriction is used to determine the maximum or minimum length of the string field.

[0111] Optionally, the amount verification rules may include value range checking, amount matching, etc., which are not limited in this embodiment.

[0112] Among them, the value range check is used to confirm whether the amount field is within a reasonable range, and whether the amount does not exceed a certain upper limit, or is not lower than a certain lower limit. The amount matching is used to confirm whether the payment amount matches the cost corresponding to the target item.

[0113] Specifically, in this embodiment, the server device verifies the format of each payment information in the initial payment information according to the format verification rules, such as ensuring that the required items in the payment information are not empty and the corresponding fields conform to the corresponding formats, etc. The payment amount is verified using the amount verification rules, such as the payment amount is not less than the amount owed or the preset amount, and is not higher than the preset upper limit amount, etc.

[0114] The payment-based data processing method provided by the present application includes format verification rules and amount verification rules in the preset smart contract verification rules; the verification rules in the preset smart contract are used to verify the initial payment information, including: using the format verification rules to verify the formats of each payment information in the initial payment information; using the amount verification rules to verify the payment amount in the initial payment information. Since the format verification rules are used to verify the formats of each payment information in the initial payment information, it is ensured that the format of all input payment information is correct, reducing problems caused by incorrect payment information formats. And the amount verification rules are used to verify the payment amount in the initial payment information, thereby ensuring that the payment amount is reasonable and in line with expectations.

[0115] As an optional implementation, based on the above embodiment, the initial payment information read from the blockchain is matched with the target payment information to obtain a matching result, including:

[0116] Match the initial payment information read from the blockchain with the target payment information to determine whether the initial payment information read from the blockchain is completely consistent with the corresponding payment information in the target payment information;

[0117] In response to the corresponding payment information being completely consistent, determining that the matching result is a successful match;

[0118] In response to the corresponding payment information being not completely consistent, it is determined that the matching result is a matching failure.

[0119] Specifically, in this embodiment, the server-side device will perform a one-to-one match between the verified initial payment information read from the blockchain and the various payment information in the target payment information. If the various payment information in the verified initial payment information read from the blockchain and the various payment information in the target payment information are all one-to-one corresponding to each other, then the matching result is determined to be a successful match. If there is at least one payment information that does not correspond to the various payment information in the verified initial payment information and the various payment information in the target payment information, then the matching result is determined to be a failed match.

[0120] The payment-based data processing method provided in the present application matches the initial payment information read from the blockchain with the target payment information to obtain a matching result, including: matching the initial payment information read from the blockchain with the target payment information, and determining whether the initial payment information read from the blockchain is completely consistent with the corresponding payment information in the target payment information; in response to the corresponding payment information being completely consistent, determining the matching result to be a successful match; in response to the corresponding payment information being not completely consistent, determining the matching result to be a failed match. Since the target payment information is used for payment, the initial payment information that has been verified is matched with the corresponding payment information in the target payment information. If the initial payment information that has been verified is consistent with the corresponding payment information in the target payment information, it is determined to be a successful match, indicating that the target payment information is accurate. If the initial payment information that has been verified is inconsistent with the corresponding payment information in the target payment information, it is determined to be a failed match, indicating that the target payment information may be at risk of being modified. Therefore, by matching the verified initial payment information with the corresponding payment information in the target payment information, the security of the target payment information can be ensured, thereby ensuring the payment security of the target user.

[0121] As an optional implementation manner, based on the above embodiment, after generating the target payment list based on the target payment information, the method further includes:

[0122] Store the target payment list in the blockchain;

[0123] After performing the payment operation, the method further includes:

[0124] Determine the payment status of the target project and use the preset smart contract to update the payment status in the target payment list in the blockchain.

[0125] Among them, the payment status of the target project may include payment success or payment failure.

[0126] Specifically, in this embodiment, the server-side device stores the generated target payment list in the blockchain, obtains the payment status of the target item after executing the payment status, and uses a preset smart contract to update the payment status in the corresponding target payment list in the blockchain based on the preset identification information.

[0127] Optionally, the preset identification information is used to search for or obtain the corresponding target payment list previously stored. The preset identification information may be identification information of the target payment list, etc., or other identification information, which is not limited in this embodiment.

[0128] Among them, the identification information of the target payment list is the identification information that uniquely identifies the target payment list, which can be the identification code of the target payment list, etc.

[0129] It can be understood that the target payment list is saved as a payment record credential. The target user can trigger a payment record query request on the payment record interface of the client device. The server device receives the payment record query request and can obtain the corresponding target payment list from the blockchain and send it to the client device for display.

[0130] Among them, for the payment record query, the payment record management module can be used to execute it, and the payment record management module can be used to manage and record the payment information of the target user.

[0131] The payment-based data processing method provided by the present application, after generating the target payment list based on the target payment information, the method further includes: storing the target payment list in the blockchain; after executing the payment operation, the method further includes: determining the payment status of the target project and using a preset smart contract to update the payment status in the target payment list in the blockchain. Since the blockchain is tamper-proof and secure, storing the target payment list in the blockchain can ensure the security and integrity of the payment information, and when determining the payment status of the target project, the payment status in the target payment list in the blockchain is automatically updated using a preset smart contract, so that each payment can be traced, which is convenient for viewing or auditing, and increases the credibility of the payment system.

[0132] As an optional implementation manner, based on the above embodiment, after determining the payment status of the target project, the method further includes:

[0133] If it is determined that the payment status of the target project is successful, a preset smart contract is used to send multiple candidate payment notification methods to the client device;

[0134] Receiving a preset payment notification method triggered by a client device through a target user;

[0135] The payment result of the target item is sent to the client device according to the preset payment notification method.

[0136] Optionally, the candidate payment notification method may be a notification method such as text message, phone call, email, etc., which is not limited in this embodiment.

[0137] Among them, the payment result is the actual payment result of the target project.

[0138] Specifically, in this embodiment, when the server device determines that the payment status of the target project is a successful payment, a preset smart contract is used to send multiple candidate payment notification methods to the client device. The target user can select any one or more notification methods from the multiple candidate payment notification methods as the preset payment notification method. After the target user selects, the client device sends the preset payment notification method triggered by the target user to the server device, and the server device sends the payment result of the target project to the client device according to the preset payment notification method.

[0139] Among them, for sending payment notification to the target user according to the preset payment notification method, a payment notification module can be used to execute it, and the payment notification module can be used to send the payment notification to the target user.

[0140] Among them, when the target user does not trigger the preset payment notification method for the first time, the server device will retain the preset payment notification method triggered by the target user last time when sending the candidate payment notification method. The target user can directly confirm the preset payment notification method triggered last time, or change the preset payment notification method.

[0141] Among them, the server-side device will obtain the payment result of the target item within the preset time. If the successful payment result of the target item is not received within the preset time, the target user will be refunded and a payment result of failed payment will be generated, which will be sent to the client device of the target user in accordance with the preset payment notification method. Therefore, it can avoid the user not receiving the payment notification for a long time and resulting in poor user experience, thereby improving the user experience.

[0142] The preset time may be 30 minutes or other time, which is not limited in this embodiment.

[0143] The payment-based data processing method provided by the present application, after determining the payment status of the target project, the method further includes: if it is determined that the payment status of the target project is a successful payment, a preset smart contract is used to send multiple candidate payment notification methods to the client device; receiving the preset payment notification method triggered by the client device through the target user; and sending the payment result of the target project to the client device according to the preset payment notification method. Since the preset smart contract is used to send multiple candidate payment notification methods to the client device after the payment is successful, the target user can independently select the payment notification method, thereby improving the user experience.

[0144] Figure 3 A flowchart of a payment-based data processing method provided in another embodiment of the present application is shown in FIG. Figure 3 As shown, the execution subject of this embodiment is a data processing system based on payment. The system includes: a server device and a client device. The data processing method provided in this embodiment includes the following steps:

[0145] S301, the client device sends a payment request for a target item triggered by a target user through a payment management interface of the target item to the server device.

[0146] S302, the server device obtains the payment record of the target item of the target user according to the target user information included in the target item payment request.

[0147] S303: If the target user has a payment record for the target item, the server device obtains the most recent payment record for the target item from the blockchain, and sends the preset payment information in the most recent payment record to the client device.

[0148] Among them, the client device receives the preset payment information in the most recent payment record and displays it on the payment management page of the target project.

[0149] S304, the server device receives the initial payment information of the target item sent by the client device.

[0150] Among them, if the target user has a payment record for the target project, the initial payment information is determined based on the preset payment information; if the target user does not have a payment record for the target project, the initial payment information is entered by the user in the payment management interface.

[0151] S305, the client device sends a payment request for the target item to the server device.

[0152] S306, in response to receiving the payment request for the target item sent by the client device, obtaining the target payment information and generating a target payment list based on the target payment information, and storing the target payment list in the blockchain. S307, the server device matches the initial payment information read from the blockchain with the target payment information to obtain a matching result.

[0153] S308, if the server device determines that the matching result is a successful match, the payment operation is executed. S309, the server device determines the payment status of the target item and uses a preset smart contract to update the payment status in the target payment list in the blockchain.

[0154] S310, if the server device determines that the payment status of the target project is successful, it uses a preset smart contract to send multiple candidate payment notification methods to the client device.

[0155] S311, the client device sends a preset payment notification method triggered by the target user to the server device.

[0156] S312, the server device sends the payment result of the target item to the client device according to the preset payment notification method.

[0157] Figure 4 A schematic diagram of a payment-based data processing device according to an embodiment of the present application is shown in FIG. Figure 4 As shown, the payment-based data processing device provided in this embodiment is located in an electronic device, and the payment-based data processing device 40 provided in this embodiment includes: a receiving module 41, an acquisition module 42, a verification module 43, a storage module 44, a matching module 45, and an execution module 46.

[0158] Among them, the receiving module 41 is used to receive the target project payment request sent by the client device; the acquisition module 42 is used to obtain the initial payment information of the target project; the verification module 43 is used to verify the initial payment information using a preset smart contract; the storage module 44 is used to store the verified initial payment information in the blockchain; the acquisition module 42 is also used to respond to the receipt of the target project payment request, obtain the target payment information and generate a target payment list based on the target payment information; the matching module 45 is used to match the initial payment information read from the blockchain with the target payment information to obtain a matching result; the execution module 46 is used to execute the payment operation if it is determined that the matching result is a successful match.

[0159] Optionally, the target project payment request includes target user information.

[0160] Accordingly, when acquiring the initial payment information of the target project, the acquisition module 42 is specifically used to: determine whether the target user has a payment record for the target project based on the target user information; if so, obtain the most recent payment record of the target project from the blockchain, send the preset payment information in the most recent payment record to the client device for display on the payment management interface, and receive the initial payment information of the target project sent by the client device, where the initial payment information is determined based on the preset payment information; if not, receive the initial payment information of the target project sent by the client device, where the initial payment information is input by the user on the payment management interface.

[0161] Optionally, when the verification module 43 uses a preset smart contract to verify the initial payment information, it is specifically used to: use the verification rules in the preset smart contract to verify the initial payment information; if it is determined that the initial payment information meets the verification rules, then the verification result is determined to be passed; if it is determined that the initial payment information does not meet the verification rules, then the verification result is determined to be failed.

[0162] Optionally, the verification rules of the preset smart contract include format verification rules and amount verification rules.

[0163] Accordingly, when the verification module 43 uses the verification rules in the preset smart contract to verify the initial payment information, it is specifically used to: use the format verification rules to verify the format of each payment information in the initial payment information; use the amount verification rules to verify the payment amount in the initial payment information.

[0164] Optionally, when matching the initial payment information read from the blockchain with the target payment information to obtain a matching result, the matching module 45 is specifically used to: perform a corresponding match between the initial payment information read from the blockchain and the target payment information to determine whether the initial payment information read from the blockchain and the corresponding payment information in the target payment information are completely consistent; in response to the corresponding payment information being completely consistent, determine that the matching result is a successful match; in response to the corresponding payment information being not completely consistent, determine that the matching result is a failed match.

[0165] Optionally, the payment-based data processing device provided in this embodiment further includes: a determination module and an update module.

[0166] The storage module 44 is further used to: after generating a target payment list based on the target payment information, store the target payment list in the blockchain. The determination module is used to determine the payment status of the target item after executing the payment operation. The update module is used to update the payment status in the target payment list in the blockchain using a preset smart contract.

[0167] Optionally, the payment-based data processing device provided in this embodiment further includes: a sending module.

[0168] Accordingly, the sending module is used to determine the payment status of the target project. If the payment status of the target project is determined to be successful, a preset smart contract is used to send multiple candidate payment notification methods to the client device. The receiving module 41 is used to receive the preset payment notification method triggered by the client device through the target user. The sending module is used to send the payment result of the target project to the client device according to the preset payment notification method.

[0169] The payment-based data processing device provided in the embodiment of the present application can be used to execute the technical solution of the payment-based data processing method in the above-mentioned embodiment. Its implementation principle and technical effect are similar and will not be repeated here.

[0170] It should be noted that it should be understood that the division of the various modules of the above device is only a division of logical functions. In actual implementation, they can be fully or partially integrated into one physical entity, or physically separated. Moreover, these modules can be all implemented in the form of software calling through processing elements; they can also be all implemented in the form of hardware; some modules can also be implemented in the form of software calling through processing elements, and some modules can be implemented in the form of hardware.

[0171] Figure 5 This is a schematic diagram of the structure of an electronic device provided by an embodiment of the present application. Figure 5 As shown, the electronic device 50 may include: a processor 51 and a memory 52.

[0172] The memory 52 stores computer-executable instructions; the processor 51 executes the computer-executable instructions stored in the memory 52 to implement the payment-based data processing method provided by any of the above embodiments. The relevant descriptions can be understood by referring to the relevant descriptions and effects corresponding to the steps in the accompanying drawings, and no further details are given here.

[0173] The processor 51 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 gate or transistor logic devices, discrete hardware components.

[0174] The memory 52 is connected to the processor 51 via a system bus and completes communication between them. The memory 52 is used to store computer program instructions.

[0175] 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 ease of representation, only one thick line is used in the figure, but it does not mean that there is only one bus or one type of bus. The transceiver is used to realize the communication between the database access device and other computers (such as clients, read-write libraries, and read-only libraries). The memory may include random access memory (RAM) and may also include non-volatile memory.

[0176] The electronic device provided in the embodiment of the present application may be the terminal device of the above embodiment.

[0177] An embodiment of the present application also provides a chip for running instructions, which is used to execute the technical solution of the data processing method based on payment in the above embodiment.

[0178] An embodiment of the present application also provides a computer-readable storage medium, in which computer instructions are stored. When the computer instructions are executed on a computer, the computer executes the technical solution of the data processing method based on payment in the above embodiment.

[0179] An embodiment of the present application also provides a computer program product, which includes a computer program stored in a computer-readable storage medium. At least one processor can read the computer program from the computer-readable storage medium. When at least one processor executes the computer program, it can implement the technical solution of the data processing method based on payment in the above embodiment.

[0180] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic, for example, the division of modules is only a logical function division, and there may be other division methods in actual implementation, such as multiple modules can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or modules, which can be electrical, mechanical or other forms.

[0181] The modules described as separate components may or may not be physically separated, and the components shown as modules may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the modules may be selected according to actual needs to implement the solution of this embodiment.

[0182] In addition, each functional module in each embodiment of the present application can be integrated into one processing unit, or each module can exist physically separately, or two or more modules can be integrated into one unit. The above-mentioned module-composed unit can be implemented in the form of hardware or in the form of hardware plus software functional units.

[0183] The above-mentioned integrated module implemented in the form of a software function module can be stored in a computer-readable storage medium. The above-mentioned software function module is stored in a storage medium, including a number of instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor to perform some steps of the methods of various embodiments of the present application.

[0184] In the above embodiments, it should be understood that the processor can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), etc. A general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in the invention can be directly implemented as a hardware processor, or can be implemented by a combination of hardware and software modules in the processor.

[0185] The memory may include a high-speed memory (Random Access Memory, RAM), and may also include a non-volatile memory (NVM), such as at least one disk storage.

[0186] The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, the bus in the drawings of this application is not limited to only one bus or one type of bus.

[0187] The above-mentioned readable storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk. The readable storage medium can be any available medium that can be accessed by a general or special-purpose computer.

[0188] An exemplary readable storage medium is coupled to a processor so that the processor can read information from the readable storage medium and write information to the readable storage medium. Of course, the readable storage medium can also be a component of the processor. The processor and the readable storage medium can be located in an application specific integrated circuit (Application Specific Integrated Circuits, referred to as: ASIC). Of course, the processor and the readable storage medium can also exist in the device as discrete components.

[0189] The division of units is only a logical function division, and there may be other divisions in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interface, device or unit, which can be electrical, mechanical or other forms.

[0190] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0191] In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0192] If the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium, including several instructions for a computer device (which can be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods of each embodiment of the present invention. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk, etc. Various media that can store program codes.

[0193] Those skilled in the art can understand that all or part of the steps of implementing the above-mentioned method embodiments can be completed by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, the steps of the above-mentioned method embodiments are executed; and the aforementioned storage medium includes: ROM, RAM, disk or optical disk and other media that can store program codes.

[0194] Finally, it should be noted that those skilled in the art will readily conceive of other embodiments of the present invention after considering the specification and practicing the invention disclosed herein. The present invention is intended to cover any variations, uses or adaptations of the present invention, which follow the general principles of the present invention and include common knowledge or customary technical means in the art not disclosed by the present invention, are not limited to the precise structure described above and shown in the drawings, and may be modified and changed in various ways without departing from the scope thereof. The scope of the present invention is limited only by the appended claims.

Claims

1. A payment-based data processing method, characterized in that: include: Receive a payment request for a target item sent by a client device, and obtain initial payment information for the target item; The target item payment request is triggered by the target user through the payment management interface of the client device; The initial payment information is verified using a preset smart contract, and the verified initial payment information is stored in the blockchain; In response to receiving the payment request for the target item, obtaining target payment information and generating a target payment list based on the target payment information, wherein the target payment information is payment information for payment determined when the payment request for the target item is received; Matching the initial payment information read from the blockchain with the target payment information to obtain a matching result; If the matching result is determined to be successful, the payment operation is performed.

2. The method according to claim 1, characterized in that The target item payment request includes target user information; The obtaining of the initial payment information of the target project includes: Determining whether the target user has a payment record for the target item based on the target user information; If it exists, obtaining the most recent payment record of the target project from the blockchain, sending the preset payment information in the most recent payment record to the client device for display on the payment management interface, and receiving the initial payment information of the target project sent by the client device, where the initial payment information is determined based on the preset payment information; If not, initial payment information of the target item sent by the client device is received, where the initial payment information is input by the user in the payment management interface.

3. The method according to claim 1, characterized in that The verification of the initial payment information by using a preset smart contract includes: Verifying the initial payment information using the verification rules in the preset smart contract; If it is determined that the initial payment information satisfies the verification rule, then the verification result is determined to be passed; If it is determined that the initial payment information does not satisfy the verification rule, the verification result is determined to be failed.

4. The method according to claim 3, characterized in that The verification rules of the preset smart contract include format verification rules and amount verification rules; The verifying the initial payment information by using the verification rules in the preset smart contract includes: Using the format verification rules to verify the format of each payment information in the initial payment information; The payment amount in the initial payment information is verified using the amount verification rule.

5. The method according to claim 1, characterized in that The initial payment information read from the blockchain is matched with the target payment information to obtain a matching result, including: Matching the initial payment information read from the blockchain with the target payment information to determine whether the initial payment information read from the blockchain is completely consistent with the corresponding payment information in the target payment information; In response to the corresponding payment information being completely consistent, determining that the matching result is a successful match; In response to the corresponding payment information being not completely consistent, it is determined that the matching result is a matching failure.

6. The method according to claim 1, characterized in that After generating the target payment list based on the target payment information, the method further includes: Storing the target payment list in the blockchain; After the payment operation is performed, the method further includes: Determine the payment status of the target project and use the preset smart contract to update the payment status in the target payment list in the blockchain.

7. The method according to claim 6, characterized in that After determining the payment status of the target project, the method further includes: If it is determined that the payment status of the target item is successfully paid, a preset smart contract is used to send multiple candidate payment notification methods to the client device; Receiving a preset payment notification method triggered by a client device through a target user; The payment result of the target item is sent to the client device according to the preset payment notification method.

8. A payment-based data processing device, characterized in that: include: A receiving module, used for receiving a payment request for a target item sent by a client device; An acquisition module is used to obtain the initial payment information of the target project; A verification module, used to verify the initial payment information using a preset smart contract; A storage module, used to store the verified initial payment information in the blockchain; The acquisition module is further used to, in response to receiving the payment request for the target item, acquire the target payment information and generate a target payment list based on the target payment information; A matching module, used to match the initial payment information read from the blockchain with the target payment information to obtain a matching result; The execution module is used to execute the payment operation if the matching result is determined to be a successful match.

9. An electronic device, characterized in that: include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory to implement the method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions, which are used to implement the method according to any one of claims 1 to 7 when executed by a processor.

11. A computer program product, characterized in that The invention comprises a computer program, which implements the method according to any one of claims 1 to 7 when being executed by a processor.

Images