WO2016086708A1 - 支付验证方法、装置及系统 - Google Patents

支付验证方法、装置及系统 Download PDF

Info

Publication number
WO2016086708A1
WO2016086708A1 PCT/CN2015/090461 CN2015090461W WO2016086708A1 WO 2016086708 A1 WO2016086708 A1 WO 2016086708A1 CN 2015090461 W CN2015090461 W CN 2015090461W WO 2016086708 A1 WO2016086708 A1 WO 2016086708A1
Authority
WO
WIPO (PCT)
Prior art keywords
payment
payment terminal
verified
information
terminal
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/CN2015/090461
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.)
ZTE Corp
Original Assignee
ZTE Corp
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 ZTE Corp filed Critical ZTE Corp
Priority to JP2017528888A priority Critical patent/JP2017535893A/ja
Priority to EP15865494.7A priority patent/EP3229190A4/en
Priority to US15/532,923 priority patent/US20170344992A1/en
Publication of WO2016086708A1 publication Critical patent/WO2016086708A1/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
    • 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/02—Payment architectures, schemes or protocols involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
    • 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/08—Payment architectures
    • G06Q20/20—Point-of-sale [POS] network systems
    • 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/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
    • G06Q20/322—Aspects of commerce using mobile devices [M-devices]
    • 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/389—Keeping log of transactions for guaranteeing non-repudiation of a transaction
    • 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
    • G06Q20/40145—Biometric identity checks
    • 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/42—Confirmation, e.g. check or permission by the legal debtor of payment
    • G06Q20/425—Confirmation, e.g. check or permission by the legal debtor of payment using two different networks, one for transaction and one for security confirmation

Definitions

  • the present invention relates to the field of communications, and in particular to a payment verification method, apparatus, and system.
  • the embodiment of the invention provides a payment verification method, device and system, so as to at least solve the problem of security risks caused by insufficient security in the prior art.
  • a payment verification method including:
  • the first to-be-verified instruction includes at least one of the following: user characteristic information and payment account information; and the second to-be-verified instruction includes at least one of the following: user characteristic information, and payment terminal information.
  • the user feature information includes at least one of: voice, facial features, retina information; and or, the payment account information includes: an account number; and/or, the payment terminal information includes at least one of the following: Terminal ID, billing information.
  • whether the first to-be-verified instruction and the second to-be-verified instruction are the same according to the preset condition including: mode one, according to the payment account of the payment terminal pre-stored in the preset condition. Determining whether the information is the same as the payment account information in the first to-be-verified instruction; and determining user characteristic information and the second to-be-verified instruction in the first to-be-verified instruction according to the user characteristic information of the payment terminal pre-stored in the preset condition The user characteristic information is the same; the second method is to determine whether the payment account information in the first pending verification instruction is the same according to the payment account information of the payment terminal pre-stored in the preset condition; and the pre-stored payment according to the preset condition.
  • the user characteristic information of the terminal determines whether the user feature information in the first to-be-verified command is the same as the pre-stored user feature information, and determines whether the user feature information in the second to-be-verified command is the same as the pre-stored user feature information.
  • the verification result is sent to the payment terminal and/or the payment terminal by one of the following methods, including: if the determination result in the first mode or the second mode is the same, the verification is successful.
  • the message is sent to the payment terminal and/or the payment terminal; if the determination result of the mode one or the second mode is different, the verification failure message is sent to the payment terminal and/or the payment terminal.
  • the method before the sending the verification result to the payment terminal and/or the payment terminal, the method further includes: according to the user characteristic information and the payment account information in the first to-be-verified instruction, and the second to-be-verified instruction Billing information in the payment terminal information, generating consumption details; storing consumption details.
  • the first to-be-verified command and the second to-be-verified command are received in the following cases: the payment terminal establishes a payment connection with the payment terminal in advance.
  • another payment verification apparatus comprising: a receiving module, configured to receive, in a payment process, a first to-be-verified instruction sent by a payment terminal and a second to-be-verified instruction sent by a payment terminal;
  • the determining module is configured to determine, according to the preset condition, whether the first to-be-verified instruction received by the receiving module is the same as the second to-be-verified instruction; and the sending module is configured to send the verification result obtained by the determining module to the payment terminal and/or the payment terminal .
  • the determining module is configured to determine the first condition according to one of the following manners. Whether the to-be-verified instruction is the same as the second to-be-verified instruction, the first determining unit is configured to determine, according to the payment account information of the payment terminal pre-stored in the preset condition, whether the payment account information in the first to-be-verified instruction is the same And determining, according to user characteristic information of the payment terminal pre-stored in the preset condition, whether the user feature information in the first to-be-verified command and the user feature information in the second to-be-verified command are the same; the second determining unit is configured as a basis The payment account information of the payment terminal pre-stored in the preset condition is determined to be the same as the payment account information in the first pending verification instruction; and the first to be verified is determined according to the user characteristic information of the payment terminal pre-stored in the preset condition. Whether the user characteristic information in the instruction is the same as the pre-stored user characteristic information, and
  • the sending module is configured to send the verification result to the payment terminal and/or the payment terminal by using one of the following manners, including: the first sending unit, configured to be in the first determining unit or the second determining If the judgment result in the unit is the same, the message that the verification is successful is sent to the payment terminal and/or the payment terminal; and the second sending unit is set to be at least one of the first determination unit or the second determination unit. If the judgment result is different, the verification failure message is sent to the payment terminal and/or the payment terminal.
  • the device further includes: a generating module, configured to: before the sending the verification result to the payment terminal and/or the payment terminal, according to the user characteristic information and the payment account information in the first to-be-verified instruction, and The billing information in the receiving terminal information in the second to-be-verified instruction generates a consumption detail; and the storage module is configured to store the consumption details generated by the generating module.
  • a generating module configured to: before the sending the verification result to the payment terminal and/or the payment terminal, according to the user characteristic information and the payment account information in the first to-be-verified instruction, and The billing information in the receiving terminal information in the second to-be-verified instruction generates a consumption detail
  • the storage module is configured to store the consumption details generated by the generating module.
  • another payment verification system including: a server, a payment terminal, and a collection terminal, wherein the server establishes a communication connection with the payment terminal and the payment terminal, and is configured to receive the payment terminal.
  • the result; the server is any of the payment verification devices described above.
  • the first to-be-verified instruction sent by the payment terminal and the second to-be-verified instruction sent by the payment terminal are received in the payment process; and the first to-be-verified instruction and the second to-be-verified instruction are determined according to the preset condition. Whether they are the same; the verification result is sent to the payment terminal and/or the payment terminal.
  • the problem that the verification method is not safe enough and the security risks are brought about is solved, thereby achieving the effect of improving the security of the verification method.
  • FIG. 1 is a flow chart of a payment verification method according to an embodiment of the present invention.
  • FIG. 2 is a flow chart of information interaction of a payment verification method according to an embodiment of the present invention.
  • FIG. 3 is a structural block diagram of a payment verification apparatus according to an embodiment of the present invention.
  • FIG. 4 is a block diagram showing the structure of a payment verification apparatus according to a preferred embodiment of the present invention.
  • FIG. 5 is a block diagram showing another structure of a payment verification apparatus according to a preferred embodiment of the present invention.
  • FIG. 6 is a block diagram showing another structure of a payment verification apparatus according to an embodiment of the present invention.
  • FIG. 7 is a structural diagram of a payment verification system according to an embodiment of the present invention.
  • Figure 8 is a flow chart of voice-based verification in the present invention.
  • FIG. 1 is a flowchart of a payment verification method according to an embodiment of the present invention. As shown in FIG. 1, the process includes the following steps:
  • Step S102 in the payment process, receiving a first to-be-verified instruction sent by the payment terminal and a second to-be-verified instruction sent by the payment terminal;
  • Step S104 determining whether the first to-be-verified instruction and the second to-be-verified instruction are the same according to the preset condition
  • Step S106 the verification result is sent to the payment terminal and/or the payment terminal.
  • the first to-be-verified instruction sent by the payment terminal and the second to-be-verified instruction sent by the payment terminal are received; and the first to-be-verified instruction and the second to-be-verified instruction are determined according to the preset condition.
  • the payment terminal includes at least one of the following: a smart phone, a tablet computer, an MP3, an MP4, a palmtop computer; and the payment terminal includes at least one of the following: a POS machine and a cash register.
  • the payment verification method provided in the embodiment of the present invention is applicable to a server.
  • the payment terminal in the embodiment of the present invention uses a smart phone as an example, and the cash collection terminal takes a cash register as an example for description.
  • the server receives the first pending verification instruction reported by the smartphone, and the cash register The second pending verification instruction, wherein the smart phone collects the user feature through the payment client, and generates the first to-be-verified instruction by using the account information of the payment client; the cash register collects the pending verification instruction
  • the user feature in combination with the ID and billing information stored in the cash register, generates a second to-be-verified instruction; when comparing the first to-be-verified instruction with the second to-be-verified instruction, determining the first to-be-verified instruction by using a preset condition in the server Whether it is the same as the second to-be-verified instruction, thereby obtaining the verification result.
  • the verification of the user features saves the process of password input process and gesture input verification, improves payment efficiency; and because of password input and gestures In the process of inputting, it is easy to be in the wrong situation.
  • the correct rate of payment verification is improved.
  • the information security is more reliable, thereby improving the reliability.
  • the first to-be-verified instruction includes at least one of the following: user characteristic information and payment account information; and the second to-be-verified instruction includes at least one of the following: user characteristic information, and payment terminal information.
  • the user feature information includes at least one of: voice, facial features, retina information; and or, the payment account information includes: an account number; and/or, the payment terminal information includes at least one of the following: Terminal ID, billing information.
  • the user feature may be one of voice, facial features, and retina information
  • the payment terminal ID in the payment terminal information may be an ID or associated with the cash register stored in advance on the server side.
  • the account, billing information may be a purchase list of the user currently using the payment terminal.
  • the server receives the first to-be-verified instruction sent by the payment terminal and the second to-be-verified instruction sent by the payment terminal as follows:
  • the first to-be-verified instruction and the second to-be-verified instruction received by the server are respectively obtained by:
  • the first to-be-verified command the smartphone obtains the first to-be-verified instruction by encapsulating the voice of the user A, the voice of the user A, and the account of the smart phone payment client, and sends the first to-be-verified instruction to the server;
  • the second to-be-verified command since the smart phone establishes a payment connection with the cash register in advance, while the smart phone collects the user A voice, the cash register also collects the voice of the user A through the configured microphone, and the user A's The total number of settlements of the purchase list and the ID of the radio are sent to the server along with the collected voice of User A.
  • step S104 it is determined whether the first to-be-verified instruction and the second to-be-verified instruction are the same according to the preset condition, including:
  • the first method it is determined whether the first payment is based on the payment account information of the payment terminal pre-stored in the preset condition.
  • the payment account information in the verification instruction is the same; and determining whether the user feature information in the first to-be-verified instruction and the user feature information in the second to-be-verified instruction are the same according to the user characteristic information of the payment terminal pre-stored in the preset condition;
  • the server side stores the account of the payment client and the voice verification command in the smart phone used by the user A, so when verifying the first to-be-verified command and the second to-be-verified command:
  • Step 1 The server compares the account in the payment account information in the first to-be-verified command with the pre-stored account to ensure that the received account is an account payment corresponding to the same account;
  • Step 2 The server compares the voice carried in the first to-be-verified command and the voice carried in the second to-be-verified command with the voice color of the pre-stored voice verification command to ensure that the user who currently uses the account of Step1 is the same user A.
  • the second method it is determined whether the payment account information of the payment terminal is the same as the pre-stored payment account information in the preset condition, and is determined according to the user characteristic information of the payment terminal pre-stored in the preset condition. Whether the user feature information in the first to-be-verified command is the same as the pre-stored user feature information, and whether the user feature information in the second to-be-verified command is the same as the pre-stored user feature information.
  • Step 1 The server compares the account in the payment account information in the first to-be-verified command with the pre-stored account to ensure that the received account is an account payment corresponding to the same account;
  • Step 2 The server compares the voice color of the voice carried in the first to-be-verified command with the content and the voice and content of the pre-stored voice verification command, and compares the voice color and content of the voice carried in the second to-be-verified command with the pre-stored voice.
  • the tone and content of the voice verification command are compared to ensure that the user currently using the Step1 account is the same user A and that the accuracy of voice verification is ensured.
  • step S106 the verification result is sent to the payment terminal and/or the payment terminal by one of the following methods, including:
  • the successful verification message is sent to the payment terminal and/or the payment terminal;
  • the mode 1 is used as an example. If the judgment results of Step 1 and Step 2 in the first mode are the same, that is, the verification is passed, the server sends the verification pass message to the payment terminal and / or collection terminal.
  • the second method is the same as above, and will not be described here.
  • the message of the verification failure is transmitted to the payment terminal and/or the payment terminal.
  • Step 1 and Step 2 in Mode 1 or Mode 2 are different as long as the judgment result obtained by any one of them is different, the verification fails, and the server transmits a message of the verification failure to the payment terminal and/or the payment terminal.
  • the method before the sending the verification result to the payment terminal and/or the payment terminal in step S106, the method further includes:
  • Step S107 generating a consumption detail according to the user characteristic information and the payment account information in the first to-be-verified instruction, and the billing information in the collection terminal information in the second to-be-verified instruction;
  • Step S108 storing the consumption details.
  • step S107 and step S108 if the verification is successful, the server will store the details of the current verification, and further generate the consumption details, so as to be stored for the user A to query.
  • the first to-be-verified command and the second to-be-verified command are received in the following cases: the payment terminal establishes a payment connection with the payment terminal in advance.
  • FIG. 2 is a flow chart of information interaction of a payment verification method according to an embodiment of the present invention. As shown in FIG. 2, the information interaction process is as follows:
  • Step S201 the payment terminal establishes a payment connection with the payment terminal
  • Step S202 the payment terminal collects user features.
  • Step S203 the collection terminal collects user features.
  • Step S204 The payment terminal generates the first to-be-verified instruction by using the collected user feature together with the payment account.
  • Step S205 the payment terminal sends a first to-be-verified instruction to the server
  • Step S206 the payment terminal generates the second to-be-verified instruction together with the collected user feature and the payment terminal information
  • Step S207 the payment terminal sends a second to-be-verified instruction to the server
  • Step S208 the server receives the first to-be-verified instruction sent by the payment terminal and the second to-be-verified instruction sent by the payment terminal;
  • Step S209 the server determines, according to the preset condition, whether the first to-be-verified instruction and the second to-be-verified instruction are the same;
  • Step S210 the server sends the verification result to the payment terminal and/or the payment terminal;
  • Step S211 the payment terminal receives the verification result sent by the server
  • Step S212 the payment terminal receives the verification result sent by the server.
  • the payment verification method provided by the embodiment of the present invention takes voice as an example, and the facial feature or the retina information is the same as the voice verification mode, and details are not described herein.
  • the body-specific texture can also be used as the verification instruction.
  • the fingerprint is verified in the same manner as the voice verification.
  • the embodiment of the present invention is based on the implementation of a payment verification method, which is not limited.
  • a payment verification device is further provided, which is used to implement the above-mentioned embodiments and preferred embodiments, and the description thereof has been omitted.
  • the term “module” may implement a combination of software and/or hardware of a predetermined function.
  • the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.
  • FIG. 3 is a structural block diagram of a payment verification apparatus according to an embodiment of the present invention. As shown in FIG. 3, the apparatus includes: a receiving module 32, a determining module 34, and a sending module 36, where
  • the receiving module 32 is configured to receive, in the payment process, a first to-be-verified command sent by the payment terminal and a second to-be-verified command sent by the payment terminal;
  • the determining module 34 establishes a communication connection with the receiving module 32, and determines whether the first to-be-verified command received by the receiving module 32 and the second to-be-verified command are the same according to the preset condition;
  • the sending module 36 establishes a communication connection with the determining module 34, and is configured to send the verification result obtained by the determining module 34 to the payment terminal and/or the payment terminal.
  • FIG. 4 is a structural block diagram of a payment verification apparatus according to a preferred embodiment of the present invention.
  • the determination module 34 is configured to determine the first to be determined according to a preset condition by using one of the following manners. Whether the verification instruction is the same as the second verification instruction, including:
  • the first determining unit 341 is configured to determine, according to the payment account information of the payment terminal pre-stored in the preset condition, whether it is the same as the payment account information in the first to-be-verified instruction; and the user of the payment terminal pre-stored according to the preset condition Determining, by the feature information, whether the user feature information in the first to-be-verified command and the user feature information in the second to-be-verified command are the same;
  • the second determining unit 342 is configured to determine, according to the payment account information of the payment terminal that is pre-stored in the preset condition, whether it is the same as the payment account information in the first to-be-verified command; and according to the pre-stored payment terminal in the preset condition
  • the user feature information determines whether the user feature information in the first to-be-verified command is the same as the pre-stored user feature information, and determines whether the user feature information in the second to-be-verified command is the same as the pre-stored user feature information.
  • FIG. 5 is a structural block diagram of a payment verification apparatus according to a preferred embodiment of the present invention.
  • the sending module 36 is configured to send the verification result to the payment terminal and in one of the following manners. / or collection terminal, including:
  • the first sending unit 361 is configured to send a message that the verification is successful to the payment terminal and/or the payment terminal if the determination result in the first determination unit 341 or the second determination unit 342 is the same;
  • the second transmitting unit 362 is configured to transmit a message that the verification fails to the payment terminal and/or the payment terminal if the determination result of at least one of the first determination unit 341 or the second determination unit 342 is different.
  • FIG. 6 is a structural block diagram of a payment verification apparatus according to an embodiment of the present invention.
  • the apparatus includes: a generation module 38 and a storage, in addition to all the modules shown in FIG. Module 40, wherein
  • the generating module 38 is configured to: before the sending the verification result to the payment terminal and/or the payment terminal, according to the user characteristic information and the payment account information in the first to-be-verified instruction, and the payment terminal information in the second to-be-verified instruction Billing information in the account, generating consumption details;
  • the storage module 40 establishes a connection relationship with the generation module 38 and is configured to store the consumption details generated by the generation module 38.
  • FIG. 7 is a structural diagram of a payment verification system according to an embodiment of the present invention. As shown in FIG. 7, the system includes: a server 72, a payment terminal 74, and a collection terminal 76. ,among them,
  • the server 72 establishes a communication connection with the payment terminal 74 and the payment terminal 76, and is configured to receive the first to-be-verified instruction sent by the payment terminal 74 and the second to-be-verified instruction sent by the payment terminal 76, and determine according to the preset condition. Whether the first to-be-verified instruction is the same as the second to-be-verified instruction, and transmits the verification result to the payment terminal 74 and/or the payment terminal 76;
  • the server 72 is the payment verification device shown in any of FIGS. 3 to 6.
  • the embodiment of the present invention adopts a policy that a payment terminal and a collection terminal simultaneously input a voice password for performing identity verification and performing payment, that is, when the user performs payment, the voice password is dictated on the spot, and the mobile terminal and the payment terminal simultaneously Receiving and sending the voice password to the server, the server side parses and authenticates the instructions. If the authentication passes, the user verification succeeds; if the authentication fails, the user verification fails.
  • Step 1 The terminal user initiates a verification operation
  • Step 2 The user speaks the voice password on the spot, and after receiving the voice password, the payment terminal and the payment terminal simultaneously encode the password and send it to the server;
  • Step 3 After receiving the voice password, the server decodes the password.
  • Step 4 The server authenticates the parsed password, including two aspects, one is the determination of the account, to determine the account that issued the command; the other is the determination of the password content, and the judgment of the payment end and the payment end. Whether the passwords are consistent;
  • Step 5 The server returns the verification result to the client: if the authentication fails, the verification fails; if the password authentication succeeds, the verification succeeds, and the voice is recorded as a memo of the verification;
  • Step 6 Verification ends.
  • FIG. 8 is a flowchart of voice-based verification in the present invention, and the specific implementation steps are as follows:
  • Step 801 The terminal user initiates a verification operation.
  • Step 802 The user speaks the voice password on the spot, and after receiving the voice password, the payment terminal and the payment terminal simultaneously encode the password and send the password to the server;
  • Step 803 After receiving the voice password, the server performs decoding of the password.
  • Step 804 The server authenticates the parsed password, including two aspects, one is the determination of the account, to determine the account that issued the command; the other is the determination of the password content, and the judgment of the payment end and the payment end. Whether the passwords are consistent;
  • Step 805 The server returns the verification result to the client: if the authentication fails, the verification fails; if the password authentication succeeds, the verification succeeds, and the voice is recorded as a memo for the verification;
  • Step 806 The verification ends.
  • modules or steps of the present invention described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
  • the steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module.
  • the invention is not limited to any specific combination of hardware and software.
  • the technical solution provided by the embodiment of the present invention may be applied to the payment process of the terminal, and the first to-be-verified command sent by the payment terminal and the second to-be-verified command sent by the payment terminal are received in the payment process; Determining whether the first to-be-verified instruction is the same as the second to-be-verified instruction; transmitting the verification result to the payment terminal and/or the payment terminal.
  • the embodiment of the invention solves the problem that the verification method is not safe enough and brings about security risks, thereby achieving the effect of improving the security of the verification mode.

Landscapes

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

Abstract

一种支付验证方法、装置及系统，该方法包括：采用在支付过程中，接收支付终端发送的第一待验证指令与收款终端发送的第二待验证指令（S102）；依据预设条件判断所述第一待验证指令与所述第二待验证指令是否相同（S104）；将验证结果发送至所述支付终端和/或所述收款终端（S106）。采用上述技术方案，解决了相关技术中验证方式不够安全，带来的安全隐患的问题，进而达到了提升验证方式的安全性的效果。

Description

支付验证方法、装置及系统 技术领域
本发明涉及通信领域，具体而言，涉及一种支付验证方法、装置及系统。
背景技术
随着移动互联网的发展，手机的功能的越来越强大，各种应用软件也是丰富多彩，其中，各种应用软件其所包含的功能更是遍布到了生活中的方方面面，与人们的生活联系越来越紧密，并且各种应用软件所提供的服务已经成为人们日常生活不可缺少的部分。
由于手机上的应用大多与身份验证相关，比如网购、支付、身份验证、账户登录等，均需要验证用户的身份，为确保操作的安全性，目前大多数情况下采用的是密码验证的方法，这种方法比较传统，使用也非常广泛，但是如果密码一旦被破解，或者被他人知晓，那么别人就可以轻而易举的通过验证，直接进行支付或者转账，对用户的财产、个人数据安全等造成极大的威胁和伤害，并带来严重的后果。由于用户为了账户安全，往往需要设置复杂的密码，以降低被破解的可能性，但是在每次验证时都需要输入这个复杂的密码，操作起来比较麻烦，使用起来也非常不方便。
除此之外，现场支付时大多通过现金支付或者刷卡支付的方式，如果现金支付，需要准备零钱或者商家找零；如果刷卡支付，需要通过POS机刷卡，输入密码在生成的账单上进行签字，操作起来不仅耗时而且步骤繁琐。另外如果没有记录消费明细的话，时间一久用户很有可能记不起来具体购买了哪些东西，财务管理起来也就极为不方便。
基于目前的这种验证方式，需要一种更为安全、方便、快捷的验证方式，解决目前的验证方式不够安全，带来的安全隐患的问题。
针对现有技术中验证方式不够安全，带来的安全隐患的问题，目前尚未提出有效的解决方案。
发明内容
本发明实施例提供了一种支付验证方法、装置及系统，以至少解决现有技术中验证方式不够安全，带来的安全隐患的问题。
根据本发明的一个实施例，提供了一种支付验证方法，包括：
在支付过程中，接收支付终端发送的第一待验证指令与收款终端发送的第二待验证指令；依据预设条件判断第一待验证指令与第二待验证指令是否相同；将验证结果发送至支付终端和/或收款终端。
在本发明实施例中，第一待验证指令包括以下至少之一：用户特征信息、支付账号信息；第二待验证指令包括以下至少之一：用户特征信息、收款终端信息。
在本发明实施例中，用户特征信息包括以下至少之一：语音、面部特征、视网膜信息；和或，支付账号信息包括：账号；和/或，收款终端信息包括以下至少之一：收款终端ID、账单信息。
在本发明实施例中，通过以下方式之一，依据预设条件判断第一待验证指令与第二待验证指令是否相同，包括：方式一，依据预设条件中预先存储的支付终端的支付账号信息判断是否与第一待验证指令中的支付账号信息相同；并依据预设条件中预先存储的支付终端的用户特征信息，判断第一待验证指令中的用户特征信息和第二待验证指令中的用户特征信息是否相同；方式二，依据预设条件中预先存储的支付终端的支付账号信息，判断是否与第一待验证指令中的支付账号信息相同；并依据预设条件中预先存储的支付终端的用户特征信息，判断第一待验证指令中的用户特征信息是否与预先存储的用户特征信息相同，且判断第二待验证指令中的用户特征信息是否与预先存储的用户特征信息相同。
在本发明实施例中，通过以下方式之一，将验证结果发送至支付终端和/或收款终端，包括：在方式一或方式二中的判断结果均为相同的情况下，将验证成功的消息发送至支付终端和/或收款终端；在方式一或方式二中的至少之一判断结果为不同的情况下，将验证失败的消息发送至支付终端和/或收款终端。
在本发明实施例中，在将验证结果发送至支付终端和/或收款终端之前，还包括：依据第一待验证指令中的用户特征信息与支付账号信息，和第二待验证指令中的收款终端信息中的账单信息，生成消费明细；存储消费明细。
在本发明实施例中，在以下情况下，接收第一待验证指令和第二待验证指令：支付终端与收款终端预先建立支付连接。
根据本发明的一个方面，提供了另一种支付验证装置，包括：接收模块，设置为在支付过程中，接收支付终端发送的第一待验证指令与收款终端发送的第二待验证指令；判断模块，设置为依据预设条件判断接收模块接收的第一待验证指令与第二待验证指令是否相同；发送模块，设置为将判断模块得到的验证结果发送至支付终端和/或收款终端。
在本发明实施例中，判断模块，设置为通过以下方式之一，依据预设条件判断第 一待验证指令与第二待验证指令是否相同，包括：第一判断单元，设置为依据预设条件中预先存储的支付终端的支付账号信息判断是否与第一待验证指令中的支付账号信息相同；并依据预设条件中预先存储的支付终端的用户特征信息，判断第一待验证指令中的用户特征信息和第二待验证指令中的用户特征信息是否相同；第二判断单元，设置为依据预设条件中预先存储的支付终端的支付账号信息，判断是否与第一待验证指令中的支付账号信息相同；并依据预设条件中预先存储的支付终端的用户特征信息，判断第一待验证指令中的用户特征信息是否与预先存储的用户特征信息相同，且判断第二待验证指令中的用户特征信息是否与预先存储的用户特征信息相同。
在本发明实施例中，发送模块，设置为通过以下方式之一，将验证结果发送至支付终端和/或收款终端，包括：第一发送单元，设置为在第一判断单元或第二判断单元中的判断结果均为相同的情况下，将验证成功的消息发送至支付终端和/或收款终端；第二发送单元，设置为在第一判断单元或第二判断单元中的至少之一判断结果为不同的情况下，将验证失败的消息发送至支付终端和/或收款终端。
在本发明实施例中，装置还包括：生成模块，设置为在将验证结果发送至支付终端和/或收款终端之前，依据第一待验证指令中的用户特征信息与支付账号信息，和第二待验证指令中的收款终端信息中的账单信息，生成消费明细；存储模块，设置为存储生成模块生成的消费明细。
根据本发明的一个实施例，提供了另一种支付验证系统，包括：服务器、支付终端和收款终端，其中，服务器与支付终端和收款终端之间建立通信连接，设置为接收支付终端发送的第一待验证指令，和收款终端发送的第二待验证指令，并依据预设条件判断第一待验证指令与第二待验证指令是否相同，向支付终端和/或收款终端发送验证结果；服务器为上述任一所述的支付验证装置。
通过本发明实施例，采用在支付过程中，接收支付终端发送的第一待验证指令与收款终端发送的第二待验证指令；依据预设条件判断第一待验证指令与第二待验证指令是否相同；将验证结果发送至支付终端和/或收款终端。解决了验证方式不够安全，带来的安全隐患的问题，进而达到了提升验证方式的安全性的效果。
附图说明
此处所说明的附图用来提供对本发明的进一步理解，构成本申请的一部分，本发明的示意性实施例及其说明用于解释本发明，并不构成对本发明的不当限定。在附图中：
图1是根据本发明实施例的支付验证方法的流程图；
图2是根据本发明实施例的支付验证方法的信息交互流程图；
图3是根据本发明实施例的支付验证装置的结构框图；
图4是根据本发明优选实施例的支付验证装置的结构框图；
图5是根据本发明优选实施例的支付验证装置的另一结构框图；
图6是根据本发明实施例的支付验证装置的另一结构框图；
图7是根据本发明实施例的支付验证系统的结构图；
图8为本发明中的基于语音的验证流程图。
具体实施方式
下文中将参考附图并结合实施例来详细说明本发明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。
实施例一
在本实施例中提供了一种支付验证方法，图1是根据本发明实施例的支付验证方法的流程图，如图1所示，该流程包括如下步骤：
步骤S102，在支付过程中，接收支付终端发送的第一待验证指令与收款终端发送的第二待验证指令；
步骤S104，依据预设条件判断第一待验证指令与第二待验证指令是否相同；
步骤S106，将验证结果发送至支付终端和/或收款终端。
通过上述步骤，采用在支付过程中，接收支付终端发送的第一待验证指令与收款终端发送的第二待验证指令；依据预设条件判断第一待验证指令与第二待验证指令是否相同；将验证结果发送至支付终端和/或收款终端。解决了验证方式不够安全，带来的安全隐患的问题，进而达到了提升验证方式的安全性的效果。
由上可知，支付终端包括以下至少之一：智能手机、平板电脑、MP3、MP4、掌上电脑；收款终端包括以下至少之一：POS机、收银机。本发明实施例提供的支付验证方法适用于服务器中，本发明实施例中的支付终端以智能手机为例，收款终端以收银机为例进行说明，
例如，在支付过程中，服务器接收到智能手机上报的第一待验证指令，和收银机 上报的第二待验证指令，其中，智能手机在上报待验证指令时，通过支付客户端采集用户特征，结合支付客户端的账号信息生成第一待验证指令；收银机在上报待验证指令时，采集用户特征，结合收银机存储的ID和账单信息生成第二待验证指令；在比对第一待验证指令与第二待验证指令是否相同时，通过服务器中的预设条件判断第一待验证指令与第二待验证指令是否相同，从而得到验证结果。
综上可知，在支付验证的过程中对比现有的密码验证和手势验证，通过对用户特征的验证，节省了密码输入过程和手势输入验证的过程，提高了支付效率；并且由于密码输入和手势输入的过程中容易处在输错的情况，通过对用户特征的验证，提高了支付验证的正确率；进一步的，由于用户特征具备独一性，在信息安全上更具备可靠性，从而提高了支付验证的安全性。
在本发明实施例中，第一待验证指令包括以下至少之一：用户特征信息、支付账号信息；第二待验证指令包括以下至少之一：用户特征信息、收款终端信息。
在本发明实施例中，用户特征信息包括以下至少之一：语音、面部特征、视网膜信息；和或，支付账号信息包括：账号；和/或，收款终端信息包括以下至少之一：收款终端ID、账单信息。
这里结合步骤S102至步骤S106，用户特征可以为语音、面部特征、视网膜信息中的一种，收款终端信息中的收款终端ID可以为在服务器端预先存储的收银机所属的ID或关联的账户，账单信息可以为当前使用支付终端的用户的购买清单。
例如，仍旧以上述为例，其中，用户特征以语音为例进行说明，存在一个使用智能手机的用户A。在支付过程中，服务器接收支付终端发送的第一待验证指令与收款终端发送的第二待验证指令具体如下：
服务器接收到的第一待验证指令和第二待验证指令分别通过以下方式得到：
第一待验证指令：智能手机通过采集用户A的语音，将用户A的语音连同智能手机支付客户端的账号，通过封装得到第一待验证指令，并将第一待验证指令发送至服务器；
与此同时，第二待验证指令：由于智能手机预先与收银机建立了支付连接，在智能手机采集用户A语音的同时，收银机也通过配置的麦克采集用户A的语音，并将用户A的购买清单的结算总数和收音机的ID连同采集到的用户A的语音发送至服务器。
在本发明实施例中，步骤S104，通过以下方式之一，依据预设条件判断第一待验证指令与第二待验证指令是否相同，包括：
方式一，依据预设条件中预先存储的支付终端的支付账号信息判断是否与第一待 验证指令中的支付账号信息相同；并依据预设条件中预先存储的支付终端的用户特征信息，判断第一待验证指令中的用户特征信息和第二待验证指令中的用户特征信息是否相同；
例如，仍以上述用户A为例进行说明，服务器端存储有用户A所使用的智能手机中支付客户端的账号以及语音验证指令，故在验证第一待验证指令和第二待验证指令时：
Step1.服务器将第一待验证指令中的支付账号信息中的账号与预先存储的账号进行对比，以确保接收到的账号是同一账号对应的账户支付；
Step2.服务器将第一待验证指令中携带的语音和第二待验证指令中携带的语音，与预先存储的语音验证指令的音色进行对比，以确保当前使用Step1的账户的用户为同一用户A。
方式二，依据预设条件中预先存储的支付终端的支付账号信息，判断是否与第一待验证指令中的支付账号信息相同；并依据预设条件中预先存储的支付终端的用户特征信息，判断第一待验证指令中的用户特征信息是否与预先存储的用户特征信息相同，且判断第二待验证指令中的用户特征信息是否与预先存储的用户特征信息相同。
Step1.服务器将第一待验证指令中的支付账号信息中的账号与预先存储的账号进行对比，以确保接收到的账号是同一账号对应的账户支付；
Step2.服务器将第一待验证指令中携带的语音的音色与内容和预先存储的语音验证指令的音色和内容进行对比，并将第二待验证指令中携带的语音的音色与内容和预先存储的语音验证指令的音色和内容进行对比，以确保当前使用Step1的账户的用户为同一用户A，并确保语音验证的准确率。
在本发明实施例中，步骤S106，通过以下方式之一，将验证结果发送至支付终端和/或收款终端，包括：
在方式一或方式二中的判断结果均为相同的情况下，将验证成功的消息发送至支付终端和/或收款终端；
如方式一或方式二所述的情况，以方式一为例进行说明，若方式一中的Step1和Step2的判断结果均为相同时，即验证通过，服务器将验证通过的消息发送至支付终端和/或收款终端。方式二同上，此处不再赘述。
在方式一或方式二中的至少之一判断结果为不同的情况下，将验证失败的消息发送至支付终端和/或收款终端。
如上所述，若方式一或方式二中的Step1和Step2只要其中任意一个验证得到的判断结果为不相同，则验证失败，服务器将验证失败的消息发送至支付终端和/或收款终端。
在本发明实施例中，在步骤S106将验证结果发送至支付终端和/或收款终端之前，还包括：
步骤S107，依据第一待验证指令中的用户特征信息与支付账号信息，和第二待验证指令中的收款终端信息中的账单信息，生成消费明细；
步骤S108，存储消费明细。
结合步骤S107和步骤S108，若验证成功，服务器将存储本次验证的明细，进一步生成消费明细，从而进行存储，以便用户A查询。
在本发明实施例中，在以下情况下，接收第一待验证指令和第二待验证指令：支付终端与收款终端预先建立支付连接。
图2是根据本发明实施例的支付验证方法的信息交互流程图，如图2所示，该信息交互流程如下：
步骤S201，支付终端与收款终端建立支付连接；
步骤S202，支付终端采集用户特征；
步骤S203，收款终端采集用户特征；
步骤S204，支付终端将采集到的用户特征连同支付账号生成第一待验证指令；
步骤S205，支付终端向服务器发送第一待验证指令；
步骤S206，收款终端将采集到的用户特征连同收款终端信息生成第二待验证指令；
步骤S207，收款终端向服务器发送第二待验证指令；
步骤S208，服务器接收支付终端发送的第一待验证指令和收款终端发送的第二待验证指令；
步骤S209，服务器依据预设条件判断第一待验证指令与第二待验证指令是否相同；
步骤S210，服务器将验证结果发送至支付终端和/或收款终端；
步骤S211，支付终端接收服务器发送的验证结果；
步骤S212，收款终端接收服务器发送的验证结果。
本发明实施例提供的一种支付验证方法以语音为例，面部特征或视网膜信息同语音验证方式，此处不再赘述，此外，除上述验证方式，还可以以人体特有的纹路作为验证指令，例如指纹，其验证方式与语音验证同，本发明实施例以实现一种支付验证方法为准，具体不做限定。
实施例二
在本实施例中还提供了一种支付验证装置，该装置用于实现上述实施例及优选实施方式，已经进行过说明的不再赘述。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图3是根据本发明实施例的支付验证装置的结构框图，如图3所示，该装置包括：接收模块32、判断模块34和发送模块36，其中，
接收模块32，设置为在支付过程中，接收支付终端发送的第一待验证指令与收款终端发送的第二待验证指令；
判断模块34，与接收模块32建立通信连接，设置为依据预设条件判断接收模块32接收的第一待验证指令与第二待验证指令是否相同；
发送模块36，与判断模块34建立通信连接，设置为将判断模块34得到的验证结果发送至支付终端和/或收款终端。
在本发明实施例中，图4是根据本发明优选实施例的支付验证装置的结构框图，如图4所示，判断模块34，设置为通过以下方式之一，依据预设条件判断第一待验证指令与第二待验证指令是否相同，包括：
第一判断单元341，设置为依据预设条件中预先存储的支付终端的支付账号信息判断是否与第一待验证指令中的支付账号信息相同；并依据预设条件中预先存储的支付终端的用户特征信息，判断第一待验证指令中的用户特征信息和第二待验证指令中的用户特征信息是否相同；
第二判断单元342，设置为依据预设条件中预先存储的支付终端的支付账号信息，判断是否与第一待验证指令中的支付账号信息相同；并依据预设条件中预先存储的支付终端的用户特征信息，判断第一待验证指令中的用户特征信息是否与预先存储的用户特征信息相同，且判断第二待验证指令中的用户特征信息是否与预先存储的用户特征信息相同。
在本发明实施例中，图5是根据本发明优选实施例的支付验证装置的结构框图，如图5所示，发送模块36，设置为通过以下方式之一，将验证结果发送至支付终端和/或收款终端，包括：
第一发送单元361，设置为在第一判断单元341或第二判断单元342中的判断结果均为相同的情况下，将验证成功的消息发送至支付终端和/或收款终端；
第二发送单元362，设置为在第一判断单元341或第二判断单元342中的至少之一判断结果为不同的情况下，将验证失败的消息发送至支付终端和/或收款终端。
在本发明实施例中，图6是根据本发明实施例的支付验证装置的结构框图，如图6所示，该装置除包括图3所示的所有模块外，还包括：生成模块38和存储模块40，其中，
生成模块38，设置为在将验证结果发送至支付终端和/或收款终端之前，依据第一待验证指令中的用户特征信息与支付账号信息，和第二待验证指令中的收款终端信息中的账单信息，生成消费明细；
存储模块40，与生成模块38建立连接关系，设置为存储生成模块38生成的消费明细。
实施例三
在本实施例中提供了一种支付验证系统，图7是根据本发明实施例的支付验证系统的结构图，如图7所示，该系统包括：服务器72、支付终端74和收款终端76，其中，
服务器72与支付终端74和收款终端76之间建立通信连接，设置为接收支付终端74发送的第一待验证指令，和收款终端76发送的第二待验证指令，并依据预设条件判断第一待验证指令与第二待验证指令是否相同，向支付终端74和/或收款终端76发送验证结果；
其中，服务器72为图3至图6任一所示的支付验证装置。
本发明实施例采用的是支付终端与收款终端同时录入语音口令，用来进行身份验证并进行支付的策略，即在用户进行支付时，现场口述随意的语音口令，手机终端与收款终端同时接收并将此语音口令发送至服务器，服务器侧对这些指令进行解析和鉴权处理，如果鉴权通过，则用户验证成功；如果鉴权不通过，则用户验证失败。
本发明实施例提供的方法主要包括如下步骤：
步骤1：终端用户发起验证操作；
步骤2：用户在现场说出语音口令，支付终端与收款终端接收该语音口令后，同时将此口令编码后发送到服务器；
步骤3：服务器收到语音口令后，进行口令的解码；
步骤4：服务器对解析后的口令进行鉴权，包括2个方面，一方面是账号的判定，用以确定是发出指令的账号；另一方面是口令内容的判定，判定支付端和收款端的口令是否一致；
步骤5：服务器将验证结果返回给客户端：鉴权不通过则验证失败；口令鉴权通过则验证成功，同时将该语音记录下来，作为本次验证的备忘；
步骤6：验证结束。
具体如下，图8为本发明中的基于语音的验证流程图，具体实施步骤如下：
步骤801：终端用户发起验证操作；
步骤802：用户在现场说出语音口令，支付终端与收款终端接收该语音口令后，同时将此口令编码后发送到服务器；
步骤803：服务器收到语音口令后，进行口令的解码；
步骤804：服务器对解析后的口令进行鉴权，包括2个方面，一方面是账号的判定，用以确定是发出指令的账号；另一方面是口令内容的判定，判定支付端和收款端的口令是否一致；
步骤805：服务器将验证结果返回给客户端：鉴权不通过则验证失败；口令鉴权通过则验证成功，同时将该语音记录下来，作为本交次验证的备忘；
步骤806：验证结束。
显然，本领域的技术人员应该明白，上述的本发明的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本发明不限制于任何特定的硬件和软件结合。
以上所述仅为本发明的优选实施例而已，并不用于限制本发明，对于本领域的技术人员来说，本发明可以有各种更改和变化。凡在本发明的精神和原则之内，所作的 任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。
工业实用性
本发明实施例提供的技术方案，可以应用于终端的支付过程中，采用在支付过程中，接收支付终端发送的第一待验证指令与收款终端发送的第二待验证指令；依据预设条件判断第一待验证指令与第二待验证指令是否相同；将验证结果发送至支付终端和/或收款终端。本发明实施例解决了验证方式不够安全，带来的安全隐患的问题，进而达到了提升验证方式的安全性的效果。

Claims (12)

  1. 一种支付验证方法，包括：
    在支付过程中，接收支付终端发送的第一待验证指令与收款终端发送的第二待验证指令；
    依据预设条件判断所述第一待验证指令与所述第二待验证指令是否相同；
    将验证结果发送至所述支付终端和/或所述收款终端。
  2. 根据权利要求1所述的方法，其中，
    所述第一待验证指令包括以下至少之一：用户特征信息、支付账号信息；
    所述第二待验证指令包括以下至少之一：用户特征信息、收款终端信息。
  3. 根据权利要求2所述的方法，其中，所述用户特征信息包括以下至少之一：语音、面部特征、视网膜信息；和或，所述支付账号信息包括：账号；和/或，所述收款终端信息包括以下至少之一：收款终端ID、账单信息。
  4. 根据权利要求2所述的方法，其中，通过以下方式之一，依据预设条件判断所述第一待验证指令与所述第二待验证指令是否相同，包括：
    方式一，依据预设条件中预先存储的所述支付终端的支付账号信息判断是否与所述第一待验证指令中的支付账号信息相同；并依据预设条件中预先存储的所述支付终端的用户特征信息，判断所述第一待验证指令中的用户特征信息和所述第二待验证指令中的用户特征信息是否相同；
    方式二，依据预设条件中预先存储的所述支付终端的支付账号信息，判断是否与所述第一待验证指令中的支付账号信息相同；并依据预设条件中预先存储的所述支付终端的用户特征信息，判断所述第一待验证指令中的用户特征信息是否与所述预先存储的用户特征信息相同，且判断所述第二待验证指令中的用户特征信息是否与所述预先存储的用户特征信息相同。
  5. 根据权利要求4所述的方法，其中，通过以下方式之一，将验证结果发送至所述支付终端和/或所述收款终端，包括：
    在方式一或方式二中的判断结果均为相同的情况下，将验证成功的消息发送至所述支付终端和/或所述收款终端；
    在方式一或方式二中的至少之一判断结果为不同的情况下，将验证失败的消息发送至所述支付终端和/或所述收款终端。
  6. 根据权利要求2所述的方法，其中，在将验证结果发送至所述支付终端和/或所述收 款终端之前，还包括：
    依据所述第一待验证指令中的用户特征信息与所述支付账号信息，和所述第二待验证指令中的收款终端信息中的账单信息，生成消费明细；
    存储所述消费明细。
  7. 根据权利要求1所述的方法，其中，在以下情况下，接收所述第一待验证指令和所述第二待验证指令：
    所述支付终端与所述收款终端预先建立支付连接。
  8. 一种支付验证装置，包括：
    接收模块，设置为在支付过程中，接收支付终端发送的第一待验证指令与收款终端发送的第二待验证指令；
    判断模块，设置为依据预设条件判断所述接收模块接收的所述第一待验证指令与所述第二待验证指令是否相同；
    发送模块，设置为将所述判断模块得到的验证结果发送至所述支付终端和/或所述收款终端。
  9. 根据权利要求8所述的装置，其中，所述判断模块，设置为通过以下方式之一，依据预设条件判断所述第一待验证指令与所述第二待验证指令是否相同，包括：
    第一判断单元，设置为依据预设条件中预先存储的所述支付终端的支付账号信息判断是否与所述第一待验证指令中的支付账号信息相同；并依据预设条件中预先存储的所述支付终端的用户特征信息，判断所述第一待验证指令中的用户特征信息和所述第二待验证指令中的用户特征信息是否相同；
    第二判断单元，设置为依据预设条件中预先存储的所述支付终端的支付账号信息，判断是否与所述第一待验证指令中的支付账号信息相同；并依据预设条件中预先存储的所述支付终端的用户特征信息，判断所述第一待验证指令中的用户特征信息是否与所述预先存储的用户特征信息相同，且判断所述第二待验证指令中的用户特征信息是否与所述预先存储的用户特征信息相同。
  10. 根据权利要求9所述的装置，其中，发送模块，设置为通过以下方式之一，将验证结果发送至所述支付终端和/或所述收款终端，包括：
    第一发送单元，设置为在所述第一判断单元或所述第二判断单元中的判断结果均为相同的情况下，将验证成功的消息发送至所述支付终端和/或所述收款终 端；
    第二发送单元，设置为在所述第一判断单元或所述第二判断单元中的至少之一判断结果为不同的情况下，将验证失败的消息发送至所述支付终端和/或所述收款终端。
  11. 根据权利要求8所述的装置，其中，所述装置还包括：
    生成模块，设置为在将验证结果发送至所述支付终端和/或所述收款终端之前，依据所述第一待验证指令中的用户特征信息与支付账号信息，和所述第二待验证指令中的收款终端信息中的账单信息，生成消费明细；
    存储模块，设置为存储所述生成模块生成的所述消费明细。
  12. 一种支付验证系统，包括：服务器、支付终端和收款终端，其中，
    所述服务器与所述支付终端和所述收款终端之间建立通信连接，设置为接收所述支付终端发送的第一待验证指令，和所述收款终端发送的第二待验证指令，并依据预设条件判断所述第一待验证指令与所述第二待验证指令是否相同，向所述支付终端和/或所述收款终端发送验证结果；
    所述服务器为权利要求8至权利要求11中任一项所述的支付验证装置。
PCT/CN2015/090461 2014-12-02 2015-09-23 支付验证方法、装置及系统 Ceased WO2016086708A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
JP2017528888A JP2017535893A (ja) 2014-12-02 2015-09-23 支払い検証方法、装置及びシステム
EP15865494.7A EP3229190A4 (en) 2014-12-02 2015-09-23 Payment verification method, apparatus and system
US15/532,923 US20170344992A1 (en) 2014-12-02 2015-09-23 Payment verification method, apparatus and system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410720880.XA CN105719130B (zh) 2014-12-02 2014-12-02 支付验证方法、装置及系统
CN201410720880.X 2014-12-02

Publications (1)

Publication Number Publication Date
WO2016086708A1 true WO2016086708A1 (zh) 2016-06-09

Family

ID=56090970

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/090461 Ceased WO2016086708A1 (zh) 2014-12-02 2015-09-23 支付验证方法、装置及系统

Country Status (5)

Country Link
US (1) US20170344992A1 (zh)
EP (1) EP3229190A4 (zh)
JP (1) JP2017535893A (zh)
CN (1) CN105719130B (zh)
WO (1) WO2016086708A1 (zh)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106257518A (zh) * 2016-07-25 2016-12-28 四川易想电子商务有限公司 一种口令支付方法
CN108960806A (zh) * 2017-05-17 2018-12-07 北京博瑞彤芸文化传播股份有限公司 支付处理方法
US10839060B1 (en) * 2019-08-27 2020-11-17 Capital One Services, Llc Techniques for multi-voice speech recognition commands
CN111709752A (zh) * 2020-05-28 2020-09-25 腾讯科技（深圳）有限公司 虚拟资源处理方法、装置、计算机可读介质及电子设备
CN116258489A (zh) * 2022-12-19 2023-06-13 深圳市中磁计算机技术有限公司 一种应用于pos机的安全支付方法

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103034942A (zh) * 2012-12-05 2013-04-10 北京奇虎科技有限公司 用于网络支付的方法及系统
CN103679452A (zh) * 2013-06-20 2014-03-26 腾讯科技（深圳）有限公司 支付验证方法、装置及系统
CN103957107A (zh) * 2014-05-19 2014-07-30 浙江维尔科技股份有限公司 一种身份验证方法及装置

Family Cites Families (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP3490350B2 (ja) * 1999-08-30 2004-01-26 沖電気工業株式会社 電子決済システム
JP2001306985A (ja) * 2000-04-25 2001-11-02 Oki Electric Ind Co Ltd 顧客の人体特徴を利用した決済システム
JP2001351032A (ja) * 2000-06-07 2001-12-21 Visual Technology Kk 携帯型通信装置を用いた決済方法および本人認証方法ならびにこれらの方法に用いる携帯型通信装置
JP2003099691A (ja) * 2001-09-26 2003-04-04 Omron Corp 利用者照合決済方法とそのシステム、照合サーバ及び決済装置
JP2007058475A (ja) * 2005-08-24 2007-03-08 Hitachi Omron Terminal Solutions Corp 決済用ファイル管理システムおよび決済用ファイル管理方法
JP2007079903A (ja) * 2005-09-14 2007-03-29 Nippon Telegr & Teleph Corp <Ntt> 認証システム、電子決済システム、決済端末、決済方法、決済プログラムおよび記録媒体
US20100211503A1 (en) * 2009-02-18 2010-08-19 Zvi Reiss Double Verified Transaction Device and Method
US9734495B2 (en) * 2009-06-02 2017-08-15 Qualcomm Incorporated Mobile commerce authentication and authorization systems
US8485442B2 (en) * 2009-07-02 2013-07-16 Biometric Payment Solutions Electronic transaction verification system with biometric authentication
US20140201537A1 (en) * 2011-09-27 2014-07-17 George P. Sampas Mobile device-based authentication with enhanced security measures providing feedback on a real time basis
CN102609836A (zh) * 2012-02-02 2012-07-25 言金刚 一种对码校验支付系统及方法
KR20140026844A (ko) * 2012-08-23 2014-03-06 삼성전자주식회사 디바이스로부터의 결제 요청을 인증하는 방법 및 시스템
CN102945578A (zh) * 2012-10-08 2013-02-27 守望者科技（北京）有限公司 混合收款终端及方法
US20140136419A1 (en) * 2012-11-09 2014-05-15 Keith Shoji Kiyohara Limited use tokens granting permission for biometric identity verification
WO2015002346A1 (ko) * 2013-07-01 2015-01-08 비씨카드 주식회사 카드 결제 방법 및 서버
CN103942676A (zh) * 2014-03-21 2014-07-23 深圳市讯鸿科技开发有限公司 移动支付方法和系统
US9384486B2 (en) * 2014-07-15 2016-07-05 Verizon Patent And Licensing Inc. Secure financial payment

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103034942A (zh) * 2012-12-05 2013-04-10 北京奇虎科技有限公司 用于网络支付的方法及系统
CN103679452A (zh) * 2013-06-20 2014-03-26 腾讯科技（深圳）有限公司 支付验证方法、装置及系统
CN103957107A (zh) * 2014-05-19 2014-07-30 浙江维尔科技股份有限公司 一种身份验证方法及装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3229190A4 *

Also Published As

Publication number Publication date
US20170344992A1 (en) 2017-11-30
JP2017535893A (ja) 2017-11-30
CN105719130A (zh) 2016-06-29
EP3229190A4 (en) 2018-05-23
CN105719130B (zh) 2020-07-31
EP3229190A1 (en) 2017-10-11

Similar Documents

Publication Publication Date Title
US11405380B2 (en) Systems and methods for using imaging to authenticate online users
US11880829B2 (en) Provisioning of access credentials using device codes
CN106575416B (zh) 用于向装置验证客户端的系统和方法
CN106664208B (zh) 使用安全传输协议建立信任的系统和方法
CN108804906B (zh) 一种用于应用登陆的系统和方法
US9613377B2 (en) Account provisioning authentication
CN104969528B (zh) 确定验证功能的查询系统和方法
CN102088353B (zh) 基于移动终端的双因子认证方法及系统
US20130219479A1 (en) Login Using QR Code
KR20210142180A (ko) 효율적인 챌린지-응답 인증을 위한 시스템 및 방법
US10489565B2 (en) Compromise alert and reissuance
CN102202300A (zh) 一种基于双通道的动态密码认证系统及方法
CN102906776A (zh) 一种用于用户和服务提供商之间双向认证的方法
WO2016086708A1 (zh) 支付验证方法、装置及系统
KR20240005724A (ko) 암호화 지원 스마트 카드를 통한 다단계 인증
CN104680371A (zh) 一种无卡交易处理方法和系统
CN103684796A (zh) 一种用户身份识别模块卡及个人身份认证方法
CN103544598A (zh) 一种金融交易安全认证系统
US20240242206A1 (en) User verification with digital tag
KR20150104667A (ko) 인증 방법
KR20140011522A (ko) 얼굴 인식을 이용한 전자 금융 거래 수행 방법 및 장치
EP4699074A1 (en) Dynamic encryption for secure personal identification number entry
CN117097508A (zh) Nft跨设备安全管理的方法和装置
HK1237157B (zh) 使用安全传输协议建立信任的系统和方法
HK1236268B (zh) 用於向装置验证客户端的系统和方法

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: 15865494

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2017528888

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 15532923

Country of ref document: US

REEP Request for entry into the european phase

Ref document number: 2015865494

Country of ref document: EP