Patent Description:
Some web-based platforms host web pages for different entities. However, the functionality provided by a given web page may be limited relative to the functionality provided by a dedicated application store application for a given entity. For example, the web page may not be able to securely process customer data and/or requests. This problem is often exacerbated when mobile web browsers are used to access the web pages, as mobile web browsers may have limited functionality compared to other types of web browsers. Therefore, security and other risks may exist using services provided by web-based platforms. <CIT>describes a technique for autofilling card data from a contactless card to a form of a computing device.

Embodiments disclosed herein provide systems, methods, articles of manufacture, and computer-readable media for using on-demand applications to extend web services. In one example, a web browser of a device may receive selection of a uniform resource locator (URL). An operating system may download an application from an application server based on the URL. The application may identify a plurality of applications installed on the device and select a first institution corresponding to a first application. The application may receive a cryptogram from a contactless card associated with the first institution and transmit the cryptogram to an authentication server. The application may receive an authentication result specifying the authentication server decrypted the cryptogram. The web browser may receive, based on the decryption of the cryptogram, an account number, an expiration date associated with the account number, and a card verification value (CVV) associated with the account number. The web browser may provide the account number, expiration date, and CVV to a server associated with the application.

Embodiments disclosed herein provide techniques for extending web services using on-demand applications. Generally, the web services may include a plurality of web pages hosted by an ecommerce platform. Each web page may be associated with a respective merchant, of a plurality of merchants, that have a presence on the ecommerce platform. When a user accesses one of the web pages using a web browser on a device, the user may select one or more items for purchase. To improve the security of the checkout process, embodiments disclosed herein may present, in the web page, a uniform resource locator (URL) that is directed to an application hosted by an application server. The URL may include one or more additional parameters, such as a merchant identifier (e.g., a merchant identifier associated with the web page), a cart identifier for the transaction, and/or any other data element. The application may be an on-demand application associated with the ecommerce platform that processes payment for the purchase. Responsive to selection of the URL, the web browser and/or an operating system (OS) of the device may access the URL. Doing so may cause the on-demand application to be downloaded and executed on the device.

The on-demand application may then identify one or more applications installed on the device. The applications may include one or more financial institution applications. The on-demand application may then select a first financial institution application from the one or more applications. A user may provide their email address as input to the on-demand application. The on-demand application may then transmit the email address to a server of a financial institution associated with the first financial institution application. The server may use the email address to identify a phone number associated with an account in an account database. The server may then transmit a one-time passcode (OTP) to the identified phone number. Once received, the user may provide the OTP to the on-demand application. The on-demand application may compare the OTP provided by a user to an instance of the OTP received from the server.

If the comparison results in a match, the on-demand application may instruct the user to tap a contactless card to the device. In response, the user may tap the contactless card to the device, and the on-demand application may operate a card reader of the device. Doing so may cause or instruct the contactless card to generate a cryptogram, which may be included as part of a data package, such as an NFC Forum Data Exchange Format (NDEF) file. The on-demand application may read the data package via NFC and transmit the data package to the server for decryption. In some embodiments, the on-demand application may transmit additional metadata, such as the cart identifier, merchant identifier, etc., with the data package. The server may attempt to decrypt the cryptogram using the received data package.

If the server decrypts the cryptogram, the server may send a response to the on-demand application. The response may include an indication that the cryptogram was decrypted or otherwise authenticated. Furthermore, if the server decrypts the cryptogram, the server may generate payment information for the purchase in the web browser. The payment information may include a virtual account number (VAN), expiration date, card verification value (CVV) and any other information such as the user's address, etc. The server may provide the payment information to the web server. The web server may then push the payment information to the web browser, which may then fill the payment information into one or more form fields in the web browser. The web browser may then be used to submit the payment for the purchase using the payment information.

In some embodiments, a cookie may be stored on the device, e.g., by the on-demand application responsive to the decryption of the cryptogram by the server, and/or by the web browser responsive to receiving the payment information. The cookie may be used to authenticate the user for subsequent transactions. For example, if the user attempts to make a second purchase, the user may again select the URL to use the on-demand application. The on-demand application may be downloaded (if not available on the device) and executed. The on-demand application may identify the cookie stored on the device. The on-demand application may identify the first financial institution based on the cookie, and instruct the server associated with the first financial institution to generate another VAN, expiration date, and CVV. Advantageously, based on the identification of the cookie, the user is not required to tap the card to the device to facilitate decryption of another cryptogram by the server. The another VAN, expiration date, and CVV may then be used to complete the second purchase.

Advantageously, embodiments disclosed herein provide techniques to extend web services using on-demand applications. Because an ecommerce platform may host web sites provided by thousands (or more) of merchants, the ecommerce platform cannot reasonably provide a dedicated application to each merchant. However, by leveraging an on-demand application, the ecommerce platform may extend the functionality provided by web pages. Doing so may include expedited payment processing by using payment information that is automatically downloaded and inserted into one or more payment forms. By leveraging cryptograms generated by contactless cards, embodiments of the disclosure may securely verify the identity of the user with minimal risk of fraudulent activity. Furthermore, by using a web browser, a dedicated client application is not required to engage in data communications with the contactless card. Using a web browser may advantageously scale the functionality described herein to different entities and any number of users without requiring a dedicated application. Furthermore, by providing a simplified payment process, more transactions may be processed by the server, thereby improving system performance.

With general reference to notations and nomenclature used herein, one or more portions of the detailed description which follows may be presented in terms of program procedures executed on a computer or network of computers. These procedural descriptions and representations are used by those skilled in the art to most effectively convey the substances of their work to others skilled in the art. A procedure is here, and generally, conceived to be a self-consistent sequence of operations leading to a desired result. These operations are those requiring physical manipulations of physical quantities. Usually, though not necessarily, these quantities take the form of electrical, magnetic, or optical signals capable of being stored, transferred, combined, compared, and otherwise manipulated. It proves convenient at times, principally for reasons of common usage, to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, or the like. It should be noted, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to those quantities.

Further, these manipulations are often referred to in terms, such as adding or comparing, which are commonly associated with mental operations performed by a human operator. However, no such capability of a human operator is necessary, or desirable in most cases, in any of the operations described herein that form part of one or more embodiments. Rather, these operations are machine operations. Useful machines for performing operations of various embodiments include digital computers as selectively activated or configured by a computer program stored within that is written in accordance with the teachings herein, and/or include apparatus specially constructed for the required purpose or a digital computer. Various embodiments also relate to apparatus or systems for performing these operations. These apparatuses may be specially constructed for the required purpose. The required structure for a variety of these machines will be apparent from the description given.

Reference is now made to the drawings, wherein like reference numerals are used to refer to like elements throughout. In the following description, for the purpose of explanation, numerous specific details are set forth in order to provide a thorough understanding thereof. It may be evident, however, that the novel embodiments can be practiced without these specific details. The intention is to cover all modification, equivalents, and alternatives within the scope of the claims.

<FIG> depicts an exemplary system <NUM>, consistent with disclosed embodiments. Although the system <NUM> shown in <FIG> has a limited number of elements in a certain topology, it may be appreciated that the system <NUM> may include more or less elements in alternate topologies as desired for a given implementation.

As shown, the system <NUM> comprises one or more contactless cards <NUM>, one or more computing devices <NUM>, one or more financial institution servers <NUM>, one or more payment processor servers <NUM>, one or more ecommerce servers <NUM>, and one or more application servers <NUM>. The contactless card <NUM> is representative of any type of payment card, such as a credit card, debit card, ATM card, gift card, and the like. The contactless card <NUM> may comprise one or more communications interfaces <NUM>, such as a radio frequency identification (RFID) chip, configured to communicate with a communications interface <NUM> (also referred to herein as a "card reader", a "wireless card reader", and/or a "wireless communications interface") of the computing devices <NUM> via NFC, the EMV standard, or other short-range protocols in wireless communication. Although NFC is used as an example communications protocol herein, the disclosure is equally applicable to other types of wireless communications, such as the EMV standard, Bluetooth, and/or Wi-Fi.

The computing device <NUM> is representative of any number and type of computing device, such as smartphones, tablet computers, wearable devices, laptops, portable gaming devices, virtualized computing system, merchant terminals, point-of-sale systems, servers, desktop computers, and the like. The servers <NUM>, <NUM>, <NUM>, and <NUM> are representative of any number and type of computing devices, such as a server, workstation, compute cluster, cloud computing platform, virtualized computing system, and the like. Although not depicted for the sake of clarity, the computing device <NUM>, contactless card <NUM>, and servers <NUM>, <NUM>, <NUM>, and <NUM> each include one or more processor circuits to execute programs, code, and/or instructions.

As shown, a memory <NUM> of the contactless card <NUM> includes an applet <NUM>, a counter <NUM>, a master key <NUM>, a diversified key <NUM>, and a unique customer identifier (ID) <NUM>. The applet <NUM> is executable code configured to perform the operations described herein. The counter <NUM>, master key <NUM>, diversified key <NUM>, and customer ID <NUM> are used to provide security in the system <NUM> as described in greater detail below.

As shown, a memory <NUM> of the mobile device <NUM> includes an instance of an operating system (OS) <NUM>. Example operating systems <NUM> include the Android® OS, iOS®, macOS®, Linux®, and Windows® operating systems. As shown, the OS <NUM> includes a web browser <NUM> and one or more applications <NUM>. The web browser <NUM> is an application that allows the device <NUM> to access information via the network <NUM> (e.g., via the Internet). The applications <NUM> are representative of any type of application, including applications associated with one or more financial institutions and/or financial institution servers <NUM>.

As shown, a memory <NUM> of the server <NUM> includes an authentication application <NUM>. A given server <NUM> and/or authentication application <NUM> may be associated with a financial institution issuing a contactless card <NUM>, e.g., a bank. Therefore, a plurality of different servers <NUM> and/or authentication applications <NUM> may exist in the system <NUM>. As described in greater detail herein, the authentication application <NUM> is configured to facilitate generation of payment information for one or more contactless cards <NUM> via the web browser <NUM> and an on-demand application <NUM> without requiring the device <NUM> to include a dedicated application to read data from the contactless cards <NUM> and/or communicate with the financial institution servers <NUM>. Furthermore, doing so allows the web browser <NUM> and/or web page <NUM> to process transactions without a given web page <NUM> including functionality to read data from the contactless cards <NUM> and/or communicate with the financial institution servers <NUM>.

Generally, a user may use the web browser <NUM> to browse one or more web pages <NUM> on the ecommerce servers <NUM>. The web pages <NUM> may include hypertext markup language (HTML) pages, JavaScript® pages, and/or any other type of page that can be rendered by a web browser <NUM>. The ecommerce servers <NUM> may generally provide a platform for distinct merchants, or sellers, to sell goods, services, items, and the like. Therefore, each merchant is associated with at least one web page <NUM>.

Generally, while browsing, the user may select one or more items and/or services for purchase from one or more merchants having a presence on the ecommerce platform <NUM>. When the user has selected the desired items and/or services, the user may encounter an interface in a web page <NUM>-<NUM> for completing the transaction (e.g., a cart page, a checkout page, etc.) in the web browser <NUM>. Conventionally, the user is required to manually enter their name, card number, expiration date, CVV, and/or address information into forms of web page <NUM>-<NUM> in the web browser <NUM> to complete the purchase. Furthermore, while the device <NUM> is capable of reading this information from the contactless card <NUM> via the communications interface <NUM>, the web browser <NUM> and/or the web page <NUM>-<NUM> may not support such functionality. For example, the web browser <NUM> and/or the web page <NUM>-<NUM> may not be able to control the communications interface <NUM>. Similarly, the web browser <NUM> and/or the web page <NUM>-<NUM> may not be able to communicate with the authentication applications <NUM> to leverage required security features.

Advantageously, however, the web page <NUM>-<NUM> may include a URL <NUM> that is configured to initiate secure payment processing for the transaction. Generally, the URL <NUM> may be directed to one of the on-demand applications <NUM> on the application servers <NUM>. In some embodiments, the URL <NUM> may specify one or more parameters. For example, the parameters may include a merchant identifier, a transaction (or shopping cart) identifier, an identifier of the application <NUM>, and the like. One example of a URL <NUM> is "http://www. com/app123?merchantid=abc&cartid=<NUM>", where "app123" identifies an application <NUM>, "merchantid=abc" identifies a merchant, and "cartid=<NUM>" identifies a transaction and/or shopping cart. The merchant identifier may be a unique identifier associated with a merchant and/or a web page <NUM> associated with the merchant that has a presence in the ecommerce servers <NUM>. For example, the ecommerce server <NUM> may host web pages <NUM> for example entities A, B, and C. In such an example, each entity A, B, and C is associated with a respective unique identifier. The transaction identifier uniquely identifies a given transaction (e.g., the items selected for purchase, a shopping cart, etc.) and is associated with an account on the ecommerce server <NUM>. For example, the transaction identifier may be a unique alphanumeric identifier, a unique session alphanumeric identifier, a file, etc..

<FIG> depicts an embodiment where the user has selected the URL <NUM> in the web browser to complete the transaction using the contactless card <NUM> without manually entering payment information in the web browser <NUM> and/or the web page <NUM>-<NUM>. Responsive to the selection of the URL <NUM>, the OS <NUM> may dynamically download an on-demand application <NUM>-<NUM>, and dynamically install the on-demand application <NUM>-<NUM> on the device. The URL <NUM> may further be a universal link URL (or deep link URL) that opens a resource (e.g., one or more specific pages of the associated on-demand applications <NUM>). The pages of the on-demand applications <NUM> that should be opened upon execution on the mobile device <NUM> may be specified as parameters of the URL <NUM>. Similarly, the merchant identifier and/or transaction identifier may be provided to the on-demand application <NUM> via parameters of the URL <NUM>.

The on-demand applications <NUM> are non-persistent applications that may be dynamically downloaded and executed on the mobile device <NUM>. Examples of on-demand applications <NUM> include Android® instant applications, Apple® App Clips, and progressive web applications. More generally, the on-demand applications <NUM> include a subset of functionality provided by an application <NUM> associated with the financial institution servers. For example, an on-demand application <NUM> may include functionality to read data from a contactless card <NUM> and transmit the data to an authentication application <NUM> on a financial institution server <NUM> for verification. However, the on-demand application <NUM> may omit other functionality provided by a complete application <NUM> provided by the financial institution (e.g., viewing account balances, transferring funds, etc.). In some embodiments, a given on-demand application <NUM> may be associated with a distinct ecommerce platform and/or server <NUM> of a plurality of ecommerce platforms and/or servers <NUM>.

In the embodiment depicted in <FIG>, the on-demand application <NUM>-<NUM> may identify one or more of the applications <NUM> installed on the device. Doing so may allow the on-demand application <NUM>-<NUM> to determine the issuer of the contactless card <NUM>. Generally, the on-demand application <NUM>-<NUM> may search for applications <NUM> associated with a financial institution and/or financial institution server <NUM>. If one application <NUM> is identified, the on-demand application <NUM>-<NUM> may select the financial institution server <NUM> associated with the application. The association may be defined in a table or other data structure of the on-demand application <NUM>-<NUM>. In embodiments where no applications <NUM> are identified, the on-demand application <NUM>-<NUM> may include a list of financial institutions (e.g., ranked based on popularity among all users), and iteratively select each financial institution (and/or associated server <NUM>) in ranked order until the correct financial institution associated with the contactless card <NUM> is identified.

In embodiments where the on-demand application <NUM>-<NUM> identifies more than one financial institution application <NUM> installed on the device <NUM>, the on-demand application <NUM>-<NUM> may select one of the financial institution applications <NUM> and the associated financial institution server <NUM>. The on-demand application <NUM>-<NUM> may use any rules and/or selection logic to select one of the applications <NUM>. For example, the on-demand application <NUM>-<NUM> may select the most recently used application <NUM>, the most frequently accessed application <NUM>, and the like. In some embodiments, the on-demand application <NUM>-<NUM> computes a score for each application <NUM>, e.g., based on most recently used, most frequently used, etc. The on-demand application <NUM>-<NUM> may then select the application <NUM> with the highest score.

Once the on-demand application <NUM>-<NUM> selects a financial institution application <NUM> and/or a financial institution server <NUM>, the on-demand application <NUM>-<NUM> may search for a cookie on the device <NUM>. If a cookie is not found, the on-demand application <NUM>-<NUM> may instruct the user to enter their email address (or some other identifier) as part of a one-time passcode (OTP) registration flow. Once provided, the on-demand application <NUM>-<NUM> may transmit the email address (and/or a hash of the email address) to the selected financial institution server <NUM>. In response, the authentication application <NUM> may identify a phone number associated with the email address in the account data <NUM>.

The authentication application <NUM> may then generate an OTP and send the OTP to the device <NUM> using the identified phone number. The OTP may be any alphanumeric string. The user may then provide the OTP as input to the on-demand application <NUM>-<NUM>. The on-demand application <NUM>-<NUM> may then transmit the received input to the authentication application <NUM>, which compares the input to the generated OTP. The authentication application <NUM> may return a result of a comparison to the on-demand application <NUM>-<NUM>. In some embodiments, however, the authentication application <NUM> provides the generated OTP to the on-demand application <NUM>-<NUM>, which performs the comparison. Regardless of the entity performing the comparison, if the comparison results in a match, the user may be enrolled in automatic payments using the contactless card <NUM> on the ecommerce platform. In some embodiments, the on-demand application <NUM>-<NUM> may store a cookie (not pictured) responsive to the comparison resulting in the match and enrolling the user in automatic payments. If the comparison does not result in a match, the process stops and the user's request to checkout using automatic payments via the contactless card <NUM> is restricted.

<FIG> depicts an embodiment where the OTP provided by the user matches the OTP generated by the authentication application <NUM> and the on-demand application <NUM>-<NUM>. In response to determining the match and/or receiving an indication of the match from the authentication application <NUM>, the on-demand application <NUM>-<NUM> instructs the user to tap the contactless card <NUM> to the device <NUM>. The user may tap the contactless card <NUM> to the device <NUM> (or otherwise bring the contactless card <NUM> within communications range of the card reader <NUM> of the device <NUM>). Generally, once the contactless card <NUM> is brought within communications range of the communications interface <NUM> of the device <NUM>, the on-demand application <NUM>-<NUM> instructs the applet <NUM> of the contactless card <NUM> to generate a cryptogram <NUM>. The cryptogram <NUM> may be based on the customer ID <NUM> of the contactless card <NUM>. The cryptogram <NUM> may be generated based on any suitable cryptographic technique. In some embodiments, the applet <NUM> may include the cryptogram and an unencrypted customer ID <NUM> (and/or any other unique identifier) in a data package. In at least one embodiment, the data package including the cryptogram <NUM> and unencrypted customer ID <NUM> is an NDEF file.

As stated, the system <NUM> is configured to implement key diversification to secure data, which may be referred to as a key diversification technique herein. Generally, the server <NUM> (or another computing device) and the contactless card <NUM> may be provisioned with the same master key <NUM> (also referred to as a master symmetric key). More specifically, each contactless card <NUM> is programmed with a distinct master key <NUM> that has a corresponding pair in the server <NUM> associated with the financial institution issuing the contactless card <NUM>. For example, when a contactless card <NUM> is manufactured, a unique master key <NUM> may be programmed into the memory <NUM> of the contactless card <NUM>. Similarly, the unique master key <NUM> may be stored in a record of a customer associated with the contactless card <NUM> in the account data <NUM> of the server <NUM> (and/or stored in a different secure location, such as the hardware security module (HSM) <NUM>). The master key <NUM> may be kept secret from all parties other than the contactless card <NUM> and server <NUM>, thereby enhancing security of the system <NUM>. In some embodiments, the applet <NUM> of the contactless card <NUM> may encrypt and/or decrypt data (e.g., the customer ID <NUM>) using the master key <NUM> and the data as input a cryptographic algorithm. For example, encrypting the customer ID <NUM> with the master key <NUM> may result in the cryptogram <NUM>. Similarly, the server <NUM> may encrypt and/or decrypt data associated with the contactless card <NUM> using the corresponding master key <NUM>.

In other embodiments, the master keys <NUM> of the contactless card <NUM> and server <NUM> may be used in conjunction with the counters <NUM> to enhance security using key diversification. The counters <NUM> comprise values that are synchronized between the contactless card <NUM> and server <NUM>. The counter value <NUM> may comprise a number that changes each time data is exchanged between the contactless card <NUM> and the server <NUM> (and/or the contactless card <NUM> and the device <NUM>). When preparing to send data (e.g., to the server <NUM> and/or the device <NUM>), the applet <NUM> of the contactless card <NUM> may increment the counter value <NUM>. The applet <NUM> of the contactless card <NUM> may then provide the master key <NUM> and counter value <NUM> as input to a cryptographic algorithm, which produces a diversified key <NUM> as output. The cryptographic algorithm may include encryption algorithms, hash-based message authentication code (HMAC) algorithms, cipher-based message authentication code (CMAC) algorithms, and the like. Non-limiting examples of the cryptographic algorithm may include a symmetric encryption algorithm such as 3DES or AES107; a symmetric HMAC algorithm, such as HMAC-SHA-<NUM>; and a symmetric CMAC algorithm such as AES-CMAC. Examples of key diversification techniques are described in greater detail in <CIT>.

Continuing with the key diversification example, the contactless card <NUM> may then encrypt the data (e.g., the customer ID <NUM> and/or any other data) using the diversified key <NUM> and the data as input to the cryptographic algorithm. For example, encrypting the customer ID <NUM> with the diversified key <NUM> may result in the encrypted customer ID (e.g., the cryptogram <NUM>). As stated, the cryptogram <NUM> may be included in a data package, such as an NDEF file. The on-demand application <NUM>-<NUM> may then read the data package including the cryptogram <NUM> via the communications interface <NUM>.

Regardless of the encryption technique used, the on-demand application <NUM>-<NUM> may then transmit the cryptogram <NUM> to the server <NUM> via the network <NUM>. In some embodiments, the on-demand application <NUM>-<NUM> further provides the merchant identifier, transaction identifier, and any other element to the server <NUM>. For example, the merchant identifier, transaction identifier, and other data elements specified in the URL <NUM> may be provided as input to the on-demand application <NUM>-<NUM>.

The on-demand application <NUM>-<NUM> may further indicate, to the server <NUM>, that the cryptogram <NUM> was read from the contactless card <NUM> via the card reader <NUM> of the device <NUM>. Once received, the authentication application <NUM> may attempt to authenticate the cryptogram <NUM>. For example, the authentication application <NUM> may attempt to decrypt the cryptogram <NUM> using a copy of the master key <NUM> stored by the server <NUM>. In some embodiments, the authentication application <NUM> may identify the master key <NUM> and counter value <NUM> using the unencrypted customer ID <NUM> included in the data package. In some examples, the authentication application <NUM> may provide the master key <NUM> and counter value <NUM> as input to the cryptographic algorithm, which produces a diversified key <NUM> as output. The resulting diversified key <NUM> may correspond to the diversified key <NUM> of the contactless card <NUM>, which may be used to decrypt the cryptogram <NUM>.

Regardless of the decryption technique used, the authentication application <NUM> may successfully decrypt the cryptogram <NUM>, thereby verifying or authenticating the cryptogram <NUM> (e.g., by comparing the customer ID <NUM> that is produced by decrypting the cryptogram to a known customer ID stored in the account data <NUM>, and/or based on an indication that the decryption using the key <NUM> and/or <NUM> was successful). Although the keys <NUM>, <NUM> are depicted as being stored in the memory <NUM>, the keys <NUM>, <NUM> may be stored elsewhere, such as in a secure element and/or the HSM <NUM>. In such embodiments, the secure element and/or the HSM <NUM> may decrypt the cryptogram using the keys <NUM> and/or <NUM> and a cryptographic function. Similarly, the secure element and/or HSM <NUM> may generate the diversified key <NUM> based on the master key <NUM> and counter value <NUM> as described above. If the decryption is successful, the authentication application <NUM> may cause payment information to be generated and/or transmitted for the transaction. In some embodiments, the authentication application <NUM> may transmit a decryption result (also referred to as an "authentication result" or a "verification result") to the web browser <NUM> and/or the on-demand application <NUM>-<NUM> indicating whether the decryption was successful or unsuccessful.

If, however, the authentication application <NUM> is unable to decrypt the cryptogram <NUM> to yield the expected result (e.g., the customer ID <NUM> of the account associated with the contactless card <NUM>), the authentication application <NUM> does not validate the cryptogram <NUM>. In such an example, the authentication application <NUM> determines to refrain from generating payment information or otherwise providing payment information for the transaction. The authentication application <NUM> may transmit an indication of the failed decryption to the web browser <NUM> and/or the on-demand application <NUM>-<NUM>. The web page <NUM>-<NUM> and/or the on-demand application <NUM>-<NUM> may then display an indication of the failed decryption, and therefore failed automatic payment, to the user.

<FIG> illustrates an embodiment where the authentication application <NUM> successfully decrypted the cryptogram <NUM>, thereby verifying (or authenticating) the cryptogram <NUM>. In response, the authentication application <NUM> transmit a decryption result <NUM> that indicates that the authentication application <NUM> successfully decrypted the cryptogram <NUM> and that payment information <NUM> has been generated and/or transmitted for the requested purchase. The payment information <NUM> may include an account number (e.g., a primary account number (PAN)), expiration date, and CVV of the contactless card <NUM>. In some embodiments, the payment information <NUM> further includes the user's name, billing address, and/or shipping address. In some embodiments, the account number is a one-time use virtual account number (VAN).

As shown, the server <NUM> may transmit the payment information <NUM> directly to the device <NUM>, e.g., as a push notification, SMS message, etc. In such embodiments, the OS <NUM> may copy one or more elements of the information <NUM> to a clipboard (not pictured), where the clipboard may be used to paste the information <NUM> into one or more form fields in the web page <NUM>-<NUM>. Additionally and/or alternatively, the OS <NUM> may provide the payment information <NUM> to an autofill service (not pictured) that automatically fills the payment information <NUM> in the form fields of the web page <NUM>-<NUM>. The user may have the opportunity to review and approve the purchase using the received payment information <NUM>. In some embodiments, however, the purchase is automatically processed in the web page <NUM>-<NUM> without requiring further user input. In some embodiments, described in greater detail elsewhere, the server <NUM> transmits the payment information <NUM> to the on-demand application <NUM>-<NUM>, and the purchase is completed using the on-demand application <NUM>-<NUM>.

Additionally and/or alternatively, as shown, the server <NUM> may transmit the payment information <NUM> to the ecommerce server <NUM>. In such embodiments, the server <NUM> may transmit the merchant identifier and/or transaction identifier to the ecommerce server <NUM>. Doing so allows the ecommerce server <NUM> to identify a session with the web browser <NUM>. The ecommerce server <NUM> may then automatically fill the payment information <NUM> in to the one or more form fields in the web page <NUM>-<NUM> of the web browser <NUM>. In some such embodiments, however, the payment information <NUM> is not transmitted to the device <NUM>. Instead, the payment information <NUM> received from the server <NUM> is used to automatically process the transaction with the payment processor servers <NUM>. If the payment information is sent to the device <NUM>, the user may have the opportunity to review and approve the purchase using the received payment information <NUM> in the web browser <NUM>. In some embodiments, however, the purchase is automatically processed in the web page <NUM>-<NUM> without requiring further user input.

<FIG> depicts an embodiment where the purchase is processed using the payment information <NUM>. As shown, the web browser <NUM> may transmit the payment information <NUM> (e.g., in an HTTP request) to the ecommerce server <NUM> and/or the payment processor server <NUM>. In some embodiments, however, the web browser <NUM> transmits the payment information to the ecommerce server <NUM>, and the web page <NUM>-<NUM> (or another component of the ecommerce server <NUM>) provides the payment information <NUM> to the payment processor server <NUM>. The ecommerce server <NUM> may then generate a transaction record <NUM> for the transaction in the transaction database <NUM>. Similarly, the payment processor server <NUM> may generate a transaction record <NUM> in the payment processor data <NUM>.

Once the payment for the transaction is processed, the ecommerce server <NUM> may transmit a confirmation <NUM> to the web browser <NUM>. The confirmation <NUM> may be a portion of a web page <NUM>. The confirmation <NUM> generally indicates that payment for the transaction was received and the transaction has been processed. Furthermore, as shown, the memory <NUM> of the device <NUM> includes a cookie <NUM>. As stated, the cookie <NUM> may be stored by the on-demand application <NUM>-<NUM> subsequent to the OTP confirmation and/or by the web browser <NUM> based on the purchase confirmation <NUM>. The cookie <NUM> may be used to authenticate the user for subsequent transactions without requiring the OTP verification and/or cryptogram verification. The cookie <NUM> may generally include a token or some other identifier, such as a combination of a token and an identifier of the device <NUM>.

For example, if the user attempts to make a second purchase, the user may again select the URL <NUM> to use the on-demand application <NUM>-<NUM>. The on-demand application <NUM>-<NUM> may be downloaded (if not available on the device) and executed. The on-demand application <NUM>-<NUM> may identify the cookie <NUM> stored on the device. In response, the on-demand application <NUM>-<NUM> determines to forego the OTP generation and/or verification. The on-demand application on-demand application <NUM>-<NUM> may identify the first financial institution based on the cookie <NUM> and instruct the server <NUM> associated with the first financial institution to generate a second VAN, an expiration date for the second VAN, and a CVV for the second VAN. Advantageously, based on the identification of the cookie, the user is not required to tap the card to the device to facilitate decryption of another cryptogram by the server. The second VAN, expiration date, and CVV may then be used to complete the second purchase as described herein.

Advantageously, the purchase is securely processed using a web browser <NUM> and the web pages <NUM> without requiring the device <NUM> to execute a dedicated client application provided by an entity associated with the contactless card <NUM> (e.g., the application <NUM> provided by the financial institution associated with the contactless card <NUM>). Further still, each web page <NUM> does not need to include functionality for reading data from different cards and/or communicating with different servers <NUM>. Further still, the security of the card <NUM> and/or associated account is enhanced by using the cryptogram generated by the contactless card <NUM> as a condition to the purchase.

<FIG> is a schematic <NUM> depicting an example computing device <NUM>, consistent with disclosed embodiments. More specifically, <FIG> depicts an embodiment where the web browser <NUM> displays a checkout web page <NUM>-<NUM>. As shown, the web page <NUM>-<NUM> includes a selectable element <NUM> to initiate payment using a contactless card <NUM>. The selectable element <NUM> may correspond to a URL, such as the URL <NUM>, directed to one of the on-demand applications <NUM>. The URL may include a merchant identifier, transaction (or cart) identifier, and any other relevant parameters. Once selected, the device <NUM> may download the on-demand application <NUM> at the URL.

<FIG> is a schematic <NUM> illustrating an embodiment where an on-demand application <NUM>-<NUM> is downloaded and executed on the device <NUM>. As shown, the on-demand application <NUM>-<NUM> provides a welcome page and a URL <NUM> to initiate payment using the contactless card <NUM>. <FIG> reflect embodiments where the user has previously completed the OTP verification process and a cookie <NUM> has been stored on the device based on the OTP verification. Therefore, the on-demand application <NUM>-<NUM> may identify and validate a cookie <NUM> on the device <NUM> and determine to forego requesting the user's email to initiate the OTP flow.

<FIG> is a schematic <NUM> reflecting an embodiment where the user selects the URL <NUM>. As shown, the on-demand application <NUM>-<NUM> instructs the user to tap the contactless the contactless card <NUM> to the computing device <NUM> to process payment. When the card <NUM> comes within communications range of the card reader <NUM>, the on-demand application <NUM>-<NUM> controls the card reader <NUM> to instruct the applet <NUM> of the contactless card <NUM> to generate a diversified key <NUM> as described above, and use the generated diversified key <NUM> to generate a cryptogram (e.g., an encrypted customer ID <NUM>). The applet <NUM> may further generate an NDEF file or other data package that includes the cryptogram and an unencrypted identifier, e.g., an unencrypted customer ID <NUM>, the merchant ID, the transaction ID, and the like. In such embodiments, the on-demand application <NUM>-<NUM> may provide the merchant ID and/or transaction ID to the applet <NUM>.

The on-demand application <NUM>-<NUM> may then read the data package or NDEF file, e.g., via NFC. Once read, the on-demand application <NUM>-<NUM> may transmit the data package to the server <NUM> for processing. The on-demand application <NUM>-<NUM> may select the server <NUM> based on the cookie <NUM>. The on-demand application <NUM>-<NUM> may optionally process the data package, e.g., to format the data package, add the merchant ID, add the transaction ID, etc. The on-demand application <NUM>-<NUM> may further indicate, to the server <NUM>, that the cryptogram was read from the contactless card <NUM> via the card reader <NUM> of the device <NUM>.

Once received, the authentication application <NUM> may attempt to verify the cryptogram in the data package. In at least one embodiment, the unencrypted customer ID <NUM> provided by the applet <NUM> may be used by authentication application <NUM> to identify the relevant account, counter value <NUM>, and/or master key <NUM> in the account data <NUM>. The authentication application <NUM> may attempt to decrypt the cryptogram by providing the master key <NUM> and incremented counter value <NUM> as input to the cryptographic algorithm, which produces the diversified key <NUM> as output. The resulting diversified key <NUM> may correspond to the instance of the diversified key <NUM> generated by the contactless card <NUM> to create the cryptogram, which may be used to decrypt the cryptogram. Generally, the authentication application <NUM> may transmit a decryption result to the web browser <NUM> and/or the on-demand application <NUM>-<NUM> indicating whether the decryption was successful or unsuccessful. If the decryption is successful, the authentication application <NUM> may generate a virtual account number (VAN), expiration date for the VAN, and a CVV for the VAN. The authentication application <NUM> may then transmit the generated data to the device <NUM> and/or any suitable component thereof.

<FIG> is a schematic <NUM> illustrating an embodiment where the server <NUM> decrypted the cryptogram generated by the contactless card <NUM> and read by the on-demand application <NUM>-<NUM>. As shown, the on-demand application <NUM>-<NUM> may output an approval page based on the decryption result received from the server <NUM> responsive to decrypting the cryptogram. The on-demand application <NUM>-<NUM> may then include a selectable element <NUM> for requesting the user's approval to share or otherwise use the payment information for the transaction. Once selected, the on-demand application <NUM>-<NUM> may process the purchase using the payment information received from the server <NUM>. For example, the on-demand application <NUM>-<NUM> may transmit the merchant identifier, transaction identifier, account holder name, the VCN, the expiration date, the CVV, the billing address, and/or the shipping address to the ecommerce server <NUM> and/or the payment processor server <NUM> for processing. However, in some embodiments, the server <NUM> provides the payment information generated by the server <NUM> to the web browser <NUM> as described in greater detail herein responsive to the selection of selectable element <NUM>. Doing so may cause the web browser <NUM> to submit the payment information to the ecommerce server <NUM> and/or the payment processor server <NUM> for processing.

<FIG> is a schematic <NUM> depicting an embodiment where the web browser <NUM> outputs a confirmation in web page <NUM>-<NUM>. The confirmation page may be displayed based on a confirmation <NUM> received from the ecommerce server <NUM>. The confirmation may generally include details regarding the processed transaction.

Operations for the disclosed embodiments may be further described with reference to the following figures. Some of the figures may include a logic flow. Although such figures presented herein may include a particular logic flow, it can be appreciated that the logic flow merely provides an example of how the general functionality as described herein can be implemented. Further, a given logic flow does not necessarily have to be executed in the order presented unless otherwise indicated. Moreover, not all acts illustrated in a logic flow may be required in some embodiments. In addition, the given logic flow may be implemented by a hardware element, a software element executed by a processor, or any combination thereof.

<FIG> illustrate an embodiment of a logic flow <NUM>. The logic flow <NUM> may be representative of some or all of the operations executed by one or more embodiments described herein. For example, the logic flow <NUM> may include some or all of the operations to extend a transaction initiated in a web browser <NUM> using an on-demand application <NUM>. Embodiments are not limited in this context.

At block <NUM>, a web page <NUM> rendered in a browser <NUM> of a device <NUM> may include a URL, such as the URL <NUM>, that is directed to an on-demand application <NUM>. The user may select the URL <NUM> to complete a purchase using the linked on-demand application <NUM>. The URL <NUM> may further include parameters describing one or more attributes of the transaction, such as a merchant identifier, a transaction identifier, and the like. At block <NUM>, the selection of the URL causes the device <NUM> to download and execute the on-demand application <NUM>. At block <NUM>, the on-demand application <NUM> may scan the device <NUM> to identify any applications <NUM> on the device that are registered to one or more financial institutions. The on-demand application <NUM> may select one of the identified applications <NUM>, e.g., based on one or more attributes of each application <NUM> and/or a score computed for each application by the on-demand application <NUM> based on the attributes. The attributes may include, but are not limited to, the most recent use of the application <NUM>, the most frequently used application <NUM>, the number of times the application <NUM> has been used within a predetermined time period, a size of the financial institution, a number of customers of the financial institution, etc. The selected application <NUM> may be associated with at least one financial institution server <NUM>. If no applications <NUM> are identified, the on-demand application <NUM> may select one or more financial institution servers <NUM> based on a list of financial institution servers stored by the on-demand application <NUM>.

At block <NUM>, the on-demand application <NUM> requests an email address from the user and receives input comprising an email address. The on-demand application <NUM> may transmit the email address to the financial institution server <NUM> identified at block <NUM>. At block <NUM>, the authentication application <NUM> of the selected financial institution server <NUM> receives the email address from the on-demand application <NUM>. The authentication application <NUM> may query the account data <NUM> using the email address to receive a phone number of an account associated with the email address. The authentication application <NUM> may then generate an OTP and transmit the OTP to the phone number, e.g., via an SMS message.

At block <NUM>, the user provides the received OTP as input to the on-demand application <NUM>. The on-demand application <NUM> may verify the OTP entered by the user. For example, the on-demand application <NUM> may receive the OTP generated by the authentication application <NUM> and compare the received OTP to the input provided by the user. In such an example, on-demand application <NUM> may transmit a result of the comparison to the authentication application <NUM>. As another example, the on-demand application <NUM> may transmit the input received from the user to the authentication application <NUM>. The authentication application <NUM> may then compare the received input to the generated OTP and transmit a comparison result to the on-demand application <NUM>. Regardless of the entity performing the comparison, if the comparison results in a match, the email address may be verified and the account of the user in the account data <NUM> may be updated to reflect enrollment for purchases using the web browser <NUM> and an on-demand application <NUM>.

At block <NUM>, the on-demand application <NUM> instructs the user to tap their contactless card <NUM> to the device <NUM>. When the user taps the card <NUM> to the device <NUM>, the on-demand application <NUM> instructs the applet <NUM> to generate a cryptogram. In some embodiments, the on-demand application <NUM> provides the merchant ID and/or transaction ID to the applet <NUM>, which may include the merchant ID and/or transaction ID in a data package (e.g., an NDEF file) comprising the cryptogram. The on-demand application <NUM> may then read the cryptogram, which may be included in the NDEF file. At block <NUM>, the on-demand application <NUM> sends the cryptogram to the financial institution server <NUM> associated with the contactless card <NUM>. At block <NUM>, the on-demand application <NUM> receives a decryption result indicating the authentication application <NUM> decrypted the cryptogram, thereby authenticating and/or verifying the cryptogram. Based on the decryption, the authentication application <NUM> may generate a VCN, expiration date, and CVV for the account associated with the contactless card <NUM>.

At block <NUM>, the web browser <NUM> may receive payment information <NUM> generated by the authentication application <NUM> based on the verification of the OTP at block <NUM> and the decryption of the cryptogram at block <NUM>. For example, the authentication application <NUM> may provide the payment information <NUM> to the ecommerce server <NUM> hosting the web page <NUM>, and a web server of the ecommerce server <NUM> may provide the payment information <NUM> to the web browser <NUM>. At block <NUM>, the user may optionally approve the purchase using the payment information <NUM>. In some embodiments, however, user approval is not required, and the purchase is automatically completed using the received payment information <NUM>.

Continuing to <FIG>, at block <NUM>, the web browser <NUM> may submit the at least the payment information <NUM> to the ecommerce server <NUM> and/or the payment processor server <NUM> to process the transaction. At block <NUM>, the ecommerce server <NUM> and/or the payment processor server <NUM> processes the transaction using the payment information <NUM> generated by the server. At block <NUM>, the transaction complete and a confirmation is sent to the web browser <NUM>. At block <NUM>, the on-demand application <NUM> and/or the web browser <NUM> stores a cookie <NUM> on the device <NUM>. The cookie <NUM> may include a token or other information to allow the on-demand application <NUM> to determine that the user has completed the OTP registration. The token may further be used to identify the financial institution and/or financial institution server <NUM> associated with the card <NUM>. As stated, in some embodiments, the cookie <NUM> may be stored subsequent to the verification of the OTP at block <NUM>.

<FIG> illustrates an embodiment of a logic flow <NUM>. The logic flow <NUM> may be representative of some or all of the operations executed by one or more embodiments described herein. For example, the logic flow <NUM> may include some or all of the operations to extend a transaction initiated in a web browser <NUM> using an on-demand application <NUM>. Embodiments are not limited in this context.

At block <NUM>, a web page <NUM> rendered in a browser <NUM> of a device <NUM> may include a URL, such as the URL <NUM>, that is directed to an on-demand application <NUM>. The user may select the URL <NUM> to complete a purchase using the linked on-demand application <NUM>. The URL <NUM> may further include parameters describing one or more attributes of the transaction, such as a merchant identifier, a transaction identifier, and the like. At block <NUM>, the selection of the URL causes the device <NUM> to download and execute the on-demand application <NUM>. At block <NUM>, the on-demand application <NUM> identifies a cookie <NUM> stored in the memory of the device <NUM>. Doing so allows the on-demand application <NUM> to forego the OTP verification flow. At block <NUM>, the on-demand application <NUM> identifies the financial institution and/or financial institution server <NUM> associated with the card <NUM>.

At block <NUM>, the on-demand application <NUM> requests payment information from the financial institution server <NUM> identified at block <NUM>. The server <NUM> may then generate payment information <NUM> comprising a VCN, expiration date, and CVV. In some embodiments, the generation of the payment information <NUM> is conditioned on the contactless card <NUM> generating another cryptogram, and the server <NUM> verifying the cryptogram. At block <NUM>, the web browser <NUM> and/or the ecommerce server <NUM> receives the payment information <NUM> generated at block <NUM>. At block <NUM>, the web browser <NUM> submits the payment information <NUM> to the ecommerce server <NUM> and/or the payment processor server <NUM> to process the transaction. At block <NUM>, the ecommerce server <NUM> and/or the payment processor server <NUM> process the transaction. Doing so may include storing one or more transaction records for the transaction and transmitting a confirmation for the purchase to the web browser <NUM>.

<FIG> is a schematic <NUM> illustrating an example configuration of a contactless card <NUM>, which may include a payment card, such as a credit card, debit card, or gift card, issued by a service provider as displayed as service provider indicia <NUM> on the front or back of the contactless card <NUM>. In some examples, the contactless card <NUM> is not related to a payment card, and may include, without limitation, an identification card. In some examples, the contactless card may include a dual interface contactless payment card, a rewards card, and so forth. The contactless card <NUM> may include a substrate <NUM>, which may include a single layer or one or more laminated layers composed of plastics, metals, and other materials. Exemplary substrate materials include polyvinyl chloride, polyvinyl chloride acetate, acrylonitrile butadiene styrene, polycarbonate, polyesters, anodized titanium, palladium, gold, carbon, paper, and biodegradable materials. In some examples, the contactless card <NUM> may have physical characteristics compliant with the ID-<NUM> format of the ISO/IEC <NUM> standard, and the contactless card may otherwise be compliant with the ISO/IEC <NUM> standard. However, it is understood that the contactless card <NUM> according to the present disclosure may have different characteristics, and the present disclosure does not require a contactless card to be implemented in a payment card.

The contactless card <NUM> may also include identification information <NUM> displayed on the front and/or back of the card, and a contact pad <NUM>. The contact pad <NUM> 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 contactless cards. The contact pad may be designed in accordance with one or more standards, such as ISO/IEC <NUM> standard, and enable communication in accordance with the EMV protocol. The contactless card <NUM> may also include processing circuitry, antenna and other components as will be further discussed in <FIG>. These components may be located behind the contact pad <NUM> or elsewhere on the substrate <NUM>, e.g. within a different layer of the substrate <NUM>, and may electrically and physically coupled with the contact pad <NUM>. The contactless card <NUM> may also include a magnetic strip or tape, which may be located on the back of the card (not shown in <FIG>). The contactless card <NUM> may also include a Near-Field Communication (NFC) device coupled with an antenna capable of communicating via the NFC protocol. Embodiments are not limited in this manner.

As illustrated, the contact pad <NUM> of contactless card <NUM> may include processing circuitry <NUM> for storing, processing, and communicating information, including a processor <NUM>, a memory <NUM>, and one or more communications interface <NUM>. It is understood that the processing circuitry <NUM> may contain additional components, including processors, memories, error and parity/CRC checkers, data encoders, anti-collision algorithms, controllers, command decoders, security primitives and tamper proofing hardware, as necessary to perform the functions described herein.

The memory <NUM> 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 <NUM> 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 <NUM> may be encrypted memory utilizing an encryption algorithm executed by the processor <NUM> to encrypt data.

The memory <NUM> may be configured to store one or more applets <NUM>, one or more counters <NUM>, the master key <NUM>, a diversified key <NUM>, and a customer ID <NUM>. The one or more applets <NUM> may comprise one or more software applications configured to execute on one or more contactless cards, such as a Java® Card applet. However, it is understood that applets <NUM> 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 <NUM> may comprise a numeric counter sufficient to store an integer. The customer ID <NUM> may comprise a unique alphanumeric identifier assigned to a user of the contactless card <NUM>, and the identifier may distinguish the user of the contactless card from other contactless card users. In some examples, the customer ID <NUM> may identify both a customer and an account assigned to that customer and may further identify the contactless card <NUM> associated with the customer's account.

The processor <NUM> and memory elements of the foregoing exemplary embodiments are described with reference to the contact pad <NUM>, but the present disclosure is not limited thereto. It is understood that these elements may be implemented outside of the contact pad <NUM> or entirely separate from it, or as further elements in addition to processor <NUM> and memory <NUM> elements located within the contact pad <NUM>.

In some examples, the contactless card <NUM> may comprise one or more antenna(s) <NUM>. The one or more antenna(s) <NUM> may be placed within the contactless card <NUM> and around the processing circuitry <NUM> of the contact pad <NUM>. For example, the one or more antenna(s) <NUM> may be integral with the processing circuitry <NUM> and the one or more antenna(s) <NUM> may be used with an external booster coil. As another example, the one or more antenna(s) <NUM> may be external to the contact pad <NUM> and the processing circuitry <NUM>.

In an embodiment, the coil of contactless card <NUM> may act as the secondary of an air core transformer. The terminal may communicate with the contactless card <NUM> by cutting power or amplitude modulation. The contactless card <NUM> may infer the data transmitted from the terminal using the gaps in the power connection of the contactless card <NUM>, which may be functionally maintained through one or more capacitors. The contactless card <NUM> may communicate back by switching a load on the coil or load modulation. Load modulation may be detected in the terminal's coil through interference. More generally, using the antenna(s) <NUM>, processor <NUM>, and/or the memory <NUM>, the contactless card <NUM> provides a communications interface to communicate via NFC, Bluetooth, and/or Wi-Fi communications.

As explained above, contactless card <NUM> 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 <NUM> 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 <NUM> 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 device or point-of-sale terminal) and produce an NDEF message that comprises a cryptographically secure OTP encoded as an NDEF text tag.

One example of an NDEF OTP is an NDEF short-record layout (SR=<NUM>). In such an example, one or more applets <NUM> may be configured to encode the OTP as an NDEF type <NUM> well known type text tag. In some examples, NDEF messages may comprise one or more records, such as a cryptogram and an unencrypted customer ID <NUM> (or other unencrypted unique identifier for the card <NUM> and/or the associated account). The applets <NUM> may be configured to add one or more static tag records in addition to the OTP record.

In some examples, the one or more applets <NUM> 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 <NUM>. Based on the one or more applet <NUM>, an NFC read of the tag may be processed, the data may be transmitted to a server, such as a server <NUM> of a banking system, and the data may be validated at the server.

In some examples, the contactless card <NUM> and server <NUM> may include certain data such that the card may be properly identified. The contactless card <NUM> may include one or more unique identifiers (not pictured). Each time a read operation takes place, the counter <NUM> may be configured to increment. In some examples, each time data from the contactless card <NUM> is read (e.g., by a computing device <NUM>), the counter <NUM> is transmitted to the server for validation and determines whether the counter <NUM> are equal (as part of the validation) to a counter <NUM> of the server.

The one or more counter <NUM> 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 <NUM> has been read or used or otherwise passed over. If the counter <NUM> has not been used, it may be replayed. In some examples, the counter that is incremented on the card is different from the counter that is incremented for transactions. The contactless card <NUM> is unable to determine the application transaction counter <NUM> since there is no communication between applet <NUM> on the contactless card <NUM>. In some examples, the contactless card <NUM> may comprise a first applet <NUM>-<NUM>, which may be a transaction applet, and a second applet <NUM>-<NUM>, which may be an authentication applet for authenticating calls as disclosed herein. Each applet <NUM>-<NUM> and <NUM>-<NUM> may comprise a respective counter <NUM>.

In some examples, the counter <NUM> may get out of sync. In some examples, to account for accidental reads that initiate transactions, such as reading at an angle, the counter <NUM> may increment but the application does not process the counter <NUM>. In some examples, when the device <NUM> is woken up, NFC may be enabled and the device <NUM> may be configured to read available tags, but no action is taken responsive to the reads.

To keep the counter <NUM> in sync, an application, such as a background application, may be executed that would be configured to detect when the device <NUM> wakes up and synchronize with the server of a banking system (e.g., a server <NUM>) indicating that a read that occurred due to detection to then move the counter <NUM> 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 <NUM>, the counter <NUM> may be configured to move forward. But if within a different threshold number, for example within <NUM> or <NUM>, 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 <NUM> 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 <NUM>, master key, and diversified key, 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 <NUM>, 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 <NUM>. 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 5DES 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 and the counter may be used as diversification data. For example, each time the contactless card <NUM> 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 <NUM> Book <NUM> A1. <NUM> 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 <NUM> and even numbered cards may increment by <NUM>. In some examples, the increment may also vary in sequential reads, such that one card may increment in sequence by <NUM>, <NUM>, <NUM>, <NUM>, <NUM>,. 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.

<FIG> illustrates an NDEF short-record layout (SR=<NUM>) data structure <NUM> according to an example embodiment. One or more applets may be configured to encode the OTP as an NDEF type <NUM> well known type text tag. In some examples, NDEF messages may comprise one or more records. The applets may be configured to add one or more static tag records in addition to the OTP record. Exemplary tags include, without limitation, Tag type: well known type, text, encoding English (en); Applet ID: D2760000850104; Capabilities: read-only access; Encoding: the authentication message may be encoded as ASCII hex; type-length-value (TLV) data may be provided as a personalization parameter that may be used to generate the NDEF message. In an embodiment, the authentication template may comprise the first record, with a well-known index for providing the actual dynamic authentication data. In various embodiments, the payload of the data structure <NUM> may store a cryptogram (e.g., an encrypted customer ID <NUM>) and any other relevant data, such as an unencrypted customer ID <NUM>, and/or some other unencrypted value that uniquely identifies a card <NUM> and/or an account associated with the card <NUM>.

<FIG> illustrates an embodiment of an exemplary computer architecture <NUM> comprising a computing system <NUM> that may be suitable for implementing various embodiments as previously described. In one embodiment, the computer architecture <NUM> may include or be implemented as part of computing system <NUM>. In some embodiments, computing system <NUM> may be representative, for example, of the contactless card <NUM>, computing devices <NUM>, and servers <NUM>, <NUM>, <NUM>, and <NUM> of the system <NUM>. More generally, the computing architecture <NUM> is configured to implement all logic, applications, systems, methods, apparatuses, and functionality described herein with reference to <FIG>.

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 <NUM>. 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.

As shown in <FIG>, the computing architecture <NUM> includes a processor <NUM>, a system memory <NUM> and a system bus <NUM>. The processor <NUM> can be any of various commercially available processors.

The system bus <NUM> provides an interface for system components including, but not limited to, the system memory <NUM> to the processor <NUM>. Interface adapters may connect to the system bus <NUM> via slot architecture.

The computing architecture <NUM> 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.

In the illustrated embodiment shown in <FIG>, the system memory <NUM> can include non-volatile <NUM> and/or volatile <NUM> memory.

The computer <NUM> 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 <NUM>, a magnetic disk drive <NUM> to read from or write to a removable magnetic disk <NUM>, and an optical disk drive <NUM> to read from or write to a removable optical disk <NUM> (e.g., a CD-ROM or DVD). The hard disk drive <NUM>, magnetic disk drive <NUM> and optical disk drive <NUM> can be connected to system bus <NUM> the by an HDD interface <NUM>, and FDD interface <NUM> and an optical disk drive interface <NUM>, respectively. The HDD interface <NUM> for external drive implementations can include at least one or both of Universal Serial Bus (USB) and IEEE <NUM> 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 memory <NUM>, and volatile memory <NUM>, including an operating system <NUM>, one or more applications <NUM>, other program modules <NUM>, and program data <NUM>. In one embodiment, the one or more applications <NUM>, other program modules <NUM>, and program data <NUM> can include, for example, the various applications and/or components of the system <NUM>, such as the applet <NUM>, counter <NUM>, master key <NUM>, diversified key <NUM>, customer ID <NUM>, URLs <NUM>, web browser <NUM>, financial institution servers <NUM>, authentication application <NUM>, account data <NUM>, payment processor servers <NUM>, payment processor data <NUM>, ecommerce servers <NUM>, web pages <NUM>, transaction database <NUM>, application servers <NUM>, and on-demand applications <NUM>.

A user can enter commands and information into the computer <NUM> through one or more wire/wireless input devices, for example, a keyboard <NUM> and a pointing device, such as a mouse <NUM>. 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 <NUM> through an input device interface <NUM> that is coupled to the system bus <NUM> but can be connected by other interfaces such as a parallel port, IEEE <NUM> serial port, a game port, a USB port, an IR interface, and so forth.

A monitor <NUM> or other type of display device is also connected to the system bus <NUM> via an interface, such as a video adapter <NUM>.

The computer <NUM> 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) <NUM>. The remote computer(s) <NUM> 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 <NUM>, although, for purposes of brevity, only a memory and/or storage device <NUM> is illustrated. The logical connections depicted include wire/wireless connectivity to a local area network <NUM> and/or larger networks, for example, a wide area network <NUM>.

When used in a local area network <NUM> networking environment, the computer <NUM> is connected to the local area network <NUM> through a wire and/or wireless communication network interface or network adapter <NUM>. The network adapter <NUM> can facilitate wire and/or wireless communications to the local area network <NUM>, which may also include a wireless access point disposed thereon for communicating with the wireless functionality of the network adapter <NUM>.

When used in a wide area network <NUM> networking environment, the computer <NUM> can include a modem <NUM>, or is connected to a communications server on the wide area network <NUM> or has other means for establishing communications over the wide area network <NUM>, such as by way of the Internet. The modem <NUM>, which can be internal or external and a wire and/or wireless device, connects to the system bus <NUM> via the input device interface <NUM>. In a networked environment, program modules depicted relative to the computer <NUM>, or portions thereof, can be stored in the remote memory and/or storage device <NUM>. 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 <NUM> is operable to communicate with wire and wireless devices or entities using the IEEE <NUM> family of standards, such as wireless devices operatively disposed in wireless communication (e.g., IEEE <NUM> 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 <NUM> (a, b, g, n, etc.) to provide secure, reliable, fast wireless connectivity. A Wi-Fi network can be used to connect computers to each other, to the Internet, and to wire networks (which use IEEE <NUM>-related media and functions).

The various elements of the devices as previously described with reference to <FIG> may include various hardware elements, software elements, or a combination of both. Examples of hardware elements may include devices, logic devices, components, processors, microprocessors, circuits, processors, circuit elements (e.g., transistors, resistors, capacitors, inductors, and so forth), integrated circuits, application specific integrated circuits (ASIC), programmable logic devices (PLD), digital signal processors (DSP), field programmable gate array (FPGA), memory units, logic gates, registers, semiconductor device, chips, microchips, chip sets, and so forth. Examples of software elements may include software components, programs, applications, computer programs, application programs, system programs, software development programs, machine programs, operating system software, middleware, firmware, software modules, routines, subroutines, functions, methods, procedures, software interfaces, application program interfaces (API), instruction sets, computing code, computer code, code segments, computer code segments, words, values, symbols, or any combination thereof. However, determining whether an embodiment is implemented using hardware elements and/or software elements may vary in accordance with any number of factors, such as desired computational rate, power levels, heat tolerances, processing cycle budget, input data rates, output data rates, memory resources, data bus speeds and other design or performance constraints, as desired for a given implementation.

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 be 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. 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.

With general reference to notations and nomenclature used herein, the detailed descriptions herein may be presented in terms of program procedures executed on a computer or network of computers. These procedural descriptions and representations are used by those skilled in the art to most effectively convey the substance of their work to others skilled in the art.

A procedure is here, and generally, conceived to be a self-consistent sequence of operations leading to a desired result. These operations are those requiring physical manipulations of physical quantities. Usually, though not necessarily, these quantities take the form of electrical, magnetic or optical signals capable of being stored, transferred, combined, compared, and otherwise manipulated. It proves convenient at times, principally for reasons of common usage, to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, or the like. It should be noted, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to those quantities.

Further, the manipulations performed are often referred to in terms, such as adding or comparing, which are commonly associated with mental operations performed by a human operator. No such capability of a human operator is necessary, or desirable in most cases, in any of the operations described herein, which form part of one or more embodiments. Rather, the operations are machine operations. Useful machines for performing operations of various embodiments include general purpose digital computers or similar devices.

Various embodiments also relate to apparatus or systems for performing these operations. This apparatus may be specially constructed for the required purpose or it may comprise a general purpose computer as selectively activated or reconfigured by a computer program stored in the computer. The procedures presented herein are not inherently related to a particular computer or other apparatus. Various general purpose machines may be used with programs written in accordance with the teachings herein, or it may prove convenient to construct more specialized apparatus to perform the required method steps. The required structure for a variety of these machines will appear from the description given.

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.

Claim 1:
A computer-implemented method, comprising:
receiving, by a web browser executing on a processor of a device, selection of a link in a merchant web page, the merchant web page associated with a transaction;
downloading, by an operating system (OS) executing on the processor, an application from an application server based on the link;
identifying, by the application, a plurality of financial institution applications installed on the device;
selecting, by the application, a first financial institution corresponding to a first financial institution application of the plurality of financial institution applications installed on the device;
receiving, by the application, an identifier;
transmitting, by the application, the identifier to an authentication server of the first financial institution to generate a one-time passcode, OTP, and send the OTP to a phone number associated with the identifier;
receiving, by the application, an input value;
based on the input value matching the OTP, outputting, by the application, an indication to tap a contactless card associated with the first financial institution to the device;
instructing, by the application, the contactless card to generate encrypted data;
receiving, by the application, the encrypted data from the contactless card;
transmitting, by the application, the encrypted data to the authentication server of the first financial institution;
receiving, by the application, an authentication result specifying the authentication server decrypted the encrypted data;
receiving, by the web browser based on the decryption of the encrypted data by the authentication server, an account number, an expiration date associated with the account number, and a card verification value (CVV) associated with the account number; and
providing, by the web browser, the account number, the expiration date, and the CVV to a server associated with the application to process the transaction.