Payment transaction request processing method, server and storage medium

By decoding the payment transaction request of the mobile terminal on the server, and judging the legality of the encoder based on the matching between the decoded password and the pre-stored payment password, the problem of low payment security after the payment password is stolen is solved, and higher payment transaction security is achieved.

CN119558848APending Publication Date: 2025-03-04BANK OF CHINA
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411603351.1
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-11-11
Publication Date
2025-03-04

AI Technical Summary

Technical Problem

In existing online payment transactions, payment passwords are easily stolen or tampered, resulting in low payment security during payment transaction request processing.

Method used

The encoded password in the payment transaction request sent by the mobile terminal is decoded through the decoder on the server. If the decoding password is inconsistent with the pre-stored payment password, it is determined whether the pre-stored encoder of the mobile terminal is consistent with the encoder corresponding to the decoder corresponding to the account, and if it is inconsistent, the decoding process will be performed again.

Benefits of technology

Improve payment security during payment transaction request processing, preventing payment transaction operations through other mobile terminals after payment passwords are stolen.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119558848A_ABST
    Figure CN119558848A_ABST
Patent Text Reader

Abstract

The embodiment of the invention provides a payment transaction request processing method, a server and a storage medium, and relates to the field of artificial intelligence. The method comprises the following steps: in response to a payment transaction request sent by a mobile terminal held by a user, decoding a coded password in the payment transaction request based on a first decoder corresponding to an account in the payment transaction request to obtain a first decoded password; if it is determined that the first decoding password is inconsistent with the pre-stored payment password of the account, obtaining a pre-stored encoder in the mobile terminal from the mobile terminal; if it is determined that the pre-stored encoder is not the encoder corresponding to the first decoder, determining a second decoder corresponding to the pre-stored encoder, and decoding the coded password according to the second decoder to obtain a second decoded password; and processing the payment transaction request according to the second decoding password and a pre-stored payment password of the account. According to the method, the payment security in the payment transaction request processing process can be improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of artificial intelligence, and in particular to a method for processing a payment transaction request, a server, and a storage medium. Background Art

[0002] At present, online shopping and transfer payment and other online payment transaction methods have become the common methods used by people. At present, the main method of online payment is to perform payment password verification based on the payment transaction request initiated by the user.

[0003] In the prior art, when a user places an order for online shopping based on a mobile terminal, a payment transaction request is initiated through the mobile terminal. The payment account and payment password entered by the user in the payment transaction request are verified based on the server. After the verification is passed, the mobile terminal can complete the payment transaction operation.

[0004] However, in the above method, the payment password is very easy to be stolen or tampered with. Once the payment password is stolen, there is a possibility of performing payment transactions through other mobile terminals, resulting in low payment security during the payment transaction request processing process. Summary of the invention

[0005] The embodiments of the present application provide a method for processing a payment transaction request, a server, and a storage medium, so as to achieve the technical effect of improving the payment security during the payment transaction request processing.

[0006] In a first aspect, an embodiment of the present application provides a method for processing a payment transaction request, the method being applied to a server; the method comprising:

[0007] In response to a payment transaction request sent by a mobile terminal held by a user, based on a first decoder corresponding to an account in the payment transaction request, the encoded password in the payment transaction request is decoded to obtain a first decoded password; wherein the encoded password is obtained by encoding the payment password input by the user based on a pre-stored encoder;

[0008] If it is determined that the first decoding password and the pre-stored payment password of the account are inconsistent, obtaining a pre-stored encoder in the mobile terminal from the mobile terminal;

[0009] If it is determined that the pre-stored encoder is not the encoder corresponding to the first decoder, then determining a second decoder corresponding to the pre-stored encoder, and decoding the encoded password according to the second decoder to obtain a second decoded password;

[0010] The payment transaction request is processed according to the second decoding password and the pre-stored payment password of the account.

[0011] In a possible implementation, processing the payment transaction request according to the second decoding password and the pre-stored payment password of the account includes:

[0012] Determine the similarity between the second decoding password and the pre-stored payment password; and process the payment transaction request according to the similarity.

[0013] In a possible implementation, determining the similarity between the second decoding password and the pre-stored payment password includes:

[0014] If it is determined that the second decoding password is consistent with the pre-stored payment password, then determining the similarity between the second decoding password and the pre-stored payment password of the account, and determining the similarity to be a fixed value;

[0015] Alternatively, if it is determined that the second decoding password and the pre-stored payment password are inconsistent, the number of first positions and the number of second positions corresponding to each other between the second decoding password and the pre-stored payment password are determined according to each first password value in the second decoding password and each second password value in the pre-stored payment password; wherein the first password value corresponding to the first position is consistent with the second password value corresponding to the first position; and the first password value corresponding to the second position is inconsistent with the second password value corresponding to the second position;

[0016] The similarity between the second decoding password and the pre-stored payment password is determined according to the number of the first positions and the number of the second positions.

[0017] In a possible implementation, processing the payment transaction request according to the similarity includes:

[0018] If it is determined that the similarity indicates that the second decoded password is consistent with the pre-stored payment password, sending a biometric identification indication to the mobile terminal; wherein the biometric identification indication is used to collect the biometric features of the user;

[0019] Receiving the biometric feature sent by the mobile terminal; and matching the biometric feature with the pre-stored biometric feature corresponding to the account to generate a matching result;

[0020] The payment transaction request is processed according to the matching result.

[0021] In a possible implementation, the method further includes:

[0022] If it is determined that the similarity indicates that the second decoded password and the pre-stored payment password are inconsistent, determining the number of password inputs by the user;

[0023] If it is determined that the number of password input times is greater than a first number threshold, an account freezing instruction is sent to the mobile terminal; wherein the account freezing instruction is used to instruct freezing of the account.

[0024] In a possible implementation, the method further includes:

[0025] If it is determined that the pre-stored encoder is not the encoder corresponding to the first decoder, historical account information is obtained from the mobile terminal; wherein the historical account information includes at least one historical account for which an account login operation is performed based on the mobile terminal;

[0026] Determine the correlation index between the historical account and the account; and process the payment transaction request according to each of the correlation indexes; wherein the correlation index represents the correlation between the historical account and the account.

[0027] In a possible implementation, the method further includes:

[0028] If it is determined that the pre-stored encoder is the encoder corresponding to the first decoder, determining the number of password inputs by the user;

[0029] If it is determined that the number of password input times is greater than a second number threshold, an account freezing instruction is sent to the mobile terminal; wherein the account freezing instruction is used to freeze the user's account.

[0030] In a possible implementation, the method further includes:

[0031] In response to a biometric identification request sent by the mobile terminal, identifying and processing a biometric feature in the biometric identification request; wherein the biometric identification request is generated based on a login account operation of the user;

[0032] If it is determined that the biometric feature identification in the biometric identification request passes, determining a first decoder corresponding to the account in the biometric identification request and an encoder corresponding to the first decoder;

[0033] The encoder corresponding to the first decoder is sent to the mobile terminal, wherein the encoder corresponding to the first decoder is stored in a memory in the mobile terminal.

[0034] In a second aspect, an embodiment of the present application provides a payment transaction request processing device, the device being applied to a server; the device comprising:

[0035] A first decoding module, configured to respond to a payment transaction request sent by a mobile terminal held by a user, and decode the encoded password in the payment transaction request based on a first decoder corresponding to the account in the payment transaction request to obtain a first decoded password; wherein the encoded password is obtained by encoding the payment password input by the user based on a pre-stored encoder;

[0036] an acquisition module, configured to acquire a pre-stored encoder in the mobile terminal from the mobile terminal if it is determined that the first decoding password and the pre-stored payment password of the account are inconsistent;

[0037] A second decoding module, for determining a second decoder corresponding to the pre-stored encoder if it is determined that the pre-stored encoder is not the encoder corresponding to the first decoder, and decoding the encoded password according to the second decoder to obtain a second decoded password;

[0038] A processing module is used to process the payment transaction request according to the second decoding password and the pre-stored payment password of the account.

[0039] In a possible implementation manner, the processing module is specifically used to: determine the similarity between the second decoding password and the pre-stored payment password; and process the payment transaction request according to the similarity.

[0040] In one possible implementation, the processing module is specifically used to: if it is determined that the second decoding password is consistent with the pre-stored payment password, determine the similarity between the second decoding password and the pre-stored payment password of the account, and determine the similarity to be a fixed value; or, if it is determined that the second decoding password is inconsistent with the pre-stored payment password, determine the number of corresponding first positions and the number of second positions between the second decoding password and the pre-stored payment password according to each first password value in the second decoding password and each second password value in the pre-stored payment password; wherein the first password value corresponding to the first position is consistent with the second password value corresponding to the first position; the first password value corresponding to the second position is inconsistent with the second password value corresponding to the second position; and determine the similarity between the second decoding password and the pre-stored payment password according to the number of the first positions and the number of the second positions.

[0041] In a possible implementation, the processing module is further specifically used to: if it is determined that the similarity characterizes that the second decoded password and the pre-stored payment password are consistent, send a biometric indication to the mobile terminal; wherein the biometric indication is used to collect the user's biometric features; receive the biometric features sent by the mobile terminal; and match the biometric features with the pre-stored biometric features corresponding to the account to generate a matching result; and process the payment transaction request based on the matching result.

[0042] In a possible implementation, the processing module is further specifically used to: if it is determined that the similarity characterizes that the second decoding password and the pre-stored payment password are inconsistent, determine the number of times the user has entered the password; if it is determined that the number of times the password has been entered is greater than a first number threshold, send an account freezing indication to the mobile terminal; wherein the account freezing indication is used to instruct the freezing of the account.

[0043] In a possible implementation, the device is also used for: if it is determined that the pre-stored encoder is not the encoder corresponding to the first decoder, obtaining historical account information from the mobile terminal; wherein the historical account information includes at least one historical account for account login operations based on the mobile terminal; determining correlation indicators between the historical account and the account; and processing the payment transaction request according to each of the correlation indicators; wherein the correlation indicators represent the correlation between the historical account and the account.

[0044] In a possible implementation, the device is also used to: if it is determined that the pre-stored encoder is the encoder corresponding to the first decoder, determine the number of times the user has entered the password; if it is determined that the number of times the password has been entered is greater than a second number threshold, send an account freezing instruction to the mobile terminal; wherein the account freezing instruction is used to freeze the user's account.

[0045] In a possible implementation, the device is also used to: in response to a biometric request sent by the mobile terminal, identify and process the biometric features in the biometric request; wherein the biometric request is generated based on the user's login account operation; if it is determined that the biometric features in the biometric request are recognized, then determine the first decoder corresponding to the account in the biometric request and the encoder corresponding to the first decoder; send the encoder corresponding to the first decoder to the mobile terminal, wherein the encoder corresponding to the first decoder is stored in a memory in the mobile terminal.

[0046] In a third aspect, an embodiment of the present application provides a server, including: a memory, a processor;

[0047] The memory stores computer-executable instructions;

[0048] The processor executes the computer-executable instructions stored in the memory, so that the processor executes the above first aspect and / or various possible implementations of the first aspect.

[0049] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, in which computer-executable instructions are stored. When the computer-executable instructions are executed by a processor, they are used to implement the first aspect above and / or various possible implementations of the first aspect.

[0050] In a fifth aspect, an embodiment of the present application provides a computer program product, including a computer program, which, when executed by a processor, implements the above first aspect and / or various possible implementation methods of the first aspect.

[0051] The payment transaction request processing method, server and storage medium provided in the embodiments of the present application are that the user's mobile terminal pre-stores an encoder, and encodes the payment password input by the user to obtain an encoded password. Based on the decoder of the server, the encoded password carried in the payment transaction request sent by the mobile terminal is decoded to obtain a decoded password. When the decoded password is inconsistent with the pre-stored payment password, it is necessary to judge the encoder pre-stored in the mobile terminal. If the encoder pre-stored in the mobile terminal is not the encoder corresponding to the decoder corresponding to the account, it is necessary to decode again based on the decoder corresponding to the encoder pre-stored in the mobile terminal, and process the payment transaction request sent by the mobile terminal in combination with the pre-stored payment password. Furthermore, by judging the encoder pre-stored in the mobile terminal when the decoded password obtained by the decoder corresponding to the user account is inconsistent with the pre-stored payment password, the problem of performing payment transaction operations through other mobile terminals after the payment password is stolen can be solved, thereby improving the payment security during the payment transaction request processing process. BRIEF DESCRIPTION OF THE DRAWINGS

[0052] 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.

[0053] Figure 1 A schematic diagram of an application scenario provided for this application;

[0054] Figure 2 A flowchart of a method for processing a payment transaction request provided in an embodiment of the present application;

[0055] Figure 3 A flowchart of another method for processing a payment transaction request provided in an embodiment of the present application;

[0056] Figure 4 A schematic diagram of the structure of a payment transaction request processing device provided in an embodiment of the present application;

[0057] Figure 5 A schematic diagram of the structure of a server provided in an embodiment of the present application.

[0058] 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

[0059] 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.

[0060] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use, processing, transmission, provision, disclosure and application of the relevant data comply with relevant laws, regulations and standards, take necessary confidentiality measures, do not violate public order and good morals, and provide corresponding operation entrances for users to choose to authorize or refuse.

[0061] In addition, this application involves big data analysis of user information (including but not limited to personal biometrics, identity data, consumption data, asset data, electronic terminal operation data, etc.), and the use of artificial intelligence technology for automated decision-making, and a technical solution for making decisions that have a significant impact on personal rights and interests based on the results of automated decision-making. The application provides users with corresponding operation entrances for them to choose to agree or reject the results of automated decision-making; if the user chooses to reject, the expert decision-making process will be entered.

[0062] It should be noted that the payment transaction request processing method, server and storage medium of the present application can be used in the field of artificial intelligence, and can also be used in any field other than artificial intelligence. The application field of the payment transaction request processing method, server and storage medium of the present application is not limited.

[0063] Figure 1 This is a schematic diagram of an application scenario provided by this application. Figure 1As shown, the specific application scenario of the present application includes a server 101 and a mobile terminal 102. When a user 103 places an online shopping order based on the mobile terminal 102, a payment transaction request is initiated through the mobile terminal 102, and the payment account and payment password entered by the user 103 in the payment transaction request are verified based on the server 101. After the verification is passed, the mobile terminal 102 can complete the payment transaction operation.

[0064] However, in the above method, the payment password is very easy to be stolen or tampered with. Once the payment password is stolen, there is a possibility of performing payment transactions through other mobile terminals, resulting in low payment security during the payment transaction request processing process.

[0065] In response to the above technical problems, the present application proposes the following technical concept: based on the decoder of the server, the encoded password obtained by the pre-stored encoding processing of the mobile terminal is decoded to obtain the decoded password. When the decoded password is inconsistent with the pre-stored payment password, it is necessary to judge the encoder pre-stored in the mobile terminal. If the encoder pre-stored in the mobile terminal is not the encoder corresponding to the decoder corresponding to the account, it is necessary to decode again based on the decoder corresponding to the encoder pre-stored in the mobile terminal, and process the payment transaction request sent by the mobile terminal in combination with the pre-stored payment password. In this way, it can solve the problem in the prior art that when the payment password is stolen, there is a payment transaction operation through other mobile terminals, resulting in low payment security during the payment transaction request processing process.

[0066] 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.

[0067] Figure 2 A flowchart of a method for processing a payment transaction request provided in an embodiment of the present application is shown as follows: Figure 2 As shown, the method includes:

[0068] 201. In response to a payment transaction request sent by a mobile terminal held by a user, based on a first decoder corresponding to an account in the payment transaction request, the encoded password in the payment transaction request is decoded to obtain a first decoded password; wherein the encoded password is obtained by encoding the payment password input by the user based on a pre-stored encoder.

[0069] Exemplarily, the execution subject of this embodiment may be a server. The user logs in to the account on the mobile terminal, and based on the user's input operation on the mobile terminal and the user's account, initiates a payment transaction request, and obtains the payment password entered by the user at the same time. The mobile terminal calls a pre-stored encoder, and according to the pre-stored encoder, encodes the payment password entered by the user into an encoded password, and carries the encoded password in the payment transaction request and sends it to the server. The server receives the payment transaction request sent by the mobile terminal, and according to the user's account carried in the payment transaction request, calls the decoder corresponding to the account, i.e., the first decoder, and decodes the encoded password carried in the payment transaction request based on the first decoder to obtain the corresponding decoded password, i.e., the first decoded password, for processing.

[0070] 202. If it is determined that the first decoding password and the pre-stored payment password of the account are inconsistent, obtain a pre-stored encoder in the mobile terminal from the mobile terminal.

[0071] Exemplarily, the server obtains the pre-stored payment password corresponding to the account based on the currently obtained account, and compares the obtained first decoding password with the pre-stored payment password of the account. If it is determined that the first decoding password and the pre-stored payment password of the account are inconsistent, it means that there is an abnormal situation that the payment password has been stolen or tampered with. In order to avoid using other mobile terminals to perform payment transactions, the server needs to obtain the pre-stored encoder in the mobile terminal from the current mobile terminal for confirmation processing.

[0072] It is worth adding that when comparing the obtained first decoding password with the pre-stored payment password of the account, if the first decoding password and the pre-stored payment password are consistent, the server will process the payment transaction data carried in the payment transaction request and return the processed reply data to the mobile terminal; the mobile terminal executes the corresponding payment transaction operation based on the received reply data.

[0073] 203. If it is determined that the pre-stored encoder is not the encoder corresponding to the first decoder, determine a second decoder corresponding to the pre-stored encoder, and decode the encoded password according to the second decoder to obtain a second decoded password.

[0074] Exemplarily, the server matches the pre-stored encoder in the mobile terminal with the first decoder currently called, and determines whether the pre-stored encoder is the encoder corresponding to the first decoder. If it is determined that the pre-stored encoder is not the encoder corresponding to the first decoder, it means that there may be an abnormal situation in which the user uses other mobile terminals to perform payment transactions. In this case, it is necessary to obtain the decoder corresponding to the pre-stored encoder, that is, the second decoder, based on the pre-stored encoder, and based on the second decoder, the received encoded password is decoded again to obtain a new decoded password, that is, the second decoded password.

[0075] 204. Process the payment transaction request according to the second decoding password and the pre-stored payment password of the account.

[0076] Exemplarily, the server will verify and compare the second decoded password and the pre-stored payment password of the account based on a preset password verification method to generate reply data corresponding to the payment transaction request and send it to the mobile terminal. The mobile terminal performs the payment transaction operation corresponding to the payment transaction request based on the reply data.

[0077] In the present embodiment, a method for processing payment transaction requests is provided, in which a user's mobile terminal pre-stores an encoder, and encodes the payment password input by the user to obtain an encoded password, and a decoder based on a server decodes the encoded password carried in the payment transaction request sent by the mobile terminal to obtain a decoded password, and when the decoded password is inconsistent with the pre-stored payment password, it is necessary to judge the encoder pre-stored in the mobile terminal, if the encoder pre-stored in the mobile terminal is not the encoder corresponding to the decoder corresponding to the account, it is necessary to decode again based on the decoder corresponding to the encoder pre-stored in the mobile terminal, and process the payment transaction request sent by the mobile terminal in combination with the pre-stored payment password; further, by judging the encoder pre-stored in the mobile terminal when the decoded password obtained based on the decoder corresponding to the user account is inconsistent with the pre-stored payment password, the problem of performing payment transaction operations through other mobile terminals after the payment password is stolen can be solved, thereby improving the payment security in the payment transaction request processing process.

[0078] Figure 3 A flowchart of another method for processing a payment transaction request provided in an embodiment of the present application is shown as follows: Figure 3 As shown, the method includes:

[0079] 301. In response to a biometric identification request sent by a mobile terminal, identify and process the biometric features in the biometric identification request; wherein the biometric identification request is generated based on a user's login account operation.

[0080] Exemplarily, the client logs into the account on the mobile terminal and initiates a biometric identification request to the server. The server receives the biometric identification request and performs identification processing on the biometric features of the user in the biometric identification request to obtain an identification result.

[0081] 302. If it is determined that the biometric feature recognition in the biometric recognition request is passed, determine a first decoder corresponding to the account in the biometric recognition request and an encoder corresponding to the first decoder.

[0082] Exemplarily, if the server determines that the biometric feature recognition in the biometric recognition request passes, then the server determines the decoder corresponding to the account, ie, the first decoder, and the encoder corresponding to the first decoder according to the account in the biometric recognition request.

[0083] 303. Send the encoder corresponding to the first decoder to the mobile terminal, wherein the encoder corresponding to the first decoder is stored in a memory in the mobile terminal.

[0084] Exemplarily, the server sends the encoder corresponding to the first decoder to the mobile terminal, and the mobile terminal receives the encoder and pre-stores the encoder in the memory of the mobile terminal.

[0085] 304. In response to a payment transaction request sent by a mobile terminal held by a user, the encoded password in the payment transaction request is decoded based on a first decoder corresponding to the account in the payment transaction request to obtain a first decoded password; wherein the encoded password is obtained by encoding the payment password input by the user based on a pre-stored encoder.

[0086] Exemplarily, this step refers to the content of step 201, which will not be repeated here.

[0087] 305. If it is determined that the first decoding password and the pre-stored payment password of the account are inconsistent, obtain a pre-stored encoder in the mobile terminal from the mobile terminal.

[0088] Exemplarily, this step refers to the content of step 202, which will not be repeated here.

[0089] After step 305 , step 306 , step 308 , or step 310 may be executed.

[0090] 306. If it is determined that the pre-stored encoder is not the encoder corresponding to the first decoder, determine a second decoder corresponding to the pre-stored encoder, and decode the encoded password according to the second decoder to obtain a second decoded password.

[0091] Exemplarily, after step 305, this step refers to the content of step 202 and will not be repeated here.

[0092] 307. Determine the similarity between the second decoding password and the pre-stored payment password; and process the payment transaction request according to the similarity.

[0093] Exemplarily, the server calculates the second decoding password and the pre-stored payment password based on a preset similarity calculation method to obtain the similarity between the two to characterize the degree of similarity between the second decoding password and the pre-stored payment password, and based on the similarity, the server processes the received payment transaction request, such as generating reply data that can execute the payment transaction operation or not execute the payment transaction operation to instruct the mobile terminal to perform the corresponding operation.

[0094] In one example, determining the similarity between the second decoding password and the pre-stored payment password in step 307 includes the following steps:

[0095] The first step is to determine the similarity between the second decoding password and the pre-stored payment password of the account if it is determined that the second decoding password is consistent with the pre-stored payment password, and determine the similarity as a fixed value.

[0096] The second step: if it is determined that the second decoding password and the pre-stored payment password are inconsistent, determine the number of corresponding first positions and the number of corresponding second positions between the second decoding password and the pre-stored payment password according to the first password values ​​in the second decoding password and the second password values ​​in the pre-stored payment password; wherein the first password value corresponding to the first position is consistent with the second password value corresponding to the first position; and the first password value corresponding to the second position is inconsistent with the second password value corresponding to the second position.

[0097] The third step is to determine the similarity between the second decoding password and the pre-stored payment password according to the number of the first position and the number of the second position.

[0098] Exemplarily, the server first determines whether the second decoding password and the pre-stored payment password are consistent. When the second decoding password and the pre-stored payment password are consistent, the similarity between the second decoding password and the pre-stored payment password is set to a fixed value, wherein the fixed value is used to indicate that the second decoding password and the pre-stored payment password are consistent. When the second decoding password and the pre-stored payment password are inconsistent, the first password value in the second decoding password and the corresponding second password value in the pre-stored payment password at each position are compared in sequence according to the order of the positions where each password value is located, and the position where the corresponding first password value and the corresponding second password value are consistent is determined as the first position, and the position where the corresponding first password value and the corresponding second password value are inconsistent is determined as the second position, and then the number of the first position and the number of the second position in the second decoding password and the pre-stored payment password are calculated; and the number of the first position and the number of the second position are calculated and processed by a preset calculation method to obtain the similarity between the second decoding password and the pre-stored payment password.

[0099] In one example, processing the payment transaction request according to the similarity in step 307 includes the following steps:

[0100] The first step is to send a biometric identification indication to the mobile terminal if the similarity indicates that the second decoded password is consistent with the pre-stored payment password; wherein the biometric identification indication is used to collect the user's biometric features.

[0101] The second step is to receive the biometric feature sent by the mobile terminal; and match the biometric feature with the pre-stored biometric feature corresponding to the account to generate a matching result.

[0102] The third step is to process the payment transaction request according to the matching result.

[0103] Exemplarily, based on the similarity between the obtained second decoded password and the pre-stored payment password, if it is determined that the similarity indicates that the second decoded password and the pre-stored payment password are consistent, such as when the similarity is a fixed value, the server sends a biometric identification instruction to the mobile terminal for biometric identification, so that the mobile terminal collects the user's biometrics and sends them back to the server. The server receives the biometrics sent by the mobile terminal, and matches the received biometrics with the pre-stored biometrics corresponding to the current account to obtain a matching result. Then, the server can process the payment transaction request based on the matching result. For example, if the received biometrics fails to match the pre-stored biometrics corresponding to the current account, the server instructs the mobile terminal to refuse to execute the payment transaction operation corresponding to the payment transaction request. If the received biometrics successfully matches the pre-stored biometrics corresponding to the current account, the server instructs the mobile terminal to execute the payment transaction operation corresponding to the payment transaction request, so as to improve the payment security during the payment transaction processing.

[0104] In one example, the processing of the payment transaction request according to the similarity in step 307 further includes the following steps:

[0105] Step 1: If it is determined that the similarity indicates that the second decoded password and the pre-stored payment password are inconsistent, the number of password inputs by the user is determined.

[0106] Step 2: If it is determined that the number of password input times is greater than the first number threshold, an account freezing instruction is sent to the mobile terminal; wherein the account freezing instruction is used to instruct freezing of the account.

[0107] Exemplarily, when the server analyzes the similarity between the obtained second decoded password and the pre-stored payment password, if it is determined that the similarity indicates that the second decoded password and the pre-stored payment password are inconsistent, the server can obtain the number of password input times of the user operating the mobile terminal through the mobile terminal, and compare the number of password input times with a preset first number threshold. If it is determined that the number of password input times is greater than the first number threshold, the server sends an account freezing instruction to the mobile terminal, so that after receiving the account freezing instruction, the mobile terminal freezes the account currently logged in to the mobile terminal to reduce user losses.

[0108] 308. If it is determined that the pre-stored encoder is not the encoder corresponding to the first decoder, obtain historical account information from the mobile terminal; wherein the historical account information includes at least one historical account for account login operations based on the mobile terminal.

[0109] Exemplarily, after step 305, when the server determines whether the pre-stored encoder is the encoder corresponding to the first decoder, if the pre-stored encoder is not the encoder corresponding to the decoder corresponding to the account, multiple historical accounts logged in on the mobile terminal are obtained from the mobile terminal for processing.

[0110] 309. Determine the correlation index between the historical account and the account; and process the payment transaction request according to each correlation index; wherein the correlation index represents the correlation between the historical account and the account.

[0111] Exemplarily, the server analyzes each historical account and the account currently logged in by the mobile terminal through preset rules, determines the relevant indicators of each historical account and the account, and processes the relevant indicators of each historical account and the account based on the preset rules to obtain the processing results, and processes the received payment transaction request according to the processing results.

[0112] In one example, the step 309 of determining the correlation index between the historical account and the account further includes the following steps:

[0113] If it is determined that the server stores pre-stored correlation indicators corresponding to historical accounts and accounts, and the pre-stored correlation indicators are less than a preset threshold, or if it is determined that the server does not store pre-stored correlation indicators corresponding to historical accounts and accounts, then a target account set corresponding to the historical accounts is obtained; wherein the correlation indicators between each account to be selected in the target account set and the historical accounts are greater than the preset threshold.

[0114] According to the correlation indicators between each account to be selected and the historical account, the correlation indicators between the historical accounts and the accounts are determined.

[0115] Exemplarily, for each historical account among all historical accounts obtained, the server performs data query based on the historical account, and when it is determined that the server stores pre-stored correlation indicators between the historical account and the account currently logged in by the mobile terminal, and the pre-stored correlation indicators are greater than a preset threshold; or, if it is determined that the server does not store pre-stored correlation indicators corresponding to the historical account and the account, the server obtains a target account set corresponding to the historical account from a preset database, the target account set includes multiple accounts to be selected and correlation indicators between each account to be selected and the historical account, and the correlation indicators between each account to be selected and the historical account are greater than the preset threshold; the server analyzes the correlation indicators between all accounts to be selected in the target account set and the historical account based on preset rules, and then obtains the correlation indicators between the historical account and the account.

[0116] Specifically, for each historical account among all the historical accounts obtained, when analyzing the correlation indicators between all the accounts to be selected and the historical account in the target account set corresponding to the historical account, the following steps are executed in a loop until the target account set is empty or the target account set includes the account in the current payment transaction request: taking out an account to be selected from the target account set, namely the target account, wherein the correlation indicator between the target account and the historical account is the largest in the target account set; obtaining multiple related accounts of the target account; for each related account of the target account, executing the following steps: updating the correlation indicator between each related account and the historical account according to the formula R=MAX(r,r1*r2), wherein R is the correlation indicator between each related account and the historical account after the update, r is the correlation indicator between each related account and the historical account before the update, r1 is the correlation indicator between the target account and the historical account, and r2 is the correlation indicator between the target account and each related account, obtaining the correlation indicator between each related account and the historical account after the update, namely the updated correlation indicator; when each updated correlation indicator is greater than a preset threshold, inserting the related account corresponding to the updated correlation indicator into the target account set. For each historical account, after the loop step is executed, when the target account set corresponding to the historical account is empty and it is determined that the server stores the relevant indicator between the historical account and the current account, the relevant indicator is used as the relevant indicator between the historical account and the account; when the target account set is empty and it is determined that the server does not store the relevant indicator between the historical account and the account, the relevant indicator between the historical account and the account is set to 0; when the target account set includes the account, the updated relevant indicator corresponding to the account is obtained, that is, the updated relevant indicator between the account and the historical account, and the updated relevant indicator corresponding to the account is used as the relevant indicator between the historical account and the account; then, the relevant indicator between each historical account and the account is obtained.

[0117] In another example, determining the correlation indicators between historical accounts and accounts in step 309 also includes: for each historical account among all historical accounts obtained, the server performs data query based on the historical account, and when it is determined that the server stores the correlation indicators between the historical account and the account currently logged in by the mobile terminal, and the correlation indicators are greater than a preset threshold, the correlation indicators are used as the correlation indicators between the historical account and the account.

[0118] In one example, step 309 processes the payment transaction request according to the relevant indicators, including: after determining each historical account and the relevant indicators of the account, each relevant indicator is compared with a set threshold. When all relevant indicators are less than the set threshold, the server can refuse to execute the payment transaction operation corresponding to the payment transaction request, and send an indication of account freezing to the mobile terminal to instruct the mobile terminal to freeze the account and reduce the user's loss.

[0119] 310. If it is determined that the pre-stored encoder is the encoder corresponding to the first decoder, determine the number of password inputs by the user.

[0120] Exemplarily, after step 305, when the server determines whether the pre-stored encoder is the encoder corresponding to the first decoder, if the pre-stored encoder is the encoder corresponding to the first decoder, the number of password inputs by the user operating the mobile terminal can be obtained through the mobile terminal.

[0121] 311. If it is determined that the number of password input attempts is greater than the second number threshold, an account freezing instruction is sent to the mobile terminal; wherein the account freezing instruction is used to freeze the user's account.

[0122] Exemplarily, the server compares the obtained number of password input attempts with a preset second number threshold. If it is determined that the password input attempt is greater than the second number threshold, the server sends an account freezing instruction to the mobile terminal, so that after the mobile terminal receives the account freezing instruction, it freezes the account currently logged in to the mobile terminal to reduce user losses.

[0123] In this embodiment, based on the above embodiment, the server performs biometric identification on the user on the mobile terminal side and pre-stores the encoder on the mobile terminal. When it is determined that the first decoding password and the pre-stored payment password of the account are inconsistent, and the pre-stored encoder is not the encoder corresponding to the first decoder, the payment transaction request is processed by calculating the similarity between the second decoding password and the pre-stored payment password. This can avoid the abnormal situation of performing payment transaction operations through other mobile terminals after the payment password is stolen, thereby ensuring the security of user data and funds.

[0124] Figure 4 A schematic diagram of a payment transaction request processing device provided in an embodiment of the present application is shown in FIG. Figure 4 As shown, the device is applied to a server; the device includes:

[0125] The first decoding module 401 is used to decode the encoded password in the payment transaction request based on the first decoder corresponding to the account in the payment transaction request in response to the payment transaction request sent by the mobile terminal held by the user, and obtain a first decoded password; wherein the encoded password is obtained by encoding the payment password input by the user based on the pre-stored encoder;

[0126] An acquisition module 402 is configured to acquire a pre-stored encoder in the mobile terminal from the mobile terminal if it is determined that the first decoding password and the pre-stored payment password of the account are inconsistent;

[0127] The second decoding module 403 is used to determine the second decoder corresponding to the pre-stored encoder if it is determined that the pre-stored encoder is not the encoder corresponding to the first decoder, and decode the encoded password according to the second decoder to obtain a second decoded password;

[0128] The processing module 404 is used to process the payment transaction request according to the second decoding password and the pre-stored payment password of the account.

[0129] In a possible implementation, the processing module 404 is specifically used to: determine the similarity between the second decoding password and the pre-stored payment password; and process the payment transaction request according to the similarity.

[0130] In one possible implementation, the processing module 404 is specifically used to: if it is determined that the second decoding password and the pre-stored payment password are consistent, then determine the similarity between the second decoding password and the pre-stored payment password of the account, and determine the similarity as a fixed value; or, if it is determined that the second decoding password and the pre-stored payment password are inconsistent, then determine the number of corresponding first positions and the number of second positions between the second decoding password and the pre-stored payment password according to each first password value in the second decoding password and each second password value in the pre-stored payment password; wherein the first password value corresponding to the first position is consistent with the second password value corresponding to the first position; the first password value corresponding to the second position is inconsistent with the second password value corresponding to the second position; and determine the similarity between the second decoding password and the pre-stored payment password according to the number of first positions and the number of second positions.

[0131] In a possible implementation, the processing module 404 is further specifically used to: if it is determined that the similarity characterizes that the second decoded password and the pre-stored payment password are consistent, send a biometric indication to the mobile terminal; wherein the biometric indication is used to collect the user's biometric features; receive the biometric features sent by the mobile terminal; and match the biometric features with the pre-stored biometric features corresponding to the account to generate a matching result; and process the payment transaction request based on the matching result.

[0132] In a possible implementation, the processing module 404 is further specifically used to: if it is determined that the second decoding password characterized by the similarity is inconsistent with the pre-stored payment password, determine the number of times the user has entered the password; if it is determined that the number of times the password has been entered is greater than the first number threshold, send an account freezing indication to the mobile terminal; wherein the account freezing indication is used to indicate the freezing of the account.

[0133] In one possible implementation, the device is also used for: if it is determined that the pre-stored encoder is not the encoder corresponding to the first decoder, obtaining historical account information from the mobile terminal; wherein the historical account information includes at least one historical account for account login operations based on the mobile terminal; determining correlation indicators between historical accounts and accounts; and processing the payment transaction request according to each correlation indicator; wherein the correlation indicator represents the correlation between historical accounts and accounts.

[0134] In a possible implementation, the device is also used to: if it is determined that the pre-stored encoder is the encoder corresponding to the first decoder, determine the number of times the user's password is input; if it is determined that the number of password input times is greater than a second number threshold, send an account freezing instruction to the mobile terminal; wherein the account freezing instruction is used to freeze the user's account.

[0135] In a possible implementation, the device is also used to: in response to a biometric request sent by a mobile terminal, identify and process the biometric features in the biometric request; wherein the biometric request is generated based on the user's login account operation; if it is determined that the biometric features in the biometric request are identified through, then determine the first decoder corresponding to the account in the biometric request and the encoder corresponding to the first decoder; send the encoder corresponding to the first decoder to the mobile terminal, wherein the encoder corresponding to the first decoder is stored in a memory in the mobile terminal.

[0136] The device of this embodiment can execute the technical solution in the above method. Its specific implementation process and technical principles are the same and will not be repeated here.

[0137] 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 they can be physically separated. And these modules can all be implemented in the form of software called by processing elements; they can also be all implemented in the form of hardware; some modules can also be implemented in the form of software called by processing elements, and some modules can be implemented in the form of hardware. Each module can be a separately established processing element, or it can be integrated in a chip of the above device. In addition, it can also be stored in the memory of the above device in the form of program code, and called and executed by a processing element of the above device. The functions of each module. In addition, all or part of these modules can be integrated together, or they can be implemented independently. The processing element here can be an integrated circuit with signal processing capabilities. In the implementation process, each step of the above method or each module above can be completed by an integrated logic circuit of hardware in the processor element or instructions in the form of software.

[0138] Figure 5 A schematic diagram of the structure of a server provided in an embodiment of the present application, such as Figure 5 As shown, the server includes: a memory 501 and a processor 502; the memory 501 is a memory for storing instructions executable by the processor 502.

[0139] The processor 502 is configured to execute the method provided in the above embodiment.

[0140] The server further includes a receiver 503 and a transmitter 504. The receiver 503 is used to receive instructions and data sent by other devices, and the transmitter 504 is used to send instructions and data to external devices.

[0141] The specific implementation process of the processor can be found in the above method embodiment, and its implementation principle and technical effect are similar, so this embodiment will not be repeated here.

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

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

[0144] An embodiment of the present application also provides a chip for executing instructions, which is used to execute the technical solution of the processing method in the above embodiment.

[0145] The embodiment of the present application also provides a computer-readable storage medium, in which computer-executable instructions are stored. When the computer-executable instructions are executed on a computer, the computer executes the technical solution of the processing method of the above embodiment.

[0146] 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, electrically erasable programmable read-only memory, erasable programmable read-only memory, programmable read-only memory, read-only memory, 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.

[0147] 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 an integral part of the processor. The processor and the readable storage medium can be located in a dedicated integrated circuit. Of course, the processor and the readable storage medium can also exist in a device as discrete components.

[0148] 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, the technical solution of the processing method in the above embodiment can be implemented.

[0149] It should be understood that the above-mentioned device embodiments are only illustrative, and the device of the present application can also be implemented in other ways. For example, the division of units / modules in the above-mentioned embodiments is only a logical function division, and there may be other division methods in actual implementation. For example, multiple units, modules or components can be combined, or can be integrated into another system, or some features can be ignored or not executed.

[0150] Those skilled in the art will appreciate that all or part of the steps of implementing the above-mentioned method embodiments can be completed by hardware associated with 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.

[0151] 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 method for processing a payment transaction request, characterized in that: The method is applied to a server; the method comprises: In response to a payment transaction request sent by a mobile terminal held by a user, based on a first decoder corresponding to an account in the payment transaction request, the encoded password in the payment transaction request is decoded to obtain a first decoded password; wherein the encoded password is obtained by encoding the payment password input by the user based on a pre-stored encoder; If it is determined that the first decoding password and the pre-stored payment password of the account are inconsistent, obtaining a pre-stored encoder in the mobile terminal from the mobile terminal; If it is determined that the pre-stored encoder is not the encoder corresponding to the first decoder, then determining a second decoder corresponding to the pre-stored encoder, and decoding the encoded password according to the second decoder to obtain a second decoded password; The payment transaction request is processed according to the second decoding password and the pre-stored payment password of the account.

2. The method according to claim 1, characterized in that Processing the payment transaction request according to the second decoding password and the pre-stored payment password of the account includes: Determine the similarity between the second decoding password and the pre-stored payment password; and process the payment transaction request according to the similarity.

3. The method according to claim 2, characterized in that Determining the similarity between the second decoding password and the pre-stored payment password includes: If it is determined that the second decoding password is consistent with the pre-stored payment password, then determining the similarity between the second decoding password and the pre-stored payment password of the account, and determining the similarity to be a fixed value; Alternatively, if it is determined that the second decoding password and the pre-stored payment password are inconsistent, the number of first positions and the number of second positions corresponding to each other between the second decoding password and the pre-stored payment password are determined according to each first password value in the second decoding password and each second password value in the pre-stored payment password; wherein the first password value corresponding to the first position is consistent with the second password value corresponding to the first position; and the first password value corresponding to the second position is inconsistent with the second password value corresponding to the second position; The similarity between the second decoding password and the pre-stored payment password is determined according to the number of the first positions and the number of the second positions.

4. The method according to claim 2, characterized in that: Processing the payment transaction request according to the similarity includes: If it is determined that the similarity indicates that the second decoded password is consistent with the pre-stored payment password, sending a biometric identification indication to the mobile terminal; wherein the biometric identification indication is used to collect the biometric features of the user; Receiving the biometric feature sent by the mobile terminal; and matching the biometric feature with the pre-stored biometric feature corresponding to the account to generate a matching result; The payment transaction request is processed according to the matching result.

5. The method according to claim 4, characterized in that The method further comprises: If it is determined that the similarity indicates that the second decoded password and the pre-stored payment password are inconsistent, determining the number of password inputs by the user; If it is determined that the number of password input times is greater than a first number threshold, an account freezing instruction is sent to the mobile terminal; wherein the account freezing instruction is used to instruct freezing of the account.

6. The method according to claim 1, characterized in that The method further comprises: If it is determined that the pre-stored encoder is not the encoder corresponding to the first decoder, historical account information is obtained from the mobile terminal; wherein the historical account information includes at least one historical account for which an account login operation is performed based on the mobile terminal; Determine the correlation index between the historical account and the account; and process the payment transaction request according to each of the correlation indexes; wherein the correlation index represents the correlation between the historical account and the account.

7. The method according to claim 1, characterized in that The method further comprises: If it is determined that the pre-stored encoder is the encoder corresponding to the first decoder, determining the number of password inputs by the user; If it is determined that the number of password input times is greater than a second number threshold, an account freezing instruction is sent to the mobile terminal; wherein the account freezing instruction is used to freeze the user's account.

8. The method according to any one of claims 1 to 7, characterized in that The method further comprises: In response to a biometric identification request sent by the mobile terminal, identifying and processing a biometric feature in the biometric identification request; wherein the biometric identification request is generated based on a login account operation of the user; If it is determined that the biometric feature recognition in the biometric recognition request is passed, determining a first decoder corresponding to the account in the biometric recognition request and an encoder corresponding to the first decoder; The encoder corresponding to the first decoder is sent to the mobile terminal, wherein the encoder corresponding to the first decoder is stored in a memory in the mobile terminal.

9. A server, characterized in that: include: Memory, processor; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory, so that the processor performs the method according to any one of claims 1 to 8.

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 8 when executed by a processor.