Systems and methods for provisioning transaction cards to multiple merchants
Systems, methods, apparatuses, and computer-readable media for provisioning transaction cards to multiple merchants from a single access point are described. For example, a method may include receiving a payment card number request, sending a contactless payment card step-up authentication request to the user device, receiving, from the user device, encrypted authentication information obtained from the contactless payment card in response to the contactless payment card step-up request, authenticating the encrypted authentication information received from the user device, granting a token to identify a communication session established with the merchant, which may enable a continued exchange of data with the merchant, and using the token to identify the respective communication session established with the merchant, providing account information to the merchant to associate a respective merchant account with a user of the contactless payment card.
Latest Capital One Services, LLC Patents:
Consumers may store or register payment cards with various merchants. The registered payment cards may be automatically retrieved to process a purchase by a consumer to make the transaction more efficient, secure, and/or to provide other benefits to the consumer. For example, a consumer may have an online account with an e-commerce retailer. The online account may store personal information as well as payment information, such as credit card information sufficient to process a payment. When the consumer makes a purchase, the credit card information may be automatically retrieved and applied as a payment source (responsive to confirmation by the consumer).
A typical consumer may have a payment card registered with multiple merchants. For example, a single credit card may be stored as a payment source at an e-commerce retailer, a grocery store, and for automatic bill payment (for instance, with an electricity service provider, a gym membership, a media streaming membership, and/or the like). If the user obtains a new payment card that they prefer to use in place of the previous credit card, they are required to update the payment information with each individual account, vendor, etc. Using conventional technologies, updating the payment source at multiple merchants is a tedious and time-consuming process that is also error prone due to the manual data entry of the payment card information. In addition, manual updating of payment card information is an unsecure process in which the card owner is vulnerable unauthorized access to their information. Accordingly, consumers would benefit from a more secure, efficient, and easier process for managing payment information at multiple merchants.
SUMMARYSystems, methods, apparatuses, and computer-readable media for provisioning transaction cards with multiple merchants are described.
In one embodiment, a computer-implemented method may include receiving, at a financial institution server from a user device, a plurality of payment card number requests, wherein a respective payment card number request is received for each merchant website of a plurality of merchant websites; sending an authentication request to the user device, wherein the authentication request is a request for the user device to interact with a contactless payment card associated with a user financial institution account; receiving, from the user device, encrypted authentication information received from the contactless payment card in response to the authentication request; authenticating the encrypted authentication information received from the user device; based on the authenticating being successful, granting respective tokens to each respective merchant of the plurality of merchants, wherein each respective token of the granted respective tokens identifies a respective communication session established with each respective merchant and enables a continued exchange of data with each respective merchant; and using each respective token to identify the respective communication session established with each respective merchant, providing account information as needed to each respective merchant to associate a respective merchant account with a user of the contactless payment card.
In some embodiments of the method, a last payment card number request of the plurality of payment card number requests may be received within a predetermined time period.
In various embodiments of the method, the predetermined time period may be determined based on a time of a receipt of a first payment card number request of the plurality of payment card number requests.
In some embodiments of the method, the predetermined time period may be about 5 minutes, about 10 minutes, or about 20 minutes.
In exemplary embodiments of the method, receiving the plurality of payment card number requests may include establishing a secure connection with the user device.
In various embodiments of the method, the secure connection may be established based on identifying information of the user of the contactless payment card.
In some embodiments of the method, the identifying information may be received prior to receiving a first payment card number request of the plurality of payment card number requests.
In various embodiments of the method, authenticating the encrypted authentication information received from the user device may include decrypting the encrypted authentication information; and confirming information input from the user device corresponds with the decrypted authentication information accessible by the financial institution server.
In exemplary embodiments of the method, authenticating the encrypted authentication information received from the user device may include, upon successful confirmation, generating an authorization to grant the respective tokens for each payment card number request of the plurality of payment card number requests.
In one embodiment, a computer-implemented method may include, receiving, at a financial institution server from a user device, a first payment card number request from a first merchant of a plurality of merchants to associate user financial institution account information with a first merchant account; sending a contactless payment card step-up authentication request to the user device, wherein the contactless payment card step-up authentication request is a request for the user device to interact with a contactless payment card associated with the user financial institution account information; receiving, from the user mobile, device encrypted authentication information maintained on the contactless payment card in response to the contactless payment card step-up request; authenticating the encrypted authentication information received from the user device; and based on the authenticating being successful, granting a first token to the first merchant, wherein the first token identifies a communication session with the first merchant and enables a continued exchange of data with the first merchant.
In some embodiments of the method, the method may include using the token to identify the communication session, providing account information as needed for the first merchant to populate the first merchant account.
In various embodiments of the method, the method may further include receiving a second payment card number request from a second merchant; based on the authenticating being successful, granting a second token to the second merchant, the second token identifies a communication session with the second merchant and may enable a continued exchange of data of user financial institution account data with the second merchant.
In exemplary embodiments of the method, the token may enable retrieval of data by each merchant of the plurality of merchants.
In various embodiments of the method, the user financial institution account information may include a payment card number of a user of the user device and payment card number-related information.
In one embodiment, a non-transitory computer-readable storage medium may include instructions that when executed by a processor, cause the processor to: receive, from a user device, a plurality of payment card number requests, wherein a respective payment card number request is received for each merchant website of a plurality of merchant websites; send a contactless payment card step-up authentication request to the user device, wherein the contactless payment card step-up authentication request is a request for the user device to interact with a contactless payment card associated with a user financial institution account; receive, from the user device, encrypted authentication information obtained from the contactless payment card in response to the contactless payment card step-up request; authenticate the encrypted authentication information received from the user device; based on the authenticating being successful, grant respective tokens to each respective merchant of the plurality of merchants, wherein each respective token of the granted respective tokens identifies a respective communication session established with each respective merchant and enables a continued exchange of data with each respective merchant; and using each respective token to identify the respective communication session established with each respective merchant, provide account information as needed to each respective merchant to associate a respective merchant account with a user of the contactless payment card.
In some embodiments of the computer-readable storage medium, a last payment card number request of the plurality of payment card number requests may be received within a predetermined time period.
In various embodiments of the computer-readable storage medium, the predetermined time period may be determined based on a time of a receipt of a first payment card number request of the plurality of payment card number requests.
In some embodiments of the computer-readable storage medium, the predetermined time period may be about 5 minutes, about 10 minutes, or about 20 minutes.
In exemplary embodiments of the computer-readable storage medium, receiving the plurality of payment card number requests, the processor may be operable to establish a secure connection with the user device based on identifying information of the user received prior to receiving a first payment card number request of the plurality of payment card number requests.
In various embodiments of the computer-readable storage medium, authenticating the encrypted authentication information received from the user device may include: decrypting the encrypted authentication information; confirming information input from the user device corresponds with the decrypted authentication information; and upon successful confirmation, generating an authorization to grant the respective tokens for each payment card number request of the plurality of payment card number requests.
To easily identify the discussion of any particular element or act, the most significant digit or digits in a reference number refer to the figure number in which that element is first introduced.
For the purposes of promoting an understanding of the principles of the present disclosure, reference will now be made to the embodiments illustrated in the figures and specific language will be used to describe the same. It will nevertheless be understood that no limitation of the scope of the disclosure is thereby intended. Any alterations and further modifications in the described embodiments, and any further applications of the principles of the present disclosure as described herein are contemplated as would normally occur to one skilled in the art to which the disclosure relates.
The described technologies generally relate to systems and methods for provisioning transaction cards to multiple entities. In some embodiments, the transaction card may be a payment card, credit card, debit card, gift card, and/or the like. In various embodiments, the transaction card may be a contactless card (see, for example,
A user may have a registered account with an entity (an “entity account”) (e.g., Kroger®, Amazon®, Sam's Club®, Walmart®, Target®, and/or the like). The registered account may include personal information (e.g., name, address, demographic information, preferences, and/or the like) and payment information. In various embodiments, the payment information may be or may include information of a transaction card, such as a credit card, that may be applied to pay for purchases. The transaction card information may include, without limitation, card owner name, card owner address, card number, expiration date, card verification value (CVV), and/or the like. The registered account may allow the user to perform transactions with the entity via an online platform (e.g., retailer e-commerce site, mobile application (“app”), and/or the like) and/or in a physical retail location using the stored payment information. In this manner, a user may use the information stored in the account to automatically select a payment card to process a payment without having to access the physical card.
With existing systems, each time that a user wants to use a new transaction card with one or more entities, the user is required to manually update the account information with each individual entity. Updating the payment source at multiple entities is a tedious and time-consuming process that is also error prone due to the manual data entry of the payment card information. In addition, manual updating of payment card information is an unsecure process in which the card owner is vulnerable unauthorized access to their information. Therefore, when a user obtains a new transaction card, such as a credit card or debit card, the user must proceed through the onerous and unsecure process of updating the payment information with each individual entity.
Accordingly, some embodiments provide methods and systems to facilitate provisioning a transaction card to multiple different and unrelated entities (e.g., “third party entities”) via a single process through one access point.
In some embodiments, for example, a user may access an account via a transaction platform (e.g., a website, application, app, and/or the like) of a financial services provider that manages the financial services functions of the transaction card. Non-limiting examples of financial services companies may include a bank, a credit union, a credit card company, a government organization (for instance, an organization that issues government-managed payment cards), and/or the like. In one non-limiting example, the financial services provider may be Capital One Financial Corporation (“Capital One”) of McLean, Virginia, United States of America (i.e., the transaction card issuer). The financial services platform configured according to some embodiments may allow a user to specify which entity accounts should be associated with a transaction card. The financial services platform may push this information to the entity accounts operated by third-party entity systems using processes configured according to some embodiments. In this manner, a financial services platform operating according to various embodiments may allow a user to update payment information at a plurality of entities through a single access point in an efficient, accurate, and secure process.
In one illustrative and non-restrictive example, the financial services provider may set up an authorization relationship with various entities. An example of an authorization relationship may be or may include an “open authorization” or “OAuth” relationship. In general, an OAuth relationship is an open-standard authorization protocol or framework that specifies how unrelated services can safely allow authenticated access to their assets without actually sharing a single logon credential. One example OAuth implementation is the OAuth 2.0 standard for open delegation established by the Internet Engineering Task Force (IETF). The OAuth 2.0 standard enables an access token to be issued to a third-party client by an authorization server, with the approval of the resource owner. The third party then uses the access token to access the protected resources hosted by the resource server. The access token is limited to being valid for a short period of time, such as about 5 minutes, about 10 minutes, about 20 minutes, and/or the like. Although OAuth is used as an example of an authorization relationship in the present disclosure, embodiments are not so limited, as any authorization relationship that may operate according to some embodiments is contemplated herein.
The authorization relationship may allow the third-party entity (e.g., an e-commerce platform) to accept or trust the financial service company's (e.g., Capital One's) authentication and step up to authorize access to putting a new card on file with the user's third-party entity account (i.e., the user's e-commerce platform account with the third-party entity). Once the authorization relationship is setup, the user may login to and perform an authentication (e.g., a step-up authentication) with the financial services provider platform (e.g., an application interface for the credit card). Using a validation process (for instance, contactless card authentication (see, for example,
In some embodiments, the authorization relationship, such as OAuth, may be respected by the third-party entity systems such that the financial services provider backend and the third-party entity backend may communicate various items of information to the third-party entity, such as account numbers, a primary account number (PAN), virtual account number (VCN) (including a locked VCN), personally identifiable information (PII) data (e.g., name, address, phone number, email, and/or the like).
In some embodiments, the process for updating transaction card information via a financial services provider platform may operate using existing third-party entity accounts of the credit card user. In various embodiments, the financial services platform may operate to create a new account with the transaction card information.
The data network 106 may be a network, such as the internet, a wide area network, a local area network, a metropolitan area network, a cellular network, a combination of networks, or the like, that enables different devices and systems communicate with one another.
The website 108 and the mobile website 104 may be services executing on servers or cloud platforms that provide services or products from service providers or merchants.
The financial service provider (or financial institution) system 118 may be provided by an entity, such as a bank, mortgage company, investment firm, credit card issuer, financial services provider (e.g., Capital One), and/or the like, and the entity be referred to herein after as a “financial institution” or “financial services provider.” The financial institution may have business relationships with a number of third-party entities (or “merchants”). The number of merchants may include merchants that conduct business through online businesses, that sell merchandise and/or services through online transactions made possible by websites, such as website 108 and mobile website 104. In addition, or alternatively, the financial institution may have business relationships with a number of consumers that interact with the financial institution system 118 via their mobile devices, such as mobile device 102. As part of the relationship with the consumer, the financial institution may provide the consumer after a sufficient amount of vetting (to confirm identity, physical address, income, household members, account information and the like) with a contactless card 110.
The contactless card 110 as described in later examples (see for example,
The mobile device 102 may be operable to communicate with the financial institution system 118 via a communication link 114. The mobile device 102 may be operable to provide information obtained from the contactless card 110 to the financial institution system 118 via an instance of the user application 132. The user application 132 may be an application that facilitates obtaining the encrypted authentication information from the contactless card 110.
The financial institution system 118 may include a number of systems, memories, modules and components, such as a user data storage 120, a financial institution processor 122, an authentication system 124 and a communication interface 126.
The communication interface 126 may be operable to facilitate communication by the financial institution system 118 with the mobile device 102, the mobile website 104, and/or website 108 via the data network 106. The communication link 128 may couple the mobile website 104 to the data network 106. Similarly, the communication interface 126 may be operable to receive information from each of the mobile device 102, the mobile website 104 and the website 108 sent through the data network 106. The communication interface 126 may communicate via the data network 106 using known communication protocols.
The user data storage 120 may securely maintain information regarding the user that is used by the authentication system 124 to authenticate the user. For example, the maintained information regarding the user may include personal identifying information (PII), such as the user's name, home address, spousal information, telephone numbers, bank loan balances, types of accounts, types of automobiles secured by loans, mobile phone identifier (e.g., International Mobile Equipment Identity (IMEI) number or the like), passwords, permanent account numbers, past virtual account numbers, a transaction count and the like.
The financial institution processor 122 may be operable to receive the encrypted information, which may also be referred to as an encrypted authentication payload of the contactless card 110, from the communication interface 126. The financial institution processor 122 may be operable to process the encrypted information and forward encrypted authentication information to the authentication system 124.
The authentication system 124 may be a component (e.g., a processor, software, a combination of both) that decrypts (if needed) and/or authenticates information provided by a user, such as an identifier provided by the user to the website 108, authentication information from the contactless card 110, and the like. For example, the authentication system 124 may be a component that utilizes decryption algorithms to decrypt the encrypted authentication information and evaluate the decrypted to authentication information to user information obtained from the user data storage 120. Optionally, the authentication system 124 may interface with a third-party authentication system 130, which may provide some or all of the same functionality of the authentication system 124.
A customer may enter an identifier into a field of a web page presented by the web browser (such as a phone identifier, an email address, a permanent account number (PAN), or the like). For example, the user may enter the first 5 digits of the PAN, which provides the mobile website 104 with enough information to identify the user's financial institution. The identifier may include other additional information, such as a special keyword, an account number or name maintained in relation to the website 108 or mobile website 104, or the like that indicates to the website 108 and or mobile website 104. Alternatively, the user may select a financial institution presented on the web page of the website 108 and or mobile website 104 for use in the authentication process.
The website 108 may be operable to identify the user as a user in a centralized database or bank identification number. In a detailed example, the website 108 may have relationships with a number of different financial institutions and/or merchants. When the website 108 receives a user's identifying information, such as the phone identifier or email address, the website 108 may broadcast that information to all of the number of different financial institutions with which the website 108 has relationships. The first financial institution that responds with a confirmation is the one with which the website 108 will continue to conduct the transaction session with the first responding financial institution. The mobile website 104 may be operable to be presented and operate on mobile devices, such as a smartphone, laptop, tablet device or the like, and to function in a similar manner as the website 108.
The foregoing system 100 may be operable to provide the secure authentication of the user and streamlined secure transactions as outlined in the following process examples.
A customer may be asked to tap a contactless card to phone for a background read of authentication information usable by the financial institution to authenticate the user. In some examples, the present disclosure refers to a “tap” of the contactless card. However, it is understood that the present disclosure is not limited to a tap, and that the present disclosure includes other gestures (e.g., a wave or other movement of the card). The authentication information read by the phone may be a uniform resource locator (URL) (also referred to as a “link”) associated with the financial institution. The URL may contain an encrypted payload which is authenticated by an authentication system 124 of the financial institution system 118. Alternatively, the authentication of the user may also serve as an approval of the transaction, in which case, any account information or the like needed by the merchant to complete the transaction at the website 108 may be provided by the financial institution and a notification that the transaction is completed may be presented by the user.
Financial institution system 118 sends authentication response to a merchant along with rest of personal identifiable information (PII) data and possibly a virtual card number (VCN), which may be a 15- or 16-digit number like a credit card number but without the physical credit card being present.
Essentially, the user merely provides their identifier (email address or telephone number) and taps a contactless card 110 to the mobile device 102, and upon authentication, the information (e.g., PII data, most frequent shipping address, and the like) for completing the transaction may be provided to the merchant.
The request to tap card to phone may cause the launch of a web browser on either a portable device presenting the mobile website 104 or a computing device that presents the website 108. For example, the financial institution may also generate a request to tap alert (e.g., a prompt) on their phone via an in-app notification or via SMS to initiate an authentication process as discussed herein. When the website 108 generates a browsing session for the user transaction, the browsing session is assigned a browsing session identifier. Information input during the browsing session, such as user's name, the shipping address, product identifiers that identify products to be purchased, and the like are saved with reference to the browsing session identifier. The browsing session identifier allows the merchant to quickly reconvene the user's shopping experience. A link containing the browsing session identifier may be provided with the authentication request to the financial institution. Upon authentication by the financial institution system, the user may resume the commerce session at the website 108 or mobile website 104. For example, the authentication result may be delivered by the authentication system 124 or the like of the financial institution system 118 and may include the browsing session identifier and information regarding the user. The browsing session may be a secure or encrypted communication link. The information regarding the user provided by the authentication system 124 may include the user's name, user's shipping address, user's contact information, and the like.
In an example, the encrypted authentication payload is sent in URL to financial institution backend, which is expecting the payload in a message for authentication. Encrypted authentication payload may include version number (if multiple versions), unique identifier of person, application transaction counter, one-time password, and a cryptogram that is used to validate message integrity. For example, a URL message may be structured as “www.financialinstitutionname.com/fintech 1?AUTHENTICATION MESSAGE” or the like. Upon receipt of the URL message, the OS of the mobile device may be operable to contact the financial institution at the URL and provide the AUTHENTICATION MESSAGE to the financial institution system 118. The financial institution system 118 associated with the URL may be operable to take the AUTHENTICATION MESSAGE and authenticate the user, determine if there is a pending transaction (for example, based on the earlier notification from the website 108) and provide the needed information to complete the transaction. Alternatively, the URL message may be processed by the OS of the mobile device to be sent as a text message to the financial institution system, which may be operable to access the URL in the message. The information usable to complete the transaction may be provided in an authentication response to merchant that includes some additional PII data (that may not have already been input to the website 108 by the user) and possibly a virtual card number (VCN).
In some embodiments, a service provider backend (e.g., server(s)) 202 may establish a trust relationship with the backend platform of one or more merchants 203a-n. In one non-limiting example, the trust relationship may be or may include an authorization relationship, such as an OAuth relationship. The authorization relationship between the financial services provider and the merchants may be determined according to various processes. For example, the authorization relationship may be established via a contractual relationship, or a program offered to the merchants by the financial services provider. In general, the authorization process may include a process, system, etc. for merchants to trust the authentication programs and processes of the financial services provider (and/or vice versa) and allow the financial services provider to put their users and/or user's transaction card on file (e.g., add as a payment option in the user's merchant account).
In some embodiments, a user via a client device 201 may request 220 (for instance, a payment card number request) that a transaction card be set up with a merchant. For example, in response to accessing a transaction account with financial services provider backend 202, a user may be provided with an option or prompt to associate the transaction card with a third-party entity. In another example, for a contactless card (see, for example,
In various embodiments, the request 220 may include generating a VCN to be used with a specific merchant (or set of merchants). The financial services provider backend 202 may receive the request 220 and request 221 authentication. For example, the request 221 may be the financial services provider using multi-factor authentication, step-up authentication, and/or the like for the user to authenticate themselves on the client device 201. For instance, a user may initiate a transaction on a website or app, but the financial services provider may seek to ensure the identity of the user, so the financial services provider may request 221 that the user authenticate themselves on the client device 201 that already has the financial services provider app installed. The financial services provider may have trust/authentication with the client device 201 and may have various policies that are required in order to process the transaction card request (e.g., 7-day no password or phone number change, 7-day stability of the device, etc.) to ensure that the financial services provider trusts the client device 201.
If the authentication (e.g., step-up authentication) is confirmed 222, then the financial services provider backend 202 may grant 224 a token for data retrieval. In some embodiments, confirmation 222 may occur via authentication/cryptographic processes of a contactless card configured according to various embodiments (see, for example,
In some embodiments, the financial services provider backend 202 may provide the merchants 203a-n with a token for this transaction. In some embodiments, the token may identify a communication session established with the merchant. If the merchant 203a-n agrees to continue setting up the account (or adding the transaction card to an existing merchant account), the merchant 203a-n can come back with the token and an affirmative response 225 to retrieve this specific user's details to either open a new account or update the existing account with a new card number. In some embodiments, the token may operate as a header when multiple requests are coming and going from both backends 202, 203a-n to uniquely identify the transaction.
An exchange 225 for account information may occur between the financial services provider backend 202 and the merchant backend 203a-n. For example, in the exchange 2230 the merchant backend 203a-n may indicate to the financial services provider backend 202 whether an account exists at the merchant. If a match for the user is determined (e.g., via matching account number, email address, phone number, and/or the like) is found and an account exists, transaction card information (e.g., VCN and/or card number, CCV, expiration date, and/or the like) may be shared in future exchanges 225 (and/or 226). In various embodiments, if a match is not found, then a new account may be created and exchanges 225 may involve more account creation information (e.g., name, address, phone number, email address, and/or the like) may be required before card information can be shared, which may require multiple steps/exchanges 225.
Once the account has been established (either located or created), the merchant back end 203a-n may make a call to retrieve information 226, such as PII, PCI data, and/or the like. PCI data may be or may include a VCN and/or a card number, CCV, expiration date, and/or the like. Exchanges 225 and/or 226 may use a minimum amount of information to satisfy the transaction. For example, if an account is found in exchange 225, there is no need to exchange PII and only card information may be shared; however, PII may be shared, in addition to the transaction card information if an account is not found.
A business client 301 may request an access token at step 320 from the OAuth server 302. The OAuth server 302 may perform various authentication processes, such as verifying 321 the business client 301 and/or obtaining user consent 322. Responsive to verification 321 and consent 322, the OAuth server 302 may return at step 323 an access token to the business client 301. The business client 301 may request at step 324 a resource from a resource server 303. In various embodiments, the request may include the token returned at step 323 to the business client 301 from the OAuth server 302. The resource server 303 may operate to validate 325 the token provided by the business client 301 with the OAuth server 302. If the token is valid at step 326, as indicated to the resource server 303 by the OAuth server 302, the resource server 303 may return, at step 327, a resource to the business client.
Included herein are one or more logic flows representative of exemplary methodologies for performing novel aspects of the disclosed embodiments. While, for purposes of simplicity of explanation, the one or more methodologies shown herein are shown and described as a series of acts, those skilled in the art will understand and appreciate that the methodologies are not limited by the order of acts. Some acts may, in accordance therewith, occur in a different order and/or concurrently with other acts from that shown and described herein. For example, those skilled in the art will understand and appreciate that a methodology could alternatively be represented as a series of interrelated states or events, such as in a state diagram. Moreover, not all acts illustrated in a methodology may be required for a novel implementation. Blocks designated with dotted lines may be optional blocks of a logic flow.
A logic flow may be implemented in software, firmware, hardware, or any combination thereof. In software and firmware embodiments, a logic flow may be implemented by computer executable instructions stored on a non-transitory computer readable medium or machine readable medium. The embodiments are not limited in this context.
At block 402, the logic flow 400 may establish an authorization relationship between a financial services provider and a third-party entity. For example, financial services provider backend 202 may establish an authorization relationship, such as an OAuth relationship, with one or more merchants. The authorization relationship may allow the financial services provider to access a user account of a merchant or interact with a merchant to update (or allow the merchant to update with financial services provider provided information) a user account, such as an account of a user mutual to both the financial services provider and the merchant.
At block 404, the logic flow 400 may receive a request to provision a transaction card with a third-party entity. The request may be a payment card number request. For example, a user may have a credit card with a financial services provider that they would like to be associated as a payment source with a merchant. The user may access their financial services provider account (for instance, via an online platform, app, and/or the like) and submit a provision request through the financial services provider platform. In some embodiments, the request may include a transaction card (or cards) and a selection of third-party entities to provision the transaction card to. The request may include additional request information, such as card priority (for instance, transaction card should be the primary transaction card at Merchant A, but a secondary card with Merchant B), card use rules (for example, use the transaction card at Merchant A for all purchases, but only for recurring/subscription purchases at Merchant B, and/or the like), and/or other use specifications.
In some embodiments, the request may include a plurality of requests, wherein a respective payment card number request is received for each merchant of a plurality of merchants (or merchant websites). In various embodiments, a last payment card number request of the plurality of payment card number requests may be required to be received within a predetermined time period after receipt of a first payment card number request (or any previous request in a series of request) of the plurality of payment card number requests. In some embodiments, the predetermined time period may be about 5 minutes, about 10 minutes, about 20 minutes, about 30 minutes, about 60 minutes, or any time or range between any two of these values (including endpoints).
The logic flow 400 may authenticate the requesting user at block 406. For example, the financial services provider backend 202 may authenticate the user via username/password processes, multi-factor authentication, step-up authentication, OAuth processes, and/or the like. The financial services provider backend 202 may authenticate the user, the user device, and/or other elements associated with the requesting user.
At block 408, the logic flow 400 may establish a connection between the financial services provider and the third-party entity. For example, the financial services provider backend 202 may establish a network connection with one or more merchant backends 203a-n. In some embodiments, the financial services provider backend 202 and the merchant backends 203a-n may have dedicated communication channels for facilitating transaction card provisioning.
At block 410, the logic flow 400 may operate to authenticate the user account with the third-party entity. For example, the financial services provider backend 202 (alone or via prompts/exchanges with the client device 201) may provide account information to a merchant backend 203a-n to allow the merchant backend 203a-n to locate the user account associated with the provisioning request. For example, the financial services provider backend 202 may request merchant account information from the user or request that the user login to their merchant account (including via a merchant interface outside of or within the financial services provider platform, for instance, the same or similar to a PayPal® login interface to process payment within a merchant platform.). In another example, the financial services provider backend 202 may store the merchant authentication information in the user account with the financial services provider, for instance, during a registration process registering the merchant as a provisioning entity. In a further example, if a user account does not exist with the merchant, the financial services provider backend 202 may facilitate the establishment of a new account with the merchant.
At block 412, the logic flow 400 may provide transaction card information to the third-party entity. For example, responsive to authentication of the user (and/or user device) and establishment by the financial services provider that a user account exists with the merchant (either newly created or pre-existing) that is verified by the financial services provider (including through confirmation by the merchant backend 203a), the financial services provider backend 202 may provide the transaction card information to the third-party entity. The transaction card information may include information sufficient for the user to use the card via the merchant, such as card owner name, card owner address, VCN and/or card number, expiration date, CVV, and/or the like.
The logic flow 400 may update the user account at block 414. For example, the merchant backend 203a-n may update the user account with the merchant system to include the transaction card as a payment source.
At block 502, the logic flow 500 may receive, at a financial institution server from a user device, a plurality of payment card number requests, wherein a respective payment card number request is received for each merchant website of a plurality of merchant websites. For example, client device 201 may submit a request (which may be or may include request 220) to financial services provider backend 202.
At block 504, the logic flow 500 may send a contactless payment card step-up authentication request to the user device, wherein the contactless payment card step-up authentication request is a request for a user mobile device to interact with a contactless payment card associated with a user financial institution account. For example, financial services provider backend 202 may send a requests 221 for authentication, such as a multi-factor or “step up” authentication to client device 201.
At block 506, the logic flow 500 may receive, from the user mobile device, encrypted authentication information obtained from the contactless payment (see, for example,
At block 510, the logic flow 500 may, based on the authenticating being successful, grant respective tokens to each respective merchant of the plurality of merchants, wherein each respective token of the granted respective tokens identifies a respective communication session established with each respective merchant and enables a continued exchange of data with each respective merchant.
At block 512, the logic flow 500 may identify, using each respective token, the respective communication session established with each respective merchant, providing account information as needed to each respective merchant to associate a respective merchant account with a user of the contactless payment card.
The contactless card 611 may also include identification information 606 displayed on the front and/or back of the card, and a contact pad 608. The contact pad 608 may include one or more pads and be configured to establish contact with another client device, such as an ATM, a user device, smartphone, laptop, desktop, or tablet computer via transaction cards. The contact pad may be designed in accordance with one or more standards, such as ISO/IEC 7816 standard, and enable communication in accordance with the EMV protocol. The contactless card 611 may also include processing circuitry, antenna and other components as will be further discussed in
As illustrated in
The memory 784 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 611 may include one or more of these memories. A read-only memory may be factory programmable as read-only or one-time programmable. One-time programmability provides the opportunity to write once then read many times. A write once/read-multiple memory may be programmed at a point in time after the memory chip has left the factory. Once the memory is programmed, it may not be rewritten, but it may be read many times. A read/write memory may be programmed and re-programed many times after leaving the factory. A read/write memory may also be read many times after leaving the factory. In some instances, the memory 784 may be encrypted memory utilizing an encryption algorithm executed by the processor 712 to encrypted data.
The memory 784 may be configured to store one or more applets 110, one or more counters 772, a unique ID 773, the master key 775, the UDK 774, diversified key 776, and the PAN sequence 777. The one or more applets 771 may comprise one or more software applications configured to execute on one or more contactless cards 611, such as a Java® Card applet. However, it is understood that applets 771 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 772 may comprise a numeric counter sufficient to store an integer. The unique ID 773 may comprise a unique alphanumeric identifier assigned to the contactless card 611, and the identifier may distinguish the contactless card 611 from other contactless cards 611. In some examples, the unique ID 773 may identify both a customer and an account assigned to that customer.
The processor 712 and memory elements of the foregoing exemplary embodiments are described with reference to the contact pad 608, but the present disclosure is not limited thereto. It is understood that these elements may be implemented outside of the contact pad 608 or entirely separate from it, or as further elements in addition to processor 712 and memory 784 elements located within the contact pad 608.
In some examples, the contactless card 611 may comprise one or more antenna(s) 714. The one or more antenna(s) 714 may be placed within the contactless card 611 and around the processing circuitry 710 of the contact pad 608. For example, the one or more antenna(s) 714 may be integral with the processing circuitry 710 and the one or more antenna(s) 714 may be used with an external booster coil. As another example, the one or more antenna(s) 714 may be external to the contact pad 608 and the processing circuitry 710.
In an embodiment, the coil of contactless card 611 may act as the secondary of an air core transformer. The terminal may communicate with the contactless card 611 by cutting power or amplitude modulation. The contactless card 611 may infer the data transmitted from the terminal using the gaps in the power connection of the contactless card 611, which may be functionally maintained through one or more capacitors. The contactless card 611 may communicate back by switching a load on the coil of the contactless card 611 or load modulation. Load modulation may be detected in the terminal's coil through interference. More generally, using the antenna(s) 714, processor 712, and/or the memory 784, the contactless card 611 provides a communications interface to communicate via NFC, Bluetooth, and/or Wi-Fi communications.
As explained above, contactless card 611 may be built on a software platform operable on smart cards or other devices having limited memory, such as JavaCard, and one or more or more applications or applets may be securely executed. Applet 771 may be added to contactless cards to provide a one-time password (OTP) for multifactor authentication (MFA) in various mobile application-based use cases. Applet 771 may be configured to respond to one or more requests, such as near field data exchange requests, from a reader, such as a mobile NFC reader (e.g., of a mobile computing device 102 or point-of-sale terminal), and produce an NDEF message that comprises a cryptographically secure OTP encoded as an NDEF text tag. The NDEF message may include a cryptogram, and any other data.
One example of an NDEF OTP is an NDEF short-record layout (SR=1). In such an example, one or more applet 771 may be configured to encode the OTP as an NDEF type 4 well known type text tag. In some examples, NDEF messages may comprise one or more records. The applet 771 may be configured to add one or more static tag records in addition to the OTP record.
In some examples, the one or more applet s771 may be configured to emulate an RFID tag. The RFID tag may include one or more polymorphic tags. In some examples, each time the tag is read, different cryptographic data is presented that may indicate the authenticity of the contactless card. Based on the one or more applets 110, an NFC read of the tag may be processed, the data may be transmitted to a server, such as a server of a banking system, and the data may be validated at the server.
In some examples, the contactless card 611 and server may include certain data such that the card may be properly identified. The contactless card 611 may include one or more unique identifiers (not pictured). Each time a read operation takes place, the counter 772 may be configured to increment. In some examples, each time data from the contactless card 611 is read (e.g., by a mobile device), the counter 772 is transmitted to the server for validation and determines whether the counter 772 are equal (as part of the validation) to a counter of the server.
The one or more counters 772 may be configured to prevent a replay attack. For example, if a cryptogram has been obtained and replayed, that cryptogram is immediately rejected if the counter 772 has been read or used or otherwise passed over. If the counter 772 has not been used, it may be replayed. In some examples, the counter that is incremented on the contactless card 611 is different from the counter that is incremented for transactions. The contactless card 611 is unable to determine the application transaction counter 772 since there is no communication between applets 771 on the contactless card 611. In some examples, the contactless card 611 may comprise a first applet 440-1, which may be a transaction applet, and a second applet 440-2. Each applet 440-1 and 440-2 may comprise a respective counter 772.
In some examples, the counter 772 may get out of sync. In some examples, to account for accidental reads that initiate transactions, such as reading at an angle, the counter 772 may increment but the application does not process the counter 772. In some examples, when the device 102 is woken up, NFC may be enabled and the computing device 102 may be configured to read available tags, but no action is taken responsive to the reads.
To keep the counter 772 in sync, an application, such as a background application, may be executed that would be configured to detect when the computing device 102 wakes up and synchronize with the server of a banking system indicating that a read that occurred due to detection to then move the counter 772 forward. In other examples, Hashed One Time Password may be utilized such that a window of mis-synchronization may be accepted. For example, if within a threshold of 10, the counter 772 may be configured to move forward. But if within a different threshold number, for example within 10 or 600, a request for performing re-synchronization may be processed which requests via one or more applications that the user tap, gesture, or otherwise indicate one or more times via the user's device. If the counter 772 increases in the appropriate sequence, then it possible to know that the user has done so.
The key diversification technique described herein with reference to the counter 772, master key 775, UDK 774, and diversified key 776, is one example of encryption and/or decryption a key diversification technique. This example key diversification technique should not be considered limiting of the disclosure, as the disclosure is equally applicable to other types of key diversification techniques.
During the creation process of the contactless card 611, two cryptographic keys may be assigned uniquely per card. The cryptographic keys may comprise symmetric keys which may be used in both encryption and decryption of data. Triple DES (3DES) algorithm may be used by EMV and it is implemented by hardware in the contactless card 611. By using the key diversification process, one or more keys may be derived from a master key based upon uniquely identifiable information for each entity that requires a key.
In some examples, to overcome deficiencies of 3DES algorithms, which may be susceptible to vulnerabilities, a session key may be derived (such as a unique key per session) but rather than using the master key, the unique card-derived keys (e.g., the UDKs 774) and the counter may be used as diversification data. For example, each time the contactless card 611 is used in operation, a different key may be used for creating the message authentication code (MAC) and for performing the encryption. This results in a triple layer of cryptography. The session keys may be generated by the one or more applets and derived by using the application transaction counter with one or more algorithms (as defined in EMV 4.3 Book 2 A1.3.1 Common Session Key Derivation).
Further, the increment for each card may be unique, and assigned either by personalization, or algorithmically assigned by some identifying information. For example, odd numbered cards may increment by 2 and even numbered cards may increment by 5. In some examples, the increment may also vary in sequential reads, such that one card may increment in sequence by 1, 3, 5, 2, 2, . . . repeating. The specific sequence or algorithmic sequence may be defined at personalization time, or from one or more processes derived from unique identifiers. This can make it harder for a replay attacker to generalize from a small number of card instances.
The authentication message may be delivered as the content of a text NDEF record in hexadecimal ASCII format. In another example, the NDEF record may be encoded in hexadecimal format.
At line 812, the application 802 communicates with the contactless card 611 (e.g., after being brought near the contactless card 611). Communication between the application 802 and the contactless card 611 may involve the contactless card 611 being sufficiently close to a card reader (not shown) of the client device 804 to enable data transfer (for instance, via NFC) between the application 802 and the contactless card 611.
At line 810, after communication has been established between client device 804 and contactless card 611, contactless card 611 generates a message authentication code (MAC) cryptogram. In some examples, this may occur when the contactless card 611 is read by the application 802. In particular, this may occur upon a read, such as an NFC read, of a near field data exchange (NDEF) tag, which may be created in accordance with the NFC Data Exchange Format. For example, a reader application, such as application 802, may transmit a message, such as an applet select message, with the applet ID of an NDEF producing applet. Upon confirmation of the selection, a sequence of select file messages followed by read file messages may be transmitted. For example, the sequence may include “Select Capabilities file”, “Read Capabilities file”, and “Select NDEF file”. At this point, a counter value maintained by the contactless card 611 may be updated or incremented, which may be followed by “Read NDEF file.” At this point, the message may be generated which may include a header and a shared secret. Session keys may then be generated. The MAC cryptogram may be created from the message, which may include the header and the shared secret. The MAC cryptogram may then be concatenated with one or more blocks of random data, and the MAC cryptogram and a random number (RND) may be encrypted with the session key. Thereafter, the cryptogram and the header may be concatenated, and encoded as ASCII hex and returned in NDEF message format (responsive to the “Read NDEF file” message).
In some examples, the MAC cryptogram may be transmitted as an NDEF tag, and in other examples the MAC cryptogram may be included with a uniform resource indicator (e.g., as a formatted string). In some examples, application 802 may be configured to transmit a request to contactless card 611, the request comprising an instruction to generate a MAC cryptogram.
At line 814, the contactless card 611 sends the MAC cryptogram to the application 802. In some examples, the transmission of the MAC cryptogram occurs via NFC, however, the present disclosure is not limited thereto. In other examples, this communication may occur via Bluetooth, Wi-Fi, or other means of wireless data communication. At line 812, the application 802 communicates the MAC cryptogram to the processor 804.
At line 816, the processor 804 verifies the MAC cryptogram pursuant to an instruction from the application 132. For example, the MAC cryptogram may be verified, as explained below. In some examples, verifying the MAC cryptogram may be performed by a device other than client device 804, such as a server of a banking system in data communication with the client device 804. For example, processor 804 may output the MAC cryptogram for transmission to the server of the banking system, which may verify the MAC cryptogram. In some examples, the MAC cryptogram may function as a digital signature for purposes of verification. Other digital signature algorithms, such as public key asymmetric algorithms, e.g., the Digital Signature Algorithm and the RSA algorithm, or zero knowledge protocols, may be used to perform this verification.
Regarding master key management, two issuer master keys 1002, 1026 may be required for each part of the portfolio on which the one or more applets is issued. For example, the first master key 1002 may comprise an Issuer Cryptogram Generation/Authentication Key (Iss-Key-Auth) and the second master key 1026 may comprise an Issuer Data Encryption Key (Iss-Key-DEK). As further explained herein, two issuer master keys 1002, 1026 are diversified into card master keys 1008, 1020, which are unique for each card. In some examples, a network profile record ID (pNPR) 522 and derivation key index (pDKI) 1024, as back office data, may be used to identify which Issuer Master Keys 1002, 1026 to use in the cryptographic processes for authentication. The system performing the authentication may be configured to retrieve values of pNPR 1022 and pDKI 1024 for a contactless card at the time of authentication.
In some examples, to increase the security of the solution, a session key may be derived (such as a unique key per session) but rather than using the master key, the unique card-derived keys and the counter may be used as diversification data, as explained above. For example, each time the card is used in operation, a different key may be used for creating the message authentication code (MAC) and for performing the encryption. Regarding session key generation, the keys used to generate the cryptogram and encipher the data in the one or more applets may comprise session keys based on the card unique keys (Card-Key-Auth 1008 and Card-Key-Dek 1020). The session keys (Aut-Session-Key 1032 and DEK-Session-Key 1010) may be generated by the one or more applets and derived by using the application transaction counter (pATC) 1004 with one or more algorithms. To fit data into the one or more algorithms, only the 2 low order bytes of the 4-byte pATC 1004 is used. In some examples, the four byte session key derivation method may comprise: F1:=PATC (lower 2 bytes)∥‘F0’∥‘00’∥PATC (four bytes) F1:=PATC (lower 2 bytes)∥‘0F’∥‘00’∥PATC (four bytes) SK:={(ALG (MK) [F1])∥ALG (MK) [F2]}, where ALG may include 3DES ECB and MK may include the card unique derived master key.
As described herein, one or more MAC session keys may be derived using the lower two bytes of pATC 1004 counter. At each tap of the contactless card, pATC 1004 is configured to be updated, and the card master keys Card-Key-AUTH 508 and Card-Key-DEK 1020 are further diversified into the session keys Aut-Session-Key 1032 and DEK-Session-KEY 1010. pATC 1004 may be initialized to zero at personalization or applet initialization time. In some examples, the pATC counter 1004 may be initialized at or before personalization, and may be configured to increment by one at each NDEF read.
Further, the update for each card may be unique, and assigned either by personalization, or algorithmically assigned by pUID or other identifying information. For example, odd numbered cards may increment or decrement by 2 and even numbered cards may increment or decrement by 5. In some examples, the update may also vary in sequential reads, such that one card may increment in sequence by 1, 3, 5, 2, 2, . . . repeating. The specific sequence or algorithmic sequence may be defined at personalization time, or from one or more processes derived from unique identifiers. This can make it harder for a replay attacker to generalize from a small number of card instances.
The authentication message may be delivered as the content of a text NDEF record in hexadecimal ASCII format. In some examples, only the authentication data and an 8-byte random number followed by MAC of the authentication data may be included. In some examples, the random number may precede cryptogram A and may be one block long. In other examples, there may be no restriction on the length of the random number. In further examples, the total data (i.e., the random number plus the cryptogram) may be a multiple of the block size. In these examples, an additional 8-byte block may be added to match the block produced by the MAC algorithm. As another example, if the algorithms employed used 16-byte blocks, even multiples of that block size may be used, or the output may be automatically, or manually, padded to a multiple of that block size.
The MAC may be performed by a function key (AUT-Session-Key) 1032. The data specified in cryptogram may be processed with javacard.signature method: ALG_DES_MAC8_ISO9797_1_M2_ALG3 to correlate to EMV ARQC verification methods. The key used for this computation may comprise a session key AUT-Session-Key 1032, as explained above. As explained above, the low order two bytes of the counter may be used to diversify for the one or more MAC session keys. As explained below, AUT-Session-Key 1032 may be used to MAC data 1006, and the resulting data or cryptogram A 1014 and random number RND may be encrypted using DEK-Session-Key 1010 to create cryptogram B or output 1018 sent in the message.
In some examples, one or more HSM commands may be processed for decrypting such that the final 16 (binary, 32 hex) bytes may comprise a 3DES symmetric encrypting using CBC mode with a zero IV of the random number followed by MAC authentication data. The key used for this encryption may comprise a session key DEK-Session-Key 1010 derived from the Card-Key-DEK 1020. In this case, the ATC value for the session key derivation is the least significant byte of the counter pATC 1004.
The format below represents a binary version example embodiment. Further, in some examples, the first byte may be set to ASCII ‘A’.
Another exemplary format is shown below. In this example, the tag may be encoded in hexadecimal format.
The UID field of the received message may be extracted to derive, from master keys Iss-Key-AUTH 502 and Iss-Key-DEK 1026, the card master keys (Card-Key-Auth 1008 and Card-Key-DEK 1020) for that particular card. Using the card master keys (Card-Key-Auth 508 and Card-Key-DEK 1020), the counter (pATC) field of the received message may be used to derive the session keys (Aut-Session-Key 1032 and DEK-Session-Key 1010) for that particular card. Cryptogram B 1018 may be decrypted using the DEK-Session-KEY, which yields cryptogram A 1014 and RND, and RND may be discarded. The UID field may be used to look up the shared secret of the contactless card which, along with the Ver, UID, and pATC fields of the message, may be processed through the cryptographic MAC using the re-created Aut-Session-Key to create a MAC output, such as MAC′. If MAC′ is the same as cryptogram A 1014, then this indicates that the message decryption and MAC checking have all passed. Then the pATC may be read to determine if it is valid.
During an authentication session, one or more cryptograms may be generated by the one or more applications. For example, the one or more cryptograms may be generated as a 3DES MAC using ISO 9797-1 Algorithm 3 with Method 2 padding via one or more session keys, such as Aut-Session-Key 1032. The input data 1006 may take the following form: Version (2), pUID (8), pATC (4), Shared Secret (4). In some examples, the numbers in the brackets may comprise length in bytes. In some examples, the shared secret may be generated by one or more random number generators which may be configured to ensure, through one or more secure processes, that the random number is unpredictable. In some examples, the shared secret may comprise a random 4-byte binary number injected into the card at personalization time that is known by the authentication service. During an authentication session, the shared secret may not be provided from the one or more applets to the mobile application. Method 2 padding may include adding a mandatory 0x′80′ byte to the end of input data and 0x′00′ bytes that may be added to the end of the resulting data up to the 8-byte boundary. The resulting cryptogram may comprise 8 bytes in length.
In some examples, one benefit of encrypting an unshared random number as the first block with the MAC cryptogram, is that it acts as an initialization vector while using CBC (Block chaining) mode of the symmetric encryption algorithm. This allows the “scrambling” from block to block without having to pre-establish either a fixed or dynamic IV.
By including the application transaction counter (pATC) as part of the data included in the MAC cryptogram, the authentication service may be configured to determine if the value conveyed in the clear data has been tampered with. Moreover, by including the version in the one or more cryptograms, it is difficult for an attacker to purposefully misrepresent the application version in an attempt to downgrade the strength of the cryptographic solution. In some examples, the pATC may start at zero and be updated by 1 each time the one or more applications generates authentication data. The authentication service may be configured to track the pATCs used during authentication sessions. In some examples, when the authentication data uses a pATC equal to or lower than the previous value received by the authentication service, this may be interpreted as an attempt to replay an old message, and the authenticated may be rejected. In some examples, where the pATC is greater than the previous value received, this may be evaluated to determine if it is within an acceptable range or threshold, and if it exceeds or is outside the range or threshold, verification may be deemed to have failed or be unreliable. In the MAC operation 1012, data 1006 is processed through the MAC using Aut-Session-Key 1032 to produce MAC output (cryptogram A) 1014, which is encrypted.
In order to provide additional protection against brute force attacks exposing the keys on the card, it is desirable that the MAC cryptogram 1014 be enciphered. In some examples, data or cryptogram A 1014 to be included in the ciphertext may comprise: Random number (8), cryptogram (8). In some examples, the numbers in the brackets may comprise length in bytes. In some examples, the random number may be generated by one or more random number generators which may be configured to ensure, through one or more secure processes, that the random number is unpredictable. The key used to encipher this data may comprise a session key. For example, the session key may comprise DEK-Session-Key 1010. In the encryption operation 1016, data or cryptogram A 1014 and RND are processed using DEK-Session-Key 510 to produce encrypted data, cryptogram B 1018. The cryptogram 1014 may be enciphered using 3DES in cipher block chaining mode to ensure that an attacker must run any attacks over all of the ciphertext. As a non-limiting example, other algorithms, such as Advanced Encryption Standard (AES), may be used. In some examples, an initialization vector of 0x′0000000000000000′ may be used. Any attacker seeking to brute force the key used for enciphering this data will be unable to determine when the correct key has been used, as correctly decrypted data will be indistinguishable from incorrectly decrypted data due to its random appearance.
In order for the authentication service to validate the one or more cryptograms provided by the one or more applets, the following data must be conveyed from the one or more applets to the mobile device in the clear during an authentication session: version number to determine the cryptographic approach used and message format for validation of the cryptogram, which enables the approach to change in the future; pUID to retrieve cryptographic assets, and derive the card keys; and pATC to derive the session key used for the cryptogram.
At block 1104, Issuer Master Keys may be diversified by combining them with the card's unique ID number (pUID) and the PAN sequence number (PSN) of one or more applets, for example, a payment applet.
At block 1106, Card-Key-Auth and Card-Key-DEK (unique card keys) may be created by diversifying the Issuer Master Keys to generate session keys which may be used to generate a MAC cryptogram.
At block 1108, the keys used to generate the cryptogram and encipher the data in the one or more applets may comprise the session keys of block 1030 based on the card unique keys (Card-Key-Auth and Card-Key-DEK). In some examples, these session keys may be generated by the one or more applets and derived by using pATC, resulting in session keys Aut-Session-Key and DEK-Session-Key.
At block 1204, the counter value may be encrypted by the sender using the data encryption master key to produce the data encryption derived session key, and the counter value may also be encrypted by the sender using the data integrity master key to produce the data integrity derived session key. In some examples, a whole counter value or a portion of the counter value may be used during both encryptions.
In some examples, the counter value may not be encrypted. In these examples, the counter may be transmitted between the sender and the recipient in the clear, i.e., without encryption.
At block 1206, the data to be protected is processed with a cryptographic MAC operation by the sender using the data integrity session key and a cryptographic MAC algorithm. The protected data, including plaintext and shared secret, may be used to produce a MAC using one of the session keys (AUT-Session-Key).
At block 1208, the data to be protected may be encrypted by the sender using the data encryption derived session key in conjunction with a symmetric encryption algorithm. In some examples, the MAC is combined with an equal amount of random data, for example each 8 bytes long, and then encrypted using the second session key (DEK-Session-Key).
At block 1210, the encrypted MAC is transmitted, from the sender to the recipient, with sufficient information to identify additional secret information (such as shared secret, master keys, etc.), for verification of the cryptogram.
At block 1212, the recipient uses the received counter value to independently derive the two derived session keys from the two master keys as explained above.
At block 1214, the data encryption derived session key is used in conjunction with the symmetric decryption operation to decrypt the protected data. Additional processing on the exchanged data will then occur. In some examples, after the MAC is extracted, it is desirable to reproduce and match the MAC. For example, when verifying the cryptogram, it may be decrypted using appropriately generated session keys. The protected data may be reconstructed for verification. A MAC operation may be performed using an appropriately generated session key to determine if it matches the decrypted MAC. As the MAC operation is an irreversible process, the only way to verify is to attempt to recreate it from source data.
At block 1216, the data integrity derived session key is used in conjunction with the cryptographic MAC operation to verify that the protected data has not been modified.
Some examples of the methods described herein may advantageously confirm when a successful authentication is determined when the following conditions are met. First, the ability to verify the MAC shows that the derived session key was proper. The MAC may only be correct if the decryption was successful and yielded the proper MAC value. The successful decryption may show that the correctly derived encryption key was used to decrypt the encrypted MAC. Since the derived session keys are created using the master keys known only to the sender (e.g., the transmitting device) and recipient (e.g., the receiving device), it may be trusted that the contactless card which originally created the MAC and encrypted the MAC is indeed authentic. Moreover, the counter value used to derive the first and second session keys may be shown to be valid and may be used to perform authentication operations.
Thereafter, the two derived session keys may be discarded, and the next iteration of data exchange will update the counter value (returning to block 1202) and a new set of session keys may be created (at block 1210). In some examples, the combined random data may be discarded.
In block 1302, the card may be configured to dynamically generate data. In some examples, this data may include information such as an account number, card identifier, card verification value, or phone number, which may be transmitted from the card to the device. In some examples, one or more portions of the data may be encrypted via the systems and methods disclosed herein.
In block 1304, one or more portions of the dynamically generated data may be communicated to an application of the device via NFC or other wireless communication. For example, a tap of the card proximate to the device may allow the application of the device to read the one or more portions of the data associated with the contactless card. In some examples, if the device does not comprise an application to assist in activation of the card, the tap of the card may direct the device or prompt the customer to a software application store to download an associated application to activate the card. In some examples, the user may be prompted to sufficiently gesture, place, or orient the card towards a surface of the device, such as either at an angle or flatly placed on, near, or proximate the surface of the device. Responsive to a sufficient gesture, placement and/or orientation of the card, the device may proceed to transmit the one or more encrypted portions of data received from the card to the one or more servers.
In block 1306, the one or more portions of the data may be communicated to one or more servers, such as a card issuer server. For example, one or more encrypted portions of the data may be transmitted from the device to the card issuer server for activation of the card.
In block 1308, the one or more servers may decrypt the one or more encrypted portions of the data via the systems and methods disclosed herein. For example, the one or more servers may receive the encrypted data from the device and may decrypt it in order to compare the received data to record data accessible to the one or more servers. If a resulting comparison of the one or more decrypted portions of the data by the one or more servers yields a successful match, the card may be activated. If the resulting comparison of the one or more decrypted portions of the data by the one or more servers yields an unsuccessful match, one or more processes may take place. For example, responsive to the determination of the unsuccessful match, the user may be prompted to tap, swipe, or wave gesture the card again. In this case, there may be a predetermined threshold comprising a number of attempts that the user is permitted to activate the card. Alternatively, the user may receive a notification, such as a message on his or her device indicative of the unsuccessful attempt of card verification and to call, email or text an associated service for assistance to activate the card, or another notification, such as a phone call on his or her device indicative of the unsuccessful attempt of card verification and to call, email or text an associated service for assistance to activate the card, or another notification, such as an email indicative of the unsuccessful attempt of card verification and to call, email or text an associated service for assistance to activate the card.
In block 1310, the one or more servers may transmit a return message based on the successful activation of the card. For example, the device may be configured to receive output from the one or more servers indicative of a successful activation of the card by the one or more servers. The device may be configured to display a message indicating successful activation of the card. Once the card has been activated, the card may be configured to discontinue dynamically generating data so as to avoid fraudulent use. In this manner, the card may not be activated thereafter, and the one or more servers are notified that the card has already been activated.
As used in this application, the terms “system” and “component” are intended to refer to a computer-related entity, either hardware, a combination of hardware and software, software, or software in execution, examples of which are provided by the exemplary computing computer architecture 1400. For example, a component can be, but is not limited to being, a process running on a processor, a processor, a hard disk drive, multiple storage drives (of optical and/or magnetic storage medium), an object, an executable, a thread of execution, a program, and/or a computer. By way of illustration, both an application running on a server and the server can be a component. One or more components can reside within a process and/or thread of execution, and a component can be localized on one computer and/or distributed between two or more computers. Further, components may be communicatively coupled to each other by various types of communications media to coordinate operations. The coordination may involve the uni-directional or bi-directional exchange of information. For instance, the components may communicate information in the form of signals communicated over the communications media. The information can be implemented as signals allocated to various signal lines. In such allocations, each message is a signal. Further embodiments, however, may alternatively employ data messages. Such data messages may be sent across various connections. Exemplary connections include parallel interfaces, serial interfaces, and bus interfaces.
The computer architecture 1400 includes various common computing elements, such as one or more processors, multi-core processors, co-processors, memory units, chipsets, controllers, peripherals, interfaces, oscillators, timing devices, video cards, audio cards, multimedia input/output (I/O) components, power supplies, and so forth. The embodiments, however, are not limited to implementation by the computing computer architecture 1400.
As shown in
The system bus 1406 provides an interface for system components including, but not limited to, the system memory 1404 to the processor 1402. The system bus 1406 can be any of several types of bus structure that may further interconnect to a memory bus (with or without a memory controller), a peripheral bus, and a local bus using any of a variety of commercially available bus architectures. Interface adapters may connect to the system bus 1406 via slot architecture. Example slot architectures may include without limitation Accelerated Graphics Port (AGP), Card Bus, (Extended) Industry Standard Architecture ((E) ISA), Micro Channel Architecture (MCA), NuBus, Peripheral Component Interconnect (Extended) (PCI(X)), PCI Express, Personal Computer Memory Card International Association (PCMCIA), and the like.
The computer architecture 1400 may include or implement various articles of manufacture. An article of manufacture may include a computer-readable storage medium to store logic. Examples of a computer-readable storage medium may include any tangible media capable of storing electronic data, including volatile memory or non-volatile memory, removable or non-removable memory, erasable or non-erasable memory, writeable or re-writeable memory, and so forth. Examples of logic may include executable computer program instructions implemented using any suitable type of code, such as source code, compiled code, interpreted code, executable code, static code, dynamic code, object-oriented code, visual code, and the like. Embodiments may also be at least partly implemented as instructions contained in or on a non-transitory computer-readable medium, which may be read and executed by one or more processors to enable performance of the operations described herein.
The system memory 1404 may include various types of computer-readable storage media in the form of one or more higher speed memory units, such as read-only memory (ROM), random-access memory (RAM), dynamic RAM (DRAM), Double-Data-Rate DRAM (DDRAM), synchronous DRAM (SDRAM), static RAM (SRAM), programmable ROM (PROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), flash memory, polymer memory such as ferroelectric polymer memory, ovonic memory, phase change or ferroelectric memory, silicon-oxide-nitride-oxide-silicon (SONOS) memory, magnetic or optical cards, an array of devices such as Redundant Array of Independent Disks (RAID) drives, solid state memory devices (e.g., USB memory, solid state drives (SSD) and any other type of storage media suitable for storing information. In the illustrated embodiment shown in
The computer 1412 may include various types of computer-readable storage media in the form of one or more lower speed memory units, including an internal (or external) hard disk drive 1414, a magnetic disk drive 1416 to read from or write to a removable magnetic disk 1418, and an optical disk drive 1420 to read from or write to a removable optical disk 1422 (e.g., a CD-ROM or DVD). The hard disk drive 1414, magnetic disk drive 1416 and optical disk drive 1420 can be connected to the system bus 1406 by an HDD interface 1424, and FDD interface 1426 and an optical disk drive interface 1428, respectively. The HDD interface 1424 for external drive implementations can include at least one or both of Universal Serial Bus (USB) and IEEE 1394 interface technologies.
The drives and associated computer-readable media provide volatile and/or nonvolatile storage of data, data structures, computer-executable instructions, and so forth. For example, a number of program modules can be stored in the drives and non-volatile 1408, and volatile 1410, including an operating system 1430, one or more applications 1432, other program modules 1434, and program data 1436. In one embodiment, the one or more applications 1432, other program modules 1434, and program data 1436 can include, for example, the various applications and/or components of the system 100.
A user can enter commands and information into the computer 1412 through one or more wire/wireless input devices, for example, a keyboard 1438 and a pointing device, such as a mouse 1440. Other input devices may include microphones, infra-red (IR) remote controls, radio-frequency (RF) remote controls, game pads, stylus pens, card readers, dongles, finger print readers, gloves, graphics tablets, joysticks, keyboards, retina readers, touch screens (e.g., capacitive, resistive, etc.), trackballs, track pads, sensors, styluses, and the like. These and other input devices are often connected to the processor 1402 through an input device interface 1442 that is coupled to the system bus 1406 but can be connected by other interfaces such as a parallel port, IEEE 1394 serial port, a game port, a USB port, an IR interface, and so forth.
A monitor 1444 or other type of display device is also connected to the system bus 1406 via an interface, such as a video adapter 1446. The monitor 1444 may be internal or external to the computer 1412. In addition to the monitor 1444, a computer typically includes other peripheral output devices, such as speakers, printers, and so forth.
The computer 1412 may operate in a networked environment using logical connections via wire and/or wireless communications to one or more remote computers, such as a remote computer(s) 1448. The remote computer(s) 1448 can be a workstation, a server computer, a router, a personal computer, portable computer, microprocessor-based entertainment appliance, a peer device or other common network node, and typically includes many or all the elements described relative to the computer 1412, although, for purposes of brevity, only a memory and/or storage device 1450 is illustrated. The logical connections depicted include wire/wireless connectivity to a local area network 1452 and/or larger networks, for example, a wide area network 1454. Such LAN and WAN networking environments are commonplace in offices and companies, and facilitate enterprise-wide computer networks, such as intranets, all of which may connect to a global communications network, for example, the Internet.
When used in a local area network 1452 networking environment, the computer 1412 is connected to the local area network 1452 through a wire and/or wireless communication network interface or network adapter 1456. The network adapter 1456 can facilitate wire and/or wireless communications to the local area network 1452, which may also include a wireless access point disposed thereon for communicating with the wireless functionality of the network adapter 1456.
When used in a wide area network 1454 networking environment, the computer 1412 can include a modem 1458, or is connected to a communications server on the wide area network 1454 or has other means for establishing communications over the wide area network 1454, such as by way of the Internet. The modem 1458, which can be internal or external and a wire and/or wireless device, connects to the system bus 1406 via the input device interface 1442. In a networked environment, program modules depicted relative to the computer 1412, or portions thereof, can be stored in the remote memory and/or storage device 1450. It will be appreciated that the network connections shown are exemplary and other means of establishing a communications link between the computers can be used.
The computer 1412 is operable to communicate with wire and wireless devices or entities using the IEEE 802 family of standards, such as wireless devices operatively disposed in wireless communication (e.g., IEEE 802.11 over-the-air modulation techniques). This includes at least Wi-Fi (or Wireless Fidelity), WiMax, and Bluetooth™ wireless technologies, among others. Thus, the communication can be a predefined structure as with a conventional network or simply an ad hoc communication between at least two devices. Wi-Fi networks use radio technologies called IEEE 802.11 (a, b, g, n, ac, ax, etc.) to provide secure, reliable, fast wireless connectivity. A Wi-Fi network can be used to connect computers to each other, to the Internet, and to wire networks (which use IEEE 802.3-related media and functions).
The various elements of the devices as previously described with reference to
One or more aspects of at least one embodiment may be implemented by representative instructions stored on a machine-readable medium which represents various logic within the processor, which when read by a machine causes the machine to fabricate logic to perform the techniques described herein. Such representations, known as “IP cores” may be stored on a tangible, machine readable medium and supplied to various customers or manufacturing facilities to load into the fabrication machines that make the logic or processor. Some embodiments may be implemented, for example, using a machine-readable medium or article which may store an instruction or a set of instructions that, if executed by a machine, may cause the machine to perform a method and/or operations in accordance with the embodiments. Such a machine may include, for example, any suitable processing platform, computing platform, computing device, processing device, computing system, processing system, computer, processor, or the like, and may be implemented using any suitable combination of hardware and/or software. The machine-readable medium or article may include, for example, any suitable type of memory unit, memory device, memory article, memory medium, storage device, storage article, storage medium and/or storage unit, for example, memory, removable or non-removable media, erasable or non-erasable media, writeable or re-writeable media, digital or analog media, hard disk, floppy disk, Compact Disk Read Only Memory (CD-ROM), Compact Disk Recordable (CD-R), Compact Disk Rewriteable (CD-RW), optical disk, magnetic media, magneto-optical media, removable memory cards or disks, various types of Digital Versatile Disk (DVD), a tape, a cassette, or the like. The instructions may include any suitable type of code, such as source code, compiled code, interpreted code, executable code, static code, dynamic code, encrypted code, and the like, implemented using any suitable high-level, low-level, object-oriented, visual, compiled and/or interpreted programming language.
The components and features of the devices described above may be implemented using any combination of discrete circuitry, application specific integrated circuits (ASICs), logic gates and/or single chip architectures. Further, the features of the devices may be implemented using microcontrollers, programmable logic arrays and/or microprocessors or any combination of the foregoing where suitably appropriate. It is noted that hardware, firmware and/or software elements may be collectively or individually referred to herein as “logic” or “circuit.”
It will be appreciated that the exemplary devices shown in the block diagrams described above may represent one functionally descriptive example of many potential implementations. Accordingly, division, omission or inclusion of block functions depicted in the accompanying figures does not infer that the hardware components, circuits, software and/or elements for implementing these functions would necessarily be divided, omitted, or included in embodiments.
At least one computer-readable storage medium may include instructions that, when executed, cause a system to perform any of the computer-implemented methods described herein.
Some embodiments may be described using the expression “one embodiment” or “an embodiment” along with their derivatives. These terms mean that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. The appearances of the phrase “in one embodiment” in various places in the specification are not necessarily all referring to the same embodiment. Moreover, unless otherwise noted the features described above are recognized to be usable together in any combination. Thus, any features discussed separately may be employed in combination with each other unless it is noted that the features are incompatible with each other.
It is emphasized that the Abstract of the Disclosure is provided to allow a reader to quickly ascertain the nature of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In addition, in the foregoing Detailed Description, it can be seen that various features are grouped together in a single embodiment for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed embodiment. Thus the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separate embodiment. In the appended claims, the terms “including” and “in which” are used as the plain-English equivalents of the respective terms “comprising” and “wherein,” respectively. Moreover, the terms “first,” “second,” “third,” and so forth, are used merely as labels, and are not intended to impose numerical requirements on their objects.
What has been described above includes examples of the disclosed architecture. It is, of course, not possible to describe every conceivable combination of components and/or methodologies, but one of ordinary skill in the art may recognize that many further combinations and permutations are possible. Accordingly, the novel architecture is intended to embrace all such alterations, modifications and variations that fall within the spirit and scope of the appended claims.
The foregoing description of example embodiments has been presented for the purposes of illustration and description. It is not intended to be exhaustive or to limit the present disclosure to the precise forms disclosed. Many modifications and variations are possible in light of this disclosure. It is intended that the scope of the present disclosure be limited not by this detailed description, but rather by the claims appended hereto. Future filed applications claiming priority to this application may claim the disclosed subject matter in a different manner, and may generally include any set of one or more limitations as variously disclosed or otherwise demonstrated herein.
Claims
1. A computer-implemented method, comprising:
- establishing, at a financial institution server, a secure network connection between the financial institution server and a user device;
- receiving, at a financial institution server from the user device via the secure connection, a plurality of payment card number requests, wherein a respective payment card number request is received for each merchant website of a plurality of merchant websites;
- sending an authentication request to the user device, wherein the authentication request is a request for a user of the user device to bring a contactless payment card associated with a user financial institution account within a near field communication (NFC) range of the user device;
- receiving, from the user device, encrypted authentication information received from the contactless payment card in response to the authentication request, the encrypted authentication information received after the contactless payment card is brought within NFC range of the user device;
- authenticating the encrypted authentication information received from the user device;
- based on the authenticating being successful, granting respective tokens to each respective merchant of the plurality of merchants, wherein each respective token of the granted respective tokens identifies a respective communication session established with each respective merchant and enables a continued exchange of data with each respective merchant; and
- using each respective token to identify the respective communication session established with each respective merchant, providing account information as needed to each respective merchant to associate a respective merchant account with a user of the contactless payment card.
2. The computer-implemented method of claim 1, wherein a last payment card number request of the plurality of payment card number requests is received within a predetermined time period; and
- wherein the encrypted authentication information is embedded within a universal resource locator (URL) sent from the contactless payment card and forwarded to the financial institution server.
3. The computer-implemented method of claim 2, wherein the predetermined time period is determined based on a time of a receipt of a first payment card number request of the plurality of payment card number requests.
4. The computer-implemented method of claim 2, wherein the predetermined time period is about 5 minutes, about 10 minutes, or about 20 minutes.
5. The computer-implemented method of claim 1, wherein the financial institution server is configured to use a corresponding granted respective token as a header of a communication message to uniquely identify a transaction.
6. The computer-implemented method of claim 1, wherein the secure connection is established based on identifying information of the user of the contactless payment card.
7. The computer-implemented method of claim 6, wherein the identifying information is received prior to receiving a first payment card number request of the plurality of payment card number requests.
8. The computer-implemented method of claim 1, wherein authenticating the encrypted authentication information received from the user device comprises: decrypting the encrypted authentication information; and confirming information input from the user device corresponds with the decrypted authentication information accessible by the financial institution server.
9. The computer-implemented method of claim 8, wherein authenticating the encrypted authentication information received from the user device comprises, upon successful confirmation, generating an authorization to grant the respective tokens for each payment card number request of the plurality of payment card number requests.
10. A computer-implemented method, comprising:
- establishing, at a financial institution server, a secure network connection between the financial institution server and a user device;
- receiving, at the financial institution server from the user device, a first payment card number request from a first merchant of a plurality of merchants to associate user financial institution account information with a first merchant account;
- sending a contactless payment card step-up authentication request to the user device, wherein the contactless payment card step-up authentication request is a request for a contactless payment card associated with the user financial institution account information to be brought within a near field communication (NFC) range of the user device;
- receiving, from the user mobile device, encrypted authentication information maintained on the contactless payment card in response to the contactless payment card step-up request, the encrypted authentication information received after the contactless payment card is brought within NFC range of the user device;
- authenticating the encrypted authentication information received from the user device; and
- based on the authenticating being successful, granting a first token to the first merchant, wherein the first token identifies a communication session with the first merchant and enables a continued exchange of data with the first merchant.
11. The computer-implemented method of claim 10, further comprising using the token to identify the communication session, providing account information as needed for the first merchant to populate the first merchant account; and
- wherein the encrypted authentication information is embedded within a universal resource locator (URL) send from the contactless payment card and forwarded to the financial institution server.
12. The computer-implemented method of claim 10, further comprising:
- receive a second payment card number request from a second merchant;
- based on the authenticating being successful, granting a second token to the second merchant, wherein the second token identifies a communication session with the second merchant and enables a continued exchange of data of user financial institution account data with the second merchant.
13. The computer-implemented method of claim 10, wherein the token enables retrieval of data by each merchant of the plurality of merchants.
14. The computer-implemented method of claim 10, wherein the user financial institution account information includes a payment card number of a user of the user device and payment card number-related information.
15. A non-transitory computer-readable storage medium, the computer-readable storage medium including instructions that when executed by a processor, cause the processor to:
- establish a secure network connection between the processor and a user device;
- receive, from the user device via the secure network connection, a plurality of payment card number requests, wherein a respective payment card number request is received for each merchant website of a plurality of merchant websites;
- send a contactless payment card step-up authentication request to the user device, wherein the contactless payment card step-up authentication request is a request for a contactless payment card associated with a user financial institution account to be brought within a near field communication (NFC) range of the user device;
- receive, from the user device, encrypted authentication information obtained from the contactless payment card in response to the contactless payment card step-up request, the encrypted authentication information received after the contactless payment card is brought within NFC range of the user device;
- authenticate the encrypted authentication information received from the user device;
- based on the authenticating being successful, grant respective tokens to each respective merchant of the plurality of merchants, wherein each respective token of the granted respective tokens identifies a respective communication session established with each respective merchant and enables a continued exchange of data with each respective merchant; and
- using each respective token to identify the respective communication session established with each respective merchant, provide account information as needed to each respective merchant to associate a respective merchant account with a user of the contactless payment card.
16. The computer-readable storage medium of claim 15, wherein a last payment card number request of the plurality of payment card number requests is received within a predetermined time period; and
- wherein the encrypted authentication information is embedded within a universal resource locator (URL) sent from the contactless payment card.
17. The computer-readable storage medium of claim 16, wherein the predetermined time period is determined based on a time of a receipt of a first payment card number request of the plurality of payment card number requests.
18. The computer-readable storage medium of claim 16, wherein the predetermined time period is about 5 minutes, about 10 minutes, or about 20 minutes.
19. The computer-readable storage medium of claim 15, wherein receiving the plurality of payment card number requests, the processor is operable to:
- establish the secure network connection with the user device based on identifying information of the user received prior to receiving a first payment card number request of the plurality of payment card number requests.
20. The computer-readable storage medium of claim 19, wherein authenticating the encrypted authentication information received from the user device comprises:
- decrypting the encrypted authentication information;
- confirm information input from the user device corresponds with the decrypted authentication information; and
- upon successful confirmation, generate an authorization to grant the respective tokens for each payment card number request of the plurality of payment card number requests.
| 4683553 | July 28, 1987 | Mollier |
| 4827113 | May 2, 1989 | Rikuna |
| 4910773 | March 20, 1990 | Hazard et al. |
| 5036461 | July 30, 1991 | Elliott et al. |
| 5363448 | November 8, 1994 | Koopman, Jr. et al. |
| 5377270 | December 27, 1994 | Koopman, Jr. et al. |
| 5533126 | July 2, 1996 | Hazard |
| 5537314 | July 16, 1996 | Kanter |
| 5590038 | December 31, 1996 | Pitroda |
| 5592553 | January 7, 1997 | Guski et al. |
| 5616901 | April 1, 1997 | Crandall |
| 5666415 | September 9, 1997 | Kaufman |
| 5763373 | June 9, 1998 | Robinson et al. |
| 5764789 | June 9, 1998 | Pare, Jr. et al. |
| 5768373 | June 16, 1998 | Lohstroh et al. |
| 5778072 | July 7, 1998 | Samar |
| 5796827 | August 18, 1998 | Coppersmith et al. |
| 5832090 | November 3, 1998 | Raspotnik |
| 5883810 | March 16, 1999 | Franklin et al. |
| 5901874 | May 11, 1999 | Deters |
| 5929413 | July 27, 1999 | Gardner |
| 5960411 | September 28, 1999 | Hartman et al. |
| 6021203 | February 1, 2000 | Douceur et al. |
| 6049328 | April 11, 2000 | Vanderheiden |
| 6058373 | May 2, 2000 | Blinn et al. |
| 6061666 | May 9, 2000 | Do et al. |
| 6105013 | August 15, 2000 | Curry et al. |
| 6199114 | March 6, 2001 | White et al. |
| 6199762 | March 13, 2001 | Hohle |
| 6216227 | April 10, 2001 | Goldstein et al. |
| 6227447 | May 8, 2001 | Campisano |
| 6282522 | August 28, 2001 | Davis et al. |
| 6324271 | November 27, 2001 | Sawyer et al. |
| 6342844 | January 29, 2002 | Rozin |
| 6367011 | April 2, 2002 | Lee et al. |
| 6402028 | June 11, 2002 | Graham, Jr. et al. |
| 6438550 | August 20, 2002 | Doyle et al. |
| 6501847 | December 31, 2002 | Helot et al. |
| 6572015 | June 3, 2003 | Norton |
| 6631197 | October 7, 2003 | Taenzer |
| 6631849 | October 14, 2003 | Blossom |
| 6641050 | November 4, 2003 | Kelley et al. |
| 6655585 | December 2, 2003 | Shinn |
| 6662020 | December 9, 2003 | Aaro et al. |
| 6721706 | April 13, 2004 | Strubbe et al. |
| 6731778 | May 4, 2004 | Oda et al. |
| 6779115 | August 17, 2004 | Naim |
| 6792533 | September 14, 2004 | Jablon |
| 6829711 | December 7, 2004 | Kwok et al. |
| 6834271 | December 21, 2004 | Hodgson et al. |
| 6834795 | December 28, 2004 | Rasmussen et al. |
| 6852031 | February 8, 2005 | Rowe |
| 6865547 | March 8, 2005 | Brake, Jr. et al. |
| 6873260 | March 29, 2005 | Lancos et al. |
| 6873974 | March 29, 2005 | Schutzer |
| 6877656 | April 12, 2005 | Jaros et al. |
| 6889198 | May 3, 2005 | Kawan |
| 6905411 | June 14, 2005 | Nguyen et al. |
| 6910627 | June 28, 2005 | Simpson-Young et al. |
| 6971031 | November 29, 2005 | Haala |
| 6990588 | January 24, 2006 | Yasukura |
| 7006986 | February 28, 2006 | Sines et al. |
| 7085931 | August 1, 2006 | Smith et al. |
| 7127605 | October 24, 2006 | Montgomery et al. |
| 7128274 | October 31, 2006 | Kelley |
| 7140550 | November 28, 2006 | Ramachandran |
| 7152045 | December 19, 2006 | Hoffman |
| 7165727 | January 23, 2007 | de Jong |
| 7175076 | February 13, 2007 | Block et al. |
| 7202773 | April 10, 2007 | Oba et al. |
| 7206806 | April 17, 2007 | Pineau |
| 7232073 | June 19, 2007 | de Jong |
| 7246752 | July 24, 2007 | Brown |
| 7252242 | August 7, 2007 | Ho |
| 7254569 | August 7, 2007 | Goodman et al. |
| 7263507 | August 28, 2007 | Brake, Jr. et al. |
| 7270276 | September 18, 2007 | Vayssiere |
| 7278025 | October 2, 2007 | Saito et al. |
| 7287692 | October 30, 2007 | Patel et al. |
| 7290709 | November 6, 2007 | Tsai et al. |
| 7306143 | December 11, 2007 | Bonneau, Jr. et al. |
| 7319986 | January 15, 2008 | Praisner et al. |
| 7325132 | January 29, 2008 | Takayama et al. |
| 7360688 | April 22, 2008 | Harris |
| 7373515 | May 13, 2008 | Owen et al. |
| 7374099 | May 20, 2008 | de Jong |
| 7375616 | May 20, 2008 | Rowse et al. |
| 7380710 | June 3, 2008 | Brown |
| 7424977 | September 16, 2008 | Smets et al. |
| 7453439 | November 18, 2008 | Kushler et al. |
| 7472829 | January 6, 2009 | Brown |
| 7487357 | February 3, 2009 | Smith et al. |
| 7527208 | May 5, 2009 | Hammad |
| 7568631 | August 4, 2009 | Gibbs et al. |
| 7580898 | August 25, 2009 | Brown |
| 7584153 | September 1, 2009 | Brown et al. |
| 7597250 | October 6, 2009 | Finn |
| 7628322 | December 8, 2009 | Holtmanns et al. |
| 7652578 | January 26, 2010 | Braun et al. |
| 7689832 | March 30, 2010 | Talmor et al. |
| 7703142 | April 20, 2010 | Wilson et al. |
| 7748609 | July 6, 2010 | Sachdeva et al. |
| 7748617 | July 6, 2010 | Gray |
| 7748636 | July 6, 2010 | Finn |
| 7762457 | July 27, 2010 | Bonalle et al. |
| 7789302 | September 7, 2010 | Tame |
| 7793851 | September 14, 2010 | Mullen |
| 7796013 | September 14, 2010 | Murakami et al. |
| 7801799 | September 21, 2010 | Brake, Jr. et al. |
| 7801829 | September 21, 2010 | Gray et al. |
| 7805755 | September 28, 2010 | Brown et al. |
| 7809643 | October 5, 2010 | Phillips et al. |
| 7827115 | November 2, 2010 | Weller et al. |
| 7828214 | November 9, 2010 | Narendra et al. |
| 7848746 | December 7, 2010 | Juels |
| 7882553 | February 1, 2011 | Tuliani |
| 7900048 | March 1, 2011 | Andersson |
| 7908216 | March 15, 2011 | Davis et al. |
| 7922082 | April 12, 2011 | Muscato |
| 7933589 | April 26, 2011 | Mamdani et al. |
| 7949559 | May 24, 2011 | Freiberg |
| 7954716 | June 7, 2011 | Narendra et al. |
| 7954723 | June 7, 2011 | Charrat |
| 7962369 | June 14, 2011 | Rosenberg |
| 7993197 | August 9, 2011 | Kaminkow |
| 8005426 | August 23, 2011 | Huomo et al. |
| 8010405 | August 30, 2011 | Bortolin et al. |
| RE42762 | September 27, 2011 | Shin et al. |
| 8041954 | October 18, 2011 | Plesman |
| 8060012 | November 15, 2011 | Sklovsky et al. |
| 8074877 | December 13, 2011 | Mullen et al. |
| 8082450 | December 20, 2011 | Frey et al. |
| 8095113 | January 10, 2012 | Kean et al. |
| 8099332 | January 17, 2012 | Lemay et al. |
| 8103249 | January 24, 2012 | Markison |
| 8108687 | January 31, 2012 | Ellis et al. |
| 8127143 | February 28, 2012 | Abdallah et al. |
| 8135648 | March 13, 2012 | Oram et al. |
| 8140010 | March 20, 2012 | Symons et al. |
| 8141136 | March 20, 2012 | Lee et al. |
| 8150321 | April 3, 2012 | Winter et al. |
| 8150767 | April 3, 2012 | Wankmueller |
| 8186602 | May 29, 2012 | Itay et al. |
| 8196131 | June 5, 2012 | von Behren et al. |
| 8215563 | July 10, 2012 | Levy et al. |
| 8224753 | July 17, 2012 | Atef et al. |
| 8232879 | July 31, 2012 | Davis |
| 8233841 | July 31, 2012 | Griffin et al. |
| 8245292 | August 14, 2012 | Buer |
| 8249654 | August 21, 2012 | Zhu |
| 8266451 | September 11, 2012 | Leydier et al. |
| 8276814 | October 2, 2012 | Davis |
| 8285329 | October 9, 2012 | Zhu |
| 8302872 | November 6, 2012 | Mullen |
| 8312519 | November 13, 2012 | Bailey et al. |
| 8316237 | November 20, 2012 | Felsher et al. |
| 8332272 | December 11, 2012 | Fisher |
| 8346670 | January 1, 2013 | Hasson |
| 8365988 | February 5, 2013 | Medina, III et al. |
| 8369960 | February 5, 2013 | Tran et al. |
| 8371501 | February 12, 2013 | Hopkins |
| 8381307 | February 19, 2013 | Cimino |
| 8391719 | March 5, 2013 | Alameh et al. |
| 8417231 | April 9, 2013 | Sanding et al. |
| 8439271 | May 14, 2013 | Smets et al. |
| 8442914 | May 14, 2013 | Killian |
| 8475367 | July 2, 2013 | Yuen et al. |
| 8489112 | July 16, 2013 | Roeding et al. |
| 8511542 | August 20, 2013 | Pan |
| 8511547 | August 20, 2013 | Rans |
| 8519822 | August 27, 2013 | Riegebauer |
| 8559872 | October 15, 2013 | Butler |
| 8566916 | October 22, 2013 | Bailey et al. |
| 8567670 | October 29, 2013 | Stanfield et al. |
| 8572386 | October 29, 2013 | Takekawa et al. |
| 8577810 | November 5, 2013 | Dalit et al. |
| 8583454 | November 12, 2013 | Beraja et al. |
| 8589335 | November 19, 2013 | Smith et al. |
| 8594730 | November 26, 2013 | Bona et al. |
| 8615468 | December 24, 2013 | Varadarajan |
| 8620218 | December 31, 2013 | Awad |
| 8639600 | January 28, 2014 | Lee |
| 8667285 | March 4, 2014 | Coulier et al. |
| 8723941 | May 13, 2014 | Shirbabadi et al. |
| 8726405 | May 13, 2014 | Bailey et al. |
| 8740073 | June 3, 2014 | Vijayshankar et al. |
| 8750514 | June 10, 2014 | Gallo et al. |
| 8752189 | June 10, 2014 | de Jong |
| 8794509 | August 5, 2014 | Bishop et al. |
| 8799668 | August 5, 2014 | Cheng |
| 8806592 | August 12, 2014 | Ganesan |
| 8807440 | August 19, 2014 | von Behren et al. |
| 8811892 | August 19, 2014 | Khan et al. |
| 8814039 | August 26, 2014 | Bishop et al. |
| 8814052 | August 26, 2014 | Bona et al. |
| 8818867 | August 26, 2014 | Baldwin et al. |
| 8850538 | September 30, 2014 | Vernon et al. |
| 8861733 | October 14, 2014 | Benteo et al. |
| 8870081 | October 28, 2014 | Olson |
| 8880027 | November 4, 2014 | Darringer |
| 8888002 | November 18, 2014 | Marshall Chesney et al. |
| 8898088 | November 25, 2014 | Springer et al. |
| 8934837 | January 13, 2015 | Zhu et al. |
| 8939356 | January 27, 2015 | Pourfallah |
| 8977569 | March 10, 2015 | Rao |
| 8994498 | March 31, 2015 | Agrafioti et al. |
| 9004365 | April 14, 2015 | Bona et al. |
| 9038893 | May 26, 2015 | Kirkham |
| 9038894 | May 26, 2015 | Khalid |
| 9042814 | May 26, 2015 | Royston et al. |
| 9047531 | June 2, 2015 | Showering et al. |
| 9069976 | June 30, 2015 | Toole et al. |
| 9081948 | July 14, 2015 | Magne |
| 9104853 | August 11, 2015 | Venkataramani et al. |
| 9118663 | August 25, 2015 | Bailey et al. |
| 9122964 | September 1, 2015 | Krawczewicz |
| 9129199 | September 8, 2015 | Spodak |
| 9129280 | September 8, 2015 | Bona et al. |
| 9152832 | October 6, 2015 | Royston et al. |
| 9183490 | November 10, 2015 | Moreton |
| 9203800 | December 1, 2015 | Izu et al. |
| 9209867 | December 8, 2015 | Royston |
| 9251330 | February 2, 2016 | Boivie et al. |
| 9251518 | February 2, 2016 | Levin et al. |
| 9258715 | February 9, 2016 | Borghei |
| 9270337 | February 23, 2016 | Zhu et al. |
| 9275325 | March 1, 2016 | Newcombe |
| 9286606 | March 15, 2016 | Diamond |
| 9306626 | April 5, 2016 | Hall et al. |
| 9306753 | April 5, 2016 | Vandervort |
| 9306942 | April 5, 2016 | Bailey et al. |
| 9324066 | April 26, 2016 | Archer et al. |
| 9324067 | April 26, 2016 | Van Os et al. |
| 9332587 | May 3, 2016 | Salahshoor |
| 9338622 | May 10, 2016 | Bjontegard |
| 9373141 | June 21, 2016 | Shakkarwar |
| 9379841 | June 28, 2016 | Fine et al. |
| 9413430 | August 9, 2016 | Royston et al. |
| 9413768 | August 9, 2016 | Gregg et al. |
| 9420496 | August 16, 2016 | Indurkar |
| 9426132 | August 23, 2016 | Alikhani |
| 9432339 | August 30, 2016 | Bowness |
| 9455968 | September 27, 2016 | Machani et al. |
| 9473509 | October 18, 2016 | Arsanjani et al. |
| 9491626 | November 8, 2016 | Sharma et al. |
| 9501776 | November 22, 2016 | Martin |
| 9553637 | January 24, 2017 | Yang et al. |
| 9619952 | April 11, 2017 | Zhao et al. |
| 9635000 | April 25, 2017 | Muftic |
| 9665858 | May 30, 2017 | Kumar |
| 9674705 | June 6, 2017 | Rose et al. |
| 9679286 | June 13, 2017 | Colnot et al. |
| 9680942 | June 13, 2017 | Dimmick |
| 9710744 | July 18, 2017 | Wurmfeld |
| 9710804 | July 18, 2017 | Zhou et al. |
| 9740342 | August 22, 2017 | Paulsen et al. |
| 9740988 | August 22, 2017 | Levin et al. |
| 9763097 | September 12, 2017 | Robinson et al. |
| 9767329 | September 19, 2017 | Forster |
| 9769662 | September 19, 2017 | Queru |
| 9773151 | September 26, 2017 | Mil'shtein et al. |
| 9780953 | October 3, 2017 | Gaddam et al. |
| 9891823 | February 13, 2018 | Feng et al. |
| 9940571 | April 10, 2018 | Herrington |
| 9949065 | April 17, 2018 | Zarakas |
| 9953323 | April 24, 2018 | Candelore et al. |
| 9961194 | May 1, 2018 | Wiechman et al. |
| 9965632 | May 8, 2018 | Zarakas |
| 9965756 | May 8, 2018 | Davis et al. |
| 9965911 | May 8, 2018 | Wishne |
| 9977890 | May 22, 2018 | Alberti |
| 9978056 | May 22, 2018 | Seo |
| 9978058 | May 22, 2018 | Wurmfeld et al. |
| 9990795 | June 5, 2018 | Wurmfeld |
| 10007873 | June 26, 2018 | Heo |
| 10013693 | July 3, 2018 | Wyatt |
| 10043164 | August 7, 2018 | Dogin et al. |
| 10075437 | September 11, 2018 | Costigan et al. |
| 10121130 | November 6, 2018 | Pinski |
| 10129648 | November 13, 2018 | Hernandez et al. |
| 10133979 | November 20, 2018 | Eidam et al. |
| 10210505 | February 19, 2019 | Zarakas |
| 10217105 | February 26, 2019 | Sangi et al. |
| 10242368 | March 26, 2019 | Poole |
| 10296910 | May 21, 2019 | Templeton |
| 10332102 | June 25, 2019 | Zarakas |
| 10360557 | July 23, 2019 | Locke |
| 10380471 | August 13, 2019 | Locke |
| 10395244 | August 27, 2019 | Mossler |
| 10453054 | October 22, 2019 | Zarakas |
| 10474941 | November 12, 2019 | Wurmfeld |
| 10475027 | November 12, 2019 | Guise |
| 10482453 | November 19, 2019 | Zarakas |
| 10482457 | November 19, 2019 | Poole |
| 10489774 | November 26, 2019 | Zarakas |
| 10489781 | November 26, 2019 | Osborn |
| 10510070 | December 17, 2019 | Wurmfeld |
| 10515361 | December 24, 2019 | Zarakas |
| 10535068 | January 14, 2020 | Locke |
| 10546444 | January 28, 2020 | Osborn |
| 10581611 | March 3, 2020 | Osborn |
| 10664830 | May 26, 2020 | Rule |
| 10685349 | June 16, 2020 | Brickell |
| 10797882 | October 6, 2020 | Rule |
| 10880741 | December 29, 2020 | Zarakas |
| 10909525 | February 2, 2021 | Dhodapkar |
| 10970691 | April 6, 2021 | Koeppel |
| 10984416 | April 20, 2021 | Ilincic |
| 11037136 | June 15, 2021 | Rule |
| 11062098 | July 13, 2021 | Bergeron |
| 11120453 | September 14, 2021 | Rule |
| 11138593 | October 5, 2021 | Ho |
| 11138605 | October 5, 2021 | Aabye |
| 11176540 | November 16, 2021 | Gupta |
| 11188908 | November 30, 2021 | Locke |
| 11216806 | January 4, 2022 | Mossler |
| 11238441 | February 1, 2022 | Mullins |
| 11297958 | April 12, 2022 | Vukich |
| 11334872 | May 17, 2022 | Phillips |
| 11361173 | June 14, 2022 | Edwards |
| 11392933 | July 19, 2022 | Mossler |
| 11392935 | July 19, 2022 | Suresh |
| 11416844 | August 16, 2022 | Osterkamp |
| 11423392 | August 23, 2022 | Ho |
| 11443292 | September 13, 2022 | Sherif |
| 11444770 | September 13, 2022 | Wieker |
| 11461764 | October 4, 2022 | Rule |
| 11481764 | October 25, 2022 | Shakkarwar |
| 11521213 | December 6, 2022 | Rule |
| 11551200 | January 10, 2023 | Cook |
| 11556918 | January 17, 2023 | Mestre |
| 11615395 | March 28, 2023 | McHugh |
| 11777933 | October 3, 2023 | Moreton |
| 20010010723 | August 2, 2001 | Pinkas |
| 20010029485 | October 11, 2001 | Brody et al. |
| 20010034702 | October 25, 2001 | Mockett et al. |
| 20010054003 | December 20, 2001 | Chien et al. |
| 20020078345 | June 20, 2002 | Sandhu et al. |
| 20020093530 | July 18, 2002 | Krothapalli et al. |
| 20020100808 | August 1, 2002 | Norwood et al. |
| 20020120583 | August 29, 2002 | Keresman, III et al. |
| 20020152116 | October 17, 2002 | Yan et al. |
| 20020153424 | October 24, 2002 | Li |
| 20020165827 | November 7, 2002 | Gien et al. |
| 20030023554 | January 30, 2003 | Yap et al. |
| 20030034873 | February 20, 2003 | Chase et al. |
| 20030055727 | March 20, 2003 | Walker et al. |
| 20030078882 | April 24, 2003 | Sukeda et al. |
| 20030167350 | September 4, 2003 | Davis et al. |
| 20030208449 | November 6, 2003 | Diao |
| 20030220876 | November 27, 2003 | Burger |
| 20040015958 | January 22, 2004 | Veil et al. |
| 20040039919 | February 26, 2004 | Takayama et al. |
| 20040127256 | July 1, 2004 | Goldthwaite et al. |
| 20040215674 | October 28, 2004 | Odinak et al. |
| 20040230799 | November 18, 2004 | Davis |
| 20050044367 | February 24, 2005 | Gasparini et al. |
| 20050075985 | April 7, 2005 | Cartmell |
| 20050081038 | April 14, 2005 | Arditti Modiano et al. |
| 20050138387 | June 23, 2005 | Lam et al. |
| 20050149386 | July 7, 2005 | Agura |
| 20050156026 | July 21, 2005 | Ghosh et al. |
| 20050160049 | July 21, 2005 | Lundholm |
| 20050195975 | September 8, 2005 | Kawakita |
| 20050228997 | October 13, 2005 | Bicker |
| 20050247797 | November 10, 2005 | Ramachandran |
| 20050269402 | December 8, 2005 | Spitzer |
| 20060006230 | January 12, 2006 | Bear et al. |
| 20060040726 | February 23, 2006 | Szrek et al. |
| 20060041402 | February 23, 2006 | Baker |
| 20060044153 | March 2, 2006 | Dawidowsky |
| 20060047954 | March 2, 2006 | Sachdeva et al. |
| 20060059253 | March 16, 2006 | Goodman |
| 20060085848 | April 20, 2006 | Aissi et al. |
| 20060136334 | June 22, 2006 | Atkinson et al. |
| 20060173985 | August 3, 2006 | Moore |
| 20060174331 | August 3, 2006 | Schuetz |
| 20060242698 | October 26, 2006 | Inskeep et al. |
| 20060280338 | December 14, 2006 | Rabb |
| 20070033642 | February 8, 2007 | Ganesan et al. |
| 20070055630 | March 8, 2007 | Gauthier et al. |
| 20070061266 | March 15, 2007 | Moore et al. |
| 20070061487 | March 15, 2007 | Moore et al. |
| 20070116292 | May 24, 2007 | Kurita et al. |
| 20070118745 | May 24, 2007 | Buer |
| 20070197261 | August 23, 2007 | Humbel |
| 20070224969 | September 27, 2007 | Rao |
| 20070241182 | October 18, 2007 | Buer |
| 20070256134 | November 1, 2007 | Lehtonen et al. |
| 20070258594 | November 8, 2007 | Sandhu et al. |
| 20070276765 | November 29, 2007 | Hazel |
| 20070278291 | December 6, 2007 | Rans et al. |
| 20080008315 | January 10, 2008 | Fontana et al. |
| 20080011831 | January 17, 2008 | Bonalle et al. |
| 20080014867 | January 17, 2008 | Finn |
| 20080035738 | February 14, 2008 | Mullen |
| 20080071681 | March 20, 2008 | Khalid |
| 20080072303 | March 20, 2008 | Syed |
| 20080082452 | April 3, 2008 | Wankmueller |
| 20080086767 | April 10, 2008 | Kulkarni et al. |
| 20080099552 | May 1, 2008 | Grillion |
| 20080103968 | May 1, 2008 | Bies et al. |
| 20080109309 | May 8, 2008 | Landau et al. |
| 20080110983 | May 15, 2008 | Ashfield |
| 20080120711 | May 22, 2008 | Dispensa |
| 20080156873 | July 3, 2008 | Wilhelm et al. |
| 20080162312 | July 3, 2008 | Sklovsky et al. |
| 20080164308 | July 10, 2008 | Aaron et al. |
| 20080207307 | August 28, 2008 | Cunningham, II et al. |
| 20080209543 | August 28, 2008 | Aaron |
| 20080223918 | September 18, 2008 | Williams et al. |
| 20080285746 | November 20, 2008 | Landrock et al. |
| 20080308641 | December 18, 2008 | Finn |
| 20090037275 | February 5, 2009 | Pollio |
| 20090048026 | February 19, 2009 | French |
| 20090132417 | May 21, 2009 | Scipioni et al. |
| 20090143104 | June 4, 2009 | Loh et al. |
| 20090171682 | July 2, 2009 | Dixon et al. |
| 20090210308 | August 20, 2009 | Toomer et al. |
| 20090235339 | September 17, 2009 | Mennes et al. |
| 20090249077 | October 1, 2009 | Gargaro et al. |
| 20090282264 | November 12, 2009 | Ameil et al. |
| 20100023449 | January 28, 2010 | Skowronek et al. |
| 20100023455 | January 28, 2010 | Dispensa et al. |
| 20100029202 | February 4, 2010 | Jolivet et al. |
| 20100033310 | February 11, 2010 | Narendra et al. |
| 20100036769 | February 11, 2010 | Winters et al. |
| 20100078471 | April 1, 2010 | Lin et al. |
| 20100082486 | April 1, 2010 | Lee |
| 20100082491 | April 1, 2010 | Rosenblatt et al. |
| 20100094754 | April 15, 2010 | Bertran et al. |
| 20100095130 | April 15, 2010 | Bertran et al. |
| 20100100480 | April 22, 2010 | Altman et al. |
| 20100114731 | May 6, 2010 | Kingston et al. |
| 20100192230 | July 29, 2010 | Steeves et al. |
| 20100205091 | August 12, 2010 | Graziano |
| 20100207742 | August 19, 2010 | Buhot et al. |
| 20100211797 | August 19, 2010 | Westerveld et al. |
| 20100240413 | September 23, 2010 | He et al. |
| 20100257357 | October 7, 2010 | McClain |
| 20100312634 | December 9, 2010 | Cervenka |
| 20100312635 | December 9, 2010 | Cervenka |
| 20110028160 | February 3, 2011 | Roeding et al. |
| 20110035604 | February 10, 2011 | Habraken |
| 20110060631 | March 10, 2011 | Grossman et al. |
| 20110068170 | March 24, 2011 | Lehman |
| 20110084132 | April 14, 2011 | Tofighbakhsh |
| 20110101093 | May 5, 2011 | Ehrensvard |
| 20110113245 | May 12, 2011 | Varadarajan |
| 20110125638 | May 26, 2011 | Davis et al. |
| 20110131415 | June 2, 2011 | Schneider |
| 20110153437 | June 23, 2011 | Archer et al. |
| 20110153496 | June 23, 2011 | Royyuru |
| 20110155801 | June 30, 2011 | Rowberry |
| 20110208658 | August 25, 2011 | Makhotin |
| 20110208965 | August 25, 2011 | Machani |
| 20110211219 | September 1, 2011 | Bradley et al. |
| 20110218911 | September 8, 2011 | Spodak |
| 20110238564 | September 29, 2011 | Lim et al. |
| 20110246780 | October 6, 2011 | Yeap et al. |
| 20110258452 | October 20, 2011 | Coulier et al. |
| 20110280406 | November 17, 2011 | Ma et al. |
| 20110282785 | November 17, 2011 | Chin |
| 20110294418 | December 1, 2011 | Chen |
| 20110312271 | December 22, 2011 | Ma et al. |
| 20120024947 | February 2, 2012 | Naelon |
| 20120030047 | February 2, 2012 | Fuentes et al. |
| 20120030121 | February 2, 2012 | Grellier |
| 20120047071 | February 23, 2012 | Mullen et al. |
| 20120079281 | March 29, 2012 | Lowenstein et al. |
| 20120109735 | May 3, 2012 | Krawczewicz et al. |
| 20120109764 | May 3, 2012 | Martin et al. |
| 20120143703 | June 7, 2012 | Wall |
| 20120143754 | June 7, 2012 | Patel |
| 20120150737 | June 14, 2012 | Rottink et al. |
| 20120178366 | July 12, 2012 | Levy et al. |
| 20120196583 | August 2, 2012 | Kindo |
| 20120207305 | August 16, 2012 | Gallo et al. |
| 20120209773 | August 16, 2012 | Ranganathan |
| 20120238206 | September 20, 2012 | Singh et al. |
| 20120239560 | September 20, 2012 | Pourfallah et al. |
| 20120252350 | October 4, 2012 | Steinmetz et al. |
| 20120254394 | October 4, 2012 | Barras |
| 20120284194 | November 8, 2012 | Liu et al. |
| 20120290472 | November 15, 2012 | Mullen et al. |
| 20120296818 | November 22, 2012 | Nuzzi et al. |
| 20120316992 | December 13, 2012 | Oborne |
| 20120317035 | December 13, 2012 | Royyuru et al. |
| 20120317628 | December 13, 2012 | Yeager |
| 20130005245 | January 3, 2013 | Royston |
| 20130008956 | January 10, 2013 | Ashfield |
| 20130026229 | January 31, 2013 | Jarman et al. |
| 20130030997 | January 31, 2013 | Spodak |
| 20130048713 | February 28, 2013 | Pan |
| 20130054474 | February 28, 2013 | Yeager |
| 20130065564 | March 14, 2013 | Conner et al. |
| 20130080228 | March 28, 2013 | Fisher |
| 20130080229 | March 28, 2013 | Fisher |
| 20130099587 | April 25, 2013 | Lou et al. |
| 20130104251 | April 25, 2013 | Moore et al. |
| 20130106576 | May 2, 2013 | Hinman et al. |
| 20130119130 | May 16, 2013 | Braams |
| 20130130614 | May 23, 2013 | Busch-Sorensen |
| 20130138565 | May 30, 2013 | Dixon |
| 20130144793 | June 6, 2013 | Royston |
| 20130146657 | June 13, 2013 | Graef |
| 20130171929 | July 4, 2013 | Adams et al. |
| 20130179351 | July 11, 2013 | Wallner |
| 20130185772 | July 18, 2013 | Jaudon et al. |
| 20130191279 | July 25, 2013 | Calman et al. |
| 20130200999 | August 8, 2013 | Spodak et al. |
| 20130211937 | August 15, 2013 | Elbirt |
| 20130216108 | August 22, 2013 | Hwang et al. |
| 20130226791 | August 29, 2013 | Springer et al. |
| 20130226796 | August 29, 2013 | Jiang et al. |
| 20130232082 | September 5, 2013 | Krawczewicz et al. |
| 20130238894 | September 12, 2013 | Ferg et al. |
| 20130282360 | October 24, 2013 | Shimota et al. |
| 20130303085 | November 14, 2013 | Boucher et al. |
| 20130304651 | November 14, 2013 | Smith |
| 20130311363 | November 21, 2013 | Ramaci |
| 20130312082 | November 21, 2013 | Izu et al. |
| 20130314593 | November 28, 2013 | Reznik et al. |
| 20130344857 | December 26, 2013 | Berionne et al. |
| 20140002238 | January 2, 2014 | Taveau et al. |
| 20140019352 | January 16, 2014 | Shrivastava |
| 20140027506 | January 30, 2014 | Heo et al. |
| 20140032409 | January 30, 2014 | Rosano |
| 20140032410 | January 30, 2014 | Georgiev et al. |
| 20140040120 | February 6, 2014 | Cho et al. |
| 20140040139 | February 6, 2014 | Brudnicki et al. |
| 20140040147 | February 6, 2014 | Varadarakan et al. |
| 20140047235 | February 13, 2014 | Lessiak et al. |
| 20140058938 | February 27, 2014 | McClung, III |
| 20140067690 | March 6, 2014 | Pitroda et al. |
| 20140074637 | March 13, 2014 | Hammad |
| 20140074655 | March 13, 2014 | Lim et al. |
| 20140081720 | March 20, 2014 | Wu |
| 20140081785 | March 20, 2014 | Valadas Preto |
| 20140138435 | May 22, 2014 | Khalid |
| 20140171034 | June 19, 2014 | Aleksin et al. |
| 20140171039 | June 19, 2014 | Bjontegard |
| 20140172700 | June 19, 2014 | Teuwen et al. |
| 20140180851 | June 26, 2014 | Fisher |
| 20140208112 | July 24, 2014 | McDonald et al. |
| 20140214674 | July 31, 2014 | Narula |
| 20140229375 | August 14, 2014 | Zaytzsev et al. |
| 20140245391 | August 28, 2014 | Adenuga |
| 20140256251 | September 11, 2014 | Caceres et al. |
| 20140258099 | September 11, 2014 | Rosano |
| 20140258113 | September 11, 2014 | Gauthier et al. |
| 20140258125 | September 11, 2014 | Gerber et al. |
| 20140274179 | September 18, 2014 | Zhu et al. |
| 20140279479 | September 18, 2014 | Maniar et al. |
| 20140291395 | October 2, 2014 | Wankmueller |
| 20140337235 | November 13, 2014 | Van Heerden et al. |
| 20140339315 | November 20, 2014 | Ko |
| 20140346860 | November 27, 2014 | Aubry et al. |
| 20140365377 | December 11, 2014 | Salama |
| 20140365780 | December 11, 2014 | Movassaghi |
| 20140379361 | December 25, 2014 | Mahadkar et al. |
| 20150012444 | January 8, 2015 | Brown et al. |
| 20150032635 | January 29, 2015 | Guise |
| 20150071486 | March 12, 2015 | Rhoads et al. |
| 20150073983 | March 12, 2015 | Bartenstein |
| 20150088757 | March 26, 2015 | Zhou et al. |
| 20150089586 | March 26, 2015 | Ballesteros |
| 20150113271 | April 23, 2015 | Jooste |
| 20150134452 | May 14, 2015 | Williams |
| 20150134513 | May 14, 2015 | Olson |
| 20150140960 | May 21, 2015 | Powell et al. |
| 20150154595 | June 4, 2015 | Collinge et al. |
| 20150170138 | June 18, 2015 | Rao |
| 20150178724 | June 25, 2015 | Ngo et al. |
| 20150186871 | July 2, 2015 | Laracey |
| 20150199673 | July 16, 2015 | Savolainen |
| 20150199863 | July 16, 2015 | Scoggins |
| 20150205379 | July 23, 2015 | Mag et al. |
| 20150254637 | September 10, 2015 | Yang |
| 20150302409 | October 22, 2015 | Malek et al. |
| 20150317295 | November 5, 2015 | Sherry |
| 20150317626 | November 5, 2015 | Ran et al. |
| 20150332266 | November 19, 2015 | Friedlander et al. |
| 20150339474 | November 26, 2015 | Paz et al. |
| 20150371234 | December 24, 2015 | Huang et al. |
| 20160012465 | January 14, 2016 | Sharp |
| 20160026997 | January 28, 2016 | Tsui et al. |
| 20160048913 | February 18, 2016 | Rausaria et al. |
| 20160055480 | February 25, 2016 | Shah |
| 20160057619 | February 25, 2016 | Lopez |
| 20160065370 | March 3, 2016 | Le Saint et al. |
| 20160078430 | March 17, 2016 | Douglas |
| 20160087957 | March 24, 2016 | Shah et al. |
| 20160092696 | March 31, 2016 | Guglani et al. |
| 20160148177 | May 26, 2016 | Best |
| 20160148193 | May 26, 2016 | Kelley et al. |
| 20160189143 | June 30, 2016 | Koeppel |
| 20160232523 | August 11, 2016 | Venot et al. |
| 20160232527 | August 11, 2016 | Patterson |
| 20160239672 | August 18, 2016 | Khan et al. |
| 20160253651 | September 1, 2016 | Park et al. |
| 20160255072 | September 1, 2016 | Liu |
| 20160267486 | September 15, 2016 | Mitra et al. |
| 20160277383 | September 22, 2016 | Guyomarc'h et al. |
| 20160277388 | September 22, 2016 | Lowe et al. |
| 20160307187 | October 20, 2016 | Guo et al. |
| 20160307189 | October 20, 2016 | Zarakas et al. |
| 20160314472 | October 27, 2016 | Ashfield |
| 20160330027 | November 10, 2016 | Ebrahimi |
| 20160335531 | November 17, 2016 | Mullen et al. |
| 20160379217 | December 29, 2016 | Hammad |
| 20170004502 | January 5, 2017 | Quentin et al. |
| 20170011395 | January 12, 2017 | Pillai et al. |
| 20170011406 | January 12, 2017 | Tunnell et al. |
| 20170017957 | January 19, 2017 | Radu |
| 20170017964 | January 19, 2017 | Janefalkar et al. |
| 20170024716 | January 26, 2017 | Jiam et al. |
| 20170039566 | February 9, 2017 | Schipperheijn |
| 20170041759 | February 9, 2017 | Gantert et al. |
| 20170068950 | March 9, 2017 | Kwon |
| 20170103388 | April 13, 2017 | Pillai et al. |
| 20170104739 | April 13, 2017 | Lansler et al. |
| 20170109509 | April 20, 2017 | Baghdasaryan |
| 20170109730 | April 20, 2017 | Locke et al. |
| 20170116447 | April 27, 2017 | Cimino et al. |
| 20170124568 | May 4, 2017 | Moghadam |
| 20170140379 | May 18, 2017 | Deck |
| 20170154328 | June 1, 2017 | Zarakas et al. |
| 20170154333 | June 1, 2017 | Gleeson et al. |
| 20170180134 | June 22, 2017 | King |
| 20170230189 | August 10, 2017 | Toll et al. |
| 20170237301 | August 17, 2017 | Elad et al. |
| 20170289127 | October 5, 2017 | Hendrick |
| 20170295013 | October 12, 2017 | Claes |
| 20170316696 | November 2, 2017 | Bartel |
| 20170317834 | November 2, 2017 | Smith et al. |
| 20170330173 | November 16, 2017 | Woo et al. |
| 20170372275 | December 28, 2017 | Sigmund |
| 20170374070 | December 28, 2017 | Shah et al. |
| 20180034507 | February 1, 2018 | Wobak et al. |
| 20180039986 | February 8, 2018 | Essebag et al. |
| 20180039987 | February 8, 2018 | Molino |
| 20180068316 | March 8, 2018 | Essebag et al. |
| 20180129945 | May 10, 2018 | Saxena et al. |
| 20180160255 | June 7, 2018 | Park |
| 20180191501 | July 5, 2018 | Lindemann |
| 20180205712 | July 19, 2018 | Versteeg et al. |
| 20180240106 | August 23, 2018 | Garrett et al. |
| 20180254909 | September 6, 2018 | Hancock |
| 20180268132 | September 20, 2018 | Buer et al. |
| 20180270214 | September 20, 2018 | Caterino et al. |
| 20180294959 | October 11, 2018 | Traynor et al. |
| 20180300716 | October 18, 2018 | Carlson |
| 20180302396 | October 18, 2018 | Camenisch et al. |
| 20180315050 | November 1, 2018 | Hammad |
| 20180316666 | November 1, 2018 | Koved et al. |
| 20180322486 | November 8, 2018 | Deliwala et al. |
| 20180359100 | December 13, 2018 | Gaddam et al. |
| 20190014107 | January 10, 2019 | George |
| 20190019375 | January 17, 2019 | Foley |
| 20190036678 | January 31, 2019 | Ahmed |
| 20190172055 | June 6, 2019 | Hale |
| 20190238517 | August 1, 2019 | D'Agostino et al. |
| 20190303945 | October 3, 2019 | Mitra |
| 20210004806 | January 7, 2021 | Noe |
| 20210209582 | July 8, 2021 | Paliwal |
| 20210272098 | September 2, 2021 | Delsuc |
| 20210304189 | September 30, 2021 | Gupta |
| 20210383360 | December 9, 2021 | Sinha |
| 20210406869 | December 30, 2021 | Pathrabe |
| 20220114581 | April 14, 2022 | Upadhye |
| 20220207517 | June 30, 2022 | Wyatt |
| 20220284416 | September 8, 2022 | Rule |
| 20220309509 | September 29, 2022 | Akgun |
| 20220335412 | October 20, 2022 | Rule |
| 20220366410 | November 17, 2022 | Rule |
| 20220398566 | December 15, 2022 | Rule |
| 20220414648 | December 29, 2022 | Rule |
| 20230054157 | February 23, 2023 | Mao |
| 20230065163 | March 2, 2023 | Vargas |
| 20230083785 | March 16, 2023 | Maiman |
| 20230169505 | June 1, 2023 | Rule |
| 20230354020 | November 2, 2023 | Rule |
| 20230359839 | November 9, 2023 | Lovgren |
| 3010336 | July 2017 | CA |
| 101192295 | June 2008 | CN |
| 103023643 | April 2013 | CN |
| 103417202 | December 2013 | CN |
| 1085424 | March 2001 | EP |
| 1223565 | July 2002 | EP |
| 1265186 | December 2002 | EP |
| 1467330 | October 2004 | EP |
| 1783919 | May 2007 | EP |
| 2139196 | December 2009 | EP |
| 1469419 | August 2012 | EP |
| 2852070 | March 2015 | EP |
| 2457221 | August 2009 | GB |
| 2516861 | February 2015 | GB |
| 2551907 | January 2018 | GB |
| 101508320 | April 2015 | KR |
| 20150140132 | December 2015 | KR |
| WO-9858339 | December 1998 | WO |
| 9910824 | March 1999 | WO |
| 0049586 | August 2000 | WO |
| 2006070189 | July 2006 | WO |
| 2008055170 | May 2008 | WO |
| 2009025605 | February 2009 | WO |
| 2010049252 | May 2010 | WO |
| 2011112158 | September 2011 | WO |
| 2012001624 | January 2012 | WO |
| WO-2012170303 | December 2012 | WO |
| 2013039395 | March 2013 | WO |
| 2013155562 | October 2013 | WO |
| 2013192358 | December 2013 | WO |
| 2014043278 | March 2014 | WO |
| 2014170741 | October 2014 | WO |
| 2015179649 | November 2015 | WO |
| 2015183818 | December 2015 | WO |
| 2016097718 | June 2016 | WO |
| 2016160816 | October 2016 | WO |
| 2016168394 | October 2016 | WO |
| 2017042375 | March 2017 | WO |
| 2017042400 | March 2017 | WO |
| 2017047855 | March 2017 | WO |
| 2017157859 | September 2017 | WO |
| 2017208063 | December 2017 | WO |
| 2018063809 | April 2018 | WO |
| 2018137888 | August 2018 | WO |
| 2019022585 | January 2019 | WO |
| 2021051884 | March 2021 | WO |
| 2021133492 | July 2021 | WO |
| 2022108959 | May 2022 | WO |
| 2022187350 | September 2022 | WO |
| 2023017943 | February 2023 | WO |
| 2023064063 | April 2023 | WO |
- • Federal Financial Institutions Examination Council. “Retail Payment Systems.” (Apr. 2016). Retrieved online Jun. 6, 2025. https://afsaonline.org/wp-content/uploads/2021/07/Retail-Payment-Systems-IT-Booklet.pdf (Year: 2016).
- • European Payments Council. “White Paper Mobile Wallet Payments.” (Jan. 21, 2014). Retrieved online Jun. 6, 2025. https://www.europeanpaymentscouncil.eu/sites/default/files/KB/files/EPC163-13%20v2.0%20White%20Paper%20Mobile%20Wallet%20Payments.pdf (Year: 2014).
- • Visa. “Transaction Acceptance Device Guide (TADG).” (Nov. 2016). Retrieved online Jun. 6, 2025. https://www.visa.com.pe/dam/VCOM/regional/na/us/partner-with-us/documents/transaction-acceptance-device-guide-tadg.pdf (Year: 2016).
- The International Search Report and Written Opinion mailed Jul. 16, 2024, for corresponding PCT/US24/23689, eight (8) pages).
- Batina, L. and Poll, E., “SmartCards and RFID”, Course PowerPoint Presentation for IPA Security Course, Digital Security at University of Nijmegen, Netherlands (date unknown) 75 pages.
- Haykin, M. and Warnar, R., “Smart Card Technology: New Methods for Computer Access Control”, Computer Science and Technology NIST Special Publication 500-157:1-60 (1988).
- Lehpamer, H., “Component of the RFID System”, RFID Design Principles, 2nd edition pp. 133-201 (2012).
- Author Unknown, “CardrefresherSM from American Express®”, [online] 2019 [retrieved on Mar. 25, 2019]. Retrieved from Internet URL: https://merchant-channel.americanexpress.com/merchant/en_US/cardrefresher, 2 pages.
- Author Unknown, “Add Account Updater to your recurring payment tool”, [online] 2018-19 [retrieved on Mar. 25, 2019]. Retrieved from Internet URL: https://www.authorize.net/our-features/account-updater/, 5 pages.
- Author Unknown, “Visa® Account Updater for Merchants”, [online] 2019 [retrieved on Mar. 25, 2019]. Retrieved from Internet URL: https://usa.visa.com/dam/VCOM/download/merchants/visa-account-updater-product-information-fact-sheet-for-merchants.pdf, 2 pages.
- Author Unknown, “Manage the cards that you use with Apple Pay”, Apple Support [online] 2019 [retrieved on Mar. 25, 2019]. Retrieved from Internet URL: https://support.apple.com/en-us/HT205583, 5 pages.
- Author Unknown, “Contactless Specifications for Payment Systems”, EMV Book B—Entry Point Specification [online] 2016 [retrieved on Mar. 25, 2019]. Retrieved from Internet URL: https://www.emvco.com/wp-content/uploads/2017/05/BookB_Entry_Point_Specification_v2_6_20160809023257319.pdf, 52 pages.
- Author Unknown, “EMV Integrated Circuit Card Specifcations for Payment Systems, Book 2, Security and Key Management,” Version 3.4, [online] 2011 [retrieved on Mar. 25, 2019]. Retrieved from Internet URL: https://www.emvco.com/wp-content/uploads/2017/05/EMV_v4.3_Book_2_Security_and_Key_Management_20120607061923900.pdf, 174 pages.
- Author Unknown, “NFC Guide: All You Need to Know About Near Field Communication”, Square Guide [online] 2018 [retrieved on Nov. 13, 2018-11-13]. Retrieved from Internet URL: https://squareup.com/guides/nfc, 8 pages.
- Profis, S., “Everything you need to know about NFC and mobile payments” CNET Directory [online], 2014 [retrieved on Mar. 25, 2019]. Retrieved from the Internet URL: https://www.cnet.com/how-to/how-nfc-works-and-mobile-payments/, 6 pages.
- Cozma, N., “Copy data from other devices in Android 5.0 Lollipop setup”, CNET Directory [online] 2014 [retrieved on Mar. 25, 2019]. Retrieved from the Internet URL: https://www.cnet.com/how-to/copy-data-from-other-devices-in-android-5-0-lollipop-setup/, 5 pages.
- Kevin, Android Enthusiast, “How to copy text string from nfc tag”, StackExchange [online] 2013 [retrieved on Mar. 25, 2019]. Retrieved from the Internet URL: https://android.stackexchange.com/questions/55689/how-to-copy-text-string-from-nfc-tag, 11 pages.
- Author Unknown, “Tap & Go Device Setup”, Samsung [online] date unknown [retrieved on 2019-03-25]. Retrieved from the Internet URL: https://www.samsung.com/us/switch-me/switch-to-the-galaxy-s-5/app/partial/setup-device/tap-go.html, 1 page.
- Author Unknown, “Multiple encryption”, Wikipedia [online] 2019 [retrieved on Mar. 25, 2019]. Retrieved from Internet URL: https://en.wikipedia.org/wiki/Multiple_encryption, 4 pages.
- Krawczyk, et al., “HMAC: Keyed-Hashing for Message Authentication”, Network Working Group RFC:2104 memo [online] 1997 [retrieved on 2019-03-25]. Retrieved from Internet URL: https://tools.ietf.org/html/rfc2104, 12 pages.
- Song, et al., “ The AES-CMAC Algorithm”, Network Working Group RFC: 4493 memo [online] 2006 [retrieved on Mar. 25, 2019]. Retrieved from Internet URL: https://tools.ietf.org/html/rfc4493, 21 pages.
- Katz, J. and Lindell, Y., “Aggregate Message Authentication Codes”, Topics in Cryptology [online] 2008 [retrieved on Mar. 25, 2019]. Retrieved from Internet URL: https://www.cs.umd.edu/~jkatz/papers/aggregateMAC.pdf, 11 pages.
- Adams, D., and Maier, A-K., “Goldbug Big Seven open source crypto-messengers to be compared—or: Comprehensive Confidentiality Review & Audit of GoldBug Encrypting E-Mail-Client & Secure Instant Messenger”, Big Seven Study 2016 [online] [retrieved on Mar. 25, 2018]. Retrieved from Internet URL: https://sf.net/projects/goldbug/files/bigseven-crypto-audit.pdf, 309 pages.
- Author Unknown, “Triple DES”, Wikipedia [online] 2018 [retrieved on Mar. 25, 2019]. Retrieved from Internet URL: https://simple.wikipedia.org/wiki/Triple_DES, 2 pages.
- Song F., and Yun, A.I., “Quantum Security of NMAC and Related Constructions—PRF domain extension against quantum attacks”, IACR Cryptology ePrint Archive [online] 2017 [retrieved on Mar. 25, 2019]. Retrieved from Internet URL: https://eprint.iacr.org/2017/509.pdf, 41 pages.
- Saxena, N., “Lecture 10: NMAC, HMAC and Number Theory”, CS 6903 Modern Cryptography [online] 2008 [retrieved on Mar. 25, 2019]. Retrieved from Internet URL: http://isis.poly.edu/courses/cs6903/Lectures/lecture10.pdf, 8 pages.
- Berg, G., “Fundamentals of EMV”, Smart Card Alliance [online] date unknown [retrieved on Mar. 27, 2019]. Retrieveed from Internet URL: https://www.securetechalliance.org/resources/media/scap13_preconference/02.pdf, 37 pages.
- Pierce, K., “Is the amazon echo nfc compatible?”, Amazon.com Customer Q&A [online] 2016 [retrieved on Mar. 26, 2019]. Retrieved from Internet URL: https://www.amazon.com/ask/questions/Tx1RJXYSPE6XLJD?_encodi . . . , 2 pages.
- Author Unknown, “Multi-Factor Authentication”, idaptive [online] 2019 [retrieved on Mar. 25, 2019]. Retrieved from Internet URL: https://www.centrify.com/products/application-services/adaptive-multi-factor-authentication/risk-based-mfa/, 10 pages.
- Author Unknown, “Adaptive Authentication”, SecureAuth [online] 2019 [retrieved on Mar. 25, 2019}. Retrieved from Internet URL: https://www.secureauth.com/products/access-management/adaptive-authentication, 7 pages.
- Van den Breekel, J., et al., “EMV in a nutshell”, Technical Report, 2016 [retrieved on Mar. 25, 2019]. Retrieved from Internet URL: https://www.cs.ru.nl/E.Poll/papers/EMVtechreport.pdf, 37 pages.
- Author Unknown, “Autofill”, Computer Hope [online] 2018 [retrieved on Mar. 25, 2019]. Retrieved from Internet URL: https://www.computerhope.com/jargon/a/autofill.htm, 2 pages.
- Author Unknown, “Fill out forms automatically”, Google Chrome Help [online] 2019 [retrieved on Mar. 25, 2019]. Retrieved from Internet URL: https://support.google.com/chrome/answer/142893?co=GENIE.Platform%3DDesktop&hl=en, 3 pages.
- Author Unknown, “Autofill credit cards, contacts, and passwords in Safari on Mac”, Apple Safari User Guide [online] 2019 [retrieved on Mar. 25, 2019]. Retrieved from Internet URL: https://support.apple.com/guide/safari/use-autofill-ibrw1103/mac, 3 pages.
- Menghin, M.J., “Power Optimization Techniques for Near Field Communication Systems”, 2014 Dissertation at Technical University of Graz [online]. Retrieved from Internet URL: https://diglib.tugraz.at/download.php?id=576a7b910d2d6&location=browse, 135 pages.
- Mareli, M., et al., “Experimental evaluation of NFC reliability between an RFID tag and a smartphone”, Conference paper (2013) IEEE AFRICON At Mauritius [online] [retrieved on Mar. 25, 2019]. Retrieved from Internet URL: https://core.ac.uk/download/pdf/54204839.pdf, 5 pages.
- Davison, A., et al., “MonoSLAM: Real-Time Single Camera SLAM”, IEEE Transactions on Pattern Analysis and Machine Intelligence 29(6): 1052-1067 (2007).
- Barba, R., “Sharing your location with your bank sounds creepy, but it's also useful”, Bankrate, LLC [online] 2017 [retrieved on Mar. 25, 2019]. Retrieved from Internet URL: https://www.bankrate.com/banking/banking-app-location-sharing/, 6 pages.
- Author Unknown: “onetappayment™”, [online] Jan. 24, 2019, [retrieved on Mar. 25, 2019]. Retrieved from Internet URL: https://www.payubiz.in/onetap, 4 pages.
- Vu, et al., “Distinguishing users with capacitive touch communication”, Proceedings of the Annual International Conference on Mobile Computing and Networking, 2012, MOBICOM. 10.1145/2348543.2348569.
- Pourghomi, P., et al., “A Proposed NFC Payment Application,” International Journal of Advanced Computer Science and Applications, 4(8):173-181 (2013).
- Author unknown, “EMV Card Personalization Specification”, EMVCo., LLC., specification version 1.0, (2003) 81 pages.
- Ullmann et al., “On-Card” User Authentication for Contactless Smart Cards based on Gesture Recognition, paper presentation LNI proceedings, (2012) 12 pages.
- Faraj, S.T., et al., “Investigation of Java Smart Card Technology for Multi-Task Applications”, J of Al-Anbar University for Pure Science, 2(1):23 pages (2008).
- Dhamdhere, P., “Key Benefits of a Unified Platform for Loyalty, Referral Marketing, and UGC” Annex Cloud [online] May 19, 2017 [retrieved on Mar. 27, 2019]. Retrieved from Internet URL: https://www.annexcloude.com/blog/benefits-unified-platform/, 13 pages.
- Author Unknown, “Global expansion of card tapping mobile OTP for security and convenience is imminent,” Jun. 28, 2022, website: https://www.swidch.com/blogs/card-tapping-motp-blog.
- Emvco: “EMV Card Personalisation Specification”, Aug. 1, 2021, pp. 1-114, Retrieved from the Internet: URL: https://www.emvco.com/specification/?post_id=12467.
- Saush, “Getting information from an EMV chip card with Java,” Sep. 8, 2006, WordPress, pp. 1-13.
- Smart Card Alliance, “Co-Branded Multi-Application Contactless Cards for Transit and Financial Payment,” A Smart Card Alliance Transportation Council White Paper (40 pages), Mar. 2008.
Type: Grant
Filed: Apr 19, 2023
Date of Patent: Oct 13, 2026
Patent Publication Number: 20240354741
Assignee: Capital One Services, LLC (McLean, VA)
Inventors: Kaush Kumar (Vienna, VA), Jeffrey Rule (Chevy Chase, MD), Jinlian Wang (Falls Church, VA)
Primary Examiner: James A Reagan
Application Number: 18/136,497
International Classification: G06Q 20/34 (20120101); G06Q 20/40 (20120101);
