WO2022266283A1 - Systems and methods for contactless card communication and multi-device key pair cryptographic authentication - Google Patents

Systems and methods for contactless card communication and multi-device key pair cryptographic authentication Download PDF

Info

Publication number
WO2022266283A1
WO2022266283A1 PCT/US2022/033724 US2022033724W WO2022266283A1 WO 2022266283 A1 WO2022266283 A1 WO 2022266283A1 US 2022033724 W US2022033724 W US 2022033724W WO 2022266283 A1 WO2022266283 A1 WO 2022266283A1
Authority
WO
WIPO (PCT)
Prior art keywords
fido
key
authenticator
processor
instruction
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/US2022/033724
Other languages
English (en)
French (fr)
Inventor
Jeffrey Rule
Kevin Osborn
Wayne Lutz
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.)
Capital One Services LLC
Original Assignee
Capital One Services LLC
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 Capital One Services LLC filed Critical Capital One Services LLC
Priority to CN202280055032.4A priority Critical patent/CN117795505A/zh
Priority to EP22744348.8A priority patent/EP4356269A1/en
Priority to KR1020237044743A priority patent/KR20240024112A/ko
Priority to JP2023577529A priority patent/JP2024527492A/ja
Priority to CA3222325A priority patent/CA3222325A1/en
Priority to AU2022292656A priority patent/AU2022292656A1/en
Publication of WO2022266283A1 publication Critical patent/WO2022266283A1/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
    • G06F21/31—User authentication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
    • H04L9/0816—Key establishment, i.e. cryptographic processes or cryptographic protocols whereby a shared secret becomes available to two or more parties, for subsequent use
    • H04L9/0819—Key transport or distribution, i.e. key establishment techniques where one party creates or otherwise obtains a secret value, and securely transfers it to the other(s)
    • H04L9/0825—Key transport or distribution, i.e. key establishment techniques where one party creates or otherwise obtains a secret value, and securely transfers it to the other(s) using asymmetric-key encryption or public key infrastructure [PKI], e.g. key signature or public key certificates
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/14—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols using a plurality of keys or algorithms
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H04L9/3226—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using a predetermined code, e.g. password, passphrase or PIN
    • H04L9/3231—Biological data, e.g. fingerprint, voice or retina
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H04L9/3234—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving additional secure or trusted devices, e.g. TPM, smartcard, USB or software token
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H04L9/3247—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving digital signatures
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H04L9/3271—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using challenge-response
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/2103—Challenge-response

Definitions

  • the present disclosure relates to systems and methods for contactless card communication and, more specifically, for key pair cryptographic authentication of contactless cards using multiple devices.
  • Card-based operations often involve the use of a card in communication with a server or other device. It is necessary to protect such communications from interception and unauthorized access. However, there are numerous sophisticated methods for data interception that may be employed by hackers or other fraudulent actors.
  • transmission of data without encryption or other protection is susceptible to man-in-the-middle attacks, phishing attacks, replay attacks, and other attacks, and may be subject to other vulnerabilities, resulting in increased security risks and increased risks of account or card misuse. These risks may be further increased through the use of contactless cards, which communicate with other devices wirelessly, thus exposing data to potential interception during transmission.
  • Measures taken to address security risk may consume system resources and hinder operational efficiency. For large numbers of operations, the consumption of system resources and the hindrance of operation efficiency can increase, which may result in a failure to perform operations or unsatisfactory performance.
  • Embodiments of the present disclosure provide an authenticator.
  • the authenticator may include a processor and a memory.
  • the processor may be configured to receive one or more challenges.
  • the processor may be configured to generate a first instruction, the first instruction including a request to retrieve a first Fast Identity Online (FIDO) key.
  • the processor may be configured to transmit the first instruction.
  • the processor may be configured to receive the first FIDO key.
  • the processor may be configured to sign the one or more challenges using the first FIDO key.
  • the processor may be configured to transmit one or more signed challenges for validation using a second FIDO key.
  • FIDO Fast Identity Online
  • Embodiments of the present disclosure provide a method of authentication.
  • the method may include receiving, at a processor, one or more challenges.
  • the method may include generating, by the processor, a first instruction including a request to retrieve a first Fast Identity Online (FIDO) key.
  • the method may include transmitting, by the processor, the first instruction.
  • the method may include receiving the first FIDO key.
  • the method may include signing, by the processor, the one or more challenges using the first FIDO key.
  • the method may include transmitting, by the processor, one or more signed challenges for validation using a second FIDO key.
  • FIDO Fast Identity Online
  • Embodiments of the present disclosure provide a computer readable non-transitory medium comprising computer executable instructions that, when executed on a processor, perform procedures comprising the steps of: receiving one or more challenges; generating a first instruction including a request to retrieve a first Fast Identity Online (FIDO) key; transmitting the first instruction; receiving the first FIDO key; signing the one or more challenges using the first FIDO key; and transmitting one or more signed challenges for validation using a second FIDO key.
  • FIDO Fast Identity Online
  • Figure 1 depicts an authentication system according to an exemplary embodiment.
  • Figure 2A is an illustration of a first device according to an exemplary embodiment.
  • Figure 2B is an illustration of a contact pad of a first device according to an exemplary embodiment.
  • Figure 3 depicts an authentication method according to an exemplary embodiment.
  • Figure 4 depicts a sequence diagram of an authentication process according to an exemplary embodiment.
  • Figure 5 depicts an authentication method according to an exemplary embodiment.
  • Figure 6 depicts an authentication method according to an exemplary embodiment.
  • the systems and methods disclosed herein may be used to supplement authentication frameworks, including without limitation, Fast Identity Online (FIDO) authentication, Fast Identity Online 2 (FID02) authentication, WebAuthn, Client to Authenticator Protocol (CTAP) FIDO, other authentication implementations.
  • Systems and methods employed herein may be implemented with distributed storage, cloud-based storage, and other forms of storage in support of this functionality.
  • the systems and methods disclosed herein allow a device to serve as a roaming authenticator in a Fast Identity Online 2 (FID02) authentication in a browser.
  • a user may authenticate with a website in a passwordless environment using the implemented systems and methods. To log into the website, a private key may be stored on the device during the website registration process.
  • the device may enter a communication field, such as that of a mobile device, via one or more gestures including but not limited to a tap, a swipe, a wave, or the like.
  • the private key may then be transmitted from the first device to an application comprising instructions for execution on the mobile device, including but not limited to an authenticator.
  • the authenticator may be configured to sign the challenge issued by the website using the private key. Once the challenge has been signed, it may be transmitted to a relying party server and validated using the public key stored. In this manner, this authentication may serve as primary authentication to log in the user. Furthermore, this authentication may be used in conjunction with a secondary factor authentication, such as biometrics or credential, entered on the mobile device.
  • Benefits of the systems and methods disclosed herein include improved authentication by protecting communications from interception and unauthorized access and securely and quickly identifying the originator and determining their authenticity.
  • the systems and methods disclosed herein allow for the avoidance of man-in-the-middle attacks and phishing attacks, prevention of replay attacks, improved accessibility and security of authenticator devices and secure encryption and data transmission, and the reduction of other security vulnerabilities by using, without limitation iOS® and Android® executing on devices, as an authenticator in a FID02 authentication in a browser, such as a laptop browser or tablet browser or desktop browser while implementing conditional multi-factor authentication.
  • FID02 framework and other authentication frameworks are establishing the identity of the user seeking to undertake the authentication process.
  • Systems and methods described herein may reduce this vulnerability by confirming the user attempting to register credentials and authenticate via the framework is the user he or she claims to be and is authorized to perform the authentication process. By doing so, framework security and the ability to exclude unauthorized users may be increased. Accordingly, security risks may be further mitigated and compatibility across various devices and transaction efficiency may be further improved.
  • computation processing of the authenticator is reduced when instructing the first device to retrieve or generate one or more FIDO keys instead of generating the one or more FIDO keys in the authenticator.
  • the systems and methods disclosed herein reduce the risk of fraudulent activity, such as misuse of the card or an account associated with the card, while also improving secure access to authenticator devices and encrypted data transmissions.
  • Systems and methods disclosed herein improve upon implementations that lack secure authentication. These benefits may be advantageously achieved while promoting system efficiency, avoiding degradation of the user experience, and promoting compatibility across numerous devices.
  • Figure 1 illustrates an authentication system 100.
  • the system 100 may comprise a browser extension 101, first device 105, an authenticator 110 or a second device, a network 115, a relying party or server 120, and a database 125.
  • Figure 1 illustrates single instances of components of system 100, system 100 may include any number of components.
  • System 100 may include a browser extension 101.
  • the browser extension 101 may comprise Chrome ®, Internet Explorer ®, Firefox ®, or Safari ®. It is understood that software applications other than a browser extension may be utilized, including stand-alone software applications. Without limitation, an authentication request, such as a website registration may take place on any device, including but not limited to a laptop or a desktop associated with the browser extension 101.
  • a mobile-based browser extension 101, or a tablet-based browser extension 101, or a laptop-based browser extension 101, or a desktop-based browser extension 101 may be configured to transmit and receive one or more requests, as further explained below.
  • System 100 may include a first device 105.
  • the first device 105 may comprise a contactless card, a contact-based card, a network-enabled computer, or other device described herein.
  • a network-enabled computer may include, but is not limited to a computer device, or communications device including, e.g., a server, a network appliance, a personal computer, a workstation, a phone, a handheld PC, a personal digital assistant, a contactless card, a thin client, a fat client, an Internet browser, a kiosk, a tablet, a terminal, or other device.
  • a server e.g., a server, a network appliance, a personal computer, a workstation, a phone, a handheld PC, a personal digital assistant, a contactless card, a thin client, a fat client, an Internet browser, a kiosk, a tablet, a terminal, or other device.
  • first device 105 may include one or more processors 102, and memory 104.
  • Memory 104 may include one or more applets 106 and one or more counters 108. Each counter 108 may include a counter value.
  • Memory 104 may include the counter value, transmission data, and at least one key.
  • First device 105 may include a communication interface 107.
  • the communication interface 107 may comprise communication capabilities with physical interfaces and contactless interfaces.
  • the communication interface 107 may be configured to communicate with a physical interface, such as by swiping through a card swipe interface or inserting into a card chip reader found on an automated teller machine (ATM) or other device configured to communicate over a physical interface.
  • the communication interface 107 may be configured to establish contactless communication with a card reading device via a short-range wireless communication method, such as NFC, Bluetooth, Wi-Fi, RFID, and other forms of contactless communication.
  • the communication interface 107 may be configured to communicate directly with the authenticator 110 or second device, relying party or server 120, and/or database 125 via network 115.
  • First device 105 may be in data communication with any number of components of system 100. For example, first device 105 may transmit data via network 115 to the authenticator 110 or second device, and/or relying party or server 120. First device 105 may transmit data via network 115 to database 125. In some examples, first device 105 may be configured to transmit data via network 115 after entry into one or more communication fields of any device. Without limitation, each entry may be associated with a tap, a swipe, a wave, and/or any combination thereof.
  • System 100 may include an authenticator 110.
  • the authenticator 110 may comprise a roaming authenticator to another client device.
  • the authenticator 110 may include a mobile device that serves as a roaming authenticator to a laptop, a desktop, or a tablet. It is understood that the client devices are not limited to such devices, and that other client devices are within the scope of the invention.
  • the authenticator 110 may comprise a second device.
  • the authenticator 110 may include one or more processors 112, and memory 114.
  • Memory 114 may include one or more applications, including but not limited to application 116.
  • the authenticator 110 may be in data communication with any number of components of system 100.
  • the authenticator 110 may transmit data via network 115 to server 120.
  • the authenticator 110 may transmit data via network 115 to database 125.
  • the authenticator 110 may be a network-enabled computer.
  • a network-enabled computer may include, but is not limited to a computer device, or communications device including, e.g., a server, a network appliance, a personal computer, a workstation, a phone, a handheld PC, a personal digital assistant, a contactless card, a thin client, a fat client, an Internet browser, a kiosk, a tablet, a terminal, or other device.
  • the authenticator 110 also may be a mobile device; for example, a mobile device may include an iPhone, iPod, iPad from Apple® or any other mobile device running Apple’s iOS® operating system, any device running Microsoft’s Windows® Mobile operating system, any device running Google’s Android® operating system, and/or any other smartphone, tablet, or like wearable mobile device.
  • the authenticator 110 may include processing circuitry and may contain additional components, including processors, memories, error and parity/CRC checkers, data encoders, anticollision algorithms, controllers, command decoders, security primitives and tamperproofmg hardware, as necessary to perform the functions described herein.
  • the authenticator 110 may further include a display and input devices.
  • the display may be any type of device for presenting visual information such as a computer monitor, a flat panel display, and a mobile device screen, including liquid crystal displays, light-emitting diode displays, plasma panels, and cathode ray tube displays.
  • the input devices may include any device for entering information into the user’s device that is available and supported by the user’s device, such as a touch-screen, keyboard, mouse, cursor-control device, touch-screen, microphone, digital camera, video recorder or camcorder. These devices may be used to enter information and interact with the software and other devices described herein.
  • System 100 may include a network 115.
  • network 115 may be one or more of a wireless network, a wired network or any combination of wireless network and wired network, and may be configured to connect to any one of components of system 100.
  • first device 105 may be configured to connect to the relying party or server 120 via network 115.
  • network 115 may include one or more of a fiber optics network, a passive optical network, a cable network, an Internet network, a satellite network, a wireless local area network (LAN), a Global System for Mobile Communication, a Personal Communication Service, a Personal Area Network, Wireless Application Protocol, Multimedia Messaging Service, Enhanced Messaging Service, Short Message Service, Time Division Multiplexing based systems, Code Division Multiple Access based systems, D-AMPS, Wi-Fi, Fixed Wireless Data, IEEE 802.1 lb, 802.15.1, 802.1 In and 802.1 lg, Bluetooth, NFC, Radio Frequency Identification (RFID), Wi-Fi, and/or the like.
  • LAN wireless local area network
  • LAN Global System for Mobile Communication
  • a Personal Communication Service a Personal Area Network
  • Wireless Application Protocol Multimedia Messaging Service
  • Enhanced Messaging Service Enhanced Messaging Service
  • Short Message Service Time Division Multiplexing based systems
  • Code Division Multiple Access based systems Code Division Multiple Access based systems
  • D-AMPS Wi-Fi
  • network 115 may include, without limitation, telephone lines, fiber optics, IEEE Ethernet 902.3, a wide area network, a wireless personal area network, a LAN, or a global network such as the Internet.
  • network 115 may support an Internet network, a wireless communication network, a cellular network, or the like, or any combination thereof.
  • Network 115 may further include one network, or any number of the exemplary types of networks mentioned above, operating as a stand-alone network or in cooperation with each other.
  • Network 115 may utilize one or more protocols of one or more network elements to which they are communicatively coupled.
  • Network 115 may translate to or from other protocols to one or more protocols of network devices.
  • System 100 may include a server 120.
  • the server 120 may comprise a relying party.
  • the server 120 may include one or more processors 122 coupled to memory 124.
  • the server 120 may comprise a cloud- based authenticator.
  • the server 120 may be configured as a central system, server or platform to control and call various data at different times to execute a plurality of workflow actions.
  • the server 120 may be configured to connect to the first device 105.
  • the server 120 may be in data communication with the applet 106 and/or application 116.
  • a server 120 may be in data communication with applet 106 via one or more networks 115.
  • the first device 105 may be in communication with one or more servers 120 via one or more networks 115, and may operate as a respective front-end to back-end pair with server 120.
  • the first device 105 may transmit, for example from applet 106 executing thereon, one or more requests to the server 120.
  • the one or more requests may be associated with retrieving data from the server 120.
  • the server 120 may receive the one or more requests from the first device 105. Based on the one or more requests from applet 106, the server 120 may be configured to retrieve the requested data.
  • the server 120 may be configured to transmit the received data to applet 106, the received data being responsive to one or more requests.
  • the server 120 can be a dedicated server computer, such as bladed servers, or can be personal computers, laptop computers, notebook computers, palm top computers, network computers, mobile devices, wearable devices, or any processor-controlled device capable of supporting the system 100. While FIG. 1 illustrates a single relying party or server 120, it is understood that other embodiments can use multiple servers or multiple computer systems as necessary or desired to support the users and can also use back-up or redundant servers to prevent network downtime in the event of a failure of a particular server.
  • the server 120 may include an application comprising instructions for execution thereon.
  • the application may comprise instructions for execution on the server 120.
  • the application of the server 120 may be in communication with any components of system 100.
  • server 120 may execute one or more applications that enable, for example, network and/or data communications with one or more components of system 100 and transmit and/or receive data.
  • the server 120 may be a network-enabled computer.
  • a network-enabled computer may include, but is not limited to a computer device, or communications device including, e.g., a server, a network appliance, a personal computer, a workstation, a phone, a handheld PC, a personal digital assistant, a contactless card, a thin client, a fat client, an Internet browser, or other device.
  • the server 120 also may be a mobile device; for example, a mobile device may include an iPhone, iPod, iPad from Apple® or any other mobile device running Apple’s iOS® operating system, any device running Microsoft’s Windows® Mobile operating system, any device running Google’s Android® operating system, and/or any other smartphone, tablet, or like wearable mobile device.
  • the server 120 may include processing circuitry and may contain additional components, including processors, memories, error and parity/CRC checkers, data encoders, anticollision algorithms, controllers, command decoders, security primitives and tamperproofmg hardware, as necessary to perform the functions described herein.
  • the server 120 may further include a display and input devices.
  • the display may be any type of device for presenting visual information such as a computer monitor, a flat panel display, and a mobile device screen, including liquid crystal displays, light-emitting diode displays, plasma panels, and cathode ray tube displays.
  • the input devices may include any device for entering information into the user’s device that is available and supported by the user’s device, such as a touch-screen, keyboard, mouse, cursor- control device, touch-screen, microphone, digital camera, video recorder or camcorder. These devices may be used to enter information and interact with the software and other devices described herein.
  • System 100 may include one or more databases 125.
  • the database 125 may comprise a relational database, a non-relational database, or other database implementations, and any combination thereof, including a plurality of relational databases and non-relational databases.
  • the database 125 may comprise a desktop database, a mobile database, or an in memory database.
  • the database 125 may be hosted internally by any component of system 100, such as the first device 105 or server 120, or the database 125 may be hosted externally to any component of the system 100, such as the first device 105 or server 120, by a cloud-based platform, or in any storage device that is in data communication with the first device 105 and server 120.
  • database 125 may be in data communication with any number of components of system 100.
  • server 120 may be configured to retrieve the requested data from the database 125 that is transmitted by applet 106.
  • Server 120 may be configured to transmit the received data from database 125 to applet 106 via network 115, the received data being responsive to the transmitted one or more requests.
  • applet 106 may be configured to transmit one or more requests for the requested data from database 125 via network [00039]
  • exemplary procedures in accordance with the present disclosure described herein can be performed by a processing arrangement and/or a computing arrangement (e.g., computer hardware arrangement).
  • Such processing/computing arrangement can be, for example entirely or a part of, or include, but not limited to, a computer/processor that can include, for example one or more microprocessors, and use instructions stored on a computer-accessible medium (e.g., RAM, ROM, hard drive, or other storage device).
  • a computer-accessible medium e.g., RAM, ROM, hard drive, or other storage device.
  • a computer- accessible medium can be part of the memory of the first device 105, authenticator 110, server 120, and/or database 125, or other computer hardware arrangement.
  • a computer-accessible medium e.g., as described herein above, a storage device such as a hard disk, floppy disk, memory stick, CD-ROM, RAM, ROM, etc., or a collection thereof
  • the computer-accessible medium can contain executable instructions thereon.
  • a storage arrangement can be provided separately from the computer-accessible medium, which can provide the instructions to the processing arrangement so as to configure the processing arrangement to execute certain exemplary procedures, processes, and methods, as described herein.
  • the processor 122 of server 120 may be configured to receive an authentication request.
  • the authentication request may be received from browser extension 101.
  • the authentication request may comprise a request for Fast Identity Online 2 (FID02) website registration.
  • the processor 122 may be configured to generate one or more challenges.
  • the processor 122 may be configured to generate a first challenge.
  • the processor 122 may be configured to challenge the authenticator 110 to login.
  • the first challenge may include an identifier, such as a user identifier or a site identifier, that may be used to select an appropriate FIDO key pair.
  • the first challenge may further include an unpredictable number, which may be given by the server 120, that is used to prevent replay. For example, for each instance of authentication, a new unpredictable number will be needed and thus the unpredictable number will be different each time. In this manner, this avoids utilizing a signature of the old unpredictable number and instead utilizes the number for the instant session of authentication.
  • the authenticator 110 such as processor 112 of a mobile device, may be configured to prompt one or more entries of the first device 105.
  • the one or more entries may include at least one selected from the group of a tap, a swipe, a wave, or the like, and/or any combination thereof.
  • the communication interface 107 of the first device 105 may enter a communication field of the authenticator 110, such as the communication field of the mobile device.
  • the first device 105 may be configured to, depending on the first instruction received from the authenticator 110, generate or retrieve a FIDO key pair associated with a specific user or site. The generated or retrieved FIDO key pair may be read by the authenticator 110.
  • the FIDO key pair may include a FIDO private key which may be read by the authenticator 110 from the first device 105 and may be used by the authenticator 110 to sign the first challenge resulting in a signed challenge data.
  • the FIDO private key may be retrieved via entry of a communication interface 107 of the first device 105 into a communication field.
  • the FIDO private key may be encrypted by the first device 105 prior to its transfer to the authenticator 110, in which case the processor 112 of the mobile device may be configured to decrypt the received encrypted FIDO private key.
  • the server 120 may receive the signed challenge data from the authenticator 110, such as the processor 112 of the mobile device.
  • the server 120 may perform validation of the signed challenge data. For example, the server 120 may validate the signed challenge data with the FIDO public key that was stored when the user registered to the site. The validation may comprise the result of the authentication process, which includes signature verification.
  • transmission of the FIDO private key from the first device 105 to the authenticator 110 may be prevented.
  • OTA over the air
  • transmission of the FIDO private key is avoided when the first device 105 performs the signing of the first challenge.
  • the first challenge and the site or user identifier information is transmitted to the first device 105 from the authenticator, which thereby distributes its computation to the first device 105 through near field communication (NFC) via a proxy protocol.
  • NFC near field communication
  • the FIDO private key may be generated based on a master key and an identifier associated with the authentication request using one or more cryptographic algorithms.
  • the identifier may include a site identifier and combined with the master key to produce another key pair.
  • the first device 105 may be configured to store a finite number of keys in memory 104 so as to avoid having to regenerate keys.
  • the first instruction from the authenticator 110 may include a request to regenerate the FIDO private key, such as a private key which is part of a public/private key pair, by the first device 105.
  • the master key be stored in memory 104 on the first device 105, and the master key may be combined with the site identifier on the first device 105 to generate the FIDO private key.
  • the master key may be transferred from the first device 105 to the authenticator 110, in which the combining of the master key and the site identifier is performed by the authenticator 110 to generate the FIDO private key.
  • the FIDO private key may be generated or stored in a secure element belonging to the authenticator 110.
  • the FIDO private key may be stored in a secure element maintained by an authenticator 110.
  • the secure element may comprise a tamper- resistant secure storage area in which one or more keys may be securely stored and retrieved by the server 120.
  • the authenticator 110 may be configured to transmit the first instruction to the first device 105.
  • the authenticator 110 may be configured to receive, based on the first instruction, the FIDO private key from the first device 105.
  • the first instruction may be transmitted to the processor 102 of the first device 105 by the authenticator 110.
  • the processor 102 of the first device 105 may be configured to generate the FIDO private key.
  • the processor 102 of the first device 105 may be configured to transmit the FIDO private key.
  • the processor 102 of the first device 105 may be configured to transmit the FIDO private key to the authenticator 110, such as an application 116 comprising instructions for execution on the authenticator 110.
  • the authenticator 110 may be, without limitation, a mobile device such as a laptop or a tablet or a phone.
  • the FIDO private key may be transmitted and received via one or more channels.
  • the FIDO private key may be transmitted and received via an out-of-band channel.
  • the processor 102 of the first device 105 may be configured to transmit the FIDO private key to the authenticator 110 via entry of the communication interface 107 into a communication field of the authenticator 110.
  • the entry may be associated with one or more gestures, including but not limited to one or more taps, swipes, waves, and/or any combination thereof.
  • the authenticator 110 may be configured to transmit the first FIDO key to the processor 122 of the server 120 for validation, and thus the authenticator 110 may be configured to serve as an intermediary device between the first device 105 and the processor 122 of the server 120.
  • the processor 122 may be configured to validate the signed challenge data transmitted from the authenticator 110 using a second FIDO key, such as a FIDO public key, which may be part of the public/private key pair as previously explained.
  • a second FIDO key such as a FIDO public key
  • the application 116 comprising instructions for execution on the authenticator 110 may be configured to sign the first challenge issued by the website using the FIDO private key.
  • the processor 122 may be transmitted to the processor 122 for validation using the FIDO public key stored in memory 124 of the server 120.
  • the processor 122 may be configured to generate a second instruction.
  • the second instruction may include a second request to transmit input data.
  • the processor 122 may be configured to transmit the second instruction.
  • the processor 122 may be configured to transmit the second instruction to the authenticator 110.
  • the second instruction may be forwarded by the processor 122 to the application 116 via one or more push notifications.
  • the second instruction may be transmitted by the processor 122 after evaluation by processor 122 and/or database 125 of one or more conditions. For example, at least one of the one or more conditions may include determining a threshold number of authentication requests over a predetermined time period.
  • the processor 122 and/or database 125 may be configured to determine whether an abnormal number of transactions or requests were performed within any number of seconds, minutes, hours, days, weeks, months, years, etc.
  • at least one of the one or more conditions may include determining whether misuse or fraud associated with an account and/or user occurred.
  • the processor 122 and/or database 125 may be configured to determine whether a user transaction history is indicative of excessive amount of purchases or abnormal locations. In this manner, conditional multifactor authentication may be implemented to improve security, which may trigger transmittal of the second instruction for receiving the input data.
  • the processor 122 may be configured to receive, based on the second instruction, the input data.
  • the processor 122 may be configured to receive the input data from the authenticator 110, such as from application 116 comprising instructions for execution on the second device.
  • the input data may include at least one selected from the group of biometric data and credential data.
  • the input data may include biometric data, credential data, and/or any combination thereof.
  • the biometric data may include at least one selected from the group of a fingerprint, a facial scan, a retinal scan, a voice recognition, and/or any combination thereof.
  • the input data may additionally and/or alternatively include credential data.
  • the login data may include at least one selected from the group of an entry of a user name, a password, an account number, a security code, a one-time passcode, an answer to a security question, and/or any combination thereof.
  • the processor 122 may be configured to complete the authentication request by authenticating the input data.
  • the processor 122 may be configured to generate one or more outcomes by comparing the received input data with reference input data.
  • the reference input data may be stored in memory 124 of the server 120.
  • the reference input data may be requested by the processor 122.
  • the processor 122 may be configured to receive, via one or more requests, reference input data, or alternatively transmit the input data for comparison with the reference input data to a database 125.
  • the processor 122 of the server 120 may be configured to generate an outcome indicative of successful authentication when it results in a successful match based on the comparison between the received input data with reference input data.
  • the processor 122 of the server 120 may be configured to generate an outcome of unsuccessful authentication when it results in an unsuccessful match based on the comparison between the received input data with reference input data. Upon determination of an unsuccessful authentication, the processor 122 of the server 120 may be configured to re-authenticate the input data up to and including a predetermined number of attempts before successfully authenticating the input data so as to complete the authentication request, or aborting the completion of the authentication request. In this manner, system 100 may implement with distributed storage, cloud- based storage, and other forms of storage in support of the aforementioned functionalities.
  • FIG. 2A illustrates one or more first devices 200.
  • First device 200 may reference the same or similar components of first device 105, as explained above with respect to FIG. 1.
  • Figure 2A and 2B illustrate single instances of components of first device 200, any number of components may be utilized.
  • First device 200 may be configured to communicate with one or more components of system 100.
  • First device 200 may comprise a contact-based card (e.g., a card read by a swipe of a magnetic stripe or by insertion into a chip reader) or a contactless card
  • the first device 200 may comprise a payment card, such as a credit card, debit card, or gift card, issued by a service provider 205 displayed on the front or back of the first device 200.
  • the first device 200 is not related to a payment card, and may comprise, without limitation, an identification card, a membership card, and a transportation card.
  • the payment card may comprise a dual interface contactless payment card.
  • First device 200 may comprise a substrate 210, which may include a single layer or one or more laminated layers composed of plastics, metals, and other materials.
  • Exemplary substrate materials include polyvinyl chloride, polyvinyl chloride acetate, acrylonitrile butadiene styrene, polycarbonate, polyesters, anodized titanium, palladium, gold, carbon, paper, and biodegradable materials.
  • the first device 200 may have physical characteristics compliant with the ID-1 format of the ISO/IEC 7810 standard, and the first device 200 may otherwise be compliant with the ISO/IEC 14443 standard. However, it is understood that the first device 200 according to the present disclosure may have different characteristics, and the present disclosure does not require implementation in a payment card.
  • the first device 200 may also include identification information 215 displayed on the front and/or back of the card, and a contact pad 220.
  • the contact pad 220 may be configured to establish contact with another communication device, including but not limited to a user device, smartphone, laptop, desktop, or tablet computer.
  • the first device 200 may also include processing circuitry, antenna and other components not shown in FIG. 2A. These components may be located behind the contact pad 220 or elsewhere on the substrate 210.
  • the first device 200 may also include a magnetic strip or tape, which may be located on the back of the card (not shown in FIG. 2A).
  • FIG. 2B the contact pad 220 of FIG.
  • processing circuitry 225 for storing and processing information, including a processor 230, such as a microprocessor, and a memory 235. It is understood that the processing circuitry 225 may contain additional components, including processors, memories, error and parity/CRC checkers, data encoders, anticollision algorithms, controllers, command decoders, security primitives and tamperproofmg hardware, as necessary to perform the functions described herein.
  • the memory 235 may be a read-only memory, write-once read-multiple memory or read/write memory, e.g., RAM, ROM, and EEPROM, and the first device 200 may include one or more of these memories.
  • a read-only memory may be factory programmable as read-only or one time programmable. One-time programmability provides the opportunity to write once then read many times.
  • a write once/read-multiple memory may be programmed at a point in time after the memory chip has left the factory. Once the memory is programmed, it may not be rewritten, but it may be read many times.
  • a read/write memory may be programmed and re-programed many times after leaving the factory. It may also be read many times.
  • the memory 235 may be configured to store one or more applets 240, one or more counters 245, and a customer identifier 250.
  • the one or more applets 240 may comprise one or more software applications configured to execute on one or more contact-based or contactless cards, such as Java Card applet. However, it is understood that applets 240 are not limited to Java Card applets, and instead may be any software application operable on contact-based or contactless cards or other devices having limited memory.
  • the one or more counters 245 may comprise a numeric counter sufficient to store an integer.
  • the customer identifier 250 may comprise a unique alphanumeric identifier assigned to a user of the first device 200, and the identifier may distinguish the user of the contactless card from other contactless card users.
  • the customer identifier 250 may identify both a customer and an account assigned to that customer and may further identify the contactless card associated with the customer’s account.
  • the processor and memory elements of the foregoing exemplary embodiments are described with reference to the contact pad, but the present disclosure is not limited thereto. It is understood that these elements may be implemented outside of the contact pad 220 or entirely separate from it, or as further elements in addition to processor 230 and memory 235 elements located within the contact pad 220.
  • the first device 200 may comprise one or more antennas 255.
  • the one or more antennas 255 may be placed within the first device 200 and around the processing circuitry 225 of the contact pad 220.
  • the one or more antennas 255 may be integral with the processing circuitry 225 and the one or more antennas 255 may be used with an external booster coil.
  • the one or more antennas 255 may be external to the contact pad 220 and the processing circuitry 225.
  • the coil of first device 200 may act as the secondary of an air core transformer.
  • the terminal may communicate with the first device 200 by cutting power or amplitude modulation.
  • the first device 200 may infer the data transmitted from the terminal using the gaps in the first device’s power connection, which may be functionally maintained through one or more capacitors.
  • the first device 200 may communicate back by switching a load on the first device’s coil or load modulation. Load modulation may be detected in the terminal’s coil through interference.
  • Figure 3 depicts a method 300 of authentication.
  • Figure 3 may reference the same or similar components of system 100 of FIG. 1, and first device 200 of FIG. 2 A and FIG. 2B.
  • the method 300 may include receiving, at a processor, one or more challenges.
  • a relying party or server may be configured to generate a first challenge.
  • the relying party may be configured to challenge the authenticator, such as a processor of a mobile device, to login.
  • the first challenge may include an identifier, such as a user identifier or a site identifier, that may be used to select an appropriate FIDO key pair.
  • the first challenge may further include an unpredictable number, which may be given by the relying party, that is used to prevent replay. For example, for each instance of authentication, a new unpredictable number will be needed and thus the unpredictable number will be different each time. In this manner, this avoids utilizing a signature of the old unpredictable number and instead utilizes the number for the instant session of authentication.
  • an unpredictable number which may be given by the relying party, that is used to prevent replay. For example, for each instance of authentication, a new unpredictable number will be needed and thus the unpredictable number will be different each time. In this manner, this avoids utilizing a signature of the old unpredictable number and instead utilizes the number for the instant session of authentication.
  • the first request may comprise an authentication request.
  • the authentication request may comprise a request for Fast Identity Online 2 (FID02) website registration.
  • the processor may be configured to generate one or more instructions.
  • the processor may be configured to generate a first instruction.
  • Each instruction may include one or more requests.
  • the first instruction may include a first request to retrieve a first key from the processor of the first device.
  • the key may comprise a FIDO key.
  • the first key may be retrieved via entry of a communication interface of the first device into a communication field.
  • the first instruction may include a request to generate the first key by the processor of the first device.
  • the first instruction may include a request to regenerate the first FIDO key, such as a private key which is part of a public/private key pair, by the processor of the first device.
  • the method 300 may include generating, by the processor, a first instruction including a request to retrieve a first Fast Identity Online (FIDO) key from a first device.
  • the authenticator such as processor of a mobile device, may be configured to prompt one or more entries of a first device by generating one or more instructions.
  • the one or more entries may include at least one selected from the group of a tap, a swipe, a wave, or the like, and/or any combination thereof.
  • the first instruction may include a request to generate the first FIDO key by the first device.
  • the first FIDO key may be generated based on a master key and an identifier associated with the first request using one or more cryptographic algorithms.
  • the identifier may include a site identifier and combined with the master key to produce a key pair.
  • the master key be stored on the first device, and the master key may be combined with the site identifier on the first device to generate the private key.
  • the master key may be transferred from the first device to the application comprising instructions for execution on the second device, in which the combining of the master key and the site identifier is performed by the application of the second device to generate the private key.
  • the first FIDO key may be generated or stored in a secure element belonging to the second device.
  • the FIDO private key may be stored in a secure element maintained by the second device.
  • the secure element may comprise a tamper-resistant secure storage area in which one or more keys may be securely stored and retrieved by the server.
  • the method 300 may include transmitting, by the processor, the first instruction.
  • the processor may be configured to transmit the first instruction to the first device.
  • the first instruction may be transmitted to the processor of the first device by the authenticator.
  • the authenticator may be configured to transmit the first instruction to the first device.
  • the method 300 may include receiving the first FIDO key.
  • a communication interface of the first device may enter a communication field of the authenticator, such as the communication field of the mobile device, to transfer the first FIDO key.
  • the first device may be configured to, depending on the first instruction received from the authenticator, generate or retrieve a FIDO key pair associated with a specific user or site.
  • the generated or retrieved FIDO key pair may be read by the authenticator.
  • the FIDO key pair may include a FIDO private key which may be read by the authenticator from the first device and may be used by the authenticator to sign the first challenge resulting in a signed challenge data.
  • the FIDO private key may be retrieved via entry of a communication interface of the first device into a communication field.
  • the FIDO private key may be encrypted by the first device prior to its transfer to the authenticator, in which case the processor of the mobile device may be configured to decrypt the received encrypted FIDO private key.
  • the FIDO private key may be generated based on a master key and an identifier associated with the authentication request using one or more cryptographic algorithms.
  • the identifier may include a site identifier and combined with the master key to produce another key pair.
  • the first device may be configured to store a finite number of keys in its memory so as to avoid having to regenerate keys.
  • the first instruction from the authenticator may include a request to regenerate the FIDO private key, such as a private key which is part of a public/private key pair, by the first device.
  • the master key be stored in memory on the first device, and the master key may be combined with the site identifier on the first device to generate the FIDO private key.
  • the master key may be transferred from the first device to the authenticator, in which the combining of the master key and the site identifier is performed by the authenticator to generate the FIDO private key.
  • transmission of the FIDO private key from the first device to the authenticator may be prevented.
  • OTA over the air
  • transmission of the FIDO private key is avoided when the first device performs the signing of the first challenge.
  • the first challenge and the site or user identifier information is transmitted to the first device from the authenticator, which thereby distributes its computation to the first device through near field communication (NFC) via a proxy protocol.
  • NFC near field communication
  • the FIDO private key may be generated or stored in a secure element belonging to the authenticator.
  • the FIDO private key may be stored in a secure element maintained by a second device.
  • the secure element may comprise a tamper-resistant secure storage area in which one or more keys may be securely stored and retrieved by the relying party.
  • the processor of the first device may be configured to generate the FIDO private key.
  • the processor of the first device may be configured to transmit the FIDO private key.
  • the processor of the first device may be configured to transmit the FIDO private key to the authenticator, such as an application comprising instructions for execution on a second device.
  • the authenticator may be, without limitation, a mobile device such as a laptop or a tablet or a phone.
  • the FIDO private key may be transmitted and received via one or more channels.
  • the FIDO private key may be transmitted and received via an out-of-band channel.
  • the processor of the first device may be configured to transmit the FIDO private key to the authenticator via entry of the communication interface of the first device into a communication field of the authenticator.
  • the entry may be associated with one or more gestures, including but not limited to one or more taps, swipes, waves, and/or any combination thereof.
  • the processor of the first device may be configured to generate the first FIDO key.
  • the processor of the first device may be configured to transmit the first FIDO key.
  • the processor of the first device may be configured to transmit the first FIDO key to an application comprising instructions for execution on a second device.
  • the second device may be, without limitation, a mobile device such as a laptop or a tablet or a phone.
  • the first FIDO key may be transmitted and received via one or more channels.
  • the first FIDO key may be transmitted and received via an out-of-band channel.
  • the processor of the first device may be configured to transmit the first FIDO key to the application of the second device via entry of the communication interface into a communication field of the second device.
  • the entry may be associated with one or more gestures, including but not limited to one or more taps, swipes, waves, and/or any combination thereof.
  • the application of the second device may be configured to transmit the first FIDO key to the processor of the server for validation, and thus the second device may be configured to serve as an intermediary device between the first device and the processor.
  • the method 300 may include signing, by the processor, the one or more challenges using the first FIDO key.
  • the method 300 may include transmitting, by the processor, one or more signed challenges for validation using a second FIDO key.
  • the processor may be configured to transmit one or more signed challenges to the relying party.
  • the relying party may receive the signed challenge data from the authenticator, such as the processor of the mobile device.
  • the relying party may perform validation of the signed challenge data.
  • the relying party may validate the signed challenge data with the FIDO public key that was stored when the user registered to the site.
  • the validation may comprise the result of the authentication process, which includes signature verification.
  • the authenticator may be configured to transmit the first FIDO key to the processor of the relying party for validation, and thus the authenticator may be configured to serve as an intermediary device between the first device and the processor of the relying party.
  • the relying party may be configured to validate the FIDO private key via a website FIDO service.
  • the relying party may be configured to validate the signed challenge data transmitted from the authenticator using a second FIDO key, such as a FIDO public key, which may be part of the public/private key pair as previously explained.
  • a second FIDO key such as a FIDO public key
  • the application comprising instructions for execution on the second device may be configured to sign the first challenge issued by the website using the FIDO private key.
  • the processor may be transmitted to the processor for validation using the FIDO public key stored in memory of the server.
  • the relying party may be configured to generate a second instruction.
  • the second instruction may include a second request to transmit input data.
  • the relying party may be configured to transmit the second instruction.
  • the relying party may be configured to transmit the second instruction to the authenticator.
  • the second instruction may be forwarded by the relying party to the application via one or more push notifications.
  • the second instruction may be transmitted by the relying party after evaluation by the relying party and/or a database of one or more conditions. For example, at least one of the one or more conditions may include determining a threshold number of authentication requests over a predetermined time period.
  • the relying party and/or database may be configured to determine whether an abnormal number of transactions or requests were performed within any number of seconds, minutes, hours, days, weeks, months, years, etc.
  • at least one of the one or more conditions may include determining whether misuse or fraud associated with an account and/or user occurred.
  • the relying party and/or the database may be configured to determine whether a user transaction history is indicative of excessive amount of purchases or abnormal locations. In this manner, conditional multifactor authentication may be implemented to improve security, which may trigger transmittal of the second instruction for receiving the input data.
  • the relying party may be configured to receive, based on the second instruction, the input data.
  • the relying party may be configured to receive the input data from the authenticator, such as from the application comprising instructions for execution on the second device.
  • the input data may include at least one selected from the group of biometric data and credential data.
  • the input data may include biometric data, credential data, and/or any combination thereof.
  • the biometric data may include at least one selected from the group of a fingerprint, a facial scan, a retinal scan, a voice recognition, and/or any combination thereof.
  • the input data may additionally and/or alternatively include credential data.
  • the login data may include at least one selected from the group of an entry of a user name, a password, an account number, a security code, a one-time passcode, an answer to a security question, and/or any combination thereof.
  • the relying party may be configured to complete the authentication request by authenticating the input data.
  • the relying party may be configured to generate one or more outcomes by comparing the received input data with reference input data.
  • the reference input data may be stored in a memory of the relying party. In other examples, the reference input data may be requested by the relying party.
  • the relying party may be configured to receive, via one or more requests, reference input data, or alternatively transmit the input data for comparison with the reference input data to the database.
  • the processor of the relying party may be configured to generate an outcome indicative of successful authentication when it results in a successful match based on the comparison between the received input data with reference input data.
  • the processor of the relying party may be configured to generate an outcome of unsuccessful authentication when it results in an unsuccessful match based on the comparison between the received input data with reference input data.
  • the processor of the relying party may be configured to re-authenticate the input data up to and including a predetermined number of attempts before successfully authenticating the input data so as to complete the authentication request, or aborting the completion of the authentication request.
  • the authentication system may implement with distributed storage, cloud-based storage, and other forms of storage in support of the aforementioned functionalities.
  • Figure 4 depicts a sequence diagram 400 of an authentication process according to an exemplary embodiment.
  • Figure 4 may reference the same or similar components of system 100, first device 200 of FIG. 2 A and FIG. 2B, and method 300 of FIG. 3.
  • a processor may be configured to receive an authentication request.
  • the processor may be part of a relying party or server.
  • the authentication request may comprise a request for Fast Identity Online 2 (FID02) website registration.
  • the request may be received from a browser extension.
  • FID02 Fast Identity Online 2
  • the processor may be configured to generate, responsive to the authentication request, one or more challenges.
  • the processor may be configured to generate a first challenge.
  • the relying party may be configured to challenge the authenticator, such as a processor of a mobile device, to login.
  • the first challenge may include an identifier, such as a user identifier or a site identifier, that may be used to select an appropriate FIDO key pair.
  • the first challenge may further include an unpredictable number, which may be given by the relying party, that is used to prevent replay. For example, for each instance of authentication, a new unpredictable number will be needed and thus the unpredictable number will be different each time. In this manner, this avoids utilizing a signature of the old unpredictable number and instead utilizes the number for the instant session of authentication.
  • the processor may be configured to transmit the first challenge.
  • the processor may be configured to transmit the first instruction to an authenticator, such as the application comprising instructions for execution on a device, including but not limited to a mobile device.
  • a first instruction may be transmitted to a first device.
  • the first instruction may be generated and/or transmitted by the authenticator to a processor of a card.
  • the processor may be configured to generate one or more instructions.
  • the processor may be configured to generate a first instruction.
  • Each instruction may include one or more requests.
  • the first instruction may include a first request to retrieve a first key from the processor of the first device.
  • the key may comprise a FIDO key.
  • the first key may be retrieved via entry of a communication interface of the first device into a communication field, such as the communication field of the authenticator.
  • the first instruction may include a request to generate the first key by the processor of the first device.
  • the first instruction may include a request to regenerate the first FIDO key, such as a private key which is part of a public/private key pair, by the processor of the first device.
  • the authenticator such as processor of the mobile device, may be configured to prompt one or more entries of a first device by generating one or more instructions.
  • the one or more entries may include at least one selected from the group of a tap, a swipe, a wave, or the like, and/or any combination thereof.
  • the first instruction may include a request to generate the first FIDO key by the first device.
  • the first FIDO key may be generated based on a master key and an identifier associated with the first request using one or more cryptographic algorithms.
  • the identifier may include a site identifier and combined with the master key to produce a key pair.
  • the master key be stored on the first device, and the master key may be combined with the site identifier on the first device to generate the private key.
  • the processor of the first device may be configured to generate and transmit the first FIDO key.
  • a communication interface of the first device may enter a communication field of the authenticator, such as the communication field of the mobile device, to transfer the first FIDO key.
  • the first device may be configured to, depending on the first instruction received from the authenticator, generate or retrieve a FIDO key pair associated with a specific user or site. The generated or retrieved FIDO key pair may be read by the authenticator.
  • the FIDO key pair may include a FIDO private key which may be read by the authenticator from the first device and may be used by the authenticator to sign the first challenge resulting in a signed challenge data.
  • the FIDO private key may be retrieved via entry of a communication interface of the first device into a communication field.
  • the FIDO private key may be encrypted by the first device prior to its transfer to the authenticator, in which case the processor of the mobile device may be configured to decrypt the received encrypted FIDO private key.
  • the FIDO private key may be generated based on a master key and an identifier associated with the authentication request using one or more cryptographic algorithms.
  • the identifier may include a site identifier and combined with the master key to produce another key pair.
  • the first device may be configured to store a finite number of keys in its memory so as to avoid having to regenerate keys.
  • the first instruction from the authenticator may include a request to regenerate the FIDO private key, such as a private key which is part of a public/private key pair, by the first device.
  • the master key be stored in memory on the first device, and the master key may be combined with the site identifier on the first device to generate the FIDO private key.
  • the master key may be transferred from the first device to the authenticator, in which the combining of the master key and the site identifier is performed by the authenticator to generate the FIDO private key.
  • transmission of the FIDO private key from the first device to the authenticator may be prevented.
  • OTA over the air
  • transmission of the FIDO private key is avoided when the first device performs the signing of the first challenge.
  • the first challenge and the site or user identifier information is transmitted to the first device from the authenticator, which thereby distributes its computation to the first device through near field communication (NFC) via a proxy protocol.
  • NFC near field communication
  • the FIDO private key may be generated or stored in a secure element belonging to the authenticator.
  • the FIDO private key may be stored in a secure element maintained by a second device.
  • the secure element may comprise a tamper-resistant secure storage area in which one or more keys may be securely stored and retrieved by the relying party.
  • the processor of the first device may be configured to generate the FIDO private key.
  • the processor of the first device may be configured to transmit the FIDO private key.
  • the processor of the first device may be configured to transmit the FIDO private key to the authenticator, such as an application comprising instructions for execution on a second device.
  • the authenticator may be, without limitation, a mobile device such as a laptop or a tablet or a phone.
  • the FIDO private key may be transmitted and received via one or more channels.
  • the FIDO private key may be transmitted and received via an out-of-band channel.
  • the processor of the first device may be configured to transmit the FIDO private key to the authenticator via entry of the communication interface of the first device into a communication field of the authenticator.
  • the entry may be associated with one or more gestures, including but not limited to one or more taps, swipes, waves, and/or any combination thereof.
  • the authenticator may be configured to receive the first FIDO key.
  • the application of the second device may be configured to receive the first FIDO private key from the processor of the first device.
  • the authenticator may be configured to sign the first challenge using the received first FIDO key.
  • the authenticator may be configured to transmit the signed first challenge to the relying party for validation.
  • the processor of the relying party or server may be configured to validate the signed first challenge.
  • the processor of the relying party or server may be configured to receive the signed first challenge from the authenticator.
  • the relying party may validate the signed challenge data with the FIDO public key that was stored when the user registered to the site.
  • the validation may comprise the result of the authentication process, which includes signature verification.
  • the authenticator may be configured to transmit the first FIDO key to the processor of the relying party for validation, and thus the authenticator may be configured to serve as an intermediary device between the first device and the processor of the relying party.
  • the processor of the relying party or server may be configured to generate a second instruction.
  • the second instruction may include a second request to transmit input data.
  • the processor may be configured to evaluate one or more conditions.
  • the second instruction may be transmitted by the processor after evaluation of one or more conditions.
  • at least one of the one or more conditions may include determining a threshold number of authentication requests over a predetermined time period.
  • the processor may be configured to determine whether an abnormal number of transactions or requests were performed within any number of seconds, minutes, hours, days, weeks, months, years, etc.
  • at least one of the one or more conditions may include determining whether misuse or fraud associated with an account and/or user occurred.
  • the processor may be configured to determine whether a user transaction history is indicative of excessive amount of purchases or abnormal locations. In this manner, conditional multifactor authentication may be implemented to improve security, which may trigger transmittal of the second instruction for receiving the input data.
  • the authenticator may be configured to receive the second instruction.
  • the processor of the mobile device may be configured to receive, after evaluation of the one or more conditions by the relying party or server, the second instruction from the processor of the relying party or server.
  • the second instruction may be forwarded by the processor of the relying party or server to the authenticator, such as the application comprising instructions for execution of the mobile device via one or more push notifications.
  • the authenticator may be configured to transmit, based on the second instruction, the input data.
  • the processor or application of the mobile device may be configured to transmit the input data to the relying party, such as the processor of the server.
  • the input data may include at least one selected from the group of biometric data and credential data.
  • the input data may include biometric data, credential data, and/or any combination thereof.
  • the biometric data may include at least one selected from the group of a fingerprint, a facial scan, a retinal scan, a voice recognition, and/or any combination thereof.
  • the input data may additionally and/or alternatively include credential data.
  • the login data may include at least one selected from the group of an entry of a user name, a password, an account number, a security code, a one-time passcode, an answer to a security question, and/or any combination thereof.
  • the relying party or server may be configured to complete the authentication request by authenticating the input data.
  • the processor of the relying party or server may be configured to receive the input data from the authenticator, such as the processor or application comprising instructions for execution of the mobile device.
  • the processor of the relying party or server may be configured to generate one or more outcomes by comparing the received input data with reference input data.
  • the reference input data may be stored by the relying party or server. In other examples, the reference input data may be requested by the relying party or server.
  • the processor of the relying party or server may be configured to receive, via one or more requests, reference input data, or alternatively transmit the input data for comparison with the reference input data to a database.
  • the relying party or server may be configured to generate an outcome indicative of successful authentication when it results in a successful match based on the comparison between the received input data with reference input data.
  • the relying party or server may be configured to generate an outcome of unsuccessful authentication when it results in an unsuccessful match based on the comparison between the received input data with reference input data.
  • sequence diagram 400 of authentication process may implement with distributed storage, cloud- based storage, and other forms of storage in support of the aforementioned functionalities.
  • Figure 5 depicts a method of 500 of authentication according to an exemplary embodiment.
  • Figure 5 may reference the same or similar components of system 100, first device 200 of FIG. 2A and FIG. 2B, method 300 of FIG. 3, and sequence diagram 400 of FIG. 4.
  • the method 500 may include receiving, at a processor, a first instruction.
  • the processor may be coupled to a memory comprising an application which includes instructions for execution on a first device, such as a card.
  • the first instruction may be associated with completion of an authentication request.
  • the authentication request may comprise a request for Fast Identity Online 2 (FID02) website registration.
  • FID02 Fast Identity Online 2
  • the first instruction may be a part of one or more instructions that are generated and/or transmitted by a processor of an authenticator, such as an application comprising instructions for execution on a second device, such as a client device or mobile device.
  • the processor of the authenticator may be configured to generate a first instruction.
  • Each instruction may include one or more requests.
  • the first instruction may include a first request to generate or retrieve a first key from the processor of a the first device.
  • the key may comprise a FIDO key, such as a FIDO private key.
  • the first instruction may include a request to retrieve a first Fast Identity Online (FIDO) key from a first device, including but not limited to a card.
  • the first instruction may include a request to generate the first FIDO key by the first device.
  • the first FIDO key may be generated based on a master key and an identifier associated with the first request using one or more cryptographic algorithms.
  • the identifier may include a site identifier and combined with the master key to produce a key pair.
  • the master key be stored on the first device, and the master key may be combined with the site identifier on the first device to generate the private key.
  • the first FIDO key may be generated or stored in a secure element belonging to an authenticator or second device, such as a client device that may include a mobile device.
  • the FIDO private key may be stored in a secure element maintained by the second device.
  • the secure element may comprise a tamper-resistant secure storage area in which one or more keys may be securely stored and retrieved by the authenticator or relying party server.
  • the authenticator may be configured to transmit the first instruction to the first device, such that the authenticator may be configured to act as an intermediary device between the first device and the relying party or server.
  • the method 500 may include generating a first key.
  • the first key may be retrieved via entry of a communication interface of the second device into a communication field of the authenticator or client device, such as a mobile device.
  • the first instruction may include a request to generate the first key by the first device.
  • the first instruction may include a request to regenerate the first FIDO key, such as a private key which is part of a public/private key pair, by the first device.
  • the authenticator such as the processor of the mobile device, may be configured to prompt one or more entries of the first device.
  • the one or more entries may include at least one selected from the group of a tap, a swipe, a wave, or the like, and/or any combination thereof.
  • a communication interface of the first device may enter a communication field of the authenticator, such as the communication field of the mobile device.
  • the first device may be configured to, based on the first instruction received from the authenticator, generate or retrieve a FIDO key pair associated with a specific user or site.
  • the processor of the first device may be configured to receive the first instruction from the authenticator via a first entry and transmit the FIDO private key to the authenticator via a second entry of the communication interface of the first device into a communication field of the authenticator.
  • the one or more entries may be associated with one or more gestures, including but not limited to one or more taps, swipes, waves, and/or any combination thereof.
  • the FIDO private key may be generated based on a master key and an identifier associated with the authentication request using one or more cryptographic algorithms.
  • the identifier may include a site identifier and combined with the master key to produce another key pair.
  • the first device may be configured to store a finite number of keys in its memory so as to avoid having to regenerate keys.
  • the first instruction from the authenticator may include a request to regenerate the FIDO private key, such as a private key which is part of a public/private key pair, by the first device.
  • the master key be stored in memory on the first device, and the master key may be combined with the site identifier on the first device to generate the FIDO private key.
  • the master key may be transferred from the first device to the authenticator, in which the combining of the master key and the site identifier is performed by the authenticator to generate the FIDO private key.
  • the FIDO private key may be generated or stored in a secure element belonging to the authenticator.
  • the FIDO private key may be stored in a secure element maintained by a second device.
  • the method 500 may include encrypting the first key.
  • the FIDO private key may be encrypted by the first device prior to its transfer to the authenticator.
  • the processor of the mobile device may be configured to decrypt the received encrypted FIDO private key prior to signing one or more challenges.
  • the method 500 may include transmitting the encrypted first key for validation.
  • the processor of the first device may be configured to transmit the encrypted FIDO private key to the authenticator for validation.
  • the generated or retrieved FIDO key pair may be read by the authenticator, including but not limited to via near field communication (NFC).
  • the FIDO key pair may include a FIDO private key which may be read by the authenticator from the first device.
  • the FIDO private key may be retrieved via one or more entries of a communication interface of the first device into a communication field of the authenticator.
  • transmission of the encrypted FIDO private key from the first device to the authenticator may be prevented.
  • OTA over the air
  • transmission of the FIDO private key is avoided when the first device is configured to perform signing of a first challenge.
  • the first challenge and the site or user identifier information is transmitted to the first device from the authenticator, which thereby distributes its computation to the first device through near field communication (NFC) via a proxy protocol.
  • NFC near field communication
  • the FIDO private key may be transmitted and received via one or more channels.
  • the FIDO private key may be transmitted and received via an out-of- band channel.
  • the authenticator may be configured to receive the FIDO private key from the first device via an out-of-band channel.
  • the authenticator may be configured to transmit the first FIDO key to the processor of the relying party for validation, and thus the authenticator may be configured to serve as an intermediary device between the first device and the processor of the relying party.
  • the relying party may be configured to generate and/or transmit one or more second instructions.
  • the second instruction may include a request to transmit input data.
  • the authenticator such as the processor of the second device, may be configured to receive the second instruction.
  • the processor of the second device may be configured to receive the request to transmit input data from the relying party or processor of the server.
  • the second instruction may be forwarded by the relying party or processor of the server to the authenticator, such as the processor of the second device, via one or more push notifications.
  • the second instruction may be received by the authenticator after evaluation of one or more conditions by the relying party or server.
  • At least one of the one or more conditions may include determining a threshold number of authentication requests over a predetermined time period.
  • the relying party may be configured to determine whether an abnormal number of transactions or requests were performed within any number of seconds, minutes, hours, days, weeks, months, years, etc.
  • at least one of the one or more conditions may include determining whether misuse or fraud associated with an account and/or user occurred.
  • the relying party may be configured to determine whether a user transaction history is indicative of excessive amount of purchases or abnormal locations. In this manner, conditional multifactor authentication may be implemented to improve security, which may trigger transmittal of the second instruction for receiving the input data.
  • Figure 6 depicts an authentication method 600 according to an exemplary embodiment.
  • Figure 6 may reference the same or similar components of system 100, first device 200 of FIG. 2A and FIG. 2B, method 300 of FIG. 3, sequence diagram 400 of FIG. 4, and method 500 of FIG. 5.
  • the method 600 may include receiving, at a processor, an authentication request.
  • the processor may belong to a relying party or server.
  • the authentication request may comprise a request for Fast Identity Online 2 (FID02) website registration.
  • FID02 Fast Identity Online 2
  • the method 600 may include transmitting, by the processor, a first challenge.
  • the processor may be configured to transmit the first challenge to an authenticator, such as an application comprising instructions for execution on an intermediary second device or client device.
  • the processor may be configured to generate, responsive to the authentication request, one or more challenges.
  • the processor may be configured to generate a first challenge.
  • the relying party may be configured to challenge the authenticator, such as a processor of a mobile device, to login.
  • the first challenge may include an identifier, such as a user identifier or a site identifier, that may be used to select an appropriate FIDO key pair.
  • the first challenge may further include an unpredictable number, which may be given by the relying party, that is used to prevent replay. For example, for each instance of authentication, a new unpredictable number will be needed and thus the unpredictable number will be different each time. In this manner, this avoids utilizing a signature of the old unpredictable number and instead utilizes the number for the instant session of authentication.
  • the method 600 may include validating the first challenge. For example, a first instruction may be transmitted to a first device by the authenticator. In some examples, the first instruction may be generated and/or transmitted by the authenticator to a processor of a card.
  • the authenticator such as the processor of the mobile device, may be configured to generate one or more instructions.
  • the processor of the mobile device may be configured to generate a first instruction.
  • Each instruction may include one or more requests.
  • the first instruction may include a first request to retrieve a first key from the processor of a first device, such as a card.
  • the key may comprise a FIDO key.
  • the FIDO private key may be retrieved via entry of a communication interface of the first device into a communication field, such as the communication field of the authenticator.
  • the first instruction may include a request to generate the FIDO private key by the processor of the first device.
  • the first instruction may include a request to regenerate the first FIDO key, such as the FIDO private key which is part of a public/private key pair, by the processor of the first device.
  • the authenticator may be configured to prompt, based on the first challenge received from the relying party or processor of the server, one or more entries of a first device by generating one or more instructions.
  • the one or more entries may include at least one selected from the group of a tap, a swipe, a wave, or the like, and/or any combination thereof.
  • the first instruction may include a request to generate the first FIDO key by the first device.
  • the first FIDO key may be generated based on a master key and an identifier associated with the first request using one or more cryptographic algorithms.
  • the identifier may include a site identifier and combined with the master key to produce a key pair.
  • the master key be stored on the first device, and the master key may be combined with the site identifier on the first device to generate the private key.
  • thee processor of the first device may be configured to generate and transmit the first FIDO key.
  • a communication interface of the first device may enter a communication field of the authenticator, such as the communication field of the mobile device, to transfer the first FIDO key.
  • the first device may be configured to, depending on the first instruction received from the authenticator, generate or retrieve a FIDO key pair associated with a specific user or site.
  • the generated or retrieved FIDO key pair may be read by the authenticator.
  • the FIDO key pair may include a FIDO private key which may be read by the authenticator from the first device and may be used by the authenticator to sign the first challenge resulting in a signed challenge data.
  • the FIDO private key may be retrieved via entry of a communication interface of the first device into a communication field.
  • the FIDO private key may be encrypted by the first device prior to its transfer to the authenticator, in which case the processor of the mobile device may be configured to decrypt the received encrypted FIDO private key.
  • the FIDO private key may be generated based on a master key and an identifier associated with the authentication request using one or more cryptographic algorithms.
  • the identifier may include a site identifier and combined with the master key to produce another key pair.
  • the first device may be configured to store a finite number of keys in its memory so as to avoid having to regenerate keys.
  • the first instruction from the authenticator may include a request to regenerate the FIDO private key, such as a private key which is part of a public/private key pair, by the first device.
  • the master key be stored in memory on the first device, and the master key may be combined with the site identifier on the first device to generate the FIDO private key.
  • the master key may be transferred from the first device to the authenticator, in which the combining of the master key and the site identifier is performed by the authenticator to generate the FIDO private key.
  • transmission of the FIDO private key from the first device to the authenticator may be prevented.
  • OTA over the air
  • transmission of the FIDO private key is avoided when the first device performs the signing of the first challenge.
  • the first challenge and the site or user identifier information is transmitted to the first device from the authenticator, which thereby distributes its computation to the first device through near field communication (NFC) via a proxy protocol.
  • NFC near field communication
  • the FIDO private key may be generated or stored in a secure element belonging to the authenticator.
  • the FIDO private key may be stored in a secure element maintained by a second device.
  • the secure element may comprise a tamper-resistant secure storage area in which one or more keys may be securely stored and retrieved by the relying party.
  • the processor of the first device may be configured to generate the FIDO private key.
  • the processor of the first device may be configured to transmit the FIDO private key.
  • the processor of the first device may be configured to transmit the FIDO private key to the authenticator, such as an application comprising instructions for execution on a second device.
  • the authenticator may be, without limitation, a mobile device such as a laptop or a tablet or a phone.
  • the FIDO private key may be transmitted and received via one or more channels.
  • the FIDO private key may be transmitted and received via an out-of-band channel.
  • the processor of the first device may be configured to transmit the FIDO private key to the authenticator via entry of the communication interface of the first device into a communication field of the authenticator.
  • the entry may be associated with one or more gestures, including but not limited to one or more taps, swipes, waves, and/or any combination thereof.
  • the authenticator may be configured to receive the first FIDO key.
  • the application of the second device may be configured to receive the first FIDO private key from the processor of the first device.
  • the authenticator may be configured to sign the first challenge using the received first FIDO key.
  • the authenticator may be configured to transmit the signed first challenge to the relying party for validation.
  • the processor of the relying party or server may be configured to validate the signed first challenge.
  • the processor of the relying party or server may be configured to receive the signed first challenge from the authenticator.
  • the relying party may validate the signed challenge data with the FIDO public key that was stored when the user registered to the site.
  • the validation may comprise the result of the authentication process, which includes signature verification.
  • the authenticator may be configured to transmit the first FIDO key to the processor of the relying party for validation, and thus the authenticator may be configured to serve as an intermediary device between the first device and the processor of the relying party.
  • the method 600 may include evaluating, by the processor, one or more conditions.
  • at least one of the one or more conditions may include determining a threshold number of authentication requests over a predetermined time period.
  • the processor may be configured to determine whether an abnormal number of transactions or requests were performed within any number of seconds, minutes, hours, days, weeks, months, years, etc.
  • at least one of the one or more conditions may include determining whether misuse or fraud associated with an account and/or user occurred.
  • the processor may be configured to determine whether a user transaction history is indicative of excessive amount of purchases or abnormal locations. In this manner, conditional multifactor authentication may be implemented to improve security, which may trigger transmittal of the second challenge for receiving the input data.
  • the method 600 may include transmitting, by the processor, a second challenge.
  • the processor of the relying party or server may be configured to generate a second challenge.
  • the second challenge may include a second request to transmit input data.
  • the processor of the relying party or server may be configured to evaluate one or more conditions, as previously explained.
  • the second challenge may be transmitted by the processor after evaluation of one or more conditions.
  • the authenticator may be configured to receive the second challenge.
  • the processor of the mobile device may be configured to receive, after evaluation of the one or more conditions by the relying party or server, the second challenge from the processor of the relying party or server.
  • the second challenge may be forwarded by the processor of the relying party or server to the authenticator, such as the application comprising instructions for execution of the mobile device via one or more push notifications.
  • the authenticator may be configured to transmit, based on the second challenge, the input data.
  • the processor or application of the mobile device may be configured to transmit the input data to the relying party, such as the processor of the server.
  • the input data may include at least one selected from the group of biometric data and credential data.
  • the input data may include biometric data, credential data, and/or any combination thereof.
  • the biometric data may include at least one selected from the group of a fingerprint, a facial scan, a retinal scan, a voice recognition, and/or any combination thereof.
  • the input data may additionally and/or alternatively include credential data.
  • the login data may include at least one selected from the group of an entry of a user name, a password, an account number, a security code, a one-time passcode, an answer to a security question, and/or any combination thereof.
  • the method 600 may include authenticating, by the processor, received input data.
  • the processor of the relying party or server may be configured to complete the authentication request by authenticating the input data.
  • the processor of the relying party or server may be configured to receive the input data from the authenticator, such as the processor or application comprising instructions for execution of the mobile device.
  • the processor of the relying party or server may be configured to generate one or more outcomes by comparing the received input data with reference input data.
  • the reference input data may be stored by the relying party or server. In other examples, the reference input data may be requested by the relying party or server.
  • the processor of the relying party or server may be configured to receive, via one or more requests, reference input data, or alternatively transmit the input data for comparison with the reference input data to a database.
  • the relying party or server may be configured to generate an outcome indicative of successful authentication when it results in a successful match based on the comparison between the received input data with reference input data.
  • the relying party or server may be configured to generate an outcome of unsuccessful authentication when it results in an unsuccessful match based on the comparison between the received input data with reference input data.
  • sequence diagram 400 of authentication process may implement with distributed storage, cloud- based storage, and other forms of storage in support of the aforementioned functionalities.
  • sequence diagram 400 of authentication process may implement with distributed storage, cloud- based storage, and other forms of storage in support of the aforementioned functionalities.
  • the systems and methods described herein may be tangibly embodied in one of more physical media, such as, but not limited to, a compact disc (CD), a digital versatile disc (DVD), a floppy disk, a hard drive, read only memory (ROM), random access memory (RAM), as well as other physical media capable of data storage.
  • data storage may include random access memory (RAM) and read only memory (ROM), which may be configured to access and store data and information and computer program instructions.
  • Data storage may also include storage media or other suitable type of memory (e.g., such as, for example, RAM, ROM, programmable read-only memory (PROM), erasable programmable read only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, flash drives, any type of tangible and non-transitory storage medium), where the files that comprise an operating system, application programs including, for example, web browser application, email application and/or other applications, and data files may be stored.
  • RAM random access memory
  • ROM read only memory
  • ROM read only memory
  • EEPROM electrically erasable programmable read-only memory
  • magnetic disks e.g., magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, flash drives,
  • the data storage of the network-enabled computer systems may include electronic information, files, and documents stored in various ways, including, for example, a flat file, indexed file, hierarchical database, relational database, such as a database created and maintained with software from, for example, Oracle® Corporation, Microsoft® Excel file, Microsoft® Access file, a solid state storage device, which may include a flash array, a hybrid array, or a server-side product, enterprise storage, which may include online or cloud storage, or any other storage mechanism.
  • the figures illustrate various components (e.g., servers, computers, processors, etc.) separately. The functions described as being performed at various components may be performed at other components, and the various components may be combined or separated. Other modifications also may be made.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Biodiversity & Conservation Biology (AREA)
  • General Health & Medical Sciences (AREA)
  • Biomedical Technology (AREA)
  • Life Sciences & Earth Sciences (AREA)
  • Health & Medical Sciences (AREA)
  • Theoretical Computer Science (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • Computer Hardware Design (AREA)
  • General Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephone Function (AREA)
  • Telephonic Communication Services (AREA)
PCT/US2022/033724 2021-06-18 2022-06-16 Systems and methods for contactless card communication and multi-device key pair cryptographic authentication Ceased WO2022266283A1 (en)

Priority Applications (6)

Application Number Priority Date Filing Date Title
CN202280055032.4A CN117795505A (zh) 2021-06-18 2022-06-16 用于非接触式卡通信和多设备密钥对加密认证的系统与方法
EP22744348.8A EP4356269A1 (en) 2021-06-18 2022-06-16 Systems and methods for contactless card communication and multi-device key pair cryptographic authentication
KR1020237044743A KR20240024112A (ko) 2021-06-18 2022-06-16 비접촉식 카드 통신 및 다중 디바이스 키 쌍 암호화 인증을 위한 시스템 및 방법
JP2023577529A JP2024527492A (ja) 2021-06-18 2022-06-16 非接触型カード通信及びマルチ装置鍵ペア暗号認証のためのシステム及び方法
CA3222325A CA3222325A1 (en) 2021-06-18 2022-06-16 Systems and methods for contactless card communication and multi-device key pair cryptographic authentication
AU2022292656A AU2022292656A1 (en) 2021-06-18 2022-06-16 Systems and methods for contactless card communication and multi-device key pair cryptographic authentication

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US17/352,181 US12301735B2 (en) 2021-06-18 2021-06-18 Systems and methods for contactless card communication and multi-device key pair cryptographic authentication
US17/352,181 2021-06-18

Publications (1)

Publication Number Publication Date
WO2022266283A1 true WO2022266283A1 (en) 2022-12-22

Family

ID=82611093

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2022/033724 Ceased WO2022266283A1 (en) 2021-06-18 2022-06-16 Systems and methods for contactless card communication and multi-device key pair cryptographic authentication

Country Status (8)

Country Link
US (2) US12301735B2 (cg-RX-API-DMAC7.html)
EP (1) EP4356269A1 (cg-RX-API-DMAC7.html)
JP (1) JP2024527492A (cg-RX-API-DMAC7.html)
KR (1) KR20240024112A (cg-RX-API-DMAC7.html)
CN (1) CN117795505A (cg-RX-API-DMAC7.html)
AU (1) AU2022292656A1 (cg-RX-API-DMAC7.html)
CA (1) CA3222325A1 (cg-RX-API-DMAC7.html)
WO (1) WO2022266283A1 (cg-RX-API-DMAC7.html)

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
SG11202102543WA (en) * 2018-10-02 2021-04-29 Capital One Services Llc Systems and methods for cryptographic authentication of contactless cards
US12126613B2 (en) * 2021-09-17 2024-10-22 Nok Nok Labs, Inc. System and method for pre-registration of FIDO authenticators
TWI838149B (zh) * 2023-03-06 2024-04-01 中華電信股份有限公司 企業認證的安全啟用系統及其方法
US20240303649A1 (en) * 2023-03-09 2024-09-12 Capital One Services, Llc Systems and methods for secure authentication through near field communication
US20260162110A1 (en) * 2024-12-05 2026-06-11 Capital One Services, Llc Methods and systems for universal identity verification for fido passkey registration
US20260220244A1 (en) * 2025-01-30 2026-07-30 Capital One Services, Llc Methods and devices for preregistered parallel fido keys for issuer authentication

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013109932A1 (en) * 2012-01-18 2013-07-25 OneID Inc. Methods and systems for secure identity management
US20200127858A1 (en) * 2017-01-27 2020-04-23 Giesecke+Devrient Mobile Security Gmbh Method for carrying out an authentication
US20200336308A1 (en) * 2020-07-02 2020-10-22 BehavioSec Inc FIDO Authentication with Behavior Report to Maintain Secure Data Connection

Family Cites Families (566)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
FR2523745B1 (fr) 1982-03-18 1987-06-26 Bull Sa Procede et dispositif de protection d'un logiciel livre par un fournisseur a un utilisateur
JPS6198476A (ja) 1984-10-19 1986-05-16 Casio Comput Co Ltd カードターミナル
FR2613565B1 (fr) 1987-04-03 1989-06-23 Bull Cps Procede pour acheminer des cles secretes vers des modules de securite et des cartes utilisateurs, dans un reseau de traitement d'informations
US5036461A (en) 1990-05-16 1991-07-30 Elliott John C Two-way authentication system between user's smart card and issuer-specific plug-in application modules in multi-issued transaction device
FR2704341B1 (fr) 1993-04-22 1995-06-02 Bull Cp8 Dispositif de protection des clés d'une carte à puce.
US5363448A (en) 1993-06-30 1994-11-08 United Technologies Automotive, Inc. Pseudorandom number generation and cryptographic authentication
US5377270A (en) 1993-06-30 1994-12-27 United Technologies Automotive, Inc. Cryptographic authentication of transmitted messages using pseudorandom numbers
JP3053527B2 (ja) 1993-07-30 2000-06-19 インターナショナル・ビジネス・マシーンズ・コーポレイション パスワードを有効化する方法及び装置、パスワードを生成し且つ予備的に有効化する方法及び装置、認証コードを使用して資源のアクセスを制御する方法及び装置
US5537314A (en) 1994-04-18 1996-07-16 First Marketrust Intl. Referral recognition system for an incentive award program
US7152045B2 (en) 1994-11-28 2006-12-19 Indivos Corporation Tokenless identification system for authorization of electronic transactions and electronic transmissions
US5764789A (en) 1994-11-28 1998-06-09 Smarttouch, Llc Tokenless biometric ATM access system
US5778072A (en) 1995-07-07 1998-07-07 Sun Microsystems, Inc. System and method to transparently integrate private key operations from a smart card with host-based encryption services
US5666415A (en) 1995-07-28 1997-09-09 Digital Equipment Corporation Method and apparatus for cryptographic authentication
US5832090A (en) 1995-08-10 1998-11-03 Hid Corporation Radio frequency transponder stored value system employing a secure encryption protocol
US5748740A (en) 1995-09-29 1998-05-05 Dallas Semiconductor Corporation Method, apparatus, system and firmware for secure transactions
US6049328A (en) 1995-10-20 2000-04-11 Wisconsin Alumni Research Foundation Flexible access system for touch screen devices
US5616901A (en) 1995-12-19 1997-04-01 Talking Signs, Inc. Accessible automatic teller machines for sight-impaired persons and print-disabled persons
DE69704684T2 (de) 1996-02-23 2004-07-15 Fuji Xerox Co., Ltd. Vorrichtung und Verfahren zur Authentifizierung von Zugangsrechten eines Benutzers zu Betriebsmitteln nach dem Challenge-Response-Prinzip
US6226383B1 (en) 1996-04-17 2001-05-01 Integrity Sciences, Inc. Cryptographic methods for remote authentication
US5768373A (en) 1996-05-06 1998-06-16 Symantec Corporation Method for providing a secure non-reusable one-time password
US5901874A (en) 1996-05-07 1999-05-11 Breakthrough Marketing, Inc. Handicapped accessible dumpster
US6058373A (en) 1996-10-16 2000-05-02 Microsoft Corporation System and method for processing electronic order forms
US6483920B2 (en) 1996-12-04 2002-11-19 Bull, S.A. Key recovery process used for strong encryption of messages
US5796827A (en) 1996-11-14 1998-08-18 International Business Machines Corporation System and method for near-field human-body coupling for encrypted communication with identification cards
US6021203A (en) 1996-12-11 2000-02-01 Microsoft Corporation Coercion resistant one-time-pad cryptosystem that facilitates transmission of messages having different levels of security
US6061666A (en) 1996-12-17 2000-05-09 Citicorp Development Center Automatic bank teller machine for the blind and visually impaired
GB9626196D0 (en) 1996-12-18 1997-02-05 Ncr Int Inc Self-service terminal (sst) and a method of oerating the sst to control movement of a card of the sst
US6282522B1 (en) 1997-04-30 2001-08-28 Visa International Service Association Internet payment system using smart card
US7290288B2 (en) 1997-06-11 2007-10-30 Prism Technologies, L.L.C. Method and system for controlling access, by an authentication server, to protected computer resources provided via an internet protocol network
US5960411A (en) 1997-09-12 1999-09-28 Amazon.Com, Inc. Method and system for placing a purchase order via a communications network
US5983273A (en) 1997-09-16 1999-11-09 Webtv Networks, Inc. Method and apparatus for providing physical security for a user account and providing access to the user's environment and preferences
US5883810A (en) 1997-09-24 1999-03-16 Microsoft Corporation Electronic online commerce card with transactionproxy number for online transactions
AU755458B2 (en) 1997-10-14 2002-12-12 Visa International Service Association Personalization of smart cards
IL122105A0 (en) 1997-11-04 1998-04-05 Rozin Alexander A two-way radio-based electronic toll collection method and system for highway
US6889198B2 (en) 1998-01-30 2005-05-03 Citicorp Development Center, Inc. Method and system for tracking smart card loyalty points
US7207477B1 (en) 2004-03-08 2007-04-24 Diebold, Incorporated Wireless transfer of account data and signature from hand-held device to electronic check generator
US6199762B1 (en) 1998-05-06 2001-03-13 American Express Travel Related Services Co., Inc. Methods and apparatus for dynamic smartcard synchronization and personalization
ES2234203T3 (es) 1998-05-11 2005-06-16 Citicorp Development Center, Inc. Sistema y metodo de autenticacion biometrica de un usuario de tarjeta inteligente.
JP3112076B2 (ja) 1998-05-21 2000-11-27 豊 保倉 ユーザ認証システム
US6615189B1 (en) 1998-06-22 2003-09-02 Bank One, Delaware, National Association Debit purchasing of stored value card for use by and/or delivery to others
US6216227B1 (en) 1998-06-29 2001-04-10 Sun Microsystems, Inc. Multi-venue ticketing using smart cards
US6032136A (en) 1998-11-17 2000-02-29 First Usa Bank, N.A. Customer activated multi-value (CAM) card
US7660763B1 (en) 1998-11-17 2010-02-09 Jpmorgan Chase Bank, N.A. Customer activated multi-value (CAM) card
US6438550B1 (en) 1998-12-10 2002-08-20 International Business Machines Corporation Method and apparatus for client authentication and application configuration via smart cards
US6829711B1 (en) 1999-01-26 2004-12-07 International Business Machines Corporation Personal website for electronic commerce on a smart java card with multiple security check points
EP1153375B1 (en) 1999-02-18 2003-01-15 Orbis Patents Limited Credit card system and method
US6731778B1 (en) 1999-03-31 2004-05-04 Oki Electric Industry Co, Ltd. Photographing apparatus and monitoring system using same
US6402028B1 (en) 1999-04-06 2002-06-11 Visa International Service Association Integrated production of smart cards
US7127605B1 (en) 1999-05-10 2006-10-24 Axalto, Inc. Secure sharing of application methods on a microcontroller
US6227447B1 (en) 1999-05-10 2001-05-08 First Usa Bank, Na Cardless payment system
US6845498B1 (en) 1999-05-11 2005-01-18 Microsoft Corporation Method and apparatus for sharing data files among run time environment applets in an integrated circuit card
US6504945B1 (en) 1999-07-13 2003-01-07 Hewlett-Packard Company System for promoting correct finger placement in a fingerprint reader
US7908216B1 (en) 1999-07-22 2011-03-15 Visa International Service Association Internet payment, authentication and loading system using virtual smart card
US6324271B1 (en) 1999-08-17 2001-11-27 Nortel Networks Limited System and method for authentication of caller identification
SE515327C2 (sv) 1999-08-27 2001-07-16 Ericsson Telefon Ab L M Anordning för att utföra säkra transaktioner i en kommunikationsanordning
US7085931B1 (en) 1999-09-03 2006-08-01 Secure Computing Corporation Virtual smart card system and method
US6834271B1 (en) 1999-09-24 2004-12-21 Kryptosima Apparatus for and method of secure ATM debit card and credit card payment transactions via the internet
US7319986B2 (en) 1999-09-28 2008-01-15 Bank Of America Corporation Dynamic payment cards and related management systems and associated methods
US6910627B1 (en) 1999-09-29 2005-06-28 Canon Kabushiki Kaisha Smart card systems and electronic ticketing methods
JP2001195368A (ja) 1999-11-01 2001-07-19 Sony Corp 認証情報通信システムおよび認証情報通信方法、携帯情報処理装置、並びにプログラム提供媒体
US8814039B2 (en) 1999-11-05 2014-08-26 Lead Core Fund, L.L.C. Methods for processing a payment authorization request utilizing a network of point of sale devices
US8794509B2 (en) 1999-11-05 2014-08-05 Lead Core Fund, L.L.C. Systems and methods for processing a payment authorization request over disparate payment networks
AU1431301A (en) 1999-11-22 2001-06-04 Intel Corporation Integrity check values (icv) based on pseudorandom binary matrices
AU3086101A (en) 2000-01-05 2001-07-16 American Express Travel Related Services Company, Inc. Smartcard internet authorization system
EP1221131A1 (en) 2000-01-10 2002-07-10 Tarian, LLC Device using histological and physiological biometric marker for authentication and activation
US20010034702A1 (en) 2000-02-04 2001-10-25 Mockett Gregory P. System and method for dynamically issuing and processing transaction specific digital credit or debit cards
WO2001061659A1 (en) 2000-02-16 2001-08-23 Mastercard International Incorporated System and method for conducting electronic commerce with a remote wallet server
US20030034873A1 (en) 2000-02-16 2003-02-20 Robin Chase Systems and methods for controlling vehicle access
US6779115B1 (en) 2000-02-18 2004-08-17 Digital5, Inc. Portable device using a smart card to receive and decrypt digital data
US20010029485A1 (en) 2000-02-29 2001-10-11 E-Scoring, Inc. Systems and methods enabling anonymous credit transactions
US6852031B1 (en) 2000-11-22 2005-02-08 Igt EZ pay smart card and tickets system
CA2406001A1 (en) 2000-04-14 2001-10-25 American Express Travel Related Services Company, Inc. A system and method for using loyalty points
EP1277180A2 (en) 2000-04-24 2003-01-22 Visa International Service Association Online payer authentication service
US7933589B1 (en) 2000-07-13 2011-04-26 Aeritas, Llc Method and system for facilitation of wireless e-commerce transactions
US6631197B1 (en) 2000-07-24 2003-10-07 Gn Resound North America Corporation Wide audio bandwidth transduction method and device
WO2002015464A1 (en) 2000-08-14 2002-02-21 Gien Peter H System and method for secure smartcard issuance
AU2001284314A1 (en) 2000-08-17 2002-02-25 Dexrad (Proprietary) Limited The transfer of verification data
US7689832B2 (en) 2000-09-11 2010-03-30 Sentrycom Ltd. Biometric-based system and method for enabling authentication of electronic messages sent over a network
US7006986B1 (en) 2000-09-25 2006-02-28 Ecardless Bancorp, Ltd. Order file processes for purchasing on the internet using verified order information
US6873260B2 (en) 2000-09-29 2005-03-29 Kenneth J. Lancos System and method for selectively allowing the passage of a guest through a region within a coverage area
US6877656B1 (en) 2000-10-24 2005-04-12 Capital One Financial Corporation Systems, methods, and apparatus for instant issuance of a credit card
US6721706B1 (en) 2000-10-30 2004-04-13 Koninklijke Philips Electronics N.V. Environment-responsive user interface/entertainment device that simulates personal interaction
US7069435B2 (en) 2000-12-19 2006-06-27 Tricipher, Inc. System and method for authentication in a crypto-system utilizing symmetric and asymmetric crypto-keys
US7606771B2 (en) 2001-01-11 2009-10-20 Cardinalcommerce Corporation Dynamic number authentication for credit/debit cards
EP1223565A1 (en) 2001-01-12 2002-07-17 Motorola, Inc. Transaction system, portable device, terminal and methods of transaction
US20020093530A1 (en) 2001-01-17 2002-07-18 Prasad Krothapalli Automatic filling and submission of completed forms
US20020158123A1 (en) 2001-01-30 2002-10-31 Allen Rodney F. Web-based smart card system and method for maintaining status information and verifying eligibility
US20020152116A1 (en) 2001-01-30 2002-10-17 Yan Kent J. Method and system for generating fixed and/or dynamic rebates in credit card type transactions
US7181017B1 (en) 2001-03-23 2007-02-20 David Felsher System and method for secure three-party communications
DE60128785T2 (de) 2001-04-02 2008-01-31 Motorola, Inc., Schaumburg Aktivieren und Deaktivieren von Softwarefunktionen
US7290709B2 (en) 2001-04-10 2007-11-06 Erica Tsai Information card system
US7044394B2 (en) 2003-12-17 2006-05-16 Kerry Dennis Brown Programmable magnetic data storage card
US20020153424A1 (en) 2001-04-19 2002-10-24 Chuan Li Method and apparatus of secure credit card transaction
US20040015958A1 (en) 2001-05-15 2004-01-22 Veil Leonard Scott Method and system for conditional installation and execution of services in a secure computing environment
US7206806B2 (en) 2001-05-30 2007-04-17 Pineau Richard A Method and system for remote utilizing a mobile device to share data objects
DE10127511A1 (de) 2001-06-06 2003-01-02 Wincor Nixdorf Gmbh & Co Kg Schreib-/Lesegerät für eine Ausweis- oder Kreditkarte vom RFID-Typ
US20030167350A1 (en) 2001-06-07 2003-09-04 Curl Corporation Safe I/O through use of opaque I/O objects
AUPR559201A0 (en) 2001-06-08 2001-07-12 Canon Kabushiki Kaisha Card reading device for service access
US6834795B1 (en) 2001-06-29 2004-12-28 Sun Microsystems, Inc. Secure user authentication to computing resource via smart card
US7762457B2 (en) 2001-07-10 2010-07-27 American Express Travel Related Services Company, Inc. System and method for dynamic fob synchronization and personalization
US7993197B2 (en) 2001-08-10 2011-08-09 Igt Flexible loyalty points programs
US8266451B2 (en) 2001-08-31 2012-09-11 Gemalto Sa Voice activated smart card
US20030055727A1 (en) 2001-09-18 2003-03-20 Walker Jay S. Method and apparatus for facilitating the provision of a benefit to a customer of a retailer
US7373515B2 (en) 2001-10-09 2008-05-13 Wireless Key Identification Systems, Inc. Multi-factor authentication system
JP3975720B2 (ja) 2001-10-23 2007-09-12 株式会社日立製作所 Icカード、顧客情報分析システムおよび顧客情報分析結果提供方法
US6934861B2 (en) 2001-11-06 2005-08-23 Crosscheck Identification Systems International, Inc. National identification card system and biometric identity verification method for negotiating transactions
US6641050B2 (en) 2001-11-06 2003-11-04 International Business Machines Corporation Secure credit card
US7243853B1 (en) 2001-12-04 2007-07-17 Visa U.S.A. Inc. Method and system for facilitating memory and application management on a secured token
US8108687B2 (en) 2001-12-12 2012-01-31 Valve Corporation Method and system for granting access to system and content
FR2834403B1 (fr) 2001-12-27 2004-02-06 France Telecom Systeme cryptographique de signature de groupe
JP3820999B2 (ja) 2002-01-25 2006-09-13 ソニー株式会社 近接通信システム及び近接通信方法、データ管理装置及びデータ管理方法、記憶媒体、並びにコンピュータ・プログラム
SE524778C2 (sv) 2002-02-19 2004-10-05 Douglas Lundholm Förfarande och arrangemang för att skydda mjukvara för otillbörlig användning eller kopiering
US6905411B2 (en) 2002-02-27 2005-06-14 Igt Player authentication for cashless gaming machine instruments
US20030208449A1 (en) 2002-05-06 2003-11-06 Yuanan Diao Credit card fraud prevention system and method using secure electronic credit card
US7900048B2 (en) 2002-05-07 2011-03-01 Sony Ericsson Mobile Communications Ab Method for loading an application in a device, device and smart card therefor
CN100440195C (zh) 2002-05-10 2008-12-03 斯伦贝谢(北京)智能卡科技有限公司 智能卡更换方法及其更换系统
US8010405B1 (en) 2002-07-26 2011-08-30 Visa Usa Inc. Multi-application smart card device software solution for smart cardholder reward selection and redemption
US20040127256A1 (en) 2002-07-30 2004-07-01 Scott Goldthwaite Mobile device equipped with a contactless smart card reader/writer
EP3547599A1 (en) 2002-08-06 2019-10-02 Apple Inc. Methods for secure enrollment and backup of personal identity credentials into electronic devices
US7697920B1 (en) 2006-05-05 2010-04-13 Boojum Mobile System and method for providing authentication and authorization utilizing a personal wireless communication device
JP4553565B2 (ja) 2002-08-26 2010-09-29 パナソニック株式会社 電子バリューの認証方式と認証システムと装置
CZ2005209A3 (cs) 2002-09-10 2005-12-14 Ivi Smart Technologies, Inc. Bezpečné biometrické ověření identity
US7306143B2 (en) 2002-09-20 2007-12-11 Cubic Corporation Dynamic smart card/media imaging
US9710804B2 (en) 2012-10-07 2017-07-18 Andrew H B Zhou Virtual payment cards issued by banks for mobile and wearable devices
US8985442B1 (en) 2011-07-18 2015-03-24 Tiger T G Zhou One-touch payment using haptic control via a messaging and calling multimedia system on mobile device and wearable device, currency token interface, point of sale device, and electronic payment card
US20060006230A1 (en) 2002-10-16 2006-01-12 Alon Bear Smart card network interface device
US9740988B1 (en) 2002-12-09 2017-08-22 Live Nation Entertainment, Inc. System and method for using unique device indentifiers to enhance security
US9251518B2 (en) 2013-03-15 2016-02-02 Live Nation Entertainment, Inc. Centralized and device-aware ticket-transfer system and methods
US7454318B2 (en) 2003-01-14 2008-11-18 Nxp B.V. Method and terminal for detecting fake and/or modified smart card
US7453439B1 (en) 2003-01-16 2008-11-18 Forward Input Inc. System and method for continuous stroke word-based text input
US20050195975A1 (en) 2003-01-21 2005-09-08 Kevin Kawakita Digital media distribution cryptography using media ticket smart cards
US8589335B2 (en) 2003-04-21 2013-11-19 Visa International Service Association Smart card personalization assistance tool
WO2004102353A2 (en) 2003-05-12 2004-11-25 Gtech Rhode Island Corporation Method and system for authentication
US7949559B2 (en) 2003-05-27 2011-05-24 Citicorp Credit Services, Inc. Credit card rewards program system and method
US8200775B2 (en) 2005-02-01 2012-06-12 Newsilike Media Group, Inc Enhanced syndication
JP4744106B2 (ja) 2003-08-06 2011-08-10 パナソニック株式会社 セキュアデバイス、情報処理端末、通信システム及び通信方法
US20050075985A1 (en) 2003-10-03 2005-04-07 Brian Cartmell Voice authenticated credit card purchase verification
FI20031482L (fi) 2003-10-10 2005-04-11 Open Bit Oy Ltd Maksutapahtumatietojen prosessointi
US7597250B2 (en) 2003-11-17 2009-10-06 Dpd Patent Trust Ltd. RFID reader with multiple interfaces
US20050138387A1 (en) 2003-12-19 2005-06-23 Lam Wai T. System and method for authorizing software use
US7357309B2 (en) 2004-01-16 2008-04-15 Telefonaktiebolaget Lm Ericsson (Publ) EMV transactions in mobile terminals
US7374099B2 (en) 2004-02-24 2008-05-20 Sun Microsystems, Inc. Method and apparatus for processing an application identifier from a smart card
US7165727B2 (en) 2004-02-24 2007-01-23 Sun Microsystems, Inc. Method and apparatus for installing an application onto a smart card
US7584153B2 (en) 2004-03-15 2009-09-01 Qsecure, Inc. Financial transactions with dynamic card verification values
US7472829B2 (en) 2004-12-10 2009-01-06 Qsecure, Inc. Payment card with internally generated virtual account numbers for its magnetic stripe encoder and user display
EP1728219A1 (de) 2004-03-19 2006-12-06 Roger Marcel Humbel Alles-schlüssel bzw. einstell software liste in handy (pass-partout) für funk-fahrrad-schlüsser, autos, häuser, rfid-tags mit zulassungs- und zahlungsverkehrs-funktion all in one remote key
US20140019352A1 (en) 2011-02-22 2014-01-16 Visa International Service Association Multi-purpose virtual card transaction apparatuses, methods and systems
US7748617B2 (en) 2004-04-12 2010-07-06 Gray R O'neal Electronic identification system
CN100549985C (zh) 2004-05-03 2009-10-14 捷讯研究有限公司 用于应用认证的系统和方法
US8762283B2 (en) 2004-05-03 2014-06-24 Visa International Service Association Multiple party benefit from an online authentication service
US7703142B1 (en) 2004-05-06 2010-04-20 Sprint Communications Company L.P. Software license authorization system
US7660779B2 (en) 2004-05-12 2010-02-09 Microsoft Corporation Intelligent autofill
GB0411777D0 (en) 2004-05-26 2004-06-30 Crypomathic Ltd Computationally asymmetric cryptographic systems
US7314165B2 (en) 2004-07-01 2008-01-01 American Express Travel Related Services Company, Inc. Method and system for smellprint recognition biometrics on a smartcard
US7175076B1 (en) 2004-07-07 2007-02-13 Diebold Self-Service Systems Division Of Diebold, Incorporated Cash dispensing automated banking machine user interface system and method
WO2006020072A2 (en) 2004-07-15 2006-02-23 Mastercard International Incorporated Payment card signal characterization methods and circuits
US8439271B2 (en) 2004-07-15 2013-05-14 Mastercard International Incorporated Method and system using a bitmap for passing contactless payment card transaction variables in standardized data formats
US7287692B1 (en) 2004-07-28 2007-10-30 Cisco Technology, Inc. System and method for securing transactions in a contact center environment
EP1630712A1 (en) 2004-08-24 2006-03-01 Sony Deutschland GmbH Method for operating a near field communication system
EP1783919B1 (en) 2004-08-27 2017-12-20 Victorion Technology Co., Ltd. The nasal bone conduction wireless communication transmission equipment
US20060047954A1 (en) 2004-08-30 2006-03-02 Axalto Inc. Data access security implementation using the public key mechanism
US7375616B2 (en) 2004-09-08 2008-05-20 Nokia Corporation Electronic near field communication enabled multifunctional device and method of its operation
US7270276B2 (en) 2004-09-29 2007-09-18 Sap Ag Multi-application smartcard
US20060085848A1 (en) 2004-10-19 2006-04-20 Intel Corporation Method and apparatus for securing communications between a smartcard and a terminal
US7748636B2 (en) 2004-11-16 2010-07-06 Dpd Patent Trust Ltd. Portable identity card reader system for physical and logical access
GB2410113A (en) 2004-11-29 2005-07-20 Morse Group Ltd A system and method of accessing banking services via a mobile telephone
TW200642408A (en) 2004-12-07 2006-12-01 Farsheed Atef System and method for identity verification and management
US7232073B1 (en) 2004-12-21 2007-06-19 Sun Microsystems, Inc. Smart card with multiple applications
GB0428543D0 (en) 2004-12-31 2005-02-09 British Telecomm Control of data exchange
US8347088B2 (en) 2005-02-01 2013-01-01 Newsilike Media Group, Inc Security systems and methods for use with structured and unstructured data
US8200700B2 (en) 2005-02-01 2012-06-12 Newsilike Media Group, Inc Systems and methods for use of structured and unstructured distributed data
US20130104251A1 (en) 2005-02-01 2013-04-25 Newsilike Media Group, Inc. Security systems and methods for use with structured and unstructured data
DE102005004902A1 (de) 2005-02-02 2006-08-10 Utimaco Safeware Ag Verfahren zur Anmeldung eines Nutzers an einem Computersystem
US7581678B2 (en) 2005-02-22 2009-09-01 Tyfone, Inc. Electronic transaction card
EP1856903B1 (en) 2005-03-07 2018-01-24 Nokia Technologies Oy Method and mobile terminal device including smartcard module and near field communications means
US7628322B2 (en) 2005-03-07 2009-12-08 Nokia Corporation Methods, system and mobile device capable of enabling credit card personalization using a wireless network
US7128274B2 (en) 2005-03-24 2006-10-31 International Business Machines Corporation Secure credit card with near field communications
US8266441B2 (en) 2005-04-22 2012-09-11 Bank Of America Corporation One-time password credit/debit card
WO2006119184A2 (en) 2005-05-04 2006-11-09 Tricipher, Inc. Protecting one-time-passwords against man-in-the-middle attacks
US20080035738A1 (en) 2005-05-09 2008-02-14 Mullen Jeffrey D Dynamic credit card with magnetic stripe and embedded encoder and methods for using the same to provide a copy-proof credit card
US7793851B2 (en) 2005-05-09 2010-09-14 Dynamics Inc. Dynamic credit card with magnetic stripe and embedded encoder and methods for using the same to provide a copy-proof credit card
WO2006124808A2 (en) 2005-05-16 2006-11-23 Mastercard International Incorporated Method and system for using contactless payment cards in a transit system
US20060280338A1 (en) 2005-06-08 2006-12-14 Xerox Corporation Systems and methods for the visually impared
US8583454B2 (en) 2005-07-28 2013-11-12 Beraja Ip, Llc Medical claims fraud prevention system including photograph records identification and associated methods
US8762263B2 (en) 2005-09-06 2014-06-24 Visa U.S.A. Inc. System and method for secured account numbers in proximity devices
US20070067833A1 (en) 2005-09-20 2007-03-22 Colnot Vincent C Methods and Apparatus for Enabling Secure Network-Based Transactions
EP2667344A3 (en) 2005-10-06 2014-08-27 C-Sam, Inc. Transactional services
US8245292B2 (en) 2005-11-16 2012-08-14 Broadcom Corporation Multi-factor authentication using a smartcard
JP4435076B2 (ja) 2005-11-18 2010-03-17 フェリカネットワークス株式会社 携帯端末,データ通信方法,およびコンピュータプログラム
US7568631B2 (en) 2005-11-21 2009-08-04 Sony Corporation System, apparatus and method for obtaining one-time credit card numbers using a smart card
US8511547B2 (en) 2005-12-22 2013-08-20 Mastercard International Incorporated Methods and systems for two-factor authentication using contactless chip cards or devices and mobile devices or dedicated personal readers
FR2895608B1 (fr) 2005-12-23 2008-03-21 Trusted Logic Sa Procede pour la realisation d'un compteur securise sur un systeme informatique embarque disposant d'une carte a puce
US8559987B1 (en) 2005-12-31 2013-10-15 Blaze Mobile, Inc. Wireless bidirectional communications between a mobile device and associated secure element
US8352323B2 (en) 2007-11-30 2013-01-08 Blaze Mobile, Inc. Conducting an online payment transaction using an NFC enabled mobile communication device
US7775427B2 (en) 2005-12-31 2010-08-17 Broadcom Corporation System and method for binding a smartcard and a smartcard reader
US8224018B2 (en) 2006-01-23 2012-07-17 Digimarc Corporation Sensing data from physical objects
US9137012B2 (en) 2006-02-03 2015-09-15 Emc Corporation Wireless authentication methods and apparatus
US20070224969A1 (en) 2006-03-24 2007-09-27 Rao Bindu R Prepaid simcard for automatically enabling services
US7380710B2 (en) 2006-04-28 2008-06-03 Qsecure, Inc. Payment card preloaded with unique numbers
US7571471B2 (en) 2006-05-05 2009-08-04 Tricipher, Inc. Secure login using a multifactor split asymmetric crypto-key with persistent key security
DE602007008313D1 (de) 2006-05-10 2010-09-23 Inside Contactless Verfahren zur Weiterleitung von aus- und eingehenden Daten in ein NFC-Chipset
ATE440417T1 (de) 2006-06-29 2009-09-15 Incard Sa Verfahren zur diversifizierung eines schlüssels auf einer chipkarte
US9985950B2 (en) 2006-08-09 2018-05-29 Assa Abloy Ab Method and apparatus for making a decision on a card
GB0616331D0 (en) 2006-08-16 2006-09-27 Innovision Res & Tech Plc Near Field RF Communicators And Near Field Communications Enabled Devices
US20080072303A1 (en) 2006-09-14 2008-03-20 Schlumberger Technology Corporation Method and system for one time password based authentication and integrated remote access
US20080071681A1 (en) 2006-09-15 2008-03-20 Khalid Atm Shafiqul Dynamic Credit and Check Card
US8322624B2 (en) 2007-04-10 2012-12-04 Feinics Amatech Teoranta Smart card with switchable matching antenna
US8738485B2 (en) 2007-12-28 2014-05-27 Visa U.S.A. Inc. Contactless prepaid product for transit fare collection
WO2008042302A2 (en) 2006-09-29 2008-04-10 Narian Technologies Corp. Apparatus and method using near field communications
US8474028B2 (en) 2006-10-06 2013-06-25 Fmr Llc Multi-party, secure multi-channel authentication
GB2443234B8 (en) 2006-10-24 2009-01-28 Innovision Res & Tech Plc Near field RF communicators and near field RF communications enabled devices
US20080109309A1 (en) 2006-10-31 2008-05-08 Steven Landau Powered Print Advertisements, Product Packaging, and Trading Cards
US8682791B2 (en) 2006-10-31 2014-03-25 Discover Financial Services Redemption of credit card rewards at a point of sale
US8267313B2 (en) 2006-10-31 2012-09-18 American Express Travel Related Services Company, Inc. System and method for providing a gift card which affords benefits beyond what is purchased
US9251637B2 (en) 2006-11-15 2016-02-02 Bank Of America Corporation Method and apparatus for using at least a portion of a one-time password as a dynamic card verification value
US8365258B2 (en) 2006-11-16 2013-01-29 Phonefactor, Inc. Multi factor authentication
CN101192295A (zh) 2006-11-30 2008-06-04 讯想科技股份有限公司 芯片信用卡网络交易系统与方法
US8041954B2 (en) 2006-12-07 2011-10-18 Paul Plesman Method and system for providing a secure login solution using one-time passwords
US20080162312A1 (en) 2006-12-29 2008-07-03 Motorola, Inc. Method and system for monitoring secure applet events during contactless rfid/nfc communication
US7594605B2 (en) 2007-01-10 2009-09-29 At&T Intellectual Property I, L.P. Credit card transaction servers, methods and computer program products employing wireless terminal location and registered purchasing locations
GB2442249B (en) 2007-02-20 2008-09-10 Cryptomathic As Authentication device and method
US8095974B2 (en) 2007-02-23 2012-01-10 At&T Intellectual Property I, L.P. Methods, systems, and products for identity verification
US8463711B2 (en) 2007-02-27 2013-06-11 Igt Methods and architecture for cashless system security
US9081948B2 (en) 2007-03-13 2015-07-14 Red Hat, Inc. Configurable smartcard
US20080223918A1 (en) 2007-03-15 2008-09-18 Microsoft Corporation Payment tokens
WO2008114931A1 (en) 2007-03-16 2008-09-25 Lg Electronics Inc. Performing contactless applications in battery off mode
US8285329B1 (en) 2007-04-02 2012-10-09 Sprint Communications Company L.P. Mobile device-based control of smart card operation
US8667285B2 (en) 2007-05-31 2014-03-04 Vasco Data Security, Inc. Remote authentication and transaction signatures
US7739169B2 (en) 2007-06-25 2010-06-15 Visa U.S.A. Inc. Restricting access to compromised account information
US20120252350A1 (en) 2007-07-24 2012-10-04 Allan Steinmetz Vehicle safety device for reducing driver distractions
US20090037275A1 (en) 2007-08-03 2009-02-05 Pollio Michael J Consolidated membership/rewards card system
US8235825B2 (en) 2007-08-14 2012-08-07 John B. French Smart card holder for automated gaming system and gaming cards
US20110101093A1 (en) 2007-08-19 2011-05-05 Yubico Ab Device and method for generating dynamic credit card data
US7748609B2 (en) 2007-08-31 2010-07-06 Gemalto Inc. System and method for browser based access to smart cards
EP2201543A1 (en) 2007-09-21 2010-06-30 Wireless Dynamics, Inc. Wireless smart card and integrated personal area network, near field communication and contactless payment system
US8249654B1 (en) 2007-09-27 2012-08-21 Sprint Communications Company L.P. Dynamic smart card application loading
US8095113B2 (en) 2007-10-17 2012-01-10 First Data Corporation Onetime passwords for smart chip cards
GB2457221A (en) 2007-10-17 2009-08-12 Vodafone Plc Smart Card Web Server (SCWS) administration within a plurality of security domains
FR2922701B1 (fr) 2007-10-23 2009-11-20 Inside Contacless Procede de personnalisation securise d'un chipset nfc
US7652578B2 (en) 2007-10-29 2010-01-26 Motorola, Inc. Detection apparatus and method for near field communication devices
US8135648B2 (en) 2007-11-01 2012-03-13 Gtech Corporation Authentication of lottery tickets, game machine credit vouchers, and other items
US20090132417A1 (en) 2007-11-15 2009-05-21 Ebay Inc. System and method for selecting secure card numbers
US20090159703A1 (en) 2007-12-24 2009-06-25 Dynamics Inc. Credit, security, debit cards and the like with buttons
US7922082B2 (en) 2008-01-04 2011-04-12 M2 International Ltd. Dynamic card validation value
GB0801225D0 (en) 2008-01-23 2008-02-27 Innovision Res & Tech Plc Near field RF communications
US20090192912A1 (en) 2008-01-30 2009-07-30 Kent Griffin Charge-for-service near field communication transactions
WO2009102640A1 (en) 2008-02-12 2009-08-20 Cardiac Pacemakers, Inc. Systems and methods for controlling wireless signal transfers between ultrasound-enabled medical devices
US9947002B2 (en) 2008-02-15 2018-04-17 First Data Corporation Secure authorization of contactless transaction
US8302167B2 (en) 2008-03-11 2012-10-30 Vasco Data Security, Inc. Strong authentication token generating one-time passwords and signatures upon server credential verification
ATE554593T1 (de) 2008-03-27 2012-05-15 Motorola Mobility Inc Verfahren und vorrichtung für die automatische nahfeld-kommunikations-anwendungsauswahl in einem elektronischen gerät
ITMI20080536A1 (it) 2008-03-28 2009-09-29 Incard Sa Metodo per proteggere un file cap per una carta a circuito integrato.
US8024576B2 (en) 2008-03-31 2011-09-20 International Business Machines Corporation Method and system for authenticating users with a one time password using an image reader
US8365988B1 (en) 2008-04-11 2013-02-05 United Services Automobile Association (Usaa) Dynamic credit card security code via mobile device
US8347112B2 (en) 2008-05-08 2013-01-01 Texas Instruments Incorporated Encryption/decryption engine with secure modes for key decryption and key derivation
US9082117B2 (en) 2008-05-17 2015-07-14 David H. Chin Gesture based authentication for wireless payment by a mobile electronic device
US8099332B2 (en) 2008-06-06 2012-01-17 Apple Inc. User interface for application management for a mobile device
EP2139196A1 (en) 2008-06-26 2009-12-30 France Telecom Method and system for remotely blocking/unblocking NFC applications on a terminal
US8229853B2 (en) 2008-07-24 2012-07-24 International Business Machines Corporation Dynamic itinerary-driven profiling for preventing unauthorized card transactions
US8662401B2 (en) 2008-07-25 2014-03-04 First Data Corporation Mobile payment adoption by adding a dedicated payment button to mobile device form factors
US8740073B2 (en) 2008-08-01 2014-06-03 Mastercard International Incorporated Methods, systems and computer readable media for storing and redeeming electronic certificates using a wireless smart card
US8706622B2 (en) 2008-08-05 2014-04-22 Visa U.S.A. Inc. Account holder demand account update
US8438382B2 (en) 2008-08-06 2013-05-07 Symantec Corporation Credential management system and method
EP2321809B1 (en) 2008-08-08 2013-10-02 Assa Abloy Ab Directional sensing mechanism and communications authentication
US20100033310A1 (en) 2008-08-08 2010-02-11 Narendra Siva G Power negotation for small rfid card
CN102160061B (zh) 2008-08-20 2014-04-09 X卡控股有限公司 安全智能卡系统
US8103249B2 (en) 2008-08-23 2012-01-24 Visa U.S.A. Inc. Credit card imaging for mobile payment and other applications
US10970777B2 (en) 2008-09-15 2021-04-06 Mastercard International Incorporated Apparatus and method for bill payment card enrollment
US20100078471A1 (en) 2008-09-30 2010-04-01 Apple Inc. System and method for processing peer-to-peer financial transactions
US9037513B2 (en) 2008-09-30 2015-05-19 Apple Inc. System and method for providing electronic event tickets
US20100095130A1 (en) 2008-10-13 2010-04-15 Global Financial Passport, Llc Smartcards for secure transaction systems
US20100094754A1 (en) 2008-10-13 2010-04-15 Global Financial Passport, Llc Smartcard based secure transaction systems and methods
US8689013B2 (en) 2008-10-21 2014-04-01 G. Wouter Habraken Dual-interface key management
CN101729502B (zh) 2008-10-23 2012-09-05 中兴通讯股份有限公司 密钥分发方法和系统
US8371501B1 (en) 2008-10-27 2013-02-12 United Services Automobile Association (Usaa) Systems and methods for a wearable user authentication factor
EP2182439A1 (en) 2008-10-28 2010-05-05 Gemalto SA Method of managing data sent over the air to an applet having a restricted interface
US20100114731A1 (en) 2008-10-30 2010-05-06 Kingston Tamara S ELECTRONIC WALLET ("eWallet")
WO2010069033A1 (en) 2008-12-18 2010-06-24 Bce Inc Validation method and system for use in securing nomadic electronic transactions
EP2199992A1 (en) 2008-12-19 2010-06-23 Gemalto SA Secure activation before contactless banking smart card transaction
US10354321B2 (en) 2009-01-22 2019-07-16 First Data Corporation Processing transactions with an extended application ID and dynamic cryptograms
US9065812B2 (en) 2009-01-23 2015-06-23 Microsoft Technology Licensing, Llc Protecting transactions
EP2852070B1 (en) 2009-01-26 2019-01-23 Google Technology Holdings LLC Wireless communication device for providing at least one near field communication service
US9509436B2 (en) 2009-01-29 2016-11-29 Cubic Corporation Protection of near-field communication exchanges
EP2219374A1 (en) 2009-02-13 2010-08-18 Irdeto Access B.V. Securely providing a control word from a smartcard to a conditional access module
CN101820696B (zh) 2009-02-26 2013-08-07 中兴通讯股份有限公司 支持增强型近场通信的终端及其处理方法
US20100240413A1 (en) 2009-03-21 2010-09-23 Microsoft Corporation Smart Card File System
CA2697921C (en) 2009-03-27 2019-09-24 Intersections Inc. Dynamic card verification values and credit transactions
JP5262941B2 (ja) 2009-04-10 2013-08-14 ソニー株式会社 認証装置、認証方法、及びプログラム
EP2199965A1 (en) 2009-04-22 2010-06-23 Euro-Wallet B.V. Payment transaction client, server and system
US8893967B2 (en) 2009-05-15 2014-11-25 Visa International Service Association Secure Communication of payment information to merchants using a verification token
US8417231B2 (en) 2009-05-17 2013-04-09 Qualcomm Incorporated Method and apparatus for programming a mobile device with multiple service accounts
US8391719B2 (en) 2009-05-22 2013-03-05 Motorola Mobility Llc Method and system for conducting communication between mobile devices
US20100312634A1 (en) 2009-06-08 2010-12-09 Cervenka Karen L Coupon card point of service terminal processing
US20100312635A1 (en) 2009-06-08 2010-12-09 Cervenka Karen L Free sample coupon card
US9886696B2 (en) 2009-07-29 2018-02-06 Shopkick, Inc. Method and system for presence detection
US8186602B2 (en) 2009-08-18 2012-05-29 On Track Innovations, Ltd. Multi-application contactless smart card
US20110060631A1 (en) 2009-09-04 2011-03-10 Bank Of America Redemption of customer benefit offers based on goods identification
US9251538B1 (en) 2009-09-23 2016-02-02 Verient Inc System and method for automatically filling webpage fields
US8317094B2 (en) 2009-09-23 2012-11-27 Mastercard International Incorporated Methods and systems for displaying loyalty program information on a payment card
US8830866B2 (en) 2009-09-30 2014-09-09 Apple Inc. Methods and apparatus for solicited activation for protected wireless networking
US20110084132A1 (en) 2009-10-08 2011-04-14 At&T Intellectual Property I, L.P. Devices, Systems and Methods for Secure Remote Medical Diagnostics
EP2487876A4 (en) 2009-10-09 2014-04-02 Panasonic Corp VEHICLE-ASSEMBLED DEVICE
US8806592B2 (en) 2011-01-21 2014-08-12 Authentify, Inc. Method for secure user and transaction authentication and risk management
US8843757B2 (en) 2009-11-12 2014-09-23 Ca, Inc. One time PIN generation
US8799668B2 (en) 2009-11-23 2014-08-05 Fred Cheng Rubbing encryption algorithm and security attack safe OTP token
US9225526B2 (en) 2009-11-30 2015-12-29 Red Hat, Inc. Multifactor username based authentication
US9258715B2 (en) 2009-12-14 2016-02-09 Apple Inc. Proactive security for mobile devices
EP2336986A1 (en) 2009-12-17 2011-06-22 Gemalto SA Method of personalizing an application embedded in a secured electronic token
US10049356B2 (en) 2009-12-18 2018-08-14 First Data Corporation Authentication of card-not-present transactions
US9324066B2 (en) 2009-12-21 2016-04-26 Verizon Patent And Licensing Inc. Method and system for providing virtual credit card services
US8615468B2 (en) 2010-01-27 2013-12-24 Ca, Inc. System and method for generating a dynamic card value
CA2694500C (en) 2010-02-24 2015-07-07 Diversinet Corp. Method and system for secure communication
US8433914B1 (en) 2010-02-25 2013-04-30 Emc Corporation Multi-channel transaction signing
US10255601B2 (en) 2010-02-25 2019-04-09 Visa International Service Association Multifactor authentication using a directory server
US9317018B2 (en) 2010-03-02 2016-04-19 Gonow Technologies, Llc Portable e-wallet and universal card
US9129270B2 (en) 2010-03-02 2015-09-08 Gonow Technologies, Llc Portable E-wallet and universal card
SI23227A (sl) 2010-03-10 2011-05-31 Margento R&D D.O.O. Brezžični mobilni transakcijski sistem in postopek izvedbe transakcije z mobilnim telefonom
WO2011119976A2 (en) 2010-03-26 2011-09-29 Visa International Service Association System and method for early detection of fraudulent transactions
WO2011127084A2 (en) 2010-04-05 2011-10-13 Vivotech, Inc. Systems, methods, and computer readable media for performing multiple transactions through a single near field communication (nfc) tap
US10304051B2 (en) 2010-04-09 2019-05-28 Paypal, Inc. NFC mobile wallet processing systems and methods
US20120109735A1 (en) 2010-05-14 2012-05-03 Mark Stanley Krawczewicz Mobile Payment System with Thin Film Display
US9122964B2 (en) 2010-05-14 2015-09-01 Mark Krawczewicz Batteryless stored value card with display
US9047531B2 (en) 2010-05-21 2015-06-02 Hand Held Products, Inc. Interactive user interface for capturing a document in an image signal
TWI504229B (zh) 2010-05-27 2015-10-11 Mstar Semiconductor Inc 支援電子錢包功能之行動裝置
WO2011153505A1 (en) 2010-06-04 2011-12-08 Visa International Service Association Payment tokenization apparatuses, methods and systems
WO2012000091A1 (en) 2010-06-28 2012-01-05 Lionstone Capital Corporation Systems and methods for diversification of encryption algorithms and obfuscation symbols, symbol spaces and/or schemas
US8723941B1 (en) 2010-06-29 2014-05-13 Bank Of America Corporation Handicap-accessible ATM
WO2012001624A1 (en) 2010-07-01 2012-01-05 Ishai Binenstock Location-aware mobile connectivity and information exchange system
US8500031B2 (en) 2010-07-29 2013-08-06 Bank Of America Corporation Wearable article having point of sale payment functionality
US9916572B2 (en) 2010-08-18 2018-03-13 International Business Machines Corporation Payment card processing system
US8312519B1 (en) 2010-09-30 2012-11-13 Daniel V Bailey Agile OTP generation
US8799087B2 (en) 2010-10-27 2014-08-05 Mastercard International Incorporated Systems, methods, and computer readable media for utilizing one or more preferred application lists in a wireless device reader
US9965756B2 (en) 2013-02-26 2018-05-08 Digimarc Corporation Methods and arrangements for smartphone payments
CN102467789A (zh) 2010-11-18 2012-05-23 卓望数码技术(深圳)有限公司 一种零售点转账作业系统及交易数据加密传输方法
WO2012071078A1 (en) 2010-11-23 2012-05-31 X-Card Holdings, Llc One-time password card for secure transactions
US20120143754A1 (en) 2010-12-03 2012-06-07 Narendra Patel Enhanced credit card security apparatus and method
US8807440B1 (en) 2010-12-17 2014-08-19 Google Inc. Routing secure element payment requests to an alternate application
US8726405B1 (en) 2010-12-23 2014-05-13 Emc Corporation Techniques for providing security using a mobile wireless communications device having data loss prevention circuitry
US8977195B2 (en) 2011-01-06 2015-03-10 Texas Insruments Incorporated Multiple NFC card applications in multiple execution environments
US8475367B1 (en) 2011-01-09 2013-07-02 Fitbit, Inc. Biometric monitoring device having a body weight sensor, and methods of operating same
WO2012097310A1 (en) 2011-01-14 2012-07-19 Visa International Service Association Healthcare prepaid payment platform apparatuses, methods and systems
JP5692244B2 (ja) 2011-01-31 2015-04-01 富士通株式会社 通信方法、ノード、およびネットワークシステム
EP2487629B1 (en) 2011-02-10 2016-11-30 Nxp B.V. Secure smart poster
US10373160B2 (en) 2011-02-10 2019-08-06 Paypal, Inc. Fraud alerting using mobile phone location
US20130030828A1 (en) 2011-03-04 2013-01-31 Pourfallah Stacy S Healthcare incentive apparatuses, methods and systems
US20120238206A1 (en) 2011-03-14 2012-09-20 Research In Motion Limited Communications device providing near field communication (nfc) secure element disabling features related methods
WO2012125655A1 (en) 2011-03-14 2012-09-20 Conner Investments, Llc Bluetooth enabled credit card with a large date storage volume
CN102170354B (zh) 2011-04-11 2016-07-06 桂林电子科技大学 集中账号密码认证生成系统
US20120284194A1 (en) 2011-05-03 2012-11-08 Microsoft Corporation Secure card-based transactions using mobile phones or other mobile devices
EP3869443A1 (en) 2011-05-10 2021-08-25 Dynamics Inc. Systems, devices, and methods for mobile payment acceptance, mobile authorizations, mobile wallets, and contactless communication mechanisms
US20120296818A1 (en) 2011-05-17 2012-11-22 Ebay Inc. Method for authorizing the activation of a spending card
US8868902B1 (en) 2013-07-01 2014-10-21 Cryptite LLC Characteristically shaped colorgram tokens in mobile transactions
EP2718886A4 (en) 2011-06-07 2015-01-14 Visa Int Service Ass APPARATUSES, METHODS AND SYSTEMS FOR SEGMENTATION IN PAYMENT CONFIDENTIALITY UNITS
US20120317628A1 (en) 2011-06-09 2012-12-13 Yeager C Douglas Systems and methods for authorizing a transaction
US9042814B2 (en) 2011-06-27 2015-05-26 Broadcom Corporation Measurement and reporting of received signal strength in NFC-enabled devices
EP2541458B1 (en) 2011-06-27 2017-10-04 Nxp B.V. Resource management system and corresponding method
US9209867B2 (en) 2011-06-28 2015-12-08 Broadcom Corporation Device for authenticating wanted NFC interactions
US8620218B2 (en) 2011-06-29 2013-12-31 Broadcom Corporation Power harvesting and use in a near field communications (NFC) device
US9026047B2 (en) 2011-06-29 2015-05-05 Broadcom Corporation Systems and methods for providing NFC secure application support in battery-off mode when no nonvolatile memory write access is available
US9390411B2 (en) 2011-07-27 2016-07-12 Murray Jarman System or method for storing credit on a value card or cellular phone rather than accepting coin change
US9075979B1 (en) 2011-08-11 2015-07-07 Google Inc. Authentication based on proximity to mobile device
CN102956068B (zh) 2011-08-25 2017-02-15 富泰华工业(深圳)有限公司 自动柜员机及其语音提示方法
US10032171B2 (en) 2011-08-30 2018-07-24 Simplytapp, Inc. Systems and methods for secure application-based participation in an interrogation by mobile device
FR2980055B1 (fr) 2011-09-12 2013-12-27 Valeo Systemes Thermiques Dispositif de transmission de puissance inductif
GB201115896D0 (en) 2011-09-14 2011-10-26 Ec Solution Group B V Battery-less active matrix display smart card with graphical user interface
US10032036B2 (en) 2011-09-14 2018-07-24 Shahab Khan Systems and methods of multidimensional encrypted data transfer
US8977569B2 (en) 2011-09-29 2015-03-10 Raj Rao System and method for providing smart electronic wallet and reconfigurable transaction card thereof
US8577810B1 (en) 2011-09-29 2013-11-05 Intuit Inc. Secure mobile payment authorization
US9152832B2 (en) 2011-09-30 2015-10-06 Broadcom Corporation Positioning guidance for increasing reliability of near-field communications
US20140279479A1 (en) 2011-10-12 2014-09-18 C-Sam, Inc. Nfc paired bluetooth e-commerce
US10332102B2 (en) 2011-10-17 2019-06-25 Capital One Services, Llc System, method, and apparatus for a dynamic transaction card
US9978058B2 (en) 2011-10-17 2018-05-22 Capital One Services, Llc System, method, and apparatus for a dynamic transaction card
US9318257B2 (en) 2011-10-18 2016-04-19 Witricity Corporation Wireless energy transfer for packaging
US9246903B2 (en) 2011-10-31 2016-01-26 Money And Data Protection Lizenz Gmbh & Co. Kg Authentication method
US9000892B2 (en) 2011-10-31 2015-04-07 Eastman Kodak Company Detecting RFID tag and inhibiting skimming
CN104040555B (zh) 2011-11-14 2017-02-22 威斯科数据安全国际有限公司 具有安全记录特征的智能卡读取器
US8818867B2 (en) 2011-11-14 2014-08-26 At&T Intellectual Property I, L.P. Security token for mobile near field communication transactions
US9064253B2 (en) 2011-12-01 2015-06-23 Broadcom Corporation Systems and methods for providing NFC secure application support in battery on and battery off modes
US20140040139A1 (en) 2011-12-19 2014-02-06 Sequent Software, Inc. System and method for dynamic temporary payment authorization in a portable communication device
US9740342B2 (en) 2011-12-23 2017-08-22 Cirque Corporation Method for preventing interference of contactless card reader and touch functions when they are physically and logically bound together for improved authentication security
US9154903B2 (en) 2011-12-28 2015-10-06 Blackberry Limited Mobile communications device providing near field communication (NFC) card issuance features and related methods
US8880027B1 (en) 2011-12-29 2014-11-04 Emc Corporation Authenticating to a computing device with a near-field communications card
US20130179351A1 (en) 2012-01-09 2013-07-11 George Wallner System and method for an authenticating and encrypting card reader
US20130185772A1 (en) 2012-01-12 2013-07-18 Aventura Hq, Inc. Dynamically updating a session based on location data from an authentication device
US20130191279A1 (en) 2012-01-20 2013-07-25 Bank Of America Corporation Mobile device with rewritable general purpose card
US9218624B2 (en) 2012-02-03 2015-12-22 Paypal, Inc. Adding card to mobile/cloud wallet using NFC
KR101443960B1 (ko) 2012-02-22 2014-11-03 주식회사 팬택 사용자 인증 전자 장치 및 방법
US9020858B2 (en) 2012-02-29 2015-04-28 Google Inc. Presence-of-card code for offline payment processing system
US8898088B2 (en) 2012-02-29 2014-11-25 Google Inc. In-card access control and monotonic counters for offline payment processing system
US20130232082A1 (en) 2012-03-05 2013-09-05 Mark Stanley Krawczewicz Method And Apparatus For Secure Medical ID Card
EP3012981B1 (en) 2012-03-15 2019-11-13 Intel Corporation Near field communication (nfc) and proximity sensor for portable devices
AU2013248935A1 (en) 2012-04-17 2014-08-28 Secure Nfc Pty. Ltd. NFC card lock
US20130282360A1 (en) 2012-04-20 2013-10-24 James A. Shimota Method and Apparatus for Translating and Locating Services in Multiple Languages
US9953310B2 (en) 2012-05-10 2018-04-24 Mastercard International Incorporated Systems and method for providing multiple virtual secure elements in a single physical secure element of a mobile device
US20130303085A1 (en) 2012-05-11 2013-11-14 Research In Motion Limited Near field communication tag data management
US9306626B2 (en) 2012-05-16 2016-04-05 Broadcom Corporation NFC device context determination through proximity gestural movement detection
US8681268B2 (en) 2012-05-24 2014-03-25 Abisee, Inc. Vision assistive devices and user interfaces
US8862113B2 (en) 2012-06-20 2014-10-14 Qualcomm Incorporated Subscriber identity module activation during active data call
US9589399B2 (en) 2012-07-02 2017-03-07 Synaptics Incorporated Credential quality assessment engine systems and methods
US20140032410A1 (en) 2012-07-24 2014-01-30 Ipay International, S.A. Method and system for linking and controling of payment cards with a mobile
KR101421568B1 (ko) 2012-07-27 2014-07-22 주식회사 케이티 스마트카드, 스마트카드 서비스 단말 및 스마트카드 서비스 방법
US9530130B2 (en) 2012-07-30 2016-12-27 Mastercard International Incorporated Systems and methods for correction of information in card-not-present account-on-file transactions
KR101934293B1 (ko) 2012-08-03 2019-01-02 엘지전자 주식회사 이동 단말기의 이동 단말기 및 그의 nfc결제 방법
US9361619B2 (en) 2012-08-06 2016-06-07 Ca, Inc. Secure and convenient mobile authentication techniques
EP2698756B1 (en) 2012-08-13 2016-01-06 Nxp B.V. Local Trusted Service Manager
US9332587B2 (en) 2012-08-21 2016-05-03 Blackberry Limited Smart proximity priority pairing
US20140074655A1 (en) 2012-09-07 2014-03-13 David Lim System, apparatus and methods for online one-tap account addition and checkout
US10192216B2 (en) 2012-09-11 2019-01-29 Visa International Service Association Cloud-based virtual wallet NFC apparatuses, methods and systems
US9426132B1 (en) 2012-09-12 2016-08-23 Emc Corporation Methods and apparatus for rules-based multi-factor verification
US8888002B2 (en) 2012-09-18 2014-11-18 Sensormatic Electronics, LLC Access control reader enabling remote applications
US20140081720A1 (en) 2012-09-19 2014-03-20 Mastercard International Incorporated Method and system for processing coupons in a near field transaction
US9338622B2 (en) 2012-10-04 2016-05-10 Bernt Erik Bjontegard Contextually intelligent communication systems and processes
US9665858B1 (en) 2012-10-11 2017-05-30 Square, Inc. Cardless payment transactions with multiple users
US10075437B1 (en) 2012-11-06 2018-09-11 Behaviosec Secure authentication of a user of a device during a session with a connected server
US8584219B1 (en) 2012-11-07 2013-11-12 Fmr Llc Risk adjusted, multifactor authentication
CA2930752A1 (en) 2012-11-15 2014-05-22 Behzad Malek System and method for location-based financial transaction authentication
CN104471969B (zh) 2012-11-19 2019-07-30 艾利丹尼森公司 禁用未经授权的nfc安全系统和方法
US9038894B2 (en) 2012-11-20 2015-05-26 Cellco Partnership Payment or other transaction through mobile device using NFC to access a contactless transaction card
CN103023643A (zh) 2012-11-22 2013-04-03 天地融科技股份有限公司 一种动态口令牌及动态口令生成方法
US9224013B2 (en) 2012-12-05 2015-12-29 Broadcom Corporation Secure processing sub-system that is hardware isolated from a peripheral processing sub-system
US9064259B2 (en) 2012-12-19 2015-06-23 Genesys Telecomminucations Laboratories, Inc. Customer care mobile application
US10147086B2 (en) 2012-12-19 2018-12-04 Nxp B.V. Digital wallet device for virtual wallet
WO2014102721A1 (en) 2012-12-24 2014-07-03 Cell Buddy Network Ltd. User authentication system
US9015482B2 (en) 2012-12-28 2015-04-21 Nok Nok Labs, Inc. System and method for efficiently enrolling, registering, and authenticating with multiple authentication devices
US8934837B2 (en) 2013-01-03 2015-01-13 Blackberry Limited Mobile wireless communications device including NFC antenna matching control circuit and associated methods
US9942750B2 (en) 2013-01-23 2018-04-10 Qualcomm Incorporated Providing an encrypted account credential from a first device to a second device
US20140214674A1 (en) 2013-01-29 2014-07-31 Reliance Communications, Llc. Method and system for conducting secure transactions with credit cards using a monitoring device
US20140229375A1 (en) 2013-02-11 2014-08-14 Groupon, Inc. Consumer device payment token management
US9785946B2 (en) 2013-03-07 2017-10-10 Mastercard International Incorporated Systems and methods for updating payment card expiration information
US10152706B2 (en) 2013-03-11 2018-12-11 Cellco Partnership Secure NFC data authentication
US9307505B2 (en) 2013-03-12 2016-04-05 Blackberry Limited System and method for adjusting a power transmission level for a communication device
US9763097B2 (en) 2013-03-13 2017-09-12 Lookout, Inc. Method for performing device security corrective actions based on loss of proximity to another device
EP2973305A4 (en) 2013-03-15 2016-08-17 Intel Corp MECHANISM FOR ENHANCING DYNAMIC AND TARGET ADVERTISING FOR COMPUTER SYSTEMS
US9887983B2 (en) 2013-10-29 2018-02-06 Nok Nok Labs, Inc. Apparatus and method for implementing composite authenticators
US20140339315A1 (en) 2013-04-02 2014-11-20 Tnt Partners, Llc Programmable Electronic Card and Supporting Device
WO2014170741A2 (en) 2013-04-15 2014-10-23 Pardhasarthy Mahesh Bhupathi Payback payment system and method to facilitate the same
CN105144656A (zh) 2013-04-26 2015-12-09 交互数字专利控股公司 用于实现要求的认证确保级别的多因素认证
US20140337235A1 (en) 2013-05-08 2014-11-13 The Toronto-Dominion Bank Person-to-person electronic payment processing
US9104853B2 (en) 2013-05-16 2015-08-11 Symantec Corporation Supporting proximity based security code transfer from mobile/tablet application to access device
US10043164B2 (en) 2013-05-20 2018-08-07 Mastercard International Incorporated System and method for facilitating a transaction between a merchant and a cardholder
US20140365780A1 (en) 2013-06-07 2014-12-11 Safa Movassaghi System and methods for one-time password generation on a mobile computing device
US10475027B2 (en) 2013-07-23 2019-11-12 Capital One Services, Llc System and method for exchanging data with smart cards
EP3025270A1 (en) 2013-07-25 2016-06-01 Nymi inc. Preauthorized wearable biometric device, system and method for use thereof
GB2516861A (en) 2013-08-01 2015-02-11 Mastercard International Inc Paired Wearable payment device
CN103417202B (zh) 2013-08-19 2015-11-18 赵蕴博 一种腕式生命体征监测装置及其监测方法
BR112016003676B1 (pt) 2013-09-24 2022-10-18 Intel Corporation Método implantado por computador, dispositivo e sistema para controle de acesso de nfc em uma arquitetura de nfc centrada em elemento seguro
EP2854332A1 (en) 2013-09-27 2015-04-01 Gemalto SA Method for securing over-the-air communication between a mobile application and a gateway
US11748746B2 (en) 2013-09-30 2023-09-05 Apple Inc. Multi-path communication of electronic device secure element data for online payments
US10878414B2 (en) 2013-09-30 2020-12-29 Apple Inc. Multi-path communication of electronic device secure element data for online payments
JP6293276B2 (ja) 2013-11-15 2018-03-14 深▲セン▼光啓智能光子技術有限公司Kuang−Chi Intelligent Photonic Technology Ltd. コマンド情報の送信方法、受信方法及びその装置
AU2014353151B2 (en) 2013-11-19 2018-03-08 Visa International Service Association Automated account provisioning
EP3078220A4 (en) 2013-12-02 2017-05-17 Mastercard International Incorporated Method and system for secure tranmission of remote notification service messages to mobile devices without secure elements
EP3084701B1 (en) 2013-12-19 2022-05-04 Visa International Service Association Cloud-based transactions methods and systems
US20150180869A1 (en) 2013-12-23 2015-06-25 Samsung Electronics Company, Ltd. Cloud-based scalable authentication for electronic devices
US9602508B1 (en) 2013-12-26 2017-03-21 Lookout, Inc. System and method for performing an action based upon two-party authorization
US20150205379A1 (en) 2014-01-20 2015-07-23 Apple Inc. Motion-Detected Tap Input
US9420496B1 (en) 2014-01-24 2016-08-16 Sprint Communications Company L.P. Activation sequence using permission based connection to network
US9773151B2 (en) 2014-02-06 2017-09-26 University Of Massachusetts System and methods for contactless biometrics-based identification
US20160012465A1 (en) 2014-02-08 2016-01-14 Jeffrey A. Sharp System and method for distributing, receiving, and using funds or credits and apparatus thereof
US20150371234A1 (en) 2014-02-21 2015-12-24 Looppay, Inc. Methods, devices, and systems for secure provisioning, transmission, and authentication of payment data
US10096027B2 (en) 2014-03-12 2018-10-09 The Toronto-Dominion Bank System and method for authorizing a debit transaction without user authentication
EP2924914A1 (en) 2014-03-25 2015-09-30 Gemalto SA Method to manage a one time password key
US9251330B2 (en) 2014-04-09 2016-02-02 International Business Machines Corporation Secure management of a smart card
CN106416189B (zh) 2014-04-14 2020-09-25 万事达卡国际股份有限公司 用于改进的认证的系统和方法
US20150317626A1 (en) 2014-04-30 2015-11-05 Intuit Inc. Secure proximity exchange of payment information between mobile wallet and point-of-sale
AU2015253182B2 (en) 2014-05-01 2019-02-14 Visa International Service Association Data verification using access device
WO2015171942A1 (en) 2014-05-07 2015-11-12 Visa International Service Association Enhanced data interface for contactless communications
GB201408539D0 (en) 2014-05-14 2014-06-25 Mastercard International Inc Improvements in mobile payment systems
US10475026B2 (en) 2014-05-16 2019-11-12 International Business Machines Corporation Secure management of transactions using a smart/virtual card
US20150339663A1 (en) 2014-05-21 2015-11-26 Mastercard International Incorporated Methods of payment token lifecycle management on a mobile device
US9483763B2 (en) 2014-05-29 2016-11-01 Apple Inc. User interface for payments
US9449239B2 (en) 2014-05-30 2016-09-20 Apple Inc. Credit card auto-fill
KR101508320B1 (ko) 2014-06-30 2015-04-07 주식회사 인포바인 Nfc 카드를 이용한 otp 발급 장치, otp 생성 장치, 및 이를 이용한 방법
US9455968B1 (en) 2014-12-19 2016-09-27 Emc Corporation Protection of a secret on a mobile device using a secret-splitting technique with a fixed user share
US9780953B2 (en) 2014-07-23 2017-10-03 Visa International Service Association Systems and methods for secure detokenization
US20160026997A1 (en) 2014-07-25 2016-01-28 XPressTap, Inc. Mobile Communication Device with Proximity Based Communication Circuitry
US9875347B2 (en) 2014-07-31 2018-01-23 Nok Nok Labs, Inc. System and method for performing authentication using data analytics
US20160048913A1 (en) 2014-08-15 2016-02-18 Mastercard International Incorporated Systems and Methods for Assigning a Variable Length Bank Identification Number
US9775029B2 (en) 2014-08-22 2017-09-26 Visa International Service Association Embedding cloud-based functionalities in a communication device
US10242356B2 (en) 2014-08-25 2019-03-26 Google Llc Host-formatted select proximity payment system environment response
CN111756533B (zh) 2014-08-29 2023-07-04 维萨国际服务协会 用于安全密码生成的系统、方法和存储介质
CN104239783A (zh) 2014-09-19 2014-12-24 东软集团股份有限公司 一种特定信息安全输入系统及方法
US9953323B2 (en) 2014-09-23 2018-04-24 Sony Corporation Limiting e-card transactions based on lack of proximity to associated CE device
GB2530726B (en) 2014-09-25 2016-11-02 Ibm Distributed single sign-on
EP3198907B1 (en) 2014-09-26 2019-04-10 Visa International Service Association Remote server encrypted data provisioning system and methods
US9432339B1 (en) 2014-09-29 2016-08-30 Emc Corporation Automated token renewal using OTP-based authentication codes
US9473509B2 (en) 2014-09-29 2016-10-18 International Business Machines Corporation Selectively permitting or denying usage of wearable device services
CN104283886B (zh) 2014-10-14 2017-12-29 中国科学院信息工程研究所 一种基于智能终端本地认证的web安全访问的实现方法
CN104463270A (zh) 2014-11-12 2015-03-25 惠州Tcl移动通信有限公司 一种基于rfid的智能终端、金融卡以及金融管理系统
WO2016080952A1 (en) 2014-11-17 2016-05-26 Empire Technology Development Llc Mobile device prevention of contactless card attacks
US9589264B2 (en) 2014-12-10 2017-03-07 American Express Travel Related Services Company, Inc. System and method for pre-provisioned wearable contactless payments
GB2533333A (en) 2014-12-16 2016-06-22 Visa Europe Ltd Transaction authorisation
WO2016112290A1 (en) 2015-01-09 2016-07-14 Interdigital Technology Corporation Scalable policy based execution of multi-factor authentication
US10333696B2 (en) 2015-01-12 2019-06-25 X-Prime, Inc. Systems and methods for implementing an efficient, scalable homomorphic transformation of encrypted data with minimal data expansion and improved processing efficiency
US10223549B2 (en) * 2015-01-21 2019-03-05 Onion ID Inc. Techniques for facilitating secure, credential-free user access to resources
US20170011406A1 (en) 2015-02-10 2017-01-12 NXT-ID, Inc. Sound-Directed or Behavior-Directed Method and System for Authenticating a User and Executing a Transaction
US20160253651A1 (en) 2015-02-27 2016-09-01 Samsung Electronics Co., Ltd. Electronic device including electronic payment system and operating method thereof
US20160267486A1 (en) 2015-03-13 2016-09-15 Radiius Corp Smartcard Payment System and Method
US20160277383A1 (en) 2015-03-16 2016-09-22 Assa Abloy Ab Binding to a user device
US11736468B2 (en) 2015-03-16 2023-08-22 Assa Abloy Ab Enhanced authorization
WO2016160816A1 (en) 2015-03-30 2016-10-06 Hendrick Chaya Coleena Smart data cards that enable the performance of various functions upon activation/authentication by a user's fingerprint, oncard pin number entry, and/or by facial recognition of the user, or by facial recognition of a user alone, including an automated changing security number that is displayed on a screen on a card's surface following an authenticated biometric match
CN104835038A (zh) 2015-03-30 2015-08-12 恒宝股份有限公司 一种联网支付装置及方法
US20170289127A1 (en) 2016-03-29 2017-10-05 Chaya Coleena Hendrick Smart data cards that enable the performance of various functions upon activation/authentication by a user's fingerprint, oncard pin number entry, and/or by facial recognition of the user, or by facial recognition of a user alone, including an automated changing security number that is displayed on a screen on a card's surface following an authenticated biometric match
US10482453B2 (en) 2015-04-14 2019-11-19 Capital One Services, Llc Dynamic transaction card protected by gesture and voice recognition
US10360557B2 (en) 2015-04-14 2019-07-23 Capital One Services, Llc Dynamic transaction card protected by dropped card detection
EP4109372A1 (en) 2015-04-14 2022-12-28 Capital One Services, LLC A system, method, and apparatus for a dynamic transaction card
US9674705B2 (en) 2015-04-22 2017-06-06 Kenneth Hugh Rose Method and system for secure peer-to-peer mobile communications
EP3955146A1 (en) 2015-05-05 2022-02-16 Ping Identity Corporation Identity management service using a block chain
US20160335531A1 (en) 2015-05-12 2016-11-17 Dynamics Inc. Dynamic security codes, tokens, displays, cards, devices, multi-card devices, systems and methods
FR3038429B1 (fr) 2015-07-03 2018-09-21 Ingenico Group Conteneur de paiement, procede de creation, procede de traitement, dispositifs et programmes correspondants
US20170039566A1 (en) 2015-07-10 2017-02-09 Diamond Sun Labs, Inc. Method and system for secured processing of a credit card
US10108965B2 (en) 2015-07-14 2018-10-23 Ujet, Inc. Customer communication system including service pipeline
US11120436B2 (en) 2015-07-17 2021-09-14 Mastercard International Incorporated Authentication system and method for server-based payments
US20170024716A1 (en) 2015-07-22 2017-01-26 American Express Travel Related Services Company, Inc. System and method for single page banner integration
US10492163B2 (en) 2015-08-03 2019-11-26 Jpmorgan Chase Bank, N.A. Systems and methods for leveraging micro-location devices for improved travel awareness
KR20170028015A (ko) 2015-09-03 2017-03-13 엔에이치엔엔터테인먼트 주식회사 휴대용 단말기를 이용한 온라인 신용카드 결제 시스템 및 결제 방법
WO2017042400A1 (en) 2015-09-11 2017-03-16 Dp Security Consulting Sas Access method to an on line service by means of access tokens and secure elements restricting the use of these access tokens to their legitimate owner
FR3041195A1 (fr) 2015-09-11 2017-03-17 Dp Security Consulting Procede d'acces a un service en ligne au moyen d'un microcircuit securise et de jetons de securite restreignant l'utilisation de ces jetons a leur detenteur legitime
ITUB20155318A1 (it) 2015-10-26 2017-04-26 St Microelectronics Srl Tag, relativo procedimento e sistema per identificare e/o autenticare oggetti
US20170140379A1 (en) 2015-11-17 2017-05-18 Bruce D. Deck Credit card randomly generated pin
CA2944935C (en) 2015-11-27 2026-05-19 The Toronto-Dominion Bank System and method for remotely activating a pin-pad terminal
US9965911B2 (en) 2015-12-07 2018-05-08 Capital One Services, Llc Electronic access control system
US9948467B2 (en) 2015-12-21 2018-04-17 Mastercard International Incorporated Method and system for blockchain variant using digital signatures
KR101637863B1 (ko) 2016-01-05 2016-07-08 주식회사 코인플러그 본인인증용 정보 보안 전송시스템 및 방법
WO2017134281A1 (en) 2016-02-04 2017-08-10 Nasdaq Technology Ab Systems and methods for storing and sharing transactional data using distributed computer systems
US9619952B1 (en) 2016-02-16 2017-04-11 Honeywell International Inc. Systems and methods of preventing access to users of an access control system
US10148135B2 (en) 2016-02-16 2018-12-04 Intel IP Corporation System, apparatus and method for authenticating a device using a wireless charger
FR3049083A1 (fr) 2016-03-15 2017-09-22 Dp Security Consulting Sas Procede de duplication des donnees d'un microcircuit securise vers un autre microcircuit securise permettant, au plus, a un seul microcircuit securise d'etre operationnel a un instant donne
US9894199B1 (en) 2016-04-05 2018-02-13 State Farm Mutual Automobile Insurance Company Systems and methods for authenticating a caller at a call center
ES2822997T3 (es) 2016-04-07 2021-05-05 Contactoffice Group Método para satisfacer una solicitud criptográfica que requiere un valor de una clave privada
US10255816B2 (en) 2016-04-27 2019-04-09 Uber Technologies, Inc. Transport vehicle configuration for impaired riders
US10333705B2 (en) 2016-04-30 2019-06-25 Civic Technologies, Inc. Methods and apparatus for providing attestation of information using a centralized or distributed ledger
KR20170126688A (ko) 2016-05-10 2017-11-20 엘지전자 주식회사 스마트 카드 및 그 스마트 카드의 제어 방법
US9635000B1 (en) 2016-05-25 2017-04-25 Sead Muftic Blockchain identity management system based on public identities ledger
GB201609460D0 (en) 2016-05-30 2016-07-13 Silverleap Technology Ltd Increased security through ephemeral keys for software virtual contactless card in a mobile phone
US10097544B2 (en) 2016-06-01 2018-10-09 International Business Machines Corporation Protection and verification of user authentication credentials against server compromise
KR20180013710A (ko) 2016-07-28 2018-02-07 (주)이스톰 공개키 기반의 서비스 인증 방법 및 시스템
US10680677B2 (en) 2016-08-01 2020-06-09 Nxp B.V. NFC system wakeup with energy harvesting
US10032169B2 (en) 2016-08-08 2018-07-24 Ellipse World, Inc. Prepaid, debit and credit card security code generation system
US20180039986A1 (en) 2016-08-08 2018-02-08 Ellipse World S.A. Method for a Prepaid, Debit and Credit Card Security Code Generation System
US10084762B2 (en) 2016-09-01 2018-09-25 Ca, Inc. Publicly readable blockchain registry of personally identifiable information breaches
US10748130B2 (en) 2016-09-30 2020-08-18 Square, Inc. Sensor-enabled activation of payment instruments
US10462128B2 (en) 2016-10-11 2019-10-29 Michael Arthur George Verification of both identification and presence of objects over a network
US20180101847A1 (en) 2016-10-12 2018-04-12 Microsoft Technology Licensing, Llc User and device authentication for web applications
US10719771B2 (en) 2016-11-09 2020-07-21 Cognitive Scale, Inc. Method for cognitive information processing using a cognitive blockchain architecture
US20180160255A1 (en) 2016-12-01 2018-06-07 Youngsuck PARK Nfc tag-based web service system and method using anti-simulation function
US10230720B2 (en) 2016-12-12 2019-03-12 Sap Se Authorization code flow for in-browser applications
US10133979B1 (en) 2016-12-29 2018-11-20 Wells Fargo Bank, N.A. Wearable computing device-powered chip-enabled card
US10237070B2 (en) 2016-12-31 2019-03-19 Nok Nok Labs, Inc. System and method for sharing keys across authenticators
US20180240106A1 (en) 2017-02-21 2018-08-23 Legacy Ip Llc Hand-held electronics device for aggregation of and management of personal electronic data
US20180254909A1 (en) 2017-03-06 2018-09-06 Lamark Solutions, Inc. Virtual Identity Credential Issuance and Verification Using Physical and Virtual Means
US10764043B2 (en) 2017-04-05 2020-09-01 University Of Florida Research Foundation, Incorporated Identity and content authentication for phone calls
US10129648B1 (en) 2017-05-11 2018-11-13 Microsoft Technology Licensing, Llc Hinged computing device for binaural recording
US10454915B2 (en) 2017-05-18 2019-10-22 Oracle International Corporation User authentication using kerberos with identity cloud service
US20190019375A1 (en) 2017-07-14 2019-01-17 Gamblit Gaming, Llc Ad hoc customizable electronic gaming table
US9940571B1 (en) 2017-08-25 2018-04-10 Capital One Services, Llc Metal contactless transaction card
US10469490B2 (en) 2017-10-19 2019-11-05 Mastercard International Incorporated Methods and systems for providing FIDO authentication services
US10019707B1 (en) 2017-10-24 2018-07-10 Capital One Services, Llc Transaction card mode related to locating a transaction card
US11102180B2 (en) 2018-01-31 2021-08-24 The Toronto-Dominion Bank Real-time authentication and authorization based on dynamically generated cryptographic data
CA3090703A1 (en) 2018-03-16 2019-09-19 Iot And M2M Technologies, Llc Configuration systems and methods for secure operation of networked transducers
WO2020072575A1 (en) * 2018-10-02 2020-04-09 Capital One Services, Llc Systems and methods for cryptographic authentication of contactless cards
WO2020092351A1 (en) 2018-10-29 2020-05-07 Login Id Inc. Decentralized computing systems for strong user authentication and related methods
EP3663946A1 (en) 2018-12-06 2020-06-10 Fujitsu Limited Information processing apparatus, information processing method, and information processing program
FR3095528B1 (fr) * 2019-04-25 2021-05-21 CopSonic Jeton matériel d’authentification à validation déportée
US11025732B2 (en) 2019-06-17 2021-06-01 Vmware, Inc. Method and apparatus to perform user authentication during cloud provider sessions
JP7714569B2 (ja) * 2020-04-17 2025-07-29 トゥルソナ,インコーポレイテッド 暗号化認証のためのシステム及び方法
US20210352069A1 (en) * 2020-05-11 2021-11-11 Citrix Systems, Inc. Local authentication virtual authorization

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013109932A1 (en) * 2012-01-18 2013-07-25 OneID Inc. Methods and systems for secure identity management
US20200127858A1 (en) * 2017-01-27 2020-04-23 Giesecke+Devrient Mobile Security Gmbh Method for carrying out an authentication
US20200336308A1 (en) * 2020-07-02 2020-10-22 BehavioSec Inc FIDO Authentication with Behavior Report to Maintain Secure Data Connection

Also Published As

Publication number Publication date
US20220407723A1 (en) 2022-12-22
US20250379752A1 (en) 2025-12-11
CA3222325A1 (en) 2022-12-22
KR20240024112A (ko) 2024-02-23
JP2024527492A (ja) 2024-07-25
EP4356269A1 (en) 2024-04-24
AU2022292656A1 (en) 2024-01-04
CN117795505A (zh) 2024-03-29
US12301735B2 (en) 2025-05-13

Similar Documents

Publication Publication Date Title
US12301735B2 (en) Systems and methods for contactless card communication and multi-device key pair cryptographic authentication
US11562358B2 (en) Systems and methods for near field contactless card communication and cryptographic authentication
US12335412B2 (en) Systems and methods for scalable cryptographic authentication of contactless cards
WO2022266199A1 (en) Systems and methods for contactless card communication and key pair cryptographic authentication using distributed storage
EP4055796B1 (en) Systems and methods for cross coupling risk analytics and one-time-passcodes
US20230289801A1 (en) Systems and methods for authentication of access tokens
US20250390884A1 (en) Systems and methods for dynamic data generation and cryptographic card authentication
US20240303649A1 (en) Systems and methods for secure authentication through near field communication
HK40102554A (en) Systems and methods for contactless card communication and multi-device key pair cryptographic authentication
HK40108396A (en) Systems and methods for near field contactless card communication and cryptographic authentication
HK40102214A (en) Systems and methods for contactless card communication and key pair cryptographic authentication using distributed storage

Legal Events

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

Ref document number: 22744348

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 3222325

Country of ref document: CA

WWE Wipo information: entry into national phase

Ref document number: 806505

Country of ref document: NZ

Ref document number: 2022292656

Country of ref document: AU

Ref document number: AU2022292656

Country of ref document: AU

ENP Entry into the national phase

Ref document number: 2023577529

Country of ref document: JP

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 20237044743

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2022292656

Country of ref document: AU

Date of ref document: 20220616

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 2022744348

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 202280055032.4

Country of ref document: CN

ENP Entry into the national phase

Ref document number: 2022744348

Country of ref document: EP

Effective date: 20240118