Account registration using contactless cards

Abstract

To provide systems, methods, articles of manufacture, and computer-readable media for tapping to automatically input card data into a form on a computing device.SOLUTION: A method of account registration using a contactless card is provided. A payment application receives a request to generate a payment account using a contactless card, receives encrypted data from the contactless card and transmits the encrypted data to a server associated with the contactless card. The device receives a push notification from the server and opens an account application associated with the contactless card in response to selection of the push notification. The account application receives confirmation to generate the payment account using the contactless card and transmits the confirmation to the server. The device opens the payment application upon receiving verification of the encrypted data from the server.SELECTED DRAWING: Figure 4

Description

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the priority of U.S. Patent Application No. 16 / 726,366, filed on December 24, 2019 and entitled "Account Registration Using Contactless Card". The content of the aforementioned application is hereby incorporated by reference in its entirety into the present specification. TECHNICAL FIELD

[0002] Embodiments of the present specification generally relate to computing platforms, and more specifically, to using a contactless card to register an account. BACKGROUND ART

[0003] Third-party payment services allow users to make payments using different payment accounts. However, registering an account with a third-party payment service using a payment account may expose the user to security risks. For example, a malicious user may attempt to create a fraudulent account on a third-party payment service using compromised information of the user and / or the user's payment account. As a result, institutions associated with third-party payment services and / or payment accounts may not be able to distinguish between legitimate attempts and fraudulent attempts to create third-party payment accounts. SUMMARY OF THE INVENTION

[0004] Embodiments disclosed herein provide systems, methods, products, and computer-readable media for tapping to automatically populate forms on a computer device with card data. For example, a payment application running on a device can receive instructions to explicitly generate a payment account in the payment application using a contactless card. The payment application can output instructions to explicitly tap the contactless card on the device. The device can receive encrypted data from the contactless card's communication interface, which is based on a customer identifier and private key associated with the contactless card. The device can send the encrypted data to a server associated with the contactless card and receive a push notification from the server. In response to receiving a selection in the push notification, the device can open the account application associated with the contactless card. The account application can receive confirmation input explicitly to generate a payment account in the payment application using the contactless card. The account application can send instructions for confirmation input to the server. In response to the payment application receiving verification of encrypted data from the server, the device can open the payment application. The payment application can populate multiple form fields of a form displayed in the payment application with the account data received from the server and the account data associated with the contactless card. A payment application can generate a payment account using account data received from a server and entered into multiple form fields. [Brief explanation of the drawing]

[0005] [Figure 1A] This document illustrates an embodiment of a system for account creation using contactless cards. [Figure 1B] This document illustrates an embodiment of a system for account creation using contactless cards. [Figure 1C]This document illustrates an embodiment of a system for account creation using contactless cards. [Figure 1D] This document illustrates an embodiment of a system for account creation using contactless cards. [Figure 1E] This document illustrates an embodiment of a system for account creation using contactless cards. [Figure 2A] This document illustrates an embodiment of account creation using contactless cards. [Figure 2B] This document illustrates an embodiment of account creation using contactless cards. [Figure 2C] This document illustrates an embodiment of account creation using contactless cards. [Figure 2D] This document illustrates an embodiment of account creation using contactless cards. [Figure 2E] This document illustrates an embodiment of account creation using contactless cards. [Figure 2F] This document illustrates an embodiment of account creation using contactless cards. [Figure 2G] This document illustrates an embodiment of account creation using contactless cards. [Figure 3A] An example of a contactless card is shown. [Figure 3B] An example of a contactless card is shown. [Figure 4] The first embodiment of the logic flow is shown. [Figure 5] A second embodiment of the logic flow is shown. [Figure 6] This shows an embodiment of the computing architecture. [Modes for carrying out the invention]

[0006] Embodiments disclosed herein provide a secure technique for generating an account using a contactless card. The account may be a third-party payment account for a third-party payment service that provides a third-party payment application for use on a computing device. A payment account associated with a contactless card provided by a financial institution may be used to fund transactions using the third-party payment account. When attempting to register an account with a third-party payment application, a user may choose the option to securely generate an account using a contactless card. In response, the third-party payment application may output an instruction to tap the contactless card on the device. The user can then tap the contactless card on the device. The device may then instruct the contactless card to generate and send encrypted data to the device. The data generated by the contactless card may be encrypted using key diversification. The device may send the encrypted data received from the contactless card to a first server associated with the financial institution providing the contactless card.

[0007] The first server can verify the encrypted data received from the contactless card by decrypting the encrypted data. The first server can then send a push notification to the device. The device can output the push notification for display on its screen. An account application provided by the financial institution can be opened on the device in response to the user selecting the notification. The account application can then request the user to provide authentication credentials to access the account associated with the contactless card. The account application can then request the user to verify whether the account generation attempted using the third-party payment application is valid. If the user provides input indicating that the account generation is not valid, the third-party account generation may be restricted to protect the security of the account associated with the contactless card. Otherwise, the account application can send instructions to the first server indicating that the user has verified the validity of the account generation attempted using the third-party payment application.

[0008] The device can output a third-party payment application for display. The third-party payment application can receive account data for an account associated with a contactless card from a first server. The account data may include one or more of the following: first name, last name, email address, address, contactless card account number, contactless card expiration date, and contactless card card verification value (CVV). The third-party payment application can automatically populate the corresponding form fields of a form provided by the third-party payment application with the received account data. In response to receiving user input that explicitly requests the generation of an account, the third-party payment application can generate an account using the data received from the server. The record of the generated account may be stored on a second server associated with the third-party payment application. The user can then make purchases using the third-party payment application and the underlying account associated with the contactless card.

[0009] Advantageously, this improves the security of all devices and associated data. For example, verification of encrypted data by the first server provides an additional safeguard to prevent fraud by confirming that the user attempting to create an account has a contactless card. This further confirms that the contactless card is not fraudulent, as a fraudulent card is unlikely to be able to generate encrypted data that can be verified by the server. Furthermore, traditional methods require users to manually enter account data into a form. However, this makes it possible for other users or devices to ingest the card data while the user is entering it into the form. By eliminating the need for users to manually enter card data into a form, the security of account data is enhanced.

[0010] Referring generally to the notation and nomenclature used herein, one or more parts of the following detailed descriptions may be presented in relation to program procedures performed on a computer or a network of computers. These descriptions and expressions of procedures are used by those skilled in the art to most effectively convey the content of their work to others skilled in the art. A procedure is generally considered here to be a self-consistent set of actions that produce a desired result. These operations are those that require the physical manipulation of physical quantities. While not always the case, these quantities usually take the form of electrical, magnetic, or optical signals that can be stored, transferred, combined, compared, and otherwise manipulated. For reasons of general use, it is sometimes convenient to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, etc. However, it should be noted that all these and similar terms should be associated with appropriate physical quantities and are merely convenient labels applied to those quantities.

[0011] Furthermore, these operations are often referred to by terms such as addition or comparison, and these generally relate to mental actions performed by human operators. However, in any of the operations described herein that form part of one or more embodiments, such ability of a human operator is not required, or in most cases, undesirable. Rather, these operations are mechanical operations. Useful machines for performing the operations of various embodiments include digital computers selectively invoked or configured by computer programs written in accordance with the teachings herein, and / or devices or digital computers specifically configured for the required purpose. Various embodiments also relate to devices or systems for performing these operations. These devices may be specifically configured for the required purpose. The structures required for various these machines will become apparent from the given description.

[0012] Drawings are referenced here, and similar reference numbers are used throughout to indicate similar elements. The following description includes many specific details for explanatory purposes and to provide a complete understanding. However, it will be apparent that novel embodiments can be implemented without these specific details. In other examples, well-known structures and devices are shown in block diagram form for the sake of clarity. The intent is to cover all modifications, equivalents, and substitutions within the claims.

[0013] Figure 1A shows a schematic diagram of an exemplary system 100 consistent with the disclosed embodiment. As shown, the system 100 includes one or more contactless cards 101, one or more mobile devices 110, a server 120, and a third-party server 140. The contactless card 101 represents any type of payment card, such as a credit card, debit card, ATM card, or gift card. The contactless card 101 may include one or more chips (not shown), such as a radio frequency identification (RFID) chip, configured to communicate with the mobile device 110 via NFC, EMV standards, or other short-range protocols in wireless communication. While NFC is used as an exemplary communication protocol, this disclosure is equally applicable to other types of wireless communication, such as EMV standards, Bluetooth, and / or Wi-Fi. The mobile device 110 represents any type of network-enabled computing device, such as a smartphone, tablet computer, wearable device, laptop, or portable gaming device. The servers 120, 140 represent any type of computing device, such as a server, workstation, compute cluster, cloud computing platform, or virtualization computing system.

[0014] As shown in the figure, the memory 111 of the mobile device 110 contains an instance of an operating system (OS) 112. Exemplary operating systems 112 include Android® OS, iOS®, Linux®, and Windows® operating systems. As shown in the figure, the OS 112 includes an account application 113 and one or more third-party applications 115. The account application 113 enables the user to perform various account-related operations such as viewing account balances, purchasing goods, and processing payments. In some embodiments, the user may authenticate using authentication credentials to access the account application 113. For example, authentication credentials may include a username and password, biometric credentials, etc.

[0015] Third-party application 115 represents any type of payment application that allows a registered user to process transactions using a payment source added by the user. For example, a user may create an account on the third-party application 115 and register to add the contactless card 101 as a payment source. By doing so, the user can make purchases using the third-party application 115, using the contactless card 101 (and / or an account associated with the contactless card 101) as a form of payment. Examples of the third-party application 115 include, but are not limited to, PayPal®, Venmo®, Apple® Pay, Samsung® Pay, Google® Pay, and the like. Advantageously, the embodiments disclosed herein provide secure techniques for creating an account on the third-party application 115 that has the contactless card 101 as a payment source. Third-party server 140 may be associated with a given third-party application 115. The third-party server 140 may generally include a database of account data 144 for user accounts. The account data 144 may include user profile information, address information, payment information, account number, account expiration date, CVV, login credentials, as well as any other type of account and / or personal data for a plurality of users.

[0016] As illustrated, the memory 102 of the contactless card 101 includes an applet 103, a counter 104, a master key 105, a dispersion key 106, and a unique customer identifier (ID) 107. The customer ID 107 may uniquely identify the user of the financial institution that provides the contactless card 101 and / or the user's account. The applet 103 may run on a processor (not shown) of the contactless card 101 to perform various functions described in greater detail herein.

[0017] As shown in the figure, the server 120 includes a data store for account data 124 and a memory 122. The account data 124 includes account-related data for a plurality of users and / or accounts. The account data 124 may include at least a master key 105, a counter 104, a customer ID 107, an associated contactless card 101 (including an account number, an expiration date, and a CVV), an account owner name, an account billing address, one or more shipping addresses, one or more virtual card numbers, and history information for each account. The memory 122 includes a management application 123, and instances of the counter 104, the master key 105, and the distributed key 106 for one or more accounts from the account data 124.

[0018] As described above, the contactless card 101 can be used at least in part to create an account in the account data 144 of the third-party server 140 using the third-party application 115. In general, a user of the third-party application 115 can specify to use the contactless card 101 to create a new account. By doing so, the third-party application 115 outputs an instruction specifying to tap the contactless card 101 to the device 110. By doing so, the contactless card 101 enters the communication range of the card reader 118 of the mobile device 110, and causes the applet 103 to generate the encrypted customer ID 109. The applet 103 can use any number of techniques to generate the encrypted customer ID 109 based on a cryptographic algorithm and the customer ID 107.

[0019] As described above, system 100 is configured to implement key distribution to protect data, which may be referred to herein as key distribution technology. Generally, the server 120 (or another computing device) and the contactless card 101 may be provisioned with the same master key 105 (also called a master symmetric key). More specifically, each contactless card 101 is programmed with a separate master key 105 having a corresponding pair within the server 120. For example, when a contactless card 101 is manufactured, a unique master key 105 may be programmed into the memory 102 of the contactless card 101. Similarly, a unique master key 105 may be stored in the customer record associated with the contactless card 101 in the account data 124 of the server 120 (and / or in a different secure location such as a hardware security module (HSM) 125). The master key 105 may be kept secret from all parties other than the contactless card 101 and the server 120, thereby enhancing the security of system 100. In some embodiments, the applet 103 of the contactless card 101 can encrypt and / or decrypt data (e.g., customer ID 107) using the master key 105 and the data as input to a cryptographic algorithm. For example, by encrypting customer ID 107 with the master key 105, an encrypted customer ID 109 can be obtained. Similarly, the authentication server 120 can encrypt and / or decrypt data associated with the contactless card 101 using the corresponding master key 105.

[0020] In other embodiments, the master key 105 of the contactless card 101 and the server 120 can be used with a counter 104 to enhance security using key distribution. The counter 104 contains a value synchronized between the contactless card 101 and the server 120. The counter value 104 may include a number that changes each time data is exchanged between the contactless card 101 and the server 120 (and / or between the contactless card 101 and the mobile device 110). When preparing to send data (for example, to the server 120 and / or the mobile device 110), the contactless card 101 can increment the counter value 104. The contactless card 101 can then provide the master key 105 and the counter value 104 as input to a cryptographic algorithm, which generates a distributed key 106 as output. The cryptographic algorithm may include an encryption algorithm, a hash-based message authentication code (HMAC) algorithm, a cryptographic-based message authentication code (CMAC) algorithm, and the like. Non-limiting examples of cryptographic algorithms may include symmetric cryptographic algorithms such as 3DES or AES128, symmetric HMAC algorithms such as HMAC-SHA-256, and symmetric CMAC algorithms such as AES-CMAC. Examples of key distribution techniques are described in detail in U.S. Patent Application No. 16 / 205,119, filed November 29, 2018. The aforementioned patent application is incorporated herein by reference in its entirety.

[0021] Continuing with the key distribution example, the contactless card 101 can then encrypt the customer ID 107 using the distributed key 106 and data as input to a cryptographic algorithm. For example, by encrypting the customer ID 107 with the distributed key 106, the encrypted customer ID 109 can be obtained.

[0022] Regardless of the encryption technology used to encrypt the customer ID 107, the contactless card 101 can transmit the encrypted customer ID 109 to a mobile device 110 (e.g., via NFC connection, Bluetooth connection, etc.). Upon receipt, the mobile device 110 (e.g., OS 112 and / or third-party application 115) can transmit the encrypted customer ID 109 to a server 120 via the network 130. In one embodiment, the encrypted customer ID 109 is transmitted to an API provided by a management application 123 via a Hypertext Transfer Protocol Secure (HTTPS) Application Programming Interface (API) call.

[0023] Upon receipt, the management application 123 can authenticate the encrypted customer ID 109. For example, the management application 123 can attempt to decrypt the encrypted customer ID 109 using a copy of the master key 105 stored in the memory 122 of the authentication server 120. In another example, the management application 123 can provide the master key 105 and counter value 104 as input to a cryptographic algorithm, which can generate a distributed key 106 as output. The resulting distributed key 106 may correspond to the distributed key 106 of a contactless card 101 that can be used to decrypt the encrypted customer ID 109.

[0024] Regardless of the decryption technique used, the management application 123 can decrypt the encrypted customer ID 109 and thereby verify the encrypted customer ID 109 (for example, by comparing the resulting customer ID 107 with the customer ID stored in the account data 124 and / or based on the indication that decryption using keys 105 and / or 106 was successful). Although keys 105 and 106 are shown as being stored in memory 122, keys 105 and 106 may be stored in other locations, such as the secure element and / or HSM 125. In such embodiments, the secure element and / or HSM 125 can decrypt the encrypted customer ID 109 using keys 105 and / or 106 as well as the encryption function. Similarly, the secure element and / or HSM 125 can generate a distributed key 106 based on the master key 105 and counter value 104, as described above.

[0025] However, if the management application 123 is unable to decrypt the encrypted customer ID 109 and obtain the expected result (for example, the customer ID 107 of the account associated with the contactless card 101), the management application 123 will not verify the encrypted customer ID 109. In such an example, the management application 123 will send a message to the third-party application 115 indicating that verification failed. Thus, the third-party application 115 may refrain from generating the requested account in order to protect the security of the account associated with the contactless card 101. In general, the management application 123 can condition any behavior regarding whether the encrypted customer ID 109 has been successfully decrypted.

[0026] Figure 1B shows an embodiment in which the management application 123 verifies an encrypted customer ID 109. More specifically, as shown in the figure, in response to the verification (e.g., decryption) of the encrypted customer ID 109, the management application 123 sends a push notification 150 to the mobile device 110. The notification 150 may generally indicate that an account creation attempted using a third-party application 115 needs to be verified. The OS 112 may output the notification 150 for display on the mobile device 110's display. The user can tap or otherwise select the notification 150, which will display the account application 113 on the mobile device 110. The user can then provide authentication credentials to access the account associated with the contactless card 101. Once authenticated, the account application 113 may request user verification (or confirmation) of the requested account creation. If the user refuses to verify the requested account creation, account creation is restricted to protect security.

[0027] Figure 1C shows an embodiment in which a user confirms the requested account creation via the account application 113. Once the user confirms the requested account creation, the account application 113 can send a confirmation 151 to the server 120. The confirmation 151 may be sent via an HTTPS API call to an API provided by the management application 123.

[0028] Figure 1D shows an embodiment in which the management application 123 receives confirmation 151 from the mobile device 110. As shown, the management application 123 sends verification 153 containing account data 154 to the third-party application 115. Verification 153 can generally instruct the third-party application 115 that account creation has been securely verified. The management application 123 can generally send verification 153 in response to receiving confirmation 151 and based on the successful decryption of the encrypted customer ID 109. Although the decryption of the encrypted customer ID 109 was described with reference to Figures 1A / 1B, the management application 123 can attempt to decrypt the encrypted customer ID 109 at any point, such as after receiving confirmation 151.

[0029] The account data 154 provided by the management application 123 generally includes data describing the user and / or account associated with the contactless card 101. For example, the account data 154 may include the user's first name, last name, email address, address, account number for the contactless card 101, expiration date for the contactless card 101, and card verification value (CVV) for the contactless card 101. The embodiments are not limited to this context, as the account data 154 may include fewer or more data attributes. For example, in some embodiments, for security purposes, the account data 154 may include a virtual account number instead of the account number for the contactless card 101. In such embodiments, the management application 123 may transmit a virtual account number if the third-party application 115 and / or third-party server 140 do not tokenize the account number (e.g., the account number for the contactless card 101). However, if the account number is tokenized by the third-party application 115 and / or third-party server 140, the management application 123 may include the account number for the contactless card 101.

[0030] Upon receipt, the third-party application 115 can automatically populate (or add) account data 154 to multiple form fields of the form output by the third-party application 115. For example, first name / last name may be entered in the first name / last name field of the form, email address may be entered in the email address field of the form, part of the address (e.g., street number, city, state, zip code) may be entered in one or more address fields of the form, account number may be entered in the account number field of the form, account number expiration date may be entered in the expiration date field of the form, and CVV may be entered in the CVV field of the form. The user can then review and submit the form via the third-party application 115 to complete account generation. In some embodiments, the user can modify the data in the form before submitting the form. In some embodiments, the third-party application 115 can obfuscate or otherwise conceal one or more elements of the account data, such as the account number.

[0031] Figure 1E shows an embodiment in which a user submits a form via a third-party application 115. As shown, the third-party application 115 can send instructions for a new account 155 containing account data 154 to a third-party server 140. In some embodiments, the new account 155 is created by the third-party application 115. In other embodiments, the third-party application 115 sends a request to the third-party server 140 to generate a new account 155, and the third-party server 140 generates the new account 155. Regardless of the entity generating the new account 155, one or more records of the new account 155 using the account data 154 may be generated in the account database 144 of the third-party server 140.

[0032] Subsequently, the user can use the new account 155 to make purchases, transfer funds, execute transactions, and perform other financial operations using the contactless card 101 (and / or the virtual account number of the contactless card 101) via the third-party application 115. Advantageously, the embodiments disclosed herein enhance security by coordinating account creation via the third-party application 115 using the contactless card 101, at least in part, based on the verification of an encrypted customer ID 109, the authentication of account credentials within the account application 113, and secure communication between entities in the system 100.

[0033] Figure 2A is a schematic diagram 200 illustrating an exemplary embodiment of account creation using a contactless card 101. The graphical user interface (GUI) of a third-party application 115 on a mobile device 110 provides GUI elements 201 that enable the user to create an account in the third-party application 115 using the contactless card 101. When the user selects GUI 201, the third-party application 115 can output instructions 202 that explicitly prompt the user to tap the contactless card 101 on the device 110, as shown in the schematic diagram 210 of Figure 2B.

[0034] As shown in Figure 2B, a user can tap the contactless card 101 on the device 110. When the user taps the contactless card 101 on the mobile device 110, the applet 103 of the contactless card 101 generates an encrypted customer ID 109. The applet 103 can then send the encrypted customer ID 109 to the mobile device 110, for example, via NFC. Upon receipt, a third-party application 115 can send the encrypted customer ID 109 to the management application 123, for example, via an HTTPS API call.

[0035] Schematic diagram 220 in Figure 2C shows a push notification 203 that is output for display on a mobile device 110. As described above, the management application 123 can generate a push notification 203 in response to receiving and / or verifying an encrypted customer ID 109. The management application 123 can then send the push notification 203 to the mobile device 110. When the user selects the push notification 203, they can open the account application 113 on the mobile device 110.

[0036] Figure 2D is a schematic diagram 230 showing an embodiment in which the user selects a push notification 203. As shown in Figure 2D, the account application 113 is opened on the mobile device 110. The account application 113 generally notifies the user that an attempt to open an account using a third-party application 115 has been detected. The account application 113 may provide GUI elements 204 to allow the user to confirm (or verify) that the attempt is valid, for example, that it was initiated by a user associated with the account. As described above, in some embodiments, the user may need to provide authentication credentials to the account application 113 before the GUI shown in Figure 2D is output. If the user wishes to confirm, the user can select a GUI element 204. Otherwise, the user can select a GUI element 224 to restrict the creation of a new account via the third-party application 115. The account application 113 can send instructions for the selected GUI elements 204, 224 to the management application 123.

[0037] Figure 2E is a schematic diagram 240 showing an embodiment in which a user selects a GUI element 204 to verify the validity of account generation attempted via a third-party application 115. As described above, once the user selects the GUI element 204, the account application 113 can send an instruction to the management application 123 that the user has selected the GUI element 204. In doing so, the management application 123 sends verification to the third-party application 115 along with account data 154 associated with the contactless card 101. As described above, the account data 154 may include the user's first name, user's last name, user's email address, user's address, the account number of the contactless card 101, the expiration date of the contactless card 101, and the card verification value (CVV) of the contactless card 101. In some embodiments, instead of the account number, expiration date, and CVV of the contactless card 101, a virtual account number, the expiration date of the virtual account number, and the CVV of the virtual account number may be included.

[0038] As shown in the figure, the third-party application 115 may include form fields 205-209 and 211. The third-party application 115 automatically populates the form fields 205-209 and 211 with account data 154 received from the management application 123. For example, as shown in the figure, the first name is entered in the first name field 205, the last name in the last name field 206, the email address in the email address field 207, the street address in the street address field 208, and additional address information in the address information field 209. The specific values ​​shown in Figure 2E are illustrative and should not be considered limiting to this disclosure. In some embodiments, the user may optionally modify the values ​​entered in the form fields 205-209 and 211. The user can then select the Next button 212 to continue.

[0039] Figure 2F is a schematic diagram 250 showing an embodiment in which the user has selected the Next button 212 in Figure 2E. As shown, the third-party application 115 outputs form fields 213-215. The third-party application 115 has entered the card number in the card number field 213, the expiration date in the expiration date field 214, and the CVV in the CVV field 215. Although shown as part of a separate form, in one embodiment, form fields 205-209, 211, and 213-215 may be part of a single form. As mentioned above, the account number may be the basic account number or virtual account number of the contactless card 101. The user can then select the Next button 216 to continue account generation.

[0040] Figure 2G is a schematic diagram 260 showing an embodiment in which the user selects the Next button 216 in Figure 2F to complete account setup using the third-party application 115. As shown, the third-party application 115 indicates that the account has been successfully created. The user can then use the third-party application 115 to make purchases, process payments, etc., using the contactless card 101 (and / or the virtual number generated for the contactless card 101).

[0041] Figure 3A shows a contactless card 101 which may include payment cards such as credit cards, debit cards, and / or gift cards. As shown, the contactless card 101 may be issued by a service provider 305 which is displayed on the front or back of the card 101. In some examples, the contactless card 101 may include an identification card, but is not limited to and is not related to a payment card. In some examples, the payment card may include a dual-interface contactless payment card. The contactless card 101 may include a substrate 310 which may include a single layer or one or more layers made of plastic, metal, and other materials. Exemplary substrate materials include polyvinyl chloride, polyvinyl chloride acetate, acrylonitrile butadiene styrene, polycarbonate, polyester, titanium anodized oxide, palladium, gold, carbon, paper, and biodegradable materials. In some examples, the contactless card 101 may have physical properties compliant with the ID-1 format of ISO / IEC 7810, or otherwise, the contactless card may comply with ISO / IEC 14443. However, the contactless card 101 described herein may have different characteristics, and it should be understood that this disclosure does not require the contactless card to be implemented as a payment card.

[0042] The contactless card 101 may also include identification information 315 displayed on the front and / or back of the card, and a contact pad 320. The contact pad 320 may be configured to establish contact with another communication device such as a mobile device 30, a user device, a smartphone, a laptop, a desktop, or a tablet computer. The contactless card 101 may also include processing circuits, an antenna, and other components not shown in Figure 3A. These components may be located behind the contact pad 320 or elsewhere on the substrate 310. The contactless card 101 may also include a magnetic strip or tape that may be located on the back of the card (not shown in Figure 3A).

[0043] As shown in Figure 3B, the contact pads 320 of the contactless card 101 may include a processing circuit 325 for storing and processing information, which may include a microprocessor 330 and memory 102. It is understood that the processing circuit 325 may include additional components, such as a processor, memory, error and parity / CRC checker, data encoder, collision avoidance algorithm, controller, command decoder, security primitive, and tamper-proof hardware, as necessary to perform the functions described herein.

[0044] Memory 102 may be read-only memory, write-once read-multiplex memory, or read / write memory, such as RAM, ROM, and EEPROM, and the contactless card 101 may include one or more of these memories. Read-only memory may be factory programmable as read-only or one-time programmable. One-time programmability provides multiple opportunities to read after a single write. Write-once read-multiplex memory may be programmed after the memory chip leaves the factory. Once programmed, the memory cannot be rewritten but can be read multiple times. Read / write memory may be programmed and reprogrammed multiple times after leaving the factory. Read / write memory may also be read multiple times after leaving the factory.

[0045] Memory 102 can be configured to store one or more applets 103, a counter 104, a master key 105, a distributed key 106, and one or more customer (or user) IDs 107. One or more applets 103 may include one or more software applications configured to run on one or more contactless cards, such as Java® card applets. However, it is understood that applet 103 is not limited to Java card applets and may instead be any software application capable of running on contactless cards or other devices with limited memory. Customer IDs 107 may include a unique alphanumeric identifier assigned to a user of a contactless card 101, the identifier allowing a user of a contactless card to be distinguished from other contactless card users. In some examples, customer IDs 107 may identify both a customer and the account assigned to that customer, and further identify the contactless card 101 associated with the customer's account. In some embodiments, applet 103 can use customer ID 107 as input to a cryptographic algorithm having keys 105 and / or 106 to generate encrypted customer ID 109.

[0046] The processor and memory elements in the exemplary embodiments described above are described with reference to the contact pads, but the disclosure is not limited thereto. It is understood that these elements may be mounted outside the pads 320, or completely separate from the pads, or may be mounted as additional elements in addition to the processor 330 and memory 102 elements located within the contact pads 320.

[0047] In some examples, the contactless card 101 may include one or more antennas 355. The one or more antennas 355 may be located inside the contactless card 101 and around the processing circuit 325 of the contact pad 320. For example, one or more antennas 355 may be integrated with the processing circuit 325, or one or more antennas 355 may be used with an external booster coil. In another example, one or more antennas 355 may be located outside the contact pad 320 and the processing circuit 325.

[0048] In one embodiment, the coil of the contactless card 101 can function as the secondary of an air-core transformer. A terminal can communicate with the contactless card 101 by disconnected power or amplitude modulation. The contactless card 101 can infer data transmitted from the terminal using the gap in the contactless card's power connection, which can be functionally maintained through one or more capacitors. The contactless card 101 can return communication by switching the load or load modulation of the contactless card's coil. Load modulation can be detected in the terminal's coil by interference. More generally, using an antenna 355, processing circuit 325, and / or memory 102, the contactless card 101 provides a communication interface for communication via NFC, Bluetooth, and / or Wi-Fi communication.

[0049] As described above, the contactless card 101 can be built on a software platform that can run on other devices with limited memory, such as a smart card or JavaCard, and can securely run one or more applications or applets. An applet can be added to the contactless card to provide a one-time password (OTP) for multi-factor authentication (MFA) in various mobile app-based use cases. The applet may be configured to respond to one or more requests, such as a near-field wireless data exchange request from a reader, such as a mobile NFC reader (e.g., the card reader 118 of device 110), and generate an NDEF message containing a cryptographically secure OTP encoded as an NDEF text tag.

[0050] The operation of the disclosed embodiments can be further described with reference to the following figures. Some of the figures may include logical flows. While such figures presented herein may include specific logical flows, it will be understood that the logical flows merely provide examples of how the general functions described herein may be implemented. Furthermore, unless otherwise indicated, a given logical flow does not necessarily have to be executed in the order presented. Moreover, a given logical flow may be implemented by hardware elements, software elements executed by a processor, or any combination thereof. Embodiments are not limited in this context.

[0051] Figure 4 shows an embodiment of the logical flow 400. The logical flow 400 may represent some or all of the operations performed by one or more embodiments described herein. For example, the logical flow 400 may include some or all of the operations for securely generating an account in a third-party application 115 using a contactless card 101. Embodiments are not limited in this context.

[0052] As shown in the figure, the logical flow 400 begins in block 405, where the third-party application 115 receives instructions to explicitly create a payment account using the contactless card 101. For example, the user can select GUI element 201 in Figure 2A, which explicitly prompts the user to create an account in the third-party application 115 using the contactless card 101. In block 410, the user can tap the contactless card 101 on the device 110 to cause the contactless card 101 to generate and transmit encrypted data (e.g., an encrypted customer ID 109). The user can tap the contactless card 101 in response to a notification output by the third-party application 115 that explicitly prompts the user to tap the contactless card 101 on the device 110. In block 415, the applet 103 can generate the encrypted customer ID 109. In block 420, the applet 103 can send the encrypted customer ID 109 to the mobile device 110.

[0053] In block 425, the mobile device 110 (e.g., OS 112 and / or third-party application 115) can send the encrypted customer ID 109 to the management application 123 of the server 120. The third-party application 115 can further send instructions indicating that the encrypted customer ID 109 is part of an attempt to create an account in the third-party application 115. In block 430, the mobile device 110 can receive a push notification from the management application 123. As described above, in some embodiments, the management application 123 can decrypt the encrypted customer ID 109 before sending the push notification to the mobile device 110. In block 435, the account application 113 is opened in response to the user selecting the push notification. As described above, in some embodiments, the user can provide credentials to access their account through the account application 113. The account application 113 can then request input to confirm whether the account creation attempted through the third-party application 115 is valid.

[0054] In block 440, the third-party application 115 can receive input indicating that the attempted account creation is valid. For example, the user can select GUI element 204 in Figure 2D. In block 445, the third-party application 115 can send a confirmation instruction to the management application 123. In block 450, the OS 112, the account application 113, and / or the third-party application 115 can receive instructions from the management application 123 indicating that the encrypted customer ID 109 has been verified and the account creation has been approved. As described above, the management application 123 can decrypt the encrypted customer ID 109 in response to its initial receipt (e.g., in block 425) and / or at a different time. For example, the management application 123 can decrypt the encrypted customer ID 109 in response to the receipt of the confirmation in block 450. Furthermore, the verification may include account data 154 of the user account associated with the contactless card 101.

[0055] In block 455, the third-party application 115 is opened (if it is not already displayed on the mobile device 110's display). In block 460, the third-party application 115 inputs the account data 154 received from the management application 123 into several form fields. The user can optionally edit the information automatically entered into the form fields by the third-party application 115. In block 465, the third-party application 115 creates the user's account using the account data 154 received from the management application 123. For example, the third-party application 115 can cause the third-party server 140 to create a new account record in its account data 144.

[0056] Figure 5 shows an embodiment of the logical flow 500. The logical flow 500 may represent some or all of the operations performed by one or more embodiments described herein. For example, the logical flow 500 may include some or all of the operations for securely and automatically entering data associated with the contactless card 101 into a form. Embodiments are not limited in this context.

[0057] As shown in the diagram, the logical flow 500 starts at block 510, where the third-party application 115 receives account data 154 from the management application 123. In block 520, the third-party application 115 enters the name received in the account data 154 into the name field of the form. In block 530, the third-party application 115 enters the last name from the received account data 154 into the last name field of the form. In block 535, the third-party application 115 enters the email address from the received account data 154 into the email address field of the form. In block 540, the third-party application 115 enters the address from the received account data 154 into the address field of the form.

[0058] In block 550, the third-party application 115 enters the account number from the received account data 154 into the account number field of the form. The account number may be the account number of the contactless card 101 and / or a virtual account number generated by the server 120. In block 560, the third-party application 115 enters the expiration date from the received account data 154 into the expiration date field of the form. The expiration date may be that of the contactless card 101 and / or a virtual account number. In block 570, the third-party application 115 enters the CVV from the received account data 154 into the CVV field of the form. The CVV may be that of the contactless card 101 and / or a virtual account number.

[0059] In some examples, this disclosure refers to tapping a contactless card. However, it is understood that this disclosure is not limited to tapping and may include other gestures, such as shaking a card or other movements.

[0060] Figure 6 shows an exemplary embodiment of the computing architecture 600, including a computing system 602 that may be suitable for implementing the various embodiments described above. In various embodiments, the computing architecture 600 may include or be implemented as part of an electronic device. In some embodiments, the computing architecture 600 may represent, for example, a system that implements one or more components of system 100. In some embodiments, the computing system 602 may represent, for example, the mobile device 110 and the server 120 of system 100. Embodiments are not limited in this context. More generally, the computing architecture 600 is configured to implement all the logic, applications, systems, methods, apparatus, and functions described herein with reference to Figures 1 to 5.

[0061] As used in this application, the terms “system,” “component,” and “module” are intended to refer to any computer-related entity, whether hardware, a combination of hardware and software, software, or software in operation, examples of which are provided by the exemplary computing architecture 600. For example, a component may be, but is not limited to, a process running on a computer processor, a computer processor, a hard disk drive, multiple storage drives (optical and / or magnetic storage media), an object, an executable file, an execution thread, a program, and / or a computer. For example, both an application running on a server and the server may be components. One or more components may reside within a process and / or an execution thread, components may be localized on one computer and / or distributed between two or more computers. Furthermore, components may be coupled together so as to be communicative with one another by various kinds of communication media to coordinate their operation. Coordination may include unidirectional or bidirectional exchange of information. For example, components may communicate information in the form of signals communicated over a communication medium. Information may be implemented as signals assigned to various signal lines. In such an assignment, each message is a signal. However, further embodiments may use data messages instead. Such data messages can be transmitted over a variety of connections. Illustrative connections include parallel interfaces, serial interfaces, and bus interfaces.

[0062] The computing system 602 includes various common computing elements such as one or more processors, multicore processors, coprocessors, memory units, chipsets, controllers, peripherals, interfaces, oscillators, timing devices, video cards, audio cards, multimedia input / output (I / O) components, and power supplies. However, embodiments are not limited to implementations by the computing system 602.

[0063] As shown in Figure 6, the computing system 602 includes a processor 604, system memory 606, and a system bus 608. The processor 604 can be any of a variety of commercially available computer processors, including, but not limited to, AMD® Athlon®, Duron®, and Opteron® processors, ARM® application, embedded, and secure processors, IBM® and Motorola® DragonBall® and PowerPC® processors, IBM and Sony® Cell processors, Intel® Celeron®, Core®, Core(2)Duo®, Itanium®, Pentium®, Xeon®, and XScale® processors, and similar processors. Dual microprocessors, multi-core processors, and other multiprocessor architectures can also be used as the processor 604.

[0064] The system bus 608 provides the processor 604 with interfaces for system components, including but not limited to the system memory 606. The system bus 608 can be one of several types of bus structures that can further interconnect to the memory bus, peripheral bus, and local bus (with or without a memory controller) using any of various commercially available bus architectures. Interface adapters can connect to the system bus 608 via slot architectures. Exemplary slot architectures may include, but are not limited to, Accelerated Graphics Port (AGP), CardBus, Industry Standard Architecture ((E)ISA), Micro Channel Architecture (MCA), NuBus, Peripheral Component Interconnect (Extensible) (PCI(X)), PCI Express, and the International Personal Computer Memory Card Association (PCMCIA).

[0065] The system memory 606 includes read-only memory (ROM), random access memory (RAM), dynamic RAM (DRAM), double data rate DRAM (DDRAM), synchronous DRAM (SDRAM), static RAM (SRAM), programmable ROM (PROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), flash memory (e.g., one or more flash arrays), polymer memory such as ferroelectric polymer memory, ovonic memory, phase change or ferroelectric memory, silicon oxide-nitride-oxide-silicon (SON) The system memory 606 may include various types of computer-readable storage media in the form of one or more high-speed memory units, such as OS memory, magnetic or optical cards, arrays of devices such as independent disk redundant array (RAID) drives, and solid-state memory devices (e.g., USB memory, solid-state drives (SSDs), and any other type of storage medium suitable for storing information). In the exemplary embodiment shown in Figure 6, the system memory 606 may include non-volatile memory 610 and / or volatile memory 612. The basic input / output system (BIOS) may be stored in the non-volatile memory 610.

[0066] The computing system 602 may include various types of computer-readable storage media in the form of one or more low-speed memory units, including an internal (or external) hard disk drive (HDD) 614, a magnetic floppy disk drive (FDD) 616 for reading and writing a removable magnetic disk 618, and an optical disk drive 620 for reading and writing a removable optical disk 622 (e.g., a CD-ROM or DVD). The HDD 614, FDD 616, and optical disk drive 620 may be connected to the system bus 608 by an HDD interface 624, an FDD interface 626, and an optical drive interface 628, respectively. The HDD interface 624 for external drive implementation may include at least one or both of the Universal Serial Bus (USB) and IEEE 1394 interface technologies. The computing system 602 is generally configured to implement all the logic, systems, methods, apparatus, and functions described herein with reference to Figures 1 to 5.

[0067] The drive and associated computer-readable media provide volatile and / or non-volatile storage of data, data structures, computer-executable instructions, etc. For example, several program modules, including an operating system 630, one or more application programs 632, other program modules 634, and program data 636, can be stored in the drive and memory units 610, 612. In one embodiment, the one or more application programs 632, other program modules 634, and program data 636 may include, for example, various applications and / or components of system 100, such as an operating system 112, an account application 113, a third-party application 115, a third-party server 140, account data 124, and a management application 123.

[0068] The user can input commands and information to the computing system 602 via one or more wired / wireless input devices, such as a keyboard 638 and a pointing device such as a mouse 640. Other input devices may include microphones, infrared (IR) remotes, radio frequency (RF) remotes, gamepads, stylus pens, card readers, dongles, fingerprint readers, gloves, graphics tablets, joysticks, keyboards, retina readers, touchscreens (e.g., capacitive, resistive, etc.), trackballs, trackpads, sensors, styluses, etc. These and other input devices are often connected to the processor 604 via an input device interface 642 coupled to the system bus 608, but can also be connected via other interfaces such as parallel ports, IEEE 1394 serial ports, game ports, USB ports, and IR interfaces.

[0069] Monitor 644 or other types of display devices are also connected to the system bus 608 via an interface such as a video adapter 646. Monitor 644 may be located inside or outside the computing system 602. In addition to Monitor 644, the computer typically includes other peripheral output devices such as speakers and printers.

[0070] The computing system 602 can operate in a network environment using logical connections via wired and / or wireless communication to one or more remote computers, such as remote computer 648. The remote computer 648 can be a workstation, server computer, router, personal computer, portable computer, microprocessor-based entertainment equipment, peer device, or other common network node, typically including many or all of the elements described with respect to computing system 602, but for brevity, only the memory / storage device 650 is shown. The illustrated logical connections include wired / wireless connections to a local area network (LAN) 652 and / or a larger network, such as a wide area network (WAN) 654. Such LAN and WAN networking environments are common in offices and enterprises, facilitating enterprise-scale computer networks such as intranets, all of which can connect to global communication networks such as the Internet. In embodiments, the network 130 in Figure 1 is one or more of the LAN 652 and WAN 654.

[0071] When used in a LAN networking environment, the computing system 602 is connected to the LAN 652 via a wired and / or wireless network interface or adapter 656. The adapter 656 can facilitate wired and / or wireless communication to the LAN 652, and this may also include a wireless access point placed on it to communicate with the wireless capabilities of the adapter 656.

[0072] When used in a WAN networking environment, the computing system 602 may include a modem 658, or be connected to a communication server on the WAN 654, or have other means for establishing communication on the WAN 654 via the Internet or the like. The modem 658 may be internal or external and wired and / or wireless, and connect to the system bus 608 via the input device interface 642. In a network environment, program modules shown with respect to the computing system 602 or a part thereof may be stored in a remote memory / storage device 650. The illustrated network connection is illustrative, and it will be understood that other means may be used to establish communication links between computers.

[0073] Computing system 602 is capable of communicating with wired and wireless devices or entities using the IEEE 802 standard family, such as wireless devices configured to operate in wireless communication (e.g., IEEE 802.16 wireless modulation technology). This includes, among other things, at least Wi-Fi (or Wireless Fidelity), WiMAX, and Bluetooth® wireless technologies. Thus, communication can be a predefined structure, similar to conventional networks, or simply ad-hoc communication between at least two devices. Wi-Fi networks provide secure, reliable, and high-speed wireless connectivity using wireless technologies called IEEE 802.11x (a, b, g, n, etc.). Using Wi-Fi networks, computers can be connected to each other, to the Internet, and to wired networks (using IEEE 802.3 related media and functions).

[0074] Various embodiments can be implemented using hardware elements, software elements, or a combination of both. Examples of hardware elements may include processors, microprocessors, circuits, circuit elements (e.g., transistors, resistors, capacitors, inductors, etc.), integrated circuits, application-specific integrated circuits (ASICs), programmable logic devices (PLDs), digital signal processors (DSPs), field-programmable gate arrays (FPGAs), logic gates, registers, semiconductor devices, chips, microchips, chipsets, etc. Examples of software may include software components, programs, applications, computer programs, application programs, system programs, machine programs, operating system software, middleware, firmware, software modules, routines, subroutines, functions, methods, procedures, software interfaces, application program interfaces (APIs), instruction sets, computing code, computer code, code segments, computer code segments, words, values, symbols, or any combination thereof. The decision of whether an embodiment is implemented using hardware and / or software elements may vary depending on any number of factors, such as desired computing speed, power level, heat resistance, processing cycle budget, input data rate, output data rate, memory resources, data bus speed, and other design or performance constraints.

[0075] One or more aspects of at least one embodiment may be implemented by representative instructions stored in a machine-readable medium representing various logics within a processor, which, when read by a machine, create logic for performing the techniques described herein. Such representations, known as "IP cores," may be stored in tangible machine-readable medium and supplied to various customers or manufacturing facilities for loading into manufacturing machines that create logic or processors. Some embodiments may be implemented using, for example, a machine-readable medium or article that can store instructions or sets of instructions that, when executed by a machine, cause a machine to perform the methods and / or operations according to the embodiment. Such machines may include, for example, any suitable processing platform, computing platform, computing device, processing device, computing system, processing system, computer, processor, etc., and may be implemented using any suitable combination of hardware and / or software. Machine-readable media or articles can 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, such as memory, removable or non-removable media, erasable or non-erasable media, writable or rewritable media, digital or analog media, hard disks, floppy disks, compact disc read-only memory (CD-ROM), recordable compact disc (CD-R), rewritable compact disc (CD-RW), optical discs, magnetic media, magneto-optical media, removable memory cards or disks, various types of digital multi-purpose discs (DVDs), tapes, cassettes, etc. Instructions can include any suitable type of code, such as source code, compiled code, interpreted code, executable code, static code, dynamic code, encrypted code, etc., implemented using any suitable high-level, low-level, object-oriented, visual, compiled and / or interpreted programming language.

[0076] The foregoing description of exemplary embodiments is presented for illustrative and explanatory purposes only. It is not intended to be exhaustive or to limit this disclosure to the exact form disclosed. Many modifications and variations are possible in light of this disclosure. The scope of this disclosure is intended to be limited not by this detailed description, but rather by the appended claims. Future applications claiming priority to this application may claim subject matter disclosed in different ways and may generally include any set of one or more limitations disclosed or otherwise demonstrated herein in various ways.

Claims

1. It is a system, Processor and A memory for storing instructions, and when an instruction is executed by the processor, the processor, In response to a request to create a payment account in the payment application, the system receives encrypted data from a contactless card, and Transmitting the encrypted data to the server associated with the contactless card, Receiving notifications from the aforementioned server, In response to receiving the aforementioned notification, open the account application associated with the contactless card, The payment application receives confirmation input to generate the payment account using the contactless card, Sending the confirmation input instructions to the server, In response to the payment application receiving verification of the encrypted data from the server, the payment application is opened. Entering account data received from the server into a field displayed in the payment application, wherein the account data pertains to the account associated with the contactless card. A system that generates a payment account using the account data received from the server and entered into the field.

2. The memory stores instructions, and when an instruction is executed by the processor, the processor receives the instructions. The account data entered in the aforementioned field is submitted to the payment application account server, The system according to claim 1, which receives an instruction from the payment application account server indicating that a record of the payment account has been generated and stored in the payment application account database.

3. The processor further comprises: Receiving instructions that explicitly cause the payment application to generate the payment account using the contactless card, the payment application being executed by the processor, and receiving The system outputs an instruction on its display to tap the contactless card, Make it run, The system according to claim 1, wherein the received account data of the account includes (i) first name, (ii) last name, (iii) email address, (iv) address, (v) account number of the contactless card, (vi) expiration date of the contactless card, and (vii) card verification value (CVV) of the contactless card.

4. The memory stores instructions, and when an instruction is executed by the processor, the processor receives the instructions. Enter the aforementioned name into the name field of the aforementioned field, Enter the aforementioned surname into the surname field of the aforementioned field, Enter the email address in the email address field of the aforementioned field, Entering the address in the address field of the aforementioned field, Enter the account number in the account number field of the aforementioned field, Enter the expiration date in the expiration date field of the aforementioned field, The system according to claim 3, which causes the user to input the CVV into the CVV field of the aforementioned field.

5. The received account data of the account includes a virtual account number generated for the account associated with the contactless card, the expiration date of the virtual account number, and the card verification value (CVV) of the virtual account number, the memory stores instructions, and when the instructions are executed by the processor, the processor receives Enter the virtual account number in the account number field of the aforementioned field, Enter the expiration date in the expiration date field of the aforementioned field, The system according to claim 1, which causes the user to input the CVV into the CVV field of the aforementioned field.

6. The encrypted data is transmitted to the API of the server associated with the contactless card via a Hypertext Transfer Protocol Secure (HTTPS) Application Programming Interface (API) call, the memory stores the instruction, and when the instruction is executed by the processor, the processor receives the instruction. The system according to claim 1, which receives input that explicitly requests the submission of account data in order to generate the payment account.

7. The system according to claim 1, wherein the encrypted data is received from the contactless card based on the contactless card coming within the communication range of the system's card reader.

8. A non-temporary computer-readable storage medium for storing computer-readable program code executable by a processor, wherein the computer-readable program code is stored in the processor, In response to a request to create a payment account in the payment application, the system receives encrypted data from a contactless card, and Transmitting the encrypted data to the server associated with the contactless card, Receiving notifications from the aforementioned server, In response to receiving the aforementioned notification, open the account application associated with the contactless card, The payment application receives confirmation input to generate the payment account using the contactless card, Sending the confirmation input instructions to the server, In response to the payment application receiving verification of the encrypted data from the server, the payment application is opened. The payment application enters the account data received from the server into a field displayed in the payment application, wherein the account data relates to the account associated with the contactless card. A non-temporary computer-readable storage medium that causes the following to be performed: generating the payment account using the account data received from the server and entered into the field.

9. The processor stores computer-readable program code that can be executed by the processor, and the computer-readable program code is provided to the processor. The account data entered in the aforementioned field is submitted to the payment application account server, The non-temporary computer-readable storage medium according to claim 8, which causes the payment application account server to receive an instruction indicating that a record of the payment account has been generated and stored in the payment application account database.

10. The processor further comprises: Receiving instructions that explicitly cause the payment application to generate the payment account using the contactless card, the payment application being executed by the processor, and receiving Outputting an instruction to tap the contactless card on the display of the system including the processor, Make it run, The non-temporary computer-readable storage medium according to claim 8, wherein the received account data of the account includes (i) first name, (ii) last name, (iii) email address, (iv) address, (v) account number of the contactless card, (vi) expiration date of the contactless card, and (vii) card verification value (CVV) of the contactless card.

11. The processor stores computer-readable program code that can be executed by the processor, and the computer-readable program code is provided to the processor. Enter the aforementioned name into the name field of the aforementioned field, Enter the aforementioned surname into the surname field of the aforementioned field, Enter the email address in the email address field of the aforementioned field, Entering the address in the address field of the aforementioned field, Enter the account number in the account number field of the aforementioned field, Enter the expiration date in the expiration date field of the aforementioned field, A non-temporary computer-readable storage medium according to claim 10, which causes the input of the CVV into the CVV field of the aforementioned field.

12. The received account data of the account includes a virtual account number generated for the account associated with the contactless card, the expiration date of the virtual account number, and a card verification value (CVV) of the virtual account number, the medium stores computer-readable program code executable by the processor, and the computer-readable program code is transmitted to the processor, Enter the virtual account number in the account number field of the aforementioned field, Enter the expiration date in the expiration date field of the aforementioned field, A non-temporary computer-readable storage medium according to claim 8, which causes the input of the CVV into the CVV field of the aforementioned field.

13. The encrypted data is transmitted to the API of the server associated with the contactless card via a Hypertext Transfer Protocol Secure (HTTPS) Application Programming Interface (API) call, the medium stores computer-readable program code executable by the processor, and the computer-readable program code is transmitted to the processor, A non-temporary computer-readable storage medium according to claim 8, which receives input that explicitly requests the submission of account data in order to generate the payment account.

14. The non-temporary computer-readable storage medium according to claim 8, wherein the encrypted data is received from the contactless card based on the contactless card coming within the communication range of the card reader of the device including the processor.

15. It is a method, In response to a request to create a payment account in the payment application, the system receives encrypted data from a contactless card, and Transmitting the encrypted data to the server associated with the contactless card, Receiving notifications from the aforementioned server, In response to receiving the aforementioned notification, open the account application associated with the contactless card, The payment application receives confirmation input to generate the payment account using the contactless card, Sending the confirmation input instructions to the server, In response to the payment application receiving verification of the encrypted data from the server, the payment application is opened. Entering account data received from the server into a field displayed in the payment application, wherein the account data pertains to the account associated with the contactless card. A method comprising generating the payment account using the account data received from the server and entered into the fields.

16. Submitting the account data entered in the field to the payment application account server, The system further includes receiving instructions from the payment application account server indicating that a record for the payment account has been generated and stored in the payment account database. The method according to claim 15.

17. Receiving instructions that specify the use of the contactless card to generate the payment account in the payment application, wherein the payment application is executed by a processor, The system further includes outputting an instruction on the display of the system including the processor to tap the contactless card, The method according to claim 15, wherein the received account data of the account includes (i) first name, (ii) last name, (iii) email address, (iv) address, (v) account number of the contactless card, (vi) expiration date of the contactless card, and (vii) card verification value (CVV) of the contactless card.

18. Entering the name into the name field of the field, Enter the aforementioned surname into the surname field of the aforementioned field, Enter the email address in the email address field of the aforementioned field, Entering the address in the address field of the aforementioned field, Enter the account number in the account number field of the aforementioned field, Enter the expiration date in the expiration date field of the aforementioned field, This further includes entering the CVV into the CVV field of the aforementioned field, The method according to claim 17.

19. The received account data of the account includes a virtual account number generated for the account associated with the contactless card, the expiration date of the virtual account number, and the card verification value (CVV) of the virtual account number, and the method is Enter the virtual account number in the account number field of the aforementioned field, Enter the expiration date in the expiration date field of the aforementioned field, The method according to claim 15, further comprising inputting the CVV into the CVV field of the field.

20. The encrypted data is transmitted to the API of the server associated with the contactless card via a Hypertext Transfer Protocol Secure (HTTPS) Application Programming Interface (API) call, and the encrypted data is received from the contactless card based on the contactless card coming within range of the card reader of the device on which the payment application is running, and the method The method of claim 15, further comprising receiving an input that explicitly requests the submission of account data in order to generate the payment account.

Images