Username verification method and device, electronic device and computer-readable storage medium

Abstract

The present disclosure provides an account name verification method and device, an electronic device and a computer-readable storage medium, which can be used in the field of information security, finance or other fields. The account name verification method includes: obtaining the message account name and the pre-stored account name of the transfer business to be processed; determining whether the message account name needs to be converted according to the preset account name checking rules; if the message account name does not need to be converted, matching and checking the message account name and the pre-stored account name; if the message account name needs to be converted, converting the message account name according to the preset conversion rules, and matching and checking the converted message account name and the pre-stored account name; if the message account name does not need to be converted and cannot be matched, performing a similarity check on the message account name and the pre-stored account name; and if the message account name needs to be converted and the converted message account name and the pre-stored account name cannot match, performing a similarity check on the converted message account name and the pre-stored account name.

Description

Technical Field

[0001] The present disclosure relates to the field of information security technology, and more specifically, to a user name verification method and device, an electronic device, a computer-readable storage medium, and a computer program product. Background Art

[0002] With the rapid development of information technology, international business exchanges are becoming more frequent. In domestic and overseas payment scenarios, the payee needs to verify the payee account name and customer name in the message in order to accept or reject the transfer.

[0003] In the process of realizing the concept of the present disclosure, the inventors found that there are at least the following problems in the related technology. In the existing domestic and overseas payment scenarios, the account name verification rules are inconsistent for different countries or regions, and customized rules are used for each region or country. The existing verification method relies on the accuracy of the customer's account opening name and the remitter's account name. An accurate match is required for processing. If there is an inconsistency, it needs to be rejected or handled on the spot. The business processing efficiency is relatively low, which cannot meet the characteristics of the diversity of overseas account names, affecting the transfer success rate and customer satisfaction. Summary of the invention

[0004] In view of this, the present disclosure provides a user name verification method and device, an electronic device, a computer-readable storage medium, and a computer program product.

[0005] One aspect of the present disclosure provides a method for verifying an account name, including:

[0006] Obtain the message account name and pre-deposited account name of the pending transfer business, where the message account name is the account name provided by the transferor when executing the transfer business, and the pre-deposited account name is the account name created by the payee when opening the account;

[0007] According to the preset username check rules, determine whether the message username needs to be converted;

[0008] When the message user name does not need to be converted, the message user name and the pre-stored user name are matched and checked; when the message user name needs to be converted, the message user name is converted according to a preset conversion rule, and the converted message user name and the pre-stored user name are matched and checked;

[0009] When the message username does not need to be converted and cannot be matched, a similarity check is performed on the message username and the pre-stored username; and when the message username needs to be converted and the converted message username and the pre-stored username cannot be matched, a similarity check is performed on the converted message username and the pre-stored username.

[0010] According to an embodiment of the present disclosure, determining whether a message user name needs to be converted according to a preset user name checking rule includes:

[0011] Obtaining basic information of pending transfer business, wherein the basic information of pending transfer business includes the payee's account opening region, business message type, business type, account type and customer type;

[0012] Based on the basic information of the pending transfer business and the preset account name checking rules, determine whether the account name in the message needs to be converted.

[0013] According to an embodiment of the present disclosure, the preset account name check rules include: the payee's account opening region meets the preset conditions, and the business message type meets the preset conditions, and the business type meets the preset conditions, and the account type meets the preset conditions, and the customer type meets the preset conditions.

[0014] According to an embodiment of the present disclosure, when a message user name needs to be converted, converting the message user name according to a preset conversion rule includes:

[0015] When the message user name needs to be converted, the message user name is converted once according to the preset conversion rules;

[0016] Perform a match check between the converted message account name and the pre-stored account name;

[0017] When the user name of the message after the conversion does not match the pre-stored user name, the user name of the message after the conversion is reversed.

[0018] According to an embodiment of the present disclosure, converting the message user name once according to a preset conversion rule includes:

[0019] If the message user name contains spaces, remove the spaces in the message user name;

[0020] If the message user name contains special characters, remove the special characters in the message user name; and

[0021] If the message user name is abbreviated, convert the message user name into a full name.

[0022] According to an embodiment of the present disclosure, the pre-deposited account name includes: a pre-deposited account name in Chinese, a pre-deposited account name in English, a pre-deposited customer name in Chinese, and a pre-deposited customer name in English.

[0023] According to an embodiment of the present disclosure, performing similarity verification on a message account name and a pre-stored account name includes:

[0024] Determine the similarity algorithm;

[0025] Calculate the similarity between the message account name and the pre-stored account name using a similarity algorithm to obtain a similarity calculation value;

[0026] According to the similarity calculation value and the preset threshold value, the verification result of the similarity verification between the message account name and the pre-stored account name is determined.

[0027] According to an embodiment of the present disclosure, the similarity algorithm includes one of the following: a cosine algorithm of a space vector, a Jaccard distance algorithm, a string similarity algorithm, and a Euclidean distance algorithm.

[0028] Another aspect of the present disclosure provides a user name verification device, including: an acquisition module, a determination module, a first verification module and a second verification module.

[0029] The acquisition module is used to acquire the message account name and pre-deposited account name of the pending transfer business, wherein the message account name is the account name provided by the transferor when executing the transfer business, and the pre-deposited account name is the account name created by the payee when opening the account.

[0030] The determination module is used to determine whether the message user name needs to be converted according to a preset user name checking rule.

[0031] Among them, the above-mentioned first verification module is used to match and verify the message username and the pre-stored username when the message username does not need to be converted, and to convert the message username according to the preset conversion rules when the message username needs to be converted, and to match and verify the converted message username and the pre-stored username.

[0032] Among them, the above-mentioned second verification module is used to perform a similarity verification on the message username and the pre-stored username when the message username does not need to be converted and cannot be matched, and to perform a similarity verification on the converted message username and the pre-stored username when the message username needs to be converted and the converted message username and the pre-stored username cannot match.

[0033] According to an embodiment of the present disclosure, the above-mentioned determination module includes an acquisition unit and a first determination unit.

[0034] The acquisition unit is used to acquire basic information of pending transfer business, wherein the basic information of pending transfer business includes the region where the payee's account is opened, the business message type, the business type, the account type and the customer type. The first determination unit is used to determine whether the message account name needs to be converted according to the basic information of pending transfer business and the preset account name checking rules.

[0035] According to an embodiment of the present disclosure, in the above-mentioned determination module, the preset account name checking rules include: the region where the payee's account is opened meets the preset conditions, and the business message type meets the preset conditions, and the business type meets the preset conditions, and the account type meets the preset conditions, and the customer type meets the preset conditions.

[0036] According to an embodiment of the present disclosure, the first verification module includes a primary conversion unit, a primary verification unit and an account name reversal unit.

[0037] The primary conversion unit is used to convert the message user name according to the preset conversion rules when the message user name needs to be converted. The primary verification unit is used to match the message user name after the primary conversion with the pre-stored user name. The user name reversal unit is used to reverse the user name after the primary conversion of the message when the user name after the primary conversion does not match the pre-stored user name.

[0038] According to an embodiment of the present disclosure, in the above-mentioned one-time conversion unit, according to the preset conversion rules, the message username is converted once, including: when the message username contains spaces, the spaces in the message username are removed; and when the message username contains special characters, the special characters in the message username are removed; and when the message username is an abbreviation, the message username is converted into a full name.

[0039] According to an embodiment of the present disclosure, in the above-mentioned acquisition module, the pre-stored account name includes: a pre-stored account name in Chinese, a pre-stored account name in English, a pre-stored customer name in Chinese, and a pre-stored customer name in English.

[0040] According to an embodiment of the present disclosure, in the second verification module, performing similarity verification on the message account name and the pre-stored account name includes:

[0041] Determine a similarity algorithm; use the similarity algorithm to calculate the similarity between the message account name and the pre-stored account name to obtain a similarity calculation value; and determine a verification result of the similarity verification between the message account name and the pre-stored account name based on the similarity calculation value and a preset threshold.

[0042] According to an embodiment of the present disclosure, the similarity algorithm includes one of the following: a cosine algorithm of a space vector, a Jaccard distance algorithm, a string similarity algorithm, and a Euclidean distance algorithm.

[0043] Another aspect of the present disclosure provides an electronic device, including: one or more processors; a memory for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the above-mentioned user name verification method.

[0044] Another aspect of the present disclosure provides a computer-readable storage medium storing computer-executable instructions, which are used to implement the above user name verification method when executed.

[0045] Another aspect of the present disclosure provides a computer program product, which includes computer executable instructions, and the instructions are used to implement the above user name verification method when executed.

[0046] According to the embodiments of the present disclosure, by setting a preset account name check rule, it is determined whether the message account name needs to be converted, and when the message account name before and after the conversion and the pre-stored account name are matched and checked and cannot match, the message account name before and after the conversion and the pre-stored account name are further similarity checked. Through the above technical means, the message account name can be checked without completely and accurately matching the pre-stored account name, so it at least partially overcomes the technical problem in the prior art that the verification can only be completed when there is an accurate match, resulting in relatively low business processing efficiency. Further, through the account name verification method of the embodiments of the present disclosure, the characteristics of the diversity of overseas account names can be met, the business processing efficiency is improved, and the impact on the success rate of transfers and customer satisfaction is improved. BRIEF DESCRIPTION OF THE DRAWINGS

[0047] The above and other objects, features and advantages of the present disclosure will become more apparent through the following description of the embodiments of the present disclosure with reference to the accompanying drawings, in which:

[0048] Figure 1 Schematically illustrates an exemplary system architecture to which the method and apparatus of the present disclosure may be applied;

[0049] Figure 2 A flowchart of a method for verifying an account name according to an embodiment of the present disclosure is schematically shown;

[0050] Figure 3 A flowchart of a method for verifying an account name according to another embodiment of the present disclosure is schematically shown;

[0051] Figure 4 A flowchart schematically shows a similarity check between a message account name and a pre-stored account name according to an embodiment of the present disclosure;

[0052] Figure 5 A block diagram schematically shows a user name verification device according to an embodiment of the present disclosure; and

[0053] Figure 6 A block diagram of an electronic device for implementing a user name verification method according to an embodiment of the present disclosure is schematically shown. DETAILED DESCRIPTION

[0054] Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of the present disclosure. In the following detailed description, for ease of explanation, many specific details are set forth to provide a comprehensive understanding of the embodiments of the present disclosure. However, it is apparent that one or more embodiments may also be implemented without these specific details. In addition, in the following description, descriptions of known structures and technologies are omitted to avoid unnecessary confusion of the concepts of the present disclosure.

[0055] The terms used herein are only for describing specific embodiments and are not intended to limit the present disclosure. The terms "comprise", "include", etc. used herein indicate the existence of the features, steps, operations and / or components, but do not exclude the existence or addition of one or more other features, steps, operations or components.

[0056] All terms (including technical and scientific terms) used herein have the meanings commonly understood by those skilled in the art unless otherwise defined. It should be noted that the terms used herein should be interpreted as having a meaning consistent with the context of this specification and should not be interpreted in an idealized or overly rigid manner.

[0057] In the case of using expressions such as "at least one of A, B, and C, etc.", it should generally be interpreted in accordance with the meaning of the expression generally understood by those skilled in the art (for example, "a system having at least one of A, B, and C" should include but is not limited to a system having A alone, B alone, C alone, A and B, A and C, B and C, and / or A, B, C, etc.). In the case of using expressions such as "at least one of A, B, or C, etc.", it should generally be interpreted in accordance with the meaning of the expression generally understood by those skilled in the art (for example, "a system having at least one of A, B, or C" should include but is not limited to a system having A alone, B alone, C alone, A and B, A and C, B and C, and / or A, B, C, etc.).

[0058] Before elaborating on the embodiments of the present disclosure in detail, the system structure and application scenarios involved in the methods provided in the embodiments of the present disclosure are first introduced as follows.

[0059] Figure 1 The exemplary system architecture 100 to which the method and apparatus of the present disclosure can be applied is schematically shown. It should be noted that: Figure 1 What is shown is merely an example of a system architecture to which the embodiments of the present disclosure can be applied, in order to help those skilled in the art understand the technical content of the present disclosure, but it does not mean that the embodiments of the present disclosure cannot be used in other devices, systems, environments or scenarios.

[0060] like Figure 1 As shown, the system architecture 100 according to this embodiment may include a message receiving system 101 , an account name verification system 102 , and an account processing system 103 .

[0061] The message receiving system 101 is used to receive basic information of pending transfer business in the form of messages, such as the name and account information of the payee provided by the transferor when executing the transfer business, the bank information of the transferor and the payee who executes the transfer business, the area where the payee's account is opened, the business message type, business type, account type and customer type, etc.

[0062] The account name verification system 102 is used to receive the basic business transaction information provided by the receiving system 101, and verify the account name in the message according to the basic business transaction information and the preset verification rules. Specifically, the account name in the message is matched and verified with the account name pre-stored in the bank business system (the account name created by the payee when opening the account). During the verification, the account name in the message is verified layer by layer by combining the account name conversion and similarity verification methods.

[0063] Specifically, first, determine whether it is necessary to convert the message user name. If the message user name does not need to be converted, perform a match check on the message user name and the pre-stored user name. If the message user name needs to be converted, convert the message user name according to the preset conversion rule, and perform a match check on the converted message user name and the pre-stored user name. If the message user name (or the converted message user name) and the pre-stored user name match successfully, the check passes. If the message user name (or the converted message user name) and the pre-stored user name cannot match successfully, perform a similarity check on the message user name (or the converted message user name) and the pre-stored user name. If the similarity is within the preset threshold range, the check passes. If the similarity is not within the preset threshold range, the check fails.

[0064] The accounting processing system 103 is used to record or reject the business according to the verification result (pass or fail) of the account name verification system 102. That is, if the verification result is passed, the business is recorded, and if the verification result is failed, the business is rejected.

[0065] It should be noted that the method and device disclosed herein can be applied not only to domestic remittance scenarios, but also to scenarios such as QR code payment, bank card collection, credit card repayment, etc. that require name verification.

[0066] The account name verification method and device disclosed in the present invention can be used in the information security field and the financial field, and can also be used in any field other than the information security field and the financial field. The present invention does not limit the application field of the account name verification method and device.

[0067] Figure 2 The flowchart of the user name verification method according to the embodiment of the present disclosure is schematically shown. Figure 2 As shown, the method includes operations S201 to S204.

[0068] In operation S201, the message account name and pre-stored account name of the pending transfer business are obtained, wherein the message account name is the account name provided by the transferor when performing the transfer business, that is, the account name filled in by the transferor in the message. The pre-stored account name is the account name pre-stored in the banking business system, that is, the account name created by the payee when opening the account.

[0069] According to an embodiment of the present disclosure, the pre-deposited account name of the pending transfer business can be obtained based on the account information of the payee filled in the message by the transferor, and the pre-deposited account name of the payee can be obtained from the bank business system based on the account number. The pre-deposited account name of the payee can include, for example, the pre-deposited account name in Chinese, the pre-deposited account name in English, the pre-deposited customer name in Chinese, and the pre-deposited customer name in English.

[0070] In operation S202, according to the preset account name check rule, it is determined whether the message account name needs to be converted. The preset account name check rule is a rule preset according to the basic information of the pending transfer business. The pending transfer business basic information may include a variety of information, such as the payee account opening area, the business message type, etc. The account name check rule is a rule set according to one or more of the pending transfer business basic information. For example, the account name check rule can be to determine whether the payee account opening area is within the preset area range. If the payee account opening area is within the preset area range, then the account name conversion is not required; if the payee account opening area is not within the preset area range, then the account name conversion is required (for example, in mainland China, the account name conversion is not required, but in Hong Kong, China, the account name conversion is required).

[0071] In operation S203, when the message username does not need to be converted, the message username and the pre-stored username are matched and checked; and when the message username needs to be converted, the message username is converted according to a preset conversion rule, and the converted message username and the pre-stored username are matched and checked.

[0072] In operation S204, when the message username does not need to be converted and cannot be matched, a similarity check is performed on the message username and the pre-stored username; and when the message username needs to be converted and the converted message username and the pre-stored username cannot match, a similarity check is performed on the converted message username and the pre-stored username.

[0073] The above operations S203 and S204 are combined with the method of user name conversion and similarity verification to perform layer-by-layer verification on the message user name. Specifically, first, it is determined whether the message user name needs to be converted. If the message user name does not need to be converted, the message user name and the pre-stored user name are matched and verified. If the message user name needs to be converted, the message user name is converted according to the preset conversion rules (for example, spaces and special characters in the message user name are removed, the message user name is converted from an abbreviation to a full name, the user name is reversed, etc.), and the converted message user name and the pre-stored user name are matched and verified. If the message user name (or the converted message user name) matches the pre-stored user name successfully, the verification is passed. If the message account name (or the converted message account name) and the pre-stored account name cannot be matched successfully, a similarity check is performed on the message account name (or the converted message account name) and the pre-stored account name. If the similarity is within the preset threshold range, the check passes and the account is recorded. If the similarity is not within the preset threshold range, the check fails and the account is rejected.

[0074] According to the embodiments of the present disclosure, by setting a preset account name check rule, it is determined whether the message account name needs to be converted, and when the message account name before and after the conversion and the pre-stored account name are matched and checked and cannot match, the message account name before and after the conversion and the pre-stored account name are further similarity checked. Through the above technical means, the message account name can be checked without completely and accurately matching the pre-stored account name, so it at least partially overcomes the technical problem in the prior art that the verification can only be completed when there is an accurate match, resulting in relatively low business processing efficiency. Further, through the account name verification method of the embodiments of the present disclosure, the characteristics of the diversity of overseas account names can be met, the business processing efficiency is improved, and the impact on the success rate of transfers and customer satisfaction is improved.

[0075] According to an embodiment of the present disclosure, in the above operation S202, determining whether the message account name needs to be converted according to a preset account name checking rule includes: obtaining basic information of the pending transfer business, and determining whether the message account name needs to be converted according to the preset account name checking rule based on the basic information of the pending transfer business.

[0076] The basic information of the pending transfer business may include information of one or more dimensions, such as but not limited to one or more of the region where the payee's account is opened, the business message type, the business type, the account type and the customer type. The business message type is determined according to the clearing organization, the business type includes, for example, ordinary remittance, alias remittance, etc., the account type includes, for example, ordinary current account, credit card account, intellectual property account, etc., and the customer type includes, for example, corporate customer, individual customer, etc.

[0077] The account name check rule is a rule set based on one or more dimensions of the basic information of the pending transfer business. The preset account name check rules include but are not limited to at least one of the following: the payee's account opening region meets the preset conditions, the business message type meets the preset conditions, the business type meets the preset conditions, the account type meets the preset conditions, and the customer type meets the preset conditions.

[0078] For example, the account name check rule can be to determine whether the payee's account opening area is within the preset area range. If the payee's account opening area is within the preset area range, there is no need to convert the account name; if the payee's account opening area is not within the preset area range, the account name needs to be converted (for example, in mainland China and Singapore, there is no need to convert the account name, but in Hong Kong, China, it is necessary to convert the account name). For another example, it can also be determined whether the payee's account opening area is within the preset area range, whether the business type is within the preset type range, and whether the account type is within the preset type range. That is, only when all three are met at the same time, there is no need to convert the account name (for example, in mainland China, if the business type is ordinary remittance, and the account type is an ordinary current account type, there is no need to convert the account name).

[0079] According to the embodiments of the present disclosure, the account name checking rules are set according to one or more dimensions of basic information of the pending transfer business. Through the account name checking rules, unified verification rules are established for different countries or regions, and there is no need to set up separate verification methods for different message types, business types, account types and customer types, etc., which meets the characteristics of the diversity of overseas account names and improves business processing efficiency.

[0080] Figure 3 The flowchart of the user name verification method according to another embodiment of the present disclosure is schematically shown. Figure 3 As shown, the method includes operations S301 to S304.

[0081] Figure 3 In the illustrated embodiment, operation S301 and a specific method of operation S301, and Figure 2 In the illustrated embodiment, operation S201 and the method of operation S201 are the same and will not be described in detail herein. Figure 3 As shown, the method further includes operations S303 and S304.

[0082] In operations S303 and S304, according to the result determined in operation S202 (whether the message user name needs to be converted), a matching check or a similarity check is performed on the message user name (or the converted message user name) and the pre-stored user name.

[0083] Specifically, in operation S303, when the message account name does not need to be converted, the message account name and the pre-stored account name are matched and checked. If the message account name and the pre-stored account name match successfully, the check is passed and the account entry is processed. If the message account name and the pre-stored account name cannot match successfully, in operation S304, the message account name and the pre-stored account name are checked for similarity. If the similarity is within the preset threshold range, the check is passed and the account entry is processed. If the similarity is not within the preset threshold range, the check is not passed and the account entry is rejected.

[0084] In addition, in operation S303, if the message user name needs to be converted, the message user name is converted according to the preset conversion rule, and the converted message user name is matched with the pre-stored user name. In this case, operation S303 includes operations S3031-S3034.

[0085] In operation S3031, the message user name is converted according to a preset conversion rule.

[0086] According to an embodiment of the present disclosure, the message user name is converted once according to the preset conversion rules, including but not limited to: removing the spaces in the message user name when the message user name contains spaces; removing the special characters in the message user name when the message user name contains special characters or titles (such as Mr, %, #, ?, *, etc.); and converting the message user name into a full name when the message user name is an abbreviation. For example: converting "Li*?Ming" into "LiMing", converting "Mr Jason" into "Jason".

[0087] In operation S3032, the converted message account name and the pre-stored account name are matched and verified. If the converted message account name and the pre-stored account name match successfully, the verification is passed and the account entry process is performed.

[0088] If the converted message user name and the pre-stored user name cannot be matched successfully, in operation S3033, the converted message user name is reversed, for example, "Ming Li" is converted into "LiMing".

[0089] Furthermore, in operation S3034, the reversed message account name and the pre-stored account name are matched and verified. If the reversed message account name and the pre-stored account name match successfully, the verification is passed and the account entry process is performed.

[0090] If the reversed message account name and the pre-stored account name cannot be matched successfully, in operation S304, the reversed message account name and the pre-stored account name are checked for similarity. If the similarity is within the preset threshold range, the check passes and the account is recorded. If the similarity is not within the preset threshold range, the check fails and the account is rejected.

[0091] According to the embodiments of the present disclosure, when the message account name needs to be converted, the message account name is converted once and further reversed according to the preset conversion rules, covering a variety of special situations that can be normally entered into the account but cannot be entered into the account, such as situations where the account name cannot be entered into the account due to the negligence or erroneous input of the transferor, special characters appearing in the account name, and spaces in the message account name cannot be entered into the account, and the account names of the message and the pre-stored account names are reversed and cannot be entered into the account due to inconsistencies in the formats of the message account name and the pre-stored account name, etc. Through the above technical means, the message account name does not need to be completely and accurately matched with the pre-stored account name to complete the verification, which can meet the characteristics of the diversity of overseas account names, further improve business processing efficiency, improve the transfer success rate and customer satisfaction.

[0092] Figure 4 The flowchart of performing similarity check between a message user name and a pre-stored user name according to an embodiment of the present disclosure is schematically shown. Figure 4 As shown, the method includes operations S401 to S403.

[0093] In operation S401, a similarity algorithm is determined.

[0094] In operation S402, a similarity algorithm is used to calculate the similarity between the message account name and the pre-stored account name to obtain a similarity calculation value.

[0095] In operation S403, the verification result of the similarity check between the message account name and the pre-stored account name is determined based on the similarity calculation value and the preset threshold. If the similarity calculation value is within the preset threshold range, the verification passes and the account is recorded. If the similarity calculation value is not within the preset threshold range, the verification fails and the account is rejected.

[0096] For example, the similarity algorithm uses the cosine algorithm of the space vector to calculate the similarity between the message account name "LiMin" and the pre-stored account name "LiMing", and the similarity calculation value is 85%. The preset threshold is set to 80%. If the similarity calculation value is within the preset threshold range, the verification is passed and the account is entered.

[0097] In addition, it should be noted that, according to the embodiments of the present disclosure, although Figure 4 The method shown schematically illustrates a method for performing similarity verification on a message account name and a pre-stored account name. However, all account name verification methods involved in the present disclosure may adopt this method. For example, Figure 2 and Figure 3 This method can be used for similarity checking between the converted message account name and the pre-stored account name, or for similarity checking between the reversed message account name and the pre-stored account name mentioned in the illustrated embodiment. This method does not limit the type of account name to be checked.

[0098] According to an embodiment of the present disclosure, the similarity algorithm includes but is not limited to one of the following: a cosine algorithm of a space vector, a Jaccard distance algorithm, a string similarity algorithm, and a Euclidean distance algorithm. The above algorithms are introduced below respectively.

[0099] (1) The cosine algorithm of space vectors, also known as cosine similarity, evaluates the similarity between two vectors by calculating the cosine value of the angle between them. Cosine similarity plots vectors into a vector space, such as the most common two-dimensional space, based on their coordinate values.

[0100] When using two vectors A and B in the middle of a vector to measure string similarity, you need to vectorize the string first. The closer the cosine value is to 1, the closer the angle is to 0 degrees, that is, the more similar the two vectors (strings) are.

[0101] For example:

[0102] Message user name: string String1 = "Apple"

[0103] Pre-deposited account name: string String2 = "App"

[0104] The word bag is {A, e, l, p}. If we use 0 and 1 to determine whether an element is in the word bag, the strings 1 and 2 can be converted into:

[0105] StringA=

[1111]

[0106] StringB=

[1001]

[0107]

[0108] Then, according to the cosine formula, the similarity between the two strings can be calculated as: 0.707.

[0109] (2) Jaccard distance algorithm

[0110] The ratio of the number of elements in the intersection of two sets A and B to the number of elements in the union of A and B is called the Jaccard coefficient of the two sets, which is used to measure the similarity of the two sets. The larger the Jaccard coefficient value, the higher the sample similarity. It is calculated by dividing the intersection of the two samples by the value obtained by the union. When the two samples are completely consistent, the result is 1, and when the two samples are completely different, the result is 0. The calculation formula is as follows:

[0111]

[0112] For example:

[0113] Message user name: string String1 = "apple"

[0114] Pre-deposited account name: string String2 = "app"

[0115] Then the calculated similarity value of the two strings is: J=3 / 5=0.6.

[0116] (3) String Similarity Algorithm (Jaro-Winkler Distance)

[0117] Jaro-Winkler Distance is used to measure the similarity between two strings. It is actually a variant of Jaro distance. Jaro distance belongs to the category of edit distance and is used in the field of record linking to link records in heterogeneous data sources to synonymous entities. It can also be used for spelling correction. Jaro distance is defined as follows:

[0118]

[0119] Among them, m is the number of characters that match in the two strings, and t is half of the number of transpositions in the characters. That is, if a and b appear in the i-th position of the string, and b and a appear in the j-th position, it means that the two are transposed. For example:

[0120] Message user name: s1=MARTHA

[0121] Deposit account name: s2=MARHTA

[0122] Then m=6, |s1|=6, |s2|=6, T / H and H / T belong to two pairs of transposed characters, so t=(1+1) / 2=1

[0123] Substituting into the formula we get: J=0.944.

[0124] Based on the Jaro distance, the JW distance (Jaro-Winkler Distance) is defined as:

[0125]

[0126] Among them, d j is the Jaro distance; l is the largest common prefix of the string, which is no more than 4; p is a scaling factor used to adjust l to avoid d w If it exceeds 1, it is usually set to 0.1; b t It is the boost threshold (defined threshold). When the value exceeds this value, the Jaro distance is stimulated to be the JW distance. This value is generally set to 0.7.

[0127] Still taking the above two strings as an example, d j =0.944>0.7, l=3, p=0.1, substituting into the formula, we can calculate d w =0.961 (i.e. the calculated similarity value of the two strings).

[0128] (4) Euclidean distance

[0129] The Euclidean distance algorithm is defined in the vector space model and is calculated using the Euclidean distance formula. The Euclidean distance algorithm can reflect the absolute difference of individual numerical features, so it is more used in analyses that need to reflect differences in the numerical size of dimensions, such as using user behavior indicators to analyze the similarity or difference of user values.

[0130] For example: Message user name: s1=MARTHA

[0131] Deposit account name: s2=MARHTA

[0132] The Euclidean distance algorithm is used to calculate the similarity between the two strings, and the calculated value is 0.892.

[0133] According to an embodiment of the present disclosure, the pre-stored account name includes but is not limited to: a pre-stored account name in Chinese, a pre-stored account name in English, a pre-stored customer name in Chinese, and a pre-stored customer name in English.

[0134] Further, in Figure 2 , Figure 3 In the illustrated embodiment, the method for matching and checking the message account name and the pre-stored account name, and the method for matching and checking the converted message account name (including the message account name after one conversion and the reversed message account name) and the pre-stored account name are the same. Here, the method for matching and checking the message account name and the pre-stored account name is described.

[0135] The pre-stored user names include but are not limited to one or more of the above four types. The message user name and the pre-stored user name are matched and verified. The message user name and all types of pre-stored user names can be matched separately. As long as the message user name and any pre-stored user name can be accurately matched, the verification is passed.

[0136] According to the embodiments of the present disclosure, multiple categories of pre-stored user names are set. When the message user name and the pre-stored user name are matched and verified, only one of the matches needs to be met for the verification to pass, thereby improving the success rate of the verification and accelerating the business processing efficiency.

[0137] Figure 5 The block diagram of the user name verification device 500 according to the embodiment of the present disclosure is schematically shown.

[0138] The user name verification device 500 can be used to implement reference Figure 2 The method shown.

[0139] like Figure 5 As shown, the user name verification device 500 includes: an acquisition module 501 , a determination module 502 , a first verification module 503 and a second verification module 504 .

[0140] The acquisition module 501 is used to acquire the message account name and pre-stored account name of the pending transfer business, wherein the message account name is the account name provided by the transferor when executing the transfer business, and the pre-stored account name is the account name created by the payee when opening the account.

[0141] The determination module 502 is used to determine whether the message user name needs to be converted according to a preset user name checking rule.

[0142] Among them, the above-mentioned first verification module 503 is used to match and verify the message username and the pre-stored username when the message username does not need to be converted, and to convert the message username according to the preset conversion rules when the message username needs to be converted, and to match and verify the converted message username and the pre-stored username.

[0143] Among them, the above-mentioned second verification module 504 is used to perform a similarity verification on the message username and the pre-stored username when the message username does not need to be converted and cannot be matched, and to perform a similarity verification on the converted message username and the pre-stored username when the message username needs to be converted and the converted message username and the pre-stored username cannot match.

[0144] According to the embodiment of the present disclosure, through the determination module 502, according to the preset account name check rules, it is determined whether the message account name needs to be converted, and through the first verification module 503 and the second verification module 504, when the message account name before and after the conversion and the pre-stored account name are matched and checked and cannot match, the message account name before and after the conversion and the pre-stored account name are further similarity checked. Through the above technical means, the message account name can be verified without completely and accurately matching the pre-stored account name, so it at least partially overcomes the technical problem in the prior art that the verification can only be completed when there is an accurate match, resulting in relatively low business processing efficiency. Then, through the account name verification method of the embodiment of the present disclosure, the characteristics of the diversity of overseas account names can be met, the business processing efficiency is improved, and the impact on the success rate of transfer and customer satisfaction is improved.

[0145] According to an embodiment of the present disclosure, the above-mentioned determination module 502 includes an acquisition unit and a first determination unit.

[0146] The acquisition unit is used to acquire basic information of pending transfer business, wherein the basic information of pending transfer business includes the region where the payee's account is opened, the business message type, the business type, the account type and the customer type. The first determination unit is used to determine whether the message account name needs to be converted according to the basic information of pending transfer business and the preset account name checking rules.

[0147] According to an embodiment of the present disclosure, in the above-mentioned determination module 502, the preset account name checking rules include: the region where the payee's account is opened meets the preset conditions, and the business message type meets the preset conditions, and the business type meets the preset conditions, and the account type meets the preset conditions, and the customer type meets the preset conditions.

[0148] According to an embodiment of the present disclosure, the first verification module 503 includes a primary conversion unit, a primary verification unit and an account name reversal unit.

[0149] The primary conversion unit is used to convert the message user name according to the preset conversion rules when the message user name needs to be converted. The primary verification unit is used to match the message user name after the primary conversion with the pre-stored user name. The user name reversal unit is used to reverse the user name after the primary conversion of the message when the user name after the primary conversion does not match the pre-stored user name.

[0150] According to an embodiment of the present disclosure, in the above-mentioned one-time conversion unit, according to the preset conversion rules, the message username is converted once, including: when the message username contains spaces, the spaces in the message username are removed; and when the message username contains special characters, the special characters in the message username are removed; and when the message username is an abbreviation, the message username is converted into a full name.

[0151] According to an embodiment of the present disclosure, in the above-mentioned acquisition module 501, the pre-stored account name includes: a pre-stored account name in Chinese, a pre-stored account name in English, a pre-stored customer name in Chinese, and a pre-stored customer name in English.

[0152] According to an embodiment of the present disclosure, in the second verification module 504, the similarity verification between the message account name and the pre-stored account name includes:

[0153] Determine a similarity algorithm; use the similarity algorithm to calculate the similarity between the message account name and the pre-stored account name to obtain a similarity calculation value; and determine a verification result of the similarity verification between the message account name and the pre-stored account name based on the similarity calculation value and a preset threshold.

[0154] According to an embodiment of the present disclosure, the similarity algorithm includes one of the following: a cosine algorithm of a space vector, a Jaccard distance algorithm, a string similarity algorithm, and a Euclidean distance algorithm.

[0155] According to the embodiments of the present invention, any one or more of the modules, submodules, units, and subunits, or at least part of the functions of any one of them can be implemented in one module. According to the embodiments of the present invention, any one or more of the modules, submodules, units, and subunits can be split into multiple modules for implementation. According to the embodiments of the present invention, any one or more of the modules, submodules, units, and subunits can be at least partially implemented as hardware circuits, such as field programmable gate arrays (FPGAs), programmable logic arrays (PLAs), systems on chips, systems on substrates, systems on packages, application specific integrated circuits (ASICs), or can be implemented by hardware or firmware in any other reasonable way of integrating or packaging circuits, or can be implemented in any one of the three implementation methods of software, hardware, and firmware, or in any appropriate combination of any of them. Alternatively, according to the embodiments of the present invention, one or more of the modules, submodules, units, and subunits can be at least partially implemented as computer program modules, and when the computer program modules are run, the corresponding functions can be performed.

[0156] For example, any multiple of the acquisition module 501, the determination module 502, the first verification module 503, and the second verification module 504 can be combined in one module / unit / sub-unit for implementation, or any one of the modules / units / sub-units can be split into multiple modules / units / sub-units. Alternatively, at least part of the functions of one or more of these modules / units / sub-units can be combined with at least part of the functions of other modules / units / sub-units and implemented in one module / unit / sub-unit. According to an embodiment of the present disclosure, at least one of the acquisition module 501, the determination module 502, the first verification module 503, and the second verification module 504 can be at least partially implemented as a hardware circuit, such as a field programmable gate array (FPGA), a programmable logic array (PLA), a system on a chip, a system on a substrate, a system on a package, an application specific integrated circuit (ASIC), or can be implemented by hardware or firmware such as any other reasonable way of integrating or packaging the circuit, or by any one of the three implementation methods of software, hardware, and firmware, or by a suitable combination of any of them. Alternatively, at least one of the acquisition module 501, the determination module 502, the first verification module 503 and the second verification module 504 may be at least partially implemented as a computer program module, and when the computer program module is executed, a corresponding function may be executed.

[0157] Figure 6 A block diagram of an electronic device for implementing a user name verification method according to an embodiment of the present disclosure is schematically shown. Figure 6 The electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present disclosure.

[0158] like Figure 6 As shown, the electronic device 600 according to an embodiment of the present disclosure includes a processor 601, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 602 or a program loaded from a storage part 608 to a random access memory (RAM) 603. The processor 601 may include, for example, a general-purpose microprocessor (such as a CPU), an instruction set processor and / or a related chipset and / or a special-purpose microprocessor (for example, an application-specific integrated circuit (ASIC)), etc. The processor 601 may also include an onboard memory for caching purposes. The processor 601 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of the present disclosure.

[0159] In RAM 603, various programs and data required for the operation of electronic device 600 are stored. Processor 601, ROM 602 and RAM 603 are connected to each other via bus 604. Processor 601 performs various operations of the method flow according to the embodiment of the present disclosure by executing the program in ROM 602 and / or RAM 603. It should be noted that the program can also be stored in one or more memories other than ROM 602 and RAM 603. Processor 601 can also perform various operations of the method flow according to the embodiment of the present disclosure by executing the program stored in the one or more memories.

[0160] According to an embodiment of the present disclosure, the electronic device 600 may further include an input / output, i.e., an I / O interface 605, which is also connected to the bus 604. The system may further include one or more of the following components connected to the I / O interface 605: an input portion 606 including a keyboard, a mouse, etc.; an output portion 607 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage portion 608 including a hard disk, etc.; and a communication portion 609 including a network interface card such as a LAN card, a modem, etc. The communication portion 609 performs communication processing via a network such as the Internet. A drive 610 is also connected to the I / O interface 605 as needed. A removable medium 611, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 610 as needed, so that a computer program read therefrom is installed into the storage portion 608 as needed.

[0161] According to an embodiment of the present disclosure, the method flow according to an embodiment of the present disclosure can be implemented as a computer software program. For example, an embodiment of the present disclosure includes a computer program product, which includes a computer program carried on a computer-readable storage medium, and the computer program contains a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 609, and / or installed from the removable medium 611. When the computer program is executed by the processor 601, the above-mentioned functions defined in the system of the embodiment of the present disclosure are executed. According to an embodiment of the present disclosure, the system, equipment, device, module, unit, etc. described above can be implemented by a computer program module.

[0162] The present disclosure also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments; or may exist independently without being assembled into the device / apparatus / system. The above computer-readable storage medium carries one or more programs, and when the above one or more programs are executed, the method according to the embodiment of the present disclosure is implemented.

[0163] According to an embodiment of the present disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium. For example, it may include, but is not limited to: a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In the present disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program that may be used by or in combination with an instruction execution system, apparatus, or device.

[0164] For example, according to an embodiment of the present disclosure, the computer-readable storage medium may include the ROM 602 and / or the RAM 603 described above and / or one or more memories other than the ROM 602 and the RAM 603 .

[0165] The embodiments of the present disclosure also include a computer program product, which includes a computer program, and the computer program contains a program code for executing the method provided by the embodiments of the present disclosure. When the computer program product runs on an electronic device, the program code is used to enable the electronic device to implement the user name verification method provided by the embodiments of the present disclosure.

[0166] When the computer program is executed by the processor 601, the above functions defined in the system / device of the embodiment of the present disclosure are executed. According to the embodiment of the present disclosure, the system, device, module, unit, etc. described above can be implemented by a computer program module.

[0167] In one embodiment, the computer program may rely on tangible storage media such as optical storage devices, magnetic storage devices, etc. In another embodiment, the computer program may also be transmitted and distributed in the form of signals on a network medium, and downloaded and installed through the communication part 609, and / or installed from a removable medium 611. The program code contained in the computer program may be transmitted using any appropriate network medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.

[0168] According to an embodiment of the present disclosure, the program code for executing the computer program provided by the embodiment of the present disclosure can be written in any combination of one or more programming languages. Specifically, these computing programs can be implemented using high-level process and / or object-oriented programming languages, and / or assembly / machine languages. Programming languages ​​include, but are not limited to, Java, C++, python, "C" language or similar programming languages. The program code can be executed entirely on the user computing device, partially on the user device, partially on the remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device can be connected to the user computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computing device (for example, using an Internet service provider to connect through the Internet).

[0169] The flowcharts and block diagrams in the accompanying drawings illustrate the possible architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each box in the flowchart or block diagram may represent a module, a program segment, or a part of a code, and the above-mentioned module, program segment, or a part of the code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box may also occur in an order different from that marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flowchart, and the combination of boxes in the block diagram or flowchart, can be implemented with a dedicated hardware-based system that performs the specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions. It can be understood by those skilled in the art that the features recorded in the various embodiments and / or claims of the present disclosure can be combined and / or combined in a variety of ways, even if such a combination or combination is not explicitly recorded in the present disclosure. In particular, without departing from the spirit and teaching of the present disclosure, the features described in the various embodiments and / or claims of the present disclosure may be combined and / or combined in a variety of ways. All of these combinations and / or combinations fall within the scope of the present disclosure.

[0170] The embodiments of the present disclosure are described above. However, these embodiments are only for illustrative purposes and are not intended to limit the scope of the present disclosure. Although the embodiments are described above separately, this does not mean that the measures in the various embodiments cannot be used in combination to advantage. The scope of the present disclosure is defined by the attached claims and their equivalents. Without departing from the scope of the present disclosure, those skilled in the art may make a variety of substitutions and modifications, which should all fall within the scope of the present disclosure.

Claims

1. A method for verifying an account name, comprising: Obtaining a message account name and a pre-deposited account name of a pending transfer service, wherein the message account name is the account name provided by the transferor when executing the transfer service, and the pre-deposited account name is the account name created by the payee when opening an account; Determine whether the message account name needs to be converted according to a preset account name checking rule; When the message user name does not need to be converted, the message user name and the pre-stored user name are matched and checked; when the message user name needs to be converted, the message user name is converted according to a preset conversion rule, and the converted message user name and the pre-stored user name are matched and checked; When the message username does not need to be converted and cannot be matched, the message username and the pre-stored username are checked for similarity; and when the message username needs to be converted and the converted message username and the pre-stored username cannot be matched, the converted message username and the pre-stored username are checked for similarity; If the similarity is within the preset threshold, the verification is passed and the account is recorded; If the similarity is not within the preset threshold, the verification fails and the account is rejected.

2. The method according to claim 1, wherein: The determining whether the message username needs to be converted according to the preset username checking rule includes: Obtaining basic information of pending transfer business, wherein the basic information of pending transfer business includes the payee's account opening region, business message type, business type, account type and customer type; According to the basic information of the pending transfer business and the preset account name checking rules, it is determined whether the account name in the message needs to be converted.

3. The method according to claim 2, wherein: The preset account name checking rule includes: the payee account opening region meets the preset conditions, and the business message type meets the preset conditions, and the business type meets the preset conditions, and the account type meets the preset conditions, and the customer type meets the preset conditions.

4. The method according to claim 1, wherein: In the case where the message user name needs to be converted, converting the message user name according to a preset conversion rule includes: When the message user name needs to be converted, convert the message user name according to a preset conversion rule; Performing a match check between the converted message account name and the pre-stored account name; In the case that the message account name after the first conversion cannot match the pre-stored account name, the account name of the message after the first conversion is reversed.

5. The method according to claim 4, wherein: The converting of the message user name according to the preset conversion rule includes: If the message user name contains a space, remove the space in the message user name; If the message user name contains special characters, remove the special characters in the message user name; and When the message user name is an abbreviation, the message user name is converted into a full name.

6. The method according to claim 1, wherein: The pre-deposited account name includes: a pre-deposited account name in Chinese, a pre-deposited account name in English, a pre-deposited customer name in Chinese and a pre-deposited customer name in English.

7. The method according to claim 1, wherein: Performing a similarity check on the message account name and the pre-stored account name, including: Determine the similarity algorithm; Calculate the similarity between the message account name and the pre-stored account name using the similarity algorithm to obtain a similarity calculation value; A verification result of performing a similarity check between the message account name and the pre-stored account name is determined according to the similarity calculation value and a preset threshold value.

8. The method according to claim 7, wherein: The similarity algorithm includes one of the following: a cosine algorithm of a space vector, a Jaccard distance algorithm, a string similarity algorithm, and a Euclidean distance algorithm.

9. A user name verification device, comprising: An acquisition module, used to acquire a message account name and a pre-deposited account name of a pending transfer service, wherein the message account name is the account name provided by the transferor when executing the transfer service, and the pre-deposited account name is the account name created by the payee when opening an account; A determination module, used to determine whether the message account name needs to be converted according to a preset account name checking rule; A first verification module is used to perform a matching verification on the message account name and the pre-stored account name when the message account name does not need to be converted, and to convert the message account name according to a preset conversion rule when the message account name needs to be converted, and to perform a matching verification on the converted message account name and the pre-stored account name; A second verification module is used to perform a similarity verification on the message account name and the pre-stored account name when the message account name does not need to be converted and cannot be matched, and to perform a similarity verification on the converted message account name and the pre-stored account name when the message account name needs to be converted and the converted message account name and the pre-stored account name cannot match; If the similarity is within the preset threshold, the verification is passed and the account is recorded; If the similarity is not within the preset threshold, the verification fails and the account is rejected.

10. An electronic device, comprising: one or more processors; a memory for storing one or more programs, Wherein, when the one or more programs are executed by the one or more processors, The one or more processors are caused to implement the method of any one of claims 1 to 8.

11. A computer-readable storage medium having executable instructions stored thereon, which, when executed by a processor, causes the processor to implement the method according to any one of claims 1 to 8.

12. A computer program product, comprising computer executable instructions, which are used to implement the method of any one of claims 1 to 8 when executed.

Images