Account registration using a contactless card

Abstract

Account registration is performed using a contactless card. The payment app running on the device can receive a request to generate a payment account using a contactless card. The payment app can receive encrypted data from the contactless card and transmit the encrypted data to a server associated with the contactless card. The device can receive a push notification from the server and, in response to the push notification, open the account app associated with the contactless card. The account app can receive confirmation of generating a payment account using the contactless card and transmit the confirmation to the server. The device can open the payment app in response to verification of encrypted data received from the server. The payment app can use the account data received from the server to fill in form fields and use the account data received from the server and filled in the form fields to generate the payment account.

Description

[0001] Related applications

[0002] This application claims priority to U.S. Patent Application Serial No. 16 / 726,366, filed December 24, 2019, entitled "Account Registration Using a Contactless Card". The contents of the aforementioned application are incorporated herein by reference in their entirety. Technical Field

[0003] The embodiments described herein generally relate to computing platforms, and more specifically, to the use of contactless cards to register accounts. Background Technology

[0004] Third-party payment services allow users to make payments using different payment accounts. However, using payment accounts to register accounts through third-party payment services may expose security risks. For example, malicious users may attempt to use compromised information about the user and / or the user's payment account to create fraudulent accounts through third-party payment services. Consequently, third-party payment services and / or institutions associated with payment accounts may be unable to distinguish between legitimate attempts to create third-party payment accounts and fraudulent attempts. Summary of the Invention

[0005] The embodiments disclosed herein provide systems, methods, articles of art, and computer-readable media for automatically filling card data into a form on a computing device by tapping. According to one example, a payment application running on the device can receive an instruction specifying the use of a contactless card to generate a payment account using the payment application. The payment application can output an instruction specifying a tap on the contactless card. The device can receive encrypted data from a communication interface of the contactless card, the encrypted data being based on a customer identifier and a private key associated with the contactless card. The device can transmit the encrypted data to a server associated with the contactless card and receive a push notification from the server. The device can open an account application associated with the contactless card in response to receiving an option for the push notification. The account application can receive confirmation input specifying the use of the contactless card to generate a payment account using the payment application. The account application can transmit an instruction to the server confirming the input. The device can open the payment application in response to verification that the payment application receives encrypted data from the server. The payment application can use the account data received from the server to fill multiple form fields of a form displayed in the payment application, the account data of which is associated with the contactless card. Payment applications can generate payment accounts using account data received from the server and filled into multiple form fields. Attached Figure Description

[0006] Figures 1A to 1EAn embodiment of a system for generating accounts using contactless cards is shown.

[0007] Figures 2A to 2G An example of account generation using contactless cards is shown.

[0008] Figures 3A to 3B An example contactless card is shown.

[0009] Figure 4 An embodiment of the first logic flow is shown.

[0010] Figure 5 An embodiment of the second logic flow is shown.

[0011] Figure 6 An example of a computing architecture is shown. Detailed Implementation

[0012] The embodiments disclosed herein provide security techniques for generating accounts using contactless cards. The account can be a third-party payment account used to provide third-party payment services for use on a computing device by a third-party payment application. The payment account associated with a contactless card provided by a financial institution can be used to fund transactions using the third-party payment account. When attempting to register an account using a third-party payment application, the user can select the option to securely generate an account using a contactless card. In response, the third-party payment application can output an instruction to tap the contactless card on the device. The user can then tap the contactless card on the device. The device can then instruct the contactless card to generate encrypted data and transmit it to the device. The data generated by the contactless card can be encrypted using key diversification. The device can transmit the encrypted data received from the contactless card to a first server associated with the financial institution providing the contactless card.

[0013] The first server can verify encrypted data received from the contactless card by decrypting the encrypted data. The first server can then transmit a push notification to the device. The device can output the push notification for display on a screen. In response to a user-selected notification, an account application provided by a financial institution can be opened on the device. 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 confirm whether the attempted account generation using a third-party payment application is valid. If the user provides input indicating that the account generation is invalid, third-party account generation can be restricted to maintain the security of the account associated with the contactless card. Otherwise, the account application can transmit an indication to the first server that the user has confirmed the validity of the attempted account generation using the third-party payment application.

[0014] The device can output a third-party payment application for display. The third-party payment application can receive account data associated with the contactless card from a first server. 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 received account data into corresponding form fields provided by the third-party payment application. In response to receiving user input specifying the creation of an account, the third-party payment application can use the data received from the server to create an account. The record of the created account can be stored on a second server associated with the third-party payment application. The user can then use the third-party payment application and the underlying account associated with the contactless card to make purchases.

[0015] Advantageously, this approach enhances the security of all devices and associated data. For example, verification of encrypted data by the first server provides additional protection against fraudulent activity by confirming that the user attempting to create an account possesses a contactless card. This further confirms that the contactless card is not fraudulent, as fraudulent cards are unlikely to generate encrypted data that can be verified by the server. Furthermore, conventional methods require users to manually enter account data into forms. However, this could allow other users or devices to capture card data while the user is entering it into the form. By eliminating the need for users to manually enter card data into forms, the security of account data is enhanced.

[0016] Referring generally to the notation and nomenclature used herein, one or more portions of the following detailed description may be presented according to program procedures executed on a computer or computer network. These procedures are described and represented by those skilled in the art to most effectively communicate the substance of their work to others skilled in the art. A program herein is, and is generally considered, a self-consistent sequence of operations that leads to the desired result. These operations are those that require physical manipulation of physical quantities. Typically, though not always, these quantities take the form of electrical, magnetic, or optical signals that can be stored, transmitted, combined, compared, and otherwise manipulated. It is sometimes convenient to refer to these signals as bits, values, elements, symbols, characters, items, numbers, etc., primarily for general reasons. However, it should be noted that all these and similar terms are associated with appropriate physical quantities and are merely convenient labels applied to those quantities.

[0017] Furthermore, these operations are often referred to by terms such as addition or comparison, which are generally associated with mental operations performed by a human operator. However, in any of the operations described herein that form part of one or more embodiments, such capability of a human operator is not necessary, or in most cases not desirable. Rather, these operations are machine operations. Useful machines for performing the operations of the various embodiments include digital computers selectively activated or configured by computer programs stored therein and written in accordance with the teachings herein, and / or include means specifically constructed for the desired purpose or for the digital computer. The various embodiments also relate to means or systems for performing these operations. These means can be specifically constructed for the desired purpose. The desired structure of the various such machines will be apparent from the given description.

[0018] Referring now to the accompanying drawings, wherein the same reference numerals are consistently used to refer to the same elements. In the following description, numerous specific details are set forth for purposes of explanation in order to provide a thorough understanding thereof. However, it will be apparent, however, that novel embodiments may be practiced without these specific details. In other instances, well-known structures and devices are shown in block diagram form for the purpose of description. The intention is to cover all modifications, equivalents, and alternatives within the scope of the claims.

[0019] Figure 1A A schematic diagram of an exemplary system 100 consistent with the disclosed embodiments is depicted. As shown, system 100 includes one or more contactless cards 101, one or more mobile devices 110, server 120, and third-party server 140. The contactless card 101 represents any type of payment card, such as a credit card, debit card, ATM card, gift card, etc. The contactless card 101 may include one or more chips (not depicted), such as a radio frequency identification (RFID) chip, which is 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 example 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, wearable device, laptop, portable gaming device, etc. Servers 120 and 140 represent any type of computing device, such as a server, workstation, computing cluster, cloud computing platform, virtualized computing system, etc.

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

[0021] 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 can register to create an account using third-party application 115 and add contactless card 101 as a payment source. This allows the user to make purchases using third-party application 115 with contactless card 101 (and / or the account associated with contactless card 101) as a form of payment. Examples of third-party applications 115 include, but are not limited to, PayPal®, Venmo®, Apple® Pay, Samsung® Pay, Google® Pay, etc. Advantageously, the embodiments disclosed herein provide security techniques for creating an account using third-party application 115 when contactless card 101 is used as a payment source. Third-party server 140 may be associated with a given third-party application 115. Third-party server 140 may typically include a database of account data 144 for user accounts. Account data 144 may include user biometrics, address information, payment information, account number, account expiration date, CVV, login credentials, and any other types of account and / or personal data for multiple users.

[0022] As shown, the memory 102 of the contactless card 101 includes a program 103, a counter 104, a master key 105, a multi-key 106, and a unique customer identifier (ID) 107. The customer ID 107 can uniquely identify a user and / or user account using the financial institution providing the contactless card 101. The program 103 can be executed on the processor (not shown) of the contactless card 101 to perform various functions described in more detail herein.

[0023] As shown, server 120 includes a data storage device 124 and a memory 122 for account data. Account data 124 includes account-related data for multiple users and / or accounts. Account data 124 may include at least a master key 105, a counter 104, a customer ID 107, an associated contactless card 101 (including account number, expiration date, and CVV), account holder name, account billing address, one or more shipping addresses, one or more virtual card numbers, and biometric information for each account. Memory 122 includes an application 123 and instances of counter 104, master key 105, and diversity keys 106 for one or more accounts from account data 124.

[0024] As stated, the contactless card 101 can be used, at least in part, to create an account in account data 144 of a third-party server 140 using a third-party application 115. Generally, a user of the third-party application 115 can specify the use of the contactless card 101 to create a new account. This causes the third-party application 115 to output an instruction specifying a tap on the contactless card 101 on the device 110. This brings the contactless card 101 into the communication range of the card reader 118 of the mobile device 110 and causes applet 103 to generate an encrypted customer ID 109. Applet 103 can use any number of techniques to generate the encrypted customer ID 109 based on cryptographic algorithms and the customer ID 107.

[0025] As stated herein, system 100 is configured to implement key diversification to protect data, which may be referred to herein as key diversification techniques. Generally, server 120 (or another computing device) and contactless cards 101 may share the same master key 105 (also known as a master symmetric key). More specifically, each contactless card 101 is programmed with a different master key 105, which has a corresponding pair within server 120. For example, when manufacturing contactless cards 101, a unique master key 105 may be programmed into the memory 102 of the contactless card 101. Similarly, the unique master key 105 may be stored in the account data 124 of server 120 in the records of customers associated with contactless cards 101 (and / or stored in a different secure location, such as a hardware security module (HSM) 125). The master key 105 can be kept secret from all parties except for the contactless cards 101 and server 120, thereby enhancing the security of system 100. In some embodiments, the applet 103 of the contactless card 101 can use the master key 105 and data as input to a cryptographic algorithm to encrypt and / or decrypt data (e.g., customer ID 107). For example, encrypting customer ID 107 using the master key 105 can produce an encrypted customer ID 109. Similarly, the authentication server 120 can use the corresponding master key 105 to encrypt and / or decrypt data associated with the contactless card 101.

[0026] In other embodiments, the master key 105 of the contactless card 101 and server 120 can be used in conjunction with a counter 104 to enhance security using key diversification. The counter 104 includes a value synchronized between the contactless card 101 and server 120. The counter value 104 can include a number that changes whenever data is exchanged between the contactless card 101 and server 120 (and / or the contactless card 101 and mobile device 110). When ready to send data (e.g., to server 120 and / or 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 that produces a diversification key 106 as output. The cryptographic algorithm can include encryption algorithms, hash-based message authentication code (HMAC) algorithms, cipher-based message authentication code (CMAC) algorithms, etc. Non-limiting examples of cryptographic algorithms may include symmetric encryption 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 diversification techniques are described in more detail in U.S. Patent Application 16 / 205,119, filed November 29, 2018. The aforementioned patent application is incorporated herein by reference in its entirety.

[0027] Continuing with the key diversification example, the contactless card 101 can then use a diversification key 106 and data as input to a cryptographic algorithm to encrypt the customer ID 107. For example, encrypting the customer ID 107 using the diversification key 106 can produce an encrypted customer ID 109.

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

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

[0030] Regardless of the decryption technique used, management application 123 can decrypt the encrypted customer ID 109 to verify it (e.g., by comparing the obtained customer ID 107 with the customer ID stored in account data 124, and / or based on an indication of successful decryption using keys 105 and / or 106). Although keys 105 and 106 are depicted as being stored in memory 122, they can be stored elsewhere, such as in a secure element and / or HSM 125. In such an embodiment, the secure element and / or HSM 125 can use keys 105 and / or 106 along with cryptographic functions to decrypt the encrypted customer ID 109. Similarly, the secure element and / or HSM 125 can generate a diversification key 106 based on the master key 105 and counter value 104, as described above.

[0031] However, if the management application 123 cannot decrypt the encrypted customer ID 109 to produce the expected result (e.g., customer ID 107 of the account associated with contactless card 101), then the management application 123 does not verify the encrypted customer ID 109. In such an example, the management application 123 transmits an indication of failed verification to the third-party application 115. Thus, the third-party application 115 can avoid generating the requested account to maintain the security of the account associated with contactless card 101. Generally, the management application 123 can make the successful decryption of the encrypted customer ID 109 a condition for any operation.

[0032] Figure 1BAn embodiment is depicted in which management application 123 has verified the encrypted customer ID 109. More specifically, as shown, in response to verification (e.g., decryption) of the encrypted customer ID 109, management application 123 transmits a push notification 150 to mobile device 110. Notification 150 may typically indicate that an attempted account generation using third-party application 115 requires verification. OS 112 may output notification 150 for display on the display of mobile device 110. The user may tap or otherwise select notification 150, causing account application 113 to appear on mobile device 110. The user can then provide authentication credentials to access the account associated with contactless card 101. Once authenticated, account application 113 may request user verification (or confirmation) for the requested account generation. If the user refuses to verify the requested account generation, account generation is restricted to protect security.

[0033] Figure 1C An embodiment in which a user verifies a requested account creation via account application 113 is described. Once the user verifies the requested account creation, account application 113 can transmit confirmation 151 to server 120. Confirmation 151 can be sent to an API provided by management application 123 via an HTTPS API call.

[0034] Figure 1D An embodiment is depicted in which management application 123 has received confirmation 151 from mobile device 110. As shown, management application 123 transmits verification 153, including account data 154, to third-party application 115. Verification 153 can typically instruct the account to generate a third-party application 115 that has been securely verified. Management application 123 can typically transmit verification 153 in response to receiving confirmation 151 and based on successful decryption of the encrypted customer ID 109. Although references Figure 1A / 1B discusses the decryption of the encrypted customer ID 109, but the management application 123 may attempt to decrypt the encrypted customer ID 109 at any time (such as after receiving confirmation 151).

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

[0036] Once received, the third-party application 115 can automatically populate (or add) account data 154 into multiple form fields of the form output by the third-party application 115. For example, first name / last name can be populated into the first name / last name field of the form, email address can be populated into the email address field of the form, parts of the address (e.g., street address, city, state, ZIP code) can be populated into one or more address fields of the form, account number can be populated into the account number field of the form, account expiry date can be populated into the expiry date field of the form, and CVV can be populated into the CVV field of the form. The user can then review and submit the form via the third-party application 115 to complete the 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 avoid displaying one or more elements of the account data, such as the account number.

[0037] Figure 1E An embodiment is depicted where a user has submitted a form via a third-party application 115. As shown, the third-party application 115 may transmit an instruction to a third-party server 140 for a new account 155, including account data 154. In some embodiments, the new account 155 is created by the third-party application 115. In other embodiments, the third-party application 115 transmits 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 for the new account 155 using account data 154 may be generated in the account database 144 of the third-party server 140.

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

[0039] Figure 2A This is a schematic diagram 200 depicting an example embodiment of account generation using contactless card 101. The graphical user interface (GUI) of a third-party application 115 on mobile device 110 provides GUI elements 201 that allow the user to generate an account using contactless card 101 via the third-party application 115. When the user selects GUI 201, the third-party application 115 can output instructions 202 specifying a tap on the contactless card 101 on device 110, such as... Figure 2B As depicted in diagram 210.

[0040] like Figure 2B As shown, a user can tap the contactless card 101 on device 110. Once the user taps the contactless card 101 on device 110, a mini-program 103 on the contactless card 101 generates an encrypted customer ID 109. The mini-program 103 can then transmit the encrypted customer ID 109 to device 110, for example, via NFC. Once received, a third-party application 115 can transmit the encrypted customer ID 109 to management application 123, for example, via an HTTPS API call.

[0041] Figure 2C The schematic diagram 220 depicts a push notification 203 output for display on mobile device 110. As stated, management application 123 may generate push notification 203 in response to receiving and / or verifying an encrypted customer ID 109. Management application 123 may then transmit push notification 203 to mobile device 110. Once the user selects push notification 203, account application 113 can be opened on mobile device 110.

[0042] Figure 2D This is a schematic diagram 230 illustrating an embodiment where the user selects push notification 203. (See diagram 230 for details.) Figure 2DAs shown, account application 113 is opened on mobile device 110. Account application 113 typically notifies the user that an attempt to open the account using third-party application 115 has been detected. Account application 113 may provide GUI element 204 to allow the user to confirm (or verify) that the attempt is valid, for example, initiated by a user associated with the account. As stated, in some embodiments, in the output Figure 2D Before the GUI is displayed, the user may need to provide authentication credentials to the account application 113. If the user wishes to confirm, the user can select GUI element 204. Otherwise, the user can select GUI element 224, which restricts the creation of new accounts via third-party application 115. The account application 113 can transmit the instructions for the selected GUI elements 204 and 224 to the management application 123.

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

[0044] As shown, third-party application 115 may include form fields 205 to 209 and 211. Third-party application 115 has automatically populated form fields 205 to 209 and 211 using account data 154 received from management application 123. For example, as shown, the first name has been filled into the first name field 205, the last name has been filled into the last name field 206, the email address has been filled into the email address field 207, the street address has been filled into the street address field 208, and additional address information has been filled into the address information field 209. Figure 2E The specific values ​​depicted are exemplary and should not be considered as limiting the scope of this disclosure. In some embodiments, the user may optionally modify the values ​​entered into form fields 205 to 209 and 211. The user can then select the Next button 212 to continue.

[0045] Figure 2FIt shows where the user has already selected Figure 2E A schematic diagram of embodiment 250 of the Next button 212 is shown. As illustrated, third-party application 115 outputs form fields 213 to 215. Third-party application 115 has filled in the card number in card number field 213, the expiration date in expiration date field 214, and the CVV in CVV field 215. Although depicted as separate parts of a form, in one embodiment, form fields 205 to 209, 211, and 213 to 215 may be part of a single form. As stated, the account may be the primary account or a virtual account of contactless card 101. The user can then select the Next button 216 to continue account generation.

[0046] Figure 2G It shows where the user selects Figure 2F The next button 216 is shown in 260, illustrating an embodiment of using the third-party application 115 to complete account setup. 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 a virtual number generated for the contactless card 101).

[0047] Figure 3A A contactless card 101 is shown, 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 displayed on the front or back of the card 101. In some examples, the contactless card 101 is not a payment card and may include, but is not limited to, an identification 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 laminates made of plastic, metal, and other materials. Exemplary substrate materials include polyvinyl chloride, polyvinyl chloride acetate, acrylonitrile butadiene styrene, polycarbonate, polyester, anodized titanium, palladium, gold, carbon, paper, and biodegradable materials. In some examples, the contactless card 101 may have physical properties conforming to the ID-1 format of the ISO / IEC 7810 standard, and the contactless card may additionally conform to the ISO / IEC 14443 standard. However, it should be understood that the contactless card 101 according to this disclosure may have different characteristics, and this disclosure does not require the implementation of contactless cards in payment cards.

[0048] 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 a connection with another communication device, such as a mobile device 30, user equipment, smartphone, laptop, desktop computer, or tablet computer. The contactless card 101 may also include a processing circuitry, an antenna, and... Figure 3A Other components not shown. These components may be located behind the contact pad 320 or elsewhere on the base 310. The contactless card 101 may also include components that can be located on the back of the card ( Figure 3A (Not shown in the image) Magnetic strips or magnetic tapes.

[0049] like Figure 3B As shown, the contact pad 320 of the contactless card 101 may include a processing circuitry system 325 for storing and processing information, which includes a microprocessor 330 and a memory 102. It should be understood that the processing circuitry system 325 may include additional components necessary to perform the functions described herein, including a processor, memory, error and parity / CRC checkers, a data encoder, anti-collision algorithms, a controller, a command decoder, security primitives, and tamper-proof hardware.

[0050] Memory 102 can be a read-only memory, a write-once-read-many memory, or a read / write memory, such as RAM, ROM, and EEPROM, and the contactless card 101 can include one or more of these memories. Read-only memory can be factory-programmable or one-time programmable. One-time programmability provides the opportunity to write once and then read many times. Write-once / read-many memory can be programmed at some point after the memory chip has left the factory. Once programmed, the memory may not be rewritten, but it may be read multiple times. Read / write memory can be programmed and reprogrammed multiple times after leaving the factory. Read / write memory can also be read multiple times after leaving the factory.

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

[0052] The processor and storage elements of the foregoing exemplary embodiments have been described with reference to the contact pad, but this disclosure is not limited thereto. It should be understood that these elements may be implemented outside of the pad 320, or completely separated from the pad, or as other elements besides the processor 330 and memory 102 elements located within the contact pad 320.

[0053] In some examples, the contactless card 101 may include one or more antennas 355. The one or more antennas 355 may be housed within the contactless card 101 and surrounding the processing circuitry system 325 of the contact pad 320. For example, the one or more antennas 355 may be integrated with the processing circuitry system 325, and the one or more antennas 355 may be used in conjunction with an external boost coil. As another example, the one or more antennas 355 may be external to the contact pad 320 and the processing circuitry system 325.

[0054] In this embodiment, the coil of the contactless card 101 can act as the secondary coil of an air-core transformer. The terminal can communicate with the contactless card 101 by cutting off power or by amplitude modulation. The contactless card 101 can infer data transmitted from the terminal using gaps in the power connection of the contactless card, which can be functionally maintained by one or more capacitors. The contactless card 101 can communicate by switching the load or load modulation on the coil of the contactless card. Load modulation can be detected in the terminal coil by interference. More generally, using antenna 355, processing circuitry 325, and / or memory 102, the contactless card 101 provides a communication interface for communication via NFC, Bluetooth, and / or Wi-Fi.

[0055] As explained above, the contactless card 101 can be built on a software platform that operates on smart cards or other devices with limited memory, such as JavaCards, and can securely execute one or more applications or applets. Applets can be added to the contactless card to provide a one-time password (OTP) for multifactor authentication (MFA) in various mobile application-based use cases. The appletter can 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., reader 118 of device 110) and generate an NDEF message that includes a cryptographically secure OTP encoded as an NDEF text tag.

[0056] The operation of the disclosed embodiments can be further described with reference to the following accompanying drawings. Some of the drawings may include logical flows. Although these figures presented herein may include specific logical flows, it is understood that these logical flows merely provide examples of how the general functionality described herein can be implemented. Furthermore, the given logical flows do not necessarily have to be executed in the order presented unless otherwise stated. Additionally, the given logical flows may be implemented by hardware elements, software elements executed by a processor, or any combination thereof. The embodiments are not limited to this context.

[0057] Figure 4 An embodiment of logic flow 400 is illustrated. Logic flow 400 may represent some or all of the operations performed by one or more embodiments described herein. For example, logic flow 400 may include some or all of the operations of securely generating an account using a contactless card 101 with a third-party application 115. The embodiments are not limited to this context.

[0058] As shown, logic flow 400 begins at box 405, where third-party application 115 receives an instruction specifying the creation of a payment account using contactless card 101. For example, a user can optionally specify the use of contactless card 101 to generate an account using third-party application 115. Figure 2A The GUI element 201. In box 410, the user can tap the contactless card 101 on 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 a third-party application 115 specifying a tap on device 110. In box 415, the app 103 can generate the encrypted customer ID 109. In box 420, the app 103 can transmit the encrypted customer ID 109 to the mobile device 110.

[0059] At box 425, mobile device 110 (e.g., OS 112 and / or third-party application 115) may transmit encrypted customer ID 109 to management application 123 of server 120. Third-party application 115 may also transmit an indication specifying that encrypted customer ID 109 is part of an attempt to generate an account using third-party application 115. At box 430, mobile device 110 may receive push notifications from management application 123. As stated, in some embodiments, management application 123 may decrypt encrypted customer ID 109 before transmitting push notifications to mobile device 110. At box 435, in response to a user selecting push notifications, account application 113 is opened. As stated, in some embodiments, a user may provide credentials to access their account via account application 113. Account application 113 may then request confirmation of whether the attempted account generation via third-party application 115 is valid input.

[0060] In box 440, third-party application 115 can receive input specifying that the attempted account generation is valid. For example, the user can select... Figure 2D The GUI element 204. In box 445, third-party application 115 can transmit an indication of confirmation to management application 123. In box 450, OS 112, account application 113, and / or third-party application 115 can receive from management application 123 an indication that the encrypted customer ID 109 has been verified and account generation has been approved. As stated, management application 123 can decrypt the encrypted customer ID 109 in response to the initial receipt of the encrypted customer ID 109 (e.g., in box 425) and / or at different times. For example, management application 123 can decrypt the encrypted customer ID 109 in response to receiving confirmation in box 450. Additionally, verification may include account data 154 of the user account associated with contactless card 101.

[0061] In box 455, the third-party application 115 is opened (if it is not already displayed on the display of the mobile device 110). In box 460, the third-party application 115 uses account data 154 received from the management application 123 to populate multiple form fields. The user can optionally edit the information automatically populated into the form fields by the third-party application 115. In box 465, the third-party application 115 uses the account data 154 received from the management application 123 to create an account for the user. For example, the third-party application 115 may cause a record of creating a new account to be created in the account data 144 of the third-party server 140.

[0062] Figure 5An embodiment of logic flow 500 is illustrated. Logic flow 500 may represent some or all of the operations performed by one or more embodiments described herein. For example, logic flow 500 may include some or all of the operations for securely and automatically filling data associated with contactless card 101 into a form. The embodiments are not limited to this context.

[0063] As shown, the logic flow 500 begins at box 510, where third-party application 115 receives account data 154 from management application 123. At box 520, third-party application 115 fills in the name field of the form with the name received from account data 154. At box 530, third-party application 115 fills in the last name field of the form with the last name received from account data 154. At box 535, third-party application 115 fills in the email address field of the form with the email address received from account data 154. At box 540, third-party application 115 fills in the address field of the form with the address received from account data 154.

[0064] In box 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 can be the account number of the contactless card 101 and / or a virtual account generated by the server 120. In box 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 can be the expiration date of the contactless card 101 and / or the virtual account. In box 570, the third-party application 115 enters the CVV from the received account data 154 into the CVV field of the form. The CVV can be the CVV of the contactless card 101 and / or the virtual account.

[0065] In some examples, this disclosure relates to tapping a contactless card. However, it should be understood that this disclosure is not limited to tapping, and that it includes other gestures (e.g., waving or other movement of the card).

[0066] Figure 6 An embodiment of an exemplary computing architecture 600 including a computing system 602 is illustrated, which can be adapted to implement various embodiments as 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 implementing one or more components of system 100. In some embodiments, the computing system 602 may represent, for example, a mobile device 110 and a server 120 of system 100. The embodiments are not limited thereto. More generally, the computing architecture 600 is configured to implement the embodiments described herein with reference to Figures 1 to 120. Figure 5 The complete logic, application, system, method, device, and function described.

[0067] As used herein, the terms “system,” “component,” and “module” are intended to refer to computer-related entities, hardware, combinations of hardware and software, software, or software in execution, examples of which are provided by the exemplary computing architecture 600. For example, a component can 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 executing thread, a program, and / or a computer. For example, both an application running on a server and the server itself can be components. One or more components may reside within a process and / or an executing thread, and components may reside on a single computer and / or be distributed across two or more computers. Furthermore, components can communicatively couple with each other through various types of communication media to coordinate operations. Coordination may include one-way or two-way information exchange. For example, components may transmit information in the form of signals transmitted via a communication medium. This information can be implemented as signals assigned to various signal lines. In such an assignment, each message is a signal. However, alternative embodiments may employ data messages. Such data messages can be sent through various connections. Exemplary connections include parallel interfaces, serial interfaces, and bus interfaces.

[0068] The computing system 602 includes various common computing elements, such as one or more processors, multi-core processors, coprocessors, memory units, chipsets, controllers, peripherals, interfaces, oscillators, timing devices, video cards, sound cards, multimedia input / output (I / O) components, power supplies, and so on. However, embodiments are not limited to those implemented by the computing system 602.

[0069] like Figure 6 As shown, computing system 602 includes processor 604, system memory 606, and system bus 608. 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 security processors; IBM® and Motorola® DragonBal® 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 processor 604.

[0070] System bus 608 provides interfaces for system components, including but not limited to the interface between system memory 606 and processor 604. System bus 608 can be any of several types of bus architectures, which can also interconnect to memory buses (with or without memory controllers), peripheral buses, and local buses using any of a variety of commercially available bus architectures. Interface adapters can be connected to system bus 608 via slot architectures. Example slot architectures can include, but are not limited to, Accelerated Graphics Port (AGP), card bus, (Extended) Industry Standard Architecture (E)ISA, MicroChannel Architecture (MCA), NuBus, Peripheral Component Interconnect (Extended) (PCI(X)), PCI Express, Personal Computer Memory Card International Association (PCMCIA), etc.

[0071] System memory 606 may include various types of computer-readable storage media in the form of one or more high-speed memory cells, such as read-only memory (ROM), random-access memory (RAM), dynamic RAM (DRAM), double-data-rate DRAM (DDRAM), synchronous DRAM (SDRAM), static RAM (SRAM), programmable ROM (PROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEROM), flash memory (e.g., one or more flash memory arrays), polymer memory such as ferroelectric polymer memory, bidirectional memory, phase-change or ferroelectric memory, silicon-oxide-nitride-oxide-silicon (SONOS) memory, magnetic cards or optical cards, device arrays such as Redundant Array of Independent Disks (RAID) drives, solid-state memory devices (e.g., USB storage, solid-state drives). Drives (SSDs) and any other type of storage medium suitable for storing information. Figure 6 In the illustrated embodiment, system memory 606 may include non-volatile memory 610 and / or volatile memory 612. The basic input / output system (BIOS) may be stored in non-volatile memory 610.

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

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

[0074] Users can input commands and information into the computing system 602 through one or more wired / wireless input devices, such as keyboard 638 and pointing devices (such as mouse 640). Other input devices may include microphones, infrared (IR) remote controls, radio-frequency (RF) remote controls, game pads, styluses, card readers, dongles, fingerprint readers, gloves, graphics tablets, joysticks, keyboards, retinal readers, touchscreens (e.g., capacitive touchscreens, resistive touchscreens, etc.), trackballs, touchpads, sensors, styluses, etc. These and other input devices are typically connected to the processor 604 via input device interface 642 coupled to system bus 608, but may also be connected via other interfaces such as parallel ports, IEEE 1394 serial ports, game ports, USB ports, IR interfaces, etc.

[0075] Monitor 644 or other types of display devices are also connected to system bus 608 via an interface such as video adapter 646. Monitor 644 can be internal or external to computing system 602. In addition to monitor 644, computers typically include other peripheral output devices such as speakers, printers, etc.

[0076] Computing system 602 can operate in a networked environment using logical connections to one or more remote computers (e.g., remote computer 648) via wired and / or wireless communications. Remote computer 648 can be a workstation, server computer, router, personal computer, portable computer, microprocessor-based entertainment device, peer-to-peer device, or other public network node, and typically includes many or all of the elements described relative to computing system 602, although for simplicity only memory / storage device 650 is shown. The depicted logical connections include wired / wireless connectivity to a local area network (LAN) 652 and / or a larger network (e.g., a wide area network (WAN) 654). Such LAN and WAN networking environments are common in offices and corporations and facilitate enterprise-wide computer networks, such as intranets, all of which can connect to global communication networks, such as the Internet. In an embodiment, network 130 of FIG1 is one or more of LAN 652 and WAN 654.

[0077] When used in a LAN networking environment, the computing system 602 is connected to the LAN 652 via a wired and / or wireless communication network interface or adapter 656. Adapter 656 facilitates wired and / or wireless communication to the LAN 652, which may also include a wireless access point configured thereon for communicating with the wireless functionality of adapter 656.

[0078] When used in a WAN networking environment, computing system 602 may include a modem 658, or a communication server connected to WAN 654, or other means for establishing communication over WAN 654, such as via the Internet. Modem 658 (which may be internal or external to wired and / or wireless devices) is connected to system bus 608 via input device interface 642. In a networked environment, program modules or portions thereof depicted relative to computing system 602 may be stored in remote memory / storage device 650. It should be understood that the network connections shown are exemplary, and other means of establishing communication links between computers may be used.

[0079] The computing system 602 is operable to communicate with wired and wireless devices or entities using the IEEE 802 series of standards, such as operable to configure wireless devices in wireless communication (e.g., IEEE 802.16 air modulation technology). This includes at least Wi-Fi (or Wireless Fidelity), WiMax, and Bluetooth wireless technologies. Therefore, communication can be a predefined structure like a regular network, or simply point-to-point communication between at least two devices. Wi-Fi networks use radio technologies known as IEEE 802.11x (a, b, g, n, etc.) to provide secure, reliable, and fast wireless connectivity. Wi-Fi networks can be used to interconnect computers, connect to the Internet, and connect to wired networks (which use media and functions related to IEEE 802.3).

[0080] Various embodiments may be implemented using hardware elements, software elements, or a combination of both. Examples of hardware elements may include processors, microprocessors, circuits, circuit elements (e.g., transistors, resistors, capacitors, inductors, 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, computational code, computer code, code segments, computer code segments, words, values, symbols, or any combination thereof. Determining whether an embodiment is implemented using hardware and / or software components can vary depending on many factors, such as desired computing speed, power level, thermal tolerance, processing cycle budget, input data rate, output data rate, memory resources, data bus speed, and other design or performance constraints.

[0081] One or more aspects of at least one embodiment can be implemented by representative instructions stored on a machine-readable medium, representing various logic within a processor, which, when read by a machine, cause the machine-made logic to perform the techniques described herein. Such a representation, referred to as an "IP core," can be stored on a tangible machine-readable medium and supplied to various customers or manufacturing facilities for loading into a manufacturing machine that makes the logic or processor. Some embodiments can be implemented, for example, using a machine-readable medium or article that can store instructions or a set of instructions that, if executed by a machine, can cause the machine to perform the methods and / or operations according to the embodiments. Such a machine can include, for example, any suitable processing platform, computing platform, computing device, processing device, computing system, processing system, computer, processor, etc., and can be implemented using any suitable combination of hardware and / or software. Machine-readable media or articles of art can include, for example, any suitable type of memory cell, memory device, memory article, memory medium, storage device, storage article, storage medium and / or storage cell, such as memory, removable or non-removable media, erasable or non-erasable media, writable or rewritable 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 discs, various types of digital versatile disks (DVD), magnetic tape, cassette tape, etc. Instructions can include any suitable type of code implemented using any suitable high-level, low-level, object-oriented, visual, compiled and / or interpreted programming language, such as source code, compiled code, interpreted code, executable code, static code, dynamic code, encrypted code, etc.

[0082] The foregoing description of exemplary embodiments has been presented for purposes of illustration and description. It is not intended to be exhaustive or to limit this disclosure to the precise forms disclosed. Many modifications and variations are possible based on this disclosure. The scope of this disclosure is intended to be limited not by this detailed description, but by the appended claims. Future applications claiming priority to this application may claim protection for the disclosed subject matter in different ways and may generally include any set or more of the limitations disclosed herein or otherwise shown.

Claims

1. A method comprising: The device's processor receives an instruction specifying the generation of a payment account, wherein the instruction is received by a payment application executing on the processor, and the payment account is generated using a contactless card via the payment application. The processor receives encrypted data from the contactless card; The processor transmits the encrypted data to a server associated with the issuer of the contactless card; The processor opens the account application associated with the issuer of the contactless card; The account application receives confirmation input specifying the use of the contactless card to generate the payment account using the payment application; The account application transmits the confirmation input instruction to a server associated with the issuer of the contactless card; The processor opens the payment application in response to receiving verification of the encrypted data from a server associated with the issuer of the contactless card; and The payment application generates the payment account using account data generated by a server associated with the issuer of the contactless card. The account data is an account associated with the contactless card, and the payment application is different from the account application. The method further includes: The payment application receives the account data from a server associated with the issuer of the contactless card. The payment application automatically fills the received account data into the corresponding form fields in the form provided by the payment application.

2. The method according to claim 1, wherein the 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) expiry date of the contactless card, and (vii) card verification value (CVV) of the contactless card.

3. The method according to claim 2, further comprising: The name is filled into the name form field, one of the multiple form fields in the form of the payment application; The payment application fills the surname into the surname form field of the plurality of form fields; The payment application fills the email address into the email address form field of the plurality of form fields; The payment application fills the address into the address form field of the plurality of form fields; The payment application fills the account information into the account form field of the plurality of form fields; The payment application fills the deadline into the deadline form field among the multiple form fields; The payment application fills the CVV into the CVV form field of the plurality of form fields; as well as The payment application receives input specifying the form submission to generate a payment account.

4. The method of claim 1, wherein the confirmation instruction is transmitted to the API of a server associated with the issuer of the contactless card via a Hypertext Transfer Security Protocol (HTTPS) application programming interface (API) call.

5. The method according to claim 1, further comprising: The processor receives a push notification specifying the provision of the confirmation input; and The processor receives input selecting the push notification, wherein the account application is opened based on the input selecting the push notification.

6. The method of claim 1, wherein the account data of the account includes a virtual account generated for the account associated with the contactless card, the expiration date of the virtual account, and the card verification value (CVV) of the virtual account, the method further comprising: The virtual account is displayed in the account field of the form within the payment application. The payment application displays the expiration date in the expiration date form field among the multiple form fields of the form; The payment application displays the CVV in the CVV form field among multiple form fields of the form; and The payment application receives the input that specifies the form submitted to generate the payment account.

7. A non-transitory computer-readable storage medium, the computer-readable storage medium comprising instructions that, when executed by a processor, cause the processor to perform the following operations: The system receives an instruction specifying the generation of a payment account, wherein the instruction is received by a payment application executing on the processor, and the payment account is generated using a contactless card via the payment application. Receive encrypted data from the contactless card; The encrypted data is transmitted to a server associated with the issuer of the contactless card; Open the account application associated with the issuer of the contactless card; The account application receives confirmation input specifying the use of the contactless card to generate the payment account using the payment application; The account application transmits the confirmation input instruction to a server associated with the issuer of the contactless card; The payment application is opened in response to receiving verification of the encrypted data from a server associated with the issuer of the contactless card; and The payment application generates the payment account using account data generated by a server associated with the issuer of the contactless card. The account data is an account associated with the contactless card, the payment application is different from the account application, and the instructions further cause the processor to: The payment application receives the account data from a server associated with the issuer of the contactless card. The payment application automatically fills the received account data into the corresponding form fields in the form provided by the payment application.

8. The computer-readable storage medium of claim 7, wherein the 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) expiry date of the contactless card, and (vii) card verification value (CVV) of the contactless card.

9. The computer-readable storage medium of claim 8, wherein the instructions further cause the processor to: The name is filled into the name form field, one of the multiple form fields in the form of the payment application; The payment application fills the surname into the surname form field of the plurality of form fields; The payment application fills the email address into the email address form field of the plurality of form fields; The payment application fills the address into the address form field of the plurality of form fields; The payment application fills the account information into the account form field of the plurality of form fields; The payment application fills the deadline into the deadline form field among the multiple form fields; The payment application fills the CVV into the CVV form field of the plurality of form fields; as well as The payment application receives input specifying the form submission to generate a payment account.

10. The computer-readable storage medium of claim 7, wherein the confirmation instruction is transmitted via a Hypertext Transfer Security Protocol (HTTPS) application programming interface (API) call to an API associated with a server of the issuer of the contactless card.

11. The computer-readable storage medium of claim 7, wherein the instructions further cause the processor to: Receive a push notification specifying the confirmation input; and Receive input to select the push notification, wherein the account application is opened based on the input to select the push notification.

12. The computer-readable storage medium of claim 7, wherein the account data of the account includes a virtual account generated for the account associated with the contactless card, an expiration date of the virtual account, and a card verification value (CVV) of the virtual account, wherein the instructions further cause the processor to: The virtual account is displayed in the account field of the form within the payment application. The payment application displays the expiration date in the expiration date form field among the multiple form fields of the form; The payment application displays the CVV in the CVV form field among multiple form fields of the form; and The payment application receives the input that specifies the form submitted to generate the payment account.

13. A computing device, comprising: processor; as well as The memory stores instructions that, when executed by the processor, cause the processor to: The system receives an instruction specifying the generation of a payment account, wherein the instruction is received by a payment application executing on the processor, and the payment account is generated using a contactless card via the payment application. Receive encrypted data from the contactless card; The encrypted data is transmitted to a server associated with the issuer of the contactless card; Open the account application associated with the issuer of the contactless card; The account application receives confirmation input specifying the use of the contactless card to generate the payment account using the payment application; The account application transmits the confirmation input instruction to a server associated with the issuer of the contactless card; The payment application is opened in response to receiving verification of the encrypted data from a server associated with the issuer of the contactless card; and The payment application generates the payment account using account data generated by a server associated with the issuer of the contactless card. The account data is an account associated with the contactless card, the payment application is different from the account application, and the instructions further cause the processor to: The payment application receives the account data from a server associated with the issuer of the contactless card. The payment application automatically fills the received account data into the corresponding form fields in the form provided by the payment application.

14. The computing device of claim 13, wherein the 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) expiry date of the contactless card, and (vii) card verification value (CVV) of the contactless card.

15. The computing device of claim 14, wherein the instructions further cause the processor to: The name is filled into the name form field, one of the multiple form fields in the form of the payment application; The payment application fills the surname into the surname form field of the plurality of form fields; The payment application fills the email address into the email address form field of the plurality of form fields; The payment application fills the address into the address form field of the plurality of form fields; The payment application fills the account information into the account form field of the plurality of form fields; The payment application fills the deadline into the deadline form field among the multiple form fields; The payment application fills the CVV into the CVV form field of the plurality of form fields; as well as The payment application receives input specifying the form submission to generate a payment account.

16. The computing device of claim 13, wherein the confirmation instruction is transmitted via a Hypertext Transfer Security Protocol (HTTPS) application programming interface (API) call to an API associated with the issuer of the contactless card, wherein the instruction further causes the processor to: The payment application receives the account data from a server associated with the issuer of the contactless card.

17. The computing device of claim 13, wherein the instructions further cause the processor to: Receive a push notification specifying the confirmation input; and Receive input to select the push notification, wherein the account application is opened based on the input to select the push notification.

Images