WO2021088534A1 - 收款账户的验证方法及其装置 - Google Patents

收款账户的验证方法及其装置 Download PDF

Info

Publication number
WO2021088534A1
WO2021088534A1 PCT/CN2020/116420 CN2020116420W WO2021088534A1 WO 2021088534 A1 WO2021088534 A1 WO 2021088534A1 CN 2020116420 W CN2020116420 W CN 2020116420W WO 2021088534 A1 WO2021088534 A1 WO 2021088534A1
Authority
WO
WIPO (PCT)
Prior art keywords
account
complete
verified
module
user
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2020/116420
Other languages
English (en)
French (fr)
Inventor
许吉
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Alipay Hangzhou Information Technology Co Ltd
Original Assignee
Alipay Hangzhou Information Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Alipay Hangzhou Information Technology Co Ltd filed Critical Alipay Hangzhou Information Technology Co Ltd
Publication of WO2021088534A1 publication Critical patent/WO2021088534A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G06Q20/401—Transaction verification
    • G06Q20/4014—Identity check for transactions

Definitions

  • This specification relates to the field of data processing technology, and in particular to a verification method and device for a collection account.
  • the embodiments of the present specification aim to solve one of the technical problems in the related technology at least to a certain extent.
  • the first purpose of the embodiments of this specification is to propose a method for verifying the receiving account, which realizes that the payer does not need to manually enter the complete account number of the receiving account, but only needs to fill in the missing account number corresponding to the receiving account. This not only reduces the length of the characters entered by the payer, reduces the possibility of error, but also enables the payer to verify the payee’s account before paying, so that the payer can smoothly transfer the payment to the payee’s account.
  • the second purpose of the embodiments of this specification is to provide a verification device for a collection account.
  • the third purpose of the embodiments of this specification is to provide a computer device.
  • the fourth purpose of the embodiments of this specification is to provide a non-transitory computer-readable storage medium.
  • the first aspect of the embodiments of this specification proposes a method for verifying a receiving account, which includes: obtaining a complete account corresponding to the receiving account to be verified; hiding at least one character in the complete account to generate all The missing account number corresponding to the receiving account to be verified; the missing account number is displayed, and the user is prompted to complete the at least one character; the completed account number is compared with the complete account number; according to the comparison As a result, the verification of the receiving account to be verified is completed.
  • the payer in the embodiment of this specification does not need to manually enter the complete account number of the receiving account, but only needs to fill in the missing account number corresponding to the receiving account. Compare the completed account number with the complete account number of the receiving account to verify the receiving account.
  • the method for verifying a receiving account in the embodiment of this specification also has the following additional technical features: optionally, at least one character in the complete account is hidden to generate the receiving account to be verified
  • the corresponding missing account includes: determining the length of the complete account; determining the position corresponding to the at least one character to be hidden according to the length of the complete account; The characters are hidden to generate the missing account number corresponding to the receiving account to be verified.
  • the comparing the completed account number with the complete account number includes: sequentially comparing each character in the completed account number with the character at the corresponding position in the complete account number. Make comparisons.
  • the completing the verification of the receiving account to be verified according to the comparison result includes: in the case that the completed account is the same as the complete account, allowing the user to report to the Payment of the receiving account to be verified; in the case that the completed account is not the same as the complete account, the user is prompted that the verification has failed.
  • the method further includes: counting the number of times the user verification fails; in the case that the number of times the user verification fails exceeds a preset threshold, prohibiting the user for a preset time period Continue verification within.
  • the method further includes: obtaining the account information keywords input by the user; screening out candidate accounts related to the account information keywords, and displaying them ; According to the user's selection of the candidate account, determine the to-be-verified collection account.
  • the second aspect of the embodiments of this specification proposes a verification device for a receiving account, which includes: a first obtaining module for obtaining a complete account corresponding to the receiving account to be verified; a hiding module for storing the information in the complete account At least one character is hidden to generate a missing account number corresponding to the receiving account to be verified; a display module is used to display the missing account number; a prompt module is used to prompt the user to complete the at least one character; The comparison module is used to compare the completed account with the complete account; the verification module is used to complete the verification of the to-be-verified receiving account according to the comparison result.
  • the verification device for the payment account in the embodiment of the present specification also has the following additional technical features:
  • the hiding module includes: a first determining sub-module for obtaining the length of the complete account; 2. A determining sub-module, which is used to determine the position corresponding to the at least one character to be hidden according to the length of the complete account; a hiding sub-module, which is used to hide the character at the position in the complete account , To generate the vacant account number corresponding to the receiving account to be verified.
  • the comparison module is specifically configured to sequentially compare each character in the completed account with the character at the corresponding position in the complete account.
  • the verification module includes: an allow sub-module, configured to allow the user to pay to the receiving account to be verified when the completed account is the same as the full account; prompt The sub-module is used to prompt the user that the verification fails when the completed account is not the same as the complete account.
  • the verification module further includes: a statistics sub-module for counting the number of times the user verification fails; a prohibition sub-module for prohibiting when the number of user verification failures exceeds a preset threshold The user continues to verify within the preset time period.
  • the device further includes: a second acquiring module, configured to acquire account information keywords input by the user; a screening module, configured to filter candidate accounts related to the account information keywords, and display them
  • the determination module is used to determine the receiving account to be verified according to the user's selection of the candidate account.
  • the third aspect of the embodiments of this specification proposes a computer device, including a memory and a processor; the memory stores a computer program that can be run by the processor; when the processor runs the computer program, it executes the method as described above.
  • the fourth aspect of the embodiments of this specification proposes a non-transitory computer-readable storage medium on which a computer program is stored, and when the computer program is executed by a processor, the verification of the collection account as described in the foregoing method embodiment is implemented. method.
  • FIG. 1 is a schematic flowchart of a method for verifying a collection account proposed in an embodiment of this specification
  • FIG. 2 is a schematic flowchart of another method for verifying a collection account proposed in an embodiment of this specification
  • FIG. 3 is a schematic flowchart of another method for verifying a collection account proposed in an embodiment of this specification
  • FIG. 4 is a schematic flow diagram of another method for verifying a payment account according to an embodiment of the specification
  • FIGS 5a-5g are schematic diagrams of the technical effects of the method for verifying payment accounts proposed in the embodiments of this specification.
  • FIG. 6 is a schematic structural diagram of a verification device for a collection account proposed in an embodiment of this specification.
  • FIG. 7 is a schematic structural diagram of another verification device for a collection account proposed in an embodiment of this specification.
  • FIG. 8 is a schematic structural diagram of another device for verifying a payment account according to an embodiment of the specification.
  • Fig. 9 is a schematic structural diagram of another device for verifying a payment account according to an embodiment of the specification.
  • each account corresponds to a unique account number, which is used to identify the account.
  • the payee Before receiving the payment, the payee provides the account number corresponding to the designated receiving account to the transferer.
  • the transfer party needs to enter the account number corresponding to the receiving account, so that the payment system can determine the corresponding receiving account, and then transfer the payment to the receiving account to complete the payment.
  • the payment may not be smoothly transferred to the payee account designated by the payee, resulting in payment failure.
  • the embodiment of this specification proposes a method for verifying a receiving account.
  • the payer does not need to manually enter the complete account number of the receiving account, but only needs to fill in the missing account number corresponding to the receiving account. Compare the completed account number with the complete account number of the receiving account to verify the receiving account.
  • Fig. 1 is a schematic flowchart of a method for verifying a payment account proposed in an embodiment of this specification. As shown in Fig. 1, the method includes step S101 to step S109.
  • Step S101 Obtain a complete account corresponding to the receiving account to be verified.
  • the complete account number corresponding to the receiving account to be verified is a string of characters used to uniquely identify the receiving account to be verified in the payment system.
  • the method for verifying the receiving account does not rely on the complete account entered by the user to directly determine the receiving account, but first determines the receiving account through other methods as the account to be verified. The complete account number corresponding to the receiving account is then obtained, and the receiving account is verified by the complete account, thereby ensuring that the receiving account that is successfully verified is the receiving account designated by the receiving party.
  • the receiving account to be verified has a one-to-one correspondence with its corresponding complete account.
  • the corresponding receiving account can be determined based on the complete account, or the corresponding complete account can also be determined based on the receiving account.
  • step S101 before obtaining the complete account number corresponding to the receiving account to be verified, step S11 to step S15 are further included.
  • Step S11 Acquire the account information keywords input by the user.
  • step S13 candidate accounts related to the account information keywords are screened out and displayed.
  • account information keywords to filter all accounts in the system can be implemented by using any existing keyword retrieval technology, which is not limited in the embodiment of this specification.
  • One possible implementation is to arrange the candidate accounts according to the degree of correlation between the account information of the candidate accounts and the account information keywords in descending order.
  • Another possible implementation is to arrange the candidate accounts in descending order according to the number of times the candidate accounts have been queried within a preset time.
  • the account information of the candidate accounts can also be displayed together.
  • Step S15 according to the user's selection of the candidate account, determine the receiving account to be verified.
  • the user can determine the receiving account to be verified by checking the corresponding account information.
  • step S103 at least one character in the complete account number is hidden to generate a missing account number corresponding to the receiving account to be verified.
  • step S105 the missing account number is displayed, and the user is prompted to complete at least one character.
  • the first aspect is that the user must fill in the hidden characters to verify the receiving account and cannot be skipped.
  • the user only needs to fill in the hidden part of the number, which is relatively simple and not easy to make mistakes.
  • the displayed account number is incomplete, the third party cannot directly obtain the complete account number of the receiving account to be verified.
  • the receiving account to be verified is the receiving account designated by the payee, then the user can complete the missing account number into a complete account based on the account number provided by the payee.
  • the account number provided by the payee is different from the full account number of the receiving account to be verified, and the following possible situations will occur.
  • the user finds that in the displayed missing account number, the characters that are not hidden are different from the characters in the corresponding position of the account number provided by the payee, and the user realizes that the receiving account to be verified is not the payee designated by the payee. Account, you can directly terminate the verification of the receiving account to be verified.
  • the user does not check the characters displayed in the missing account number one by one, and directly completes the missing account number according to the account number provided by the payee, and the payment system needs to check the completed account number and the complete account number. Make comparisons.
  • the user has carefully compared the missing account number with the account number provided by the payee, but no difference is found, that is, the characters that are different between the two accounts have just been hidden, and payment is required.
  • the system compares the completed account with the complete account.
  • step S107 the completed account is compared with the complete account.
  • the complete account is a string of characters
  • the completed account is also a string of characters.
  • one possible implementation is to sequentially compare each character in the completed account with the character at the corresponding position in the complete account.
  • Another possible implementation is to calculate the hash value of the completed account and the hash value of the complete account separately, and compare the sizes of the two hash values.
  • Step S109 According to the comparison result, the verification of the receiving account to be verified is completed.
  • the user completes the missing account number. If the completed account number is exactly the same as the full account number, it means that the receiving account to be verified is the receiving account designated by the payee. If the completed account number is different from the full account number, it may be that the user made a mistake during the completion, resulting in the wrong character input, or the account number provided by the payee is originally different from the full account number.
  • the method for verifying a receiving account obtains a complete account corresponding to the receiving account to be verified. Hide at least one character in the complete account number to generate a missing account number corresponding to the receiving account to be verified. Display the missing account and prompt the user to complete multiple characters. The completed account is compared with the complete account, and the verification of the receiving account to be verified is completed according to the comparison result.
  • the payer does not need to manually enter the complete account number of the receiving account, but only needs to fill in the missing account number corresponding to the receiving account, which reduces the length of characters entered by the payer, reduces the possibility of error, and makes the payer Before paying the fee, the account of the payee can be verified, so that the payer can smoothly transfer the payment to the account of the payee.
  • FIG. 2 is an embodiment of the specification.
  • Step S201 Obtain a complete account corresponding to the receiving account to be verified.
  • Step S203 Determine the length of the complete account.
  • Step S205 Determine the position corresponding to at least one character to be hidden according to the length of the complete account.
  • step S207 the characters in the position in the complete account are hidden to generate the vacant account corresponding to the receiving account to be verified.
  • step S209 the missing account number is displayed, and the user is prompted to complete at least one character.
  • step S211 the completed account is compared with the complete account.
  • Step S213 According to the comparison result, the verification of the receiving account to be verified is completed.
  • step S101 to step S109 are also applicable to the method steps in the embodiment of this specification, and will not be repeated here.
  • the embodiment of this specification also proposes another method for verifying the receiving account, as shown in Figure 3 A schematic flow diagram of another method for verifying a receiving account proposed in the embodiment of this specification. As shown in Fig. 3, the method includes step S301 to step S311.
  • Step S301 Obtain a complete account corresponding to the receiving account to be verified.
  • step S303 at least one character in the complete account number is hidden to generate a missing account number corresponding to the receiving account to be verified.
  • step S305 the missing account number is displayed, and the user is prompted to complete at least one character.
  • step S307 the completed account is compared with the complete account.
  • step S309 when the completed account is the same as the complete account, the user is allowed to pay to the receiving account to be verified.
  • step S311 if the completed account is not the same as the complete account, the user is prompted that the verification has failed.
  • the completed account is not the same as the full account, it may be that the user made a mistake when completing the completion, resulting in the wrong character input, or it may be that the account number provided by the payee is different from the full account number, no matter which one it is. In either case, the user should be notified that the authentication has failed.
  • the user finds that it was a mistake in input that caused the wrong character to be entered, the user can re-complete the missing account. If the user finds that there is no error in the input, it means that the account number provided by the payee is different from the full account number, and it is necessary to re-determine whether the receiving account to be verified is the receiving account designated by the payee.
  • one possible implementation is that, after prompting the user to verify the failure, it also includes: counting the number of times the user has failed to verify. If the number of failures exceeds the preset threshold, the user is prohibited from continuing to verify within the preset time period. For example, if a user fails to verify three times for the same receiving account in the same day, the user is prohibited from continuing to verify within one hour.
  • step S101 to step S109 are also applicable to the method steps in the embodiment of this specification, and will not be repeated here.
  • FIG. 4 is another method of verifying the receiving account proposed in the embodiment of this specification.
  • Step S401 Acquire the account information keywords input by the user.
  • step S403 candidate accounts related to the account information keywords are screened out and displayed.
  • Step S405 According to the user's selection of the candidate account, the receiving account to be verified is determined.
  • Step S407 Obtain a complete account corresponding to the receiving account to be verified.
  • Step S409 Determine the length of the complete account.
  • Step S411 Determine the position corresponding to at least one character to be hidden according to the length of the complete account.
  • step S413 the characters in the position in the complete account number are hidden to generate a missing account number corresponding to the receiving account to be verified.
  • step S415 the missing account number is displayed, and the user is prompted to complete at least one character.
  • step S417 each character in the completed account is sequentially compared with the character in the corresponding position in the complete account.
  • step S419 in the case that the completed account is the same as the complete account, the user is allowed to pay to the receiving account to be verified.
  • step S421 in the case that the completed account is not the same as the complete account, the user is prompted that the verification has failed.
  • Step S423 Count the number of user authentication failures.
  • step S425 when the number of user verification failures exceeds the preset threshold, the user is forbidden to continue verification within the preset time period.
  • the receiving account to be verified is determined through the account information keywords, and the verification of the account information of the receiving account to be verified is completed.
  • the user completes the missing account number to compare the complete account of the receiving account to be verified, and then complete the verification of the receiving account to be verified.
  • the overseas institution When international students pay fees to the collection account designated by the overseas institution, the overseas institution usually informs the international student of the account number corresponding to the collection account, as well as the name of the recipient and other information. Therefore, the method for verifying the receiving account provided in the embodiment of this specification can be used to ensure that the fee is transferred to the designated receiving account smoothly, and to avoid the failure of the transfer and causing trouble to the study and life of the international student.
  • Figures 5a-5g are schematic diagrams of the technical effects of the method for verifying payment accounts proposed in the embodiments of this specification.
  • an international student needs to transfer money to the receiving account designated by Cardfidd University, he can first enter the name of the payee Cardfidd University.
  • the system retrieves the receiving account related to Cardfidd University, and finds the receiving account corresponding to Cardfidd University, as well as the account information of the receiving account, and displays it to the international students.
  • International students can use the account information to preliminarily judge whether the receiving account is the receiving account designated by Cardfidd University.
  • the system hides part of the numbers in the complete account corresponding to the receiving account, generates and displays the missing account, and prompts the international student to complete the account.
  • International students can fill in the vacant numbers in the interface shown in Figure 5c according to the account number provided by Cardfidd University, and can also judge whether the receiving account is the account designated by the payee through the number not hidden by the system.
  • the system compares the completed account number with the complete account number of the receiving account.
  • the receiving account is a receiving account designated by overseas colleges and universities, and international students are allowed to perform transfer operations.
  • FIG. 6 is a schematic structural diagram of the verification device for a collection account proposed in the embodiment of this specification. As shown in FIG. 6, the device includes: a first acquisition module 510, a hiding module 520, a display module 530, a prompt module 540, a comparison module 550, and a verification module 560.
  • the first obtaining module 510 is configured to obtain a complete account corresponding to the receiving account to be verified.
  • the hiding module 520 is configured to hide at least one character in the complete account number to generate a missing account number corresponding to the receiving account to be verified.
  • the display module 530 is used to display the missing account.
  • the prompt module 540 is used to prompt the user to complete at least one character.
  • the comparison module 550 is used to compare the completed account with the complete account.
  • the verification module 560 is configured to complete the verification of the receiving account to be verified according to the comparison result.
  • the device further includes: a second obtaining module configured to obtain the account information keywords input by the user.
  • the screening module is used to screen out candidate accounts related to account information keywords and display them.
  • the determining module is used to determine the receiving account to be verified according to the user's selection of the candidate account.
  • the comparison module 550 is specifically used to sequentially compare each character in the completed account with the corresponding position in the complete account. Characters are compared.
  • a verification device for a collection account is proposed in the embodiment of this specification.
  • the completed account is compared with the complete account, and the verification of the receiving account to be verified is completed according to the comparison result.
  • the payer does not need to manually enter the complete account number of the receiving account, but only needs to fill in the missing account number corresponding to the receiving account, which reduces the length of characters entered by the payer, reduces the possibility of error, and makes the payer Before paying the fee, the account of the payee can be verified, so that the payer can smoothly transfer the payment to the account of the payee.
  • FIG. 7 is a schematic structural diagram of another device for verifying payment accounts proposed in the embodiment of this specification. As shown in FIG. 7, the device includes: a first acquisition module 610, a hiding module 620, a display module 630, a prompt module 640, a comparison module 650, and a verification module 660.
  • the first obtaining module 610 is configured to obtain a complete account corresponding to the receiving account to be verified.
  • the hiding module 620 is configured to hide at least one character in the complete account number to generate a missing account number corresponding to the receiving account to be verified.
  • the display module 630 is used to display the missing account number.
  • the prompt module 640 is used to prompt the user to complete at least one character.
  • the comparison module 650 is used to compare the completed account with the complete account.
  • the verification module 660 is configured to complete the verification of the receiving account to be verified according to the comparison result.
  • the hiding module 620 includes: a first determining sub-module 621, configured to obtain the length of the complete account.
  • the second determining sub-module 622 is configured to determine the position corresponding to at least one character to be hidden according to the length of the complete account.
  • the hiding sub-module 623 is used to hide the characters in the position in the complete account to generate a missing account corresponding to the receiving account to be verified.
  • FIG. 8 is a schematic structural diagram of another device for verifying payment accounts proposed in the embodiment of this specification. As shown in FIG. 8, the device includes: a first acquisition module 710, a hiding module 720, a display module 730, a prompt module 740, a comparison module 750, and a verification module 760.
  • the first obtaining module 710 is configured to obtain a complete account corresponding to the receiving account to be verified.
  • the hiding module 720 is configured to hide at least one character in the complete account number to generate a missing account number corresponding to the receiving account to be verified.
  • the display module 730 is used to display the missing account.
  • the prompt module 740 is used to prompt the user to complete at least one character.
  • the comparison module 750 is used to compare the completed account with the complete account.
  • the verification module 760 is used to complete the verification of the receiving account to be verified according to the comparison result.
  • the verification module 760 includes: an allow sub-module 761, which is used to allow the user to pay to the receiving account to be verified when the completed account is the same as the full account.
  • the prompting sub-module 762 is used to prompt the user that the verification fails when the completed account is not the same as the full account.
  • the verification module 760 further includes a statistics sub-module for counting the number of user verification failures.
  • the prohibition sub-module is used to prohibit the user from continuing the verification within the preset time period when the number of user verification failures exceeds the preset threshold.
  • FIG. 9 is a schematic structural diagram of another device for verifying payment accounts proposed in the embodiment of this specification.
  • the device includes: a second acquisition module 810, a screening module 820, a determination module 830, a first acquisition module 840, a hiding module 850, a display module 860, a prompt module 870, a comparison module 880, and a verification module 890 .
  • the second acquiring module 810 is configured to acquire the account information keywords input by the user.
  • the screening module 820 is used to screen out candidate accounts related to account information keywords and display them.
  • the determining module 830 is configured to determine the receiving account to be verified according to the user's selection of the candidate account.
  • the first obtaining module 840 is configured to obtain a complete account corresponding to the receiving account to be verified.
  • the hiding module 850 is configured to hide at least one character in the complete account number to generate a missing account number corresponding to the receiving account to be verified.
  • the display module 860 is used to display the missing account.
  • the prompt module 870 is used to prompt the user to complete at least one character.
  • the comparison module 880 is used to sequentially compare each character in the completed account with the character at the corresponding position in the complete account.
  • the verification module 890 is configured to complete the verification of the receiving account to be verified according to the comparison result.
  • the hiding module 850 includes: a first determining sub-module 851, which is used to obtain the length of the complete account.
  • the second determining sub-module 852 is used to determine the position corresponding to at least one character to be hidden according to the length of the complete account.
  • the hiding sub-module 853 is used to hide the characters in the position in the complete account to generate a missing account corresponding to the receiving account to be verified.
  • the verification module 890 includes an permission sub-module 891, which is used to allow the user to pay to the receiving account to be verified when the completed account is the same as the full account.
  • the prompting sub-module 892 is used to prompt the user that the verification fails when the completed account is not the same as the full account.
  • the statistics sub-module 893 is used to count the number of user verification failures.
  • the prohibition sub-module 894 is configured to prohibit the user from continuing to perform verification within a preset time period when the number of user verification failures exceeds a preset threshold.
  • the receiving account to be verified is determined through the account information keywords, and the verification of the account information of the receiving account to be verified is completed.
  • the user completes the missing account number to compare the complete account of the receiving account to be verified, and then complete the verification of the receiving account to be verified.
  • the embodiment of this specification also proposes a computer device, including a memory and a processor; the memory stores a computer program that can be run by the processor; when the processor runs the computer program, it executes the same as in the foregoing method embodiment.
  • the verification method of the receiving account is also proposed.
  • the embodiment also proposes a non-transitory computer-readable storage medium on which a computer program is stored.
  • the computer program is executed by a processor, the method for verifying a collection account as in the foregoing method embodiment is implemented.
  • first and second are only used for descriptive purposes, and cannot be understood as indicating or implying relative importance or implicitly indicating the number of indicated technical features.
  • the characteristics defined with “first” and “second” may explicitly or implicitly include at least one of the characteristics.
  • a plurality of means at least two, such as two, three, etc., unless specifically defined otherwise.
  • the terms “installed”, “connected”, “connected”, “fixed” and other terms should be understood in a broad sense.
  • it may be a fixed connection or an optional Disassembled connection, or integrated; it can be mechanical connection or electrical connection; it can be directly connected, or indirectly connected through an intermediate medium, it can be the internal communication of two components or the interaction relationship between two components, unless otherwise There are clear limits.
  • the specific meanings of the above-mentioned terms in the embodiments of this specification can be understood according to specific circumstances.
  • the first feature "on” or “under” the second feature may be in direct contact with the first and second features, or the first and second features pass through the middle. Indirect media contact.
  • the "above”, “above” and “above” of the first feature on the second feature may mean that the first feature is directly above or diagonally above the second feature, or it simply means that the level of the first feature is higher than the second feature.
  • the “below”, “below” and “below” of the second feature of the first feature may be that the first feature is directly below or obliquely below the second feature, or it simply means that the level of the first feature is smaller than the second feature.

Landscapes

  • Business, Economics & Management (AREA)
  • Engineering & Computer Science (AREA)
  • Accounting & Taxation (AREA)
  • Computer Security & Cryptography (AREA)
  • Finance (AREA)
  • Strategic Management (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Abstract

本说明书实施例公开了一种收款账户的验证方法及其装置。其中，方法包括：获取待验证收款账户对应的完整账号。将完整账号中的至少一个字符进行隐藏，以生成待验证收款账户对应的缺位账号。将缺位账号进行显示，并提示用户补全多个字符。将补全后的账号与完整账号进行比对，根据比对结果，完成对待验证收款账户的验证。由此，实现了缴费方无需手动输入收款账户的完整账号，只需补全收款账户对应的缺位账号，既减少了缴费方输入字符的长度，降低了出错可能性，又使得缴费方在缴费之前，能够对收款方的账号进行验证，让缴费方顺利将缴费款项转入收款方的账户。

Description

收款账户的验证方法及其装置 技术领域
本说明书涉及数据处理技术领域，尤其涉及一种收款账户的验证方法及其装置。
背景技术
随着信息技术的发展，人们越来越多地采用在线缴费的方式进行缴费。相关技术中，在缴费时，缴费方需要输入收款方的账号，才能将缴费款项转入收款方的账户。但是，一旦缴费方输错了收款方的账号，则可能导致缴费款项无法顺利转入收款方的账户，导致缴费失败。
因此，亟需一种收款账户的验证方法，让缴费方能够对收款账户进行验证。
发明内容
本说明书实施例旨在至少在一定程度上解决相关技术中的技术问题之一。
为此，本说明书实施例的第一个目的在于提出一种收款账户的验证方法，实现了缴费方无需手动输入收款账户的完整账号，只需补全收款账户对应的缺位账号，既减少了缴费方输入字符的长度，降低了出错可能性，又使得缴费方在缴费之前，能够对收款方的账号进行验证，让缴费方顺利将缴费款项转入收款方的账户。
本说明书实施例的第二个目的在于提出一种收款账户的验证装置。
本说明书实施例的第三个目的在于提出一种计算机设备。
本说明书实施例的第四个目的在于提出一种非临时性计算机可读存储介质。
为达上述目的，本说明书实施例第一方面提出了收款账户的验证方法，包括：获取待验证收款账户对应的完整账号；将所述完整账号中的至少一个字符进行隐藏，以生成所述待验证收款账户对应的缺位账号；将所述缺位账号进行显示，并提示用户补全所述至少一个字符；将补全后的账号与所述完整账号进行比对；根据比对结果，完成对所述待验证收款账户的验证。
和现有技术相比，本说明书实施例缴费方无需手动输入收款账户的完整账号，只需补全收款账户对应的缺位账号。将补全后的账号与收款账户的完整账号进行比对，以 实现对收款账户的验证。
另外，本说明书实施例的收款账户的验证方法，还具有如下附加的技术特征：可选地，所述将所述完整账号中的至少一个字符进行隐藏，以生成所述待验证收款账户对应的缺位账号，包括：确定所述完整账号的长度；根据所述完整账号的长度，确定要隐藏的所述至少一个字符所对应的位置；将所述完整账号中的所述位置上的字符进行隐藏，以生成所述待验证收款账户对应的所述缺位账号。
可选地，所述将补全后的账号与所述完整账号进行比对，包括：依次将所述补全后的账号中的每一位字符，分别与所述完整账号中对应位置的字符进行比对。
可选地，所述根据比对结果，完成对所述待验证收款账户的验证，包括：在所述补全后的账号与所述完整账号相同的情况下，允许所述用户向所述待验证收款账户缴费；在所述补全后的账号与所述完整账号不相同的情况下，提示所述用户验证失败。
可选地，在所述提示用户验证失败之后，还包括：统计所述用户验证失败的次数；在所述用户验证失败的次数超过预设阈值的情况下，禁止所述用户在预设时间段内继续进行验证。
可选地，在所述获取待验证收款账户对应的完整账号之前，还包括：获取所述用户输入的账户信息关键字；筛选出与所述账户信息关键字相关的候选账户，并进行显示；根据所述用户对所述候选账户的选择，确定所述待验证收款账户。
本说明书实施例第二方面提出了一种收款账户的验证装置，包括：第一获取模块，用于获取待验证收款账户对应的完整账号；隐藏模块，用于将所述完整账号中的至少一个字符进行隐藏，以生成所述待验证收款账户对应的缺位账号；显示模块，用于将所述缺位账号进行显示；提示模块，用于提示用户补全所述至少一个字符；比对模块，用于将补全后的账号与所述完整账号进行比对；验证模块，用于根据比对结果，完成对所述待验证收款账户的验证。
另外，本说明书实施例的收款账户的验证装置，还具有如下附加的技术特征：可选地，所述隐藏模块，包括：第一确定子模块，用于获取所述完整账号的长度；第二确定子模块，用于根据所述完整账号的长度，确定要隐藏的所述至少一个字符所对应的位置；隐藏子模块，用于将所述完整账号中的所述位置上的字符进行隐藏，以生成所述待验证收款账户对应的所述缺位账号。
可选地，所述比对模块，具体用于依次将所述补全后的账号中的每一位字符，分 别与所述完整账号中对应位置的字符进行比对。
可选地，所述验证模块，包括：允许子模块，用于在所述补全后的账号与所述完整账号相同的情况下，允许所述用户向所述待验证收款账户缴费；提示子模块，用于在所述补全后的账号与所述完整账号不相同的情况下，提示所述用户验证失败。
可选地，所述验证模块，还包括：统计子模块，用于统计所述用户验证失败的次数；禁止子模块，用于在所述用户验证失败的次数超过预设阈值的情况下，禁止所述用户在预设时间段内继续进行验证。
可选地，所述装置还包括：第二获取模块，用于获取所述用户输入的账户信息关键字；筛选模块，用于筛选出与所述账户信息关键字相关的候选账户，并进行显示；确定模块，用于根据所述用户对所述候选账户的选择，确定所述待验证收款账户。
本说明书实施例第三方面提出了一种计算机设备，包括存储器和处理器；所述存储器上存储有可由处理器运行的计算机程序；所述处理器运行所述计算机程序时，执行如前述方法实施例所述的收款账户的验证方法。
本说明书实施例第四方面提出了一种非临时性计算机可读存储介质，其上存储有计算机程序，所述计算机程序被处理器执行时实现如前述方法实施例所述的收款账户的验证方法。
本说明书实施例附加的方面和优点将在下面的描述中部分给出，部分将从下面的描述中变得明显，或通过本说明书实施例的实践了解到。
附图说明
为了更清楚地说明本说明书实施例的技术方案，下面将对实施例中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本说明书的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其它的附图。
图1为本说明书实施例所提出的一种收款账户的验证方法的流程示意图；
图2为本说明书实施例所提出的另一种收款账户的验证方法的流程示意图；
图3为本说明书实施例所提出的又一种收款账户的验证方法的流程示意图；
图4为本说明书实施例所提出的再一种收款账户的验证方法的流程示意图；
图5a-5g为本说明书实施例所提出的收款账户的验证方法的技术效果示意图；
图6为本说明书实施例所提出的一种收款账户的验证装置的结构示意图；
图7为本说明书实施例所提出的另一种收款账户的验证装置的结构示意图；
图8为本说明书实施例所提出的又一种收款账户的验证装置的结构示意图；
图9为本说明书实施例所提出的再一种收款账户的验证装置的结构示意图。
具体实施方式
下面详细描述本说明书的实施例，所述实施例的示例在附图中示出，其中自始至终相同或类似的标号表示相同或类似的元件或具有相同或类似功能的元件。下面通过参考附图描述的实施例是示例性的，旨在用于解释本说明书实施例，而不能理解为对本说明书实施例的限制。
下面参考附图描述本说明书实施例的收款账户的验证方法及其装置。
基于上述现有技术的描述可以知道，在缴费系统中，每一个账户对应有唯一的账号，用于对该账户进行识别。收款方在收款前，将指定的收款账户对应的账号提供给转账方。转账方在转账时，需要先输入收款账户对应的账号，使得缴费系统能够确定对应的收款账户，再将缴费款项转入该收款账户，完成缴费。
但是，一旦缴费方在缴费时输错了收款方的账号，则可能导致缴费款项无法顺利转入收款方指定的收款账户，导致缴费失败。
针对这一问题，本说明书实施例提出了一种收款账户的验证方法，缴费方无需手动输入收款账户的完整账号，只需补全收款账户对应的缺位账号。将补全后的账号与收款账户的完整账号进行比对，以实现对收款账户的验证。
图1为本说明书实施例所提出的一种收款账户的验证方法的流程示意图。如图1所示，该方法包括步骤S101至步骤S109。
步骤S101，获取待验证收款账户对应的完整账号。
其中，待验证收款账户对应的完整账号是缴费系统中，用于唯一标识待验证收款账户的一串字符。
需要说明的是，本说明书实施例所提出的收款账户的验证方法，没有依靠用户输入的完整账号来直接确定收款账户，而是先通过其他方式确定收款账户，作为待验证账 户。再获取收款账户对应的完整账号，从而借助完整账号对收款账户进行验证，进而保证验证成功的收款账户为收款方指定的收款账户。
可以理解，待验证收款账户与其对应的完整账号一一对应，既可以根据完整账号，确定对应的收款账户，还可以根据收款账户，确定对应的完整账号。
可以理解，收款方在开设收款账户时，需要提供相关信息，比如收款方的名称等信息，作为账户信息。
为了确定待验证账户，一种可能的实现方式是，在步骤S101，获取待验证收款账户对应的完整账号之前，还包括步骤S11至步骤S15。
步骤S11，获取用户输入的账户信息关键字。
可以理解，作为缴费方的用户，要确定收款账户，除了可以通过完整账号，还可以通过收款账户的账户信息来实现。具体可以输入账户信息关键字，比如收款方的名称，收款账户的开设银行等。
步骤S13，筛选出与账户信息关键字相关的候选账户，并进行显示。
应当理解，使用账户信息关键字来对系统中的所有账户进行筛选，可以使用现有的任何关键字检索技术来实现，本说明书实施例对此不做限定。
可以理解，当候选账户的数量为多个时，还需要对候选账户进行排列和显示，以便于用户对候选账户进行选择。
一种可能的实现方式是，按照候选账户的账户信息与账户信息关键字之间的相关度从大到小进行排列。
另一种可能的实现方式是，按照候选账户在预设时间内被查询的次数从大到小进行排列。
在对候选账户进行显示时，还可以将候选账户的账户信息一起显示。
步骤S15，根据用户对候选账户的选择，确定待验证收款账户。
可以理解，对于步骤S13中显示的候选账户，用户可以通过核对对应的账户信息，来确定待验证收款账户。
需要说明的是，对待验证收款账户的确定过程，实际上已经完成了对待验证收款账户的账户信息的验证。
步骤S103，将完整账号中的至少一个字符进行隐藏，以生成待验证收款账户对应的缺位账号。
步骤S105，将缺位账号进行显示，并提示用户补全至少一个字符。
可以理解，让用户对完整账号的每一个字符进行核对，一方面让用户觉得不耐烦，可能会选择直接跳过这步，另一方面用户核对时容易眼花，达不到验证的效果。本说明书实施例所提出的收款账户的验证方法，将完整账号中的至少一个字符进行隐藏，并让用户进行补全操作。
第一方面，用户必须填入隐藏部分的字符，才能进行对收款账户进行验证，无法跳过。第二方面，用户只需要填入隐藏部分的数字，较为简单，不容易出错。第三方面，由于显示的账号不完整，第三方无法直接获取待验证收款账户的完整账号。
可以理解，若待验证收款账户为收款方指定的收款账户，那么用户能够根据收款方提供的账号，将缺位账号补全为完整账号。
若待验证收款账户不是收款方指定的收款账户，那么收款方提供的账号，与待验证收款账户的完整账号不同，就会产生以下几种可能的情况。
第一种可能的情况，用户发现显示的缺位账号中，没有隐藏的字符与收款方提供的账号对应位置的字符不一样，用户意识到了待验证收款账户不是收款方指定的收款账户，可以直接终止对待验证收款账户的验证。
第二种可能的情况，用户没有对缺位账号中显示的字符进行一一核对，直接根据收款方提供的账号对缺位账号进行补全，需要缴费系统对补全后的账号与完整账号进行比对。
第三种可能的情况，用户对缺位账号和收款方提供的账号进行了仔细比对，但是没有发现不同，也就是说，两个账号之间存在区别的字符刚好被隐藏了，需要缴费系统对补全后的账号与完整账号进行比对。
步骤S107，将补全后的账号与完整账号进行比对。
可以理解，完整账号是一串字符，补全后的账号也是一串字符。
为了比较两串字符是否完全一致，一种可能的实现方式是，依次将补全后的账号中的每一位字符，分别与完整账号中对应位置的字符进行比对。
另一种可能的实现方式是，分别计算补全后的账户的哈希值和完整账号的哈希值， 进行比较两个哈希值的大小。
步骤S109，根据比对结果，完成对待验证收款账户的验证。
可以理解，用户对缺位账号进行补全，如果得到的补全后的账号与完整账号一模一样，则说明待验证收款账户为收款方指定的收款账户。如果得到的补全后的账号与完整账号不同，则可能是用户进行补全时出现了失误，导致输错了字符，还可能是收款方提供的账号与完整账号原本就不同。
综上所述，本说明书实施例所提出的一种收款账户的验证方法，获取待验证收款账户对应的完整账号。将完整账号中的至少一个字符进行隐藏，以生成待验证收款账户对应的缺位账号。将缺位账号进行显示，并提示用户补全多个字符。将补全后的账号与完整账号进行比对，根据比对结果，完成对待验证收款账户的验证。由此，实现了缴费方无需手动输入收款账户的完整账号，只需补全收款账户对应的缺位账号，既减少了缴费方输入字符的长度，降低了出错可能性，又使得缴费方在缴费之前，能够对收款方的账号进行验证，让缴费方顺利将缴费款项转入收款方的账户。
为了更加清楚地说明本说明书实施例所提出的收款账户的验证方法是如何生成缺位账号的，本说明书实施例还提出了另一种收款账户的验证方法，图2为本说明书实施例所提出的另一种收款账户的验证方法的流程示意图。如图2所示，该方法包括步骤S201至步骤S213。
步骤S201，获取待验证收款账户对应的完整账号。
步骤S203，确定完整账号的长度。
步骤S205，根据完整账号的长度，确定要隐藏的至少一个字符所对应的位置。
需要说明的是，对于世界上不同国家的银行开设的收款账户，所对应的账号在长度和格式上存在区别。相应地，可以根据完整账号的长度，选择不同位置的字符进行隐藏。
步骤S207，将完整账号中的位置上的字符进行隐藏，以生成待验证收款账户对应的缺位账号。
可以理解，由于不同长度的完整账号中的隐藏字符所对应的位置不同，因此生成的缺位账号的长度和格式也不同。
步骤S209，将缺位账号进行显示，并提示用户补全至少一个字符。
步骤S211，将补全后的账号与完整账号进行比对。
步骤S213，根据比对结果，完成对待验证收款账户的验证。
需要说明的是，前述对步骤S101-步骤S109的说明解释，也适用于本说明书实施例的方法步骤，此处不再赘述。
从而，实现了对于不同长度的完整账号，生成不同长度和格式的缺位账号。
为了更加清楚地说明本说明书实施例所提出的收款账户的验证方法是如何完成对待验证收款账户的验证的，本说明书实施例还提出了又一种收款账户的验证方法，图3为本说明书实施例所提出的又一种收款账户的验证方法的流程示意图。如图3所示，该方法包括步骤S301至步骤S311。
步骤S301，获取待验证收款账户对应的完整账号。
步骤S303，将完整账号中的至少一个字符进行隐藏，以生成待验证收款账户对应的缺位账号。
步骤S305，将缺位账号进行显示，并提示用户补全至少一个字符。
步骤S307，将补全后的账号与完整账号进行比对。
步骤S309，在补全后的账号与完整账号相同的情况下，允许用户向待验证收款账户缴费。
基于前述说明，可以知道，如果补全后的账号与完整账号相同，说明待验证收款账户为收款方指定的收款账户，那么用户可以进行下一步操作，向待验证收款账户进行缴费，无需担心缴费失败。
步骤S311，在补全后的账号与完整账号不相同的情况下，提示用户验证失败。
如果补全后的账号与完整账号不相同，则可能是用户进行补全时出现了失误，导致输错了字符，还可能是收款方提供的账号与完整账号原本就不同，无论是哪一种情况，都应当提示用户验证失败。
若用户发现是输入时的失误，导致输错了字符，那么用户可以对缺位账号进行重新补全。若用户发现输入没有错误，那么说明收款方提供的账号与完整账号原本就不同，需要重新确定待验证收款账户是否为收款方指定的收款账户。
进一步地，为了防止第三方通过试错的方式来获取收款账户对应的完整账号，一 种可能的实现方式是，在提示用户验证失败之后，还包括：统计用户验证失败的次数，在用户验证失败的次数超过预设阈值的情况下，禁止用户在预设时间段内继续进行验证。比如说，若用户同日内对于同一个收款账户，验证失败的次数达到三次，则禁止该用户一小时内继续进行验证。
需要说明的是，前述对步骤S101-步骤S109的说明解释，也适用于本说明书实施例的方法步骤，此处不再赘述。
从而，实现了根据比对结果，对用户的验证操作进行不同的处理。
为了更加清楚地说明本说明书实施例所提出的收款账户的验证方法的整个流程，本说明书实施例还提出了再一种收款账户的验证方法，图4为本说明书实施例所提出的再一种收款账户的验证方法的流程示意图。如图4所示，该方法包括步骤S401至步骤S425。
步骤S401，获取用户输入的账户信息关键字。
步骤S403，筛选出与账户信息关键字相关的候选账户，并进行显示。
步骤S405，根据用户对候选账户的选择，确定待验证收款账户。
步骤S407，获取待验证收款账户对应的完整账号。
步骤S409，确定完整账号的长度。
步骤S411，根据完整账号的长度，确定要隐藏的至少一个字符所对应的位置。
步骤S413，将完整账号中的位置上的字符进行隐藏，以生成待验证收款账户对应的缺位账号。
步骤S415，将缺位账号进行显示，并提示用户补全至少一个字符。
步骤S417，依次将补全后的账号中的每一位字符，分别与完整账号中对应位置的字符进行比对。
步骤S419，在补全后的账号与完整账号相同的情况下，允许用户向待验证收款账户缴费。
步骤S421，在补全后的账号与完整账号不相同的情况下，提示用户验证失败。
步骤S423，统计用户验证失败的次数。
步骤S425，在用户验证失败的次数超过预设阈值的情况下，禁止用户在预设时间 段内继续进行验证。
需要说明的是，前述对其他实施例的方法步骤的说明解释，也适用于本说明书实施例的方法步骤，此处不再赘述。
从而，实现了通过账户信息关键字，确定待验证收款账户，并完成对待验证收款账户的账户信息的验证。通过用户补全缺位账号的方式，来对待验证收款账户的完整账号进行比对，进而完成对待验证收款账户的验证。
为了更加清楚地说明本说明书所提出的收款账户的验证方法的技术效果，下面进行举例说明。
留学生在向海外院校指定的收款账户进行缴纳费用时，海外院校通常会告知留学生收款账户对应的账号，以及收款方的名称等信息。因此可以使用本说明书实施例所提供的收款账户的验证方法，来确保费用顺利转入指定的收款账户，避免转账失败而给留学生的学习生活带来麻烦。
具体来说，图5a-5g为本说明书实施例所提出的收款账户的验证方法的技术效果示意图。如图5a所示，若留学生需要向Cardfidd University指定的收款账户进行转账，可以先输入收款方的名称Cardfidd University。如图5b所示，系统经过对Cardfidd University相关的收款账户进行检索，查询到对应于Cardfidd University的收款账户，以及该收款账户的账户信息，并显示给留学生。留学生可以通过账户信息来初步判断该收款账户是否是Cardfidd University指定的收款账户。
如图5c所示，在完成了初步确定后，系统将该收款账户对应的完整账号中的部分数字进行隐藏，生成并显示缺位账号，提示留学生补全账号。留学生可以根据Cardfidd University提供的账号，在图5c所示的界面中填入空缺数字，还可以通过系统未隐藏的数字判断该收款账户是否是收款方指定的账户。
如图5d所示，当留学生填入空缺数字后，系统将补全的账号与该收款账户的完整账号进行比对。
如图5e所示，若补全的账号与该收款账户的完整账号相同，则校验成功吗，说明该收款账户为海外院校指定的收款账户，允许留学生进行转账操作。
如图5f所示，若补全的账号与该收款账户的完整账号不同，则校验失败，提升留学生重新填入空缺数字。
如图5g所示，若连续三次填入的数字都无法通过校验，则1小时内禁止该留学生对该收款账户进行校验。
从而，能够确保留学生将费用成功转入海外院校指定的收款账户。
为了实现上述实施例，本说明书实施例还提出了一种收款账户的验证装置，图6为本说明书实施例所提出的一种收款账户的验证装置的结构示意图。如图6所示，该装置包括：第一获取模块510、隐藏模块520、显示模块530、提示模块540、比对模块550、验证模块560。
第一获取模块510，用于获取待验证收款账户对应的完整账号。
隐藏模块520，用于将完整账号中的至少一个字符进行隐藏，以生成待验证收款账户对应的缺位账号。
显示模块530，用于将缺位账号进行显示。
提示模块540，用于提示用户补全至少一个字符。
比对模块550，用于将补全后的账号与完整账号进行比对。
验证模块560，用于根据比对结果，完成对待验证收款账户的验证。
进一步地，为了确定待验证账户，一种可能的实现方式是，该装置还包括：第二获取模块，用于获取用户输入的账户信息关键字。筛选模块，用于筛选出与账户信息关键字相关的候选账户，并进行显示。确定模块，用于根据用户对候选账户的选择，确定待验证收款账户。
进一步地，为了比较两串字符是否完全一致，一种可能的实现方式是，比对模块550，具体用于依次将补全后的账号中的每一位字符，分别与完整账号中对应位置的字符进行比对。
需要说明的是，前述对收款账户的验证方法实施例的解释说明也适用于该实施例的收款账户的验证装置，此处不再赘述。
综上所述，本说明书实施例所提出的一种收款账户的验证装置。在对收款账户进行验证时，获取待验证收款账户对应的完整账号。将完整账号中的至少一个字符进行隐藏，以生成待验证收款账户对应的缺位账号。将缺位账号进行显示，并提示用户补全多个字符。将补全后的账号与完整账号进行比对，根据比对结果，完成对待验证收款账户的验证。由此，实现了缴费方无需手动输入收款账户的完整账号，只需补全收款账户对 应的缺位账号，既减少了缴费方输入字符的长度，降低了出错可能性，又使得缴费方在缴费之前，能够对收款方的账号进行验证，让缴费方顺利将缴费款项转入收款方的账户。
为了实现上述实施例，本说明书实施例还提出了另一种收款账户的验证装置，图7为本说明书实施例所提出的另一种收款账户的验证装置的结构示意图。如图7所示，该装置包括：第一获取模块610、隐藏模块620、显示模块630、提示模块640、比对模块650、验证模块660。
第一获取模块610，用于获取待验证收款账户对应的完整账号。
隐藏模块620，用于将完整账号中的至少一个字符进行隐藏，以生成待验证收款账户对应的缺位账号。
显示模块630，用于将缺位账号进行显示。
提示模块640，用于提示用户补全至少一个字符。
比对模块650，用于将补全后的账号与完整账号进行比对。
验证模块660，用于根据比对结果，完成对待验证收款账户的验证。
其中，隐藏模块620，包括：第一确定子模块621，用于获取完整账号的长度。第二确定子模块622，用于根据完整账号的长度，确定要隐藏的至少一个字符所对应的位置。隐藏子模块623，用于将完整账号中的位置上的字符进行隐藏，以生成待验证收款账户对应的缺位账号。
需要说明的是，前述对收款账户的验证方法实施例的解释说明也适用于该实施例的收款账户的验证装置，此处不再赘述。
从而，实现了对于不同长度的完整账号，生成不同长度和格式的缺位账号。
为了实现上述实施例，本说明书实施例还提出了又一种收款账户的验证装置，图8为本说明书实施例所提出的又一种收款账户的验证装置的结构示意图。如图8所示，该装置包括：第一获取模块710、隐藏模块720、显示模块730、提示模块740、比对模块750、验证模块760。
第一获取模块710，用于获取待验证收款账户对应的完整账号。
隐藏模块720，用于将完整账号中的至少一个字符进行隐藏，以生成待验证收款账户对应的缺位账号。
显示模块730，用于将缺位账号进行显示。
提示模块740，用于提示用户补全至少一个字符。
比对模块750，用于将补全后的账号与完整账号进行比对。
验证模块760，用于根据比对结果，完成对待验证收款账户的验证。
其中，验证模块760，包括：允许子模块761，用于在补全后的账号与完整账号相同的情况下，允许用户向待验证收款账户缴费。提示子模块762，用于在补全后的账号与完整账号不相同的情况下，提示用户验证失败。
进一步地，为了防止第三方通过试错的方式来获取收款账户对应的完整账号，一种可能的实现方式是，验证模块760，还包括：统计子模块，用于统计用户验证失败的次数。禁止子模块，用于在用户验证失败的次数超过预设阈值的情况下，禁止用户在预设时间段内继续进行验证。
需要说明的是，前述对收款账户的验证方法实施例的解释说明也适用于该实施例的收款账户的验证装置，此处不再赘述。
从而，实现了根据比对结果，对用户的验证操作进行不同的处理。
为了实现上述实施例，本说明书实施例还提出了再一种收款账户的验证装置，图9为本说明书实施例所提出的再一种收款账户的验证装置的结构示意图。如图9所示，该装置包括：第二获取模块810、筛选模块820、确定模块830、第一获取模块840、隐藏模块850、显示模块860、提示模块870、比对模块880、验证模块890。
第二获取模块810，用于获取用户输入的账户信息关键字。
筛选模块820，用于筛选出与账户信息关键字相关的候选账户，并进行显示。
确定模块830，用于根据用户对候选账户的选择，确定待验证收款账户。
第一获取模块840，用于获取待验证收款账户对应的完整账号。
隐藏模块850，用于将完整账号中的至少一个字符进行隐藏，以生成待验证收款账户对应的缺位账号。
显示模块860，用于将缺位账号进行显示。
提示模块870，用于提示用户补全至少一个字符。
比对模块880，用于依次将补全后的账号中的每一位字符，分别与完整账号中对应 位置的字符进行比对。
验证模块890，用于根据比对结果，完成对待验证收款账户的验证。
其中，隐藏模块850，包括：第一确定子模块851，用于获取完整账号的长度。第二确定子模块852，用于根据完整账号的长度，确定要隐藏的至少一个字符所对应的位置。隐藏子模块853，用于将完整账号中的位置上的字符进行隐藏，以生成待验证收款账户对应的缺位账号。
验证模块890，包括：允许子模块891，用于在补全后的账号与完整账号相同的情况下，允许用户向待验证收款账户缴费。提示子模块892，用于在补全后的账号与完整账号不相同的情况下，提示用户验证失败。统计子模块893，用于统计用户验证失败的次数。禁止子模块894，用于在用户验证失败的次数超过预设阈值的情况下，禁止用户在预设时间段内继续进行验证。
需要说明的是，前述对收款账户的验证方法实施例的解释说明也适用于该实施例的收款账户的验证装置，此处不再赘述。
从而，实现了通过账户信息关键字，确定待验证收款账户，并完成对待验证收款账户的账户信息的验证。通过用户补全缺位账号的方式，来对待验证收款账户的完整账号进行比对，进而完成对待验证收款账户的验证。
为了实现上述实施例，本说明书实施例还提出一种计算机设备，包括存储器和处理器；存储器上存储有可由处理器运行的计算机程序；当处理器运行计算机程序时，执行如前述方法实施例的收款账户的验证方法。
为了实现上述实施例，实施例还提出一种非临时性计算机可读存储介质，其上存储有计算机程序，计算机程序被处理器执行时实现如前述方法实施例的收款账户的验证方法。
上述对本说明书特定实施例进行了描述。其它实施例在所附权利要求书的范围内。在一些情况下，在权利要求书中记载的动作或步骤可以按照不同于实施例中的顺序来执行并且仍然可以实现期望的结果。另外，在附图中描绘的过程不一定要求示出的特定顺序或者连续顺序才能实现期望的结果。在某些实施方式中，多任务处理和并行处理也是可以的或者可能是有利的。
此外，术语“第一”、“第二”仅用于描述目的，而不能理解为指示或暗示相对重要性或者隐含指明所指示的技术特征的数量。由此，限定有“第一”、“第二”的特 征可以明示或者隐含地包括至少一个该特征。在本说明书实施例的描述中，“多个”的含义是至少两个，例如两个，三个等，除非另有明确具体的限定。
在本说明书实施例中，除非另有明确的规定和限定，术语“安装”、“相连”、“连接”、“固定”等术语应做广义理解，例如，可以是固定连接，也可以是可拆卸连接，或成一体；可以是机械连接，也可以是电连接；可以是直接相连，也可以通过中间媒介间接相连，可以是两个元件内部的连通或两个元件的相互作用关系，除非另有明确的限定。对于本领域的普通技术人员而言，可以根据具体情况理解上述术语在本说明书实施例中的具体含义。
在本说明书实施例中，除非另有明确的规定和限定，第一特征在第二特征“上”或“下”可以是第一和第二特征直接接触，或第一和第二特征通过中间媒介间接接触。而且，第一特征在第二特征“之上”、“上方”和“上面”可是第一特征在第二特征正上方或斜上方，或仅仅表示第一特征水平高度高于第二特征。第一特征在第二特征“之下”、“下方”和“下面”可以是第一特征在第二特征正下方或斜下方，或仅仅表示第一特征水平高度小于第二特征。
在本说明书的描述中，参考术语“一个实施例”、“一些实施例”、“示例”、“具体示例”、或“一些示例”等的描述意指结合该实施例或示例描述的具体特征、结构、材料或者特点包含于本说明书实施例的至少一个实施例或示例中。在本说明书中，对上述术语的示意性表述不必须针对的是相同的实施例或示例。而且，描述的具体特征、结构、材料或者特点可以在任一个或多个实施例或示例中以合适的方式结合。此外，在不相互矛盾的情况下，本领域的技术人员可以将本说明书中描述的不同实施例或示例以及不同实施例或示例的特征进行结合和组合。
尽管上面已经示出和描述了本申请的实施例，可以理解的是，上述实施例是示例性的，不能理解为对本申请的限制，本领域的普通技术人员在本发明的范围内可以对上述实施例进行变化、修改、替换和变型。

Claims (14)

  1. 一种收款账户的验证方法，包括：
    获取待验证收款账户对应的完整账号；
    将所述完整账号中的至少一个字符进行隐藏，以生成所述待验证收款账户对应的缺位账号；
    将所述缺位账号进行显示，并提示用户补全所述至少一个字符；
    将补全后的账号与所述完整账号进行比对；
    根据比对结果，完成对所述待验证收款账户的验证。
  2. 如权利要求1所述的方法，其中，所述将所述完整账号中的至少一个字符进行隐藏，以生成所述待验证收款账户对应的缺位账号，包括：
    确定所述完整账号的长度；
    根据所述完整账号的长度，确定要隐藏的所述至少一个字符所对应的位置；
    将所述完整账号中的所述位置上的字符进行隐藏，以生成所述待验证收款账户对应的所述缺位账号。
  3. 如权利要求1所述的方法，其中，所述将补全后的账号与所述完整账号进行比对，包括：
    依次将所述补全后的账号中的每一位字符，分别与所述完整账号中对应位置的字符进行比对。
  4. 如权利要求1所述的方法，其中，所述根据比对结果，完成对所述待验证收款账户的验证，包括：
    在所述补全后的账号与所述完整账号相同的情况下，允许所述用户向所述待验证收款账户缴费；
    在所述补全后的账号与所述完整账号不相同的情况下，提示所述用户验证失败。
  5. 如权利要求4所述的方法，其中，在所述提示用户验证失败之后，还包括：
    统计所述用户验证失败的次数；
    在所述用户验证失败的次数超过预设阈值的情况下，禁止所述用户在预设时间段内继续进行验证。
  6. 如权利要求1-5中任一项所述的方法，其中，在所述获取待验证收款账户对应的完整账号之前，还包括：
    获取所述用户输入的账户信息关键字；
    筛选出与所述账户信息关键字相关的候选账户，并进行显示；
    根据所述用户对所述候选账户的选择，确定所述待验证收款账户。
  7. 一种收款账户的验证装置，包括：
    第一获取模块，用于获取待验证收款账户对应的完整账号；
    隐藏模块，用于将所述完整账号中的至少一个字符进行隐藏，以生成所述待验证收款账户对应的缺位账号；
    显示模块，用于将所述缺位账号进行显示；
    提示模块，用于提示用户补全所述至少一个字符；
    比对模块，用于将补全后的账号与所述完整账号进行比对；
    验证模块，用于根据比对结果，完成对所述待验证收款账户的验证。
  8. 如权利要求7所述的装置，其中，所述隐藏模块，包括：
    第一确定子模块，用于获取所述完整账号的长度；
    第二确定子模块，用于根据所述完整账号的长度，确定要隐藏的所述至少一个字符所对应的位置；
    隐藏子模块，用于将所述完整账号中的所述位置上的字符进行隐藏，以生成所述待验证收款账户对应的所述缺位账号。
  9. 如权利要求7所述的装置，其中，所述比对模块，具体用于依次将所述补全后的账号中的每一位字符，分别与所述完整账号中对应位置的字符进行比对。
  10. 如权利要求7所述的装置，其中，所述验证模块，包括：
    允许子模块，用于在所述补全后的账号与所述完整账号相同的情况下，允许所述用户向所述待验证收款账户缴费；
    提示子模块，用于在所述补全后的账号与所述完整账号不相同的情况下，提示所述用户验证失败。
  11. 如权利要求10所述的装置，其中，所述验证模块，还包括：
    统计子模块，用于统计所述用户验证失败的次数；
    禁止子模块，用于在所述用户验证失败的次数超过预设阈值的情况下，禁止所述用户在预设时间段内继续进行验证。
  12. 如权利要求7-11中任一项所述的装置，其中，所述装置还包括：
    第二获取模块，用于获取所述用户输入的账户信息关键字；
    筛选模块，用于筛选出与所述账户信息关键字相关的候选账户，并进行显示；
    确定模块，用于根据所述用户对所述候选账户的选择，确定所述待验证收款账户。
  13. 一种计算机设备，包括存储器和处理器；所述存储器上存储有可由处理器运行 的计算机程序；所述处理器运行所述计算机程序时，执行如权利要求1-6中任一项所述的收款账户的验证方法。
  14. 一种非临时性计算机可读存储介质，其上存储有计算机程序，所述计算机程序被处理器执行时实现如权利要求1-6中任一项所述的收款账户的验证方法。
PCT/CN2020/116420 2019-11-06 2020-09-21 收款账户的验证方法及其装置 Ceased WO2021088534A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201911078360.2 2019-11-06
CN201911078360.2A CN110827035B (zh) 2019-11-06 2019-11-06 收款账户的验证方法及其装置

Publications (1)

Publication Number Publication Date
WO2021088534A1 true WO2021088534A1 (zh) 2021-05-14

Family

ID=69552931

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/116420 Ceased WO2021088534A1 (zh) 2019-11-06 2020-09-21 收款账户的验证方法及其装置

Country Status (3)

Country Link
CN (2) CN113095833A (zh)
TW (1) TWI741593B (zh)
WO (1) WO2021088534A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113095833A (zh) * 2019-11-06 2021-07-09 支付宝(杭州)信息技术有限公司 收款账户的验证方法及其装置
CN111523878A (zh) * 2020-04-30 2020-08-11 北京三快在线科技有限公司 业务处理方法、装置、系统及存储介质
CN114723431A (zh) * 2022-03-23 2022-07-08 车主邦（北京）科技有限公司 订单处理方法及装置、电子设备以及存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101996368A (zh) * 2009-08-21 2011-03-30 阿里巴巴集团控股有限公司 一种跨银行批量付款方法及系统
US20120272328A1 (en) * 2008-09-09 2012-10-25 Applied Systems, Inc. Method, system and apparatus for secure data editing
CN105763429A (zh) * 2016-04-28 2016-07-13 乐视控股（北京）有限公司 账号输入自动补全方法及系统
CN106156662A (zh) * 2015-04-14 2016-11-23 阿里巴巴集团控股有限公司 终端安全保护方法及装置
CN110827035A (zh) * 2019-11-06 2020-02-21 支付宝(杭州)信息技术有限公司 收款账户的验证方法及其装置

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1897041A (zh) * 2005-07-14 2007-01-17 刘庆志 指令密码系统及指令密码处理方法
CN101950451A (zh) * 2010-08-19 2011-01-19 中国民生银行股份有限公司 银行账户间收付款处理方法及系统
CN103856915A (zh) * 2012-12-06 2014-06-11 阿里巴巴集团控股有限公司 数据资源转移方法和设备
US20170262822A1 (en) * 2013-01-21 2017-09-14 Robert Conyers Disbursement and settlements system and method
CN106156149B (zh) * 2015-04-14 2020-01-03 阿里巴巴集团控股有限公司 一种数据转移方法及装置
CN106815723A (zh) * 2017-02-10 2017-06-09 深圳前海微众银行股份有限公司 转账方法及装置
CN107239193A (zh) * 2017-05-25 2017-10-10 努比亚技术有限公司 一种联系人添加方法、移动终端以及计算机可读存储介质
CN107301551B (zh) * 2017-07-15 2020-09-29 刘兴丹 一种网络支付前搜索、查询、验证的方法、装置、系统
TWI665577B (zh) * 2018-03-19 2019-07-11 財金資訊股份有限公司 具網路交易資訊確認功能之卡片讀取裝置及其支付方法
CN110163714A (zh) * 2019-04-01 2019-08-23 阿里巴巴集团控股有限公司 一种基于相似度算法挖掘隐藏风险商户的方法和装置
TWM584476U (zh) * 2019-06-06 2019-10-01 中國信託金融控股股份有限公司 轉帳伺服系統
TWM588277U (zh) * 2019-08-06 2019-12-21 台新國際商業銀行股份有限公司 付款檔轉檔系統

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120272328A1 (en) * 2008-09-09 2012-10-25 Applied Systems, Inc. Method, system and apparatus for secure data editing
CN101996368A (zh) * 2009-08-21 2011-03-30 阿里巴巴集团控股有限公司 一种跨银行批量付款方法及系统
CN106156662A (zh) * 2015-04-14 2016-11-23 阿里巴巴集团控股有限公司 终端安全保护方法及装置
CN105763429A (zh) * 2016-04-28 2016-07-13 乐视控股（北京）有限公司 账号输入自动补全方法及系统
CN110827035A (zh) * 2019-11-06 2020-02-21 支付宝(杭州)信息技术有限公司 收款账户的验证方法及其装置

Also Published As

Publication number Publication date
CN113095833A (zh) 2021-07-09
CN110827035A (zh) 2020-02-21
TWI741593B (zh) 2021-10-01
CN110827035B (zh) 2021-06-04
TW202119246A (zh) 2021-05-16

Similar Documents

Publication Publication Date Title
WO2021088534A1 (zh) 收款账户的验证方法及其装置
US20200151706A1 (en) Trigger peer to peer payment with financial cards and phone camera
WO2021036652A1 (zh) 多角色页面跳转方法、装置、计算机设备及可读存储介质
US12574370B2 (en) Verifying party identities for secure transactions
KR20120019021A (ko) 사용자 인증을 수행하는 화상형성장치 및 화상형성장치의 사용자 인증 수행 방법
US20210056618A1 (en) Transferring transactions between financial institutions
CN108241999A (zh) 一种发票信息的生成方法、装置及系统
US9087354B1 (en) Ordering checks using a mobile device
CN108446654A (zh) 一种基于图像的人脸辨识方法
CN111028076A (zh) 基于异步处理的银行线上开户方法、装置及存储介质
CN112633271A (zh) 一种基于ocr识别的金融交易系统认证方法
CN110532018A (zh) 代码提交方法及装置
CN106909812A (zh) 终端解锁处理方法及终端
JP7620604B2 (ja) 銀行相続手続支援方法
HK40055829A (zh) 收款账户的验证方法及其装置
HK40023534B (zh) 收款账户的验证方法及其装置
HK40023534A (zh) 收款账户的验证方法及其装置
KR102389783B1 (ko) 다건이체 방법 및 이를 수행하는 뱅킹 서버
JP2016048421A (ja) 情報処理システム、情報処理装置、画面生成装置、表示制御装置およびプログラム
JP2020030586A (ja) 施設利用管理システム、施設利用管理方法、及びプログラム
CA3189486A1 (en) System and method for rapid student verification
US12033428B2 (en) Method, server and communication system of verifying user for transportation purposes
CN115392893A (zh) 基于区块链实现安全转账的处理方法及装置
WO2018145241A1 (zh) 一种基于指纹信息的电子支付方法和装置
US20140058940A1 (en) Remote deposit capture internet deposit application

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20884769

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20884769

Country of ref document: EP

Kind code of ref document: A1