A secure payment protection method and system based on multi-source information fusion

Abstract

The present invention relates to the field of payment security, and discloses a secure payment protection method and system based on multi-source information fusion, which matches payment keywords input by a user during payment with payment security-related information in a database, determines whether to continue the payment process, detects the security of a payment device through a device security score, determines whether to continue the payment process, detects the security of a user's payment account through an account security value, determines whether to continue the payment process, detects whether a user's payment identity has a security risk through an identity security risk value, determines whether to continue the payment process, determines whether the payment time exceeds a time limit, determines whether to continue the payment process, and then detects whether the environment of the entire payment process is safe, and issues warning information, which helps to timely discover and eliminate potential security risks, more comprehensively identify security risks that may exist in the payment process, and improve risk defense capabilities.

Description

Technical Field

[0001] The present invention relates to the field of payment security technology, and more specifically to a secure payment protection method and system based on multi-source information fusion. Background Art

[0002] With the rapid development of Internet technology, payment methods are becoming increasingly diversified, including online payment, mobile payment, QR code payment and NFC payment. The complexity of the payment environment has increased the risk points in the payment process, such as the security of payment channels, the authenticity of transaction data and the verification of user identity, which need to be effectively guaranteed. During the payment process, a large amount of multi-source information will be generated, including transaction data, user behavior logs, security databases and user feedback. Through multi-source information fusion technology, scattered payment information can be integrated to form a more comprehensive and accurate payment security method. However, the payment field faces a variety of security threats, such as cyber attacks, data leaks and fraudulent transactions. In order to effectively deal with these threats, the secure payment protection method of multi-source information fusion has emerged. By real-time monitoring of users' payment behaviors and transaction records, payment institutions can promptly detect abnormal transactions and potential risks, and take corresponding measures to prevent and deal with them;

[0003] However, the above process still has the following disadvantages:

[0004] First, the existing payment security protection methods mainly monitor and evaluate the security risks of users' payment behaviors and transaction records during the payment process, but lack the function of screening and matching users' payment keywords. It is unable to preliminarily rule out the problem that the keywords entered by users do not match the payment security information in the database and terminate the payment process, which may lead to transaction risks caused by incorrect or leaked payment information;

[0005] Second, the existing secure payment protection methods are unable to detect security risks in the payment process from multiple aspects. At the same time, the lack of detection of payment environment security in the entire payment process may lead to the inability to fully identify security risks in the payment process. Summary of the invention

[0006] In order to overcome the above-mentioned defects of the prior art, the present invention provides a secure payment protection method and system based on multi-source information fusion to solve the problems existing in the above-mentioned background technology.

[0007] The present invention provides the following technical solution: a secure payment protection method based on multi-source information fusion, comprising:

[0008] S1: extracting payment security related information from the data source, including user identity authentication information, transaction feature information, and risk indication information, and importing the extracted payment security related information into the database;

[0009] S2: Process the payment security related information imported into the database, classify and mark the payment security related information according to data type, and update the imported payment security related information in the database in real time;

[0010] S3: Match the payment keyword input by the user during payment with the payment security related information in the database to obtain the information matching degree, and determine whether the payment keyword input by the user matches the payment security related information in the database according to the information matching degree. If not, the payment procedure is terminated immediately. If matched, S4 is continued to be executed to detect the security of the payment device.

[0011] S4: used to calculate the device security score, and detect whether the payment device is safe through the device security score. If the payment device is detected to be unsafe, the payment procedure is terminated immediately. If the payment device is detected to be safe, S5 is continued to perform security detection of the user's payment account;

[0012] S5: used to analyze and calculate the account security value, and detect whether the user's payment account is safe through the account security value. If it is detected that the user's payment account is not safe, the payment program is immediately terminated. If it is detected that the user's payment account is safe, S6 is continued to be executed to detect the correctness of the user's payment identity;

[0013] S6: Detecting whether the user's payment identity has security risks by analyzing and calculating the identity security risk value. If it is detected that the user's payment identity is not secure, the payment procedure is terminated immediately. If it is detected that the user's payment identity is secure, continue to execute S7 to detect the payment time.

[0014] S7: Detecting whether the payment time exceeds the time limit. If it is detected that the payment time exceeds the time limit, the payment procedure is immediately terminated and the user is prompted to re-authenticate. If it is detected that the payment time does not exceed the payment time limit, S9 is continued to be executed to detect the security of the payment environment;

[0015] S8: By calculating the environmental risk coefficient, detect whether the environment of the entire payment process is safe. If it is detected that the environment of the entire payment process is unsafe, immediately interrupt the payment procedure and issue a prompt warning message.

[0016] Preferably, the S1 identifies data sources related to payment security, including transaction system databases, user behavior logs, and security databases;

[0017] By obtaining the transaction system database connection information, the database driver is used to automatically extract transaction feature information from the transaction system database, including transaction amount, transaction time, transaction location and transaction frequency;

[0018] Extract user authentication information, including username, password, phone number, and verification code, by reading user behavior logs using file I / O operations;

[0019] By obtaining the security database connection information, use the ORM tool to automatically extract risk indication information from the security database, including the number of failed logins, the number of abnormal account activities, and the number of security warnings.

[0020] Preferably, the process of S2 processing the payment security related information imported into the database includes: data cleaning, data conversion and data verification, and classifying the processed payment security related information in the database according to the payment security information data type, and then marking the classified payment security related information by using an automated tool, and storing the classified and marked payment security related information in a corresponding data table. At the same time, the payment security related information is regularly backed up and updated in the database according to the import time.

[0021] Preferably, S3 extracts payment keywords from user input, retrieves security information related to the keywords in the database, compares the keywords input by the user with the retrieved information, calculates the degree of information matching based on the comparison results, and calculates the degree of information matching through the cosine similarity formula. A represents the keyword vector input by the user, and B represents the payment security information vector in the database;

[0022] The information matching degree D is compared with the preset information matching threshold d. When the information matching degree D ≥ the preset information matching threshold d, it indicates that the keyword vector input by the user is similar to the payment security information vector in the database. It is determined that the keyword input by the user matches the payment security information in the database, and the security check of the payment device continues. When the information matching degree D < the preset information matching threshold d, it indicates that the keyword input by the user does not match the payment security information in the database. The payment keyword is determined to be invalid and the payment procedure is terminated.

[0023] Preferably, the device security score of S4 is obtained by automatically obtaining the actual scores s1, s2, s3, ..., s i ,…,s n The calculation formula is S represents the device security score, a i represents the weight of the i-th safety detection index, s i represents the actual score of the i-th safety detection indicator, with a value range of [0,1], and n represents the total number of safety detection indicators;

[0024] Compare the device security score S with the security score threshold x. When the device security score S < security score threshold x, the device is determined to be unsafe. When the device security score S ≥ security score threshold x, the device is determined to be safe and the security check of the user's payment account continues.

[0025] Preferably, S5 calculates the account security value Q=B-(I+P) by obtaining the account login behavior abnormality score I, the account password complexity score B and the payment behavior abnormality score P;

[0026] The account security value Q is compared with the account security threshold τ. When the account security value Q < the account security threshold τ, the account is determined to be unsafe and the payment procedure is terminated immediately. When the account security value Q ≥ the account security threshold τ, the account is determined to be safe and the payment identity detection is continued.

[0027] Preferably, S6 calculates the identity security risk value by monitoring the number of identity authentications R1, the number of identity authentication failures R2, and the number of password changes R3 within the time t. b1, b2 are weight coefficients;

[0028] The identity security risk value F is compared with the identity security risk threshold r. When the identity security risk value F>identity security risk threshold r, the user's payment identity is determined to be insecure and the payment procedure is terminated immediately. When the identity security risk value F≤identity security risk threshold r, the user's payment identity is determined to be secure and the payment time detection continues.

[0029] Preferably, the specific steps of S7 detecting the payment time are:

[0030] Step S711: Set a payment time limit. When the user starts the payment process, record the payment start time T start ;

[0031] Step S712: When the user performs a payment operation, the current time T is monitored in real time. current , and calculate the elapsed time T from the start of payment to the current time used =T current -T start ;

[0032] Step S713: Set the elapsed time T used The payment time T is set limit For comparison,

[0033] If T used ≤T limit , then continue to test the security of the payment environment;

[0034] If Tused >T limit , the payment process is terminated immediately, all unfinished data in the current payment process is cleared, and a prompt message is displayed to the user, informing him that the payment time has exceeded and that re-identification is required.

[0035] Preferably, the S8 calculates the environmental risk coefficient by monitoring the data changes of the entire payment process, and the specific calculation formula is: S represents the device security score, x represents the security score threshold, Q represents the account security value, q represents the account security threshold, F represents the identity security risk value, r represents the identity security risk threshold, T used Indicates the elapsed time from the start of payment to the current time, T limit Indicates the set payment limit time;

[0036] The calculated environmental risk coefficient Z is compared with the set environmental risk threshold κ; when the environmental risk coefficient Z ≤ the set environmental risk threshold κ, the payment environment is judged to be safe and the payment process is allowed to continue; when the environmental risk coefficient Z > the set environmental risk threshold κ, the payment procedure is immediately interrupted and a warning message is issued to the user payment interface for display.

[0037] To achieve the above object, the present invention provides the following technical solution: a secure payment protection system based on multi-source information fusion, implementing the above secure payment protection method based on multi-source information fusion, comprising:

[0038] Payment information collection module: extracts payment security related information from the data source, including user identity authentication information, transaction feature information, and risk indication information, and imports the extracted payment security related information into the database;

[0039] Payment information processing and classification module: performs data processing on the payment security related information imported into the database, classifies and marks the payment security related information by data type, and updates the imported payment security related information in the database in real time;

[0040] Payment information matching module: matches the payment keyword input by the user during payment with the payment security related information in the database to obtain the information matching degree, and determines whether the payment keyword input by the user matches the payment security related information in the database through the information matching degree. If not, the payment procedure is terminated immediately; if matched, the security of the payment device is continued to be tested;

[0041] Device security detection module: used to calculate the device security score and detect whether the payment device is safe through the device security score. If the payment device is detected to be unsafe, the payment procedure is terminated immediately. If the payment device is detected to be safe, the security detection of the user's payment account is continued;

[0042] Account security detection module: used to analyze and calculate the account security value, and detect whether the user's payment account is safe through the account security value. If it is detected that the user's payment account is not safe, the payment procedure is terminated immediately. If it is detected that the user's payment account is safe, the correct detection of the user's payment identity will continue;

[0043] Identity security risk detection module: detects whether the user's payment identity has security risks by analyzing and calculating the identity security risk value. If it is detected that the user's payment identity is not secure, the payment procedure is terminated immediately. If it is detected that the user's payment identity is secure, the payment time is continued to be detected.

[0044] Payment time detection module: detects whether the payment time exceeds the time limit. If it is detected that the payment time exceeds the time limit, the payment process is immediately terminated and the user is prompted to re-authenticate. If it is detected that the payment time does not exceed the payment time limit, the security of the payment environment is continuously tested;

[0045] Payment environment risk assessment module: By calculating the environmental risk coefficient, it detects whether the environment of the entire payment process is safe. If it is detected that the environment of the entire payment process is unsafe, the payment procedure will be immediately interrupted and a prompt warning message will be issued.

[0046] Technical effects and advantages of the present invention:

[0047] The present invention processes and classifies data by importing payment security related information extracted from a data source into a database, matches payment keywords input by a user during payment with payment security related information in the database, determines whether to continue the payment process, detects whether a payment device is safe by device security scoring, determines whether to continue the payment process, detects whether a user's payment account is safe by account security value, determines whether to continue the payment process, detects whether a user's payment identity has security risks by analyzing and calculating identity security risk values, determines whether to continue the payment process, detects whether a payment time exceeds a time limit, determines whether to continue the payment process, detects whether the environment of the entire payment process is safe by calculating an environmental risk coefficient, and immediately interrupts the payment procedure and issues a prompt warning message if the environment of the entire payment process is detected to be unsafe, and helps prevent malicious users from forging or tampering with payment information to conduct fraudulent transactions through preliminary screening and matching of user payment keywords, reduces transaction risks caused by incorrect or leaked payment information, detects security risks of the payment process and payment environment security by multiple aspects, helps to timely discover and eliminate potential security risks, more comprehensively identify security risks that may exist in the payment process, improves risk defense capabilities, and thus improves the security of the entire payment system. BRIEF DESCRIPTION OF THE DRAWINGS

[0048] Figure 1 The figure is a flow chart of the method steps of the present invention.

[0049] Figure 2 It is the overall structural block diagram of the present invention. DETAILED DESCRIPTION

[0050] The technical solution of the present invention will be clearly and completely described below in conjunction with the accompanying drawings in the present invention. In addition, the forms of the various structures recorded in the following embodiments are only examples. The present invention involves a secure payment protection method and system based on multi-source information fusion. It is not limited to the various structures recorded in the following embodiments. All other implementations obtained by ordinary technicians in this field without making creative work belong to the scope of protection of the present invention.

[0051] like Figure 1 This embodiment provides a secure payment protection method based on multi-source information fusion, including:

[0052] S1: Extract payment security related information from the data source, including user identity authentication information, transaction feature information, and risk indication information, and import the extracted payment security related information into the database.

[0053] In this embodiment, the S1 identifies the data source of information related to payment security, including a transaction system database, a user behavior log, and a security database;

[0054] By obtaining the transaction system database connection information, the database driver is used to automatically extract transaction feature information from the transaction system database, including transaction amount, transaction time, transaction location and transaction frequency;

[0055] Extract user authentication information, including username, password, phone number, and verification code, by reading user behavior logs using file I / O operations;

[0056] By obtaining the security database connection information, use the ORM tool to automatically extract risk indication information from the security database, including the number of failed logins, the number of abnormal account activities, and the number of security warnings.

[0057] S2: Process the payment security related information imported into the database, classify and mark the payment security related information by data type, and update the imported payment security related information in the database in real time.

[0058] In this embodiment, the process of S2 processing the payment security related information imported into the database includes: data cleaning, data conversion and data verification, and classifying the processed payment security related information in the database according to the payment security information data type, and then marking the classified payment security related information by using an automated tool, and storing the classified and marked payment security related information in the corresponding data table. At the same time, the payment security related information is regularly backed up and updated in the database according to the import time.

[0059] S3: Match the payment keyword entered by the user during payment with the payment security related information in the database to obtain the degree of information matching. Determine whether the payment keyword entered by the user matches the payment security related information already in the database through the degree of information matching. If not, terminate the payment procedure immediately. If matched, continue to execute S4 to check the security of the payment device.

[0060] In this embodiment, S3 extracts payment keywords from user input, retrieves security information related to the keywords in the database, compares the keywords input by the user with the retrieved information, calculates the degree of information matching based on the comparison results, and calculates the degree of information matching through the cosine similarity formula. A represents the keyword vector input by the user, and B represents the payment security information vector in the database;

[0061] The information matching degree D is compared with the preset information matching threshold d. When the information matching degree D ≥ the preset information matching threshold d, it indicates that the keyword vector input by the user is similar to the payment security information vector in the database. It is determined that the keyword input by the user matches the payment security information in the database, and the security check of the payment device continues. When the information matching degree D < the preset information matching threshold d, it indicates that the keyword input by the user does not match the payment security information in the database. The payment keyword is determined to be invalid and the payment procedure is terminated.

[0062] It should be specifically explained that the keywords input by the user are converted into vector A and the payment security information in the database is converted into vector B, where A·B represents the sum of the similarities between the keywords input by the user and the security information in the database in various dimensions, and ||A||×||B|| represents the calculation of the Euclidean norm of the keyword vector input by the user and the payment security information vector in the database.

[0063] S4: used to calculate the device security score, and detect whether the payment device is safe through the device security score. If the payment device is detected to be unsafe, the payment procedure is terminated immediately. If the payment device is detected to be safe, S5 is continued to be executed to check the security of the user's payment account.

[0064] In this embodiment, the device security score of S4 is obtained by automatically obtaining the actual scores s1, s2, s3, ..., s i ,…,s n The calculation formula is S represents the device security score, a i represents the weight of the i-th safety detection index, s i represents the actual score of the i-th safety detection indicator, with a value range of [0,1], and n represents the total number of safety detection indicators;

[0065] Compare the device security score S with the security score threshold x. When the device security score S < security score threshold x, the device is determined to be unsafe. When the device security score S ≥ security score threshold x, the device is determined to be safe and the security check of the user's payment account continues.

[0066] It should be specified that the actual scores of multiple security detection indicators of the payment device include the actual score of the device authentication status, the actual score of the device software update status, the actual score of the device security vulnerability,... and the actual score of the device's network connection security.

[0067] S5: used to analyze and calculate the account security value, and detect whether the user's payment account is safe through the account security value. If it is detected that the user's payment account is not safe, the payment procedure is terminated immediately. If it is detected that the user's payment account is safe, continue to execute S6 to detect the correctness of the user's payment identity.

[0068] In this embodiment, S5 calculates the account security value Q=B-(I+P) by obtaining the account login behavior abnormality score I, the account password complexity score B, and the payment behavior abnormality score P;

[0069] The account security value Q is compared with the account security threshold τ. When the account security value Q < the account security threshold τ, the account is determined to be unsafe and the payment procedure is terminated immediately. When the account security value Q ≥ the account security threshold τ, the account is determined to be safe and the payment identity detection is continued.

[0070] S6: Detect whether the user's payment identity has security risks by analyzing and calculating the identity security risk value. If it is detected that the user's payment identity is not secure, terminate the payment procedure immediately. If it is detected that the user's payment identity is secure, continue to execute S7 to detect the payment time.

[0071] In this embodiment, S6 calculates the identity security risk value by monitoring the number of identity authentication attempts R1, the number of identity authentication failures R2, and the number of password changes R3 within a time period t. b1, b2 are weight coefficients;

[0072] The identity security risk value F is compared with the identity security risk threshold r. When the identity security risk value F>identity security risk threshold r, the user's payment identity is determined to be insecure and the payment procedure is terminated immediately. When the identity security risk value F≤identity security risk threshold r, the user's payment identity is determined to be secure and the payment time detection continues.

[0073] S7: Detect whether the payment time exceeds the time limit. If it is detected that the payment time exceeds the time limit, terminate the payment program immediately and prompt the user to re-authenticate the user. If it is detected that the payment time does not exceed the payment time limit, continue to execute S9 to detect the security of the payment environment.

[0074] In this embodiment, the specific steps of S7 detecting the payment time are:

[0075] Step S711: Set a payment time limit. When the user starts the payment process, record the payment start time T start ;

[0076] Step S712: When the user performs a payment operation, the current time T is monitored in real time. current, and calculate the elapsed time T from the start of payment to the current time used =T current -T start ;

[0077] Step S713: Set the elapsed time T used The payment time T is set limit For comparison,

[0078] If T used ≤T limit , then continue to test the security of the payment environment;

[0079] If T used >T limit , the payment process is terminated immediately, all unfinished data in the current payment process is cleared, and a prompt message is displayed to the user, informing him that the payment time has exceeded and that re-identification is required.

[0080] S8: By calculating the environmental risk coefficient, detect whether the environment of the entire payment process is safe. If it is detected that the environment of the entire payment process is unsafe, immediately interrupt the payment procedure and issue a prompt warning message.

[0081] In this embodiment, S8 calculates the environmental risk coefficient by monitoring the data changes of the entire payment process. The specific calculation formula is: S represents the device security score, x represents the security score threshold, Q represents the account security value, q represents the account security threshold, F represents the identity security risk value, r represents the identity security risk threshold, T used Indicates the elapsed time from the start of payment to the current time, T limit Indicates the set payment limit time;

[0082] The calculated environmental risk coefficient Z is compared with the set environmental risk threshold κ; when the environmental risk coefficient Z ≤ the set environmental risk threshold κ, the payment environment is judged to be safe and the payment process is allowed to continue; when the environmental risk coefficient Z > the set environmental risk threshold κ, the payment procedure is immediately interrupted and a warning message is issued to the user payment interface for display.

[0083] like Figure 2The embodiment shown provides an implementation system corresponding to a secure payment protection method based on multi-source information fusion, including a payment information collection module, a payment information processing and classification module, a payment information matching module, a device security detection module, an account security detection module, an identity security risk detection module, a payment time detection module, and a payment environment risk assessment module. The payment information collection module is connected to the payment information processing and classification module, the payment information processing and classification module is connected to the payment information matching module, the payment information matching module is connected to the device security detection module, the device security detection module is connected to the account security detection module, the account security detection module is connected to the identity security risk detection module, the identity security risk detection module is connected to the payment time detection module, and the payment environment risk assessment module is connected to the device security detection module, the account security detection module, the identity security risk detection module, and the payment time detection module.

[0084] The payment information collection module extracts payment security related information from the data source, including user identity authentication information, transaction feature information, and risk indication information, and imports the extracted payment security related information into the database;

[0085] The payment information processing and classification module processes the payment security related information imported into the database, classifies and marks the payment security related information according to data type, and updates the imported payment security related information in the database in real time;

[0086] The payment information matching module matches the payment keyword input by the user during payment with the payment security related information in the database to obtain the information matching degree, and determines whether the payment keyword input by the user matches the payment security related information already in the database according to the information matching degree. If not, the payment procedure is terminated immediately; if matched, the security of the payment device is continuously tested;

[0087] The device security detection module is used to calculate the device security score, and detect whether the payment device is safe through the device security score. If it is detected that the payment device is not safe, the payment procedure is immediately terminated. If it is detected that the payment device is safe, the security detection of the user's payment account continues;

[0088] The account security detection module is used to analyze and calculate the account security value, and detect whether the user's payment account is safe through the account security value. If it is detected that the user's payment account is not safe, the payment procedure is immediately terminated. If it is detected that the user's payment account is safe, the correct detection of the user's payment identity is continued;

[0089] The identity security risk detection module detects whether the user's payment identity has security risks by analyzing and calculating the identity security risk value. If it is detected that the user's payment identity is not secure, the payment procedure is terminated immediately. If it is detected that the user's payment identity is secure, the payment time is continued to be detected.

[0090] The payment time detection module detects whether the payment time exceeds the time limit. If it is detected that the payment time exceeds the time limit, the payment program is immediately terminated and the user is prompted to re-authenticate. If it is detected that the payment time does not exceed the payment time limit, the security of the payment environment is continuously detected;

[0091] The payment environment risk assessment module calculates the environmental risk coefficient to detect whether the environment of the entire payment process is safe. If it is detected that the environment of the entire payment process is unsafe, the payment procedure is immediately interrupted and a prompt warning message is issued.

[0092] Finally: The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention should be included in the protection scope of the present invention.

[0093] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A secure payment protection method based on multi-source information fusion, characterized in that: include: S1: extracting payment security related information from the data source, including user identity authentication information, transaction feature information, and risk indication information, and importing the extracted payment security related information into the database; S2: Process the payment security related information imported into the database, classify and mark the payment security related information according to data type, and update the imported payment security related information in the database in real time; S3: Match the payment keyword input by the user during payment with the payment security related information in the database to obtain the information matching degree, and determine whether the payment keyword input by the user matches the payment security related information in the database according to the information matching degree. If not, the payment procedure is terminated immediately. If matched, S4 is continued to be executed to detect the security of the payment device. S4: used to calculate the device security score, and detect whether the payment device is safe through the device security score. If the payment device is detected to be unsafe, the payment procedure is terminated immediately. If the payment device is detected to be safe, S5 is continued to perform security detection of the user's payment account; S5: used to analyze and calculate the account security value, and detect whether the user's payment account is safe through the account security value. If it is detected that the user's payment account is not safe, the payment program is immediately terminated. If it is detected that the user's payment account is safe, S6 is continued to be executed to detect the correctness of the user's payment identity; S6: Detecting whether the user's payment identity has security risks by analyzing and calculating the identity security risk value. If it is detected that the user's payment identity is not secure, the payment procedure is terminated immediately. If it is detected that the user's payment identity is secure, continue to execute S7 to detect the payment time. S7: Detecting whether the payment time exceeds the time limit. If it is detected that the payment time exceeds the time limit, the payment procedure is immediately terminated and the user is prompted to re-authenticate. If it is detected that the payment time does not exceed the payment time limit, S8 is continued to be executed to detect the security of the payment environment. S8: By calculating the environmental risk coefficient, detect whether the environment of the entire payment process is safe. If it is detected that the environment of the entire payment process is unsafe, immediately interrupt the payment process and issue a warning message; S3 extracts payment keywords from user input, retrieves security information related to the keywords in the database, compares the keywords input by the user with the retrieved information, calculates the degree of information matching based on the comparison results, and calculates the degree of information matching through the cosine similarity formula A represents the keyword vector input by the user, and B represents the payment security information vector in the database; Compare the information matching degree D with the preset information matching threshold d. When the information matching degree D ≥ the preset information matching threshold d, it means that the keyword vector input by the user is similar to the payment security information vector in the database. It is determined that the keyword input by the user matches the payment security information in the database, and the security detection of the payment device continues. When the information matching degree D < the preset information matching threshold d, it means that the keyword input by the user does not match the payment security information in the database, and the payment keyword is determined to be invalid, and the payment procedure is terminated. It is characterized in that the device security score of S4 is obtained by automatically obtaining the actual scores s1, s2, s3, ..., s i ,…,s n The calculation formula is S represents the device security score, a i represents the weight of the i-th safety detection index, s i represents the actual score of the i-th safety detection indicator, with a value range of [0,1], and n represents the total number of safety detection indicators; Compare the device security score S with the security score threshold x. When the device security score S < security score threshold x, the device is determined to be unsafe. When the device security score S ≥ security score threshold x, the device is determined to be safe and the security check of the user's payment account continues. S5 calculates the account security value Q=B-(I+P) by obtaining the account login behavior abnormality score I, the account password complexity score B and the payment behavior abnormality score P; Compare the account security value Q with the account security threshold τ. When the account security value Q < the account security threshold τ, the account is determined to be unsafe and the payment procedure is terminated immediately. When the account security value Q ≥ the account security threshold τ, the account is determined to be safe and the payment identity detection is continued. S6 calculates the identity security risk value by monitoring the number of times R1, the number of failed authentications R2, and the number of password changes R3 within the time t. b1, b2 are weight coefficients; Compare the identity security risk value F with the identity security risk threshold r. When the identity security risk value F> the identity security risk threshold r, the user's payment identity is determined to be unsafe and the payment procedure is terminated immediately. When the identity security risk value F≤ the identity security risk threshold r, the user's payment identity is determined to be safe and the payment time detection is continued. The specific steps of S7 for detecting payment time are as follows: Step S711: Set a payment time limit. When the user starts the payment process, record the payment start time T start ; Step S712: When the user performs a payment operation, the current time T is monitored in real time. current , and calculate the elapsed time T from the start of payment to the current time used =T current -T start ; Step S713: Set the elapsed time T used The payment time T is set limit For comparison, If T used ≤T limit , then continue to test the security of the payment environment; If T used >T limit , the payment process is terminated immediately, all unfinished data in the current payment process is cleared, and a prompt message is displayed to the user, informing him that the payment time has exceeded the limit and that he needs to re-authenticate. The S8 calculates the environmental risk coefficient by monitoring the data changes of the entire payment process. The specific calculation formula is: S represents the device security score, x represents the security score threshold, Q represents the account security value, q represents the account security threshold, F represents the identity security risk value, r represents the identity security risk threshold, T used Indicates the elapsed time from the start of payment to the current time, T limit Indicates the set payment limit time; The calculated environmental risk coefficient Z is compared with the set environmental risk threshold κ; when the environmental risk coefficient Z ≤ the set environmental risk threshold κ, the payment environment is judged to be safe and the payment process is allowed to continue; when the environmental risk coefficient Z > the set environmental risk threshold κ, the payment procedure is immediately interrupted and a warning message is issued to the user payment interface for display.

2. A secure payment protection method based on multi-source information fusion according to claim 1, characterized in that: The S1 identifies the data sources of information related to payment security, including transaction system database, user behavior log and security database; By obtaining the transaction system database connection information, the database driver is used to automatically extract transaction feature information from the transaction system database, including transaction amount, transaction time, transaction location and transaction frequency; Extract user authentication information, including username, password, phone number, and verification code, by reading user behavior logs using file I / O operations; By obtaining the security database connection information, use the ORM tool to automatically extract risk indication information from the security database, including the number of failed logins, the number of abnormal account activities, and the number of security warnings.

3. A secure payment protection method based on multi-source information fusion according to claim 1, characterized in that: The process of S2 processing the payment security related information imported into the database includes: data cleaning, data conversion and data verification, and classifying the processed payment security related information in the database according to the payment security information data type, and then marking the classified payment security related information by using an automated tool, and storing the classified and marked payment security related information in a corresponding data table. At the same time, the payment security related information is regularly backed up and updated in the database according to the import time.

4. A secure payment protection system based on multi-source information fusion, implementing a secure payment protection method based on multi-source information fusion as described in any one of claims 1 to 3, characterized in that: include: Payment information collection module: extracts payment security related information from the data source, including user identity authentication information, transaction feature information, and risk indication information, and imports the extracted payment security related information into the database; Payment information processing and classification module: performs data processing on the payment security related information imported into the database, classifies and marks the payment security related information by data type, and updates the imported payment security related information in the database in real time; Payment information matching module: matches the payment keyword input by the user during payment with the payment security related information in the database to obtain the information matching degree, and determines whether the payment keyword input by the user matches the payment security related information in the database through the information matching degree. If not, the payment procedure is terminated immediately; if matched, the security of the payment device is continued to be tested; Device security detection module: used to calculate the device security score and detect whether the payment device is safe through the device security score. If the payment device is detected to be unsafe, the payment procedure is terminated immediately. If the payment device is detected to be safe, the security detection of the user's payment account is continued; Account security detection module: used to analyze and calculate the account security value, and detect whether the user's payment account is safe through the account security value. If it is detected that the user's payment account is not safe, the payment procedure is terminated immediately. If it is detected that the user's payment account is safe, the correct detection of the user's payment identity will continue; Identity security risk detection module: detects whether the user's payment identity has security risks by analyzing and calculating the identity security risk value. If it is detected that the user's payment identity is not secure, the payment procedure is terminated immediately. If it is detected that the user's payment identity is secure, the payment time is continued to be detected. Payment time detection module: detects whether the payment time exceeds the time limit. If it is detected that the payment time exceeds the time limit, the payment process is immediately terminated and the user is prompted to re-authenticate. If it is detected that the payment time does not exceed the payment time limit, the security of the payment environment is continuously tested; Payment environment risk assessment module: By calculating the environmental risk coefficient, it detects whether the environment of the entire payment process is safe. If it is detected that the environment of the entire payment process is unsafe, the payment procedure will be immediately interrupted and a prompt warning message will be issued.

Images