Patent Publication Number: US-2022237609-A1

Title: Systems and methods for authentication of access tokens

Description:
FIELD OF THE DISCLOSURE 
     The present disclosure relates to systems and methods for authentication of access tokens. 
     BACKGROUND 
     Card-based transactions are becoming increasingly common. These transactions often involve the use of a card in communication with a point of sale device, a server, or other device. It is necessary to protect such communications from interception and unauthorized access. However, transmission of data in the clear, i.e., without encryption or other protection, is susceptible to phishing attacks and replay attacks, resulting in increased security risks and account or card misuse. These risks may be increased through the use of contactless cards, which communication with other devices wirelessly. 
     These and other deficiencies exist. Accordingly, there is a need for systems and methods for authenticating access tokens that overcome these deficiencies and provides access to one or more resources in a secure and reliable manner by protecting communications from interception and unauthorized access. 
     SUMMARY OF THE DISCLOSURE 
     Embodiments of the present disclosure provide a first device, comprising. The first device may include a memory including a counter value, transmission data, and at least one key. The first device may include a communication interface. The first device may include one or more processors in communication with the memory and communication interface. The one or more processors may be configured to create a cryptogram using the at least one key and counter value, wherein the cryptogram includes the counter value and the transmission data. The one or more processors may be configured to transmit the cryptogram via the communication interface. The one or more processors may be configured to update the counter value after transmission of the cryptogram. The one or more processors may be configured to receive an encrypted access token via the communication interface. The one or more processors may be configured to decrypt the encrypted access token. The one or more processors may be configured to store the decrypted access token in the memory. The one or more processors may be configured to transmit, after entry of the communication interface into a communication field, the access token via the communication interface for access to one or more resources, wherein the access token is encrypted. 
     Embodiments of the present disclosure provide an authentication method. The method may include creating a cryptogram using at least one key and counter value, wherein the cryptogram includes the counter value and transmission data. The method may include transmitting, via a communication interface, the cryptogram. The method may include updating the counter value. The method may include receiving, via the communication interface, an encrypted access token. The method may include decrypting the encrypted access token. The method may include storing the decrypted access token in memory. The method may include transmitting, after entry of the communication interface into a communication field, the access token via the communication interface to receive access to one or more resources, wherein the access token is encrypted. 
     Embodiments of the present disclosure provide a computer readable non-transitory medium comprising computer-executable instructions that are executed on a processor and comprising the steps of: creating a cryptogram using one or more keys and a counter value, wherein the cryptogram includes the counter value and transmission data; transmitting the cryptogram; updating the counter value; receiving an encrypted access token; decrypting the encrypted access token; transmitting, after entry of a communication interface into a communication field, the access token via the communication interface, wherein the access token is encrypted; and receiving, after authentication of the access token, access to one or more resources 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
       Various embodiments of the present disclosure, together with further objects and advantages, may best be understood by reference to the following description taken in conjunction with the accompanying drawings. 
         FIG. 1  depicts an authentication system according to an exemplary embodiment. 
         FIG. 2A  is an illustration of a contactless card according to an exemplary embodiment. 
         FIG. 2B  is an illustration of a contact pad of a contactless card according to an exemplary embodiment. 
         FIG. 3  depicts a method of authentication according to an exemplary embodiment. 
         FIG. 4  depicts a sequence diagram of a process for authentication according to an exemplary embodiment. 
         FIG. 5  depicts an authentication system according to an exemplary embodiment. 
         FIG. 6  depicts a method of authentication according to an exemplary embodiment. 
     
    
    
     DETAILED DESCRIPTION 
     The following description of embodiments provides non-limiting representative examples referencing numerals to particularly describe features and teachings of different aspects of the invention. The embodiments described should be recognized as capable of implementation separately, or in combination, with other embodiments from the description of the embodiments. A person of ordinary skill in the art reviewing the description of embodiments should be able to learn and understand the different described aspects of the invention. The description of embodiments should facilitate understanding of the invention to such an extent that other implementations, not specifically covered but within the knowledge of a person of skill in the art having read the description of embodiments, would be understood to be consistent with an application of the invention. 
     Benefits of the systems and methods disclosed herein include improved security to provide access to one or more resources by protecting communications from interception and unauthorized access. The systems and methods disclosed herein allow for the avoidance of phishing attacks and preventing replay attacks through encrypted data communications and the removal of the need to send data in the clear. In addition, by generating and authenticating access tokens and challenge responses, access tokens and cards may be securely issued, validated, and reissued, rather than collecting the cards, and programming each card for reissuance, thereby mitigating security risks, improving the user experience, and improving transaction efficiency. Accordingly, the systems and methods disclosed herein reduce the risk of fraudulent activity, such as misuse of the card or an account associated with the card. 
       FIG. 1  illustrates an authentication system  100 . The system  100  may comprise a first device  105 , a second device  112 , a third device  117 , a network  120 , a server  125 , and a database  130 . Although  FIG. 1  illustrates single instances of components of system  100 , system  100  may include any number of components. 
     System  100  may include a first device  105 . The first device  105  may comprise a contactless card, a contact-based card, or other device described herein. As further explained below in  FIGS. 2A-2B , first device  105  may include one or more processors  102 , and memory  104 . Memory  104  may include one or more applets  106  and one or more counters  108 . Each counter  108  may include a counter value. Memory  104  may include the counter value, transmission data, and at least one key. 
     First device  105  may include a communication interface  107 . The communication interface  107  may comprise communication capabilities with physical interfaces and contactless interfaces. For example, the communication interface  107  may be configured to communicate with a physical interface, such as by swiping through a card swipe interface or inserting into a card chip reader found on an automated teller machine (ATM) or other device configured to communicate over a physical interface. In other examples, the communication interface  107  may be configured to establish contactless communication with a card reading device via a short-range wireless communication method, such as NFC, Bluetooth, Wi-Fi, RFID, and other forms of contactless communication. As shown in  FIG. 1 , the communication interface  107  may be configured to communicate directly with the second device  112 , third device  117 , server  125 , and/or database  130  via network  120 . 
     First device  105  may be in data communication with any number of components of system  100 . For example, first device  105  may transmit data via network  120  to second device  112 , third device  117 , and/or server  125 . First device  105  may transmit data via network  120  to database  130 . In some examples, first device  105  may be configured to transmit data via network  120  after entry into one or more communication fields of any device. Without limitation, each entry may be associated with a tap, a swipe, a wave, and/or any combination thereof. 
     System  100  may include a second device  112 . The second device  112  may include one or more processors  113 , and memory  114 . Memory  114  may include one or more applications, including but not limited to first application  110  and second application  111 . Second device  112  may be in data communication with any number of components of system  100 . For example, second device  112  may transmit data via network  120  to server  125 . Second device  112  may transmit data via network  120  to database  130 . Without limitation, second device  112  may be a network-enabled computer. As referred to herein, a network-enabled computer may include, but is not limited to a computer device, or communications device including, e.g., a server, a network appliance, a personal computer, a workstation, a phone, a handheld PC, a personal digital assistant, a contactless card, a thin client, a fat client, an Internet browser, a kiosk, a tablet, a terminal, or other device. Second device  112  also may be a mobile device; for example, a mobile device may include an iPhone, iPod, iPad from Apple® or any other mobile device running Apple&#39;s iOS® operating system, any device running Microsoft&#39;s Windows® Mobile operating system, any device running Google&#39;s Android® operating system, and/or any other smartphone, tablet, or like wearable mobile device. 
     The second device  112  may include processing circuitry and may contain additional components, including processors, memories, error and parity/CRC checkers, data encoders, anticollision algorithms, controllers, command decoders, security primitives and tamperproofing hardware, as necessary to perform the functions described herein. The second device  112  may further include a display and input devices. The display may be any type of device for presenting visual information such as a computer monitor, a flat panel display, and a mobile device screen, including liquid crystal displays, light-emitting diode displays, plasma panels, and cathode ray tube displays. The input devices may include any device for entering information into the user&#39;s device that is available and supported by the user&#39;s device, such as a touch-screen, keyboard, mouse, cursor-control device, touch-screen, microphone, digital camera, video recorder or camcorder. These devices may be used to enter information and interact with the software and other devices described herein. 
     System  100  may include a third device  117 . The third device  117  may include one or more processors  116 , and memory  118 . Memory  118  may include one or more applications, such as application  115 . Third device  117  may be in data communication with any number of components of system  100 . For example, third device  117  may transmit data via network  120  to server  125 . Third device  117  may transmit data via network  120  to database  130 . Without limitation, third device  117  may be a network-enabled computer. As referred to herein, a network-enabled computer may include, but is not limited to a computer device, or communications device including, e.g., a server, a network appliance, a personal computer, a workstation, a phone, a handheld PC, a personal digital assistant, a contactless card, a thin client, a fat client, an Internet browser, a kiosk, a tablet, a terminal, a reader, or other device. Third device  117  also may be a mobile device; for example, a mobile device may include an iPhone, iPod, iPad from Apple® or any other mobile device running Apple&#39;s iOS® operating system, any device running Microsoft&#39;s Windows® Mobile operating system, any device running Google&#39;s Android® operating system, and/or any other smartphone, tablet, or like wearable mobile device. 
     The third device  117  may include processing circuitry and may contain additional components, including processors, memories, error and parity/CRC checkers, data encoders, anticollision algorithms, controllers, command decoders, security primitives and tamperproofing hardware, as necessary to perform the functions described herein. The third device  117  may further include a display and input devices. The display may be any type of device for presenting visual information such as a computer monitor, a flat panel display, and a mobile device screen, including liquid crystal displays, light-emitting diode displays, plasma panels, and cathode ray tube displays. The input devices may include any device for entering information into the user&#39;s device that is available and supported by the user&#39;s device, such as a touch-screen, keyboard, mouse, cursor-control device, touch-screen, microphone, digital camera, video recorder or camcorder. These devices may be used to enter information and interact with the software and other devices described herein. 
     System  100  may include a network  120 . In some examples, network  120  may be one or more of a wireless network, a wired network or any combination of wireless network and wired network, and may be configured to connect to any one of components of system  100 . For example, first device  105  may be configured to connect to server  125  via network  120 . In some examples, network  120  may include one or more of a fiber optics network, a passive optical network, a cable network, an Internet network, a satellite network, a wireless local area network (LAN), a Global System for Mobile Communication, a Personal Communication Service, a Personal Area Network, Wireless Application Protocol, Multimedia Messaging Service, Enhanced Messaging Service, Short Message Service, Time Division Multiplexing based systems, Code Division Multiple Access based systems, D-AMPS, Wi-Fi, Fixed Wireless Data, IEEE 802.11b, 802.15.1, 802.11n and 802.11g, Bluetooth, NFC, Radio Frequency Identification (RFID), Wi-Fi, and/or the like. 
     In addition, network  120  may include, without limitation, telephone lines, fiber optics, IEEE Ethernet 902.3, a wide area network, a wireless personal area network, a LAN, or a global network such as the Internet. In addition, network  120  may support an Internet network, a wireless communication network, a cellular network, or the like, or any combination thereof. Network  120  may further include one network, or any number of the exemplary types of networks mentioned above, operating as a stand-alone network or in cooperation with each other. Network  120  may utilize one or more protocols of one or more network elements to which they are communicatively coupled. Network  120  may translate to or from other protocols to one or more protocols of network devices. Although network  120  is depicted as a single network, it should be appreciated that according to one or more examples, network  120  may comprise a plurality of interconnected networks, such as, for example, the Internet, a service provider&#39;s network, a cable television network, corporate networks, such as credit card association networks, and home networks. 
     System  100  may include one or more servers  125 . In some examples, server  125  may include one or more processors  127  coupled to memory  129 . Server  125  may be configured as a central system, server or platform to control and call various data at different times to execute a plurality of workflow actions. Server  125  may be configured to connect to first device  105 . Server  125  may be in data communication with the applet  106 , application  110 , application  111 , and/or application  115 . For example, a server  125  may be in data communication with applet  106  via one or more networks  120 . First device  105  may be in communication with one or more servers  125  via one or more networks  120 , and may operate as a respective front-end to back-end pair with server  125 . First device  105  may transmit, for example from applet  106  executing thereon, one or more requests to server  125 . The one or more requests may be associated with retrieving data from server  125 . Server  125  may receive the one or more requests from first device  105 . Based on the one or more requests from applet  106 , server  125  may be configured to retrieve the requested data. Server  125  may be configured to transmit the received data to applet  106 , the received data being responsive to one or more requests. 
     In some examples, server  125  can be a dedicated server computer, such as bladed servers, or can be personal computers, laptop computers, notebook computers, palm top computers, network computers, mobile devices, wearable devices, or any processor-controlled device capable of supporting the system  100 . While  FIG. 1  illustrates a single server  125 , it is understood that other embodiments can use multiple servers or multiple computer systems as necessary or desired to support the users and can also use back-up or redundant servers to prevent network downtime in the event of a failure of a particular server. 
     Server  125  may include an application comprising instructions for execution thereon. For example, the application may comprise instructions for execution on the server  125 . The application may be in communication with any components of system  100 . For example, server  125  may execute one or more applications that enable, for example, network and/or data communications with one or more components of system  100  and transmit and/or receive data. Without limitation, server  125  may be a network-enabled computer. As referred to herein, a network-enabled computer may include, but is not limited to a computer device, or communications device including, e.g., a server, a network appliance, a personal computer, a workstation, a phone, a handheld PC, a personal digital assistant, a contactless card, a thin client, a fat client, an Internet browser, or other device. Server  125  also may be a mobile device; for example, a mobile device may include an iPhone, iPod, iPad from Apple® or any other mobile device running Apple&#39;s iOS® operating system, any device running Microsoft&#39;s Windows® Mobile operating system, any device running Google&#39;s Android® operating system, and/or any other smartphone, tablet, or like wearable mobile device. 
     The server  125  may include processing circuitry and may contain additional components, including processors, memories, error and parity/CRC checkers, data encoders, anticollision algorithms, controllers, command decoders, security primitives and tamperproofing hardware, as necessary to perform the functions described herein. The server  125  may further include a display and input devices. The display may be any type of device for presenting visual information such as a computer monitor, a flat panel display, and a mobile device screen, including liquid crystal displays, light-emitting diode displays, plasma panels, and cathode ray tube displays. The input devices may include any device for entering information into the user&#39;s device that is available and supported by the user&#39;s device, such as a touch-screen, keyboard, mouse, cursor-control device, touch-screen, microphone, digital camera, video recorder or camcorder. These devices may be used to enter information and interact with the software and other devices described herein. 
     System  100  may include one or more databases  130 . The database  130  may comprise a relational database, a non-relational database, or other database implementations, and any combination thereof, including a plurality of relational databases and non-relational databases. In some examples, the database  130  may comprise a desktop database, a mobile database, or an in-memory database. Further, the database  130  may be hosted internally by any component of system  100 , such as the first device  105  or server  125 , or the database  130  may be hosted externally to any component of the system  100 , such as the first device  105  or server  125 , by a cloud-based platform, or in any storage device that is in data communication with the first device  105  and server  125 . In some examples, database  130  may be in data communication with any number of components of system  100 . For example, server  125  may be configured to retrieve the requested data from the database  130  that is transmitted by applet  106 . Server  125  may be configured to transmit the received data from database  130  to applet  106  via network  120 , the received data being responsive to the transmitted one or more requests. In other examples, applet  106  may be configured to transmit one or more requests for the requested data from database  130  via network  120 . 
     In some examples, exemplary procedures in accordance with the present disclosure described herein can be performed by a processing arrangement and/or a computing arrangement (e.g., computer hardware arrangement). Such processing/computing arrangement can be, for example entirely or a part of, or include, but not limited to, a computer/processor that can include, for example one or more microprocessors, and use instructions stored on a computer-accessible medium (e.g., RAM, ROM, hard drive, or other storage device). For example, a computer-accessible medium can be part of the memory of the first device  105 , server  125 , and/or database  130 , or other computer hardware arrangement. 
     In some examples, a computer-accessible medium (e.g., as described herein above, a storage device such as a hard disk, floppy disk, memory stick, CD-ROM, RAM, ROM, etc., or a collection thereof) can be provided (e.g., in communication with the processing arrangement). The computer-accessible medium can contain executable instructions thereon. In addition or alternatively, a storage arrangement can be provided separately from the computer-accessible medium, which can provide the instructions to the processing arrangement so as to configure the processing arrangement to execute certain exemplary procedures, processes, and methods, as described herein above, for example. 
     The one or more processors  102  may be configured to create a cryptogram using the at least one key and the counter value. The cryptogram may include the counter value and the transmission data. The one or more processors  102  may be configured to transmit the cryptogram via the communication interface  107 . For example, the one or more processors  102  may be configured to transmit the cryptogram to one or more applications. In some examples, the one or more processors  102  may be configured to transmit the cryptogram to a first application  110  comprising instructions for execution on a second device  112 . The one or more processors  102  may be configured to update the counter value after transmission of the cryptogram. The one or more processors  102  may be configured to receive an access token via the communication interface  107 . For example, the one or more processors  102  may be configured to receive the access token from the first application  110 . In some examples, the access token may be generated and/or encrypted by the first application  110 . In some examples, the access token may be created when a user authenticates into a first or primary system, which may comprise an application, including but not limited to first application  110  comprising instructions for execution on second device  112 , or a network login, including but not limited to login associated with network  120 . At that point, the access token may be created that encapsulates the security identity that has been established through presenting one or more credentials, including but not limited to at least one selected from the group of a username and/or password, a mobile device number, an account number, a card number, and a biometric (e.g., facial scan, a retina scan, a fingerprint, and a voice input for voice recognition). A database, such as database  130 , that is initially authenticated against, may be configured to create the token. In this model, the access token is then encrypted and transmitted to the first device  105  for secure storage. When a user wishes to gain access to a second system, the first device  105  may be presented and the second system may be configured to query for it. To the extent that the access token is still valid and the first and second systems respect each other, through a protocol such as OAuth or Security Assertion Markup Language (SAML), the user may gain access to the secondary system. In some examples, the access token may be encrypted prior to transmission. For example, the first application  110  may be configured to encrypt the access token prior to transmission to the one or more processors  102  of the first device  105 . 
     The one or more processors  102  may be configured to decrypt the access token. The one or more processors  102  may be configured to store the access token in the memory  104 . The one or more processors  102  may be configured to transmit, after one or more entries of the communication interface  107  into a communication field of any device, the access token. The one or more entries may be associated with at least one selected from the group of a tap, a swipe, a wave, and/or any combination thereof. For example, the one or more processors  102  may be configured to transmit the access token to the first application  110 . The access token may be transmitted via near field communication (NFC). Without limitation, the access token may be transmitted via Bluetooth, Wi-Fi, RFID. 
     In another example, the one or more processors  102  may be configured to transmit the access token to a second application  111  comprising instructions for execution on the second device  112 . The one or more processors  102  may be configured to transmit, after one or more entries of the communication interface  107  into a communication field of the second device  112 , the access token. The one or more entries may be associated with at least one selected from the group of a tap, a swipe, a wave, and/or any combination thereof. For example, the one or more processors  102  may be configured to transmit the access token to the second application  111 . The access token may be transmitted via near field communication (NFC). Without limitation, the access token may be transmitted via Bluetooth, Wi-Fi, RFID. 
     In another example, the one or more processors  102  may be configured to transmit the access token to an application  115  comprising instructions for execution on a third device.  117  The one or more processors  102  may be configured to transmit, after one or more entries of the communication interface  107  into a communication field of a third device  117 , the access token. The one or more entries may be associated with at least one selected from the group of a tap, a swipe, a wave, and/or any combination thereof. The access token may be transmitted via near field communication (NFC). Without limitation, the access token may be transmitted via Bluetooth, Wi-Fi, RFID. 
     The access token may be transmitted for verification prior to providing access to one or more resources. For example, the application  115  comprising instructions for execution on a third device  117  may be configured to receive the access token from the one or more processors  102  and verify the access token by transmitting one or more requests to one or more servers  125 . The one or more servers  125  may be configured to receive the one or more requests from the application  115  comprising instructions for execution on the third device  117 . The one or more requests may include the access token. The one or more servers  125  may be configured to verify the access token by comparison with a reference access token to determine a successful match. In some examples, the server  125  may be configured to verify the access token. If the comparison between the access token and reference access token yields a successful match, the access token is verified and access is provided to one or more resources. If the comparison between the access token and the reference access token yields an unsuccessful match, access to one or more resources may further proceed in the following manner. For example, the access to one or more resources may be denied based on the determination of an unsuccessful match. In another example, the access to one or more resources may be re-attempted up to and including a predetermined threshold number of times by re-sending and re-receiving the access token before denying access to one or more resources. In this manner, access to one or more resources may be denied and/or permission privileges may be revoked after token usage, as further discussed below. 
     In some examples, a database  130  may be configured to verify the access token. For example, the one or more servers  125  may be configured to verify the access token by transmitting one or more requests to a database  130 . The one or more requests may include the access token. The database  130  may be configured to receive the one or more requests from the one or more servers  125 . The database  130  may be configured to verify the access token by comparison with a reference access token to determine a successful match. If the comparison between the access token and reference access token yields a successful match, the access token is verified and access is provided to one or more resources. If the comparison between the access token and the reference access token yields an unsuccessful match, access to one or more resources may further proceed in the following manner. In some examples, the access to one or more resources may be denied based on the determination of an unsuccessful match. In other examples, the request for access to one or more resources may be re-attempted up to and including a predetermined threshold number of times by re-sending and re-receiving the access token before denying access to one or more resources. In this manner, access to one or more resources may be denied and/or permission privileges may be revoked after token usage, as further discussed below. 
     The access token may comprise a limited use token. The access token may include one or more elements, such as an access identifier. The access identifier may be configured to allow a user to be identified across a plurality of systems, such as the first system and the second system. The access identifier may be unique to the user, tied to a login session, and/or any combination thereof. In some examples, the access identifier may comprise a group of identifiers which may be configured to describe the user as belonging to one or more access groups. In some examples, the token may include a one-time use token. In other examples, the token may include a time-based token. For example, the token may be restricted to usage for a predetermined time period, such as at least one selected from the group of seconds, minutes, hours, days, weeks, months, years, and/or any combination thereof. After the token has been used, for example after a one-time usage and/or after expiration of a predetermined time period usage, the token may be invalidated and no longer usable. 
     In some examples, the first application  110  comprising instructions for execution on the second device  112  may be a different application than the second application  111  comprising instructions for execution on the second device  112 . In some examples, the second device  112  may be a different device than the third device  117 . In some examples, the third device  117  may be external to the second device  112 . For example, the third device  117  may not be part of the second device  112 . In some examples, the third device  117  may be integral with the second device  112 . For example, the third device  117  may be a part of or internal to the second device  112 . The third device  117  may comprise a reader, such as a card reader. In some examples, the card reader may be configured to provide access to a physical space. In some examples, the card reader may be configured to provide access to a digital experience. In some examples, the card reader may be configured to provide access to a ticketed event. In some examples, the card reader may be configured to provide access to a safe deposit box. In some examples, the card reader may be configured to provide access to another device, such as a network-enabled computer. 
     In other examples, the one or more processors  102  may be configured to receive one or more challenges via the communication interface  107  from the first application  110  comprising instructions for execution on the second device  112 . The challenge may include a public key and an encrypted test. The one or more processors  102  may be configured to transmit one or more responses that are responsive to the one or more challenges via the communication interface  107 . For example, the one or more processors  102  may be configured to transmit, via the communication interface  107 , a challenge response to the first application  110  comprising instructions for execution on the second device  112 . 
     In other examples, the one or more processors  102  may be configured to receive one or more challenges via the communication interface  107 . For example, the one or more processors  102  may be configured to receive a challenge from the application  115  comprising instructions for execution on the third device  117 . The challenge may include a public key and an encrypted test. The one or more processors  102  may be configured to transmit one or more responses that are responsive to the one or more challenges via the communication interface  107 . For example, the one or more processors  102  may be configured to transmit, via the communication interface  107 , a challenge response to the application  115  comprising instructions for execution on the third device  117 . 
     The one or more processors  102  may be configured to decrypt the encrypted test. For example, the one or more processors  102  may be configured to decrypt the encrypted test using the private key and generate a decrypted test. In some examples, the one or more processors  102  may be configured to include the decrypted test in the challenge response transmitted, via the communication interface  107 . In some examples, the one or more processors  102  may be configured to transmit, via the communication interface  107 , the challenge response including the decrypted test to the first application  110  comprising instructions for execution on the second device  112 . In other examples, the one or more processors  102  may be configured to transmit, via the communication interface  107 , the challenge response including the decrypted test to the second application  111  comprising instructions for execution on the second device  112 . In other examples, the one or more processors  102  may be configured to transmit, via the communication interface  107 , the challenge response including the decrypted test to the application  115  comprising instructions for execution on the third device  117 . 
     The second device  112  and/or third device  117  may be in data communication with one or more servers  125  and/or one or more databases  130 . In some examples, the first application  110  and second application  111  comprising instructions for execution on the second device  112  may be in data communication with the one or more servers  125  and/or one or more databases  130  via network  120 . The application  115  comprising instructions for execution on the third device  117  may be in data communication with the one or more servers  125  and/or one or more databases  130  via network  120 . The server  125  may be configured to receive one or more challenges from the application  115  comprising instructions for execution on the third device  117 . The application  115  comprising instructions for execution on the third device  117  may be configured to transmit the one or more challenges to the server  125 . The challenge may include a public key and an encrypted test. The server  125  may be configured to transmit one or more responses to the application  115  comprising instructions for execution on the third device  117  and that are responsive to the one or more challenges. The server  125  may be configured to generate a decrypted test by decrypting the encrypted test using the private key. In addition, the server  125  may be configured to include the decrypted test in the challenge response. 
     In some examples, the card reader may be configured to provide access to one or more resources, such as a physical space. As discussed above, the card reader may be internal to the second device  112 . In other examples, the card reader may be external to the second device  112 , such as a part of a third device  117 . For example, the access may be provided after successful authentication of the token. In some examples, the card reader may be configured to provide access to the physical space after one or more entries of the communication interface  107  into a communication field of a device, such as device  112  or device  117 , associated with the card reader. Without limitation, the physical space may include any space of a building, a room, a school, a governmental agency, an elevator, or the like such that the card reader is configured to grant access thereto via the one or more entries that are part of the token validation. In some examples, the physical space may also include any space or location where mobile devices, such as a cell phone or tablet or laptop or universal serial bus device, are restricted or otherwise prohibited, such as a cloud server facility or governmental facility or any other secure facility. 
     In some examples, the card reader may be configured to provide access to a digital experience. As discussed above, the card reader may be internal to the second device  112 . In other examples, the card reader may be external to the second device  112 , such as a part of a third device  117 . For example, the access may be provided after successful authentication of the token. In some examples, the card reader may be configured to provide access to the digital experience after one or more entries of the communication interface  107  into a communication field of a device, such as device  112  or device  117 , associated with the card reader. Without limitation, the digital experience may be associated with any application comprising instructions for execution on any device, a virtual reality program, a mobile or web browser, an email client, a game, or the like. 
     In some examples, the card reader may be configured to provide access to a ticketed event. As discussed above, the card reader may be internal to the second device  112 . In other examples, the card reader may be external to the second device  112 , such as a part of a third device  117 . For example, the access may be provided after successful authentication of the token. In some examples, the card reader may be configured to provide access to the ticketed event after one or more entries of the communication interface  107  into a communication field of a device, such as device  112  or device  117 , associated with the card reader. Without limitation, the ticketed event may be associated with a school event, a sporting event, a concert event, a private event, a government event, a music event, or the like. 
     In some examples, the card reader may be configured to provide access to a safe deposit box. As discussed above, the card reader may be internal to the second device  112 . In other examples, the card reader may be external to the second device  112 , such as a part of a third device  117 . For example, the access may be provided after successful authentication of the token. In some examples, the card reader may be configured to provide access to the safe deposit box after one or more entries of the communication interface  107  into a communication field of a device, such as device  112  or device  117 , associated with the card reader. In some examples, the card reader may be external to the safe deposit box. In other examples, the card reader may be internal to the safe deposit box. In some examples, the safe deposit box may comprise a storage enclosure configured to store one or more items, such as a product or grocery item, available for access to the retrievable one or more items. 
     In some examples, the card reader may be configured to provide access to another device, such as a network-enabled computer. In other examples, the card reader can be configured to provide access to a secure or offline computer, configured for communication only with the card reader. The card reader may be configured to read the access token from the first device  105  and pass it to the reader. The card reader may be configured to share the access token with or otherwise make accessible to the authentication system  100 . As previously explained, to the extent that the authentication system  100  respects the access token, through a protocol such as OAuth or SAML, then the user may gain access to authentication system  100 . 
       FIG. 2A  illustrates one or more first devices  200 . First device  200  may reference the same or similar components of first device  105 , as explained above with respect to  FIG. 1 . Although  FIGS. 2A and 2B  illustrate single instances of components of first device  200 , any number of components may be utilized. 
     First device  200  may be configured to communicate with one or more components of system  100 . First device  200  may comprise a contact-based card or contactless card, which may comprise a payment card, such as a credit card, debit card, or gift card, issued by a service provider  205  displayed on the front or back of the card  200 . In some examples, the contactless card  200  is not related to a payment card, and may comprise, without limitation, an identification card, a membership card, and a transportation card. In some examples, the payment card may comprise a dual interface contactless payment card. The contactless card  200  may comprise a substrate  210 , which may include a single layer or one or more laminated layers composed of plastics, metals, and other materials. Exemplary substrate materials include polyvinyl chloride, polyvinyl chloride acetate, acrylonitrile butadiene styrene, polycarbonate, polyesters, anodized titanium, palladium, gold, carbon, paper, and biodegradable materials. In some examples, the contactless card  200  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  200  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  200  may also include identification information  215  displayed on the front and/or back of the card, and a contact pad  220 . The contact pad  220  may be configured to establish contact with another communication device, including but not limited to a user device, smart phone, laptop, desktop, or tablet computer. The contactless card  200  may also include processing circuitry, antenna and other components not shown in  FIG. 2A . These components may be located behind the contact pad  220  or elsewhere on the substrate  210 . The contactless card  200  may also include a magnetic strip or tape, which may be located on the back of the card (not shown in  FIG. 2A ). 
     As illustrated in  FIG. 2B , the contact pad  220  of  FIG. 2A  may include processing circuitry  225  for storing and processing information, including a processor  230 , such as a microprocessor, and a memory  235 . It is understood that the processing circuitry  225  may contain additional components, including processors, memories, error and parity/CRC checkers, data encoders, anticollision algorithms, controllers, command decoders, security primitives and tamperproofing hardware, as necessary to perform the functions described herein. 
     The memory  235  may be a read-only memory, write-once read-multiple memory or read/write memory, e.g., RAM, ROM, and EEPROM, and the contactless card  200  may include one or more of these memories. A read-only memory may be factory programmable as read-only or one-time programmable. One-time programmability provides the opportunity to write once then read many times. A write once/read-multiple memory may be programmed at a point in time after the memory chip has left the factory. Once the memory is programmed, it may not be rewritten, but it may be read many times. A read/write memory may be programmed and re-programed many times after leaving the factory. It may also be read many times. 
     The memory  235  may be configured to store one or more applets  240 , one or more counters  245 , and a customer identifier  250 . The one or more applets  240  may comprise one or more software applications configured to execute on one or more contactless cards, such as Java Card applet. However, it is understood that applets  240  are not limited to Java Card applets, and instead may be any software application operable on contactless cards or other devices having limited memory. The one or more counters  245  may comprise a numeric counter sufficient to store an integer. The customer identifier  250  may comprise a unique alphanumeric identifier assigned to a user of the contactless card  200 , and the identifier may distinguish the user of the contactless card from other contactless card users. In some examples, the customer identifier  250  may identify both a customer and an account assigned to that customer and may further identify the contactless card associated with the customer&#39;s account. 
     The processor and memory elements of the foregoing exemplary embodiments are described with reference to the contact pad, but the present disclosure is not limited thereto. It is understood that these elements may be implemented outside of the pad  220  or entirely separate from it, or as further elements in addition to processor  230  and memory  235  elements located within the contact pad  220 . 
     In some examples, the contactless card  200  may comprise one or more antennas  255 . The one or more antennas  255  may be placed within the contactless card  200  and around the processing circuitry  225  of the contact pad  220 . For example, the one or more antennas  255  may be integral with the processing circuitry  225  and the one or more antennas  255  may be used with an external booster coil. As another example, the one or more antennas  255  may be external to the contact pad  220  and the processing circuitry  225 . 
     In an embodiment, the coil of contactless card  200  may act as the secondary of an air core transformer. The terminal may communicate with the contactless card  200  by cutting power or amplitude modulation. The contactless card  200  may infer the data transmitted from the terminal using the gaps in the contactless card&#39;s power connection, which may be functionally maintained through one or more capacitors. The contactless card  200  may communicate back by switching a load on the contactless card&#39;s coil or load modulation. Load modulation may be detected in the terminal&#39;s coil through interference. 
       FIG. 3  depicts a method  300  of authentication.  FIG. 3  may reference the same or similar components of system  100 , and first device  200  of  FIG. 2A  and  FIG. 2B . 
     At block  305 , the method  300  may include creating a cryptogram using at least one key and a counter value. For example, one or more processors of a first device may be configured to create a cryptogram using the at least one key and the counter value. The cryptogram may include the counter value and the transmission data. The first device may include a memory containing one or more keys, including the at least one key, a counter value, and the transmission data. The first device may further include a communication interface. 
     At block  310 , the method  300  may include transmitting the cryptogram. For example, the one or more processors may be configured to transmit the cryptogram via the communication interface. For example, the one or more processors may be configured to transmit the cryptogram to one or more applications. In some examples, the one or more processors may be configured to transmit the cryptogram to a first application comprising instructions for execution on a second device. 
     At block  315 , the method  300  may include updating the counter value. For example, the one or more processors may be configured to update the counter value after transmission of the cryptogram. 
     At block  320 , the method  300  may include receiving, via a communication interface, an encrypted access token. For example, the one or more processors may be configured to receive an access token via the communication interface. In some examples, the one or more processors may be configured to receive the access token from the first application. In some examples, the access token may be generated and/or encrypted by the first application. In some examples, the access token may be created when a user authenticates into a first or primary system, which may comprise an application, including but not limited to first application comprising instructions for execution on second device, or a network login. At that point, the access token may be created that encapsulates the security identity that has been established through presenting one or more credentials, including but not limited to at least one selected from the group of a username and/or password, a mobile device number, an account number, a card number, and a biometric (e.g., facial scan, a retina scan, a fingerprint, and a voice input for voice recognition). A database that is initially authenticated against, may be configured to create the token. In this model, the access token is then encrypted and transmitted to the first device for secure storage. When a user wishes to gain access to a second system, the first device may be presented and the second system may be configured to query for it. To the extent that the access token is still valid and the first and second systems respect each other, through a protocol such as OAuth or SAML, the user may gain access to the secondary system. In some examples, the access token may be encrypted prior to transmission. For example, the first application may be configured to encrypt the access token prior to transmission to the one or more processors of the first device. 
     At block  325 , the method  300  may include decrypting the encrypted access token. For example, the one or more processors may be configured to decrypt the access token. 
     At block  330 , the method  300  may include storing the decrypted access token. For example, the one or more processors may be configured to store the access token in the memory. 
     At block  335 , the method  300  may include transmitting, after entry of the communication interface into a communication field, the access token for authentication to receive access to one or more resources. For example, the one or more processors may be configured to transmit, after one or more entries of the communication interface into a communication field of any device, the access token. The one or more entries may be associated with at least one selected from the group of a tap, a swipe, a wave, and/or any combination thereof. For example, the one or more processors may be configured to transmit the access token to the first application. The access token may be transmitted via near field communication (NFC). Without limitation, the access token may be transmitted via Bluetooth, Wi-Fi, RFID. 
     In another example, the one or more processors may be configured to transmit the access token to a second application comprising instructions for execution on the second device. The one or more processors may be configured to transmit, after one or more entries of the communication interface into a communication field of the second device, the access token. The one or more entries may be associated with at least one selected from the group of a tap, a swipe, a wave, and/or any combination thereof. For example, the one or more processors may be configured to transmit the access token to the second application. The access token may be transmitted via near field communication (NFC). Without limitation, the access token may be transmitted via Bluetooth, Wi-Fi, RFID. 
     In another example, the one or more processors may be configured to transmit the access token to an application comprising instructions for execution on a third device. The one or more processors may be configured to transmit, after one or more entries of the communication interface into a communication field of a third device, the access token. The one or more entries may be associated with at least one selected from the group of a tap, a swipe, a wave, and/or any combination thereof. The access token may be transmitted via near field communication (NFC). Without limitation, the access token may be transmitted via Bluetooth, Wi-Fi, RFID. 
     The access token may be transmitted for verification prior to providing access to one or more resources. For example, the application comprising instructions for execution on a third device may be configured to receive the access token from the one or more processors and verify the access token by transmitting one or more requests to one or more servers. The one or more servers may be configured to receive the one or more requests from the application comprising instructions for execution on the third device. The one or more requests may include the access token. The one or more servers may be configured to verify the access token by comparison with a reference access token to determine a successful match. In some examples, the server may be configured to verify the access token. If the comparison between the access token and reference access token yields a successful match, the access token is verified and access is provided to one or more resources. If the comparison between the access token and the reference access token yields an unsuccessful match, access to one or more resources may further proceed in the following manner. For example, the access to one or more resources may be denied based on the determination of an unsuccessful match. In another example, the access to one or more resources may be re-attempted up to and including a predetermined threshold number of times by re-sending and re-receiving the access token before denying access to one or more resources. In this manner, access to one or more resources may be denied and/or permission privileges may be revoked after token usage, as further discussed below. 
     In some examples, a database may be configured to verify the access token. For example, the one or more servers may be configured to verify the access token by transmitting one or more requests to a database. The one or more requests may include the access token. The database may be configured to receive the one or more requests from the one or more servers. The database may be configured to verify the access token by comparison with a reference access token to determine a successful match. If the comparison between the access token and reference access token yields a successful match, the access token is verified and access is provided to one or more resources. If the comparison between the access token and the reference access token yields an unsuccessful match, access to one or more resources may further proceed in the following manner. In some examples, the access to one or more resources may be denied based on the determination of an unsuccessful match. In other examples, the request for access to one or more resources may be re-attempted up to and including a predetermined threshold number of times by re-sending and re-receiving the access token before denying access to one or more resources. In this manner, access to one or more resources may be denied and/or permission privileges may be revoked after token usage, as further discussed below. 
     The access token may comprise a limited use token. The access token may include one or more elements, such as an access identifier. The access identifier may be configured to allow a user to be identified across a plurality of systems, such as the first system and the second system. The access identifier may be unique to the user, tied to a login session, and/or any combination thereof. In some examples, the access identifier may comprise a group of identifiers which may be configured to describe the user as belonging to one or more access groups. In some examples, the token may include a one-time use token. In other examples, the token may include a time-based token. For example, the token may be restricted to usage for a predetermined time period, such as at least one selected from the group of seconds, minutes, hours, days, weeks, months, years, and/or any combination thereof. After the token has been used, for example after a one-time usage and/or after expiration of a predetermined time period usage, the token may be invalidated and no longer usable. 
     In some examples, the first application comprising instructions for execution on the second device may be a different application than the second application comprising instructions for execution on the second device. In some examples, the second device may be a different device than the third device. In some examples, the third device may be external to the second device. For example, the third device may not be part of the second device. In some examples, the third device may be integral with the second device. For example, the third device may be a part of or internal to the second device. The third device may comprise a reader, such as a card reader. In some examples, the card reader may be configured to provide access to a physical space. In some examples, the card reader may be configured to provide access to a digital experience. In some examples, the card reader may be configured to provide access to a ticketed event. In some examples, the card reader may be configured to provide access to a safe deposit box. 
     In other examples, the one or more processors may be configured to receive one or more challenges via the communication interface from the first application comprising instructions for execution on the second device. The challenge may include a public key and an encrypted test. The one or more processors may be configured to transmit one or more responses that are responsive to the one or more challenges via the communication interface. For example, the one or more processors may be configured to transmit, via the communication interface, a challenge response to the first application comprising instructions for execution on the second device. 
     In other examples, the one or more processors may be configured to receive one or more challenges via the communication interface. For example, the one or more processors may be configured to receive a challenge from the application comprising instructions for execution on the third device. The challenge may include a public key and an encrypted test. The one or more processors may be configured to transmit one or more responses that are responsive to the one or more challenges via the communication interface. For example, the one or more processors may be configured to transmit, via the communication interface, a challenge response to the application comprising instructions for execution on the third device. 
     The one or more processors may be configured to decrypt the encrypted test. For example, the one or more processors may be configured to decrypt the encrypted test using the private key and generate a decrypted test. In some examples, the one or more processors may be configured to include the decrypted test in the challenge response transmitted, via the communication interface. In some examples, the one or more processors may be configured to transmit, via the communication interface, the challenge response including the decrypted test to the first application comprising instructions for execution on the second device. In other examples, the one or more processors may be configured to transmit, via the communication interface, the challenge response including the decrypted test to the second application comprising instructions for execution on the second device. In other examples, the one or more processors may be configured to transmit, via the communication interface, the challenge response including the decrypted test to the application comprising instructions for execution on the third device. 
     The second device and/or third device may be in data communication with one or more servers and/or one or more databases. In some examples, the first application and second application comprising instructions for execution on the second device may be in data communication with the one or more servers and/or one or more databases. The application comprising instructions for execution on the third device may be in data communication with the one or more servers and/or one or more databases. The server may be configured to receive one or more challenges from the application comprising instructions for execution on the third device. The application comprising instructions for execution on the third device may be configured to transmit the one or more challenges to the server. The challenge may include a public key and an encrypted test. The server may be configured to transmit one or more responses to the application comprising instructions for execution on the third device and that are responsive to the one or more challenges. The server may be configured to generate a decrypted test by decrypting the encrypted test using the private key. In addition, the server may be configured to include the decrypted test in the challenge response. 
     In some examples, the card reader may be configured to provide access to one or more resources, such as a physical space. As discussed above, the card reader may be internal to the second device. In other examples, the card reader may be external to the second device, such as a part of a third device. For example, the access may be provided after successful authentication of the token. In some examples, the card reader may be configured to provide access to the physical space after one or more entries of the communication interface into a communication field of a device associated with the card reader. Without limitation, the physical space may include any space of a building, a room, a school, a governmental agency, an elevator, or the like such that the card reader is configured to grant access thereto via the one or more entries that are part of the token validation. In some examples, the physical space may also include any space or location where mobile devices, such as a cell phone or tablet or laptop or universal serial bus device, are restricted or otherwise prohibited, such as a cloud server facility or governmental facility or any other secure facility. 
     In some examples, the card reader may be configured to provide access to a digital experience. As discussed above, the card reader may be internal to the second device. In other examples, the card reader may be external to the second device, such as a part of a third device. For example, the access may be provided after successful authentication of the token. In some examples, the card reader may be configured to provide access to the digital experience after one or more entries of the communication interface into a communication field of a device associated with the card reader. Without limitation, the digital experience may be associated with any application comprising instructions for execution on any device, a virtual reality program, a mobile or web browser, an email client, a game, or the like. 
     In some examples, the card reader may be configured to provide access to a ticketed event. As discussed above, the card reader may be internal to the second device. In other examples, the card reader may be external to the second device, such as a part of a third device. For example, the access may be provided after successful authentication of the token. In some examples, the card reader may be configured to provide access to the ticketed event after one or more entries of the communication interface into a communication field of a device associated with the card reader. Without limitation, the ticketed event may be associated with a school event, a sporting event, a concert event, a private event, a government event, a music event, or the like. 
     In some examples, the card reader may be configured to provide access to a safe deposit box. As discussed above, the card reader may be internal to the second device. In other examples, the card reader may be external to the second device, such as a part of a third device. For example, the access may be provided after successful authentication of the token. In some examples, the card reader may be configured to provide access to the safe deposit box after one or more entries of the communication interface into a communication field of a device associated with the card reader. In some examples, the card reader may be external to the safe deposit box. In other examples, the card reader may be internal to the safe deposit box. In some examples, the safe deposit box may comprise a storage enclosure configured to store one or more items, such as a product or grocery item, available for access to the retrievable one or more items. 
       FIG. 4  depicts a sequence diagram  400  of a process for authentication according to an exemplary embodiment.  FIG. 4  may reference the same or similar components of system  100 , first device  200  of  FIG. 2A  and  FIG. 2B , and method  300  of  FIG. 3 . 
     At step  405 , one or more processors may be configured to transmit a cryptogram via a communication interface. For example, one or more processors of a first device may be configured to create a cryptogram using the at least one key and the counter value. The cryptogram may include the counter value and the transmission data. The first device may include a memory containing one or more keys, including the at least one key, a counter value, and the transmission data. The first device may further include a communication interface. For example, the one or more processors may be configured to transmit the cryptogram via the communication interface. For example, the one or more processors may be configured to transmit the cryptogram to one or more applications of a user device or a second device. In some examples, the one or more processors may be configured to transmit the cryptogram to a first application comprising instructions for execution on a second device. 
     At step  410 , an application of a user device or second device may be configured to transmit an encrypted first token. For example, the application of the user device may be configured to transmit, via a communication interface, an encrypted first token after validation of the cryptogram. The encrypted first token may comprise an encrypted access token. In some examples, the access token may be generated and/or encrypted by the first application. In some examples, the access token may be created when a user authenticates into a first or primary system, which may comprise an application, including but not limited to first application comprising instructions for execution on second device, or a network login. At that point, the access token may be created that encapsulates the security identity that has been established through presenting one or more credentials, including but not limited to at least one selected from the group of a username and/or password, a mobile device number, an account number, a card number, and a biometric (e.g., facial scan, a retina scan, a fingerprint, and a voice input for voice recognition). A database that is initially authenticated against, may be configured to create the token. In this model, the access token is then encrypted and transmitted to the first device for secure storage. When a user wishes to gain access to a second system, the first device may be presented and the second system may be configured to query for it. To the extent that the access token is still valid and the first and second systems respect each other, through a protocol such as OAuth or SAML, the user may gain access to the secondary system. In some examples, the access token may be encrypted prior to transmission. For example, the first application may be configured to encrypt the access token prior to transmission to the one or more processors of the first device. 
     The first token may comprise a limited use token. The access token may include one or more elements, such as an access identifier. The access identifier may be configured to allow a user to be identified across a plurality of systems, such as the first system and the second system. The access identifier may be unique to the user, tied to a login session, and/or any combination thereof. In some examples, the access identifier may comprise a group of identifiers which may be configured to describe the user as belonging to one or more access groups. In some examples, the token may include a one-time use token. In other examples, the token may include a time-based token. For example, the token may be restricted to usage for a predetermined time period, such as at least one selected from the group of seconds, minutes, hours, days, weeks, months, years, and/or any combination thereof. After the token has been used, for example after a one-time usage and/or after expiration of a predetermined time period usage, the token may be invalidated and no longer usable. 
     At step  415 , the one or more processors may be configured to decrypt the encrypted first token and store into memory. For example, the one or more processors may be configured to receive an encrypted first token via the communication interface from the application of the user device. The decrypted first token may be stored into memory of the first device. 
     At step  420 , the one or more processors may be configured to transmit, after entry of the communication interface into a communication field of a reader, the first token to a reader. As previously discussed, the reader may be external to the user device. In other examples, the reader may be internal to the user device. The reader may be a different device than the user device. The reader may include an application comprising instructions for execution that differs from the application comprising instructions for execution on the user device. The reader may be configured to read one or more messages from a tag, such as an NFC tag, from the first device. 
     The one or more processors may be configured to transmit the first token to an application comprising instructions for execution on a third device, such as a reader. The one or more processors may be configured to transmit, after one or more entries of the communication interface into a communication field of a third device, the access token. The one or more entries may be associated with at least one selected from the group of a tap, a swipe, a wave, and/or any combination thereof. The access token may be transmitted via near field communication (NFC). Without limitation, the access token may be transmitted via Bluetooth, Wi-Fi, RFID. 
     At step  425 , the reader may be configured to transmit one or more challenges to the one or more processors. For example, the one or more processors may be configured to receive one or more challenges via the communication interface from the reader. For example, the one or more processors may be configured to receive a challenge from the application comprising instructions for execution on the third device. The challenge may include a public key and an encrypted test. 
     At step  430 , the one or more processors may be configured to transmit one or more challenge responses, responsive to the one or more challenges, to the reader. For example, the one or more processors may be configured to transmit one or more responses that are responsive to the one or more challenges via the communication interface to the reader. For example, the one or more processors may be configured to transmit, via the communication interface, a challenge response to the application comprising instructions for execution on the third device. The one or more processors may be configured to decrypt the encrypted test. For example, the one or more processors may be configured to decrypt the encrypted test using the private key and generate a decrypted test. In some examples, the one or more processors may be configured to include the decrypted test in the challenge response transmitted, via the communication interface. For example, the one or more processors may be configured to transmit, via the communication interface, the challenge response including the decrypted test to the application comprising instructions for execution on the third device. 
     At step  435 , the reader may be configured to authenticate the one or more challenge responses to grant access to one or more resources. In some examples, the card reader may be configured to provide access to a physical space. In some examples, the card reader may be configured to provide access to a digital experience. In some examples, the card reader may be configured to provide access to a ticketed event. In some examples, the card reader may be configured to provide access to a safe deposit box. 
     In some examples, the card reader may be configured to provide access to one or more resources, such as a physical space. As discussed above, the card reader may be internal to the second device. In other examples, the card reader may be external to the second device, such as a part of a third device. For example, the access may be provided after successful authentication of the token. In some examples, the card reader may be configured to provide access to the physical space after one or more entries of the communication interface into a communication field of a device associated with the card reader. Without limitation, the physical space may include any space of a building, a room, a school, a governmental agency, an elevator, or the like such that the card reader is configured to grant access thereto via the one or more entries that are part of the token validation. In some examples, the physical space may also include any space or location where mobile devices, such as a cell phone or tablet or laptop or universal serial bus device, are restricted or otherwise prohibited, such as a cloud server facility or governmental facility or any other secure facility. 
     In some examples, the card reader may be configured to provide access to a digital experience. As discussed above, the card reader may be internal to the second device. In other examples, the card reader may be external to the second device, such as a part of a third device. For example, the access may be provided after successful authentication of the token. In some examples, the card reader may be configured to provide access to the digital experience after one or more entries of the communication interface into a communication field of a device associated with the card reader. Without limitation, the digital experience may be associated with any application comprising instructions for execution on any device, a virtual reality program, a mobile or web browser, an email client, a game, or the like. 
     In some examples, the card reader may be configured to provide access to a ticketed event. As discussed above, the card reader may be internal to the second device. In other examples, the card reader may be external to the second device, such as a part of a third device. For example, the access may be provided after successful authentication of the token. In some examples, the card reader may be configured to provide access to the ticketed event after one or more entries of the communication interface into a communication field of a device associated with the card reader. Without limitation, the ticketed event may be associated with a school event, a sporting event, a concert event, a private event, a government event, a music event, or the like. 
     In some examples, the card reader may be configured to provide access to a safe deposit box. As discussed above, the card reader may be internal to the second device. In other examples, the card reader may be external to the second device, such as a part of a third device. For example, the access may be provided after successful authentication of the token. In some examples, the card reader may be configured to provide access to the safe deposit box after one or more entries of the communication interface into a communication field of a device associated with the card reader. In some examples, the card reader may be external to the safe deposit box. In other examples, the card reader may be internal to the safe deposit box. In some examples, the safe deposit box may comprise a storage enclosure configured to store one or more items, such as a product or grocery item, available for access to the retrievable one or more items. 
       FIG. 5  depicts an authentication system  500  according to an exemplary embodiment.  FIG. 5  may reference the same or similar components of system  100 , first device  200  of  FIG. 2A  and  FIG. 2B , method  300  of  FIG. 3 , and sequence diagram  400  of  FIG. 4 . Authentication system  500  may include first device  505 , second device  510 , and network  515 . Although  FIG. 5  illustrates single instances of components of system  500 , system  500  may include any number of components. 
     System  500  may include a first device  505 . The first device  505  may comprise a contactless card, a contact-based card, or other device described herein. As previously explained, first device  505  may include one or more processors  502 , and memory  504 . Memory  504  may include one or more applets  506  and one or more counters  508 . Each counter  508  may include a counter value. Memory  504  may include the counter value, transmission data, and at least one key. 
     First device  505  may include a communication interface  507 . The communication interface  507  may comprise communication capabilities with physical interfaces and contactless interfaces. For example, the communication interface  507  may be configured to communicate with a physical interface, such as by swiping through a card swipe interface or inserting into a card chip reader found on an automated teller machine (ATM) or other device configured to communicate over a physical interface. In other examples, the communication interface  507  may be configured to establish contactless communication with a card reading device via a short-range wireless communication method, such as NFC, Bluetooth, Wi-Fi, RFID, and other forms of contactless communication. As shown in  FIG. 5 , the communication interface  507  may be configured to communicate directly with the second device  510  via network  515 . 
     First device  505  may be in data communication with any number of components of system  100 . For example, first device  505  may transmit data via network  515  to second device  510 . First device  505  may transmit and/or receive data via network  515 . In some examples, first device  505  may be configured to transmit data via network  515  after entry of communication interface  507  into one or more communication fields of any device. Without limitation, each entry may be associated with a tap, a swipe, a wave, and/or any combination thereof. 
     System  500  may include a second device  510 . The second device  510  may include one or more processors  512 , memory  514 , and reader  519 . Memory  514  may include one or more applications, including but not limited to first application  516  and second application  518 . The reader  519  may be configured to read one or more messages from a tag, such as an NFC tag, from the first device  505 . Second device  510  may be in data communication with any number of components of system  500 . For example, second device  510  may transmit and/or receive data via network  515  to and from first device  505 . Without limitation, second device  510  may be a network-enabled computer. As referred to herein, a network-enabled computer may include, but is not limited to a computer device, or communications device including, e.g., a server, a network appliance, a personal computer, a workstation, a phone, a handheld PC, a personal digital assistant, a contactless card, a thin client, a fat client, an Internet browser, a kiosk, a tablet, a terminal, or other device. Second device  510  also may be a mobile device; for example, a mobile device may include an iPhone, iPod, iPad from Apple® or any other mobile device running Apple&#39;s iOS® operating system, any device running Microsoft&#39;s Windows® Mobile operating system, any device running Google&#39;s Android® operating system, and/or any other smartphone, tablet, or like wearable mobile device. 
     The second device  510  may include processing circuitry and may contain additional components, including processors, memories, error and parity/CRC checkers, data encoders, anticollision algorithms, controllers, command decoders, security primitives and tamperproofing hardware, as necessary to perform the functions described herein. The second device  510  may further include a display and input devices. The display may be any type of device for presenting visual information such as a computer monitor, a flat panel display, and a mobile device screen, including liquid crystal displays, light-emitting diode displays, plasma panels, and cathode ray tube displays. The input devices may include any device for entering information into the user&#39;s device that is available and supported by the user&#39;s device, such as a touch-screen, keyboard, mouse, cursor-control device, touch-screen, microphone, digital camera, video recorder or camcorder. These devices may be used to enter information and interact with the software and other devices described herein. 
     System  500  may include a network  515 . In some examples, network  515  may be one or more of a wireless network, a wired network or any combination of wireless network and wired network, and may be configured to connect to any one of components of system  500 . For example, first device  505  may be configured to connect to device  510  via network  515 . In some examples, network  515  may include one or more of a fiber optics network, a passive optical network, a cable network, an Internet network, a satellite network, a wireless local area network (LAN), a Global System for Mobile Communication, a Personal Communication Service, a Personal Area Network, Wireless Application Protocol, Multimedia Messaging Service, Enhanced Messaging Service, Short Message Service, Time Division Multiplexing based systems, Code Division Multiple Access based systems, D-AMPS, Wi-Fi, Fixed Wireless Data, IEEE 802.11b, 802.15.1, 802.11n and 802.11g, Bluetooth, NFC, Radio Frequency Identification (RFID), Wi-Fi, and/or the like. 
     In addition, network  515  may include, without limitation, telephone lines, fiber optics, IEEE Ethernet 902.3, a wide area network, a wireless personal area network, a LAN, or a global network such as the Internet. In addition, network  515  may support an Internet network, a wireless communication network, a cellular network, or the like, or any combination thereof. Network  515  may further include one network, or any number of the exemplary types of networks mentioned above, operating as a stand-alone network or in cooperation with each other. Network  515  may utilize one or more protocols of one or more network elements to which they are communicatively coupled. Network  515  may translate to or from other protocols to one or more protocols of network devices. Although network  515  is depicted as a single network, it should be appreciated that according to one or more examples, network  515  may comprise a plurality of interconnected networks, such as, for example, the Internet, a service provider&#39;s network, a cable television network, corporate networks, such as credit card association networks, and home networks. 
     In some examples, exemplary procedures in accordance with the present disclosure described herein can be performed by a processing arrangement and/or a computing arrangement (e.g., computer hardware arrangement). Such processing/computing arrangement can be, for example entirely or a part of, or include, but not limited to, a computer/processor that can include, for example one or more microprocessors, and use instructions stored on a computer-accessible medium (e.g., RAM, ROM, hard drive, or other storage device). For example, a computer-accessible medium can be part of the memory of the first device  505 , or other computer hardware arrangement. 
     In some examples, a computer-accessible medium (e.g., as described herein above, a storage device such as a hard disk, floppy disk, memory stick, CD-ROM, RAM, ROM, etc., or a collection thereof) can be provided (e.g., in communication with the processing arrangement). The computer-accessible medium can contain executable instructions thereon. In addition or alternatively, a storage arrangement can be provided separately from the computer-accessible medium, which can provide the instructions to the processing arrangement so as to configure the processing arrangement to execute certain exemplary procedures, processes, and methods, as described herein above, for example. 
     The one or more processors  502  may be configured to create a cryptogram using the at least one key and the counter value. The cryptogram may include the counter value and the transmission data. The one or more processors  502  may be configured to transmit the cryptogram via the communication interface  507 . For example, the one or more processors  502  may be configured to transmit the cryptogram to one or more applications for verification. In some examples, the one or more processors  502  may be configured to transmit the cryptogram to a first application  516  comprising instructions for execution on a second device  510 . The one or more processors  502  may be configured to update the counter value after transmission and verification of the cryptogram. The one or more processors  502  may be configured to receive an access token via the communication interface  507  after verification of the cryptogram. For example, the one or more processors  502  may be configured to receive the access token from the first application  516 . In some examples, the access token may be generated and/or encrypted by the first application  516 . In some examples, the access token may be created when a user authenticates into a first or primary system, which may comprise an application, including but not limited to first application  516  comprising instructions for execution on first device  510 , or a network login, including but not limited to login associated with network  515 . At that point, the access token may be created that encapsulates the security identity that has been established through presenting one or more credentials, including but not limited to at least one selected from the group of a username and/or password, a mobile device number, an account number, a card number, and a biometric (e.g., facial scan, a retina scan, a fingerprint, and a voice input for voice recognition). A database may also be included of system  500  and is initially authenticated against, may be configured to create the token. In this model, the access token is then encrypted and transmitted to the first device  505  for secure storage. When a user wishes to gain access to a second system, the first device  505  may be presented and the second system may be configured to query for it. To the extent that the access token is still valid and the first and second systems respect each other, through a protocol such as OAuth or SAM), the user may gain access to the secondary system. In some examples, the access token may be encrypted prior to transmission. For example, the first application  516  may be configured to encrypt the access token prior to transmission to the one or more processors  502  of the first device  505 . 
     The one or more processors  502  may be configured to decrypt the access token. The one or more processors  502  may be configured to store the access token in the memory  504 . The one or more processors  502  may be configured to transmit, after one or more entries of the communication interface  507  into a communication field of any device, the access token. The one or more entries may be associated with at least one selected from the group of a tap, a swipe, a wave, and/or any combination thereof. For example, the one or more processors  502  may be configured to transmit the access token to the first application  516 . The access token may be transmitted via near field communication (NFC). Without limitation, the access token may be transmitted via Bluetooth, Wi-Fi, RFID. 
     The one or more processors  502  may be configured to transmit the access token to a second application  518  comprising instructions for execution on the second device  510 . The one or more processors  502  may be configured to transmit, after one or more entries of the communication interface  507  into a communication field of the second device  510 , the access token. The one or more entries may be associated with at least one selected from the group of a tap, a swipe, a wave, and/or any combination thereof. For example, the one or more processors  102  may be configured to transmit the access token to the second application  518 . The access token may be transmitted via near field communication (NFC). Without limitation, the access token may be transmitted via Bluetooth, Wi-Fi, RFID. The access token may be transmitted for verification prior to providing access to one or more resources, as previously explained. 
     The access token may comprise a limited use token. The access token may include one or more elements, such as an access identifier. The access identifier may be configured to allow a user to be identified across a plurality of systems, such as the first system and the second system. The access identifier may be unique to the user, tied to a login session, and/or any combination thereof. In some examples, the access identifier may comprise a group of identifiers which may be configured to describe the user as belonging to one or more access groups. In some examples, the token may include a one-time use token. In other examples, the token may include a time-based token. For example, the token may be restricted to usage for a predetermined time period, such as at least one selected from the group of seconds, minutes, hours, days, weeks, months, years, and/or any combination thereof. After the token has been used, for example after a one-time usage and/or after expiration of a predetermined time period usage, the token may be invalidated and no longer usable. 
     In some examples, the first application  516  comprising instructions for execution on the second device  510  may be a different application than the second application  518  comprising instructions for execution on the second device  510 . In some examples, the card reader  519  may be configured to provide access to a physical space. In some examples, the card reader  519  may be configured to provide access to a digital experience. In some examples, the card reader  519  may be configured to provide access to a ticketed event. In some examples, the card reader  519  may be configured to provide access to a safe deposit box. 
     In other examples, the one or more processors  502  may be configured to receive one or more challenges via the communication interface  507  from the first application  516  or second application  518  comprising instructions for execution on the second device  510 . The challenge may include a public key and an encrypted test. The one or more processors  502  may be configured to transmit one or more responses that are responsive to the one or more challenges via the communication interface  507 . For example, the one or more processors  502  may be configured to transmit, via the communication interface  507 , a challenge response to the first application  516  or second application  518  comprising instructions for execution on the second device  510 . 
     The one or more processors  502  may be configured to decrypt the encrypted test. For example, the one or more processors  502  may be configured to decrypt the encrypted test using the private key and generate a decrypted test. In some examples, the one or more processors  502  may be configured to include the decrypted test in the challenge response transmitted, via the communication interface  507 . In some examples, the one or more processors  502  may be configured to transmit, via the communication interface  507 , the challenge response including the decrypted test to the first application  516  or second application  518  comprising instructions for execution on the second device  510 . 
     In some examples, the card reader  519  may be configured to provide access to one or more resources, such as a physical space. As discussed above, the card reader may be internal to the second device  510 . For example, the access may be provided after successful authentication of the token. In some examples, the card reader  519  may be configured to provide access to the physical space after one or more entries of the communication interface  507  into a communication field of a device, such as device  510 , associated with the card reader  519 . Without limitation, the physical space may include any space of a building, a room, a school, a governmental agency, an elevator, or the like such that the card reader is configured to grant access thereto via the one or more entries that are part of the token validation. In some examples, the physical space may also include any space or location where mobile devices, such as a cell phone or tablet or laptop or universal serial bus device, are restricted or otherwise prohibited, such as a cloud server facility or governmental facility or any other secure facility. 
     In some examples, the card reader  519  may be configured to provide access to a digital experience. As discussed above, the card reader may be internal to the second device  510 . For example, the access may be provided after successful authentication of the token. In some examples, the card reader  519  may be configured to provide access to the digital experience after one or more entries of the communication interface  507  into a communication field of a device, such as device  510 , associated with the card reader  519 . Without limitation, the digital experience may be associated with any application comprising instructions for execution on any device, a virtual reality program, a mobile or web browser, an email client, a game, or the like. In some examples, the first application  516  may be configured to generate and transmit the access token to the first device  505 , and the second application  518  may be associated with the digital experience. 
     In some examples, the card reader  519  may be configured to provide access to a ticketed event. As discussed above, the card reader may be internal to the second device  510 . For example, the access may be provided after successful authentication of the token. In some examples, the card reader  519  may be configured to provide access to the ticketed event after one or more entries of the communication interface  507  into a communication field of a device, such as device  510 , associated with the card reader  519 . Without limitation, the ticketed event may be associated with a school event, a sporting event, a concert event, a private event, a government event, a music event, or the like. 
     In some examples, the card reader  519  may be configured to provide access to a safe deposit box. As discussed above, the card reader  519  may be internal to the second device  510 . For example, the access may be provided after successful authentication of the token. In some examples, the card reader  519  may be configured to provide access to the safe deposit box after one or more entries of the communication interface  507  into a communication field of a device, such as device  510 , associated with the card reader  519 . In some examples, the card reader may be external to the safe deposit box. In some examples, the safe deposit box may comprise a storage enclosure configured to store one or more items, such as a product or grocery item, available for access to the retrievable one or more items. 
       FIG. 6  depicts a method  600  of authentication according to an exemplary embodiment.  FIG. 6  may reference the same or similar components of system  100 , first device  200  of  FIG. 2A  and  FIG. 2B , method  300  of  FIG. 3 , sequence diagram  400  of  FIG. 4 , and system  500  of  FIG. 5 . 
     At block  605 , the method  600  may include transmitting a challenge including a public key and an encrypted test. For example, an application comprising instructions for execution on a device, such as a client device or a card reader, may be configured to transmit one or more challenges via a communication interface of a first device. One or more processors of the first device may be configured to receive one or more challenges via a communication interface from an application comprising instructions for execution on a device. The challenge may include a public key and an encrypted test. In some examples, the challenge may be transmitted after authentication of the token, as previously explained above. 
     At block  610 , the method  600  may include generating a decrypted test. For example, the one or more processors may be configured to decrypt the encrypted test. For example, the one or more processors may be configured to decrypt the encrypted test using the private key and generate a decrypted test. 
     At block  615 , the method  600  may include including the decrypted test in the challenge response. For example, the one or more processors may be configured to include the decrypted test in the challenge response transmitted via the communication interface. 
     At block  620 , the method  600  may include transmitting the challenge response. For example, the one or more processors may be configured to transmit one or more responses that are responsive to the one or more challenges via the communication interface. For example, the one or more processors may be configured to transmit, via the communication interface, a challenge response to the application comprising instructions for execution on the device, such as a client device or card reader. 
     At block  625 , the method  600  may include authenticating the challenge response. For example, the application comprising instructions for execution on the device, such as the client device or card reader, may be configured to authenticate the challenge response received from the one or more processors. In some examples, the application may be configured to determine if the one or more responses indicate decryption of the encrypted test. For example, if the one or more responses indicate successful decryption of the encrypted test, the response may be deemed authenticated. If the one or more responses indicate unsuccessful decryption of the encrypted test the response may be unauthenticated. In some examples, the one or more processors may be configured to re-transmit the one or more responses including successful decryption of the encrypted test. The re-transmission of the one or more responses may include a predetermined threshold number of attempts, such as one or more entries of the communication interface of the first device into one or more communication fields of a device, such as a client device or card reader, prior to timing out the authentication process. In another example, the re-transmission of the one or more responses may also be subject to a predetermined threshold time period of attempts, such as one or more entries of the communication interface of the communication interface into one or more communication fields of a device, such as a client device or card reader, prior to timing out the authentication process. The predetermined threshold time period may include at least one selected from the group of seconds, minutes, hours, days, weeks, months, years, or the like, and/or any combination thereof. 
     In some examples, the application may be configured to authenticate the challenge response by decrypting the response with a private key. In other examples, the application may be configured to authenticate the challenge response by transmitting one or more requests to one or more servers and/or one or more databases. For example, the one or more servers may be configured to receive the one or more requests for authentication from the application. The one or more servers may be configured to decrypt the challenge response via a private key. In other examples, the one or more databases may be configured to receive the one or more requests for authentication from the one or more servers. The one or more databases may be configured to decrypt the challenge response via a private key. 
     At block  630 , the method  600  may include providing access to one or more resources. For example, the access to one or more resources may be conditioned on the determination of an outcome associated with the authentication of the challenge response. In this manner, access to the one or more resources may be denied or granted based on the determination of the authenticated challenge response. In some examples, the card reader may be configured to provide access to one or more resources, such as a physical space. As discussed above, the card reader may be internal to the client device. In other examples, the card reader may be external to the client device, such as a part of a third device. For example, the access may be provided after successful authentication of the challenge response. In some examples, the card reader may be configured to provide access to the physical space after one or more entries of the communication interface into a communication field of a device associated with the card reader. Without limitation, the physical space may include any space of a building, a room, a school, a governmental agency, an elevator, or the like such that the card reader is configured to grant access thereto via the one or more entries that are part of the token validation. In some examples, the physical space may also include any space or location where mobile devices, such as a cell phone or tablet or laptop or universal serial bus device, are restricted or otherwise prohibited, such as a cloud server facility or governmental facility or any other secure facility. 
     In some examples, the card reader may be configured to provide access to a digital experience. As discussed above, the card reader may be internal to the client device. In other examples, the card reader may be external to the client device, such as a part of a third device. For example, the access may be provided after successful authentication of the challenge response. In some examples, the card reader may be configured to provide access to the digital experience after one or more entries of the communication interface into a communication field of a device associated with the card reader. Without limitation, the digital experience may be associated with any application comprising instructions for execution on any device, a virtual reality program, a mobile or web browser, an email client, a game, or the like. 
     In some examples, the card reader may be configured to provide access to a ticketed event. As discussed above, the card reader may be internal to the client device. In other examples, the card reader may be external to the client device, such as a part of a third device. For example, the access may be provided after successful authentication of the challenge response. In some examples, the card reader may be configured to provide access to the ticketed event after one or more entries of the communication interface into a communication field of a device associated with the card reader. Without limitation, the ticketed event may be associated with a school event, a sporting event, a concert event, a private event, a government event, a music event, or the like. 
     In some examples, the card reader may be configured to provide access to a safe deposit box. As discussed above, the card reader may be internal to the client device. In other examples, the card reader may be external to the client device, such as a part of a third device. For example, the access may be provided after successful authentication of the challenge response. In some examples, the card reader may be configured to provide access to the safe deposit box after one or more entries of the communication interface into a communication field of a device associated with the card reader. In some examples, the card reader may be external to the safe deposit box. In other examples, the card reader may be internal to the safe deposit box. In some examples, the safe deposit box may comprise a storage enclosure configured to store one or more items, such as a product or grocery item, available for access to the retrievable one or more items. 
     It is further noted that the systems and methods described herein may be tangibly embodied in one of more physical media, such as, but not limited to, a compact disc (CD), a digital versatile disc (DVD), a floppy disk, a hard drive, read only memory (ROM), random access memory (RAM), as well as other physical media capable of data storage. For example, data storage may include random access memory (RAM) and read only memory (ROM), which may be configured to access and store data and information and computer program instructions. Data storage may also include storage media or other suitable type of memory (e.g., such as, for example, RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, flash drives, any type of tangible and non-transitory storage medium), where the files that comprise an operating system, application programs including, for example, web browser application, email application and/or other applications, and data files may be stored. The data storage of the network-enabled computer systems may include electronic information, files, and documents stored in various ways, including, for example, a flat file, indexed file, hierarchical database, relational database, such as a database created and maintained with software from, for example, Oracle® Corporation, Microsoft® Excel file, Microsoft® Access file, a solid state storage device, which may include a flash array, a hybrid array, or a server-side product, enterprise storage, which may include online or cloud storage, or any other storage mechanism. Moreover, the figures illustrate various components (e.g., servers, computers, processors, etc.) separately. The functions described as being performed at various components may be performed at other components, and the various components may be combined or separated. Other modifications also may be made. 
     In the preceding specification, various embodiments have been described with references to the accompanying drawings. It will, however, be evident that various modifications and changes may be made thereto, and additional embodiments may be implemented, without departing from the broader scope of the invention as set forth in the claims that follow. The specification and drawings are accordingly to be regarded as an illustrative rather than restrictive sense.