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

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

Info

Publication number
WO2017088262A1
WO2017088262A1 PCT/CN2015/099617 CN2015099617W WO2017088262A1 WO 2017088262 A1 WO2017088262 A1 WO 2017088262A1 CN 2015099617 W CN2015099617 W CN 2015099617W WO 2017088262 A1 WO2017088262 A1 WO 2017088262A1
Authority
WO
WIPO (PCT)
Prior art keywords
payment
user equipment
verification
public key
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/CN2015/099617
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.)
Xiaomi Inc
Original Assignee
Xiaomi Inc
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 Xiaomi Inc filed Critical Xiaomi Inc
Priority to JP2016519995A priority Critical patent/JP6401784B2/ja
Priority to RU2016128502A priority patent/RU2652425C1/ru
Priority to KR1020167009689A priority patent/KR101918827B1/ko
Priority to MX2016005792A priority patent/MX383991B/es
Publication of WO2017088262A1 publication Critical patent/WO2017088262A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0861—Network architectures or network communication protocols for network security for authentication of entities using biometrical features, e.g. fingerprint, retina-scan
    • 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/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
    • 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/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]
    • G06Q20/3223—Realising banking transactions through 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/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]
    • G06Q20/3227—Aspects of commerce using mobile devices [M-devices] using secure elements embedded in 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/382—Payment protocols; Details thereof insuring higher security of transaction
    • G06Q20/3829—Payment protocols; Details thereof insuring higher security of transaction involving key management
    • 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/387—Payment using discounts or coupons
    • 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

Definitions

  • the present disclosure relates to the field of security technologies, and in particular, to a payment verification system, method, and apparatus.
  • biometric identification information With the development of security technology, the use of fingerprints, irises, sounds, etc. for biometric identification information has become simpler, and the use of biometric information such as fingerprints for payment has become more and more popular.
  • the Android system itself is in an unsafe environment.
  • the device manufacturer divides the mobile phone into two areas: TEE (Trusted Execution Environment) and REE (Rich Execution Environment).
  • TEE Trusted Execution Environment
  • REE Raich Execution Environment
  • the Android system is placed in the REE, and the storage and processing of sensitive data is completed in the TEE.
  • the protection of key data is realized at the hardware level. For example, the storage of information such as fingerprint information, the recognition of the fingerprint image, and the like are all performed by moving to the TEE.
  • the device manufacturer side needs to complete the following three things to ensure the identity verification of the party that initiated the payment request: the verification request is indeed from the authentic trusted device; the verification request is indeed from the authentic trusted application; verification The request does come from a truly authentic user.
  • the first two verification processes complete the opening of the payment function, and the last verification process ensures that the fingerprint payment function can be used normally.
  • the present disclosure provides a payment verification system, method and apparatus.
  • the present disclosure provides a payment verification system, the system comprising a device verification server and at least one payment verification server; the device verification server is configured to register a biometric information based payment function for the payment verification server; the device verification server is further used for When the user equipment activates the payment function, the user equipment is verified; when the user equipment activates the payment function, if the device verification server verifies the user equipment, the payment application running on the user equipment is verified, and After the payment application is verified, the payment function is activated for the user equipment; the payment verification service is provided.
  • the server is further configured to verify the payment request if a payment request of the user equipment is received.
  • the device verification server is configured to save the device public key of the user equipment, and when receiving the first payment provisioning request of the user equipment, according to the device of the user equipment
  • the public key performs verification on the first signature information carried by the first payment provisioning request, and sends a verification pass message to the payment verification server when the verification passes, the first signature information is used by the user equipment to use the device private key of the user equipment to the specific content. Signature is obtained.
  • the payment verification server is configured to receive an application public key uploaded by the user equipment, and save the user equipment when receiving the verification pass message sent by the device verification server Application public key;
  • the payment verification server is further configured to receive a second payment activation request that is carried by the user equipment and carries the user public key and the second signature information, and the second signature information is verified according to the application public key of the user equipment, and when the verification is passed, the user equipment is saved.
  • the user's public key, the second signature information is obtained by the user equipment to sign the specific content using the application private key of the user equipment.
  • the payment verification server is configured to verify the third signature information according to the user public key of the user equipment when receiving the payment request carrying the third signature information When the verification is passed, a payment request is executed.
  • system further includes a payment server for signaling transmission between the user equipment and the payment verification server.
  • the present disclosure provides a payment verification method, which is applied to the above payment verification system.
  • the method includes: the device verification server registers a biometric information-based payment function for the payment verification server; and the device verification server opens the payment at the user device.
  • the user equipment is authenticated; when the user authentication device passes the payment function, the device verification server verifies the payment application running on the user equipment, and after the payment application is verified, The user equipment activates the payment function; the payment verification server receives the payment request of the user equipment and verifies the payment request.
  • the device verification server when the user equipment enables the payment function, verifying the user equipment, including:
  • the device verification server saves the device public key of the user equipment, and when receiving the first payment provisioning request of the user equipment, verifies the first signature information carried by the first payment opening request according to the device public key of the user equipment, when When the verification is passed, the verification pass message is sent to the payment verification server, and the first signature information is obtained by the user equipment using the device private key of the user equipment to sign the specific content.
  • the payment verification server performs verification on the payment application running on the user equipment if the device verification server passes the verification of the user equipment when the user equipment activates the payment function.
  • the payment function for the user equipment includes:
  • the payment verification server receives the application public key uploaded by the user equipment, and saves the application public key of the user equipment when receiving the verification pass message sent by the device verification server;
  • the payment verification server receives the second payment activation request that is carried by the user equipment and carries the user public key and the second signature information, and verifies the second signature information according to the application public key of the user equipment.
  • the verification is passed, the user equipment of the user equipment is saved.
  • the second signature information is obtained by the user equipment by using the application private key of the user equipment to sign the specific content.
  • the payment verification server receives the payment request of the user equipment, and the verification of the payment request includes:
  • the payment verification server When receiving the payment request carrying the third signature information, the payment verification server verifies the third signature information according to the user private key of the user equipment, and when the verification passes, executes the payment request.
  • the payment request is transmitted by the payment server between the user device and the payment verification server.
  • the present disclosure provides a payment verification method, including:
  • the application public key sent by the user equipment is received, and the application public key of the user equipment is saved when receiving the verification pass message sent by the device verification server;
  • the second signature information is verified according to the application public key of the user equipment, and when the verification is passed, the user equipment of the user equipment is saved.
  • the second signature information is obtained by the user equipment by using the application private key of the user equipment to sign the specific content;
  • the third signature information Upon receiving the payment request carrying the third signature information, the third signature information is verified according to the user public key of the user equipment, and when the verification is passed, the payment request is executed, and the third signature information is specified by the user equipment using the user private key The content signature is obtained.
  • the present disclosure provides a payment verification apparatus, including:
  • a registration module configured to register a biometric information-based payment function on the device verification server
  • a receiving module configured to receive an application public key uploaded by the user equipment after the registration is successful
  • a saving module configured to save an application public key of the user equipment when receiving the verification pass message sent by the device verification server;
  • the verification module is configured to: when receiving the second payment opening request that carries the user public key and the second signature information uploaded by the user equipment, verify the second signature information according to the application public key of the user equipment, and when the verification succeeds, triggering
  • the saving module saves the user public key of the user equipment, and the second signature information is obtained by the user equipment using the application private key of the user equipment to sign the specific content;
  • the verification module is further configured to: according to the user public key pair of the user equipment, when receiving the payment request carrying the third signature information The third signature information is verified;
  • the processing module is configured to execute a payment request when the third signature information is verified to pass, and the third signature information is obtained by the user equipment to sign the specific content by using the user private key.
  • the present disclosure provides a payment verification apparatus, including:
  • a memory for storing instructions executable by the processor
  • processor is configured to:
  • the application public key sent by the user equipment is received, and the application public key of the user equipment is saved when receiving the verification pass message sent by the device verification server;
  • the second signature information is verified according to the application public key of the user equipment, and when the verification is passed, the user equipment of the user equipment is saved.
  • the second signature information is obtained by the user equipment by using the application private key of the user equipment to sign the specific content;
  • the third signature information Upon receiving the payment request carrying the third signature information, the third signature information is verified according to the user public key of the user equipment, and when the verification is passed, the payment request is executed, and the third signature information is specified by the user equipment using the user private key The content signature is obtained.
  • the disclosure opens the device verification server into an open platform, so that other payment verification servers can register the biometric information-based payment function on the open platform, and the device verification server on the device manufacturer side verifies the user device in the payment opening phase.
  • the payment verification server is independently responsible for verifying the application during the payment opening phase, and the payment verification server verifies the identity of the user in the payment phase, and not only improves the payment function but also ensures the stability of the payment system.
  • the scalability improves the support for third-party applications, and avoids the load pressure on the device verification server due to the extension of the payment function, and solves the problem of cost increase and security caused by the increase in the number of TAs.
  • FIG. 1 is an architectural diagram of a payment verification system, according to an exemplary embodiment.
  • FIG. 3 is a flowchart of a payment verification method according to an exemplary embodiment.
  • FIG. 4 is a block diagram of a payment verification apparatus, according to an exemplary embodiment.
  • FIG. 5 is a block diagram of a payment verification apparatus 500, according to an exemplary embodiment.
  • TEE Trusted Execution Environment
  • Secure World Secure World
  • Trusted OS Trusted Operating System
  • TEE Trusted Operating System
  • CA Cosmetic Application
  • the program running in REE refers to the Android software itself on the Android phone.
  • System TA System Trusted Application
  • System TA System Trusted Application
  • SP TA Service Provider Trusted Application
  • TA Service Provider Trusted Application
  • FIG. 1 is a block diagram of a payment verification system according to an exemplary embodiment. As shown in FIG. 1, the system includes a device verification server on the device manufacturer side and at least one payment verification server on the payment service providing side.
  • the device verification server is configured to register a biometric information-based payment function for the payment verification server; the device verification server is further configured to verify the user device when the user device activates the payment function.
  • the biometric identification information may be fingerprint information, iris information, facial features or sound features, and the biometric identification information may be used for various verification methods such as fingerprint recognition, iris recognition, face recognition, and vocal recognition.
  • the payment verification server is configured to: when the user equipment activates the payment function, if the device verification server verifies the user equipment, the payment application running on the user equipment is verified, and after the payment application is verified, the The user equipment activates the payment function; the payment verification server is further configured to verify the payment request if the payment request of the user equipment is received.
  • a payment verification server may provide a verification service for at least one payment application, which is not specifically limited in the embodiment of the present disclosure.
  • the user equipment may send any of the above requests to the payment server corresponding to the payment application, and then the payment server sends the verification request to the payment verification server for verification.
  • the payment verification server and the payment server may be two functional modules located on the same physical device, or may be located on different physical devices, which is not limited by the embodiment of the present disclosure.
  • the biometric identification client, the payment client, and the like can be run in the REE on the user equipment, and the user equipment can run the biometric TA corresponding to the biometric client on the TEE side, and also multiple payment The client runs with a corresponding payment TA to perform the verification process through the payment application and the payment service providing side during the payment process.
  • the user equipment is configured with a sensor for collecting the biometric information of the user, and the like.
  • the disclosure opens the device verification server into an open platform, so that other payment verification servers can register the biometric information-based payment function on the open platform, and the device verification server on the device manufacturer side verifies the user device in the payment opening phase.
  • the payment verification server is independently responsible for verifying the application during the payment opening phase, and the payment verification server verifies the identity of the user in the payment phase, and not only improves the payment function but also ensures the stability of the payment system.
  • the scalability improves the support for third-party applications, and avoids the load pressure on the device verification server due to the extension of the payment function, and solves the problem of cost increase and security caused by the increase in the number of TAs.
  • FIG. 2 is an interaction flowchart of an architecture diagram based on the foregoing payment verification system. Referring to FIG. 2, the interaction process specifically includes:
  • step 201 the device verification server registers a biometric information based payment function for the payment verification server.
  • the application operator can register on the device verification server, and the device verification server can open the biometric information-based payment function, so that the third party application registered on the server can use the payment function.
  • Trading For a payment application, the application operator can register on the device verification server, and the device verification server can open the biometric information-based payment function, so that the third party application registered on the server can use the payment function.
  • Trading For a payment application, the application operator can register on the device verification server, and the device verification server can open the biometric information-based payment function, so that the third party application registered on the server can use the payment function.
  • the device verification server can open the biometric information-based payment function, so that the third party application registered on the server can use the payment function.
  • step 202 the device verification server saves the device public key of the user device.
  • the user equipment has a public key and a private key, and the device public key of the user equipment can be saved to the device verification server before leaving the factory.
  • the pair of keys is strongly associated with the user equipment and is uniquely associated with the user equipment and can be used to verify the authenticity of the user equipment.
  • an application key pair and a user key pair may be generated based on a preset algorithm, the application key
  • the pair may include an application private key and an application public key
  • the user key pair may include a user private key and a user public key
  • the two key pairs may be used to verify the validity of the user data.
  • the device verification server when receiving the first payment initiation request of the user equipment, performs verification on the first signature information carried in the first payment activation request according to the device public key of the user equipment.
  • a signature information is obtained by the user equipment signing the specific content using the device private key of the user equipment.
  • the first payment activation request may be issued by the user via a payment application running on the user device, and the payment function needs to be activated before the user wants to use the payment application to perform the payment activity.
  • step 204 when the device verification server verifies the first signature information, the verification verification message is sent to the payment verification server.
  • the device verification server may decrypt the first signature information by using the device private key of the user equipment. If the decryption is successful, the first signature information is verified, and the first payment initiation request may be determined to be sent by the legal user equipment.
  • the payment authentication server can be authorized to save the application public key of the user device.
  • step 205 the payment verification server receives the application public key uploaded by the user equipment.
  • the user equipment may further carry the application public key of the user equipment in the first payment activation request. Therefore, when the payment verification server receives and forwards the first payment activation request, the user may extract the user.
  • the application's public key for the device may also be sent after the first payment initiation request is sent by the user equipment, which is not specifically limited in this embodiment of the disclosure.
  • step 204 and the step 205 may be performed at other timings, for example, the step 205 is performed first, and then executed. Step 204, or step 204 and step 205 occur simultaneously, that is, as long as the steps 204 and 205 are completed before the step 206, the embodiment of the present disclosure does not specifically limit this.
  • step 206 the payment verification server saves the application public key of the user equipment when receiving the verification pass message sent by the device verification server.
  • the payment verification server may be notified to save the application public key to verify the user equipment in the subsequent payment process.
  • the device verification server has saved the application public key of the user equipment on the payment verification server, and implements the payment of the device verification server and the payment service providing side of the device manufacturer side. Verify key exchange between servers to ensure communication security between the two.
  • step 207 the payment verification server receives a second payment activation request that is carried by the user equipment and carries the user public key and the second signature information, and the second signature information is used by the user equipment to use the user equipment's application private key to the specific content. Signature is obtained.
  • the second payment activation request may be sent by the user equipment after the first payment activation request, and the second payment activation request does not need to be sent to the device verification server, which is specifically used to enable the payment function of the user equipment on the payment verification server.
  • step 208 the payment verification server verifies the second signature information according to the application public key of the user equipment.
  • step 209 when the payment verification server verifies the second signature information, the user public key of the user equipment is saved.
  • the payment verification server can save the user public key of the user equipment, so that the subsequent payment process can be verified according to the user public key of the user equipment.
  • step 210 the payment verification server, when receiving the payment request carrying the third signature information, verifies the third signature information according to the user public key of the user equipment, and when the verification passes, executes the payment request.
  • the device verification server participation on the device manufacturer side is not required, but the payment request is sent by the payment client on the device, and after the biometric information verification is passed, the user device uses the user private key pair.
  • the payment verification server on the payment service providing side receives the payment request, and uses the user public key to verify the third signature information. If the verification is passed, the user identity is recognized and the payment request can be executed. To complete the payment process.
  • the disclosure opens the device verification server into an open platform, so that other payment verification servers can register the biometric information-based payment function on the open platform, and the device verification server on the device manufacturer side verifies the user device in the payment opening phase.
  • the payment verification server is independently responsible for verifying the application during the payment opening phase, and the payment verification server verifies the identity of the user in the payment phase, and not only improves the payment function but also ensures the stability of the payment system.
  • the scalability improves the support for third-party applications, and avoids the load pressure on the device verification server due to the extension of the payment function, and solves the problem of cost increase and security caused by the increase in the number of TAs.
  • the system architecture provided by the disclosure effectively regulates the server-side process of fingerprint payment, and better expands the support of the payment device by the user equipment such as the mobile phone from the server, and effectively reduces the pressure of the background server of the device manufacturer.
  • the top-level device authentication server in the system architecture not only ensures the stability of the service, but also has a large degree of concurrency, which ensures the stability of the interaction between the servers.
  • FIG. 3 is a flowchart of a payment verification method according to an exemplary embodiment. Referring to Figure 3, the method includes:
  • step 301 a biometric information based payment function is registered on the device verification server.
  • step 302 after the registration is successful, the application public key sent by the user equipment is received, and the device is received.
  • the authentication server sends a verification pass message, the application public key of the user equipment is saved.
  • step 303 when receiving the second payment activation request that is carried by the user equipment and carries the user public key and the second signature information, the second signature information is verified according to the application public key of the user equipment, and the verification is passed. And saving the user public key of the user equipment, where the second signature information is obtained by the user equipment using the application private key of the user equipment to sign the specific content.
  • step 304 when receiving the payment request carrying the third signature information, verifying the third signature information according to the user public key of the user equipment, and when the verification is passed, executing the payment request, the third signature information
  • the user device is signed by the user's private key using the user's private key.
  • the specific content may refer to the transaction information, the user information, and the like, which is not limited in the disclosure.
  • the specific content that is the object of the signature may be the same content, and may be different content according to the process in which it is located and the algorithm used.
  • FIG. 4 is a block diagram of a payment verification apparatus, according to an exemplary embodiment.
  • the apparatus includes a registration module 401, a receiving module 402, a saving module 403, a verification module 404, and a processing module 405.
  • a registration module 401 configured to register a biometric information-based payment function on the device verification server
  • the receiving module 402 is configured to: after the registration is successful, receive an application public key that is sent by the user equipment;
  • the saving module 403 is configured to save an application public key of the user equipment when receiving the verification pass message sent by the device verification server;
  • the verification module 404 is configured to verify the second signature information according to the application public key of the user equipment when receiving the second payment initiation request that is carried by the user equipment and carries the user public key and the second signature information, when the verification is performed. And transmitting, by the saving module, the user public key of the user equipment, where the second signature information is obtained by the user equipment by using the application private key of the user equipment to sign the specific content;
  • the verification module 404 is further configured to: when receiving the payment request carrying the third signature information, verify the third signature information according to the user public key of the user equipment;
  • the processing module 405 is configured to execute the payment request when the third signature information is verified, and the third signature information is obtained by the user equipment to sign the specific content by using the user private key.
  • FIG. 5 is a block diagram of a payment verification apparatus 500, according to an exemplary embodiment.
  • device 500 can be provided as a server.
  • apparatus 500 includes a processing component 522 that further includes one or more processors, and memory resources represented by memory 532 for storing instructions executable by processing component 522, such as Use the program.
  • An application stored in memory 532 can include one or more modules each corresponding to a set of instructions.
  • processing component 522 is configured to execute instructions to perform the payment verification method described above.
  • Apparatus 500 can also include a power supply component 526 configured to perform power management of apparatus 500, a wired or wireless network interface 550 configured to connect apparatus 500 to the network, and an input/output (I/O) interface 558.
  • Device 500 can operate based on an operating system stored in the memory 532, such as Windows Server TM, Mac OS X TM , Unix TM, Linux TM, FreeBSD TM or the like.

Landscapes

  • Business, Economics & Management (AREA)
  • Engineering & Computer Science (AREA)
  • Accounting & Taxation (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Strategic Management (AREA)
  • Finance (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Health & Medical Sciences (AREA)
  • Biomedical Technology (AREA)
  • General Health & Medical Sciences (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Abstract

本公开提供了一种支付验证系统、方法及装置，属于安全技术领域。所述方法包括：所述系统包括设备验证服务器和至少一个支付验证服务器。本公开通过将设备验证服务器开放成一个开放平台，使得其他支付验证服务器可以在该开放平台上注册基于生物识别信息的支付功能，由设备厂商侧的设备验证服务器在支付开通阶段对用户设备进行验证，而由支付验证服务器独立负责在该支付开通阶段对应用进行验证，并由支付验证服务器在支付阶段对用户的身份进行验证，在保证支付系统的稳定性的前提下，不仅提高了支付功能的拓展性，而且避免了由于支付功能扩展对设备验证服务器的负载压力。

Description

支付验证系统、方法及装置
本申请基于申请号为201510818893.5、申请日为2015年11月23日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此引入本申请作为参考。
技术领域
本公开涉及安全技术领域，尤其涉及一种支付验证系统、方法及装置。
背景技术
随着安全技术的发展，用户使用指纹、虹膜、声音等进行生物识别信息也变得简单起来，而利用指纹等生物信息识别来进行支付的行为越来越多。
从软件层面来讲，Android系统本身则是处在一个不安全的环境里。为了解决手机中普通操作系统容易被攻击的问题，设备厂商在硬件层面将手机分为了TEE(Trusted Execution Environment，可信执行环境)和REE(Rich Execution Environment，不安全的执行环境)两块区域。在安卓Android手机上，将Android系统放在了REE里，在TEE里完成对敏感数据的存储和处理，依赖这项技术，在硬件级别实现对关键数据的保护。例如指纹信息等信息的存储，对指纹图像的识别等，将全部迁移到TEE中来进行。
在相关技术中，设备厂商侧需要完成以下三件事情，来保证对发起支付请求的一方的身份验证：验证请求确实来自于真实可信的设备；验证请求确实来自于真实可信的应用；验证请求确实来自于真实可信的用户。前两个验证过程完成支付功能的开通，最后一个验证过程保证指纹支付功能能够正常使用。
上述验证过程，当设备数量以及支付应用的用户数大量增加时，设备厂商侧的服务器会面临巨大的并发访问量，对服务器的负载能力是个极大的考验。
发明内容
本公开提供一种支付验证系统、方法及装置。
第一方面，本公开提供了一种支付验证系统，系统包括设备验证服务器和至少一个支付验证服务器；设备验证服务器用于为支付验证服务器注册基于生物识别信息的支付功能；设备验证服务器还用于在用户设备开通支付功能时，对用户设备进行验证；支付验证服务器用于在用户设备开通支付功能时，如果设备验证服务器对用户设备验证通过，对用户设备上运行的支付应用进行验证，并在支付应用验证通过后，为用户设备开通支付功能；支付验证服 务器还用于如果接收到用户设备的支付请求，对支付请求进行验证。
结合第一方面，在第一方面的第一种可能实现方式中，设备验证服务器用于保存用户设备的设备公钥，并在接收到用户设备的第一支付开通请求时，根据用户设备的设备公钥，对第一支付开通请求所携带的第一签名信息进行验证，当验证通过时，向支付验证服务器发送验证通过消息，第一签名信息由用户设备使用用户设备的设备私钥对特定内容签名得到。
结合第一方面，在第一方面的第二种可能实现方式中，支付验证服务器用于接收用户设备上传的应用公钥，并在接收到设备验证服务器发送的验证通过消息时，保存用户设备的应用公钥；
支付验证服务器还用于接收用户设备上传的携带用户公钥和第二签名信息的第二支付开通请求，根据用户设备的应用公钥对第二签名信息进行验证，当验证通过时，保存用户设备的用户公钥，第二签名信息由用户设备使用用户设备的应用私钥对特定内容签名得到。
结合第一方面，在第一方面的第三种可能实现方式中，支付验证服务器用于在接收到携带第三签名信息的支付请求时，根据用户设备的用户公钥对第三签名信息进行验证，当验证通过时，执行支付请求。
结合第一方面，在第一方面的第四种可能实现方式中，系统还包括支付服务器，支付服务器用于在用户设备和支付验证服务器之间进行信令传输。
第二方面，本公开提供了一种支付验证方法，应用于权利要求上述支付验证系统，方法包括：设备验证服务器为支付验证服务器注册基于生物识别信息的支付功能；设备验证服务器在用户设备开通支付功能时，对用户设备进行验证；支付验证服务器在用户设备开通支付功能时，如果设备验证服务器对用户设备验证通过，对用户设备上运行的支付应用进行验证，并在支付应用验证通过后，为用户设备开通支付功能；支付验证服务器在接收到用户设备的支付请求，对支付请求进行验证。
结合第二方面，在第二方面的第一种可能实现方式中，设备验证服务器在用户设备开通支付功能时，对用户设备进行验证包括：
设备验证服务器保存用户设备的设备公钥，并在接收到用户设备的第一支付开通请求时，根据用户设备的设备公钥，对第一支付开通请求所携带的第一签名信息进行验证，当验证通过时，向支付验证服务器发送验证通过消息，第一签名信息由用户设备使用用户设备的设备私钥对特定内容签名得到。
结合第二方面，在第二方面的第二种可能实现方式中，支付验证服务器在用户设备开通支付功能时，如果设备验证服务器对用户设备验证通过，对用户设备上运行的支付应用进行验证，并在支付应用验证通过后，为用户设备开通支付功能包括：
支付验证服务器接收用户设备上传的应用公钥，并在接收到设备验证服务器发送的验证通过消息时，保存用户设备的应用公钥；
支付验证服务器接收用户设备上传的携带用户公钥和第二签名信息的第二支付开通请求，根据用户设备的应用公钥对第二签名信息进行验证，当验证通过时，保存用户设备的用户公钥，第二签名信息由用户设备使用用户设备的应用私钥对特定内容签名得到。
结合第二方面，在第二方面的第三可能实现方式中，支付验证服务器在接收到用户设备的支付请求，对支付请求进行验证包括：
支付验证服务器在接收到携带第三签名信息的支付请求时，根据用户设备的用户私钥对第三签名信息进行验证，当验证通过时，执行支付请求。
结合第二方面，在第二方面的第四种可能实现方式中，支付请求由支付服务器在用户设备和支付验证服务器之间进行传输。
第三方面，本公开提供了一种支付验证方法，包括：
在设备验证服务器上注册基于生物识别信息的支付功能；
在注册成功后，接收用户设备发上传的应用公钥，并在接收到设备验证服务器发送的验证通过消息时，保存用户设备的应用公钥；
在接收到用户设备上传的携带用户公钥和第二签名信息的第二支付开通请求时，根据用户设备的应用公钥对第二签名信息进行验证，当验证通过时，保存用户设备的用户公钥，第二签名信息由用户设备使用用户设备的应用私钥对特定内容签名得到；
在接收到携带第三签名信息的支付请求时，根据用户设备的用户公钥对第三签名信息进行验证，当验证通过时，执行支付请求，第三签名信息由用户设备使用用户私钥对特定内容签名得到。
第四方面，本公开提供了一种支付验证装置，包括：
注册模块，用于在设备验证服务器上注册基于生物识别信息的支付功能；
接收模块，用于在注册成功后，接收用户设备发上传的应用公钥；
保存模块，用于在接收到设备验证服务器发送的验证通过消息时，保存用户设备的应用公钥；
验证模块，用于在接收到用户设备上传的携带用户公钥和第二签名信息的第二支付开通请求时，根据用户设备的应用公钥对第二签名信息进行验证，当验证通过时，触发保存模块保存用户设备的用户公钥，第二签名信息由用户设备使用用户设备的应用私钥对特定内容签名得到；
验证模块还用于在接收到携带第三签名信息的支付请求时，根据用户设备的用户公钥对 第三签名信息进行验证；
处理模块，用于当对第三签名信息验证通过时，执行支付请求，第三签名信息由用户设备使用用户私钥对特定内容签名得到。
第五方面，本公开提供了一种支付验证装置，包括：
处理器；
用于存储处理器可执行的指令的存储器；
其中，处理器被配置为：
在设备验证服务器上注册基于生物识别信息的支付功能；
在注册成功后，接收用户设备发上传的应用公钥，并在接收到设备验证服务器发送的验证通过消息时，保存用户设备的应用公钥；
在接收到用户设备上传的携带用户公钥和第二签名信息的第二支付开通请求时，根据用户设备的应用公钥对第二签名信息进行验证，当验证通过时，保存用户设备的用户公钥，第二签名信息由用户设备使用用户设备的应用私钥对特定内容签名得到；
在接收到携带第三签名信息的支付请求时，根据用户设备的用户公钥对第三签名信息进行验证，当验证通过时，执行支付请求，第三签名信息由用户设备使用用户私钥对特定内容签名得到。
本公开的实施例提供的技术方案可以包括以下有益效果：
本公开通过将设备验证服务器开放成一个开放平台，使得其他支付验证服务器可以在该开放平台上注册基于生物识别信息的支付功能，由设备厂商侧的设备验证服务器在支付开通阶段对用户设备进行验证，而由支付验证服务器独立负责在该支付开通阶段对应用进行验证，并由支付验证服务器在支付阶段对用户的身份进行验证，在保证支付系统的稳定性的前提下，不仅提高了支付功能的拓展性，提高了对第三方应用的支持能力，而且避免了由于支付功能扩展对设备验证服务器的负载压力，并解决了由于TA数量增加造成的成本升高问题和安全性问题。
应当理解的是，以上的一般描述和后文的细节描述仅是示例性和解释性的，并不能限制本公开。
附图说明
此处的附图被并入说明书中并构成本说明书的一部分，示出了符合本公开的实施例，并与说明书一起用于解释本公开的原理。
图1是根据一示例性实施例示出的一种支付验证系统的架构图。
图2是基于上述支付验证系统的架构图的交互流程图。
图3是根据一示例性实施例示出的一种支付验证方法的流程图。
图4是根据一示例性实施例示出的一种支付验证装置框图。
图5是根据一示例性实施例示出的一种支付验证装置500的框图。
具体实施方式
为使本公开的目的、技术方案和优点更加清楚，下面将结合附图对本公开实施方式作进一步地详细描述。
这里将详细地对示例性实施例进行说明，其示例表示在附图中。下面的描述涉及附图时，除非另有表示，不同附图中的相同数字表示相同或相似的要素。以下示例性实施例中所描述的实施方式并不代表与本公开相一致的所有实施方式。相反，它们仅是与如所附权利要求书中所详述的、本公开的一些方面相一致的装置和方法的例子。
TEE(Trusted Execution Environment，可信执行环境)是指安全的执行环境，也称为Secure World。
REE(Rich Execution Environment，不安全的执行环境)，也叫Normal World或Non-Secure World。
Trusted OS(Trusted Operating System，可信的操作系统)，运行于TEE。在安卓手机上与Android系统并行运行与手机芯片上。
CA(Client Application)，REE中运行的程序，在Android手机上指的是Android软件本身。
System TA(System Trusted Application，系统级TA)，需要用系统密钥进行签名，以预装的形式在手机出厂前放置到手机对应的目录。
SP TA(Service Provider Trusted Application，应用服务级TA)，第三方开发的TA，需要使用SP密钥进行签名，后期可以通过下载的方式放置在手机的对应目录。
图1是根据一示例性实施例示出的一种支付验证系统的架构图，如图1所示，该系统包括设备厂商侧的设备验证服务器和支付服务提供侧的至少一个支付验证服务器。
该设备验证服务器用于为该支付验证服务器注册基于生物识别信息的支付功能；该设备验证服务器还用于在用户设备开通该支付功能时，对该用户设备进行验证。
其中，该生物识别信息可以为指纹信息、虹膜信息、脸部特征或声音特征等，该生物识别信息可以用于指纹识别、虹膜识别、人脸识别以及人声识别等多种验证方式。
该支付验证服务器用于在用户设备开通该支付功能时，如果该设备验证服务器对该用户设备验证通过，对该用户设备上运行的支付应用进行验证，并在该支付应用验证通过后，为该用户设备开通该支付功能；该支付验证服务器还用于如果接收到该用户设备的支付请求，对该支付请求进行验证。
一个支付验证服务器可以为至少一个支付应用提供验证服务，本公开实施例对此不做具体限定。而对于来自用户设备的支付请求或开通支付功能请求，用户设备可以将上述任一请求发送至支付应用对应的支付服务器，再由支付服务器发送至支付验证服务器进行验证。当然，该支付验证服务器和支付服务器可以是位于同一物理设备上的两个功能模块，或位于不同物理设备上，本公开实施例对此不做限定。
在用户设备侧，用户设备上可以在REE中运行有生物识别客户端、支付客户端等，而用户设备可以在TEE侧运行有与生物识别客户端对应的生物识别TA，而还为多个支付客户端运行有相应的支付TA，以便在支付过程中通过支付应用与支付服务提供侧进行验证过程。当然，对于用户设备来说，该用户设备上配置有用于采集用户的生物识别信息的传感器等，本公开实施例对此不作限定。
本公开通过将设备验证服务器开放成一个开放平台，使得其他支付验证服务器可以在该开放平台上注册基于生物识别信息的支付功能，由设备厂商侧的设备验证服务器在支付开通阶段对用户设备进行验证，而由支付验证服务器独立负责在该支付开通阶段对应用进行验证，并由支付验证服务器在支付阶段对用户的身份进行验证，在保证支付系统的稳定性的前提下，不仅提高了支付功能的拓展性，提高了对第三方应用的支持能力，而且避免了由于支付功能扩展对设备验证服务器的负载压力，并解决了由于TA数量增加造成的成本升高问题和安全性问题。
图2是基于上述支付验证系统的架构图的交互流程图，参见图2，该交互流程具体包括：
在步骤201中，设备验证服务器为该支付验证服务器注册基于生物识别信息的支付功能。
对于一个支付应用来说，可以由应用运营商在设备验证服务器上进行注册，该设备验证服务器可以开放基于生物识别信息的支付功能，使得在该服务器上进行注册的第三方应用可以使用该支付功能进行交易。
在步骤202中，设备验证服务器保存用户设备的设备公钥。
该用户设备具备公钥和私钥，该用户设备的设备公钥可以在出厂前保存至该设备验证服务器。这对密钥与用户设备强关联，并且与该用户设备唯一相关，可以用于验证用户设备的真实性。用户设备在出厂后，可以基于预设算法生成应用密钥对和用户密钥对，该应用密钥 对可以包括应用私钥和应用公钥，用户密钥对可以包括用户私钥和用户公钥，该两个密钥对可以用于验证用户数据的有效性。
在步骤203中，设备验证服务器在接收到该用户设备的第一支付开通请求时，根据该用户设备的设备公钥，对该第一支付开通请求所携带的第一签名信息进行验证，该第一签名信息由该用户设备使用该用户设备的设备私钥对特定内容签名得到。
该第一支付开通请求可以由用户通过运行于该用户设备上的支付应用发出，当用户想要使用该支付应用进行支付活动之前，需要激活支付功能。
在步骤204中，设备验证服务器对该第一签名信息验证通过时，向该支付验证服务器发送验证通过消息。
设备验证服务器可以采用用户设备的设备私钥对该第一签名信息进行解密，如果解密成功，则该第一签名信息验证通过，可以确定该第一支付开通请求确实为合法用户设备发送，此时，可以授权支付验证服务器保存用户设备的应用公钥。
在步骤205中，该支付验证服务器接收该用户设备上传的应用公钥。
用户设备在发送第一支付开通请求时，可以在第一支付开通请求中还携带该用户设备的应用公钥，因此，在支付验证服务器接收并转发该第一支付开通请求时，可以提取该用户设备的应用公钥。当然，该用户设备的应用公钥还可以在用户设备发出第一支付开通请求以后发送，本公开实施例对此不作具体限定。
需要说明的是，在本公开实施例中，仅以当前步骤时序为例进行说明，在实际场景中，该步骤204和步骤205也可以是以其他时序进行，如，先执行步骤205，再执行步骤204，或者，步骤204和步骤205同时发生，也即是，只要在步骤206之前，该步骤204和205均已完成即可，本公开实施例对此不做具体限定。
在步骤206中，该支付验证服务器在接收到该设备验证服务器发送的该验证通过消息时，保存该用户设备的应用公钥。
当设备验证服务器对用户设备验证通过后，可以通知该支付验证服务器将应用公钥保存下来，以便在后续支付过程中对用户设备进行验证。
通过上述步骤，可以看出，通过对用户设备的初步验证，设备验证服务器已经将用户设备的应用公钥保存于支付验证服务器上，实现了设备厂商侧的设备验证服务器与支付服务提供侧的支付验证服务器之间的密钥交换，保证了两者之间的通信安全。
在步骤207中，支付验证服务器接收该用户设备上传的携带用户公钥和第二签名信息的第二支付开通请求，该第二签名信息由该用户设备使用该用户设备的应用私钥对特定内容签名得到。
该第二支付开通请求可以是用户设备在第一支付开通请求之后发送，该第二支付开通请求无需再发送至设备验证服务器，其具体用于在支付验证服务器上开通该用户设备的支付功能。
在步骤208中，支付验证服务器根据该用户设备的应用公钥对该第二签名信息进行验证。
在步骤209中，支付验证服务器对该第二签名信息验证通过时，保存该用户设备的用户公钥。
经过上述验证过程，支付验证服务器可以保存有用户设备的用户公钥，从而可以根据该用户设备的用户公钥对后续支付过程进行验证。
在步骤210中，该支付验证服务器在接收到携带第三签名信息的支付请求时，根据该用户设备的用户公钥对该第三签名信息进行验证，当验证通过时，执行该支付请求。
通过上述过程，在支付过程中，就无需设备厂商侧的设备验证服务器的参与，而是由设备上的支付客户端发出支付请求，在进行生物识别信息验证通过后，用户设备使用用户私钥对特定内容进行签名，支付服务提供侧的支付验证服务器接收到支付请求时，使用用户公钥对第三签名信息进行验证，如果验证通过时，则认为该用户身份被认可，可以执行该支付请求，以完成支付流程。
本公开通过将设备验证服务器开放成一个开放平台，使得其他支付验证服务器可以在该开放平台上注册基于生物识别信息的支付功能，由设备厂商侧的设备验证服务器在支付开通阶段对用户设备进行验证，而由支付验证服务器独立负责在该支付开通阶段对应用进行验证，并由支付验证服务器在支付阶段对用户的身份进行验证，在保证支付系统的稳定性的前提下，不仅提高了支付功能的拓展性，提高了对第三方应用的支持能力，而且避免了由于支付功能扩展对设备验证服务器的负载压力，并解决了由于TA数量增加造成的成本升高问题和安全性问题。该公开提供的系统架构有效的规范指纹支付的服务端流程，并且从服务端更好的拓展了手机等用户设备对支付应用的支持，还能有效降低设备厂商的后台服务器压力。系统架构中最上层的设备验证服务器不仅能够保证业务的稳定性，还具有较大程度的并发能力，保证了服务器之间交互的稳定。
上述所有可选技术方案，可以采用任意结合形成本公开的可选实施例，在此不再一一赘述。
图3是根据一示例性实施例示出的一种支付验证方法的流程图。参见图3，该方法包括：
在步骤301中，在设备验证服务器上注册基于生物识别信息的支付功能。
在步骤302中，在注册成功后，接收用户设备发上传的应用公钥，并在接收到该设备验 证服务器发送的验证通过消息时，保存该用户设备的应用公钥。
在步骤303中，在接收到该用户设备上传的携带用户公钥和第二签名信息的第二支付开通请求时，根据该用户设备的应用公钥对该第二签名信息进行验证，当验证通过时，保存该用户设备的用户公钥，该第二签名信息由该用户设备使用该用户设备的应用私钥对特定内容签名得到。
在步骤304中，在接收到携带第三签名信息的支付请求时，根据该用户设备的用户公钥对该第三签名信息进行验证，当验证通过时，执行该支付请求，该第三签名信息由该用户设备使用用户私钥对特定内容签名得到。
需要说明的是，在上述实施例中，特定内容可以是指交易信息、用户信息等，本公开对此不作限定。且每次作为签名对象的特定内容可以是相同内容，也可以根据其所处流程以及所使用算法的不同，分别为不同内容，本公开实施例对此不做具体限定。
图4是根据一示例性实施例示出的一种支付验证装置框图。参照图2，该装置包括注册模块401，接收模块402，保存模块403，验证模块404和处理模块405。
注册模块401，用于在设备验证服务器上注册基于生物识别信息的支付功能；
接收模块402，用于在注册成功后，接收用户设备发上传的应用公钥；
保存模块403，用于在接收到该设备验证服务器发送的验证通过消息时，保存该用户设备的应用公钥；
验证模块404，用于在接收到该用户设备上传的携带用户公钥和第二签名信息的第二支付开通请求时，根据该用户设备的应用公钥对该第二签名信息进行验证，当验证通过时，触发该保存模块保存该用户设备的用户公钥，该第二签名信息由该用户设备使用该用户设备的应用私钥对特定内容签名得到；
该验证模块404还用于在接收到携带第三签名信息的支付请求时，根据该用户设备的用户公钥对该第三签名信息进行验证；
处理模块405，用于当对该第三签名信息验证通过时，执行该支付请求，该第三签名信息由该用户设备使用用户私钥对特定内容签名得到。
关于上述实施例中的装置，其中各个模块执行操作的具体方式已经在有关该方法的实施例中进行了详细描述，此处将不做详细阐述说明。
图5是根据一示例性实施例示出的一种支付验证装置500的框图。例如，装置500可以被提供为一服务器。参照图5，装置500包括处理组件522，其进一步包括一个或多个处理器，以及由存储器532所代表的存储器资源，用于存储可由处理部件522的执行的指令，例如应 用程序。存储器532中存储的应用程序可以包括一个或一个以上的每一个对应于一组指令的模块。此外，处理组件522被配置为执行指令，以执行上述支付验证方法。
装置500还可以包括一个电源组件526被配置为执行装置500的电源管理，一个有线或无线网络接口550被配置为将装置500连接到网络，和一个输入输出(I/O)接口558。装置500可以操作基于存储在存储器532的操作系统，例如Windows ServerTM，Mac OS XTM，UnixTM,LinuxTM，FreeBSDTM或类似。
本领域技术人员在考虑说明书及实践这里公开的发明后，将容易想到本公开的其它实施方案。本申请旨在涵盖本公开的任何变型、用途或者适应性变化，这些变型、用途或者适应性变化遵循本公开的一般性原理并包括本公开未公开的本技术领域中的公知常识或惯用技术手段。说明书和实施例仅被视为示例性的，本公开的真正范围和精神由下面的权利要求指出。
应当理解的是，本公开并不局限于上面已经描述并在附图中示出的精确结构，并且可以在不脱离其范围进行各种修改和改变。本公开的范围仅由所附的权利要求来限制。

Claims (13)

  1. 一种支付验证系统，其特征在于，所述系统包括设备验证服务器和至少一个支付验证服务器；
    所述设备验证服务器用于为所述支付验证服务器注册基于生物识别信息的支付功能；
    所述设备验证服务器还用于在用户设备开通所述支付功能时，对所述用户设备进行验证；
    所述支付验证服务器用于在用户设备开通所述支付功能时，如果所述设备验证服务器对所述用户设备验证通过，对所述用户设备上运行的支付应用进行验证，并在所述支付应用验证通过后，为所述用户设备开通所述支付功能；
    所述支付验证服务器还用于如果接收到所述用户设备的支付请求，对所述支付请求进行验证。
  2. 根据权利要求1所述的系统，其特征在于，所述设备验证服务器用于保存用户设备的设备公钥，并在接收到所述用户设备的第一支付开通请求时，根据所述用户设备的设备公钥，对所述第一支付开通请求所携带的第一签名信息进行验证，当验证通过时，向所述支付验证服务器发送验证通过消息，所述第一签名信息由所述用户设备使用所述用户设备的设备私钥对特定内容签名得到。
  3. 根据权利要求1所述的系统，其特征在于，所述支付验证服务器用于接收所述用户设备上传的应用公钥，并在接收到所述设备验证服务器发送的所述验证通过消息时，保存所述用户设备的应用公钥；
    所述支付验证服务器还用于接收所述用户设备上传的携带用户公钥和第二签名信息的第二支付开通请求，根据所述用户设备的应用公钥对所述第二签名信息进行验证，当验证通过时，保存所述用户设备的用户公钥，所述第二签名信息由所述用户设备使用所述用户设备的应用私钥对特定内容签名得到。
  4. 根据权利要求1所述的系统，其特征在于，所述支付验证服务器用于在接收到携带第三签名信息的支付请求时，根据所述用户设备的用户公钥对所述第三签名信息进行验证，当验证通过时，执行所述支付请求。
  5. 根据权利要求1所述的系统，其特征在于，所述系统还包括支付服务器，所述支付服 务器用于在所述用户设备和所述支付验证服务器之间进行信令传输。
  6. 一种支付验证方法，应用于权利要求1所提供的支付验证系统，其特征在于，所述方法包括：
    设备验证服务器为所述支付验证服务器注册基于生物识别信息的支付功能；
    所述设备验证服务器在用户设备开通所述支付功能时，对所述用户设备进行验证；
    支付验证服务器在用户设备开通所述支付功能时，如果所述设备验证服务器对所述用户设备验证通过，对所述用户设备上运行的支付应用进行验证，并在所述支付应用验证通过后，为所述用户设备开通所述支付功能；
    所述支付验证服务器在接收到所述用户设备的支付请求，对所述支付请求进行验证。
  7. 根据权利要求6所述的方法，其特征在于，所述设备验证服务器在用户设备开通所述支付功能时，对所述用户设备进行验证包括：
    所述设备验证服务器保存用户设备的设备公钥，并在接收到所述用户设备的第一支付开通请求时，根据所述用户设备的设备公钥，对所述第一支付开通请求所携带的第一签名信息进行验证，当验证通过时，向所述支付验证服务器发送验证通过消息，所述第一签名信息由所述用户设备使用所述用户设备的设备私钥对特定内容签名得到。
  8. 根据权利要求6所述的方法，其特征在于，支付验证服务器在用户设备开通所述支付功能时，如果所述设备验证服务器对所述用户设备验证通过，对所述用户设备上运行的支付应用进行验证，并在所述支付应用验证通过后，为所述用户设备开通所述支付功能包括：
    所述支付验证服务器接收所述用户设备上传的应用公钥，并在接收到所述设备验证服务器发送的所述验证通过消息时，保存所述用户设备的应用公钥；
    所述支付验证服务器接收所述用户设备上传的携带用户公钥和第二签名信息的第二支付开通请求，根据所述用户设备的应用公钥对所述第二签名信息进行验证，当验证通过时，保存所述用户设备的用户公钥，所述第二签名信息由所述用户设备使用所述用户设备的应用私钥对特定内容签名得到。
  9. 根据权利要求6所述的方法，其特征在于，所述支付验证服务器在接收到所述用户设备的支付请求，对所述支付请求进行验证包括：
    所述支付验证服务器在接收到携带第三签名信息的支付请求时，根据所述用户设备的用户私钥对所述第三签名信息进行验证，当验证通过时，执行所述支付请求。
  10. 根据权利要求1所述的系统，其特征在于，所述支付请求由支付服务器在所述用户设备和所述支付验证服务器之间进行传输。
  11. 一种支付验证方法，其特征在于，包括：
    在设备验证服务器上注册基于生物识别信息的支付功能；
    在注册成功后，接收用户设备发上传的应用公钥，并在接收到所述设备验证服务器发送的验证通过消息时，保存所述用户设备的应用公钥；
    在接收到所述用户设备上传的携带用户公钥和第二签名信息的第二支付开通请求时，根据所述用户设备的应用公钥对所述第二签名信息进行验证，当验证通过时，保存所述用户设备的用户公钥，所述第二签名信息由所述用户设备使用所述用户设备的应用私钥对特定内容签名得到；
    在接收到携带第三签名信息的支付请求时，根据所述用户设备的用户公钥对所述第三签名信息进行验证，当验证通过时，执行所述支付请求，所述第三签名信息由所述用户设备使用用户私钥对特定内容签名得到。
  12. 一种支付验证装置，其特征在于，包括：
    注册模块，用于在设备验证服务器上注册基于生物识别信息的支付功能；
    接收模块，用于在注册成功后，接收用户设备发上传的应用公钥；
    保存模块，用于在接收到所述设备验证服务器发送的验证通过消息时，保存所述用户设备的应用公钥；
    验证模块，用于在接收到所述用户设备上传的携带用户公钥和第二签名信息的第二支付开通请求时，根据所述用户设备的应用公钥对所述第二签名信息进行验证，当验证通过时，触发所述保存模块保存所述用户设备的用户公钥，所述第二签名信息由所述用户设备使用所述用户设备的应用私钥对特定内容签名得到；
    所述验证模块还用于在接收到携带第三签名信息的支付请求时，根据所述用户设备的用户公钥对所述第三签名信息进行验证；
    处理模块，用于当对所述第三签名信息验证通过时，执行所述支付请求，所述第三签名 信息由所述用户设备使用用户私钥对特定内容签名得到。
  13. 一种支付验证装置，其特征在于，包括：
    处理器；
    用于存储处理器可执行的指令的存储器；
    其中，所述处理器被配置为：
    在设备验证服务器上注册基于生物识别信息的支付功能；
    在注册成功后，接收用户设备发上传的应用公钥，并在接收到所述设备验证服务器发送的验证通过消息时，保存所述用户设备的应用公钥；
    在接收到所述用户设备上传的携带用户公钥和第二签名信息的第二支付开通请求时，根据所述用户设备的应用公钥对所述第二签名信息进行验证，当验证通过时，保存所述用户设备的用户公钥，所述第二签名信息由所述用户设备使用所述用户设备的应用私钥对特定内容签名得到；
    在接收到携带第三签名信息的支付请求时，根据所述用户设备的用户公钥对所述第三签名信息进行验证，当验证通过时，执行所述支付请求，所述第三签名信息由所述用户设备使用用户私钥对特定内容签名得到。
PCT/CN2015/099617 2015-11-23 2015-12-29 支付验证系统、方法及装置 Ceased WO2017088262A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
JP2016519995A JP6401784B2 (ja) 2015-11-23 2015-12-29 決済認証システム、方法及び装置
RU2016128502A RU2652425C1 (ru) 2015-11-23 2015-12-29 Система, способ и устройство подтверждения оплаты
KR1020167009689A KR101918827B1 (ko) 2015-11-23 2015-12-29 결제 검증 시스템, 방법 및 장치
MX2016005792A MX383991B (es) 2015-11-23 2015-12-29 Sistema, método y aparato de verificación de pagos.

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510818893.5 2015-11-23
CN201510818893.5A CN105306490B (zh) 2015-11-23 2015-11-23 支付验证系统、方法及装置

Publications (1)

Publication Number Publication Date
WO2017088262A1 true WO2017088262A1 (zh) 2017-06-01

Family

ID=55203240

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/099617 Ceased WO2017088262A1 (zh) 2015-11-23 2015-12-29 支付验证系统、方法及装置

Country Status (8)

Country Link
US (1) US20170148029A1 (zh)
EP (1) EP3171315A1 (zh)
JP (1) JP6401784B2 (zh)
KR (1) KR101918827B1 (zh)
CN (1) CN105306490B (zh)
MX (1) MX383991B (zh)
RU (1) RU2652425C1 (zh)
WO (1) WO2017088262A1 (zh)

Families Citing this family (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105488679B (zh) * 2015-11-23 2019-12-03 北京小米支付技术有限公司 基于生物识别技术的移动支付设备、方法和装置
CN108475304B (zh) 2015-12-29 2021-08-13 华为技术有限公司 一种关联应用程序和生物特征的方法、装置以及移动终端
GB201609462D0 (en) * 2016-05-30 2016-07-13 Silverleap Technology Ltd System and method for ensuring system integrity against, and detection of, rollback attacks for stored value data in mobile devices
WO2018000370A1 (zh) * 2016-06-30 2018-01-04 华为技术有限公司 一种移动终端的认证方法及移动终端
WO2018094584A1 (zh) * 2016-11-23 2018-05-31 刘洪文 基于生物特征识别的支付及身份认证系统
CN107196901B (zh) * 2017-03-30 2020-06-02 阿里巴巴集团控股有限公司 一种身份注册及认证的方法及装置
CN107947934B (zh) * 2017-11-08 2021-07-30 中国银行股份有限公司 基于银行系统的移动终端的指纹识别认证系统及方法
CN107994995A (zh) * 2017-11-29 2018-05-04 深圳市文鼎创数据科技有限公司 一种低安全介质的交易方法、系统及终端设备
US11405386B2 (en) 2018-05-31 2022-08-02 Samsung Electronics Co., Ltd. Electronic device for authenticating user and operating method thereof
CN108986153B (zh) * 2018-08-01 2021-03-12 Oppo广东移动通信有限公司 图像处理方法和装置、电子设备、计算机可读存储介质
WO2020024603A1 (zh) 2018-08-01 2020-02-06 Oppo广东移动通信有限公司 图像处理方法和装置、电子设备、计算机可读存储介质
CN110677418B (zh) * 2019-09-29 2021-11-19 四川虹微技术有限公司 可信声纹认证方法、装置、电子设备及存储介质
CN110910132B (zh) * 2019-12-05 2025-07-04 上海商米科技集团股份有限公司 智能商业终端上支付功能实现的方法和装置
CN111062725B (zh) * 2019-12-16 2023-07-07 腾讯科技（深圳）有限公司 人脸支付方法、装置及系统、计算机可读存储介质
CN111401901B (zh) * 2020-03-23 2021-06-04 腾讯科技（深圳）有限公司 生物支付设备的认证方法、装置、计算机设备和存储介质
CN112053161B (zh) * 2020-05-09 2022-11-11 支付宝(杭州)信息技术有限公司 绑定处理方法、装置及设备
CN111951463B (zh) * 2020-06-05 2022-08-19 陶源 一种售货机激活系统及售货机离线售货方法

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101093566A (zh) * 2006-06-23 2007-12-26 联想(北京)有限公司 一种安全的移动支付系统、设备及方法
CN101192284A (zh) * 2006-11-28 2008-06-04 北京握奇数据系统有限公司 基于移动设备签名的远程支付方法和系统
WO2010138611A1 (en) * 2009-05-29 2010-12-02 Ebay, Inc. Trusted integrity manager (tim)
WO2015066028A1 (en) * 2013-11-04 2015-05-07 Apple Inc. Using biometric authentication for nfc-based payments

Family Cites Families (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7047416B2 (en) * 1998-11-09 2006-05-16 First Data Corporation Account-based digital signature (ABDS) system
JP5160003B2 (ja) * 2000-05-10 2013-03-13 ソニー株式会社 決済管理装置，プログラム，記憶媒体，管理方法，クライアント装置，処理方法，およびデータ記憶装置
WO2002013444A2 (en) * 2000-08-04 2002-02-14 First Data Corporation Trusted authentication digital signature (tads) system
JP4145118B2 (ja) * 2001-11-26 2008-09-03 松下電器産業株式会社 アプリケーション認証システム
JP2005025337A (ja) * 2003-06-30 2005-01-27 Sony Corp 機器登録システム、機器登録サーバ、機器登録方法、機器登録プログラム、記憶媒体、及び端末機器
EP2485186A1 (en) * 2004-01-21 2012-08-08 Qualcomm Incorporated Application-based value billing in a wireless subscriber network
KR20060117631A (ko) * 2005-05-13 2006-11-17 주식회사 디젠트 결제 기능을 구비한 휴대용 유에스비 메모리 스틱 및 이를 이용한 결제 시스템
KR20070059891A (ko) * 2005-12-07 2007-06-12 한국전자통신연구원 어플리케이션 인증 보안 시스템 및 그 인증 보안 방법
JP5107731B2 (ja) * 2008-01-18 2012-12-26 株式会社日立製作所 生体情報登録システム
US20100262506A1 (en) * 2009-04-08 2010-10-14 Microsoft Corporation Mobile content delivery on a mobile network
US8725122B2 (en) * 2009-05-13 2014-05-13 First Data Corporation Systems and methods for providing trusted service management services
CN101719250B (zh) * 2009-12-10 2013-07-24 中国联合网络通信集团有限公司 支付认证方法、平台和系统
CN101834946A (zh) * 2010-05-11 2010-09-15 丁峰 一种进行安全手机支付的方法和进行安全支付的手机
WO2013081421A1 (ko) * 2011-12-01 2013-06-06 에스케이씨앤씨 주식회사 안전한 모바일 지갑 거래 방법 및 시스템
CN102610045B (zh) * 2012-03-22 2014-11-26 瑞达信息安全产业股份有限公司 一种可信移动支付系统及移动支付方法
US20140214670A1 (en) * 2013-01-30 2014-07-31 Jason C. McKenna Method for verifying a consumer's identity within a consumer/merchant transaction
KR102460459B1 (ko) * 2015-02-27 2022-10-28 삼성전자주식회사 전자 장치를 이용한 카드 서비스 방법 및 장치
CN104994114B (zh) * 2015-07-27 2018-10-16 上海位坤电子商务有限公司 一种基于电子身份证的身份认证系统和方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101093566A (zh) * 2006-06-23 2007-12-26 联想(北京)有限公司 一种安全的移动支付系统、设备及方法
CN101192284A (zh) * 2006-11-28 2008-06-04 北京握奇数据系统有限公司 基于移动设备签名的远程支付方法和系统
WO2010138611A1 (en) * 2009-05-29 2010-12-02 Ebay, Inc. Trusted integrity manager (tim)
WO2015066028A1 (en) * 2013-11-04 2015-05-07 Apple Inc. Using biometric authentication for nfc-based payments

Also Published As

Publication number Publication date
MX2016005792A (es) 2017-11-30
KR20170073547A (ko) 2017-06-28
CN105306490A (zh) 2016-02-03
KR101918827B1 (ko) 2018-11-14
RU2652425C1 (ru) 2018-04-26
EP3171315A1 (en) 2017-05-24
MX383991B (es) 2025-03-14
US20170148029A1 (en) 2017-05-25
JP6401784B2 (ja) 2018-10-10
JP2018504789A (ja) 2018-02-15
CN105306490B (zh) 2018-04-24

Similar Documents

Publication Publication Date Title
WO2017088262A1 (zh) 支付验证系统、方法及装置
CN108777684B (zh) 身份认证方法、系统及计算机可读存储介质
CN110555706B (zh) 基于安全单元和可信执行环境的人脸支付安全方法及平台
CN113114624B (zh) 基于生物特征的身份认证方法和装置
JP7798572B2 (ja) 効率的なチャレンジ応答認証のためのシステム及び方法
US10075437B1 (en) Secure authentication of a user of a device during a session with a connected server
CN106612180B (zh) 实现会话标识同步的方法及装置
KR102382474B1 (ko) 보안 전송 프로토콜을 사용하여 신뢰를 설정하기 위한 시스템 및 방법
CN110061842B (zh) 带外远程认证
CN114444134B (zh) 一种数据使用授权方法、系统及装置
US9935953B1 (en) Secure authenticating an user of a device during a session with a connected server
JP6530049B2 (ja) ホスト型認証サービスを実装するためのシステム及び方法
JP2018532301A (ja) 本人認証方法及び装置
CN109474437B (zh) 一种基于生物识别信息来应用数字证书的方法
WO2017167093A1 (zh) 基于生物特征的身份注册、认证的方法和装置
US12231555B2 (en) Authentication and validation procedure for improved security in communications systems
CN111431719A (zh) 一种移动终端密码保护模块、移动终端及密码保护方法
KR20220019834A (ko) 디바이스로의 보안 자격증명 전송을 인증하는 방법 및 시스템
EP3206329B1 (en) Security check method, device, terminal and server
WO2021190197A1 (zh) 生物支付设备的认证方法、装置、计算机设备和存储介质
CN112559993A (zh) 身份认证方法、装置、系统及电子设备
TWM595792U (zh) 跨平台授權存取資源的授權存取系統
CN110838919B (zh) 通信方法、存储方法、运算方法及装置
WO2025108029A1 (zh) 第三方授权登录
CN118764319A (zh) 一种基于fido的系统登录认证方法、装置及设备

Legal Events

Date Code Title Description
ENP Entry into the national phase

Ref document number: 2016519995

Country of ref document: JP

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 20167009689

Country of ref document: KR

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: MX/A/2016/005792

Country of ref document: MX

ENP Entry into the national phase

Ref document number: 2016128502

Country of ref document: RU

Kind code of ref document: A

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

Ref document number: 15909173

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

Country of ref document: EP

Kind code of ref document: A1