User Interface for Loyalty Accounts and Private Label Accounts for Wearable Devices

Abstract

The invention is titled "User Interfaces for Loyalty Accounts and Private Label Accounts for Wearable Devices". This disclosure generally relates to the use of loyalty accounts, private label payment accounts, and general payment accounts using a wearable electronic device having an electronic wallet. Various accounts are linked to the electronic device. In some examples, the electronic device supports NFC. The electronic device can be used to provide loyalty account information and payment account information to a payment terminal such as an NFC-enabled payment terminal.

Description

[0001] Cross - Reference to Related Applications

[0002] This application is a divisional application of the Chinese patent application with the application number 201610371774.4, the filing date of May 30, 2016, and the invention title of "User Interface for Loyalty Accounts and Private Label Accounts for Wearable Devices".

[0003] This patent application claims priority to U.S. Provisional Application Serial No. 62 / 230,430, filed on June 5, 2015, with the title "USER INTERFACE FOR LOYALTY ACCOUNTS AND PRIVATE LABEL ACCOUNTS FOR A WEARABLE DEVICE", which is hereby incorporated by reference in its entirety for all purposes.

[0004] This patent application is related to the following provisional patent applications: U.S. Patent Application Serial No. 62 / 004,886, titled "USER INTERFACE FOR PAYMENTS", filed on May 29, 2014 (Reference No. P22848USP1); U.S. Patent Application Serial No. 62 / 047,545, titled "USER INTERFACE FOR PAYMENTS", filed on September 8, 2014 (Reference No. P22848USP2); U.S. Patent Application Serial No. 62 / 127,790, titled "USER INTERFACE FOR PAYMENTS", filed on March 3, 2015 (Reference No. P22848USP3); and U.S. Patent Application Serial No. 62 / 110,566, titled "USER INTERFACE FOR PAYMENTS", filed on February 1, 2015 (Reference No. P26049USP1); U.S. Patent Application Serial No. 61 / 912,727, titled "PROVISIONING AND AUTHENTICATING CREDENTIALS ON AN ELECTRONIC DEVICE", filed on December 6, 2013 (Reference No. P19543USP1); U.S. Patent Application Serial No. 61 / 909,717, titled "PROVISIONING OF CREDENTIALS ON AN ELECTRONIC DEVICE USING PASSWORDS COMMUNICATED OVER VERIFIED CHANNELS", filed on November 27, 2013 (Reference No. P19950USP1); U.S. Patent Application Serial No. 62 / 004,182, titled "ONLINE PAYMENTS USING A SECURE ELEMENT OF AN ELECTRONIC DEVICE", filed on May 28, 2014 (Reference No. P20450USP4); U.S. Patent Application Serial No. 61 / 920,029, titled "DELETION OF CREDENTIALS FROM AN ELECTRONIC DEVICE", filed on December 23, 2013 (Reference No. P21084USP1); U.S. Patent Application Serial No. 61 / 899,737, titled "USING BIOAUTHENTICATION IN NEAR-FIELD-COMMUNICATION TRANSACTIONS", filed on November 4, 2013 (Reference No. P21646USP1);U.S. Patent Application Serial No. 61 / 905,035 (Reference No. P21714USP1) titled "GENERATING TRANSACTION IDENTIFIERS", filed on November 15, 2013; U.S. Patent Application Serial No. 61 / 905,042 (Reference No. 21734USP1) titled "ELECTRONIC RECEIPTS FOR NFC-BASED FINANCIAL TRANSACTIONS", filed on November 15, 2013; U.S. Patent Application Serial No. 62 / 004,798 (Reference No. P23211USP1) titled "FINANCIAL-TRANSACTION NOTIFICATIONS", filed on May 29, 2014; U.S. Patent Application Serial No. 62 / 004,837 (Reference No. P23215USP1) titled "METHODS FOR MANAGING PAYMENT APPLETS ON A SECURE ELEMENT TO CONDUCT MOBILE PAYMENT TRANSACTIONS", filed on May 29, 2014; U.S. Patent Application Serial No. 62 / 004,840 (Reference No. P23223USP1) titled "METHODS FOR OPERATING A PORTABLE ELECTRONIC DEVICE TO CONDUCT MOBILE PAYMENT TRANSACTIONS", filed on May 29, 2014; U.S. Patent Application Serial No. 62 / 004,835 (Reference No. P23224USP1) titled "METHODS FOR USING A PRIMARY USER DEVICE TO PROVISION CREDENTIALS ONTO A SECONDARY USER DEVICE", filed on May 29, 2014; U.S. Patent Application Serial No. 62 / 004,832 (Reference No. P23261USP1) titled "METHODS FOR USING A RANDOM AUTHORIZATION NUMBER TO PROVIDE ENHANCED SECURITY FOR A SECURE ELEMENT", filed on May 29, 2014;U.S. Patent Application Serial No. 62 / 004,338, filed on May 29, 2014, entitled "USER DEVICE SECURE PARTICIPATION IN TRANSACTIONS VIA LOCAL SECURE ELEMENT DETECTION OF MECHANICAL INPUT" (Reference No. P22931USP1); and U.S. Patent Application Serial No. 14 / 092,205, filed on November 27, 2013, entitled "SECURE PROVISIONING OF CREDENTIALS ON AN ELECTRONIC DEVICE" (Reference No. P19545US1); each of these patent applications is hereby incorporated by reference in its entirety; FIELD OF THE TECHNOLOGY

[0005] The present disclosure generally relates to computer user interfaces and, more particularly, to technologies for computer user interfaces for loyalty accounts and payment accounts. BACKGROUND OF THE TECHNOLOGY

[0006] In recent years, the use of electronic devices to make payments via the Internet at point-of-sale terminals has increased significantly. Exemplary point-of-sale terminals include terminals that support near field communication (NFC-enabled), terminals that support Bluetooth, and terminals that support barcode scanners. Electronic devices can be used in conjunction with these exemplary terminals to enable users of the electronic devices to make payments for purchases such as goods or services. SUMMARY OF THE INVENTION

[0007] However, some technologies for linking accounts to electronic devices, selecting accounts for transactions, and transmitting account information in transactions are generally cumbersome and inefficient. For example, the prior art uses complex and time-consuming user interfaces that may include multiple button presses or keystrokes. The prior art requires more time than necessary, which results in wasted user time and device energy. This latter consideration is particularly important in battery-powered devices.

[0008] Accordingly, the present invention provides faster and more efficient methods and interfaces for an electronic device to link accounts to the electronic device, select an account to be used in a transaction, and transmit account information in a transaction. Such methods and interfaces optionally supplement or replace other methods for performing similar tasks. Such methods and interfaces can reduce the cognitive burden imposed on the user and create a more efficient human-machine interface. Such methods and interfaces can also reduce the amount of unnecessary, redundant, repetitive, and / or superfluous input, and can create a faster and more efficient user interface layout that can reduce the amount of input required, reduce processing power, and reduce the amount of time the user interface needs to be displayed to access and perform the desired function. For battery-powered computing devices, such methods and interfaces save power and increase the time interval between two battery charges.

[0009] A method includes: at an electronic device having a display, a touch-sensitive surface, and one or more wireless communication elements: receiving an input for requesting to enable the device for a payment transaction; in response to receiving the input for requesting to enable the device for a payment transaction: displaying a first visual indicator on the display for identifying a first account; and enabling the electronic device to participate in a transaction using the first account via the one or more wireless communication elements; receiving one or more swipe inputs in a first direction via the touch-sensitive surface; in response to receiving the one or more user swipe inputs: displaying a second visual indicator on the display for identifying a second account; and enabling the electronic device to participate in a transaction using the second account via the one or more wireless communication elements; and wherein the first visual indicator is different from the second visual indicator.

[0010] A method includes: at an electronic device having a display and a location sensor: using the location sensor to detect a current location; determining whether the current location is associated with a first account; in accordance with a failure to determine that the current location is associated with an account other than a default payment account, displaying a visual indication of the default payment account on the display; in accordance with determining that the current location is associated with the first account, simultaneously displaying a visual indication of the default payment account and a visual indication of the first account on the display; and wherein the default payment account and the first account are linked to the electronic device, and the default payment account and the first account are different.

[0011] A method, comprising: at an electronic device having a display and a location sensor: receiving an input for requesting to enable the device for a payment transaction; and in response to receiving the input: using the location sensor to detect a current location; determining whether a set of one or more payment criteria is satisfied, wherein the set of one or more payment criteria includes criteria that are satisfied when the current location is associated with a first payment account; in accordance with determining that the set of one or more payment criteria is not satisfied, displaying a visual indication of a default payment account on the display, wherein the default payment account is different from the first payment account; and in accordance with determining that the set of one or more payment criteria is satisfied, displaying a visual indication of the first payment account on the display.

[0012] A method, comprising: at an electronic device having a display and one or more wireless communication elements: receiving an input for requesting to enable the device for a payment transaction; in response to receiving the input, displaying a payment indication on the display, the payment indication representing a plurality of payment accounts including a first payment account and a second payment account; receiving, via the one or more wireless communication elements, a request for account information corresponding to a payment transaction; in response to receiving the request for account information corresponding to the payment transaction: in accordance with determining that payment criteria for the first payment account are satisfied, transmitting, via the one or more wireless communication elements, the account information of the first payment account without transmitting the account information of the second payment account; and in accordance with determining that payment criteria for the second payment account are satisfied, transmitting, via the one or more wireless communication elements, the account information of the second payment account without transmitting the account information of the first payment account.

[0013] A method, comprising: at an electronic device having a display, a touch-sensitive surface configured to detect an intensity of contact, and one or more wireless communication elements: receiving a first input; in response to receiving the first input: displaying a first user interface on the display, wherein the first user interface includes: a first visual indicator for identifying a payment card associated with a plurality of payment accounts, and a second visual indicator for identifying a first payment account among the plurality of payment accounts of the payment card; enabling the electronic device to participate in a payment transaction using the first payment account via the one or more wireless communication elements; detecting a first contact on the touch-sensitive surface; determining whether a characteristic intensity of the first contact is higher than an intensity threshold; and in accordance with determining that the characteristic intensity of the first contact is higher than the intensity threshold, displaying a second user interface on the display, wherein the second user interface enables selection between different payment accounts represented by the first visual indicator.

[0014] A method includes: at a first electronic device having a display and one or more wireless communication elements: receiving a first request to link a payment account associated with a payment card to the first electronic device; in response to receiving the first request, initiating a process to link the payment account to the first electronic device; after successfully linking the payment account to the first electronic device, simultaneously displaying on the display: an indication that the payment account has been successfully linked to the first electronic device; and an optional enabling representation for linking the payment account to a second electronic device different from the first electronic device; and receiving an activation of the optional enabling representation; and in response to receiving the activation of the optional enabling representation, initiating a process to link the payment account to the second electronic device.

[0015] A method includes: at a first electronic device having a display and one or more wireless communication elements: displaying on the display a payment account user interface of a second electronic device associated with the first electronic device, wherein displaying the payment account user interface includes simultaneously displaying: a representation of a first payment account together with status information of the first payment account, the status information indicating that the first payment account is linked to the second electronic device and the second electronic device is configured to enable payments using the first payment account; and a representation of a second payment account together with status information of the second payment account, the status information indicating that the second payment account is linked to the first electronic device but not linked to the second electronic device.

[0016] An electronic device includes: a display; a touch-sensitive surface; and means for receiving an input for requesting to enable the device to perform a payment transaction; means for performing the following operations in response to receiving the input for requesting to enable the device to perform a payment transaction: displaying on the display a first visual indicator for identifying a first account; and enabling the electronic device to participate in a transaction using the first account via the one or more wireless communication elements; means for receiving, via the touch-sensitive surface, one or more swipe inputs in a first direction; means for performing the following operations in response to receiving the one or more user swipe inputs: displaying on the display a second visual indicator for identifying a second account; and enabling the electronic device to participate in a transaction using the second account via the one or more wireless communication elements; and wherein the first visual indicator is different from the second visual indicator.

[0017] An electronic device, comprising: a display; a touch-sensitive surface; and means for detecting a current location using the location sensor; means for determining whether the current location is associated with a first account; means for displaying a visual indication of a default payment account on the display based on a failure to determine that the current location is associated with an account other than the default payment account; means for displaying, on the display, a visual indication of the default payment account and a visual indication of the first account simultaneously based on determining that the current location is associated with the first account; and wherein the default payment account and the first account are linked to the electronic device and the default payment account and the first account are different.

[0018] An electronic device, comprising: a display; a touch-sensitive surface; and means for receiving an input for requesting to enable the device for a payment transaction; and means for performing the following operations in response to receiving the input: detecting a current location using the location sensor; determining whether a set of one or more payment criteria is satisfied, wherein the set of one or more payment criteria includes criteria satisfied when the current location is associated with a first payment account; displaying a visual indication of a default payment account on the display based on determining that the set of one or more payment criteria is not satisfied, wherein the default payment account is different from the first payment account; and displaying a visual indication of the first payment account on the display based on determining that the set of one or more payment criteria is satisfied.

[0019] An electronic device, comprising: a display; a touch-sensitive surface; and means for receiving an input for requesting to enable the device for a payment transaction; means for displaying, on the display, a payment indication representing a plurality of payment accounts including a first payment account and a second payment account in response to receiving the input; means for receiving, via the one or more wireless communication elements, a request for account information corresponding to a payment transaction; means for performing the following operations in response to receiving the request for account information corresponding to the payment transaction: transmitting the account information of the first payment account via the one or more wireless communication elements without transmitting the account information of the second payment account based on determining that the payment criteria of the first payment account are satisfied; and transmitting the account information of the second payment account via the one or more wireless communication elements without transmitting the account information of the first payment account based on determining that the payment criteria of the second payment account are satisfied.

[0020] An electronic device, comprising: a display; a touch-sensitive surface configured to detect the intensity of contact; and means for receiving a first input; means for displaying a first user interface on the display in response to receiving the first input, wherein the first user interface includes: a first visual indicator for identifying a payment card associated with a plurality of payment accounts, and a second visual indicator for identifying a first payment account among the plurality of payment accounts of the payment card; means for enabling the electronic device to participate in a payment transaction using the first payment account via the one or more wireless communication elements; means for detecting a first contact on the touch-sensitive surface; means for determining whether a characteristic intensity of the first contact is higher than an intensity threshold; and means for displaying a second user interface on the display based on determining that the characteristic intensity of the first contact is higher than the intensity threshold, wherein the second user interface enables selection between different payment accounts represented by the first visual indicator.

[0021] An electronic device, comprising: a display; a touch-sensitive surface; and means for receiving a first request to link a payment account associated with a payment card to the first electronic device; means for initiating a process to link the payment account to the first electronic device in response to receiving the first request; means for simultaneously displaying on the display, after the payment account is successfully linked to the first electronic device: an indication that the payment account has been successfully linked to the first electronic device; and an optional enabling representation for linking the payment account to a second electronic device different from the first electronic device; and means for receiving an activation of the optional enabling representation; and means for initiating a process to link the payment account to the second electronic device in response to receiving the activation of the optional enabling representation.

[0022] An electronic device, comprising: a display; a touch-sensitive surface; and means for displaying on the display a payment account user interface of a second electronic device associated with the first electronic device, wherein displaying the payment account user interface includes simultaneously displaying: a representation of a first payment account together with status information of the first payment account, the status information indicating that the first payment account is linked to the second electronic device and the second electronic device is configured to enable payment using the first payment account; and a representation of a second payment account together with status information of the second payment account, the status information indicating that the second payment account is linked to the first electronic device but not linked to the second electronic device.

[0023] A non-transitory computer-readable storage medium includes one or more programs for execution by one or more processors of an electronic device having a display, a touch-sensitive surface, and one or more wireless communication elements. The one or more programs include instructions that, when executed by the one or more processors, cause the electronic device to: receive an input for requesting to enable the device to perform a payment transaction; in response to receiving the input for requesting to enable the device to perform a payment transaction: display a first visual indicator on the display for identifying a first account; and enable the electronic device to participate in a transaction using the first account via the one or more wireless communication elements; receive one or more swipe inputs in a first direction via the touch-sensitive surface; in response to receiving the one or more user swipe inputs: display a second visual indicator on the display for identifying a second account; and enable the electronic device to participate in a transaction using the second account via the one or more wireless communication elements; and wherein the first visual indicator is different from the second visual indicator.

[0024] An electronic device includes: a display; a touch-sensitive surface; one or more wireless communication elements; one or more processors; a memory; and one or more programs stored in the memory. The one or more programs include instructions that, when executed by the one or more processors, cause the electronic device to: receive an input for requesting to enable the device to perform a payment transaction; in response to receiving the input for requesting to enable the device to perform a payment transaction: display a first visual indicator on the display for identifying a first account; and enable the electronic device to participate in a transaction using the first account via the one or more wireless communication elements; receive one or more swipe inputs in a first direction via the touch-sensitive surface; in response to receiving the one or more user swipe inputs: display a second visual indicator on the display for identifying a second account; and enable the electronic device to participate in a transaction using the second account via the one or more wireless communication elements; and wherein the first visual indicator is different from the second visual indicator.

[0025] A non-transitory computer-readable storage medium, comprising one or more programs for execution by one or more processors of an electronic device having a display and a position sensor, the one or more programs including instructions that, when executed by the one or more processors, cause the electronic device to: detect a current position using the position sensor; determine whether the current position is associated with a first account; display a visual indication of a default payment account on the display based on a failure to determine that the current position is associated with an account other than the default payment account; display a visual indication of the default payment account and a visual indication of the first account on the display based on determining that the current position is associated with the first account; and wherein the default payment account and the first account are linked to the electronic device and the default payment account and the first account are different.

[0026] An electronic device, comprising: a display; a position sensor; one or more processors; a memory; and one or more programs stored in the memory, the one or more programs including instructions that, when executed by the one or more processors, cause the electronic device to: detect a current position using the position sensor; determine whether the current position is associated with a first account; display a visual indication of a default payment account on the display based on a failure to determine that the current position is associated with an account other than the default payment account; display a visual indication of the default payment account and a visual indication of the first account on the display based on determining that the current position is associated with the first account; and wherein the default payment account and the first account are linked to the electronic device and the default payment account and the first account are different.

[0027] A non-transitory computer-readable storage medium, comprising one or more programs for execution by one or more processors of an electronic device having a display and a position sensor, the one or more programs including instructions that, when executed by the one or more processors, cause the electronic device to: receive an input for requesting to enable the device for a payment transaction; and in response to receiving the input: detect a current position using the position sensor; determine whether a set of one or more payment criteria has been met, wherein the set of one or more payment criteria includes criteria that are met when the current position is associated with a first payment account; display a visual indication of a default payment account on the display based on determining that the set of one or more payment criteria has not been met, wherein the default payment account is different from the first payment account; and display a visual indication of the first payment account on the display based on determining that the set of one or more payment criteria has been met.

[0028] An electronic device, comprising: a display; a position sensor; one or more processors; a memory; and one or more programs stored in the memory, the one or more programs including instructions that, when executed by the one or more processors, cause the electronic device to: receive an input for requesting to enable the device to perform a payment transaction; and in response to receiving the input: use the position sensor to detect a current position; determine whether a set of one or more payment criteria is satisfied, wherein the set of one or more payment criteria includes criteria that are satisfied when the current position is associated with a first payment account; in accordance with a determination that the set of one or more payment criteria is not satisfied, display a visual indication of a default payment account on the display, wherein the default payment account is different from the first payment account; and in accordance with a determination that the set of one or more payment criteria is satisfied, display a visual indication of the first payment account on the display.

[0029] A non-transitory computer-readable storage medium, comprising one or more programs for execution by one or more processors of an electronic device having a display and one or more wireless communication elements, the one or more programs including instructions that, when executed by the one or more processors, cause the electronic device to: receive an input for requesting to enable the device to perform a payment transaction; in response to receiving the input, display a payment indication on the display, the payment indication representing a plurality of payment accounts including a first payment account and a second payment account; receive, via the one or more wireless communication elements, a request for account information corresponding to a payment transaction; in response to receiving the request for the account information corresponding to the payment transaction: transmit, via the one or more wireless communication elements, the account information of the first payment account without transmitting the account information of the second payment account, in accordance with a determination that payment criteria for the first payment account are satisfied; and transmit, via the one or more wireless communication elements, the account information of the second payment account without transmitting the account information of the first payment account, in accordance with a determination that payment criteria for the second payment account are satisfied.

[0030] An electronic device, comprising: a display; one or more wireless communication components; one or more processors; a memory; and one or more programs stored in the memory, the one or more programs including instructions that, when executed by the one or more processors, cause the electronic device to: receive an input for requesting to enable the device to perform a payment transaction; in response to receiving the input, display a payment indication on the display, the payment indication representing a plurality of payment accounts including a first payment account and a second payment account; receive, via the one or more wireless communication components, a request for account information corresponding to the payment transaction; in response to receiving the request for the account information corresponding to the payment transaction: transmit, via the one or more wireless communication components, the account information of the first payment account without transmitting the account information of the second payment account according to a determination that the payment criteria for the first payment account have been met; and transmit, via the one or more wireless communication components, the account information of the second payment account without transmitting the account information of the first payment account according to a determination that the payment criteria for the second payment account have been met.

[0031] A non-transitory computer-readable storage medium, comprising one or more programs for execution by one or more processors of an electronic device having a display, a touch-sensitive surface configured to detect the intensity of contact, and one or more wireless communication components, the one or more programs including instructions that, when executed by the one or more processors, cause the electronic device to: receive a first input; in response to receiving the first input: display a first user interface on the display, wherein the first user interface includes: a first visual indicator for identifying a payment card associated with a plurality of payment accounts, and a second visual indicator for identifying a first payment account among the plurality of payment accounts of the payment card; enable the electronic device to participate in a payment transaction using the first payment account via the one or more wireless communication components; detect a first contact on the touch-sensitive surface; determine whether a characteristic intensity of the first contact is higher than an intensity threshold; and in response to determining that the characteristic intensity of the first contact is higher than the intensity threshold, display a second user interface on the display, wherein the second user interface enables selection between different payment accounts represented by the first visual indicator.

[0032] An electronic device, comprising: a display; a touch-sensitive surface configured to detect the intensity of contact; one or more wireless communication components; one or more processors; a memory; and one or more programs stored in the memory, the one or more programs including instructions that, when executed by the one or more processors, cause the electronic device to: receive a first input; in response to receiving the first input: display a first user interface on the display, wherein the first user interface includes: a first visual indicator for identifying a payment card associated with a plurality of payment accounts, and a second visual indicator for identifying a first payment account among the plurality of payment accounts of the payment card; enable the electronic device to participate in a payment transaction using the first payment account via the one or more wireless communication components; detect a first contact on the touch-sensitive surface; determine whether a characteristic intensity of the first contact is higher than an intensity threshold; and in accordance with determining that the characteristic intensity of the first contact is higher than the intensity threshold, display a second user interface on the display, wherein the second user interface enables selection between different payment accounts represented by the first visual indicator.

[0033] A non-transitory computer-readable storage medium, comprising one or more programs for execution by one or more processors of a first electronic device having a display and one or more wireless communication components, the one or more programs including instructions that, when executed by the one or more processors, cause the first electronic device to: receive a first request to link a payment account associated with a payment card to the first electronic device; in response to receiving the first request, initiate a process for linking the payment account to the first electronic device; after successfully linking the payment account to the first electronic device, simultaneously display on the display: an indication that the payment account has been successfully linked to the first electronic device; and an optional enabling representation for linking the payment account to a second electronic device different from the first electronic device; and receive an activation of the optional enabling representation; and in response to receiving the activation of the optional enabling representation, initiate a process for linking the payment account to the second electronic device.

[0034] A first electronic device, comprising: a display; one or more wireless communication components; one or more processors; a memory; and one or more programs stored in the memory, the one or more programs including instructions that, when executed by the one or more processors, cause the first electronic device to: receive a first request for linking a payment account associated with a payment card to the first electronic device; in response to receiving the first request, initiate a process for linking the payment account to the first electronic device; after successfully linking the payment account to the first electronic device, simultaneously display on the display: an indication that the payment account has been successfully linked to the first electronic device; and an optional enabling representation for linking the payment account to a second electronic device different from the first electronic device; and receive an activation of the optional enabling representation; and in response to receiving the activation of the optional enabling representation, initiate a process for linking the payment account to the second electronic device.

[0035] A non-transitory computer-readable storage medium, comprising one or more programs for execution by one or more processors of a first electronic device having a display and one or more wireless communication components, the one or more programs including instructions that, when executed by the one or more processors, cause the first electronic device to: display on the display a payment account user interface of a second electronic device associated with the first electronic device, wherein displaying the payment account user interface includes simultaneously displaying: a representation of a first payment account together with status information of the first payment account, the status information indicating that the first payment account is linked to the second electronic device and the second electronic device is configured to enable payment using the first payment account; and a representation of a second payment account together with status information of the second payment account, the status information indicating that the second payment account is linked to the first electronic device but not linked to the second electronic device.

[0036] A first electronic device, comprising: a display; one or more wireless communication components; one or more processors; a memory; and one or more programs stored in the memory, the one or more programs including instructions that, when executed by the one or more processors, cause the first electronic device to: display on the display a payment account user interface of a second electronic device associated with the first electronic device, wherein displaying the payment account user interface includes simultaneously displaying: a representation of a first payment account together with status information of the first payment account, the status information indicating that the first payment account is linked to the second electronic device and the second electronic device is configured to enable payments to be made using the first payment account; and a representation of a second payment account together with status information of the second payment account, the status information indicating that the second payment account is linked to the first electronic device but not linked to the second electronic device.

[0037] An electronic device, comprising: a touch-sensitive surface unit; a display unit; a wireless communication unit including one or more wireless communication components; and a processing unit coupled to the display unit, the touch-sensitive surface unit, and the wireless communication unit, the processing unit being configured to: receive an input for requesting to enable the device to conduct a payment transaction; in response to receiving the input for requesting to enable the device to conduct a payment transaction: enable the display on the display unit of a first visual indicator for identifying a first account; and enable the electronic device to participate in a transaction using the first account via the one or more wireless communication components; receive one or more swipe inputs in a first direction via the touch-sensitive surface unit; in response to receiving the one or more user swipe inputs: enable the display on the display unit of a second visual indicator for identifying a second account; and enable the electronic device to participate in a transaction using the second account via the one or more wireless communication components; and wherein the first visual indicator is different from the second visual indicator.

[0038] An electronic device, comprising: a display unit; a position sensor unit; and a processing unit coupled to the display unit and the position sensor unit, the processing unit being configured to: detect a current position using the position sensor unit; determine whether the current position is associated with a first account; based on a failure to determine that the current position is associated with an account other than a default payment account, enable the display on the display unit of a visual indication of the default payment account; based on determining that the current position is associated with the first account, enable the simultaneous display on the display unit of a visual indication of the default payment account and a visual indication of the first account; and wherein the default payment account and the first account are linked to the electronic device and the default payment account and the first account are different.

[0039] An electronic device, comprising: a display unit; a position sensor unit; and a processing unit coupled to the display unit and the position sensor unit, the processing unit being configured to: receive an input for requesting to enable the device to perform a payment transaction; and in response to receiving the input: use the position sensor unit to detect a current position; determine whether a set of one or more payment criteria is satisfied, wherein the set of one or more payment criteria includes criteria satisfied when the current position is associated with a first payment account; according to a determination that the set of one or more payment criteria is not satisfied, enable a display of a visual indication of a default payment account on the display unit, wherein the default payment account is different from the first payment account; and according to a determination that the set of one or more payment criteria is satisfied, enable a display of a visual indication of the first payment account on the display unit.

[0040] An electronic device, comprising: a display unit; a wireless communication unit including one or more wireless communication elements; and a processing unit coupled to the display unit and the wireless communication unit, the processing unit being configured to: receive an input for requesting to enable the device to perform a payment transaction; in response to receiving the input, enable a display of a payment indication on the display unit, the payment indication representing a plurality of payment accounts including a first payment account and a second payment account; receive a request for account information corresponding to a payment transaction via the one or more wireless communication elements; in response to receiving the request for the account information corresponding to the payment transaction: transmit the account information of the first payment account via the one or more wireless communication elements without transmitting the account information of the second payment account according to a determination that the payment criteria of the first payment account are satisfied; and transmit the account information of the second payment account via the one or more wireless communication elements without transmitting the account information of the first payment account according to a determination that the payment criteria of the second payment account are satisfied.

[0041] An electronic device, comprising: a display unit; a touch-sensitive surface unit; a wireless communication unit including one or more wireless communication elements; and a processing unit coupled to the display unit, the touch-sensitive surface unit configured to detect the intensity of contact, and the wireless communication unit, the processing unit being configured to: receive a first input; in response to receiving the first input: enable the display of a first user interface on the display unit, wherein the first user interface includes: a first visual indicator for identifying a payment card associated with a plurality of payment accounts, and a second visual indicator for identifying a first payment account among the plurality of payment accounts of the payment card; enable the electronic device to participate in a payment transaction using the first payment account via the one or more wireless communication elements; detect a first contact on the touch-sensitive surface unit; determine whether a characteristic intensity of the first contact is higher than an intensity threshold; and in accordance with determining that the characteristic intensity of the first contact is higher than the intensity threshold, enable the display of a second user interface on the display unit, wherein the second user interface enables selection between different payment accounts represented by the first visual indicator.

[0042] A first electronic device, comprising: a display unit; a wireless communication unit having one or more wireless communication elements; and a processing unit coupled to the display unit and the wireless communication unit, the processing unit being configured to: receive a first request to link a payment account associated with a payment card to the first electronic device; in response to receiving the first request, initiate a process for linking the payment account to the first electronic device; after successfully linking the payment account to the first electronic device, enable simultaneous display on the display unit of: an indication that the payment account has been successfully linked to the first electronic device; and an optional enabling representation for linking the payment account to a second electronic device different from the first electronic device; and receive activation of the optional enabling representation; and in response to receiving activation of the optional enabling representation, initiate a process for linking the payment account to the second electronic device.

[0043] A first electronic device, comprising: a display unit; a wireless communication unit including one or more wireless communication elements; and a processing unit coupled to the display unit and the wireless communication unit, the processing unit being configured to: enable, on the display unit, a display of a payment account user interface of a second electronic device associated with the first electronic device, wherein enabling the display of the payment account user interface includes enabling a simultaneous display of: a representation of a first payment account together with status information of the first payment account, the status information indicating that the first payment account is linked to the second electronic device and the second electronic device is configured to enable payments using the first payment account; and a representation of a second payment account together with status information of the second payment account, the status information indicating that the second payment account is linked to the first electronic device but not linked to the second electronic device.

[0044] A transient computer-readable storage medium, comprising one or more programs for execution by one or more processors of an electronic device having a display, a touch-sensitive surface, and one or more wireless communication elements, the one or more programs including instructions that, when executed by the one or more processors, cause the electronic device to: receive an input for requesting enabling the device for a payment transaction; in response to receiving the input for requesting enabling the device for a payment transaction: display, on the display, a first visual indicator for identifying a first account; and enable the electronic device to participate in a transaction using the first account via the one or more wireless communication elements; receive, via the touch-sensitive surface, one or more swipe inputs in a first direction; in response to receiving the one or more user swipe inputs: display, on the display, a second visual indicator for identifying a second account; and enable the electronic device to participate in a transaction using the second account via the one or more wireless communication elements; and wherein the first visual indicator is different from the second visual indicator.

[0045] A transient computer-readable storage medium, comprising one or more programs for execution by one or more processors of an electronic device having a display and a position sensor, the one or more programs including instructions that, when executed by the one or more processors, cause the electronic device to: detect a current position using the position sensor; determine whether the current position is associated with a first account; display a visual indication of a default payment account on the display based on a failure to determine that the current position is associated with an account other than the default payment account; display, on the display, a visual indication of the default payment account and a visual indication of the first account simultaneously based on a determination that the current position is associated with the first account; and wherein the default payment account and the first account are linked to the electronic device and the default payment account and the first account are different.

[0046] A transient computer-readable storage medium includes one or more programs for execution by one or more processors of an electronic device having a display and a position sensor. The one or more programs include instructions that, when executed by the one or more processors, cause the electronic device to: receive an input for requesting to enable the device to perform a payment transaction; and in response to receiving the input: use the position sensor to detect a current location; determine whether a set of one or more payment criteria is satisfied, where the set of one or more payment criteria includes criteria that are satisfied when the current location is associated with a first payment account; based on determining that the set of one or more payment criteria is not satisfied, display a visual indication of a default payment account on the display, where the default payment account is different from the first payment account; and based on determining that the set of one or more payment criteria is satisfied, display a visual indication of the first payment account on the display.

[0047] A transient computer-readable storage medium includes one or more programs for execution by one or more processors of an electronic device having a display and one or more wireless communication elements. The one or more programs include instructions that, when executed by the one or more processors, cause the electronic device to: receive an input for requesting to enable the device to perform a payment transaction; in response to receiving the input, display a payment indication on the display, the payment indication representing a plurality of payment accounts including a first payment account and a second payment account; receive, via the one or more wireless communication elements, a request for account information corresponding to a payment transaction; in response to receiving the request for account information corresponding to the payment transaction: based on determining that the payment criteria for the first payment account are satisfied, transmit the account information of the first payment account via the one or more wireless communication elements without transmitting the account information of the second payment account; and based on determining that the payment criteria for the second payment account are satisfied, transmit the account information of the second payment account via the one or more wireless communication elements without transmitting the account information of the first payment account.

[0048] A transient computer-readable storage medium includes one or more programs for execution by one or more processors of an electronic device having a display, a touch-sensitive surface configured to detect the intensity of contact, and one or more wireless communication elements. The one or more programs include instructions that, when executed by the one or more processors, cause the electronic device to: receive a first input; in response to receiving the first input: display a first user interface on the display, where the first user interface includes: a first visual indicator for identifying a payment card associated with a plurality of payment accounts, and a second visual indicator for identifying a first payment account among the plurality of payment accounts of the payment card; enable the electronic device to participate in a payment transaction using the first payment account via the one or more wireless communication elements; detect a first contact on the touch-sensitive surface; determine whether a characteristic intensity of the first contact is higher than an intensity threshold; and in accordance with determining that the characteristic intensity of the first contact is higher than the intensity threshold, display a second user interface on the display, where the second user interface enables selection between different payment accounts represented by the first visual indicator.

[0049] A transient computer-readable storage medium includes one or more programs for execution by one or more processors of a first electronic device having a display and one or more wireless communication elements. The one or more programs include instructions that, when executed by the one or more processors, cause the first electronic device to: receive a first request to link a payment account associated with a payment card to the first electronic device; in response to receiving the first request, initiate a process for linking the payment account to the first electronic device; after successfully linking the payment account to the first electronic device, simultaneously display on the display: an indication that the payment account has been successfully linked to the first electronic device; and an optional enabling representation for linking the payment account to a second electronic device different from the first electronic device; and receive an activation of the optional enabling representation; and in response to receiving the activation of the optional enabling representation, initiate a process for linking the payment account to the second electronic device.

[0050] A transient computer-readable storage medium includes one or more programs for execution by one or more processors of a first electronic device having a display and one or more wireless communication elements. The one or more programs include instructions that, when executed by the one or more processors, cause the first electronic device to: display on the display a payment account user interface of a second electronic device associated with the first electronic device, wherein displaying the payment account user interface includes simultaneously displaying: a representation of a first payment account together with status information of the first payment account, the status information indicating that the first payment account is linked to the second electronic device and the second electronic device is configured to enable payments using the first payment account; and a representation of a second payment account together with status information of the second payment account, the status information indicating that the second payment account is linked to the first electronic device but not linked to the second electronic device.

[0051] Accordingly, faster and more efficient methods and interfaces for linking accounts to the device, selecting accounts for transactions, and transmitting account information in transactions are provided for the device, thereby improving the effectiveness, efficiency, and user satisfaction of such devices. Such methods and interfaces may supplement or replace other methods for performing similar tasks.

[0052] Executable instructions for performing these functions are optionally included in a non-transient computer-readable storage medium or other computer program product configured for execution by one or more processors. Executable instructions for performing these functions are optionally included in a transient computer-readable storage medium or other computer program product configured for execution by one or more processors. BRIEF DESCRIPTION OF THE DRAWINGS

[0053] To better understand the various described embodiments, reference should be made to the following detailed description in conjunction with the following drawings, in which like reference numerals refer to corresponding parts throughout the drawings.

[0054] Figure 1A is a block diagram showing a portable multifunctional device having a touch-sensitive display in accordance with some embodiments.

[0055] Figure 1B is a block diagram showing exemplary components for event handling in accordance with some embodiments.

[0056] Figure 2 shows a portable multifunctional device having a touch screen in accordance with some embodiments.

[0057] Figure 3 is a block diagram of an exemplary multifunctional device having a display and a touch-sensitive surface in accordance with some embodiments.

[0058] Figure 4A Shows an exemplary user interface of an application menu on a portable multifunctional device according to some embodiments.

[0059] Figure 4B Shows an exemplary user interface of a multifunctional device having a touch-sensitive surface separate from a display according to some embodiments.

[0060] Figure 5A Shows a personal electronic device according to some embodiments.

[0061] Figure 5B Is a block diagram showing a personal electronic device according to some embodiments.

[0062] Figure 5C - 5D Shows exemplary components of a personal electronic device having a touch-sensitive display and an intensity sensor according to some embodiments.

[0063] Figure 5E - 5H Shows exemplary components and a user interface of a personal electronic device according to some embodiments.

[0064] Figure 5I Shows exemplary devices connected via one or more communication channels to complete a payment transaction according to some embodiments.

[0065] Figure 6A - 6G Shows exemplary techniques and an exemplary user interface for receiving a selection of an account according to some embodiments.

[0066] Figure 7 Is a flowchart showing a method for receiving a selection of an account according to some embodiments.

[0067] Figure 8A - 8D Shows exemplary techniques and an exemplary user interface for selecting an account according to some embodiments.

[0068] Figure 9 Is a flowchart showing a method for selecting an account according to some embodiments.

[0069] Figure 10A - 10E Shows exemplary techniques and an exemplary user interface for selecting an account according to some embodiments.

[0070] Figure 11 Is a flowchart showing a method for selecting an account according to some embodiments.

[0071] Figure 12A - 12D Shows exemplary techniques and an exemplary user interface for transmitting account information of an account according to some embodiments.

[0072] Figure 13 FIG. 1A is a flowchart showing a method for transmitting account information of an account according to some embodiments.

[0073] Figure 14A - 14E FIGS. 1B-1C illustrate exemplary techniques and exemplary user interfaces for receiving a selection of an account according to some embodiments.

[0074] Figure 15 FIG. 2 is a flowchart showing a method for receiving a selection of an account according to some embodiments.

[0075] Figure 16A to Figure 16G FIGS. 3A-3B illustrate exemplary methods and exemplary user interfaces for linking a payment account to one or more electronic devices according to some embodiments.

[0076] Figure 17 FIG. 4 is a flowchart showing a method for linking a payment account to one or more electronic devices according to some embodiments.

[0077] Figure 18A to Figure 18C FIGS. 5A-5B illustrate exemplary methods and exemplary user interfaces for linking a payment account to an electronic device according to some embodiments.

[0078] Figure 19 FIG. 6 is a flowchart showing a method for linking a payment account to an electronic device according to some embodiments.

[0079] Figure 20 - 26 FIG. 7 shows a functional block diagram according to some embodiments. DETAILED DESCRIPTION

[0080] The following description sets forth exemplary methods, parameters, etc. It should be recognized, however, that such description is not intended to limit the scope of the present disclosure but is provided as a description of exemplary embodiments.

[0081] There is a need for electronic devices to provide more efficient methods and interfaces for linking an account to the electronic device, selecting an account for a transaction, and transmitting account information in a transaction. Specifically, there is a need for efficient methods and interfaces for wearable devices such as smartwatches. Such techniques can reduce the cognitive burden on users accessing event notifications, thereby increasing productivity. Additionally, such techniques can reduce processor power and battery power that would otherwise be wasted on redundant user input.

[0082] Hereinafter, FIGS. 1A-1B, Figure 2 , Figure 3 , Figure 4A - 4B and Figure 5A - 5B provide a description of exemplary devices. Figure 6A - 6G FIGS. 1B-1C illustrate exemplary techniques and exemplary user interfaces for receiving a selection of an account. Figure 7is a flowchart showing a method for receiving a selection of an account. Figure 6A - 6G The user interface in Figure 7 is used to show Figure 8A - 8D the process in Figure 9 is a flowchart showing a method for selecting an account. Figure 8A - 8D The user interface in Figure 9 is used to show Figure 10A - 10E the process in Figure 11 is a flowchart showing a method for selecting an account according to some embodiments. Figure 10A - 10E The user interface in Figure 11 is used to show Figure 12A - 12D the process in Figure 13 is a flowchart showing a method for transmitting account information of an account according to some embodiments. Figure 12A - 12D The user interface in Figure 13 is used to show Figure 14A - 14E the process in Figure 15 is a flowchart showing a method for receiving a selection of an account. Figure 14A - 14E The user interface in Figure 15 is used to show Figure 16A - 16G the process in Figure 17 is a flowchart showing a method for linking a payment account to one or more electronic devices. Figure 16A - 16G The user interface in Figure 17 is used to show Figure 18A to Figure 18C the process in Figure 19 is a flowchart showing a method for linking a payment account to an electronic device according to some embodiments. Figure 18A - 18C The user interface in Figure 19 is used to show

[0083] Although the following description uses terms such as "first" and "second" to describe various elements, these elements should not be limited by the terms. These terms are only used to distinguish one element from another. For example, a first touch may be named a second touch and similarly a second touch may be named a first touch without departing from the scope of the various described embodiments. Both the first touch and the second touch are touches, but they are not the same touch.

[0084] The terms used in the description of the various embodiments herein are for the purpose of describing particular embodiments only and are not intended to be limiting. As used in the description of the various embodiments and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term "and / or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It will also be understood that the term "comprises", "comprising", "includes", and / or "including" when used in this specification specifies the presence of the stated feature, integer, step, operation, element, and / or component, but does not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0085] Depending on the context, the term "if" may be interpreted to mean "when" or "upon" or "in response to determining" or "in response to detecting". Similarly, depending on the context, the phrases "if determined..." or "if [stated condition or event] is detected" may be interpreted to mean "when determining..." or "in response to determining..." or "when [stated condition or event] is detected" or "in response to detecting [stated condition or event]".

[0086] Embodiments of electronic devices, user interfaces for such devices, and associated processes of using such devices are described herein. 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 the portable multifunctional device include, but are not limited to, those from Apple Inc (Cupertino, California) iPod and devices. Optionally, other portable electronic devices such as a laptop or tablet computer having a touch-sensitive surface (e.g., a touch screen display and / or a touchpad) are used. It should also be understood that in some embodiments, the device is not a portable communication device, but a desktop computer having a touch-sensitive surface (e.g., a touch screen display and / or a touchpad).

[0087] In the following discussion, an electronic device including a display and a touch-sensitive surface is described. 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.

[0088] The device can support multiple applications, such as one or more of the following applications: drawing applications, presentation applications, word processing applications, website creation applications, disk editing applications, spreadsheet applications, gaming applications, telephone applications, video conferencing applications, email applications, instant messaging applications, fitness support applications, photo management applications, digital camera applications, digital video camera applications, web browsing applications, digital music player applications, and / or digital video player applications.

[0089] The various applications executed on the device optionally use at least one shared physical user interface device such as a touch-sensitive surface. One or more functions of the touch-sensitive surface and the corresponding information displayed on the device are optionally adjusted and / or varied from one application to the next and / or within the respective application. Thus, the shared physical architecture of the device (such as the touch-sensitive surface) optionally supports the various applications with a user interface that is intuitive and clear to the user.

[0090] Now turn to an embodiment of a portable device having a touch-sensitive display. Figure 1A FIG. is a block diagram of a portable multifunctional device 100 having a touch-sensitive display system 112 in accordance with some embodiments. The touch-sensitive display 112 is sometimes called a "touch screen" for convenience and may sometimes be referred to as or called a "touch-sensitive display system". The device 100 includes a memory 102 (which optionally includes one or more computer-readable storage media), a memory controller 122, one or more processing units (CPUs) 120, a peripheral device interface 118, an RF circuit 108, an audio circuit 110, a speaker 111, a microphone 113, an input / output (I / O) subsystem 106, other input control devices 116, and an external port 124. The device 100 optionally includes one or more optical sensors 164. The device 100 optionally includes one or more contact intensity sensors 165 for detecting the intensity of a contact on the device 100 (e.g., a touch-sensitive surface such as the touch-sensitive display system 112 of the device 100). The device 100 optionally includes one or more tactile output generators 167 for generating tactile output on the device 100 (e.g., generating tactile output on a touch-sensitive surface such as the touch-sensitive display system 112 of the device 100 or the touchpad 355 of the device 300). These components optionally communicate via one or more communication buses or signal lines 103.

[0091] As used in this specification and the claims, the "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 to a surrogate 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 different values and more typically includes hundreds of different values (e.g., at least 256). The intensity of a contact is optionally determined (or measured) using a variety of methods and a variety of sensors or combinations of sensors. For example, one or more force sensors beneath or adjacent to the touch-sensitive surface are optionally used to measure the force at different points on the touch-sensitive surface. In some embodiments, force measurements from multiple force sensors are combined (e.g., a weighted average) to determine an estimated contact force. Similarly, the 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 size of the contact area detected on the touch-sensitive surface, the capacitance and / or change in capacitance of the touch-sensitive surface adjacent to the contact, and / or the resistance and / or change in resistance of the touch-sensitive surface adjacent to the contact are optionally used as surrogates for the force or pressure of a contact on the touch-sensitive surface. In some embodiments, the surrogate measurements of contact force or pressure are used directly to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the surrogate measurements). In some embodiments, the surrogate measurements of contact force or pressure are converted into an estimated force or pressure, and the estimated force or pressure is used to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure). Using the intensity of a contact as an attribute of user input allows a user to access additional device functions that would otherwise be inaccessible on a smaller device with limited footprint, the smaller device being used to (e.g., on a touch-sensitive display) display affordances and / or receive user input (e.g., via a touch-sensitive display, a touch-sensitive surface, or physical / mechanical controls such as knobs or buttons).

[0092] As used in this specification and the claims, the term "haptic output" refers to a physical displacement of the device relative to a previous position of the device detected by the user using the user's sense of touch, a physical displacement of a component of the device (e.g., a touch-sensitive surface) relative to another component of the device (e.g., the housing), or a displacement of the component relative to the center of mass of the device. For example, in the case of contact between the device or a component of the device and a surface of the user sensitive to touch (e.g., a finger, palm, or other part of the user's hand), the haptic output generated by the physical displacement will be interpreted by the user as a sense of touch that corresponds to a perceived change in the physical characteristics of the device or the component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or a touchpad) is optionally interpreted by the user as a "press click" or "release click" of a physical actuation button. In some cases, the user will feel a sense of touch, such as a "press click" or "release click", even when the physical actuation button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user's movement does not move. As another example, movement of a touch-sensitive surface will optionally be interpreted or sensed by the user as "roughness" of the touch-sensitive surface even when there is no change in the smoothness of the touch-sensitive surface. Although such interpretations of touch by the user will be limited by the user's individual sensory perception, there are many sensory perceptions of touch that are common to most users. Thus, when a haptic output is described as corresponding to a particular sensory perception of the user (e.g., "press click", "release click", "roughness"), unless otherwise stated, the generated haptic output corresponds to a physical displacement of the device or its component that will generate the sensory perception of a typical (or average) user.

[0093] It should be understood that device 100 is only one example of a portable multifunctional device, and device 100 optionally has more or fewer components than shown, optionally combines two or more components, or optionally has a different configuration or arrangement of these components. Figure 1A The various components shown 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.

[0094] Memory 102 optionally includes high-speed random access memory and also includes non-volatile memory, such as one or more disk storage devices, flash memory devices, or other non-volatile solid state memory devices. A memory controller 122 can control access to memory 102 by other components of device 100.

[0095] The peripheral device interface 118 can be used to couple input and output peripheral devices of the device to the CPU 120 and the memory 102. The one or more processors 120 run or execute various software programs and / or instruction sets stored in the memory 102 to perform various functions of the device 100 and process data. In some embodiments, the peripheral device interface 118, the CPU 120, and the memory controller 122 can be implemented on a single chip such as chip 104. In some other embodiments, they can be implemented on separate chips.

[0096] The RF (Radio Frequency) circuit 108 receives and transmits RF signals, which are also called electromagnetic signals. The RF circuit 108 converts electrical signals into electromagnetic signals / converts electromagnetic signals into electrical signals, and communicates with the communication network and other communication devices via electromagnetic signals. The RF circuit 108 optionally includes well-known circuits for performing these functions, including but not limited to antenna systems, RF transceivers, one or more amplifiers, tuners, one or more oscillators, digital signal processors, codec chip sets, subscriber identity module (SIM) cards, memories, and so on. The RF circuit 108 optionally communicates with the network and other devices via wireless communication, and the network is such as the Internet (also known as the World Wide Web (WWW)), intranet, and / or wireless networks (such as cellular phone networks, wireless local area networks (LANs), and / or metropolitan area networks (MANs)). The RF circuit 108 optionally includes well-known circuits for detecting the near field communication (NFC) field, such as detecting through short-range communication radio components. The wireless communication optionally uses any one of a variety of communication standards, protocols, and technologies, including but not limited to 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 (DC-HSPDA), 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, 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), WiMAX, email protocols (e.g., Internet Message Access Protocol (IMAP) and / or Post Office Protocol (POP)), instant messaging (e.g., Extensible 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 date of submission of this document.

[0097] The audio circuit 110, speaker 111, and microphone 113 provide an audio interface between the user and the device 100. The audio circuit 110 receives audio data from the peripheral interface 118, converts the audio data into an electrical signal, and transmits the electrical signal to the speaker 111. The speaker 111 converts the electrical signal into sound waves audible to humans. The audio circuit 110 also receives the electrical signal converted by the microphone 113 based on the sound waves. The audio circuit 110 converts the electrical signal into audio data and transmits the audio data to the peripheral interface 118 for processing. The audio data can be retrieved by the peripheral interface 118 from the memory 102 and / or the RF circuit 108 and / or be transmitted to the memory 102 and / or the RF circuit 108. In some embodiments, the audio circuit 110 also includes a headset interface (e.g., Figure 2 212 in

[0098] ). The headset interface provides an interface between the audio circuit 110 and a removable audio input / output peripheral device such as an output-only headset or a headset having both an output (e.g., a mono or stereo headset) and an input (e.g., a microphone). Figure 2 Figure 2 Figure 2 The I / O subsystem 106 couples input / output peripheral devices on the device 100 such as the touch screen 112 and other input control devices 116 to the peripheral interface 118. The I / O subsystem 106 optionally includes a display controller 156, an optical sensor controller 158, an intensity sensor controller 159, a haptic feedback controller 161, and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive electrical signals from the other input control devices 116 / send electrical signals to the other input control devices 116. The other input control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slide switches, joysticks, click wheels, and the like. In some alternative embodiments, the one or more input controllers 160 are optionally coupled to (or not coupled to) any of the following: a keyboard, an infrared port, a USB port, and a pointing device such as a mouse. One or more buttons (e.g.,

[0099] Quickly pressing the depress button can unlock the touch screen 112 or start the process of unlocking the device using gestures on the touch screen, as described in U.S. Patent Application 11 / 322,549, titled "Unlocking a Device by Performing Gestures on an Unlock Image," filed on December 23, 2005, and U.S. Patent No. 7,657,849. The above-mentioned U.S. patent applications are hereby incorporated by reference in their entirety. Pressing the depress button (e.g., 206) for a longer time can power on or power off the device 100. The user can customize the functions of one or more buttons. The touch screen 112 is used to implement virtual buttons or soft buttons and one or more soft keyboards.

[0100] The touch-sensitive display 112 provides an input interface and an output interface between the device and the user. The display controller 156 receives electrical signals from the touch screen 112 and / or sends electrical signals to the touch screen 112. The touch screen 112 displays visual output to the user. The visual output may include graphics, text, icons, videos, and any combination thereof (collectively referred to as "graphics"). In some embodiments, some or all of the visual output may correspond to user interface objects.

[0101] The touch screen 112 has a touch-sensitive surface, sensor, or sensor group that accepts input from the user based on tactile and / or haptic contact. The touch screen 112 and the display controller 156 (along with any associated modules and / or instruction sets in the memory 102) detect contact (and any movement or interruption of the contact) on the touch screen 112 and convert the detected contact into an interaction with a user interface object (e.g., one or more soft keys, icons, web pages, or images) displayed on the touch screen 112. In an exemplary embodiment, the point of contact between the touch screen 112 and the user corresponds to the user's finger.

[0102] The touch screen 112 can use LCD (liquid crystal display) technology, LPD (light-emitting polymer display) technology, or LED (light-emitting diode) technology, but in other embodiments, other display technologies may be used. The touch screen 112 and the display controller 156 can use any of a variety of touch-sensing technologies, now known or later developed, as well as other proximity sensor arrays or other elements for determining one or more points of contact with the touch screen 112 to detect contact and any movement or interruption thereof. The variety of touch-sensing technologies includes, but is not limited to, capacitive technology, resistive technology, infrared technology, and surface acoustic wave technology. In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as from Apple Inc. (Cupertino, California) the technology found in the iPod Touch.

[0103] The touch-sensitive display in some embodiments of the touch screen 112 may be similar to the multi-touch sensitive touchpad described in the following U.S. patents: 6,323,846 (Westerman et al.), 6,570,557 (Westerman et al.) and / or 6,677,932 (Westerman); and / or U.S. Patent Publication 2002 / 0015024A1, each of these patent applications being hereby incorporated by reference in its entirety. However, the touch screen 112 displays visual output from the device 100, while the touch-sensitive touchpad does not provide visual output.

[0104] The touch-sensitive display in some embodiments of the touch screen 112 may be described as in the following patent applications: (1) U.S. Patent Application No. 11 / 381,313, titled "Multipoint Touch Surface Controller," filed on May 2, 2006; (2) U.S. Patent Application No. 10 / 840,862, titled "Multipoint Touchscreen," filed on May 6, 2004; (3) U.S. Patent Application No. 10 / 903,964, titled "Gestures For TouchSensitive Input Devices," filed on July 30, 2004; (4) U.S. Patent Application No. 11 / 048,264, titled "Gestures For Touch Sensitive Input Devices," filed on January 31, 2005; (5) U.S. Patent Application No. 11 / 038,590, titled "Mode-Based Graphical User Interfaces For TouchSensitive Input Devices," filed on January 18, 2005; (6) U.S. Patent Application No. 11 / 228,758, titled "Virtual Input Device Placement On A Touch Screen User Interface," filed on September 16, 2005; (7) U.S. Patent Application No. 11 / 228,700, titled "Operation Of A Computer WithATouch Screen Interface," filed on September 16, 2005; (8) U.S. Patent Application No. 11 / 228,737, titled "Activating Virtual Keys Of A Touch-Screen Virtual Keyboard," filed on September 16, 2005; and (9) U.S. Patent Application No. 11 / 367,749, titled "Multi-Functional Hand-HeldDevice," filed on March 3, 2006. The entire text of all these patent applications is incorporated herein by reference.

[0105] The touch screen 112 may have a video resolution of more than 100 dpi. In some embodiments, the touch screen has a video resolution of about 160 dpi. A user may use any suitable object or attachment such as a stylus, a finger, etc. to contact the touch screen 112. In some embodiments, the user interface is designed to work primarily with finger-based contacts and gestures, which may not be as precise as stylus-based input due to the larger contact area of the finger on the touch screen. In some embodiments, the device translates the finger-based rough input into an accurate pointer / cursor position or command for performing the action desired by the user.

[0106] In some embodiments, in addition to the touch screen, the device 100 may include a touch pad (not shown) for activating or deactivating specific functions. In some embodiments, the touch pad is a touch-sensitive area of the device that is different from the touch screen and does not display a visual output. The touch pad may be a touch-sensitive surface separate from the touch screen 112 or an extension of the touch-sensitive surface formed by the touch screen.

[0107] The device 100 also includes a power system 162 for powering various components. The power system 162 may include a power management system, one or more power sources (e.g., a battery, alternating current (AC)), a recharge system, a power failure detection circuit, a power converter or inverter, a power status indicator (e.g., a light-emitting diode (LED)), and any other components associated with the generation, management, and distribution of power in a portable device.

[0108] The device 100 may also include one or more optical sensors 164. Figure 1A An optical sensor coupled to the optical sensor controller 158 in the I / O subsystem 106 is shown. The optical sensor 164 may include a charge-coupled device (CCD) or a complementary metal-oxide semiconductor (CMOS) phototransistor. The optical sensor 164 receives light projected through one or more lenses from the environment and converts the light into data representing an image. In combination with the imaging module 143 (also referred to as a camera module), the optical sensor 164 may capture a still image or video. In some embodiments, the optical sensor is located on the rear of the device 100 opposite the touch screen display 112 on the front of the device, such that the touch screen display may be used as a viewfinder for still image and / or video image capture. In some embodiments, the optical sensor is located on the front of the device such that an image of the user may be obtained while the user views other video conference participants on the touch screen display for video conferencing. In some embodiments, the position of the optical sensor 164 may be changed by the user (e.g., by rotating the lens and sensor in the device housing) such that a single optical sensor 164 may be used with the touch screen display for both video conferencing and still image and / or video image capture.

[0109] Device 100 optionally further includes one or more contact intensity sensors 165. Figure 1A A contact intensity sensor coupled to an intensity sensor controller 159 in the I / O subsystem 106 is shown. The contact intensity sensor 165 optionally includes one or more piezoresistive strain gauges, capacitive force sensors, electro-mechanical force sensors, piezoelectric force sensors, optical force sensors, capacitive touch-sensitive surfaces, or other intensity sensors (e.g., sensors for measuring the force (or pressure) of a contact on a touch-sensitive surface). The contact intensity sensor 165 receives contact intensity information (e.g., pressure information or a surrogate for pressure information) from the environment. In some embodiments, at least one contact intensity sensor is juxtaposed or adjacent to a touch-sensitive surface (e.g., the touch-sensitive display system 112). In some embodiments, at least one contact intensity sensor is located on the rear of the device 100 opposite the touch screen display 112 located on the front of the device 100.

[0110] Device 100 may also include one or more proximity sensors 166. Figure 1A A proximity sensor 166 coupled to the peripheral device interface 118 is shown. Alternatively, the proximity sensor 166 may be coupled to an input controller 160 in the I / O subsystem 106. The proximity sensor 166 may operate as described in the following U.S. patent applications: 11 / 241,839, titled "Proximity Detector In Handheld Device"; 11 / 240,788, titled "Proximity DetectorIn Handheld Device"; 11 / 620,702, titled "Using Ambient Light Sensor To AugmentProximity Sensor Output"; 11 / 586,862, titled "Automated Response To And SensingOf User Activity In Portable Devices"; and 11 / 638,251, titled "Methods And SystemsFor Automatic Configuration Of Peripherals", which U.S. patent applications are hereby incorporated by reference in their entirety. In some embodiments, when the multifunctional device is placed near the user's ear (e.g., when the user is making a phone call), the proximity sensor turns off and disables the touch screen 112.

[0111] Device 100 optionally further includes one or more haptic output generators 167. Figure 1AIllustrated is a haptic output generator coupled to a haptic feedback controller 161 in the I / O subsystem 106. The haptic output generator 167 optionally includes one or more electroacoustic devices such as speakers or other audio components; and / or electromechanical devices for converting energy into linear motion such as motors, solenoids, electroactive polymers, piezoelectric actuators, electrostatic actuators, or other haptic output generating components (e.g., components for converting an electrical signal into a haptic output on the device). The contact intensity sensor 165 receives haptic feedback generation instructions from the haptic feedback module 133 and generates a haptic output on the device 100 that can be sensed by a user of the device 100. In some embodiments, at least one haptic output generator is juxtaposed or adjacent to a touch-sensitive surface (e.g., the touch-sensitive display system 112), and optionally generates a haptic output by moving the touch-sensitive surface vertically (e.g., in / out of the surface of the device 100) or laterally (e.g., backward and forward in the same plane as the surface of the device 100). In some embodiments, at least one haptic output generator sensor is located on the rear of the device 100 opposite to the touch screen display 112 located on the front of the device 100.

[0112] The device 100 may also include one or more accelerometers 168. Figure 1A Illustrated is an accelerometer 168 coupled to the peripheral device interface 118. As an alternative, the accelerometer 168 may be coupled to the input controller 160 in the I / O subsystem 106. The accelerometer 168 may operate as described in the following U.S. Patent Publications: 20050190059, titled "Acceleration-based Theft Detection System for Portable Electronic Devices" and 20060017692, titled "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 in a portrait view or a landscape view on the touch screen display based on an analysis of data received from the one or more accelerometers. The device 100 optionally includes a magnetometer (not shown) and a GPS (or GLONASS or other global navigation system) receiver (not shown) in addition to the one or more accelerometers 168 for obtaining information about the location and orientation (e.g., portrait or landscape) of the device 100.

[0113] In some embodiments, the software components stored in the memory 102 include an operating system 126, a communication module (or set of instructions) 128, a touch / motion module (or set of instructions) 130, a graphics module (or set of instructions) 132, a text input module (or set of instructions) 134, a Global Positioning System (GPS) module (or set of instructions) 135, and application programs (or sets of instructions) 136. Additionally, in some embodiments, the memory 102 ( Figure 1A ) or 370 ( Figure 3 ) stores a device / global internal state 157, as Figure 1A and Figure 3 shown. The device / global internal state 157 includes one or more of the following: an active application state that indicates which applications, if any, are currently active; a display state that indicates what applications, views, or other information occupy the various regions of the touch screen display 112; a sensor state that includes information obtained from the various sensors of the device and the input control device 116; and location information regarding the location and / or orientation of the device.

[0114] The 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 for controlling and managing general system tasks (e.g., memory management, storage device control, power management, etc.) and facilitates communication between the various hardware components and software components.

[0115] The communication 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 the RF circuit 108 and / or the external ports 124. The external ports 124 (e.g., Universal Serial Bus (USB), FireWire, etc.) are adapted to be directly coupled to other devices or indirectly coupled via a network (e.g., the Internet, a wireless LAN, etc.). In some embodiments, the external port is the same as or similar to and / or compatible with the 30-pin connector used on (a trademark of Apple Inc.) devices and / or a multi-pin (e.g., 30-pin) connector.

[0116] The contact / motion module 130 optionally detects contact with the touch screen 112 (in conjunction with the display controller 156) and other touch-sensitive devices (e.g., a touchpad or a physical click wheel). The contact / motion module 130 includes various software components for performing various operations related to contact detection, such as determining whether contact has occurred (e.g., detecting a finger press 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 movement of the contact and tracking the movement on the touch-sensitive surface (e.g., detecting one or more finger drag events), and determining whether the contact has stopped (e.g., detecting a finger lift event or contact break). The contact / motion module 130 receives contact data from the touch-sensitive surface. Determining the movement of the contact point optionally includes determining the rate (magnitude), velocity (magnitude and direction), and / or acceleration (change in magnitude and / or direction) of the contact point, the movement of which is represented by a series of contact data. These operations are optionally applied to single-point contact (e.g., single-finger contact) or multi-point simultaneous contact (e.g., "multi-touch" / multi-finger contact). In some embodiments, the contact / motion module 130 and the display controller 156 detect contact on the touchpad.

[0117] In some embodiments, the contact / motion module 130 uses a set of one or more intensity thresholds to determine whether an operation has been performed by the user (e.g., determining whether the user has "clicked" on an icon). In some embodiments, at least a subset of the intensity thresholds is determined according to software parameters (e.g., the intensity thresholds are not determined by the activation threshold of a particular physical actuator and can be adjusted without changing the physical hardware of the device 100). For example, without changing the touchpad or touch screen display hardware, the mouse "click" threshold of the touchpad or touch screen can be set to any one of a wide range of predefined thresholds. Additionally, in some implementations, software settings are provided to the user of the device for adjusting one or more of the intensity thresholds in a set of intensity thresholds (e.g., by adjusting individual intensity thresholds and / or by adjusting multiple intensity thresholds at once using a system-level click on an "intensity" parameter).

[0118] The contact / motion module 130 optionally detects gesture inputs from the user. Different gestures on the touch-sensitive surface have different contact patterns (e.g., different movements, timings, and / or intensities of the detected contact). Thus, gestures are optionally detected by detecting a particular contact pattern. For example, detecting a finger tap gesture includes detecting a finger press event and then detecting a finger lift (lift-off) event at the same location (or substantially the same location) as the finger press event (e.g., at the location of an icon). As another example, detecting a finger swipe gesture on the touch-sensitive surface includes detecting a finger press event, then detecting one or more finger drag events, and subsequently detecting a finger lift (lift-off) event.

[0119] The graphics module 132 includes various known software components for presenting and displaying graphics on the touchscreen 112 or other display, including components for altering the visual impact of the displayed graphics (e.g., brightness, transparency, saturation, contrast, or other visual characteristics). As used herein, the term "graphics" includes any object that can be displayed to a user, including, without limitation, text, web pages, icons (such as user interface objects including soft keys), digital images, videos, animations, etc.

[0120] In some embodiments, the graphics module 132 stores data representing graphics to be used. Each graphic is optionally assigned a corresponding code. The graphics module 132 receives one or more codes for specifying the graphics to be displayed from an application, etc., and also receives coordinate data and other graphic attribute data as necessary, and then generates screen image data for output to the display controller 156.

[0121] The haptic feedback module 133 includes various software components for generating instructions that are used by one or more haptic output generators 167 to generate haptic output at one or more locations on the device 100 in response to user interaction with the device 100.

[0122] The text input module 134, which can be a component of the graphics module 132, provides a soft keyboard for entering text in a variety of applications (e.g., contacts 137, email 140, IM 141, browser 147, and any other application that requires text input).

[0123] The GPS module 135 determines the location of the device and provides such information for use in various applications (e.g., provided to the phone 138 for location-based dialing; provided to the camera 143 as picture / video metadata; and provided to applications that provide location-based services such as weather widgets, local yellow pages widgets, and map / navigation widgets).

[0124] The application 136 can include the following modules (or instruction sets) or subsets or supersets thereof:

[0125] · The contacts module 137 (sometimes referred to as an address book or contact list);

[0126] · The phone module 138;

[0127] · The video conferencing module 139;

[0128] · The email client module 140;

[0129] · The instant messaging (IM) module 141;

[0130] · Fitness support module 142;

[0131] · Camera module 143 for still images and / or video images;

[0132] · Image management module 144;

[0133] · Video player module;

[0134] · Music player module;

[0135] · Browser module 147;

[0136] · Calendar module 148;

[0137] · Desktop widget module 149, which may include one or more of the following: weather desktop widget 149-1, stock market desktop widget 149-2, calculator desktop widget 149-3, alarm clock desktop widget 149-4, dictionary desktop widget 149-5, and other desktop widgets obtained by the user and user-created desktop widgets 149-6;

[0138] · Desktop widget creator module 150 for forming user-created desktop widgets 149-6;

[0139] · Search module 151;

[0140] · Video and music player module 152, which combines the video player module and the music player module;

[0141] · Notepad module 153;

[0142] · Map module 154; and / or

[0143] · Online video module 155.

[0144] Examples of other applications 136 that can be stored in the memory 102 include other word processing applications, other image editing applications, drawing applications, presentation applications, JAVA-supported applications, encryption, digital rights management, speech recognition, and speech reproduction.

[0145] In conjunction with the touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, the contacts module 137 can be used to manage an address book or contact list (e.g., the application internal state 192 of the contacts module 137 stored in the memory 102 or memory 370), including: adding one or more names to the address book; deleting one or more names from the address book; associating one or more phone numbers, one or more email addresses, one or more physical addresses, or other information with a name; associating an image with a name; categorizing and classifying names; providing a phone number or email address to initiate and / or facilitate communication via the phone 138, video conferencing module 139, email 140, or IM 141; and so on.

[0146] In conjunction with the RF circuit 108, audio circuit 110, speaker 111, microphone 113, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, the phone module 138 can be used to input a character sequence corresponding to a phone number, access one or more phone numbers in the contacts module 137, modify an entered phone number, dial the corresponding phone number, conduct a session, and disconnect or hang up when the session is complete. As described above, wireless communication can use any of a plurality of communication standards, protocols, and technologies.

[0147] In conjunction with the RF circuit 108, audio circuit 110, speaker 111, microphone 113, touch screen 112, display controller 156, optical sensor 164, optical sensor controller 158, contact / motion module 130, graphics module 132, text input module 134, contacts module 137, and phone module 138, the video conferencing module 139 includes executable instructions to initiate, conduct, and terminate a video conference between the user and one or more other participants according to user instructions.

[0148] In conjunction with the RF circuit 108, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, the email client module 140 includes executable instructions to create, send, receive, and manage emails in response to user instructions. In conjunction with the image management module 144, the email client module 140 makes it very easy to create and send emails with static or video images captured by the camera module 143.

[0149] In combination with the RF circuit 108, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, the instant messaging module 141 includes executable instructions for the following operations: inputting a character sequence corresponding to an instant message, modifying a previously input character, transmitting the corresponding instant message (e.g., using the Short Message Service (SMS) or Multimedia Messaging Service (MMS) protocol for phone-based instant messaging or using XMPP, SIMPLE, or IMPS for Internet-based instant messaging), receiving instant messages, and viewing received instant messages. In some embodiments, the transmitted and / or received instant messages may include graphics, photos, audio files, video files, and / or other attachments supported in MMS and / or Enhanced Messaging Service (EMS). As used herein, "instant message" refers to both phone-based messages (e.g., messages transmitted using SMS or MMS) and Internet-based messages (e.g., messages transmitted using XMPP, SIMPLE, or IMPS).

[0150] In combination with the RF circuit 108, touch screen 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 fitness support module 142 includes executable instructions for the following operations: creating a fitness (e.g., with time, distance, and / or calorie burn goals); communicating with a fitness sensor (mobile device); receiving fitness sensor data; calibrating the sensors for monitoring fitness; selecting and playing fitness music; and displaying, storing, and transmitting fitness data.

[0151] In combination with the touch screen 112, display controller 156, one or more optical sensors 164, optical sensor controller 158, contact / motion module 130, graphics module 132, and image management module 144, the camera module 143 includes executable instructions for the following operations: capturing still images or videos (including video streams) and storing them in the memory 102, modifying the characteristics of still images or videos, or deleting still images or videos from the memory 102.

[0152] In combination with the touch screen 112, display controller 156, contact / motion module 130, graphics module 132, text input module 134, and camera module 143, the image management module 144 includes executable instructions for arranging, modifying (e.g., editing), or otherwise manipulating, tagging, deleting, presenting (e.g., in a digital slide show or album), and storing still images and / or video images.

[0153] In combination with RF circuit 108, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, browser module 147 includes executable instructions for browsing the Internet in accordance with user instructions (including searching, linking to, receiving, and displaying web pages or portions thereof, as well as linking to attachments and other files of web pages).

[0154] In combination with RF circuitry 108, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, text input module 134, email client module 140, and browser module 147, calendar module 148 includes executable instructions for creating, displaying, modifying, and storing calendars and data associated with the calendars (e.g., calendar entries, to-do items, etc.) in accordance with user instructions.

[0155] In combination with RF circuitry 108, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, text input module 134, and browser module 147, desktop widget module 149 is a miniature application that can be downloaded and used by the user (e.g., weather desktop widget 149-1, stock market desktop widget 149-2, calculator desktop widget 149-3, alarm clock desktop widget 149-4, and dictionary desktop widget 149-5) or a miniature application created by the user (e.g., user-created desktop widget 149-6). In some embodiments, the desktop widget includes HTML (Hypertext Markup Language) files, CSS (Cascading Style Sheets) files, and JavaScript files. In some embodiments, the desktop widget includes XML (Extensible Markup Language) files and JavaScript files (e.g., Yahoo! desktop widget).

[0156] In combination with RF circuit 108, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, text input module 134, and browser module 147, desktop widget creator module 150 can be used by the user to create desktop widgets (e.g., transfer a user-specified portion of a web page into a desktop widget).

[0157] In combination with touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, search module 151 includes executable instructions for searching for text, music, sound, images, video, and / or other files in memory 102 that match one or more search criteria (e.g., one or more user-specified search terms) in accordance with user instructions.

[0158] In combination with touch screen 112, display controller 156, contact / motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, and browser module 147, video and music player module 152 includes executable instructions that allow a user to download and play back recorded music and other sound files stored in one or more file formats, such as MP3 or AAC files, and executable instructions for displaying, presenting, or otherwise playing back video (e.g., on touch screen 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.).

[0159] In combination with touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, notepad module 153 includes executable instructions to create and manage notepads, to-do lists, etc. according to user instructions.

[0160] In combination with RF circuitry 108, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147, map module 154 can be used to receive, display, modify, and store maps and data associated with the maps (e.g., driving directions, data related to stores and other points of interest at or near a particular location, and other location-based data) according to user instructions.

[0161] In combination with the touch screen 112, display controller 156, contact / motion module 130, graphics module 132, audio circuit 110, speaker 111, RF circuit 108, text input module 134, e-mail client module 140, and browser module 147, the online video module 155 includes instructions that allow a user to access, browse, receive (e.g., via streaming and / or downloading), play back (e.g., on the touch screen or on an external display connected via external port 124), send an e-mail with a link to a particular online video, and otherwise manage online videos in one or more file formats such as H.264. In some embodiments, the instant messaging module 141 rather than the e-mail client module 140 is used to send a link to a particular online video. Additional descriptions of the online video application can be found in U.S. Provisional Patent Application No. 60 / 936,562, filed Jun. 20, 2007, and titled "Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos," and U.S. Patent Application No. 11 / 968,067, filed Dec. 31, 2007, and titled "Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos," the contents of both of which are hereby incorporated by reference in their entireties.

[0162] Each of the above modules and applications corresponds to a set of executable instructions for performing one or more of the above functions and the methods described in this patent application (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 separate software programs, processes, or modules, and thus in various embodiments, various subsets of these modules may be combined or otherwise rearranged. For example, a video player module may be combined with a music player module into a single module (e.g., Figure 1A the video and music player module 152 in ). In some embodiments, the memory 102 may store a subset of the above modules and data structures. In addition, the memory 102 may store additional modules and data structures not described above.

[0163] In some embodiments, device 100 is a device that uniquely performs operations of a predefined set of functions on the device via a touch screen and / or a touchpad. By using the touch screen and / or the touchpad as the primary input control device for the operation of device 100, the number of physical input control devices (such as push buttons, dials, etc.) on device 100 can be reduced.

[0164] The predefined set of functions uniquely performed via the touch screen and / or the touchpad optionally includes navigating between user interfaces. In some embodiments, the touchpad, when touched by the user, navigates device 100 from any user interface displayed on device 100 to the main menu, home menu, or root menu. In such embodiments, the touchpad is used to implement a "menu button". In some other embodiments, the menu button is a physical push button or other physical input control device rather than the touchpad.

[0165] Figure 1B is a block diagram showing exemplary components for event handling according to some embodiments. In some embodiments, memory 102 ( Figure 1A ) or memory 370 ( Figure 3 ) includes an event classifier 170 (e.g., in operating system 126) and corresponding application 136-1 (e.g., any one of the foregoing applications 137-151, 155, 380-390).

[0166] Event classifier 170 receives event information and determines the application 136-1 to which the event information is to be delivered and the application view 191 of application 136-1. Event classifier 170 includes an event monitor 171 and an event dispatcher module 174. In some embodiments, application 136-1 includes an application internal state 192 that indicates one or more current application views displayed on the touch-sensitive display 112 when the application is active or executing. In some embodiments, the device / global internal state 157 is used by event classifier 170 to determine which application(s) is / are currently active, and the application internal state 192 is used by event classifier 170 to determine the application view 191 to which the event information is to be delivered.

[0167] In some embodiments, the application internal state 192 includes additional information such as one or more of the following: recovery information to be used when the application 136-1 resumes execution, user interface state information indicating information being displayed by or ready for display by the application 136-1, a state queue for enabling a user to return to a previous state or view of the application 136-1, and a repeat / undo queue of previous actions taken by the user.

[0168] The event monitor 171 receives event information from the peripheral device interface 118. The event information includes information about sub-events (e.g., a user touch on the touch-sensitive display 112 as part of a multi-touch gesture). The peripheral device interface 118 transmits information that it receives from the I / O subsystem 106 or sensors such as the proximity sensor 166, one or more accelerometers 168, and / or the microphone 113 (via the audio circuit 110). The information received by the peripheral device interface 118 from the I / O subsystem 106 includes information from the touch-sensitive display 112 or a touch-sensitive surface.

[0169] In some embodiments, the event monitor 171 sends requests to the peripheral device interface 118 at predetermined intervals. In response, the peripheral device interface 118 transmits event information. In other embodiments, the peripheral device interface 118 transmits event information only when there are significant events (e.g., an input received above a predetermined noise threshold and / or an input received for longer than a predetermined duration).

[0170] In some embodiments, the event classifier 170 further includes a hit view determination module 172 and / or an active event recognizer determination module 173.

[0171] When the touch-sensitive display 112 displays more than one view, the hit view determination module 172 provides a software process for determining where within one or more views a sub-event has occurred. Views are composed of controls and other elements that a user can see on the display.

[0172] Another aspect of the user interface associated with an application is a set of views, sometimes also referred to herein as application views or user interface windows, in which information is displayed and touch-based gestures occur. The application view (of the corresponding application) in which a touch is detected may correspond to a programmatic hierarchical structure of the application or a programmatic level within a view hierarchy. For example, the lowest-level view in which a touch is detected is optionally called the hit view, and the set of events identified as correct inputs is at least partially determined based on the hit view of the initial touch that starts the touch-based gesture.

[0173] The 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 hierarchical structure, the hit view determination module 172 identifies the hit view as the lowest view in the hierarchical structure that should handle the sub-event. In most cases, the hit view is the lowest-level view in which the initiating sub-event (e.g., the first sub-event in a sequence of sub-events that form an event or potential event) occurs. Once the hit view is identified by the hit view determination module 172, the hit view typically receives all sub-events related to the same touch or input source for which it was identified as the hit view.

[0174] The active event recognizer determination module 173 determines which view or views within the view hierarchy should receive a particular sequence of sub-events. In some embodiments, the active event recognizer determination module 173 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, the active event recognizer determination module 173 determines that all views that include the physical location of the sub-event are actively participating views, and thus 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 an area associated with a particular view, higher views in the hierarchy will still remain as actively participating views.

[0175] The event dispatcher module 174 distributes event information to event recognizers (e.g., event recognizer 180). In embodiments that include the active event recognizer determination module 173, the event dispatcher module 174 delivers the event information to the event recognizer determined by the active event recognizer determination module 173. In some embodiments, the event dispatcher module 174 stores the event information in an event queue, which is retrieved by the corresponding event receiver 182.

[0176] In some embodiments, the operating system 126 includes the event classifier 170. As an alternative, the application 136-1 includes the event classifier 170. In another embodiment, the event classifier 170 is a separate module, or is part of another module (such as the contact / motion module 130) stored in the memory 102.

[0177] In some embodiments, application 136-1 includes a plurality of event handlers 190 and one or more application views 191, where each application view includes instructions for handling touch events that occur within a corresponding view of the application's user interface. Each application view 191 of application 136-1 includes one or more event recognizers 180. Typically, a corresponding application view 191 includes a plurality of event recognizers 180. In other embodiments, one or more of the event recognizers 180 of an application view are part of an independent module, such as a user interface toolkit (not shown) or a higher-level object from which application 136-1 inherits methods and other properties. In some embodiments, a corresponding event handler 190 includes one or more of the following: a data updater 176, an object updater 177, a GUI updater 178, and / or event data 179 received from event classifier 170. An event handler 190 may utilize or call a data updater 176, an object updater 177, or a GUI updater 178 to update the internal state 192 of the application. As an alternative, one or more of the application views 191 include one or more corresponding event handlers 190. Additionally, in some embodiments, one or more of the data updater 176, object updater 177, and GUI updater 178 are included within a corresponding application view 191.

[0178] A corresponding event recognizer 180 receives event information (e.g., event data 179) from event classifier 170 and identifies an event 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 at least a subset of the following: metadata 183, and event delivery instructions 188 (which may include sub-event delivery instructions).

[0179] Event receiver 182 receives event information from event classifier 170. The event information includes information about a sub-event, such as a touch or a touch movement. 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 the movement of a touch, the event information may also include the rate and direction of the sub-event. In some embodiments, the event includes the device rotating from one orientation to another (e.g., from a portrait orientation to a landscape orientation, or vice versa), and the event information includes corresponding information about the current orientation of the device (also referred to as the device's attitude).

[0180] The event comparator 184 compares the event information with predefined event or sub - event definitions and determines an event or sub - event based on that comparison, or determines or updates the status of an event or sub - event. In some embodiments, the event comparator 184 includes an event definition 186. The event definition 186 contains the definitions of events (e.g., a predefined sequence of sub - events), such as event 1 (187 - 1), event 2 (187 - 2), and other events. In some embodiments, the sub - events in event 187 include, for example, touch start, touch end, touch move, touch cancel, and multi - touch. In one example, the definition of event 1 (187 - 1) is a double - tap on a displayed object. For example, a double - tap includes a first touch (touch start) of a predetermined duration on the displayed object, a first lift (touch end) of a predetermined duration, a second touch (touch start) of a predetermined duration on the displayed object, and a second lift (touch end) of a predetermined duration. In another example, the definition of event 2 (187 - 2) is a drag on a displayed object. For example, a drag includes a touch (or contact) of a predetermined duration on the displayed object, movement of the touch on the touch - sensitive display 112, and a lift of the touch (touch end). In some embodiments, the event also includes information for one or more associated event handlers 190.

[0181] In some embodiments, the event definition 187 includes the definition of an event for a corresponding user interface object. In some embodiments, the event comparator 184 performs a hit test to determine which user interface object is associated with a sub - event. For example, in an application view where three user interface objects are displayed on the touch display 112, when a touch is detected on the touch - sensitive display 112, the 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 of the displayed objects is associated with a corresponding event handler 190, the event comparator uses the result of the hit test to determine which event handler 190 should be activated. For example, the event comparator 184 selects the event handler associated with the sub - event and the object that triggered the hit test.

[0182] In some embodiments, the definition of the corresponding event (187) also includes a delay action that delays the delivery of the event information until it has been determined whether the sub - event sequence does or does not correspond to the event type of the event recognizer.

[0183] When the corresponding event recognizer 180 determines that the sub - event sequence does not match any event in the event definition 186, the corresponding event recognizer 180 enters an event - impossible, event - failed, or event - ended state, after which subsequent sub - events of the touch - based gesture are ignored. In such a case, other event recognizers (if any) that remain active for the hit view continue to track and process sub - events of the ongoing touch - based gesture.

[0184] In some embodiments, the corresponding event recognizer 180 includes metadata 183 having configurable attributes, flags, and / or lists for indicating how the event delivery system should perform sub - event delivery to the actively participating event recognizers. In some embodiments, the metadata 183 includes configurable attributes, flags, and / or lists for indicating how event recognizers interact or can interact with each other. In some embodiments, the metadata 183 includes configurable attributes, flags, and / or lists for indicating whether sub - events are delivered to different levels in the view or the programmatic hierarchy.

[0185] In some embodiments, when one or more specific sub - events of an event are recognized, the corresponding event recognizer 180 activates the event handler 190 associated with the event. In some embodiments, the corresponding event recognizer 180 delivers event information associated with the event to the event handler 190. Activating the event handler 190 is different from sending (and deferring sending) sub - events to the corresponding hit view. In some embodiments, the event recognizer 180 throws a token associated with the recognized event, and the event handler 190 associated with the token retrieves the token and executes a predefined process.

[0186] In some embodiments, the event delivery instruction 188 includes a sub - event delivery instruction that delivers event information about the sub - event without activating the event handler. Instead, the sub - event delivery instruction delivers the event information to the event handler associated with the sub - event string or to the actively participating view. The event handler associated with the sub - event sequence or with the actively participating view receives the event information and executes a predetermined process.

[0187] In some embodiments, the data updater 176 creates and updates data used in the application 136-1. For example, the data updater 176 updates the phone numbers used in the contact module 137 or stores the video files used in the video player module. In some embodiments, the object updater 177 creates and updates objects used in the application 136-1. For example, the object updater 177 creates new user interface objects or updates the positions of user interface objects. The GUI updater 178 updates the GUI. For example, the GUI updater 178 prepares display information and sends it to the graphics module 132 for display on the touch-sensitive display.

[0188] In some embodiments, one or more event handlers 190 include the data updater 176, the object updater 177, and the GUI updater 178 or have access to the data updater 176, the object updater 177, and the GUI updater 178. In some embodiments, the data updater 176, the object updater 177, and the GUI updater 178 are included in a single module of the corresponding application 136-1 or application view 191. In other embodiments, they are included in two or more software modules.

[0189] It should be understood that the above discussion regarding event handling of user touches on the touch-sensitive display also applies to other forms of user input for operating the multifunctional device 100 using an input device, and not all user input is initiated on the touchscreen. For example, mouse movement and mouse button presses optionally combined with single or multiple keyboard presses or holds; contact movement on a touchpad, such as tapping, dragging, scrolling, etc.; stylus input; movement of the device; verbal instructions; detected eye movement; biometric input; and / or any combination of inputs corresponding to sub-events for defining an event to be recognized.

[0190] Figure 2FIG. 0 shows a portable multifunctional device 100 having a touch screen 112 according to some embodiments. The touch screen optionally displays one or more graphics within a user interface (UI) 200. In this and other embodiments described hereinafter, a user is able to select one or more of these graphics by making gestures on the graphics, such as by using one or more fingers 202 (not drawn to scale in the figures) or by using one or more styli 203 (not drawn to scale in the figures). In some embodiments, selection of one or more graphics occurs when the user breaks contact with the one or more graphics. In some embodiments, gestures optionally include one or more taps, one or more swipes (from left to right, from right to left, up, and / or down), and / or rolling of a finger that has made contact with the device 100 (from right to left, from left to right, up, and / or down). In some implementations or in some cases, inadvertently contacting a graphic does not select the graphic. For example, when the gesture corresponding to selection is a tap, a swipe gesture that sweeps over an application icon optionally does not select the corresponding application.

[0191] Device 100 may also include one or more physical buttons, such as a “home” button or a menu button 204. As previously described, the menu button 204 can be used to navigate to any of a set of applications 136 that can be executed on the device 100. As an alternative, in some embodiments, the menu button is implemented as a soft key in a GUI displayed on the touch screen 112.

[0192] In some embodiments, device 100 includes a touch screen 112, a menu button 204, a push button 206 for powering on / off the device and for locking the device, one or more volume adjustment buttons 208, a subscriber identity module (SIM) card slot 210, an earphone jack 212, and a docking / charging external port 124. The push button 206 is optionally used to: power on / off the device by pressing the button and holding the button in the depressed state for a predetermined time interval; lock the device by pressing the button and releasing the button before a predetermined time interval has elapsed; and / or unlock the device or initiate an unlocking process. In an alternative embodiment, device 100 also accepts voice input for activating or deactivating certain functions via a microphone 113. Device 100 also optionally includes one or more contact intensity sensors 165 for detecting the intensity of contact on the touch screen 112, and / or one or more tactile output generators 167 for generating a tactile output for a user of the device 100.

[0193] Figure 3is a block diagram of an exemplary multifunctional device having a display and a touch-sensitive surface, in accordance with some embodiments. Device 300 need not be portable. In some embodiments, device 300 is a laptop computer, desktop computer, tablet computer, multimedia player device, navigation device, educational device (such as a children's learning toy), gaming system, or control device (e.g., a home or industrial controller). Device 300 generally 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 for interconnecting these components. The communication bus 320 optionally includes circuitry (sometimes called a chipset) that interconnects the system components and controls the communication between the system components. Device 300 includes an input / output (I / O) interface 330 having a display 340, which is typically a touch screen display. The I / O interface 330 also optionally includes a keyboard and / or mouse (or other pointing device) 350 and a touchpad 355, a haptic output generator 357 for generating haptic output on device 300 (e.g., similar to one or more of the haptic output generators 167 described above with reference to Figure 1A ), sensors 359 (e.g., optical sensors, acceleration sensors, proximity sensors, touch-sensitive sensors, and / or contact intensity sensors similar to one or more of the contact intensity sensors 165 described above with reference to Figure 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 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 one or more CPUs 310. In some embodiments, memory 370 stores programs, modules, and data structures similar to or subsets of those stored in the memory 102 of the portable multifunctional device 100 ( Figure 1A ). Additionally, memory 370 optionally stores additional programs, modules, and data structures not present in the memory 102 of the portable multifunctional device 100. For example, the memory 370 of device 300 optionally stores a drawing module 380, a presentation module 382, a word processing module 384, a website creation module 386, a disk editing module 388, and / or a spreadsheet module 390, while the memory 102 of the portable multifunctional device 100 ( Figure 1A ) optionally does not store these modules.

[0194] Figure 3Each of the above-described components in [component name] can be stored in one or more of the aforementioned memory devices. Each of the above-described modules corresponds to an instruction set for performing the above-described functions. The above-described modules or programs (e.g., instruction sets) need not be implemented as separate software programs, processes, or modules, and thus various subsets of these modules can be combined or otherwise rearranged in various embodiments. In some embodiments, memory 370 can store a subset of the above-described modules and data structures. Additionally, memory 370 can store additional modules and data structures not described above.

[0195] Attention is now turned to embodiments of a user interface that can be implemented on, for example, the portable multifunctional device 100.

[0196] Figure 4A An exemplary user interface of an application menu on the portable multifunctional device 100 according to some embodiments is shown. A similar user interface can be implemented on the device 300. In some embodiments, the user interface 400 includes the following elements or subsets or supersets thereof:

[0197] · One or more signal strength indicators 402 of one or more wireless communications such as cellular signals and Wi-Fi signals;

[0198] · Time 404;

[0199] · Bluetooth indicator 405;

[0200] · Battery status indicator 406;

[0201] · A tray 408 with icons of common applications, common application icons such as:

[0202] ○ An icon 416 labeled "Phone" of the phone module 138, the icon 416 optionally including an indicator 414 of the number of missed calls or voicemails;

[0203] ○ An icon 418 labeled "Mail" of the email client module 140, the icon 418 optionally including an indicator 410 of the number of unread emails;

[0204] ○ An icon 420 labeled "Browser" of the browser module 147; and

[0205] ○ An icon 422 labeled "iPod" of the video and music player module 152 (also referred to as the iPod (trademark of Apple Inc.) module 152); and

[0206] · Icons of other applications, such as:

[0207] ○ The icon 424 of the IM module 141 labeled as "Message";

[0208] ○ The icon 426 of the calendar module 148 labeled as "Calendar";

[0209] ○ The icon 428 of the image management module 144 labeled as "Photo";

[0210] ○ The icon 430 of the camera module 143 labeled as "Camera";

[0211] ○ The icon 432 of the online video module 155 labeled as "Online Video";

[0212] ○ The icon 434 of the stock market desktop applet 149-2 labeled as "Stock Market";

[0213] ○ The icon 436 of the map module 154 labeled as "Map";

[0214] ○ The icon 438 of the weather desktop applet 149-1 labeled as "Weather";

[0215] ○ The icon 440 of the alarm clock desktop applet 149-4 labeled as "Clock";

[0216] ○ The icon 442 of the fitness support module 142 labeled as "Fitness Support";

[0217] ○ The icon 444 of the notepad module 153 labeled as "Notepad"; and

[0218] ○ The icon 446 for setting the application or module labeled as "Settings", which provides access to the settings of the device 100 and its various applications 136.

[0219] It should be indicated that Figure 4A The icon labels shown are merely exemplary. For example, the icon 422 of the video and music player module 152 may optionally be labeled as "Music" or "Music Player". Other labels are optionally used for various application icons. In some embodiments, the label of the corresponding application icon includes the name of the application corresponding to the corresponding application icon. In some embodiments, the label of a particular application icon is different from the name of the application corresponding to the particular application icon.

[0220] Figure 4B A device (e.g., Figure 3 is shown having a touch-sensitive surface 451 (e.g., Figure 3Exemplary user interface on device 300). Device 300 also optionally includes one or more contact intensity sensors (e.g., one or more of sensors 357) for detecting the intensity of contacts on the touch-sensitive surface 451, and / or one or more tactile output generators 359 for generating tactile output for a user of device 300.

[0221] Although some of the following examples will be given with reference to input on a touch screen display 112 (where a touch-sensitive surface and a display are combined), in some embodiments, the device detects input on a touch-sensitive surface separate from the display, as Figure 4B shown. In some embodiments, the touch-sensitive surface (e.g., Figure 4B 451 in ) has a major axis (e.g., Figure 4B 452 in ) corresponding to the major axis (e.g., Figure 4B 453 in ) on the display (e.g., 450). According to these embodiments, the device detects contacts (e.g., Figure 4B 460 and 462 in ) with the touch-sensitive surface 451 at positions corresponding to respective positions on the display (e.g., in Figure 4B 460 corresponds to 468 and 462 corresponds to 470). Thus, when the touch-sensitive surface (e.g., Figure 4B 451 in ) is separate from the display of the multifunctional device ( Figure 4B 450 in ), user input detected by the device on the touch-sensitive surface (e.g., contacts 460 and 462 and their movements) is used by the device to manipulate the user interface on the display. It should be understood that similar methods are optionally used for other user interfaces described herein.

[0222] Additionally, although the following examples are mainly given with reference to finger input (e.g., finger contacts, single-finger tap gestures, finger swipe gestures), it should be understood that in some embodiments, one or more of these finger inputs are replaced by 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 the cursor along the path of the swipe (e.g., instead of movement of a contact). As another example, a tap gesture is optionally replaced by a mouse click when the cursor is above the position of the tap gesture (e.g., instead of detection of a contact, followed by termination of contact detection). Similarly, when multiple user inputs are detected simultaneously, it should be understood that multiple computer mice are optionally used simultaneously, or one mouse and multiple finger contacts are optionally used simultaneously.

[0223] Figure 5AAn exemplary personal electronic device 500 is shown. The device 500 includes a body 502. In some embodiments, the device 500 may include some or all of the features described for devices 100 and 300 (e.g., Figure 1A - 4B ). In some embodiments, the device 500 has a touch-sensitive display screen 504 hereinafter referred to as a touch screen 504. As an alternative or addition to the touch screen 504, the device 500 has a display and a touch-sensitive surface. As in the case of devices 100 and 300, in some embodiments, the touch screen 504 (or the touch-sensitive surface) may have one or more intensity sensors for detecting the intensity of an applied contact (e.g., a touch). One or more intensity sensors of the touch screen 504 (or the touch-sensitive surface) may provide output data representing the intensity of the touch. The user interface of the device 500 may respond to the touch based on the touch intensity, meaning that touches of different intensities may invoke different user interface operations on the device 500.

[0224] For example, techniques for detecting and processing touch intensity can be found in the following related patent applications: International Patent Application No. PCT / US2013 / 040061, titled "Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application," filed on May 8, 2013, and International Patent Application No. PCT / US2013 / 069483, titled "Device, Method, and Graphical User Interface for Transitioning Between Touch Input to Display Output Relationships," filed on November 11, 2013. Each of these two patent applications is hereby incorporated by reference in its entirety.

[0225] In some embodiments, the device 500 has one or more input mechanisms 506 and 508. The input mechanisms 506 and 508, if included, may be in physical form. Examples of physical input mechanisms include push buttons and rotatable mechanisms. In some embodiments, the device 500 has one or more attachment mechanisms. Such attachment mechanisms, if included, may allow the device 500 to be attached to, for example, hats, glasses, earrings, necklaces, shirts, jackets, bracelets, watchbands, bracelets, pants, belts, shoes, wallets, backpacks, etc. These attachment mechanisms may allow the user to wear the device 500.

[0226] Figure 5BAn exemplary personal electronic device 500 is shown. In some embodiments, device 500 may include some or all of the components described with reference to Figure 1A , Figure 1B and Figure 3 . Device 500 has a bus 512 that operatively couples the I / O section 514 to one or more computer processors 516 and a memory 518. The I / O section 514 may be connected to a display 504, which may have a touch-sensitive component 522 and optionally also a touch-intensity sensitive component 524. Additionally, the I / O section 514 may be connected to a communication unit 530 for receiving application and operating system data using Wi-Fi, Bluetooth, near field communication (NFC), cellular, and / or other wireless communication technologies. Device 500 may include input mechanisms 506 and / or 508. For example, input mechanism 506 may be a rotatable input device or a pressable input device and a rotatable input device. In some examples, input mechanism 508 may be a button.

[0227] In some examples, input mechanism 508 may be a microphone. The personal electronic device 500 may include 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 are operatively connected to the I / O section 514.

[0228] 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, may cause the computer processors to perform the above-described techniques, including processes 700, 900, 1100, 1300, 1500, 1700, and 1900 ( Figure 7 , Figure 9 , Figure 11 , Figure 13 , Figure 15 , Figure 17 and Figure 19 ). The personal electronic device 500 is not limited to Figure 5B the components and configurations of, but may include other components or additional components in a variety of configurations.

[0229] As used herein, the term "enabling representation" refers to user-interactive graphical user interface objects that may be displayed on the display screens of devices 100, 300, and / or 500 (FIGS. 1, 3, and 5). For example, images (e.g., icons), buttons, and text (e.g., hyperlinks) may each constitute an enabling representation.

[0230] As used herein, the term "focus selector" refers to an input element that is used to indicate the current part of the user interface with which the user is interacting. In some specific implementations that include a cursor or other position marker, the cursor acts as the "focus selector" such that when an input (e.g., a press input) is detected on a touch-sensitive surface (e.g., Figure 3 the touchpad 355 in Figure 4B or the touch-sensitive surface 451 in Figure 1A the touch-sensitive display system 112 in Figure 4A or the touch screen 112 in

[0231] when the cursor is above a particular user interface element (e.g., a button, window, slider, or other user interface element)), that particular user interface element is adjusted according to the detected input. In some specific implementations that include a touch screen display (e.g., Figure 1A the touch-sensitive display system 112 in Figure 4A or the touch screen 112 in

[0231] that enables direct interaction with user interface elements on the touch screen display), the detected contact on the touch screen acts as the "focus selector" such that when an input (e.g., a press input made by the 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 touch screen display, that particular user interface element is adjusted according to the detected input. In some specific implementations, the focus moves from one area of the user interface to another area of the user interface without a corresponding movement of the cursor or a movement of the contact on the touch screen display (e.g., by using the tab key or arrow keys to move the focus from one button to another button); in these specific implementations, the focus selector moves according to the movement of the focus between different areas of the user interface. Regardless of the specific form the focus selector takes, the focus selector is generally a user interface element (or a contact on the touch screen display) that is controlled by the user in order to deliver the interaction with the user interface that the user anticipates (e.g., by indicating to the device the element of the user interface that the user desires to interact with). For example, when a press input is detected on a touch-sensitive surface (e.g., a touchpad or touch screen), the position of the focus selector (e.g., the cursor, contact, or selection box) above the corresponding button will indicate that the user desires to activate the corresponding button (as opposed to other user interface elements shown on the device display).

[0231] As used in the specification and claims, the term "feature intensity" of a contact refers to a feature of the contact based on one or more intensities of the contact. In some embodiments, the feature intensity is based on a plurality of intensity samples. The feature intensity is optionally based on a predefined number or set of intensity samples collected during a predefined time period (e.g., 0.05 seconds, 0.1 seconds, 0.2 seconds, 0.5 seconds, 1 second, 2 seconds, 5 seconds, 10 seconds) relative to a predefined event (e.g., after detecting a contact, before detecting a contact lift, before or after detecting a contact start to move, before detecting a contact end, 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 feature intensity of a contact is optionally based on one or more of the following: the maximum value of the contact intensity, the mean value of the contact intensity, the average value of the contact intensity, the value at the top 10% of the contact intensity, the half maximum value of the contact intensity, the 90% maximum value of the contact intensity, etc. In some embodiments, the duration of the contact is used in determining the feature intensity (e.g., when the feature intensity is the average value of the contact intensity over time). In some embodiments, the feature intensity is compared to a set of one or more intensity thresholds to determine whether the user has performed an operation. For example, the set of one or more intensity thresholds can include a first intensity threshold and a second intensity threshold. In this example, a contact whose feature intensity does not exceed the first threshold results in a first operation, a contact whose feature intensity exceeds the first intensity threshold but does not exceed the second intensity threshold results in a second operation, and a contact whose feature intensity exceeds the second threshold results in a third operation. In some embodiments, the comparison between the feature intensity and one or more thresholds is used to determine whether to perform one or more operations (e.g., whether to perform the corresponding operation or to forgo performing the corresponding operation), rather than for determining whether to perform a first operation or a second operation.

[0232] Figure 5C Illustrated are a plurality of contacts 552A - 552E on a touch-sensitive display screen 504 detected by a plurality of intensity sensors 524A - 524D. Figure 5C Also included is an intensity map that shows the current intensity measurements of intensity sensors 524A - 524D in terms of intensity units. In this example, the intensity measurements of intensity sensors 524A and 524D are each 9 intensity units, and the intensity measurements of intensity sensors 524B and 524C are each 7 intensity units. In some specific implementations, the aggregated intensity is the sum of the intensity measurements of the plurality of intensity sensors 524A - 524D, which is 32 intensity units in this example. In some embodiments, each contact is assigned a corresponding intensity as part of the aggregated intensity. Figure 5DShows assigning an aggregate intensity to these contacts based on the distance of contacts 552A - 552E from the center of force 554. In this example, each of contacts 552A, 552B, and 552E is assigned a contact intensity of 8 intensity units in the aggregate intensity, and each of contacts 552C and 552D is assigned a contact intensity of 4 intensity units in the aggregate intensity. More generally, in some embodiments, according to a predefined mathematical function Ij = A·(Dj / ΣDi), a corresponding intensity Ij, which is part of the aggregate intensity A, is assigned to each contact j, where Dj is the distance of the corresponding contact j from the center of force, and ΣDi is the sum of the distances of all corresponding contacts (e.g., i = 1 to the last one) to the center of force. Refer to Figure 5C - 5D The operations described can be performed using an electronic device similar or identical to devices 100, 300, or 500. In some embodiments, the characteristic intensity of a contact is based on one or more intensities of the contact. In some embodiments, intensity sensors are used to determine a single characteristic intensity (e.g., a single characteristic intensity of a single contact). It should be noted that the intensity map is not part of the displayed user interface but is included for the convenience of the reader in Figure 5C - 5D it.

[0233] In some embodiments, a portion of an identified gesture is used to determine the characteristic intensity. For example, a touch - sensitive surface may receive a continuous swipe contact that transitions from a starting position and reaches an ending position where the intensity of the contact increases. In this example, the characteristic intensity of the contact at the ending position may be based on only a portion of the continuous swipe contact, rather than the entire swipe contact (e.g., only a portion of the swipe contact at the ending position). In some embodiments, a smoothing algorithm may be applied to the intensity of the swipe gesture before determining the characteristic intensity of the contact. For example, the smoothing algorithm optionally includes one or more of the following: an unweighted moving average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and / or an exponential smoothing algorithm. In some cases, these smoothing algorithms eliminate narrow spikes or dips in the intensity of the swipe contact for the purpose of determining the characteristic intensity.

[0234] The intensity of a contact on a touch-sensitive surface can be characterized relative to one or more intensity thresholds such as a contact detection intensity threshold, a light press intensity threshold, a deep press intensity threshold, and / or one or more other intensity thresholds. In some embodiments, the light press intensity threshold corresponds to an intensity at which the device will perform an operation typically associated with clicking a button of a physical mouse or touchpad. In some embodiments, the deep press intensity threshold corresponds to an intensity at which the device will perform an operation different from an operation typically associated with clicking a button of a physical mouse or touchpad. In some embodiments, when a contact is detected with a characteristic intensity below the light press intensity threshold (e.g., and above a nominal contact detection intensity threshold, contacts below this threshold are no longer detected), the device will move a focus selector based on the movement of the contact on the touch-sensitive surface without performing an operation associated with the light press intensity threshold or the deep press intensity threshold. Generally speaking, unless otherwise stated, these intensity thresholds are consistent between different sets of user interface drawings.

[0235] An increase in contact characteristic intensity from an intensity below the light press intensity threshold to an intensity between the light press intensity threshold and the deep press intensity threshold is sometimes referred to as a "light press" input. An increase in contact characteristic intensity from an intensity below the deep press intensity threshold to an intensity above the deep press intensity threshold is sometimes referred to as a "deep press" input. An increase in contact characteristic intensity from an intensity below the contact detection intensity threshold to an intensity between the contact detection intensity threshold and the light press intensity threshold is sometimes referred to as detecting a contact on the touch surface. A decrease in contact characteristic intensity from an intensity above the contact detection intensity threshold to an intensity below the contact detection intensity threshold is sometimes referred to as detecting a contact lift from the touch surface. In some embodiments, the contact detection intensity threshold is zero. In some embodiments, the contact detection intensity threshold is greater than zero.

[0236] In some embodiments described herein, one or more operations are performed in response to detecting a gesture that includes a corresponding press input or in response to detecting a corresponding press input performed using a corresponding contact (or contacts), where the corresponding press input is detected at least in part based on detecting an increase in the intensity of the contact (or contacts) above a press input intensity threshold. In some embodiments, a corresponding operation is performed in response to detecting an increase in the intensity of the corresponding contact above the press input intensity threshold (e.g., the "downstroke" of the corresponding press input). In some embodiments, the press input includes an increase in the intensity of the corresponding contact above the press input intensity threshold and a subsequent decrease in the intensity of the contact below the press input intensity threshold, and a corresponding operation is performed in response to detecting a subsequent decrease in the intensity of the corresponding contact below the press input threshold (e.g., the "upstroke" of the corresponding press input).

[0237] Figure 5E - 5Hshows the detection of a gesture that includes a press input corresponding to an increase in the intensity of contact 562 from Figure 5E below a light press intensity threshold (e.g., "IT L ") to Figure 5H above a deep press intensity threshold (e.g., "IT D "). A gesture performed with contact 562 is detected on the touch-sensitive surface 560, while the cursor 576 is shown above the application icon 572B corresponding to App 2 on the displayed user interface 570, which includes application icons 572A - 572D displayed in a predefined area 574. In some embodiments, the gesture is detected on the touch-sensitive display 504. An intensity sensor detects the intensity of the contact on the touch-sensitive surface 560. The device determines that the peak intensity of contact 562 is above the deep press intensity threshold (e.g., "IT D "). Contact 562 remains on the touch-sensitive surface 560. In response to detecting the gesture, and based on the fact that contact 562 has an intensity exceeding the deep press intensity threshold (e.g., "IT D ") during the gesture, representations 578A - 578C (e.g., thumbnails) of the most recently opened documents of App 2 are displayed in decreasing proportion, as Figure 5F - 5H shown. In some embodiments, the intensity compared to one or more intensity thresholds is the characteristic intensity of the contact. It should be noted that the intensity graph of contact 562 is not part of the displayed user interface but is included in Figure 5E - 5H for the convenience of the reader.

[0238] In some embodiments, the display of representations 578A - 578C includes an animation. For example, representation 578A is initially shown near the application icon 572B, as Figure 5F shown. As the animation progresses, representation 578A moves upward, and representation 578B is shown near the application icon 572B, as Figure 5G shown. Then, representation 578A moves upward, representation 578B moves upward towards representation 578A, and representation 578C is shown near the application icon 572B, as Figure 5H shown. Representations 578A - 578C form an array above the icon 572B. In some embodiments, the animation progresses according to the intensity of contact 562, as Figure 5F - 5G shown, where as the intensity of contact 562 approaches the deep press intensity threshold (e.g., "IT D "), representations 578A - 578C appear and move upward. In some embodiments, the intensity on which the animation progresses is the characteristic intensity of the contact. The operations described with reference to Figure 5E - 5H can be performed using an electronic device similar or identical to device 100, 300, or 500.

[0239] In some embodiments, the device employs strength hysteresis to avoid unexpected inputs sometimes referred to as "jitter", where the device defines or selects a hysteresis strength threshold having a predefined relationship to a press input strength threshold (e.g., the hysteresis strength threshold is X strength units lower than the press input strength threshold, or the hysteresis strength threshold is 75%, 90%, or some reasonable percentage of the press input strength threshold). Thus, in some embodiments, a press input includes an increase in the strength of a corresponding contact above the press input strength threshold and a subsequent decrease in the strength of that contact below the hysteresis strength threshold corresponding to the press input strength threshold, and a corresponding operation is performed in response to detecting that the strength of the corresponding contact subsequently decreases below the hysteresis strength threshold (e.g., the "upstroke" of the corresponding press input). Similarly, in some embodiments, a press input is detected only when the device detects an increase in the strength of a contact from a strength equal to or below the hysteresis strength threshold to a strength equal to or above the press input strength threshold and optionally a subsequent decrease in the strength of the contact to a strength equal to or below the hysteresis strength, and a corresponding operation is performed in response to detecting the press input (e.g., an increase in the strength of the contact or a decrease in the strength of the contact, depending on the environment).

[0240] For ease of explanation, optionally, a description of an operation performed in response to a press input associated with a press input strength threshold or in response to a gesture including a press input is triggered in response to detecting any one of the following various conditions: an increase in the strength of a contact above the press input strength threshold, an increase in the strength of a contact from a strength below the hysteresis strength threshold to a strength above the press input strength threshold, a decrease in the strength of a contact below the press input strength threshold, and / or a decrease in the strength of a contact below the hysteresis strength threshold corresponding to the press input strength threshold. Additionally, in an example where an operation is described as being performed in response to detecting a decrease in the strength of a contact below the press input strength threshold, the operation is optionally performed in response to detecting a decrease in the strength of the contact below the hysteresis strength threshold corresponding to and less than the press input strength threshold.

[0241] Figure 5I An exemplary device for completing a payment transaction connected via one or more communication channels is shown in accordance with some embodiments. One or more exemplary electronic devices (e.g., devices 100, 300, and 500) are configured to optionally detect an input (e.g., a specific user input, an NFC field), and optionally transmit payment information (e.g., using NFC). The one or more electronic devices optionally include NFC hardware and are configured to support NFC.

[0242] 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 the following: a person's name or company name, a billing address, a login name, a password, an account number, an expiration date, a security code, a phone number, a bank associated with the payment account (e.g., the issuing bank), and a card network identifier. In some examples, the payment account information includes an image, such as a photograph of a payment card (e.g., a photograph taken by and / or received by the device). In some examples, the electronic device receives user input that includes at least some of the payment account information (e.g., receives a credit card number, debit card number, account number, or shopping card number and an expiration date as user input). In some examples, the electronic device detects at least some of the payment account information from an image (e.g., of a payment card captured by a camera sensor of the device). In some examples, the electronic device receives at least some of the payment account information from another device (e.g., another user device or a server). In some examples, the electronic device receives payment account information from a server associated with another service (e.g., an application for renting or selling audio files and / or video files) for which the user's or user device's account has previously shopped or had payment account data identified.

[0243] In some embodiments, a payment account is added to the electronic device (e.g., devices 100, 300, and 500) such that the payment account information is securely stored on the electronic device. In some examples, after the user initiates such a process, the electronic device transmits the information of the payment account to a transaction coordination server, which then communicates with a server operated by the payment network of 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 a server that allows the electronic device to program the payment information of the account onto a secure element.

[0244] In some embodiments, communication between devices 100, 300, and 500 facilitates transactions (e.g., general transactions or specific transactions). For example, a first electronic device (e.g., 100) can function as a configuration device or a management device and can send new or updated payment account data (e.g., information for a new account, updated information for an existing account, and / or a warning regarding an existing account) to a second electronic device (e.g., 500). As another example, a first electronic device (e.g., 100) can send data to a second electronic device, where the data reflects information regarding a payment transaction facilitated at the first electronic device. The information optionally includes one or more of the following: payment amount, account used, time of purchase, and whether the default account was 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).

[0245] The electronic devices (e.g., 100, 300, 500) are configured to communicate with each other via any one of a variety of networks. For example, the devices communicate using a Bluetooth connection 580 (e.g., including a classic Bluetooth connection or a Bluetooth Low Energy connection) or using a WiFi network 582. Communication between user devices is optionally adjusted to reduce the likelihood of improper sharing of information between the devices. For example, communication regarding payment information requires the communicating devices to be paired (e.g., associated with each other via an explicit user interaction) or associated with the same user account.

[0246] In some embodiments, the electronic devices (e.g., 100, 300, 500) are used to communicate with point-of-sale (POS) payment terminals 820, 1220, which optionally support NFC. The communication optionally occurs using a variety of communication channels and / or technologies. In one example, the electronic devices (e.g., 100, 300, 500) communicate with the payment terminals 820, 1220 using an NFC channel 584. In some examples, the payment terminals 820, 1220 communicate with the electronic devices (e.g., 100, 300, 500) using a peer-to-peer NFC mode. The electronic devices (e.g., 100, 300, 500) are optionally configured to transmit a signal to the payment terminals 820, 1220, the signal including payment information for a payment account (e.g., the default account or an account selected for a specific transaction).

[0247] In some embodiments, the generation and / or transmission of the signal is controlled by a secure element in an electronic device (e.g., 100, 300, 500). Before releasing payment information, the secure element optionally requires a specific user input. For example, the secure element optionally requires: detecting an electronic device being worn, detecting a button press, detecting a password entry, detecting a touch, detecting one or more option selections (e.g., option selections received when interacting with an application), detecting a fingerprint signature, detecting speech or a voice command, and / or detecting a gesture or movement (e.g., rotation or acceleration). In some examples, if a communication channel (e.g., an NFC communication channel) is established with another device (e.g., payment terminals 820, 1220) within a defined time period from detecting the input, the secure element releases the payment information to be transmitted to the other device (e.g., payment terminals 820, 1220). In some examples, the secure element is a hardware component that controls the release of secure information. In some examples, the secure element is a software component that controls the release of secure information.

[0248] In some embodiments, the protocol associated with transaction participation depends on, for example, the device type. For example, for wearable devices (e.g., device 500) and phones (e.g., device 100), the conditions for generating and / or transmitting payment information can be different. For example, the generation conditions and / or transmission conditions for wearable devices include detecting that a button has been pressed (e.g., after security verification), while the corresponding conditions for phones do not require a button press but rather require detecting a specific interaction with an application. In some embodiments, the conditions for transmitting and / or releasing payment information include receiving specific inputs on each of a plurality of devices. For example, the release of payment information optionally requires detecting a fingerprint and / or password at a device (e.g., device 100), and detecting a mechanical input (e.g., a button press) on another device (e.g., device 500).

[0249] Payment terminals 820, 1220 optionally use the payment information to generate a signal for transmission to a payment server 590 to determine whether the payment is authorized. The payment server 590 optionally includes any device or system configured to receive payment information associated with a payment account and determine whether a proposed purchase is authorized. In some examples, the payment server 590 includes a server of an issuing bank. The payment terminals 820, 1220 communicate directly with the payment server 590 or indirectly via one or more devices or systems (e.g., a server of an acquiring bank and / or a server of a card network).

[0250] The payment server 590 optionally uses at least some of the payment information to identify a user account from a database of user accounts (e.g., 592). For example, each user account includes payment information. The account is optionally located by locating an account having specific payment information that matches the information communicated from the POS. In some examples, payment is declined when the provided payment information is inconsistent (e.g., the expiration date does not correspond to the credit card number, debit card number, or shopping card number) or when no account includes payment information that matches the information communicated from the POS.

[0251] In some embodiments, the data of the user account further identifies one or more restrictions (e.g., credit limit); current or previous balance; last transaction date, location, and / or amount; account status (e.g., active or frozen), and / or authorization instructions. In some examples, the payment server (e.g., 590) uses such data to determine whether to authorize a payment. For example, the payment server declines payment when the purchase amount added to the current balance would result in exceeding 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.

[0252] In some embodiments, the payment server 590 responds to the POS payment terminals 820, 1220 with an indication of whether the proposed purchase is authorized or declined. In some examples, the POS payment terminals 820, 1220 transmit a signal to an electronic device (e.g., 100, 300, 500) to identify the result. For example, when a purchase (e.g., via a transaction coordination server that manages a transaction application on a user device) is authorized, the POS payment terminals 820, 1220 send a receipt to the electronic device (e.g., 100, 300, 500). In some cases, the POS payment terminals 820, 1220 present an output (e.g., visual or audio output) indicating the result. The payment may be transmitted to the merchant as part of the authorization process or may be transmitted later.

[0253] In some embodiments, the electronic device (e.g., 100, 300, 500) participates in a transaction that can be completed without involving the POS payment terminals 820, 1220. For example, when a mechanical input that has been received is detected, a secure element in the electronic device (e.g., 100, 300, 500) releases payment information to allow an application on the electronic device to access the information (e.g., and transmit the information to a server associated with the application).

[0254] Attention is now turned to embodiments of a user interface (“UI”) and associated processes that can be implemented on an electronic device such as the portable multifunctional device 100, device 300, or device 500.

[0255] Some embodiments described below relate to loyalty accounts. For example, a loyalty account can be an account of a loyalty program that provides a structured marketing effort to reward customers / members. A loyalty account is optionally dedicated to a particular company, store, or chain. A company (such as a retail store or chain) can use a loyalty account to track purchases or other information about a user (e.g., a buyer). A loyalty account typically gives the user the right to a discount on current or future purchases and / or gives the user the right to allocate points that can be used for future purchases or giveaways. In some examples, a loyalty account cannot be used to make payments. Generally speaking, a loyalty account cannot be used to make monetary payments.

[0256] Some embodiments described below relate to private label accounts. For example, a private label account includes a payment account that is registered for a particular merchant, independent dealer, or manufacturer. Some private label cards and private label accounts are only accepted at a particular merchant or may offer certain benefits that are only available at a particular merchant. For example, a particular merchant can offer a private label account to a customer that can only be used when making purchases through that particular merchant. Merchants generally prefer to offer private label accounts because the private label account provides another way for customers to shop at that merchant, thereby increasing sales and providing a convenient payment option for the customer.

[0257] Some embodiments described below relate to transferring payment account information from an electronic device to a contactless payment terminal so that the contactless payment terminal can participate in a payment transaction, such as by routing the information to one or more financial institutions to verify payment credentials and / or receive authorization to complete the transaction. For example, an exemplary payment network architecture and additional details regarding the path of a payment transaction can be found in, for example Figure 2 and the accompanying description of the following application: U.S. Patent Application Serial No. 62 / 004,338 (Reference No. P22931USP1) entitled "USER DEVICE SECURE PARTICIPATION IN TRANSACTIONS VIA LOCAL SECURE ELEMENT DETECTION OF MECHANICAL INPUT" filed on May 29, 2014.

[0258] Figure 6A - 6G Exemplary techniques and exemplary user interfaces are shown in accordance with some embodiments for receiving a selection of an account from among multiple accounts in an electronic wallet, such as a loyalty account or a payment account. For example, the account information of the selected account can subsequently be transferred to an NFC-enabled payment terminal for use in a transaction (e.g., when the device is placed in the field of the payment terminal). The user interfaces in these figures are used to illustrate the processes described below, which includeFigure 7 The process in

[0259] Figure 6A FIG. 5 shows a wearable electronic device 500, which is, for example, a smartwatch. The device includes a display, a touch-sensitive surface, and one or more wireless communication elements (e.g., one or more wireless antennas, such as an NFC antenna, a WiFi antenna). The device receives an input (e.g., user input) for requesting to enable the device to perform a payment transaction (e.g., the user double-taps on the hardware button 508 of the device, preparing the device to perform an NFC payment and / or access the electronic wallet of the device).

[0260] In response to receiving the input for requesting to enable the device to perform a payment transaction, and as Figure 6A shown, the device displays a first visual indicator 602 for identifying a first account on the display, and the device enables the electronic device to participate in the transaction via one or more wireless communication elements using the first account (e.g., prepares the device to perform an NFC payment using the default payment account, or prepares the device to perform an NFC transaction using a loyalty account). The ready indicator 604 is a visual indication that the device is enabled to participate in the transaction using the first account represented by the first visual indicator 602. The first visual indicator 602 may occupy less than 70% (or 60%, 50%, or 40% or less) of the total display space of the display. The device may also display an indication 606 that other accounts are available, or an indication 606 of the number of other available accounts on the display. In this example, the indication 606 includes four paging dots. The first paging dot has a first color, which is different from the second color of the second, third, and fourth paging dots. These four paging dots indicate that a total of four accounts are available. The color of the first paging dot is different from that of the other paging dots, indicating that the device is currently displaying information corresponding to the first account (e.g., the first visual indicator 602).

[0261] At Figure 6B , the electronic device receives one or more swipe inputs in a first direction (e.g., one or more left swipes or one or more right swipes) via the touch-sensitive surface. At Figure 6B , one or more swipe inputs are detected, and the first visual indicator 602 is being transformed into not being displayed (e.g., by sliding the first visual indicator 602 in the first direction). In some examples, when the first visual indicator 602 is being transformed into not being displayed, the ready indicator 604 is no longer displayed.

[0262] As Figure 6CAs shown, in response to receiving one or more user swipe inputs, the device displays a second visual indicator 620 on the display for a second account that is different from the first account, and the device enables the electronic device to participate in a transaction using the second account via one or more wireless communication elements (e.g., prepares the device to perform an NFC transaction using the second account and prohibits the device from participating in a transaction using the first account). In some embodiments, the second visual indicator 620 is larger than the first visual indicator 602. For example, the second visual indicator occupies more than 70% (or greater than 60%, 50%, or 40%) of the total display space of the display. At Figure 6C , the first visual indicator 602 is no longer displayed, and the paging point 606 has been updated to reflect that the device is currently displaying information corresponding to the second account (e.g., the second visual indicator 620). The ready indicator 622 is a visual indication that the device is enabled to participate in a transaction using the second account.

[0263] The first visual indicator 602 is different from the second visual indicator 610. For example, the first visual indicator 602 includes: the name of the first financial institution, "AA Bank", having a first background design that corresponds to the background design of the payment card associated with the first account, at least a portion of the account number associated with the first account, and the expiration date associated with the first account. The second visual indicator 620 includes the name of the merchant associated with the loyalty account, "SUPERMARKETINC.", having a second background design that is different from the first background design, and may or may not include at least a portion of the account number associated with the second account. In this example, the second visual indicator does not display the expiration date associated with the second account.

[0264] According to some embodiments, as Figure 6A - 6C shown, the first account is a payment account and the second account is a loyalty account. According to some embodiments, as Figure 6A and 6G shown, the first account is a payment account and the second account is a payment account.

[0265] According to some embodiments, as Figure 6D - 6F shown, when displaying the second visual indicator (e.g., of a loyalty account): the electronic device receives a card code display input (e.g., a user swipe input in a second direction different from the first direction; a tap on the "display barcode" affordance 626), and in response to receiving the card code display input, the electronic device displays visual loyalty card code information (e.g., 624; a barcode or QR code) on the display. The visual loyalty card code information may optionally represent account information of the second account. For example, in

[0266] when the second visual indicator is being displayed: the electronic device receives a card code display input (e.g., a user swipe input in a second direction different from the first direction; a tap on the "display barcode" affordance 626), and in response to receiving the card code display input, the electronic device displays visual loyalty card code information (e.g., 624; a barcode or QR code) on the display. The visual loyalty card code information may optionally represent account information of the second account. For example, in Figure 6DAt this point, the device receives an upward swipe input on the touch-sensitive surface and, in response, displays barcode 624. The user may have barcode 624 visually scanned by a payment terminal. For example, at Figure 6D At this point, the device receives the same upward swipe input on the touch-sensitive surface and, in response, displays an enabling representation 626 that, when activated, displays visual loyalty card code information (e.g., 624) associated with a second account.

[0267] According to some embodiments and with reference to Figure 6C the user interface, the user places the device within the field of a contactless payment terminal. When a second visual indicator is displayed: the electronic device receives a request for account information from the contactless payment terminal and, in response to receiving the request for account information, transmits the account information of the second account to the contactless payment terminal via one or more wireless communication elements, where the account information enables the contactless payment terminal to participate in a payment transaction.

[0268] According to some embodiments, participating in a payment transaction includes routing loyalty information to one or more servers for confirmation / authorization of a loyalty account (e.g., when the second account is a loyalty account). In some embodiments, participating in a payment transaction includes routing information to one or more financial institutions to verify payment credentials and / or receive authorization to complete the transaction (e.g., when the second account is a payment account). For example, the account information is transmitted to the contactless payment terminal using NFC.

[0269] According to some embodiments (e.g., where the second account is a payment account), when the second visual indicator is displayed and after transmitting the account information of the second account to the contactless payment terminal: the electronic device receives a failed communication from the contactless payment terminal via one or more wireless communication elements (e.g., payment is declined because the payment account type is not accepted by the contactless payment terminal). In response to receiving the failed communication: the electronic device displays an indication that the second account is not accepted on the display and provides an option to enable the electronic device to participate in the transaction using an account different from the second account (e.g., a default payment account that is not a private label payment account).

[0270] According to some embodiments, after (or in response to) transmitting the account information of the second account to the contactless payment terminal, the electronic device simultaneously displays on the display an indication that both the first account and the second account are being used during the payment transaction (e.g., simultaneously displaying at least a portion of the first visual indicator and at least a portion of the second visual indicator). For example, the user may use the electronic device to provide loyalty account information with the second account and payment account information with the first account. Accordingly, the two visual indicators will be displayed simultaneously after the transaction.

[0271] According to some embodiments, enabling an electronic device to participate in a transaction using a second account via one or more wireless communication components does not require receiving a second user input for requesting to enable the device for a payment transaction. For example, the user does not need to double-tap the hardware button 508 again to prepare the device for an NFC payment or an NFC loyalty transaction using the second account.

[0272] According to some embodiments, enabling an electronic device to participate in a transaction using a first account includes: displaying a first animation of a ready indicator (e.g., 604) that appears from below a card image (e.g., a first visual indicator 602) of the first account. The ready indicator (e.g., 604) indicates that the device is enabled to participate in a payment transaction using the first account. In response to receiving a portion of one or more user swipe inputs, the electronic device displays a second animation of the ready indicator to slide the ready indicator (e.g., 604) back below the card image of the first account.

[0273] According to some embodiments, the electronic device displays a first visual indicator (e.g., 602) for identifying a first account, and then enables the electronic device to participate in a transaction using the first account via one or more wireless communication components. The electronic device displays a second visual indicator (e.g., 620) for identifying a second account on the display, and then enables the electronic device to participate in a transaction using the second account via one or more wireless communication components.

[0274] According to some embodiments, one of the first account and the second account is a payment account, and one of the first account and the second account is a loyalty account (e.g., the first account is a payment account, and the second account is a loyalty account). The first visual indicator (e.g., 602) of the first account has a first dimensional characteristic (e.g., size or aspect ratio), and the second visual indicator (e.g., 620) of the second account has a second dimensional characteristic (e.g., a different size or a different aspect ratio) that is different from the first dimensional characteristic. Thus, the visual indicator of the loyalty account looks different from the visual indicator of the payment account. This helps the user quickly identify whether the loyalty account or the payment account is being displayed and / or enabled.

[0275] According to some embodiments, the electronic wallet of the electronic device includes payment account information of a plurality of payment accounts (e.g., including payment accounts associated with 602 and 610) associated with a user of the electronic device.

[0276] As Figure 6FAs shown, the electronic device receives a second one or more swipe inputs in a first direction via the touch-sensitive surface. In response to receiving the second one or more user swipe inputs, the electronic device displays a third visual indicator on the display that identifies a third account, and the electronic device enables the electronic device to participate in a transaction via one or more wireless communication elements using the third account; and (e.g., prepares the device to use the third account for an NFC transaction and prohibits the device from participating in a transaction using the second account). The third visual indicator is different from the first visual indicator and the second visual indicator.

[0277] Figure 7 FIG. 700 is a flow diagram illustrating a method according to some embodiments for using an electronic device to receive a selection of an account from a plurality of accounts in an electronic wallet, such as a loyalty account or a payment account. Method 700 is performed at a device (e.g., 100, 300, 500) having a display, a touch-sensitive surface, and one or more wireless communication elements. Some of the operations in method 700 may be combined, the order of some operations may be changed, and some operations may be omitted.

[0278] As described below, method 700 provides an intuitive way to receive a selection of an account from a plurality of accounts in an electronic wallet, such as a loyalty account or a payment account. The method reduces the user's cognitive burden for receiving a selection of an account, thereby creating a more effective human-machine interface. For a battery-powered computing device, enabling the user to select an account faster and more efficiently saves power and increases the time interval between two battery charges.

[0279] At block 702, the electronic device receives an input (e.g., a user input at 508) for requesting to enable the device for a payment transaction.

[0280] At block 704, in response to receiving the input for requesting to enable the device for a payment transaction, the process proceeds to blocks 706-708.

[0281] At block 706, the electronic device displays a first visual indicator (e.g., 602) on the display that identifies a first account. At block 708, the electronic device enables the electronic device to participate in a transaction via one or more wireless communication elements using the first account.

[0282] At block 710, the electronic device receives one or more swipe inputs (e.g., one or more left swipes) in a first direction via the touch-sensitive surface.

[0283] At block 712, in response to receiving the one or more user swipe inputs, the process proceeds to blocks 714-716.

[0284] At block 714, the electronic device displays a second visual indicator (e.g., 620) for identifying a second account on the display. At block 716, the electronic device enables the electronic device to participate in a transaction via one or more wireless communication elements using the second account, where the first visual indicator (e.g., 601) is different from the second visual indicator (e.g., 620).

[0285] According to some embodiments, the first account is a payment account and the second account is a loyalty account. According to some embodiments, the first account is a payment account and the second account is a payment account.

[0286] According to some embodiments, when displaying the second visual indicator (e.g., the second visual indicator 620 of the loyalty account): the electronic device receives a card code display input, and in response to receiving the card code display input, the electronic device displays visual loyalty card code information (e.g., 624; bar code or QR code) on the display.

[0287] According to some embodiments, the user places the device in the field of a contactless payment terminal. When displaying the second visual indicator: the electronic device receives a request for account information from the contactless payment terminal, and in response to receiving the request for account information, transmits the account information of the second account to the contactless payment terminal via one or more wireless communication elements, where the account information enables the contactless payment terminal to participate in a payment transaction.

[0288] According to some embodiments (e.g., where the second account is a payment account), when displaying the second visual indicator and after transmitting the account information of the second account to the contactless payment terminal: the electronic device receives a failed communication from the contactless payment terminal via one or more wireless communication elements. In response to receiving the failed communication: the electronic device displays an indication that the second account is not accepted on the display, and provides an option to enable the electronic device to participate in a transaction using an account different from the second account.

[0289] According to some embodiments, after (or in response to) transmitting the account information of the second account to the contactless payment terminal, the electronic device simultaneously displays an indication on the display that both the first account and the second account are used during the payment transaction (e.g., simultaneously displays at least a portion of the first visual indicator and at least a portion of the second visual indicator).

[0290] According to some embodiments, enabling an electronic device to participate in a transaction using a first account includes displaying a first animation of a readiness indicator (e.g., 604) that appears from below a card image (e.g., first visual indicator 602) of the first account. The readiness indicator (e.g., 604) indicates that the device is enabled to participate in a payment transaction using the first account. In response to receiving a portion of one or more user swipe inputs, the electronic device displays a second animation of the readiness indicator to slide the readiness indicator (e.g., 604) back below the card image of the first account.

[0291] According to some embodiments, the electronic device displays a first visual indicator (e.g., 602) for identifying a first account and then enables the electronic device to participate in a transaction using the first account via one or more wireless communication elements. The electronic device displays a second visual indicator (e.g., 620) for identifying a second account on a display and then enables the electronic device to participate in a transaction using the second account via one or more wireless communication elements.

[0292] According to some embodiments, one of the first account and the second account is a payment account and one of the first account and the second account is a loyalty account (e.g., the first account is a payment account and the second account is a loyalty account). The first visual indicator (e.g., 602) of the first account has a first dimensional characteristic (e.g., size or aspect ratio), and the second visual indicator (e.g., 620) of the second account has a second dimensional characteristic different from the first dimensional characteristic (e.g., a different size or a different aspect ratio).

[0293] According to some embodiments, an electronic wallet of the electronic device includes payment account information of a plurality of payment accounts (e.g., including payment accounts associated with 602 and 610) associated with a user of the electronic device.

[0294] It should be noted that the details of the processes described above with reference to method 700 (e.g., Figure 7 ) also apply in a similar manner to the methods described below. For example, methods 900, 1100, 1300, 1500, 1700, and 1900 may include one or more features of the various methods described above with reference to method 700. For example, the electronic wallet, payment accounts, loyalty accounts, affordances, and inputs of methods 900, 1100, 1300, 1500, 1700, and 1900 optionally have one or more features of the electronic device, payment accounts, loyalty accounts, affordances, and inputs of method 700. For the sake of brevity, these details are not repeated below.

[0295] Figure 8A - 8DIllustrates exemplary techniques and exemplary user interfaces for selecting an account to be displayed, such as a loyalty account or a payment account, according to some embodiments. For example, account information of the selected account may subsequently be transmitted to an NFC-enabled payment terminal for use in a transaction (e.g., when the device is placed in the field of the payment terminal). The technique may be performed at an electronic device having a display and a location sensor. The user interfaces in these figures are used to illustrate the processes described below, which include Figure 9 the processes in.

[0296] Some accounts, such as private label accounts or loyalty accounts, may be associated with a particular location (e.g., a particular merchant or a particular store of a merchant). When at these locations, a user may prefer to use the associated private label account or loyalty account in a transaction. For example, if a user is located at Joe’s Electronics store, the user may prefer to use the private label account associated with Joe’s Electronics store (e.g., a private label credit card account). As another example, if a user is located at a supermarket, the user may prefer to use the loyalty account associated with the supermarket during a transaction, and the user uses the default payment account to make the payment. Thus, displaying a visual indication of an account relevant to the current situation (e.g., location) on the display of the electronic device provides value to the user.

[0297] For example, a payment account may be associated with multiple locations (e.g., multiple stores in a chain operation). Additionally, different locations may be associated with different payment accounts (e.g., the user has a Joe’s Electronics credit card and a Jack’s Home Improvement Store credit card, and the Joe’s Electronics credit card may be associated with Joe’s Electronics store, while the Jack’s Home Improvement Store card is associated with Jack’s Home Improvement Store).

[0298] Now turning to Figure 8A , the electronic device uses the location sensor to detect the current location (e.g., the electronic device determines that the device is physically located at a particular retailer or a particular store of a particular retailer). The electronic device determines whether the current location is associated with a first account (e.g., determines whether a particular private label payment account or a particular loyalty account is associated with the retailer).

[0299] As Figure 8AAs shown, based on the failure to determine (e.g., during the time period between receiving a request to prepare the default payment account and the preparation of the default payment account) that the current location is associated with an account other than the default payment account (e.g., the device determines that the location of the device is not associated with the current location, or the device fails to determine the location of the device), the electronic device displays a visual indication 802 of the default payment account (e.g., a visual depiction of a credit card associated with the default payment account) on the display. In some embodiments, the visual indication 802 of the default payment account is displayed without displaying graphical indicators of other accounts. At Figure 8A , the ready indication 804 is a visual indication that the device is ready to participate in a transaction using the default account represented by the visual indicator 802.

[0300] The visual indication 802 of the default payment account includes: the name of the first financial institution associated with the default payment account, "AA Bank", a first background design that corresponds to the background design of the payment card associated with the default payment account, at least a portion of the account number associated with the default payment account, and the expiration date associated with the default payment account.

[0301] As Figure 8B shown, based on determining that the current location is associated with a first account, the electronic device simultaneously displays a visual indication 802 of the default payment account (e.g., a visual depiction of a credit card associated with the default payment account) and a visual indication 806 of the first account (e.g., a visual depiction of a private label card or a specific loyalty account associated with a specific payment account) on the display. The default payment account and the first account are linked to the electronic device (e.g., stored in the device's electronic wallet; the electronic device has been configured for both accounts), and the default payment account and the first account are different accounts. At Figure 8B , the ready indication 804 is a visual indication that the device is ready to participate in a transaction using either the default account represented by the visual indicator 802 or the first account represented by the visual indicator 806 (or both).

[0302] The visual indication 806 of the first account may include: the name of the merchant or financial institution associated with the first account (e.g., "SHOPCO"), a first background design that corresponds to the first account, at least a portion of the account number associated with the first account, and the expiration date associated with the first account.

[0303] For example, a payment account (e.g., a first account) may be associated with multiple locations (e.g., multiple stores in a chain operation). Additionally, different locations may be associated with different payment accounts (e.g., a user has a Joe’s Electronics credit card and a Jack’s Home Improvement Store credit card. The Joe’s Electronics credit card may be associated with the Joe’s Electronics store, and the Jack’s Home Improvement Store card is associated with the Jack’s Home Improvement Store).

[0304] According to some embodiments, as Figure 8B shown, the first account is a payment account. In some embodiments, the first account is a private label account, and the visual indication 806 of the first account is an image of a payment card associated with the private label account. In some embodiments, the visual indication 806 of the first account is partially displayed behind the visual indication 802 of the default account.

[0305] According to some embodiments, as Figure 8C shown, the first account is a loyalty account. In some embodiments, the first account is a loyalty account, and the visual indication 808 is an image of a loyalty card associated with the loyalty account. In some embodiments, the visual indication 808 of the first account is partially displayed behind the visual indication 802 of the default account.

[0306] According to some embodiments, as Figure 8D shown, the electronic device receives a request associated with a payment transaction from a contactless payment terminal 820 (e.g., when the device is located in the NFC field of the contactless payment terminal 820). The electronic device determines whether the request includes a request for payment account information using a first account type corresponding to the first account (e.g., when the device is placed in the field of the terminal, the NFC-enabled terminal requests the private label credit card of a specific retailer). Based on determining that the current location is associated with the first account and based on determining that the request includes a request for payment information using the first account type, the electronic device transmits the payment account information of the first account to the contactless payment terminal using one or more wireless communication elements, wherein the payment account information of the first account enables the contactless payment terminal to participate in the payment transaction. In some embodiments, participating in the payment transaction includes routing information to one or more financial institutions to verify payment credentials and / or receive authorization to complete the transaction. For example, NFC is used to transmit the payment account information to the contactless payment terminal. In some embodiments, participating in the payment transaction includes routing loyalty information to one or more servers for confirmation / authorization of the loyalty account.

[0307] According to some embodiments, an electronic device receives a request associated with a payment transaction from a contactless payment terminal. The electronic device determines that the request includes a request for payment account information using a first account type corresponding to a first account (e.g., when the device is placed in the field of the terminal, an NFC-enabled terminal requests a private label credit card of a particular retailer). Based on a failure to determine that the current location is associated with an account other than the default payment account (and based on determining that the request includes a request for payment account information using the first account type), the electronic device transmits payment account information of the default payment account to the contactless payment terminal using one or more wireless communication elements, wherein the payment account information of the default payment account enables the contactless payment terminal to participate in the payment transaction. In some embodiments, participating in the payment transaction includes routing information to one or more financial institutions to verify payment credentials and / or receive authorization to complete the transaction. For example, NFC is used to transmit the payment account information to the contactless payment terminal.

[0308] According to some embodiments, a visual indication of the first account is displayed on the visual indication 802 of the default account, and wherein the visual indication of the first account indicates that the first account is enabled to be selected by the device for a payment transaction without additional user input. For example, the visual indication of the first account is simply text written on the card image of the default account, and the device determines (at the time of payment) which payment account to use without user intervention.

[0309] According to some embodiments, prior to using a location sensor to detect the current location, the electronic device receives an input (e.g., user input) for requesting to enable the device for a payment transaction (e.g., the user double-clicks on the hardware button 508 of the device to prepare the device for NFC payment and / or accessing the electronic wallet). In some examples, in response to receiving the user input for requesting to enable the device for a payment transaction, the device is enabled to participate in the transaction (e.g., prepare the device for NFC payment using the default payment account).

[0310] According to some embodiments, detecting the current location using a location sensor is performed in response to receiving an input for requesting to enable the device for a payment transaction.

[0311] According to some embodiments, determining whether the current location is associated with the first account is performed in response to receiving an input for requesting to enable the device for a payment transaction (e.g., the user double-clicks on the hardware button 508 of the device to prepare the device for NFC payment and / or accessing the electronic wallet). In some examples, in response to receiving the user input for requesting to enable the device for a payment transaction, the device is enabled to participate in the transaction (e.g., prepare the device for NFC payment using the default payment account).

[0312] According to some embodiments, when the device fails to determine that the current location is associated with a first account before enabling the electronic device to participate in a transaction via one or more wireless communication elements using a default payment account (e.g., determining whether the current location is associated with the first account takes longer than enabling the electronic device to participate in a transaction via one or more wireless communication elements using the default payment account), a failure to determine that the current location is associated with an account other than the default payment account occurs. Alternatively, when the device detects that the user of the electronic device is still viewing the electronic device or the electronic device is still facing the user, the electronic device simultaneously displays a visual indication of the default payment account and a visual indication of the first account on the display. For example, (1) when the user is still viewing the device or (2) when the device is still facing the user, the user is provided with an opportunity to view the change and recognize that a different payment account can be used in a payment transaction by only changing the visual indication of the account on the display.

[0313] In some embodiments, if the electronic device is worn on the user's wrist, the electronic device can detect that the user is viewing the electronic device by detecting the user lifting or turning their wrist (e.g., a lift gesture) to move the electronic device into a viewing position. The electronic device can detect that the user is no longer viewing the device by detecting the user lowering their wrist. As used herein, a viewing position is an electronic device position where the user can view the display of the electronic device. In some embodiments, the electronic device can detect a signal indicating that the user has lifted or lowered their wrist, as described in U.S. Provisional Patent Application Serial No. 62 / 026,532, “Raise Gesture Detection in a Device,” which is hereby incorporated by reference in its entirety.

[0314] In some embodiments, a lift gesture detection algorithm may progress through a series of states of increasing confidence in the executed lift gesture. For example, the lift gesture detection algorithm may select a set of motion sensor data samples (including accelerometer and / or gyro sensor data) corresponding to a time interval of interest (e.g., the amount of time it may take for a user to execute a lift gesture). By considering the oldest sample in the set, the algorithm may define a "start pose" that may reflect the spatial orientation of the device at the start of the time interval. This orientation may be defined relative to an assumed vertical axis of gravity. Based on the start pose, the algorithm may determine the amount and / or direction of motion that may occur to bring the device's display into the user's line of sight (also referred to as bringing the device into a "focus pose"). The possible amount and / or direction of motion may be expressed as criteria for identifying a "possible" lift gesture, and these criteria may be used to identify whether a possible lift gesture has occurred based on some or all of the motion sensor data samples in the set. A possible lift gesture may be further identified as a "detected" lift gesture by determining whether the device that has reached the focus pose remains in the focus pose for at least a minimum time period. If desired, further confirmation may be performed using a gesture classifier. The lift gesture detection algorithm may notify other components of the device each time it identifies a possible, detected, and / or confirmed lift gesture.

[0315] According to some embodiments, an electronic device receives a request for loyalty account information from a contactless payment terminal, where the first account is a loyalty account. In response to receiving the request for loyalty account information, and based on a failure to determine that the current location is associated with an account other than the default payment account (e.g., during the time period between receiving a request to prepare an account and preparing the account), and based on a subsequent determination that the current location is associated with the first account: the electronic device transmits account information of the first account to the contactless payment terminal via one or more wireless communication elements, and the electronic device transmits payment account information of the default payment account to the contactless payment terminal via one or more wireless communication elements. In some embodiments, the account information of the first account is provided without considering whether a representation of the first account was displayed on the display before participating in the payment transaction. In some embodiments, the account information of the first account is provided only when a representation of the first account was displayed on the display before participating in the payment transaction.

[0316] According to some embodiments, an electronic device receives a request associated with a payment transaction from a contactless payment terminal. The electronic device determines that the request includes a request for payment account information using a first account type corresponding to a first account, where the first account is a payment account different from the default payment account (e.g., when the device is placed in the field of the terminal, an NFC-enabled terminal requests a private label credit card of a specific retailer). In response to receiving the request for account information, based on a failure to determine that the current location is associated with an account other than the default payment account (e.g., during the time period between receiving the request to prepare the account and preparing the account), and based on a subsequent determination that the current location is associated with the first account: the electronic device forgoes transmitting the account information of the first account to the contactless payment terminal via one or more wireless communication elements, and the electronic device transmits the payment account information of the default payment account to the contactless payment terminal via one or more wireless communication elements. In some embodiments, the account information of the first account is provided only when a representation of the first account is displayed on the display before participating in the payment transaction.

[0317] According to some embodiments, an electronic device receives a request associated with a payment transaction from a contactless payment terminal. Before receiving the request associated with the payment transaction from the contactless payment terminal, a visual indication of the default payment account (e.g., a visual depiction of a credit card associated with the default payment account) and a visual indication of the first account (e.g., a visual depiction of a private label card or a specific loyalty account associated with a specific payment account) are simultaneously displayed on the display. The request includes a request for payment account information using a first account type corresponding to the first account (e.g., when the device is placed in the field of the terminal, an NFC-enabled terminal requests a private label credit card of a specific retailer). The first account is a payment account of the first account type. In response to receiving the request for account information and based on a failure to determine that the current location is associated with an account other than the default payment account (e.g., during the time period between receiving the request to prepare the account and preparing the account), and based on a subsequent determination that the current location is associated with the first account: the electronic device forgoes transmitting the account information of the default payment account to the contactless payment terminal via one or more wireless communication elements, and the electronic device transmits the payment account information of the first account to the contactless payment terminal via one or more wireless communication elements.

[0318] According to some embodiments, upon determining that the current location is associated with a first account, the electronic device receives a failed communication from the contactless payment terminal via one or more wireless communication elements (e.g., the payment is declined because the payment account is frozen by the bank or has no funds). In response to receiving the failed communication, the electronic device transmits account information of the default payment account to the contactless payment terminal via one or more wireless communication elements (e.g., pay with the default card as an alternative). In some embodiments, the device simultaneously displays an indication of the default payment account and another payment account to indicate to the user that either payment account can be used for a payment transaction.

[0319] According to some embodiments, simultaneously displaying a visual indication of the default payment account and a visual indication of the first account on the display includes simultaneously displaying a visual indication of the default payment account that is superimposed (e.g., above or below) on the visual indication of the first account on the display. In some embodiments, the visual indication of the first account is at least partially obscured by the visual indication of the default payment account.

[0320] Figure 9 FIG. 900 is a flowchart that illustrates a method 900 for selecting an account such as a loyalty account or a payment account to be displayed according to some embodiments. Method 900 is performed at a device (e.g., 100, 300, 500) having a display and a location sensor. Some operations in method 900 may be combined, the order of some operations may be changed, and some operations may be omitted.

[0321] As described below, method 900 provides an intuitive way to select an account such as a loyalty account or a payment account to be displayed. The method reduces the cognitive burden on the user when selecting an account, thereby creating a more effective human-machine interface. For a battery-powered computing device, enabling the user to select an account faster and more efficiently saves power and increases the time interval between two battery charges.

[0322] At block 902, the electronic device uses the location sensor to detect the current location. At block 904, the electronic device determines whether the current location is associated with a first account.

[0323] At block 904, based on a failure to determine that the current location is associated with an account other than the default payment account, the electronic device displays a visual indication of the default payment account (e.g., 802) on the display.

[0324] At block 906, based on determining that the current location is associated with a first account, the electronic device simultaneously displays a visual indication of the default payment account (e.g., 802) and a visual indication of the first account (e.g., Figure 8B 806 of; Figure 8CThe default payment account and the first account are linked to the electronic device, and the default payment account and the first account are different.

[0325] According to some embodiments, the first account is a payment account. In some embodiments, the first account is a private label account, and the visual indication (e.g., 806) of the first account is an image of a payment card associated with the private label account. In some embodiments, the visual indication (e.g., 806) of the first account is partially displayed behind the visual indication (e.g., 802) of the default account.

[0326] According to some embodiments, the first account is a loyalty account. In some embodiments, the first account is a loyalty account, and the visual indication (e.g., 808) is an image of a loyalty card associated with the loyalty account. In some embodiments, the visual indication (e.g., 808) of the first account is partially displayed behind the visual indication of the default account.

[0327] According to some embodiments, the electronic device receives a request associated with a payment transaction from a contactless payment terminal (e.g., when the device is located in the NFC field of the contactless payment terminal 820). The electronic device determines whether the request includes a request to use payment account information of a first account type corresponding to the first account. Based on determining that the current location is associated with the first account and based on determining that the request includes a request to use payment information of the first account type, the electronic device transmits the payment account information of the first account to the contactless payment terminal using one or more wireless communication elements, wherein the payment account information of the first account enables the contactless payment terminal to participate in the payment transaction. In some embodiments, participating in the payment transaction includes routing information to one or more financial institutions to verify payment credentials and / or receive authorization to complete the transaction. For example, NFC is used to transmit the payment account information to the contactless payment terminal. In some embodiments, participating in the payment transaction includes routing loyalty information to one or more servers for confirmation / authorization of the loyalty account.

[0328] According to some embodiments, an electronic device receives a request associated with a payment transaction from a contactless payment terminal. The electronic device determines that the request includes a request for payment account information using a first account type corresponding to a first account. Based on a failure to determine that the current location is associated with an account other than the default payment account (and based on determining that the request includes a request for payment account information using the first account type), the electronic device transmits, using one or more wireless communication elements, the payment account information of the default payment account to the contactless payment terminal, wherein the payment account information of the default payment account enables the contactless payment terminal to participate in the payment transaction. In some embodiments, participating in the payment transaction includes routing information to one or more financial institutions to verify payment credentials and / or receive authorization to complete the transaction.

[0329] According to some embodiments, a visual indication of the first account is displayed on a visual indication of the default account (e.g., 802), and wherein the visual indication of the first account indicates that the first account is enabled to be selected by the device for a payment transaction without additional user input.

[0330] According to some embodiments, the electronic device receives an input (e.g., user input) for requesting to enable the device for a payment transaction before using a location sensor to detect the current location.

[0331] According to some embodiments, using a location sensor to detect the current location is performed in response to receiving an input for requesting to enable the device for a payment transaction.

[0332] According to some embodiments, determining whether the current location is associated with the first account is performed in response to receiving an input for requesting to enable the device for a payment transaction (e.g., the user double-taps on a hardware button 508 of the device, preparing the device for NFC payment and / or accessing an electronic wallet).

[0333] According to some embodiments, a failure to determine that the current location is associated with an account other than the default payment account occurs when the device fails to determine that the current location is associated with the first account before enabling the electronic device to participate in a transaction using the default payment account via one or more wireless communication elements.

[0334] In some embodiments, if the electronic device is worn on the user's wrist, the electronic device can detect that the user is viewing the electronic device by detecting the user lifting or turning their wrist to move the electronic device into a viewing position. The electronic device can detect that the user is no longer viewing the device by detecting the user lowering their wrist. As used herein, a viewing position is an electronic device position where the user can view the display of the electronic device.

[0335] According to some embodiments, an electronic device receives a request for loyalty account information from a contactless payment terminal, where the first account is a loyalty account. In response to receiving the request for loyalty account information, based on a failure to determine that the current location is associated with an account other than the default payment account (e.g., during the time period between receiving a request to prepare an account and preparing the account), and based on a subsequent determination that the current location is associated with the first account: the electronic device transmits the account information of the first account to the contactless payment terminal via one or more wireless communication elements, and the electronic device transmits the payment account information of the default payment account to the contactless payment terminal via one or more wireless communication elements. In some embodiments, the account information of the first account is provided without regard to whether a representation of the first account is displayed on a display before participating in a payment transaction. In some embodiments, the account information of the first account is provided only when a representation of the first account is displayed on a display before participating in a payment transaction.

[0336] According to some embodiments, an electronic device receives a request associated with a payment transaction from a contactless payment terminal. The electronic device determines that the request includes a request for payment account information using a first account type corresponding to a first account, where the first account is a payment account different from the default payment account. In response to receiving the request for account information, based on a failure to determine that the current location is associated with an account other than the default payment account (e.g., during the time period between receiving a request to prepare an account and preparing the account), and based on a subsequent determination that the current location is associated with the first account: the electronic device forgoes transmitting the account information of the first account to the contactless payment terminal via one or more wireless communication elements, and the electronic device transmits the payment account information of the default payment account to the contactless payment terminal via one or more wireless communication elements. In some embodiments, the account information of the first account is provided only when a representation of the first account is displayed on a display before participating in a payment transaction.

[0337] According to some embodiments, an electronic device receives a request associated with a payment transaction from a contactless payment terminal. Before receiving the request associated with the payment transaction from the contactless payment terminal, a visual indication of a default payment account (e.g., 802) and a visual indication of a first account (e.g., 806 or 808) are simultaneously displayed on a display. The request includes a request for payment account information using a first account type corresponding to the first account (e.g., when the device is placed in the field of the terminal, an NFC-enabled terminal requests a private label credit card of a specific retailer). The first account is a payment account of the first account type. In response to receiving the request for account information and based on a failure to determine that the current location is associated with an account other than the default payment account (e.g., during the time period between receiving the request to prepare the account and preparing the account), and based on subsequently determining that the current location is associated with the first account: the electronic device abandons transmitting the account information of the default payment account to the contactless payment terminal via one or more wireless communication elements, and the electronic device transmits the payment account information of the first account to the contactless payment terminal via one or more wireless communication elements.

[0338] According to some embodiments, based on determining that the current location is associated with the first account, the electronic device receives a failed communication from the contactless payment terminal via one or more wireless communication elements (e.g., the payment is rejected because the payment account is frozen by the bank or has no funds). In response to receiving the failed communication, the electronic device transmits the account information of the default payment account to the contactless payment terminal via one or more wireless communication elements (e.g., pay with the default card as an alternative). In some embodiments, the device simultaneously displays an indication of the default payment account and another payment account to indicate to the user that either payment account can be used for the payment transaction.

[0339] According to some embodiments, simultaneously displaying a visual indication of the default payment account and a visual indication of the first account on the display includes simultaneously displaying a visual indication of the default payment account (e.g., 802) superimposed (e.g., above or below the visual indication of the first account) on the visual indication of the first account (e.g., 806, 808) on the display. In some embodiments, the visual indication of the first account (e.g., 806, 808) is at least partially obscured by the visual indication of the default payment account (e.g., 802).

[0340] It should be noted that the process described above with reference to method 900 (e.g., Figure 9) Details of () also apply to the methods described above and below in a similar manner. For example, methods 700, 1100, 1300, 1500, 1700, and 1900 may include one or more features of the various methods described above with reference to method 900. For example, the electronic wallet, payment account, loyalty account, affordance, and input of methods 700, 1100, 1300, 1500, 1700, and 1900 optionally have one or more features of the electronic device, payment account, loyalty account, affordance, and input of the electronic device described in method 900. For the sake of brevity, these details are not repeated hereinafter.

[0341] Figure 10A - 10E Exemplary techniques and exemplary user interfaces for selecting an account to be displayed, such as a loyalty account or a payment account, from multiple accounts in an electronic wallet are shown in accordance with some embodiments. For example, account information of the selected account may subsequently be transmitted to an NFC-enabled payment terminal for use in a transaction (e.g., when the device is placed in the field of the payment terminal). The technique is performed at an electronic device having a display, a location sensor, and one or more wireless communication elements. The user interfaces in these figures are used to illustrate the processes described below, which include Figure 11 the processes in.

[0342] The electronic device receives an input (e.g., a user input) for requesting to enable the device for a payment transaction (e.g., the user double-clicks on the hardware button 508 of the device to prepare the device for NFC payment).

[0343] In response to receiving the input, the electronic device uses the location sensor to detect the current location (e.g., determines that the device is physically located at a particular retailer or at a particular store of a particular retailer). The electronic device also determines whether a set of one or more payment criteria has been met, where the set of one or more payment criteria includes criteria that are met when a first payment account is associated with the current location (e.g., determines that a particular private label payment account is associated with the retailer).

[0344] As Figure 10A shown, based on determining that the set of one or more payment criteria has not been met, the electronic device displays a visual indication 1002 of the default payment account on the display, where the default payment account is different from the first payment account (e.g., a visual depiction 1002 of a credit card associated with the default payment account and forgoes displaying an indication of the first payment account).

[0345] The device may also display an indication 1006 on the display that other accounts are available, or an indication 1006 of the number of other available accounts. In this example, the indication 1006 includes four pagination points. The first pagination point has a first color that is different from the second color of the second, third, and fourth pagination points. These four pagination points indicate that a total of four accounts are available. The first pagination point is a different color from the other pagination points, indicating that the device is currently displaying information corresponding to the default payment account (e.g., visual indication 1002).

[0346] The device may also display a readiness indication 1004 on the display. The readiness indication 1004 is a visual indication that the device is enabled to participate in a transaction using the default payment account represented by the visual indication 1002. The visual indication 1002 may include: the name of the financial institution associated with the default payment account, "AA Bank", a background design that corresponds to the background design of the payment card associated with the default payment account, at least a portion of the account number associated with the default payment account, and the expiration date associated with the default payment account.

[0347] As Figure 10B shown, based on determining that a set of one or more payment criteria is met, the electronic device displays a visual indication 1008 of a first payment account on the display (and abandons displaying the indication of the default payment account).

[0348] The device may also display a readiness indication 1010 on the display. The readiness indication 1010 is a visual indication that the device is enabled to participate in a transaction using the first payment account represented by the visual indication 1008. The visual indication 1008 may include: the name of the merchant associated with the first payment account, "SHOPCO", a background design that corresponds to the background design of the private label card associated with the first payment account, at least a portion of the account number associated with the first payment account, and the expiration date associated with the first payment account.

[0349] According to some embodiments, based on determining that a set of one or more payment criteria is met, the electronic device enables the electronic device to participate in a transaction using the first payment account via one or more wireless communication elements. Additionally, the electronic device may abandon enabling the electronic device to participate in a transaction using the default payment account.

[0350] According to some embodiments, based on determining that a set of one or more payment criteria is not met, the electronic device enables the electronic device to participate in a transaction using the default payment account via one or more wireless communication elements. Additionally, the electronic device may abandon enabling the electronic device to participate in a transaction using the first payment account.

[0351] According to some embodiments, based on determining that a set of one or more payment criteria is not met, the electronic device forgoes displaying a visual indication of a first payment account on the display (e.g., displays a visual indication of the default payment account instead of the visual indication of the first payment account).

[0352] According to some embodiments, the electronic device includes a touch-sensitive surface. As Figure 10C shown, the electronic device receives one or more inputs in a first direction (e.g., receives one or more left or right swipes via the touch-sensitive surface, or detects a change in the device orientation in the first direction). As Figure 10D shown, in response to receiving the one or more inputs: the electronic device displays on the display a second visual indicator 1012 for identifying (e.g., capable of identifying) a second account that is different from the first payment account and the default payment account. The electronic device enables the electronic device to participate in a transaction using the second account via one or more wireless communication elements (e.g., prepares the device to perform an NFC transaction using the second account and prohibits the device from participating in the transaction using the first account). Thus, when the device presents the payment accounts, the user can provide an input to change to a payment account (e.g., select a payment account from among multiple payment accounts in the electronic wallet of the device).

[0353] According to some embodiments, the electronic device receives a request for account information from a contactless payment terminal (e.g., when the device detects that the user has placed the device within the field of a contactless payment terminal that supports NFC). In response to receiving the request for account information, the electronic device transmits, via one or more wireless communication elements, the account information of the corresponding enabled account to the contactless payment terminal (e.g., any account for which the device is enabled to participate in a payment transaction; any account that is currently being displayed), wherein the account information enables the contactless payment terminal to participate in a payment transaction. In some embodiments, participating in a payment transaction includes routing information to one or more financial institutions to verify payment credentials and / or receive authorization to complete the transaction (e.g., if the account information of a payment account is transmitted to the terminal). For example, the payment account information is transmitted to the contactless payment terminal using NFC. In some embodiments, participating in a payment transaction includes routing loyalty information to one or more servers for confirmation / authorization of a loyalty account (e.g., if the account information of a loyalty account is transmitted to the terminal).

[0354] According to some embodiments, the set of one or more criteria includes criteria that are met when the device is authorized to use (e.g., without user confirmation) the first payment account (e.g., to override the default payment account) to perform a transaction at the current location.

[0355] According to some embodiments, the electronic device determines that the current location is associated with a loyalty account. The electronic device simultaneously displays a visual indication of the loyalty account on the display, along with a corresponding visual indication of a payment account (e.g., along with the visual indication of the default payment account or the first payment account). Thus, if the availability of a suitable loyalty card is detected, the device displays an indication of the default payment card (or private label card), along with an indication of the loyalty card.

[0356] According to some embodiments, the electronic device includes one or more input devices. Before receiving user input for requesting to enable the device for payment transactions: The electronic device receives a request to link a payment account to the electronic device (e.g., manual input, import from a server, or input using the camera sensor of the electronic device). The request includes account information of the payment account (e.g., card number, card expiration date, name on the card). The electronic device links the payment account to the electronic device; (e.g., adds the payment account to the electronic wallet of the electronic device). The electronic device determines that the financial institution associated with the payment account has authorized the payment account for location-based selection without user input. The electronic device receives user input to activate the payment account for location-based selection without user input, as Figure 10E shown.

[0357] As Figure 10E shown, the user can activate the payment account to be used for location-based selection by activating the "Yes" enabling indication 1030. Alternatively, the user can deactivate the activation of the payment account for location-based selection by activating the "No" enabling indication 1032. In some embodiments, the option to activate the payment account for location-based selection is displayed during card setup (e.g., during or just after the card is linked to the electronic device). Alternatively (or in addition), at some time after the payment account has been linked to the electronic device, the financial institution may authorize the payment account for location-based selection (without user input). In this case, a new option may appear in the settings menu of the payment account. Similarly, when the device detects that a payment has been made, the device may display a pop-up notification. The notification indicates that the payment account is now able to be used for location-based selection. Subsequently, the user can choose to activate (or not activate) this feature for location-based selection without user input.

[0358] According to some embodiments, based on determining a set of one or more payment criteria are met, an electronic device enables the electronic device to participate in a transaction using a first payment account via one or more wireless communication elements. The electronic device receives a request associated with a payment transaction from a contactless payment terminal. The electronic device determines whether the request includes a request for payment account information for an account type corresponding to a second payment account different from the first payment account (e.g., when the device is placed in the field of the terminal, an NFC-enabled terminal requests a private label credit card of a particular retailer). Based on determining that the request includes a request for payment information for the second account type, the electronic device provides a notification (e.g., a visual notification, an audio notification, or a tactile notification) requesting authorization to transmit the payment account information of the second account to the contactless payment terminal using one or more wireless communication elements, wherein the payment account information of the second account enables the contactless payment terminal to participate in the payment transaction. Thus, when the device determines that the first payment account is applicable to a particular location, but the contactless payment terminal requests payment using a different payment account, the user receives a notification and is requested to provide authorization to continue the payment transaction using the second payment account.

[0359] Figure 11 FIG. is a flowchart that illustrates a method 1100 for selecting an account to be displayed, such as a loyalty account or a payment account, from multiple accounts in an electronic wallet according to some embodiments. Method 1100 is performed at a device (e.g., 100, 300, 500) having a display and a location sensor. Some operations in method 1100 may be combined, the order of some operations may be changed, and some operations may be omitted.

[0360] As described below, method 1100 provides an intuitive way to select an account. The method reduces the cognitive burden on the user for selecting the account to be displayed and / or paid, thereby creating a more efficient human-machine interface. For a battery-powered computing device, enabling the user to select an account faster and more efficiently saves power and increases the time interval between two battery charges.

[0361] At block 1102, the electronic device receives an input (e.g., a user input) for requesting to enable the device to perform a payment transaction (e.g., the user double-clicks on a hardware button 508 of the device to prepare the device for NFC payment).

[0362] At block 1104, in response to receiving the input, the technique proceeds to block 1106. At block 1106, the electronic device uses the location sensor to detect the current location (e.g., determines that the device is physically located at a particular retailer or at a particular store of a particular retailer).

[0363] At block 1108, the electronic device determines whether a set of one or more payment criteria has been met, where the set of one or more payment criteria includes criteria that are met when a first payment account is associated with the current location (e.g., determining that a specific private label payment account is associated with a retailer).

[0364] At block 1110, based on determining that the set of one or more payment criteria has not been met, the electronic device displays a visual indication of a default payment account (e.g., 1002) on the display, where the default payment account is different from the first payment account (e.g., a visual depiction of a credit card associated with the default payment account, and forgoes displaying an indication of a specific payment account).

[0365] According to some embodiments, at block 1112, based on determining that the set of one or more payment criteria has not been met, the electronic device enables the electronic device to participate in a transaction using the default payment account via one or more wireless communication elements.

[0366] At block 1114, based on determining that the set of one or more payment criteria has been met, the electronic device displays a visual indication of the first payment account (e.g., 1008) on the display (and forgoes displaying an indication of the default payment account).

[0367] According to some embodiments, at block 1116, based on determining that the set of one or more payment criteria has been met, the electronic device enables the electronic device to participate in a transaction using the first payment account via one or more wireless communication elements.

[0368] According to some embodiments, based on determining that the set of one or more payment criteria has not been met, the electronic device forgoes displaying a visual indication of the first payment account (e.g., 1008) on the display (e.g., displays a visual indication of the default payment account instead of the visual indication of the first payment account).

[0369] According to some embodiments, the electronic device includes a touch-sensitive surface. The electronic device receives one or more inputs in a first direction (e.g., receives one or more left or right swipes via the touch-sensitive surface, or detects a change in the device orientation in the first direction). In response to receiving the one or more inputs, the electronic device displays a second visual indicator (e.g., 1012) on the display for identifying a second account that is different from the first payment account and the default payment account, and the electronic device enables the electronic device to participate in a transaction using the second account via one or more wireless communication elements (e.g., prepares the device to make an NFC transaction using the second account and prohibits the device from participating in a transaction using the first account).

[0370] According to some embodiments, an electronic device receives a request for account information from a contactless payment terminal. In response to receiving the request for account information, the electronic device transmits account information of a corresponding enabled account to the contactless payment terminal via one or more wireless communication elements, wherein the account information enables the contactless payment terminal to participate in a payment transaction. In some embodiments, participating in a payment transaction includes routing information to one or more financial institutions to verify payment credentials and / or receive authorization to complete the transaction (e.g., if account information of a payment account is transmitted to the terminal).

[0371] According to some embodiments, a set of one or more criteria includes criteria that are satisfied when the device is authorized to use (e.g., without user confirmation) a first payment account (e.g., to override a default payment account) to conduct a transaction at a current location.

[0372] According to some embodiments, the electronic device determines that a current location is associated with a loyalty account. The electronic device simultaneously displays a visual indication of the loyalty account on a display, along with a corresponding visual indication of a payment account (e.g., along with a visual indication of a default payment account or a first payment account). Thus, if the availability of an appropriate loyalty card is detected, the device displays an indication of the default payment card (or private label card), along with an indication of the loyalty card.

[0373] According to some embodiments, the electronic device includes one or more input devices. Before receiving user input to request enabling the device for payment transactions: The electronic device receives a request to link a payment account to the electronic device (e.g., manual entry, import from a server, or entry using a camera sensor of the electronic device). The request includes account information of the payment account (e.g., card number, card expiration date, name on the card). The electronic device links the payment account to the electronic device; (e.g., adds the payment account to an electronic wallet of the electronic device). The electronic device determines that a financial institution associated with the payment account has authorized the payment account for location-based selection without user input. The electronic device receives user input to activate the payment account for location-based selection without user input.

[0374] According to some embodiments, based on determining a set of one or more payment criteria are met, an electronic device enables the electronic device to participate in a transaction using a first payment account via one or more wireless communication elements. The electronic device receives a request associated with a payment transaction from a contactless payment terminal. The electronic device determines whether the request includes a request for payment account information for an account type corresponding to a second payment account different from the first payment account (e.g., when the device is placed in the field of the terminal, an NFC-enabled terminal requests a private label credit card of a particular retailer). Based on determining that the request includes a request for payment information for the second account type, the electronic device provides a notification (e.g., a visual notification, an audio notification, or a tactile notification) that requests authorization to transmit the payment account information of the second account to the contactless payment terminal using one or more wireless communication elements, wherein the payment account information of the second account enables the contactless payment terminal to participate in the payment transaction. Thus, when the device determines that the first payment account is applicable to a particular location, but the contactless payment terminal requests payment using a different payment account, the user receives a notification and is requested to provide authorization to continue the payment transaction using the second payment account.

[0375] It should be noted that the details of the processes described above with reference to method 1100 (e.g., Figure 11 ) also apply in a similar manner to the methods described above and below. For example, methods 700, 900, 1300, 1500, 1700, and 1900 may include one or more features of the various methods described above with reference to method 1100. For example, the electronic wallet, payment account, loyalty account, affordances, and inputs of methods 700, 900, 1300, 1500, 1700, and 1900 optionally have one or more features of the electronic device, payment account, loyalty account, affordances, and inputs of method 1100. For the sake of brevity, these details are not repeated below.

[0376] Figure 12A - 12D Exemplary techniques and exemplary user interfaces are shown in accordance with some embodiments for transmitting account information for an account selected from a plurality of accounts in an electronic wallet. The technique is performed at an electronic device having a display and one or more wireless communication elements (e.g., one or more wireless antennas such as NFC antennas, WiFi antennas). The user interfaces in these figures are used to illustrate the processes described below, which include Figure 13 the processes in.

[0377] The electronic device receives an input (e.g., a user input) for requesting to enable the device for a payment transaction (e.g., the user double-clicks a hardware button of the device to prepare the device for NFC payment). In Figure 12AAt, in response to receiving an input, the electronic device displays on the display a payment instruction (e.g., 1202) representing a plurality of payment accounts including a first payment account and a second payment account (e.g., displaying a "smart selection" instruction that does not identify a specific payment account).

[0378] As Figure 12B shown, the user places the electronic device 500 in the NFC field of the contactless payment terminal 1220. The electronic device receives a request for account information corresponding to a payment transaction via one or more wireless communication elements (e.g., received from the contactless payment terminal 1220).

[0379] In response to receiving a request for account information corresponding to a payment transaction, based on determining that the payment criteria for the first payment account have been met (e.g., the first payment account is associated with the current location of the device), the electronic device transmits the account information of the first payment account via one or more wireless communication elements without transmitting the account information of the second payment account (and, optionally, not transmitting the payment account information of any other payment account associated with the payment instruction other than the first payment account). In response to receiving a request for account information corresponding to a payment transaction, based on determining that the payment criteria for the second payment account have been met (e.g., the second payment account is associated with the current location of the device), the electronic device transmits the account information of the second payment account via one or more wireless communication elements without transmitting the account information of the first payment account (and, optionally, not transmitting the payment account information of any other payment account associated with the payment instruction other than the second payment account). Accordingly, the user can see a visual indication that the "smart selection" feature has been selected. When the device detects an attempt to make a payment, the electronic device transmits the account information of the appropriate account.

[0380] According to some embodiments, the electronic device is configured to enable payment using one of a default payment account and a plurality of non - default payment accounts (e.g., payment accounts that are used only when the payment criteria corresponding to the respective payment accounts are met). Based on determining that the payment criteria have not been met for any non - default payment account, the electronic device transmits the account information of the default payment account via one or more wireless communication elements without transmitting the account information of the non - default payment accounts.

[0381] According to some embodiments, the payment criteria include criteria determined based on the current location associated with the electronic device. For example, the criteria are met when the electronic device is within a determined geographical area. Another example is that the criteria are not met when the electronic device is not within the determined geographical area.

[0382] According to some embodiments, as Figure 12AAs shown, the payment instruction 1202 indicating multiple payment accounts does not include an instruction for the first payment account and does not include an instruction for the second payment account. For example, there is no instruction on the display for indicating the first payment account or the second payment account. The payment instruction 1202 indicating multiple payment accounts does not look like a credit card and does not look like an instruction for the first payment account or the second payment account. Therefore, the user can understand at a glance that the device is in a special operation mode.

[0383] According to some embodiments, the multiple payment accounts only include the following payment accounts: for which the electronic device has received user input for activating location-based selection without user input.

[0384] According to some embodiments, the multiple payment accounts only include the following payment accounts: for which the financial institution associated with the payment account authorizes the corresponding payment account to be selected based on location without user input.

[0385] According to some embodiments, the scenario selection operation mode is represented as an optional payment option, in which the device selects which payment account among the multiple payment accounts to use for a payment transaction based on the scenario. In some embodiments, the device receives a selection of the optional payment option and, in response to the selection of the optional payment option, switches to the scenario selection operation mode.

[0386] In Figure 12C According to some embodiments, the electronic device includes a touch-sensitive surface. For example, before making a payment as shown in Figure 12B , the electronic device receives one or more inputs (e.g., user input) in a first direction (e.g., receives one or more left or right swipes via the touch-sensitive surface, or receives a change in the device orientation in the first direction). As shown in Figure 12C , the electronic device can display an animation that includes causing the payment instruction 1202 to turn away from the display. In response to receiving the one or more inputs, the electronic device replaces the payment instruction 1202 indicating multiple payment accounts on the display with a second visual indicator 1230 different from the payment instruction 1202 indicating multiple payment accounts, where the second visual selection indicator identifies a third payment account different from the first payment account and the second payment account. In response to receiving the one or more inputs, the electronic device enables the electronic device to participate in a transaction using the third payment account via one or more wireless communication elements. (e.g., prepares the device to perform an NFC transaction using the second account and prohibits the device from participating in a transaction using the first account). Therefore, the user can select a specific payment account. Once the user selects a specific payment account, the user can use that account to make a payment, as shown in Figure 12B .

[0387] According to some embodiments, a payment instruction 1202 representing multiple payment accounts is different from a visual indicator (e.g., 1230) of an individual payment account among the multiple payment accounts. For example, the payment instruction 1202 includes an identification without a surrounding card, while all other payment accounts are represented by a card image (e.g., visual indicator 1230), or the payment instruction is accompanied by text that indicates that the payment instruction represents a scenario selection among multiple different payment accounts (e.g., "automatic selection").

[0388] Figure 13 is a flowchart showing a method for transmitting account information of an account selected from multiple accounts in an electronic wallet according to some embodiments. Method 1300 is performed at an electronic device (e.g., 100, 300, 500) having a display and one or more wireless communication elements. Some operations in method 1300 may be combined, the order of some operations may be changed, and some operations may be omitted.

[0389] As described below, method 1300 provides an intuitive way to transmit account information of an account selected from multiple accounts in an electronic wallet. The method reduces the cognitive burden on the user when selecting an account for payment, thereby creating a more effective human-machine interface. For battery-powered computing devices, enabling the user to select an account faster and more efficiently saves power and increases the time interval between two battery charges.

[0390] At block 1302, the electronic device receives an input (e.g., user input) for requesting to enable the device for a payment transaction (e.g., the user double-clicks on the hardware button 508 of the device to prepare the device for an NFC payment).

[0391] At block 1304, in response to receiving the input, the electronic device displays on the display a payment instruction (e.g., 1202) that represents multiple payment accounts including a first payment account and a second payment account (e.g., displays a "smart selection" indicator that does not identify a specific payment account).

[0392] At block 1306, the electronic device receives a request for account information corresponding to the payment transaction (e.g., received from the contactless payment terminal 1220) via one or more wireless communication elements.

[0393] At block 1308, in response to receiving a request for account information corresponding to a payment transaction, the method further proceeds to blocks 1310-1312. At block 1310, based on determining that the payment criteria for the first payment account are met, the electronic device transmits the account information of the first payment account via one or more wireless communication elements without transmitting the account information of the second payment account (and, optionally, without transmitting the payment account information of any other payment account associated with the payment instruction other than the first payment account).

[0394] At block 1312, based on determining that the payment criteria for the second payment account are met, the account information of the second payment account is transmitted via one or more wireless communication elements without transmitting the account information of the first payment account (and, optionally, without transmitting the payment account information of any other payment account associated with the payment instruction other than the second payment account).

[0395] According to some embodiments, the electronic device is configured to enable payments using a default payment account and one of a plurality of non-default payment accounts (e.g., a payment account that is used only when the payment criteria for the payment account are met). Based on determining that the payment criteria have not been met for any non-default payment account, the electronic device transmits the account information of the default payment account via one or more wireless communication elements without transmitting the account information of the non-default payment account.

[0396] According to some embodiments, the payment criteria include criteria determined based on the current location associated with the electronic device. For example, the criteria are met when the electronic device is within a determined geographical area. As another example, the criteria are not met when the electronic device is not within the determined geographical area.

[0397] According to some embodiments, the payment instruction (e.g., 1202) representing the plurality of payment accounts does not include an indication of the first payment account and does not include an indication of the second payment account.

[0398] According to some embodiments, the plurality of payment accounts includes only payment accounts for which the electronic device has received user input for activating location-based selection without user input.

[0399] According to some embodiments, the plurality of payment accounts includes only payment accounts for which the financial institution associated with the payment account authorizes the corresponding payment account for location-based selection without user input.

[0400] According to some embodiments, the scenario selection operation mode is presented as an optional payment option in which the device selects, based on the scenario, which payment account among a plurality of payment accounts to use for a payment transaction. In some embodiments, the device receives a selection of the optional payment option and, in response to the selection of the optional payment option, switches to the scenario selection operation mode.

[0401] According to some embodiments, an electronic device includes a touch-sensitive surface. The electronic device receives one or more inputs in a first direction (e.g., user input) (e.g., one or more left swipes or right swipes via the touch-sensitive surface, or a change in the orientation of the device in the first direction). In response to receiving the one or more inputs, the electronic device replaces a payment indicator (e.g., 1202) representing a plurality of payment accounts on a display with a second visual indicator (e.g., 1230) different from the payment indicator (e.g., 1202) representing the plurality of payment accounts, where the second visual selection indicator identifies a third payment account different from a first payment account and a second payment account. In response to receiving the one or more inputs, the electronic device enables the electronic device to participate in a transaction using the third payment account via one or more wireless communication elements. Thus, a user can select a particular payment account.

[0402] According to some embodiments, a payment indicator (e.g., 1202) representing a plurality of payment accounts is different from a visual indicator (e.g., 1230) of an individual payment account among the plurality of payment accounts.

[0403] It should be noted that the details of the processes described above with reference to method 1300 (e.g., Figure 13 ) also apply in a similar manner to the methods described above and below. For example, methods 700, 900, 1100, 1500, 1700, and 1900 may include one or more features of the various methods described above with reference to method 1300. For example, the electronic wallet, payment accounts, loyalty accounts, affordances, and inputs of methods 700, 900, 1100, 1500, 1700, and 1900 optionally have one or more features of the electronic device, payment accounts, loyalty accounts, affordances, and inputs of the electronic device described in method 1300. For the sake of brevity, these details are not repeated below.

[0404] Figure 14A to Figure 14EIllustrates an exemplary method and an exemplary user interface for receiving a selection of an account from multiple accounts in an electronic wallet. For example, account information of the selected account may then be transmitted to an NFC-enabled payment terminal for use in a transaction (e.g., when the device is placed in the field of the payment terminal). The method is performed at an electronic device having a display, a touch-sensitive surface configured to detect the intensity of contact, and one or more wireless communication elements. The user interfaces in these figures are used to illustrate the processes described below, which include Figure 15 the processes in

[0405] The electronic device receives a first input (e.g., user input at a hardware button). For example, the user double-clicks the mechanical button or the capacitive button 508 of the device.

[0406] As Figure 14A shown, in response to receiving the first input, the electronic device displays a first user interface on the display (e.g., Figure 14A the user interface of Figure 14A ), where the first user interface includes a first visual indicator 1402 for identifying a payment card associated with multiple payment accounts, and a second visual identifier 1406 for identifying a first payment account (e.g., a savings account) among the multiple payment accounts of the payment card. As

[0407] shown, the second visual indicator 1406 may include "Savings Account" to indicate that the savings account of the payment card is active or selected. The first visual indicator 1402 may include one or more of the following: the name of the financial institution providing the payment account, the account number, the expiration date, the background design.

[0407] The electronic device enables the electronic device to participate in a payment transaction using the first payment account via one or more wireless communication elements. For example, once enabled for the first payment account, the user can place the electronic device in the field of a contactless payment terminal to make an NFC payment using the first payment account. In Figure 14A , the ready indicator 1404 is a visual indication that the device has been enabled to participate in a payment transaction using the first payment account.

[0408] As Figure 14B shown, the electronic device detects a first contact on the touch-sensitive surface. The electronic device determines whether the characteristic intensity of the first contact is higher than an intensity threshold.

[0409] As Figure 14C and Figure 14D shown, based on determining that the characteristic intensity of the first contact is higher than the intensity threshold (e.g., pressing hard), the electronic device displays a second user interface on the display, where the second user interface enables selection between different payment accounts represented by the first visual indicator. For example, pressing hard may result in Figure 14Ddisplay of the user interface. For another example, pressing hard can obtain Figure 14C display, and then, at Figure 14C the activation of the affordance representing 1412 at the user interface of Figure 14D display of the user interface.

[0410] The user can access the user interface in multiple ways, and the user interface allows selection from multiple payment accounts of a payment card. One method is to enable the electronic device to participate in a payment transaction (e.g., using an electronic wallet application), such that a first visual indicator is displayed when the device is in a payment mode, as discussed above. Another method is to access the settings or details of a specific payment account from the electronic wallet application, such that the first visual indicator is displayed when the device is not in a payment mode (e.g., not enabled to participate in a payment transaction via one or more wireless communication components). When the user interface is displayed (and not in a payment mode), the device detects a contact on the touch-sensitive surface; the device determines whether the characteristic intensity of the contact is higher than an intensity threshold; and based on determining that the characteristic intensity of the contact is higher than the intensity threshold (e.g., pressing hard), the device displays an additional user interface on the display, wherein the additional user interface enables selection between different payment accounts represented by the first visual indicator. These two methods (via payment mode and non-payment mode) both allow the user to select from multiple payment accounts of a payment card through an account selection interface.

[0411] As Figure 14C shown, according to some embodiments, the second user interface includes a payment account selection affordance representing 1412. The electronic device detects a second contact on the touch-sensitive surface at a position corresponding to the payment account selection affordance representing 1412. As Figure 14D shown, in response to detecting the second contact, the electronic device displays a third user interface 1418 on the display, wherein the third user interface 1418 includes one or more account affordances (e.g., 1420, 1422, 1424) corresponding to at least some of the multiple payment accounts. The electronic device detects a third contact at a position associated with the account affordance 1424 among the one or more account affordances (e.g., 1420, 1422, 1424), wherein the account affordance 1424 corresponds to a second payment account (e.g., a credit account) among the multiple payment accounts, and the second payment account is different from the first payment account. In some examples, when the electronic device detects the activation of a cancel affordance 1426, the electronic device displays Figure 14C the user interface of

[0412] As Figure 14E shown, in response to detecting the third contact, the electronic device displays a fourth user interface (e.g., Figure 14Eof the user interface), where the fourth user interface includes: a first visual indicator 1402 for identifying a payment card associated with a plurality of payment accounts (e.g., the payment card has not changed), and a third visual identifier 1430 for identifying a second payment account among the plurality of payment accounts of the payment card (e.g., a credit account different from a checking account). For example, the third visual indicator 1430 indicates "credit account" to indicate that the credit account of the payment card is active or selected. In response to detecting the third contact, the electronic device also enables the electronic device to participate in a payment transaction using the second payment account via one or more wireless communication elements (and prohibits the electronic device from participating in the payment transaction using the first payment account). For example, the user can place the electronic device in the field of a contactless payment terminal to make an NFC payment using the first payment account. For example, the ready indication 14032 is a visual indication that the device has been enabled to participate in a payment transaction using the second payment account.

[0413] According to some embodiments, based on determining that the characteristic intensity of the first contact is below an intensity threshold (e.g., a light press), the electronic device maintains the display of the first visual indicator 1402 (and optionally the second visual indicator 1406) without displaying the second user interface on the display.

[0414] According to some embodiments, one or more account enabling representations 1420, 1422, 1424 include a plurality of account enabling representations.

[0415] According to some embodiments, the visual indicator of the currently selected payment account (e.g., 1420, 1422, 1424) is highlighted (e.g., different color, with a checkmark 1428, etc.) on the second user interface.

[0416] According to some embodiments, detecting the second contact includes determining that the characteristic intensity of the second contact is not higher than the intensity threshold (e.g., it is not a hard press).

[0417] According to some embodiments, the second user interface includes a payment account deletion enabling representation 1410. The electronic device detects the activation of the payment account deletion enabling representation 1410. In response to detecting the activation of the payment account deletion enabling representation 1410, the electronic device removes (e.g., unlinks from the electronic device) the plurality of payment accounts of the payment card from the electronic wallet of the device.

[0418] According to some embodiments, the payment account deletion enabling representation 1410 includes one or more visual features that distinguish the payment account deletion enabling representation from the payment account selection enabling representation 1412. For example, the enabling representations have different shapes, different fill colors, or different text, which helps prevent the user from misidentifying one enabling representation as another.

[0419] According to some embodiments, when displaying a fourth user interface on a display, the electronic device detects a swipe input (e.g., a horizontal swipe input) on the touch-sensitive surface. In some embodiments, the swipe input has a characteristic intensity below an intensity threshold. In response to detecting the swipe input, the electronic device displays a fifth user interface, where the fifth user interface includes a fourth visual indicator for identifying a second payment card different from the payment card. Thus, the user can swipe to change the payment card.

[0420] According to some embodiments, the first user interface, the second user interface, the third user interface, and the fourth user interface are user interfaces of a single electronic wallet application that includes multiple payment accounts associated with a user of the electronic device.

[0421] According to some embodiments, the electronic device receives a request for account information from a contactless payment terminal. In response to receiving the request for account information, the electronic device transmits the account information of the second payment account to the contactless payment terminal via one or more wireless communication elements, where the account information enables the contactless payment terminal to participate in a payment transaction. In some embodiments, participating in a payment transaction includes routing information to one or more financial institutions to verify payment credentials and / or receive authorization to complete the transaction. For example, NFC is used to transmit payment account information to the contactless payment terminal.

[0422] Figure 15 is a flowchart showing a method for receiving a selection of an account from multiple accounts in an electronic wallet according to some embodiments. Method 1500 is performed at a device (e.g., 100, 300, 500) having a display, a touch-sensitive surface configured to detect the intensity of contact, and one or more wireless communication elements. Some operations in method 1500 may be combined, the order of some operations may be changed, and some operations may be omitted.

[0423] As described below, method 1500 provides an intuitive way to receive a selection of an account from multiple accounts in an electronic wallet. The method reduces the cognitive burden on the user when selecting an account, thereby creating a more efficient human-machine interface. For a battery-powered computing device, enabling the user to select an account faster and more efficiently saves power and increases the time interval between two battery charges.

[0424] At block 1502, the electronic device receives a first input (e.g., user input at a hardware button). For example, the user double-clicks a mechanical button or a capacitive button of the device.

[0425] At block 1504, in response to receiving a first input, the technique proceeds to 1506. At block 1506, the electronic device displays a first user interface (e.g., Figure 14A 's user interface) on the display, where the first user interface includes: a first visual indicator (e.g., 1402) for identifying a payment card associated with multiple payment accounts, and a second visual identifier (e.g., 1406) for identifying a first payment account among the multiple payment accounts of the payment card.

[0426] At block 1506, the electronic device enables the electronic device to participate in a payment transaction using the first payment account via one or more wireless communication elements. At block 1508, the electronic device detects a first contact on the touch-sensitive surface.

[0427] At block 1510, the electronic device determines whether the characteristic intensity of the first contact is higher than an intensity threshold.

[0428] At block 1512, based on determining that the characteristic intensity of the first contact is higher than the intensity threshold (e.g., pressing hard), the electronic device displays a second user interface (e.g., Figure 14D 1418 in Figure 14C or the user interface in

[0429] on the display, where the second user interface enables selection between different payment accounts represented by the first visual indicator. According to some embodiments, the second user interface includes a payment account selection enabling representation (e.g., 1412). The electronic device detects a second contact on the touch-sensitive surface at a location corresponding to the payment account selection enabling representation (e.g., 1412). In response to detecting the second contact, the electronic device displays a third user interface (e.g., 1418) on the display, where the third user interface (e.g., 1418) includes one or more account enabling representations (e.g., 1420, 1422, 1424) corresponding to at least some of the multiple payment accounts. The electronic device detects a third contact at a location associated with an account enabling representation (e.g., 1424) among the one or more account enabling representations (e.g., 1420, 1422, 1424), where the account enabling representation (e.g., 1424) corresponds to a second payment account among the multiple payment accounts, and the second payment account is different from the first payment account.

[0430] In response to detecting the third contact, the electronic device displays a fourth user interface (e.g., Figure 14Ethe user interface), wherein the fourth user interface includes: a first visual indicator (e.g., 1402) for identifying a payment card associated with multiple payment accounts, and a third visual identifier (e.g., 1430) for identifying a second payment account among the multiple payment accounts of the payment card. In response to detecting the third contact, the electronic device enables the electronic device to participate in a payment transaction using the second payment account via one or more wireless communication elements (and prohibits the electronic device from participating in the payment transaction using the first payment account).

[0431] According to some embodiments, based on determining that the characteristic intensity of the first contact is lower than the intensity threshold (e.g., a light press), the electronic device maintains the display of the first visual indicator (e.g., 1402) (and optionally the second visual indicator 1406) without displaying the second user interface on the display.

[0432] According to some embodiments, one or more account enabling representations (e.g., 1420, 1422, 1424) include multiple account enabling representations.

[0433] According to some embodiments, the visual indicator (e.g., 1420, 1422, 1424) of the currently selected payment account is highlighted (e.g., different color, with a checkmark 1428, etc.) on the second user interface.

[0434] According to some embodiments, detecting the second contact includes determining that the characteristic intensity of the second contact is not higher than the intensity threshold (e.g., it is not a hard press).

[0435] According to some embodiments, the second user interface includes a payment account deletion enabling representation (e.g., 1410). The electronic device detects the activation of the payment account deletion enabling representation (e.g., 1410). In response to detecting the activation of the payment account deletion enabling representation (e.g., 1410), the electronic device removes (e.g., unlinks from the electronic device) the multiple payment accounts of the payment card from the electronic wallet of the device.

[0436] According to some embodiments, the payment account deletion enabling representation (e.g., 1410) includes one or more visual features that distinguish the payment account deletion enabling representation from the payment account selection enabling representation (e.g., 1412).

[0437] According to some embodiments, when the fourth user interface is displayed on the display, the electronic device detects a swipe input (e.g., a horizontal swipe input) on the touch-sensitive surface. In some embodiments, the swipe input has a characteristic intensity lower than the intensity threshold. In response to detecting the swipe input, the electronic device displays a fifth user interface, wherein the fifth user interface includes a fourth visual indicator for identifying a second payment card different from the payment card.

[0438] According to some embodiments, the first user interface, the second user interface, the third user interface, and the fourth user interface are user interfaces of a single electronic wallet application that includes multiple payment accounts associated with a user of an electronic device.

[0439] According to some embodiments, the electronic device receives a request for account information from a contactless payment terminal. In response to receiving the request for account information, the electronic device transmits account information of a second payment account to the contactless payment terminal via one or more wireless communication elements, where the account information enables the contactless payment terminal to participate in a payment transaction. In some embodiments, participating in a payment transaction includes routing information to one or more financial institutions to verify payment credentials and / or receive authorization to complete the transaction. For example, NFC is used to transmit payment account information to the contactless payment terminal.

[0440] It should be noted that the details of the processes described above with reference to method 1500 (e.g., Figure 15 ) also apply to the methods described above and below in a similar manner. For example, methods 700, 900, 1100, 1300, 1700, and 1900 may include one or more features of the various methods described above with reference to method 1500. For example, the electronic wallet, payment account, loyalty account, affordance, and input of methods 700, 900, 1100, 1300, 1700, and 1900 optionally have one or more features of the electronic device, payment account, loyalty account, affordance, and input of the electronic device described in method 1500. For the sake of brevity, these details are not repeated below.

[0441] Figure 16A to Figure 16G Exemplary methods and exemplary user interfaces for linking a payment account to one or more electronic devices are shown. The method is performed at a first electronic device having a display and one or more wireless communication elements (e.g., one or more wireless antennas, such as an AFC antenna, a WiFi antenna). The user interfaces in these figures are used to illustrate the processes described below, which include Figure 17 the processes in.

[0442] A user may want to add a payment account to two devices that are paired with each other, such as the user's phone and the user's smartwatch. The following specification describes a method that links a payment account to the user's first device (e.g., phone) and the user's second device (e.g., smartwatch) in a convenient and efficient manner.

[0443] In Figure 16AIn [description], a first electronic device displays a user interface that includes three affordance representations for linking a payment account to the first electronic device. For example, when affordance representation 1606 is activated, it allows importing payment account details from a remote server; when affordance representation 1608 is activated, it allows manual entry of payment account details (e.g., using the displayed keyboard); when affordance representation 1610 is activated, it allows capturing payment account details using the camera sensor of the first electronic device.

[0444] In Figure 16B [description], the first electronic device may display a user interface that includes a payment account indicator 1612 for representing a payment account. The device may prompt the user to enter a security code for the payment account (e.g., a digital card security code such as CVD, CVV, CVC). For example, the device may use a keyboard 1616 to receive input into a security code input field 1614. Thus, the first electronic device receives a first request (e.g., user input) for linking a payment account associated with a payment card (e.g., a credit card) to the first electronic device.

[0445] In response to receiving the first request, the first electronic device initiates a process for linking the payment account to the first electronic device. As Figure 16B shown, during the process of linking the payment account to the first electronic device, the first electronic device receives an input of the security code for the payment card (e.g., a digital card security code such as CVD, CVV, CVC). For example, the user may enter the security code into the security code input field 1614 by using the keyboard 1616. In some embodiments, the first electronic device determines whether further verification is required to link the payment account to the first electronic device. Based on the determination that no further verification is required to link the payment account to the first electronic device, the first electronic device links the payment account to the electronic device. As Figure 16CAs shown, based on determining that further verification is needed to link a payment account to a first electronic device, the first electronic device provides an indication that further verification is needed to link the payment account to the corresponding device (e.g., the first electronic device that displays on a display that approval of linking the payment account is pending, or requests the user to call a phone number for verification). In this example, the user can activate the enablement representation 1618 to receive a phone call to complete the further verification, or alternatively, the user can activate the enablement representation 1620 to receive an email to complete the further verification. In some embodiments, the indication that further verification is needed to link a payment account to a first electronic device includes an alphanumeric visual indicator displayed on the display of the electronic device (e.g., an alphanumeric indicator including "approval pending", which indicates that the further verification step has been initiated without additional user input). For example, a financial institution associated with the payment account (e.g., a bank) may need to confirm the details of the payment account before the payment account is linked to the corresponding device. The verification may or may not require additional user interaction with the financial institution. More details regarding the determination and process for further verification are described in U.S. Provisional Patent Application Serial No. 62 / 004,886, "USER INTERFACE FOR PAYMENTS", which is hereby incorporated by reference in its entirety.

[0446] As Figure 16D shown, after successfully linking a payment account to a first electronic device (e.g., in response to linking the payment account to the first electronic device), the first electronic device simultaneously displays on the display an indication 1638 that the payment account has been successfully linked to the first electronic device and an optional enablement representation 1640 for linking the payment account to a second electronic device different from the first electronic device.

[0447] The first electronic device receives an activation of the optional enablement representation 1640 (e.g., the user activates the optional enablement representation 1640 by tapping on the enablement representation). In response to receiving the activation of the optional enablement representation 1640, the first electronic device initiates a process for linking the payment account to the second electronic device (e.g., as Figure 16E to Figure 16F shown).

[0448] According to some embodiments, the second electronic device is uniquely paired with the first electronic device. For example, the second electronic device has a special relationship with the first electronic device because the second electronic device is only paired with the first electronic device and not with any other device.

[0449] According to some embodiments, a first electronic device is paired with a second electronic device, and the first electronic device is paired with a third electronic device, where the pairing relationship between the first electronic device and the second electronic device is different from the pairing relationship between the first electronic device and the third electronic device.

[0450] According to some embodiments, initiating a process for linking a payment account to a second electronic device includes (the first electronic device) transmitting an indication to a financial institution associated with a payment card to uniquely pair the second electronic device with the first electronic device via one or more wireless communication elements. For example, the first electronic device sends a security token to the financial institution, indicating that the second electronic device is to be uniquely paired with a device linked to the same payment account.

[0451] According to some embodiments, after initiating the linking of a payment account to a second electronic device, the first electronic device receives a confirmation from the second electronic device that the second electronic device has been successfully linked to the payment account. The primary account number of the second electronic device linked to the payment account (e.g., a digital PAN, DPAN, 16 - digit account number, or other account number, which, for example, cannot be used to complete a manual transaction via a voice call - only for electronic payments via a device) is different from the primary account number of the first electronic device linked to the payment account (e.g., a digital PAN, DPAN, 16 - digit account number, or other account number). As Figure 16G shown, in some examples, the first electronic device displays a confirmation 1636 that the payment account has been linked to the second electronic device.

[0452] According to some embodiments, a first request (e.g., user input) to link a payment account (to the first electronic device) includes the account number of a payment card (e.g., provided by the user via manual input, imported from a server, or input by the user via a camera sensor of the electronic device), and the process for initiating the linking of the payment account to the second electronic device occurs without an additional input of the account number of the payment card (e.g., user input).

[0453] As Figure 16F shown, according to some embodiments, a second request (e.g., to link a payment account to a second electronic device, which initiates the process for linking the payment account to the second electronic device) includes the security code (e.g., a digital card security code such as CVD, CVV, CVC) of a payment card (e.g., input by the user). For example, the user can use a keyboard 1628 to enter the security code into a security code input field 1634.

[0454] According to some embodiments, a first electronic device initiates a process for linking a payment account to a second electronic device.

[0455] According to some embodiments, initiating a process for linking a payment account to a second electronic device includes (the first electronic device) transmitting, via one or more wireless communication elements, (1) the account number of a credit card and (2) a security token for verifying that the payment account was previously linked to the first electronic device to a financial institution associated with the payment card. In some embodiments, the security token is generated by the electronic device after the payment account is linked to the first device. In some embodiments, the security token is received by the electronic device from the financial institution after the payment account is linked to the first device.

[0456] According to some embodiments, initiating a process for linking a payment account to a second electronic device includes: (the first electronic device) determining whether further verification is required to link the payment account to the second electronic device; in accordance with determining that no further verification is required to link the payment account to the second electronic device, (the firs...

Claims

1. A method, comprising: at a first electronic device having a display and one or more wireless communication elements: displaying, on the display, a payment account user interface for a second electronic device associated with the first electronic device, wherein displaying the payment account user interface includes simultaneously displaying: a representation of a first payment account along with status information for the first payment account, the status information for the first payment account indicating that the first payment account is linked to the second electronic device and indicating that the second electronic device is configured to use the first payment account to effect payments; a representation of a second payment account along with status information for the second payment account, the status information for the second payment account indicating that the second payment account is linked to the first electronic device but not linked to the second electronic device; and a link enabling representation associated with the second payment account; when the payment account user interface for the second electronic device is displayed on the display, detecting an activation of the link enabling representation associated with the second payment account; in response to detecting the activation of the link enabling representation, displaying, on the display, a user interface for linking the second payment account to the second electronic device; when the payment account user interface for linking the second payment account to the second electronic device is displayed on the display, receiving a request to initiate linking the second payment account to the second electronic device, wherein the request to initiate linking the second payment account to the second electronic device does not include an input of the account number of the second payment account; and in response to receiving the request to initiate linking the second payment account to the second electronic device, initiating linking the second payment account to the second electronic device.

2. The method according to claim 1, wherein the status information for the first payment account further indicates that the first payment account is linked to the first electronic device.

3. The method according to any one of claims 1-2, wherein the payment account user interface comprises: A representation of one or more accounts associated with a user of the electronic device and not linked to the first electronic device and not linked to the second electronic device.

4. The method according to any one of claims 1-2, wherein the user interface for linking the second payment account to the second electronic device includes a synchronization option for synchronizing payment notifications between the first electronic device and the second electronic device, and the method further includes: detecting an activation of the synchronization option; and in response to detecting the activation of the synchronization option, synchronizing future payment notifications to be presented at both the first electronic device and the second electronic device.

5. The method according to any one of claims 1-2, wherein displaying the payment account user interface includes simultaneously displaying: a first plurality of first representations of payment accounts that are linked to the second electronic device and not linked to the first electronic device; and A second set of second plurality of representations of payment accounts that are linked to the first electronic device and not linked to the second electronic device.

6. The method according to any one of claims 1-2, wherein the payment account user interface includes a second link enabling representation associated with the first payment account, and wherein the first payment account is not linked to the first electronic device, and the method further includes: Detecting an activation of the second link enabling representation; In response to detecting the activation of the second link enabling representation, displaying, on the display, a user interface for linking the first payment account to the first electronic device; And When the user interface for linking the first payment account to the first electronic device is displayed on the display, receiving a request to initiate linking the first payment account to the first electronic device, wherein the request to initiate linking the first payment account to the first electronic device does not include an input of the account number of the first payment account.

7. The method according to any one of claims 1-2, wherein the first electronic device is a handheld device and the second electronic device is a wearable device.

8. The method according to any one of claims 1-2, wherein the first electronic device is a handheld device and the second electronic device is a personal computing device larger than the first electronic device.

9. The method according to any one of claims 1-2, wherein the payment account user interface for the second electronic device associated with the first electronic device further includes: A representation of a third payment account together with status information for the third payment account, the status information for the third payment account indicating that the third payment account is linked to a third electronic device and indicating that the third electronic device is configured to use the third payment account to effect a payment, wherein the third electronic device is different from the first electronic device and the second electronic device.

10. A first electronic device, comprising: A display; One or more wireless communication elements; One or more processors; A memory; And One or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions for: Displaying, on the display, a payment account user interface for a second electronic device associated with the first electronic device, wherein displaying the payment account user interface includes simultaneously displaying: A representation of a first payment account together with status information for the first payment account, the status information for the first payment account indicating that the first payment account is linked to the second electronic device and indicating that the second electronic device is configured to use the first payment account to effect a payment; An identification of a second payment account together with status information for the second payment account, the status information for the second payment account indicating that the second payment account is linked to the first electronic device but not linked to the second electronic device; and a link enabling representation associated with the second payment account; when the payment account user interface for the second electronic device is displayed on the display, detecting an activation of the link enabling representation associated with the second payment account; in response to detecting the activation of the link enabling representation, displaying on the display a user interface for linking the second payment account to the second electronic device; when the payment account user interface for linking the second payment account to the second electronic device is displayed on the display, receiving a request to initiate linking the second payment account to the second electronic device, wherein the request to initiate linking the second payment account to the second electronic device does not include an input of the account number of the second payment account; and in response to receiving the request to initiate linking the second payment account to the second electronic device, initiating linking the second payment account to the second electronic device.

11. The first electronic device according to claim 10, wherein the status information for the first payment account further indicates that the first payment account is linked to the first electronic device.

12. The first electronic device according to any one of claims 10-11, wherein the payment account user interface comprises: A representation of one or more accounts associated with a user of the electronic device, not linked to the first electronic device, and not linked to the second electronic device.

13. The first electronic device according to any one of claims 10-11, wherein the user interface for linking the second payment account to the second electronic device includes a synchronization option for synchronizing payment notifications between the first electronic device and the second electronic device, and the one or more programs further include instructions for: detecting an activation of the synchronization option; and in response to detecting the activation of the synchronization option, synchronizing future payment notifications to be presented at both the first electronic device and the second electronic device.

14. The first electronic device according to any one of claims 10-11, wherein displaying the payment account user interface includes simultaneously displaying: a first set of first plurality of representations of payment accounts linked to the second electronic device and not linked to the first electronic device; and a second set of second plurality of representations of payment accounts linked to the first electronic device and not linked to the second electronic device.

15. The first electronic device according to any one of claims 10-11, wherein the payment account user interface includes a second link enabling representation associated with the first payment account, and wherein the first payment account is not linked to the first electronic device, and the one or more programs further include a program for: detecting an activation of the second link enabling representation; in response to detecting the activation of the second link enabling representation, displaying on the display a user interface for linking the first payment account to the first electronic device; and When a user interface for linking the first payment account to the first electronic device is displayed on the display, receive a request to initiate linking the first payment account to the first electronic device, wherein the request to initiate linking the first payment account to the first electronic device does not include an input of the account number of the first payment account.

16. The first electronic device according to any one of claims 10-11, wherein the first electronic device is a handheld device and the second electronic device is a wearable device.

17. The first electronic device according to any one of claims 10-11, wherein the first electronic device is a handheld device and the second electronic device is a personal computing device larger than the first electronic device.

18. The first electronic device according to any one of claims 10-11, wherein the payment account user interface for the second electronic device associated with the first electronic device further comprises: a representation of a third payment account together with status information for the third payment account, the status information for the third payment account indicating that the third payment account is linked to a third electronic device and indicating that the third electronic device is configured to use the third payment account to effect a payment, wherein the third electronic device is different from the first electronic device and the second electronic device.

19. A computer-readable storage medium storing one or more programs, the one or more programs being configured to be executed by one or more processors of a first electronic device having a display and one or more wireless communication elements, the one or more programs including one or more instructions for: displaying on the display a payment account user interface for a second electronic device associated with the first electronic device, wherein displaying the payment account user interface includes simultaneously displaying: a representation of a first payment account together with status information for the first payment account, the status information for the first payment account indicating that the first payment account is linked to the second electronic device and indicating that the second electronic device is configured to use the first payment account to effect a payment; A representation of a second payment account together with status information for the second payment account, the status information for the second payment account indicating that the second payment account is linked to the first electronic device but not linked to the second electronic device; and a link enabling representation associated with the second payment account; when the payment account user interface for the second electronic device is displayed on the display, detecting an activation of the link enabling representation associated with the second payment account; in response to detecting the activation of the link enabling representation, displaying on the display a user interface for linking the second payment account to the second electronic device; when a payment account user interface for linking the second payment account to the second electronic device is displayed on the display, receiving a request to initiate linking the second payment account to the second electronic device, wherein the request to initiate linking the second payment account to the second electronic device does not include an input of the account number of the second payment account; and In response to receiving the request to initiate linking the second payment account to the second electronic device, initiate linking the second payment account to the second electronic device.

20. The computer-readable storage medium according to claim 19, wherein the status information for the first payment account further indicates that the first payment account is linked to the first electronic device.

21. The computer-readable storage medium according to any one of claims 19-20, wherein the payment account user interface comprises: A representation of one or more accounts associated with a user of the electronic device, not linked to the first electronic device, and not linked to the second electronic device.

22. The computer-readable storage medium according to any one of claims 19-20, wherein the user interface for linking the second payment account to the second electronic device includes a synchronization option for synchronizing payment notifications between the first electronic device and the second electronic device, and the one or more programs further include instructions for: Detecting activation of the synchronization option; and In response to detecting activation of the synchronization option, synchronizing future payment notifications to be presented at both the first electronic device and the second electronic device.

23. The computer-readable storage medium according to any one of claims 19-20, wherein displaying the payment account user interface includes simultaneously displaying: A first set of first pluralities of representations of payment accounts linked to the second electronic device and not linked to the first electronic device; and A second set of second pluralities of representations of payment accounts linked to the first electronic device and not linked to the second electronic device.

24. The computer-readable storage medium according to any one of claims 19-20, wherein the payment account user interface includes a second link-enabled representation associated with the first payment account, and wherein the first payment account is not linked to the first electronic device, and the one or more programs further include instructions for: Detecting activation of the second link-enabled representation; In response to detecting activation of the second link-enabled representation, displaying on the display a user interface for linking the first payment account to the first electronic device; and When the user interface for linking the first payment account to the first electronic device is displayed on the display, receiving a request to initiate linking the first payment account to the first electronic device, wherein the request to initiate linking the first payment account to the first electronic device does not include an input of the account number of the first payment account.

25. The computer-readable storage medium according to any one of claims 19-20, wherein the first electronic device is a handheld device and the second electronic device is a wearable device.

26. The computer-readable storage medium according to any one of claims 19-20, wherein the first electronic device is a handheld device and the second electronic device is a personal computing device larger than the first electronic device.

27. The computer-readable storage medium according to any one of claims 19-20, wherein the payment account user interface for the second electronic device associated with the first electronic device further comprises: a representation of a third payment account together with status information for the third payment account, the status information for the third payment account indicating that the third payment account is linked to a third electronic device and indicating that the third electronic device is configured to use the third payment account to effect payment, wherein the third electronic device is different from the first electronic device and the second electronic device.

28. A first electronic device, comprising: a display; one or more wireless communication elements; and means for performing any one of the methods of claims 1 or 2.

29. A computer program product, the computer program product comprising a computer program which, when executed by a processor of a device, causes the device to perform the method according to any one of claims 1 to 9.

Images