User Interface for Loyalty and Private Label Accounts for Wearable Devices

Abstract

A method, a storage medium, and an electronic device for paying for purchases using an electronic device equipped with an electronic wallet in conjunction with a terminal are provided. [Solution] A method for linking a payment account to one or more electronic devices, wherein a first electronic device receives a first request to link a payment account associated with a payment card to the first electronic device, initiates processing to link the payment account to the first electronic device, and after successfully linking the payment account to the first electronic device, simultaneously displays on a display an indication that the payment account has been successfully linked to the first electronic device and a selectable affordance for linking the payment account to a second electronic device different from the first electronic device, receives activation of the selectable affordance, and in response initiates processing to link the payment account to the second electronic device.

Description

[Technical field]

[0001] (CROSS REFERENCE TO RELATED APPLICATIONS) This application claims priority from U.S. Provisional Patent Application No. 62 / 230,430, filed June 5, 2015, and entitled "USER INTERFACE FOR LOYALTY ACCOUNTS AND PRIVATE LABEL ACCOUNTS FOR A WEARABLE DEVICE," which is incorporated by reference in its entirety for all purposes.

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

[0003] The present disclosure relates generally to computer user interfaces, and more particularly to techniques for computer user interfaces for loyalty and payment accounts. [Background technology]

[0004] In recent years, there has been a great increase in the use of electronic devices to make payments at point-of-sale terminals and over the Internet. Exemplary point-of-sale terminals include near field communication enabled (NFC enabled) terminals, bluetooth enabled terminals, and barcode scanner enabled terminals. Used in conjunction with these exemplary terminals, electronic devices enable users of the electronic devices to make payments for purchases of goods or services, for example. Summary of the Invention

[0005] However, some techniques for linking accounts to electronic devices, selecting accounts to use in a transaction, and transmitting account information during a transaction are generally cumbersome and inefficient. For example, existing techniques use complex and time-consuming user interfaces that may involve multiple key presses or strokes. Existing techniques require more time than necessary, wasting user time and device power. This latter consideration is particularly important in battery-operated devices.

[0006] Thus, the present invention provides an electronic device with faster, more efficient methods and interfaces for linking accounts to the electronic device, selecting accounts to use in a transaction, and transmitting account information during a transaction. Such methods and interfaces optionally complement or replace other methods for performing similar tasks. Such methods and interfaces reduce the cognitive burden on the user and provide a more efficient human-machine interface. Such methods and interfaces may also reduce the number of unnecessary, irrelevant, repetitive, and / or redundant inputs, creating faster, more efficient user interface configurations, which may reduce the number of required inputs, reduce processing power, and reduce the amount of time a user interface needs to be displayed to access and perform a desired function. In the case of battery-operated computing devices, such methods and interfaces may conserve power and increase the time between battery charges.

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

[0008] 1. A method in an electronic device having a display and a position sensor, comprising: detecting a current location using the position sensor; determining whether the current location is associated with a first account; displaying a visual representation of the default payment account on the display in accordance with determining that the current location is not associated with an account other than the default payment account; and simultaneously displaying a visual representation of the default payment account and a visual representation of the first account on the display in accordance with determining that the current location is associated with the first account, 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.

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

[0010] 11. A method, in an electronic device having a display and one or more wireless communication elements, comprising: receiving an input requesting to enable the device for a payment transaction; in response to receiving the input, displaying on the display a payment display 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 the payment transaction; receiving, via the one or more wireless communication elements, the request for account information corresponding to the payment transaction; and in response to receiving the request for account information corresponding to the payment transaction, in accordance with a determination that a payment criterion for the first payment account is satisfied, transmitting, via the one or more wireless communication elements, the account information for the first payment account without transmitting the account information for the second payment account; and in accordance with a determination that a payment criterion for the second payment account is satisfied, transmitting, via the one or more wireless communication elements, the account information for the second payment account without transmitting the account information for the first payment account.

[0011] 11. A method in an electronic device having a display, a touch-sensitive surface configured to detect an intensity of a contact, and one or more wireless communication elements, comprising: receiving a first input; and in response to receiving the first input, displaying a first user interface on the display, the first user interface including a first visual indicator identifying a payment card associated with a plurality of payment accounts and a second visual indicator identifying a first payment account of the plurality of payment accounts of the payment card; enabling the electronic device to conduct 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 above an intensity threshold; and in accordance with a determination that the characteristic intensity of the first contact is above the intensity threshold, displaying a second user interface on the display, the second user interface enabling a selection to be made between different payment accounts represented by the first visual indicators.

[0012] 1. A method comprising: receiving, at a first electronic device having a display and one or more wireless communication elements, a first request to link a payment account associated with a payment card to the first electronic device; initiating a process for linking the payment account to the first electronic device in response to receiving the first request; 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 a selectable affordance for linking the payment account to a second electronic device different from the first electronic device; receiving activation of the selectable affordance; and initiating a process for linking the payment account to the second electronic device in response to receiving the activation of the selectable affordance.

[0013] 1. A method in a first electronic device having a display and one or more wireless communication elements, comprising: 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 the first payment account with status information for the first payment account indicating that the first payment account is linked to the second electronic device and that the second electronic device is configured to enable payments using the first payment account, and a representation of a second payment account with status information for the second payment account indicating that the second payment account is linked to the first electronic device but not to the second electronic device.

[0014] 1. An electronic device comprising: a display; a touch-sensitive surface; means for receiving an input requesting that the device be enabled for a payment transaction; means for, in response to receiving the input requesting that the device be enabled for a payment transaction, displaying on the display a first visual indicator identifying a first account and enabling the electronic device via one or more wireless communication elements; means for receiving one or more swipe inputs in a first direction via the touch-sensitive surface; and means for, in response to receiving the one or more user swipe inputs, displaying on the display a second visual indicator identifying a second account and enabling the electronic device via the one or more wireless communication elements, wherein the first visual indicator is different from the second visual indicator.

[0015] 1. An electronic device comprising: a display; a touch-sensitive surface; means for detecting a current location using a position sensor; means for determining whether the current location is associated with a first account; means for displaying a visual representation of the default payment account on the display in response to the current location not being determined to be associated with an account other than the default payment account; and means for simultaneously displaying a visual representation of the default payment account and a visual representation of the first account on the display in response to a determination that the current location is associated with the first account, 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.

[0016] 1. An electronic device comprising: a display; a touch-sensitive surface; and means for receiving an input requesting to enable the device for a payment transaction; and means for, in response to receiving the input, detecting a current location using a position sensor; determining whether a set of one or more payment criteria are satisfied, the set of one or more payment criteria including criteria that are satisfied when the current location is associated with a first payment account; displaying on the display a visual representation of a default payment account in accordance with a determination that the set of one or more payment criteria are not satisfied, the default payment account being different from the first payment account; and displaying on the display a visual representation of the first payment account in accordance with a determination that the set of one or more payment criteria are satisfied.

[0017] 11. A method for an electronic device comprising: a display; a touch-sensitive surface; means for receiving an input requesting to enable the device for a payment transaction; means for displaying on the display a payment display 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 one or more wireless communication elements, a request for account information corresponding to the payment transaction; and in response to receiving the request for account information corresponding to the payment transaction, transmitting, via the one or more wireless communication elements, the account information for the first payment account without transmitting the account information for the second payment account in accordance with a determination that a payment criterion for the first payment account is satisfied, and transmitting, via the one or more wireless communication elements, the account information for the second payment account without transmitting the account information for the first payment account in accordance with a determination that a payment criterion for the second payment account is satisfied.

[0018] 1. An electronic device comprising: a display; a touch-sensitive surface configured to detect an intensity of a contact; means for receiving a first input; and means for displaying a first user interface on the display in response to receiving the first input, the first user interface including a first visual indicator identifying a payment card associated with a plurality of payment accounts and a second visual indicator identifying a first payment account of the plurality of payment accounts of the payment card; means for enabling the electronic device to conduct a payment transaction using the first payment account via one or more wireless communication elements; means for detecting the first contact on the touch-sensitive surface; means for determining whether a characteristic intensity of the first contact exceeds an intensity threshold; and means for displaying a second user interface on the display in accordance with a determination that the characteristic intensity of the first contact exceeds the intensity threshold, the second user interface enabling a selection to be made between different payment accounts represented by the first visual indicators.

[0019] 1. An electronic device comprising: a display; a touch-sensitive surface; means for receiving a first request to link a payment account associated with a payment card to a 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 an indication of successful linking of the payment account to the first electronic device and a selectable affordance for linking the payment account to a second electronic device different from the first electronic device after successful linking of the payment account to the first electronic device; means for receiving activation of the selectable affordance; and means for initiating a process to link the payment account to the second electronic device in response to receiving activation of the selectable affordance.

[0020] 11. A method comprising: a display; a touch-sensitive surface; and means 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 the first payment account with status information for the first payment account indicating that the first payment account is linked to the second electronic device and that the second electronic device is configured to enable payments using the first payment account, and a representation of the second payment account and status information for the second payment account indicating that the second payment account is linked to the first electronic device but not to the second electronic device.

[0021] 1. 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, and one or more wireless communication elements, the one or more programs, when executed by the one or more processors, cause the electronic device to: receive an input requesting that the device be enabled for a payment transaction; in response to receiving the input requesting that the device be enabled for a payment transaction, display on the display a first visual indicator that identifies a first account and enable the electronic device via the one or more wireless communication elements; receive one or more swipe inputs in a first direction via the touch-sensitive surface; and in response to receiving the one or more user swipe inputs, display on the display a second visual indicator that identifies a second account and enable the electronic device via the one or more wireless communication elements, wherein the first visual indicator is different from the second visual indicator.

[0022] 14. An electronic device comprising: a display; a touch-sensitive surface; one or more wireless communication elements; one or more processors; memory; and one or more programs stored in the memory containing instructions that, when executed by the one or more processors, cause the electronic device to: receive an input requesting that the device be enabled for a payment transaction; in response to receiving the input requesting that the device be enabled for a payment transaction, display on the display a first visual indicator identifying a first account, and enable the electronic device via the one or more wireless communication elements to participate in a transaction using the first account; 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 on the display a second visual indicator identifying a second account, and enable the electronic device via the one or more wireless communication elements to participate in a transaction using the second account, where the first visual indicator is different from the second visual indicator.

[0023] 1. 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 location 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 location using the location sensor; determine whether the current location is associated with a first account; display on the display a visual representation of the default payment account in accordance with determining that the current location is not associated with an account other than the default payment account; and display on the display a visual representation of the default payment account and a visual representation of the first account in accordance with determining that the current location is associated with the first account, 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.

[0024] 1. An electronic device comprising: a display; a location sensor; one or more processors; a memory; and one or more programs stored in the memory including instructions that, when executed by the one or more processors, cause the electronic device to: detect a current location using the location sensor; determine whether the current location is associated with a first account; display on the display a visual representation of the default payment account in accordance with determining that the current location is not associated with an account other than the default payment account; and simultaneously display on the display a visual representation of the default payment account and a visual representation of the first account in accordance with determining that the current location is associated with the first account, 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.

[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, when executed by the one or more processors, cause the electronic device to: receive an input requesting to enable the device for a payment transaction; in response to receiving the input, detect a current location using the position sensor; determine whether a set of one or more payment criteria are satisfied, the set of one or more payment criteria including criteria that are satisfied when the current location is associated with a first payment account; in accordance with a determination that the set of one or more payment criteria are not satisfied, display on the display a visual representation of a default payment account, where 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 are satisfied, display on the display a visual representation of the first payment account.

[0026] 1. An electronic device comprising: a display; a location sensor; one or more processors; a memory; and one or more programs stored in the memory including instructions that, when executed by the one or more processors, cause the electronic device to: receive an input requesting that the device be enabled for payment transactions; and in response to receiving the input, detect a current location using the location sensor; determine whether a set of one or more payment criteria are satisfied, the set of one or more payment criteria including criteria that are satisfied when the current location is associated with a first payment account; in accordance with a determination that the set of one or more payment criteria are not satisfied, display on the display a visual representation of a default payment account, the default payment account being different from the first payment account; and in accordance with a determination that the set of one or more payment criteria are satisfied, display on the display a visual representation of the first payment account.

[0027] 1. 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, when executed by the one or more processors, cause the electronic device to: receive an input requesting to enable the device for a payment transaction; in response to receiving the input, display on the display a payment display 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 the payment transaction; and, in response to receiving the request for account information corresponding to the payment transaction, in accordance with a determination that a payment criterion for the first payment account is satisfied, transmit, via the one or more wireless communication elements, the account information for the first payment account without transmitting the account information for the second payment account, and in accordance with a determination that a payment criterion for the second payment account is satisfied, transmit, via the one or more wireless communication elements, the account information for the second payment account without transmitting the account information for the first payment account.

[0028] 1. An electronic device having a display, one or more wireless communication elements, one or more processors, and a memory, the electronic device, when executed by the one or more processors, causing the electronic device to: receive an input requesting that the device be enabled for a payment transaction; in response to receiving the input, display on the display a payment display 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 the payment transaction; and, in response to receiving the request for account information corresponding to the payment transaction, in accordance with a determination that a payment criterion for the first payment account is satisfied, transmit, via the one or more wireless communication elements, the account information for the first payment account without transmitting the account information for the second payment account; and in accordance with a determination that a payment criterion for the second payment account is satisfied, transmit, via the one or more wireless communication elements, the account information for the second payment account without transmitting the account information for the first payment account.

[0029] 1. 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 an intensity of a contact, and one or more wireless communication elements, the one or more programs, when executed by the one or more processors, causing the electronic device to receive a first input and, in response to receiving the first input, display a first user interface on the display, the first user interface including a first visual indicator identifying a payment card associated with a plurality of payment accounts and a first visual indicator identifying a first one of the plurality of payment accounts of the payment card. a first visual indicator identifying the first payment account; enabling the electronic device to conduct a payment transaction using the first payment account via 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 above an intensity threshold; and displaying a second user interface on the display in accordance with a determination that the characteristic intensity of the first contact is above the intensity threshold, the second user interface enabling a selection to be made between the different payment accounts represented by the first visual indicator.

[0030] 11. An electronic device comprising: a display; a touch-sensitive surface configured to detect an intensity of a contact; one or more wireless communication elements; a memory; and one or more programs stored in the memory 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, the first user interface including a first visual indicator that identifies a payment card associated with a plurality of payment accounts and a second visual indicator that identifies a first payment account of the plurality of payment accounts of the payment card; enable the electronic device to conduct 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 above an intensity threshold; and in accordance with a determination that the characteristic intensity of the first contact is above the intensity threshold, display a second user interface on the display, the second user interface enabling a selection to be made between the different payment accounts represented by the first visual indicators.

[0031] 1. 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 elements, the one or more programs, 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 linking of the payment account to the first electronic device was successful and a selectable affordance for linking the payment account to a second electronic device, different from the first electronic device; receive activation of the selectable affordance; and in response to receiving the activation of the selectable affordance, initiate a process for linking the payment account to the second electronic device.

[0032] 1. A first electronic device comprising: a display; one or more wireless communication elements; one or more processors; a memory; and one or more programs stored in the memory 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 linking of the payment account to the first electronic device was successful and a selectable affordance for linking the payment account to a second electronic device different from the first electronic device; and receive activation of the selectable affordance; and in response to receiving the activation of the selectable affordance, initiate a process for linking the payment account to the second electronic device.

[0033] 1. 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 elements, the one or more programs comprising instructions, when executed by the one or more processors, to cause the first electronic device to display, 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 the first payment account with status information for the first payment account indicating that the first payment account is linked to the second electronic device and that the second electronic device is configured to enable payments using the first payment account, and a representation of the second payment account with status information for the second payment account indicating that the second payment account is linked to the first electronic device but not to the second electronic device.

[0034] 1. A first electronic device comprising: a display; one or more wireless communication elements; one or more processors; a memory; and one or more programs stored in the memory 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 for a second electronic device associated with the first electronic device, where displaying the payment account user interface includes simultaneously displaying a representation of the first payment account with status information for the first payment account indicating that the first payment account is linked to the second electronic device and that the second electronic device is configured to enable payments using the first payment account, and a representation of the second payment account with status information for the second payment account indicating that the second payment account is linked to the first electronic device but not to the second electronic device.

[0035] 1. An electronic device comprising: a touch-sensitive surface unit; a display 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, and the wireless communication unit, the processing unit configured to: receive an input requesting that the device be enabled for a payment transaction; in response to receiving the input requesting that the device be enabled for a payment transaction, enable display on the display of a first visual indicator identifying a first account, and enable the electronic device via the one or more wireless communication elements to participate in a transaction using the first account; 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, enable display on the display of the first visual indicator identifying the first account, and enable the electronic device via the one or more wireless communication elements to participate in a transaction using a second account, where the first visual indicator is different from the second visual indicator.

[0036] 1. 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 configured to: detect a current location using the position sensor unit; determine whether the current location is associated with a first account; enable display of a visual representation of the default payment account on the display unit in accordance with the current location not being determined to be associated with an account other than the default payment account; and enable simultaneous display of a visual representation of the default payment account and a visual representation of the first account on the display unit in accordance with a determination that the current location is associated with the first account, wherein the default payment account and the first account are linked to the electronic device, and the processing unit is configured to:

[0037] 1. 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 configured to: receive an input requesting to enable the device for payment transactions; and in response to receiving the input, detect a current location using the position sensor unit; determine whether a set of one or more payment criteria are satisfied, the set of one or more payment criteria including criteria that are satisfied when the current location is associated with a first payment account; enable, in accordance with a determination that the set of one or more payment criteria are not satisfied, display on the display unit a visual representation of a default payment account, the default payment account being different from the first payment account; and enable, in accordance with a determination that the set of one or more payment criteria are satisfied, display on the display unit a visual representation of the first payment account.

[0038] 1. 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 configured to: receive an input requesting to enable the device for a payment transaction; in response to receiving the input, enable display on the display unit of a payment display 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 the payment transaction; in response to receiving the request for account information corresponding to the payment transaction, in accordance with a determination that a payment criterion for the first payment account is satisfied, transmit, via the one or more wireless communication elements, the account information for the first payment account without transmitting the account information for the second payment account; and in response to a determination that a payment criterion for the second payment account is satisfied, transmit, via the one or more wireless communication elements, the account information for the second payment account without transmitting the account information for the first payment account.

[0039] 11. 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 an intensity of a contact, and the wireless communication unit, the processing unit configured to: receive a first input; in response to receiving the first input, enable display of a first user interface on the display unit, the first user interface including a first visual indicator identifying a payment card associated with a plurality of payment accounts and a second visual indicator identifying a first payment account of the plurality of payment accounts of the payment card; enable the electronic device to conduct a payment transaction using the first payment account via the one or more wireless communication elements; detect the first contact on the touch-sensitive surface unit; determine whether a characteristic intensity of the first contact is above an intensity threshold; and in accordance with a determination that the characteristic intensity of the first contact is above the intensity threshold, enable display of a second user interface on the display unit, the second user interface enabling a selection to be made between the different payment accounts represented by the first visual indicators.

[0040] 1. 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 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 successful linking of the payment account to the first electronic device, enable simultaneous display on the display of a successful linking of the payment account to the first electronic device and a selectable affordance for linking the payment account to a second electronic device different from the first electronic device; and receive activation of the selectable affordance; and in response to receiving the activation of the selectable affordance, initiate a process for linking the payment account to the second electronic device.

[0041] 1. 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 configured to: enable display of a payment account user interface on the display unit for a second electronic device associated with the first electronic device, where enabling display of the payment account user interface includes enabling simultaneous display of a representation of the first payment account with status information for the first payment account indicating that the first payment account is linked to the second electronic device and that the second electronic device is configured to enable payments using the first payment account, and a representation of a second payment account with status information for the second payment account indicating that the second payment account is linked to the first electronic device but not to the second electronic device.

[0042] A temporary 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, when executed by the one or more processors, that cause the electronic device to: receive an input requesting that the device be enabled for a payment transaction; in response to receiving the input requesting that the device be enabled for a payment transaction, display on the display a first visual indicator identifying a first account and enabling the electronic device via the one or more wireless communication elements; receive one or more swipe inputs in a first direction via the touch-sensitive surface; and in response to receiving the one or more user swipe inputs, display on the display a second visual indicator identifying a second account and enabling the electronic device via the one or more wireless communication elements, where the first visual indicator is different from the second visual indicator.

[0043] A temporary 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 location sensor, the one or more programs including instructions, when executed by the one or more processors, that cause the electronic device to: detect a current location using the location sensor; determine whether the current location is associated with a first account; display on the display a visual representation of the default payment account in accordance with determining that the current location is not associated with an account other than the default payment account; and simultaneously display on the display a visual representation of the default payment account and a visual representation of the first account in accordance with determining that the current location is associated with the first account, 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.

[0044] 1. A temporary 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 comprising instructions, when executed by the one or more processors, that cause the electronic device to: receive an input requesting to enable the device for a payment transaction; in response to receiving the input, detect a current location using the position sensor; determine whether a set of one or more payment criteria are satisfied, the set of one or more payment criteria including criteria that are satisfied when the current location is associated with a first payment account; in accordance with a determination that the set of one or more payment criteria are not satisfied, displaying on the display a visual representation of a default payment account, the default payment account being different from the first payment account; and in accordance with a determination that the set of one or more payment criteria are satisfied, displaying on the display a visual representation of the first payment account.

[0045] 1. A temporary 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, when executed by the one or more processors, that cause the electronic device to: receive an input requesting that the device be enabled for a payment transaction; in response to receiving the input, display on the display a payment display 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 the payment transaction; and, in accordance with a determination that a payment criterion for the first payment account is satisfied, transmit, via the one or more wireless communication elements, the account information for the first payment account without transmitting the account information for the second payment account, and in accordance with a determination that a payment criterion for the second payment account is satisfied, transmit, via the one or more wireless communication elements, the account information for the second payment account without transmitting the account information for the first payment account.

[0046] 1. A temporary 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 an intensity of a contact, and one or more wireless communication elements, the one or more programs, when executed by the one or more processors, causing the electronic device to receive a first input and, in response to receiving the first input, display a first user interface on the display, the first user interface including a first visual indicator identifying a payment card associated with a plurality of payment accounts and a first visual indicator identifying a first one of the plurality of payment accounts of the payment card. a first visual indicator identifying the first payment account; enabling the electronic device to conduct a payment transaction using the first payment account via 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 above an intensity threshold; and displaying a second user interface on the display in accordance with a determination that the characteristic intensity of the first contact is above the intensity threshold, the second user interface enabling a selection to be made between the different payment accounts represented by the first visual indicator.

[0047] 1. A temporary 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 elements, the one or more programs including instructions, when executed by the one or more processors, that 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 a selectable affordance for linking the payment account to a second electronic device different from the first electronic device; receive activation of the selectable affordance; and in response to receiving the activation of the selectable affordance, initiate a process for linking the payment account to the second electronic device.

[0048] 1. A temporary 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 elements, the one or more programs comprising instructions, when executed by the one or more processors, that cause the first electronic device to display, 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 the first payment account with status information for the first payment account indicating that the first payment account is linked to the second electronic device and that the second electronic device is configured to enable payments using the first payment account, and a representation of the second payment account with status information for the second payment account indicating that the second payment account is linked to the first electronic device but not to the second electronic device.

[0049] Thus, devices are provided with faster, more efficient methods and interfaces for linking accounts to the device, selecting accounts to use in a transaction, and transmitting account information during a transaction, thereby increasing the effectiveness, efficiency, and user satisfaction of such devices. Such methods and interfaces may complement or replace other methods for performing similar tasks.

[0050] Executable instructions to perform these functions are optionally included in a non-transitory computer-readable storage medium or other computer program product configured to be executed by one or more processors. Executable instructions to perform these functions are optionally included in a transitory computer-readable storage medium or other computer program product configured to be executed by one or more processors.

[0051] For a better understanding of the various described embodiments, please refer to the following Detailed Description in conjunction with the following drawings, in which like reference numerals refer to corresponding parts throughout the drawings, in which: [Brief description of the drawings]

[0052] [Figure 1A] 1 is a block diagram illustrating a portable multifunction device with a touch-sensitive display in accordance with some embodiments. [Figure 1B] FIG. 2 is a block diagram illustrating example components for event processing according to some embodiments. [Diagram 2] 1 illustrates a portable multifunction device with a touch screen according to some embodiments. [Diagram 3] 1 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface in accordance with some embodiments. [Figure 4A] 1 illustrates an exemplary user interface for a menu of applications on a portable multifunction device in accordance with some embodiments. [Figure 4B] 1 illustrates an exemplary user interface for a multifunction device with a touch-sensitive surface separate from a display in accordance with some embodiments. [Figure 5A] 1 illustrates a personal electronic device according to some embodiments. [Figure 5B] 1 is a block diagram illustrating a personal electronic device according to some embodiments. [Figure 5C] 1 illustrates example components of a personal electronic device having a touch-sensitive display and an intensity sensor according to some embodiments. [Figure 5D] 1 illustrates example components of a personal electronic device having a touch-sensitive display and an intensity sensor according to some embodiments. [Figure 5E] 1 illustrates example components and a user interface of a personal electronic device according to some embodiments. [Figure 5F]1 illustrates example components and a user interface of a personal electronic device according to some embodiments. [Figure 5G] 1 illustrates example components and a user interface of a personal electronic device according to some embodiments. [Figure 5H] 1 illustrates example components and a user interface of a personal electronic device according to some embodiments. [Figure 5I] 1 illustrates example devices connected via one or more communication channels to complete a payment transaction according to some embodiments. [Figure 6A] 1 illustrates an example technique and an example user interface for receiving an account selection according to some embodiments. [Figure 6B] 1 illustrates an example technique and an example user interface for receiving an account selection according to some embodiments. [Figure 6C] 1 illustrates an example technique and an example user interface for receiving an account selection according to some embodiments. [Figure 6D] 1 illustrates an example technique and an example user interface for receiving an account selection according to some embodiments. [Figure 6E] 1 illustrates an example technique and an example user interface for receiving an account selection according to some embodiments. [Figure 6F] 1 illustrates an example technique and an example user interface for receiving an account selection according to some embodiments. [Figure 6G] 1 illustrates an example technique and an example user interface for receiving an account selection according to some embodiments. [Figure 7] FIG. 11 is a flow diagram illustrating a method for receiving an account selection according to some embodiments. [Figure 8A] 1 illustrates an example technique and an example user interface for selecting an account according to some embodiments. [Figure 8B]1 illustrates an example technique and an example user interface for selecting an account according to some embodiments. [Figure 8C] 1 illustrates an example technique and an example user interface for selecting an account according to some embodiments. [Figure 8D] 1 illustrates an example technique and an example user interface for selecting an account according to some embodiments. [Figure 9] FIG. 1 is a flow diagram illustrating a method for selecting an account according to some embodiments. [Figure 10A] 1 illustrates an example technique and an example user interface for selecting an account according to some embodiments. [Figure 10B] 1 illustrates an example technique and an example user interface for selecting an account according to some embodiments. [Figure 10C] 1 illustrates an example technique and an example user interface for selecting an account according to some embodiments. [Figure 10D] 1 illustrates an example technique and an example user interface for selecting an account according to some embodiments. [Figure 10E] 1 illustrates an example technique and an example user interface for selecting an account according to some embodiments. [Figure 11] FIG. 1 is a flow diagram illustrating a method for selecting an account according to some embodiments. [Figure 12A] 1 illustrates an example technique and an example user interface for transmitting account information for an account according to some embodiments. [Figure 12B] 1 illustrates an example technique and an example user interface for transmitting account information for an account according to some embodiments. [Figure 12C] 1 illustrates an example technique and an example user interface for transmitting account information for an account according to some embodiments. [Figure 12D]1 illustrates an example technique and an example user interface for transmitting account information for an account according to some embodiments. [Figure 13] FIG. 1 is a flow diagram illustrating a method for transmitting account information for an account according to some embodiments. [Figure 14A] 1 illustrates an example technique and an example user interface for receiving an account selection according to some embodiments. [Figure 14B] 1 illustrates an example technique and an example user interface for receiving an account selection according to some embodiments. [Figure 14C] 1 illustrates an example technique and an example user interface for receiving an account selection according to some embodiments. [Figure 14D] 1 illustrates an example technique and an example user interface for receiving an account selection according to some embodiments. [Figure 14E] 1 illustrates an example technique and an example user interface for receiving an account selection according to some embodiments. [Figure 15] FIG. 11 is a flow diagram illustrating a method for receiving an account selection according to some embodiments. [Figure 16A] 1 illustrates an example technique and an example user interface for linking a payment account to one or more electronic devices according to some embodiments. [Figure 16B] 1 illustrates an example technique and an example user interface for linking a payment account to one or more electronic devices according to some embodiments. [Figure 16C] 1 illustrates an example technique and an example user interface for linking a payment account to one or more electronic devices according to some embodiments. [Figure 16D] 1 illustrates an example technique and an example user interface for linking a payment account to one or more electronic devices according to some embodiments. [Figure 16E]1 illustrates an example technique and an example user interface for linking a payment account to one or more electronic devices according to some embodiments. [Figure 16F] 1 illustrates an example technique and an example user interface for linking a payment account to one or more electronic devices according to some embodiments. [Figure 16G] 1 illustrates an example technique and an example user interface for linking a payment account to one or more electronic devices according to some embodiments. [Figure 17] FIG. 1 is a flow diagram illustrating a method for linking a payment account to one or more electronic devices according to some embodiments. [Figure 18A] 1 illustrates an example technique and an example user interface for linking a payment account to an electronic device according to some embodiments. [Figure 18B] 1 illustrates an example technique and an example user interface for linking a payment account to an electronic device according to some embodiments. [Figure 18C] 1 illustrates an example technique and an example user interface for linking a payment account to an electronic device according to some embodiments. [Figure 19] FIG. 1 is a flow diagram illustrating a method for linking a payment account to an electronic device according to some embodiments. [Figure 20] FIG. 1 illustrates a functional block diagram according to some embodiments. [Figure 21] FIG. 1 illustrates a functional block diagram according to some embodiments. [Figure 22] FIG. 1 illustrates a functional block diagram according to some embodiments. [Diagram 23] FIG. 1 illustrates a functional block diagram according to some embodiments. [Figure 24] FIG. 1 illustrates a functional block diagram according to some embodiments. [Diagram 25] FIG. 1 illustrates a functional block diagram according to some embodiments. [Figure 26] FIG. 1 illustrates a functional block diagram according to some embodiments. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0053] In the following description, example methods, parameters, etc. are set forth, however, it is to be understood that the purpose of such description is not to limit the scope of the disclosure, but rather to provide a description of example embodiments.

[0054] There is a need for electronic devices that provide efficient methods and interfaces for linking accounts to the electronic device, selecting accounts to use in a transaction, and transmitting account information during a transaction. In particular, there is a need to provide efficient methods and interfaces for wearable devices such as smart watches. Such techniques may reduce the cognitive burden on users to access event notifications, thereby increasing productivity. Furthermore, such techniques may reduce processor and battery power that is otherwise wasted on redundant user input.

[0055] The following Figures 1A-1B, 2, 3, 4A-4B, and 5A-5B provide an example device description. Figures 6A-6G show an example technique and an example user interface for receiving an account selection. Figure 7 is a flow diagram illustrating a method for receiving an account selection. The user interfaces of Figures 6A-6G are used to explain the process of Figure 7. Figures 8A-8D show an example technique and an example user interface for selecting an account. Figure 9 is a flow diagram illustrating a method for selecting an account. The user interfaces of Figures 8A-8D are used to explain the process of Figure 9. Figures 10A-10E show an example technique and an example user interface for selecting an account. Figure 11 is a flow diagram illustrating a method for selecting an account, according to some embodiments. The user interfaces of Figures 10A-10E are used to explain the process of Figure 11. Figures 12A-12D show an example technique and an example user interface for transmitting account information of an account. Figure 13 is a flow diagram illustrating a method for transmitting account information of an account, according to some embodiments. The user interfaces of FIGS. 12A-12D are used to explain the process of FIG. 13. FIGS. 14A-14E show an example technique and an example user interface for receiving an account selection. FIG. 15 is a flow diagram illustrating a method for receiving an account selection. The user interfaces of FIGS. 14A-14E are used to explain the process of FIG. 15. FIGS. 16A-16G show an example technique and an example user interface for linking a payment account to one or more electronic devices. FIG. 17 is a flow diagram illustrating a method for linking a payment account to one or more electronic devices. The user interfaces of FIGS. 16A-16G are used to explain the process of FIG. 17. FIGS. 18A-18C show an example technique and an example user interface for linking a payment account to an electronic device, according to some embodiments. FIG. 19 is a flow diagram illustrating a method for linking a payment account to an electronic device.The user interfaces of FIGS. 18A to 18C are used to explain the process of FIG.

[0056] In the following description, terms such as "first" and "second" are used to describe various elements, but these elements should not be limited by these terms. These terms are only used to distinguish one element from another element. For example, a first touch can be referred to as a second touch, and similarly, a second touch can be referred to as a first touch, without departing from the scope of the various embodiments described. A first touch and a second touch are both touches, but are not the same touch.

[0057] The terms used in the description of the various embodiments described herein are for the purpose of describing particular embodiments only and are not intended to be limiting. When used in the description of the various embodiments described and in the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It is also to be understood that the term "and / or" as used herein refers to and includes any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms "includes," "including," "comprises," and / or "comprising," as used herein, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0058] The term "if" can be interpreted to mean "when" or "upon" or "in response to determining" or "in response to detecting," depending on the context. Similarly, the phrases "if it is determined" or "if [a stated condition or event] is detected" can be interpreted to mean "upon determining," or "in response to determining," or "upon detecting [the stated condition or event]," or "in response to detecting [the stated condition or event]," depending on the context.

[0059] Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the device is a portable communication device, such as a mobile telephone, that also includes other functions, such as PDA and / or music player functions. Exemplary embodiments of portable multifunction devices include, but are not limited to, the iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, California. Other portable electronic devices, such as laptops or tablet computers with touch-sensitive surfaces (e.g., touchscreen displays and / or touchpads), are also optionally used. It should also be understood that in some embodiments, the device is not a portable communication device, but rather a desktop computer with a touch-sensitive surface (e.g., touchscreen displays and / or touchpads).

[0060] In the following discussion, we describe an electronic device with a display and a touch-sensitive surface, however it should be understood that the electronic device optionally includes one or more other physical user-interface devices, such as a physical keyboard, a mouse, and / or a joystick.

[0061] The device may support a variety of applications, such as one or more of drawing applications, presentation applications, word processing applications, website creation applications, disc authoring applications, spreadsheet applications, gaming applications, telephony applications, video conferencing applications, email applications, instant messaging applications, training 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.

[0062] Various applications executing on the device optionally use at least one common physical user-interface device, such as a touch-sensitive surface. One or more features of the touch-sensitive surface and corresponding information displayed on the device are optionally adjusted and / or changed for each application and / or within the corresponding application. In this way, the common physical architecture (such as the touch-sensitive surface) of the device optionally supports a variety of applications with user interfaces that are intuitive and transparent to the user.

[0063] Attention is now directed to embodiments of portable devices with touch-sensitive displays. FIG. 1A is a block diagram illustrating a portable multifunction device 100 with a touch-sensitive display system 112, according to some embodiments. Touch-sensitive display 112 may be conveniently referred to as a "touch screen" and may also be known or referred to as a "touch-sensitive display system." Device 100 includes memory 102 (optionally including one or more computer-readable storage media), a memory controller 122, one or more processing units (CPUs) 120, a peripherals interface 118, RF circuitry 108, audio circuitry 110, a speaker 111, a microphone 113, an input / output (I / O) subsystem 106, other input control devices 116, and an external port 124. Device 100 optionally includes one or more light sensors 164. Device 100 optionally includes one or more contact intensity sensors 165 for detecting the intensity of a contact on device 100 (e.g., a touch-sensitive surface such as touch-sensitive display system 112 of device 100). Device 100 optionally includes one or more tactile output generators 167 for generating a tactile output on device 100 (e.g., generating a tactile output on a touch-sensitive surface such as touch-sensitive display system 112 of device 100 or touchpad 355 of device 300). These components optionally communicate via one or more communication buses or signal lines 103.

[0064] As used herein and in the claims, the term “intensity” of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact) on the touch-sensitive surface, or a surrogate (proxy) for the force or pressure of a contact on the touch-sensitive surface. The intensity of a contact has a range of values ​​that includes at least four distinct values, and more typically includes hundreds 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 disposed under or adjacent to the touch-sensitive surface are optionally used to measure the force at various points on the touch-sensitive surface. In some implementations, the force measurements of multiple force sensors are combined (e.g., a weighted average) to determine an estimate of the contact force. Similarly, a pressure-sensitive tip of a stylus is optionally used to determine the pressure of the stylus on the touch-sensitive surface. Alternatively, the size and / or change in a contact area detected on the touch-sensitive surface, the capacitance and / or change in the capacitance of the touch-sensitive surface proximate the contact, and / or the resistance and / or change in the capacitance of the touch-sensitive surface proximate the contact are optionally used as a surrogate for the force or pressure of the contact on the touch-sensitive surface. In some implementations, the surrogate measure of the force or pressure of the contact is used directly to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the surrogate measure). In some implementations, the surrogate measure of the force or pressure of the contact is converted to 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 contact as an attribute of user input allows a user access to additional device functionality that may otherwise be inaccessible to the user on a device of reduced size that has a limited area for displaying affordances (e.g., on a touch-sensitive display) and / or receiving user input (e.g., via a touch-sensitive display, touch-sensitive surface, or physical / mechanical controls such as knobs or buttons).

[0065] As used herein and in the claims, the term "tactile output" refers to a physical displacement of a device relative to a previous position of the device, a physical displacement of a component of the device (e.g., a touch-sensitive surface) relative to another component of the device (e.g., a housing), or a displacement of a component relative to the center of mass of the device, that is to be detected by a user with the user's sense of touch. For example, in a situation where a device or a component of the device is in contact with a touch-sensitive surface of a user (e.g., a finger, palm, or other part of a user's hand), the tactile output generated by the physical displacement is interpreted by the user as a tactile sensation that corresponds to a perceived change in a physical property of the device or a component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is optionally interpreted by the user as a "down-click" or "up-click" of a physical actuator button. In some cases, a user will feel a tactile sensation such as a "down-click" or "up-click" even when there is no movement of a physical actuator button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user's action. As another example, movement of the touch-sensitive surface is optionally interpreted or sensed by a user as "roughness" of the touch-sensitive surface, even when there is no change in the smoothness of the touch-sensitive surface. Although such user interpretation of touch will depend on the user's personal sensory perception, there are many sensory perceptions of touch that are common to a majority of users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., an "up click," "down click," "roughness"), unless otherwise noted, the generated tactile output corresponds to a physical displacement of the device, or a component of the device, that produces the described sensory perception of a typical (or average) user.

[0066] It should be understood that device 100 is only one example of a portable multifunction device, and that device 100 optionally has more or fewer components than those shown, optionally combines two or more components, or optionally has a different configuration or arrangement of those components. The various components shown in FIG. 1A may be implemented as hardware, software, or a combination of both hardware and software, including one or more signal processing circuits and / or application specific integrated circuits.

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

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

[0069] The RF (Radio Frequency) circuitry 108 transmits and receives RF signals, also called electromagnetic signals. The RF circuitry 108 converts electrical signals to electromagnetic signals or electromagnetic signals to electrical signals and communicates with communication networks and other communication devices via electromagnetic signals. The RF circuitry 108 optionally includes well-known circuitry for performing these functions, including, but not limited to, an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, and the like. The RF circuitry 108 optionally communicates by wireless communication with networks, such as the Internet, also called the World Wide Web (WWW), an intranet, and / or a wireless network, such as a wireless local area network (LAN), and / or a metropolitan area network (MAN), and other devices. The RF circuitry 108 optionally includes well-known circuitry for detecting a near field communication (NFC) field, such as by near field communication radio. The wireless communication optionally uses any of a number of communication standards, protocols, and technologies, including Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packet access (HSDPA), high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual-Cell HSPA (DC-HSPA), long term evolution (LTE), near field communication (NFC), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), and other communication standards, protocols, and technologies.IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n, and / or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, protocols for email (e.g., Internet message access protocol (IMAP) and / or post office protocol (POP)), instant messaging (e.g., extensible messaging and presence protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE)), instant messaging and presence services (e.g., IEEE 802.11b), time division multiple access (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n, and / or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, protocols for email (e.g., Internet message access protocol (IMAP) and / or post office protocol (POP)), instant messaging (e.g., extensible messaging and presence protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE)), instant messaging and presence services (e.g., IEEE 802.11b), instant messaging and presence services (e.g., IEEE 802.11c), instant messaging and presence services (e.g., IEEE 802.11d), instant messaging and presence services (e.g., IEEE 802.11e), instant messaging and presence services (e.g., IEEE 802.11g ... Examples of suitable communication protocols include, but are not limited to, Intermediate and Intermediate Presence Service (IMPS), and / or Short Message Service (SMS), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document.

[0070] The audio circuit 110, speaker 111, and microphone 113 provide an audio interface between a user and the device 100. The audio circuit 110 receives audio data from the peripherals interface 118, converts the audio data to 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 an electrical signal converted from the sound waves by the microphone 113. The audio circuit 110 converts the electrical signal into audio data and transmits the audio data to the peripherals interface 118 for processing. The audio data may be retrieved from and / or transmitted to the memory 102 and / or the RF circuit 108 by the peripherals interface 118. In some embodiments, the audio circuit 110 further comprises a headset jack (e.g., 212 in FIG. 2). The headset jack provides an interface between audio circuitry 110 and a removable audio input / output peripheral device, such as an output-only headphone or a headset that has both an output (e.g., one- or binaural headphones) and an input (e.g., a microphone).

[0071] The I / O subsystem 106 connects input / output peripherals of the device 100, such as the touch screen 112 and other input control devices 116, to a peripheral interface 118. The I / O subsystem 106 optionally includes a display controller 156, a light 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 / send electrical signals to / from the other input control devices 116. The other input control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, etc. In some alternative embodiments, the input controller(s) 160 are optionally connected to any (or none) of a keyboard, an infrared port, a USB port, and a pointer device such as a mouse. The one or more buttons (e.g., 208 in FIG. 2) optionally include up / down buttons for adjusting the volume of the speaker 111 and / or microphone 113. The one or more buttons optionally include a push button (e.g., 206 in FIG. 2).

[0072] A quick press of the push button may unlock the touch screen 112 or initiate a process of using gestures on the touch screen to unlock the device, as described in U.S. Patent Application Serial No. 11 / 322,549, "Unlocking a Device by Performing Gestures on an Unlock Image," U.S. Patent No. 7,657,849, filed December 23, 2005, which is incorporated by reference in its entirety. A longer press of the push button (e.g., 206) may power the device 100 on or off. The user may customize the functionality of one or more buttons. The touch screen 112 may be used to implement virtual or soft buttons and one or more soft keyboards.

[0073] The touch-sensitive display 112 provides an input and output interface between the device and a user. The display controller 156 receives electrical signals from and / or sends electrical signals to the touch screen 112. The touch screen 112 displays visual output to the user. This visual output may include images, text, icons, video, 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.

[0074] Touchscreen 112 has a touch-sensitive surface, sensor, or set of sensors that accepts input from a user based on haptic and / or tactile contact. Touchscreen 112 and display controller 156 (along with any associated modules and / or instruction sets in memory 102) detects contacts (and any movement or breaking of contact) on touchscreen 112 and translates the detected contacts into interactions with user interface objects (e.g., one or more soft keys, icons, web pages, or images) displayed on touchscreen 112. In an exemplary embodiment, the point of contact between touchscreen 112 and the user corresponds to the user's finger.

[0075] Touch screen 112 may use liquid crystal display (LCD), light emitting polymer display (LPD), or light emitting diode (LED) technology, although other display technologies may be used in other embodiments. Touch screen 112 and display controller 156 may detect contact and any movement or disruption of that contact using any of a number of touch sensing technologies now known or later developed, including, but not limited to, capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements to determine one or more points of contact with touch screen 112. In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as that found in the iPhone® and iPod Touch® by Apple Inc. of Cupertino, California.

[0076] The touch-sensitive display in some embodiments of touchscreen 112 may be similar to the multi-touch-sensing touchpads 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 Application Publication No. 2002 / 0015024 A1, each of which is incorporated by reference in its entirety herein, except that touchscreen 112 displays visual output from device 100, whereas touch-sensitive touchpads do not provide visual output.

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

[0078] 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 approximately 160 dpi. A user may contact the touch screen 112 using any suitable object or appendage, such as a stylus, a finger, etc. In some embodiments, the user interface is designed to function primarily through finger-based contact and gestures, which may be less precise than stylus-based input due to the large contact area of ​​a finger on the touch screen. In some embodiments, the device translates the coarse finger-based input into a precise pointer / cursor position or a command to perform the user's desired action.

[0079] In some embodiments, in addition to a touchscreen, device 100 may include a touchpad (not shown) for activating or deactivating certain functions. In some embodiments, a touchpad is a touch-sensitive area of ​​a device that, unlike a touchscreen, does not display visual output. A touchpad can be a touch-sensitive surface separate from touchscreen 112 or an extension of the touch-sensitive surface formed by the touchscreen.

[0080] Device 100 also includes a power system 162 for providing power to the various components. Power system 162 may include a power management system, one or more power sources (e.g., batteries, alternating current (AC)), a recharging system, power failure detection circuitry, power converters or inverters, power status indicators (e.g., light emitting diodes (LEDs)), and any other components associated with the generation, management, and distribution of power in a portable device.

[0081] The device 100 may also include one or more light sensors 164. FIG. 1A shows a light sensor coupled to a light sensor controller 158 in the I / O subsystem 106. The light sensor 164 may include a charge-coupled device (CCD) or a complementary metal-oxide semiconductor (CMOS) phototransistor. The light sensor 164 receives light from the environment, projected through one or more lenses, and converts the light into data representing an image. In conjunction with an imaging module 143 (also called a camera module), the light sensor 164 can capture still images or video. In some embodiments, the light sensor is located on the back of the device 100, opposite the touchscreen display 112 on the front of the device, so that the touchscreen display can be used as a viewfinder for still and / or video image acquisition. In some embodiments, the light sensor is located on the front of the device so that an image of the user can be obtained for a video conference while the user sees other video conference participants on the touchscreen display. In some embodiments, the position of the light sensor 164 can be changed by the user (e.g., by rotating the lens and sensor within the device housing), thereby allowing a single light sensor 164 to be used in conjunction with a touch screen display for both video conferencing and capturing still and / or video images.

[0082] Device 100 also optionally includes one or more contact intensity sensors 165. FIG. 1A shows a contact intensity sensor coupled to intensity sensor controller 159 in I / O subsystem 106. Contact intensity sensor 165 optionally includes one or more piezoresistive strain gauges, capacitive force sensors, electrical force sensors, piezoelectric force sensors, optical force sensors, capacitive touch-sensitive surfaces, or other intensity sensors (e.g., sensors used to measure the force (or pressure) of a contact on a touch-sensitive surface). Contact intensity sensor 165 receives contact intensity information (e.g., pressure information or a proxy for pressure information) from the environment. In some embodiments, at least one contact intensity sensor is located on or proximate to a touch-sensitive surface (e.g., touch-sensitive display system 112). In some embodiments, at least one contact intensity sensor is located on the back of device 100, opposite touchscreen display 112 located on the front of device 100.

[0083] Device 100 may include one or more proximity sensors 166. FIG. 1A shows proximity sensor 166 connected to peripherals interface 118. Alternatively, proximity sensor 166 may be coupled to input controller 160 in I / O subsystem 106. Proximity sensor 166 functions as described in U.S. patent application Ser. No. 11 / 241,839, entitled "Proximity Detector In Handheld Device," Ser. No. 11 / 240,788, entitled "Proximity Detector In Handheld Device," Ser. No. 11 / 620,702, entitled "Using Ambient Light Sensor To Augment Proximity Sensor Output," Ser. No. 11 / 586,862, entitled "Automated Response To And Sensing Of User Activity In Portable Devices," and Ser. No. 11 / 638,251, entitled "Methods And Systems For Automatic Configuration Of Peripherals," all of which are incorporated herein by reference in their entireties. In some embodiments, the proximity sensor turns off and disables touch screen 112 when the multifunction device is placed near the user's ear (eg, when the user is making a phone call).

[0084] Device 100 also optionally includes one or more tactile output generators 167. FIG. 1A shows a tactile output generator coupled to haptic feedback controller 161 in I / O subsystem 106. Tactile output generator 167 optionally includes one or more electroacoustic devices, such as speakers or other audio components, and / or electromechanical devices that convert energy into linear motion, such as motors, solenoids, electroactive polymers, piezoelectric actuators, electrostatic actuators, or other tactile output generating components (e.g., components that convert electrical signals into tactile output on the device). Contact intensity sensor 165 receives haptic feedback generation instructions from haptic feedback module 133 and generates a tactile output on device 100 that can be sensed by a user of device 100. In some embodiments, at least one tactile output generator is disposed on or proximate to a touch-sensitive surface (e.g., touch-sensitive display system 112) and optionally generates a tactile output by moving the touch-sensitive surface vertically (e.g., in / out of the surface of device 100) or laterally (e.g., back and forth in the same plane as the surface of device 100). In some embodiments, at least one tactile output generator sensor is disposed on the back of device 100, opposite touchscreen display 112 disposed on the front of device 100.

[0085] Device 100 may also include one or more accelerometers 168. FIG. 1A shows accelerometer 168 connected to peripherals interface 118. Alternatively, accelerometer 168 may be coupled to input controller 160 in I / O subsystem 106. Accelerometer 168 may function as described in U.S. Patent Application Publication Nos. 20050190059, “Acceleration-based Theft Detection System for Portable Electronic Devices,” and 20060017692, “Methods And Apparatuses For Operating A Portable Device Based On An Accelerometer,” both of which are incorporated herein by reference in their entireties. In some embodiments, information is displayed on a touchscreen display in portrait or landscape orientation based on an analysis of data received from one or more accelerometers. In addition to accelerometer(s) 168, device 100 optionally includes a magnetometer (not shown) and a GPS (or GLONASS or other global navigation system) receiver (not shown) for obtaining information regarding the location and orientation (e.g., portrait or landscape) of device 100.

[0086] In some embodiments, the software components stored in memory 102 include an operating system 126, a communications module (or instruction set) 128, a touch / motion module (or instruction set) 130, a graphics module (or instruction set) 132, a text input module (or instruction set) 134, a global positioning system (GPS) module (or instruction set) 135, and applications (or instruction sets) 136. Additionally, in some embodiments, as shown in FIGS. 1A and 3, memory 102 (FIG. 1A) or memory 370 (FIG. 3) stores device / global internal state 157. Device / global internal state 157 includes one or more of the following: active application state, indicating which applications, if any, are currently active; display state, indicating which applications, views, or other information are occupying various regions of touchscreen display 112; sensor state, including information obtained from the device's various sensors and input control devices 116; and location information regarding the device's position and / or orientation.

[0087] 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 common system tasks (e.g., memory management, storage device control, power management, etc.) and facilitating communication between various hardware and software components.

[0088] Communications module 128 facilitates communication with other devices via one or more external ports 124 and includes various software components for processing data received by RF circuitry 108 and / or external port 124. External port 124 (e.g., Universal Serial Bus (USB), FIREWIRE®, etc.) is adapted to connect to other devices directly or indirectly through a network (e.g., Internet, wireless LAN, etc.). In some embodiments, the external port is a multi-pin (e.g., 30-pin) connector the same as or similar to the 30-pin connector used on iPod® (trademark of Apple Inc.) devices and / or a compatible multi-pin (e.g., 30-pin) connector.

[0089] Contact / motion module 130, optionally in conjunction with display controller 156, detects contact with touch screen 112 and other touch-sensing devices (e.g., a touchpad or physical click wheel). Contact / motion module 130 includes various software components for performing various operations related to detecting contact, such as determining whether contact has occurred (e.g., detecting a finger down event), determining the strength 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 across 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 up event or an interruption of the contact). Contact / motion module 130 receives contact data from the touch-sensitive surface. Determining the movement of the contact point represented by the set of contact data optionally includes determining the speed (magnitude), velocity (magnitude and direction), and / or acceleration (change in magnitude and / or direction) of the contact point. These actions are, optionally, applied to a single contact (e.g., one finger contact) or multiple simultaneous contacts (e.g., "multi-touch" / multiple finger contacts). In some embodiments, contact / motion module 130 and display controller 156 detect contacts on a touchpad.

[0090] In some embodiments, the contact / motion module 130 uses a set of one or more intensity thresholds for determining whether an action has been performed by a user (e.g., for determining whether a user has “clicked” on an icon). In some embodiments, at least a subset of the intensity thresholds are determined according to software parameters (e.g., the intensity thresholds are not determined by the activation thresholds of a particular physical actuator and may be adjusted without modifying the physical hardware of the device 100). For example, the mouse “click” threshold of a trackpad or touchscreen display may be set to any of a wide range of predefined thresholds without modifying the hardware of the trackpad or touchscreen display. Additionally, in some implementations, a user of the device is provided with a software setting for adjusting one or more of the set of intensity thresholds (e.g., by adjusting individual intensity thresholds and / or by adjusting multiple intensity thresholds at once via a system-level click “strength” parameter).

[0091] Contact / motion module 130 optionally detects gesture input by a user. Different gestures on a touch-sensitive surface have different contact patterns (e.g., different movements, timing, and / or intensity of detected contact). Thus, a gesture is optionally detected by detecting a particular contact pattern. For example, detecting a finger tap gesture includes detecting a finger down event (e.g., at an icon location) followed by detecting a finger lift off event at the same location (or substantially the same location) as the finger down event. As another example, detecting a finger swipe gesture on a touch-sensitive surface includes detecting a finger down event followed by detecting one or more finger drag events followed by detecting a finger lift off event.

[0092] Graphics module 132 includes various known software components for rendering and displaying graphics on touchscreen 112 or other display, including components for modifying the visual effects (e.g., brightness, transparency, saturation, contrast, or other visual characteristics) of the displayed graphics. As used herein, the term "graphics" includes any object that can be displayed to a user, including, but not limited to, text, web pages, icons (such as user interface objects including soft keys), digital images, videos, animations, and the like.

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

[0094] The tactile feedback module 133 includes various software components for generating instructions used by the tactile output generator(s) 167 to generate tactile outputs at one or more locations on the device 100 in response to user interaction with the device 100.

[0095] Text input module 134, which may be a component of graphics module 132, provides a soft keyboard for entering text within various applications (e.g., contacts 137, email 140, IM 141, browser 147, and any other application requiring text input).

[0096] The GPS module 135 determines the location of the device and provides this information for use by various applications (e.g., to the phone 138 for location-based telephony use, to the camera 143 as photo / video metadata, and to applications that provide location-based services, such as a weather widget, a local yellow pages widget, and a maps / navigation widget).

[0097] The application 136 may include the following modules (or sets of instructions), or a subset or superset thereof: ● a contacts module 137 (sometimes called an address book or contact list); ●Telephone module 138, ● Videoconferencing module 139, ● an email client module 140; ● Instant messaging (IM) module 141; ● Training support module 142, A camera module 143 for still and / or video images, ● Image management module 144, ●Video playback module, ●Music playback module, ● Browser module 147, ● Calendar module 148, A widget module 149, which may include one or more of a weather widget 149-1, a stock widget 149-2, a calculator widget 149-3, an alarm clock widget 149-4, a dictionary widget 149-5, and other widgets obtained by the user, as well as user-created widgets 149-6; ● a widget creation module 150 for creating user-created widgets 149-6; ● Search module 151, ● A video and music playback module 152 that integrates a video playback module and a music playback module; ● Memo module 153, Map module 154, and / or ●Online video module 155.

[0098] Examples of other applications 136 that may be stored in memory 102 include other word processing applications, other image editing applications, drawing applications, presentation applications, JAVA® enabled applications, encryption, digital rights management, voice recognition, and voice duplication.

[0099] In conjunction with the touch screen 112, the display controller 156, the contact / motion module 130, the graphics module 132, and the text input module 134, the contacts module 137 is used to manage an address book or contact list (e.g., stored in the memory 102 or in the application internal state 192 of the contacts module 137 in the memory 370), including adding a name(s) to the address book, deleting a name(s) from the address book, associating phone number(s), email address(es), address(es), or other information with a name, associating a picture with a name, categorizing and sorting names, providing phone numbers or email addresses to initiate and / or facilitate communication by phone 138, videoconferencing module 139, email 140, or IM 141, and the like.

[0100] In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, telephone module 138 can be used to enter a series of characters corresponding to a telephone number, access one or more telephone numbers in contacts module 137, modify an entered telephone number, dial the corresponding telephone number, conduct a conversation, and disconnect or hang up when the conversation is completed. As discussed above, wireless communication can use any of a number of communication standards, protocols, and technologies.

[0101] In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, light sensor 164, light sensor controller 158, contact / motion module 130, graphics module 132, text input module 134, contacts module 137, and telephone module 138, videoconferencing module 139 contains executable instructions to initiate, conduct, and terminate a videoconference between a user and one or more other participants in accordance with the user's instructions.

[0102] In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, email client module 140 contains executable instructions for creating, sending, receiving, and managing emails in response to user instructions. Email client module 140 in conjunction with image management module 144 greatly facilitates creating and sending emails with attachments of still or video images captured by camera module 143.

[0103] In cooperation with the RF circuitry 108, the touch screen 112, the display controller 156, the contact / motion module 130, the graphics module 132, and the text input module 134, the instant messaging module 141 includes executable instructions for inputting characters corresponding to an instant message, modifying characters already input, sending the corresponding instant message (e.g., using Short Message Service (SMS) or Multimedia Message Service (MMS) protocols for telephone-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, sent and / or received instant messages may include graphics, photos, audio files, video files, and / or other attachments, such as those supported by MMS and / or Enhanced Messaging Service (EMS). As used herein, "instant messaging" refers to both telephone-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS).

[0104] In conjunction with the RF circuitry 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 playback module, the training support module 142 includes executable instructions for: creating workouts (e.g., having time, distance, and / or calorie burn goals), communicating with training sensors (sports devices), receiving training sensor data, calibrating sensors used to monitor the workouts, selecting and playing music for the workouts, and displaying, storing, and transmitting the workout data.

[0105] In cooperation with touch screen 112, display controller 156, light sensor(s) 164, light sensor controller 158, contact / motion module 130, graphics module 132, and image management module 144, camera module 143 contains executable instructions to capture still images or video (including video streams) and store them in memory 102, change characteristics of the still images or video, or delete the still images or video from memory 102.

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

[0107] In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, browser module 147 contains executable instructions for browsing the Internet in accordance with a user's instructions, including retrieving, linking, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.

[0108] In cooperation 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 contains executable instructions to create, display, modify, and store calendars and data associated with calendars (e.g., calendar items, to-do lists, etc.) in accordance with a user's instructions.

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

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

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

[0112] In conjunction with touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, and browser module 147, video and music playback module 152 contains executable instructions that enable a user to download and play recorded music and other sound files stored in one or more file formats, such as MP3 or AAC files, as well as executable instructions to display, present, or otherwise play videos (on touchscreen 112 or on an external display connected via external port 124). In some embodiments, device 100 optionally includes the functionality of an MP3 player, such as an iPod (a trademark of Apple Inc.).

[0113] In conjunction with the touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, the notes module 153 contains executable instructions for creating and managing notes, to-do lists, and the like, in accordance with a user's instructions.

[0114] In conjunction with RF circuitry 108, touch screen 112, display controller 156, touch / 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 for stores and other points of interest at or near a particular location, and other location-based data) in accordance with a user's instructions.

[0115] In conjunction with touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, text input module 134, email client module 140, and browser module 147, online video module 155 contains instructions that enable a user to access, view, receive (e.g., by streaming and / or downloading), play (e.g., on the touchscreen or on an external display connected via external port 124), and send and otherwise manage emails containing links to particular online videos in one or more file formats, such as H.264. In some embodiments, instant messaging module 141 is used to send links to particular online videos, rather than email client module 140. Further description of online video applications can be found in U.S. Provisional Patent Application No. 60 / 936,562, entitled "Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos," filed June 20, 2007, and U.S. Patent Application No. 11 / 968,067, entitled "Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos," filed December 31, 2007, the contents of which are incorporated by reference in their entireties herein.

[0116] Each of the above-identified modules and applications corresponds to an executable set of instructions and methods (e.g., computer-implemented methods and other information processing methods described herein) that perform one or more of the above-identified functions. These modules (e.g., sets of instructions) need not be implemented as separate software programs, procedures, or modules, and thus, in various embodiments, various subsets of these modules may be combined or otherwise rearranged. For example, a video playback module may be combined with a music playback module into a single module (e.g., video and music playback module 152 of FIG. 1A). In some embodiments, memory 102 may store a subset of the above-identified modules and data structures. Additionally, memory 102 may store additional modules and data structures not described above.

[0117] In some embodiments, device 100 is a device in which operation of a predefined set of functions on the device is performed exclusively via a touchscreen and / or touchpad. By using the touchscreen and / or touchpad as the primary input control device for operation of device 100, the number of physical input control devices (e.g., push buttons, dials, etc.) on device 100 can be reduced.

[0118] The set of predefined functions performed solely via the touchscreen and / or touchpad optionally includes navigation between user interfaces. In some embodiments, the touchpad, when touched by a user, navigates device 100 to a main menu, a home menu, or a root menu from any user interface displayed on device 100. In such an embodiment, a "menu button" is implemented using the touchpad. In some other embodiments, the menu button is a physical push button or other physical input control device instead of a touchpad.

[0119] 1B is a block diagram illustrating example components for event processing, according to some embodiments. In some embodiments, memory 102 (FIG. 1A) or memory 370 (FIG. 3) includes an event sorter 170 (e.g., in operating system 126) and a corresponding application 136-1 (e.g., any of applications 137-151, 155, 380-390 described above).

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

[0121] In some embodiments, application internal state 192 includes additional information such as one or more of resume information used when application 136-1 resumes execution, user interface state information indicating information is being displayed or ready to be displayed by application 136-1, a state queue to allow the user to return to a previous state or view of application 136-1, and a redo / undo queue of actions previously performed by the user.

[0122] Event monitor 171 receives event information from peripherals interface 118. The event information includes information about sub-events (e.g., a user's touch on touch-sensitive display 112 as part of a multi-touch gesture). Peripherals interface 118 transmits information it receives from I / O subsystem 106 or sensors such as proximity sensor 166, accelerometer(s) 168, and / or microphone 113 (via audio circuitry 110). Information that peripherals interface 118 receives from I / O subsystem 106 includes information from touch-sensitive display 112 or a touch-sensitive surface.

[0123] In some embodiments, event monitor 171 sends requests to peripherals interface 118 at predetermined intervals. In response, peripherals interface 118 transmits event information. In other embodiments, peripherals interface 118 transmits event information only when there is a significant event (e.g., receiving an input above a predetermined noise threshold and / or for a predetermined duration).

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

[0125] Hit view determination module 172 provides software procedures for determining where in one or more views a sub-event occurred when touch-sensitive display 112 displays more than one view. A view consists of controls and other elements that a user can see on the display.

[0126] Another aspect of a user interface associated with an application is the set of views, sometimes referred to herein as application views or user interface windows, in which information is displayed and in which touch-based gestures occur. The application view (of the corresponding application) in which a touch is detected may correspond to a programmatic level within the programmatic or view hierarchy of that application. For example, the lowest-level view in which a touch is detected may be referred to as the hit view, and the set of events that are recognized as appropriate inputs may be determined, at least in part, based on the hit view of the initial touch that initiates a touch-based gesture.

[0127] Hit view determination module 172 receives information associated with sub-events of a touch-based gesture. If an application has multiple views organized as a hierarchy, hit view determination module 172 identifies the hit view as the lowest view in the hierarchy that should process the sub-event. In most situations, the hit view is the lowest level view in which the first sub-event occurs (e.g., the first sub-event in a sequence of sub-events that form an event or potential event). Once a hit view is identified by hit view determination module 172, the hit view typically receives all sub-events associated with the same touch or input source for which it was identified as the hit view.

[0128] Active event recognizer determination module 173 determines which view(s) in the view hierarchy should receive the particular sequence of sub-events. In some embodiments, active event recognizer determination module 173 determines that only the hit view should receive the particular sequence of sub-events. In other embodiments, active event recognizer determination module 173 determines that all views that contain the physical location of the sub-event are actively participating views, and therefore all actively participating views should receive the particular sequence of sub-events. In other embodiments, even if the touch sub-event is completely confined to the area associated with a particular view, views higher in the hierarchy remain actively participating views.

[0129] Event dispatcher module 174 sends the event information to an event recognizer (e.g., event recognizer 180). In embodiments that include active event recognizer determination module 173, event dispatcher module 174 delivers the event information to the event recognizers determined by active event recognizer determination module 173. In some embodiments, event dispatcher module 174 stores event information obtained by a corresponding event receiver 182 in an event queue.

[0130] In some embodiments, operating system 126 includes event sorter 170. Alternatively, application 136-1 includes event sorter 170. In yet other embodiments, event sorter 170 is a stand-alone module or part of another module stored in memory 102, such as contact / motion module 130.

[0131] In some embodiments, application 136-1 includes multiple event handlers 190 and one or more application views 191, each of which includes instructions for handling touch events that occur within a respective view of the application's user interface. Each application view 191 of application 136-1 includes one or more event recognizers 180. Typically, each application view 191 includes multiple event recognizers 180. In other embodiments, one or more of the event recognizers 180 are part of a separate module, such as a user interface kit (not shown) or a higher level object from which application 136-1 inherits methods and other properties. In some embodiments, each event handler 190 includes one or more of a data updater 176, an object updater 177, a GUI updater 178, and / or event data 179 received from event sorter 170. Event handler 190 may utilize or call data updater 176, object updater 177, or GUI updater 178 to update application internal state 192. Alternatively, one or more of the application views 191 includes one or more corresponding event handlers 190. In some embodiments, one or more of a data updater 176, an object updater 177, and a GUI updater 178 are also included in the corresponding application view 191.

[0132] Each event recognizer 180 receives event information (e.g., event data 179) from event sorter 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 further includes at least a subset of metadata 183 and event delivery instructions 188 (which may include sub-event delivery instructions).

[0133] The event receiver 182 receives event information from the event sorter 170. The event information includes information about a sub-event, e.g., information about 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. If the sub-event relates to a touch movement, the event information may also include the speed and direction of the sub-event. In some embodiments, the event includes a rotation of the device from one orientation to another (e.g., from portrait to landscape or vice versa), and the event information includes corresponding information about the device's current orientation (also called the device's attitude).

[0134] The event comparator 184 compares the event information to predefined event or sub-event definitions and determines the event or sub-event or determines or updates the state of the event or sub-event based on the comparison. In some embodiments, the event comparator 184 includes an event definition 186. The event definition 186 includes a definition of an event (e.g., a predefined sequence of sub-events), such as, for example, event 1 (187-1), event 2 (187-2), etc. In some embodiments, the sub-events in an event (187) include, for example, touch start, touch end, touch movement, touch stop, and multiple touches. In one example, the definition of event 1 (187-1) is a double tap on a displayed object. The double tap includes, for example, a first touch on a displayed object for a given stage (touch start), a first lift off (touch end) for the given stage, a second touch on a displayed object for a given stage (touch start), and a second lift off (touch end) for the given stage. In another example, a definition of event 2 (187-2) is a drag operation on a displayed object, including, for example, a touch (or contact) on the displayed object for a given step, a movement of the touch across the touch-sensitive display 112, and a lift-off of the touch (end of the touch). In some embodiments, the event also includes information about one or more associated event handlers 190.

[0135] In some embodiments, event definition 187 includes a definition of the event for each user interface object. In some embodiments, event comparator 184 performs a hit test to determine which user interface object is associated with the sub-event. For example, in an application view in which three user interface objects are displayed on touch-sensitive display 112, when a touch is detected on touch-sensitive display 112, event comparator 184 performs a hit test to determine which of the three user interface objects is associated with the touch (sub-event). If each displayed object is associated with a corresponding event handler 190, event comparator 184 uses the results of the hit test to determine which event handler 190 to activate. For example, event comparator 184 selects the event handler associated with the sub-event and the object that triggers the hit test.

[0136] In some embodiments, each event 187 definition also includes a delay action that delays delivery of the event information until it is determined whether the sequence of sub-events corresponds or does not correspond to the event type of the event recognizer.

[0137] If the respective event recognizer 180 determines that the sequence of sub-events does not match any of the events in the event definition 186, the respective event recognizer 180 enters an event disabled, event failed, or event finished state and thereafter ignores the next sub-event of the touch-based gesture. In this situation, any other event recognizers that remain active for the hit view continue to track and process sub-events of the ongoing touch-based gesture.

[0138] In some embodiments, each event recognizer 180 includes metadata 183 with configurable properties, flags, and / or lists that indicate how the event delivery system performs sub-event delivery to actively participating event recognizers. In some embodiments, metadata 183 includes configurable properties, flags, and / or lists that indicate how event recognizers may or may be able to interact with each other. In some embodiments, metadata 183 includes configurable properties, flags, and / or lists that indicate whether sub-events are delivered to various levels in a view or programmatic hierarchy.

[0139] In some embodiments, each event recognizer 180 activates an event handler 190 associated with the event when one or more specific sub-events of the event are recognized. In some embodiments, each event recognizer 180 delivers event information associated with the event to the event handler 190. Activating the event handler 190 is distinct from sending (and postponing sending) the sub-events to the corresponding hit view. In some embodiments, the event recognizer 180 throws a flag associated with the recognized event, and the event handler 190 associated with the flag catches the flag and performs a predetermined process.

[0140] In some embodiments, the event delivery instructions 188 include sub-event delivery instructions that deliver event information about a sub-event without activating an event handler. Instead, the sub-event delivery instructions deliver the event information to an event handler associated with a set of sub-events or an actively participating view. The event handler associated with the set of sub-events or an actively participating view receives the event information and performs a predetermined process.

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

[0142] In some embodiments, event handler(s) 190 include or have access to data updater 176, object updater 177, and GUI updater 178. In some embodiments, data updater 176, object updater 177, and GUI updater 178 are included in a single module of a respective application 136-1 or application view 191. In other embodiments, they are included in two or more software modules.

[0143] It should be understood that the foregoing description of event processing of a user's touch on a touch-sensitive display also applies to other forms of user input for operating multifunction device 100 with an input device, not all of which are initiated on a touch screen. For example, mouse movements and mouse button presses, optionally in conjunction with single or multiple keyboard presses or holds, touch movements such as tapping, dragging, scrolling on a touchpad, pen stylus input, device movements, verbal cues, detected eye movements, biometric input, and / or any combination thereof, are optionally utilized as inputs corresponding to sub-events that define the event to be recognized.

[0144] FIG. 2 illustrates portable multifunction device 100 having touch screen 112, according to some embodiments. The touch screen optionally displays one or more graphics in user interface (UI) 200. In this embodiment, as well as other embodiments described below, a user can select one or more of the graphics by making a gesture on the graphics, for example, with one or more fingers 202 (not drawn to scale) or one or more styluses 203 (not drawn to scale). In some embodiments, selection of one or more graphics occurs when the user loses contact with the one or more graphics. In some embodiments, the gesture optionally includes one or more taps, one or more swipes (left to right, right to left, upward and / or downward), and / or rolling of a finger in contact with device 100 (right to left, left to right, upward and / or downward). In some implementations or situations, accidental contact with a graphic does not select the graphic. For example, if the gesture corresponding to selection is a tap, a swipe gesture sweeping over an application icon optionally does not select the corresponding application.

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

[0146] In some embodiments, device 100 includes touch screen 112, menu button 204, push button 206 for turning power to the device on / off and locking the device, volume control button(s) 208, subscriber identity module (SIM) card slot 210, headset jack 212, and external port 124 for docking / charging. Push button 206 is optionally used to turn power on / off on the device by pressing and holding the button down for a predefined time, lock the device by pressing and releasing the button before the predefined time has elapsed, and / or unlock the device or initiate an unlocking process. In another embodiment, device 100 also receives verbal input through microphone 113 for activating or deactivating some functions. Device 100 also optionally includes one or more contact intensity sensors 165 for detecting the intensity of a contact on touch screen 112 and / or one or more tactile output generators 167 for generating a tactile output to a user of device 100.

[0147] FIG. 3 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface, according to some embodiments. Device 300 need not be portable. In some embodiments, device 300 is a laptop computer, a desktop computer, a tablet computer, a multimedia playback device, a navigation device, an educational device (such as a child's learning toy), a gaming system, or a control device (e.g., a home or commercial controller). Device 300 typically includes one or more processing units (CPUs) 310, one or more network or other communication interfaces 360, memory 370, and one or more communication buses 320 for interconnecting these components. Communication bus 320 optionally includes circuitry (sometimes called a chipset) that interconnects and controls communication between system components. Device 300 includes an input / output (I / O) interface 330 with a display 340, which is typically a touchscreen display. I / O interface 330 also optionally includes a keyboard and / or mouse (or other pointing device) 350, as well as a touchpad 355, a tactile output generator 357 (e.g., similar to tactile output generator(s) 167 described above with reference to FIG. 1A) for generating tactile output on device 300, and sensors 359 (e.g., optical sensors, acceleration sensors, proximity sensors, touch-sensitive sensors, and / or contact intensity sensors similar to contact intensity sensor(s) 165 described above with reference to FIG. 1A). Memory 370 includes high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid-state memory devices, and optionally includes non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. Memory 370 optionally includes one or more storage devices that are remote from CPU(s) 310.In some embodiments, memory 370 stores programs, modules, and data structures similar to, or a subset of, the programs, modules, and data structures stored in memory 102 of portable multifunction device 100 (FIG. 1A). Additionally, memory 370 optionally stores additional programs, modules, and data structures not present in memory 102 of portable multifunction device 100. For example, memory 370 of device 300 optionally stores drawing module 380, presentation module 382, ​​word processing module 384, website creation module 386, disk authoring module 388, and / or spreadsheet module 390, while memory 102 of portable multifunction device 100 (FIG. 1A) optionally does not store these modules.

[0148] Each of the above-identified elements in FIG. 3 may be stored in one or more of the memory devices mentioned above. Each of the above-identified modules corresponds to an instruction set that performs the functions described above. The above-identified modules or programs (e.g., instruction sets) need not be implemented as separate software programs, procedures, or modules, and thus, in various embodiments, various subsets of these modules may be combined or otherwise rearranged. In some embodiments, memory 370 may store a subset of the above-identified modules and data structures. Additionally, memory 370 may store additional modules and data structures not described above.

[0149] Attention is now directed to user interface embodiments that may be implemented on portable multifunction device 100, for example.

[0150] 4A shows an exemplary user interface for a menu of applications on portable multifunction device 100, according to some embodiments. A similar user interface may be implemented on device 300. In some embodiments, user interface 400 includes the following elements, or a subset or superset thereof: ● signal strength indicator(s) 402 for wireless communication(s), such as cellular and Wi-Fi signals; ●Time 404, ●Bluetooth indicator 405 ● Battery status indicator 406, A tray 408 containing icons for frequently used applications, such as: ○ An icon 416 for the phone module 138, labeled "Phone", optionally including an indicator 414 of the number of missed calls or voicemail messages; ○ An icon 418 for the email client module 140, labeled "Mail", optionally including an indicator 410 of the number of unread emails; ○ An icon 420 for the browser module 147, labeled "Browser", and ○ An icon 422 for the video and music playback module 152, also referred to as the iPod (trademark of Apple Inc.) module 152, labeled "iPod"; and ●Icons for other applications, such as: ○ An icon 424 for the IM module 141, labeled "Messages"; ○ Icon 426 for the Calendar module 148, labeled "Calendar", ○ An icon 428 for the image management module 144, labeled "Photos"; ○ An icon 430 for the camera module 143, labeled "camera"; ○ An icon 432 for the online video module 155, labeled "Online Video"; ○ Icon 434 for stock widget 149-2, labeled "Stocks"; ○ Icon 436 for map module 154, labeled "Map"; ○ Icon 438 for weather widget 149-1, labeled "Weather"; ○ Icon 440 for alarm clock widget 149-4, labeled "Clock"; ○ An icon 442 for the training support module 142, labeled "Training Support"; ○ Icon 444 for the Notes module 153, labeled "Notes"; ○ An icon 446 for a settings application or module, labeled “Settings,” that provides access to settings related to the device 100 and its various applications 136.

[0151] 4A are merely exemplary. For example, icon 422 for video and music playback module 152 may optionally be labeled "Music" or "Music Player." Other labels are optionally used for the various application icons. In some embodiments, the label for each application icon includes the name of the application that corresponds to the respective application icon. In some embodiments, the label of a particular application icon is different from the name of the application that corresponds to the particular application icon.

[0152] 4B shows an exemplary user interface on a device (e.g., device 300 of FIG. 3) that includes a touch-sensitive surface 451 (e.g., tablet or touchpad 355 of FIG. 3) that is separate from display 450 (e.g., touchscreen display 112). Device 300 also optionally includes one or more contact intensity sensors (e.g., one or more of sensors 357) for detecting the intensity of a contact on touch-sensitive surface 451 and / or one or more tactile output generators 359 for generating a tactile output to a user of device 300.

[0153] Although some of the following examples are described with reference to input on touch screen display 112 (where the touch-sensitive surface and display are combined), in some embodiments, the device detects input on a touch-sensitive surface that is separate from the display, as shown in FIG. 4B. In some embodiments, this touch-sensitive surface (e.g., 451 in FIG. 4B) has a major axis (e.g., 452 in FIG. 4B) that corresponds to a major axis (e.g., 453 in FIG. 4B) on the display (e.g., 450). According to these embodiments, the device detects contact with touch-sensitive surface 451 (e.g., 460 and 462 in FIG. 4B) at locations that correspond to their respective locations on the display (e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470). In this manner, when the touch-sensitive surface is separate from the display, user input (e.g., contacts 460 and 462 and their movement) detected by the device on the touch-sensitive surface (e.g., 451 in FIG. 4B ) is used by the device to operate a user interface on the display (e.g., 450 in FIG. 4B ) of the multifunction device. It is to be understood that similar methods are optionally used for the other user interfaces described herein.

[0154] Furthermore, while the following description is primarily described with reference to finger input (e.g., finger contact, finger tap gesture, finger swipe gesture), it should be understood that in some embodiments, one or more of the finger inputs are replaced with input from another input device (e.g., mouse-based input or stylus input). For example, a swipe gesture is optionally replaced with a mouse click (e.g., instead of a contact) followed by cursor movement along the path of the swipe (e.g., instead of a contact movement). As another example, a tap gesture is optionally replaced with a mouse click while the cursor is positioned over the tap gesture location (e.g., instead of stopping contact detection following contact detection). Similarly, when multiple user inputs are detected simultaneously, it will be understood that multiple computer mice are optionally being used simultaneously, or that mice and finger contacts are optionally being used simultaneously.

[0155] FIG. 5A illustrates an exemplary personal electronic device 500. Device 500 includes a body 502. In some embodiments, device 500 may include some or all of the features described with respect to devices 100 and 300 (e.g., FIGS. 1A-4B). In some embodiments, device 500 has a touch-sensitive display screen 504, hereafter touchscreen 504. Instead of, or in addition to, touchscreen 504, device 500 has a display and a touch-sensitive surface. Similar to devices 100 and 300, in some embodiments, touchscreen 504 (or the touch-sensitive surface) may include one or more intensity sensors for detecting the intensity of a contact (e.g., a touch) being applied. The one or more intensity sensors of touchscreen 504 (or the touch-sensitive surface) may provide output data representative of the intensity of the touch. A user interface of device 500 may respond to a touch based on the intensity of the touch, meaning that touches of different intensities may invoke different user interface actions on device 500.

[0156] Techniques for detecting and processing touch intensity can be found, for example, in related applications, International Application No. PCT / US2013 / 040061, filed May 8, 2013, entitled "Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application," and PCT / US2013 / 069483, filed November 11, 2013, entitled "Device, Method, and Graphical User Interface for Transitioning Between Touch Input to Display Output Relationships," each of which is incorporated by reference in its entirety.

[0157] In some embodiments, device 500 has one or more input mechanisms 506 and 508. Input mechanisms 506 and 508, if included, can be physical. Examples of physical input mechanisms include push buttons and rotatable mechanisms. In some embodiments, device 500 has one or more attachment mechanisms. Such attachment mechanisms, if included, can allow device 500 to be attached to, for example, hats, eyewear, earrings, necklaces, shirts, jackets, bracelets, watch bands, chains, pants, belts, shoes, wallets, backpacks, etc. These attachment mechanisms allow device 500 to be worn by a user.

[0158] FIG. 5B illustrates an exemplary personal electronic device 500. In some embodiments, the device 500 may include some or all of the components described with respect to FIGS. 1A, 1B, and 3. The device 500 has a bus 512 operably connecting an I / O unit 514 to one or more computer processors 516 and a memory 518. The I / O unit 514 may be connected to a display 504, which may have a touch-sensitive component 522 and, optionally, a touch intensity sensing component 524. Additionally, the I / O unit 514 may connect 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 techniques. The device 500 may include an input mechanism 506 and / or an input mechanism 508. The input mechanism 506 may be, for example, a rotatable input device or a depressible and rotatable input device. The input mechanism 508 may be a button in some embodiments.

[0159] The input mechanism 508 may be a microphone in some embodiments. 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 may be operably connected to the I / O section 514.

[0160] 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 techniques described above, including processes 700, 900, 1100, 1300, 1500, 1700, and 1900 (FIGS. 7, 9, 11, 13, 15, 17, and 19). The personal electronic device 500 is not limited to the components and configuration of FIG. 5B and may include other or additional components in multiple configurations.

[0161] As used herein, the term "affordance" refers to a user-interactive graphical user interface object that may be displayed on a display screen of device 100, 300, and / or 500 (FIGS. 1, 3, and 5). For example, images (e.g., icons), buttons, and text (e.g., hyperlinks) can each constitute an affordance.

[0162] As used herein, the term "focus selector" refers to an input element that indicates the current portion of a user interface with which a user is interacting. In some implementations involving a cursor or other position marker, when an input (e.g., a press input) is detected on a touch-sensitive surface (e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B), the cursor acts as a "focus selector" when the cursor is over a particular user interface element (e.g., a button, window, slider, or other user interface element) and the particular user interface element is adjusted according to the detected input. In some implementations involving a touchscreen display (e.g., touch-sensitive display system 112 in FIG. 1A or touchscreen 112 in FIG. 4A) that allows direct interaction with user interface elements on the touchscreen display, contact detected on the touchscreen acts as a "focus selector" such that when an input (e.g., a press input by contact) is detected at the location of a particular user interface element (e.g., a button, window, slider, or other user interface element) on the touchscreen display, the particular user interface element is adjusted according to the detected input. In some implementations, focus is moved from one region of the user interface to another region of the user interface (e.g., by using the tab or arrow keys to move focus from one button to another) without a corresponding cursor movement or contact movement on the touch-screen display. In these implementations, the focus selector moves to follow the movement of focus between different regions of the user interface. Regardless of the specific form that the focus selector takes, the focus selector is generally a user interface element (or a contact on a touch-screen display) that is controlled by the user to communicate the user's intended interaction with the user interface (e.g., by indicating to the device which element of the user interface the user intends to interact with).For example, positioning of a focus selector (e.g., a cursor, touch, or selection box) over a corresponding button while a press input is detected on a touch-sensitive surface (e.g., a touchpad or touchscreen) indicates that the user intends to activate that corresponding button (and not another user interface element shown on the device's display).

[0163] As used herein and in the claims, the term "characteristic intensity" of a contact refers to a characteristic of that contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on a plurality of intensity samples. The characteristic intensity is optionally based on a predetermined number of intensity samples or a set of intensity samples collected within a predetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10 seconds) for a predetermined event (e.g., after detecting a contact, before detecting lift-off of the contact, before or after detecting the start of movement of the contact, before detecting the end of the contact, before or after detecting an increase in the intensity of the contact, and / or before or after detecting a decrease in the intensity of the contact). The characteristic intensity of a contact is optionally based on one or more of: a maximum intensity of the contact, a mean value of the intensity of the contact, an average value of the intensity of the contact, the top 10% of the intensity of the contact, half the maximum intensity of the contact, 90% of the maximum intensity of the contact, etc. In some embodiments, the duration of the contact is used to determine the characteristic intensity (e.g., when the characteristic intensity is an average of the intensity of the contact over time). In some embodiments, the characteristic intensity is compared to a set of one or more intensity thresholds to determine whether an action is performed by the user. For example, the set of one or more intensity thresholds may include a first intensity threshold and a second intensity threshold. In this example, a contact having a characteristic intensity that does not exceed the first threshold results in a first action being performed, a contact having a characteristic intensity that exceeds the first intensity threshold but does not exceed the second intensity threshold results in a second action being performed, and a contact having a characteristic intensity that exceeds the second threshold results in a third action being performed. In some embodiments, the comparison between the characteristic intensity and the one or more thresholds is not used to determine whether to perform the first or second action, but rather to determine whether to perform one or more actions (e.g., to perform the respective action or to omit performing the respective action).

[0164] FIG. 5C illustrates the detection of multiple contacts 552A-552E on the touch-sensitive display screen 504 by multiple intensity sensors 524A-524D. FIG. 5C additionally includes an intensity diagram illustrating the current intensity measurements of the intensity sensors 524A-524D in terms of intensity units. In this example, the intensity measurements of the intensity sensors 524A and 524D are each 9 intensity units, and the intensity measurements of the intensity sensors 524B and 524C are each 7 intensity units. In some implementations, the total intensity is the sum of the intensity measurements of the multiple intensity sensors 524A-524D, which in this example is 32 intensity units. In some embodiments, each contact is assigned a respective intensity that is a portion of the total intensity. FIG. 5D illustrates the assignment of the total intensity to the contacts 552A-552E based on the distance of the 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 of the total intensity, and each of contacts 552C and 552D is assigned a contact intensity of 4 intensity units of the total intensity. More generally, in some implementations, each contact j is assigned a respective intensity Ij that is a portion of the total intensity A according to a predetermined mathematical function Ij=A·(Dj / ΣDi), where Dj is the distance from the center of force to the respective contact j, and ΣDi is the sum of the distances from the center of force to all respective contacts (e.g., from i=1 to the end). The operations described with reference to Figures 5C-5D can be performed using electronic devices similar or identical to device 100, 300, or 500. In some embodiments, the characteristic intensity of the contact is based on one or more intensities of the contact. In some embodiments, an intensity sensor is used to determine a single characteristic intensity (e.g., a single characteristic intensity of a single contact). Note that the intensity plots are not part of the displayed user interface, but are included in FIGS. 5C-5D for the reader's convenience.

[0165] In some embodiments, a portion of the gesture is identified for purposes of determining the characteristic intensity. For example, a touch-sensitive surface may receive a continuous swipe contact that transitions from a start position to an end position where the intensity of the contact increases. In this example, the characteristic intensity of the contact at the end position may be based on only a portion of the swipe contact (e.g., only the portion of the swipe contact at the end position) rather than the entire continuous swipe contact. In some embodiments, a smoothing algorithm may be applied to the intensity of the swipe contact before determining the characteristic intensity of the contact. For example, the smoothing algorithm optionally includes one or more of an unweighted moving average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and / or an exponential smoothing algorithm. In some circumstances, these smoothing algorithms filter out small increases or decreases in the intensity of the swipe contact for purposes of determining the characteristic intensity.

[0166] The intensity of a contact on the touch-sensitive surface may be characterized against one or more intensity thresholds, such as a contact-detection intensity threshold, a light pressure intensity threshold, a deep pressure intensity threshold, and / or one or more other intensity thresholds. In some embodiments, the light pressure intensity threshold corresponds to an intensity that causes the device to perform an action typically associated with a physical mouse button or a click of a trackpad. In some embodiments, the deep pressure intensity threshold corresponds to an intensity that causes the device to perform an action different from the action typically associated with a physical mouse button or a click of a trackpad. In some embodiments, if a contact is detected with a characteristic intensity below the light pressure intensity threshold (e.g., and above a slight contact-detection intensity threshold below which the contact is no longer detected), the device moves a focus selector in accordance with the movement of the contact on the touch-sensitive surface without performing an action associated with the light pressure intensity threshold or the deep pressure intensity threshold. Generally, unless otherwise specified, these intensity thresholds are consistent across different sets of user interface diagrams.

[0167] An increase in the characteristic intensity of a contact from an intensity below a light pressure intensity threshold to an intensity between the light pressure intensity threshold and the deep pressure intensity threshold may be referred to as a "light press" input. An increase in the characteristic intensity of a contact from an intensity below a deep pressure intensity threshold to an intensity above a deep pressure intensity threshold may be referred to as a "deep press" input. An increase in the characteristic intensity of a contact from an intensity below a contact detection intensity threshold to an intensity between the contact detection intensity threshold and the light pressure intensity threshold may be referred to as detecting a contact on the touch surface. A decrease in the characteristic intensity of a contact from an intensity above the contact detection intensity threshold to an intensity below the contact detection intensity threshold may be referred to as detecting a lift-off of the contact 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.

[0168] In some embodiments described herein, one or more actions are performed in response to detection of a gesture including a respective pressure input or in response to detection of a respective pressure input performed on a respective contact (or multiple contacts), where the respective pressure input is detected based at least in part on detection of an increase in intensity of the contact (or multiple contacts) above a pressure input intensity threshold. In some embodiments, the respective actions are performed in response to detection of an increase in intensity of the corresponding contact (e.g., a "downstroke" of the corresponding pressure input) above a pressure input intensity threshold. In some embodiments, the pressure input includes an increase in intensity of the corresponding contact above a pressure input intensity threshold and a subsequent decrease in intensity of the contact below the pressure input intensity threshold, where the corresponding action is performed in response to detection of a subsequent decrease in intensity of the corresponding contact below the pressure input intensity threshold (e.g., an "upstroke" of the corresponding pressure input).

[0169] 5E to 5H show the results of the light pressure intensity threshold (e.g., “IT L " ) to the deep press intensity threshold in Figure 5H (e.g., "IT D5 illustrates detection of a gesture including a press input corresponding to an increase in the intensity of contact 562 to an intensity above a deep pressure intensity threshold (e.g., "IT 1"). The gesture made by contact 562 is detected on touch-sensitive surface 560. In doing so, cursor 576 is displayed over application icon 572B corresponding to app2 on displayed user interface 570, which includes application icons 572A-572D displayed in predetermined area 574. In some embodiments, the gesture is detected on touch-sensitive display 504. An intensity sensor detects the intensity of the contact on touch-sensitive surface 560. The device detects whether the intensity of contact 562 exceeds a deep pressure intensity threshold (e.g., "IT D Contact 562 is maintained on touch-sensitive surface 560. In response to detecting the gesture and during the gesture, a deep pressure intensity threshold (e.g., “IT D In response to contact 562 having an intensity greater than "," displaying reduced representations 578A-578C (e.g., thumbnails) of recently opened documents for app2, as shown in Figures 5F-5H. In some embodiments, the intensity is a characteristic intensity of the contact that is compared to one or more intensity thresholds. Note that the intensity diagram of contact 562 is not part of the displayed user interface, but is included in Figures 5E-5H for the reader.

[0170] In some embodiments, the display of representations 578A-578C includes an animation. For example, representation 578A is initially displayed near application icon 572B, as shown in FIG. 5F. As the animation progresses, representation 578A moves up and representation 578B is displayed near application icon 572B, as shown in FIG. 5G. Then, representation 578A moves up and representation 578B moves up toward representation 578A and representation 578C is displayed near application icon 572B, as shown in FIG. 5H. Representations 578A-578C form an array above icon 572B. In some embodiments, the animation progresses as a function of the intensity of contact 562, as shown in FIGS. 5F-5G, where the intensity of contact 562 exceeds a deep pressure intensity threshold (e.g., "IT D Representations 578A-578C appear and move upward as the intensity of the animation increases toward "intensity of contact." In some embodiments, the intensity on which the animation progression is based is a characteristic intensity of the contact. The operations described with reference to FIGS. 5E-5H may be performed using an electronic device similar or identical to device 100, 300, or 500.

[0171] In some embodiments, the device employs intensity hysteresis to avoid accidental inputs, sometimes referred to as "jitter," and the device defines or selects a hysteresis intensity threshold having a predetermined relationship to the pressure input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units below the pressure input intensity threshold, or the hysteresis intensity threshold is 75%, 90%, or some reasonable percentage of the pressure input intensity threshold). Thus, in some embodiments, the pressure input includes a corresponding increase in intensity of the contact above the pressure input intensity threshold and a subsequent decrease in intensity of the contact below a hysteresis intensity threshold corresponding to the pressure input intensity threshold, and a corresponding action is performed in response to detecting a subsequent corresponding decrease in intensity of the contact below that hysteresis intensity threshold (e.g., an "upstroke" of the corresponding pressure input). Similarly, in some embodiments, a pressure input is detected only when the device detects an increase in the intensity of the contact from an intensity below the hysteresis intensity threshold to an intensity above the pressure input intensity threshold, and optionally a subsequent decrease in the intensity of the contact to an intensity below the hysteresis intensity, and a corresponding action is performed in response to detection of that pressure input (e.g., an increase in the intensity of the contact or a decrease in the intensity of the contact, as the case may be).

[0172] For ease of explanation, an action is described as being performed in response to a pressure input associated with a pressure input intensity threshold or in response to a gesture including the pressure input, optionally triggered in response to detecting any of an increase in the intensity of the contact above the pressure input intensity threshold, an increase in the intensity of the contact from an intensity below a hysteresis intensity threshold to an intensity above the pressure input intensity threshold, a decrease in the intensity of the contact below the pressure input intensity threshold, and / or a decrease in the intensity of the contact below a hysteresis intensity threshold corresponding to the pressure input intensity threshold. Further, in examples where an action is described as being performed in response to detecting a decrease in the intensity of the contact below a pressure input intensity threshold, the action is optionally performed in response to detecting a decrease in the intensity of the contact below a hysteresis intensity threshold corresponding to and lower than the pressure input intensity threshold.

[0173] 5I illustrates exemplary devices connected via one or more communication channels to complete a payment transaction, according to some embodiments. One or more exemplary electronic devices (e.g., devices 100, 300, and 500) are configured to optionally detect input (e.g., specific user input, NFC field) and optionally transmit payment information (e.g., using NFC). One or more electronic devices optionally include NFC hardware and are configured to be NFC-enabled.

[0174] An electronic device (e.g., devices 100, 300, and 500) is optionally configured to store payment account information associated with each of one or more payment accounts. The payment account information includes, for example, one or more of a person's or company's name, a billing address, a login, a password, an account number, an expiration date, a security code, a phone number, a bank (e.g., an issuing bank) associated with the payment account, and a card network identifier. In some embodiments, the payment account information includes an image, such as a photo of a payment card (e.g., taken by the device and / or received by the device). In some embodiments, the electronic device receives user input that includes at least some payment account information (e.g., a credit, debit, account, or gift card number and expiration date entered by the user). In some embodiments, the electronic device detects at least some payment account information from an image (e.g., of the device's payment card captured by a camera sensor of the device). In some embodiments, the electronic device receives at least some payment account information from another device (e.g., another user device or a server). In some embodiments, the electronic device receives payment account information from a server associated with another service (e.g., an app for renting or selling audio and / or video files) for which the user or user device has previously made a purchase or identified payment account data.

[0175] In some embodiments, a payment account is added to an electronic device (e.g., devices 100, 300, and 500), resulting in the payment account information being securely stored on the electronic device. In some implementations, after a user initiates such a process, the electronic device transmits information about the payment account to a transaction reconciliation server, which then communicates with a server operated by the payment network regarding the account (e.g., a payment server) to ensure the validity of the information. The electronic device is optionally configured to receive a script from the server that enables the electronic device to program the payment information regarding the account onto the secure element.

[0176] In some embodiments, communication between electronic devices 100, 300, and 500 facilitates transactions (e.g., generally or specific transactions). For example, a first electronic device (e.g., 100) can act as a provisioning or management device and send notifications of new or updated payment account data (e.g., information about new accounts, updated information about existing accounts, and / or alerts related to existing accounts) to a second electronic device (e.g., 500). In another example, the first electronic device (e.g., 100) can send data to a second selection device, where the data reflects information about a payment transaction facilitated at the first electronic device. The information optionally includes one or more of the payment amount, the account used, the time of purchase, and whether the default account has been 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).

[0177] The electronic devices (e.g., 100, 300, 500) are configured to communicate with each other over any of a variety of networks. For example, the devices communicate using a Bluetooth connection 580 (including, e.g., a conventional Bluetooth connection or a Bluetooth Low Energy connection) or using a WiFi network 582. Communications between user devices are optionally regulated to reduce the possibility of information being inappropriately shared between the devices. For example, communications related to payment information require that the communicating devices are paired (e.g., associated with each other via explicit user interaction) or associated with the same user account.

[0178] In some embodiments, an electronic device (e.g., 100, 300, 500) is used to communicate with a point-of-sale (POS) payment terminal 820, 1220, which is optionally NFC-enabled. The communication is optionally performed using various communication channels and / or technologies. In one embodiment, the electronic device (e.g., 100, 300, 500) communicates with the payment terminal 820, 1220 using an NFC channel 584. In some embodiments, the payment terminal 820, 1220 communicates with the electronic device (e.g., 100, 300, 500) using a peer-to-peer NFC mode. The electronic device (e.g., 100, 300, 500) is optionally configured to transmit a signal to the payment terminal 820, 1220 that includes payment information regarding a payment account (e.g., a default account or an account selected for a particular transaction).

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

[0180] In some embodiments, the protocols associated with transaction participation depend, for example, on the type of device. For example, the conditions for generating and / or transmitting payment information may be different for a wearable device (e.g., device 500) and a phone (e.g., device 100). For example, a generating and / or transmitting condition for a wearable device may include detecting a button being pressed (e.g., after security verification), while a corresponding condition for a phone may not require a button press, but instead detection of a specific interaction with an application. In some implementations, the conditions for transmitting and / or publishing payment information include receiving a specific input at each of a plurality of devices. For example, publishing payment information optionally requires detection of a fingerprint and / or passcode on a device (e.g., device 100) and detection of a mechanical input (e.g., a button press) on another device (e.g., device 500).

[0181] The payment terminal 820, 1220 optionally uses the payment information to generate a signal to send to the 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 submitted purchase is authorized. In some implementations, the payment server 590 includes an issuing bank's server. The payment terminal 820, 1220 communicates with the payment server 590 directly or indirectly via one or more other devices or systems (e.g., an accruing bank's server and / or a card network's server).

[0182] Payment server 590 optionally uses at least a portion of the payment information to identify a user account in 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 whose particular payment information matches the payment information from the POS communication. In some implementations, a payment is denied when the provided payment information is inconsistent (e.g., an expiration date does not correspond to a credit, debit, or gift card number) or when no account exists with payment information matching the payment information from the POS communication.

[0183] In some embodiments, the data regarding the user account includes one or more of limitations (e.g., credit limit), current or previous balance, date, location, and / or amount of previous transactions, account status (e.g., active or frozen), and / or authorization instructions. In some implementations, the payment server (e.g., 590) uses such data to determine whether to authorize a payment. For example, the payment server denies a payment when adding the purchase amount to the current balance would exceed an account limit, when the account is frozen, when the amount of previous transactions exceeds a threshold, or when the number or frequency of previous transactions exceeds a threshold.

[0184] In some embodiments, the payment server 590 responds to the POS payment terminal 820, 1220 with an indication of whether the submitted purchase is authorized or denied. In some implementations, the POS payment terminal 820, 1220 sends a signal to the electronic device (e.g., 100, 300, 500) to identify this outcome. For example, the POS payment terminal 820, 1220 sends a receipt to the electronic device (e.g., 100, 300, 500) when the purchase is authorized (e.g., via a transaction reconciliation server that manages a transaction app on the user device). In some instances, the POS payment terminal 820, 1220 presents an output (e.g., a visual or audio output) indicating this outcome. Payment can be sent to the merchant as part of the authorization process or can be sent at a later time.

[0185] In some embodiments, the electronic device (e.g., 100, 300, 500) participates in a transaction that is completed without involving the POS payment terminal 820, 1220. For example, upon detecting that a mechanical input is being received, a secure element within the electronic device (e.g., 100, 300, 500) may expose payment information and allow an application on the electronic device to access this information (e.g., and transmit the information to a server associated with the application).

[0186] Attention is now directed to embodiments of user interfaces (“UI”) and associated processes that may be implemented in an electronic device such as portable multifunction device 100, device 300, or device 500.

[0187] Some embodiments described below relate to loyalty accounts. For example, a loyalty account may be an account of a loyalty program that provides structured marketing activities that reward customers / members. A loyalty account is optionally specific to one particular company, store, or chain of stores. A company (e.g., a retail store or chain of stores) may use a loyalty account to track purchases or other information about a user (e.g., a purchaser). A loyalty account typically entitles a user to discounts on current or future purchases and / or an allocation of points that can be used toward future purchases or gifts. In some implementations, a loyalty account cannot be used to make payments. In general, a loyalty account cannot be used to make monetary payments.

[0188] Some embodiments described below relate to private label accounts. For example, a private label account includes a payment account branded to represent a particular merchant, independent seller, or manufacturer. Some private label cards and private label accounts may only be accepted at a particular merchant or may offer some benefits that are only available at a particular merchant. For example, a particular merchant may offer a customer a private label account that can only be used when making purchases through the particular merchant. Merchants often prefer to offer private label accounts because they provide customers with another way to shop with the merchant, thereby increasing sales and providing customers with convenient payment options.

[0189] Some embodiments described below relate to transmitting payment account information from an electronic device to a contactless payment terminal that enables the contactless payment terminal to conduct a payment transaction, for example, by forwarding the information to one or more financial institutions to verify payment authentication information and / or receive authorization to complete the transaction. Additional details regarding an exemplary payment network architecture and forwarding for payment transactions can be found, for example, in FIG. 2 and the accompanying description of U.S. Patent Application No. 62 / 004,338, filed May 29, 2014, and entitled "USER DEVICE SECURE PARTICIPATION IN TRANSACTIONS VIA LOCAL SECURE ELEMENT DETECTION OF MECHANICAL INPUT" (Reference No. P22931USP1).

[0190] 6A-6G show example techniques and example user interfaces for receiving a selection of an account, such as a loyalty account or a payment account, from among multiple accounts in an electronic wallet, according to some embodiments. For example, account information for the selected account can then be sent 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, including the process of FIG. 7.

[0191] 6A shows a wearable electronic device 500, such as 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, etc.). The device receives an input (e.g., a user input) requesting that the device be enabled for a payment transaction (e.g., the user double-clicks a hardware button 508 on the device, which prepares the device to make an NFC payment and / or access the device's electronic wallet).

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

[0193] In 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. In Figure 6B, the one or more swipe inputs are detected and first visual indicator 602 is transitioning to an undisplayed state (e.g., by sliding first visual indicator 602 in a first direction). In some implementations, ready indication 604 is no longer displayed while first visual indicator 602 is transitioning to an undisplayed state.

[0194] As shown in FIG. 6C, in response to receiving one or more user swipe inputs, the device displays on the display a second visual indicator 620 that identifies a second account 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 conduct an NFC transaction using the second account and disables 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 may occupy more than 70% (or more than 60%, 50%, or 40%) of the total display space of the display. In FIG. 6C, the first visual indicator 602 is no longer displayed, and the paging dots 606 are updated to reflect that the device is now displaying information corresponding to the second account (e.g., the second visual indicator 620). The ready indication 622 is a visual indication that the device is enabled to participate in a transaction using the second account.

[0195] 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," has first background art corresponding to the background art of a payment card associated with the first account, at least a portion of an account number associated with the first account, and an expiration date associated with the first account. The second visual indicator 620 includes the name of the merchant associated with the loyalty account, "SUPERMARKET INC.", has second background art different from the first background art, and may or may not include at least a portion of an account number associated with the second account. In this example, the second visual indicator does not display an expiration date associated with the second account.

[0196] In some embodiments, the first account is a payment account and the second account is a loyalty account, as shown in Figures 6A-6C. In some embodiments, the first account is a payment account and the second account is a payment account, as shown in Figures 6A and 6G.

[0197] According to some embodiments, as shown in FIGS. 6D-6F, while displaying a 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, tapping on a "bar code display" 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 bar code or a QR code) on the display. The visual loyalty card code information may optionally represent account information of the second account. For example, in FIG. 6D, the device receives an upward swipe input on the touch-sensitive surface and in response displays bar code 624. A user may optically scan bar code 624 with a payment terminal. As another example, in FIG. 6D, the device receives the same upward swipe input on the touch-sensitive surface and in response displays affordance 626. This affordance 626, when activated, displays visual loyalty card code information (eg, 624) associated with the second account.

[0198] According to some embodiments, and with reference to the user interface of Figure 6C, a user may place the device within a field of a contactless payment terminal. During display of 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 account information regarding the second account to the contactless payment terminal via the one or more wireless communication elements, where the account information enables the contactless payment terminal to conduct a payment transaction.

[0199] According to some embodiments, conducting the payment transaction includes forwarding the loyalty information to one or more servers for loyalty account verification / authentication (e.g., when the second account is a loyalty account). In some embodiments, conducting the payment transaction includes forwarding the 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 a contactless payment terminal using NFC.

[0200] According to some embodiments (e.g., when the second account is a payment account), during display of the second visual indicator and after transmitting account information regarding the second account to the contactless payment terminal, the electronic device receives a failure communication from the contactless payment terminal via the one or more wireless communication elements (e.g., the payment was rejected because the contactless payment terminal did not accept the payment account type). In response to receiving the failure communication, the electronic device displays an indication on the display that the second account was not accepted 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).

[0201] According to some embodiments, after (or in response to) transmitting the account information regarding 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 were 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, a user may use the electronic device to provide loyalty account information using the second account and to provide payment account information using the first account. As a result, after the transaction, both visual indicators will be displayed simultaneously.

[0202] According to some embodiments, enabling the electronic device to participate in a transaction using a second account via one or more wireless communication elements does not require receiving a second user input requesting to enable the device for payment transactions, e.g., the user does not need to double-click the hardware button 508 again to prepare the device to make an NFC payment or NFC loyalty transaction using the second account.

[0203] According to some embodiments, enabling the electronic device to participate in a transaction using the first account includes displaying a first animation (e.g., 604) of a ready indicator emerging from beneath an image of a card for the first account (e.g., first visual indicator 602). The ready indicator (e.g., 604) indicates that the device has been enabled to participate in a payment transaction using the first account. In response to receiving a portion of the 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 beneath the image of the card for the first account.

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

[0205] 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). A first visual indicator of the first account (e.g., 602) has a first dimensional characteristic (e.g., a size or aspect ratio) and a second visual indicator of the second account (e.g., 620) 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 representation of the loyalty account is visually different from the visual representation of the payment account. This helps a user quickly identify whether a loyalty account or a payment account is being displayed and / or enabled.

[0206] According to some embodiments, the electronic wallet of the electronic device contains payment account information for multiple payment accounts associated with the user of the electronic device (eg, the payment accounts associated with 602 and 610).

[0207] As shown in Figure 6F, 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 on the display a third visual indicator identifying a third account, and the electronic device enables the electronic device to participate in a transaction using the third account via the one or more wireless communication elements (e.g., prepares the device to conduct NFC transactions using the third account and disables the device from participating in a transaction using the second account). The third visual indicator is distinct from the first visual indicator and the second visual indicator.

[0208] 7 is a flow diagram illustrating a method for receiving a selection of an account, such as a loyalty account or a payment account, from among multiple accounts in an electronic wallet using an electronic device, according to some embodiments. Method 700 is performed on a device (e.g., 100, 300, 500) that includes a display, a touch-sensitive surface, and one or more wireless communication elements. Some operations of method 700 may be combined, some operations may be reordered, and some operations may be omitted.

[0209] As described below, the method 700 provides an intuitive way to receive a selection of an account, such as a loyalty account or a payment account, from among multiple accounts in an electronic wallet. The method reduces the cognitive burden on the user receiving the account selection, thereby creating a more efficient human-machine interface. In the case of battery-operated computing devices, allowing the user to select an account faster and more efficiently conserves power and increases the time between battery charges.

[0210] In block 702, the electronic device receives input (eg, the user input at 508) requesting that the device be enabled for payment transactions.

[0211] In response to receiving input at block 704 requesting that the device be enabled for payment transactions, processing proceeds to blocks 706-708.

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

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

[0214] In block 712, in response to receiving one or more user swipe inputs, processing proceeds to blocks 714-716.

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

[0216] 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.

[0217] According to some embodiments, while displaying the second visual indicator (e.g., 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, a barcode or QR code) on the display.

[0218] According to some embodiments, a user may place the device within a field of a contactless payment terminal. During display of 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 account information regarding the second account to the contactless payment terminal via the one or more wireless communication elements, where the account information enables the contactless payment terminal to conduct a payment transaction.

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

[0220] According to some embodiments, after (or in response to) transmitting the account information regarding 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 were 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).

[0221] According to some embodiments, enabling the electronic device to participate in a transaction using the first account includes displaying a first animation (e.g., 604) of a ready indicator emerging from beneath an image of a card for the first account (e.g., first visual indicator 602). The ready indicator (e.g., 604) indicates that the device has been enabled to participate in a payment transaction using the first account. In response to receiving a portion of the 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 beneath the image of the card for the first account.

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

[0223] 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). A first visual indicator of the first account (e.g., 602) has a first dimensional characteristic (e.g., a size or aspect ratio) and a second visual indicator of the second account (e.g., 620) has a second dimensional characteristic that is different from the first dimensional characteristic (e.g., a different size or a different aspect ratio).

[0224] According to some embodiments, the electronic wallet of the electronic device contains payment account information for multiple payment accounts (eg, including the payment accounts associated with 602 and 610) associated with the user of the electronic device.

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

[0226] 8A-8D show example techniques and example user interfaces for selecting a displayed account, such as a loyalty account or a payment account, according to some embodiments. For example, account information for the selected account can then be transmitted to an NFC-enabled payment terminal for use in a transaction (e.g., when the device is placed in the payment terminal's field). The techniques can be performed in an electronic device with a display and a position sensor. The user interfaces in these figures are used to illustrate the processes described below, including the process of FIG. 9.

[0227] 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, the user may prefer to use the associated private label account or loyalty account in a transaction. For example, when a user is at a Joe's Electronics store, the user may prefer to use a private label account (e.g., a private label credit card account) associated with the Joe's Electronics store. As another example, when a user is at a supermarket, the user may prefer to use a loyalty account associated with the supermarket during a transaction in which the user makes a payment using a default payment account. Thus, displaying a visual representation of accounts related to a current situation (e.g., location) on the display of an electronic device provides value to the user.

[0228] For example, a payment account may be associated with multiple locations (e.g., multiple stores in a chain), and different locations may be associated with different payment accounts (e.g., a user may have 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 multiple Joe's Electronics stores, and the Jack's Home Improvement Store card is associated with multiple Jack's Home Improvement Stores).

[0229] 8A , the electronic device detects a current location using a location sensor (e.g., the electronic device determines that the device is physically located at a particular retailer or at a particular store of a particular retailer). The electronic device determines whether the current location is associated with a first account (e.g., the electronic device determines that a particular private label payment account or a particular loyalty account is associated with the retailer).

[0230] As shown in FIG. 8A , pursuant to not determining that the current location is associated with an account other than the default payment account (e.g., during the time between receiving a request to prepare a default payment account and preparing the default payment account) (e.g., the device determines that the device's location is not associated with the current location or the device fails to determine the device's location), the electronic device displays on the display a visual indication 802 of the default payment account (e.g., a visual depiction of a credit card associated with the default payment account). In some embodiments, the visual indication 802 of the default payment account is displayed and no graphic indicators for other accounts are displayed. In FIG. 8A , the ready indication 804 is a visual indication that the device is ready to participate in transactions using the default account represented by visual indicator 802.

[0231] The visual representation 802 of the default payment account includes a name of a first financial institution associated with the default payment account, “AA Bank,” first background art corresponding to the background art of a payment card associated with the default payment account, at least a portion of an account number associated with the default payment account, and an expiration date associated with the default payment account.

[0232] As shown in FIG. 8B, following a determination that the current location is associated with the first account, the electronic device simultaneously displays on the display a visual representation 802 of a default payment account (e.g., a visual representation of a credit card associated with the default payment account) and a visual representation 806 of a first account (e.g., a visual representation of a private label card or a particular loyalty account associated with the particular payment account). The default payment account and the first account are linked to the electronic device (e.g., stored in the device's electronic wallet and the electronic device is provisioned with both accounts), and the default payment account and the first account are different accounts. In FIG. 8B, the ready indication 804 is a visual indication that the device is ready to participate in a transaction using either (or both) of the default account represented by visual indicator 802 and the first account represented by visual indicator 806.

[0233] The visual representation 806 of the first payment account may include the name of the merchant or financial institution associated with the first account (e.g., “SHOPCO”), first background art corresponding to the first account, at least a portion of an account number associated with the first account, and an expiration date associated with the first account.

[0234] For example, a payment account (e.g., a first account) may be associated with multiple locations (e.g., multiple stores in a chain). 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 multiple Joe's Electronics stores, and the Jack's Home Improvement Store card is associated with multiple Jack's Home Improvement Stores).

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

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

[0237] According to some embodiments, as shown in FIG. 8D, the electronic device receives a request associated with a payment transaction from the contactless payment terminal 820 (e.g., while the device is within 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 a first account (e.g., when the device is placed within the field of an NFC-enabled terminal, the terminal requests a private label credit card of a particular retailer). Pursuant to a determination that the current location is associated with the first account and in accordance with a determination that the request includes a request for payment information using the first account type, the electronic device transmits, using one or more wireless communication elements, the payment account information of the first account to the contactless payment terminal, where the payment account information of the first account enables the contactless payment terminal to perform the payment transaction. In some embodiments, performing the payment transaction includes forwarding information to one or more financial institutions to verify payment authentication information and / or to receive authorization to complete the transaction. For example, the payment account information is transmitted to the contactless payment terminal using NFC. In some embodiments, conducting a payment transaction includes transmitting loyalty information to one or more servers for validation / authentication of the loyalty account.

[0238] 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 a field of an NFC-enabled terminal, the terminal requests a private label credit card for a particular retailer). Pursuant to determining that the current location is not associated with an account other than a default payment account (and in accordance with 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, payment account information for the default payment account to the contactless payment terminal, where the payment account information for the default payment account enables the contactless payment terminal to perform the payment transaction. In some embodiments, performing the payment transaction includes forwarding information to one or more financial institutions to verify payment authentication information and / or to receive authorization to complete the transaction. For example, the payment account information is transmitted to the contactless payment terminal using NFC.

[0239] According to some embodiments, the visual representation of the first account is displayed over the visual representation of the default account 802, where the visual representation of the first account indicates that the device is enabled to select the first account for use in a payment transaction without requiring additional user input. For example, the visual representation of the first account is simply text over an image of the default account's card, and the device determines (at the time of payment) which payment account to use without user intervention.

[0240] According to some embodiments, prior to detecting a current location using a location sensor, the electronic device receives an input (e.g., a user input) requesting that the device be enabled for payment transactions (e.g., a user double-clicks a hardware button 508 on the device, which prepares the device to make an NFC payment and / or access an electronic wallet). In some implementations, in response to receiving a user input requesting that the device be enabled for payment transactions, the device is enabled to participate in a transaction (e.g., prepares the device to make an NFC payment using a default payment account).

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

[0242] According to some embodiments, determining whether the current location is associated with the first account is responsive to receiving input requesting that the device be enabled for payment transactions (e.g., a user double-clicks a hardware button 508 on the device, which prepares the device to make an NFC payment and / or access an electronic wallet). In some implementations, in response to receiving user input requesting that the device be enabled for payment transactions, the device is enabled to participate in a transaction (e.g., preparing the device to make an NFC payment using a default payment account).

[0243] According to some embodiments, failure to determine that the current location is associated with an account other than the default payment account occurs when the electronic device fails to determine that the current location is associated with the first account before the electronic device is able to participate in a transaction using the default payment account via one or more wireless communication elements (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 using the default payment account via one or more wireless communication elements). Alternatively, optionally, the electronic device simultaneously displays on the display a visual representation of the default payment account and a visual representation of the first account, when the device detects that a user of the electronic device is still looking at the electronic device or that the electronic device is still facing the user. For example, simply changing the visual representation of the account on the display while (1) the user is still looking at the device or (2) the device is still facing the user provides the user with an opportunity to see the change and appreciate that a different payment account can be used in the payment transaction.

[0244] In some embodiments, when the electronic device is worn on a user's wrist, the electronic device can detect that the user is looking at the electronic device by detecting that the user moves the electronic device into a viewing position by raising or rotating their wrist (e.g., a raise gesture). The electronic device can detect that the user is no longer looking at the device by detecting that the user lowers their wrist. As used herein, a viewing position is a position of the electronic device at which the user can view the display of the electronic device. In some embodiments, the electronic device detects a signal indicative of the user raising or lowering their wrist, as described in U.S. Provisional Patent Application No. 62 / 026,532, "Raise Gesture Detection in a Device," which is incorporated by reference herein in its entirety.

[0245] In some embodiments, the raise gesture detection algorithm can proceed through a series of states that increase the confidence that a raise gesture has been made. For example, the raise gesture detection algorithm can select a set of motion sensor data samples (including accelerometer and / or gyro sensor data) that corresponds to a time span of interest (e.g., the time it would likely take a user to make a raise gesture). By considering the oldest sample or samples in the set, the algorithm can determine a "start pose" that can reflect the spatial orientation of the device at the beginning of the time span. This orientation can be relative to an assumed vertical axis of gravity. Based on the start pose, the algorithm can determine the amount and / or direction(s) of movement that would likely occur to bring the device's display into the user's line of sight (also referred to as the device being in a "focus pose"). This amount and / or direction(s) of movement that would likely occur can be expressed as criteria for identifying a "probable" raise gesture, and these criteria can be used to identify whether a possible raise gesture has occurred based on some or all of the set of motion sensor data samples. Additionally, a potential raise gesture may be identified as a "detected" raise gesture by determining whether a device that has reached the focus pose remains in the focus pose for at least a minimum amount of time. If necessary, further confirmation may be performed using a gesture classifier. The raise gesture detection algorithm may notify other components of the device whenever it identifies a potential raise gesture, a detected raise gesture, and / or a confirmed raise gesture.

[0246] According to some embodiments, the electronic device receives a request for loyalty account information from the contactless payment terminal, where the first account is a loyalty account. In response to receiving the request for loyalty account information, in accordance with not determining that the current location is associated with an account other than the default payment account (e.g., during the time between receiving the request to provision the account and provisioning the account), and in accordance with a subsequent determination that the current location is associated with the first account, the electronic device transmits account information regarding the first account to the contactless payment terminal via one or more wireless communication elements, and the electronic device also 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 regarding the first account is provided regardless of whether a representation of the first account is displayed on the display prior to making the payment transaction. In some embodiments, the account information regarding the first account is provided only when a representation of the first account is displayed on the display prior to making the payment transaction.

[0247] According to some embodiments, the 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 different payment account than the default payment account (e.g., when the device is placed in a field of an NFC-enabled terminal, the terminal requests a private label credit card of a particular retailer). In response to receiving the request for account information, pursuant to not determining that the current location is associated with an account other than the default payment account (e.g., during the time between receiving the request to provision the account and provisioning the account), and pursuant to a subsequent determination that the current location is associated with the first account, the electronic device ceases transmitting account information regarding 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 regarding the first account is provided only when a representation of the first account is displayed on the display prior to making the payment transaction.

[0248] According to some embodiments, the electronic device receives a request associated with a payment transaction from the contactless payment terminal. Prior to receiving the request associated with the payment transaction from the contactless payment terminal, a visual representation of a default payment account (e.g., a visual representation of a credit card associated with the default payment account) and a visual representation of a first account (e.g., a private label card or a visual representation of a particular loyalty account associated with the particular 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 an NFC-enabled terminal, the terminal requests a private label credit card of a particular retailer). The first account is a payment account of the first account type. In response to receiving the request for account information, and in accordance with not determining that the current location is associated with an account other than the default payment account (e.g., during the time between receiving the request to prepare the account and preparing the account), and in accordance with a subsequent determination that the current location is associated with the first account, the electronic device ceases transmitting account information regarding the default payment account to the contactless payment terminal via the one or more wireless communication elements, and the electronic device transmits payment account information for the first account to the contactless payment terminal via the one or more wireless communication elements.

[0249] According to some embodiments, following a determination that the current location is associated with the first account, the electronic device receives a failure communication from the contactless payment terminal via one or more wireless communication elements (e.g., the payment was rejected because the payment account has been dormant by the bank or has no funds). In response to receiving the failure communication, the electronic device transmits account information regarding a default payment account to the contactless payment terminal via one or more wireless communication elements (e.g., pay with a default card instead). 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 in the payment transaction.

[0250] According to some embodiments, simultaneously displaying the visual representation of the default payment account and the visual representation of the first account on the display includes simultaneously displaying the visual representation of the default payment account overlaid with (e.g., above or below) the visual representation of the first account on the display. In some embodiments, the visual representation of the first account is at least partially obscured by the visual representation of the default payment account.

[0251] 9 is a flow diagram illustrating a method 900 for selecting a displayed account, such as a loyalty account or a payment account, according to some embodiments. The method 900 is performed in a device (e.g., 100, 300, or 500) with a display and a position sensor. Some operations of the method 900 may be combined, some operations may be reordered, and some operations may be omitted.

[0252] As described below, method 900 provides an intuitive way to select a displayed account, such as a loyalty account or a payment account. This method reduces the cognitive burden on the user to select an account, thereby creating a more efficient human-machine interface. In the case of battery-operated computing devices, allowing a user to select an account faster and more efficiently conserves power and increases the time between battery charges.

[0253] In block 902, the electronic device detects a current location using a location sensor. In block 904, the electronic device determines whether the current location is associated with a first account.

[0254] In block 904, pursuant to determining that the current location is not associated with an account other than the default payment account, the electronic device displays on the display a visual representation of the default payment account (e.g., 802).

[0255] In block 906, pursuant to determining that the current location is associated with the first account, the electronic device simultaneously displays on the display a visual representation of the default payment account (e.g., 802) and a visual representation of the first account (e.g., 806 of FIG. 8B, 808 of FIG. 8C). 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.

[0256] 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 representation of the first account (e.g., 806) is an image of a payment card associated with the private label account. In some embodiments, the visual representation of the first account (e.g., 806) is displayed partially behind the visual representation of the default account (e.g., 802).

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

[0258] According to some embodiments, the electronic device receives a request associated with a payment transaction from the contactless payment terminal (e.g., while the device is within an 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 a first account. In accordance with determining that the current location is associated with the first account and in accordance with determining that the request includes a request for payment information using the first account type, the electronic device transmits, using one or more wireless communication elements, payment account information for the first account to the contactless payment terminal, where the payment account information for the first account enables the contactless payment terminal to perform the payment transaction. In some embodiments, performing the payment transaction includes forwarding information to one or more financial institutions to verify payment authentication information and / or to receive authorization to complete the transaction. For example, the payment account information is transmitted to the contactless payment terminal using NFC. In some embodiments, performing the payment transaction includes forwarding loyalty information to one or more servers for loyalty account verification / authentication.

[0259] 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. Pursuant to determining that the current location is not associated with an account other than the default payment account (and in accordance with 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, payment account information of the default payment account to the contactless payment terminal, where the payment account information of the default payment account enables the contactless payment terminal to perform the payment transaction. In some embodiments, performing the payment transaction includes forwarding information to one or more financial institutions to verify payment authentication information and / or to receive authorization to complete the transaction.

[0260] According to some embodiments, the visual representation of the first account is displayed over a visual representation of a default account (e.g., 802), where the visual representation of the first account indicates that the device is enabled to select the first account for use in a payment transaction without requiring additional user input.

[0261] According to some embodiments, prior to detecting a current location using a location sensor, the electronic device receives an input (eg, a user input) requesting that the device be enabled for a payment transaction.

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

[0263] According to some embodiments, determining whether the current location is associated with the first account is in response to receiving an input requesting to enable the device for a payment transaction (e.g., the user double-clicks the device's hardware button 508, which prepares the device to make an NFC payment and / or access an electronic wallet).

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

[0265] In some embodiments, when the electronic device is worn on a user's wrist, the electronic device can detect that the user is looking at the electronic device by detecting the user raising or rotating their wrist to move the electronic device into a viewing position. The electronic device can detect that the user is no longer looking at the device by detecting the user lowering their wrist. As used herein, a viewing position is a position of the electronic device at which the user can see the display of the electronic device.

[0266] According to some embodiments, the electronic device receives a request for loyalty account information from the contactless payment terminal, where the first account is a loyalty account. In response to receiving the request for loyalty account information, in accordance with not determining that the current location is associated with an account other than the default payment account (e.g., during the time between receiving the request to provision the account and provisioning the account), and in accordance with a subsequent determination that the current location is associated with the first account, the electronic device transmits account information regarding the first account to the contactless payment terminal via one or more wireless communication elements, and the electronic device also 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 regarding the first account is provided regardless of whether a representation of the first account is displayed on the display prior to making the payment transaction. In some embodiments, the account information regarding the first account is provided only when a representation of the first account is displayed on the display prior to making the payment transaction.

[0267] According to some embodiments, the 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 different payment account than the default payment account. In response to receiving the request for account information, in accordance with not determining that the current location is associated with an account other than the default payment account (e.g., during the time between receiving the request to provision the account and provisioning the account), and in accordance with a subsequent determination that the current location is associated with the first account, the electronic device ceases transmitting account information regarding the first account to the contactless payment terminal via the 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 the one or more wireless communication elements. In some embodiments, the account information regarding the first account is provided only when a representation of the first account is displayed on the display prior to making the payment transaction.

[0268] According to some embodiments, the electronic device receives a request associated with a payment transaction from the contactless payment terminal. Prior to receiving the request associated with the payment transaction from the contactless payment terminal, a visual representation of the default payment account (e.g., 802) and a visual representation of the first account (e.g., 806 or 808) were 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 a field of an NFC-enabled terminal, the terminal requests a private label credit card of a particular retailer). The first account is a payment account of the first account type. In response to receiving the request for account information, and in accordance with not determining that the current location is associated with an account other than the default payment account (e.g., during the time between receiving the request to provision the account and provisioning the account), and in accordance with a subsequent determination that the current location is associated with the first account, the electronic device ceases transmitting account information regarding the default payment account to the contactless payment terminal via one or more wireless communication elements, and the electronic device transmits payment account information of the first account to the contactless payment terminal via one or more wireless communication elements.

[0269] According to some embodiments, following a determination that the current location is associated with the first account, the electronic device receives a failure communication from the contactless payment terminal via one or more wireless communication elements (e.g., the payment was rejected because the payment account has been dormant by the bank or has no funds). In response to receiving the failure communication, the electronic device transmits account information regarding a default payment account to the contactless payment terminal via one or more wireless communication elements (e.g., pay with a default card instead). 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 in the payment transaction.

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

[0271] It should be noted that the details of the process (e.g., FIG. 9) described above with respect to method 900 are also applicable in an analogous manner to the methods described above and below. For example, methods 700, 1100, 1300, 1500, 1700, and 1900 may include one or more of the features of the various methods described above with reference to method 900. For example, the electronic wallet, payment account, loyalty account, affordances, and inputs of methods 700, 1100, 1300, 1500, 1700, and 1900 optionally have one or more of the features of the electronic device, payment account, loyalty account, affordances, and inputs of the electronic device described in method 900. For the sake of brevity, these details will not be repeated below.

[0272] 10A-10E show an example technique and an example user interface for selecting a displayed account, such as a loyalty account or a payment account, from among multiple accounts in an electronic wallet, according to some embodiments. For example, account information for the selected account can 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 technique is performed in an electronic device with a display, a position sensor, and one or more wireless communication elements. The user interfaces in these figures are used to illustrate the processes described below, including the process of FIG. 11.

[0273] The electronic device receives input (e.g., user input) requesting that the device be enabled for a payment transaction (e.g., the user double-clicks the device's hardware button 508 to prepare the device to make an NFC payment).

[0274] In response to receiving the input, the electronic device detects a current location using a location sensor (e.g., determining 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 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 (e.g., determining that a particular private label payment account is associated with the retailer).

[0275] As shown in FIG. 10A , following a determination that the set of one or more payment criteria has not been satisfied, the electronic device displays on the display a visual representation 1002 of a default payment account, where the default payment account is different from the first payment account (e.g., ceases displaying the visual representation 1002 of a credit card associated with the default payment account and the representation of the first payment account).

[0276] The device may display an indication 1006 on the display that other accounts are available or an indication 1006 of the number of other accounts available. In this example, the indication 1006 includes four paging dots. The first paging dot is of a first color that is different from the second color of the second, third, and fourth paging dots. The four paging dots indicate that a total of four accounts are available. The first paging dot, which is a different color from the other paging dots, indicates that the device is currently displaying information (e.g., visual indication 1002) corresponding to the default payment account.

[0277] The device may also display a ready indication 1004 on the display. The ready indication 1004 is a visual indication that the device is ready to participate in a transaction using the default payment account represented by visual indication 1002. The visual indication 1002 may include the name of the financial institution associated with the default payment account, "AA Bank," background art corresponding to the background art 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 an expiration date associated with the default payment account.

[0278] As shown in FIG. 10B, following a determination that a set of one or more payment criteria are satisfied, the electronic device displays on the display a visual representation 1008 of the first payment account (and ceases to display a representation of the default payment account).

[0279] The device may also display a ready indication 1010 on the display. The ready indication 1010 is a visual indication that the device is ready 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," background art corresponding to the background art of a private label card associated with the first payment account, at least a portion of an account number associated with the first payment account, and an expiration date associated with the first payment account.

[0280] According to some embodiments, in response to a determination that the set of one or more payment criteria is satisfied, the electronic device enables the electronic device to participate in a transaction using the first payment account via the one or more wireless communication elements. Further, the electronic device may discontinue enabling the electronic device to participate in a transaction using the default payment account.

[0281] According to some embodiments, in response to a determination that the set of one or more payment criteria is not satisfied, the electronic device enables the electronic device to participate in the transaction using the default payment account via the one or more wireless communication elements. Further, the electronic device may discontinue enabling the electronic device to participate in the transaction using the first payment account.

[0282] According to some embodiments, following a determination that the set of one or more payment criteria has not been satisfied, the electronic device ceases displaying a visual representation of the first payment account on the display (e.g., displays a visual representation of a default payment account and does not display a visual representation of the first payment account).

[0283] According to some embodiments, the electronic device includes a touch-sensitive surface. As shown in FIG. 10C, 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 device orientation in the first direction). As shown in FIG. 10D, in response to receiving the one or more inputs, the electronic device displays on the display a second visual indicator 1012 that identifies (e.g., identifies) 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 NFC transactions using the second account and disables the device from participating in a transaction using the first account). Thus, when the device presents a payment account, 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 device's electronic wallet).

[0284] According to some embodiments, the electronic device receives a request for account information from the contactless payment terminal (e.g., when the device detects that a user has placed the device within the field of an NFC-enabled contactless payment terminal). In response to receiving the request for account information, the electronic device transmits, via one or more wireless communication elements, account information for each enabled account (e.g., any account for which the device has been enabled to participate in payment transactions, any currently displayed account) to the contactless payment terminal, where the account information enables the contactless payment terminal to perform the payment transaction. In some embodiments, performing the payment transaction includes forwarding information to one or more financial institutions to verify payment authentication information (e.g., when account information for a payment account is transmitted to the terminal) and / or to receive authorization to complete the transaction. For example, the payment account information is transmitted to the contactless payment terminal using NFC. In some embodiments, performing the payment transaction includes forwarding loyalty information to one or more servers for verification / authentication of the loyalty account (e.g., when account information for a loyalty account is transmitted to the terminal).

[0285] According to some embodiments, the set of one or more criteria includes criteria that are satisfied when the device is authenticated to transact using a first payment account (e.g., without user confirmation) in the current location (e.g., to override a default payment account).

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

[0287] According to some embodiments, the electronic device includes one or more input devices. Prior to receiving user input requesting to enable the device for payment transactions, the electronic device receives a request (e.g., manually entered, imported from a server, or entered using a camera sensor on the electronic device) to link a payment account with the electronic device. The request includes account information (e.g., card number, card expiration date, name on card) for the payment account. The electronic device links the payment account with the electronic device (e.g., adds the payment account to an electronic wallet on the electronic device). The electronic device determines that a financial institution associated with the payment account has authorized the location-based selected payment account without user input. The electronic device receives user input to activate the location-based selected payment account without user input, as shown in FIG. 10E.

[0288] As shown in FIG. 10E, the user can activate the payment account to be used for location-based selection by activating the yes affordance 1030. Alternatively, the user can cancel the activation of the location-based selection of the payment account by activating the no affordance 1032. In some embodiments, the option to activate the location-based selection of the payment account is displayed during the setup of the card (e.g., while the card is linked to the electronic device or shortly thereafter). Alternatively (or in addition), the financial institution can authorize the location-based selection of the payment account (without user input) at a point after the payment account is linked to the electronic device. In this situation, a new option may appear in the setup menu for the payment account. Similarly, the device can display a pop-up notification when the device detects that a payment is to be made. The notification indicates that the payment account is now capable of location-based selection. The user can then choose to activate (or not activate) the functionality for location-based selection without user input.

[0289] According to some embodiments, in response to a determination that a set of one or more payment criteria is satisfied, the 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 using an account type corresponding to a second payment account different from the first payment account (e.g., when the device is placed in a field of an NFC-enabled terminal, the terminal requests a private label credit card of a particular retailer). In response to a determination that the request includes a request for payment information using the second account type, the electronic device provides a notification (e.g., visual, audio, or tactile) requesting authorization to transmit payment account information of the second account to the contactless payment terminal using one or more wireless communication elements, where the payment account information of the second account enables the contactless payment terminal to conduct the payment transaction. Thus, when the device determines that a first payment account is appropriate for a particular location, but the contactless payment terminal requests a payment using a different payment account, the user is notified and requested to provide authorization to proceed with the payment transaction using the second payment account.

[0290] 11 is a flow diagram illustrating a method 1100 for selecting a displayed account, such as a loyalty account or a payment account, among multiple accounts in an electronic wallet, according to some embodiments. The method 1100 is performed in a device (e.g., 100, 300 or 500) equipped with a display and a position sensor. Some operations of the method 1100 may be combined, some operations may be reordered, and some operations may be omitted.

[0291] As described below, method 1100 provides an intuitive way to select an account. This method reduces the cognitive burden on the user of selecting an account for display and / or payment, thereby creating a more efficient human-machine interface. In the case of battery-operated computing devices, allowing the user to select an account faster and more efficiently conserves power and increases the time between battery charges.

[0292] In block 1102, the electronic device receives input (e.g., user input) requesting that the device be enabled for a payment transaction (e.g., the user double-clicks the device's hardware button 508 to prepare the device to make an NFC payment).

[0293] In response to receiving the input at block 1104, the technique continues to block 1106. At block 1106, the electronic device detects a current location using a location sensor (e.g., determines that the device is physically located at a particular retailer or at a particular store of a particular retailer).

[0294] In block 1108, the electronic device determines 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 (e.g., determining that a particular private label payment account is associated with the retailer).

[0295] In block 1110, pursuant to a determination that the set of one or more payment criteria has not been satisfied, the electronic device displays on the display a visual representation of a default payment account (e.g., 1002), where the default payment account is different from the first payment account (e.g., ceasing to display the visual representation of the credit card associated with the default payment account and the representation of the particular payment account).

[0296] According to some embodiments, at block 1112, following a determination that the set of one or more payment criteria is not satisfied, the electronic device enables the electronic device to participate in the transaction using a default payment account via one or more wireless communication elements.

[0297] In block 1114, pursuant to a determination that the set of one or more payment criteria is satisfied, the electronic device displays on the display a visual representation of the first payment account (e.g., 1008) (and ceases displaying the representation of the default payment account).

[0298] According to some embodiments, at block 1116, in accordance with a determination that the set of one or more payment criteria are satisfied, the electronic device enables the electronic device to participate in the transaction using the first payment account via the one or more wireless communication elements.

[0299] According to some embodiments, following a determination that the set of one or more payment criteria has not been satisfied, the electronic device ceases displaying the visual representation of the first payment account (e.g., 1008) on the display (e.g., displaying a visual representation of the default payment account and not displaying the visual representation of the first payment account).

[0300] 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., one or more left or right swipes via the touch-sensitive surface or detection of a change in device orientation in the first direction). In response to receiving the one or more inputs, the electronic device displays on the display a second visual indicator (e.g., 1012) that identifies a second account different from the first payment account and the default payment account, and the electronic device enables the electronic device to participate in transactions using the second account via one or more wireless communication elements (e.g., prepares the device to conduct NFC transactions using the second account and disables the device from participating in transactions using the first account).

[0301] According to some embodiments, the electronic device receives a request for account information from the contactless payment terminal. In response to receiving the request for account information, the electronic device transmits, via one or more wireless communication elements, account information for each enabled account to the contactless payment terminal, where the account information enables the contactless payment terminal to conduct a payment transaction. In some embodiments, conducting the payment transaction includes forwarding information to one or more financial institutions to verify payment authentication information (e.g., when account information for a payment account is transmitted to the terminal) and / or to receive authorization to complete the transaction.

[0302] According to some embodiments, the set of one or more criteria includes criteria that are satisfied when the device is authenticated to transact using a first payment account (e.g., without user confirmation) in the current location (e.g., to override a default payment account).

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

[0304] According to some embodiments, the electronic device includes one or more input devices. Prior to receiving user input requesting to enable the device for payment transactions, the electronic device receives a request (e.g., manually entered, imported from a server, or entered using a camera sensor on the electronic device) to link a payment account with the electronic device. The request includes account information (e.g., card number, card expiration date, name on card) for the payment account. The electronic device links the payment account with the electronic device (e.g., adds the payment account to an electronic wallet on the electronic device). The electronic device determines that a financial institution associated with the payment account has authorized the location-based selected payment account without user input. The electronic device receives user input to activate the location-based selected payment account without user input.

[0305] According to some embodiments, in response to a determination that a set of one or more payment criteria is satisfied, the 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 using an account type corresponding to a second payment account different from the first payment account (e.g., when the device is placed in a field of an NFC-enabled terminal, the terminal requests a private label credit card of a particular retailer). In response to a determination that the request includes a request for payment information using the second account type, the electronic device provides a notification (e.g., visual, audio, or tactile) requesting authorization to transmit payment account information of the second account to the contactless payment terminal using one or more wireless communication elements, where the payment account information of the second account enables the contactless payment terminal to conduct the payment transaction. Thus, when the device determines that a first payment account is appropriate for a particular location, but the contactless payment terminal requests a payment using a different payment account, the user is notified and requested to provide authorization to proceed with the payment transaction using the second payment account.

[0306] It should be noted that the details of the process (e.g., FIG. 11) described above with respect to method 1100 are also applicable in an analogous manner to the methods described above and below. For example, methods 700, 900, 1300, 1500, 1700 and 1900 may include one or more of the 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 of the features of the electronic device, payment account, loyalty account, affordances and inputs of the electronic device described in method 1100. For the sake of brevity, these details will not be repeated below.

[0307] 12A-12D show an example technique and an example user interface for transmitting account information of a selected account among multiple accounts in an electronic wallet according to some embodiments. The technique is performed in an electronic device having a display and one or more wireless communication elements (e.g., one or more wireless antennas such as an NFC antenna, a WiFi antenna, etc.). The user interfaces in these figures are used to illustrate the processes described below, including the process of FIG. 13.

[0308] The electronic device receives an input (e.g., user input) requesting that the device be enabled for a payment transaction (e.g., the user double-clicks a hardware button on the device to prepare the device to make an NFC payment). In Figure 12A, in response to receiving the input, the electronic device displays on the display a payment indication (e.g., 1202) representing multiple payment accounts, including a first payment account and a second payment account (e.g., displays a "smart selection" indication that does not identify a particular payment account).

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

[0310] In response to receiving a request for account information corresponding to a payment transaction, and in accordance with a determination that a payment criterion for the first payment account is satisfied (e.g., the first payment account is associated with the device's current location), the electronic device transmits, via one or more wireless communication elements, account information for the first payment account, without transmitting account information for the second payment account (and, optionally, without transmitting payment account information for any other payment accounts associated with payment indications other than the first payment account). In response to receiving a request for account information corresponding to a payment transaction, and in accordance with a determination that a payment criterion for the second payment account is satisfied (e.g., the second payment account is associated with the device's current location), the electronic device transmits, via one or more wireless communication elements, account information for the second payment account, without transmitting account information for the first payment account (and, optionally, without transmitting payment account information for any other payment accounts associated with payment indications other than the second payment account). Thus, the user may see a visual indication that the "smart selection" function has been selected. When the device detects an attempt to make a payment, the electronic device transmits account information for the appropriate account.

[0311] According to some embodiments, the electronic device is configured to enable payment using a default payment account and one of a number of non-default payment accounts (e.g., payment accounts that are used only when payment criteria corresponding to the respective payment accounts are satisfied). Pursuant to a determination that payment criteria are not satisfied for any of the non-default payment accounts, the electronic device transmits, via the one or more wireless communication elements, account information for the default payment account without transmitting account information for the non-default payment accounts.

[0312] According to some embodiments, the payment criteria include criteria based on a determination associated with a current location of the electronic device. For example, the criteria are satisfied when the electronic device is within a defined geographic area. As another example, the criteria are not satisfied when the electronic device is not within the defined geographic area.

[0313] According to some embodiments, as shown in FIG. 12A, the payment display 1202 representing multiple payment accounts does not include a display of the first payment account and does not include a display of the second payment account. For example, there is no display on the display indicating the first payment account or the second payment account. The payment display 1202 representing multiple payment accounts does not look like a credit card or like a display of the first payment account or a display of the second payment account. Thus, a user can understand at a glance that the device is in a special operating mode.

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

[0315] According to some embodiments, the plurality of payment accounts includes only those payment accounts for which a financial institution associated with the payment account has authorized the payment account to be selected based on location without corresponding user input.

[0316] According to some embodiments, a contextual selection mode of operation, in which the device selects which of a plurality of payment accounts to use for a payment transaction based on a context, is represented as a selectable payment option. In some embodiments, the device receives a selection of the selectable payment option and switches to the contextual selection mode of operation in response to the selection of the selectable payment option.

[0317] In FIG. 12C, according to some embodiments, the electronic device includes a touch-sensitive surface. For example, prior to making a payment as shown in FIG. 12B, the electronic device receives one or more inputs (e.g., user inputs) in a first direction (e.g., one or more left or right swipes via the touch-sensitive surface or a change in the orientation of the device in the first direction). As shown in FIG. 12C, the electronic device may display an animation that includes transitioning the payment indication 1202 off the display. In response to receiving the one or more inputs, the electronic device replaces on the display the payment indication 1202 representing the multiple payment accounts with a second visual indicator 1220 that is different from the payment indication 1202 representing the multiple payment accounts, where the second visual selection indicator identifies a third payment account that is 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 disables the device from participating in a transaction using the first account). Thus, the user may select a particular payment account, after which the user may make a payment using that account, as shown in Figure 12B.

[0318] According to some embodiments, a payment indication 1202 representing multiple payment accounts is distinct from the visual indicators (e.g., 1220) of individual payment accounts of the multiple payment accounts. For example, payment indication 1202 includes a logo without a surrounding card, while all other payment accounts are represented by card images (e.g., visual indication 1220). Or, the payment indication is accompanied by text (e.g., "AUTO SELECT") indicating that it represents a contextual selection between multiple different payment accounts.

[0319] 13 is a flow diagram illustrating a method for transmitting account information of a selected account among multiple accounts in an electronic wallet, according to some embodiments. The method 1300 is performed in a device (e.g., 100, 300, 500) that includes a display and one or more wireless communication elements. Some operations of the method 1300 may be combined, some operations may be reordered, and some operations may be omitted.

[0320] As described below, the method 1300 provides an intuitive way to transmit account information of a selected account among multiple accounts in an electronic wallet. This method reduces the cognitive burden on the user to select an account to use in a payment, thereby creating a more efficient human-machine interface. In the case of battery-operated computing devices, allowing the user to select an account faster and more efficiently conserves power and increases the time between battery charges.

[0321] In block 1302, the electronic device receives input (e.g., user input) requesting that the device be enabled for a payment transaction (e.g., the user double-clicks the device's hardware button 508 to prepare the device to make an NFC payment).

[0322] At block 1304, in response to receiving the input, the electronic device displays on the display a payment display (e.g., 1202) representing a plurality of payment accounts, including the first payment account and the second payment account (e.g., displaying a “smart selection” display that does not identify a particular payment account).

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

[0324] In block 1308, in response to receiving a request for account information corresponding to the payment transaction, the technique proceeds to blocks 1310-1312. In block 1310, pursuant to a determination that the payment criteria for the first payment account are satisfied, the electronic device transmits, via one or more wireless communication elements, account information for the first payment account without transmitting account information for the second payment account (and, optionally, without transmitting payment account information for any other payment accounts associated with payment indications other than the first payment account).

[0325] In block 1312, pursuant to a determination that the payment criteria for the second payment account are satisfied, transmitting, via one or more wireless communication elements, account information for the second payment account without transmitting account information for the first payment account (and, optionally, without transmitting payment account information for any other payment accounts associated with payment indications other than the second payment account).

[0326] According to some embodiments, the electronic device is configured to enable payment using a default payment account and one of a number of non-default payment accounts (e.g., payment accounts that are used only when payment criteria for the payment accounts are satisfied). Pursuant to a determination that payment criteria are not satisfied for any of the non-default payment accounts, the electronic device transmits, via the one or more wireless communication elements, account information for the default payment account without transmitting account information for the non-default payment accounts.

[0327] According to some embodiments, the payment criteria include criteria based on a determination associated with a current location of the electronic device. For example, the criteria are satisfied when the electronic device is within a defined geographic area. As another example, the criteria are not satisfied when the electronic device is not within the defined geographic area.

[0328] According to some embodiments, a payment indication (eg, 1202) representing multiple payment accounts does not include an indication of the first payment account and does not include an indication of the second payment account.

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

[0330] According to some embodiments, the plurality of payment accounts includes only those payment accounts for which a financial institution associated with the payment account has respectively authorized the payment account to be selected based on location without user input.

[0331] According to some embodiments, a contextual selection mode of operation, in which the device selects which of a plurality of payment accounts to use for a payment transaction based on a context, is represented as a selectable payment option. In some embodiments, the device receives a selection of the selectable payment option and switches to the contextual selection mode of operation in response to the selection of the selectable payment option.

[0332] According to some embodiments, an electronic device includes a touch-sensitive surface. The electronic device receives one or more inputs (e.g., user inputs) in a first direction (e.g., one or more left or right swipes via the touch-sensitive surface or a change in orientation of the device in the first direction). In response to receiving the one or more inputs, the electronic device replaces on the display a payment indication (e.g., 1202) representing the multiple payment accounts with a second visual indicator (e.g., 1220) that is different from the payment indication (e.g., 1202) representing the multiple payment accounts, where the second visual selection indicator identifies a third payment account that is different from the first and second payment accounts. 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. In this way, a user can select a particular payment account.

[0333] According to some embodiments, a payment display (eg, 1202) representing multiple payment accounts is distinct from visual indicators (eg, 1220) of individual payment accounts of the multiple payment accounts.

[0334] It should be noted that the details of the process (e.g., FIG. 13) described above with respect to method 1300 are also applicable in an analogous manner to the methods described above and below. For example, methods 700, 900, 1100, 1500, 1700 and 1900 may include one or more of the features of the various methods described above with reference to method 1300. For example, the electronic wallet, payment account, loyalty account, affordances and inputs of methods 700, 900, 1100, 1500, 1700 and 1900 optionally have one or more of the features of the electronic device, payment account, loyalty account, affordances and inputs of the electronic device described in method 1300. For the sake of brevity, these details will not be repeated below.

[0335] 14A-14E show example techniques and example user interfaces for receiving a selection of an account from among multiple accounts in an electronic wallet, according to some embodiments. For example, account information for the selected account can 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 techniques are performed in an electronic device with 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, including the process of FIG. 15.

[0336] The electronic device receives a first input (e.g., a user input on a hardware button), e.g., a user double-clicks a mechanical or capacitive button 508 on the device.

[0337] As shown in Figure 14A, in response to receiving the first input, the electronic device displays on the display a first user interface (e.g., the user interface of Figure 14A), where the first user interface includes a first visual indicator 1402 identifying a payment card associated with a plurality of payment accounts and a second visual indicator 1406 identifying a first payment account (e.g., a savings account) of the plurality of payment accounts of the payment card. As shown in Figure 14A, 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 name of the financial institution offering the payment account, an account number, an expiration date, and background art.

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

[0339] 14B, the electronic device detects a first contact on the touch-sensitive surface. The electronic device determines whether a characteristic intensity of the first contact exceeds an intensity threshold.

[0340] 14C and 14D, pursuant to determining that the characteristic intensity of the first contact exceeds an intensity threshold (e.g., a hard press), the electronic device displays, on the display, a second user interface that allows a selection between different payment accounts represented by the first visual indicators. For example, a hard press can result in the display of the user interface of FIG. 14D. As another example, a hard press can result in the display of FIG. 14C, after which activation of affordance 1412 in the user interface of FIG. 14C results in the display of the user interface of FIG. 14D.

[0341] There are multiple ways for a user to access a user interface that allows selection among multiple payment accounts of a payment card. One way is to enable the electronic device to perform a payment transaction (e.g., using an electronic wallet application), which results in the display of the first visual indicator while the device is in a payment mode, as discussed above. Another way is to access settings or details of a particular payment account from the electronic wallet application, which results in the display of the first visual indicator while the device is not in a payment mode (e.g., not enabled to perform payment transactions via one or more wireless communication elements). While displaying the user interface (and not in a payment mode), the device detects a contact on the touch-sensitive surface, the device determines whether a characteristic intensity of the contact exceeds an intensity threshold, and pursuant to a determination that the characteristic intensity of the contact exceeds an intensity threshold (e.g., a hard press), the device displays an additional user interface on the display, where the additional user interface allows selection to be made among the different payment accounts represented by the first visual indicator. Either of these methods (via payment and non-payment modes) allows the user to bring up an account selection interface to select among multiple payment accounts on the payment card.

[0342] As shown in FIG. 14C, according to some embodiments, the second user interface includes a payment account selection affordance 1412. The electronic device detects a second contact at a location on the touch-sensitive surface corresponding to the payment account selection affordance 1412. As shown in FIG. 14D, in response to detecting the second contact, the electronic device displays a third user interface 1418 on the display, where 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 location associated with an account affordance 1424 of the one or more account affordances (e.g., 1420, 1422, 1424), where the account affordance 1424 corresponds to a second payment account (e.g., a credit account) of the multiple payment accounts, the second payment account being different from the first payment account. In some implementations, when the electronic device detects activation of the cancel affordance 1426, the electronic device displays the user interface of FIG. 14C.

[0343] As shown in FIG. 14E, in response to detecting the third contact, the electronic device displays a fourth user interface (e.g., the user interface of FIG. 14E) on the display, where the fourth user interface includes a first visual indicator 1402 identifying a payment card associated with the multiple payment accounts (e.g., the payment card is unchanged) and a third visual indicator 1430 identifying a second payment account (e.g., a credit account different from the checking account) of the multiple payment accounts of the payment card. For example, the third visual indicator 1430 reads "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 make a payment transaction using the second payment account via one or more wireless communication elements (and disables the electronic device from making a payment transaction using the first payment account). For example, a user can place the electronic device within a field of a contactless payment terminal to make an NFC payment using the first payment account. For example, ready indication 14032 is a visual indication that the device is ready to participate in a payment transaction using a second payment account.

[0344] According to some embodiments, following a determination that the characteristic intensity of the first contact is below an intensity threshold (e.g., a light pressure), the electronic device maintains the display of the first visual indicator 1402 (and, optionally, the second visual indicator 1406) and does not display the second user interface on the display.

[0345] According to some embodiments, one or more of the account affordances 1420, 1422, 1424 include multiple account affordances.

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

[0347] According to some embodiments, detecting the second contact includes determining that a characteristic intensity of the second contact does not exceed an intensity threshold (eg, it is not a hard press).

[0348] According to some embodiments, the second user interface includes a delete payment account affordance 1410. The electronic device detects activation of the delete payment account affordance 1410. In response to detecting activation of the delete payment account affordance 1410, the electronic device removes the multiple payment accounts of the payment card from the device's electronic wallet (e.g., unlinks them from the electronic device).

[0349] According to some embodiments, the delete payment account affordance 1410 includes one or more visual characteristics that distinguish it from the select payment account affordance 1412. For example, these affordances have different shapes, different fill colors, or different text to help a user avoid confusing one affordance for the other.

[0350] According to some embodiments, while displaying a fourth user interface 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 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 that identifies a second payment card that is different from the previously presented payment card. In this manner, the user may change payment cards by swiping.

[0351] 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, the single electronic wallet application including multiple payment accounts associated with a user of the electronic device.

[0352] According to some embodiments, the electronic device receives a request for account information from the contactless payment terminal. In response to receiving the request for account information, the electronic device transmits, via one or more wireless communication elements, account information regarding the second payment account to the contactless payment terminal, where the account information enables the contactless payment terminal to conduct the payment transaction. In some embodiments, conducting the payment transaction includes forwarding information to one or more financial institutions to verify payment credentials and / or to receive authorization to complete the transaction. For example, the payment account information is transmitted to the contactless payment terminal using NFC.

[0353] 15 is a flow diagram illustrating a method for receiving a selection of an account from among multiple accounts in an electronic wallet, according to some embodiments. Method 1500 is performed on a device (e.g., 100, 300, 500) with a display and one or more wireless communication elements including a touch-sensitive surface configured to detect an intensity of contact and one or more wireless communication elements. Some operations of method 1500 may be combined, some operations may be reordered, and some operations may be omitted.

[0354] As described below, the method 1500 provides an intuitive way to receive an account selection from among multiple accounts in an electronic wallet. This method reduces the cognitive burden on the user of selecting an account, thereby creating a more efficient human-machine interface. In the case of battery-operated computing devices, allowing the user to select an account faster and more efficiently conserves power and increases the time between battery charges.

[0355] In block 1502, the electronic device receives a first input (e.g., a user input on a hardware button), e.g., a user double-clicks a mechanical or capacitive button on the device.

[0356] At block 1504, in response to receiving a first input, the technique proceeds to 1506. At block 1506, the electronic device displays on the display a first user interface (e.g., the user interface of FIG. 15A ), where the first user interface includes a first visual indicator (e.g., 1402) that identifies a payment card associated with a plurality of payment accounts and a second visual indicator (e.g., 1406) that identifies a first payment account of the plurality of payment accounts of the payment card.

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

[0358] In block 1510, the electronic device determines whether the characteristic intensity of the first contact exceeds an intensity threshold.

[0359] In block 1512, pursuant to a determination that the characteristic intensity of the first contact exceeds the intensity threshold (e.g., a hard press), the electronic device displays a second user interface on the display (e.g., 1418 of FIG. 14D, or the user interface of FIG. 14C), where the second user interface enables a selection to be made between the different payment accounts represented by the first visual indicator.

[0360] According to some embodiments, the second user interface includes a payment account selection affordance (e.g., 1412). The electronic device detects a second contact at a location on the touch-sensitive surface corresponding to the payment account selection affordance (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 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 location associated with an account affordance (e.g., 1424) of the one or more account affordances (e.g., 1420, 1422, 1424), where the account affordance (e.g., 1424) corresponds to a second payment account of the multiple payment accounts, the second payment account being different from the first payment account.

[0361] In response to detecting the third contact, the electronic device displays on the display a fourth user interface (e.g., the user interface of FIG. 14E), where the fourth user interface includes a first visual indicator (e.g., 1402) that identifies a payment card associated with the multiple payment accounts and a third visual indicator (e.g., 1430) that identifies a second payment account of the multiple payment accounts of the payment card. In response to detecting the third contact, the electronic device enables the electronic device to conduct payment transactions using the second payment account (and disables the electronic device from conducting payment transactions using the first payment account) via the one or more wireless communication elements.

[0362] According to some embodiments, following a determination that the characteristic intensity of the first contact is below an intensity threshold (e.g., a light pressure), the electronic device maintains the display of the first visual indicator (e.g., 1402) (and, optionally, the second visual indicator 1406) and does not display the second user interface on the display.

[0363] According to some embodiments, one or more of the account affordances (eg, 1420, 1422, 1424) include multiple account affordances.

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

[0365] According to some embodiments, detecting the second contact includes determining that a characteristic intensity of the second contact does not exceed an intensity threshold (eg, it is not a hard press).

[0366] According to some embodiments, the second user interface includes a delete payment account affordance (e.g., 1410). The electronic device detects activation of the delete payment account affordance (e.g., 1410). In response to detecting activation of the delete payment account affordance (e.g., 1410), the electronic device removes the multiple payment accounts of the payment card from the device's electronic wallet (e.g., unlinks them from the electronic device).

[0367] According to some embodiments, the delete payment account affordance (eg, 1410) includes one or more visual characteristics that distinguish it from the select payment account affordance (eg, 1412).

[0368] According to some embodiments, while displaying a fourth user interface 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 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 that identifies a second payment card that is different from the previously presented payment card.

[0369] 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, the single electronic wallet application including multiple payment accounts associated with a user of the electronic device.

[0370] According to some embodiments, the electronic device receives a request for account information from the contactless payment terminal. In response to receiving the request for account information, the electronic device transmits, via one or more wireless communication elements, account information regarding the second payment account to the contactless payment terminal, where the account information enables the contactless payment terminal to conduct the payment transaction. In some embodiments, conducting the payment transaction includes forwarding information to one or more financial institutions to verify payment credentials and / or to receive authorization to complete the transaction. For example, the payment account information is transmitted to the contactless payment terminal using NFC.

[0371] It should be noted that the details of the process (e.g., FIG. 15) described above with respect to method 1500 are also applicable in an analogous manner to the methods described above and below. For example, methods 700, 900, 1100, 1300, 1700 and 1900 may include one or more of the characteristics of the various methods described above with reference to method 1500. For example, the electronic wallets, payment accounts, loyalty accounts, affordances and inputs of methods 700, 900, 1100, 1300, 1700 and 1900 optionally have one or more of the characteristics of the electronic device, payment accounts, loyalty accounts, affordances and inputs of the electronic device described in method 1500. For the sake of brevity, these details will not be repeated below.

[0372] 16A-16G illustrate example techniques and example user interfaces for linking a payment account to one or more electronic devices, according to some embodiments. The techniques are performed on a first electronic device that includes a display and one or more wireless communication elements (e.g., one or more wireless antennas, such as an NFC antenna, a WiFi antenna, etc.). The user interfaces in these figures are used to illustrate the processes described below, including the process of FIG. 17.

[0373] A user may wish 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 description describes techniques for linking a payment account to a user's first device (e.g., a phone) and a user's second device (e.g., a smartwatch) in a convenient and efficient manner.

[0374] 16A, the first electronic device displays a user interface that includes three affordances for linking a payment account to the first electronic device. For example, affordance 1606 may be activated to allow payment account details to be imported from a remote server, affordance 1608 may be activated to allow payment account details to be entered manually (e.g., using a displayed keypad), and affordance 1610 may be activated to allow payment account details to be captured using a camera sensor of the first electronic device.

[0375] 16B, the first electronic device may display a user interface including a payment account display 1612 representing a payment account. The device may prompt the user to enter a security code for the payment account (e.g., a numeric card security code such as a CVD, CVV, CVC, etc.). For example, the device may receive input using a keypad 1616 to enter the security code into field 1614. Thus, the first electronic device receives a first request (e.g., user input) to link a payment account associated with a payment card (e.g., a credit card) to the first electronic device.

[0376] In response to receiving the first request, the first electronic device initiates a process to link the payment account to the first electronic device. As shown in FIG. 16B, in some implementations, during the process to link the payment account to the first electronic device, the first electronic device receives input of a payment card security code (e.g., a numeric card security code, such as CVD, CVV, CVC, etc.). For example, a user can enter the security code into field 1614 by using keypad 1616. In some implementations, the first electronic device determines whether further verification is required to link the payment account to the first electronic device. In accordance with a determination that further verification is not required to link the payment account to the first electronic device, the first electronic device links the payment account to the electronic device. As shown in FIG. 16C, following a determination that further verification is required to link the payment account to the first electronic device, the first electronic device provides an indication that further verification is required to link the payment account to the respective device (e.g., displaying on a display of the first electronic device that approval to link the payment account is pending or requesting the user to call a verification phone number). In this example, the user may activate affordance 1618 to receive a phone call to complete the further verification, or the user may activate affordance 1620 to receive an email to complete the further verification. In some embodiments, the indication that further verification is required to link the payment account to the first electronic device includes an alphanumeric visual indicator displayed on a display of the electronic device (e.g., an alphanumeric indicator including “approval pending” indicating that a further verification step is being initiated without additional user input). For example, a financial institution (e.g., a bank) associated with the payment account may need to verify the details of the payment account before the payment account is linked to the respective device. The verification may or may not require additional user interaction with the financial institution.Additional details regarding the determination and processing for further verification are set forth in U.S. Provisional Patent Application No. 62 / 004,886, entitled "USER INTERFACE FOR PAYMENTS," which is incorporated herein by reference in its entirety.

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

[0378] The first electronic device receives activation of the selectable affordance 1640 (e.g., a user activates the selectable affordance 1640 by tapping on it). In response to receiving the activation of the selectable affordance 1640, the first electronic device initiates a process to link the payment account to the second electronic device (e.g., as shown in FIGS. 16E-16F).

[0379] According to some embodiments, the second electronic device is uniquely paired with the first electronic device, e.g., the second electronic device has a special relationship with the first electronic device in that the second electronic device is paired only with the first electronic device and not with any other devices.

[0380] According to some embodiments, the 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.

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

[0382] According to some embodiments, after initiating the linking of the payment account to the second electronic device, the first electronic device receives a confirmation from the second electronic device that the linking of the second electronic device to the payment account was successful. The primary account number (e.g., Digital PAN, DPAN, 16-digit account number, or other account number, which cannot be used to complete a human-conducted transaction, e.g., via a voice call - it can only be used to complete a payment electronically via the device) linked to the second electronic device as a payment account is different from the primary account number (e.g., Digital PAN, DPAN, 16-digit account number, or other account number) linked to the first electronic device as a payment account. As shown in FIG. 16G, in some implementations, the first electronic device displays a confirmation 1636 that the payment account has been linked to the second electronic device.

[0383] According to some embodiments, the first request (e.g., user input) to link a payment account (to a first electronic device) includes a payment card account number (e.g., provided manually by a user, imported from a server, or entered by a user via a camera sensor on the electronic device), in which case initiating the process to link the payment account to the second electronic device occurs without requiring additional input (e.g., user input) of the payment card account number.

[0384] 16F, according to some embodiments, the second request (e.g., to link a payment account to a second electronic device, thereby initiating a process to link the payment account to the second electronic device) includes a payment card security code (e.g., entered by a user) (e.g., a numeric card security code such as CVD, CVV, CVC, etc.). For example, the user can use keypad 1628 to enter the security code into field 1634.

[0385] According to some embodiments, the first electronic device initiates a process to link a payment account to the second electronic device.

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

[0387] According to some embodiments, initiating a process for l...

Claims

1. 1. A method performed by an electronic device having a display and a position sensor, comprising: detecting a current location using the location sensor while the electronic device is associated with a plurality of accounts, including a default payment account and a plurality of other accounts, where the plurality of other accounts include a loyalty account and a first private label payment account; determining whether the current location is associated with the loyalty account of the plurality of other accounts; displaying, on the display, a visual representation of the default payment account without displaying any visual representation of the plurality of other accounts in accordance with determining that the current location is not associated with an account of the plurality of other accounts associated with the electronic device; and concurrently displaying on the display the visual representation of the default payment account and the visual representation of the loyalty account of the plurality of other accounts in response to a determination that the current location is associated with the loyalty account of the plurality of other accounts; wherein the default payment account and the loyalty account are linked to the electronic device, the default payment account and the loyalty account are different; determining whether the current location is associated with the first private label payment account of the plurality of other accounts; concurrently displaying on the display the visual representation of the default payment account and the visual representation of the first private label payment account of the plurality of other accounts in accordance with a determination that the current location is associated with the first private label payment account of the plurality of other accounts; wherein the first private label payment account is linked to the electronic device, and the default payment account and the first private label payment account are different; receiving a first request associated with a payment transaction from a contactless payment terminal; transmitting, using one or more wireless communication elements, payment account information of the first private label payment account to the contactless payment terminal in response to a determination that the current location is associated with the first private label payment account of the plurality of other accounts and in response to a determination that the first request includes a first request for payment information corresponding to the first private label payment account, wherein the payment account information of the first private label payment account enables the contactless payment terminal to conduct the payment transaction; A method comprising:

2. receiving a second request associated with the payment transaction from the contactless payment terminal; determining that the second request includes a second request for payment account information using the first private label payment account; transmitting, using one or more wireless communication elements, payment account information of the default payment account to the contactless payment terminal in accordance with determining that the current location is not associated with an account of the plurality of other accounts associated with the electronic device, wherein the payment account information of the default payment account enables the contactless payment terminal to perform the payment transaction; The method of claim 1 further comprising:

3. 3. The method of claim 1 or 2, wherein the visual representation of the loyalty account among the plurality of other accounts is displayed above the visual representation of the default payment account, and the visual representation of the loyalty account among the plurality of other accounts indicates that the loyalty account is selectable by the electronic device for use in a payment transaction without requiring additional user input.

4. receiving an input requesting that the electronic device be enabled for a payment transaction prior to detecting the current location using the location sensor; The method of claim 1 , further comprising:

5. The method of claim 4 , wherein detecting the current location using the location sensor occurs in response to receiving the input requesting to enable the electronic device for a payment transaction.

6. 6. The method of claim 1, wherein determining whether the current location is associated with the loyalty account of the plurality of other accounts is performed in response to receiving an input requesting that the electronic device be enabled for a payment transaction.

7. 7. The method of claim 1, wherein the failure to determine that the current location is associated with an account of the plurality of other accounts associated with the electronic device occurs when the electronic device fails to determine that the current location is associated with the loyalty account of the plurality of other accounts before the electronic device is enabled to participate in a transaction using the default payment account via one or more wireless communication elements.

8. receiving a request for loyalty account information from a contactless payment terminal; in response to receiving the request for loyalty account information, in accordance with determining that the current location is not associated with an account of the plurality of other accounts associated with the electronic device, and in accordance with a subsequent determination that the current location is associated with the loyalty account of the plurality of other accounts; transmitting, via one or more wireless communication elements, account information relating to the loyalty account to the contactless payment terminal; and transmitting payment account information of the default payment account to the contactless payment terminal via the one or more wireless communication elements; The method of claim 1 , further comprising:

9. receiving a third request associated with the payment transaction from the contactless payment terminal; determining that the third request includes a third request for payment account information using the first private label payment account; in response to receiving the third request for account information, in accordance with determining that the current location is not associated with an account of the plurality of other accounts associated with the electronic device, and in accordance with a subsequent determination that the current location is associated with the first private label payment account of the plurality of other accounts. discontinuing transmitting account information regarding the first private label payment account to the contactless payment terminal via one or more wireless communication elements; and transmitting payment account information of the default payment account to the contactless payment terminal via the one or more wireless communication elements; The method of claim 1 , further comprising:

10. receiving a fourth request associated with the payment transaction from the contactless payment terminal; prior to receiving the fourth request associated with the payment transaction from the contactless payment terminal, the visual representation of the default payment account and the visual representation of the first private label payment account are simultaneously displayed on the display; the fourth request includes a fourth request for payment account information using the first private label payment account; in response to receiving the fourth request for account information, in accordance with determining that the current location is not associated with an account of the plurality of other accounts associated with the electronic device, and in accordance with a subsequent determination that the current location is associated with the first private label payment account of the plurality of other accounts. discontinuing transmitting account information regarding the default payment account to the contactless payment terminal via one or more wireless communication elements; and transmitting payment account information of the first private label payment account to the contactless payment terminal via the one or more wireless communication elements; The method of claim 1 , further comprising:

11. In response to the determination that the current location is associated with the first private label payment account of the plurality of other accounts, receiving a failure communication from the contactless payment terminal via the one or more wireless communication elements; In response to receiving said failure notification, transmitting, via one or more wireless communication elements, account information regarding the default payment account to the contactless payment terminal; The method of claim 1 , further comprising:

12. The method of any one of claims 1 to 11, wherein simultaneously displaying on the display the visual representation of the default payment account and the visual representation of the loyalty account among the plurality of other accounts includes simultaneously displaying on the display the visual representation of the default payment account overlaid on the visual representation of the loyalty account among the plurality of other accounts.

13. The method of claim 1 , wherein the current location is a current physical location.

14. 14. The method of claim 1, wherein the determination that the current location is associated with the first private label payment account of the plurality of other accounts is a determination that a merchant present at the current location is associated with the first private label payment account of the plurality of other accounts.

15. 15. The method of claim 1, wherein the determining that the current location is associated with an account of the plurality of other accounts associated with the electronic device includes displaying the visual representation of the default payment account without displaying any visual representation of the plurality of other accounts, including the loyalty account and the first private label payment account.

16. 16. The method of claim 1, wherein the default payment account is the same as the account that is displayed when the current location is not determined to be associated with an account among the plurality of other accounts associated with the electronic device, and that is displayed when the current location is associated with the first private label payment account among the plurality of other accounts.

17. A computer program causing a computer to carry out the method according to any one of claims 1 to 16.

18. A memory for storing the computer program of claim 17; and one or more processors capable of executing the computer programs stored in the memory.

19. 17. An electronic device having means for carrying out the method according to any one of claims 1 to 16.

Images