US20230252452A1 - Secure authentication based on identity data stored in a contactless card - Google Patents
Secure authentication based on identity data stored in a contactless card Download PDFInfo
- Publication number
- US20230252452A1 US20230252452A1 US18/124,050 US202318124050A US2023252452A1 US 20230252452 A1 US20230252452 A1 US 20230252452A1 US 202318124050 A US202318124050 A US 202318124050A US 2023252452 A1 US2023252452 A1 US 2023252452A1
- Authority
- US
- United States
- Prior art keywords
- age
- contactless card
- data
- customer
- pos terminal
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 claims abstract description 33
- 230000015654 memory Effects 0.000 claims description 56
- 238000012795 verification Methods 0.000 claims description 37
- 238000003860 storage Methods 0.000 claims description 20
- 230000001360 synchronised effect Effects 0.000 claims description 4
- 238000004519 manufacturing process Methods 0.000 abstract description 4
- 238000004891 communication Methods 0.000 description 32
- 238000012546 transfer Methods 0.000 description 18
- 238000012545 processing Methods 0.000 description 16
- 230000008569 process Effects 0.000 description 11
- 230000003287 optical effect Effects 0.000 description 8
- 230000005291 magnetic effect Effects 0.000 description 7
- 230000006870 function Effects 0.000 description 5
- 230000002093 peripheral effect Effects 0.000 description 4
- 238000010079 rubber tapping Methods 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 3
- 239000000463 material Substances 0.000 description 3
- 230000006855 networking Effects 0.000 description 3
- 230000004044 response Effects 0.000 description 3
- 239000000758 substrate Substances 0.000 description 3
- KDLHZDBZIXYQEI-UHFFFAOYSA-N Palladium Chemical compound [Pd] KDLHZDBZIXYQEI-UHFFFAOYSA-N 0.000 description 2
- 239000003990 capacitor Substances 0.000 description 2
- 238000004590 computer program Methods 0.000 description 2
- 230000009977 dual effect Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 229920000642 polymer Polymers 0.000 description 2
- 239000007787 solid Substances 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 238000010200 validation analysis Methods 0.000 description 2
- FMFKNGWZEQOWNK-UHFFFAOYSA-N 1-butoxypropan-2-yl 2-(2,4,5-trichlorophenoxy)propanoate Chemical compound CCCCOCC(C)OC(=O)C(C)OC1=CC(Cl)=C(Cl)C=C1Cl FMFKNGWZEQOWNK-UHFFFAOYSA-N 0.000 description 1
- OKTJSMMVPCPJKN-UHFFFAOYSA-N Carbon Chemical compound [C] OKTJSMMVPCPJKN-UHFFFAOYSA-N 0.000 description 1
- 229920001756 Polyvinyl chloride acetate Polymers 0.000 description 1
- RTAQQCXQSZGOHL-UHFFFAOYSA-N Titanium Chemical compound [Ti] RTAQQCXQSZGOHL-UHFFFAOYSA-N 0.000 description 1
- XECAHXYUAAWDEL-UHFFFAOYSA-N acrylonitrile butadiene styrene Chemical compound C=CC=C.C=CC#N.C=CC1=CC=CC=C1 XECAHXYUAAWDEL-UHFFFAOYSA-N 0.000 description 1
- 229920000122 acrylonitrile butadiene styrene Polymers 0.000 description 1
- 239000004676 acrylonitrile butadiene styrene Substances 0.000 description 1
- 238000013459 approach Methods 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 229910052799 carbon Inorganic materials 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000012790 confirmation Methods 0.000 description 1
- 238000005520 cutting process Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 230000002708 enhancing effect Effects 0.000 description 1
- PCHJSUWPFVWCPO-UHFFFAOYSA-N gold Chemical compound [Au] PCHJSUWPFVWCPO-UHFFFAOYSA-N 0.000 description 1
- 229910052737 gold Inorganic materials 0.000 description 1
- 239000010931 gold Substances 0.000 description 1
- 239000010410 layer Substances 0.000 description 1
- 239000003550 marker Substances 0.000 description 1
- 230000003340 mental effect Effects 0.000 description 1
- 229910052751 metal Inorganic materials 0.000 description 1
- 239000002184 metal Substances 0.000 description 1
- 150000002739 metals Chemical class 0.000 description 1
- 229910052763 palladium Inorganic materials 0.000 description 1
- 229920003023 plastic Polymers 0.000 description 1
- 239000004033 plastic Substances 0.000 description 1
- 229920000515 polycarbonate Polymers 0.000 description 1
- 239000004417 polycarbonate Substances 0.000 description 1
- 229920000728 polyester Polymers 0.000 description 1
- 239000004800 polyvinyl chloride Substances 0.000 description 1
- 229920000915 polyvinyl chloride Polymers 0.000 description 1
- 210000001525 retina Anatomy 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 229910052710 silicon Inorganic materials 0.000 description 1
- 239000010703 silicon Substances 0.000 description 1
- 239000002356 single layer Substances 0.000 description 1
- 239000000126 substance Substances 0.000 description 1
- 229910052719 titanium Inorganic materials 0.000 description 1
- 239000010936 titanium Substances 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/0853—Network architectures or network communication protocols for network security for authentication of entities using an additional device, e.g. smartcard, SIM or a different communication terminal
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/34—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using cards, e.g. integrated circuit [IC] cards or magnetic cards
- G06Q20/352—Contactless payments by cards
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR 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
- G06F21/34—User authentication involving the use of external additional devices, e.g. dongles or smart cards
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
- G06Q20/3821—Electronic credentials
- G06Q20/38215—Use of certificates or encrypted proofs of transaction rights
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
- G06Q20/3825—Use of electronic signatures
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
- G06Q20/3829—Payment protocols; Details thereof insuring higher security of transaction involving key management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
- G06Q20/401—Transaction verification
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
- G06Q20/401—Transaction verification
- G06Q20/4014—Identity check for transactions
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
- H04L63/0428—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
- H04L63/0442—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload wherein the sending and receiving network entities apply asymmetric encryption, i.e. different keys for encryption and decryption
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/083—Network architectures or network communication protocols for network security for authentication of entities using passwords
- H04L63/0838—Network architectures or network communication protocols for network security for authentication of entities using passwords using one-time-passwords
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/0861—Network architectures or network communication protocols for network security for authentication of entities using biometrical features, e.g. fingerprint, retina-scan
-
- 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
- H04L2463/00—Additional details relating to network architectures or network communication protocols for network security covered by H04L63/00
- H04L2463/082—Additional details relating to network architectures or network communication protocols for network security covered by H04L63/00 applying multi-factor authentication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L2463/00—Additional details relating to network architectures or network communication protocols for network security covered by H04L63/00
- H04L2463/102—Additional details relating to network architectures or network communication protocols for network security covered by H04L63/00 applying security measure for e-commerce
Definitions
- Embodiments herein generally relate to computing platforms, and more specifically, to using a contactless card storing identity data for secure authentication.
- Identity verification is an important task for modern computing systems.
- Conventional approaches may require that users provide additional information, such as a one-time passcode (OTP), when attempting to access computing systems or perform electronic transactions.
- OTP one-time passcode
- security vulnerabilities may exist in these solutions.
- the OTP may be intercepted and used to gain unauthorized access.
- different systems may require different types of additional information for identity verification, making conventional solutions impractical for many users.
- an application may receive an indication specifying to perform an operation associated with an account.
- the application may receive encrypted data from a contactless card associated with the account.
- the application may receive, from an authentication server, an indication specifying that the authentication server decrypted the encrypted data.
- the application may determine a type of authentication data required to authorize the operation.
- the application may receive, based on the determined type of authentication data, a first data element from the contactless card, the first data element comprising passport data or driver license data.
- the application may determine that the first data element satisfies at least one rule for authorizing the operation.
- the application may authorize performance of the operation based on the received indication specifying that the authentication server verified the encrypted data and the determination that the first data element satisfies the at least one rule for authorizing the operation.
- FIGS. 1 A- 1 B illustrate embodiments of a system for secure authentication based on identity data stored in a contactless card.
- FIGS. 2 A- 2 C illustrate embodiments of tapping a contactless card to a computing device to provide secure authentication based on identity data stored in the contactless card.
- FIGS. 3 A- 3 C illustrate embodiments of tapping a contactless card to a computing device to provide secure authentication based on identity data stored in the contactless card.
- FIGS. 4 A- 4 B illustrate an example contactless card.
- FIG. 5 illustrates an embodiment of a first logic flow.
- FIG. 6 illustrates an embodiment of a second logic flow.
- FIG. 7 illustrates an embodiment of a third logic flow.
- FIG. 8 illustrates an embodiment of a computing system.
- Embodiments disclosed herein provide techniques for secure authentication using identity data stored in a contactless card.
- a contactless card may store a plurality of different types of information for a user, such as driver's license information, passport information, social security number, and/or any other biographical information.
- the user may then attempt to perform an operation, such as making a purchase, transferring funds via an application executing on a mobile device, requesting a credit increase via the application, and the like.
- the application may determine a type of authentication data required to authorize the requested operation. For example, a rule may specify that transferring funds via the application requires authentication based on passport data stored in the contactless card. Therefore, the application may determine that passport data as the type of authentication data.
- the user may then tap the contactless card to the mobile device to initiate the secure authentication process.
- the contactless card may generate and transmit encrypted data to the application.
- the encrypted data may be generated based on a cryptographic algorithm, a customer identifier, and an encryption key for the contactless card.
- the application may then transmit the encrypted data to an authentication server for authentication.
- the server may then decrypt the encrypted data using a local copy of the encryption key for the contactless card to yield the customer identifier, thereby authenticating the encrypted data.
- the server may then transmit an indication of the authentication of the encrypted data to the application.
- the application may then process the passport data.
- the passport data is sent by the contactless card to the application with the encrypted customer identifier.
- the passport data is sent by the contactless card subsequent to another tap of the contactless card to the mobile device.
- the application may perform any number of operations.
- the passport data stored on the contactless card may include a passport image depicting the user.
- the application may instruct the user to capture an image depicting their face using the mobile device. Once captured, the application may compare the images to determine a similarity between the images. If the similarity exceeds a threshold level of similarity specified in a rule, the application may authenticate the user and/or validate the identity of the user.
- the application may then authorize the performance of the operation based on the received indication specifying that the authentication server verified the encrypted data and the determination that the similarity of the images exceeds the threshold level of similarity. For example, the user may be permitted to access an interface of the application to transfer funds from one account to another.
- embodiments disclosed herein improve the security of all devices and associated data. For example, by requiring validation of encrypted data generated by the contactless card to access applications and/or data, the security of the applications and/or data are improved. As another example, by requiring validation of the encrypted data prior to performing operations (e.g., making purchases, extending credit, etc.), the security of such operations and associated assets is improved.
- FIG. 1 A depicts a schematic of an exemplary system 100 , consistent with disclosed embodiments.
- the system 100 includes one or more contactless cards 101 , one or more mobile computing devices 110 , and an authentication server 120 .
- the contactless cards 101 are representative of any type of payment cards, such as a credit card, debit card, ATM card, gift card, and the like.
- the contactless cards 101 may comprise one or more communications interfaces 133 , such as a radio frequency identification (RFID) chip, configured to communicate with the computing devices 110 via NFC, the EMV standard, or other short-range protocols in wireless communication.
- RFID radio frequency identification
- NFC is used as an example communications protocol, the disclosure is equally applicable to other types of wireless communications, such as the EMV standard, Bluetooth, and/or Wi-Fi.
- the mobile devices 110 are representative of any type of network-enabled computing devices, such as smartphones, tablet computers, wearable devices, laptops, portable gaming devices, and the like.
- the authentication server 120 is representative of any type of computing device, such as a server, workstation, compute cluster, cloud computing platform, virtualized computing system, and the like.
- a memory 102 of the contactless card includes an applet 103 , a counter 104 , a master key 105 , a diversified key 106 , a unique customer identifier (ID) 107 , passport data 108 , driver's license data 109 , and other user data 131 .
- the applet 103 is executable code configured to perform the operations described herein.
- the counter 104 , master key 105 , diversified key 106 , and customer ID 107 are used to provide security in the system 100 as described in greater detail below.
- the passport data 108 is representative of an electronic passport of a user associated with the contactless card 101 .
- the passport data 108 may include any number and types of data.
- the passport data 108 may include text data describing different attributes of the passport and/or user (e.g., name, date of birth, passport number, passport issue date, passport expiration date, issuing nation, etc.) as well as image data (e.g., one or more images of the passport itself, an image of the user included in the passport, etc.).
- image data e.g., one or more images of the passport itself, an image of the user included in the passport, etc.
- the customer ID 107 , passport data 108 , driver's license data 109 , and other user data 131 may collectively be referred to herein as “identity data.”
- the driver's license data 109 is representative of one or more driver's licenses held by the user associated with the contactless card.
- the driver's license data 109 may include any number and types of data.
- the driver's license data 109 may include a barcode (or other computer-readable marker) that encodes different attributes of the driver's license and/or user (e.g., name, date of birth, license number, license issue date, expiration date, issuing state, etc.), text data representing the attributes (and/or the barcode), and/or image data (e.g., one or more images of the driver's license, an image of the user included in the driver's license, etc.).
- the other user data 131 is representative of other data describing the user.
- the other user data 131 may include social security numbers, images, data representing biometric identifiers of the user, other identification cards, loyalty program information, and the like.
- the passport data 108 , driver's license data 109 , and other user data 131 are encrypted.
- a memory 111 of the mobile device 110 includes an instance of an operating system (OS) 112 .
- Example operating systems 112 include the Android® OS, iOS®, macOS®, Linux®, and Windows® operating systems.
- the OS 112 includes an account application 113 .
- the account application 113 allows users to perform various account-related operations, such as viewing account balances, purchasing items, processing payments, and the like.
- the account application 113 may further control access permissions to different functions provided by the account application 113 and/or the other applications 114 .
- a user may authenticate using authentication credentials to access certain features of the account application 113 .
- the authentication credentials may include a username (or login) and password, biometric credentials (e.g., fingerprints, Face ID, etc.), and the like.
- the user may request and/or attempt to perform an operation.
- the operation may include any type of operation, such as using the contactless card 101 to make a purchase, accessing certain features of the account application 113 , performing various account-related operations using the account application 113 , and/or accessing the other applications 114 (or any feature thereof).
- the other applications 114 are representative of any type of computing application, such as web browsers, messaging applications, word processing applications, social media applications, and the like.
- the user may desire to transfer funds from their account to another account using the account application 113 .
- the use of a specific operation as a reference example herein is not limiting of the disclosure, as the disclosure is equally applicable to any other type of operation.
- the system 100 To authorize the requested operation, (e.g., the previous example of transferring funds), the system 100 must authenticate and/or verify the identity of the user. To authenticate the identity of the user, embodiments disclosed herein may leverage the contactless card 101 . More specifically, once the user requests to perform the operation (or otherwise access a restricted resource), the account application 113 may output a notification instructing the user to tap the contactless card 101 to the device 110 . Generally, once the contactless card 101 is brought within communications range of the communications interface 118 of the device 110 , the applet 103 of the contactless card 101 may generate encrypted data, e.g., an encrypted customer ID 132 as part of the authentication process required to authorize the requested operation.
- encrypted data e.g., an encrypted customer ID 132
- the account application 113 may communicate with the contactless card 101 when the contactless card 101 is sufficiently close to the communications interface 118 of the mobile device 110 .
- the communications interface 118 may be configured to read from and/or communicate with the communications interface 133 of the contactless card 101 (e.g., via NFC, Bluetooth, RFID, etc.). Therefore, example communications interfaces 118 include NFC communication modules, Bluetooth communication modules, and/or RFID communication modules.
- the system 100 is configured to implement key diversification to secure data, which may be referred to as a key diversification technique herein.
- the server 120 or another computing device
- the contactless card 101 may be provisioned with the same master key 105 (also referred to as a master symmetric key). More specifically, each contactless card 101 is programmed with a distinct master key 105 that has a corresponding pair in the server 120 . For example, when a contactless card 101 is manufactured, a unique master key 105 may be programmed into the memory 102 of the contactless card 101 .
- the unique master key 105 may be stored in a record of a customer associated with the contactless card 101 in the account data 124 of the server 120 (and/or stored in a different secure location, such as the hardware security module (HSM) 125 ).
- the master key may be kept secret from all parties other than the contactless card 101 and server 120 , thereby enhancing security of the system 100 .
- the applet 103 of the contactless card 101 may encrypt and/or decrypt data (e.g., the customer ID 107 , passport data 108 , driver's license data 109 , and/or other user data 131 ) using the master key 105 and the data as input a cryptographic algorithm. For example, encrypting the customer ID 107 with the master key 105 may result in the encrypted customer ID 132 .
- the authentication server 120 may encrypt and/or decrypt data associated with the contactless card 101 using the corresponding master key 105 .
- the master keys 105 of the contactless card 101 and server 120 may be used in conjunction with the counters 104 to enhance security using key diversification.
- the counters 104 comprise values that are synchronized between the contactless card 101 and server 120 .
- the counter value 104 may comprise a number that changes each time data is exchanged between the contactless card 101 and the server 120 (and/or the contactless card 101 and the mobile device 110 ).
- the contactless card 101 may increment the counter value 104 .
- the contactless card 101 may then provide the master key 105 and counter value 104 as input to a cryptographic algorithm, which produces a diversified key 106 as output.
- the cryptographic algorithm may include encryption algorithms, hash-based message authentication code (HMAC) algorithms, cipher-based message authentication code (CMAC) algorithms, and the like.
- HMAC hash-based message authentication code
- CMAC cipher-based message authentication code
- Non-limiting examples of the cryptographic algorithm may include a symmetric encryption algorithm such as 3DES or AES128; a symmetric HMAC algorithm, such as HMAC-SHA-256; and a symmetric CMAC algorithm such as AES-CMAC. Examples of key diversification techniques are described in greater detail in U.S. patent application Ser. No. 16/205,119, filed Nov. 29, 2018. The aforementioned patent application is incorporated by reference herein in its entirety.
- the contactless card 101 may then encrypt the data (e.g., the customer ID 107 and/or any other data, such as the passport data 108 , driver's license data 109 , and/or other user data 131 ) using the diversified key 106 and the data as input to the cryptographic algorithm. For example, encrypting the customer ID 107 with the diversified key 106 may result in the encrypted customer ID 132 .
- the data e.g., the customer ID 107 and/or any other data, such as the passport data 108 , driver's license data 109 , and/or other user data 131
- the diversified key 106 may result in the encrypted customer ID 132 .
- the contactless card 101 may then transmit the encrypted data (e.g., the encrypted customer ID 132 ) to the account application 113 of the mobile device 110 (e.g., via an NFC connection, Bluetooth connection, etc.).
- the account application 113 of the mobile device 110 may then transmit the encrypted customer ID 132 to the server 120 via the network 130 .
- the contactless card 101 transmits the counter value 104 with the encrypted data.
- the contactless card 101 may transmit an encrypted counter value 104 , or an unencrypted counter value 104 .
- the authentication application 123 may authenticate the encrypted customer ID 132 .
- the authentication application 123 may attempt to decrypt the encrypted customer ID 132 using a copy of the master key 105 stored in the memory 122 of the authentication server 120 .
- the authentication application 123 may provide the master key 105 and counter value 104 as input to the cryptographic algorithm, which produces a diversified key 106 as output.
- the resulting diversified key 106 may correspond to the diversified key 106 of the contactless card 101 , which may be used to decrypt the encrypted customer ID 132 .
- the authentication application 123 may successfully decrypt the encrypted customer ID 132 , thereby verifying the encrypted customer ID 132 (e.g., by comparing the resulting customer ID 107 to a customer ID stored in the account data 124 , and/or based on an indication that the decryption using the key 105 and/or 106 was successful).
- the keys 105 , 106 are depicted as being stored in the memory 122 , the keys 105 , 106 may be stored elsewhere, such as in a secure element and/or the HSM 125 .
- the secure element and/or the HSM 125 may decrypt the encrypted customer ID 132 using the keys 105 and/or 106 and a cryptographic function.
- the secure element and/or HSM 125 may generate the diversified key 106 based on the master key 105 and counter value 104 as described above.
- the authentication application 123 If, however, the authentication application 123 is unable to decrypt the encrypted customer ID 132 to yield the expected result (e.g., the customer ID 107 of the account associated with the contactless card 101 ), the authentication application 123 does not validate the encrypted customer ID 132 . In such an example, the authentication application 123 transmits an indication of the failed verification to the account application 113 . As such, the account application 113 may reject performance of the requested operation to preserve the security of the account.
- FIG. 1 B illustrates an embodiment where the authentication application 123 has decrypted the encrypted customer ID 132 , thereby verifying (or authenticating) the encrypted data.
- the authentication application 123 transmits a verification 134 to the mobile device 110 , where the verification 134 indicates that the authentication application 123 successfully decrypted the encrypted customer ID 132 .
- the account application 113 may reference the rules 115 to determine what, if any, additional authentication steps are required.
- the rules 115 may generally specify a plurality of different authentication rules and/or thresholds for different requested operations. The rules may be based on the type of requested operation. For example, for the transfer of funds, the rules 115 may require additional authentication based on additional data elements such as the passport data 108 and/or the driver's license data 109 .
- the account application 113 may output an indication specifying that the user tap the contactless card 101 to the mobile device 110 .
- the account application 113 may then instruct the contactless card 101 to transmit the passport data 108 .
- the contactless card 101 may transmit the passport data 108 to the account application 113 .
- the passport data 108 may be encrypted.
- the account application 113 may transmit the encrypted passport data 108 to the server 120 for decryption (e.g., based on the keys 105 and/or 106 ), which then sends the decrypted passport data 108 to the account application 113 .
- the user may provide input to the account application 113 used to decrypt the encrypted passport data 108 .
- the account application 113 may instruct the user to capture an image depicting themselves using the camera 119 .
- the account application 113 may then compare the captured image to a passport image in the passport data 108 to determine a similarity of the persons depicted in each image. If the account application 113 determines that the similarity of the persons depicted in the images exceeds a threshold similarity specified in the rules 115 , the account application 113 may authorize the requested operation. The user may then proceed to complete the transfer of funds using the account application 113 .
- the rules 115 may require authentication based on the driver's license data 109 .
- the account application 113 may then output an indication specifying that the user tap the contactless card 101 to the mobile device 110 .
- the account application 113 may then instruct the contactless card 101 to transmit the driver's license data 109 .
- the contactless card 101 may transmit the driver's license data 109 to the account application 113 .
- the driver's license data 109 may be encrypted.
- the account application 113 may restrict performance of the operation (e.g., by restricting access to the graphical user interface (GUI) of the account application 113 used to transfer funds).
- the account application 113 may transmit the encrypted driver's license data 109 to the server 120 for decryption, which then sends the decrypted driver's license data 109 to the account application 113 .
- GUI graphical user interface
- the account application 113 then may instruct the user to capture an image depicting themselves using the camera 119 .
- the account application 113 may then compare the captured image to a driver's license image in the driver's license data 109 to determine a similarity of the persons depicted in each image. If the account application 113 determines that the similarity of the persons depicted in the images exceeds a threshold similarity specified in the rules 115 , the account application 113 may authorize the requested operation. Otherwise, the account application 113 may restrict performance of the operation (e.g., by restricting access to the GUI of the account application 113 used to transfer funds). The user may then proceed to complete the transfer of funds using the account application 113 .
- the account application 113 may determine whether the name on the passport and/or driver's license matches a name on the account associated with the contactless card 101 .
- the account application 113 may determine whether data encoded in the driver's license data 109 is readable.
- the account application 113 may determine whether a date of birth in passport and/or driver's license matches known a date of birth, e.g., a date of birth specified in the account data 124 for the account associated with the contactless card 101 .
- a social security number stored in the other user data 131 may be compared to a known social security number of the user associated with the account. If a matching name and/or social security number is found, the account application 113 may authorize the attempted operation. Otherwise, the account application 113 may reject the attempted operation.
- the applet 103 of the contactless card 101 may generate a digital signature (not pictured) for the passport data 108 and/or the driver's license data 109 using the keys 105 and/or 106 .
- a respective digital signature may sign the passport data 108 and/or driver's license data 109 .
- the contactless card 101 may then transmit the digital signatures with the passport data 108 and/or driver's license data 109 to the account application 113 , which in turn transmits the digital signatures to the authentication server 120 .
- the authentication application 123 may also verify the digital signature by decrypting the digital signature using a public key associated with the contactless card 101 and stored by the server 120 .
- the authentication application 123 may transmit an indication of the successful verification to the account application 113 , which may permit performance of the operation based on verification of the digital signature. If the digital signature is not verified, the account application 113 may restrict performance of the operation.
- the passport data 108 and/or the driver's license data 109 may be transmitted with the encrypted customer ID 132 responsive to a single tap of the contactless card 101 to the mobile device 110 .
- the user may obtain new and/or updated identification information, such as a passport, driver's license, etc.
- the account application 113 may receive the new and/or updated versions of the passport data 108 , driver's license data 109 , and/or other user data 131 , e.g., from the authentication server 120 .
- the account application 113 may transmit the data received from the server 120 to the contactless card 101 , and the applet 103 may store the received data in the memory 102 .
- FIG. 2 A is a schematic 200 depicting an example embodiment of tapping the contactless card 101 to provide secure authentication based on identity data stored in the contactless card 101 .
- the account application 113 may receive a request to perform an operation. Continuing with the previous example, the request may be to transfer funds from one account to another account.
- the account application 113 may output an indication to tap the contactless card 101 to the device 110 .
- the applet 103 of the contactless card 101 generates the encrypted customer ID 132 .
- the applet 103 may then transmit the encrypted customer ID 132 to the mobile device 110 , e.g., via NFC.
- the account application 113 may transmit the encrypted customer ID 132 to the authentication application 123 .
- the authentication application 123 may then attempt to decrypt the encrypted customer ID 132 using the master key 105 and/or the diversified key 106 associated with the contactless card 101 . If the authentication application 123 is unable to decrypt the encrypted customer ID 132 to yield an expected result (e.g., the customer ID 107 of the account, etc.), the authentication application 123 does not verify the encrypted customer ID 132 and informs the account application 113 of the failed verification. The account application 113 may then reject the request to initiate the transfer of funds.
- an expected result e.g., the customer ID 107 of the account, etc.
- the authentication application 123 If the authentication application 123 successfully decrypts the encrypted customer ID 132 to yield an expected result (e.g., the customer ID 107 of the account, etc.), the authentication application 123 verifies the encrypted customer ID 132 and transmits an indication of the verification of the encrypted customer ID 132 to the account application 113 .
- an expected result e.g., the customer ID 107 of the account, etc.
- the account application 113 may reference the rules 115 to determine which type of data is required to authorize the requested transfer of funds.
- the rules 115 may specify that fund transfers require verification of the encrypted customer ID 132 and verification based on the passport data 108 .
- the type of data specified by the rules 115 is based on the type of requested operation (e.g., the transfer of funds).
- the rules 115 may specify different levels of security for different types of transaction (e.g., requiring verification of passport data 108 for higher risk operations, while not requiring verification of the passport data 108 for lower risk operations).
- the account application 113 may output another indication to tap the contactless card 101 to the device 110 .
- the account application 113 may instruct the contactless card 101 to transmit the passport data 108 .
- the applet 103 may then transmit the passport data 108 to the mobile device 110 , e.g., via NFC.
- the account application 113 may then output an indication instructing the user to capture an image depicting their face.
- the user may then capture an image depicting their face using the camera 119 .
- the account application 113 may then compare the captured image to a passport image in the passport data 108 to determine a similarity of the persons depicted in each image. If the account application 113 determines that the similarity of the persons depicted in the images exceeds a threshold similarity specified in the rules 115 , the account application 113 may authorize the requested fund transfer operation. Otherwise, the account application 113 may reject the requested fund transfer operation and restrict access to the GUI of the account application 113 to perform fund transfers. In the example depicted in FIG. 2 B , the similarity exceeds the threshold, and the account application 113 permits performance of the requested transfer. The user may then proceed to complete the transfer of funds using a corresponding GUI of the account application 113 .
- FIG. 3 A is a schematic 300 illustrating an example embodiment of tapping the contactless card 101 to provide secure authentication based on identity data stored in the contactless card 101 .
- the contactless card 101 may be used as a form of payment for a purchase and the system 100 may use identity data stored in the contactless card to provide secure authentication when processing the payment. While an in-person transaction is depicted as a reference example, the disclosure is equally applicable to online transactions.
- a merchant device 301 display 302 outputs an indication specifying that an age-restricted item has been identified as part of the requested purchase and the age of the customer must be provided to complete the requested purchase.
- the merchant device 301 is representative of any type of device that can process payments, such as card reader devices, smartphones, tablet computers, desktop computers, point of sale (POS) terminals, servers, workstations, laptop computers, and the like.
- the merchant device 301 includes a communications interface 303 configured to communicate via one or more of NFC, Bluetooth, RFID, and/or Wi-Fi. Therefore, the merchant device 301 may communicate with the contactless card 101 and/or the mobile device 110 .
- the communications interface 118 of the mobile device 110 operates in NFC card-emulation mode to emulate the contactless card 101 and pay for a transaction via the merchant device 301 .
- the account application 113 may receive an indication from the merchant device 301 specifying that verification of the customer's age is needed. The account application 113 may then output an indication specifying to tap the contactless card 101 to the device 110 . Once the customer taps the contactless card 101 to the mobile device 110 , the applet 103 of the contactless card 101 generates the encrypted customer ID 132 . The applet 103 may then transmit the encrypted customer ID 132 to the mobile device 110 , e.g., via NFC. In the embodiment depicted in FIGS. 3 A- 3 C , the contactless card 101 also encrypts and transmits the driver's license data 109 to the mobile device 110 with the encrypted customer ID 132 .
- the account application 113 may transmit the encrypted customer ID 132 and the driver's license data to the authentication application 123 .
- the authentication application 123 may then decrypt the encrypted customer ID 132 , thereby verifying the encrypted customer ID 132 .
- the authentication application 123 may further decrypt the driver's license data 109 .
- FIG. 3 B illustrates an embodiment where the account application 113 receives an indication from the authentication application 123 that the encrypted customer ID 132 was validated.
- the account application 113 may further receive the decrypted driver's license data 109 from the authentication application 123 .
- the account application 113 (and/or the authentication application 123 ) may read the driver's license data 109 to determine the customer's age (e.g., based on a difference between a current date and a date of birth specified in the driver's license data 109 ). If the determined age exceeds the minimum age for purchasing the age-restricted item, the account application 113 transmits an indication of verification 310 to the merchant device 301 .
- the account application 113 transmits the relevant driver's license data 109 (e.g., date of birth) to the merchant device 301 . Doing so allows the merchant device 301 to independently verify that the customer is of the requisite age to purchase the age-restricted item.
- the relevant driver's license data 109 e.g., date of birth
- FIG. 3 C illustrates an embodiment where the account application 113 instructs the user to tap the contactless card 101 to the mobile device 110 to complete the payment for the purchase based on the verification of the encrypted customer ID 132 by the authentication application 123 and the verification of the customer's age.
- the communications interface 118 of the mobile device 110 acting in NFC card-emulation mode, may cause the applet 103 of the contactless card 101 to transmit payment information (e.g., a card number, expiration date, and/or card verification value (CVV)) to the account application 113 .
- the payment information includes an encrypted customer ID 132 , which is transmitted by the account application 113 to the server 120 for verification.
- the account application 113 transmits the received payment information to the merchant device 301 as payment data 311 .
- the merchant device 301 may then process the transaction using the received payment data 311 .
- FIG. 4 A illustrates a contactless card 101 , which may comprise a payment card, such as a credit card, debit card, and/or a gift card.
- the contactless card 101 may be issued by a service provider 405 displayed on the front or back of the card 101 .
- the contactless card 101 is not related to a payment card, and may comprise, without limitation, an identification card.
- the payment card may comprise a dual interface contactless payment card.
- the contactless card 101 may comprise a substrate 410 , 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 contactless card 101 may have physical characteristics compliant with the ID-1 format of the ISO/IEC 7810 standard, and the contactless card may otherwise be compliant with the ISO/IEC 14443 standard. However, it is understood that the contactless card 101 according to the present disclosure may have different characteristics, and the present disclosure does not require a contactless card to be implemented in a payment card.
- the contactless card 101 may also include identification information 415 displayed on the front and/or back of the card, and a contact pad 420 .
- the contact pad 420 may be configured to establish contact with another communication device, such as the mobile devices 40 , a user device, smart phone, laptop, desktop, or tablet computer.
- the contactless card 101 may also include processing circuitry, antenna and other components not shown in FIG. 4 A . These components may be located behind the contact pad 420 or elsewhere on the substrate 410 .
- the contactless card 101 may also include a magnetic strip or tape, which may be located on the back of the card (not shown in FIG. 4 A ).
- the contact pad 420 of contactless card 101 may include processing circuitry 425 for storing and processing information, including a microprocessor 430 and the memory 102 . It is understood that the processing circuitry 425 may contain additional components, including processors, memories, error and parity/CRC checkers, data encoders, anti-collision algorithms, controllers, command decoders, security primitives and tamper proofing hardware, as necessary to perform the functions described herein.
- the memory 102 may be a read-only memory, write-once read-multiple memory or read/write memory, e.g., RAM, ROM, and EEPROM, and the contactless card 101 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. A read/write memory may also be read many times after leaving the factory.
- the memory 102 may be configured to store one or more applets 103 , the counter 104 , master key 105 , the diversified key 106 , one or more customer (or user) IDs 107 , the passport data 108 , the driver's license data 109 , and the other user data 131 .
- the one or more applets 103 may comprise one or more software applications configured to execute on one or more contactless cards, such as a Java® Card applet. However, it is understood that applets 103 are not limited to Java Card applets, and instead may be any software application operable on contactless cards or other devices having limited memory.
- the customer ID 107 may comprise a unique alphanumeric identifier assigned to a user of the contactless card 101 , and the identifier may distinguish the user of the contactless card from other contactless card users. In some examples, the customer ID 107 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. In some embodiments, the applet 103 may use the customer ID 107 as input to a cryptographic algorithm with the keys 105 and/or 106 to generate the encrypted customer ID 132 .
- 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 pad 420 or entirely separate from it, or as further elements in addition to processor 430 and memory 102 elements located within the contact pad 420 .
- the contactless card 101 may comprise one or more antennas 455 .
- the one or more antennas 455 may be placed within the contactless card 101 and around the processing circuitry 425 of the contact pad 420 .
- the one or more antennas 455 may be integral with the processing circuitry 425 and the one or more antennas 455 may be used with an external booster coil.
- the one or more antennas 455 may be external to the contact pad 420 and the processing circuitry 425 .
- the coil of contactless card 101 may act as the secondary of an air core transformer.
- the terminal may communicate with the contactless card 101 by cutting power or amplitude modulation.
- the contactless card 101 may infer the data transmitted from the terminal using the gaps in the contactless card's power connection, which may be functionally maintained through one or more capacitors.
- the contactless card 101 may communicate back by switching a load on the contactless card's coil or load modulation. Load modulation may be detected in the terminal's coil through interference. More generally, using the antennas 455 , processing circuitry 425 , and/or the memory 102 , the contactless card 101 provides a communications interface to communicate via NFC, Bluetooth, and/or Wi-Fi communications.
- contactless cards 101 may be built on a software platform operable on smart cards or other devices having limited memory, such as JavaCard, and one or more or more applications or applets may be securely executed. Applets may be added to contactless cards to provide a one-time password (OTP) for multifactor authentication (MFA) in various mobile application-based use cases. Applets may be configured to respond to one or more requests, such as near field data exchange requests, from a reader, such as a mobile NFC reader (e.g., the communications interface 118 of the device 110 ), and produce an NDEF message that comprises a cryptographically secure OTP encoded as an NDEF text tag.
- OTP one-time password
- MFA multifactor authentication
- FIG. 1 Some of the figures may include a logic flow. Although such figures presented herein may include a particular logic flow, it can be appreciated that the logic flow merely provides an example of how the general functionality as described herein can be implemented. Further, a given logic flow does not necessarily have to be executed in the order presented unless otherwise indicated. In addition, the given logic flow may be implemented by a hardware element, a software element executed by a processor, or any combination thereof. The embodiments are not limited in this context.
- FIG. 5 illustrates an embodiment of a logic flow 500 .
- the logic flow 500 may be representative of some or all of the operations executed by one or more embodiments described herein.
- the logic flow 500 may include some or all of the operations to use the contactless card 101 to provide secure authentication based on identity data stored in the contactless card 101 .
- Embodiments are not limited in this context.
- the logic flow 500 begins at block 505 , where the account application 113 receives a request to perform an operation.
- the requested operation may be received based on input from a user of the account application 113 , an external source (e.g., the merchant device 301 ), one of the other applications 114 , or any other source.
- the request may be related to, for example and without limitation, use of the account application 113 , use of the other applications 114 , operations related to the account associated with the contactless card 101 , and/or a transaction. More generally, the request may be received subsequent to a user providing authentication credentials required to access the account in the account application 113 .
- a user taps the contactless card 101 to the mobile device 110 to cause the applet 103 of the contactless card 101 to generate and transmit the encrypted customer ID 132 to the mobile device 110 .
- the account application 113 may receive the encrypted customer ID 132 from the contactless card 101 .
- the account application 113 may then transmit the encrypted customer ID 132 received from the contactless card 101 to the authentication server 120 .
- the server 120 may attempt to decrypt the encrypted customer ID 132 as described herein.
- the account application 113 receives an indication from the server 120 that the encrypted customer ID 132 was verified by decrypting the encrypted customer ID 132 .
- the account application 113 determines a type of the request.
- the account application 113 determines a type of verification data specified in the rules 115 required to authorize the type of operation.
- the passport data 108 may be specified as the verification data required by the rules 115 .
- the user taps the contactless card 101 to the mobile device 110 . Doing so instructs the applet 103 of the contactless card 101 to transmit the passport data 108 to the mobile device 110 .
- the account application 113 may receive the additional data (e.g., the passport data 108 ) from the contactless card 101 at block 535 .
- the account application 113 may receive the additional data from the contactless card 101 .
- the account application 113 may process the data received at block 540 .
- the account application 113 may perform any age-verification, account verification, and/or identify verification specified by the rules 115 .
- the account application 113 and/or the authentication server 120 may verify a digital signature of the received data.
- the account application 113 determines that the processed data satisfies the rules 115 .
- the account application 113 permits performance of the requested operation based on the verification of the encrypted customer ID 132 by the server 120 and the determination that the processed data received at block 535 satisfies the rules 115 .
- the requested operation may be performed, e.g., by the user and/or by the account application 113 .
- FIG. 6 illustrates an embodiment of a logic flow 600 .
- the logic flow 600 may be representative of some or all of the operations executed by one or more embodiments described herein.
- the logic flow 600 may include some or all of the operations to provide authentication based on the passport data 108 stored in the contactless card 101 .
- Embodiments are not limited in this context.
- the logic flow 600 begins at block 610 , where the account application 113 determines that the rules 115 require passport-based verification based on the type of the requested operation.
- the account application 113 outputs an instruction to the user to capture an image depicting at least the face of the user.
- the account application 113 receives the image captured by the camera 119 of the mobile device 110 .
- the account application 113 compares the captured image received at block 630 to one or more images associated with the passport in the passport data 108 and determines that a similarity of the persons depicted in each image exceeds a threshold level of similarity specified by the rules 115 .
- the account application 113 determines, based on the determination at block 640 , that the user depicted in the captured image matches the person depicted in the passport image of the passport data 108 .
- the account application 113 permits performance of the requested operation based at least in part on the determinations that the user depicted in the captured image matches the person depicted in the passport image of the passport data 108 and/or that the determined similarity exceeds the threshold specified by the rules 115 .
- the logic flow 600 relates to an image in the passport data 108
- the logic flow 600 is equally applicable to image-based verification using an image of the user in the driver's license data 109 . Therefore, the account application 113 may determine whether the user in the captured image matches a user depicted in the driver's license data 109 . Embodiments are not limited in these contexts.
- FIG. 7 illustrates an embodiment of a logic flow 700 .
- the logic flow 700 may be representative of some or all of the operations executed by one or more embodiments described herein.
- the logic flow 700 may include some or all of the operations to provide authentication based on the driver's license data 109 stored in the contactless card 101 .
- Embodiments are not limited in this context.
- the logic flow 700 begins at block 710 , where the account application 113 receives an indication from a merchant device 301 specifying that age verification is required to purchase an age-restricted item.
- the account application 113 receives the driver's license data 109 from the contactless card 101 based on a tap of the card 101 to the mobile device 110 .
- the account application 113 processes the driver's license data 109 to determine the age of the associated person, e.g., based on a date of birth included in the driver's license data.
- the account application 113 determines that the age of the person determined at block 730 exceeds a minimum age threshold. At block 750 , the account application 113 transmits an indication that the person's age exceeds the threshold. Additionally and/or alternatively, the account application 113 may transmit the age and/or the driver's license data 109 to the merchant device 301 for processing and verification.
- the account application 113 receives payment data from the contactless card 101 responsive to a tap of the contactless card 101 to the mobile device 110 .
- the account application 113 transmits the payment data to the merchant device 301 .
- the merchant device 301 may process the transaction using the received payment data. In some embodiments, the merchant device 301 transmits a payment confirmation to the account application 113 .
- FIG. 8 illustrates an embodiment of an exemplary computing architecture 800 comprising a computing system 802 that may be suitable for implementing various embodiments as previously described.
- the computing architecture 800 may comprise or be implemented as part of an electronic device.
- the computing architecture 800 may be representative, for example, of a system that implements one or more components of the system 100 .
- computing system 802 may be representative, for example, of the contactless card 101 , mobile devices 110 , and authentication server 120 of the system 100 .
- the embodiments are not limited in this context. More generally, the computing architecture 800 is configured to implement all logic, applications, systems, methods, apparatuses, and functionality described herein with reference to FIGS. 1 - 7 .
- a component can be, but is not limited to being, a process running on a computer processor, a computer processor, a hard disk drive, multiple storage drives (of optical and/or magnetic storage medium), an object, an executable, a thread of execution, a program, and/or a computer.
- a component can be, but is not limited to being, a process running on a computer processor, a computer processor, a hard disk drive, multiple storage drives (of optical and/or magnetic storage medium), an object, an executable, a thread of execution, a program, and/or a computer.
- an application running on a server and the server can be a component.
- One or more components can reside within a process and/or thread of execution, and a component can be localized on one computer and/or distributed between two or more computers. Further, components may be communicatively coupled to each other by various types of communications media to coordinate operations. The coordination may involve the uni-directional or bi-directional exchange of information. For instance, the components may communicate information in the form of signals communicated over the communications media. The information can be implemented as signals allocated to various signal lines. In such allocations, each message is a signal. Further embodiments, however, may alternatively employ data messages. Such data messages may be sent across various connections. Exemplary connections include parallel interfaces, serial interfaces, and bus interfaces.
- the computing system 802 includes various common computing elements, such as one or more processors, multi-core processors, co-processors, memory units, chipsets, controllers, peripherals, interfaces, oscillators, timing devices, video cards, audio cards, multimedia input/output (I/O) components, power supplies, and so forth.
- processors multi-core processors
- co-processors memory units
- chipsets controllers
- peripherals peripherals
- oscillators oscillators
- timing devices video cards
- audio cards audio cards
- multimedia input/output (I/O) components power supplies, and so forth.
- the embodiments are not limited to implementation by the computing system 802 .
- the computing system 802 comprises a processor 804 , a system memory 806 and a system bus 808 .
- the processor 804 can be any of various commercially available computer processors, including without limitation an AMD® Athlon®, Duron® and Opteron® processors; ARM® application, embedded and secure processors; IBM® and Motorola® DragonBall® and PowerPC® processors; IBM and Sony® Cell processors; Intel® Celeron®, Core®, Core (2) Duo®, Itanium®, Pentium®, Xeon®, and XScale® processors; and similar processors. Dual microprocessors, multi-core processors, and other multi processor architectures may also be employed as the processor 804 .
- the system bus 808 provides an interface for system components including, but not limited to, the system memory 806 to the processor 804 .
- the system bus 808 can be any of several types of bus structure that may further interconnect to a memory bus (with or without a memory controller), a peripheral bus, and a local bus using any of a variety of commercially available bus architectures.
- Interface adapters may connect to the system bus 808 via a slot architecture.
- Example slot architectures may include without limitation Accelerated Graphics Port (AGP), Card Bus, (Extended) Industry Standard Architecture ((E)ISA), Micro Channel Architecture (MCA), NuBus, Peripheral Component Interconnect (Extended) (PCI(X)), PCI Express, Personal Computer Memory Card International Association (PCMCIA), and the like.
- the system memory 806 may include various types of computer-readable storage media in the form of one or more higher speed memory units, such as read-only memory (ROM), random-access memory (RAM), dynamic RAM (DRAM), Double-Data-Rate DRAM (DDRAM), synchronous DRAM (SDRAM), static RAM (SRAM), programmable ROM (PROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), flash memory (e.g., one or more flash arrays), polymer memory such as ferroelectric polymer memory, ovonic memory, phase change or ferroelectric memory, silicon-oxide-nitride-oxide-silicon (SONOS) memory, magnetic or optical cards, an array of devices such as Redundant Array of Independent Disks (RAID) drives, solid state memory devices (e.g., USB memory, solid state drives (SSD) and any other type of storage media suitable for storing information.
- the system memory 806 can include non-volatile memory (EEPROM), flash
- the computing system 802 may include various types of computer-readable storage media in the form of one or more lower speed memory units, including an internal (or external) hard disk drive (HDD) 814 , a magnetic floppy disk drive (FDD) 816 to read from or write to a removable magnetic disk 818 , and an optical disk drive 820 to read from or write to a removable optical disk 822 (e.g., a CD-ROM or DVD).
- the HDD 814 , FDD 816 and optical disk drive 820 can be connected to the system bus 808 by a HDD interface 824 , an FDD interface 826 and an optical drive interface 828 , respectively.
- the HDD interface 824 for external drive implementations can include at least one or both of Universal Serial Bus (USB) and IEEE 1394 interface technologies.
- the computing system 802 is generally is configured to implement all logic, systems, methods, apparatuses, and functionality described herein with reference to FIGS. 1 - 7 .
- the drives and associated computer-readable media provide volatile and/or nonvolatile storage of data, data structures, computer-readable instructions, computer-executable instructions, and so forth.
- a number of program modules can be stored in the drives and memory units 810 , 812 , including an operating system 830 , one or more application programs 832 , other program modules 834 , and program data 836 .
- the one or more application programs 832 , other program modules 834 , and program data 836 can include, for example, the various applications and/or components of the system 100 , e.g., the applet 103 , counter 104 , master key 105 , diversified key 106 , customer ID 107 , passport data 108 , driver's license data 109 , other user data 131 , encrypted customer ID 132 , operating system 112 , account application 113 , other applications 114 , the authentication application 123 , and/or the account data 124 .
- the applet 103 the applet 103
- counter 104 e.g., master key 105 , diversified key 106 , customer ID 107 , passport data 108 , driver's license data 109 , other user data 131 , encrypted customer ID 132 , operating system 112 , account application 113 , other applications 114 , the authentication application 123 , and/or the account data 124 .
- master key 105
- a user can enter commands and information into the computing system 802 through one or more wire/wireless input devices, for example, a keyboard 838 and a pointing device, such as a mouse 840 .
- Other input devices may include microphones, infra-red (IR) remote controls, radio-frequency (RF) remote controls, game pads, stylus pens, card readers, dongles, finger print readers, gloves, graphics tablets, joysticks, keyboards, retina readers, touch screens (e.g., capacitive, resistive, etc.), trackballs, trackpads, sensors, styluses, and the like.
- IR infra-red
- RF radio-frequency
- input devices are often connected to the processor 804 through an input device interface 842 that is coupled to the system bus 808 , but can be connected by other interfaces such as a parallel port, IEEE 1394 serial port, a game port, a USB port, an IR interface, and so forth.
- a monitor 844 or other type of display device is also connected to the system bus 808 via an interface, such as a video adaptor 846 .
- the monitor 844 may be internal or external to the computing system 802 .
- a computer typically includes other peripheral output devices, such as speakers, printers, and so forth.
- the computing system 802 may operate in a networked environment using logical connections via wire and/or wireless communications to one or more remote computers, such as a remote computer 848 .
- the remote computer 848 can be a workstation, a server computer, a router, a personal computer, portable computer, microprocessor-based entertainment appliance, a peer device or other common network node, and typically includes many or all of the elements described relative to the computing system 802 , although, for purposes of brevity, only a memory/storage device 850 is illustrated.
- the logical connections depicted include wire/wireless connectivity to a local area network (LAN) 852 and/or larger networks, for example, a wide area network (WAN) 854 .
- LAN local area network
- WAN wide area network
- the network 130 of FIG. 1 is one or more of the LAN 852 and the WAN 854 .
- the computing system 802 When used in a LAN networking environment, the computing system 802 is connected to the LAN 852 through a wire and/or wireless communication network interface or adaptor 856 .
- the adaptor 856 can facilitate wire and/or wireless communications to the LAN 852 , which may also include a wireless access point disposed thereon for communicating with the wireless functionality of the adaptor 856 .
- the computing system 802 can include a modem 858 , or is connected to a communications server on the WAN 854 , or has other means for establishing communications over the WAN 854 , such as by way of the Internet.
- the modem 858 which can be internal or external and a wire and/or wireless device, connects to the system bus 808 via the input device interface 842 .
- program modules depicted relative to the computing system 802 can be stored in the remote memory/storage device 850 . It will be appreciated that the network connections shown are exemplary and other means of establishing a communications link between the computers can be used.
- the computing system 802 is operable to communicate with wired and wireless devices or entities using the IEEE 802 family of standards, such as wireless devices operatively disposed in wireless communication (e.g., IEEE 802.16 over-the-air modulation techniques).
- wireless communication e.g., IEEE 802.16 over-the-air modulation techniques.
- the communication can be a predefined structure as with a conventional network or simply an ad hoc communication between at least two devices.
- Wi-Fi networks use radio technologies called IEEE 802.11x (a, b, g, n, etc.) to provide secure, reliable, fast wireless connectivity.
- a Wi-Fi network can be used to connect computers to each other, to the Internet, and to wire networks (which use IEEE 802.3-related media and functions).
- Various embodiments may be implemented using hardware elements, software elements, or a combination of both.
- hardware elements may include processors, microprocessors, circuits, circuit elements (e.g., transistors, resistors, capacitors, inductors, and so forth), integrated circuits, application specific integrated circuits (ASIC), programmable logic devices (PLD), digital signal processors (DSP), field programmable gate array (FPGA), logic gates, registers, semiconductor device, chips, microchips, chip sets, and so forth.
- Examples of software may include software components, programs, applications, computer programs, application programs, system programs, machine programs, operating system software, middleware, firmware, software modules, routines, subroutines, functions, methods, procedures, software interfaces, application program interfaces (API), instruction sets, computing code, computer code, code segments, computer code segments, words, values, symbols, or any combination thereof. Determining whether an embodiment is implemented using hardware elements and/or software elements may vary in accordance with any number of factors, such as desired computational rate, power levels, heat tolerances, processing cycle budget, input data rates, output data rates, memory resources, data bus speeds and other design or performance constraints.
- One or more aspects of at least one embodiment may be implemented by representative instructions stored on a machine-readable medium which represents various logic within the processor, which when read by a machine causes the machine to fabricate logic to perform the techniques described herein.
- Such representations known as “IP cores” may be stored on a tangible, machine readable medium and supplied to various customers or manufacturing facilities to load into the fabrication machines that make the logic or processor.
- Some embodiments may be implemented, for example, using a machine-readable medium or article which may store an instruction or a set of instructions that, if executed by a machine, may cause the machine to perform a method and/or operations in accordance with the embodiments.
- Such a machine may include, for example, any suitable processing platform, computing platform, computing device, processing device, computing system, processing system, computer, processor, or the like, and may be implemented using any suitable combination of hardware and/or software.
- the machine-readable medium or article may include, for example, any suitable type of memory unit, memory device, memory article, memory medium, storage device, storage article, storage medium and/or storage unit, for example, memory, removable or non-removable media, erasable or non-erasable media, writeable or re-writeable media, digital or analog media, hard disk, floppy disk, Compact Disk Read Only Memory (CD-ROM), Compact Disk Recordable (CD-R), Compact Disk Rewriteable (CD-RW), optical disk, magnetic media, magneto-optical media, removable memory cards or disks, various types of Digital Versatile Disk (DVD), a tape, a cassette, or the like.
- CD-ROM Compact Disk Read Only Memory
- CD-R Compact Disk Recordable
- CD-RW Compact Dis
- the instructions may include any suitable type of code, such as source code, compiled code, interpreted code, executable code, static code, dynamic code, encrypted code, and the like, implemented using any suitable high-level, low-level, object-oriented, visual, compiled and/or interpreted programming language.
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Accounting & Taxation (AREA)
- Computer Security & Cryptography (AREA)
- Theoretical Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Physics & Mathematics (AREA)
- Strategic Management (AREA)
- General Business, Economics & Management (AREA)
- Finance (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- General Engineering & Computer Science (AREA)
- Computer Hardware Design (AREA)
- Computing Systems (AREA)
- Microelectronics & Electronic Packaging (AREA)
- Health & Medical Sciences (AREA)
- Biomedical Technology (AREA)
- General Health & Medical Sciences (AREA)
- Software Systems (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
- Lock And Its Accessories (AREA)
- Storage Device Security (AREA)
Abstract
Systems, methods, articles of manufacture, and computer-readable media for secure authentication based on identity data stored in a contactless card associated with an account. An application may receive an indication specifying to perform an operation. The application may receive encrypted data from the card. The application may receive an indication that the authentication server decrypted the encrypted data. The application may determine a type of data required to authorize the operation. The application may receive data comprising passport data or driver license data from the card. The application may determine that the data satisfies a rule for authorizing the operation and authorize performance of the operation based on the authentication server verifying the encrypted data and the data satisfying the at least one rule.
Description
- This application is a continuation of U.S. patent application Ser. No. 17/085,721, filed Oct. 30, 2020, which is a continuation of U.S. patent application Ser. No. 16/726,385, titled “SECURE AUTHENTICATION BASED ON IDENTITY DATA STORED IN A CONTACTLESS CARD” filed on Dec. 24, 2019. The contents of the aforementioned application are incorporated herein by reference in their entirety.
- Embodiments herein generally relate to computing platforms, and more specifically, to using a contactless card storing identity data for secure authentication.
- Identity verification is an important task for modern computing systems. Conventional approaches may require that users provide additional information, such as a one-time passcode (OTP), when attempting to access computing systems or perform electronic transactions. However, security vulnerabilities may exist in these solutions. For example, the OTP may be intercepted and used to gain unauthorized access. Furthermore, different systems may require different types of additional information for identity verification, making conventional solutions impractical for many users.
- Embodiments disclosed herein provide systems, methods, articles of manufacture, and computer-readable media for secure authentication based on identity data stored in a contactless card. In one example, an application may receive an indication specifying to perform an operation associated with an account. The application may receive encrypted data from a contactless card associated with the account. The application may receive, from an authentication server, an indication specifying that the authentication server decrypted the encrypted data. The application may determine a type of authentication data required to authorize the operation. The application may receive, based on the determined type of authentication data, a first data element from the contactless card, the first data element comprising passport data or driver license data. The application may determine that the first data element satisfies at least one rule for authorizing the operation. The application may authorize performance of the operation based on the received indication specifying that the authentication server verified the encrypted data and the determination that the first data element satisfies the at least one rule for authorizing the operation.
-
FIGS. 1A-1B illustrate embodiments of a system for secure authentication based on identity data stored in a contactless card. -
FIGS. 2A-2C illustrate embodiments of tapping a contactless card to a computing device to provide secure authentication based on identity data stored in the contactless card. -
FIGS. 3A-3C illustrate embodiments of tapping a contactless card to a computing device to provide secure authentication based on identity data stored in the contactless card. -
FIGS. 4A-4B illustrate an example contactless card. -
FIG. 5 illustrates an embodiment of a first logic flow. -
FIG. 6 illustrates an embodiment of a second logic flow. -
FIG. 7 illustrates an embodiment of a third logic flow. -
FIG. 8 illustrates an embodiment of a computing system. - Embodiments disclosed herein provide techniques for secure authentication using identity data stored in a contactless card. Generally, a contactless card may store a plurality of different types of information for a user, such as driver's license information, passport information, social security number, and/or any other biographical information. The user may then attempt to perform an operation, such as making a purchase, transferring funds via an application executing on a mobile device, requesting a credit increase via the application, and the like. The application may determine a type of authentication data required to authorize the requested operation. For example, a rule may specify that transferring funds via the application requires authentication based on passport data stored in the contactless card. Therefore, the application may determine that passport data as the type of authentication data.
- The user may then tap the contactless card to the mobile device to initiate the secure authentication process. Once tapped, the contactless card may generate and transmit encrypted data to the application. The encrypted data may be generated based on a cryptographic algorithm, a customer identifier, and an encryption key for the contactless card. The application may then transmit the encrypted data to an authentication server for authentication. The server may then decrypt the encrypted data using a local copy of the encryption key for the contactless card to yield the customer identifier, thereby authenticating the encrypted data. The server may then transmit an indication of the authentication of the encrypted data to the application.
- The application may then process the passport data. In some embodiments, the passport data is sent by the contactless card to the application with the encrypted customer identifier. In other embodiments, the passport data is sent by the contactless card subsequent to another tap of the contactless card to the mobile device. To process the passport data, the application may perform any number of operations. For example, the passport data stored on the contactless card may include a passport image depicting the user. In such an example, the application may instruct the user to capture an image depicting their face using the mobile device. Once captured, the application may compare the images to determine a similarity between the images. If the similarity exceeds a threshold level of similarity specified in a rule, the application may authenticate the user and/or validate the identity of the user. The application may then authorize the performance of the operation based on the received indication specifying that the authentication server verified the encrypted data and the determination that the similarity of the images exceeds the threshold level of similarity. For example, the user may be permitted to access an interface of the application to transfer funds from one account to another.
- Advantageously, embodiments disclosed herein improve the security of all devices and associated data. For example, by requiring validation of encrypted data generated by the contactless card to access applications and/or data, the security of the applications and/or data are improved. As another example, by requiring validation of the encrypted data prior to performing operations (e.g., making purchases, extending credit, etc.), the security of such operations and associated assets is improved.
- With general reference to notations and nomenclature used herein, one or more portions of the detailed description which follows may be presented in terms of program procedures executed on a computer or network of computers. These procedural descriptions and representations are used by those skilled in the art to most effectively convey the substances of their work to others skilled in the art. A procedure is here, and generally, conceived to be a self-consistent sequence of operations leading to a desired result. These operations are those requiring physical manipulations of physical quantities. Usually, though not necessarily, these quantities take the form of electrical, magnetic, or optical signals capable of being stored, transferred, combined, compared, and otherwise manipulated. It proves convenient at times, principally for reasons of common usage, to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, or the like. It should be noted, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to those quantities.
- Further, these manipulations are often referred to in terms, such as adding or comparing, which are commonly associated with mental operations performed by a human operator. However, no such capability of a human operator is necessary, or desirable in most cases, in any of the operations described herein that form part of one or more embodiments. Rather, these operations are machine operations. Useful machines for performing operations of various embodiments include digital computers as selectively activated or configured by a computer program stored within that is written in accordance with the teachings herein, and/or include apparatus specially constructed for the required purpose or a digital computer. Various embodiments also relate to apparatus or systems for performing these operations. These apparatuses may be specially constructed for the required purpose. The required structure for a variety of these machines will be apparent from the description given.
- Reference is now made to the drawings, wherein like reference numerals are used to refer to like elements throughout. In the following description, for the purpose of explanation, numerous specific details are set forth in order to provide a thorough understanding thereof. It may be evident, however, that the novel embodiments can be practiced without these specific details. In other instances, well-known structures and devices are shown in block diagram form in order to facilitate a description thereof. The intention is to cover all modification, equivalents, and alternatives within the scope of the claims.
-
FIG. 1A depicts a schematic of anexemplary system 100, consistent with disclosed embodiments. As shown, thesystem 100 includes one or morecontactless cards 101, one or moremobile computing devices 110, and anauthentication server 120. Thecontactless cards 101 are representative of any type of payment cards, such as a credit card, debit card, ATM card, gift card, and the like. Thecontactless cards 101 may comprise one ormore communications interfaces 133, such as a radio frequency identification (RFID) chip, configured to communicate with thecomputing devices 110 via NFC, the EMV standard, or other short-range protocols in wireless communication. Although NFC is used as an example communications protocol, the disclosure is equally applicable to other types of wireless communications, such as the EMV standard, Bluetooth, and/or Wi-Fi. Themobile devices 110 are representative of any type of network-enabled computing devices, such as smartphones, tablet computers, wearable devices, laptops, portable gaming devices, and the like. Theauthentication server 120 is representative of any type of computing device, such as a server, workstation, compute cluster, cloud computing platform, virtualized computing system, and the like. - As shown, a
memory 102 of the contactless card includes anapplet 103, acounter 104, amaster key 105, adiversified key 106, a unique customer identifier (ID) 107,passport data 108, driver'slicense data 109, and other user data 131. Theapplet 103 is executable code configured to perform the operations described herein. Thecounter 104,master key 105,diversified key 106, and customer ID 107 are used to provide security in thesystem 100 as described in greater detail below. Thepassport data 108 is representative of an electronic passport of a user associated with thecontactless card 101. Thepassport data 108 may include any number and types of data. For example, thepassport data 108 may include text data describing different attributes of the passport and/or user (e.g., name, date of birth, passport number, passport issue date, passport expiration date, issuing nation, etc.) as well as image data (e.g., one or more images of the passport itself, an image of the user included in the passport, etc.). The customer ID 107,passport data 108, driver'slicense data 109, and other user data 131 may collectively be referred to herein as “identity data.” - The driver's
license data 109 is representative of one or more driver's licenses held by the user associated with the contactless card. As with thepassport data 108, the driver'slicense data 109 may include any number and types of data. For example, the driver'slicense data 109 may include a barcode (or other computer-readable marker) that encodes different attributes of the driver's license and/or user (e.g., name, date of birth, license number, license issue date, expiration date, issuing state, etc.), text data representing the attributes (and/or the barcode), and/or image data (e.g., one or more images of the driver's license, an image of the user included in the driver's license, etc.). The other user data 131 is representative of other data describing the user. For example, the other user data 131 may include social security numbers, images, data representing biometric identifiers of the user, other identification cards, loyalty program information, and the like. In some embodiments, thepassport data 108, driver'slicense data 109, and other user data 131 are encrypted. - As shown, a
memory 111 of themobile device 110 includes an instance of an operating system (OS) 112. Example operating systems 112 include the Android® OS, iOS®, macOS®, Linux®, and Windows® operating systems. As shown, the OS 112 includes anaccount application 113. Theaccount application 113 allows users to perform various account-related operations, such as viewing account balances, purchasing items, processing payments, and the like. Theaccount application 113 may further control access permissions to different functions provided by theaccount application 113 and/or theother applications 114. Generally, a user may authenticate using authentication credentials to access certain features of theaccount application 113. For example, the authentication credentials may include a username (or login) and password, biometric credentials (e.g., fingerprints, Face ID, etc.), and the like. - According to various embodiments, the user may request and/or attempt to perform an operation. The operation may include any type of operation, such as using the
contactless card 101 to make a purchase, accessing certain features of theaccount application 113, performing various account-related operations using theaccount application 113, and/or accessing the other applications 114 (or any feature thereof). Theother applications 114 are representative of any type of computing application, such as web browsers, messaging applications, word processing applications, social media applications, and the like. For example, the user may desire to transfer funds from their account to another account using theaccount application 113. The use of a specific operation as a reference example herein is not limiting of the disclosure, as the disclosure is equally applicable to any other type of operation. - To authorize the requested operation, (e.g., the previous example of transferring funds), the
system 100 must authenticate and/or verify the identity of the user. To authenticate the identity of the user, embodiments disclosed herein may leverage thecontactless card 101. More specifically, once the user requests to perform the operation (or otherwise access a restricted resource), theaccount application 113 may output a notification instructing the user to tap thecontactless card 101 to thedevice 110. Generally, once thecontactless card 101 is brought within communications range of thecommunications interface 118 of thedevice 110, theapplet 103 of thecontactless card 101 may generate encrypted data, e.g., an encrypted customer ID 132 as part of the authentication process required to authorize the requested operation. To enable NFC data transfer between thecontactless card 101 and themobile device 110, theaccount application 113 may communicate with thecontactless card 101 when thecontactless card 101 is sufficiently close to thecommunications interface 118 of themobile device 110. Thecommunications interface 118 may be configured to read from and/or communicate with thecommunications interface 133 of the contactless card 101 (e.g., via NFC, Bluetooth, RFID, etc.). Therefore,example communications interfaces 118 include NFC communication modules, Bluetooth communication modules, and/or RFID communication modules. - As stated, the
system 100 is configured to implement key diversification to secure data, which may be referred to as a key diversification technique herein. Generally, the server 120 (or another computing device) and thecontactless card 101 may be provisioned with the same master key 105 (also referred to as a master symmetric key). More specifically, eachcontactless card 101 is programmed with adistinct master key 105 that has a corresponding pair in theserver 120. For example, when acontactless card 101 is manufactured, aunique master key 105 may be programmed into thememory 102 of thecontactless card 101. Similarly, theunique master key 105 may be stored in a record of a customer associated with thecontactless card 101 in theaccount data 124 of the server 120 (and/or stored in a different secure location, such as the hardware security module (HSM) 125). The master key may be kept secret from all parties other than thecontactless card 101 andserver 120, thereby enhancing security of thesystem 100. In some embodiments, theapplet 103 of thecontactless card 101 may encrypt and/or decrypt data (e.g., the customer ID 107,passport data 108, driver'slicense data 109, and/or other user data 131) using themaster key 105 and the data as input a cryptographic algorithm. For example, encrypting the customer ID 107 with themaster key 105 may result in the encrypted customer ID 132. Similarly, theauthentication server 120 may encrypt and/or decrypt data associated with thecontactless card 101 using the correspondingmaster key 105. - In other embodiments, the
master keys 105 of thecontactless card 101 andserver 120 may be used in conjunction with thecounters 104 to enhance security using key diversification. Thecounters 104 comprise values that are synchronized between thecontactless card 101 andserver 120. Thecounter value 104 may comprise a number that changes each time data is exchanged between thecontactless card 101 and the server 120 (and/or thecontactless card 101 and the mobile device 110). When preparing to send data (e.g., to theserver 120 and/or the mobile device 110), thecontactless card 101 may increment thecounter value 104. Thecontactless card 101 may then provide themaster key 105 andcounter value 104 as input to a cryptographic algorithm, which produces adiversified key 106 as output. The cryptographic algorithm may include encryption algorithms, hash-based message authentication code (HMAC) algorithms, cipher-based message authentication code (CMAC) algorithms, and the like. Non-limiting examples of the cryptographic algorithm may include a symmetric encryption algorithm such as 3DES or AES128; a symmetric HMAC algorithm, such as HMAC-SHA-256; and a symmetric CMAC algorithm such as AES-CMAC. Examples of key diversification techniques are described in greater detail in U.S. patent application Ser. No. 16/205,119, filed Nov. 29, 2018. The aforementioned patent application is incorporated by reference herein in its entirety. - Continuing with the key diversification example, the
contactless card 101 may then encrypt the data (e.g., the customer ID 107 and/or any other data, such as thepassport data 108, driver'slicense data 109, and/or other user data 131) using thediversified key 106 and the data as input to the cryptographic algorithm. For example, encrypting the customer ID 107 with thediversified key 106 may result in the encrypted customer ID 132. - Regardless of the encryption technique used, the
contactless card 101 may then transmit the encrypted data (e.g., the encrypted customer ID 132) to theaccount application 113 of the mobile device 110 (e.g., via an NFC connection, Bluetooth connection, etc.). Theaccount application 113 of themobile device 110 may then transmit the encrypted customer ID 132 to theserver 120 via thenetwork 130. In at least one embodiment, thecontactless card 101 transmits thecounter value 104 with the encrypted data. In such embodiments, thecontactless card 101 may transmit anencrypted counter value 104, or anunencrypted counter value 104. - Once received, the
authentication application 123 may authenticate the encrypted customer ID 132. For example, theauthentication application 123 may attempt to decrypt the encrypted customer ID 132 using a copy of themaster key 105 stored in thememory 122 of theauthentication server 120. In another example, theauthentication application 123 may provide themaster key 105 andcounter value 104 as input to the cryptographic algorithm, which produces adiversified key 106 as output. The resultingdiversified key 106 may correspond to thediversified key 106 of thecontactless card 101, which may be used to decrypt the encrypted customer ID 132. - Regardless of the decryption technique used, the
authentication application 123 may successfully decrypt the encrypted customer ID 132, thereby verifying the encrypted customer ID 132 (e.g., by comparing the resulting customer ID 107 to a customer ID stored in theaccount data 124, and/or based on an indication that the decryption using the key 105 and/or 106 was successful). Although thekeys memory 122, thekeys HSM 125. In such embodiments, the secure element and/or theHSM 125 may decrypt the encrypted customer ID 132 using thekeys 105 and/or 106 and a cryptographic function. Similarly, the secure element and/orHSM 125 may generate thediversified key 106 based on themaster key 105 andcounter value 104 as described above. - If, however, the
authentication application 123 is unable to decrypt the encrypted customer ID 132 to yield the expected result (e.g., the customer ID 107 of the account associated with the contactless card 101), theauthentication application 123 does not validate the encrypted customer ID 132. In such an example, theauthentication application 123 transmits an indication of the failed verification to theaccount application 113. As such, theaccount application 113 may reject performance of the requested operation to preserve the security of the account. -
FIG. 1B illustrates an embodiment where theauthentication application 123 has decrypted the encrypted customer ID 132, thereby verifying (or authenticating) the encrypted data. As shown, theauthentication application 123 transmits averification 134 to themobile device 110, where theverification 134 indicates that theauthentication application 123 successfully decrypted the encrypted customer ID 132. Responsive to receiving theverification 134, theaccount application 113 may reference therules 115 to determine what, if any, additional authentication steps are required. Therules 115 may generally specify a plurality of different authentication rules and/or thresholds for different requested operations. The rules may be based on the type of requested operation. For example, for the transfer of funds, therules 115 may require additional authentication based on additional data elements such as thepassport data 108 and/or the driver'slicense data 109. - In the example where additional authentication is based on the
passport data 108, theaccount application 113 may output an indication specifying that the user tap thecontactless card 101 to themobile device 110. Theaccount application 113 may then instruct thecontactless card 101 to transmit thepassport data 108. In response, thecontactless card 101 may transmit thepassport data 108 to theaccount application 113. In some embodiments, thepassport data 108 may be encrypted. In such embodiments, theaccount application 113 may transmit theencrypted passport data 108 to theserver 120 for decryption (e.g., based on thekeys 105 and/or 106), which then sends the decryptedpassport data 108 to theaccount application 113. In another embodiment, the user may provide input to theaccount application 113 used to decrypt theencrypted passport data 108. - Furthermore, the
account application 113 may instruct the user to capture an image depicting themselves using thecamera 119. Theaccount application 113 may then compare the captured image to a passport image in thepassport data 108 to determine a similarity of the persons depicted in each image. If theaccount application 113 determines that the similarity of the persons depicted in the images exceeds a threshold similarity specified in therules 115, theaccount application 113 may authorize the requested operation. The user may then proceed to complete the transfer of funds using theaccount application 113. - As stated, in another example, the
rules 115 may require authentication based on the driver'slicense data 109. Theaccount application 113 may then output an indication specifying that the user tap thecontactless card 101 to themobile device 110. Theaccount application 113 may then instruct thecontactless card 101 to transmit the driver'slicense data 109. In response, thecontactless card 101 may transmit the driver'slicense data 109 to theaccount application 113. In some embodiments, the driver'slicense data 109 may be encrypted. Otherwise, theaccount application 113 may restrict performance of the operation (e.g., by restricting access to the graphical user interface (GUI) of theaccount application 113 used to transfer funds). In such embodiments, theaccount application 113 may transmit the encrypted driver'slicense data 109 to theserver 120 for decryption, which then sends the decrypted driver'slicense data 109 to theaccount application 113. - As with the passport-based authentication, the
account application 113 then may instruct the user to capture an image depicting themselves using thecamera 119. Theaccount application 113 may then compare the captured image to a driver's license image in the driver'slicense data 109 to determine a similarity of the persons depicted in each image. If theaccount application 113 determines that the similarity of the persons depicted in the images exceeds a threshold similarity specified in therules 115, theaccount application 113 may authorize the requested operation. Otherwise, theaccount application 113 may restrict performance of the operation (e.g., by restricting access to the GUI of theaccount application 113 used to transfer funds). The user may then proceed to complete the transfer of funds using theaccount application 113. - Although image-based authentication is used as an example, other data elements may be used to authorize the requested operation. For example, the
account application 113 may determine whether the name on the passport and/or driver's license matches a name on the account associated with thecontactless card 101. As another example, theaccount application 113 may determine whether data encoded in the driver'slicense data 109 is readable. As yet another example, theaccount application 113 may determine whether a date of birth in passport and/or driver's license matches known a date of birth, e.g., a date of birth specified in theaccount data 124 for the account associated with thecontactless card 101. In another example, a social security number stored in the other user data 131 may be compared to a known social security number of the user associated with the account. If a matching name and/or social security number is found, theaccount application 113 may authorize the attempted operation. Otherwise, theaccount application 113 may reject the attempted operation. - In at least one embodiment, the
applet 103 of thecontactless card 101 may generate a digital signature (not pictured) for thepassport data 108 and/or the driver'slicense data 109 using thekeys 105 and/or 106. A respective digital signature may sign thepassport data 108 and/or driver'slicense data 109. Thecontactless card 101 may then transmit the digital signatures with thepassport data 108 and/or driver'slicense data 109 to theaccount application 113, which in turn transmits the digital signatures to theauthentication server 120. Theauthentication application 123 may also verify the digital signature by decrypting the digital signature using a public key associated with thecontactless card 101 and stored by theserver 120. If the digital signature is verified, theauthentication application 123 may transmit an indication of the successful verification to theaccount application 113, which may permit performance of the operation based on verification of the digital signature. If the digital signature is not verified, theaccount application 113 may restrict performance of the operation. - Although depicted in
FIGS. 1A-1B as occurring in separate tap operations, in some embodiments, thepassport data 108 and/or the driver'slicense data 109 may be transmitted with the encrypted customer ID 132 responsive to a single tap of thecontactless card 101 to themobile device 110. - Furthermore, in some embodiments, the user may obtain new and/or updated identification information, such as a passport, driver's license, etc. In such embodiments, the
account application 113 may receive the new and/or updated versions of thepassport data 108, driver'slicense data 109, and/or other user data 131, e.g., from theauthentication server 120. In such embodiments, theaccount application 113 may transmit the data received from theserver 120 to thecontactless card 101, and theapplet 103 may store the received data in thememory 102. -
FIG. 2A is a schematic 200 depicting an example embodiment of tapping thecontactless card 101 to provide secure authentication based on identity data stored in thecontactless card 101. As shown, theaccount application 113 may receive a request to perform an operation. Continuing with the previous example, the request may be to transfer funds from one account to another account. In response, theaccount application 113 may output an indication to tap thecontactless card 101 to thedevice 110. Once the user taps thecontactless card 101 to themobile device 110, theapplet 103 of thecontactless card 101 generates the encrypted customer ID 132. Theapplet 103 may then transmit the encrypted customer ID 132 to themobile device 110, e.g., via NFC. Once received, theaccount application 113 may transmit the encrypted customer ID 132 to theauthentication application 123. - The
authentication application 123 may then attempt to decrypt the encrypted customer ID 132 using themaster key 105 and/or thediversified key 106 associated with thecontactless card 101. If theauthentication application 123 is unable to decrypt the encrypted customer ID 132 to yield an expected result (e.g., the customer ID 107 of the account, etc.), theauthentication application 123 does not verify the encrypted customer ID 132 and informs theaccount application 113 of the failed verification. Theaccount application 113 may then reject the request to initiate the transfer of funds. If theauthentication application 123 successfully decrypts the encrypted customer ID 132 to yield an expected result (e.g., the customer ID 107 of the account, etc.), theauthentication application 123 verifies the encrypted customer ID 132 and transmits an indication of the verification of the encrypted customer ID 132 to theaccount application 113. - Responsive to receiving the verification from the
authentication application 123, theaccount application 113 may reference therules 115 to determine which type of data is required to authorize the requested transfer of funds. For example, therules 115 may specify that fund transfers require verification of the encrypted customer ID 132 and verification based on thepassport data 108. In at least one embodiment, the type of data specified by therules 115 is based on the type of requested operation (e.g., the transfer of funds). Generally, therules 115 may specify different levels of security for different types of transaction (e.g., requiring verification ofpassport data 108 for higher risk operations, while not requiring verification of thepassport data 108 for lower risk operations). - The
account application 113 may output another indication to tap thecontactless card 101 to thedevice 110. Theaccount application 113 may instruct thecontactless card 101 to transmit thepassport data 108. Theapplet 103 may then transmit thepassport data 108 to themobile device 110, e.g., via NFC. - As shown in the schematic 210 of
FIG. 2B , theaccount application 113 may then output an indication instructing the user to capture an image depicting their face. The user may then capture an image depicting their face using thecamera 119. Theaccount application 113 may then compare the captured image to a passport image in thepassport data 108 to determine a similarity of the persons depicted in each image. If theaccount application 113 determines that the similarity of the persons depicted in the images exceeds a threshold similarity specified in therules 115, theaccount application 113 may authorize the requested fund transfer operation. Otherwise, theaccount application 113 may reject the requested fund transfer operation and restrict access to the GUI of theaccount application 113 to perform fund transfers. In the example depicted inFIG. 2B , the similarity exceeds the threshold, and theaccount application 113 permits performance of the requested transfer. The user may then proceed to complete the transfer of funds using a corresponding GUI of theaccount application 113. -
FIG. 3A is a schematic 300 illustrating an example embodiment of tapping thecontactless card 101 to provide secure authentication based on identity data stored in thecontactless card 101. As stated, thecontactless card 101 may be used as a form of payment for a purchase and thesystem 100 may use identity data stored in the contactless card to provide secure authentication when processing the payment. While an in-person transaction is depicted as a reference example, the disclosure is equally applicable to online transactions. - As shown, a
merchant device 301display 302 outputs an indication specifying that an age-restricted item has been identified as part of the requested purchase and the age of the customer must be provided to complete the requested purchase. Themerchant device 301 is representative of any type of device that can process payments, such as card reader devices, smartphones, tablet computers, desktop computers, point of sale (POS) terminals, servers, workstations, laptop computers, and the like. Themerchant device 301 includes acommunications interface 303 configured to communicate via one or more of NFC, Bluetooth, RFID, and/or Wi-Fi. Therefore, themerchant device 301 may communicate with thecontactless card 101 and/or themobile device 110. In some embodiments, thecommunications interface 118 of themobile device 110 operates in NFC card-emulation mode to emulate thecontactless card 101 and pay for a transaction via themerchant device 301. - Therefore, the
account application 113 may receive an indication from themerchant device 301 specifying that verification of the customer's age is needed. Theaccount application 113 may then output an indication specifying to tap thecontactless card 101 to thedevice 110. Once the customer taps thecontactless card 101 to themobile device 110, theapplet 103 of thecontactless card 101 generates the encrypted customer ID 132. Theapplet 103 may then transmit the encrypted customer ID 132 to themobile device 110, e.g., via NFC. In the embodiment depicted inFIGS. 3A-3C , thecontactless card 101 also encrypts and transmits the driver'slicense data 109 to themobile device 110 with the encrypted customer ID 132. Once received, theaccount application 113 may transmit the encrypted customer ID 132 and the driver's license data to theauthentication application 123. Theauthentication application 123 may then decrypt the encrypted customer ID 132, thereby verifying the encrypted customer ID 132. Theauthentication application 123 may further decrypt the driver'slicense data 109. -
FIG. 3B illustrates an embodiment where theaccount application 113 receives an indication from theauthentication application 123 that the encrypted customer ID 132 was validated. Theaccount application 113 may further receive the decrypted driver'slicense data 109 from theauthentication application 123. The account application 113 (and/or the authentication application 123) may read the driver'slicense data 109 to determine the customer's age (e.g., based on a difference between a current date and a date of birth specified in the driver's license data 109). If the determined age exceeds the minimum age for purchasing the age-restricted item, theaccount application 113 transmits an indication ofverification 310 to themerchant device 301. In some embodiments, theaccount application 113 transmits the relevant driver's license data 109 (e.g., date of birth) to themerchant device 301. Doing so allows themerchant device 301 to independently verify that the customer is of the requisite age to purchase the age-restricted item. -
FIG. 3C illustrates an embodiment where theaccount application 113 instructs the user to tap thecontactless card 101 to themobile device 110 to complete the payment for the purchase based on the verification of the encrypted customer ID 132 by theauthentication application 123 and the verification of the customer's age. The communications interface 118 of themobile device 110, acting in NFC card-emulation mode, may cause theapplet 103 of thecontactless card 101 to transmit payment information (e.g., a card number, expiration date, and/or card verification value (CVV)) to theaccount application 113. In some embodiments, the payment information includes an encrypted customer ID 132, which is transmitted by theaccount application 113 to theserver 120 for verification. Once verified, theaccount application 113 transmits the received payment information to themerchant device 301 aspayment data 311. Themerchant device 301 may then process the transaction using the receivedpayment data 311. -
FIG. 4A illustrates acontactless card 101, which may comprise a payment card, such as a credit card, debit card, and/or a gift card. As shown, thecontactless card 101 may be issued by aservice provider 405 displayed on the front or back of thecard 101. In some examples, thecontactless card 101 is not related to a payment card, and may comprise, without limitation, an identification card. In some examples, the payment card may comprise a dual interface contactless payment card. Thecontactless card 101 may comprise asubstrate 410, 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. In some examples, thecontactless card 101 may have physical characteristics compliant with the ID-1 format of the ISO/IEC 7810 standard, and the contactless card may otherwise be compliant with the ISO/IEC 14443 standard. However, it is understood that thecontactless card 101 according to the present disclosure may have different characteristics, and the present disclosure does not require a contactless card to be implemented in a payment card. - The
contactless card 101 may also includeidentification information 415 displayed on the front and/or back of the card, and acontact pad 420. Thecontact pad 420 may be configured to establish contact with another communication device, such as the mobile devices 40, a user device, smart phone, laptop, desktop, or tablet computer. Thecontactless card 101 may also include processing circuitry, antenna and other components not shown inFIG. 4A . These components may be located behind thecontact pad 420 or elsewhere on thesubstrate 410. Thecontactless card 101 may also include a magnetic strip or tape, which may be located on the back of the card (not shown inFIG. 4A ). - As illustrated in
FIG. 4B , thecontact pad 420 ofcontactless card 101 may include processingcircuitry 425 for storing and processing information, including amicroprocessor 430 and thememory 102. It is understood that theprocessing circuitry 425 may contain additional components, including processors, memories, error and parity/CRC checkers, data encoders, anti-collision algorithms, controllers, command decoders, security primitives and tamper proofing hardware, as necessary to perform the functions described herein. - The
memory 102 may be a read-only memory, write-once read-multiple memory or read/write memory, e.g., RAM, ROM, and EEPROM, and thecontactless card 101 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. A read/write memory may also be read many times after leaving the factory. - The
memory 102 may be configured to store one ormore applets 103, thecounter 104,master key 105, thediversified key 106, one or more customer (or user) IDs 107, thepassport data 108, the driver'slicense data 109, and the other user data 131. The one ormore applets 103 may comprise one or more software applications configured to execute on one or more contactless cards, such as a Java® Card applet. However, it is understood thatapplets 103 are not limited to Java Card applets, and instead may be any software application operable on contactless cards or other devices having limited memory. The customer ID 107 may comprise a unique alphanumeric identifier assigned to a user of thecontactless card 101, and the identifier may distinguish the user of the contactless card from other contactless card users. In some examples, the customer ID 107 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. In some embodiments, theapplet 103 may use the customer ID 107 as input to a cryptographic algorithm with thekeys 105 and/or 106 to generate the encrypted customer ID 132. - 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
pad 420 or entirely separate from it, or as further elements in addition toprocessor 430 andmemory 102 elements located within thecontact pad 420. - In some examples, the
contactless card 101 may comprise one ormore antennas 455. The one ormore antennas 455 may be placed within thecontactless card 101 and around theprocessing circuitry 425 of thecontact pad 420. For example, the one ormore antennas 455 may be integral with theprocessing circuitry 425 and the one ormore antennas 455 may be used with an external booster coil. As another example, the one ormore antennas 455 may be external to thecontact pad 420 and theprocessing circuitry 425. - In an embodiment, the coil of
contactless card 101 may act as the secondary of an air core transformer. The terminal may communicate with thecontactless card 101 by cutting power or amplitude modulation. Thecontactless card 101 may infer the data transmitted from the terminal using the gaps in the contactless card's power connection, which may be functionally maintained through one or more capacitors. Thecontactless card 101 may communicate back by switching a load on the contactless card's coil or load modulation. Load modulation may be detected in the terminal's coil through interference. More generally, using theantennas 455,processing circuitry 425, and/or thememory 102, thecontactless card 101 provides a communications interface to communicate via NFC, Bluetooth, and/or Wi-Fi communications. - As explained above,
contactless cards 101 may be built on a software platform operable on smart cards or other devices having limited memory, such as JavaCard, and one or more or more applications or applets may be securely executed. Applets may be added to contactless cards to provide a one-time password (OTP) for multifactor authentication (MFA) in various mobile application-based use cases. Applets may be configured to respond to one or more requests, such as near field data exchange requests, from a reader, such as a mobile NFC reader (e.g., thecommunications interface 118 of the device 110), and produce an NDEF message that comprises a cryptographically secure OTP encoded as an NDEF text tag. - Operations for the disclosed embodiments may be further described with reference to the following figures. Some of the figures may include a logic flow. Although such figures presented herein may include a particular logic flow, it can be appreciated that the logic flow merely provides an example of how the general functionality as described herein can be implemented. Further, a given logic flow does not necessarily have to be executed in the order presented unless otherwise indicated. In addition, the given logic flow may be implemented by a hardware element, a software element executed by a processor, or any combination thereof. The embodiments are not limited in this context.
-
FIG. 5 illustrates an embodiment of alogic flow 500. Thelogic flow 500 may be representative of some or all of the operations executed by one or more embodiments described herein. For example, thelogic flow 500 may include some or all of the operations to use thecontactless card 101 to provide secure authentication based on identity data stored in thecontactless card 101. Embodiments are not limited in this context. - As shown, the
logic flow 500 begins atblock 505, where theaccount application 113 receives a request to perform an operation. As stated, the requested operation may be received based on input from a user of theaccount application 113, an external source (e.g., the merchant device 301), one of theother applications 114, or any other source. The request may be related to, for example and without limitation, use of theaccount application 113, use of theother applications 114, operations related to the account associated with thecontactless card 101, and/or a transaction. More generally, the request may be received subsequent to a user providing authentication credentials required to access the account in theaccount application 113. Atblock 510, a user taps thecontactless card 101 to themobile device 110 to cause theapplet 103 of thecontactless card 101 to generate and transmit the encrypted customer ID 132 to themobile device 110. - At
block 515, theaccount application 113 may receive the encrypted customer ID 132 from thecontactless card 101. Theaccount application 113 may then transmit the encrypted customer ID 132 received from thecontactless card 101 to theauthentication server 120. Theserver 120 may attempt to decrypt the encrypted customer ID 132 as described herein. Atblock 520, theaccount application 113 receives an indication from theserver 120 that the encrypted customer ID 132 was verified by decrypting the encrypted customer ID 132. - At
block 525, theaccount application 113 determines a type of the request. Atblock 530, theaccount application 113 determines a type of verification data specified in therules 115 required to authorize the type of operation. For example, thepassport data 108 may be specified as the verification data required by therules 115. Atblock 530, the user taps thecontactless card 101 to themobile device 110. Doing so instructs theapplet 103 of thecontactless card 101 to transmit thepassport data 108 to themobile device 110. Theaccount application 113 may receive the additional data (e.g., the passport data 108) from thecontactless card 101 atblock 535. - At
block 540, theaccount application 113 may receive the additional data from thecontactless card 101. Atblock 545, theaccount application 113 may process the data received atblock 540. For example, theaccount application 113 may perform any age-verification, account verification, and/or identify verification specified by therules 115. As another example, theaccount application 113 and/or theauthentication server 120 may verify a digital signature of the received data. Atblock 550, theaccount application 113 determines that the processed data satisfies therules 115. Atblock 555, theaccount application 113 permits performance of the requested operation based on the verification of the encrypted customer ID 132 by theserver 120 and the determination that the processed data received atblock 535 satisfies therules 115. Atblock 560, the requested operation may be performed, e.g., by the user and/or by theaccount application 113. -
FIG. 6 illustrates an embodiment of alogic flow 600. Thelogic flow 600 may be representative of some or all of the operations executed by one or more embodiments described herein. For example, thelogic flow 600 may include some or all of the operations to provide authentication based on thepassport data 108 stored in thecontactless card 101. Embodiments are not limited in this context. - As shown, the
logic flow 600 begins atblock 610, where theaccount application 113 determines that therules 115 require passport-based verification based on the type of the requested operation. Atblock 620, theaccount application 113 outputs an instruction to the user to capture an image depicting at least the face of the user. Atblock 630, theaccount application 113 receives the image captured by thecamera 119 of themobile device 110. Atblock 640, theaccount application 113 compares the captured image received atblock 630 to one or more images associated with the passport in thepassport data 108 and determines that a similarity of the persons depicted in each image exceeds a threshold level of similarity specified by therules 115. Atblock 650, theaccount application 113 determines, based on the determination atblock 640, that the user depicted in the captured image matches the person depicted in the passport image of thepassport data 108. Atblock 660, theaccount application 113 permits performance of the requested operation based at least in part on the determinations that the user depicted in the captured image matches the person depicted in the passport image of thepassport data 108 and/or that the determined similarity exceeds the threshold specified by therules 115. - Although the
logic flow 600 relates to an image in thepassport data 108, thelogic flow 600 is equally applicable to image-based verification using an image of the user in the driver'slicense data 109. Therefore, theaccount application 113 may determine whether the user in the captured image matches a user depicted in the driver'slicense data 109. Embodiments are not limited in these contexts. -
FIG. 7 illustrates an embodiment of alogic flow 700. Thelogic flow 700 may be representative of some or all of the operations executed by one or more embodiments described herein. For example, thelogic flow 700 may include some or all of the operations to provide authentication based on the driver'slicense data 109 stored in thecontactless card 101. Embodiments are not limited in this context. - As shown, the
logic flow 700 begins atblock 710, where theaccount application 113 receives an indication from amerchant device 301 specifying that age verification is required to purchase an age-restricted item. Atblock 720, theaccount application 113 receives the driver'slicense data 109 from thecontactless card 101 based on a tap of thecard 101 to themobile device 110. Atblock 730, theaccount application 113 processes the driver'slicense data 109 to determine the age of the associated person, e.g., based on a date of birth included in the driver's license data. - At
block 740, theaccount application 113 determines that the age of the person determined atblock 730 exceeds a minimum age threshold. Atblock 750, theaccount application 113 transmits an indication that the person's age exceeds the threshold. Additionally and/or alternatively, theaccount application 113 may transmit the age and/or the driver'slicense data 109 to themerchant device 301 for processing and verification. Atblock 760, theaccount application 113 receives payment data from thecontactless card 101 responsive to a tap of thecontactless card 101 to themobile device 110. Atblock 770, theaccount application 113 transmits the payment data to themerchant device 301. Atblock 780, themerchant device 301 may process the transaction using the received payment data. In some embodiments, themerchant device 301 transmits a payment confirmation to theaccount application 113. -
FIG. 8 illustrates an embodiment of anexemplary computing architecture 800 comprising acomputing system 802 that may be suitable for implementing various embodiments as previously described. In various embodiments, thecomputing architecture 800 may comprise or be implemented as part of an electronic device. In some embodiments, thecomputing architecture 800 may be representative, for example, of a system that implements one or more components of thesystem 100. In some embodiments,computing system 802 may be representative, for example, of thecontactless card 101,mobile devices 110, andauthentication server 120 of thesystem 100. The embodiments are not limited in this context. More generally, thecomputing architecture 800 is configured to implement all logic, applications, systems, methods, apparatuses, and functionality described herein with reference toFIGS. 1-7 . - As used in this application, the terms “system” and “component” and “module” are intended to refer to a computer-related entity, either hardware, a combination of hardware and software, software, or software in execution, examples of which are provided by the
exemplary computing architecture 800. For example, a component can be, but is not limited to being, a process running on a computer processor, a computer processor, a hard disk drive, multiple storage drives (of optical and/or magnetic storage medium), an object, an executable, a thread of execution, a program, and/or a computer. By way of illustration, both an application running on a server and the server can be a component. One or more components can reside within a process and/or thread of execution, and a component can be localized on one computer and/or distributed between two or more computers. Further, components may be communicatively coupled to each other by various types of communications media to coordinate operations. The coordination may involve the uni-directional or bi-directional exchange of information. For instance, the components may communicate information in the form of signals communicated over the communications media. The information can be implemented as signals allocated to various signal lines. In such allocations, each message is a signal. Further embodiments, however, may alternatively employ data messages. Such data messages may be sent across various connections. Exemplary connections include parallel interfaces, serial interfaces, and bus interfaces. - The
computing system 802 includes various common computing elements, such as one or more processors, multi-core processors, co-processors, memory units, chipsets, controllers, peripherals, interfaces, oscillators, timing devices, video cards, audio cards, multimedia input/output (I/O) components, power supplies, and so forth. The embodiments, however, are not limited to implementation by thecomputing system 802. - As shown in
FIG. 8 , thecomputing system 802 comprises aprocessor 804, asystem memory 806 and asystem bus 808. Theprocessor 804 can be any of various commercially available computer processors, including without limitation an AMD® Athlon®, Duron® and Opteron® processors; ARM® application, embedded and secure processors; IBM® and Motorola® DragonBall® and PowerPC® processors; IBM and Sony® Cell processors; Intel® Celeron®, Core®, Core (2) Duo®, Itanium®, Pentium®, Xeon®, and XScale® processors; and similar processors. Dual microprocessors, multi-core processors, and other multi processor architectures may also be employed as theprocessor 804. - The
system bus 808 provides an interface for system components including, but not limited to, thesystem memory 806 to theprocessor 804. Thesystem bus 808 can be any of several types of bus structure that may further interconnect to a memory bus (with or without a memory controller), a peripheral bus, and a local bus using any of a variety of commercially available bus architectures. Interface adapters may connect to thesystem bus 808 via a slot architecture. Example slot architectures may include without limitation Accelerated Graphics Port (AGP), Card Bus, (Extended) Industry Standard Architecture ((E)ISA), Micro Channel Architecture (MCA), NuBus, Peripheral Component Interconnect (Extended) (PCI(X)), PCI Express, Personal Computer Memory Card International Association (PCMCIA), and the like. - The
system memory 806 may include various types of computer-readable storage media in the form of one or more higher speed memory units, such as read-only memory (ROM), random-access memory (RAM), dynamic RAM (DRAM), Double-Data-Rate DRAM (DDRAM), synchronous DRAM (SDRAM), static RAM (SRAM), programmable ROM (PROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), flash memory (e.g., one or more flash arrays), polymer memory such as ferroelectric polymer memory, ovonic memory, phase change or ferroelectric memory, silicon-oxide-nitride-oxide-silicon (SONOS) memory, magnetic or optical cards, an array of devices such as Redundant Array of Independent Disks (RAID) drives, solid state memory devices (e.g., USB memory, solid state drives (SSD) and any other type of storage media suitable for storing information. In the illustrated embodiment shown inFIG. 8 , thesystem memory 806 can includenon-volatile memory 810 and/orvolatile memory 812. A basic input/output system (BIOS) can be stored in thenon-volatile memory 810. - The
computing system 802 may include various types of computer-readable storage media in the form of one or more lower speed memory units, including an internal (or external) hard disk drive (HDD) 814, a magnetic floppy disk drive (FDD) 816 to read from or write to a removablemagnetic disk 818, and anoptical disk drive 820 to read from or write to a removable optical disk 822 (e.g., a CD-ROM or DVD). TheHDD 814,FDD 816 andoptical disk drive 820 can be connected to thesystem bus 808 by aHDD interface 824, anFDD interface 826 and anoptical drive interface 828, respectively. TheHDD interface 824 for external drive implementations can include at least one or both of Universal Serial Bus (USB) and IEEE 1394 interface technologies. Thecomputing system 802 is generally is configured to implement all logic, systems, methods, apparatuses, and functionality described herein with reference toFIGS. 1-7 . - The drives and associated computer-readable media provide volatile and/or nonvolatile storage of data, data structures, computer-readable instructions, computer-executable instructions, and so forth. For example, a number of program modules can be stored in the drives and
memory units operating system 830, one ormore application programs 832,other program modules 834, andprogram data 836. In one embodiment, the one ormore application programs 832,other program modules 834, andprogram data 836 can include, for example, the various applications and/or components of thesystem 100, e.g., theapplet 103, counter 104,master key 105,diversified key 106, customer ID 107,passport data 108, driver'slicense data 109, other user data 131, encrypted customer ID 132, operating system 112,account application 113,other applications 114, theauthentication application 123, and/or theaccount data 124. - A user can enter commands and information into the
computing system 802 through one or more wire/wireless input devices, for example, akeyboard 838 and a pointing device, such as amouse 840. Other input devices may include microphones, infra-red (IR) remote controls, radio-frequency (RF) remote controls, game pads, stylus pens, card readers, dongles, finger print readers, gloves, graphics tablets, joysticks, keyboards, retina readers, touch screens (e.g., capacitive, resistive, etc.), trackballs, trackpads, sensors, styluses, and the like. These and other input devices are often connected to theprocessor 804 through aninput device interface 842 that is coupled to thesystem bus 808, but can be connected by other interfaces such as a parallel port, IEEE 1394 serial port, a game port, a USB port, an IR interface, and so forth. - A
monitor 844 or other type of display device is also connected to thesystem bus 808 via an interface, such as avideo adaptor 846. Themonitor 844 may be internal or external to thecomputing system 802. In addition to themonitor 844, a computer typically includes other peripheral output devices, such as speakers, printers, and so forth. - The
computing system 802 may operate in a networked environment using logical connections via wire and/or wireless communications to one or more remote computers, such as aremote computer 848. Theremote computer 848 can be a workstation, a server computer, a router, a personal computer, portable computer, microprocessor-based entertainment appliance, a peer device or other common network node, and typically includes many or all of the elements described relative to thecomputing system 802, although, for purposes of brevity, only a memory/storage device 850 is illustrated. The logical connections depicted include wire/wireless connectivity to a local area network (LAN) 852 and/or larger networks, for example, a wide area network (WAN) 854. Such LAN and WAN networking environments are commonplace in offices and companies, and facilitate enterprise-wide computer networks, such as intranets, all of which may connect to a global communications network, for example, the Internet. In embodiments, thenetwork 130 ofFIG. 1 is one or more of theLAN 852 and theWAN 854. - When used in a LAN networking environment, the
computing system 802 is connected to theLAN 852 through a wire and/or wireless communication network interface oradaptor 856. Theadaptor 856 can facilitate wire and/or wireless communications to theLAN 852, which may also include a wireless access point disposed thereon for communicating with the wireless functionality of theadaptor 856. - When used in a WAN networking environment, the
computing system 802 can include amodem 858, or is connected to a communications server on theWAN 854, or has other means for establishing communications over theWAN 854, such as by way of the Internet. Themodem 858, which can be internal or external and a wire and/or wireless device, connects to thesystem bus 808 via theinput device interface 842. In a networked environment, program modules depicted relative to thecomputing system 802, or portions thereof, can be stored in the remote memory/storage device 850. It will be appreciated that the network connections shown are exemplary and other means of establishing a communications link between the computers can be used. - The
computing system 802 is operable to communicate with wired and wireless devices or entities using theIEEE 802 family of standards, such as wireless devices operatively disposed in wireless communication (e.g., IEEE 802.16 over-the-air modulation techniques). This includes at least Wi-Fi (or Wireless Fidelity), WiMax, and Bluetooth™ wireless technologies, among others. Thus, the communication can be a predefined structure as with a conventional network or simply an ad hoc communication between at least two devices. Wi-Fi networks use radio technologies called IEEE 802.11x (a, b, g, n, etc.) to provide secure, reliable, fast wireless connectivity. A Wi-Fi network can be used to connect computers to each other, to the Internet, and to wire networks (which use IEEE 802.3-related media and functions). - Various embodiments may be implemented using hardware elements, software elements, or a combination of both. Examples of hardware elements may include processors, microprocessors, circuits, circuit elements (e.g., transistors, resistors, capacitors, inductors, and so forth), integrated circuits, application specific integrated circuits (ASIC), programmable logic devices (PLD), digital signal processors (DSP), field programmable gate array (FPGA), logic gates, registers, semiconductor device, chips, microchips, chip sets, and so forth. Examples of software may include software components, programs, applications, computer programs, application programs, system programs, machine programs, operating system software, middleware, firmware, software modules, routines, subroutines, functions, methods, procedures, software interfaces, application program interfaces (API), instruction sets, computing code, computer code, code segments, computer code segments, words, values, symbols, or any combination thereof. Determining whether an embodiment is implemented using hardware elements and/or software elements may vary in accordance with any number of factors, such as desired computational rate, power levels, heat tolerances, processing cycle budget, input data rates, output data rates, memory resources, data bus speeds and other design or performance constraints.
- One or more aspects of at least one embodiment may be implemented by representative instructions stored on a machine-readable medium which represents various logic within the processor, which when read by a machine causes the machine to fabricate logic to perform the techniques described herein. Such representations, known as “IP cores” may be stored on a tangible, machine readable medium and supplied to various customers or manufacturing facilities to load into the fabrication machines that make the logic or processor. Some embodiments may be implemented, for example, using a machine-readable medium or article which may store an instruction or a set of instructions that, if executed by a machine, may cause the machine to perform a method and/or operations in accordance with the embodiments. Such a machine may include, for example, any suitable processing platform, computing platform, computing device, processing device, computing system, processing system, computer, processor, or the like, and may be implemented using any suitable combination of hardware and/or software. The machine-readable medium or article may include, for example, any suitable type of memory unit, memory device, memory article, memory medium, storage device, storage article, storage medium and/or storage unit, for example, memory, removable or non-removable media, erasable or non-erasable media, writeable or re-writeable media, digital or analog media, hard disk, floppy disk, Compact Disk Read Only Memory (CD-ROM), Compact Disk Recordable (CD-R), Compact Disk Rewriteable (CD-RW), optical disk, magnetic media, magneto-optical media, removable memory cards or disks, various types of Digital Versatile Disk (DVD), a tape, a cassette, or the like. The instructions may include any suitable type of code, such as source code, compiled code, interpreted code, executable code, static code, dynamic code, encrypted code, and the like, implemented using any suitable high-level, low-level, object-oriented, visual, compiled and/or interpreted programming language.
- The foregoing description of example embodiments has been presented for the purposes of illustration and description. It is not intended to be exhaustive or to limit the present disclosure to the precise forms disclosed. Many modifications and variations are possible in light of this disclosure. It is intended that the scope of the present disclosure be limited not by this detailed description, but rather by the claims appended hereto. Future filed applications claiming priority to this application may claim the disclosed subject matter in a different manner, and may generally include any set of one or more limitations as variously disclosed or otherwise demonstrated herein.
Claims (20)
1. A method, comprising:
receiving, by a point-of-sale (POS) terminal, a request to perform an age verification via a contactless card for an age-restricted purchase;
presenting, on a display device of the POS terminal, an indication to provide the contactless card to the POS terminal to perform the age verification;
receiving, by the POS terminal from the contactless card, data indicating an age of a customer associated with the contactless card; and
enabling or restricting, by the POS terminal, the age-restricted purchase based on whether the data indicating the age of the customer meets an age requirement for the age-restricted purchase.
2. The method of claim 1 , further comprising prior to receiving the data indicating the age of the customer:
receiving, by the POS terminal from the contactless card, encrypted data;
transmitting, by the POS terminal, the encrypted data to an authentication server; and
determining, by the POS terminal, that the authentication server decrypted the encrypted data.
3. The method of claim 2 , wherein the encrypted data is based on a diversified key of the contactless card, wherein the diversified key is based on another key and a counter value of the contactless card.
4. The method of claim 3 , wherein the counter value is synchronized between the contactless card and the authentication server.
5. The method of claim 1 , further comprising prior to enabling or preventing the age-restricted purchase:
receiving, by the POS terminal from the contactless card, a digital signature of the data indicating the age of the customer; and
verifying, by the POS terminal, the digital signature based on a public key for the contactless card.
6. The method of claim 1 , wherein the data indicating the age of the customer is based on encrypted government-issued identification stored in the contactless card.
7. The method of claim 6 , further comprising prior to enabling or preventing the age-restricted purchase:
decrypting, by the POS terminal, the encrypted government-issued identification, wherein the decrypted government-issued identification comprises the age of the customer;
determining, by the POS terminal, that the age of the customer does not meet the age requirement for the age-restricted purchase; and
restricting, by the POS terminal, the age-restricted purchase based on the determination that the age of the customer does not meet the age requirement for the age-restricted purchase.
8. A point-of-sale (POS) terminal, comprising:
a processor; and
a memory storing instructions that, when executed by the processor, cause the processor to:
receive a request to perform an age verification via a contactless card for an age-restricted purchase;
present, on a display device of the POS terminal, an indication to provide the contactless card to the POS terminal to perform the age verification;
receive, from the contactless card, data indicating an age of a customer associated with the contactless card; and
enable or restrict the age-restricted purchase based on whether the data indicating the age of the customer meets an age requirement for the age-restricted purchase.
9. The POS terminal of claim 8 , wherein the instructions further cause the processor to, prior to receiving the data indicating the age of the customer:
receive, by the POS terminal from the contactless card, encrypted data;
transmit, by the POS terminal, the encrypted data to an authentication server; and
determine, by the POS terminal, that the authentication server decrypted the encrypted data.
10. The POS terminal of claim 9 , wherein the encrypted data is based on a diversified key of the contactless card, wherein the diversified key is based on another key and a counter value of the contactless card.
11. The POS terminal of claim 8 , wherein the instructions further cause the processor to, prior to enabling or restricting the age-restricted purchase:
receive, from the contactless card, a digital signature of the data indicating the age of the customer; and
verify the digital signature based on a public key for the contactless card.
12. The POS terminal of claim 8 , wherein the data indicate the age of the customer is based on encrypted government-issued identification stored in the contactless card.
13. The POS terminal of claim 12 , wherein the instructions further cause the processor to, prior to enabling or restricting the age-restricted purchase:
decrypt the encrypted government-issued identification, wherein the decrypted government-issued identification comprises the age of the customer;
determine that the age of the customer does not meet the age requirement for the age-restricted purchase; and
restrict the age-restricted purchase based on the determination that the age of the customer does not meet the age requirement for the age-restricted purchase.
14. A non-transitory computer-readable storage medium, the computer-readable storage medium including instructions that when executed by a processor of a point-of-sale (POS) terminal, cause the processor to:
receive a request to perform an age verification via a contactless card for an age-restricted purchase;
present, on a display device of the POS terminal, an indication to provide the contactless card to the POS terminal to perform the age verification;
receive, from the contactless card, data indicating an age of a customer associated with the contactless card; and
enable or restrict the age-restricted purchase based on whether the data indicating the age of the customer meets an age requirement for the age-restricted purchase.
15. The computer-readable storage medium of claim 14 , wherein the instructions further cause the processor to, prior to receiving the data indicate the age of the customer:
receive, from the contactless card, encrypted data;
transmit the encrypted data to an authentication server; and
determine that the authentication server decrypted the encrypted data.
16. The computer-readable storage medium of claim 15 , wherein the encrypted data is based on a diversified key of the contactless card, wherein the diversified key is based on another key and a counter value of the contactless card.
17. The computer-readable storage medium of claim 16 , wherein the counter value is synchronized between the contactless card and the authentication server.
18. The computer-readable storage medium of claim 14 , wherein the instructions further cause the processor to, prior to enabling or restricting the age-restricted purchase:
receive, from the contactless card, a digital signature of the data indicating the age of the customer; and
verify the digital signature based on a public key for the contactless card.
19. The computer-readable storage medium of claim 14 , wherein the data indicate the age of the customer is based on encrypted government-issued identification stored in the contactless card.
20. The computer-readable storage medium of claim 19 , wherein the instructions further configure the computer to prior to enabling or restricting the age-restricted purchase:
decrypt the encrypted government-issued identification, wherein the decrypted government-issued identification comprises the age of the customer;
determine that the age of the customer does not meet the age requirement for the age-restricted purchase; and
restrict the age-restricted purchase based on the determination that the age of the customer does not meet the age requirement for the age-restricted purchase.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US18/124,050 US20230252452A1 (en) | 2019-12-24 | 2023-03-21 | Secure authentication based on identity data stored in a contactless card |
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US16/726,385 US10853795B1 (en) | 2019-12-24 | 2019-12-24 | Secure authentication based on identity data stored in a contactless card |
US17/085,721 US11645645B2 (en) | 2019-12-24 | 2020-10-30 | Secure authentication based on identity data stored in a contactless card |
US18/124,050 US20230252452A1 (en) | 2019-12-24 | 2023-03-21 | Secure authentication based on identity data stored in a contactless card |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US17/085,721 Continuation US11645645B2 (en) | 2019-12-24 | 2020-10-30 | Secure authentication based on identity data stored in a contactless card |
Publications (1)
Publication Number | Publication Date |
---|---|
US20230252452A1 true US20230252452A1 (en) | 2023-08-10 |
Family
ID=73554906
Family Applications (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/726,385 Active US10853795B1 (en) | 2019-12-24 | 2019-12-24 | Secure authentication based on identity data stored in a contactless card |
US17/085,721 Active 2040-09-08 US11645645B2 (en) | 2019-12-24 | 2020-10-30 | Secure authentication based on identity data stored in a contactless card |
US18/124,050 Pending US20230252452A1 (en) | 2019-12-24 | 2023-03-21 | Secure authentication based on identity data stored in a contactless card |
Family Applications Before (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/726,385 Active US10853795B1 (en) | 2019-12-24 | 2019-12-24 | Secure authentication based on identity data stored in a contactless card |
US17/085,721 Active 2040-09-08 US11645645B2 (en) | 2019-12-24 | 2020-10-30 | Secure authentication based on identity data stored in a contactless card |
Country Status (9)
Country | Link |
---|---|
US (3) | US10853795B1 (en) |
EP (1) | EP4082167A1 (en) |
JP (2) | JP7434324B2 (en) |
KR (1) | KR20220119308A (en) |
CN (1) | CN113316784A (en) |
AU (2) | AU2020414358B2 (en) |
CA (1) | CA3121963A1 (en) |
SG (1) | SG11202107177YA (en) |
WO (1) | WO2021133491A1 (en) |
Families Citing this family (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
FR3095056B1 (en) * | 2019-04-15 | 2021-10-22 | Idemia France | Display on a smartphone screen of a positioning pattern of a contactless card to improve near-field communication |
US12021861B2 (en) * | 2021-01-04 | 2024-06-25 | Bank Of America Corporation | Identity verification through multisystem cooperation |
US20230020843A1 (en) * | 2021-07-19 | 2023-01-19 | Capital One Services, Llc | System and method to perform digital authentication using multiple channels of communication |
US11995653B1 (en) * | 2021-12-09 | 2024-05-28 | Donald Anderson | Age verification card and method |
US20230230088A1 (en) * | 2022-01-06 | 2023-07-20 | Socure, Inc. | Method and System of Predictive Document Verification and Machine Learning Therefor |
CN116308379B (en) * | 2023-02-03 | 2024-05-31 | 星汉智能科技股份有限公司 | Smart card holder identity authentication method, smart card, terminal and medium |
Citations (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030177102A1 (en) * | 2001-09-21 | 2003-09-18 | Timothy Robinson | System and method for biometric authorization for age verification |
US20050033688A1 (en) * | 2002-07-09 | 2005-02-10 | American Express Travel Related Services Company, Inc. | Methods and apparatus for a secure proximity integrated circuit card transactions |
US20060231610A1 (en) * | 2005-04-15 | 2006-10-19 | Beacon Communication Kk | Handheld system and method for age verification |
US20080071674A1 (en) * | 2006-09-20 | 2008-03-20 | Thackston James D | System and method for on-line commerce operations including payment transactions |
US7472825B2 (en) * | 2002-01-11 | 2009-01-06 | Hand Held Products, Inc. | Transaction terminal |
US20120323621A1 (en) * | 2011-06-17 | 2012-12-20 | International Business Machines Corporation | Assisting Customers At A Self-Checkout Terminal |
US20150073995A1 (en) * | 2013-09-10 | 2015-03-12 | The Toronto Dominion Bank | System and method for authorizing a financial transaction |
US20160239887A1 (en) * | 2015-02-17 | 2016-08-18 | Mastercard International Incorporated | Age Verification Through Mobile Wallet Method and Apparatus |
US20180349889A1 (en) * | 2017-05-31 | 2018-12-06 | Paypal, Inc. | Accessing digital wallet information using a point-of-sale device |
US20190066063A1 (en) * | 2017-08-22 | 2019-02-28 | Jeffery J. Jessamine | Method and System for Secure Identity Transmission with Integrated Service Network and Application Ecosystem |
Family Cites Families (549)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
FR2523745B1 (en) | 1982-03-18 | 1987-06-26 | Bull Sa | METHOD AND DEVICE FOR PROTECTING SOFTWARE DELIVERED BY A SUPPLIER TO A USER |
JPS6198476A (en) | 1984-10-19 | 1986-05-16 | Casio Comput Co Ltd | Card terminal and its certifying system |
FR2613565B1 (en) | 1987-04-03 | 1989-06-23 | Bull Cps | METHOD FOR ROUTING SECRET KEYS TO SECURITY MODULES AND USER CARDS, IN AN INFORMATION PROCESSING NETWORK |
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 (en) | 1993-04-22 | 1995-06-02 | Bull Cp8 | Device for protecting the keys of a smart card. |
US5377270A (en) | 1993-06-30 | 1994-12-27 | United Technologies Automotive, Inc. | Cryptographic authentication of transmitted messages using pseudorandom numbers |
US5363448A (en) | 1993-06-30 | 1994-11-08 | United Technologies Automotive, Inc. | Pseudorandom number generation and cryptographic authentication |
JP3053527B2 (en) | 1993-07-30 | 2000-06-19 | インターナショナル・ビジネス・マシーンズ・コーポレイション | Method and apparatus for validating a password, method and apparatus for generating and preliminary validating a password, method and apparatus for controlling access to resources using an authentication code |
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 (en) | 1996-02-23 | 2004-07-15 | Fuji Xerox Co., Ltd. | Device and method for authenticating a user's access rights to resources according to the challenge-response principle |
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 |
US5763373A (en) | 1996-06-20 | 1998-06-09 | High Point Chemical Corp. | Method of preparing an alkaline earth metal tallate |
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 |
DE69824437T2 (en) | 1997-10-14 | 2005-06-23 | Visa International Service Association, Foster City | PERSONALIZING CHIP 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 |
ATE282990T1 (en) | 1998-05-11 | 2004-12-15 | Citicorp Dev Ct Inc | SYSTEM AND METHOD FOR BIOMETRIC AUTHENTICATION OF A USER USING A CHIP CARD |
JP3112076B2 (en) | 1998-05-21 | 2000-11-27 | 豊 保倉 | User authentication system |
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 |
CA2363003A1 (en) | 1999-02-18 | 2000-08-24 | 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 (en) | 1999-08-27 | 2001-07-16 | Ericsson Telefon Ab L M | Device for carrying out secure transactions in a communication device |
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 (en) | 1999-11-01 | 2001-07-19 | Sony Corp | Authentication information communication system, authentication information communication method, portable information processor and program provision medium |
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 |
JP2003519879A (en) | 2000-01-10 | 2003-06-24 | タリアン・エルエルシー | Device using histopathological and physiological biometric markers 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 |
EP1272954A4 (en) | 2000-02-16 | 2004-08-18 | Zipcar Inc | Systems and methods for controlling vehicle access |
US8150767B2 (en) | 2000-02-16 | 2012-04-03 | Mastercard International Incorporated | System and method for conducting electronic commerce with a remote wallet server |
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 |
US8046256B2 (en) | 2000-04-14 | 2011-10-25 | American Express Travel Related Services Company, Inc. | System and method for using loyalty rewards as currency |
AU2001257280C1 (en) | 2000-04-24 | 2009-01-15 | 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 |
AU2001286464A1 (en) | 2000-08-14 | 2002-02-25 | Peter H. Gien | System and method for secure smartcard issuance |
WO2002015117A2 (en) | 2000-08-17 | 2002-02-21 | Dexrad (Proprietary) Limited | The transfer of verification data |
AU2001288679A1 (en) | 2000-09-11 | 2002-03-26 | Sentrycom Ltd. | A 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 |
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 |
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 |
US7181017B1 (en) | 2001-03-23 | 2007-02-20 | David Felsher | System and method for secure three-party communications |
ATE364202T1 (en) | 2001-04-02 | 2007-06-15 | Motorola Inc | ACTIVATE AND DISABLE SOFTWARE FEATURES |
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 (en) | 2001-06-06 | 2003-01-02 | Wincor Nixdorf Gmbh & Co Kg | Read / write device for an ID or credit card of the RFID type |
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 (en) | 2001-10-23 | 2007-09-12 | 株式会社日立製作所 | IC card, customer information analysis system, and customer information analysis result providing method |
US6641050B2 (en) | 2001-11-06 | 2003-11-04 | International Business Machines Corporation | Secure credit card |
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 |
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 (en) | 2001-12-27 | 2004-02-06 | France Telecom | CRYPTOGRAPHIC GROUP SIGNATURE SYSTEM |
JP3820999B2 (en) | 2002-01-25 | 2006-09-13 | ソニー株式会社 | Proximity communication system and proximity communication method, data management apparatus and data management method, storage medium, and computer program |
SE524778C2 (en) | 2002-02-19 | 2004-10-05 | Douglas Lundholm | Procedure and arrangements for protecting software for unauthorized use or copying |
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 (en) | 2002-05-10 | 2008-12-03 | 斯伦贝谢(北京)智能卡科技有限公司 | Intelligent card replacing method and system |
US20040127256A1 (en) | 2002-07-30 | 2004-07-01 | Scott Goldthwaite | Mobile device equipped with a contactless smart card reader/writer |
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 |
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 (en) | 2002-08-26 | 2010-09-29 | パナソニック株式会社 | Electronic value authentication method, authentication system and device |
CZ2005209A3 (en) | 2002-09-10 | 2005-12-14 | Ivi Smart Technologies, Inc. | Safe biometric verification of 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 |
WO2004036492A2 (en) | 2002-10-16 | 2004-04-29 | Sci-Tel Ltd. | 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 |
EP1588318A1 (en) | 2003-01-14 | 2005-10-26 | Koninklijke Philips Electronics N.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 |
EP1632091A4 (en) | 2003-05-12 | 2006-07-26 | Gtech Corp | Method and system for authentication |
US7949559B2 (en) | 2003-05-27 | 2011-05-24 | Citicorp Credit Services, Inc. | Credit card rewards program system and method |
US7685642B2 (en) * | 2003-06-26 | 2010-03-23 | Contentguard Holdings, Inc. | System and method for controlling rights expressions by stakeholders of an item |
US8200775B2 (en) | 2005-02-01 | 2012-06-12 | Newsilike Media Group, Inc | Enhanced syndication |
JP4744106B2 (en) | 2003-08-06 | 2011-08-10 | パナソニック株式会社 | Secure device, information processing terminal, communication system, and communication method |
US20050075985A1 (en) | 2003-10-03 | 2005-04-07 | Brian Cartmell | Voice authenticated credit card purchase verification |
FI20031482A (en) | 2003-10-10 | 2005-04-11 | Open Bit Oy Ltd | processing of payment transaction data |
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 |
US20050137987A1 (en) | 2003-12-22 | 2005-06-23 | Robert May | Customer age verification |
US7357309B2 (en) | 2004-01-16 | 2008-04-15 | Telefonaktiebolaget Lm Ericsson (Publ) | EMV transactions in mobile terminals |
US7165727B2 (en) | 2004-02-24 | 2007-01-23 | Sun Microsystems, Inc. | Method and apparatus for installing an application onto a smart card |
US7374099B2 (en) | 2004-02-24 | 2008-05-20 | Sun Microsystems, Inc. | Method and apparatus for processing an application identifier from 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 |
JP2007529797A (en) | 2004-03-19 | 2007-10-25 | フンベル ローガー | All-in-one key or control software card in mobile phones for wireless bicycle keys, cars, houses, RFID tags with authentication and payment functions |
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 (en) | 2004-05-03 | 2009-10-14 | 捷讯研究有限公司 | The system and method that is used for application authorization |
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 |
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 |
US7424977B2 (en) | 2004-07-15 | 2008-09-16 | Mastercard International Incorporated | Method and system for conducting contactless payment card transactions |
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 |
BRPI0514159A2 (en) | 2004-08-27 | 2008-11-25 | Victorion Technology Co Ltd | nasal bone conduction wireless communication device, nasal bone conduction wireless communication system, and nasal bone conduction hearing aid |
US20060047954A1 (en) | 2004-08-30 | 2006-03-02 | Axalto Inc. | Data access security implementation using the public key mechanism |
US7664109B2 (en) * | 2004-09-03 | 2010-02-16 | Microsoft Corporation | System and method for distributed streaming of scalable media |
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 |
US20130104251A1 (en) | 2005-02-01 | 2013-04-25 | Newsilike Media Group, Inc. | Security systems and methods for use with structured and unstructured data |
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 |
DE102005004902A1 (en) | 2005-02-02 | 2006-08-10 | Utimaco Safeware Ag | Method for registering a user on a computer system |
US7581678B2 (en) | 2005-02-22 | 2009-09-01 | Tyfone, Inc. | Electronic transaction card |
CN101171604A (en) | 2005-03-07 | 2008-04-30 | 诺基亚公司 | Method and mobile terminal device including smartcard module and near field communication 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 |
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 |
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 |
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 |
CA2624981C (en) | 2005-10-06 | 2017-06-13 | C-Sam, Inc. | Three-dimensional transaction authentication |
US8245292B2 (en) | 2005-11-16 | 2012-08-14 | Broadcom Corporation | Multi-factor authentication using a smartcard |
JP4435076B2 (en) | 2005-11-18 | 2010-03-17 | フェリカネットワークス株式会社 | Mobile terminal, data communication method, and computer program |
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 (en) | 2005-12-23 | 2008-03-21 | Trusted Logic Sa | METHOD FOR MAKING A SECURED COUNTER ON AN ON-BOARD COMPUTER SYSTEM HAVING A CHIP CARD |
US8352323B2 (en) | 2007-11-30 | 2013-01-08 | Blaze Mobile, Inc. | Conducting an online payment transaction using an NFC enabled mobile communication device |
US8559987B1 (en) | 2005-12-31 | 2013-10-15 | Blaze Mobile, Inc. | Wireless bidirectional communications between a mobile device and associated secure element |
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 (en) | 2006-05-10 | 2010-09-23 | Inside Contactless | Method for forwarding incoming and outgoing data to an NFC chipset |
EP1873962B1 (en) | 2006-06-29 | 2009-08-19 | Incard SA | Method for key diversification on an IC Card |
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 |
US7962369B2 (en) | 2006-09-29 | 2011-06-14 | Einar Rosenberg | 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 |
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 |
US8682791B2 (en) | 2006-10-31 | 2014-03-25 | Discover Financial Services | Redemption of credit card rewards at a point of sale |
WO2008054715A2 (en) | 2006-10-31 | 2008-05-08 | Solicore, Inc. | Powered print advertisements, product packaging, and trading cards |
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 (en) | 2006-11-30 | 2008-06-04 | 讯想科技股份有限公司 | Chip credit card network transaction system and method |
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 |
EP2135359A4 (en) | 2007-03-16 | 2011-07-27 | 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 |
US20090143104A1 (en) | 2007-09-21 | 2009-06-04 | Michael Loh | 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 |
GB2457221A (en) | 2007-10-17 | 2009-08-12 | Vodafone Plc | Smart Card Web Server (SCWS) administration within a plurality of security domains |
US8095113B2 (en) | 2007-10-17 | 2012-01-10 | First Data Corporation | Onetime passwords for smart chip cards |
FR2922701B1 (en) | 2007-10-23 | 2009-11-20 | Inside Contacless | SECURE CUSTOMIZATION METHOD OF AN NFC CHIPSET |
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 |
US20090159705A1 (en) | 2007-12-24 | 2009-06-25 | Dynamics Inc. | Payment cards and devices operable to receive point-of-sale actions before point-of-sale and forward actions at point-of-sale |
WO2009089099A1 (en) | 2008-01-04 | 2009-07-16 | M2 International Ltd. | Dynamic card verification value |
GB0801225D0 (en) | 2008-01-23 | 2008-02-27 | Innovision Res & Tech Plc | Near field RF communications |
US9558485B2 (en) | 2008-01-30 | 2017-01-31 | Paypal, Inc. | Two step near field communication transactions |
US8369960B2 (en) | 2008-02-12 | 2013-02-05 | 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 |
ES2386164T3 (en) | 2008-03-27 | 2012-08-10 | Motorola Mobility, Inc. | Method and apparatus for automatic selection of a near field communication application in an electronic device |
ITMI20080536A1 (en) | 2008-03-28 | 2009-09-29 | Incard Sa | METHOD TO PROTECT A CAP FILE FOR AN INTEGRATED CIRCUIT CARD. |
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 |
US20100033310A1 (en) | 2008-08-08 | 2010-02-11 | Narendra Siva G | Power negotation for small rfid card |
CA2733522C (en) | 2008-08-08 | 2013-10-01 | Assa Abloy Ab | Directional sensing mechanism and communications authentication |
CN102160061B (en) | 2008-08-20 | 2014-04-09 | X卡控股有限公司 | Secure smart card system |
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 |
US20100094754A1 (en) | 2008-10-13 | 2010-04-15 | Global Financial Passport, Llc | Smartcard based secure transaction systems and methods |
US20100095130A1 (en) | 2008-10-13 | 2010-04-15 | Global Financial Passport, Llc | Smartcards for secure transaction systems |
US8689013B2 (en) | 2008-10-21 | 2014-04-01 | G. Wouter Habraken | Dual-interface key management |
CN101729502B (en) | 2008-10-23 | 2012-09-05 | 中兴通讯股份有限公司 | Method and system for distributing key |
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 |
CN103152080B (en) | 2009-02-26 | 2015-12-23 | 中兴通讯股份有限公司 | The terminal of support of enhanced near-field communication and processing method thereof |
US20100240413A1 (en) | 2009-03-21 | 2010-09-23 | Microsoft Corporation | Smart Card File System |
US8567670B2 (en) | 2009-03-27 | 2013-10-29 | Intersections Inc. | Dynamic card verification values and credit transactions |
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 |
US9307065B2 (en) | 2009-10-09 | 2016-04-05 | Panasonic Intellectual Property Management Co., Ltd. | Method and apparatus for processing E-mail and outgoing calls |
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 |
US10255601B2 (en) | 2010-02-25 | 2019-04-09 | Visa International Service Association | Multifactor authentication using a directory server |
US9129270B2 (en) | 2010-03-02 | 2015-09-08 | Gonow Technologies, Llc | Portable E-wallet and universal card |
US9317018B2 (en) | 2010-03-02 | 2016-04-19 | Gonow Technologies, Llc | Portable e-wallet and universal card |
SI23227A (en) | 2010-03-10 | 2011-05-31 | Margento R&D D.O.O. | Wireless mobile transaction system and procedure of carrying out transaction with mobile telephone |
US20110238564A1 (en) | 2010-03-26 | 2011-09-29 | Kwang Hyun Lim | System and Method for Early Detection of Fraudulent Transactions |
US8811892B2 (en) | 2010-04-05 | 2014-08-19 | Mastercard International Incorporated | 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 |
US9122964B2 (en) | 2010-05-14 | 2015-09-01 | Mark Krawczewicz | Batteryless stored value card with display |
US20120109735A1 (en) | 2010-05-14 | 2012-05-03 | Mark Stanley Krawczewicz | Mobile Payment System with Thin Film 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 (en) | 2010-05-27 | 2015-10-11 | Mstar Semiconductor Inc | Mobile device with electronic wallet function |
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 |
CN103109259A (en) | 2010-07-01 | 2013-05-15 | 以谢·白南斯托克 | 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 |
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 |
US20140379361A1 (en) | 2011-01-14 | 2014-12-25 | Shilpak Mahadkar | Healthcare Prepaid Payment Platform Apparatuses, Methods And Systems |
WO2012104978A1 (en) | 2011-01-31 | 2012-08-09 | 富士通株式会社 | Communication method, node, and network system |
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 |
US20120284194A1 (en) | 2011-05-03 | 2012-11-08 | Microsoft Corporation | Secure card-based transactions using mobile phones or other mobile devices |
EP2707847A4 (en) | 2011-05-10 | 2015-04-01 | 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 |
WO2013101297A1 (en) | 2011-06-07 | 2013-07-04 | Visa International Service Association | Payment privacy tokenization apparatuses, methods and systems |
WO2012170895A1 (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 (en) | 2011-08-25 | 2017-02-15 | 富泰华工业(深圳)有限公司 | Automatic teller machine and voice prompting method thereof |
BR112014004374B1 (en) | 2011-08-30 | 2021-09-21 | Simplytapp, Inc | METHOD FOR SECURE APPLICATION-BASED PARTICIPATION IN A PAYMENT CARD TRANSACTION AUTHORIZATION PROCESS BY A MOBILE DEVICE, SYSTEM FOR SECURE APPLICATION-BASED PARTICIPATION BY A MOBILE DEVICE IN POINT OF SALE INQUIRIES |
FR2980055B1 (en) | 2011-09-12 | 2013-12-27 | Valeo Systemes Thermiques | INDUCTIVE POWER TRANSMISSION DEVICE |
WO2013039395A1 (en) | 2011-09-14 | 2013-03-21 | Ec Solution Group B.V. | Active matrix display smart card |
US10032036B2 (en) | 2011-09-14 | 2018-07-24 | Shahab Khan | Systems and methods of multidimensional encrypted data transfer |
US8577810B1 (en) | 2011-09-29 | 2013-11-05 | Intuit Inc. | Secure mobile payment authorization |
US8977569B2 (en) | 2011-09-29 | 2015-03-10 | Raj Rao | System and method for providing smart electronic wallet and reconfigurable transaction card thereof |
US9152832B2 (en) | 2011-09-30 | 2015-10-06 | Broadcom Corporation | Positioning guidance for increasing reliability of near-field communications |
EP2579199A1 (en) | 2011-10-06 | 2013-04-10 | Gemalto SA | Method for paying for a product or a service on a commercial website by means of an internet connection and corresponding terminal |
US20140279479A1 (en) | 2011-10-12 | 2014-09-18 | C-Sam, Inc. | Nfc paired bluetooth e-commerce |
US9183490B2 (en) * | 2011-10-17 | 2015-11-10 | Capital One Financial Corporation | System and method for providing contactless payment with a near field communications attachment |
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 |
CA2851691C (en) | 2011-10-31 | 2016-11-29 | 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 |
US8818867B2 (en) | 2011-11-14 | 2014-08-26 | At&T Intellectual Property I, L.P. | Security token for mobile near field communication transactions |
EP2780854B1 (en) | 2011-11-14 | 2017-04-12 | Vasco Data Security International GmbH | A smart card reader with a secure logging feature |
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 (en) | 2012-02-22 | 2014-11-03 | 주식회사 팬택 | Electronic device and method for user identification |
US8898088B2 (en) | 2012-02-29 | 2014-11-25 | Google Inc. | In-card access control and monotonic counters for offline payment processing system |
US9020858B2 (en) | 2012-02-29 | 2015-04-28 | Google Inc. | Presence-of-card code for offline payment processing system |
US20130232082A1 (en) | 2012-03-05 | 2013-09-05 | Mark Stanley Krawczewicz | Method And Apparatus For Secure Medical ID Card |
BR122016030290A2 (en) | 2012-03-15 | 2019-08-27 | Intel Corp | portable electronic device and electronic device to provide proximity detection and proximity field communication (nfc) |
WO2013155562A1 (en) | 2012-04-17 | 2013-10-24 | 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 (en) | 2012-07-27 | 2014-07-22 | 주식회사 케이티 | Smart card, device and method for smart card service |
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 (en) | 2012-08-03 | 2019-01-02 | 엘지전자 주식회사 | Mobile terminal and nfc payment method thereof |
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 |
AU2013315510B2 (en) | 2012-09-11 | 2019-08-22 | Visa International Service Association | Cloud-based Virtual Wallet NFC Apparatuses, methods and systems |
US9275218B1 (en) | 2012-09-12 | 2016-03-01 | Emc Corporation | Methods and apparatus for verification of a user at a first device based on input received from a second device |
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 |
WO2014075162A1 (en) | 2012-11-15 | 2014-05-22 | Behzad Malek | System and method for location-based financial transaction authentication |
EP3429250A1 (en) | 2012-11-19 | 2019-01-16 | Avery Dennison Corporation | Nfc security system and method for disabling unauthorized tags |
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 (en) | 2012-11-22 | 2013-04-03 | 天地融科技股份有限公司 | Dynamic password card and dynamic password generating method |
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 |
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 facilitating dynamic and targeted advertisements for computing systems |
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 |
JP6307593B2 (en) | 2013-04-26 | 2018-04-04 | インターデイジタル パテント ホールディングス インコーポレイテッド | Multi-factor authentication to achieve the required level of certification assurance |
CA2851895C (en) | 2013-05-08 | 2023-09-26 | 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 |
US8994498B2 (en) | 2013-07-25 | 2015-03-31 | Bionym 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 (en) | 2013-08-19 | 2015-11-18 | 赵蕴博 | A kind of wrist-life physical sign monitoring device and monitoring method thereof |
EP3050335B1 (en) | 2013-09-24 | 2019-12-04 | Intel Corporation | Systems and methods for nfc access control in a secure element centric nfc architecture |
EP2854332A1 (en) | 2013-09-27 | 2015-04-01 | Gemalto SA | Method for securing over-the-air communication between a mobile application and a gateway |
US10878414B2 (en) | 2013-09-30 | 2020-12-29 | Apple Inc. | Multi-path communication of electronic device secure element data for online payments |
US11748746B2 (en) | 2013-09-30 | 2023-09-05 | Apple Inc. | Multi-path communication of electronic device secure element data for online payments |
EP3070602A4 (en) | 2013-11-15 | 2016-12-14 | Kuang-Chi Intelligent Photonic Tech Ltd | Instruction information transmission and reception methods and devices thereof |
CA2930149A1 (en) | 2013-11-19 | 2015-05-28 | Visa International Service Association | Automated account provisioning |
KR102103377B1 (en) | 2013-12-02 | 2020-04-23 | 마스터카드 인터내셔날, 인코포레이티드 | Method and system for secure transmission of remote notification service messages to mobile devices without secure elements |
KR102293822B1 (en) | 2013-12-19 | 2021-08-26 | 비자 인터네셔널 서비스 어소시에이션 | Cloud-based transactions methods and systems |
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 |
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 |
US20150317626A1 (en) | 2014-04-30 | 2015-11-05 | Intuit Inc. | Secure proximity exchange of payment information between mobile wallet and point-of-sale |
CA2946150A1 (en) | 2014-05-01 | 2015-11-05 | Visa International Service Association | Data verification using access device |
SG11201609220YA (en) | 2014-05-07 | 2016-12-29 | Visa Int Service Ass | Enhanced data interface for contactless communications |
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 |
US10043185B2 (en) | 2014-05-29 | 2018-08-07 | Apple Inc. | User interface for payments |
US9449239B2 (en) | 2014-05-30 | 2016-09-20 | Apple Inc. | Credit card auto-fill |
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 |
KR101508320B1 (en) | 2014-06-30 | 2015-04-07 | 주식회사 인포바인 | Apparatus for issuing and generating one time password using nfc card, and method using the same |
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 |
AU2015308608B2 (en) | 2014-08-29 | 2019-07-04 | Visa International Service Association | Methods for secure cryptogram generation |
CN104239783A (en) | 2014-09-19 | 2014-12-24 | 东软集团股份有限公司 | System and method for safely inputting customizing messages |
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 |
AU2015319804B2 (en) | 2014-09-26 | 2019-03-14 | Visa International Service Association | Remote server encrypted data provisioning system and methods |
US9473509B2 (en) | 2014-09-29 | 2016-10-18 | International Business Machines Corporation | Selectively permitting or denying usage of wearable device services |
US9432339B1 (en) | 2014-09-29 | 2016-08-30 | Emc Corporation | Automated token renewal using OTP-based authentication codes |
CN104463270A (en) | 2014-11-12 | 2015-03-25 | 惠州Tcl移动通信有限公司 | Intelligent terminal, financial card and financial management system based on RFID |
US9379841B2 (en) | 2014-11-17 | 2016-06-28 | Empire Technology Development Llc | Mobile device prevention of contactless card attacks |
US10223689B2 (en) | 2014-12-10 | 2019-03-05 | American Express Travel Related Services Company, Inc. | System and method for over the air 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 |
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 |
CN105930040A (en) | 2015-02-27 | 2016-09-07 | 三星电子株式会社 | 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 |
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 |
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 |
US10482453B2 (en) | 2015-04-14 | 2019-11-19 | Capital One Services, Llc | Dynamic transaction card protected by gesture and voice recognition |
CA2982764C (en) | 2015-04-14 | 2023-05-23 | Capital One Services, Llc | A system, method, and apparatus for a dynamic transaction card |
US10360557B2 (en) | 2015-04-14 | 2019-07-23 | Capital One Services, Llc | Dynamic transaction card protected by dropped card detection |
US9674705B2 (en) | 2015-04-22 | 2017-06-06 | Kenneth Hugh Rose | Method and system for secure peer-to-peer mobile communications |
US10007913B2 (en) | 2015-05-05 | 2018-06-26 | ShoCard, Inc. | Identity management service using a blockchain providing identity transactions between devices |
US20160335531A1 (en) | 2015-05-12 | 2016-11-17 | Dynamics Inc. | Dynamic security codes, tokens, displays, cards, devices, multi-card devices, systems and methods |
FR3038429B1 (en) | 2015-07-03 | 2018-09-21 | Ingenico Group | PAYMENT CONTAINER, CREATION METHOD, PROCESSING METHOD, DEVICES AND PROGRAMS THEREOF |
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 |
CN108026730B (en) | 2015-07-24 | 2019-11-22 | 明和科技(唐山)股份有限公司 | Light-weight environment-friendly type polypropylene composite materials floor and preparation method thereof |
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 (en) | 2015-09-03 | 2017-03-13 | 엔에이치엔엔터테인먼트 주식회사 | on-line credit card payment system using mobile terminal and payment method thereof |
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 (en) | 2015-09-11 | 2017-03-17 | Dp Security Consulting | METHOD OF ACCESSING ONLINE SERVICE USING SECURE MICROCIRCUIT AND SECURITY TOKENS RESTRICTING THE USE OF THESE TOKENS TO THEIR LEGITIMATE HOLDER |
ITUB20155318A1 (en) | 2015-10-26 | 2017-04-26 | St Microelectronics Srl | TAG, ITS PROCEDURE AND SYSTEM TO IDENTIFY AND / OR AUTHENTICATE ITEMS |
US20170140379A1 (en) | 2015-11-17 | 2017-05-18 | Bruce D. Deck | Credit card randomly generated pin |
CA2944935A1 (en) | 2015-11-27 | 2017-05-27 | The Toronto-Dominion Bank | System and method for remotely activating a pin-pad terminal |
EP3374740A4 (en) | 2015-12-07 | 2019-09-25 | 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 (en) | 2016-01-05 | 2016-07-08 | 주식회사 코인플러그 | Security system and method for transmitting a password |
WO2017134281A1 (en) | 2016-02-04 | 2017-08-10 | Nasdaq Technology Ab | Systems and methods for storing and sharing transactional data using distributed computer systems |
US10148135B2 (en) | 2016-02-16 | 2018-12-04 | Intel IP Corporation | System, apparatus and method for authenticating a device using a wireless charger |
US9619952B1 (en) | 2016-02-16 | 2017-04-11 | Honeywell International Inc. | Systems and methods of preventing access to users of an access control system |
US9961194B1 (en) | 2016-04-05 | 2018-05-01 | State Farm Mutual Automobile Insurance Company | Systems and methods for authenticating a caller at a call center |
EP3229397B1 (en) | 2016-04-07 | 2020-09-09 | ContactOffice Group | Method for fulfilling a cryptographic request requiring a value of a private key |
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 (en) | 2016-05-10 | 2017-11-20 | 엘지전자 주식회사 | Smart card and method for controlling the same |
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 |
CN106157025A (en) | 2016-07-05 | 2016-11-23 | 清华大学深圳研究生院 | The mobile terminal safety method of payment of identity-based card and system |
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 |
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 |
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 |
DE102017000768A1 (en) | 2017-01-27 | 2018-08-02 | Giesecke+Devrient Mobile Security Gmbh | Method for performing two-factor authentication |
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 |
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 |
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 |
US10510074B1 (en) | 2019-02-01 | 2019-12-17 | Capital One Services, Llc | One-tap payment using a contactless card |
US10438437B1 (en) | 2019-03-20 | 2019-10-08 | Capital One Services, Llc | Tap to copy data to clipboard via NFC |
-
2019
- 2019-12-24 US US16/726,385 patent/US10853795B1/en active Active
-
2020
- 2020-10-30 US US17/085,721 patent/US11645645B2/en active Active
- 2020-11-23 CN CN202080007261.XA patent/CN113316784A/en active Pending
- 2020-11-23 KR KR1020217023805A patent/KR20220119308A/en unknown
- 2020-11-23 EP EP20820735.7A patent/EP4082167A1/en active Pending
- 2020-11-23 CA CA3121963A patent/CA3121963A1/en active Pending
- 2020-11-23 JP JP2021533182A patent/JP7434324B2/en active Active
- 2020-11-23 WO PCT/US2020/061785 patent/WO2021133491A1/en unknown
- 2020-11-23 AU AU2020414358A patent/AU2020414358B2/en active Active
- 2020-11-23 SG SG11202107177YA patent/SG11202107177YA/en unknown
-
2023
- 2023-03-21 US US18/124,050 patent/US20230252452A1/en active Pending
- 2023-05-02 AU AU2023202708A patent/AU2023202708A1/en active Pending
-
2024
- 2024-02-07 JP JP2024017071A patent/JP2024054241A/en active Pending
Patent Citations (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030177102A1 (en) * | 2001-09-21 | 2003-09-18 | Timothy Robinson | System and method for biometric authorization for age verification |
US7472825B2 (en) * | 2002-01-11 | 2009-01-06 | Hand Held Products, Inc. | Transaction terminal |
US20050033688A1 (en) * | 2002-07-09 | 2005-02-10 | American Express Travel Related Services Company, Inc. | Methods and apparatus for a secure proximity integrated circuit card transactions |
US20060231610A1 (en) * | 2005-04-15 | 2006-10-19 | Beacon Communication Kk | Handheld system and method for age verification |
US20080071674A1 (en) * | 2006-09-20 | 2008-03-20 | Thackston James D | System and method for on-line commerce operations including payment transactions |
US20120323621A1 (en) * | 2011-06-17 | 2012-12-20 | International Business Machines Corporation | Assisting Customers At A Self-Checkout Terminal |
US20150073995A1 (en) * | 2013-09-10 | 2015-03-12 | The Toronto Dominion Bank | System and method for authorizing a financial transaction |
US20160239887A1 (en) * | 2015-02-17 | 2016-08-18 | Mastercard International Incorporated | Age Verification Through Mobile Wallet Method and Apparatus |
US20180349889A1 (en) * | 2017-05-31 | 2018-12-06 | Paypal, Inc. | Accessing digital wallet information using a point-of-sale device |
US20190066063A1 (en) * | 2017-08-22 | 2019-02-28 | Jeffery J. Jessamine | Method and System for Secure Identity Transmission with Integrated Service Network and Application Ecosystem |
Also Published As
Publication number | Publication date |
---|---|
US11645645B2 (en) | 2023-05-09 |
US10853795B1 (en) | 2020-12-01 |
EP4082167A1 (en) | 2022-11-02 |
WO2021133491A1 (en) | 2021-07-01 |
AU2020414358A1 (en) | 2021-07-22 |
KR20220119308A (en) | 2022-08-29 |
JP2024054241A (en) | 2024-04-16 |
SG11202107177YA (en) | 2021-09-29 |
CA3121963A1 (en) | 2021-06-24 |
JP7434324B2 (en) | 2024-02-20 |
AU2020414358B2 (en) | 2023-03-16 |
US20210192494A1 (en) | 2021-06-24 |
JP2022553463A (en) | 2022-12-23 |
CN113316784A (en) | 2021-08-27 |
AU2023202708A1 (en) | 2023-05-18 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11645645B2 (en) | Secure authentication based on identity data stored in a contactless card | |
US11610280B2 (en) | Steganographic image encoding of biometric template information on a card | |
US11645646B2 (en) | Determining specific terms for contactless card activation | |
US11671454B2 (en) | Enabling communications between applications in a mobile operating system | |
US11676152B2 (en) | Application-based point of sale system in mobile operating systems | |
US11922398B2 (en) | Delegated administration of permissions using a contactless card | |
US11777933B2 (en) | URL-based authentication for payment cards | |
US20240177149A1 (en) | Secure authentication based on passport data stored in a contactless card | |
US11200563B2 (en) | Account registration using a contactless card |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STPP | Information on status: patent application and granting procedure in general |
Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION |
|
AS | Assignment |
Owner name: CAPITAL ONE SERVICES, LLC, VIRGINIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:CAPURSO, NICHOLAS;EDWARDS, SAMUEL;PRIBBLE, JASON;SIGNING DATES FROM 20191027 TO 20191114;REEL/FRAME:063748/0553 |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |