A Zero-Trust Digital RMB Payment System and Security Protection Method

Abstract

This invention provides a zero-trust digital RMB payment system and security protection method, including a payment APP, a zero-trust payment gateway, a mobile payment server, a zero-trust policy management system, and a risk information system. It identifies the terminal, person, account, and payment platform in mobile payment, and performs continuous and reliable verification of the identity in mobile payment. At the same time, it assumes that identity authentication credentials and payment messages are not trusted by default, and performs continuous and reliable verification on all of them. Even if the identity is completely forged, the content is controllable, and every link of the payment is trustworthy.

Description

Technical Field

[0001] This invention belongs to the field of computer technology, specifically relating to a zero-trust digital RMB payment system and security protection method. Background Technology

[0002] With the development of the digital yuan, mobile payment and mobile transfer have become relatively normal financial activities in people's daily lives. Currently, mobile payment transfer functions typically require users to log in with their account password, enter the target account, and then undergo strong authentication via facial or fingerprint recognition. Once the strong authentication is successful, the transfer is considered complete.

[0003] Current mobile transfers rely on user authentication, but several risks remain: account passwords can be compromised, allowing attackers to impersonate users; fingerprint and facial recognition information can be maliciously stolen, leading to unauthorized transfers and financial losses; mobile payments are also vulnerable to man-in-the-middle attacks, where payment details can be altered, resulting in losses for legitimate users; and legitimate users can be tricked into transferring money to fraudulent accounts. Therefore, improving mobile payment security has been a key research area for security companies and cybersecurity experts. Summary of the Invention

[0004] Based on the aforementioned technological status, the purpose of this invention is to provide a zero-trust digital RMB payment system and security protection method, which identifies the terminal, person, account, and payment platform in mobile payment, performs continuous and reliable verification of the identity in mobile payment, and at the same time, assumes that the identity authentication certificate and payment message are not trusted by default, and performs continuous and reliable verification of all of them, so that even if the identity is completely forged, the content is controllable, and every link of the payment is trustworthy.

[0005] The technical solution adopted in this invention is as follows: a mobile payment system based on zero-trust digital RMB, including a payment APP, a zero-trust payment gateway, a mobile payment server, a zero-trust policy management system, and a risk information system;

[0006] The payment app allows users to register their terminals, supports authentication of user accounts and terminals, obtains user identification information and trusted tags, enables users to actually perform mobile payments and mobile transfers, and sends trusted verification messages to the zero-trust payment gateway.

[0007] The zero-trust payment gateway is used to verify messages. After receiving a message, it extracts the user identification information, obtains the user's trusted label from the zero-trust policy management system based on the user identification information, uses the trusted label to perform trusted verification on the message, and denoises and restores the message.

[0008] The mobile payment server provides users with mobile payment and mobile transfer capabilities;

[0009] The zero-trust policy management system is responsible for the management of terminals and user accounts. After authenticating and binding the terminals and user accounts, it generates user identification information and trusted tags for users with legitimate binding relationships, and is responsible for sending the trusted tags to the payment APP and the zero-trust payment gateway.

[0010] The risk information system is used to assess the risk of the target account to which funds are being transferred, and sends the risk assessment information to the payment app through the zero-trust strategy management system.

[0011] The zero-trust policy management system performs risk monitoring and assessment based on changes in user information. If a risk is detected, enhanced identity verification is triggered. The changes in information include changes in the user's IP address and changes in the user's geographical location.

[0012] The trusted verification messages supported by the payment app include user identity authentication messages and payment messages. Both the authentication message and the payment message include the following verification steps:

[0013] S1. The payment APP generates the original message pakData, then calculates the hash value of the original message pakData and appends it to the original message pakData;

[0014] S2. Use the trusted label as noiseData, add noiseData to the original message to obtain the intermediate message SecpakData, and the intermediate message SecpakData = pakData XOR noiseData;

[0015] S3. Recalculate the hash value and place it after the intermediate message to obtain the message to be sent. The message content of the message to be sent is SecpakData.

[0016] S4. Add user identification information to the message information of the message to be sent, and then send it to the zero trust payment gateway. The zero trust payment gateway extracts the user identification information and obtains the corresponding noise data based on the user identification information.

[0017] S5. Perform message verification:

[0018] S5.1 Verify the correctness of the hash value of the message content SecpakData. If it is correct, continue the verification.

[0019] S5.2, Obtain the original message pakData = SecpakData XOR noiseData;

[0020] S5.3 Verify the correctness of the hash value of the original message pakData. If it is correct, it is a trustworthy message.

[0021] Furthermore, this invention also claims protection for a zero-trust digital RMB payment security protection method, which uses the aforementioned zero-trust digital RMB mobile payment system, and the method is as follows:

[0022] Users register user accounts and terminals, and bind user accounts and terminals through authentication to generate trusted tags and user identification information, and send trusted tags and user identification information to the payment APP and zero-trust payment gateway;

[0023] When a user makes a mobile transfer, the user sends an authentication message to the Zero Trust Payment Gateway through the payment app. The authentication message carries the user's identification information and adds a "trusted label" as noise to the content of the authentication message. After receiving the message, the Zero Trust Payment Gateway extracts the user's identification information from the message and extracts the trusted label based on the user's identification information. Then it verifies the message and allows it to proceed after the verification is successful.

[0024] After a user enters the account to be paid through the payment app, the Zero Trust Strategy Management System obtains the risk information of the account through the risk information system. If a risk is confirmed, the user is notified and the user stops the transfer.

[0025] The zero-trust policy management system monitors and assesses risks based on changes in user information. If a risk is detected, enhanced identity verification is triggered. If the enhanced identity verification fails, it is considered an illegal binding relationship, and the transfer is stopped.

[0026] In the above method, users register an account through mobile banking or offline, and at the same time register a mobile terminal (register a payment APP account). After logging into the terminal, users first perform terminal authentication, and then perform basic authentication of the user account. After successful authentication, the binding relationship between the user account and the terminal is confirmed, that is, the terminal and the user are bound together.

[0027] To achieve the above objectives, the present invention also proposes a zero-trust digital RMB payment security protection device, characterized in that it includes:

[0028] At least one processor;

[0029] At least one memory for storing at least one program;

[0030] When the at least one program is executed by at least one processor, the at least one processor implements the zero-trust digital RMB payment security protection method as described above.

[0031] To achieve the above objectives, the present invention also proposes a computer storage medium storing a processor-executable program, characterized in that the processor-executable program, when executed by the processor, implements the zero-trust digital RMB payment security protection method described above.

[0032] By adopting the technical solution provided by this invention, the following technical advantages can be achieved:

[0033] (1) Based on the zero-trust concept, the user account and terminal are bound together, which solves the problem that the account and password can be stolen and then the user can log in illegally.

[0034] (2) Based on the zero-trust concept, it realizes trusted verification of strong authentication biometric authentication such as face and fingerprint, and prevents malicious attackers from illegally stealing fingerprint and face information for illegal payment and transfer.

[0035] (3) Based on the zero-trust concept, the payment message is trusted and authenticated to prevent illegal transfers after the payment message is attacked by a man in the middle. Attached Figure Description

[0036] Figure 1 This invention relates to a zero-trust digital RMB mobile payment framework structure;

[0037] Figure 2 This is a flowchart of the message verification process in the technical solution of this invention. Detailed Implementation

[0038] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0039] It should be noted that although functional modules are divided in the system diagram and the logical order is shown in the flowchart, in some cases, the steps shown or described may be performed in a different order than the module division in the system or the order in the flowchart. The terms "first," "second," etc., in the specification, claims, and the aforementioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence.

[0040] In the following description, the use of suffixes such as "module," "part," or "unit" to denote elements is solely for the purpose of illustrative purposes and has no inherent meaning. Therefore, "module," "part," or "unit" may be used interchangeably.

[0041] like Figure 1The diagram shows the framework structure of the zero-trust digital RMB mobile payment system of the present invention. The zero-trust digital RMB mobile payment system includes a payment APP, a zero-trust payment gateway, a mobile payment server, a zero-trust policy management system, and a risk information system.

[0042] The payment app is a user payment app issued by a bank. The payment app supports terminal and user authentication (obtaining user identification information and trusted tags), mobile payment and mobile transfer, and supports strong authentication and trusted verification of the target account.

[0043] The zero-trust payment gateway receives trusted user identification information and trusted tags. After receiving a payment message, it extracts the user identification information, uses the trusted tags to verify the trustworthiness of the payment message, and restores the payment message (removing noise).

[0044] The mobile payment server is responsible for providing users with mobile payment and mobile transfer capabilities;

[0045] The zero-trust policy management system is mainly used for policy management of zero-trust trusted payments. It is responsible for terminal and mobile payment account management, including: binding terminals and accounts; authenticating terminals and accounts and generating user identification information for legitimate users; risk monitoring and assessment of users (e.g., assessment based on changes in user IP address and user geographical location); generating trusted tags for legitimate users and distributing trusted tags to payment apps and zero-trust payment gateways; and trusted verification of transfer target accounts.

[0046] The aforementioned risk information system is an account risk assessment system. This system assesses the risk of the target account for the transfer and determines whether it is a fraudulent account. Specifically, it relies on the anti-fraud platform of the public security organs or the financial transaction platform to list accounts involved in fraud cases reported from the public as risk lists, and to list accounts that receive funds more than a certain frequency as risk warning accounts, thereby combining network financial security protection with social financial security protection.

[0047] Based on the zero-trust policy management system of the aforementioned mobile payment system, users register an account through mobile banking or offline, and at the same time register a mobile terminal (register a payment APP account). The user terminal and the user are bound together. During authentication, the user logs in to the mobile terminal, first performs terminal authentication, and then performs basic user authentication (password authentication). After successful authentication, the binding relationship between the user and the terminal is confirmed, a trusted label and user identification information are generated, and the trusted label and user identification information are sent to the payment APP and the zero-trust payment gateway.

[0048] The payment app performs subsequent authentication on users, such as "face" and "fingerprint" authentication. The authentication message carries user identification information and adds a "trusted label" as noise to the content of the authentication message to prevent malicious forgery. In the subsequent "face" and "fingerprint" authentication, noise extraction and recognition are performed first. If it is legitimate, deep authentication is then carried out. Specifically, after the zero-trust payment gateway receives the message, it extracts the user identification information from the message and extracts the trusted label based on the user identification information. Then, it verifies the message. If the verification is successful, it can be allowed to proceed.

[0049] Through the payment app, the user's payment account is disclosed to the Zero Trust Strategy Management System. The Zero Trust Strategy Management System obtains risk information about the account being paid through its risk information system. If a risk is confirmed, the user is notified and the transfer is stopped. Simultaneously, the Zero Trust Strategy Management System monitors and assesses the user's behavior for risk, such as continuous risk monitoring based on location, time, and IP address. If a risk is detected, enhanced identity verification is implemented, such as face-to-face video authentication.

[0050] The aforementioned message verification includes trusted verification of both authentication messages and payment messages, and the processes for both are as follows:

[0051] The payment app generates the original message pakData, calculates its hash value, and appends it to the original message pakData. The trusted tag is used as noiseData, which is then added to the original message to obtain the intermediate message SecpakData. The intermediate message SecpakData is calculated as pakData XORed with noiseData. The hash value is then recalculated and appended to the intermediate message to obtain the message to be sent. The content of the message to be sent is SecpakData. User identification information is added to the message information and then the message is sent; the message arrives at the zero-trust payment gateway, the zero-trust payment gateway extracts the user identification information, obtains the corresponding noiseData based on the user identification information, and then performs message verification; the message verification process includes: (1) verifying the correctness of the hash value of the message content SecpakData, and if it is correct, continue to verify; (2) obtaining the original message pakData = SecpakData XOR noiseData; (3) verifying the correctness of the hash value of the original message pakData, and if it is correct, it is a trusted message.

[0052] In the aforementioned terminal authentication, users can only successfully authenticate using a registered terminal; otherwise, the zero-trust policy management system will determine that the user and terminal binding relationship is illegal and prevent further operation.

[0053] The zero-trust digital RMB mobile payment system and the digital RMB payment security protection method based on the present invention can prevent the leakage of user accounts, passwords, fingerprints, and facial information, which could lead to unauthorized users impersonating users to log in and transfer funds. By verifying payment messages with credibility, it can avoid property losses caused by man-in-the-middle attacks. Furthermore, by conducting risk assessments on the target account of the transfer through a risk information system, it can reduce the risk of transferring funds to fraudulent accounts.

[0054] As can be seen from the specific embodiments of this application and the content of the given examples, the method of this application can be stored or loaded onto a computer or other programmable data processing device by computer program instructions, that is, these computer programs can be specified on a computer or other programmable data processing device to generate a machine, the machine being able to execute instructions to implement the functions specified in one or more processes of the flowchart.

[0055] The method of this application can be stored or loaded into a computer or other programmable data processing device by computer program instructions, causing the computer or other programmable data processing device to execute a series of operational steps by reading the instructions to produce a computer-implemented process, thereby executing in the computer or other programmable data processing device the steps provided by the instructions for implementing the functions specified in one or more processes of the flowchart.

[0056] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present invention are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state disk (SSD)).

Claims

1. A mobile payment system based on zero-trust digital RMB, comprising a payment APP, a zero-trust payment gateway, a mobile payment server, a zero-trust policy management system, and a risk information system; The payment app allows users to register their terminals, supports authentication of user accounts and terminals, obtains user identification information and trusted tags, enables users to actually perform mobile payments and mobile transfers, and sends trusted verification messages to the zero-trust payment gateway. The zero-trust payment gateway is used to verify messages. After receiving a message, it extracts the user identification information, obtains the user's trusted label from the zero-trust policy management system based on the user identification information, uses the trusted label to perform trusted verification on the message, and denoises and restores the message. The mobile payment server provides users with mobile payment and mobile transfer capabilities; The zero-trust policy management system is responsible for the management of terminals and user accounts. After authenticating and binding the terminals and user accounts, it generates user identification information and trusted tags for users with legitimate binding relationships, and is responsible for sending the trusted tags to the payment APP and the zero-trust payment gateway. The risk information system is used to assess the risk of the target account to which funds are being transferred, and sends the risk assessment information to the payment APP through the zero-trust strategy management system. Both authentication and payment messages include the following verification steps: S1. The payment APP generates the original message pakData, then calculates the hash value of the original message pakData and appends it to the original message pakData; S2. Use the trusted label as noiseData, add noiseData to the original message to obtain the intermediate message SecpakData, and the intermediate message SecpakData = pakData XOR noiseData; S3. Recalculate the hash value and place it after the intermediate message to obtain the message to be sent. The message content of the message to be sent is SecpakData. S4. Add user identification information to the message information of the message to be sent, and then send it to the zero trust payment gateway. The zero trust payment gateway extracts the user identification information and obtains the corresponding noise data based on the user identification information. S5. Perform message verification: S5.1 Verify the correctness of the hash value of the message content SecpakData. If it is correct, continue the verification. S5.2, Obtain the original message pakData = SecpakData XOR noiseData; S5.3 Verify the correctness of the hash value of the original message pakData. If it is correct, it is a trustworthy message.

2. The zero-trust digital RMB mobile payment system according to claim 1, further characterized in that, The zero-trust policy management system performs risk monitoring and assessment based on changes in user information. If a risk is detected, enhanced identity verification is triggered. The changes in information include changes in the user's IP address and changes in the user's geographical location.

3. The zero-trust digital RMB mobile payment system according to claim 1, further characterized in that, The trusted verification messages supported by the payment app include user identity authentication messages and payment messages.

4. A method for security protection of zero-trust digital RMB payments, which uses the zero-trust digital RMB mobile payment system as described in any one of claims 1-3, wherein the method is as follows: Users register user accounts and terminals, and bind user accounts and terminals through authentication to generate trusted tags and user identification information, and send trusted tags and user identification information to the payment APP and zero-trust payment gateway; When a user makes a mobile transfer, the user sends an authentication message to the Zero Trust Payment Gateway through the payment app. The authentication message carries the user's identification information and adds a "trusted label" as noise to the content of the authentication message. After receiving the message, the Zero Trust Payment Gateway extracts the user's identification information from the message and extracts the trusted label based on the user's identification information. Then it verifies the message and allows it to proceed after the verification is successful. After a user enters the account to be paid through the payment app, the Zero Trust Strategy Management System obtains the risk information of the account through the risk information system. If a risk is confirmed, the user is notified and the user stops the transfer. The zero-trust policy management system monitors and assesses risks based on changes in user information. If a risk is detected, enhanced identity verification is triggered. If the enhanced identity verification fails, it is considered an illegal binding relationship, and the transfer is stopped.

5. The method according to claim 4, characterized in that, After logging into the terminal, users first undergo terminal authentication, followed by basic authentication of their user accounts. Once authentication is successful, the binding relationship between the user account and the terminal is confirmed.

6. A security protection device for zero-trust digital RMB payments, characterized in that, include: At least one processor; At least one memory for storing at least one program; When the at least one program is executed by at least one processor, the at least one processor implements the zero-trust digital RMB payment security protection method as described in claim 4 or 5.

7. A computer storage medium storing a processor-executable program, characterized in that, When executed by the processor, the program executable by the processor implements the zero-trust digital RMB payment security protection method as described in claim 4 or 5.

Images