Various embodiments are directed to applying, via contactless card authentication, one or more restrictions to a virtual card number and generating the card number for use by a recipient. The one or more restrictions may be specifically personalized to the recipient and may include, for example, a merchant restriction, an amount restriction, a time period restriction, or a location restriction. The generated virtual card number along with the applied one or more restrictions may be consumed in various ways, such as writing the number to a blank card, transmitting the number directly to the recipient's computing device, etc., all via near-field communication.

Various embodiments are directed to applying, via contactless card authentication, one or more restrictions to a virtual card number and generating the card number for use by a recipient. The one or more restrictions may be specifically personalized to the recipient and may include, for example, a merchant restriction, an amount restriction, a time period restriction, or a location restriction. The generated virtual card number along with the applied one or more restrictions may be consumed in various ways, such as writing the number to a blank card, transmitting the number directly to the recipient's computing device, etc., all via near-field communication.

Account registration using a contactless card. A payment application executing on a device may receive a request to generate a payment account using a contactless card. The payment application may receive encrypted data from the contactless card and transmit the encrypted data to a server associated with the contactless card. The device may receive a push notification from the server and open an account application associated with the contactless card responsive to selection of the push notification. The account application may receive confirmation to generate the payment account using the contactless card and transmit the confirmation to the server. The device may open the payment application responsive to receiving verification of the encrypted data from the server. The payment application may fill form fields with account data received from the server and generate the payment account using the account data received from the server filled into the form fields.

Techniques are provided for propagating updates to user profile information using a blockchain and for controlling access to user profile information using a blockchain. In one embodiment, a first block is added to a blockchain. The first block includes a first transaction ID that identifies a first transaction entry in the blockchain and a first version of user profile information encrypted using the first encryption key. The first transaction ID and a first decryption key that is able to decrypt information encrypted with the first encryption key is communicated to a plurality of entity computing devices that are to use the user profile information. The user profile information is updated by adding a second block to the blockchain that refers to the first transaction ID and includes a second version of the profile information encrypted using the first encryption key.

A user is provided with a GUI that may allow the user to change functionality associated with a non-powered card, a powered card or other device (e.g., a mobile telephonic device). The functionality associated with the device may be displayed by the GUI as a list of third-party applications that may be executed when the user's card or other device is used to complete a purchase transaction. The GUI allows the user to purchase/redeem goods and/or services from a third-party vendor after the purchase transaction is completed or may allow the goods and/or services to be purchased/redeemed without first requiring a purchase transaction. A fulfillment system hosted by a remote facility administers the goods/services delivery by tracking user information, mailing information, and delivery status tracking information.

Apparatus and methods for providing a digital card asset construction service. In and embodiment, a digital card asset service computer provides access to a digital card asset application user interface (API) to an issuer device, then receives a request from a user to construct or update a digital payment card product and receives card art data for the digital payment card product responsive to one or more queries presented by the digital card asset API. The process also includes receiving, by the digital card asset service computer from the issuer device, digital payment card product characteristics data responsive to at least one digital payment card product characteristic query, transmitting computer executable instructions to the issuer device for rendering an image of a payment card on a display screen of the issuer device as the user inputs data, then receiving an indication that the user is finished inputting data, and lastly storing a payment card product data file that includes card art data and payment card product characteristics data to a cloud service.

Techniques for mobile devices configured to support or function as multiple contactless cards, such as Mifare contactless cards, are disclosed. According to one embodiment, a mobile device embedded with an emulator is loaded with a plurality of software modules or applications, each emulating one card or one type of contactless cards. An emulator is implemented in a secure element that is personalized for a user of the mobile device while the applications are respectively provisioned via their respective providers per the personalized secure element. When the mobile device is to be used as a contactless card to perform a monetary function, a corresponding application is loaded into and executed in the emulator. When the mobile device is to be used to perform another monetary function, a corresponding application is loaded into the emulator to replace the previous application entirely or partially in the emulator. As a result, the mobile device can be used as a monetary device in lieu of multiple contactless cards.

Techniques for mobile devices configured to support settlement of charges in electronic invoices or bills are described. A first mobile device is used to obtain from a second mobile device data pertaining to the electronic invoices for payment. The data includes the electronic invoice and other information regarding a registered user of the second mobile device. After the user verifies the amount being charged and authorizes the payment, the first mobile device determines if there is a balance enough to cover the authorized payment before communicating with a payment server configured to proceed with the payment and send a confirmation to the second mobile device.

Programmable cards, computer-readable media, and systems are disclosed for token payment. For example, a programmable card for token payment, according to some embodiments, may include an antenna and a contact interface. The card may be configured to store, in the rewritable memory, a token transmitted from a user device via a first near field communication (NFC) signal received by the antenna, and provide the stored token to a point of sales terminal via a second NFC signal transmitted by the antenna or via the contact interface.

Embodiments of the invention relate to systems and methods for efficiently provisioning mobile devices with personalization data. For some embodiments, a method is disclosed comprising receiving a request for provisioning comprising device information for a mobile device and user authentication information for a user, generating a partial personalization script, an activation script, and a deletion script using the device information, sending the partial personalization script, the activation script, and the deletion script to an application provider computer, wherein the application provider computer initiates execution of the partial personalization script on the mobile device, authenticating the user authentication information, and sending an activation message to the application provider computer, wherein the application provider computer initiates execution of the activation script.