US10990957B2 - Scan and pay method and device utilized in mobile apparatus - Google Patents

Scan and pay method and device utilized in mobile apparatus Download PDF

Info

Publication number
US10990957B2
US10990957B2 US16/400,550 US201916400550A US10990957B2 US 10990957 B2 US10990957 B2 US 10990957B2 US 201916400550 A US201916400550 A US 201916400550A US 10990957 B2 US10990957 B2 US 10990957B2
Authority
US
United States
Prior art keywords
mobile device
behavioral biometric
information
biometric signature
payment
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.)
Active, expires
Application number
US16/400,550
Other languages
English (en)
Other versions
US20190259021A1 (en
Inventor
Yicheng Lu
Shuai Chen
Tao Chen
Jupeng Xia
Ning Wang
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.)
Advanced New Technologies Co Ltd
Original Assignee
Advanced New Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Advanced New Technologies Co Ltd filed Critical Advanced New Technologies Co Ltd
Assigned to ALIBABA GROUP HOLDING LIMITED reassignment ALIBABA GROUP HOLDING LIMITED ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: CHEN, SHUAI, CHEN, TAO, LU, YICHENG, WANG, NING, XIA, Jupeng
Publication of US20190259021A1 publication Critical patent/US20190259021A1/en
Assigned to ADVANTAGEOUS NEW TECHNOLOGIES CO., LTD. reassignment ADVANTAGEOUS NEW TECHNOLOGIES CO., LTD. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: ALIBABA GROUP HOLDING LIMITED
Assigned to Advanced New Technologies Co., Ltd. reassignment Advanced New Technologies Co., Ltd. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: ADVANTAGEOUS NEW TECHNOLOGIES CO., LTD.
Application granted granted Critical
Publication of US10990957B2 publication Critical patent/US10990957B2/en
Active legal-status Critical Current
Adjusted expiration legal-status Critical

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR 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; CALCULATING OR 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; CALCULATING OR 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; CALCULATING OR 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/326—Payment applications installed on the mobile devices
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR 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/327—Short range or proximity payments by means of M-devices
    • G06Q20/3274—Short range or proximity payments by means of M-devices using a pictured code, e.g. barcode or QR-code, being displayed on the M-device
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR 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/327—Short range or proximity payments by means of M-devices
    • G06Q20/3276—Short range or proximity payments by means of M-devices using a pictured code, e.g. barcode or QR-code, being read by the M-device
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR 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/3825—Use of electronic signatures
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR 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
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR 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/4016—Transaction verification involving fraud or risk level assessment in transaction processing
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR 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

  • This application relates generally to Internet technologies, and more specifically, to a scan-to-pay method and related devices.
  • a conventional offline scan-to-pay method typically comprises the following steps: first, upon a payment request, a payment code is generated on a client; second, a merchant reads the payment code on the client using a scanning device to obtain transaction information; third, the transaction information is uploaded to a server via the merchant's network; fourth, the server performs risk control; and fifth, depending on an outcome of the risk control, the server either requests further online identity verification, or approves the payment request.
  • an offline payment method should possess the following three characteristics: first, the transaction speed should be fast. Consequently, a typical goal in developing an offline payment method is to ensure a short transaction time. Second, the amount of data to be transmitted should be kept at a minimum, since an offline payment will frequently happen in an environment with limited network connection, which is capable of transmitting only a small amount of data. For example, in an offline payment process, a mobile device may transmit a payment code generated by a client to a merchant scanning device. However, doing so would generate substantial network traffic and would post a challenge to a subsequent risk control process due to limited network capability. Third, each payment needs to go through a real-time risk control process to ensure its security.
  • a scan-to-pay method and related devices are provided to address the problem of conventional offline payment methods that risk control processes take too much time and consume too much resources.
  • the embodiments of the specification provide a scan-to-pay method for a mobile device.
  • the method comprises receiving a payment request from an operator of the mobile device and generating a payment code based on the payment request.
  • the payment code comprises first information and second information, with the first information associated with a payment account, and the second information associated with at least one recent behavioral biometric signature of the operator and at least one historical behavioral biometric signature recorded in the mobile device.
  • the embodiments of this specification provide a device comprising one or more processors and one or more non-transitory machine-readable memories coupled to the one or more processors and configured with instructions executable by the one or more processors to cause the device to perform the following operations: receiving a payment request from an operator of a mobile device and generating a payment code based on the payment request.
  • the payment code comprises first information and second information, with the first information associated with a payment account, and the second information associated with at least one recent behavioral biometric signature of the operator and at least one historical behavioral biometric signature recorded in the mobile device.
  • the embodiments of this specification further present a risk control method, including obtaining a payment code from the mobile device.
  • the payment code comprises first information and second information, with the first information associated with a payment account, and the second information associated with at least one recent behavioral biometric signature of an operator of the mobile device and at least one historical behavioral biometric signature recorded in the mobile device.
  • the method may further include determining whether to activate a server-side risk control process based on the second information.
  • the embodiments of this specification further provide a scan and pay device on a mobile device.
  • the device comprises a receiving unit for receiving a payment request of an operator of the mobile device and a generating unit for generating a payment code based on the payment request.
  • the payment code at least comprises first information associated with a payment account and second information associated with at least one behavioral biometric signature of the operator and at least one historical behavioral biometric signature recorded in the mobile device.
  • the embodiments of the specification further provide a risk control method utilized for performing scan and pay in a mobile device.
  • the method comprises obtaining a payment code provided by the mobile device.
  • the payment code at least comprises first information associated with a payment account and second information associated with at least one behavioral biometric signature of an operator of the mobile device and at least one historical behavioral biometric signature recorded in the mobile device.
  • the method may further comprise determining whether to activate risk control identification of a server based on the second information comprised in the payment code.
  • this specification further provides a risk control device for performing scan and pay in a mobile device
  • the device comprises an obtaining unit for obtaining a payment code provided by the mobile device.
  • the payment code comprises first information associated with a payment account and second information associated with at least one behavioral biometric signature of an operator of the mobile device and at least one historical behavioral biometric signature recorded in the mobile device.
  • the device may further includes a risk control processing unit for determining whether to activate risk control identification of a server based on the second information comprised in the payment code.
  • a determination result based on behavioral biological information of an operator is encoded into a payment code and transmitted to a server for risk assessment.
  • the risk control system of this application evaluates the risk based on more comprehensive data, and therefore provides more accurate results.
  • the risk control processes of this application first makes a risk assessment based on behavioral biological information of the operator, and the server-side risk control process is required only if the risk assessment indicates that the operator may not be the account owner. Therefore, networking and computing resource needed on the server can be substantially reduced.
  • the risk assessment based on behavioral biological information of the operator may be performed on a local terminal, and a server-side risk control process is necessary only if the risk assessment returns unfavorable results, therefore compare to conventional server-side risk control processes, the risk control processes of this application can be performed much faster.
  • FIG. 1 shows a flowchart illustrating a scan-to-pay method for a mobile device in accordance with some embodiments.
  • FIG. 2 shows a flowchart illustrating a risk control method for scan-to-pay on a mobile device in accordance with some embodiments.
  • FIG. 3 shows a flowchart illustrating a risk control method for scan-to-pay on a mobile device in accordance with some embodiments.
  • FIG. 4 shows a schematic diagram illustrating a scan-to-pay device for a mobile device in accordance with some embodiments.
  • FIG. 5 shows a schematic diagram illustrating a risk control device for scan-to-pay on a mobile device in accordance with some embodiments.
  • Biometric techniques are gradually finding their ways into payment applications. Each individual possesses measurable or verifiable physiological characteristics or behavioral characteristics, collectively known as biological characteristics, that are unique to himself/herself.
  • Biological characteristics of a person may include physiological biometric signatures and behavioral biometric signatures (BBS).
  • the physiological biometric signatures may include a person's eye characteristics (including eye features, iris characteristics, sclera characteristics, etc.), voiceprint, fingerprint, palm print, heartbeat pattern, heart pulse pattern, chromosome, DNA sequences, bite mark, etc.
  • the behavioral biometric signatures may include a person's walking posture, sound, handwriting, keystroke pattern, key-pressing force, gesture to hold an electronic device, as well as a person's online browse log and Remote Procedure Call (RPC) protocol requesting record, etc.
  • Biometric techniques rely on a person's unique physiological characteristics to verify his/her identity.
  • the method comprises: receiving a payment request from an operator of the mobile device and generating a payment code based on the payment request, with the payment code comprising first information associated with a payment account and second information associated with at least one recent behavioral biometric signature of the operator and at least one historical behavioral biometric signature recorded in the mobile device.
  • information related to the recent behavioral biometric signatures of the operator and the historical behavioral biometric signatures recorded in the mobile device is encoded in the payment code and transmitted to a server for risk assessment.
  • the risk control system of this application evaluates the risk based on more comprehensive data, and therefore provides more accurate results.
  • the behavioral biometric signatures used in the embodiments include at least one of a person's RPC request record, browse log, gesture to hold a mobile device, and finger pressing characteristics.
  • FIG. 1 shows a flowchart illustrating a scan-to-pay method for a mobile device in accordance with some embodiments. This scan-to-pay method is described below with reference to FIG. 1 .
  • step 101 a payment request from an operator of a mobile device is received.
  • the operator of the mobile device may send a payment request through a payment widget or a payment webpage link on a website.
  • the payment request may be sent to a client of the mobile device.
  • the mobile device may already possess some behavioral biometric signatures of the operator of the mobile device before he/she makes the payment request.
  • these behavioral biometric signatures may be collected by a system or device installed on the mobile device that is capable of identifying behavioral biometric signatures of the operator. These signatures may be obtained by other manners, thus this application is not limited herein.
  • the behavioral biometric signatures are collected by a system or device installed on the mobile device that is capable of identifying behavioral biometric signatures of the operator.
  • behavioral biometric signatures depict, to a degree, behavioral habits of the operator.
  • a person's behavioral biometric signatures largely remain consistent over time, therefore an operator's behavioral biometric signatures in operating a mobile device, which can be collected by a system or device install on the mobile device, can be used to verify the identity of the operator.
  • online contents a user browsed over a period of time typically reflect the user's personal or professional preferences, which are unlikely to change abruptly. Therefore if a system or device monitoring behavioral biometric signatures of the user of a mobile device detects a substantial change on the online contents browsed by the operator in a short period of time (i.e., distinct browse log activities), it can be inferred that the user of the mobile device may have changed, i.e., the user currently using the mobile device may not be the user who had registered his/her behavioral biometric signatures.
  • a behavioral biometric signature monitoring system or device may be used to collect behavioral biometric signatures of an operator of a mobile device, and a client-side risk control system on the mobile device may determine whether the operator is the registered owner of the mobile device based on behavioral biometric signatures collected. In case a “no-match” is found, the client-side risk control system may provide conflicting signatures to the server-side risk control system to facilitate further risk control processes.
  • the conflicting signatures depict the differences between the behavioral biometric signatures collected and the behavioral biometric signatures in the records, which provide a comprehensive assessment on the identity of the operator.
  • the operator of the mobile device may conduct other operations on the mobile device, such as browsing web pages, swiping on the screen, etc. All these operations may be referred to as behavioral biometric signatures of the operator, and may be collected by the behavioral biometric signature monitoring system or device on the mobile device.
  • the behavioral biometric signatures collected by the behavioral biometric signature monitoring system or device may be stored in a designated storage space.
  • a library of behavioral biometric signatures may be maintained in a designated storage space to store the behavioral biometric signatures of the operators collected at different times.
  • behavioral biometric signatures stored in the designated storage space of a device may be mostly those of the owner of the mobile device.
  • the designated storage space may store only the behavioral biometric signatures within a certain period of time. For example, it may only store the behavioral biometric signatures that are collected recently (“recently” here may mean a set period of time (e.g., a week) before the payment request is made).
  • behavioral biometric signatures may be referred to as “recent behavioral biometric signatures.” Behavioral biometric signatures collected on other times (i.e., those collected before the past week) may be referred to as “historical behavioral biometric signatures” and may be disposed by other means. For example, they may be stored on the mobile device, sent to a server, or stored in a hard disk drive.
  • a mapping relationship between a collection time and the collected behavioral biometric signatures will also be stored in the library of behavioral biometric signatures described above.
  • step 102 a payment code is generated based on the payment request.
  • the payment code may comprise first information and second information, with the first information associated with a payment account and the second information associated with at least one recent behavioral biometric signature of the operator and at least one historical behavioral biometric signature recorded in the mobile device.
  • the payment code may be generated by a client in the mobile device immediately upon receiving the payment request.
  • the first information associated with a payment account and the second information associated with at least one recent behavioral biometric signature of the operator and at least one historical behavioral biometric signature recorded in the mobile device will first be identified.
  • the first information may include information associated with a payment account, such as an account identifier, an account name, an account number, a payment account identifier, or a mobile device identifier, etc.
  • the second information will be described in details below.
  • the second information in some embodiments may be associated with at least one recent behavioral biometric signature of the operator and at least one historical behavioral biometric signature recorded in the mobile device.
  • a time period will first be determined to define a time window under which the behavioral biometric signatures stored in the mobile device will be included in the second information.
  • the time period may be determined by a client based on the time the payment request is received. Based on the time period selected, the client may identify behavioral biometric signatures in the designated storage space of the mobile device that are collected during the selected time period. These behavioral biometric signatures may be referred to as “recent behavioral biometric signatures” of the operator. For example, behavioral biometric signatures collected within a time period before the payment request is received may be used as recent behavioral biometrics signatures. Behavioral biometric signatures collected before that time period may be used as historical behavioral biometric signatures.
  • the second information may be determined after at least one recent behavioral biometric signature are obtained.
  • the second information may also include conflicting signatures obtained from a risk identification module in the client. Subsequently, after the server receives a payment code comprising the first information and the second information, some risk identification processes may be done based on the second information alone, which substantially reduces the networking and computing resource needed on the server and improves the efficiency of the risk identification process.
  • the second information may be obtained in several manners described below:
  • a comparison between the recent behavioral biometric signature of the operator and historical behavioral biometric signature recorded in the mobile device may be conducted to determine whether the operator is the owner of the mobile device.
  • a similarity between the recent behavioral biometric signature of the operator and historical behavioral biometric signature recorded in the mobile device may be calculated, and a determination that whether the operator is the owner of the mobile device may be made according to the calculated similarity.
  • a similarity greater than a set threshold indicates that the operator is the owner of the mobile device, while a similarity less than the set threshold indicates otherwise.
  • the second information may be obtained based on the determination that whether the operator is the owner of the mobile device. That is, the second information may comprise a determination result that whether the operator is the owner of the mobile device, wherein the determination result may be that the operator is the owner of the mobile device or the operator is not the owner of the mobile device.
  • the second information may also include a combination of different information. That is, in addition to a determination result of whether the operator is the owner of the mobile device, the second information may further include a determination result of whether some or all of the recent behavioral biometric signatures are distinct in comparison with the corresponding historical behavioral signatures in the records. By including a combination of different comparison results, the second information can provide a more accurate determination on the identity of the operator.
  • the second information may further comprise a determination result that whether some or all of collected behavioral biometric signatures are distinct compared to corresponding historical behavioral biometric signatures, such as a determination result that whether the RPC request records are distinct from those in the records, or a determination result that whether the browse logs are distinct from those in the records, etc.
  • a binary value (true or false) may be used to represent the determination result that whether the operator is the owner of the mobile device, In this case, the mobile device may need to perform substantial computation to obtain an accurate result, which leads to large computational burdens for the mobile device.
  • the determination result may be expressed as a probability in a numerical value.
  • a probability that the operator being the owner of the mobile device is lower than a set threshold will result in a determination that the operator is not the owner of the mobile device.
  • the determination result may be adjusted, and the subsequent operations on the server may also be affected accordingly.
  • the server receives the payment code
  • the determination of the operator identity is not made based on one single comparison, as in the case of the first manner, instead the determination is made through mutual corroboration among various comparison results, and that improves the efficiency and accuracy of the risk control process.
  • the second information may be obtained by the second manner when the payment code is generated, thus the second information may include additional information to produce a more accurate determination of the operator identity.
  • a payment code is generated based on the first information and the second information.
  • the payment code may be generated by encoding the first information and the second information.
  • the second information comprises a binary determination result
  • an identifier value of 1 corresponds to a determination result that the operator is the owner of the mobile device
  • an identifier value of 0 corresponds to a determination result that the operator is not the owner of the mobile device.
  • the payment code can be obtained by using the identifier value to encode the second information.
  • the server When the server receives the payment code, it can complete operator identification based on the second information in the payment code. That is, if the identifier value in the payment code is 0, the server determines that the operator is not the owner of the mobile device; if the identifier value in the payment code is 1, the server determines that the operator is the owner of the mobile device. As a result, the server can complete risk control for the payment request without substantial computation.
  • the second information since the second information comprises a combination of different comparison results, the second information needs to go through a more complicate conversion process to obtain the identifier value corresponding to the second information.
  • the conversion process of the second information will be described below using an example wherein the second information comprises three comparison results: a determination result whether the operator is the owner of the mobile device, a determination result whether the RPC request records are distinct from those in the records, and a determination result whether the browse logs are distinct from those in the records.
  • these three comparison results can be represented by a three-digit binary number: [X][Y][Z], with X corresponding to the determination result whether the operator is the owner of the mobile device, i.e., the value of X is x1 if the determination result is that the operator is the owner of the mobile device, otherwise, the value of X is x2;
  • Y corresponds to the determination result that whether the browse logs are distinct, i.e., the value of Y is y1 if the determination result is the browse logs are not distinct, otherwise, the value of Y is y2;
  • Z corresponds to the determination result that whether the RPC request records are distinct, i.e., the value of Z is z1 if the determination result is that the RPC request records are not distinct, otherwise, the value of Z is z2.
  • the mobile device can obtain a binary code, which may be referred to as an identifier value corresponding to the second information.
  • the binary code may further be converted to a decimal number, and in that case, the decimal number is an identifier value corresponding to the second information.
  • the identifier value corresponding to the second information may be determined in a random manner. For example, a number randomly selected from 10 numbers of 0 to 9 may be used to represent each of x1, x2, y1, y2, z1, and z2 based on a mapping relationship between this number and [X][Y][Z].
  • 1 to 2 numbers may be randomly selected from the 10 numbers of 0 to 9 as redundant numbers, redundant numbers increase the encoding noise for increased security.
  • the redundant numbers cannot be a number that have been used to represent X, Y, or Z.
  • [X][Y][Z] is typically a three-digit binary number, and thus has a value range from 0 to 7 (in decimal format).
  • the information represented by [X][Y][Z] may have a total of eight possible combinations, thus eight numbers may be selected from the 10 numbers of 0 to 9, with each representing one of eight possible combinations.
  • a combination of the determination results that “the operator is the owner, the RPC records are not distinct, and the browse logs are not distinct” may be represented by a binary number of [1][0][0], which has a decimal number of 4.
  • the number for storing the behavioral biometric signatures after decoding is 4, it represents a combination of the determination results that “the operator is the owner, the RPC records are not distinct, and the browse logs are not distinct.”
  • Number selections for the encoding may be fully customizable.
  • number 4 represents a combination of the determination results that “the operator is the owner, the RPC records are not distinct, and the browse logs are not distinct.” Any other number from 0 to 9 may replace number 4 to represent the same results.
  • the exact number that can be used to present a particular determination result is customizable.
  • redundant numbers used for encoding noise may also be customizable. By changing the numbers in the encoding and the numbers for redundant numbers regularly or irregularly, encoding security can be improved.
  • behavioral biometric signatures listed in the embodiments described above are merely preferred examples, and are not exhaustive. Any behavioral biometric signature that can be collected on a mobile device may be used to determine whether the operator is the owner of the mobile device. Some embodiments that are not fully described herein may further comprise determining whether to activate a server-side risk control process based on information related to the behavioral biometric signatures.
  • the mapping relationship between the identifier and the second information may be at least partially changed regularly or periodically.
  • the mapping relationship between the identifier and the second information may be changed by changing at least one of the redundant numbers for enhanced security.
  • the method may further comprise: if the determination result is that the probability that the operator is the owner of the mobile device is lower than a set threshold and it is determined that the mobile device is in an offline payment state, activating an online identity verification process against the operator of the mobile device.
  • the determination result when determining whether the operator is the owner of the mobile device, the determination result may be represented by a probability, a probability lower than a set threshold indicates a high likelihood that the operator is not the owner of the mobile device. If the mobile device is in an offline payment state at this moment, an online identity verification process may be activated to further verify the identity the operator of the mobile device. That is, the operator of the mobile device is required to initiate an online payment request and go through an online identity verification process.
  • the scan-to-pay method in accordance with some embodiments may refer to, for example, a process of generating a payment code on the mobile device, and a merchant reading information in the payment code using a scanning device, and sending the information to a server to complete the payment.
  • a payment code may be generated on the mobile device for a merchant to scan to complete the payment.
  • determination results based on the behavioral biometric signatures are encoded into the payment code, which essentially provides an auxiliary offline risk control assistance.
  • This auxiliary offline risk control assistance substantially reduces the burden on the server to conduct the risk control process, and thus reduces the resources consumption and processing time of the risk control process.
  • a payment code is generated based on the payment request.
  • the payment code comprises first information associated with a payment account, and second information associated with at least one recent behavioral biometric signature of the operator and at least one historical behavioral biometric signature recorded in the mobile device.
  • a determination result based on the behavioral biometric information of the operator is encoded into the payment code and transmitted to the server for risk control process.
  • user identity verification is conducted on a client based on the behavioral biometric signatures. That not only ensures the security of offline payment, but also reduces the cost to conduct risk control on the server. Thus the efficiency of offline payment risk control process may be improved.
  • FIG. 2 shows a flowchart illustrating a risk control method for scan-to-pay on a mobile device in accordance with some embodiments. This method can be performed on a scanner or a server. If it is performed on a server, the server may be different from the one performing risk identification described above. The risk control method of FIG. 2 is described below.
  • step 201 a payment code provided by a mobile device is received.
  • the payment code may comprise: first information associated with a payment account and second information associated with at least one recent behavioral biometric signature of an operator of the mobile device and at least one historical behavioral biometric signature recorded in the mobile device.
  • the payment code provided by the mobile device may be obtained by using a scanning gun to scan the payment code, or using a payment code identification device to receive a payment code.
  • the methods that can be used to obtain the payment code are not limited herein.
  • a two-dimensional (2D) barcode image provided by the mobile device may be scanned; and, from the 2D barcode image, the first information associated with a payment account and second information associated with the at least one recent behavioral biometric signature of the operator of the mobile device and the at least one historical behavioral biometric signature recorded in the mobile device may be extracted.
  • 2D barcode image For example, a two-dimensional (2D) barcode image provided by the mobile device may be scanned; and, from the 2D barcode image, the first information associated with a payment account and second information associated with the at least one recent behavioral biometric signature of the operator of the mobile device and the at least one historical behavioral biometric signature recorded in the mobile device may be extracted.
  • the information in the payment code provided by the mobile device may be extracted by scanning the payment code.
  • step 202 a determination result of whether to activate a server-side risk control process is made based on the second information in the payment code.
  • the second information in the payment code may be obtained by conducting a decoding operation on the payment code.
  • the second information includes only a determination result that whether the operator is the owner of the mobile device, then a risk control request will be sent to the server if the determination result is that the operator is not the owner of the mobile device; if the determination result is that the operator is the owner of the mobile device, then the payment request will be fulfilled.
  • the probability that the operator is the owner of the mobile device is determined through the combination of different determination results.
  • a probability that the operator is the owner of the mobile device may be determined through a combination of the following determination results: a determination result of whether the operator is the owner of the mobile device based on the methods described above, a determination result that whether the browse logs are distinct from those in the records, and a determination result that whether the RPC request records are distinct from those in the records.
  • the determination result (expressed as a probability value) that the operator is the owner of the mobile device is lower than a set threshold, it can be determined that the probability that the operator is the owner of the mobile device is lower than a second threshold when at least one of the browse logs and the RPC request records is determined to be distinct, and it can be determined that the probability that the operator is the owner of the mobile device is less than a second threshold but higher than a first threshold when both the browse logs and the RPC request records are determined to be not distinct.
  • the determination result (expressed as a probability value) that the operator is the owner of the mobile device is higher than the set threshold, it can be determined that the probability that the operator is the owner of the mobile device is not higher than the first threshold and higher than the second threshold if at least one of the browse logs and the RPC request records is determined to be distinct. If both the browse logs and the RPC request records are determined to be not distinct, it can be determined that the probability that the operator is the owner of the mobile device is higher than the first threshold.
  • the payment request may be fulfilled
  • a risk identification request will be sent to a risk control system on the server to activate a server-side risk control process
  • an identity verification request which requires the operator to provide offline identity verifications (e.g., presenting an I.D., providing information proving that the operator is the owner of the mobile device, etc.) to the user of the scanning device, may be sent to a scanning device to ensure the security of the transaction.
  • an online transaction request may be sent to the scanning device, requesting the user using the scanning device to notify the operator to activate an online payment process, so that the identity of the operator can be verified online.
  • whether a further server-side risk control process is necessary may be determined based on a determination result of a risk control process based on the behavioral biometric signatures of the operator in the payment code.
  • Experimental results demonstrate that, by using a local risk identification system on a local terminal to complete the risk control, a 70% reduction on the computation cost of the terminal device can be achieved, which indicates a substantially reduction to the cost associated with server-side risk control process and an improvement on the efficiency of the server-side risk control process.
  • FIG. 3 shows a flowchart illustrating a risk control method for scan-to-pay on a mobile device in accordance with some embodiments. These embodiments will be described in details.
  • step 301 a payment request from a user is received by a mobile device.
  • the payment request may be sent to a mobile device when the user of the mobile device is in an offline state.
  • the mobile device When the mobile device receives the payment request, it identifies the behavioral biometric signatures of the user collected within a certain period of time, these behavioral biometric signatures are referred to as “recent behavioral biometric signatures” in succeeding discussions.
  • step 302 a payment code is generated by the mobile device based on the payment request.
  • the payment code may comprise information about a payment account of the user, at least one recent behavioral biometric signature of the user, at least one historical behavioral biometric signature recorded in the mobile device, and a determination that whether the user is the owner of the mobile device.
  • step 303 the payment code provided by the mobile device is scanned, and the determination that whether the user is the owner of the mobile device is made based on the payment code, with the determination result being represented in a percentage form.
  • step 304 the determination result is compared with a first threshold and a second threshold.
  • the first threshold may be different from the second threshold in some embodiments, with the second threshold smaller than the first threshold.
  • step 305 if the determination result (expressed as a probability value) is smaller than the second threshold, indicating the operator is not the owner of the mobile device, a risk identification request will be sent to a risk control identification system on the server to activate a server-side risk control identification process.
  • step 306 if the determination result is not higher than the first threshold and higher than the second threshold, indicating there is a risk that the operator is not the owner of the mobile device, an identity verification request will be sent to the scanning device, requesting the user of the scanning device to perform offline identity verification on the operator.
  • step 307 if the determination result is higher than the first threshold, indicating that the operator is the owner of the mobile device (or at least the risk of otherwise is low), the payment request will be fulfilled.
  • the information associated with a user's behavioral biometric signatures is encoded offline into the payment code and a decision of whether to activate a server-side risk control process is made based on the information.
  • the cost associated with server-side risk control can be substantially reduced, which increases the speed for overall risk control and improves user experience.
  • FIG. 4 shows a schematic diagram illustrating a scan-to-pay device for a mobile device in accordance with some embodiments of this application.
  • the device comprises: a receiving unit 41 and a generating unit 42 , wherein the receiving unit 41 is for receiving a payment request of an operator of the mobile device, and the generating unit 42 is for generating a payment code based on the payment request.
  • the payment code comprises: first information associated with a payment account and second information associated with at least one recent behavioral biometric signature of the operator and at least one historical behavioral biometric signature recorded in the mobile device.
  • the second information may further comprise: a determination result of whether the operator is the owner of the mobile device based on a comparison of at least on recent behavioral biometric signature of the operator and at least one historical behavioral biometric signature recorded in the mobile device.
  • the device may further comprise: a processing unit 43 , wherein the processing unit 43 activates an online identity verification process to the operator of the mobile device, if the determination result is that the probability that the operator is the owner of the mobile device is lower than a set threshold and it is determined that the mobile device is in an offline payment state.
  • the generating unit 42 generating a payment code based on the payment request may comprise: determining the first information associated with the payment account and the second information associated with the at least one recent behavioral biometric signature of the operator and the at least one historical behavioral biometric signature recorded in the mobile device based on the payment request; determining an identifier value corresponding to the second information according to a mapping relationship between the second information and the identifier value; and generating a payment code based on the identifier value and the first information, with at least one digit of the payment code corresponding to the identifier value.
  • the behavioral biometric signatures may comprise at least one of a user's RPC request record, browse log, gesture to hold a mobile device, and finger pressing characteristics.
  • the device in some embodiments of the specification may be implemented through either a software or a hardware, and this specification is not limited herein.
  • the device receives a payment request of an operator of the mobile device; and generates a payment code based on the payment request, with the payment code comprising first information associated with a payment account and second information associated with at least one recent behavioral biometric signature of the operator and at least one historical behavioral biometric signature recorded in the mobile device.
  • an identification result based on the behavioral biometric information of the operator is encoded into the payment code and transmitted to the server to determine whether any further risk control process is necessary.
  • the risk control system of this application evaluates the risk based on more comprehensive data, provides more accurate results, and overall is a more efficiency process.
  • FIG. 5 shows a schematic diagram illustrating a risk control device for scan-to-pay on a mobile device in accordance with some embodiments of this application.
  • the risk control device comprises an acquisition unit 51 and a risk control processing unit 52 , with the acquisition unit 51 obtaining a payment code from the mobile device.
  • the payment code comprises first information associated with a payment account and second information associated with at least one recent behavioral biometric signature of an operator of the mobile device and at least one historical behavioral biometric signature recorded in the mobile device.
  • the risk control processing unit 52 is for determining whether to activate a server-side risk control identification based on the second information in the payment code.
  • the acquisition unit 51 may obtain the payment code provided by the mobile device through the follow steps: first, the acquisition unit 51 scans a 2D barcode image provided by the mobile device, and second, the acquisition unit 51 extracts from the 2D barcode image the first information associated with a payment account and the second information associated with the at least one recent behavioral biometric signature of the operator of the mobile device and the at least one historical behavioral biometric signature recorded in the mobile device.
  • the second information may comprise a determination result of whether the operator is the owner of the mobile device based on a comparison of at least one recent behavioral biometric signature of the operator and at least one historical behavioral biometric signature recorded in the mobile device.
  • the risk control processing unit 52 may determine whether to activate a server-side risk control identification by evaluating the determination result in the payment code. That is, if the determination result in the payment code is that the operator is not the owner of the mobile device, the risk control processing unit 52 activates the server-side risk control identification.
  • the second information may comprise a determination result of whether the operator is the owner of the mobile device, a determination result of whether the browse log is distinct, and a determination result of whether the Remote Procedure Call Protocol is distinct based on a comparison of recent behavioral biometric signatures of the operator and historical behavioral biometric signatures recorded in the mobile device.
  • the risk control processing unit 52 may determine whether to activate a server-side risk control identification by evaluating the determination result. That is, if the determination result in the payment code is that the probability that the operator is the owner of the mobile device is lower than a set threshold, the server-side risk control identification will be activated when at least one of the browse log and the RPC request records is determined to be distinct.
  • the risk control device in some embodiments may be implemented through either a software or a hardware, and this specification is not limited herein.
  • the risk control device may determine whether a server-side risk control operation is necessary based on a result of risk control identification performed by the terminal device based on behavioral biometric signatures of the operator in the payment code.
  • Experimental results show that, by using a local risk identification system on a local terminal to complete the risk control, a 70% reduction on the computation cost of the terminal device can be achieved, which indicates a substantially reduction to the cost associated with server-side risk control process and an improvement on the efficiency of the server-side risk control process.
  • an improvement to a technology can be easily differentiated into a hardware improvement (e.g., an improvement to a circuit structure, such as a diode, a transistor, a switch, etc.) or a software improvement (an improvement to a flow of a method).
  • a hardware improvement e.g., an improvement to a circuit structure, such as a diode, a transistor, a switch, etc.
  • a software improvement an improvement to a flow of a method.
  • Programmable Logic Device e.g., Field Programmable Gate Array (FPGA)
  • FPGA Field Programmable Gate Array
  • a digital system may be “integrated” onto one piece of PLD by a designer, without resorting to a chip manufacturer to design and manufacture a dedicated IC chip.
  • logic compiler software is similar to a software compiler used for program development, and a particular programming language, known as Hardware Description Language (HDL), must be used for writing source codes prior to compiling.
  • HDL Hardware Description Language
  • HDL may further comprise several different languages, including Advanced Boolean Expression Language (ABEL), Altera Hardware Description Language (AHDL), Confluence, Georgia University Programming Language (CUPL), HDCal, Java Hardware Description Language (JHDL), Lava, Lola, MyHDL, PALASM, Ruby Hardware Description Language (RHDL), etc., and Very-High-Speed Integrated Circuit Hardware Description Language (VHDL) and Verilog are among those that are most frequently used.
  • ABEL Advanced Boolean Expression Language
  • AHDL Altera Hardware Description Language
  • CUPL Cornell University Programming Language
  • HDCal Java Hardware Description Language
  • JHDL Java Hardware Description Language
  • Lava Lava
  • Lola MyHDL
  • PALASM Ruby Hardware Description Language
  • RHDL Ruby Hardware Description Language
  • Verilog Very-High-Speed Integrated Circuit Hardware Description Language
  • HDL Hardware Description Language
  • Verilog Very-High-Speed Integrated Circuit Hardware Description Language
  • IC Integrated Circuit
  • a controller may be implemented by any proper method.
  • a controller may have a form of a microprocessor (or a processor), a machine-readable medium storing machine-readable programs (e.g., software or firmware) that can be executed by the microprocessor (or processor), logic gates, switches, Application Specific Integrated Circuit (ASIC), programmable logic controllers, and embedded microcontrollers.
  • machine-readable programs e.g., software or firmware
  • ASIC Application Specific Integrated Circuit
  • programmable logic controllers e.g., programmable logic controllers
  • embedded microcontrollers e.g., embedded microcontrollers.
  • Examples of the controller may include, but not limited to: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320.
  • a memory controller may further be implemented as a part of a control logic of a memory.
  • controllers may also be implemented by logic gates, switches, ASIC, programmable logic controllers, and embedded microcontrollers by logic programming. Therefore, such a controller can be deemed a hardware, and the internal components of the controller that are configured to achieve various functionalities may also be deemed as an internal structure of the hardware. Alternatively, devices configured to achieve various functionalities may be deemed as both software modules to implement a method and an internal structure of a hardware.
  • the systems, devices, modules or units described in the embodiments may be implemented by a computer chip, a hardware component, or a functional product.
  • a typical implementation device is a computer.
  • the computer may be a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a medium player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.
  • this specification may be provided as a method, a system, or a computer program product. Accordingly, this specification may be implemented as a pure hardware embodiment, a pure software embodiment, or an embodiment with a combination of software and hardware embodiments. Additionally, this specification may be implemented in the form of a computer program product implemented on one or more of machine-readable storage media (including, but not limited to, a Hard Disk Drive, a CD-ROM, an optical storage medium, etc.) comprising machine-readable programs.
  • machine-readable storage media including, but not limited to, a Hard Disk Drive, a CD-ROM, an optical storage medium, etc.
  • These computer program instructions may also be stored in a machine-readable memory that can instruct a computer or other programmable data processing devices to work in a particular manner, so that a manufactured article that includes an instruction device may be generated by the instructions stored in the machine-readable memory.
  • the instruction device may implement a function specified in one or more processes in the flowcharts and/or in one or more blocks in the block diagrams.
  • These computer program instructions may also be loaded onto a computer or other programmable data processing devices, so that a series of operations can be performed on the computer or other programmable devices to generate a computer-implemented processing. Therefore, the instructions executed by the computer or other programmable devices may implement a function specified in one or more processes in the flowcharts and/or in one or more blocks in the block diagrams.
  • the computation device may include one or more processors (CPUs), input/output interfaces, network interfaces, and a memory.
  • the memory may include machine-readable media, such as a volatile memory, a Random Access Memory (RAM), and/or a non-volatile memory, e.g., a Read-Only Memory (ROM) or a flash RAM.
  • RAM Random Access Memory
  • ROM Read-Only Memory
  • the memory is an example of a machine-readable medium.
  • Machine-readable media may include permanent, volatile, mobile, and immobile media, and information storage can be implemented through any known method or technology.
  • the information may be machine-readable instructions, data structures, program modules, or other data.
  • Examples of storage media of computers include, but not limited to, Phase-change Random Access Memories (PRAMs), Static Random Access Memories (SRAMs), Dynamic Random Access Memories (DRAMs), other types of Random Access Memories (RAMs), Read-Only Memories (ROMs), Electrically Erasable Programmable Read-Only Memories (EEPROMs), flash memories or other memory technologies, Compact Disk Read-Only Memories (CD-ROMs), Digital Versatile Discs (DVDs) or other optical memories, cassettes, cassette and disk memories or other magnetic memory devices, or any other non-transmission media, which can be used for storing information accessible to a computation device.
  • the machine-readable media do not include transitory media, such as modulated data signals and carriers.
  • the embodiments of this specification may be provided as a method, a system, or a computer program product. Therefore, the embodiments may be implemented as a complete hardware embodiment, a complete software embodiment, or an embodiment combing software and hardware. Moreover, the present application may be in the form of a computer program product implemented on one or more computer usable storage media (including, but not limited to, a magnetic disk memory, CD-ROM, an optical memory, etc.) comprising computer usable program codes.
  • a computer usable storage media including, but not limited to, a magnetic disk memory, CD-ROM, an optical memory, etc.
  • This specification may be described in a regular context of a computer executable instruction that is executed by a computer, such as a program module.
  • the program module comprises a routine, a program, an object, a component, a data structure, etc. for executing a particular task or implementing a particular abstract data type.
  • This specification may also be practiced in distributed computing environments. In these distributed computing environments, remote processing devices connected via communication networks carry out tasks. In the distributed computing environments, a program module may be located in local and remote computer storage media, including storage devices.

Landscapes

  • Business, Economics & Management (AREA)
  • Engineering & Computer Science (AREA)
  • Accounting & Taxation (AREA)
  • Theoretical Computer Science (AREA)
  • Strategic Management (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Finance (AREA)
  • Computer Security & Cryptography (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
  • Telephone Function (AREA)
  • Collating Specific Patterns (AREA)
  • User Interface Of Digital Computer (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Cash Registers Or Receiving Machines (AREA)
  • Telephonic Communication Services (AREA)
US16/400,550 2017-01-03 2019-05-01 Scan and pay method and device utilized in mobile apparatus Active 2038-01-06 US10990957B2 (en)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
CN201710001426.2A CN108269084A (zh) 2017-01-03 2017-01-03 一种用于在移动设备上进行扫码支付的方法及装置
CN201710001426.2 2017-01-03
PCT/CN2017/118277 WO2018126924A1 (zh) 2017-01-03 2017-12-25 一种用于在移动设备上进行扫码支付的方法及装置

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/118277 Continuation WO2018126924A1 (zh) 2017-01-03 2017-12-25 一种用于在移动设备上进行扫码支付的方法及装置

Publications (2)

Publication Number Publication Date
US20190259021A1 US20190259021A1 (en) 2019-08-22
US10990957B2 true US10990957B2 (en) 2021-04-27

Family

ID=62770504

Family Applications (1)

Application Number Title Priority Date Filing Date
US16/400,550 Active 2038-01-06 US10990957B2 (en) 2017-01-03 2019-05-01 Scan and pay method and device utilized in mobile apparatus

Country Status (15)

Country Link
US (1) US10990957B2 (es)
EP (1) EP3567534A4 (es)
JP (2) JP2020513622A (es)
KR (1) KR102137919B1 (es)
CN (1) CN108269084A (es)
AU (2) AU2017390725B2 (es)
BR (1) BR112019010976A2 (es)
CA (1) CA3043391C (es)
MX (1) MX2019005359A (es)
MY (1) MY191645A (es)
PH (1) PH12019501081A1 (es)
RU (1) RU2725158C1 (es)
TW (1) TWI681350B (es)
WO (1) WO2018126924A1 (es)
ZA (1) ZA201903303B (es)

Families Citing this family (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109615802A (zh) * 2018-11-05 2019-04-12 北京三快在线科技有限公司 用于自助收银的方法，自助收银设备和用户端，存储介质
CN110046881A (zh) 2018-11-19 2019-07-23 阿里巴巴集团控股有限公司 离线场景下的支付处理方法、服务器及可读存储介质
CN111626726B (zh) * 2019-02-28 2023-07-21 百度在线网络技术（北京）有限公司 生活缴费方法、装置、设备及存储介质
JP6765483B1 (ja) * 2019-07-24 2020-10-07 ＬＩＮＥ Ｐａｙ株式会社 情報処理方法、プログラム、端末
WO2021014786A1 (ja) * 2019-07-24 2021-01-28 ＬＩＮＥ Ｐａｙ株式会社 情報処理方法、プログラム、端末
JP7306770B2 (ja) * 2019-07-24 2023-07-11 ＬＩＮＥ Ｐａｙ株式会社 プログラム、情報処理方法、端末
JP6815447B1 (ja) * 2019-07-24 2021-01-20 ＬＩＮＥ Ｐａｙ株式会社 プログラム、情報処理方法、端末
JP7306771B2 (ja) * 2019-07-24 2023-07-11 ＬＩＮＥ Ｐａｙ株式会社 プログラム、情報処理方法、端末
CN110516918B (zh) * 2019-08-02 2024-05-03 创新先进技术有限公司 一种风险识别方法和装置
CN113657886B (zh) * 2019-11-25 2024-01-02 支付宝（中国）网络技术有限公司 一种支付系统、方法、服务器设备、介质及装置
CN111445258A (zh) * 2020-06-12 2020-07-24 支付宝(杭州)信息技术有限公司 风险防控信息处理方法、装置及设备
CN111932244B (zh) * 2020-07-24 2023-10-20 中国银联股份有限公司 信息处理方法、装置、设备及介质
US20220351211A1 (en) * 2020-12-11 2022-11-03 Rakuten Group, Inc. Fraud detection system, fraud detection device, fraud detection method, and program
CN113159757B (zh) * 2021-01-19 2023-06-30 中国银联股份有限公司 一种支付码生成方法及装置
US20230396649A1 (en) * 2022-06-02 2023-12-07 Vmware, Inc. Url pattern-based risk scoring and anomaly detection
CN115049395B (zh) * 2022-08-15 2022-11-11 山东双仁信息技术有限公司 一种移动支付安全检测方法及系统
CN115510984B (zh) * 2022-09-29 2024-01-02 广州合利宝支付科技有限公司 支付平台的防侵入方法、系统及云平台

Citations (60)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020073027A1 (en) 2000-12-11 2002-06-13 Hui Helen Shan-Shan Mobile payment system
US6430305B1 (en) * 1996-12-20 2002-08-06 Synaptics, Incorporated Identity verification methods
JP2004258845A (ja) 2003-02-25 2004-09-16 Ntt Data Systems Corp 本人認証装置、行動記録方法、交通費精算方法
US20040257197A1 (en) * 2001-07-10 2004-12-23 American Express Travel Related Services Company, Inc. Method for biometric security using a transponder-reader
JP2005208822A (ja) 2004-01-21 2005-08-04 Seiko Epson Corp 認証装置、携帯端末、電子決済システムおよび認証プログラム
US20060000891A1 (en) * 2004-07-01 2006-01-05 American Express Travel Related Services Company, Inc. System for biometric security using a smartcard
US20060206709A1 (en) 2002-08-08 2006-09-14 Fujitsu Limited Authentication services using mobile device
KR20060132763A (ko) 2006-09-04 2006-12-22 김동규 오티피코드가 부가된 바코드 인증 시스템 및 그 방법
CN101025806A (zh) 2006-02-20 2007-08-29 普天信息技术研究院 一种用移动通信终端进行费用支付的身份认证方法
US20070260558A1 (en) * 2006-04-17 2007-11-08 Look Thomas F Methods and systems for secure transactions with electronic devices
US7379921B1 (en) 2004-11-08 2008-05-27 Pisafe, Inc. Method and apparatus for providing authentication
US20080133351A1 (en) 2006-10-24 2008-06-05 Brigette White Method and apparatus for reward messaging, discounting and redemption at the point of interaction
US7483858B2 (en) 2000-02-11 2009-01-27 Internet Payments Patents Ltd. Network-based system
US20090254479A1 (en) 2008-04-02 2009-10-08 Pharris Dennis J Transaction server configured to authorize payment transactions using mobile telephone devices
JP2009301440A (ja) 2008-06-16 2009-12-24 Nippon Telegr & Teleph Corp <Ntt> 個人認証装置および個人認証方法
JP2010097467A (ja) 2008-10-17 2010-04-30 Nomura Research Institute Ltd リスクベース認証システムおよびリスクベース認証方法
US20100138344A1 (en) * 2008-12-02 2010-06-03 Ebay Inc. Mobile barcode generation and payment
US20100299258A1 (en) * 1999-12-10 2010-11-25 Terri Page System and method for verifying the authenticity of a check and authorizing payment thereof
CN101958025A (zh) 2010-09-06 2011-01-26 广东铭鸿数据处理有限公司 一种应用条码技术的手机支付方法、现场支付终端及系统
US20110033090A1 (en) 2009-08-04 2011-02-10 International Business Machines Reflexive iris template
US20110153497A1 (en) * 2009-12-21 2011-06-23 Honeywell International Inc. Secure transaction system and method based on biometric identification
US20110202453A1 (en) 2010-02-15 2011-08-18 Oto Technologies, Llc System and method for mobile secure transaction confidence score
US20120084200A1 (en) 2010-10-01 2012-04-05 Michel Triana Systems and methods for completing a financial transaction
US20120143722A1 (en) 2007-05-04 2012-06-07 Michael Sasha John Fraud Deterrence for Electronic Transactions
CN102609837A (zh) 2012-01-21 2012-07-25 伯泰雄森（北京）网络科技有限公司 基于特定信息与终端号码关联的支付方法和系统
WO2012113189A1 (zh) 2011-02-23 2012-08-30 中兴通讯股份有限公司 移动支付系统、移动终端及移动支付业务的实现方法
US8380177B2 (en) 2010-04-09 2013-02-19 Paydiant, Inc. Mobile phone payment processing methods and systems
WO2013023499A1 (zh) 2011-08-17 2013-02-21 广州广电运通金融电子股份有限公司 手机支付安全控制方法及系统
US20130159186A1 (en) 2011-12-19 2013-06-20 Sequent Software Inc. System and Method for One-Time Payment Authorization in a Portable Communication Device
US20130240622A1 (en) 2011-07-18 2013-09-19 Andrew H. B. Zhou Facilitating mobile device payments using mobile payment account, mobile barcode and universal digital mobile currency
US8666893B1 (en) * 2009-01-05 2014-03-04 Bank Of America Corporation Electronic funds transfer authentication system
CN103745397A (zh) 2014-01-27 2014-04-23 上海坤士合生信息科技有限公司 基于位置场景识别实现电子交易风险控制的系统及方法
CN103955637A (zh) 2014-04-09 2014-07-30 可牛网络技术（北京）有限公司 移动终端用户身份的识别方法及装置
US20140316984A1 (en) 2013-04-17 2014-10-23 International Business Machines Corporation Mobile device transaction method and system
US20150039507A1 (en) 2013-07-31 2015-02-05 Wistron Corporation Mobile device and authentication method for mobile payment system
US20150120547A1 (en) * 2013-10-29 2015-04-30 Mastercard International Incorporated Systems and methods for tokenless authentication of consumers during payment transactions
CN104835040A (zh) 2015-05-26 2015-08-12 浙江维尔科技股份有限公司 一种支付方法及系统
US20150269577A1 (en) * 2014-03-18 2015-09-24 International Business Machines Corporation Detecting fraudulent mobile payments
JP2015176233A (ja) 2014-03-13 2015-10-05 株式会社日立ソリューションズ 認証装置、認証システム及び認証方法
WO2015157021A1 (en) 2014-04-07 2015-10-15 Eyeverify, Llc Bio leash for user authentication
US20150363785A1 (en) * 2014-06-12 2015-12-17 Mastercard International Incorporated Systems and methods for consumer authentication using behavioral biometrics
CN105243539A (zh) 2015-09-15 2016-01-13 重庆智韬信息技术中心 实现二维码安全支付的身份认证方法
US9240005B2 (en) 2009-11-06 2016-01-19 Mastercard International, Incorporated Methods for risk management in payment-enabled mobile device
US20160028724A1 (en) 2014-07-28 2016-01-28 Microsoft Corporation Identity Reputation
US20160110718A1 (en) * 2014-10-15 2016-04-21 Paypal, Inc. Systems and methods for facilitating offline payments
US20160132864A1 (en) 2014-11-07 2016-05-12 Paypal, Inc. Payment processing apparatus
US20160162901A1 (en) * 2013-04-25 2016-06-09 Offla Selfsafe Ltd. Remotely generated behavioral profile for storage and use on mobile device
US20160189149A1 (en) * 2014-12-30 2016-06-30 Ebay Inc. Biometric systems and methods for authentication and determination of group characteristics
CN105740667A (zh) 2014-12-10 2016-07-06 阿里巴巴集团控股有限公司 一种基于用户行为的信息识别方法及装置
CN105740666A (zh) 2014-12-09 2016-07-06 阿里巴巴集团控股有限公司 识别线上操作风险的方法及装置
CN205608764U (zh) 2016-04-25 2016-09-28 广州尚汉信息科技有限公司 一种证件的识别系统及证件
CN106127461A (zh) 2016-06-16 2016-11-16 中国银联股份有限公司 双向验证移动支付方法及系统
WO2016188281A1 (zh) 2015-05-25 2016-12-01 阿里巴巴集团控股有限公司 信息交互方法、装置及系统
TW201701205A (zh) 2015-06-26 2017-01-01 康迪 在線離線整合商務之驗證暨勾稽裝置、雲端伺服器及驗證暨勾稽方法
US20170011405A1 (en) * 2015-07-09 2017-01-12 Mastercard International Incorporated Simultaneous multi-factor authentication systems and methods for payment transactions
US9785943B2 (en) 2010-03-25 2017-10-10 Mastercard International Incorporated Methods for risk management in payment device system
US20170357981A1 (en) * 2016-06-13 2017-12-14 Mastercard International Incorporated Systems and Methods for Use in Approving Transactions, Based on Biometric Data
US20180012227A1 (en) * 2016-07-05 2018-01-11 NXT-ID, Inc. Biometric, Behavioral-Metric, Knowledge-Metric, and Electronic-Metric Directed Authentication and Transaction Method and System
US20180150846A1 (en) * 2016-11-29 2018-05-31 Mastercard Asia/Pacific Pte. Ltd. System and method for utilizing biometric data in a payment transaction
US20180176727A1 (en) * 2016-12-15 2018-06-21 David H. Williams Systems and methods of using wireless location, context, and/or one or more communication networks for monitoring for, preempting, and/or mitigating pre-identified behavior

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10769625B2 (en) * 2013-12-20 2020-09-08 Cellco Partnership Dynamic generation of quick response (QR) codes for secure communication from/to a mobile device

Patent Citations (68)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6430305B1 (en) * 1996-12-20 2002-08-06 Synaptics, Incorporated Identity verification methods
US20100299258A1 (en) * 1999-12-10 2010-11-25 Terri Page System and method for verifying the authenticity of a check and authorizing payment thereof
US7483858B2 (en) 2000-02-11 2009-01-27 Internet Payments Patents Ltd. Network-based system
US20020073027A1 (en) 2000-12-11 2002-06-13 Hui Helen Shan-Shan Mobile payment system
US20040257197A1 (en) * 2001-07-10 2004-12-23 American Express Travel Related Services Company, Inc. Method for biometric security using a transponder-reader
US20060206709A1 (en) 2002-08-08 2006-09-14 Fujitsu Limited Authentication services using mobile device
JP2004258845A (ja) 2003-02-25 2004-09-16 Ntt Data Systems Corp 本人認証装置、行動記録方法、交通費精算方法
JP2005208822A (ja) 2004-01-21 2005-08-04 Seiko Epson Corp 認証装置、携帯端末、電子決済システムおよび認証プログラム
US20060000891A1 (en) * 2004-07-01 2006-01-05 American Express Travel Related Services Company, Inc. System for biometric security using a smartcard
US7379921B1 (en) 2004-11-08 2008-05-27 Pisafe, Inc. Method and apparatus for providing authentication
CN101025806A (zh) 2006-02-20 2007-08-29 普天信息技术研究院 一种用移动通信终端进行费用支付的身份认证方法
KR20090005336A (ko) 2006-04-17 2009-01-13 베리텍 인코포레이티드 전자장치로 안전한 거래를 위한 방법 및 시스템
US20070260558A1 (en) * 2006-04-17 2007-11-08 Look Thomas F Methods and systems for secure transactions with electronic devices
KR20060132763A (ko) 2006-09-04 2006-12-22 김동규 오티피코드가 부가된 바코드 인증 시스템 및 그 방법
US20080133351A1 (en) 2006-10-24 2008-06-05 Brigette White Method and apparatus for reward messaging, discounting and redemption at the point of interaction
US20120143722A1 (en) 2007-05-04 2012-06-07 Michael Sasha John Fraud Deterrence for Electronic Transactions
US20090254479A1 (en) 2008-04-02 2009-10-08 Pharris Dennis J Transaction server configured to authorize payment transactions using mobile telephone devices
JP2009301440A (ja) 2008-06-16 2009-12-24 Nippon Telegr & Teleph Corp <Ntt> 個人認証装置および個人認証方法
JP2010097467A (ja) 2008-10-17 2010-04-30 Nomura Research Institute Ltd リスクベース認証システムおよびリスクベース認証方法
US20100138344A1 (en) * 2008-12-02 2010-06-03 Ebay Inc. Mobile barcode generation and payment
US8666893B1 (en) * 2009-01-05 2014-03-04 Bank Of America Corporation Electronic funds transfer authentication system
US20110033090A1 (en) 2009-08-04 2011-02-10 International Business Machines Reflexive iris template
US9240005B2 (en) 2009-11-06 2016-01-19 Mastercard International, Incorporated Methods for risk management in payment-enabled mobile device
US20110153497A1 (en) * 2009-12-21 2011-06-23 Honeywell International Inc. Secure transaction system and method based on biometric identification
US20110202453A1 (en) 2010-02-15 2011-08-18 Oto Technologies, Llc System and method for mobile secure transaction confidence score
US9785943B2 (en) 2010-03-25 2017-10-10 Mastercard International Incorporated Methods for risk management in payment device system
US8380177B2 (en) 2010-04-09 2013-02-19 Paydiant, Inc. Mobile phone payment processing methods and systems
CN101958025A (zh) 2010-09-06 2011-01-26 广东铭鸿数据处理有限公司 一种应用条码技术的手机支付方法、现场支付终端及系统
US20120084200A1 (en) 2010-10-01 2012-04-05 Michel Triana Systems and methods for completing a financial transaction
WO2012113189A1 (zh) 2011-02-23 2012-08-30 中兴通讯股份有限公司 移动支付系统、移动终端及移动支付业务的实现方法
US20130240622A1 (en) 2011-07-18 2013-09-19 Andrew H. B. Zhou Facilitating mobile device payments using mobile payment account, mobile barcode and universal digital mobile currency
WO2013023499A1 (zh) 2011-08-17 2013-02-21 广州广电运通金融电子股份有限公司 手机支付安全控制方法及系统
US20130159186A1 (en) 2011-12-19 2013-06-20 Sequent Software Inc. System and Method for One-Time Payment Authorization in a Portable Communication Device
RU2014129856A (ru) 2011-12-19 2016-02-10 Сиквент Софтвэр Инк. Система и способ динамического временного разрешения на платеж в переносном устройстве связи
US20130191275A1 (en) 2012-01-21 2013-07-25 Broaddeep (Beijing) Network Technology Co., Ltd Method and system for payment based on correlation between product specific information and terminal numbers
CN102609837A (zh) 2012-01-21 2012-07-25 伯泰雄森（北京）网络科技有限公司 基于特定信息与终端号码关联的支付方法和系统
CN105164707A (zh) 2012-09-15 2015-12-16 周海斌 使用移动支付账户、移动条码和通用数字移动货币来便于移动设备支付
US20140316984A1 (en) 2013-04-17 2014-10-23 International Business Machines Corporation Mobile device transaction method and system
US20160162901A1 (en) * 2013-04-25 2016-06-09 Offla Selfsafe Ltd. Remotely generated behavioral profile for storage and use on mobile device
CN104348825A (zh) 2013-07-31 2015-02-11 纬创资通股份有限公司 用于移动支付系统的移动装置及验证方法
TWI553568B (zh) 2013-07-31 2016-10-11 緯創資通股份有限公司 用於行動支付系統之行動裝置及驗證方法
US20150039507A1 (en) 2013-07-31 2015-02-05 Wistron Corporation Mobile device and authentication method for mobile payment system
US20150120547A1 (en) * 2013-10-29 2015-04-30 Mastercard International Incorporated Systems and methods for tokenless authentication of consumers during payment transactions
CN103745397A (zh) 2014-01-27 2014-04-23 上海坤士合生信息科技有限公司 基于位置场景识别实现电子交易风险控制的系统及方法
JP2015176233A (ja) 2014-03-13 2015-10-05 株式会社日立ソリューションズ 認証装置、認証システム及び認証方法
US20150269577A1 (en) * 2014-03-18 2015-09-24 International Business Machines Corporation Detecting fraudulent mobile payments
WO2015157021A1 (en) 2014-04-07 2015-10-15 Eyeverify, Llc Bio leash for user authentication
CN103955637A (zh) 2014-04-09 2014-07-30 可牛网络技术（北京）有限公司 移动终端用户身份的识别方法及装置
US20150363785A1 (en) * 2014-06-12 2015-12-17 Mastercard International Incorporated Systems and methods for consumer authentication using behavioral biometrics
US20160028724A1 (en) 2014-07-28 2016-01-28 Microsoft Corporation Identity Reputation
US20160110718A1 (en) * 2014-10-15 2016-04-21 Paypal, Inc. Systems and methods for facilitating offline payments
US20160132864A1 (en) 2014-11-07 2016-05-12 Paypal, Inc. Payment processing apparatus
CN105740666A (zh) 2014-12-09 2016-07-06 阿里巴巴集团控股有限公司 识别线上操作风险的方法及装置
CN105740667A (zh) 2014-12-10 2016-07-06 阿里巴巴集团控股有限公司 一种基于用户行为的信息识别方法及装置
US20160189149A1 (en) * 2014-12-30 2016-06-30 Ebay Inc. Biometric systems and methods for authentication and determination of group characteristics
US20180068290A1 (en) 2015-05-25 2018-03-08 Alibaba Group Holding Limited Transaction scheme for offline payment
WO2016188281A1 (zh) 2015-05-25 2016-12-01 阿里巴巴集团控股有限公司 信息交互方法、装置及系统
CN104835040A (zh) 2015-05-26 2015-08-12 浙江维尔科技股份有限公司 一种支付方法及系统
TWI584210B (zh) 2015-06-26 2017-05-21 康迪 在線離線整合商務之驗證暨勾稽裝置、雲端伺服器及驗證暨勾稽方法
TW201701205A (zh) 2015-06-26 2017-01-01 康迪 在線離線整合商務之驗證暨勾稽裝置、雲端伺服器及驗證暨勾稽方法
US20170011405A1 (en) * 2015-07-09 2017-01-12 Mastercard International Incorporated Simultaneous multi-factor authentication systems and methods for payment transactions
CN105243539A (zh) 2015-09-15 2016-01-13 重庆智韬信息技术中心 实现二维码安全支付的身份认证方法
CN205608764U (zh) 2016-04-25 2016-09-28 广州尚汉信息科技有限公司 一种证件的识别系统及证件
US20170357981A1 (en) * 2016-06-13 2017-12-14 Mastercard International Incorporated Systems and Methods for Use in Approving Transactions, Based on Biometric Data
CN106127461A (zh) 2016-06-16 2016-11-16 中国银联股份有限公司 双向验证移动支付方法及系统
US20180012227A1 (en) * 2016-07-05 2018-01-11 NXT-ID, Inc. Biometric, Behavioral-Metric, Knowledge-Metric, and Electronic-Metric Directed Authentication and Transaction Method and System
US20180150846A1 (en) * 2016-11-29 2018-05-31 Mastercard Asia/Pacific Pte. Ltd. System and method for utilizing biometric data in a payment transaction
US20180176727A1 (en) * 2016-12-15 2018-06-21 David H. Williams Systems and methods of using wireless location, context, and/or one or more communication networks for monitoring for, preempting, and/or mitigating pre-identified behavior

Non-Patent Citations (12)

* Cited by examiner, † Cited by third party
Title
Examination Report No. 1 for Australian Application No. 2017390725 dated Jan. 21, 2020.
First Office Action and First Search for Taiwanese Application No. 106139460, dated Mar. 29, 2019, 8 pages.
First Office Action for Chinese Application No. 201710001426.2 dated Feb. 3, 2020.
First Search Report for Chinese Application No. 201710001426.2 dated Jan. 14, 2020.
International Preliminary Report on Patentability for International PCT Application No. PCT/CN2017/118277, dated Jul. 18, 2019, 9 pages.
Notice of Allowance for Korean Application No. 10-2019-7015667 dated Jun. 23, 2020.
Office Action and Search Report for Russian Application No. 2019114212 dated Feb. 21, 2020.
Office Action for Japanese Application No. 2019-529606 dated May 26, 2020.
Search Report for European Application No. 17889771.6 dated Apr. 24, 2020.
Second Examination Report for Australian Application No. 2017390725 dated Jun. 26, 2020.
Second Office Action for Chinese Application No. 201710001426.2 dated Apr. 13, 2020.
Written Opinion of the International Searching Authority and International Search Report for International PCT Application No. PCT/CN2017/118277, dated Mar. 28, 2018, 12 pages.

Also Published As

Publication number Publication date
EP3567534A1 (en) 2019-11-13
CN108269084A (zh) 2018-07-10
MY191645A (en) 2022-07-05
WO2018126924A1 (zh) 2018-07-12
KR102137919B1 (ko) 2020-07-27
PH12019501081A1 (en) 2019-12-11
JP2020513622A (ja) 2020-05-14
AU2019101596A4 (en) 2020-01-23
AU2017390725B2 (en) 2020-10-22
KR20190077053A (ko) 2019-07-02
JP7092911B2 (ja) 2022-06-28
BR112019010976A2 (pt) 2019-10-15
TWI681350B (zh) 2020-01-01
EP3567534A4 (en) 2020-05-27
RU2725158C1 (ru) 2020-06-30
AU2017390725A1 (en) 2019-05-23
US20190259021A1 (en) 2019-08-22
CA3043391C (en) 2022-05-17
CA3043391A1 (en) 2018-07-12
TW201826189A (zh) 2018-07-16
MX2019005359A (es) 2019-07-01
ZA201903303B (en) 2021-07-28
JP2021089774A (ja) 2021-06-10

Similar Documents

Publication Publication Date Title
US10990957B2 (en) Scan and pay method and device utilized in mobile apparatus
KR101839860B1 (ko) 동적 키보드 및 터치스크린 생체 측정
US11263634B2 (en) Payment method and device
US20190130411A1 (en) Method and system for data processing
CN111414119A (zh) 用于生物特征认证系统的方法、系统和装置
KR102090940B1 (ko) 특징 정보를 추출하기 위한 방법 및 시스템
US12021864B2 (en) Systems and methods for contactless authentication using voice recognition
JP7444219B2 (ja) 生体データ照合システム
US20240296847A1 (en) Systems and methods for contactless authentication using voice recognition
EP3327613A1 (en) Fingerprint entry method, apparatus, and terminal device
CN110730459B (zh) 一种近场通信认证的发起方法及相关装置
US20200204365A1 (en) Apparatus, system and method for application-specific biometric processing in a computer system
CN111160251B (zh) 一种活体识别方法及装置
WO2024212861A1 (zh) 应用程序的登录验证方法、装置、电子设备、计算机可读存储介质及计算机程序产品
US10488940B2 (en) Input commands via visual cues
CN111784352A (zh) 认证风险识别方法、装置和电子设备
AU2021101257A4 (en) Usb: auto data store your gmail and link share your mobile no.) using ai- based programming
EP4260519A1 (en) User authentication
CN118575155A (zh) 电子设备及其控制方法
Nakakuni et al. A method of personal authentication by shape recognition of the lips and front teeth

Legal Events

Date Code Title Description
AS Assignment

Owner name: ALIBABA GROUP HOLDING LIMITED, CAYMAN ISLANDS

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:LU, YICHENG;CHEN, SHUAI;CHEN, TAO;AND OTHERS;REEL/FRAME:049052/0373

Effective date: 20190409

FEPP Fee payment procedure

Free format text: ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: BIG.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

STPP Information on status: patent application and granting procedure in general

Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION

STPP Information on status: patent application and granting procedure in general

Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER

AS Assignment

Owner name: ADVANTAGEOUS NEW TECHNOLOGIES CO., LTD., CAYMAN ISLANDS

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:ALIBABA GROUP HOLDING LIMITED;REEL/FRAME:053702/0392

Effective date: 20200826

AS Assignment

Owner name: ADVANCED NEW TECHNOLOGIES CO., LTD., CAYMAN ISLANDS

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:ADVANTAGEOUS NEW TECHNOLOGIES CO., LTD.;REEL/FRAME:053796/0281

Effective date: 20200910

STPP Information on status: patent application and granting procedure in general

Free format text: NOTICE OF ALLOWANCE MAILED -- APPLICATION RECEIVED IN OFFICE OF PUBLICATIONS

STPP Information on status: patent application and granting procedure in general

Free format text: PUBLICATIONS -- ISSUE FEE PAYMENT RECEIVED

STPP Information on status: patent application and granting procedure in general

Free format text: PUBLICATIONS -- ISSUE FEE PAYMENT VERIFIED

STCF Information on status: patent grant

Free format text: PATENTED CASE

MAFP Maintenance fee payment

Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

Year of fee payment: 4