Account Management
Efficient account management methods and interfaces on electronic devices streamline account operations, reducing user interaction and power consumption by enabling simultaneous display and selection of multiple accounts with automatic credential switching and streamlined provisioning.
Patent Information
- Application Number
- JP2024566673
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2023-05-10
- Filing Date
- 2023-05-11
- Publication Date
- 2025-12-19
- Estimated Expiration
- 2043-05-11
AI Technical Summary
Existing account management techniques on electronic devices are cumbersome and inefficient, often requiring multiple key presses and consuming excessive time and energy, particularly in battery-operated devices.
Implementing faster and more efficient account management methods and interfaces that allow simultaneous display and selection of multiple accounts, automatic credential switching based on account functionality, and streamlined provisioning and autofill operations, utilizing visual representations and user inputs to enhance user interaction and reduce power consumption.
Enhances user efficiency, reduces cognitive burden, and conserves power by providing quicker account management processes while extending battery life in battery-operated devices.
Smart Images

Figure 0007788783000001 
Figure 0007788783000002 
Figure 0007788783000003
Abstract
Description
CROSS-REFERENCE TO RELATED APPLICATIONS
[0001] This application claims priority to U.S. Provisional Patent Application No. 63 / 340,916 entitled "ACCOUNT MANAGEMENT," filed May 11, 2022, U.S. Provisional Patent Application No. 63 / 349,137 entitled "ACCOUNT MANAGEMENT," filed June 5, 2022, U.S. Provisional Patent Application No. 63 / 404,172 entitled "ACCOUNT MANAGEMENT," filed September 6, 2022, and U.S. Patent Application No. 18 / 195,855 entitled "ACCOUNT MANAGEMENT," filed May 10, 2023. The contents of each of these applications are incorporated herein by reference in their entirety. [Technical Field]
[0002] TECHNICAL FIELD The present disclosure relates generally to computer user interfaces, and more particularly to techniques for managing accounts. [Background technology]
[0003] Electronic devices often contain account information for various accounts, which may be made available for use in various ways, such as by submission via a website and / or transmission via near field communications. Summary of the Invention
[0004] However, some techniques for managing accounts using electronic devices are generally cumbersome and inefficient. For example, some existing techniques use complex and time-consuming user interfaces that may involve multiple key presses or strokes. Existing techniques take more time than necessary, wasting the user's time and the device's energy. This latter consideration is particularly important in battery-operated devices.
[0005] Thus, the present technology provides electronic devices with faster, more efficient methods and interfaces for managing accounts. Such methods and interfaces optionally complement or replace other methods for managing accounts. Such methods and interfaces reduce the cognitive burden on users and create a more efficient human-machine interface. For battery-operated computing devices, such methods and interfaces conserve power and extend the time between battery charges.
[0006] An exemplary method is described herein in a computer system in communication with a display generation component and one or more input devices, the exemplary method including: simultaneously displaying, via the display generation component, a portion of a first visual representation corresponding to a first asset account provisioned on an electronic wallet of the computer system and a portion of a second visual representation different from the first visual representation corresponding to a second asset account provisioned on the electronic wallet of the computer system and different from the first asset account; receiving, via the one or more input devices, a selection of the first visual representation corresponding to the first asset account while simultaneously displaying the portion of the first visual representation and the portion of the second visual representation; and, in response to receiving the selection of the first visual representation corresponding to the first asset account, selecting, via the display generation component, a set of virtual account criteria, wherein a first virtual account criterion of the set of virtual account criteria is met when virtual account functionality is not enabled for the first asset account, in accordance with a determination that the set of virtual account criteria is met. displaying a first selectable user interface object for initiating a process for enabling virtual account functionality for the account, wherein when the virtual account functionality is not enabled for the first asset account, the computer system automatically uses the same credential information for successive transactions performed using the first asset account, and when the virtual account functionality is enabled for the first asset account, the computer system automatically uses different credential information for successive transactions performed using the first asset account; ceasing to display the first selectable user interface object for initiating the process for enabling the virtual account functionality for the first asset account according to a determination that the set of virtual account criteria is not satisfied; and receiving, via the display generation component, a selection of the first visual representation via the one or more input devices while displaying the first selectable user interface object that is displayed in response to receiving, via the display generation component, a selection of the first visual representation;receiving a selection of the first selectable user interface object; and in response to receiving the selection of the first selectable user interface object, initiating a process for enabling virtual account functionality for the first asset account.
[0007] An exemplary method includes, in a computer system in communication with a display generating component and one or more input devices, displaying, via the display generating component, a provisioning user interface including an indication that one or more accounts are enabled for performing application autofill operations on the computer system and are not provisioned on the computer system's electronic wallet, and a first selectable user interface object for initiating a process for provisioning the one or more accounts on the computer system's electronic wallet; receiving, via the one or more input devices, a selection of the first selectable user interface object; and initiating, in response to receiving the selection of the first selectable user interface object, a process for provisioning a first account of the one or more accounts into the computer system's electronic wallet, the process for provisioning the first account of the one or more accounts into the computer system's electronic wallet using at least some account information related to the first account, the account information being stored for use in the application autofill operation; and following receiving the selection of the first selectable user interface object, provisioning the first account into the computer system's electronic wallet using at least some account information related to the first account, the account information being stored for use in the application autofill operation.
[0008] An exemplary method includes, in a computer system in communication with a display generation component and one or more input devices, displaying, via the display generation component, a plurality of selectable user interface objects, including a first selectable user interface object corresponding to a first account provisioned on an electronic wallet of the computer system and a second selectable user interface object corresponding to a second account enabled at the computer system for performing application autofill operations and not provisioned on the electronic wallet of the computer system, the second selectable user interface object being different from the first account; receiving, via the one or more input devices, user input selecting one of the plurality of selectable user interface objects; In response to receiving user input selecting one, in accordance with a determination that the user input corresponds to selection of a first selectable user interface object, initiating a process to perform an autofill operation to populate one or more fields using credentials of the first account, wherein the credentials of the first account populated in a first field of the one or more fields are visually obfuscated; and in accordance with a determination that the user input corresponds to selection of a second selectable user interface object, initiating a process to perform an autofill operation to populate one or more fields using credentials of the second account, wherein the credentials of the second account populated in a first field of the one or more fields are not visually obfuscated.
[0009] An exemplary method is for a computer system in communication with a display generation component, one or more input devices, and one or more communications radios, to display, via the display generation component, a plurality of selectable user interface objects, including: a first selectable user interface object corresponding to a first account provisioned on an electronic wallet of the computer system, the computer system configured to perform transfers using near field communications via the one or more communications radios, a second selectable user interface object corresponding to a second account provisioned on the electronic wallet of the computer system, different from the first account, the computer system configured to perform transfers using near field communications via the one or more communications radios, and an order tracking user interface object for tracking order status. receiving a first user input selecting one of the plurality of selectable user interface objects; ceasing the display of a second selectable user interface object in response to receiving the first user input selecting one of the plurality of selectable user interface objects in accordance with a determination that the first user input corresponds to the selection of the first selectable user interface object; displaying, via the display generation component, information regarding one or more transfers performed using the first account; displaying, via the display generation component in accordance with a determination that the first user input corresponds to the selection of an order tracking user interface object, a plurality of order summaries including a first summary of a first order from a first merchant and a second summary of a second order from a second merchant different from the first merchant; and receiving, while displaying the plurality of order summaries, a second user input selecting one of the plurality of order summaries via one or more input devices.In response to receiving a second user input selecting one of the plurality of order summaries, displaying, via the display generation component, order tracking details for the first order using a default arrangement in accordance with a determination that the second user input corresponds to a selection of a first summary for the first order; and displaying, via the display generation component, order tracking details for the second order using a default arrangement in accordance with a determination that the second user input corresponds to a selection of a second summary for the second order.
[0010] An exemplary method includes, in a computer system in communication with a display generation component, one or more input devices, and one or more communication radios, displaying, via the display generation component, a plurality of selectable user interface options for applying future rewards of a first asset account, the plurality of selectable user interface options including a first selectable option for applying future rewards of a first asset account to a second asset account, the first selectable option being configured to perform a transfer using the second asset account, the second asset account being different from the first asset account, using short-range communication via the one or more communication radios; and a second selectable option for applying future rewards of the first asset account to a third asset account, the third asset account being different from the first asset account and the second asset account; and selecting, via the one or more input devices, one of the plurality of selectable user interface options for applying future rewards of the first asset account to the respective asset account. and in response to receiving the first user input selecting one of a plurality of selectable user interface options, initiating a process for applying future rewards of the first asset account to a second asset account in accordance with a determination that the first user input corresponds to selection of the first selectable option; initiating a process for applying future rewards of the first asset account to a third asset account in accordance with a determination that the first user input corresponds to selection of the second selectable option; after completing the process for applying the future rewards of the first asset account to the individual accounts, performing a transfer using the first asset account using short-range communication via one or more communication radios, wherein a reward based on the transfer using the first asset account is applied to the individual account; and displaying via a display generation component the balance of the individual account including the applied reward.
[0011] An exemplary method includes, in a computer system in communication with a display generation component and one or more communications radios, displaying, via the display generation component, a visual object corresponding to a total amount of lifetime rewards received for a first asset account provisioned in an electronic wallet of the computer system, the first asset account and a second asset account being provisioned in the electronic wallet of the computer system, the total amount being provisioned in the electronic wallet of the computer system, the visual object corresponding to a total amount of lifetime rewards received for the first asset account, a first portion of the visual object corresponding to a first type of reward received for the first asset account being visually distinct from a second portion of the visual object corresponding to a second type of reward received for the first asset account, an area of the first portion of the visual object being a first size based on an amount of the first type of reward received relative to a total amount of lifetime rewards received for the first asset account, and an area of the second portion of the visual object being a second size based on an amount of the second type of reward received relative to a total amount of lifetime rewards received for the first asset account. and a visual object corresponding to the total amount of lifetime rewards received for the first asset account, the visual object being a visual object of a different size than the first size; after simultaneously displaying the total amount of lifetime rewards received for the first asset account and the visual object corresponding to the total amount of lifetime rewards received for the first asset account, performing a first transfer using the first asset account via one or more communication radios; performing a second transfer using the second asset account via the one or more communication radios; and following the performing the first and second transfers, displaying, via the display generation component, a visual object corresponding to the total amount of lifetime rewards received for the first asset account, the total amount of lifetime rewards being updated to include rewards received based on the first transfer but not including rewards received based on the second transfer, the visual object corresponding to the updated total amount of lifetime rewards received for the first asset account, the visual object being a visual object of a different size than the first size, the visual object being a visual object of a different size than the first size, the visual object being a visual object corresponding to the updated total amount of lifetime rewards received for the first asset account ...and simultaneously displaying a visual object that is updated to a fourth size smaller than the second size, the fourth size being based on a reward received based on the first transfer that does not correspond to the second type of reward.
[0012] An exemplary non-transitory computer-readable storage medium is described herein. The exemplary non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more input devices, and includes: simultaneously displaying, via the display generation component, a portion of a first visual representation corresponding to a first asset account provisioned in an electronic wallet of the computer system and a portion of a second visual representation different from the first visual representation corresponding to a second asset account provisioned in the electronic wallet of the computer system and different from the first asset account; receiving, via the one or more input devices, a selection of the first visual representation corresponding to the first asset account while simultaneously displaying the portion of the first visual representation and the portion of the second visual representation; and, in response to receiving the selection of the first visual representation corresponding to the first asset account, selecting a set of virtual account criteria, the first virtual account criteria of the set of virtual account criteria indicating that virtual account functionality is enabled for the first asset account. and displaying, via the display generating component, a virtual account feature for the first asset account, wherein the virtual account feature is satisfied when the set of virtual account criteria is not enabled for the first asset account, the computer system automatically uses the same credential information for successive transactions performed using the first asset account when the virtual account feature is not enabled for the first asset account, and automatically uses different credential information for successive transactions performed using the first asset account when the virtual account feature is enabled for the first asset account; and, according to a determination that the set of virtual account criteria is not satisfied, ceasing to display the first selectable user interface object for initiating the process for enabling the virtual account feature for the first asset account, via the display generating component.The method includes instructions for receiving, via one or more input devices, a selection of the first selectable user interface object while displaying the first selectable user interface object that is displayed in response to receiving the selection of the first visual representation, and for initiating a process for enabling virtual account functionality for the first asset account in response to receiving the selection of the first selectable user interface object.
[0013] An exemplary non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system in communication with a display generating component and one or more input devices; displaying, via the display generating component, a provisioning user interface including an indication that one or more accounts are enabled for performing application autofill operations on the computer system but are not provisioned in an electronic wallet of the computer system and a first selectable user interface object for initiating a process for provisioning the one or more accounts on the electronic wallet of the computer system; receiving, via the one or more input devices, a selection of the first selectable user interface object; and, in response to receiving the selection of the first selectable user interface object, a process for provisioning a first account of the one or more accounts into the electronic wallet of the computer system using at least some account information related to the first account, the account information being stored for use in the application autofill operation. The exemplary non-transitory computer-readable storage medium includes instructions for initiating the provisioning process and, following receiving the selection of the first selectable user interface object, provisioning the first account into the electronic wallet of the computer system using at least some account information related to the first account, the account information being stored for use in the application autofill operation.
[0014] An exemplary non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more input devices, and displays, via the display generation component, a plurality of selectable user interface objects, including a first selectable user interface object corresponding to a first account provisioned on an electronic wallet of the computer system and a second selectable user interface object corresponding to a second account, different from the first account, that is enabled for performing an application autofill operation on the computer system and is not provisioned on the electronic wallet of the computer system; receives, via the one or more input devices, user input selecting one of the plurality of selectable user interface objects; and The method includes instructions for initiating, in response to receiving user input selecting one of the selectable user interface objects, a process for performing an autofill operation to populate one or more fields with credentials of a first account, wherein the credentials of the first account populated in a first field of the one or more fields are visually obfuscated, in accordance with a determination that the user input corresponds to selection of a first selectable user interface object, and for initiating, in accordance with a determination that the user input corresponds to selection of a second selectable user interface object, a process for performing an autofill operation to populate one or more fields with credentials of a second account, wherein the credentials of the second account populated in a first field of the one or more fields are not visually obfuscated.
[0015] An exemplary non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component, one or more input devices, and one or more communications radios, and displays, via the display generation component, a first selectable user interface object corresponding to a first account provisioned on an electronic wallet of the computer system, the computer system being configured to perform a transfer using the first account using near field communications via the one or more communications radios; a second selectable user interface object corresponding to a second account provisioned on the electronic wallet of the computer system, different from the first account, the computer system being configured to perform a transfer using the second account using near field communications via the one or more communications radios; and an order tracking user interface object for tracking order status. and receiving a first user input selecting one of the plurality of selectable user interface objects; in response to receiving the first user input selecting one of the plurality of selectable user interface objects, ceasing to display a second selectable user interface object in accordance with a determination that the first user input corresponds to the selection of the first selectable user interface object; displaying, via the display generation component, information regarding one or more transfers performed using the first account; in accordance with a determination that the first user input corresponds to the selection of an order tracking user interface object, displaying, via the display generation component, a plurality of order summaries including a first summary of a first order from a first merchant and a second summary of a second order from a second merchant different from the first merchant; and receiving, while displaying the plurality of order summaries, a second user input selecting one of the plurality of order summaries via one or more input devices;In response to receiving a second user input selecting one of the plurality of order summaries, instructions include: displaying, via the display generation component, order tracking details for the first order using a default arrangement in accordance with a determination that the second user input corresponds to selecting a first summary for the first order; and displaying, via the display generation component, order tracking details for the second order using a default arrangement in accordance with a determination that the second user input corresponds to selecting a second summary for the second order.
[0016] An exemplary non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component, one or more input devices, and one or more communication radios; and displays, via the display generation component, a plurality of selectable user interface options for applying future rewards of a first asset account, including a first selectable option for applying future rewards of a first asset account to a second asset account, the computer system being configured to perform a transfer using short-range communication via the one or more communication radios, the second asset account being different from the first asset account, and a second selectable option for applying future rewards of the first asset account to a third asset account being different from the first asset account and the second asset account; and displays, via the one or more input devices, a plurality of selectable user interface options for applying future rewards of the first asset account to the respective asset accounts. The system includes instructions for receiving a first user input selecting one of a plurality of selectable user interface options; in response to receiving the first user input selecting one of the plurality of selectable user interface options, initiating a process for applying future rewards of the first asset account to a second asset account in accordance with a determination that the first user input corresponds to a selection of the first selectable option; initiating a process for applying future rewards of the first asset account to a third asset account in accordance with a determination that the first user input corresponds to a selection of the second selectable option; after completing the process for applying the future rewards of the first asset account to the individual account, performing a transfer using the first asset account using short-range communication via one or more communication radios, wherein a reward based on the transfer using the first asset account is applied to the individual account; and displaying, via a display generation component, the balance of the individual account including the applied reward.
[0017] An exemplary non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more communications radios, and displays, via the display generation component, a visual object corresponding to a total amount of lifetime rewards received for a first asset account provisioned to an electronic wallet of the computer system, the first asset account and a second asset account being provisioned to the electronic wallet of the computer system, the total amount being provisioned to the electronic wallet of the computer system, the visual object corresponding to a total amount of lifetime rewards received for the first asset account, a first portion of the visual object corresponding to a first type of reward received for the first asset account visually distinct from a second portion of the visual object corresponding to a second type of reward received for the first asset account, an area of the first portion of the visual object having a first size based on the amount of the first type of reward received relative to the total amount of lifetime rewards received for the first asset account, and an area of the second portion of the visual object having a first size based on the amount of the first type of reward received relative to the total amount of lifetime rewards received for the first asset account. and a visual object corresponding to the total amount of lifetime rewards received for the first asset account, the visual object having a second size based on the amount of a second type of reward received relative to the total amount of lifetime rewards received for the first asset account; after simultaneously displaying the total amount of lifetime rewards received for the first asset account and the visual object corresponding to the total amount of lifetime rewards received for the first asset account, execute a first transfer using the first asset account via one or more communication radios, execute a second transfer using the second asset account via one or more communication radios; and following execution of the first transfer and the second transfer, display, via the display generation component, the total amount of lifetime rewards received for the first asset account, the total amount of lifetime rewards being updated to include rewards received based on the first transfer but not the rewards received based on the second transfer, and the visual object corresponding to the updated total amount of lifetime rewards received for the first asset account, the area of the first portion of the visual object being updated to a third size greater than the first size, the third size being:The method further includes instructions to simultaneously display the visual object and the visual object, based on a reward received based on the first transfer corresponding to the first type of reward, the visual object being updated to a fourth size smaller than the second size, the fourth size being based on a reward received based on the first transfer not corresponding to the second type of reward.
[0018] An exemplary temporary computer-readable storage medium is described herein, the exemplary temporary computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more input devices, to simultaneously display, via the display generation component, a portion of a first visual representation corresponding to a first asset account provisioned in an electronic wallet of the computer system and a portion of a second visual representation different from the first visual representation corresponding to a second asset account provisioned in the electronic wallet of the computer system and different from the first asset account, receive, via the one or more input devices, a selection of the first visual representation corresponding to the first asset account while simultaneously displaying the portion of the first visual representation and the portion of the second visual representation, and in response to receiving the selection of the first visual representation corresponding to the first asset account, select a set of virtual account criteria, the first virtual account criteria of the set of virtual account criteria indicating that virtual account functionality is enabled for the first asset account. and displaying, via the display generating component, a virtual account feature for a first asset account, the virtual account feature being satisfied when the set of virtual account criteria is not enabled for the first asset account, the computer system automatically using the same credential information for successive transactions performed using the first asset account when the virtual account feature is not enabled for the first asset account, and automatically using different credential information for successive transactions performed using the first asset account when the virtual account feature is enabled for the first asset account; and displaying, via the display generating component, a first selectable user interface object for initiating a process for enabling the virtual account feature; and, according to a determination that the set of virtual account criteria is not satisfied, ceasing to display the first selectable user interface object for initiating a process for enabling the virtual account feature for the first asset account;The method includes instructions for receiving, via one or more input devices, a selection of the first selectable user interface object while displaying the first selectable user interface object that is displayed in response to receiving the selection of the first visual representation, and for initiating a process for enabling virtual account functionality for the first asset account in response to receiving the selection of the first selectable user interface object.
[0019] An exemplary temporary computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system in communication with a display generating component and one or more input devices; displaying, via the display generating component, a provisioning user interface including an indication that one or more accounts are enabled for performing application autofill operations on the computer system but are not provisioned in an electronic wallet of the computer system and a first selectable user interface object for initiating a process for provisioning the one or more accounts on the electronic wallet of the computer system; receiving, via the one or more input devices, a selection of the first selectable user interface object; and, in response to receiving the selection of the first selectable user interface object, a process for provisioning a first account of the one or more accounts into the electronic wallet of the computer system using at least some account information related to the first account, the account information being stored for use in the application autofill operation. The exemplary temporary computer-readable storage medium includes one or more programs configured to be executed by one or more processors of a computer system in communication with a display generating component and one or more input devices; displaying, via the display generating component, a provisioning user interface including an indication that one or more accounts are enabled for performing application autofill operations on the computer system but are not provisioned in an electronic wallet of the computer system and a first selectable user interface object for initiating a process for provisioning the one or more accounts on the electronic wallet of the computer system using at least some account information related to the first account, the account information being stored for use in the application autofill operation.
[0020] An exemplary temporary computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more input devices, and displays, via the display generation component, a plurality of selectable user interface objects, including a first selectable user interface object corresponding to a first account provisioned on an electronic wallet of the computer system and a second selectable user interface object corresponding to a second account, different from the first account, that is enabled for performing an application autofill operation on the computer system and is not provisioned on the electronic wallet of the computer system; receives, via the one or more input devices, user input selecting one of the plurality of selectable user interface objects; and and in response to receiving user input selecting one of the selectable user interface objects, in accordance with a determination that the user input corresponds to selection of a first selectable user interface object, initiate a process to perform an autofill operation to populate the one or more fields with credentials of a first account, wherein the credentials of the first account populated in a first field of the one or more fields are visually obfuscated; and in accordance with a determination that the user input corresponds to selection of a second selectable user interface object, initiate a process to perform an autofill operation to populate the one or more fields with credentials of a second account, wherein the credentials of the second account populated in a first field of the one or more fields are not visually obfuscated.
[0021] An exemplary transient computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component, one or more input devices, and one or more communications radios, the program including: a first selectable user interface object corresponding to a first account provisioned on an electronic wallet of the computer system, the computer system configured to perform transfers using the first account using near field communications via the one or more communications radios; a second selectable user interface object corresponding to a second account provisioned on the electronic wallet of the computer system, different from the first account, the computer system configured to perform transfers using near field communications via the one or more communications radios; and an order tracking user interface object for tracking order status. and receiving a first user input selecting one of the plurality of selectable user interface objects; in response to receiving the first user input selecting one of the plurality of selectable user interface objects, ceasing to display a second selectable user interface object in accordance with a determination that the first user input corresponds to the selection of the first selectable user interface object; displaying, via the display generation component, information regarding one or more transfers performed using the first account; in accordance with a determination that the first user input corresponds to the selection of an order tracking user interface object, displaying, via the display generation component, a plurality of order summaries including a first summary of a first order from a first merchant and a second summary of a second order from a second merchant different from the first merchant; and while displaying the plurality of order summaries, receiving, via one or more input devices, a second user input selecting one of the plurality of order summaries;In response to receiving a second user input selecting one of the plurality of order summaries, instructions include: displaying, via the display generation component, order tracking details for the first order using a default arrangement in accordance with a determination that the second user input corresponds to selecting a first summary for the first order; and displaying, via the display generation component, order tracking details for the second order using a default arrangement in accordance with a determination that the second user input corresponds to selecting a second summary for the second order.
[0022] An exemplary temporary computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component, one or more input devices, and one or more communication radios; and displays, via the display generation component, a plurality of selectable user interface options for applying future rewards of a first asset account, including a first selectable option for applying future rewards of a first asset account to a second asset account, the first selectable option being configured to perform a transfer using the second asset account, the second asset account being different from the first asset account, using short-range communication via the one or more communication radios; and a second selectable option for applying future rewards of the first asset account to a third asset account, the third asset account being different from the first asset account and the second asset account; and displays, via the one or more input devices, a plurality of selectable user interface options for applying future rewards of the first asset account to separate asset accounts. The method includes instructions for receiving a first user input selecting one of the plurality of selectable user interface options, in response to receiving the first user input selecting one of the plurality of selectable user interface options, initiating a process for applying future rewards of the first asset account to a second asset account in accordance with a determination that the first user input corresponds to selection of the first selectable option, initiating a process for applying future rewards of the first asset account to a third asset account in accordance with a determination that the first user input corresponds to selection of the second selectable option, and after completing the process for applying future rewards of the first asset account to the individual account, performing a transfer using the first asset account using short-range communication via one or more communication radios, wherein a reward based on the transfer using the first asset account is applied to the individual account, and displaying, via a display generation component, the balance of the individual account including the applied reward.
[0023] An exemplary transient computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more communications radios, and displays, via the display generation component, a visual object corresponding to a total amount of lifetime rewards received for a first asset account provisioned to an electronic wallet of the computer system, the first asset account and a second asset account being provisioned to the electronic wallet of the computer system, the total amount being provisioned to the electronic wallet of the computer system, the visual object corresponding to a total amount of lifetime rewards received for the first asset account, a first portion of the visual object corresponding to a first type of reward received for the first asset account visually distinct from a second portion of the visual object corresponding to a second type of reward received for the first asset account, an area of the first portion of the visual object having a first size based on the amount of the first type of reward received relative to the total amount of lifetime rewards received for the first asset account, and an area of the second portion of the visual object and a visual object corresponding to the total amount of lifetime rewards received for the first asset account, the visual object having a second size based on the amount of a second type of reward received relative to the total amount of lifetime rewards received for the first asset account; after simultaneously displaying the total amount of lifetime rewards received for the first asset account and the visual object corresponding to the total amount of lifetime rewards received for the first asset account, perform a first transfer using the first asset account via one or more communication radios, perform a second transfer using the second asset account via one or more communication radios; and following the execution of the first transfer and the second transfer, display, via the display generation component, the total amount of lifetime rewards received for the first asset account, the total amount of lifetime rewards being updated to include rewards received based on the first transfer but not the rewards received based on the second transfer, and a visual object corresponding to the updated total amount of lifetime rewards received for the first asset account, the area of the first portion of the visual object being updated to a third size greater than the first size, the third size being:The method further includes instructions to simultaneously display the visual object and the visual object, based on a reward received based on the first transfer corresponding to the first type of reward, the visual object being updated to a fourth size smaller than the second size, the fourth size being based on a reward received based on the first transfer not corresponding to the second type of reward.
[0024] An exemplary computer system is described herein. The exemplary computer system is configured to communicate with a display generation component and one or more input devices, and includes one or more processors and a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs simultaneously displaying, via the display generation component, a portion of a first visual representation corresponding to a first asset account provisioned on an electronic wallet of the computer system and a portion of a second visual representation different from the first visual representation corresponding to a second asset account different from the first asset account provisioned on the electronic wallet of the computer system; receiving, via the one or more input devices, a selection of the first visual representation corresponding to the first asset account while simultaneously displaying the portion of the first visual representation and the portion of the second visual representation; and in response to receiving the selection of the first visual representation corresponding to the first asset account, selecting a set of virtual account criteria, wherein a first virtual account criterion of the set of virtual account criteria is associated with a virtual account for the first asset account. In accordance with a determination that a set of virtual account criteria are satisfied when the account feature is not enabled, the computer system displays, via the display generation component, a first selectable user interface object for initiating a process for enabling the virtual account feature for the first asset account, wherein when the virtual account feature is not enabled for the first asset account, the computer system automatically uses the same credential information for successive transactions performed using the first asset account, and when the virtual account feature is enabled for the first asset account, the computer system automatically uses different credential information for successive transactions performed using the first asset account; and in accordance with a determination that the set of virtual account criteria are not satisfied, the computer system ceases to display, via the display generation component, the first selectable user interface object for initiating a process for enabling the virtual account feature for the first asset account.The method includes instructions for receiving, via one or more input devices, a selection of the first selectable user interface object while displaying the first selectable user interface object that is displayed in response to receiving the selection of the first visual representation, and for initiating a process for enabling virtual account functionality for the first asset account in response to receiving the selection of the first selectable user interface object.
[0025] An exemplary computer system is configured to communicate with a display generation component and one or more input devices, and includes one or more processors and a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs displaying, via the display generation component, a provisioning user interface including an indication that one or more accounts are enabled for performing application autofill operations at the computer system but are not provisioned on an electronic wallet of the computer system, and a first selectable user interface object for initiating a process to provision the one or more accounts on an electronic wallet of the computer system, receiving, via the one or more input devices, a selection of the first selectable user interface object, and selecting the first selectable user interface object. A process for provisioning a first account of one or more accounts into an electronic wallet of a computer system in response to receiving a selection of an interface object, the process for provisioning a first account of the one or more accounts into an electronic wallet of the computer system using at least some account information about the first account, the account information being stored for use in an application autofill operation. The process includes instructions for initiating a provisioning process and, following receiving a selection of a first selectable user interface object, provisioning the first account into an electronic wallet of the computer system using at least some account information about the first account, the account information being stored for use in an application autofill operation.
[0026] An exemplary computer system is configured to communicate with a display generation component and one or more input devices, and includes one or more processors and a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs displaying, via the display generation component, a plurality of selectable user interface objects including a first selectable user interface object corresponding to a first account provisioned on an electronic wallet of the computer system and a second selectable user interface object corresponding to a second account different from the first account that is enabled for performing an application autofill operation at the computer system and is not provisioned on the electronic wallet of the computer system, and allowing a user to select one of the plurality of selectable user interface objects via the one or more input devices. and in response to receiving the user input selecting one of the plurality of selectable user interface objects, initiating a process to perform an autofill operation to populate the one or more fields with credentials of a first account in accordance with a determination that the user input corresponds to selection of a first selectable user interface object, wherein the credentials of the first account populated in a first field of the one or more fields are visually obfuscated; and initiating a process to perform an autofill operation to populate the one or more fields with credentials of a second account in accordance with a determination that the user input corresponds to selection of a second selectable user interface object, wherein the credentials of the second account populated in a first field of the one or more fields are not visually obfuscated.
[0027] An exemplary computer system is configured to communicate with a display generation component, one or more input devices, and one or more communication radios, and includes one or more processors and a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs being configured to display, via the display generation component, a first selectable user interface object corresponding to a first account provisioned on an electronic wallet of the computer system, the computer system being configured to perform a transfer using the first account using near field communications via the one or more communication radios, and a second selectable user interface object corresponding to a second account provisioned on the electronic wallet of the computer system, different from the first account, the computer system being configured to perform a transfer using near field communications via the one or more communication radios. and an order tracking user interface object for tracking an order status; receiving a first user input selecting one of the plurality of selectable user interface objects; in response to receiving the first user input selecting one of the plurality of selectable user interface objects, ceasing to display a second selectable user interface object in accordance with a determination that the first user input corresponds to the selection of the first selectable user interface object; displaying, via the display generation component, information regarding one or more transfers performed using the first account; in accordance with a determination that the first user input corresponds to the selection of the order tracking user interface object, displaying, via the display generation component, a plurality of order summaries including a first summary of a first order from a first merchant and a second summary of a second order from a second merchant different from the first merchant; and while displaying the plurality of order summaries, via one or more input devices.The system includes instructions for receiving a second user input selecting one of the plurality of order summaries; and, in response to receiving the second user input selecting one of the plurality of order summaries, displaying, via the display generation component, order tracking details for the first order using a default arrangement in accordance with a determination that the second user input corresponds to selecting a first summary for the first order; and displaying, via the display generation component, order tracking details for the second order using a default arrangement in accordance with a determination that the second user input corresponds to selecting a second summary for the second order.
[0028] An exemplary computer system is configured to communicate with a display generation component, one or more input devices, and one or more communication radios, and comprises one or more processors and a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs displaying, via the display generation component, a plurality of selectable user interface options for applying future rewards of a first asset account, including a first selectable option for applying future rewards of a first asset account to a second asset account, the computer system being configured to perform a transfer using short-range communication via the one or more communication radios, the first selectable option being a first selectable option for applying future rewards of the first asset account to a second asset account, the second asset account being different from the first asset account, and a second selectable option for applying future rewards of the first asset account to a third asset account being different from the first asset account and the second asset account, and displaying, via the one or more input devices, a plurality of selectable user interface options for applying future rewards of the first asset account to a third asset account, the third asset account being different from the first asset account and the second asset account, the method further comprises instructions for receiving a first user input selecting one of a plurality of selectable user interface options for applying future rewards of the first asset account to the individual account; in response to receiving the first user input selecting one of the plurality of selectable user interface options, initiating a process for applying future rewards of the first asset account to a second asset account in accordance with a determination that the first user input corresponds to a selection of the first selectable option; initiating a process for applying future rewards of the first asset account to a third asset account in accordance with a determination that the first user input corresponds to a selection of the second selectable option; after completing the process for applying the future rewards of the first asset account to the individual account, performing a transfer using the first asset account using short range communication via one or more communication radios, wherein a reward based on the transfer using the first asset account is applied to the individual account; and displaying, via a display generation component, the balance of the individual account including the applied rewards.
[0029] An exemplary computer system is configured to communicate with a display generation component and one or more communications radios, and includes one or more processors and a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs being configured to, via the display generation component, display a total amount of lifetime rewards received for a first asset account provisioned on an electronic wallet of the computer system, the first asset account and a second asset account being provisioned on the electronic wallet of the computer system; a visual object corresponding to the lifetime rewards received for the first asset account, a first portion of the visual object corresponding to the first type of rewards received for the first asset account visually distinct from a second portion of the visual object corresponding to the second type of rewards received for the first asset account, an area of the first portion of the visual object being a first size based on the total amount of the first type of rewards received relative to the total amount of lifetime rewards received for the first asset account; and simultaneously displaying a visual object corresponding to the total amount of lifetime rewards received for the first asset account, wherein the area of a second portion of the visual object is a second size based on the total amount of the second type of rewards received relative to the total amount of lifetime rewards received for the first asset account; after simultaneously displaying the total amount of lifetime rewards received for the first asset account and the visual object corresponding to the total amount of lifetime rewards received for the first asset account, perform a first transfer using the first asset account via the one or more communication radios, perform a second transfer using the second asset account via the one or more communication radios; and following the execution of the first transfer and the second transfer, display, via the display generation component, a visual object corresponding to the total amount of lifetime rewards received for the first asset account, wherein the total amount of lifetime rewards received is updated to include rewards received based on the first transfer but not the rewards received based on the second transfer, and the updated total amount of lifetime rewards received for the first asset account, wherein the area of the first portion of the visual object is updated to a third size greater than the first size;The third size is based on a reward received based on the first transfer corresponding to the first type of reward, and the area of the second portion of the visual object is updated to a fourth size smaller than the second size, and the fourth size is based on a reward received based on the first transfer not corresponding to the second type of reward, and the visual object is simultaneously displayed.
[0030] An exemplary computer system is configured to communicate with a display generation component and one or more input devices, and includes means for simultaneously displaying, via the display generation component, a portion of a first visual representation corresponding to a first asset account provisioned on the computer system's electronic wallet and a portion of a second visual representation different from the first visual representation corresponding to a second asset account provisioned on the computer system's electronic wallet, the second visual representation different from the first asset account; means for receiving, via the one or more input devices, a selection of the first visual representation corresponding to the first asset account while simultaneously displaying the portion of the first visual representation and the portion of the second visual representation; and means for, in response to receiving the selection of the first visual representation corresponding to the first asset account, selecting a set of virtual account criteria, wherein a first virtual account criterion of the set of virtual account criteria is met when virtual account functionality is not enabled for the first asset account, via the display generation component, to select the first asset account as a virtual account in accordance with a determination that the set of virtual account criteria is met. When the counting function is not enabled for the first asset account, the computer system automatically uses the same credential information for successive transactions performed using the first asset account, and when the virtual account function is enabled for the first asset account, the computer system automatically uses different credential information for successive transactions performed using the first asset account; means for displaying a first selectable user interface object for initiating a process for enabling the virtual account function for the first asset account and ceasing to display the first selectable user interface object for initiating the process for enabling the virtual account function for the first asset account according to a determination that the set of virtual account criteria is not satisfied; means for receiving, via the display generation component, a selection of the first selectable user interface object while displaying the first selectable user interface object, the first selectable user interface object being displayed in response to receiving a selection of a first visual representation;and means for initiating a process for enabling virtual account functionality for the first asset account in response to receiving a selection of the first selectable user interface object.
[0031] An exemplary computer system is configured to communicate with a display generating component and one or more input devices, and includes: means for displaying, via the display generating component, a provisioning user interface including an indication that one or more accounts are enabled for performing application autofill operations on the computer system and are not provisioned on the computer system's electronic wallet, and a first selectable user interface object for initiating a process of provisioning the one or more accounts on the computer system's electronic wallet; means for receiving, via the one or more input devices, a selection of the first selectable user interface object; and initiating, in response to receiving the selection of the first selectable user interface object, a process of provisioning a first account of the one or more accounts into the computer system's electronic wallet, wherein the process of provisioning the first account of the one or more accounts into the computer system's electronic wallet uses at least some account information related to the first account, the account information being stored for use in the application autofill operation; and means for provisioning the first account into the computer system's electronic wallet using at least some account information related to the first account following receiving the selection of the first selectable user interface object, wherein the account information is stored for use in the application autofill operation.
[0032] An exemplary computer system is configured to communicate with a display generation component and one or more input devices, and includes means for displaying, via the display generation component, a plurality of selectable user interface objects, including a first selectable user interface object corresponding to a first account provisioned on an electronic wallet of the computer system, and a second selectable user interface object corresponding to a second account different from the first account, enabled for performing application autofill operations at the computer system, and not provisioned on the electronic wallet of the computer system; means for receiving, via the one or more input devices, user input for selecting one of the plurality of selectable user interface objects; and means for selecting one of the plurality of selectable user interface objects. and means for initiating, in response to receiving user input selecting one, a process for performing an autofill operation to populate one or more fields using credentials of the first account in accordance with a determination that the user input corresponds to selection of a first selectable user interface object, wherein the credentials of the first account to be populated into a first field of the one or more fields are visually obfuscated; and for initiating, in accordance with a determination that the user input corresponds to selection of a second selectable user interface object, a process for performing an autofill operation to populate one or more fields using credentials of the second account, wherein the credentials of the second account populated into a first field of the one or more fields are not visually obfuscated.
[0033] An exemplary computer system is configured to communicate with a display generation component, one or more input devices, and one or more communication radios, and includes, via the display generation component, a simultaneous display of multiple selectable user interface objects, including a first selectable user interface object corresponding to a first account provisioned on the electronic wallet of the computer system, the computer system being configured to perform a transfer using the first account using near field communication via the one or more communication radios, a second selectable user interface object corresponding to a second account provisioned on the electronic wallet of the computer system, different from the first account, the computer system being configured to perform a transfer using near field communication via the one or more communication radios, and an order tracking user interface object for tracking order status. means for displaying a user interface of a mobile internet application; means for receiving a first user input selecting one of the plurality of selectable user interface objects; in response to receiving the first user input selecting one of the plurality of selectable user interface objects, ceasing to display a second selectable user interface object in accordance with a determination that the first user input corresponds to a selection of the first selectable user interface object, and displaying, via a display generation component, information regarding one or more transfers performed using the first account; in response to a determination that the first user input corresponds to a selection of an order tracking user interface object, displaying, via the display generation component, a plurality of order summaries including a first summary of a first order from a first merchant and a second summary of a second order from a second merchant different from the first merchant; while displaying the plurality of order summaries, means for receiving, via one or more input devices, a second user input selecting one of the plurality of order summaries; in response to receiving the second user input selecting one of the plurality of order summaries,means for displaying, via the display generation component, the order tracking details for the first order using a default arrangement in accordance with a determination that the second user input corresponds to a selection of a first summary for the first order, and for displaying, via the display generation component, the order tracking details for the second order using a default arrangement in accordance with a determination that the second user input corresponds to a selection of a second summary for the second order;
[0034] An exemplary computer system is configured to communicate with a display generation component, one or more input devices, and one or more communication radios, and includes means for displaying, via the display generation component, a plurality of selectable user interface options for applying future rewards of a first asset account, the plurality of selectable user interface options including a first selectable option for applying future rewards of a first asset account to a second asset account, the computer system being configured to perform a transfer using short-range communication via the one or more communication radios, the first selectable option being a first selectable option for applying future rewards of a first asset account to a second asset account, the second asset account being different from the first asset account, and a second selectable option for applying future rewards of the first asset account to a third asset account being different from the first asset account and the second asset account; and means for displaying, via the one or more input devices, a plurality of selectable user interface options for applying future rewards of the first asset account to a separate asset account. The system includes a means for receiving a first user input selecting one of the plurality of selectable user interface options; a means for initiating a process for applying future rewards of the first asset account to a second asset account in response to receiving the first user input selecting one of the plurality of selectable user interface options in accordance with a determination that the first user input corresponds to a selection of the first selectable option, and a means for initiating a process for applying future rewards of the first asset account to a third asset account in accordance with a determination that the first user input corresponds to a selection of the second selectable option; a means for executing a transfer using the first asset account using short-range communication via one or more communication radios after completing the process for applying future rewards of the first asset account to the individual account, wherein rewards based on the transfer using the first asset account are applied to the individual account; and a means for displaying the balance of the individual account including the applied rewards via a display generation component.
[0035] An exemplary computer system is configured to communicate with a display generation component and one or more communications radios, and displays, via the display generation component, a visual object corresponding to a total amount of lifetime rewards received for a first asset account provisioned in an electronic wallet of the computer system, the first asset account and a second asset account being provisioned in the electronic wallet of the computer system, the total amount being a total amount of lifetime rewards received for the first asset account, a first portion of the visual object corresponding to a first type of reward received for the first asset account being visually distinct from a second portion of the visual object corresponding to a second type of reward received for the first asset account, an area of the first portion of the visual object being a first size based on the amount of the first type of reward received relative to the total amount of lifetime rewards received for the first asset account, and an area of the second portion of the visual object being based on the amount of the second type of reward received relative to the total amount of lifetime rewards received for the first asset account. means for simultaneously displaying a visual object having two sizes, the visual object being a first size and the visual object being a second size; means for executing, via one or more communication radios, a first transfer using the first asset account and a second transfer using the second asset account after simultaneously displaying the total amount of lifetime rewards received for the first asset account and the visual object corresponding to the total amount of lifetime rewards received for the first asset account; and means for simultaneously displaying, via one or more communication radios, a visual object having two sizes, the visual object being a first size and the visual object being a second size and the visual object being a second size and the visual object being a third size and the visual object being a second size and the visual object being a third size and the visual object being a first size and the visual object being a second size and the visual object being a third size and the visual object being a second size and the visual object being a third size and the visual object being a second size and the visual object being a third size and the visual object being a third size and the visual object being a third size and the visual object being a fourth ... fifth size and the visual object being a fourth size and the visual object being a fifth size and the visual object being a fourth size and the visual object being a fifth size and the visual object being a fifth size and the visual object being a fifth size and the visual object being a fifth size and the visual object being a fifth size and the visual object being a fifth size and the visual object being a fifth size and the visual object being a fifth size and the visual object being a fifth size and the visual object being a fifth size and the visual object being a fifth size and the visual object being a fifth size and the visual object being a fifth size and the visual object being a fifth size and the visual objectand means for simultaneously displaying a visual object that is updated to a fourth size smaller than the second size, the fourth size being based on a reward received based on the first transfer that does not correspond to the second type of reward.
[0036] An exemplary computer program product is described herein. The exemplary computer program product includes one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more input devices, the one or more programs simultaneously displaying, via the display generation component, a portion of a first visual representation corresponding to a first asset account provisioned on an electronic wallet of the computer system and a portion of a second visual representation different from the first visual representation corresponding to a second asset account provisioned on the electronic wallet of the computer system and different from the first asset account; receiving, via the one or more input devices, a selection of the first visual representation corresponding to the first asset account while simultaneously displaying the portion of the first visual representation and the portion of the second visual representation; and in response to receiving the selection of the first visual representation corresponding to the first asset account, a set of virtual account criteria, the first virtual account criteria of the set of virtual account criteria being associated with a virtual account function for the first asset account. and displaying, via the display generating component, a virtual account feature for the first asset account, wherein when the virtual account feature is not enabled for the first asset account, the computer system automatically uses the same credential information for successive transactions performed using the first asset account, and when the virtual account feature is enabled for the first asset account, the computer system automatically uses different credential information for successive transactions performed using the first asset account, in accordance with a determination that the set of virtual account criteria are satisfied, the set of virtual account criteria being satisfied when the virtual account feature is not enabled for the first asset account. Also, according to a determination that the set of virtual account criteria are not satisfied, the computer system ceases displaying, via the display generating component, a first selectable user interface object for initiating a process for enabling the virtual account feature for the first asset account.The method includes instructions for receiving, via one or more input devices, a selection of the first selectable user interface object while displaying the first selectable user interface object that is displayed in response to receiving the selection of the first visual representation, and for initiating a process for enabling virtual account functionality for the first asset account in response to receiving the selection of the first selectable user interface object.
[0037] An exemplary computer program product includes one or more programs configured to be executed by one or more processors of a computer system in communication with a display generating component and one or more input devices, the one or more programs display, via the display generating component, a provisioning user interface including an indication that one or more accounts are enabled for performing application autofill operations at the computer system and are not provisioned on an electronic wallet of the computer system, and a first selectable user interface object for initiating a process to provision the one or more accounts on the electronic wallet of the computer system; receive, via the one or more input devices, a selection of the first selectable user interface object; and, in response to receiving the selection of the first selectable user interface object, select one or more of the following: A process for provisioning a first of the one or more accounts into an electronic wallet of a computer system, the process for provisioning a first of the one or more accounts into the electronic wallet of the computer system using at least some account information about the first account, the account information being stored for use in application autofill operations. Initiating the process for provisioning a first of the one or more accounts into the electronic wallet of the computer system includes instructions for, following receiving a selection of a first selectable user interface object, provisioning the first account into the electronic wallet of the computer system using at least some account information about the first account, the account information being stored for use in application autofill operations.
[0038] An exemplary computer program product includes one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more input devices, the one or more programs displaying, via the display generation component, a plurality of selectable user interface objects including a first selectable user interface object corresponding to a first account provisioned on an electronic wallet of the computer system and a second selectable user interface object corresponding to a second account, different from the first account, that is enabled for performing application autofill operations at the computer system and is not provisioned on the electronic wallet of the computer system, and receiving, via the one or more input devices, user input selecting one of the plurality of selectable user interface objects. In response to receiving user input selecting one of the plurality of selectable user interface objects, in accordance with a determination that the user input corresponds to a selection of a first selectable user interface object, initiate a process to perform an autofill operation to populate one or more fields using credentials of a first account, wherein the credentials of the first account populated in a first field of the one or more fields are visually obfuscated; and in accordance with a determination that the user input corresponds to a selection of a second selectable user interface object, initiate a process to perform an autofill operation to populate one or more fields using credentials of a second account, wherein the credentials of the second account populated in a first field of the one or more fields are not visually obfuscated.
[0039] An exemplary computer program product includes one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component, one or more input devices, and one or more communications radios, the one or more programs displaying, via the display generation component, a first selectable user interface object corresponding to a first account provisioned on an electronic wallet of the computer system, the computer system being configured to perform a transfer using the first account using near field communications via the one or more communications radios; a second selectable user interface object corresponding to a second account provisioned on the electronic wallet of the computer system, different from the first account, the computer system being configured to perform a transfer using the second account using near field communications via the one or more communications radios; and an order status indicator. and an order tracking user interface object for tracking the status of an electronic wallet application; receiving a first user input selecting one of the plurality of selectable user interface objects; in response to receiving the first user input selecting one of the plurality of selectable user interface objects, ceasing to display a second selectable user interface object in accordance with a determination that the first user input corresponds to the selection of the first selectable user interface object; displaying, via the display generation component, information regarding one or more transfers performed using the first account; in accordance with a determination that the first user input corresponds to the selection of the order tracking user interface object, displaying, via the display generation component, a plurality of order summaries including a first summary of a first order from a first merchant and a second summary of a second order from a second merchant different from the first merchant; and, while displaying the plurality of order summaries, inputting, via one or more input devices,The system includes instructions for receiving a second user input selecting one of the plurality of order summaries; and, in response to receiving the second user input selecting one of the plurality of order summaries, displaying, via the display generation component, order tracking details for the first order using a default arrangement in accordance with a determination that the second user input corresponds to selecting a first summary for the first order; and displaying, via the display generation component, order tracking details for the second order using a default arrangement in accordance with a determination that the second user input corresponds to selecting a second summary for the second order.
[0040] An exemplary computer program product includes one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component, one or more input devices, and one or more communications radios, the one or more programs display, via the display generation component, a plurality of selectable user interface options for applying future rewards of a first asset account, including a first selectable option for applying future rewards of a first asset account to a second asset account, the computer system being configured to perform a transfer using short-range communication via the one or more communications radios, the first selectable option being a first selectable option for applying future rewards of the first asset account to a third asset account, the third asset account being different from the first asset account and the second asset account, and a second selectable option for applying future rewards of the first asset account to a third asset account, the third asset account being different from the first asset account and the second asset account, and a plurality of selectable user interface options for applying future rewards of the first asset account to a third asset account, the third asset account being different from the first asset account and the second asset account, via the one or more input devices. the instructions include instructions to receive a first user input selecting one of a plurality of selectable user interface options for applying a future reward of the first asset account to a second asset account in response to receiving the first user input selecting one of the plurality of selectable user interface options, initiate a process for applying the future reward of the first asset account to a third asset account in accordance with a determination that the first user input corresponds to a selection of the second selectable option, and, after completing the process for applying the future reward of the first asset account to the individual account, perform a transfer using the first asset account using short range communication via one or more communication radios, where a reward based on the transfer using the first asset account is applied to the individual account; and display, via a display generation component, the balance of the individual account including the applied reward.
[0041] An exemplary computer program product includes one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more communications radios, the one or more programs displaying, via the display generation component, a total amount of lifetime rewards received for a first asset account provisioned in an electronic wallet of the computer system, the first asset account and a second asset account being provisioned in the electronic wallet of the computer system; a visual object corresponding to the total amount of lifetime rewards received for the first asset account, a first portion of the visual object corresponding to a first type of reward received for the first asset account visually distinct from a second portion of the visual object corresponding to a second type of reward received for the first asset account, an area of the first portion of the visual object being a first size based on the amount of the first type of reward received relative to the total amount of lifetime rewards received for the first asset account; and a visual object corresponding to the total amount of lifetime rewards received for the first asset account, wherein the area of the portion is a second size based on the amount of a second type of reward received relative to the total amount of lifetime rewards received for the first asset account; after simultaneously displaying the total amount of lifetime rewards received for the first asset account and the visual object corresponding to the total amount of lifetime rewards received for the first asset account, execute a first transfer using the first asset account via one or more communication radios, execute a second transfer using the second asset account via one or more communication radios; and following execution of the first transfer and the second transfer, display, via the display generation component, the total amount of lifetime rewards received for the first asset account, wherein the total amount of lifetime rewards is updated to include rewards received based on the first transfer but not the rewards received based on the second transfer; and a visual object corresponding to the updated total amount of lifetime rewards received for the first asset account, wherein the area of the first portion of the visual object is updated to a third size greater than the first size, wherein the third size isThe method further includes instructions to simultaneously display the visual object and the visual object, based on a reward received based on the first transfer corresponding to the first type of reward, the visual object being updated to a fourth size smaller than the second size, the fourth size being based on a reward received based on the first transfer not corresponding to the second type of reward.
[0042] Executable instructions to perform these functions are optionally contained in a non-transitory computer-readable storage medium or other computer program product configured for execution by one or more processors. Executable instructions to perform these functions are optionally contained in a transitory computer-readable storage medium or other computer program product configured for execution by one or more processors.
[0043] This provides devices with fast and efficient methods and interfaces for managing accounts, thereby increasing the effectiveness, efficiency, and user satisfaction of such devices. Such methods and interfaces may complement or replace other methods for managing accounts. [Brief explanation of the drawings]
[0044] For a better understanding of the various described embodiments, reference should be made to the following Detailed Description of the Invention in conjunction with the following drawings, in which like reference numerals refer to corresponding parts throughout:
[0045] [Figure 1A] FIG. 1 is a block diagram illustrating a portable multifunction device with a touch-sensitive display in accordance with some embodiments.
[0046] [Figure 1B] FIG. 2 is a block diagram illustrating exemplary components for event processing according to some embodiments.
[0047] [Figure 2]FIG. 1 illustrates a portable multifunction device with a touch screen in accordance with some embodiments.
[0048] [Figure 3] FIG. 1 is a block diagram of an exemplary multifunction device having a display and a touch-sensitive surface in accordance with some embodiments.
[0049] [Figure 4A] 1 illustrates an exemplary user interface for a menu of applications on a portable multifunction device in accordance with some embodiments.
[0050] [Figure 4B] 1 illustrates an exemplary user interface for a multifunction device having a touch-sensitive surface that is separate from the display in accordance with some embodiments.
[0051] [Figure 5A] 1 illustrates a personal electronic device according to some embodiments.
[0052] [Figure 5B] FIG. 1 is a block diagram illustrating a personal electronic device according to some embodiments.
[0053] [Figure 5C] 1 illustrates exemplary devices connected via one or more communication channels in accordance with some embodiments.
[0054] [Figure 6A] 1 illustrates an exemplary user interface for managing storage account numbers according to some embodiments. [Figure 6B] 1 illustrates an exemplary user interface for managing storage account numbers according to some embodiments. [Figure 6C] 1 illustrates an exemplary user interface for managing storage account numbers according to some embodiments. [Figure 6D] 1 illustrates an exemplary user interface for managing storage account numbers according to some embodiments.
[0055] [Figure 7A] 1 illustrates an exemplary user interface for managing virtual account numbers according to some embodiments. [Figure 7B] 1 illustrates an exemplary user interface for managing virtual account numbers according to some embodiments. [Figure 7C] 1 illustrates an exemplary user interface for managing virtual account numbers according to some embodiments. [Figure 7D] 1 illustrates an exemplary user interface for managing virtual account numbers according to some embodiments. [Figure 7E] 1 illustrates an exemplary user interface for managing virtual account numbers according to some embodiments. [Figure 7F] 1 illustrates an exemplary user interface for managing virtual account numbers according to some embodiments. [Figure 7G] 1 illustrates an exemplary user interface for managing virtual account numbers according to some embodiments. [Figure 7H] 1 illustrates an exemplary user interface for managing virtual account numbers according to some embodiments. [Figure 7I] 1 illustrates an exemplary user interface for managing virtual account numbers according to some embodiments. [Figure 7J] 1 illustrates an exemplary user interface for managing virtual account numbers according to some embodiments. [Figure 7K] 1 illustrates an exemplary user interface for managing virtual account numbers according to some embodiments. [Figure 7L] 1 illustrates an exemplary user interface for managing virtual account numbers according to some embodiments. [Figure 7M] 1 illustrates an exemplary user interface for managing virtual account numbers according to some embodiments.
[0056] [Figure 8] FIG. 1 is a flow diagram illustrating a method for managing account numbers according to some embodiments.
[0057] [Figure 9A] 1 illustrates an exemplary user interface for provisioning storage accounts according to some embodiments. [Figure 9B] 1 illustrates an exemplary user interface for provisioning storage accounts according to some embodiments. [Figure 9C] 1 illustrates an exemplary user interface for provisioning storage accounts according to some embodiments.
[0058] [Figure 10A] 1 illustrates an exemplary user interface for provisioning an account, according to some embodiments. [Figure 10B] 1 illustrates an exemplary user interface for provisioning an account, according to some embodiments. [Figure 10C] 1 illustrates an exemplary user interface for provisioning an account, according to some embodiments. [Figure 10D] 1 illustrates an exemplary user interface for provisioning an account, according to some embodiments. [Figure 10E] 1 illustrates an exemplary user interface for provisioning an account, according to some embodiments. [Figure 10F] 1 illustrates an exemplary user interface for provisioning an account, according to some embodiments. [Figure 10G]1 illustrates an exemplary user interface for provisioning an account, according to some embodiments. [Figure 10H] 1 illustrates an exemplary user interface for provisioning an account, according to some embodiments.
[0059] [Figure 11] FIG. 1 is a flow diagram illustrating a method for provisioning an account according to some embodiments.
[0060] [Figure 12A] 1 illustrates an exemplary user interface for obfuscating storage account credentials according to some embodiments. [Figure 12B] 1 illustrates an exemplary user interface for obfuscating storage account credentials according to some embodiments. [Figure 12C] 1 illustrates an exemplary user interface for obfuscating storage account credentials according to some embodiments.
[0061] [Figure 13A] 1 illustrates an exemplary user interface for obfuscating account credentials according to some embodiments. [Figure 13B] 1 illustrates an exemplary user interface for obfuscating account credentials according to some embodiments. [Figure 13C] 1 illustrates an exemplary user interface for obfuscating account credentials according to some embodiments. [Figure 13D] 1 illustrates an exemplary user interface for obfuscating account credentials according to some embodiments. [Figure 13E] 1 illustrates an exemplary user interface for obfuscating account credentials according to some embodiments. [Figure 13F]1 illustrates an exemplary user interface for obfuscating account credentials according to some embodiments. [Figure 13G] 1 illustrates an exemplary user interface for obfuscating account credentials according to some embodiments. [Figure 13H] 1 illustrates an exemplary user interface for obfuscating account credentials according to some embodiments. [Figure 13I] 1 illustrates an exemplary user interface for obfuscating account credentials according to some embodiments. [Figure 13J] 1 illustrates an exemplary user interface for obfuscating account credentials according to some embodiments.
[0062] [Figure 14] FIG. 1 is a flow diagram illustrating a method for obfuscating account credentials according to some embodiments.
[0063] [Figure 15A] 1 illustrates an exemplary user interface for managing orders according to some embodiments. [Figure 15B] 1 illustrates an exemplary user interface for managing orders according to some embodiments. [Figure 15C] 1 illustrates an exemplary user interface for managing orders according to some embodiments. [Figure 15D] 1 illustrates an exemplary user interface for managing orders according to some embodiments. [Figure 15E] 1 illustrates an exemplary user interface for managing orders according to some embodiments.
[0064] [Figure 16A] 1 illustrates an exemplary user interface for managing orders according to some embodiments. [Figure 16B]1 illustrates an exemplary user interface for managing orders according to some embodiments. [Figure 16C] 1 illustrates an exemplary user interface for managing orders according to some embodiments. [Figure 16D] 1 illustrates an exemplary user interface for managing orders according to some embodiments. [Figure 16E] 1 illustrates an exemplary user interface for managing orders according to some embodiments. [Figure 16F] 1 illustrates an exemplary user interface for managing orders according to some embodiments. [Figure 16G] 1 illustrates an exemplary user interface for managing orders according to some embodiments. [Figure 16H] 1 illustrates an exemplary user interface for managing orders according to some embodiments. [Figure 16I] 1 illustrates an exemplary user interface for managing orders according to some embodiments. [Figure 16J] 1 illustrates an exemplary user interface for managing orders according to some embodiments. [Figure 16K] 1 illustrates an exemplary user interface for managing orders according to some embodiments. [Figure 16L] 1 illustrates an exemplary user interface for managing orders according to some embodiments.
[0065] [Figure 17] FIG. 1 is a flow diagram illustrating a method for managing orders, according to some embodiments.
[0066] [Figure 18] 1 illustrates an exemplary user interface for managing rewards for an account, according to some embodiments.
[0067] [Figure 19A]1 illustrates an exemplary user interface for managing accounts, according to some embodiments. [Figure 19B] 1 illustrates an exemplary user interface for managing accounts, according to some embodiments. [Figure 19C] 1 illustrates an exemplary user interface for managing accounts, according to some embodiments. [Figure 19D] 1 illustrates an exemplary user interface for managing accounts, according to some embodiments. [Figure 19E] 1 illustrates an exemplary user interface for managing accounts, according to some embodiments. [Figure 19F] 1 illustrates an exemplary user interface for managing accounts, according to some embodiments. [Figure 19G] 1 illustrates an exemplary user interface for managing accounts, according to some embodiments. [Figure 19H] 1 illustrates an exemplary user interface for managing accounts, according to some embodiments. [Figure 19I] 1 illustrates an exemplary user interface for managing accounts, according to some embodiments. [Figure 19J] 1 illustrates an exemplary user interface for managing accounts, according to some embodiments. [Figure 19K] 1 illustrates an exemplary user interface for managing accounts, according to some embodiments. [Figure 19L] 1 illustrates an exemplary user interface for managing accounts, according to some embodiments. [Figure 19M] 1 illustrates an exemplary user interface for managing accounts, according to some embodiments. [Figure 19N] 1 illustrates an exemplary user interface for managing accounts, according to some embodiments. [Figure 19O] 1 illustrates an exemplary user interface for managing accounts, according to some embodiments. [Figure 19P] 1 illustrates an exemplary user interface for managing accounts, according to some embodiments. [Figure 19Q] 1 illustrates an exemplary user interface for managing accounts, according to some embodiments. [Figure 19R] 1 illustrates an exemplary user interface for managing accounts, according to some embodiments. [Figure 19S] 1 illustrates an exemplary user interface for managing accounts, according to some embodiments. [Figure 19T] 1 illustrates an exemplary user interface for managing accounts, according to some embodiments. [Figure 19U] 1 illustrates an exemplary user interface for managing accounts, according to some embodiments. [Figure 19V] 1 illustrates an exemplary user interface for managing accounts, according to some embodiments. [Figure 19W] 1 illustrates an exemplary user interface for managing accounts, according to some embodiments.
[0068] [Figure 20] FIG. 1 is a flow diagram illustrating a method for managing rewards for an account, according to some embodiments.
[0069] [Figure 21] FIG. 1 is a flow diagram illustrating a method for managing rewards for an account, according to some embodiments. DETAILED DESCRIPTION OF THE INVENTION
[0070] The following description sets forth example methods, parameters, etc. However, it should be recognized that such description is not intended as a limitation on the scope of the present disclosure, but rather is provided as a description of example embodiments.
[0071] There is a need for electronic devices that provide efficient methods and interfaces for managing accounts. Such technology can reduce the cognitive burden on users managing accounts, thereby increasing productivity. Furthermore, such technology can reduce processor and battery power that is otherwise wasted on redundant user input.
[0072] 1A-1B, 2, 3, 4A-4B, and 5A-5B provide a description of an example device for performing techniques for managing event notifications. FIG. 5C illustrates example devices connected via one or more communication channels according to some embodiments. FIGS. 6A-6D illustrate example user interfaces for managing storage account numbers. FIGS. 7A-7M illustrate example user interfaces for managing virtual account numbers. FIG. 8 is a flow diagram illustrating a method for managing account numbers according to some embodiments. The user interfaces of FIGS. 6A-6D and 7A-7M are used to illustrate processes described below, including the process of FIG. 8. FIGS. 9A-9C illustrate example user interfaces for provisioning a storage account. FIGS. 10A-10H illustrate example user interfaces for provisioning an account. FIG. 11 is a flow diagram illustrating a method for provisioning an account according to some embodiments. The user interfaces of FIGS. 9A-9C and 10A-10H are used to illustrate processes described below, including the process of FIG. 11. FIGS. 12A-12C show example user interfaces for obfuscating storage account credentials. FIGS. 13A-13J show example user interfaces for obfuscating account credentials. FIG. 14 is a flow diagram illustrating a method for obfuscating account credentials, according to some embodiments. The user interfaces of FIGS. 12A-12C and 13A-13J are used to illustrate processes described below, including the process of FIG. 14. FIGS. 15A-15E show example user interfaces for managing orders. FIGS. 16A-16L show example user interfaces for managing orders. FIG. 17 is a flow diagram illustrating a method for managing orders, according to some embodiments. The user interfaces of FIGS. 15A-15E and 16A-16L are used to illustrate processes described below, including the process of FIG. 17. FIG. 18 shows an example user interface for managing account rewards.19A-19W show example user interfaces for managing account rewards. FIG. 20 is a flow diagram illustrating a method for managing account rewards, according to some embodiments. FIG. 21 is a flow diagram illustrating a method for managing account rewards, according to some embodiments. The user interfaces of FIG. 18 and FIG. 19A-19W are used to illustrate processes described below, including the processes of FIG. 20 and FIG. 21.
[0073] The processes described below enhance the usability of a device and streamline the user-device interface (e.g., by helping the user provide appropriate inputs when operating / interacting with the device and reducing user errors) through various techniques, including providing improved visual feedback to the user, reducing the number of inputs required to perform an action, providing additional control options without cluttering the user interface with additionally displayed controls, performing an action without requiring further user input when a set of conditions is met, and / or other techniques. These techniques also reduce power usage and improve the device's battery life by allowing the user to use the device more quickly and efficiently.
[0074] Furthermore, for methods described herein in which one or more steps are conditioned on one or more conditions being satisfied, it should be understood that the described method can be repeated in multiple iterations, such that over the course of the iterations, all of the conditions on which the method steps are conditioned are satisfied in different iterations of the method. For example, if a method requires performing a first step if a condition is satisfied and a second step if the condition is not satisfied, one skilled in the art will understand that the steps recited in the claim are repeated in a particular order until the conditions are satisfied and then no longer satisfied. Thus, a method described with one or more steps that depend on one or more conditions being satisfied can be rewritten as a method that is repeated until each condition recited in the method is satisfied. However, this is not required for system or computer-readable medium claims in which the system or computer-readable medium includes instructions that perform a conditional action based on the satisfaction of the corresponding one or more conditions, and thus can determine whether a contingency is met without explicitly repeating the method steps until all conditions on which the method steps are conditioned are satisfied. Those skilled in the art will also understand that, as with methods having conditional steps, the system or computer-readable storage medium may repeat the steps of the method as many times as necessary to ensure that all of the conditional steps have been performed.
[0075] In the following description, terms such as "first" and "second" are used to describe various elements, but these elements should not be limited by these terms. In some embodiments, these terms are used to distinguish one element from another. For example, a first touch can be referred to as a second touch, and similarly, a second touch can be referred to as a first touch, without departing from the scope of various described embodiments. In some embodiments, the first touch and the second touch are two separate references to the same touch. In some embodiments, the first touch and the second touch are both touches, but they are not the same touch.
[0076] The terminology used in the description of various embodiments set forth herein is for the purpose of describing particular embodiments only and is not intended to be limiting. In the description of the various embodiments set forth and in the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly dictates otherwise. Also, as used herein, the term "and / or" should be understood to refer to and include any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms "includes," "including," "comprises," and / or "comprising," as used herein, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.
[0077] The term "if" is interpreted, optionally, according to the context, to mean "when" or "upon," or "in response to determining" or "in response to detecting." Similarly, the phrases "if it is determined" or "if [a stated condition or event] is detected" are interpreted, optionally, according to the context, to mean "upon determining" or "in response to determining," or "upon detecting [the stated condition or event]" or "in response to detecting [the stated condition or event]."
[0078] Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the device is a portable communication device, such as a mobile phone, that also includes other functions, such as PDA and / or music player functions. Exemplary embodiments of portable multifunction devices include, but are not limited to, the iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, California. Optionally, other portable electronic devices, such as a laptop computer or tablet computer having a touch-sensitive surface (e.g., a touchscreen display and / or touchpad), are also used. It should also be understood that in some embodiments, the device is not a portable communication device, but rather a desktop computer having a touch-sensitive surface (e.g., a touchscreen display and / or touchpad). In some embodiments, the electronic device is a computer system in communication (e.g., via wired communication, via wireless communication) with a display generation component. The display generation component is configured to provide a visual output, such as a display via a CRT display, a display via an LED display, or a display via image projection. In some embodiments, the display generation component is integrated with the computer system. In some embodiments, the display generation component is separate from the computer system. As used herein, "displaying" content includes displaying content (e.g., video data rendered or decoded by display controller 156) by transmitting data (e.g., image data or video data) over a wired or wireless connection to an integrated or external display generation component to visually generate the content.
[0079] In the following discussion, electronic devices are described that include a display and a touch-sensitive surface, however, it should be understood that the electronic device optionally includes one or more other physical user-interface devices, such as a physical keyboard, a mouse, and / or a joystick.
[0080] The device typically supports a variety of applications, such as one or more of a drawing application, a presentation application, a word processing application, a website creation application, a disc authoring application, a spreadsheet application, a gaming application, a telephony application, a video conferencing application, an email application, an instant messaging application, a training support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, and / or a digital video player application.
[0081] Various applications running on the device optionally use at least one common physical user-interface device, such as a touch-sensitive surface. One or more features of the touch-sensitive surface and corresponding information displayed on the device are optionally adjusted and / or changed for each application and / or within individual applications. In this way, the common physical architecture of the device (such as the touch-sensitive surface) optionally supports various applications with user interfaces that are intuitive and transparent to the user.
[0082] Attention now turns to embodiments of portable devices with touch-sensitive displays. FIG. 1A is a block diagram illustrating portable multifunction device 100 having touch-sensitive display system 112, according to some embodiments. Touch-sensitive display 112 may conveniently be referred to as a "touch screen" and may also be known or referred to as a "touch-sensitive display system." Device 100 includes memory 102 (optionally including one or more computer-readable storage media), memory controller 122, one or more processing units (CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, input / output (I / O) subsystem 106, other input control devices 116, and external port 124. Device 100 optionally includes one or more optical sensors 164. Device 100 optionally includes one or more contact intensity sensors 165 that detect the intensity of a contact on device 100 (e.g., a touch-sensitive surface, such as touch-sensitive display system 112 of device 100). Device 100 optionally includes one or more tactile output generators 167 that generate tactile output on device 100 (e.g., generate tactile output on a touch-sensitive surface such as touch-sensitive display system 112 of device 100 or touchpad 355 of device 300). These components optionally communicate via one or more communication buses or signal lines 103.
[0083] As used herein and in the claims, the term “intensity” of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact) on the touch-sensitive surface, or a proxy for the force or pressure of a contact on the touch-sensitive surface. The intensity of a contact has a range of values that includes at least four distinct values and more typically includes hundreds (e.g., at least 256) distinct values. The intensity of a contact is optionally determined (or measured) using various techniques and various sensors or combinations of sensors. For example, one or more force sensors under or adjacent to the touch-sensitive surface are optionally used to measure force at various points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (e.g., weighted averaged) to determine an estimated force of the contact. Similarly, a pressure-sensitive tip of a stylus is optionally used to determine the pressure of the stylus on the touch-sensitive surface. Alternatively, the size and / or change in the contact area detected on the touch-sensitive surface, the capacitance and / or change in the capacitance of the touch-sensitive surface proximate the contact, and / or the resistance and / or change in the capacitance of the touch-sensitive surface proximate the contact are optionally used as a surrogate for the force or pressure of the contact on the touch-sensitive surface. In some implementations, the surrogate measure of the force or pressure of the contact is used directly to determine whether an intensity threshold is exceeded (e.g., the intensity threshold is described in units corresponding to the surrogate measure). In some implementations, the surrogate measure of the contact force or pressure is converted to an estimate of the force or pressure, and the estimate of the force or pressure is used to determine whether an intensity threshold is exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure). Using contact intensity as an attribute of user input allows users to access additional device functionality (e.g., on a touch-sensitive display) and / or receive user input (e.g., via a touch-sensitive display, touch-sensitive surface, or physical / mechanical controls such as knobs or buttons) that may not otherwise be accessible to users on devices of reduced size that have limited footprint for displaying affordances.
[0084] As used herein and in the claims, the term “tactile output” refers to a physical displacement of a device relative to a previous position of the device, a physical displacement of a component of the device (e.g., a touch-sensitive surface) relative to another component of the device (e.g., a housing), or a displacement of a component relative to the center of mass of the device, that will be detected by the user with the user's sense of touch. For example, in a situation where a device or a component of a device is in contact with a touch-sensitive surface of a user (e.g., the fingers, palm, or other part of the user's hand), the tactile output produced by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in a physical property of the device or a component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is optionally interpreted by the user as a “downclick” or “upclick” of a physical actuator button. In some cases, a user feels a tactile sensation such as a “downclick” or “upclick” even when there is no movement of a physical actuator button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user's action. As another example, movement of a touch-sensitive surface is optionally interpreted or perceived by a user as "roughness" of the touch-sensitive surface, even if there is no change in the smoothness of the touch-sensitive surface. While such user interpretation of touch depends on the user's personal sensory perception, there are many sensory perceptions of touch that are common to the majority of users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., "upclick," "downclick," "roughness"), unless otherwise specified, the generated tactile output corresponds to a physical displacement of the device, or a component of the device, that produces the described sensory perception for a typical (or average) user.
[0085] It should be understood that device 100 is only one example of a portable multifunction device, and that device 100 optionally has more or fewer components than those shown, optionally combines two or more components, or optionally has a different configuration or arrangement of its components. The various components shown in Figure 1A are implemented in hardware, software, or a combination of both hardware and software, including one or more signal processing circuits and / or application specific integrated circuits.
[0086] Memory 102 optionally includes high-speed random access memory, and optionally includes non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. Memory controller 122 optionally controls access to memory 102 by other components of device 100.
[0087] Peripheral interface 118 may be used to couple input and output peripherals of the device to CPU 120 and memory 102. One or more processors 120 operate or execute various software programs (e.g., computer programs (e.g., including instructions)) and / or instruction sets stored in memory 102 to perform various functions and process data for device 100. In some embodiments, peripheral interface 118, CPU 120, and memory controller 122 are optionally implemented on a single chip, such as chip 104. In some other embodiments, they are optionally implemented on separate chips.
[0088] RF (radio frequency) circuitry 108 transmits and receives RF signals, also called electromagnetic signals. RF circuitry 108 converts electrical signals to electromagnetic signals and electromagnetic signals to communicate with communication networks and other communication devices via electromagnetic signals. RF circuitry 108 optionally includes well-known circuitry for performing these functions, including, but not limited to, an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, etc. RF circuitry 108 optionally communicates via wireless communication with networks, such as the Internet, also known as the World Wide Web (WWW), an intranet, and / or wireless networks, such as cellular telephone networks, wireless local area networks (LANs) and / or metropolitan area networks (MANs), and with other devices. RF circuitry 108 optionally includes well-known circuitry for detecting near field communication (NFC) fields, such as by short-range radios. Wireless communication optionally uses any of a number of communication standards, protocols, and technologies, including Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packet access (HSDPA), high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual-Cell HSPA (Dual-Cell HSPA), and the like.HSPA, DC-HSPA, long term evolution (LTE), near field communication (NFC), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth®, Bluetooth Low Energy (BTLE), Wireless Fidelity (Wi-Fi)® (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n, and / or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, protocols for email (e.g., Internet message access protocol (IMAP) and / or post office protocol (POP)), instant messaging (e.g., extensible messaging and presence protocol), messaging and presence protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS), and / or Short Message Service (SMS), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document.
[0089] Audio circuit 110, speaker 111, and microphone 113 provide an audio interface between a user and device 100. Audio circuit 110 receives audio data from peripherals interface 118, converts the audio data into electrical signals, and transmits the electrical signals to speaker 111. Speaker 111 converts the electrical signals into sound waves audible to humans. Audio circuit 110 also receives electrical signals converted from sound waves by microphone 113. Audio circuit 110 converts the electrical signals into audio data and transmits the audio data to peripherals interface 118 for processing. The audio data is optionally retrieved from and / or transmitted to memory 102 and / or RF circuit 108 by peripherals interface 118. In some embodiments, audio circuit 110 also includes a headset jack (e.g., 212 in FIG. 2 ). The headset jack provides an interface between audio circuitry 110 and a detachable audio input / output peripheral, such as an output-only headphone or a headset with both an output (e.g., mono or binaural headphones) and an input (e.g., a microphone).
[0090] I / O subsystem 106 couples input / output peripherals on device 100, such as touchscreen 112 and other input control devices 116, to peripheral interface 118. I / O subsystem 106 optionally includes display controller 156, optical sensor controller 158, depth camera controller 169, intensity sensor controller 159, haptic feedback controller 161, and one or more input controllers 160 for other input or control devices. One or more input controllers 160 receive / send electrical signals from / to other input control devices 116. Other input control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, etc. In some embodiments, input controller(s) 160 are optionally coupled to any (or none) of a keyboard, an infrared port, a USB port, and a pointer device such as a mouse. The one or more buttons (e.g., 208 in FIG. 2 ) optionally include up / down buttons for volume control of speaker 111 and / or microphone 113. The one or more buttons optionally include push buttons (e.g., 206 in FIG. 2 ). In some embodiments, the electronic device is a computer system in communication with one or more input devices (e.g., via wireless communication over wired communication). In some embodiments, the one or more input devices include a touch-sensitive surface (e.g., a trackpad as part of a touch-sensitive display). In some embodiments, the one or more input devices include one or more camera sensors (e.g., one or more optical sensors 164 and / or one or more depth camera sensors 175), such as for tracking user gestures (e.g., hand gestures and / or air gestures) as input. In some embodiments, the one or more input devices are integrated with the computer system. In some embodiments, the one or more input devices are separate from the computer system.In some embodiments, an air gesture is a gesture that is detected without the user touching an input element that is part of the device (or independent of an input element that is part of the device) and is based on detected movement of a part of the user's body in the air, including movement of the user's body relative to an absolute reference (e.g., the angle of the user's arm relative to the ground or the distance of the user's hand relative to the ground), movement of the user's body relative to another part of the user's body (e.g., movement of the user's hand relative to the user's shoulder, movement of the user's other hand relative to one of the user's hands, and / or movement of the user's fingers relative to another finger or part of the user's hand), and / or absolute movement of the user's body part (e.g., a tap gesture that includes movement of the hand in a predetermined pose by a predetermined amount and / or speed, or a shake gesture that includes rotation of the user's body part at a predetermined speed or amount).
[0091] A quick press of a push button optionally unlocks the touchscreen 112 or optionally initiates the process of unlocking the device using gestures on the touchscreen, as described in U.S. Patent Application Serial No. 11 / 322,549, filed December 23, 2005, "Unlocking a Device by Performing Gestures on an Unlock Image," U.S. Patent No. 7,657,849, which is incorporated herein by reference in its entirety. A longer press of a push button (e.g., 206) optionally turns power on or off to the device 100. The functionality of one or more of the buttons is optionally customizable by the user. The touchscreen 112 is used to implement virtual or soft buttons and one or more soft keyboards.
[0092] Touch-sensitive display 112 provides an input and output interface between the device and a user. Display controller 156 receives and / or sends electrical signals to touchscreen 112. Touchscreen 112 displays visual output to the user. This visual output optionally includes graphics, text, icons, animation, and any combination thereof (collectively "graphics"). In some embodiments, some or all of the visual output optionally corresponds to user interface objects.
[0093] Touchscreen 112 has a touch-sensitive surface, sensor, or set of sensors that accepts input from a user based on haptic and / or tactile contact. Touchscreen 112 and display controller 156 (along with any associated modules and / or instruction sets in memory 102) detects contacts (and any movement or cessation of contact) on touchscreen 112 and translates the detected contacts into interactions with user interface objects (e.g., one or more softkeys, icons, web pages, or images) displayed on touchscreen 112. In an exemplary embodiment, the point of contact between touchscreen 112 and the user corresponds to the user's finger.
[0094] Touchscreen 112 optionally uses LCD (liquid crystal display), LPD (light emitting polymer display), or LED (light emitting diode) technology, although other display technologies are used in other embodiments. Touchscreen 112 and display controller 156 optionally use any of a number of now known or later developed touch sensing technologies to detect contact and any movement or disruption thereof, including, but not limited to, capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements that determine one or more points of contact with touchscreen 112. In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as that found in the iPhone® and iPod Touch® from Apple Inc. of Cupertino, California.
[0095] The touch-sensitive display in some embodiments of touchscreen 112 is optionally similar to the multi-touch-sensing touchpad described in U.S. Patent Nos. 6,323,846 (Westerman et al.), 6,570,557 (Westerman et al.), and / or 6,677,932 (Westerman), and / or U.S. Patent Application Publication No. 2002 / 0015024 A1, each of which is incorporated by reference herein in its entirety. However, touchscreen 112 displays visual output from device 100, whereas touch-sensitive touchpads do not provide visual output.
[0096] The touch-sensitive display in some embodiments of touch screen 112 is described in the following applications: (1) U.S. patent application Ser. No. 11 / 381,313, filed May 2, 2006, entitled "Multipoint Touch Surface Controller," (2) U.S. patent application Ser. No. 10 / 840,862, filed May 6, 2004, entitled "Multipoint Touchscreen," (3) U.S. patent application Ser. No. 10 / 903,964, filed July 30, 2004, entitled "Gestures For Touch Sensitive Input Devices," (4) U.S. patent application Ser. No. 11 / 048,264, filed January 31, 2005, entitled "Gestures For Touch Sensitive Input Devices," and (5) U.S. patent application Ser. No. 11 / 038,590, filed January 18, 2005, entitled "Mode-Based Graphical User Interfaces For Touch Sensitive Input Devices." No. 11 / 228,758, filed September 16, 2005, entitled "Virtual Input Device Placement On A Touch Screen User Interface," (7) U.S. Patent Application No. 11 / 228,700, filed September 16, 2005, entitled "Operation Of A Computer With A Touch Screen Interface," (8) U.S. Patent Application No. 11 / 228,737, filed September 16, 2005, entitled "Activating Virtual Keys Of A Touch-Screen Virtual Keyboard," and (9) U.S. Patent Application No. 11 / 367,749, filed March 3, 2006, entitled "Multi-Functional Hand-Held Device," all of which are incorporated herein by reference in their entireties.
[0097] Touchscreen 112 optionally has a video resolution greater than 100 dpi. In some embodiments, the touchscreen has a video resolution of approximately 160 dpi. A user optionally contacts touchscreen 112 using any suitable object or accessory, such as a stylus, a finger, or the like. In some embodiments, the user interface is designed to operate primarily using finger-based contact and gestures, which may not be as precise as stylus-based input due to the larger contact area of a finger on the touchscreen. In some embodiments, the device translates the coarse finger input into precise pointer / cursor positions or commands to perform the action desired by the user.
[0098] In some embodiments, in addition to the touchscreen, device 100 optionally includes a touchpad for activating or deactivating certain functions. In some embodiments, the touchpad is a touch-sensitive area of the device that, unlike the touchscreen, does not display visual output. The touchpad is optionally a touch-sensitive surface separate from touchscreen 112 or an extension of the touch-sensitive surface formed by the touchscreen.
[0099] Device 100 also includes a power system 162 that provides power to the various components. Power system 162 optionally includes a power management system, one or more power sources (e.g., battery, alternating current (AC)), a recharging system, power failure detection circuitry, power converters or inverters, power status indicators (e.g., light emitting diodes (LEDs)), and any other components associated with the generation, management, and distribution of electrical power within a portable device.
[0100] Device 100 also optionally includes one or more optical sensors 164. FIG. 1A shows an optical sensor coupled to optical sensor controller 158 in I / O subsystem 106. Optical sensor 164 optionally includes a charge-coupled device (CCD) or a complementary metal-oxide semiconductor (CMOS) phototransistor. Optical sensor 164 receives light from the environment projected through one or more lenses and converts the light into data representing an image. Optical sensor 164 optionally works in conjunction with imaging module 143 (also called a camera module) to capture still images or video. In some embodiments, the optical sensor is located on the back side of device 100 opposite touchscreen display 112 on the front of the device, so that the touchscreen display can be used as a viewfinder for capturing still images and / or video. In some embodiments, the optical sensor is located on the front of the device so that an image of a user is optionally captured for video conferencing while the user views other video conference participants on the touchscreen display. In some embodiments, the position of the optical sensor 164 can be changed by the user (e.g., by rotating the lens and sensor within the device housing), so that a single optical sensor 164 is used for both video conferencing and capturing still images and / or video, along with a touchscreen display.
[0101] Device 100 also optionally includes one or more depth camera sensors 175. FIG. 1A shows a depth camera sensor coupled to depth camera controller 169 in I / O subsystem 106. Depth camera sensor 175 receives data from the environment and creates a three-dimensional model of an object (e.g., a face) in a scene from a viewpoint (e.g., the depth camera sensor). In some embodiments, in conjunction with imaging module 143 (also referred to as a camera module), depth camera sensor 175 is optionally used to determine a depth map of different portions of an image captured by imaging module 143. In some embodiments, a depth camera sensor is located on the front of device 100 to obtain images of the user with depth information for videoconferences and to capture selfie images with depth map data while the user views other videoconference participants on a touchscreen display. In some embodiments, depth camera sensor 175 is located on the back of the device, or on the back and front of device 100. In some embodiments, the position of the depth camera sensor 175 can be changed by the user (e.g., by rotating the lens and sensor within the device housing), so that the depth camera sensor 175 is used for both video conferencing and capturing still images and / or video, in conjunction with a touchscreen display.
[0102] Device 100 also optionally includes one or more contact intensity sensors 165. FIG. 1A shows a contact intensity sensor coupled to intensity sensor controller 159 in I / O subsystem 106. Contact intensity sensor 165 optionally includes one or more piezoresistive strain gauges, capacitive force sensors, electric force sensors, piezoelectric force sensors, optical force sensors, capacitive touch-sensitive surfaces, or other intensity sensors (e.g., sensors used to measure the force (or pressure) of a contact on a touch-sensitive surface). Contact intensity sensor 165 receives contact intensity information (e.g., pressure information, or a proxy for pressure information) from the environment. In some embodiments, at least one contact intensity sensor is juxtaposed with or proximate to the touch-sensitive surface (e.g., touch-sensitive display system 112). In some embodiments, at least one contact intensity sensor is located on the back of device 100, opposite touchscreen display 112, which is located on the front of device 100.
[0103] Device 100 also optionally includes one or more proximity sensors 166. Figure 1A shows proximity sensor 166 coupled to peripherals interface 118. Alternatively, proximity sensor 166 is optionally coupled to input controller 160 within I / O subsystem 106. Proximity sensor 166 optionally functions as described in U.S. patent application Ser. Nos. 11 / 241,839, "Proximity Detector In Handheld Device," 11 / 240,788, "Proximity Detector In Handheld Device," 11 / 620,702, "Using Ambient Light Sensor To Augment Proximity Sensor Output," 11 / 586,862, "Automated Response To And Sensing Of User Activity In Portable Devices," and 11 / 638,251, "Methods And Systems For Automatic Configuration Of Peripherals," which are incorporated herein by reference in their entireties. In some embodiments, the proximity sensor turns off and disables touchscreen 112 when the multifunction device is placed near the user's ear (e.g., when the user is making a phone call).
[0104] Device 100 also optionally includes one or more tactile output generators 167. FIG. 1A shows tactile output generators coupled to haptic feedback controller 161 in I / O subsystem 106. Tactile output generator 167 optionally includes one or more electroacoustic devices, such as speakers or other audio components, and / or electromechanical devices that convert energy into linear motion, such as motors, solenoids, electroactive polymers, piezoelectric actuators, electrostatic actuators, or other tactile output generating components (e.g., components that convert electrical signals into tactile output on the device). Contact intensity sensor 165 receives tactile feedback generation instructions from haptic feedback module 133 and generates a tactile output on device 100 that can be sensed by a user of device 100. In some embodiments, at least one tactile output generator is juxtaposed with or proximate to a touch-sensitive surface (e.g., touch-sensitive display system 112) and generates a tactile output, optionally by moving the touch-sensitive surface vertically (e.g., in / out of the surface of device 100) or horizontally (e.g., back and forth in the same plane as the surface of device 100). In some embodiments, at least one tactile output generator sensor is located on the back of device 100, opposite touchscreen display 112, which is located on the front of device 100.
[0105] Device 100 also optionally includes one or more accelerometers 168. FIG. 1A shows accelerometer 168 coupled to peripherals interface 118. Alternatively, accelerometer 168 is optionally coupled to input controller 160 in I / O subsystem 106. Accelerometer 168 optionally functions as described in U.S. Patent Application Publication No. 20050190059, "Acceleration-based Theft Detection System for Portable Electronic Devices," and U.S. Patent Application Publication No. 20060017692, "Methods And Apparatuses For Operating A Portable Device Based On An Accelerometer," both of which are incorporated herein by reference in their entireties. In some embodiments, information is displayed on the touchscreen display in portrait or landscape orientation based on an analysis of data received from the one or more accelerometers. In addition to accelerometer(s) 168, device 100 optionally includes a magnetometer and a GPS (or GLONASS or other global navigation system) receiver for obtaining information about the location and orientation (e.g., vertical or horizontal) of device 100.
[0106] In some embodiments, software components stored in memory 102 include operating system 126, communication module (or instruction set) 128, touch / motion module (or instruction set) 130, graphics module (or instruction set) 132, text input module (or instruction set) 134, Global Positioning System (GPS) module (or instruction set) 135, and applications (or instruction set) 136. Additionally, in some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3) stores device / global internal state 157, as shown in FIGS. 1A and 3. Device / global internal state 157 includes one or more of: active application state indicating which applications, if any, are currently active; display state indicating which applications, views, or other information occupy various regions of touchscreen display 112; sensor state including information obtained from the device's various sensors and input control devices 116; and location information regarding the device's location and / or orientation.
[0107] Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS, WINDOWS, or an embedded operating system such as VxWorks) includes various software components and / or drivers that control and manage general system tasks (e.g., memory management, storage device control, power management, etc.) and facilitate communication between various hardware and software components.
[0108] Communications module 128 facilitates communication with other devices via one or more external ports 124 and also includes various software components for processing data received by RF circuitry 108 and / or external port 124. External port 124 (e.g., Universal Serial Bus (USB), FIREWIRE, etc.) is adapted to couple to other devices directly or indirectly via a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is a multi-pin (e.g., 30-pin) connector that is the same as, similar to, and / or compatible with the 30-pin connector used on iPod® (trademark of Apple Inc.) devices.
[0109] Contact / motion module 130, optionally in conjunction with display controller 156, detects contact with touchscreen 112 and other touch-sensing devices (e.g., a touchpad or physical click wheel). Contact / motion module 130 includes various software components for performing various operations related to contact detection, such as determining whether contact occurs (e.g., detecting a finger-down event), determining the intensity of the contact (e.g., the force or pressure of the contact, or a surrogate for the force or pressure of the contact), determining whether there is contact movement and tracking the movement across the touch-sensitive surface (e.g., detecting one or more finger-drag events), and determining whether the contact has ceased (e.g., detecting a finger-up event or an interruption of the contact). Contact / motion module 130 receives contact data from the touch-sensitive surface. Determining the movement of the contact, as represented by the series of contact data, optionally includes determining the speed (magnitude), velocity (magnitude and direction), and / or acceleration (change in magnitude and / or direction) of the contact. These actions are optionally applied to a single contact (e.g., a single finger contact) or multiple simultaneous contacts (e.g., "multi-touch" / multiple finger contacts). In some embodiments, contact / motion module 130 and display controller 156 detect contacts on the touchpad.
[0110] In some embodiments, contact / motion module 130 uses a set of one or more intensity thresholds to determine whether an action has been performed by a user (e.g., to determine whether a user has “clicked” on an icon). In some embodiments, at least a subset of the intensity thresholds are determined according to software parameters (e.g., the intensity thresholds are not determined by the activation threshold of a particular physical actuator, but can be adjusted without modifying the physical hardware of device 100). For example, the mouse “click” threshold of a trackpad or touchscreen display can be set to any of a wide range of predefined thresholds without modifying the trackpad or touchscreen display hardware. Additionally, in some implementations, a user of the device is provided with a software setting to adjust one or more of the set of intensity thresholds (e.g., by adjusting individual intensity thresholds and / or by adjusting multiple intensity thresholds at once via a system-level click “intensity” parameter).
[0111] Contact / motion module 130 optionally detects gesture input by a user. Different gestures on the touch-sensitive surface have different contact patterns (e.g., different movements, timing, and / or intensities of detected contacts). Thus, gestures are optionally detected by detecting particular contact patterns. For example, detecting a finger tap gesture includes detecting a finger down event, followed by detecting a finger up (lift off) event at the same position (or substantially the same position) as the finger down event (e.g., the position of an icon). As another example, detecting a finger swipe gesture on the touch-sensitive surface includes detecting a finger down event, followed by one or more finger drag events, followed by detecting a finger up (lift off) event.
[0112] Graphics module 132 includes various known software components that render and display graphics on touchscreen 112 or other display, including components that modify the visual impact (e.g., brightness, transparency, saturation, contrast, or other visual properties) of the displayed graphics. As used herein, the term "graphic" includes any object that can be displayed to a user, including, but not limited to, text, web pages, icons (such as user interface objects including soft keys), digital images, video, animation, etc.
[0113] In some embodiments, graphics module 132 stores data representing graphics to be used. Each graphic is optionally assigned a corresponding code. Graphics module 132 receives one or more codes specifying the graphics to be displayed, including coordinate data and other graphic property data, as needed, from an application or the like, and then generates screen image data to output to display controller 156.
[0114] The tactile feedback module 133 includes various software components for generating instructions used by the tactile output generator(s) 167 to generate tactile outputs at one or more locations on the device 100 in response to a user's interaction with the device 100.
[0115] Text input module 134 is optionally a component of graphics module 132 and provides a soft keyboard for entering text in various applications (e.g., contacts module 137, email client module 140, IM module 141, browser module 147, and any other application requiring text input).
[0116] The GPS module 135 determines the location of the device and provides this information for use within various applications (e.g., to the phone module 138 for use in location-based dialing, to the camera module 143 as picture / video metadata, and to applications that provide location-based services such as a weather widget, a local yellow pages widget, and a maps / navigation widget).
[0117] Application 136 optionally includes the following modules (or sets of instructions), or a subset or superset thereof: ● a contacts module 137 (sometimes called an address book or contact list); ● Telephone module 138, ● Videoconferencing module 139; ● an email client module 140; ● Instant messaging (IM) module 141; ● Training support module 142, ● a camera module 143 for still images and / or video; ● Image management module 144; ● Video player module, ● Music player module, ● Browser module 147, ● Calendar module 148; • a widget module 149 optionally including one or more of a weather widget 149-1, a stock price widget 149-2, a calculator widget 149-3, an alarm clock widget 149-4, a dictionary widget 149-5, and other widgets obtained by the user, and a user-created widget 149-6; ● a widget creator module 150 for creating user-created widgets 149-6; ● Search module 151, a video and music player module 152 that integrates a video player module and a music player module; ● Memo module 153, Map module 154, and / or ● Online video module 155.
[0118] Examples of other applications 136 optionally stored in memory 102 include other word processing applications, other image editing applications, drawing applications, presentation applications, JAVA-enabled applications, encryption, digital rights management, voice recognition, and voice duplication.
[0119] Contacts module 137, along with touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, is optionally used to manage an address book or contact list (e.g., stored in memory 102 or in the application internal state 192 of contacts module 137 in memory 370), including adding name(s) to the address book, removing name(s) from the address book, associating phone number(s), email address(es), street address(es), or other information with names, associating images with names, categorizing and sorting names, providing phone numbers or email addresses to initiate and / or facilitate communication via telephone 138, videoconferencing module 139, email client module 140, or IM module 141, etc.
[0120] Telephone module 138, in conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, is optionally used to enter a series of characters corresponding to a telephone number, access one or more telephone numbers in contacts module 137, modify entered telephone numbers, dial individual telephone numbers, place calls, and disconnect and hang up when the call is complete. As previously mentioned, wireless communication optionally uses any of a number of communication standards, protocols, and technologies.
[0121] Videoconferencing module 139 includes executable instructions to cooperate with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touchscreen 112, display controller 156, optical sensor 164, optical sensor controller 158, touch / motion module 130, graphics module 132, text input module 134, contacts module 137, and telephone module 138 to initiate, conduct, and end a videoconference between a user and one or more other participants according to the user's commands.
[0122] Email client module 140, in conjunction with RF circuitry 108, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, contains executable instructions for composing, sending, receiving, and managing emails in response to user commands. In conjunction with image management module 144, email client module 140 greatly facilitates the creation and sending of emails with still or video images captured by camera module 143.
[0123] Instant messaging module 141 includes executable instructions, in conjunction with RF circuitry 108, touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, to enter a series of characters corresponding to an instant message, modify previously entered characters, send individual instant messages (e.g., using Short Message Service (SMS) or Multimedia Message Service (MMS) protocols for telephony-based instant messaging, or XMPP, SIMPLE, or IMPS for Internet-based instant messaging), receive instant messages, and view received instant messages. In some embodiments, sent and / or received instant messages optionally include graphics, photos, audio files, video files, and / or other attachments, such as those supported by MMS and / or Enhanced Messaging Service (EMS). As used herein, "instant messaging" refers to both telephony-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS).
[0124] In conjunction with the RF circuitry 108, touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, text input module 134, GPS module 135, map module 154, and music player module, the training support module 142 includes executable instructions to create workouts (e.g., with time, distance, and / or calorie burn goals), communicate with training sensors (sports devices), receive training sensor data, calibrate sensors used to monitor workouts, select and play music for workouts, and display, store, and transmit workout data.
[0125] Camera module 143, in conjunction with touchscreen 112, display controller 156, optical sensor(s) 164, optical sensor controller 158, contact / motion module 130, graphics module 132, and image management module 144, includes executable instructions to capture and store still images or video (including video streams) in memory 102, modify characteristics of still images or video, or delete still images or video from memory 102.
[0126] Image management module 144 includes executable instructions for arranging, modifying (e.g., editing), or otherwise manipulating, labeling, deleting, presenting (e.g., in a digital slideshow or album), and storing still and / or video images in conjunction with touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, text input module 134, and camera module 143.
[0127] Browser module 147, in conjunction with RF circuitry 108, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, contains executable instructions for browsing the Internet according to user commands, including retrieving, linking to, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.
[0128] The calendar module 148 includes executable instructions to cooperate with the RF circuitry 108, the touch screen 112, the display controller 156, the contact / motion module 130, the graphics module 132, the text input module 134, the email client module 140, and the browser module 147 to create, display, modify, and store calendars and data associated with the calendars (e.g., calendar items, to-do lists, etc.) according to user instructions.
[0129] Widget module 149, in conjunction with RF circuitry 108, touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, and browser module 147, optionally provides mini-applications (e.g., weather widget 149-1, stock price widget 149-2, calculator widget 149-3, alarm clock widget 149-4, and dictionary widget 149-5) downloaded and used by a user, or mini-applications created by a user (e.g., user-created widget 149-6). In some embodiments, a widget includes an HTML (Hypertext Markup Language) file, a CSS (Cascading Style Sheets) file, and a JavaScript file. In some embodiments, a widget includes an XML (Extensible Markup Language) file and a JavaScript file (e.g., Yahoo! Widgets).
[0130] The widget creator module 150, in conjunction with the RF circuitry 108, the touch screen 112, the display controller 156, the contact / motion module 130, the graphics module 132, the text input module 134, and the browser module 147, is optionally used by a user to create a widget (e.g., turn a user-specified portion of a web page into a widget).
[0131] The search module 151 includes executable instructions for working in conjunction with the touch screen 112, the display controller 156, the contact / motion module 130, the graphics module 132, and the text input module 134 to search for text, music, sound, images, video, and / or other files in the memory 102 that match one or more search criteria (e.g., one or more user-specified search terms) in accordance with a user's commands.
[0132] Video and music player module 152 includes executable instructions that, in conjunction with touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, and browser module 147, enable a user to download and play pre-recorded music and other sound files stored in one or more file formats, such as MP3 or AAC files, as well as executable instructions for displaying, presenting, or otherwise playing videos (e.g., on touchscreen 112 or on an external display connected via external port 124). In some embodiments, device 100 optionally includes the functionality of an MP3 player, such as an iPod (a trademark of Apple Inc.).
[0133] The notes module 153 includes executable instructions for working with the touch screen 112, the display controller 156, the contact / motion module 130, the graphics module 132, and the text input module 134 to create and manage notes, to-do lists, and the like according to user commands.
[0134] Map module 154, in conjunction with RF circuitry 108, touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147, is used to receive, display, modify, and store maps and data associated with maps (e.g., driving directions, data regarding businesses and other points of interest at or near a particular location, and other location-based data), optionally in accordance with user instructions.
[0135] Online video module 155, in conjunction with touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, text input module 134, email client module 140, and browser module 147, contains instructions that enable a user to access, browse for, receive (e.g., by streaming and / or downloading), and play (e.g., on the touchscreen or on an external display connected via external port 124) particular online videos, send emails with links to particular online videos, and otherwise manage online videos in one or more file formats, such as H.264. In some embodiments, instant messaging module 141 is used to send links to particular online videos, rather than email client module 140. For additional description of online video applications, see U.S. Provisional Patent Application No. 60 / 936,562, filed June 20, 2007, entitled "Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos," and U.S. Patent Application No. 11 / 968,067, filed December 31, 2007, entitled "Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos," the contents of which are incorporated herein by reference in their entireties.
[0136] The above-identified modules and applications each correspond to sets of executable instructions that perform one or more of the functions and methods described herein (e.g., the computer-implemented methods and other information processing methods described herein). These modules (e.g., sets of instructions) need not be implemented as respective software programs (e.g., computer programs (e.g., including instructions)), procedures, or modules; thus, in various embodiments, various subsets of these modules are optionally combined or otherwise rearranged. For example, a video player module is optionally combined with a music player module into a single module (e.g., video and music player module 152 of FIG. 1A). In some embodiments, memory 102 optionally stores a subset of the above-identified modules and data structures. Additionally, memory 102 optionally stores additional modules and data structures not described above.
[0137] In some embodiments, device 100 is a device in which operation of a predetermined set of functions on the device is performed solely via a touchscreen and / or touchpad. Using the touchscreen and / or touchpad as the primary input control device for operation of device 100 optionally reduces the number of physical input control devices (push buttons, dials, etc.) on device 100.
[0138] The set of predefined functions performed only through the touchscreen and / or touchpad optionally includes navigation between user interfaces. In some embodiments, the touchpad, when touched by a user, navigates device 100 to a main menu, home menu, or root menu from any user interface displayed on device 100. In such embodiments, a "menu button" is implemented using the touchpad. In some other embodiments, the menu button is a physical push button or other physical input control device rather than a touchpad.
[0139] 1B is a block diagram illustrating exemplary components for event processing, according to some embodiments. In some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3) includes an event sorter 170 (e.g., within operating system 126) and a separate application 136-1 (e.g., any of applications 137-151, 155, 380-390 described above).
[0140] Event sorter 170 receives the event information and determines which application 136-1 to deliver the event information to and application view 191 for application 136-1. Event sorter 170 includes event monitor 171 and event dispatcher module 174. In some embodiments, application 136-1 includes application internal state 192 that indicates the current application view(s) that are displayed on touch-sensitive display 112 when the application is active or running. In some embodiments, device / global internal state 157 is used by event sorter 170 to determine which application(s) are currently active, and application internal state 192 is used by event sorter 170 to determine which application(s) are currently active, and application internal state 192 is used by event sorter 170 to determine which application view(s) to deliver the event information to.
[0141] In some embodiments, application internal state 192 includes additional information such as one or more of resume information to be used when application 136-1 resumes execution, user interface state information indicating or ready to display information being displayed by application 136-1, state cues that allow the user to return to a previous state or view of application 136-1, and redo / undo cues for previous actions taken by the user.
[0142] Event monitor 171 receives event information from peripherals interface 118. The event information includes information about sub-events (e.g., a user touch as part of a multi-touch gesture on touch-sensitive display 112). Peripherals interface 118 transmits information it receives from I / O subsystem 106 or sensors such as proximity sensor 166, accelerometer(s) 168, and / or microphone 113 (via audio circuitry 110). Information that peripherals interface 118 receives from I / O subsystem 106 includes information from touch-sensitive display 112 or a touch-sensitive surface.
[0143] In some embodiments, event monitor 171 sends requests to peripherals interface 118 at predetermined intervals. In response, peripherals interface 118 transmits event information. In other embodiments, peripherals interface 118 transmits event information only when there is a significant event (e.g., receipt of an input above a predetermined noise threshold and / or for more than a predetermined duration).
[0144] In some embodiments, the event sorter 170 also includes a hit view determination module 172 and / or an active event recognizer determination module 173 .
[0145] Hit view determination module 172 provides software procedures that determine where a sub-event occurred within one or more views when touch-sensitive display 112 displays more than one view. A view consists of the controls and other elements that a user can see on the display.
[0146] Another aspect of a user interface associated with an application is the set of views, sometimes referred to herein as application views or user interface windows, in which information is displayed and touch-based gestures occur. The application views (of individual applications) in which touches are detected optionally correspond to programmatic levels within the application's programmatic or view hierarchy. For example, the lowest-level view in which a touch is detected is optionally referred to as the hit view, and the set of events that are recognized as appropriate inputs is optionally determined based at least in part on the hit view of the initial touch that initiates the touch gesture.
[0147] Hit view determination module 172 receives information related to sub-events of a touch-based gesture. When an application has multiple views organized in a hierarchy, hit view determination module 172 identifies the hit view as the lowest view in the hierarchy that should process the sub-events. In most situations, the hit view is the lowest-level view in which an initiating sub-event occurs (e.g., the first sub-event in a series of sub-events that form an event or potential event). Once a hit view is identified by hit view determination module 172, the hit view typically receives all sub-events related to the same touch or input source identified as the hit view.
[0148] Active event recognizer determination module 173 determines which view(s) in the view hierarchy should receive a particular sequence of sub-events. In some embodiments, active event recognizer determination module 173 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, active event recognizer determination module 173 determines that all views that contain the physical location of the sub-events are actively participating views, and therefore determines that all actively participating views should receive a particular sequence of sub-events. In other embodiments, even if a touch sub-event is completely confined to the area associated with one particular view, views higher in the hierarchy still remain actively participating views.
[0149] Event dispatcher module 174 dispatches event information to event recognizers (e.g., event recognizer 180). In embodiments that include active event recognizer determination module 173, event dispatcher module 174 delivers event information to the event recognizers determined by active event recognizer determination module 173. In some embodiments, event dispatcher module 174 stores event information in an event queue, which is retrieved by individual event receivers 182.
[0150] In some embodiments, operating system 126 includes event sorter 170. Alternatively, application 136-1 includes event sorter 170. In still other embodiments, event sorter 170 is a stand-alone module or is part of another module stored in memory 102, such as contact / motion module 130.
[0151] In some embodiments, application 136-1 includes multiple event handlers 190 and one or more application views 191, each containing instructions for processing touch events that occur within a separate view of the application's user interface. Each application view 191 of application 136-1 includes one or more event recognizers 180. Typically, an individual application view 191 includes multiple event recognizers 180. In other embodiments, one or more of the event recognizers 180 are part of a separate module, such as a user interface kit or a higher-level object from which application 136-1 inherits methods and other properties. In some embodiments, individual event handlers 190 include one or more of data updater 176, object updater 177, GUI updater 178, and / or event data 179 received from event sorter 170. Event handler 190 optionally utilizes or invokes data updater 176, object updater 177, or GUI updater 178 to update application internal state 192. Alternatively, one or more of the application views 191 include one or more respective event handlers 190. Also, in some embodiments, one or more of the data updater 176, the object updater 177, and the GUI updater 178 are included in individual application views 191.
[0152] A separate event recognizer 180 receives event information (e.g., event data 179) from event sorter 170 and identifies events from the event information. Event recognizer 180 includes an event receiver 182 and an event comparator 184. In some embodiments, event recognizer 180 also includes metadata 183 and at least a subset of event delivery instructions 188 (optionally including sub-event delivery instructions).
[0153] The event receiver 182 receives event information from the event sorter 170. The event information includes information about a sub-event, e.g., a touch or a movement of a touch. Depending on the sub-event, the event information also includes additional information, such as the location of the sub-event. When the sub-event involves a movement of a touch, the event information also optionally includes the speed and direction of the sub-event. In some embodiments, the event includes a rotation of the device from one orientation to another (e.g., from portrait to landscape or vice versa), and the event information includes corresponding information about the current orientation of the device (also called the device's posture).
[0154] The event comparator 184 compares the event information to predefined event or sub-event definitions and determines the event or sub-event, or determines or updates the state of the event or sub-event, based on the comparison. In some embodiments, the event comparator 184 includes an event definition 186. The event definition 186 includes definitions of events (e.g., a predefined set of sub-events), such as Event 1 (187-1) and Event 2 (187-2). In some embodiments, sub-events within Events (187-1 and / or 187-2) include, for example, touch start, touch end, touch movement, touch cancellation, and multiple touches. In one example, the definition for Event 1 (187-1) is a double tap on a displayed object. The double tap includes, for example, a first touch on a displayed object relative to a predetermined phase (touch start), a first lift-off (touch end) relative to the predetermined phase, a second touch on a displayed object relative to the predetermined phase (touch start), and a second lift-off (touch end) relative to the predetermined phase. In another example, a definition of event 2 (187-2) is a drag on a displayed object. Drag includes, for example, a touch (or contact) on the displayed object to a predetermined stage, a movement of the touch across the touch-sensitive display 112, and a lift-off of the touch (touch end). In some embodiments, the event also includes information about one or more associated event handlers 190.
[0155] In some embodiments, event definition 186 includes definitions of events for individual user interface objects. In some embodiments, event comparator 184 performs a hit test to determine which user interface objects are associated with the sub-event. For example, if a touch is detected on touch-sensitive display 112 in an application view in which three user interface objects are displayed on touch-sensitive display 112, event comparator 184 performs a hit test to determine which of the three user interface objects is associated with the touch (sub-event). If each displayed object is associated with a separate event handler 190, event comparator 184 uses the results of the hit test to determine which event handler 190 to activate. For example, event comparator 184 selects the event handler associated with the sub-event and object that triggers the hit test.
[0156] In some embodiments, the definition of an individual event 187 also includes a delay action that delays delivery of the event information until it is determined whether a set of sub-events corresponds to the event recognizer's event type.
[0157] If the individual event recognizer 180 determines that the sequence of sub-events does not match any of the events in the event definition 186, the individual event recognizer 180 enters an event disabled, event failed, or event finished state, after which it ignores the next sub-event of the touch-based gesture. In this situation, any other event recognizers that remain active for the hit view continue to track and process sub-events of the ongoing touch gesture.
[0158] In some embodiments, individual event recognizers 180 include metadata 183 with configurable properties, flags, and / or lists that indicate to actively participating event recognizers how the event delivery system should perform sub-event delivery. In some embodiments, metadata 183 includes configurable properties, flags, and / or lists that indicate how event recognizers interact with each other or how event recognizers are allowed to interact with each other. In some embodiments, metadata 183 includes configurable properties, flags, and / or lists that indicate how sub-events are delivered to various levels in the view or programmatic hierarchy.
[0159] In some embodiments, an individual event recognizer 180 activates an event handler 190 associated with an event when one or more specific sub-events of the event are recognized. In some embodiments, the individual event recognizer 180 delivers event information associated with the event to the event handler 190. Activating the event handler 190 is separate from sending (and postponing sending) sub-events to the individual hit view. In some embodiments, the event recognizer 180 pops a flag associated with the recognized event, and the event handler 190 associated with the flag catches the flag and performs a predetermined process.
[0160] In some embodiments, the event delivery instructions 188 include sub-event delivery instructions that deliver event information about a sub-event without activating an event handler. Instead, the sub-event delivery instructions deliver the event information to an event handler associated with a set of sub-events or to an actively participating view. The event handler associated with the set of sub-events or the actively participating view receives the event information and performs a predetermined process.
[0161] In some embodiments, data updater 176 creates and updates data used by application 136-1. For example, data updater 176 updates phone numbers used by contacts module 137 or stores video files used by a video player module. In some embodiments, object updater 177 creates and updates objects used by application 136-1. For example, object updater 177 creates new user interface objects or updates the positions of user interface objects. GUI updater 178 updates the GUI. For example, GUI updater 178 prepares display information and sends the display information to graphics module 132 for display on the touch-sensitive display.
[0162] In some embodiments, event handler(s) 190 include or have access to data updater 176, object updater 177, and GUI updater 178. In some embodiments, data updater 176, object updater 177, and GUI updater 178 are included in a single module of an individual application 136-1 or application view 191. In other embodiments, they are included in two or more software modules.
[0163] It should be understood that the foregoing description of event processing of a user's touch on a touch-sensitive display also applies to other forms of user input for operating multifunction device 100 using input devices, although not all of them are initiated on a touchscreen. For example, mouse movements and mouse button presses, contact movements such as tapping, dragging, scrolling on a touchpad, optionally coordinated with single or multiple keyboard presses or holds, pen stylus input, device movement, verbal commands, detected eye movements, biometric input, and / or any combination thereof, optionally utilize as inputs corresponding to sub-events that define the event to be recognized.
[0164] FIG. 2 illustrates portable multifunction device 100 having touchscreen 112, according to some embodiments. The touchscreen optionally displays one or more graphics within user interface (UI) 200. In this embodiment, as well as other embodiments described below, a user may select one or more of the graphics by performing a gesture on the graphics, for example, using one or more fingers 202 (not drawn to scale) or one or more styluses 203 (not drawn to scale). In some embodiments, selection of one or more graphics is performed when the user breaks contact with the one or more graphics. In some embodiments, the gesture optionally includes one or more taps, one or more swipes (left to right, right to left, upward and / or downward), and / or rolling (right to left, left to right, upward and / or downward) of a finger in contact with device 100. In some implementations or situations, accidental contact with a graphic does not select the graphic, for example, if the gesture corresponding to selection is a tap, a swipe gesture sweeping over an application icon optionally does not select the corresponding application.
[0165] Device 100 also optionally includes one or more physical buttons, such as a "home" button or menu button 204. As previously mentioned, menu button 204 is optionally used to navigate to any application 136 within a set of applications running on device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key within a GUI displayed on touchscreen 112.
[0166] In some embodiments, device 100 includes touchscreen 112, menu button 204, pushbutton 206 for powering the device on / off and locking the device, volume control button(s) 208, subscriber identity module (SIM) card slot 210, headset jack 212, and external docking / charging port 124. Pushbutton 206 is optionally used to power the device on / off by pressing and holding the button down for a predetermined period of time, to lock the device by pressing and releasing the button before the predetermined time has elapsed, and / or to unlock the device or initiate the unlocking process. In alternative embodiments, device 100 also accepts verbal input via microphone 113 to activate or deactivate certain functions. Device 100 also optionally includes one or more contact intensity sensors 165 for detecting the intensity of a contact on touchscreen 112 and / or one or more tactile output generators 167 for generating a tactile output for a user of device 100.
[0167] FIG. 3 is a block diagram of an exemplary multifunction device having a display and a touch-sensitive surface, according to some embodiments. Device 300 need not be portable. In some embodiments, device 300 is a laptop computer, a desktop computer, a tablet computer, a multimedia player device, a navigation device, an educational device (such as a child's learning toy), a gaming system, or a control device (e.g., a home or commercial controller). Device 300 typically includes one or more processing units (CPUs) 310, one or more network or other communication interfaces 360, memory 370, and one or more communication buses 320 interconnecting these components. Communication bus 320 optionally includes circuitry (sometimes called a chipset) that interconnects and controls communication between system components. Device 300 includes input / output (I / O) interface 330, including display 340, which is typically a touchscreen display. I / O interface 330 also optionally includes a keyboard and / or mouse (or other pointing device) 350 and a touchpad 355, a tactile output generator 357 that generates tactile output on device 300 (e.g., similar to tactile output generator(s) 167 described above with reference to FIG. 1A ), and sensors 359 (e.g., light, acceleration, proximity, touch-sensing, and / or contact intensity sensors similar to contact intensity sensor(s) 165 described above with reference to FIG. 1A ). Memory 370 includes high-speed random-access memory such as DRAM, SRAM, DDR RAM, or other random-access solid-state memory devices, and optionally includes non-volatile memory such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. Memory 370 optionally includes one or more storage devices located remotely from CPU(s) 310.In some embodiments, memory 370 stores programs, modules, and data structures similar to, or a subset of, programs, modules, and data structures stored in memory 102 of portable multifunction device 100 (FIG. 1A). Additionally, memory 370 optionally stores additional programs, modules, and data structures not present in memory 102 of portable multifunction device 100. For example, memory 370 of device 300 optionally stores drawing module 380, presentation module 382, word processing module 384, website creation module 386, disk authoring module 388, and / or spreadsheet module 390, whereas memory 102 of portable multifunction device 100 (FIG. 1A) optionally does not store these modules.
[0168] Each of the above-identified elements of FIG. 3 is optionally stored in one or more of the memory devices mentioned above. Each of the above-identified modules corresponds to an instruction set that performs the functions mentioned above. The above-identified modules or computer programs (e.g., including an instruction set or instructions) need not be implemented as separate software programs (e.g., computer programs (e.g., including instructions)), procedures, or modules; thus, in various embodiments, various subsets of these modules are optionally combined or otherwise reconfigured. In some embodiments, memory 370 optionally stores a subset of the above-identified modules and data structures. Additionally, memory 370 optionally stores additional modules and data structures not described above.
[0169] Attention is now optionally directed to user interface embodiments, for example, as implemented on portable multifunction device 100.
[0170] 4A shows an exemplary user interface for a menu of applications on portable multifunction device 100, according to some embodiments. A similar user interface is optionally implemented on device 300. In some embodiments, user interface 400 includes the following elements, or a subset or superset thereof: ● signal strength indicator(s) 402 for wireless communication(s), such as cellular and Wi-Fi signals; ● Time 404, ● Bluetooth indicator 405, ● Battery status indicator 406; A tray 408 with icons of frequently used applications, such as: o An icon 416 for the phone module 138, labeled "Phone", which optionally includes an indicator 414 of the number of missed calls or voicemail messages; an icon 418 for the email client module 140, labeled "Mail," which optionally includes an indicator 410 of the number of unread emails; ○ An icon 420 for the browser module 147, labeled "Browser"; and o An icon 422 for the video and music player module 152, also called the iPod (trademark of Apple Inc.) module 152, labeled "iPod"; and ● Icons of other applications, such as: ○ Icon 424 of IM module 141, labeled "Messages" ○ Icon 426 of the Calendar module 148, labeled "Calendar"; ○ Icon 428 in the image management module 144, labeled "Photos" ○ An icon 430 of the camera module 143, labeled "camera"; ○ Icon 432 of the Online Video module 155, labeled "Online Video"; Icon 434 of Stocks widget 149-2, labeled "Stocks" ○ Icon 436 of the map module 154, labeled "Map" ○ Icon 438 of weather widget 149-1, labeled "Weather" ○ Icon 440 of alarm clock widget 149-4, labeled "Clock" ○ Icon 442 of Training Support module 142, labeled "Training Support"; icon 444 of the Notes module 153, labeled "Notes"; and o A settings application or module icon 446 labeled "Settings" that provides access to settings for the device 100 and its various applications 136.
[0171] Note that the icon labels shown in FIG. 4A are merely exemplary. For example, icon 422 of video and music player module 152 is labeled "Music" or "Music Player." Other labels are optionally used for various application icons. In some embodiments, the label for an individual application icon includes the name of the application that corresponds to the individual application icon. In some embodiments, the label of a particular application icon is different from the name of the application that corresponds to that particular application icon.
[0172] 4B shows an example user interface on a device (e.g., device 300 of FIG. 3 ) that has touch-sensitive surface 451 (e.g., tablet or touchpad 355 of FIG. 3 ) that is separate from display 450 (e.g., touchscreen display 112). Device 300 also optionally includes one or more contact intensity sensors (e.g., one or more of sensors 359) that detect the intensity of a contact on touch-sensitive surface 451, and / or one or more tactile output generators 357 that generate a tactile output for a user of device 300.
[0173] Although some of the following examples are given with reference to input on touchscreen display 112 (which combines a touch-sensitive surface and a display), in some embodiments, the device detects input on a touch-sensitive surface that is separate from the display, as shown in FIG. 4B . In some embodiments, the touch-sensitive surface (e.g., 451 in FIG. 4B ) has a primary axis (e.g., 452 in FIG. 4B ) that corresponds to a primary axis (e.g., 453 in FIG. 4B ) on the display (e.g., 450). According to these embodiments, the device detects contact with touch-sensitive surface 451 (e.g., 460 and 462 in FIG. 4B ) at locations that correspond to respective locations on the display (e.g., in FIG. 4B , 460 corresponds to 468 and 462 corresponds to 470). In this way, user input (e.g., contacts 460 and 462 and their movement) detected by the device on the touch-sensitive surface (e.g., 451 in FIG. 4B ) is used by the device to operate a user interface on the display (e.g., 450 in FIG. 4B ) of the multifunction device when the touch-sensitive surface is separate from the display. It should be understood that similar methods are optionally used for the other user interfaces described herein.
[0174] Additionally, while the following examples are given primarily with reference to finger input (e.g., finger contact, finger tap gesture, finger swipe gesture), it should be understood that in some embodiments, one or more of the finger inputs are replaced with input from another input device (e.g., mouse-based input or stylus input). For example, a swipe gesture is optionally replaced by a mouse click (e.g., instead of a contact) followed by movement of a cursor along the path of the swipe (e.g., instead of movement of the contact). As another example, a tap gesture is optionally replaced by a mouse click (e.g., instead of detecting a contact and then ceasing contact detection) while the cursor is positioned over the location of the tap gesture. Similarly, it should be understood that when multiple user inputs are detected simultaneously, multiple computer mice are optionally used simultaneously, or a mouse and finger contacts are optionally used simultaneously.
[0175] FIG. 5A shows an exemplary personal electronic device 500. Device 500 includes a main body 502. In some embodiments, device 500 can include some or all of the functionality described with respect to devices 100 and 300 (e.g., FIGS. 1A-4B ). In some embodiments, device 500 has a touch-sensitive display screen 504, hereafter touchscreen 504. Alternatively, or in addition to touchscreen 504, device 500 has a display and a touch-sensitive surface. Similar to devices 100 and 300, in some embodiments, touchscreen 504 (or the touch-sensitive surface) optionally includes one or more intensity sensors that detect the intensity of contact (e.g., touches) being applied. The one or more intensity sensors of touchscreen 504 (or the touch-sensitive surface) can provide output data representing the intensity of the touch. The user interface of device 500 can respond to touches based on their intensity, meaning that touches of different intensities can invoke different user interface actions on device 500.
[0176] For exemplary techniques for detecting and processing touch intensity, see, for example, related applications International Patent Application No. PCT / US2013 / 040061, filed May 8, 2013, entitled "Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application," published as International Publication No. WO / 2013 / 169849, and International Patent Application No. PCT / US2013 / 069483, filed November 11, 2013, entitled "Device, Method, and Graphical User Interface for Transitioning Between Touch Input to Display Output Relationships," published as International Publication No. WO / 2014 / 105276, each of which is incorporated herein by reference in its entirety.
[0177] In some embodiments, device 500 has one or more input mechanisms 506 and 508. Input mechanisms 506 and 508, if included, may be physical. Examples of physical input mechanisms include push buttons and rotatable mechanisms. In some embodiments, device 500 has one or more attachment mechanisms. Such attachment mechanisms, if included, may allow device 500 to be attached to, for example, hats, eyewear, earrings, necklaces, shirts, jackets, bracelets, watch bands, chains, pants, belts, shoes, wallets, backpacks, etc. These attachment mechanisms allow device 500 to be worn by a user.
[0178] FIG. 5B illustrates an exemplary personal electronic device 500. In some embodiments, device 500 can include some or all of the components described with respect to FIGS. 1A, 1B, and 3. Device 500 has a bus 512 that operably couples an I / O section 514 to one or more computer processors 516 and a memory 518. I / O section 514 can be connected to a display 504, which can have touch-sensing components 522 and, optionally, an intensity sensor 524 (e.g., a contact intensity sensor). Additionally, I / O section 514 can be connected to a communication unit 530 that receives application and operating system data using Wi-Fi, Bluetooth, near field communication (NFC), cellular, and / or other wireless communication technologies. Device 500 can include input mechanisms 506 and / or 508. Input mechanism 506 is optionally, for example, a rotatable input device or a depressible and rotatable input device. In some embodiments, input mechanism 508 is optionally a button.
[0179] In some embodiments, input mechanism 508 is optionally a microphone. Personal electronic device 500 optionally includes various sensors, such as a GPS sensor 532, an accelerometer 534, an orientation sensor 540 (e.g., a compass), a gyroscope 536, a motion sensor 538, and / or combinations thereof, all of which may be operably connected to I / O section 514.
[0180] The memory 518 of the personal electronic device 500 may include one or more non-transitory computer-readable storage media for storing computer-executable instructions that, when executed by one or more computer processors 516, can cause the computer processors to perform the techniques described below, including, for example, process 800 ( FIG. 8 ), process 1100 ( FIG. 11 ), process 1400 ( FIG. 14 ), process 1700 ( FIG. 17 ), process 2000 ( FIG. 20 ), and process 2100 ( FIG. 21 ). A computer-readable storage medium may be any medium that can tangibly contain or store computer-executable instructions used by or in connection with an instruction execution system, apparatus, or device. In some embodiments, the storage medium is a transient computer-readable storage medium. In some embodiments, the storage medium is a non-transitory computer-readable storage medium. Non-transitory computer-readable storage media may include, but are not limited to, magnetic storage, optical storage, and / or semiconductor storage. Examples of such storage devices include magnetic disks, optical disks based on CD, DVD, or Blu-ray technology, and persistent solid-state memory such as flash, solid-state drives, etc. Personal electronic device 500 is not limited to the components and configuration of Figure 5B and may include other or additional components in multiple configurations.
[0181] As used herein, the term "affordance" refers to a user-interactive graphical user interface object, optionally displayed on a display screen of device 100, 300, and / or 500 (FIGS. 1A, 3, and 5A-5B). For example, images (e.g., icons), buttons, and text (e.g., hyperlinks) each, optionally, constitute an affordance.
[0182] As used herein, the term “focus selector” refers to an input element that indicates the current portion of the user interface with which the user is interacting. In some implementations involving a cursor or other location marker, the cursor acts as the “focus selector,” such that when input (e.g., a press input) is detected on a touch-sensitive surface (e.g., touchpad 355 of FIG. 3 or touch-sensitive surface 451 of FIG. 4B) while the cursor is positioned over a particular user interface element (e.g., a button, window, slider, or other user interface element), the particular user interface element is adjusted according to the detected input. In some implementations involving a touchscreen display (e.g., touch-sensitive display system 112 of FIG. 1A or touchscreen 112 of FIG. 4A) that allows direct interaction with user interface elements on the touchscreen display, a detected contact on the touchscreen acts as the “focus selector,” such that when input (e.g., a press input by contact) is detected at the location of a particular user interface element (e.g., a button, window, slider, or other user interface element) on the touchscreen display, the particular user interface element is adjusted according to the detected input. In some implementations, focus is moved from one region of the user interface to another region of the user interface without a corresponding cursor movement or contact movement on the touchscreen display (e.g., by using the tab key or arrow keys to move focus from one button to another), and in these implementations, the focus selector moves to follow the movement of focus between various regions of the user interface. Regardless of the specific form the focus selector takes, the focus selector is generally a user interface element (or contact on a touchscreen display) that is controlled by the user to communicate the user's intended interaction with the user interface (e.g., by indicating to the device the element of the user interface through which the user intends to interact).For example, the location of a focus selector (e.g., a cursor, touch, or selection box) over an individual button while a press input is detected on a touch-sensitive surface (e.g., a touchpad or touchscreen) indicates that the user intends to activate that individual button (and not other user interface elements shown on the device's display).
[0183] As used herein and in the claims, the term "characteristic intensity" of a contact refers to a characteristic of that contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on a plurality of intensity samples. The characteristic intensity is optionally based on a predetermined number of intensity samples, i.e., a set of intensity samples collected during a predetermined time (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10 seconds) associated with a predetermined event (e.g., after detecting the contact, before detecting lift-off of the contact, before or after detecting the start of contact movement, before detecting the end of the contact, before or after detecting an increase in the intensity of the contact, and / or before or after detecting a decrease in the intensity of the contact). The characteristic intensity of the contact is optionally based on one or more of the maximum intensity of the contact, the mean intensity of the contact, the average intensity of the contact, the top 10 percentile intensity of the contact, half the maximum intensity of the contact, 90 percent of the maximum intensity of the contact, etc. In some embodiments, the duration of the contact is used in determining the characteristic intensity (e.g., when the characteristic intensity is an average of the intensity of the contact over time). In some embodiments, the characteristic intensity is compared to a set of one or more intensity thresholds to determine whether an action is performed by the user. For example, the set of one or more intensity thresholds optionally includes a first intensity threshold and a second intensity threshold. In this example, a contact having a characteristic intensity that does not exceed the first threshold results in a first action, a contact having a characteristic intensity above the first intensity threshold but not above the second intensity threshold results in a second action, and a contact having a characteristic intensity above the second threshold results in a third action. In some embodiments, the comparison between the characteristic intensity and the one or more thresholds is not used to determine whether to perform the first action or the second action, but rather to determine whether to perform one or more actions (e.g., whether to perform an individual action or to forgo performing an individual action).
[0184] 5C illustrates exemplary devices connected via one or more communication channels to engage in a transaction according to some embodiments. One or more exemplary electronic devices (e.g., devices 100, 300, and 500) are optionally configured to detect input (e.g., specific user input, NFC field) and optionally transmit payment information (e.g., using NFC). One or more electronic devices optionally include NFC hardware and are configured to be NFC-enabled.
[0185] An electronic device (e.g., devices 100, 300, and 500) is optionally configured to store payment account information associated with each of one or more payment accounts. The payment account information includes, for example, one or more of a person's or company's name, a billing address, a login, a password, an account number, an expiration date, a security code, a telephone number, a bank (e.g., an issuing bank) associated with the payment account, and a card network identifier. In some embodiments, the payment account information includes an image, such as a photograph of a payment card (e.g., taken by and / or received at the device). In some embodiments, the electronic device receives user input including at least some payment account information (e.g., receives a credit, debit, account, or gift card number and expiration date entered by a user). In some embodiments, the electronic device detects at least some payment account information from an image (e.g., a payment card captured by a camera sensor of the device). In some embodiments, the electronic device receives at least some payment account information from another device (e.g., another user device or a server). In some embodiments, the electronic device receives payment account information from a server associated with another service (e.g., an app for renting or selling audio and / or video files) to which the user or user device or account for the identified payment account data has previously made a purchase.
[0186] In some embodiments, a payment account is added to an electronic device (e.g., devices 100, 300, and 500), whereby the payment account information is securely stored on the electronic device. In some embodiments, after a user initiates such a process, the electronic device transmits information for the payment account to a transaction coordination server, which then communicates with a server operated by the payment network for the account (e.g., a payment server) to ensure the validity of the information. The electronic device is optionally configured to receive a script from the server that enables the electronic device to program the payment information for the account onto the secure element.
[0187] In some embodiments, communication between electronic devices 100, 300, and 500 facilitates a transaction (e.g., a general or specific transaction). For example, a first electronic device (e.g., 100) can act as a provisioning or management device and send notifications of new or updated payment account data (e.g., information about new accounts, updated information about existing accounts, and / or alerts for existing accounts) to a second electronic device (e.g., 500). In another example, a first electronic device (e.g., 100) can send data to a second electronic device reflecting information about a payment transaction facilitated at the first electronic device. The information optionally includes one or more of the payment amount, the account used, the time of purchase, and whether the default account has changed. The second device (e.g., 500) optionally uses such information to update the default payment account (e.g., based on a learning algorithm or explicit user input).
[0188] The electronic devices (e.g., 100, 300, 500) are configured to communicate with each other over any of a variety of networks. For example, the devices communicate using a Bluetooth connection 558 (e.g., including a conventional Bluetooth connection or a Bluetooth low energy connection) or a WiFi network 556. Communications between user devices are optionally coordinated to reduce the likelihood of inappropriate sharing of information between devices. For example, communications involving payment information require the communicating devices to be paired (e.g., associated with each other through explicit user interaction) or associated with the same user account.
[0189] In some embodiments, the electronic device (e.g., 100, 300, 500) is used to communicate with a point-of-sale (POS) payment terminal 550, which is optionally NFC-enabled. This communication optionally occurs using various communication channels and / or technologies. In some embodiments, the electronic device (e.g., 100, 300, 500) communicates with the payment terminal 550 using an NFC channel 560. In some embodiments, the payment terminal 550 communicates with the electronic device (e.g., 100, 300, 500) using a peer-to-peer NFC mode. The electronic device (e.g., 100, 300, 500) is optionally configured to transmit a signal to the payment terminal 550 that includes payment information for a payment account (e.g., a default account or an account selected for a particular transaction).
[0190] In some embodiments, proceeding with the transaction includes transmitting a signal including payment information for an account, such as a payment account. In some embodiments, proceeding with the transaction includes reconfiguring the electronic device (e.g., 100, 300, 500) to respond as a contactless payment card, such as an NFC-enabled contactless payment card, and then transmitting the account credentials via NFC to the payment terminal 550, etc. In some embodiments, after transmitting the account credentials via NFC, the electronic device reconfigures itself to not respond as a contactless payment card (e.g., requiring authorization before reconfiguring to respond as a contactless payment card via NFC again).
[0191] In some embodiments, the generation and / or transmission of the signal is controlled by a secure element within the electronic device (e.g., 100, 300, 500). The secure element optionally requires a specific user input before releasing the payment information. For example, the secure element optionally requires detecting that the electronic device is being worn, a button press, a passcode entry, a touch, one or more option selections (e.g., received during interaction with an application), a fingerprint signature, a voice or audio command, and / or a gesture or movement (e.g., rotation or acceleration). In some embodiments, if a communication channel (e.g., an NFC communication channel) is established with another device (e.g., payment terminal 550) within a defined period of time from detecting the input, the secure element releases the payment information to be sent to the other device (e.g., payment terminal 550). In some embodiments, the secure element is a hardware component that controls the release of the secure information. In some embodiments, the secure element is a software component that controls the release of the secure information.
[0192] In some embodiments, the protocols involved in engaging in a transaction depend, for example, on the device type. For example, the conditions for generating and / or transmitting payment information may be different for a wearable device (e.g., device 500) than for a phone (e.g., device 100). For example, the conditions for generating and / or transmitting on a wearable device may include detecting a button press (e.g., after security verification), while the conditions on a phone may not require a button press but instead require detection of a specific interaction with an application. In some embodiments, the conditions for transmitting and / or publishing payment information include receiving a specific input on each of multiple devices. For example, publishing payment information optionally requires detection of a fingerprint and / or passcode on a device (e.g., device 100) and detection of a mechanical input (e.g., a button press) on another device (e.g., device 500).
[0193] The payment terminal 550 optionally uses the payment information to generate a signal that it sends to a payment server 554 to determine whether the payment is authorized. The payment server 554 optionally includes any device or system configured to receive payment information associated with a payment account and determine whether the proposed purchase is authorized. In some embodiments, the payment server 554 includes an issuing bank's server. The payment terminal 550 communicates with the payment server 554 directly or indirectly via one or more other devices or systems (e.g., an acquiring bank's server and / or a card network's server).
[0194] The payment server 554 optionally uses at least a portion of the payment information to identify a user account in a database of user accounts (e.g., 552). For example, each user account includes payment information. The account is optionally located by locating an account with specific payment information that matches the payment information from the POS communication. In some embodiments, the payment is denied when the provided payment information is inconsistent (e.g., the expiration date does not correspond to a credit, debit, or gift card number) or when there is no account with payment information that matches the payment information from the POS communication.
[0195] In some embodiments, the data for the user account further identifies one or more limits (e.g., credit limit), current or previous balance, previous transaction date, location, and / or amount, account status (e.g., active or frozen), and / or authorization instructions. In some embodiments, the payment server (e.g., 554) uses such data to determine whether to authorize a payment. For example, the payment server denies a payment when the purchase amount added to the current balance would exceed the account limit, when the account is frozen, when the previous transaction amount exceeds a threshold, or when the number or frequency of previous transactions exceeds a threshold.
[0196] In some embodiments, the payment server 554 responds to the POS payment terminal 550 with an indication as to whether the proposed purchase was authorized or denied. In some embodiments, the POS payment terminal 550 sends a signal to the electronic device (e.g., 100, 300, 500) to identify the outcome. For example, the POS payment terminal 550 sends a receipt to the electronic device (e.g., 100, 300, 500) when the purchase is authorized (e.g., via a transaction coordination server that manages the transaction app on the user device). In some cases, the POS payment terminal 550 presents an output (e.g., a visual or audio output) indicating the outcome. Payment can be sent to the merchant as part of the authorization process or can be sent at a later time.
[0197] In some embodiments, the electronic device (e.g., 100, 300, 500) participates in a transaction that is completed without the intervention of the POS payment terminal 550. For example, upon detecting that machine input has been received, a secure element within the electronic device (e.g., 100, 300, 500) exposes payment information and allows an application on the electronic device to access the information (e.g., transmit the information to a server associated with the application).
[0198] Attention is now directed to embodiments of user interfaces (“UIs”) and related processes implemented on an electronic device such as portable multifunction device 100, device 300, or device 500.
[0199] 6A-6D show exemplary user interfaces for managing storage account numbers, according to some embodiments. The user interfaces in these figures are used to illustrate processes described below, including the process of FIG. 8. In some embodiments, device 600 includes one or more functions of devices 100, 300, and / or 500.
[0200] 6A , electronic device 600 displays on display 602 (e.g., touchscreen 702) a user interface 610 of a transfer application (e.g., an electronic wallet application). In some embodiments, user interface 610 includes representations 612 (or portions thereof) corresponding to different accounts (e.g., transfer accounts) provisioned on electronic device 600. As shown, representation 612 includes, for example, representation 612a corresponding to a computer storage management account and representation 612b corresponding to a personal storage account. In some embodiments, representation 612a corresponds to a computer storage management account issued (or branded) by a first party manufacturer.
[0201] While displaying user interface 610, device 600 detects a selection of representation 612a corresponding to a computer storage management account. In some embodiments, the selection of representation 612a is a tap gesture 605a on the representation 612a of the computer storage management account. As shown in FIG. 7B , in response to detecting tap gesture 605a, device 600 displays storage account interface 620.
[0202] In some embodiments, storage account interface 620 includes storage transfer history 622 that indicates multiple recent account activities corresponding to previously requested transfers (e.g., transfers of computer storage resources) associated with the computer storage management account. As one example, transfer history 622 includes first transfer 622a corresponding to a request to transfer a specified amount (e.g., 50 MB) to the computer storage management account. As another example, transfer history 622 includes second transfer 622b corresponding to a request to transfer a specified amount (e.g., 25 MB) from the computer storage management account. As shown, first transfer 622a and second transfer 622b of transfer history 622 include respective dates indicating, for example, the date the transfer request was made (or when the respective operation was completed).
[0203] In some embodiments, storage account interface 620 further includes a notification 624 indicating that virtual account functionality may be enabled for the computer storage management account (e.g., based on electronic device 600 determining that the computer storage management account is compatible with the virtual account functionality and / or that the virtual account functionality has not been enabled for the computer storage management account). In some embodiments, the virtual account functionality allows a virtual account number to be provided (e.g., assigned) to the computer storage management account such that transfers to the computer storage management account may be made using the virtual account number. In some embodiments, the virtual account functionality allows different account credentials (e.g., account number, account security code) associated with the computer storage management account to be used for successive transfers (e.g., each transfer of the multiple transfers uses different account credentials). In some embodiments, notification 624 includes a settings affordance 624a that, when selected, initiates a process for enabling the virtual account functionality for the computer storage management account. For example, while displaying storage account interface 620, device 600 detects selection of settings affordance 624a. In some embodiments, the selection is a tap gesture 605b on the settings affordance 624a. As shown in Figure 6C, in response to detecting the tap gesture 605b, the device 700 displays a settings interface 630. In some embodiments, the settings interface 630 is overlaid on the storage account interface 620.
[0204] The configuration interface 630 includes a confirmation affordance 632, the selection of which initiates (and / or confirms the user's intent to initiate) the process of enabling the virtual account functionality for the computer storage management account. The device 600 then executes the process to enable the virtual account functionality for the computer storage management account.
[0205] 6A , in some embodiments, a user may select a representation of a computer storage management account that is incompatible with the virtual account functionality. For example, while displaying user interface 610, device 600 detects a selection of representation 612b. In some embodiments, the selection of representation 612b is a tap gesture 607a on the transfer account representation 612b. As shown in FIG. 6D , in response to detecting tap gesture 605a, device 600 displays storage account interface 610A. Because the transfer account corresponding to storage account interface 610A is incompatible with the virtual account functionality, device 600 displays storage account interface 610A without a notification (e.g., notification 624) indicating that virtual account functionality may be enabled for the computer storage management account corresponding to storage account interface 610A.
[0206] 7A-7M show exemplary user interfaces for managing virtual account numbers, according to some embodiments. The user interfaces in these figures are used to illustrate processes described below, including the process of FIG. 8. In some embodiments, device 700 includes one or more functions of devices 100, 300, and / or 500.
[0207] In some embodiments, the virtual account number described herein is associated with a user account (or multiple user accounts). In some embodiments, the user account is a transfer account. In some embodiments, the transfer account is a first-party transfer account (e.g., a transfer account issued or branded by the manufacturer of the electronic device) that optionally provides rewards (e.g., cashback rewards and / or bonus point rewards) based on the amount of transfers (e.g., payment transactions and / or points transfers) made using the transfer account (e.g., cashback rewards based on a certain percentage of the price of each transaction) and / or made using a different account. In some embodiments, the transfer account is a points account (e.g., for meal points, printer credits, and / or membership points) that provides rewards (e.g., points rewards) based on the amount of points used using the transfer account.
[0208] 7A-7F show examples for providing a virtual account number for a user account.
[0209] 7A illustrates electronic device 700. In FIG. 7A, electronic device 700 is a portable multifunction device and includes one or more of the components described above with respect to one or more of devices 100, 300, and 500.
[0210] 7A , electronic device 700 displays on display 702 (e.g., touchscreen 702) a user interface 710 of a transfer application (e.g., an electronic wallet application). In some embodiments, user interface 710 includes representations 712 corresponding to different transfer accounts (e.g., payment accounts, such as third-party credit card accounts, debit card accounts, and / or stored value accounts, points accounts, and / or rewards accounts) provisioned on electronic device 700. As shown, representations 712 include, for example, representation 712a corresponding to a transfer account and representation 712b corresponding to a medical account (e.g., an HSA account). In some embodiments, representation 712a corresponds to a first party transfer account. In some embodiments, user interface 710 includes representations 714 (e.g., representations 714a-714c) corresponding to various other accounts (e.g., transfer accounts, points cards, and / or rewards cards), ID cards (e.g., student IDs and / or government-issued IDs), and / or tickets (e.g., event tickets and / or boarding passes) provisioned or linked on electronic device 700.
[0211] While displaying user interface 710, device 700 detects a selection of representation 712a corresponding to a transfer account. In some embodiments, the selection of representation 712a is a tap gesture 705a on the transfer account representation 712a. As shown in FIG. 7B , in response to detecting tap gesture 705a, device 700 displays a transfer account interface 720.
[0212] In some embodiments, transfer account interface 720 includes a transfer history 722 that shows multiple recent account activity corresponding to previously requested transfers (e.g., transfers of funds) associated with the transfer account. As one example, transfer history 722 includes a first transfer 722a corresponding to a request to transfer a specified amount (e.g., $5.01) from the transfer account. As another example, transfer history 722 includes a second transfer 722b corresponding to a request to transfer a specified amount (e.g., $12.96) from the transfer account. As shown, first transfer 722a and second transfer 722b of transfer history 722 include respective dates, indicating, for example, the date the transfer request was made (or when the respective action was completed).
[0213] In some embodiments, the transfer account interface 720 further includes a notification 724 indicating that virtual account functionality may be enabled for the transfer account (e.g., based on the electronic device 700 determining that the transfer account is compatible with the virtual account functionality and / or that the virtual account functionality has not been enabled for the transfer account). In some embodiments, the virtual account functionality allows a virtual account number to be provided (e.g., assigned) to the transfer account such that transactions for the transfer account can be conducted using the virtual account number. In some embodiments, the virtual account functionality allows different account credentials (e.g., account number, security code, CCV, and / or CVV) associated with the transfer account to be used for successive transfers (e.g., each transfer of the multiple transfers uses different account credentials). In some embodiments, the notification 724 includes a settings affordance 724a that, when selected, initiates a process for enabling virtual account functionality for the transfer account. For example, while displaying the transfer account interface 720, the device 700 detects a selection of the settings affordance 724a. In some embodiments, the selection is a tap gesture 705b on the settings affordance 724a. 7C, in response to detecting tap gesture 705b, device 700 displays settings interface 730. In some embodiments, settings interface 730 overlays transfer account interface 720.
[0214] Settings interface 730 includes a confirmation affordance 732, the selection of which confirms the user's intent to begin the process of enabling the virtual account functionality for the transfer account. While displaying settings interface 730, device 700 detects a selection of confirmation affordance 732. In some embodiments, the selection is a tap gesture 705c on confirmation affordance 732. As shown in FIG. 7D , in response to detecting tap gesture 705c, device 700 displays authentication interface 740. In some embodiments, in response to detecting tap gesture 705c, device 700 displays transfer account interface 720 (e.g., replacing the display of settings interface 730 with transfer account interface 720) and overlays authentication interface 740 on transfer account interface 720.
[0215] Authentication interface 740 includes instructions 742 instructing the user to provide input (e.g., pressing a button on device 700 and / or pressing a button twice on device 700) to authorize enabling the virtual account functionality. While displaying authentication interface 740, device 700 detects input 705d (e.g., pressing button 703 twice), and in response, device 700 authenticates the user of device 700. As shown in FIG. 7E, for example, device 700 modifies the authentication user interface to include glyph 746 to indicate that device 700 is performing biometric authentication (e.g., facial authentication, fingerprint authentication, and / or iris authentication) of the user.
[0216] 7F, once the user of device 700 is authenticated, device 700 displays virtual account number interface 750. The virtual number interface includes status 752 indicating that the virtual account feature has been enabled for the transfer account. Optionally, status 752 includes animation 752a that serves as a dynamic indicator that the virtual account feature has been enabled.
[0217] 7G , once the virtual account functionality is enabled for the transfer account, the device 700 displays a completion interface 760 (e.g., replaces the display of the virtual account number interface 750 with the completion interface 760). In some embodiments, the completion interface 760 includes a status 764 indicating that the virtual account functionality has been enabled for the transfer account. Optionally, the status 764 includes an indicator 764a (e.g., a check mark) to provide a non-textual indication that the functionality has been enabled.
[0218] In some embodiments, completion interface 760 includes an affordance 766 that, when selected, allows the user to enable virtual account functionality for one or more other transfer accounts. For example, while displaying completion interface 760, device 700 detects selection of affordance 766. In some embodiments, the selection is a tap gesture 705g on affordance 766. As shown in FIG. 7H , in response to detecting selection of affordance 766, device 700 displays account selection interface 770.
[0219] Account selection interface 770 includes candidate accounts 772, each of which corresponds to a transfer account provisioned on device 700. In some embodiments, candidate accounts 772 include only transfer accounts that are compatible with (e.g., eligible for and / or capable of being configured with) the virtual account functionality and / or that are not currently enabled for the virtual account functionality. While account selection interface 770 is displayed, the user optionally selects any number of candidate accounts 772 (e.g., candidate account 772a and / or candidate account 772b). Device 700 then detects selection of continuation affordance 774 and, in response, initiates a process to enable the virtual account functionality for each selected candidate account. In some embodiments, the virtual account functionality is enabled sequentially for each selected candidate account. In some embodiments, the virtual account functionality is enabled simultaneously for each selected candidate account.
[0220] 7G , completion interface 760 includes an exit affordance 768 that, when selected, causes device 700 to display transfer account interface 720. For example, while displaying completion interface 760, device 700 detects a selection of exit affordance 768. In some embodiments, the selection is a tap gesture 707g on exit affordance 768. As shown in FIG. 7I , in response to detecting a selection of exit affordance 768, device 700 displays transfer account interface 720.
[0221] Because the virtual account functionality has been enabled for the transfer account corresponding to the transfer account interface 720, the device 700 displays a notification 726 (e.g., rather than notification 724) in the transfer account interface 720 indicating that the virtual account functionality has been enabled for the transfer account (e.g., a virtual account number has been provided).
[0222] In some embodiments, a user may desire to access and / or view a virtual account number corresponding to the virtual account feature for a transfer account. In some embodiments, the virtual account number is viewed using transfer account interface 720. By way of example, while displaying transfer account interface 720, device 700 detects a selection of menu affordance 780. In some embodiments, the selection is a tap gesture 705i on menu affordance 780. In response to detecting a selection of menu affordance 780, device 700 displays menu 784 including information affordance 784a.
[0223] While displaying menu 784, device 700 detects a selection of information affordance 784a. In some embodiments, the selection is a tap gesture 707i on information affordance 784a. As shown in FIG. 7J, in response to detecting the selection of information affordance 784a, device 700 displays an authentication glyph 788. In some embodiments, authentication glyph 788 is overlaid on transfer account interface 720.
[0224] Generally, the authentication glyph (and optionally, one or more other glyphs) is displayed to indicate that device 600 is performing biometric authentication (e.g., facial authentication, fingerprint authentication, and / or iris authentication) of the user. As shown in FIG. 7K, once the user of device 700 is authenticated, device 700 displays information interface 790. Information interface 790 includes a virtual account number 792 and an expiration date 794, which, in some embodiments, is the expiration date of virtual account number 792. Information interface 790 further includes a security code 796. In some embodiments, security code 796 is a rotating security code (e.g., as indicated by indicator 796A) for virtual account number 792 that changes periodically (e.g., after each transaction using the transfer account and / or once a day).
[0225] Information interface 790 further includes account information affordance 798. In response to selection of account information affordance 798, device 700 provides at least a portion of the physical account number of the transfer account and / or at least a portion of the virtual account number of the transfer account. For example, while displaying information interface 790, device 700 detects selection of information affordance 798. In some embodiments, the selection is a tap gesture 705k on information affordance 798. As shown in FIG. 7L , in response to detecting selection of information affordance 798, device 700 displays number interface 700A including physical account number 702A corresponding to the transfer account and virtual account number 704A corresponding to the transfer account. In some embodiments, virtual account number 792 and virtual account number 704A are the same virtual account number.
[0226] 7A , in some embodiments, a user may select a representation of a transfer account that is incompatible with the virtual account functionality. For example, while displaying user interface 710, device 700 detects a selection of representation 712b. In some embodiments, the selection of representation 712b is a tap gesture 707a on the transfer account representation 712b. As shown in FIG. 7M , in response to detecting tap gesture 705a, device 700 displays transfer account interface 710A. Because the transfer account corresponding to transfer account interface 710A is incompatible with the virtual account functionality, device 700 displays transfer account interface 710A without a notification (e.g., notification 724) indicating that the virtual account functionality may be enabled for the transfer account corresponding to transfer account interface 710A.
[0227] 8 is a flow diagram illustrating a method for managing account numbers, according to some embodiments. Method 800 is performed in a computer system (e.g., 100, 300, 500, and / or 700) (e.g., a smartwatch, a smartphone, a head-mounted device (e.g., a head-mounted augmented reality and / or augmented reality device), a self-propelled device and / or system, and / or a personal computer) in communication with a display generation component (e.g., an integrated display, a head-mounted display system, and / or a display controller) and one or more input devices (e.g., a touch-sensitive surface (e.g., a touch screen), a mouse, and / or a keyboard). Some operations of method 800 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.
[0228] As described below, method 800 provides an intuitive way to manage account numbers. This method reduces the cognitive burden on users to manage account numbers, thereby creating a more efficient human-machine interface. For battery-operated computing devices, allowing users to manage account numbers more quickly and efficiently conserves power and increases the time between battery charges.
[0229] In some embodiments, a computer system (e.g., 600 and / or 700), via a display generation component (e.g., 602 and / or 702), simultaneously displays (802) a portion (e.g., all or less than all) of a first visual representation (e.g., 612a and / or 712a) corresponding to a first asset account (e.g., a memory allocation account, a printing allocation account, a transit system account, a payment account, or a store loyalty account) provisioned on the computer system's electronic wallet and a portion (e.g., all or less than all) of a second visual representation (e.g., 612b and / or 712b) different from the first visual representation corresponding to a second asset account (e.g., a memory allocation account, a printing allocation account, a transit system account, a payment account, or a store loyalty account) provisioned on the computer system's electronic wallet and different from the first asset account. In some embodiments, the portion of the first visual representation and the portion of the second visual representation are displayed as part of an electronic wallet application on the computer system. In some embodiments, the first asset account and the second asset account belong to a user of a computer system and / or are provisioned on the computer system. In some embodiments, details of one or more of the provisioned asset accounts are stored in a secure element of the computer system as part of the provisioning process. In some embodiments, the secure element is a hardware component (e.g., of the computer system) (e.g., a secure microcontroller chip) configured to securely store data or algorithms such that the securely stored data cannot be accessed by the computer system without proper authentication information from the user of the computer system.By maintaining the securely stored data in the secure element separate from other storage on the computer system, access to the securely stored data is prevented even if other storage locations on the computer system are compromised (e.g., by malicious code or other attempts to compromise information stored on the computer system). In some embodiments, the secure element provides (or reveals) account information (e.g., account number and / or transaction-specific dynamic security code). In some examples, the secure element provides (or reveals) the account information in response to the computer system receiving authorization, such as user authentication (e.g., biometric authentication (e.g., fingerprint authentication, facial authentication, iris authentication, passcode authentication)). In some embodiments, the revealed account information is transferred or transmitted to effect a transfer (e.g., transfer of assets). In some embodiments, a first selectable user interface object for initiating a process to enable virtual account functionality for a first asset account is not displayed simultaneously with portions of the first and second visual representations of the first and second asset accounts.
[0230] In some embodiments, while simultaneously displaying a portion of the first visual representation and a portion of the second visual representation, the computer system receives (804) via one or more input devices a selection (e.g., 605a and / or 705a) of the first visual representation (e.g., via a tap input and / or a press and hold) corresponding to the first asset account.
[0231] In some embodiments, in response to receiving a selection of the first visual representation corresponding to the first asset account, in accordance with a determination that the set of virtual account criteria is met and a first virtual account criterion of the set of virtual account criteria is met when virtual account functionality is not enabled for the first asset account, the computer system, via the display generation component, displays (806) a first selectable user interface object (e.g., 624a and / or 724a) for initiating a process to enable virtual account functionality for the first asset account (e.g., without initiating a process to enable virtual account number functionality for a second asset account (e.g., the first user interface object is for enabling the functionality for only the selected asset account), or by initiating a process to enable virtual account number functionality for the second asset account (e.g., the first user interface object is for enabling the functionality for multiple (or all) asset accounts provisioned in the electronic wallet). In some embodiments, if the virtual account functionality is not enabled for the first asset account, the computer system automatically uses (e.g., transmits via a short-range communication radio such as NFC, automatically populates fields, and / or transmits via a wired or wireless communication channel, such as during a transaction conducted over the Internet) the same credential information (e.g., the same account number, the same expiration date, the same account holder name, and / or the same security code) for consecutive (e.g., two consecutive, three consecutive, and / or all) transactions performed using the first asset account.In some embodiments, once the virtual account functionality is enabled for the first asset account, the computer system automatically uses (e.g., transmits via a near field communication radio such as NFC to automatically populate fields, and / or transmits via a wired or wireless communication channel, such as during a transaction conducted over the Internet) different credential information (e.g., different account numbers, different expiration dates, different account holder names (e.g., John Doe vs. John H. Doe), and / or different security codes corresponding to the same account) for consecutive (e.g., two consecutive, three consecutive, and / or all) transactions performed using the first asset account. Automatically displaying a first selectable user interface object for initiating the process of enabling the virtual account functionality for the first asset account based on the set of virtual account criteria provides the user with visual feedback regarding whether the set of virtual account criteria has been met, thereby providing the user with improved feedback regarding the status of the computer system.
[0232] In some embodiments, the set of virtual account criteria includes a second virtual account criteria that is satisfied if the first asset account is compatible for use with the virtual account functionality. In some embodiments, some asset accounts provisioned on the computer system's electronic wallet are compatible for use with the virtual account functionality and some accounts provisioned on the computer system's electronic wallet are not compatible for use with the virtual account functionality.
[0233] In some embodiments, in response to receiving a selection of the first visual representation corresponding to the first asset account, following a determination that the set of virtual account criteria is not met (e.g., virtual account functionality is enabled for the first asset account and / or other criteria in the set of virtual account criteria are not met), the computer system ceases displaying the first selectable user interface object (e.g., ceases displaying 624a and / or 724a) (808) to begin a process of enabling the virtual account functionality for the first asset account.
[0234] In some embodiments, the computer system receives (810) a selection of the first selectable user interface object (e.g., 605b and / or 705b) via one or more input devices while displaying, via the display generation component, the first selectable user interface object that is displayed in response to receiving the selection of the first visual representation.
[0235] In some embodiments, in response to receiving a selection of the first selectable user interface object, the computer system initiates (812) a process to enable the virtual account functionality for the first asset account (e.g., without initiating a process to enable the virtual account number functionality for a second asset account (e.g., the first user interface object is for enabling the functionality for only the selected asset account), or by initiating a process to enable the virtual account number functionality for the second asset account (e.g., the first user interface object is for enabling the functionality for multiple (or all) asset accounts provisioned in the electronic wallet). Automatically displaying the first selectable user interface object for initiating a process to enable the virtual account functionality for the first asset account based on the set of virtual account criteria provides the user with visual feedback regarding whether the set of virtual account criteria was satisfied, thereby providing the user with improved feedback regarding the status of the computer system.
[0236] In some embodiments, the computer system, in response to receiving a selection of the first visual representation corresponding to the first asset account, displays, via the display generation component, an indication (e.g., 726) that the virtual account functionality has been enabled for the first asset account in accordance with a determination that the virtual account functionality has been enabled for the first asset account. In some embodiments, in response to receiving a selection of the first visual representation corresponding to the first asset account and in accordance with a determination that the virtual account functionality has been enabled for the first asset account, the computer system displays a selectable user interface object (e.g., "Learn More" at 726) that, when activated, provides additional information about the virtual account functionality (e.g., what the functionality is, how the functionality works, and / or how to enable and / or disable the functionality). Displaying an indication that the virtual account functionality has been enabled for the first asset account provides the user with visual feedback that the functionality has been enabled, thereby providing the user with improved visual feedback about the state of the computer system.
[0237] In some embodiments, the computer system receives (e.g., via one or more wireless communication radios, via NFC, via a communications network, and / or via a touch-sensitive surface of the computer system) a first request (e.g., an NFC request and / or a user request) to provide credentials for a first asset account (e.g., to populate forms and / or fields with credential information) for a first asset transfer (e.g., a transfer of memory allocation, a transfer of print allocation, a transfer of transit credits, a transfer of funds, or a transfer of loyalty account information) while virtual account functionality is enabled for the first asset account. In some embodiments, in response to receiving the first request to provide credentials for the first asset account for the first asset transfer, the computer system provides the first credentials (e.g., to populate forms and / or fields with credential information) using the first asset account without providing a second credential different from the first credential. In some embodiments, after providing the first credentials, the computer system receives a second request to provide credentials for the first asset account for a second asset transfer that is different from the first asset transfer. In some embodiments, in response to receiving the second request to provide credentials for the first asset account for the second asset transfer, the computer system provides the second credentials using the first asset account (e.g., populates forms and / or fields with the credential information) without providing the first credentials. In some embodiments, the computer system provides an account number, expiration date, account holder name, and / or security code for use in the asset transfer. In some embodiments, the account number remains the same in successive transactions, and the security code changes in successive transactions. In some embodiments, the account number changes in successive transactions, and / or the security code changes in successive transactions.Providing different credentials for the same asset account when the virtual account feature is enabled provides increased security by reducing the ability of other parties to access and use valid credentials.
[0238] In some embodiments, the computer system receives, during the process of enabling the virtual account functionality for the first asset account, one or more user inputs for enabling the virtual account functionality for the first asset account via one or more input devices (e.g., authentication information captured during biometric authentication during displays of 605c, 705c, 705d, and / or 740). In some embodiments, the computer system enables the virtual account functionality for the first asset account in response to receiving the one or more user inputs for enabling the virtual account functionality for the first asset account. Enabling the virtual account functionality based on user inputs provides improved security by reducing the ability of other parties to access and use valid credentials.
[0239] In some embodiments, the computer system requires authentication during the process of enabling the virtual account functionality for the first asset account. In some embodiments, the computer system receives authentication information (e.g., biometric information captured during display 740) via one or more input devices (e.g., a passcode, facial authentication information, iris authentication information, and / or fingerprint authentication information, with or without a physical button press after providing the information). In some embodiments, the one or more user inputs for enabling the virtual account functionality for the first asset account include the authentication information. In some embodiments, the process of enabling the virtual account functionality for the first asset account proceeds only if the authentication information matches a registered user of the computer system. Requiring user authentication via authentication information to enable the virtual account functionality increases the security of the computer system by only enabling the functionality with permission from an authenticated user.
[0240] In some embodiments, in response to receiving one or more user inputs to enable the virtual account functionality for the first asset account, the computer system provides information to an autofill application (e.g., the autofill application of FIG. 13A ) (e.g., an autofill application (e.g., a web browser application (of the computer system or an external device) that autofills a form and / or another application (of the computer system or an external device)) to enable the autofill application to use a first autofill option to autofill using the virtual account functionality for the first asset account. In some embodiments, once the autofill application is enabled to use the virtual account functionality for the first asset account, the autofill application can autofill credential information for the first asset account that differs for each successive autofill (e.g., a first autofill request results in first credentials based on which the first asset account is autofilled, and a second autofill request results in second credentials that are different from the first credentials). Enabling the autofill application to automatically autofill credential information for the first asset account based on the enabled virtual account functionality reduces the need for the user to provide additional input to enable the autofill application, thereby reducing the number of inputs required.
[0241] In some embodiments, in response to receiving one or more user inputs to enable the virtual account functionality for the first asset account, the computer system removes from an autofill application (e.g., a web browser application (of the computer system or an external device) and / or another application (of the computer system or an external device) that autofills forms) a second autofill option for autofilling using the first asset account without the virtual account functionality. In some embodiments, before the virtual account functionality is enabled for the first asset account, the autofill application presents an option for the user to autofill using the first asset account without the virtual account functionality (e.g., the same credential autofill for successive autofill operations (e.g., multiple times or each time)). In some embodiments, once the virtual account functionality for the first asset account is enabled, the autofill application replaces the option for the user to autofill using the first asset account without the virtual account functionality with an option for the user to autofill using the virtual account functionality for the first asset account (e.g., different credential autofill for successive autofill operations). By removing duplicate autofill options from the autofill application, users can more easily access various options without having to scroll through duplicate options, thereby reducing the number of entries required to access a desired option.
[0242] In some embodiments, after enabling the virtual account functionality for the first asset account (e.g., in response to and / or at some point thereafter), the computer system displays, via a display generating component, an option (e.g., 766) for initiating a process for enabling the virtual account functionality for one or more asset accounts different from the first asset account. In some embodiments, the computer system receives, via one or more input devices, a selection of an option (e.g., 705g) for initiating a process for enabling the virtual account functionality for one or more asset accounts different from the first asset account. In some embodiments, the computer system initiates a process for enabling the virtual account functionality for one or more asset accounts different from the first asset account in response to receiving a selection of the option for initiating a process for enabling the virtual account functionality for one or more asset accounts different from the first asset account. In some embodiments, the computer system progresses through a process for sequentially enabling the virtual account functionality for several asset accounts. In some embodiments, the option for enabling the virtual account functionality for one or more asset accounts different from the first asset account is displayed simultaneously with an indication that the virtual account functionality has been enabled for the first asset account. Displaying an option for the user to enable virtual account functionality for additional asset accounts allows the user to begin the process more quickly without having to provide more user input and provides visual feedback to the user that other accounts are available for enabling virtual account functionality, thereby providing improved visual feedback.
[0243] In some embodiments, after enabling the virtual account functionality for the first asset account (e.g., in response to and / or at some point thereafter), the computer system displays, via the display generation component, an option (e.g., 784a, 798) to display account information for the first asset account (e.g., without initiating a process to enable virtual account functionality for one or more asset accounts different from the first asset account). In some embodiments, the computer system receives, via one or more input devices, a selection of the option (e.g., 705i, 705k) to display account information for the first asset account. In some embodiments, in response to receiving the option to display account information for the first asset account, the computer system displays, via the display generation component, a user interface (e.g., 720) for the first asset account that includes a first visual representation corresponding to the first asset account (e.g., without initiating a process to enable virtual account functionality for one or more asset accounts different from the first asset account) (e.g., the user interface for the first asset account does not include a second visual representation corresponding to the second asset account). In some embodiments, the computer system displays a first visual representation corresponding to the first asset account, simultaneously with one or more transfers performed using the first asset account and an indication that the virtual account functionality has been enabled for the first asset account. Displaying account information for the first asset account provides the user with additional feedback regarding the status of the asset account and the computer system, thereby providing the user with improved visual feedback.
[0244] In some embodiments, the computer system receives one or more sets of user inputs (e.g., authentication interfaces captured during biometric authentication while 705i, 788 are displayed) via one or more input devices while the virtual account functionality is enabled for the first asset account, and displays a virtual account number based on the virtual account functionality enabled for the first asset account. In some embodiments, the set of one or more user inputs includes user authentication (e.g., biometric authentication (e.g., fingerprint authentication, facial authentication, iris authentication, passcode authentication)). Displaying the virtual account number in response to receiving the one or more sets of user inputs provides visual feedback to the user regarding the virtual account number, thereby providing improved visual feedback to the user.
[0245] In some embodiments, in response to receiving a selection of a first visual representation (e.g., 612a and / or 712a) corresponding to a first asset account, the computer system simultaneously displays, via the display generation component, the first visual representation corresponding to the first asset account and information regarding one or more transfers performed using the first asset account (e.g., 622 and / or 722). In some embodiments, in response to receiving a selection of the first visual representation corresponding to the first asset account, the computer system does not display visual representations corresponding to asset accounts different from the first asset account. Displaying information regarding one or more transfers performed using the first asset account provides the user with improved visual feedback regarding the status of the first asset account and how it has been used in the past, which also allows the user to verify that the account is not being misused, thereby providing improved security for the user.
[0246] It should be noted that the process details described above with respect to method 800 (e.g., FIG. 8) are also applicable in a similar manner to the methods described below. For example, method 1400 optionally includes one or more of the features of the various methods described above with reference to method 800. For example, after enabling virtual account functionality for the transfer account as described with respect to method 800, a virtual card number for the transfer account is optionally used to populate one or more fields during the transaction as described with respect to method 1400. For the sake of brevity, these details will not be repeated below.
[0247] 9A-9C show exemplary user interfaces for provisioning a storage account, according to some embodiments. The user interfaces in these figures are used to illustrate processes described below, including the process of FIG. 11. In some embodiments, device 900 includes one or more of the functionality of devices 100, 300, and / or 500.
[0248] 9A , electronic device 900 displays on display 902 (e.g., touchscreen 702) a user interface 910 of a transfer application (e.g., an electronic wallet application). In some embodiments, user interface 910 includes representations 912 (or portions thereof) corresponding to different accounts (e.g., transfer accounts) provisioned on electronic device 600. As shown, representation 912 includes representation 912a corresponding to, for example, a computer storage management account. In some embodiments, representation 912a corresponds to a computer storage management account issued (or branded) by a first party manufacturer.
[0249] In some embodiments, device 900 determines whether one or more computer storage management accounts are available to be provisioned. In some embodiments, the computer storage management accounts available to be provisioned include computer storage management accounts that are enabled for application autofill operations on device 900 (e.g., account information autofill operations) but are not provisioned on device 900 (e.g., not provisioned in an electronic wallet application of device 900 and / or not stored in a secure element of device 900). In some embodiments, the application autofill operations are performed using a web browsing application of device 900, for example, during a transfer performed using the web browsing application.
[0250] 9A , if device 900 determines that a computer storage management account is available for provisioning on device 900, device 900 displays provisioning affordance 916 within user interface 910, indicating that a computer storage management account (or multiple computer storage management accounts) is available for provisioning on device 900. In response to selection of provisioning affordance 916, device 900 displays confirmation interface 930, as shown in FIG. 9B . While displaying confirmation interface 930, device 1000 detects selection of provisioning affordance 932. In some embodiments, the selection is a tap gesture 905c on provisioning affordance 932. In response to selection of provisioning affordance 932, device 900 initiates a process to provision a computer storage management account on device 900 (e.g., on a wallet application of device 900).
[0251] As shown in FIG. 9C, once a computer storage management account is provisioned on device 900, user interface 910 includes a representation (eg, representation 912c) corresponding to the provisioned transfer account.
[0252] 10A-10H show exemplary user interfaces for provisioning an account, according to some embodiments. The user interfaces in these figures are used to illustrate processes described below, including the process of FIG. 11. In some embodiments, device 1000 includes one or more functions of devices 100, 300, and / or 500.
[0253] In some embodiments, the virtual account number described herein is associated with a user account (or multiple user accounts). In some embodiments, the user account is a transfer account. In some embodiments, the transfer account is a first-party transfer account (e.g., a transfer account issued or branded by the manufacturer of the electronic device) that optionally provides rewards (e.g., cashback rewards, bonus point rewards) based on the amount of transfers (e.g., payment transactions and / or points transfers) made using the transfer account (e.g., cashback rewards based on a certain percentage of the price of each transaction) and / or made using a different account. In some embodiments, the transfer account is a points account (e.g., for meal points, printer credits, and / or membership points) that provides rewards (e.g., points rewards) based on the amount of points used using the transfer account.
[0254] 10A-10H, described below, generally illustrate examples of initiating and / or executing a process for provisioning a transfer account on device 1000, and more specifically within an electronic wallet application of device 1000. In some embodiments, electronic device 1000 is a portable multifunction device and includes one or more components described above with respect to one or more of devices 100, 300, and 500.
[0255] 10A , electronic device 1000 displays on display 1002 (e.g., touchscreen 1002) a user interface 1010 of a transfer application (e.g., an electronic wallet application). In some embodiments, user interface 1010 includes representations 1012 corresponding to different transfer accounts (e.g., payment accounts, points accounts, and / or rewards accounts, such as third-party credit card accounts, debit card accounts, and / or stored value accounts) provisioned on the electronic device. As shown, representation 1012 includes, for example, representation 1012a corresponding to a first transfer account and representation 1012b corresponding to a second transfer account. In some embodiments, representation 1012a corresponds to a first party transfer account. In some embodiments, the user interface 1010 includes representations 1014 (e.g., representations 1014a-1014d) corresponding to various other accounts (e.g., transfer accounts, points cards, and / or rewards cards), ID cards (e.g., student IDs and / or government-issued IDs), and / or tickets (e.g., event tickets and / or boarding passes) provisioned or linked on the electronic device 1000.
[0256] In some embodiments, device 1000 determines whether one or more transfer accounts are available for provisioning. In some embodiments, transfer accounts available for provisioning include transfer accounts that are enabled for application autofill operations on device 1000 (e.g., autofill operations of account information and / or payment information) but are not provisioned on device 1000 (e.g., not provisioned in an electronic wallet application of device 1000 and / or not stored in a secure element of device 1000). In some embodiments, application autofill operations are performed using a web browsing application of device 1000, for example, during a transaction performed using the web browsing application.
[0257] 10A , if device 1000 determines that one or more transfer accounts are available for provisioning on device 1000, device 1000 displays provisioning affordance 1016 within user interface 1010 indicating that one or more transfer accounts are available for provisioning on device 1000. In response to selection of provisioning affordance 1016, device 1000 initiates a process for provisioning transfer accounts on device 1000 (e.g., on a wallet application of device 1000), as shown in FIG.
[0258] In some embodiments, device 1000 prompts the user to provision a transfer account on device 1000. By way of example, and referring to FIG. 10B , device 1000 displays prompt 1022 on home interface 1020 indicating that one or more transfer accounts are available for provisioning. In response to selection of prompt 1022, device 1000 initiates a process for provisioning a transfer account. In some embodiments, prompt 1022 is displayed in response to device 1000 performing a transaction that corresponds to a transfer account available for provisioning on device 1000 or a transfer account that is already provisioned on device 1000, for example.
[0259] In Figure 10C, device 1000 displays confirmation interface 1030. Figure 10C is displayed in response to, for example, selection of notification 1016 (Figure 10A) and / or prompt 1022 (Figure 10B). While displaying confirmation interface 1030, device 1000 detects selection of continuation affordance 1032. In some embodiments, the selection is a tap gesture 1005c on continuation affordance 1032.
[0260] 10D , in response to detecting selection of continuation affordance 1032, device 1000 displays account selection interface 1040. Account selection interface 1040 includes candidate accounts 1042, each of which corresponds to a transfer account available for provisioning on device 1000. While account selection interface 1040 is displayed, the user can select any number of candidate accounts 1042 (e.g., candidate account 1042a and / or candidate account 1042b) to be provisioned on device 1000. In the example shown in FIG. 10D , the user has selected candidate account 1042b to be provisioned on device 1000.
[0261] While displaying account selection interface 1040, device 1000 detects selection of continuation affordance 1044. In some embodiments, the selection is a tap gesture 1005d on continuation affordance 1044. As shown in FIG. 10E, in response to detecting selection of continuation affordance 1044, device 1000 displays account interface 1050.
[0262] In FIG. 10E , account interface 1050 includes various information regarding the transfer account (e.g., the transfer account corresponding to selected candidate account 1042b). As an example, the transfer account includes an account identifier 1054, which in some embodiments may be an image of a physical card associated with the transfer account. The account interface further includes credential fields 1052. Credential fields 1052a and 1052b, in some embodiments, are fields for a first credential (e.g., account number) and a second credential (e.g., security code) of the transfer account, respectively. In some embodiments, device 1000 automatically populates (e.g., fills in) credential fields 1052a and 1052b with the first and second credentials, respectively, during display of account interface 1050. In some embodiments, device 1000 automatically populates the credential fields using information from an autofill application. In some embodiments, the device 1000 populates only the credential field 1052a, and the credential field 1052b is populated by the user, for example, to verify the user's access to the account.
[0263] Once the credential field 1052 is populated, the device 1000 detects a selection of the continuation affordance 1056. In some embodiments, the selection is a tap gesture 1005e on the continuation affordance 1056. As shown in FIG. 10F , in response to detecting the selection of the continuation affordance 1056, the device 1000 displays a provisioning interface 1060.
[0264] 10F, provisioning interface 1060 includes a status 1062 indicating that the selected transfer account is being provisioned on device 1000. Optionally, status 1062 includes an animation 1062a that serves as a dynamic indicator that the transfer account is being provisioned.
[0265] 10G, once the transfer account is provisioned, device 1000 displays completion interface 1070 (e.g., replaces the display of provisioning interface 1060 with completion interface 1070). In some embodiments, completion interface 1070 includes status 1074 indicating that the transfer account has been provisioned. Optionally, status 1074 includes indicator 1074a (e.g., a check mark) that provides a non-textual indication that the transfer account has been provisioned.
[0266] 10H, once a transfer account is provisioned, a representation (e.g., representation 1012c) corresponding to the provisioned transfer account is included in user interface 1010. Thus, device 1000 enables a fast and efficient process by which transfer accounts can be provisioned on device 1000 that are available for autofill operations using the autofill application.
[0267] 11 is a flow diagram illustrating a method for provisioning an account using a computer system, according to some embodiments. Method 1100 is performed on a computer system (e.g., 100, 300, 500, and / or 1000) (e.g., a smartwatch, a smartphone, a head-mounted device (e.g., a head-mounted augmented reality and / or augmented reality device), a self-propelled device and / or system, and / or a personal computer) in communication with a display generation component (e.g., an integrated display, a head-mounted display system, and / or a display controller) and one or more input devices (e.g., a touch-sensitive surface (e.g., a touch screen), a mouse, and / or a keyboard). Some operations of method 1100 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.
[0268] As described below, method 1100 provides an intuitive method for provisioning an account. This method reduces the cognitive burden on a user to provision an account, thereby creating a more efficient human-machine interface. For battery-operated computing devices, allowing a user to provision an account more quickly and efficiently conserves power and increases the time between battery charges.
[0269] In some embodiments, the computer system, via a display generation component, displays (1102) a provisioning user interface (e.g., 910 and / or 1010). In some embodiments, the provisioning interface includes an indication (e.g., 916 and / or 1016) that one or more accounts are enabled (e.g., storing account information locally or remotely for use) to perform an application (e.g., a web browser application or a non-web browser application) autofill operation (e.g., account information autofill and / or payment information autofill) on the computer system (e.g., functionality to automatically populate application forms, such as website forms or non-web site forms, with account information (e.g., login / password, payment account information, email information, and / or physical address information), and / or functionality to populate forms or fields (e.g., of a website or application) displayed by the application based on (e.g., in response to) a user selection of an account), but are not provisioned in an electronic wallet on the computer system (e.g., a wallet that enables NFC payments using the computer system and / or stores account credentials in a secure element of the computer system). In some embodiments, credentials for one or more accounts enabled to perform application autofill operations are not stored in the secure element of the computer system, but credentials for accounts provisioned on the electronic wallet of the computer system are stored in the secure element of the computer system. In some embodiments, the transaction terminal (e.g., contactless payment terminal) communicates directly with the secure element through the (NFC) controller of the computer system via a dedicated hardware bus of the computer system.In some embodiments, the provisioning interface includes a first selectable user interface object (e.g., 916, 1016, 1022) for initiating a process of provisioning one or more accounts into an electronic wallet of the computer system. In some embodiments, the first selectable user interface object includes an indication.
[0270] In some embodiments, the computer system receives (1104) a selection of a first selectable user interface object (e.g., a tap input or other selection of any of 916, 1016, and / or 1022) via one or more input devices.
[0271] In some embodiments, in response to receiving a selection of the first selectable user interface object, the computer system initiates a process (1106) to provision a first account (and, optionally, a second account and / or all accounts) of the one or more accounts into an electronic wallet of the computer system (e.g., as shown in Figures 9B, 10C, and / or 10D). In some embodiments, the process of provisioning a first account (and, optionally, a second account and / or all accounts) of the one or more accounts into an electronic wallet of the computer system uses at least some account information about the first account (e.g., information that an application autofill operation populates in an application (e.g., web browser or non-web browser) form, login / password, email information, physical address information, and / or payment account information such as account number, account expiration date, account holder name, and / or security code), which account information is stored for use in the application autofill operation.
[0272] In some embodiments, after receiving the selection of the first selectable user interface object, the computer system provisions (1108) the first account on the electronic wallet of the computer system using at least some account information about the first account (e.g., information that an application autofill operation would populate an application form, login / password, email information, physical address information, and / or payment account information such as account number, account expiration date, account holder name, and / or security code), where the account information is stored for use in the application autofill operation. In some embodiments, provisioning the first account on the electronic wallet of the computer system includes storing credential information about the first account in a secure element of the computer system. In some embodiments, provisioning the first account on the electronic wallet of the computer system includes enabling the computer system to use the first account for NFC and / or other near-field transactions (e.g., transfers and / or payments). Displaying an indication that one or more accounts are enabled for performing application autofill operations at the computer system but are not provisioned on the electronic wallet of the computer system provides the user with visual feedback regarding the status of the accounts on the computer system, thereby providing improved visual feedback.
[0273] In some embodiments, the computer system performs the transfer using a first account provisioned in the computer system's electronic wallet via one or more short-range communication radios (e.g., NFC radio(s) and / or short-range communication radio(s)). In some embodiments, the computer system, in response to performing the transfer using the first account, pursuant to determining that one or more accounts are enabled (e.g., have account information stored locally or remotely for use) at the computer system to perform application (e.g., web browser application or non-web browser application) autofill operations (e.g., account information autofill and / or payment information autofill), (e.g., functionality for automatically populating application forms, such as website forms or non-web site forms, with account information (e.g., login / password, payment account information, email information, and / or physical address information), and / or functionality for populating forms or fields displayed by the application (e.g., at a website or application) with information corresponding to the account based on (e.g., in response to) a user selection of an account), and are not provisioned on the computer system's electronic wallet, displays, via the display generation component, a notification (e.g., 916, 1016, and / or 1022) (e.g., overlaid on another user interface of the computer system) indicating that the one or more accounts are enabled at the computer system to perform application autofill operations and are not provisioned on the computer system's electronic wallet.In some embodiments, in response to performing a transfer using the first account, the computer system, in accordance with a determination that no accounts are enabled at the computer system to perform application autofill operations and not provisioned on the computer system's electronic wallet (e.g., all accounts enabled to perform autofill operations are also provisioned on the electronic wallet, or no accounts are enabled to perform autofill operations), ceases displaying a notification indicating that one or more accounts are enabled at the computer system to perform application autofill operations and not provisioned on the computer system's electronic wallet (e.g., ceases displaying any of 916, 1016, and / or 1022). In some embodiments, in response to receiving a selection of the notification indicating that one or more accounts are enabled at the computer system to perform application autofill operations and not provisioned on the computer system's electronic wallet, the computer system initiates a process to provision at least some of the one or more accounts on the computer system's electronic wallet. Displaying a notification indicating that one or more accounts are enabled at the computer system to perform application autofill operations and not provisioned on the computer system's electronic wallet provides the user with visual feedback regarding the status of the accounts on the computer system, thereby providing improved visual feedback.
[0274] In some embodiments, the computer system receives user input (e.g., 1222a, 1222b, 1322a, and / or 1322b) (e.g., account information for a second account) via one or more input devices to enable performing an application (e.g., a web browser application or a non-web browser application) autofill operation using the second account, different from the first account. In some embodiments, the computer system, in response to receiving the user input enabling performing an application autofill operation using the second account (and optionally following a determination that the second account is not provisioned on the computer system's electronic wallet), displays, via the display generation component, a notification (e.g., 916, 1016, and / or 1022) (e.g., overlaid on another user interface of the computer system) indicating that one or more accounts are enabled for performing application autofill operations at the computer system but are not provisioned on the computer system's electronic wallet. In some embodiments, when the computer system receives a user instruction to add a new account to an application for performing an autofill operation (e.g., without provisioning the account and / or without enabling the account to use virtual account functionality), the computer system prompts the user with a notification indicating that the account may be provisioned on the computer system. In some embodiments, in response to receiving a selection of the notification indicating that one or more accounts are enabled for performing application autofill operations at the computer system but are not provisioned on the computer system's electronic wallet, the computer system initiates a process to provision at least some of the one or more accounts on the computer system's electronic wallet.Displaying a notification indicating that one or more accounts are enabled for performing application autofill operations on the computer system and are not provisioned on the electronic wallet of the computer system provides the user with visual feedback regarding the status of the accounts on the computer system, thereby providing improved visual feedback.
[0275] In some embodiments, the computer system receives, via one or more input devices, a selection of an option to perform a transfer using an account provisioned on the computer system while displaying, via a display generation component, a first user interface of a first application while the first account is provisioned on the computer system's electronic wallet. In some embodiments, the computer system, in response to receiving the selection of the option to perform the transfer using the account provisioned on the computer system, displays, via the display generation component, a second user interface of a second application (e.g., a wallet application corresponding to the electronic wallet and / or an operating system application) identifying the first account for performing the transfer. In some embodiments, the computer system receives, via the one or more input devices, one or more user inputs including authorization to use the first account provisioned on the computer system's electronic wallet for the transfer and user authentication (e.g., biometric authentication (e.g., fingerprint authentication, face authentication, iris authentication, passcode authentication)). In some embodiments, the computer system transfers credential information (e.g., account information and / or payment information) for a first account from the second application to the first application in response to receiving one or more user inputs, where the credential information is exposed from a secure element of the computer system based on the received authorization and user authentication. In some embodiments, the authorization indicates that the user wishes to proceed with the transfer, and the user authentication confirms that the user is an authorized user of the computer system. Performing the transfer using the first account between the first application and the second application based on the user authentication allows the computer system to perform the operation securely, thereby providing improved security.
[0276] In some embodiments, in response to receiving a selection of the first selectable user interface object, the computer system displays, via a display generating component, an option for aborting the process of provisioning a first account of the one or more accounts (and, optionally, a second account and / or all accounts of the one or more accounts) into the electronic wallet of the computer system (e.g., selection of the “No Thanks” option in FIG. 10C ). In some embodiments, the computer system receives, via one or more input devices, a selection of the option for aborting the process of provisioning the first account. In some embodiments, the computer system aborts the process of provisioning the first account into the electronic wallet of the computer system in response to receiving a selection of the option to abort the process of provisioning the first account. Providing the user with an option to abort the process of provisioning the first account into the electronic wallet of the computer system provides visual feedback to the user that the process of provisioning the first account into the electronic wallet has begun, thereby providing the user with improved visual feedback.
[0277] In some embodiments, an indication (e.g., 916, 1016, and / or 1022) that one or more accounts are enabled for performing application autofill operations at the computer system and are not provisioned on the computer system's electronic wallet is displayed based on one or more accounts being eligible for provisioning on the computer system's electronic wallet. In some embodiments, this indication does not include accounts that are not provisioned on the electronic wallet when application autofill operations can be performed and the accounts are not eligible for provisioning on the computer system's electronic wallet. Displaying the indication based on one or more accounts being eligible for provisioning on the computer system's electronic wallet provides visual feedback to the user that one or more accounts are eligible for provisioning, thereby providing improved visual feedback.
[0278] In some embodiments, the computer system receives a request (e.g., 1222a, 1222b, 1322a, and / or 1322b) via one or more input devices to perform an autofill operation (e.g., automatically fill in fields with account information and / or automatically fill in a payment form with account information) using the first account prior to provisioning the first account into the electronic wallet of the computer system. In some embodiments, in response to receiving a request to perform an autofill operation using the first account, the computer system performs the autofill operation without using the virtual account functionality of the first account. In some embodiments, when the virtual account functionality is not enabled for the first account, the computer system automatically uses (e.g., transmits via short-range communication radio such as NFC, automatically populates fields, and / or transmits via a wired or wireless communication channel, such as during transactions and / or autofill operations over the Internet) the same credential information (e.g., the same account number, the same expiration date, the same account holder name, and / or the same security code) for consecutive (e.g., for two consecutive, three consecutive, and / or all transactions) transactions performed using the first account. In some embodiments, when the virtual account functionality is enabled for a first account, the computer system automatically uses (e.g., transmitted via short-range communication radio such as NFC, automatically populating fields, automatically populating fields, and / or transmitted via a wired or wireless communication channel, such as during transactions and / or autofill operations over the Internet) different credential information (e.g., different account numbers corresponding to the same account, different expiration dates, different account holder names (e.g., John Doe vs. John H. Doe), and / or different security codes) for consecutive (e.g., two consecutive, three consecutive, and / or all transactions) transactions performed using the first account.Performing an autofill operation for the first account without using the virtual account feature allows the computer system to reuse the same credential information for successive transactions, making it easier for the user to verify that the correct credential is being used, thereby providing improved visual feedback to the user.
[0279] In some embodiments, provisioning a first account on the electronic wallet of the computer system includes enabling virtual account functionality for the first account. In some embodiments, when virtual account functionality is not enabled for the first account, the computer system automatically uses (e.g., transmits via short-range communication wirelessly such as NFC, automatically populates fields, and / or transmits via a wired or wireless communication channel, such as during a transaction and / or an autofill operation over the Internet) the same credential information (e.g., the same account number, the same expiration date, the same account holder name, and / or the same security code) for consecutive (e.g., two consecutive, three consecutive, and / or all) transactions performed using the first account. In some embodiments, when the virtual account functionality is enabled for a first account, the computer system automatically uses (e.g., transmitted via short-range communication radio such as NFC, automatically populating fields, automatically populating fields, and / or transmitted via a wired or wireless communication channel, such as during transactions and / or autofill operations conducted over the Internet) different credential information (e.g., different account numbers, different expiration dates, different account holder names (e.g., John Doe vs. John H. Doe), and / or different security codes corresponding to the same account) for consecutive (e.g., two consecutive, three consecutive, and / or all transactions) transactions performed using the first account. Performing an autofill operation using the virtual account functionality for the first account allows the computer system to use different credential information for consecutive transactions, thereby providing improved security to the user.
[0280] In some embodiments, after provisioning the first account into the electronic wallet of the computer system, the computer system receives, via one or more input devices, a second request (e.g., 1222a, 1222b, 1322a, and / or 1322b) to perform an autofill operation using the first account (e.g., automatically fill in fields with account information and / or automatically fill in a payment form with account information). In some embodiments, in response to receiving the second request to perform the autofill operation using the first account, the computer system performs the autofill operation using a virtual account feature of the first account. Performing the autofill operation using the virtual account feature for the first account allows the computer system to use different credentials for successive transactions, thereby providing improved security to the user.
[0281] In some embodiments, the process of provisioning a first account of the one or more accounts (and, optionally, a second account and / or all of the one or more accounts) on an electronic wallet of the computer system includes displaying, via a display generating component, a request for second account information (e.g., card security code and / or billing address information) related to the first account. In some embodiments, the process of provisioning a first account of the one or more accounts (and, optionally, a second account and / or all of the one or more accounts) on an electronic wallet of the computer system includes receiving second information (e.g., from a user) via one or more input devices, and using the second account information to provision the first account of the one or more accounts (and, optionally, a second account and / or all of the one or more accounts) on the electronic wallet of the computer system. Using the second account information to provision the first account improves security of the first account and the computer system by verifying that the user has access to the second account information before the first account is provisioned (thereby verifying that the user has access to the first account).
[0282] In some embodiments, the computer system, in response to detecting a transfer using a second account provisioned on the computer system's electronic wallet, enables virtual account functionality for the second account provisioned on the computer system's electronic wallet. In some embodiments, the computer system, in response to detecting a transfer using the second account provisioned on the computer system's electronic wallet, configures an autofill application to use the virtual account functionality for the second account (e.g., when browser autofill operations are performed, the autofill operations use different account information for successive autofill operations). In some embodiments, in response to detecting a transfer using the second account provisioned on the computer system's electronic wallet, the computer system displays, via a display generation component, an indication that the virtual account functionality has been enabled for the second account and is available for use in the autofill application. In some embodiments, if the virtual account feature is not enabled for an individual account, the computer system automatically uses (e.g., transmits via short-range communication radio such as NFC, auto-populates fields, and / or transmits via a wired or wireless communication channel, such as during transactions and / or autofill operations over the Internet) the same credential information (e.g., the same account number, the same expiration date, the same account holder name, and / or the same security code) for consecutive (e.g., two consecutive, three consecutive, and / or all transactions) transactions performed using the individual account.In some embodiments, when the virtual account functionality is enabled for an individual account, the computer system automatically uses (e.g., transmits via short-range communication radio such as NFC, automatically populates fields, automatically populates fields, and / or transmits via a wired or wireless communication channel, such as during a transaction and / or autofill operation conducted over the Internet) different credential information (e.g., different account numbers, different expiration dates, different account holder names (e.g., John Doe vs. John H. Doe), and / or different security codes corresponding to the same account) for consecutive (e.g., two consecutive, three consecutive, and / or all transactions) transactions performed using the individual account. Automatically enabling the virtual account functionality for a second account provisioned on the computer system's electronic wallet and configuring the autofill application to use the virtual account functionality for the second account reduces the need for a user to provide input to enable the virtual account functionality and configure the autofill application, thereby reducing the number of inputs required.
[0283] In some embodiments, in accordance with a determination that the individual account is not provisioned on the computer system's electronic wallet, the individual account is not available for performing transfers using the computer system's communications radio (e.g., NFC radio and / or short-range communications radio). In some embodiments, in accordance with a determination that the individual account is provisioned on the computer system's electronic wallet, the individual account is available for performing transfers using the computer system's communications radio (e.g., NFC radio and / or short-range communications radio). In some embodiments, in accordance with a determination that the individual account is not provisioned on the computer system's electronic wallet, credential information for the individual account is not stored in the computer system's secure element (e.g., is disclosed after authentication and / or authorization for use in transfers), and in accordance with a determination that the individual account is provisioned on the computer system's electronic wallet, credential information for the individual account is stored in the computer system's secure element (e.g., is disclosed after authentication and / or authorization for use in transfers). An account available for transfer via a communications radio when provisioned on the computer system's electronic wallet enables the computer system to perform transactions using additional techniques (e.g., NFC), thereby making the computer system more efficient.
[0284] It should be noted that the details of the process (e.g., FIG. 11 ) described above with respect to method 1100 are also applicable in an analogous manner to the methods described above and / or below. For example, method 800 optionally includes one or more of the features of the various methods described above with reference to method 1100. For example, after provisioning a transfer account as described with respect to method 1100, virtual account functionality may be enabled for the provisioned transfer account as described with respect to method 800. For the sake of brevity, these details will not be repeated below.
[0285] 12A-12C illustrate exemplary user interfaces for obfuscating storage account credentials, according to some embodiments. The user interfaces in these figures are used to illustrate processes described below, including the process of FIG. 14. In some embodiments, device 1200 includes one or more features of devices 100, 300, and / or 500.
[0286] 12A , electronic device 1200 displays on display 1202 (e.g., touchscreen 1302) user interface 1210 corresponding to a first transaction. In some embodiments, the first transaction is a transaction conducted using a web browsing application. Thus, in some embodiments, user interface 1210 is a user interface of the web browsing application (e.g., a website displayed by the web browsing application).
[0287] User interface 1210 includes credential fields 1212 corresponding to various credentials for a computer storage management account. As one example, credential field 1212a is a field for an account number (e.g., a virtual account number or a physical account number) for the computer storage management account. As another example, credential field 1212b is a field for a name associated with the computer storage management account. As yet another example, credential field 1212c is a field for an expiration date for the account number for the computer storage management account. As yet another example, credential field 1212d is a field for a security code for the computer storage management account.
[0288] 12A, the user interface 1210, in some embodiments, further includes a keypad 1214 that can be used to manually enter an account number into the credential field 1212a. In FIG. 12A, the device 1200 further displays an autofill interface 1220. The autofill interface 1220, in some embodiments, is overlaid on the user interface 1210.
[0289] Autofill interface 1220 includes account affordances 1222, each of which corresponds to a distinct computer storage management account. In some embodiments, account affordances 1222 correspond only to computer storage management accounts provisioned on device 1200 (e.g., available in an electronic wallet application of device 1200 and / or stored in a secure element of device 1200). In some embodiments, account affordances 1222 correspond to computer storage management accounts provisioned on device 1200 and to computer storage management accounts not provisioned on device 1200 but for which autofill operations are enabled.
[0290] While displaying the autofill interface 1220, the device 1200 detects a selection of an account affordance 1222a corresponding to a first computerized storage management account (the “star account”). In some embodiments, the selection is a tap gesture 1205b on the account affordance 1222a. As shown in FIG. 12B , in response to detecting the selection of the account affordance 1222a, the device 1200 autofills one or more credential fields 1212 with credentials corresponding to the first computerized storage management account.
[0291] In some embodiments, virtual account functionality has been enabled for the first computer storage management account. In some embodiments, as a result of enabling the virtual account functionality for the first computer storage management account, a virtual account number (e.g., a number ending in “8890”) and / or other virtual credentials have been provided for the first computer storage management account (e.g., a “star account”). Thus, when autofilling credential field 1212 with credentials corresponding to the first computer storage management account, device 1200 autofills the credential field with the virtual credentials (e.g., the virtual account number and / or rotating security code) of the first computer storage management account. As an example, credential field 1212a is autofilled with the virtual account number (e.g., a number ending in “8890”) of the transfer account, and credential field 1312d is autofilled with the rotating security code (e.g., a number ending in “4”) of the transfer account.
[0292] 12A , account affordance 1222a is shown as an account having an account number ending in "0234." In some embodiments, the number shown in autofill interface 1320 corresponds to at least a portion of the physical account number of the first computer storage management account. In contrast, in FIG. 12B , the number autofilled into credential field 1212a (e.g., corresponding to the virtual account number of the computer storage management account) is a number ending in "8890." Thus, in some embodiments, device 1200 displays autofill interface 1220 with a reference to the physical account number and autofills using the virtual account number (e.g., when provided for the computer storage management account).
[0293] In some embodiments, one or more virtual credentials are obscured when used to autofill credential fields 1212. As an example, in Figure 12B, device 1200 obscures at least a portion of the virtual account number autofilled into credential field 1212a and / or the rotated security code autofilled into credential field 1212d. In some embodiments, the rotated security code autofilled into credential field 1212d is completely obscured so that none of the digits are readable.
[0294] 12A , device 1200 detects a selection of account affordance 1222b corresponding to a second computerized storage management account (“cloud storage”). In some embodiments, the selection is a tap gesture 1207b on account affordance 1222b. As shown in FIG. 12C , in response to detecting the selection of account affordance 1222b, device 1200 autofills one or more credential fields 1212 with credentials corresponding to the second computerized storage management account.
[0295] In some embodiments, the virtual account functionality is not enabled for the second computer storage management account. Thus, when autofilling the credential fields 1212 using credentials corresponding to the second computer storage management account, the device 13200 autofills the credential fields using the physical credentials (e.g., the physical account number and / or the physical security code) of the second computer storage management account, as shown in Figure 12C. As an example, the credential field 1212a in Figure 12C is autofilled using the physical account number of the second computer storage management account, and the credential field 1212d is autofilled using the physical security code of the second computer storage management account.
[0296] In some embodiments, the physical credential is displayed without obfuscation (e.g., without obscuring) when used to autofill credential field 1212. As an example, in Figure 12C, device 1200 displays the physical account number (e.g., a number ending in "1234") autofilled into credential field 1212a and / or the physical security code (e.g., "777") autofilled into credential field 1212d without obfuscation.
[0297] 13A-13J show exemplary user interfaces for obfuscating account credentials, according to some embodiments. The user interfaces in these figures are used to illustrate processes described below, including the process of FIG. 14. In some embodiments, device 130000 includes one or more functions of devices 100, 300, and / or 500.
[0298] 13A-13J illustrate various examples in which transactions are performed using credentials corresponding to various transfer accounts. As described in more detail below, in some embodiments, the credentials (e.g., virtual credentials for transfer accounts provided with virtual account numbers, as described with respect to FIGS. 7A-7M) are selectively obscured during a transaction.
[0299] 13A-13G illustrate the operation of device 1300 during a first transaction. In some embodiments, device 1300 is a portable multifunction device and has one or more components described above with respect to one or more of devices 100, 300, and 500.
[0300] 13A , electronic device 1300 displays on display 1302 (e.g., touchscreen 1302) user interface 1310 corresponding to a first transaction. In some embodiments, the first transaction is a transaction conducted using a web browsing application. Thus, in some embodiments, user interface 1310 is a user interface of the web browsing application (e.g., a website displayed by the web browsing application).
[0301] User interface 1310 includes credential fields ...
Claims
1. 1. A method comprising: A computer system in communication with a display generation component and one or more input devices, comprising: receiving, via the one or more input devices, user instructions enabling adding account information for a first account of one or more accounts to an application on the computer system and performing an application autofill operation using the first account, the first account not being provisioned on an electronic wallet on the computer system; In response to receiving the user command, adding the account information for the first account to the application on the computer system without provisioning the first account in the electronic wallet on the computer system; Enabling execution of an application autofill action using the first account; via the display generation component, an indication that the one or more accounts are enabled to perform application autofill operations on the computer system and are not provisioned on the electronic wallet on the computer system; and a first selectable user interface object that initiates a process for provisioning the one or more accounts on the electronic wallet of the computer system; displaying a provisioning user interface including: receiving a selection of the first selectable user interface object via the one or more input devices; In response to receiving a selection of the first selectable user interface object, initiating a process for provisioning the first account of the one or more accounts into the electronic wallet of the computer system, the process for provisioning the first account of the one or more accounts into the electronic wallet of the computer system using at least some account information related to the first account, the account information being stored for use in the application autofill operation; provisioning the first account on the electronic wallet of the computer system using at least some account information related to the first account after receiving a selection of the first selectable user interface object, the account information being stored for use in the application autofill operation; A method comprising:
2. performing a transfer using a first account provisioned in the electronic wallet of the computer system via one or more short-range communication radios; In response to performing the transfer using the first account, pursuant to determining that one or more accounts are enabled at the computer system to perform application autofill operations but are not provisioned on the electronic wallet at the computer system, displaying, via the display generating component, a notification indicating that one or more accounts are enabled at the computer system to perform application autofill operations but are not provisioned on the electronic wallet at the computer system; 10. The method of claim 1, further comprising: in accordance with a determination that there are no accounts enabled at the computer system to perform application autofill operations and that are not provisioned on the electronic wallet at the computer system, ceasing to display the notification indicating that one or more accounts are enabled at the computer system to perform application autofill operations and that are not provisioned on the electronic wallet at the computer system.
3. While the first account is being provisioned in the electronic wallet of the computer system, receiving, via the one or more input devices, a selection of an option to perform a transfer using an account provisioned on the computer system while displaying, via the display generation component, a first user interface of a first application; In response to receiving a selection of the option to perform the transfer using an account provisioned on the computer system, displaying, via the display generation component, a second user interface of a second application identifying the first account for performing the transfer; via the one or more input devices; authorization to use the first account provisioned on the electronic wallet of the computer system for the transfer; User authentication; receiving one or more user inputs including: receiving, in response to receiving the one or more user inputs, transferring credential information for the first account from the second application to the first application, the credential information being exposed from a secure element of the computer system based on the received authorization and user authentication; The method of claim 1 further comprising:
4. In response to receiving a selection of the first selectable user interface object, displaying, via the display generation component, an option to abort the process of provisioning the first of the one or more accounts into the electronic wallet of the computer system; receiving, via the one or more input devices, a selection of the option to abort the process of provisioning the first account; In response to receiving a selection of the option to abort the process of provisioning the first account, aborting the process of provisioning the first account in the electronic wallet of the computer system; The method of claim 1 further comprising:
5. 2. The method of claim 1, wherein the indication that one or more accounts are enabled for performing application autofill operations on the computer system and are not provisioned on the electronic wallet of the computer system is displayed based on the one or more accounts being eligible for provisioning on the electronic wallet of the computer system.
6. receiving, via the one or more input devices, a request to perform an autofill operation using the first account prior to provisioning the first account on the electronic wallet of the computer system; In response to receiving the request to perform an autofill operation using the first account, performing the autofill operation without using virtual account functionality for the first account; when the virtual account functionality is not enabled for the first account, the computer system automatically uses the same credential information for successive transactions performed using the first account; performing the autofill operation, in which the computer system automatically uses different credential information for successive transactions performed using the first account when the virtual account functionality is enabled for the first account; The method of claim 1 further comprising:
7. Provisioning the first account on the electronic wallet of the computer system includes enabling virtual account functionality for the first account, when the virtual account functionality is not enabled for the first account, the computer system automatically uses the same credential information for successive transactions performed using the first account; 10. The method of claim 1, further comprising enabling a virtual account feature, wherein when the virtual account feature is enabled for the first account, the computer system automatically uses different credential information for successive transactions performed using the first account.
8. receiving, via the one or more input devices, a second request to perform an autofill operation using the first account after provisioning the first account in the electronic wallet of the computer system; 8. The method of claim 7, further comprising, in response to receiving the second request to perform an autofill operation using the first account, performing the autofill operation using the virtual account functionality for the first account.
9. the process of provisioning the first of the one or more accounts into the electronic wallet of the computer system, displaying, via the display generation component, a request for second account information related to the first account; receiving the second account information via the one or more input devices; and provisioning the first of the one or more accounts into the electronic wallet of the computer system using the second account information.
10. in response to detecting a transfer using a second account provisioned on the electronic wallet of the computer system; enabling virtual account functionality for the second account provisioned on the electronic wallet of the computer system; configuring the application autofill behavior to use the virtual account functionality for the second account; displaying, via the display generation component, an indication that the virtual account functionality has been enabled for the second account and is available for use in the application autofill operation; When the virtual account feature is not enabled for an individual account, the computer system automatically uses the same credential information for successive transactions performed using the individual account; when the virtual account functionality is enabled for the individual account, the computer system automatically uses different credentials for successive transactions performed using the individual account. Displaying an indication; and The method of claim 1 further comprising:
11. In accordance with a determination that an individual account is not provisioned on the electronic wallet of the computer system, the individual account is not available to perform a transfer using a communications radio of the computer system; 10. The method of claim 1, wherein, pursuant to a determination that the individual account is provisioned on the electronic wallet of the computer system, the individual account is available to perform transfers using the communications radio of the computer system.
12. A computer program that causes a computer to execute a method according to any one of claims 1 to 11.
13. A computer system comprising: a memory for storing the computer program of claim 12; one or more processors capable of executing the computer programs stored in the memory; Equipped with The computer system is configured to communicate with a display generation component and one or more input devices.
14. 1. A computer system configured to communicate with a display generation component and one or more input devices, comprising: A computer system comprising means for carrying out the method according to any one of claims 1 to 11.
Citation Information
Patent Citations
ELECTRONIC WALLET DEVICE, METHOD AND COMPUTER PROGRAM PRODUCT
JP2016500182A
Secure Transaction Interface
JP2019506649A
Method and system for providing financial transaction using empty card
JP2020027653A
Managing program credentials on electronic devices
US20170272413A1
Systems and methods for configuration information autofill at a browser linked with user accounts
US20220058617A1