In various embodiments, the present invention relates generally to systems and methods for ensuring secure payment transactions.
Traditional methodologies for making payments utilize paper instruments, such as cash or checks, and electronic transactions, such as credit or debit cards. Paper instruments advantageously allow a full payment to be completed immediately at the point of sale without the need for any further exchange after the good or service has been delivered. When the transferred funds are large, however, paper instruments may not be practical. In addition, the fear of theft or loss discourages possession of paper instruments. Electronic transactions developed successfully due to the advent of secure data systems and networks that permit payments made to vendors at the point of sale without physical transfer of paper currency. Electronic transactions thus greatly increase consumer convenience, especially when the transacted commerce is large. Electronic commerce, however, generally requires fixed, immobile infrastructure (such as automated teller machines (ATMs), shared banking networks, or point-of-sale (POS) terminals) that may sometimes be inaccessible. In addition, although completion of a transaction typically requires the physical presence of the consumer—who may be asked to authenticate himself, present a physical token and/or provide a signature to a merchant or bank—fraudulent use of the physical tokens (e.g., credit and debit card numbers) still occurs frequently.
Widespread usage of computationally advanced mobile telecommunication devices can potentially extend the reach of electronic transactions. Because a mobile payment (or “m-payment”) may directly initiate, authorize, and confirm an exchange of financial value in return for goods and services, the need for consumers to carry paper instruments or physical tokens and/or access immobile infrastructure is minimized. Existing m-payment approaches typically create a transaction flow in which a consumer presents payment data to a merchant who then presents it to a payment processor; the customer data (e.g., a credit-card or debit-card number) required to transact the payment is stored directly on a physical medium (e.g., credit cards) or digitally on network-accessible servers (e.g., Google wallet or a secured near-field communication (NFC) mobile wallet). At each stage of this traditional m-payment, however, the collectively stored consumer data is accessible and vulnerable to compromise.
Securing customers' privacy during payment transactions is of paramount importance; even a few instances of customers suffering a financial loss may destroy the marketplace viability of an m-payment scheme. Because conventional m-payments workflows store the identity and financial account information of the user within a single organization or server cluster, the central store of sensitive data provides a tempting target to malicious “hackers,” who circumvent security measures and steal payment credentials. Such violations have been fairly common in Internet-based commerce; many consumers have experienced identity theft when information is stolen from an entity that maintains financial accounts. As a result, adoption of mobile devices that facilitate m-payments has been limited by security concerns; these security concerns have discouraged users from signing up form-payment procedures that require registration or provide personal information to the system infrastructure.
Consequently, there is a need for an approach that is conveniently implemented and used, but which can securely transact payments for goods or services using a mobile device.
In various embodiments, the present invention facilitates secure mobile payments by distributing storage of the transaction-enabling data elements, including the customer's identity and information about the payment instrument, among unrelated parties. Because the customer's data is stored by multiple parties, unauthorized access to the records of any single party in the transaction flow will not enable a thief to “spoof’ the user's identity and initiate transactions under his name. In addition, the customer's information may be distributed so that various parties directly involved in a payment transaction receive no information about the customer's information stored by other parties. The parties that are involved in a payment transaction thereby cannot store any payment-relevant information transmitted from other parties. For example, in a “triple blind” payment system, none of the paying party (i.e., the customer), the party receiving the payment (i.e., the merchant), or the party facilitating the payment (i.e., the identity and payment manager) possesses both the customer's identity and the underlying payment instrument (e.g., a credit-card or debit-card number) or any data that could be used to reverse engineer or “spoof’ the instrument. Accordingly, the customer's identity and privacy is highly secure and the possibility of financial losses for the customer is minimized during a mobile-payment transaction.
Accordingly, in one aspect, the invention pertains to a server-based method of facilitating payment by a user registered with a server. In representative embodiments, the method includes, at the server, generating and storing, for the user, a code readable by a merchant device; transmitting the code to a mobile device of the user; facilitating provision of information characterizing a payment instrument from the user to a payment-processing entity without storing the data at the server; receiving, from the payment-processing entity, a token indicative of the payment instrument but not encoding data that would enable use of the instrument; computationally associating the token with the user; receiving, from a merchant device, the code and a payment amount; matching the received code to the user and retrieving the token associated with the user; and providing the token and the payment amount to the payment-processing entity to facilitate completion of a transaction between the user and the merchant.
The code may be a QR code, a bar code, a radio-frequency identification, a near-field-communication signal, an audio signal, and/or an infrared signal. Additionally, the code may be a seed code that can further generate a unique “mature” code readable by a merchant device. The code may be reset, by the server, after a predetermined period of time or upon receiving a request, by the server, from the user. In one embodiment, the code is transmitted from the server to the mobile device via wireless cell phone communication, Internet, ultrasound, Bluetooth, or near-field communication.
In various embodiments, the server includes a database for storing records, a database record being associated with the user and including user-identifying information, the code or a seed therefor, and the token. In some embodiments, the mobile device is selected from the group including a cellular phone, a smart phone, a computer, a personal digital assistant (PDA), an Internet Protocol Television and an electronic gaming device.
In another aspect, the invention relates to a server for facilitating payment by a user registered with the server. In various embodiments, the server includes a processor; a processor-executable code-generation module for generating, for the user, a code readable by a merchant device; a communication module; a web server for generating a form-containing web page and associated programming for execution on a client-side computer; and a database for storing a token received from the payment-processing entity via the communication module and associating the token with the user. The programming may be executable to cause transmission of information entered on the form to a payment-processing entity without storing the data at the server. In various embodiments, the processor is configured to (i) operate the communication module to cause the code to be transmitted to a mobile device of the user, (ii) operate the communication module to receive, from a merchant, the readable code and a payment amount, (iii) match the received readable code to the user and retrieving the token associated with the user, and (iv) following the match, operate the communication module to provide the token and the payment amount to a payment processor to facilitate completion of a transaction between the user and the merchant.
The code may be a QR code, a bar code, a radio-frequency identification, a near-field-communication signal, an audio signal, and/or an infrared signal. In addition, the code may be a seed code for generation, by the code-generating module, a unique mature code readable by a merchant device. The code may be reset by the code-generation module after a predetermined period of time or upon receiving a request from the user.
In various embodiments, the transmitted form is configured to receive information characterizing a payment instrument. The database includes a series of stored records, each record being associated with a user and including user-identifying information, the code or a seed therefor, and the token. In some embodiments, the communication module transmits the code from the server to the mobile device via wireless cell phone communication, Internet, ultrasound, Bluetooth, or near-field communication.
Reference throughout this specification to “one example,” “an example,” “one embodiment,” or “an embodiment” means that a particular feature, structure, or characteristic described in connection with the example is included in at least one example of the present technology. Thus, the occurrences of the phrases “in one example,” “in an example,” “one embodiment,” or “an embodiment” in various places throughout this specification are not necessarily all referring to the same example. Furthermore, the particular features, structures, routines, steps, or characteristics may be combined in any suitable manner in one or more examples of the technology. The headings provided herein are for convenience only and are not intended to limit or interpret the scope or meaning of the claimed technology.
In the drawings, like reference characters generally refer to the same parts throughout the different views. Also, the drawings are not necessarily to scale, with an emphasis instead generally being placed upon illustrating the principles of the invention. In the following description, various embodiments of the present invention are described with reference to the following drawings, in which:
Refer first to
Referring to
Referring to
Referring to
In the registration phase, the user registers a payment instrument (e.g., a credit card, a bank account, or a pre-loaded payment card) to her user account. In a representative transaction flow, the user U first issues a registration request to the management server 106 using the mobile device 102. The management server 106 responds to the request with a registration form (e.g., in the form of a web page), which is displayed on the mobile device 102 in a manner that permits the user U to enter information identifying the payment instrument to be registered. In one embodiment, the registration form includes a client-side script that directly submits the data entered by the user to a third-party payment processor's gateway 320 over, for example, a secure sockets layer (SSL) connection. The user-entered data is stored in or by the third-party payment gateway 320, which also generates a “redirect” uniform resource locator (URL) that includes the Internet address of the management server 106 and a token that identifies the payment instrument, but which does not identify the user U. When the user submits the entered registration data, the client-side script causes a request for the redirect URL also to be transmitted to the gateway 320. When the redirect URL arrives at the mobile device 102 and is processed by the user's browser, it redirects the browser back to the management server 106 without displaying any content, thus creating the impression that the user has never left the management server site. In another representative transaction flow, the user U transmits information about the payment instrument to the management server 106 using the mobile device 102. The management server 106 encrypts the received information with a one-way key and passes the encrypted data to the third-party payment gateway 320. The third-party gateway 320, which is the only party having the key to decrypt the date in the transaction, generates a token that identifies the registered payment instrument. The generated token is transmitted back to the management server 106 and stored therein for transacting future payments. Because the data including a user's identity and payment instrument are separately stored in the management server 106 and the third-party payment gateway 320, respectively, unauthorized access to any one of the records therein is insufficient to initiate a payment transaction under the user's name; this, again, ensures the security of the mobile payment.
In various embodiments, the token generated by the third-party payment gateway 320 is transmitted to the management server 106. The management server 106 associates the token with the user's account record and stores it in the database 314 as a payment identifier. Upon receiving a payment request from the user U, the management server 106 uses the stored token to initiate the payment transaction through the third-party payment gateway 320, against the payment instrument previously submitted, without ever having knowledge or possession of the payment-instrument data itself. Since the payment-instrument data is not stored and cannot be obtained by the management server 106, this approach, again, prevents fraudulent payments.
In the use phase, the management server 106 executes the instructions of the code payment process 222 and transmits a QR code to the user's mobile device 102 for presentation to a merchant; as noted above, the QR code may be revised periodically for security purposes, and is typically generated using encryption based on user-specific information in the database 314. A payment transaction is initiated when the user presents the QR code stored in the mobile device 102 to the merchant system 108. The merchant system 108 may scan the code using, e.g., a POS integrated scanner 322, and thereupon transmits the scanned data along with the payment amount to the management server 106. Thus, at the time of the payment transaction, neither the merchant 108 nor the user U has access to the underlying payment instrument; the QR code merely identifies the user. Further, in the case of a QR code that resets, even an image of the presented QR code may not be used again for future payments (as the user would by then have a new QR code).
In various embodiments, upon receiving the QR code and payment amount from the merchant system 108, the management server 106 decodes the QR code and matches the information therein to the user's record stored in the database 314. The management server 106 then retrieves the stored payment token associated with the user's account and passes the token and the amount to be charged to the third-party gateway 320 for authorizing a payment. The third-party payment gateway 320 authorizes and processes (or rejects) the payment request against the payment instrument corresponding to the token, and creates an associated transaction identifier or rejection code. The created identifier or code may be sent to the management server 106 for re-transmission to the merchant system 108, or may instead be sent directly to the merchant system 108 to complete the transaction. Where the created identifier is first handled by the management server 106 before transmittal to the merchant system 108, the management server 106 may generate and provide additional information (e.g., tracking information) to the merchant system 108 to enable a closed-loop environment of consumer information—e.g., effectiveness of advertisement, consumer demographics, and referral information. Again, because none of the user's mobile device 102, the merchant system 108, the management server 106, or the third-party gateway 320 possesses both user identity information and the underlying payment instrument, this triple-blind payment system provides high security for the user's identity and privacy; accordingly, the possibility of financial losses for the customer is minimized during an m-payment transaction in accordance herewith.
A representative method 400 for safely transacting a payment in accordance with embodiments of the current invention is shown in
For example, the method of identifier transferred from the customer to the merchant may be irrelevant. The transfer may include a scan of a bar code, a scan of a QR code, a NFC scan, an audio transmission, a video transmission, an IR transmission, a manual input of a code, and so forth.
More generally, those skilled in the art will readily appreciate that all parameters, dimensions, materials, and configurations described herein are meant to be exemplary and that the actual parameters, dimensions, materials, and/or configurations will depend upon the specific application or applications for which the inventive teachings is/are used. Those skilled in the art will recognize, or be able to ascertain using no more than routine experimentation, many equivalents to the specific inventive embodiments described herein. It is, therefore, to be understood that the foregoing embodiments are presented by way of example only and that, within the scope of the appended claims and equivalents thereto, inventive embodiments may be practiced otherwise than as specifically described and claimed. Inventive embodiments of the present disclosure are directed to each individual feature, system, article, material, kit, and/or method described herein. In addition, any combination of two or more such features, systems, articles, materials, kits, and/or methods, if such features, systems, articles, materials, kits, and/or methods are not mutually inconsistent, is included within the inventive scope of the present disclosure.
As used herein, the term “or” is intended to mean an inclusive “or” rather than an exclusive “or.” That is, unless specified otherwise, or clear from context, “X employs A or B” is intended to mean any of the natural inclusive permutations. That is, if X employs A; X employs B; or X employs both A and B, then “X employs A or B” is satisfied under any of the foregoing instances. Moreover, articles “a” and “an” as used in the subject specification and annexed drawings should generally be construed to mean “one or more” unless specified otherwise or clear from context to be directed to a singular form. In addition, the terms like “user equipment,” “mobile station,” “mobile,” “communication device,” “access terminal,” “terminal,” “handset,” and similar terminology, refer to a wireless device (e.g., cellular phone, smart phone, computer, PDA, set-top box, Internet Protocol Television (IPTV), electronic gaming device, printer, and so forth) utilized by a user of a wireless communication service to receive or convey data, control, voice, video, sound, gaming, or substantially any data-stream or signaling-stream. The foregoing terms are utilized interchangeably in the subject specification and related drawings. The terms “component,” “system,” “platform,” “module,” and the like refer broadly to a computer-related entity or an entity related to an operational machine with one or more specific functionalities. Such entities can be hardware, a combination of hardware and software, software, or software in execution. For example, a component may be, but is not limited to being, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, and/or a computer. By way of illustration, both an application running on a server and the server can be a component. One or more components may reside within a process and/or thread of execution and a component may be localized on one computer and/or distributed between two or more computers. Also, these components can execute from various computer readable media having various data structures stored thereon. The components may communicate via local and/or remote processes such as in accordance with a signal having one or more data packets (e.g., data from one component interacting with another component in a local system, distributed system, and/or across a network such as the Internet with other systems via the signal).
The processing unit that executes commands and instructions may be a general purpose computer, but may utilize any of a wide variety of other technologies including a special purpose computer, a microcomputer, minicomputer, mainframe computer, programmed microprocessor, micro-controller, peripheral integrated circuit element, a CSIC (customer-specific integrated circuit), ASIC (application-specific integrated circuit), a logic circuit, a digital signal processor, a programmable logic device, such as an FPGA (field-programmable gate array), PLD (programmable logic device), PLA (programmable logic array), RFID processor, smart chip, or any other device or arrangement of devices that is capable of implementing the steps of the processes of the invention.
Various implementations of the systems and techniques described here can be realized in digital electronic circuitry, integrated circuitry, specially designed ASICs (application specific integrated circuits), computer hardware, firmware, software, and/or combinations thereof. These various implementations can include implementation in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, coupled to receive data and instructions from, and to transmit data and instructions to, a storage system, at least one input device, and at least one output device.
These computer programs (also known as programs, software, software applications or code) include machine instructions for a programmable processor, and can be implemented in a high-level procedural and/or object-oriented programming language, and/or in assembly/machine language. As used herein, the terms “machine-readable medium” “computer-readable medium” refers to any computer program product, apparatus and/or device (e.g., magnetic discs, optical disks, memory, Programmable Logic Devices (PLDs)) used to provide machine instructions and/or data to a programmable processor, including a machine-readable medium that receives machine instructions as a machine-readable signal. The term “machine-readable signal” refers to any signal used to provide machine instructions and/or data to a programmable processor.
The mobile device 102 acts as a gateway for transmitting the user's data to the network 104. The mobile device 102 can support multiple communication channels for exchanging multimedia and other data with the servers 106,110 and other devices using a Wi-Fi LAN (e.g., IEEE 802.11 standard) for Internet access, a short-range Bluetooth wireless connection for point-to-point access, and/or an NFC channel for close-proximity access.
The storage devices 238, 242 may include computer storage media in the form of volatile and/or nonvolatile memory such as read only memory (ROM) and random access memory (RAM). A basic input/output system (BIOS), containing the basic routines that help to transfer information between elements, such as during start-up, is typically stored in ROM. RAM typically contains data and/or program modules that are immediately accessible to and/or presently being operated on by processing unit. The data or program modules may include an operating system, application programs, other program modules, and program data. The operating system may be or include a variety of operating systems such as Microsoft WINDOWS operating system, the UNIX operating system, the LINUX operating system, the Xenix operating system, the IBM AIX operating system, the Hewlett Packard UX operating system, the Novell NETWARE operating system, the Sun Microsystems SOLARIS operating system, the OS/2 operating system, the BeOS operating system, the MACINTOSH operating system, the APACHE operating system, an OPENS TEP operating system or another operating system of platform.
The storage devices 238, 242 may also include other removable/nonremovable, volatile/nonvolatile computer storage media. For example, a hard disk drive may read or write to nonremovable, nonvolatile magnetic media. A magnetic disk drive may read from or writes to a removable, nonvolatile magnetic disk, and an optical disk drive may read from or write to a removable, nonvolatile optical disk such as a CD-ROM or other optical media. Other removable/nonremovable, volatile/nonvolatile computer storage media that can be used in the exemplary operating environment include, but are not limited to, magnetic tape cassettes, flash memory cards, digital versatile disks, digital video tape, solid state RAM, solid state ROM, and the like. The storage media are typically connected to the system bus through a removable or non-removable memory interface.
The foregoing description does not represent an exhaustive list of all possible implementations consistent with this disclosure or of all possible variations of the implementations described. A number of implementations have been described. Nevertheless, it will be understood that various modifications may be made without departing from the spirit and scope of the systems, devices, methods and techniques described herein. For example, various forms of the flows shown above may be used, with steps re-ordered, added, or removed. Accordingly, other implementations are within the scope of the following claims.
The terms and expressions employed herein are used as terms and expressions of description and not of limitation, and there is no intention, in the use of such terms and expressions, of excluding any equivalents of the features shown and described or portions thereof. In addition, having described certain embodiments of the invention, it will be apparent to those of ordinary skill in the art that other embodiments incorporating the concepts disclosed herein may be used without departing from the spirit and scope of the invention. Accordingly, the described embodiments are to be considered in all respects as only illustrative and not restrictive.
This application is a continuation application of U.S. patent application Ser. No. 14/103,101, filed Dec. 11, 2013, which is a continuation of U.S. patent application Ser. No. 13/718,466, filed Dec. 18, 2012, now U.S. Pat. No. 8,639,619, which claims priority to and the benefit of U.S. Provisional Patent Application No. 61/671,381, filed Jul. 13, 2012, each of which is incorporated herein by this reference in its entirety.
Number | Name | Date | Kind |
---|---|---|---|
D24069 | Chase | Feb 1895 | S |
D38205 | Alexander | Aug 1906 | S |
D104560 | Chamberlain | May 1937 | S |
D127030 | Beltcher | May 1941 | S |
D154818 | Strauss | Aug 1949 | S |
D164158 | Clay | Aug 1951 | S |
D169369 | Forrester | Apr 1953 | S |
D173647 | Elle et al. | Dec 1954 | S |
D181589 | Kellock et al. | Feb 1957 | S |
D180734 | Hirose | Aug 1957 | S |
D180887 | Weinstein | Aug 1957 | S |
D181019 | Parcher | Sep 1957 | S |
D184351 | Grosso | Feb 1959 | S |
D199598 | Lanigan | Nov 1964 | S |
D210281 | Specht | Feb 1968 | S |
D213446 | Sabella | Mar 1969 | S |
D215035 | Steinbach | Aug 1969 | S |
3748765 | Bass et al. | Jul 1973 | A |
D240460 | Simonelli | Jul 1976 | S |
D240609 | Schwartz | Jul 1976 | S |
D245934 | Donaldson | Sep 1977 | S |
D249527 | Stralka | Sep 1978 | S |
D252932 | Felder | Sep 1979 | S |
D254602 | Gess | Apr 1980 | S |
D255455 | Gensike et al. | Jun 1980 | S |
D260096 | Overman et al. | Aug 1981 | S |
D268029 | Fisher | Feb 1983 | S |
D268590 | Miller et al. | Apr 1983 | S |
D270644 | Kinney | Sep 1983 | S |
D276618 | Hanke | Dec 1984 | S |
D280103 | Bonnefoy | Aug 1985 | S |
D290708 | Rea | Jul 1987 | S |
D295413 | Nakamura et al. | Apr 1988 | S |
D310359 | Inukai | Sep 1990 | S |
D316707 | Allegier | May 1991 | S |
D323894 | Rosati et al. | Feb 1992 | S |
D325729 | Forsythe et al. | Apr 1992 | S |
D327878 | Fukutake et al. | Jul 1992 | S |
5140141 | Inagaki et al. | Aug 1992 | A |
5179382 | Decker | Jan 1993 | A |
5198650 | Wike, Jr. | Mar 1993 | A |
D334896 | Shimizu et al. | Apr 1993 | S |
D344745 | Miyazawa | Mar 1994 | S |
D348260 | Allgeier | Jun 1994 | S |
5343529 | Goldfine et al. | Aug 1994 | A |
5396417 | Burks et al. | Mar 1995 | A |
D359059 | Omi | Jun 1995 | S |
D359483 | Saunders et al. | Jun 1995 | S |
D373354 | Maslow | Sep 1996 | S |
D373576 | Kanno et al. | Sep 1996 | S |
D378587 | Kanno et al. | Mar 1997 | S |
D378916 | Kanno et al. | Apr 1997 | S |
5619574 | Johnson et al. | Apr 1997 | A |
D381590 | Thoeni et al. | Jul 1997 | S |
D381651 | Banik et al. | Jul 1997 | S |
5665955 | Collins, Jr. et al. | Sep 1997 | A |
D386489 | Goldman et al. | Nov 1997 | S |
D387337 | Sween et al. | Dec 1997 | S |
D388075 | Bayer et al. | Dec 1997 | S |
5710886 | Christensen et al. | Jan 1998 | A |
5756981 | Soustaei et al. | May 1998 | A |
5784463 | Chen et al. | Jul 1998 | A |
5797002 | Patterson et al. | Aug 1998 | A |
5819226 | Gopinathan et al. | Oct 1998 | A |
D400553 | Kung | Nov 1998 | S |
5834751 | Jager et al. | Nov 1998 | A |
5885214 | Monroe et al. | Mar 1999 | A |
D408806 | Schmidt et al. | Apr 1999 | S |
5892900 | Ginter et al. | Apr 1999 | A |
5992747 | Katoh et al. | Nov 1999 | A |
D420657 | Keen et al. | Feb 2000 | S |
6078908 | Schmitz | Jun 2000 | A |
D430588 | Goldberg et al. | Sep 2000 | S |
6178409 | Weber et al. | Jan 2001 | B1 |
6216953 | Kumagai et al. | Apr 2001 | B1 |
6233064 | Griffin | May 2001 | B1 |
D445417 | Lee et al. | Jul 2001 | S |
D447137 | Hultzman | Aug 2001 | S |
D454879 | Lin et al. | Mar 2002 | S |
6357661 | Schonenberg et al. | Mar 2002 | B1 |
D464969 | Byun et al. | Oct 2002 | S |
D480397 | Forsythe et al. | Oct 2003 | S |
D483371 | Johnston | Dec 2003 | S |
D486827 | Detallante et al. | Feb 2004 | S |
6760843 | Carter | Jul 2004 | B1 |
D493794 | Berentzen et al. | Aug 2004 | S |
D495335 | Masamitsu et al. | Aug 2004 | S |
6799271 | Kugai | Sep 2004 | B2 |
6834270 | Pagani et al. | Dec 2004 | B1 |
6836485 | Bendak et al. | Dec 2004 | B1 |
D504429 | Muto | Apr 2005 | S |
D509508 | Ko et al. | Sep 2005 | S |
D512065 | Ko et al. | Nov 2005 | S |
D512698 | Augenbraun et al. | Dec 2005 | S |
D515574 | Colbum | Feb 2006 | S |
D520638 | Zeindler | May 2006 | S |
7048188 | Kumagai et al. | May 2006 | B2 |
7081979 | Cotter et al. | Jul 2006 | B2 |
7093757 | Boucher et al. | Aug 2006 | B2 |
D528444 | Horie et al. | Sep 2006 | S |
D542291 | Kang et al. | May 2007 | S |
7280981 | Huang et al. | Oct 2007 | B2 |
7287009 | Libermann | Oct 2007 | B1 |
7287692 | Patel et al. | Oct 2007 | B1 |
D556068 | Fugman et al. | Nov 2007 | S |
D558811 | Higgins et al. | Jan 2008 | S |
D562834 | Bashan et al. | Feb 2008 | S |
7328189 | Ling | Feb 2008 | B2 |
7330826 | Porat et al. | Feb 2008 | B1 |
RE40444 | Linehan | Jul 2008 | E |
7400932 | Ackley et al. | Jul 2008 | B2 |
D574738 | Khurana | Aug 2008 | S |
D574829 | Shirai et al. | Aug 2008 | S |
D578535 | Schmitz | Oct 2008 | S |
7437757 | Holdsworth | Oct 2008 | B2 |
7442167 | Dunki-Jacobs et al. | Oct 2008 | B2 |
7454356 | Fields et al. | Nov 2008 | B2 |
7496527 | Silverstein et al. | Feb 2009 | B2 |
7533044 | Scott | May 2009 | B2 |
7555460 | Barkan | Jun 2009 | B1 |
D596969 | Igelmund | Jul 2009 | S |
D597865 | Bernard et al. | Aug 2009 | S |
D598305 | Li et al. | Aug 2009 | S |
7596530 | Glasberg | Sep 2009 | B1 |
D602913 | Han et al. | Oct 2009 | S |
7606560 | Labrou et al. | Oct 2009 | B2 |
7627967 | Torvik | Dec 2009 | B1 |
7690614 | Mudd et al. | Apr 2010 | B1 |
D615887 | Alexander et al. | May 2010 | S |
7730321 | Gasparini et al. | Jun 2010 | B2 |
7734527 | Uzo | Jun 2010 | B2 |
7753265 | Harris | Jul 2010 | B2 |
7822666 | Bursch | Oct 2010 | B1 |
D628611 | Lewis | Dec 2010 | S |
7870077 | Woo et al. | Jan 2011 | B2 |
7917444 | Bursch | Mar 2011 | B1 |
7941369 | Juras et al. | May 2011 | B2 |
7946502 | Faith et al. | May 2011 | B2 |
7978363 | Takayama | Jul 2011 | B2 |
D646187 | Edgar | Oct 2011 | S |
8041603 | Suk | Oct 2011 | B2 |
8052057 | Smith et al. | Nov 2011 | B2 |
D651530 | Baumgartner et al. | Jan 2012 | S |
8131642 | De Ruiter et al. | Mar 2012 | B2 |
8157175 | Kotlarsky et al. | Apr 2012 | B2 |
8186592 | Fletecher | May 2012 | B2 |
D662534 | Chang | Jun 2012 | S |
8205797 | Tredoux et al. | Jun 2012 | B2 |
8255696 | Florencio et al. | Aug 2012 | B2 |
8290876 | Powell | Oct 2012 | B1 |
8300799 | Steul | Oct 2012 | B2 |
8301494 | Wills | Oct 2012 | B2 |
D671542 | Siekmann et al. | Nov 2012 | S |
D671934 | Alman et al. | Dec 2012 | S |
8335745 | Perlman et al. | Dec 2012 | B2 |
8346670 | Hasson et al. | Jan 2013 | B2 |
8359274 | Yoder et al. | Jan 2013 | B2 |
8364544 | McAlhaney | Jan 2013 | B2 |
8366005 | Koltarsky et al. | Feb 2013 | B2 |
8380177 | Laracey | Feb 2013 | B2 |
8381969 | Miller et al. | Feb 2013 | B1 |
8386349 | Dixon et al. | Feb 2013 | B2 |
8423466 | Lane | Apr 2013 | B2 |
D682905 | Kendall et al. | May 2013 | S |
8442894 | Blackhurst et al. | May 2013 | B2 |
8473354 | Psota et al. | Jun 2013 | B2 |
8479992 | Kotlarsky et al. | Jul 2013 | B2 |
D689478 | Wikel et al. | Sep 2013 | S |
8534559 | Drzymala et al. | Sep 2013 | B2 |
8538821 | Nguyen et al. | Sep 2013 | B2 |
8559923 | Drzyzga et al. | Oct 2013 | B2 |
8571996 | Johnson | Oct 2013 | B2 |
8577803 | Chatterjee et al. | Nov 2013 | B2 |
8584251 | McGuire et al. | Nov 2013 | B2 |
8589237 | Fischer et al. | Nov 2013 | B2 |
8595841 | Britton et al. | Nov 2013 | B2 |
8620754 | Fisher | Dec 2013 | B2 |
8620790 | Priebatsch | Dec 2013 | B2 |
8630620 | Cha et al. | Jan 2014 | B2 |
8630851 | Hertschuh et al. | Jan 2014 | B1 |
8635157 | Smith et al. | Jan 2014 | B2 |
8639619 | Priebatsch | Jan 2014 | B1 |
D701894 | Reznik et al. | Apr 2014 | S |
8694438 | Jernigan et al. | Apr 2014 | B1 |
D706145 | Pavlak et al. | Jun 2014 | S |
8770478 | Priebatsch | Jul 2014 | B2 |
D712756 | Rump et al. | Sep 2014 | S |
8838501 | Priebatsch | Sep 2014 | B1 |
8924260 | Priebatsch | Dec 2014 | B1 |
D721371 | Rivera et al. | Jan 2015 | S |
20010032884 | Ring et al. | Oct 2001 | A1 |
20020069155 | Nafeh et al. | Jun 2002 | A1 |
20020095303 | Asayama et al. | Jul 2002 | A1 |
20020120587 | D'Agostino | Aug 2002 | A1 |
20020131444 | Moodie et al. | Sep 2002 | A1 |
20020154342 | Haining | Oct 2002 | A1 |
20020193141 | Wu | Dec 2002 | A1 |
20030004901 | Dutta et al. | Jan 2003 | A1 |
20030059127 | Khovaylo et al. | Mar 2003 | A1 |
20030061170 | Uzo | Mar 2003 | A1 |
20030061171 | Gilbert et al. | Mar 2003 | A1 |
20030074317 | Hofi | Apr 2003 | A1 |
20030171993 | Chappuis | Sep 2003 | A1 |
20030181168 | Herrod et al. | Sep 2003 | A1 |
20030200184 | Dominguez et al. | Oct 2003 | A1 |
20040010463 | Hahn-Carlson et al. | Jan 2004 | A1 |
20040024707 | Perre et al. | Feb 2004 | A1 |
20040039651 | Grunzig et al. | Feb 2004 | A1 |
20040073688 | Sampson | Apr 2004 | A1 |
20040107170 | Labrou et al. | Jun 2004 | A1 |
20040133507 | Barbour | Jul 2004 | A1 |
20040230489 | Goldthwaite et al. | Nov 2004 | A1 |
20050091068 | Ramamoorthy et al. | Apr 2005 | A1 |
20050171900 | Onneken | Aug 2005 | A1 |
20050199727 | Schmidt et al. | Sep 2005 | A1 |
20060095369 | Hofi | May 2006 | A1 |
20060116892 | Grimes et al. | Jun 2006 | A1 |
20060131390 | Kim | Jun 2006 | A1 |
20060151609 | Schonenberg et al. | Jul 2006 | A1 |
20060165060 | Dua | Jul 2006 | A1 |
20060235796 | Johnson et al. | Oct 2006 | A1 |
20070130463 | Law et al. | Jun 2007 | A1 |
20070219905 | Gohmann et al. | Sep 2007 | A1 |
20070233615 | Tumminaro | Oct 2007 | A1 |
20070260544 | Wankmueller | Nov 2007 | A1 |
20070299736 | Perrochon et al. | Dec 2007 | A1 |
20080033880 | Fiebiger et al. | Feb 2008 | A1 |
20080210754 | Lovett | Sep 2008 | A1 |
20080212771 | Hauser | Sep 2008 | A1 |
20080262925 | Kim et al. | Oct 2008 | A1 |
20080281726 | Gupta | Nov 2008 | A1 |
20080281733 | Kubo et al. | Nov 2008 | A1 |
20080319905 | Carlson | Dec 2008 | A1 |
20090024452 | Martinez et al. | Jan 2009 | A1 |
20090198617 | Soghoian et al. | Aug 2009 | A1 |
20090254479 | Pharris | Oct 2009 | A1 |
20090281948 | Carlson | Nov 2009 | A1 |
20090300738 | Dewe et al. | Dec 2009 | A1 |
20100070364 | Dugan | Mar 2010 | A1 |
20100088236 | Karabulut et al. | Apr 2010 | A1 |
20100106569 | Grimes | Apr 2010 | A1 |
20100145861 | Law et al. | Jun 2010 | A1 |
20100218239 | Tang et al. | Aug 2010 | A1 |
20100250290 | Lefkowitz et al. | Sep 2010 | A1 |
20100257023 | Kendall et al. | Oct 2010 | A1 |
20100262546 | Sahota et al. | Oct 2010 | A1 |
20100312649 | Lurie | Dec 2010 | A1 |
20100318412 | Karypis et al. | Dec 2010 | A1 |
20100325053 | Hogg et al. | Dec 2010 | A1 |
20110054981 | Faith et al. | Mar 2011 | A1 |
20110078081 | Pizadeh et al. | Mar 2011 | A1 |
20110087595 | Sabella | Apr 2011 | A1 |
20110112957 | Ingram et al. | May 2011 | A1 |
20110112968 | Florek et al. | May 2011 | A1 |
20110155799 | Meszaros et al. | Jun 2011 | A1 |
20110161233 | Tieken | Jun 2011 | A1 |
20110191160 | Blackhurst et al. | Aug 2011 | A1 |
20110196796 | Florek et al. | Aug 2011 | A1 |
20110238476 | Carr et al. | Sep 2011 | A1 |
20110246284 | Chaikin et al. | Oct 2011 | A1 |
20110251892 | Laracey | Oct 2011 | A1 |
20110283042 | Jeon et al. | Nov 2011 | A1 |
20120000982 | Gao et al. | Jan 2012 | A1 |
20120011019 | Wakim | Jan 2012 | A1 |
20120016799 | Killian et al. | Jan 2012 | A1 |
20120018516 | Gao et al. | Jan 2012 | A1 |
20120028609 | Hruska | Feb 2012 | A1 |
20120078789 | Harrell | Mar 2012 | A1 |
20120089461 | Greenspan | Apr 2012 | A1 |
20120095855 | Sterling | Apr 2012 | A1 |
20120116861 | Dobyns | May 2012 | A1 |
20120123847 | Wane et al. | May 2012 | A1 |
20120136780 | El-Awady et al. | May 2012 | A1 |
20120150598 | Griggs | Jun 2012 | A1 |
20120150748 | Law et al. | Jun 2012 | A1 |
20120158455 | Pathak et al. | Jun 2012 | A1 |
20120159647 | Sanin et al. | Jun 2012 | A1 |
20120162401 | Melder et al. | Jun 2012 | A1 |
20120166264 | Shum et al. | Jun 2012 | A1 |
20120019556 | Forges et al. | Jul 2012 | A1 |
20120169857 | Sato | Jul 2012 | A1 |
20120179558 | Fischer | Jul 2012 | A1 |
20120187184 | Challa et al. | Jul 2012 | A1 |
20120197749 | Gray | Aug 2012 | A1 |
20120197801 | Jimenez | Aug 2012 | A1 |
20120203620 | Dobyns | Aug 2012 | A1 |
20120209360 | Ihm et al. | Aug 2012 | A1 |
20120226540 | Batalion et al. | Sep 2012 | A1 |
20120239577 | Wolfs et al. | Sep 2012 | A1 |
20120246015 | Bennett et al. | Sep 2012 | A1 |
20120253852 | Pourfallah et al. | Oct 2012 | A1 |
20120253903 | Tavares et al. | Oct 2012 | A1 |
20120284195 | McMillen et al. | Nov 2012 | A1 |
20120290376 | Dryer et al. | Nov 2012 | A1 |
20120290389 | Greenough et al. | Nov 2012 | A1 |
20120296828 | Bergdale et al. | Nov 2012 | A1 |
20120303425 | Katzin et al. | Nov 2012 | A1 |
20120310838 | Harris et al. | Dec 2012 | A1 |
20120316950 | LaPorte et al. | Dec 2012 | A1 |
20120317036 | Bower et al. | Dec 2012 | A1 |
20120323657 | Tiku et al. | Dec 2012 | A1 |
20120323663 | Leach | Dec 2012 | A1 |
20120330744 | Aissa | Dec 2012 | A1 |
20120330846 | Light et al. | Dec 2012 | A1 |
20130013433 | Rose et al. | Jan 2013 | A1 |
20130018715 | Zhou et al. | Jan 2013 | A1 |
20130024254 | Libenson et al. | Jan 2013 | A1 |
20130043305 | Zhou et al. | Feb 2013 | A1 |
20130046603 | Grigg et al. | Feb 2013 | A1 |
20130080231 | Fisher | Mar 2013 | A1 |
20130080239 | Okerlund | Mar 2013 | A1 |
20130103512 | Fisher | Apr 2013 | A1 |
20130103574 | Conrad et al. | Apr 2013 | A1 |
20130110658 | Lyman et al. | May 2013 | A1 |
20130126605 | Rooke et al. | May 2013 | A1 |
20130134213 | Pallakoff et al. | May 2013 | A1 |
20130138491 | Gao et al. | May 2013 | A1 |
20130144792 | Nisson et al. | Jun 2013 | A1 |
20130145173 | Shablygin et al. | Jun 2013 | A1 |
20130151402 | Howard | Jun 2013 | A1 |
20130158455 | Ruschmeyer et al. | Jun 2013 | A1 |
20130159170 | Gandhi et al. | Jun 2013 | A1 |
20130173475 | Lund | Jul 2013 | A1 |
20130191195 | Carlson et al. | Jul 2013 | A1 |
20130191213 | Beck et al. | Jul 2013 | A1 |
20130197991 | Basu et al. | Aug 2013 | A1 |
20130204690 | Liebmann | Aug 2013 | A1 |
20130204894 | Faith et al. | Aug 2013 | A1 |
20130212007 | Mattsson et al. | Aug 2013 | A1 |
20130218701 | Challa et al. | Aug 2013 | A1 |
20130218721 | Borhan et al. | Aug 2013 | A1 |
20130246203 | Laracey | Sep 2013 | A1 |
20130246266 | Coleman et al. | Sep 2013 | A1 |
20130254028 | Salci | Sep 2013 | A1 |
20130254052 | Royyuru et al. | Sep 2013 | A1 |
20130256403 | Mackinnon Keith | Oct 2013 | A1 |
20130262204 | Stiles et al. | Oct 2013 | A1 |
20130268381 | Randazza et al. | Oct 2013 | A1 |
20130275308 | Paraskeva et al. | Oct 2013 | A1 |
20130276023 | Kent et al. | Oct 2013 | A1 |
20130282581 | Singh | Oct 2013 | A1 |
20130282588 | Hruska | Oct 2013 | A1 |
20130311375 | Priebatsch | Nov 2013 | A1 |
20130325621 | Sanginiti et al. | Dec 2013 | A1 |
20130332251 | Loannidis et al. | Dec 2013 | A1 |
20130334308 | Priebatsch | Dec 2013 | A1 |
20140006289 | Puthenveetil | Jan 2014 | A1 |
20140019358 | Priebatsch | Jan 2014 | A1 |
20140039999 | Levene et al. | Feb 2014 | A1 |
20140074571 | Hope et al. | Mar 2014 | A1 |
20140074719 | Gressel et al. | Mar 2014 | A1 |
20140263608 | Rivera et al. | Sep 2014 | A1 |
20140279554 | Priebatsch | Sep 2014 | A1 |
20140279556 | Priebatsch | Sep 2014 | A1 |
20140351012 | Jemigan et al. | Nov 2014 | A1 |
20140351030 | Priebatsch | Nov 2014 | A1 |
20140351126 | Priebatsch | Nov 2014 | A1 |
20150014413 | Priebatsch | Jan 2015 | A1 |
20150019428 | Priebatsch | Jan 2015 | A1 |
Number | Date | Country |
---|---|---|
101593197 | Dec 2009 | CN |
102254264 | Nov 2011 | CN |
202221590 | May 2012 | CN |
1467300 | Oct 2004 | EP |
1710980 | Oct 2006 | EP |
2224781 | Sep 2010 | EP |
2507762 | Oct 2012 | EP |
2605202 | Jun 2013 | EP |
2003-187281 | Jul 2003 | JP |
10-2010-0097951 | Sep 2010 | KR |
194379 | Nov 2013 | SG |
WO2001077856 | Oct 2001 | WO |
WO2003084175 | Oct 2003 | WO |
WO2004053640 | Jun 2004 | WO |
WO2005017795 | Feb 2005 | WO |
WO2005086593 | Sep 2005 | WO |
WO2006039353 | Apr 2006 | WO |
WO2008069969 | Jun 2008 | WO |
WO2008148118 | Dec 2008 | WO |
WO2009012731 | Jan 2009 | WO |
WO2009131549 | Oct 2009 | WO |
WO2009151832 | Dec 2009 | WO |
WO2010064128 | Jun 2010 | WO |
WO2010133755 | Nov 2010 | WO |
WO2010141239 | Dec 2010 | WO |
WO2011028486 | Mar 2011 | WO |
WO2011056609 | May 2011 | WO |
WO2011097250 | Aug 2011 | WO |
WO201114301 | Nov 2011 | WO |
WO2011146054 | Nov 2011 | WO |
WO2012064964 | May 2012 | WO |
WO2012065128 | May 2012 | WO |
WO2012078407 | Jun 2012 | WO |
WO2012097171 | Jul 2012 | WO |
WO2012119052 | Sep 2012 | WO |
WO2012125940 | Sep 2012 | WO |
WO2012151590 | Nov 2012 | WO |
WO2012154189 | Nov 2012 | WO |
WO2012158133 | Nov 2012 | WO |
WO2013006725 | Jan 2013 | WO |
WO2013012953 | Jan 2013 | WO |
WO2013051031 | Apr 2013 | WO |
WO2013068719 | May 2013 | WO |
WO2013071310 | May 2013 | WO |
WO2013106679 | Jul 2013 | WO |
WO2013115853 | Aug 2013 | WO |
WO2013117738 | Aug 2013 | WO |
WO2013119914 | Aug 2013 | WO |
WO2013126815 | Aug 2013 | WO |
WO2013126894 | Aug 2013 | WO |
WO2013126996 | Sep 2013 | WO |
WO2013127579 | Sep 2013 | WO |
WO2013138195 | Sep 2013 | WO |
WO2013140196 | Sep 2013 | WO |
WO2013142209 | Sep 2013 | WO |
WO2013144929 | Oct 2013 | WO |
WO2013144930 | Oct 2013 | WO |
WO2013149578 | Oct 2013 | WO |
WO2013151797 | Oct 2013 | WO |
WO2013152247 | Oct 2013 | WO |
WO2013163217 | Oct 2013 | WO |
WO2013170228 | Nov 2013 | WO |
Entry |
---|
Priebatsch, U.S. Appl No. 14/103,101, filed Dec. 11, 2013, Office Action, dated Aug. 25, 2016. |
Priebatsch, U.S. Appl No. 14/103,101, filed Dec. 11, 2013, Final Office Action, dated Jun. 5, 2017. |
Priebatsch, U.S. Appl No. 14/103,101, filed Dec. 11, 2013, Office Action, dated Sep. 19, 2019. |
Priebatsch, U.S. Appl No. 14/103,101, filed Dec. 11, 2013, Final Office Action, dated Feb. 6, 2020. |
Bichsel et al., “Data-Minimizing Authentication Goes Mobile”, Lecture Notes in Computer Science, vol. 7394, dated 2012, pp. 55-71. |
Number | Date | Country | |
---|---|---|---|
20210012315 A1 | Jan 2021 | US |
Number | Date | Country | |
---|---|---|---|
61671381 | Jul 2012 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 14103101 | Dec 2013 | US |
Child | 16986110 | US | |
Parent | 13718466 | Dec 2012 | US |
Child | 14103101 | US |