User interface for trading

Abstract

The present disclosure generally relates to user interfaces for transactions. In some embodiments, a user is notified if transaction parameters are incorrect, and the device determines if there are potentially compatible transaction parameters on an electronic device. In some embodiments, a user is notified if transaction parameters are incorrect, and the user is prompted to enter new transaction information using another device.

Description

[0001] This application is a divisional application of Chinese patent application 201780033899.9, whose application date is May 4, 2017 and whose invention name is “User Interface for Transactions”.

[0002] CROSS-REFERENCE TO RELATED APPLICATIONS

[0003] This patent application claims priority to U.S. Provisional Patent Application No. 62 / 349,010, filed on June 12, 2016, entitled “USER INTERFACES FORTRANSACTIONS,” the contents of which are incorporated herein by reference in their entirety. This patent application claims priority to Danish Patent Application No. PA 2016 70622, filed on August 16, 2016, entitled “USER INTERFACES FORTRANSACTIONS,” the contents of which are incorporated herein by reference in their entirety. This patent application claims priority to U.S. Non-Provisional Patent Application No. 15 / 433,320, filed on February 15, 2017, entitled “USER INTERFACES FORTRANSACTIONS,” the contents of which are incorporated herein by reference in their entirety. Technical Field

[0004] The present disclosure relates generally to computer user interfaces and, more particularly, to techniques for managing transactions. Background Art

[0005] In recent years, the use of electronic devices to participate in transactions has increased significantly. Exemplary techniques for participating in transactions include making online purchases of goods or services on websites. Participating in transactions using such traditional techniques often requires users to manually enter information, such as account information and personal information, using unsafe and slow methods. Summary of the invention

[0006] However, some techniques for managing transactions using electronic devices are often cumbersome and inefficient. For example, some prior art techniques use complex and time-consuming user interfaces, which may include multiple keystrokes or keystrokes, even on reduced-size electronic devices (such as smart watches). Prior art techniques require more time than necessary, which results in wasted user time and device energy. This latter consideration is particularly important in battery-powered devices. For another example, some prior art techniques require users to manually input extended information to be used for transactions on devices (such as smart watches). This may be inefficient when other devices (such as smart phones or laptops) with enhanced input mechanisms are available.

[0007] Thus, the present technology provides a faster, more efficient and more secure method and interface for electronic devices to manage transactions. Such methods and interfaces optionally supplement or replace other methods for managing transactions. Such methods and interfaces reduce the cognitive burden imposed on users and produce a more efficient human-computer interface. For battery-powered computing devices, such methods and interfaces save power and increase the time interval between battery charges. In addition, such methods and interfaces reduce the amount of input required at electronic devices (such as smart watches).

[0008] According to some embodiments, a method performed at an electronic device having a display, one or more input devices, and a hardware button is described. The method includes: displaying an application user interface for a corresponding application on the display, wherein the application user interface includes a transaction enablement representation for requesting payment for an activity associated with the corresponding application; while displaying the application user interface, detecting a selection of the transaction enablement representation via one or more input devices; and in response to detecting the selection of the transaction enablement representation, displaying a transaction user interface, the transaction user interface including simultaneously displaying: transaction details for the activity associated with the corresponding application; and instructions for activating the hardware button of the device to authorize payment for the activity associated with the corresponding application.

[0009] According to some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device having a display, one or more input devices, and a hardware button. The one or more programs include instructions for performing the following operations: displaying an application user interface for a corresponding application on a display, wherein the application user interface includes a transaction enable representation for requesting payment for an activity associated with the corresponding application; when displaying the application user interface, detecting the selection of the transaction enable representation via one or more input devices; and in response to detecting the selection of the transaction enable representation, displaying a transaction user interface, the transaction user interface includes simultaneously displaying: transaction details for an activity associated with the corresponding application; and instructions for activating a hardware button of the device to authorize payment for an activity associated with the corresponding application.

[0010] According to some embodiments, a transient computer-readable storage medium is described. The transient computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device having a display, one or more input devices, and a hardware button. The one or more programs include instructions for performing the following operations: displaying an application user interface for a corresponding application on a display, wherein the application user interface includes a transaction enable representation for requesting payment for an activity associated with the corresponding application; when displaying the application user interface, detecting the selection of the transaction enable representation via one or more input devices; and in response to detecting the selection of the transaction enable representation, displaying a transaction user interface, the transaction user interface includes simultaneously displaying: transaction details for an activity associated with the corresponding application; and instructions for activating a hardware button of the device to authorize payment for an activity associated with the corresponding application.

[0011] According to some embodiments, an electronic device is described. The electronic device includes: a display; one or more input devices; hardware buttons; one or more processors; and storage configured to be executed by one or more processors One or more programs, the one or more programs including instructions for performing the following operations: displaying an application user interface for a corresponding application on the display, wherein the application user interface includes a transaction enablement representation for requesting payment for an activity associated with the corresponding application; while displaying the application user interface, detecting a selection of the transaction enablement representation via one or more input devices; and in response to detecting the selection of the transaction enablement representation, displaying a transaction user interface, the transaction user interface including simultaneously displaying: transaction details for an activity associated with the corresponding application; and instructions for activating the device's hardware button to authorize payment for the activity associated with the corresponding application.

[0012] According to some embodiments, an electronic device is described. The electronic device includes: a display; one or more input devices; a hardware button; a device for displaying an application user interface for a corresponding application on the display, wherein the application user interface includes a transaction enablement representation for requesting payment for an activity associated with the corresponding application; a device for detecting selection of the transaction enablement representation via the one or more input devices while displaying the application user interface; and in response to detecting selection of the transaction enablement representation, a device for displaying a transaction user interface, the transaction user interface including simultaneously displaying: transaction details for the activity associated with the corresponding application; and instructions for activating the hardware button of the device to authorize payment for the activity associated with the corresponding application.

[0013] According to some embodiments, a method performed at an electronic device having a display and one or more input devices is described. The method includes: receiving a request to conduct a transaction using transaction parameters; in response to the request to conduct the transaction, displaying an error notification indicating that an error has been detected based on determining that the transaction parameters are incorrect; receiving a request to correct the error via one or more input devices; and in response to receiving the request to correct the error: based on determining that there are potentially compatible transaction parameters on the electronic device, displaying one or more parameters of the potentially compatible transaction parameters on the display; and based on determining that there are no potentially compatible transaction parameters on the device, displaying on the display instructions for entering additional transaction parameters on a companion device different from the electronic device.

[0014] According to some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device having a display and one or more input devices, the one or more programs including instructions for performing the following operations: receiving a request to conduct a transaction using transaction parameters; in response to the request to conduct the transaction, displaying an error notification indicating that an error has been detected based on determining that the transaction parameters are incorrect; receiving a request to correct the error via one or more input devices; and in response to receiving the request to correct the error: displaying one or more parameters of the potentially compatible transaction parameters on the display based on determining that there are potentially compatible transaction parameters on the electronic device; and displaying on the display instructions for entering additional transaction parameters on a companion device different from the electronic device based on determining that there are no potentially compatible transaction parameters on the device.

[0015] According to some embodiments, a transient computer-readable storage medium is described. The transient computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device having a display and one or more input devices, the one or more programs including instructions for performing the following operations: receiving a request to conduct a transaction using transaction parameters; in response to the request to conduct the transaction, displaying an error notification indicating that an error has been detected based on determining that the transaction parameters are incorrect; receiving a request to correct the error via one or more input devices; and in response to receiving the request to correct the error: displaying one or more parameters of the potentially compatible transaction parameters on the display based on determining that there are potentially compatible transaction parameters on the electronic device; and displaying on the display instructions for entering additional transaction parameters on a companion device different from the electronic device based on determining that there are no potentially compatible transaction parameters on the device.

[0016] According to some embodiments, an electronic device is described. The electronic device includes: a display; one or more input devices; one or more processors; and a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for performing the following operations: receiving a request to conduct a transaction using transaction parameters; in response to the request to conduct the transaction, displaying an error notification indicating that an error has been detected based on determining that the transaction parameters are incorrect; receiving a request to correct the error via one or more input devices; and in response to receiving the request to correct the error: displaying one or more parameters of the potentially compatible transaction parameters on the display based on determining that there are potentially compatible transaction parameters on the electronic device; and displaying on the display instructions for entering additional transaction parameters on a companion device different from the electronic device based on determining that there are no potentially compatible transaction parameters on the device.

[0017] According to some embodiments, an electronic device is described. The electronic device includes: a display; one or more input devices; a device for receiving a request to conduct a transaction using transaction parameters; in response to the request to conduct the transaction, based on determining that the transaction parameters are incorrect, a device for displaying an error notification indicating that an error has been detected; a device for receiving a request to correct the error via one or more input devices; and in response to receiving the request to correct the error, a device for performing the following operations: based on determining that there are potentially compatible transaction parameters on the electronic device, displaying one or more parameters of the potentially compatible transaction parameters on the display; and based on determining that there are no potentially compatible transaction parameters on the device, displaying on the display instructions for entering additional transaction parameters on a companion device different from the electronic device.

[0018] According to some embodiments, an electronic device is described. The electronic device includes: a display unit; one or more input device units; a hardware button unit; and a processing unit, the processing unit coupled to the display unit, the one or more input device units and the hardware button unit, the processing unit being configured to: enable an application user interface for a corresponding application to be displayed on the display unit, wherein the application user interface includes a transaction enablement representation for requesting payment for an activity associated with the corresponding application; when enabling the display of the application user interface, detecting the selection of the transaction enablement representation via the one or more input device units; and in response to detecting the selection of the transaction enablement representation, enable the display of the transaction user interface on the display unit, the transaction user interface including simultaneously displaying: transaction details for an activity associated with the corresponding application; and an instruction to activate the hardware button unit of the electronic device to authorize payment for the activity associated with the corresponding application.

[0019] According to some embodiments, an electronic device is described. The electronic device includes: a display unit; one or more input device units; and a processing unit, the processing unit being coupled to the display unit and the one or more input device units, the processing unit being configured to: receive a request to conduct a transaction using transaction parameters; in response to the request to conduct the transaction, based on determining that the transaction parameters are incorrect, enable an error notification indicating that an error has been detected to be displayed on the display unit; receive a request to correct the error via the one or more input device units; and in response to receiving the request to correct the error: based on determining that there are potentially compatible transaction parameters on the electronic device, enable one or more parameters of the potentially compatible transaction parameters to be displayed on the display unit; and based on determining that there are no potentially compatible transaction parameters on the electronic device, enable an instruction to enter additional transaction parameters on a companion device different from the electronic device to be displayed on the display unit.

[0020] Executable instructions for performing these functions are optionally included in a non-transitory computer-readable storage medium or other computer program product configured for execution by one or more processors. Executable instructions for performing these functions are optionally included in a transient computer-readable storage medium or other computer program product configured for execution by one or more processors.

[0021] Thus, a faster, more efficient method and interface is provided for devices for managing transactions, thereby increasing the effectiveness, efficiency, and user satisfaction of such devices. Such methods and interfaces may supplement or replace other methods for managing transactions. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] For a better understanding of the various described embodiments, reference should be made to the following detailed description taken in conjunction with the following drawings, wherein like reference numerals designate corresponding parts throughout the several views.

[0023] Figure 1A is a block diagram showing a portable multifunction device with a touch-sensitive display according to some embodiments.

[0024] Figure 1B is a block diagram illustrating example components for event processing according to some embodiments.

[0025] Figure 2 A portable multifunction device with a touch screen according to some embodiments is shown.

[0026] Figure 3 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface according to some embodiments.

[0027] Figure 4AAn exemplary user interface for a menu of applications on a portable multifunction device is shown according to some embodiments.

[0028] Figure 4B An exemplary user interface is shown for a multifunction device having a touch-sensitive surface that is separate from the display according to some embodiments.

[0029] Figure 5A A personal electronic device according to some embodiments is shown.

[0030] Figure 5B is a block diagram illustrating a personal electronic device according to some embodiments.

[0031] Figure 5C-5D Example components of a personal electronic device with a touch-sensitive display and an intensity sensor are shown according to some embodiments.

[0032] Figure 5E-Figure 5H Exemplary components and user interfaces of a personal electronic device according to some embodiments are shown.

[0033] Figure 6 Illustrated are example devices connected via one or more communication channels to fully participate in a transaction in accordance with some embodiments.

[0034] Figure 7A-Figure 7O An exemplary user interface for managing transactions is shown according to some embodiments.

[0035] Figure 8 is a flow chart illustrating a method for managing transactions according to some embodiments.

[0036] Figure 9A-9N An exemplary user interface for managing transactions is shown according to some embodiments.

[0037] Fig.10 is a flow chart illustrating a method for managing transactions according to some embodiments.

[0038] Figure 11-Figure 12 is a functional block diagram according to some embodiments. DETAILED DESCRIPTION

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

[0040] Electronic devices need to provide more efficient methods and interfaces for managing transactions. According to some embodiments, the user is notified if the transaction parameters are incorrect, and the device determines if there are potentially compatible transaction parameters on the electronic device. According to some embodiments, the user is notified if the transaction parameters are incorrect, and the user is prompted to enter new transaction information using another device. Such techniques can reduce the cognitive burden of users participating in the transaction, thereby improving productivity. In addition, such techniques can reduce processor power and battery power that would otherwise be wasted on redundant user input.

[0041] under Figure 1A-1B , Figure 2 , Figure 3 , Figure 4A-4B and Figure 5A-5H A description of an exemplary device for performing techniques for management event notifications is provided. Figure 6 Illustrated are example devices connected via one or more communication channels to fully participate in a transaction in accordance with some embodiments. Figure 7A-Figure 7O An exemplary user interface for managing transactions is shown. Figure 8 is a flow chart illustrating a method for managing transactions according to some embodiments. Figure 7A-Figure 7O The user interface is used to show the Figure 8 The process is described below in the process. Figure 9A-9N An exemplary user interface for managing transactions is shown. Fig.10 is a flow chart illustrating a method for managing transactions according to some embodiments. Figure 9A-9N The user interface is used to show the Fig.10 The process is described below in the process.

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

[0043] The terms used in the description of various described embodiments in this article are only for the purpose of describing specific embodiments, and are not intended to be limited. As used in the description of various described embodiments and in the appended claims, the singular forms "one" and "the" are intended to also include plural forms, unless the context clearly indicates otherwise. It will also be understood that the term "and / or" used herein refers to and encompasses any and all possible combinations of one or more items in the associated listed items. It will also be understood that the term "including" when used in this specification specifies the presence of stated features, integers, steps, operations, elements and / or parts, but does not exclude the presence or addition of one or more other features, integers, steps, operations, elements, parts and / or their grouping.

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

[0045] Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described herein. In some embodiments, the device is a portable communication device, such as a mobile phone, that also includes other functions, such as a PDA and / or a music player function. Exemplary embodiments of portable multifunction devices include, but are not limited to, the Apple iPod from Apple Inc. (Cupertino, California). Devices, iPod Equipment and Device. Other portable electronic devices, such as laptops or tablets with touch-sensitive surfaces (e.g., touch screen displays and / or trackpads) are optionally used. It should also be understood that in some embodiments, the device is not a portable communication device, but a desktop computer with a touch-sensitive surface (e.g., touch screen displays and / or trackpads).

[0046] In the following discussion, an electronic device including a display and a touch-sensitive surface is described. However, it should be understood that the electronic device optionally includes one or more other physical user interface devices, such as a physical keyboard, mouse, and / or joystick.

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

[0048] Various applications executed on the device optionally use at least one common physical user interface device, such as a touch-sensitive surface. One or more functions of the touch-sensitive surface and corresponding information displayed on the device are optionally adjusted and / or varied for different application programs and / or adjusted and / or varied within the corresponding application. In this way, the common physical architecture of the device (such as a touch-sensitive surface) optionally supports various applications with a user interface that is intuitive and clear to the user.

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

[0050] As used in this specification and 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 to a surrogate (surrogate) of the force or pressure of a contact on the touch-sensitive surface. The intensity of a contact has a range of values ​​that includes at least four different values ​​and more typically includes hundreds of different values ​​(e.g., at least 256). The intensity of a contact is optionally determined (or measured) using various methods and various sensors or combinations of sensors. For example, one or more force sensors below or adjacent to the touch-sensitive surface are optionally used to measure the force at different points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (e.g., weighted averaged) to determine an estimated contact force. Similarly, the pressure-sensitive tip of a stylus is optionally used to determine the pressure of the stylus on the touch-sensitive surface. Alternatively, the size of the contact area detected on the touch-sensitive surface and / or its change, the capacitance of the touch-sensitive surface near the contact and / or its change, and / or the resistance of the touch-sensitive surface near the contact and / or its change are optionally used as a substitute for the force or pressure of the contact on the touch-sensitive surface. In some embodiments, the substitute measurement of the contact force or pressure is used directly to determine whether the intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the substitute measurement). In some embodiments, the substitute measurement of the contact force or pressure is converted into an estimated force or pressure, and the estimated force or pressure is used to determine whether the intensity threshold has been exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure). Using the intensity of the contact as an attribute of the user input allows the user to access additional device functions that would otherwise be inaccessible to the user on a smaller device with limited real estate, which is used to display an enable indication (e.g., on a touch-sensitive display) and / or receive user input (e.g., via a touch-sensitive display, a touch-sensitive surface, or a physical control / mechanical control, such as a knob or button).

[0051] As used in this specification and 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, which will be detected by a user using the user's sense of touch. For example, in the case where a device or a component of the device is in contact with a user's touch-sensitive surface (e.g., a finger, palm, or other part of the user's hand), the tactile output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in a physical characteristic of the device or 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 "press click" or "release click" to a physical actuation button. In some cases, the user will feel a tactile sensation, such as a "press click" or "release click", even when the physical actuation button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user's movement does not move. As another example, even when there is no change in the smoothness of the touch-sensitive surface, movement of the touch-sensitive surface may optionally be interpreted or sensed by the user as "roughness" of the touch-sensitive surface. Although such a user's interpretation of touch will be limited by the user's individualized sensory perceptions, many sensory perceptions of touch are common to most users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., "press click," "release click," "roughness"), unless otherwise stated, the generated tactile output corresponds to a physical displacement of the device or a component thereof that would generate that sensory perception for a typical (or average) user.

[0052] It should be understood that device 100 is merely one example of a portable multifunction device, and that device 100 optionally has more or fewer components than shown, optionally combines two or more components, or optionally has a different configuration or arrangement of the components. Figure 1A The various components shown in the EMBODIMENTS 2000 are implemented in hardware, software, or a combination of hardware and software, including one or more signal processing and / or application specific integrated circuits.

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

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

[0055] RF (radio frequency) circuit 108 receives and transmits RF signals, also called electromagnetic signals. RF circuit 108 converts electrical signals into / converts electromagnetic signals into electrical signals, and communicates with communication networks and other communication devices via electromagnetic signals. RF circuit 108 optionally includes well-known circuits for performing these functions, including but not limited to antenna systems, RF transceivers, one or more amplifiers, tuners, one or more oscillators, digital signal processors, codec chipsets, user identity modules (SIM) cards, memory, etc. RF circuit 108 optionally communicates with networks and other devices through wireless communications, such as the Internet (also known as the World Wide Web (WWW)), intranets, and / or wireless networks (such as cellular telephone networks, wireless local area networks (LANs), and / or metropolitan area networks (MANs)). RF circuit 108 optionally includes well-known circuits for detecting near field communication (NFC) fields, such as by detecting through a short-range communication radio component. Wireless communication optionally uses any of a variety of communication standards, protocols and technologies, including, but not limited to, Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), High Speed ​​Downlink Packet Access (HSDPA), High Speed ​​Uplink Packet Access (HSUPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual Cell HSPA (DC-HSPDA), Long Term Evolution (LTE), Near Field Communication (NFC), Wideband Code Division Multiple Access (W-CDMA), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11d), IEEE 802.11e, IEEE 802.11f, IEEE 802.11g, IEEE 802.11g). 802.11n and / or IEEE 802.11ac), Voice over Internet Protocol (VoIP), Wi-MAX, email protocols (e.g., Internet Message Access Protocol (IMAP) and / or Post Office Protocol (POP)), instant messaging (e.g., Extensible Messaging and Presence Protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Utilizing Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), and / or Short Message Service (SMS), or any other suitable communication protocol including communication protocols that have not been developed as of the filing date of this document.

[0056] The audio circuit 110, the speaker 111, and the microphone 113 provide an audio interface between the user and the device 100. The audio circuit 110 receives audio data from the peripheral device interface 118, converts the audio data into electrical signals, and transmits the electrical signals to the speaker 111. The speaker 111 converts the electrical signals into sound waves audible to the human ear. The audio circuit 110 also receives electrical signals converted from sound waves by the microphone 113. The audio circuit 110 converts the electrical signals into audio data and transmits the audio data to the peripheral device interface 118 for processing. The audio data is optionally retrieved from and / or transmitted to the memory 102 and / or the RF circuit 108 by the peripheral device interface 118. In some embodiments, the audio circuit 110 also includes a headphone jack (e.g., Figure 2 The headset jack provides an interface between the audio circuit 110 and a removable audio input / output peripheral device, such as an output-only headset or a headset having both output (e.g., a single or dual-ear headset) and input (e.g., a microphone).

[0057] The I / O subsystem 106 couples input / output peripherals on the device 100, such as a touch screen 112 and other input control devices 116, to a peripheral device interface 118. The I / O subsystem 106 optionally includes a display controller 156, an optical sensor controller 158, an intensity sensor controller 159, a tactile 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 from other input control devices 116. Other input control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slide switches, joysticks, click wheels, etc. In some alternative embodiments, one or more input controllers 160 are optionally coupled to any (or none) of the following: a keyboard, an infrared port, a USB port, and a pointer device such as a mouse. One or more buttons (e.g., Figure 2 208) optionally includes an up / down button for volume control of the speaker 111 and / or the microphone 113. The one or more buttons optionally include a push button (e.g., Figure 2 206).

[0058] A quick press of the push button optionally unlocks the touch screen 112 or optionally begins the process of unlocking the device using gestures on the touch screen, as described in U.S. Patent Application 11 / 322,549, filed on December 23, 2005, entitled "Unlocking a Device by Performing Gestures on an Unlock Image" (i.e., U.S. Patent No. 7,657,849), which is hereby incorporated by reference in its entirety. A long press of the push button (e.g., 206) optionally turns the device 100 on or off. The functions of one or more buttons are optionally user-customizable. The touch screen 112 is used to implement virtual buttons or soft buttons and one or more soft keyboards.

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

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

[0061] The touch screen 112 optionally uses LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, although other display technologies are used in other embodiments. The touch screen 112 and display controller 156 optionally use any of a variety 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 for determining one or more points of contact with the touch screen 112 to detect contact and any movement or interruption thereof. In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as in the Apple 1000 from Apple Inc. (Cupertino, California). and iPod The technology used in

[0062] The touch-sensitive display in some embodiments of the touch screen 112 is optionally similar to the multi-touch-sensitive trackpad 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 et al.), and / or U.S. Patent Publication 2002 / 0015024A1, each of which is hereby incorporated by reference in its entirety. However, the touch screen 112 displays visual output from the device 100, while the touch-sensitive trackpad does not provide visual output.

[0063] In some embodiments, the touch-sensitive display of the touch screen 112 is as described in the following patent applications: (1) U.S. patent application No. 11 / 381,313, entitled “Multipoint Touch Surface Controller,” filed on May 2, 2006; (2) U.S. patent application No. 10 / 840,862, entitled “Multipoint Touchscreen,” filed on May 6, 2004; (3) U.S. patent application No. 10 / 903,964, entitled “Gestures For Touch Sensitive Input Devices,” filed on July 30, 2004; (4) U.S. patent application No. 11 / 048,264, entitled “Gestures For Touch Sensitive Input Devices,” filed on January 31, 2005; (5) U.S. patent application No. 11 / 086,874, entitled “Mode-Based Graphical User Interfaces For Touch Sensitive Input Devices,” filed on January 18, 2005 and (9) U.S. patent application No. 11 / 367,749, filed on March 3, 2006, entitled “Multi-Functional Hand-Held Device.” All of these applications are hereby incorporated by reference in their entirety.

[0064] The touch screen 112 optionally has a video resolution of more than 100 dpi. In some embodiments, the touch screen has a video resolution of about 160 dpi. The user optionally uses any suitable object or attachment such as a stylus, finger, etc. to contact the touch screen 112. In some embodiments, the user interface is designed to work primarily through finger-based contacts and gestures, which may not be as precise as stylus-based input due to the larger contact area of ​​the finger on the touch screen. In some embodiments, the device converts rough finger-based input into precise pointer / cursor positions or commands for performing the actions desired by the user.

[0065] In some embodiments, in addition to the touch screen, the device 100 optionally includes a touchpad (not shown) for activating or deactivating specific functions. In some embodiments, the touchpad is a touch-sensitive area of ​​the device that, unlike the touch screen, does not display visual output. The touchpad is optionally a touch-sensitive surface that is separate from the touch screen 112 or an extension of the touch-sensitive surface formed by the touch screen.

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

[0067] Device 100 optionally also includes one or more optical sensors 164 . Figure 1AAn optical sensor coupled to an optical sensor controller 158 in the I / O subsystem 106 is shown. The optical sensor 164 optionally includes a charge coupled device (CCD) or a complementary metal oxide semiconductor (CMOS) phototransistor. The optical sensor 164 receives light projected through one or more lenses from the environment and converts the light into data representing an image. In conjunction with the imaging module 143 (also called a camera module), the optical sensor 164 optionally captures a static image or video. In some embodiments, the optical sensor is located on the rear of the device 100, opposite to the touch screen display 112 on the front of the device, so that the touch screen display can be used as a viewfinder for static image and / or video image acquisition. In some embodiments, the optical sensor is located on the front of the device so that the image of the user is optionally obtained when the user views other video conference participants on the touch screen display for video conferencing. In some embodiments, the position of the optical sensor 164 can be changed by the user (e.g., by rotating the lens and sensor in the device housing) so that a single optical sensor 164 is used with the touch screen display for both video conferencing and static image and / or video image acquisition.

[0068] Device 100 optionally also includes one or more contact intensity sensors 165 . Figure 1A A contact force sensor is shown coupled to a force sensor controller 159 in the I / O subsystem 106. Contact force 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 force sensors (e.g., sensors for measuring the force (or pressure) of contact on a touch-sensitive surface). Contact force sensor 165 receives contact force information (e.g., pressure information or a surrogate for pressure information) from the environment. In some embodiments, at least one contact force sensor is juxtaposed or adjacent to a touch-sensitive surface (e.g., touch-sensitive display system 112). In some embodiments, at least one contact force sensor is located on the rear of device 100 opposite to touch screen display 112 located on the front of device 100.

[0069] Device 100 optionally also includes one or more proximity sensors 166 . Figure 1AA proximity sensor 166 is shown coupled to the peripherals interface 118. Alternatively, the proximity sensor 166 is optionally coupled to the input controller 160 in the I / O subsystem 106. The proximity sensor 166 is optionally implemented as described in the following U.S. patent applications: No. 11 / 241,839, entitled "Proximity Detector In Handheld Device"; No. 11 / 240,788, entitled "Proximity Detector In Handheld Device"; No. 11 / 620,702, entitled "Using Ambient Light Sensor To Augment Proximity Sensor Output"; No. 11 / 586,862, entitled "Automated Response To And Sensing Of User Activity In Portable Devices"; and No. 11 / 638,251, entitled "Methods And Systems For Automatic Configuration Of Peripherals", which are hereby incorporated by reference in their entirety. In some embodiments, when the multifunction device is placed near the user's ear (e.g., when the user is on a phone call), the proximity sensor turns off and disables the touch screen 112.

[0070] Device 100 optionally also includes one or more tactile output generators 167 . Figure 1AA tactile output generator is shown coupled to a tactile feedback controller 161 in the I / O subsystem 106. The tactile output generator 167 optionally includes one or more electroacoustic devices such as a speaker or other audio component; and / or an electromechanical device for converting energy into linear motion such as a motor, solenoid, electroactive polymer, piezoelectric actuator, electrostatic actuator, or other tactile output generating component (e.g., a component for converting an electrical signal into a tactile output on the device). The contact force sensor 165 receives tactile feedback generation instructions from the tactile feedback module 133 and generates a tactile output on the device 100 that can be felt by a user of the device 100. In some embodiments, at least one tactile output generator is arranged in parallel or adjacent to a touch-sensitive surface (e.g., a touch-sensitive display system 112) and optionally generates a tactile output by moving the touch-sensitive surface vertically (e.g., inward / outward of the surface of the device 100) or laterally (e.g., backward and forward in the same plane as the surface of the device 100). In some embodiments, at least one tactile output generator sensor is located on the back of the device 100, opposite the touch screen display 112 located on the front of the device 100.

[0071] Device 100 optionally also includes one or more accelerometers 168 . Figure 1A An accelerometer 168 is shown coupled to the peripherals interface 118. Alternatively, the accelerometer 168 is optionally coupled to the input controller 160 in the I / O subsystem 106. The accelerometer 168 optionally implements as described in the following U.S. Patent Publication No. 20050190059, entitled "Acceleration-based Theft Detection System for Portable Electronic Devices" and U.S. Patent Publication No. 20060017692, entitled "Methods And Apparatuses For Operating A Portable Device Based On An Accelerometer", both of which are hereby incorporated by reference in their entirety. In some embodiments, information is displayed in a portrait view or a landscape view on the touch screen display based on analysis of data received from one or more accelerometers. Device 100 optionally includes a magnetometer (not shown) and a GPS (or GLONASS or other global navigation system) receiver (not shown) in addition to one or more accelerometers 168 for obtaining information about the position and orientation (e.g., portrait or landscape) of device 100.

[0072] In some embodiments, the software components stored in memory 102 include an operating system 126, a communication module (or instruction set) 128, a contact / 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 an application (or instruction set) 136. In addition, in some embodiments, memory 102 ( Figure 1A ) or 370( Figure 3 ) storage device / global internal state 157, such as Figure 1A and Figure 3 . The device / global internal state 157 includes one or more of the following: an active application state, which indicates which applications (if any) are currently active; a display state, which indicates what applications, views, or other information occupy various areas of the touch screen display 112; a sensor state, including information obtained from the device's various sensors and input control devices 116; and position information about the device's position and / or posture.

[0073] The operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS, WINDOWS, or an embedded operating system such as VxWorks) includes various software components and / or drivers for controlling and managing general system tasks (e.g., memory management, storage device control, power management, etc.), and facilitating communication between various hardware components and software components.

[0074] The communication module 128 facilitates communication with other devices through one or more external ports 124, and also includes various software components for processing data received by the RF circuit 108 and / or the external port 124. The external port 124 (e.g., Universal Serial Bus (USB), FireWire, etc.) is suitable for coupling directly to other devices, or indirectly through a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is connected to (trademark of Apple Inc.) devices.

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

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

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

[0078] The graphics module 132 includes various known software components for presenting and displaying graphics on the touch screen 112 or other display, including components for changing the visual impact (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, etc.

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

[0080] Haptic feedback module 133 includes various software components for generating instructions used by one or more tactile output generators 167 to produce tactile output at one or more locations on device 100 in response to user interaction with device 100 .

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

[0082] The GPS module 135 determines the location of the device and provides this information for use in various applications (e.g., to the phone 138 for location-based dialing; to the camera 143 as picture / video metadata; and to applications that provide location-based services, such as the Weather widget, the Local Pages widget, and the Maps / Navigation widget).

[0083] The application 136 optionally includes the following modules (or instruction sets) or a subset or superset thereof:

[0084] Contacts module 137 (sometimes called address book or contact list);

[0085] Telephone module 138;

[0086] Video conferencing module 139;

[0087] Email client module 140;

[0088] Instant messaging (IM) module 141;

[0089] Fitness support module 142;

[0090] A camera module 143 for still images and / or video images;

[0091] Image management module 144;

[0092] Video player module;

[0093] Music player module;

[0094] Browser module 147;

[0095] Calendar module 148;

[0096] A widget module 149, which optionally includes one or more of the following: a weather widget 149-1, a stock market widget 149-2, a calculator widget 149-3, an alarm clock widget 149-4, a dictionary widget 149-5, and other widgets acquired by the user, and a user-created widget 149-6;

[0097] A widget creator module 150 for forming a user-created widget 149-6;

[0098] Search module 151;

[0099] Video and music player module 152, which merges the video player module and the music player module;

[0100] Notepad module 153;

[0101] Map module 154; and / or

[0102] Online video module 155.

[0103] Examples of other applications 136 that are optionally stored in memory 102 include other word processing applications, other image editing applications, drawing applications, presentation applications, JAVA-enabled applications, encryption, digital rights management, voice recognition, and voice replication.

[0104] In conjunction with the touch screen 112, display controller 156, touch / motion module 130, graphics module 132 and text input module 134, the contact module 137 is optionally used to manage an address book or contact list (for example, stored in the application internal state 192 of the contact module 137 in memory 102 or memory 370), including: adding one or more names to the address book; deleting names from the address book; associating telephone numbers, email addresses, physical addresses or other information with names; associating images with names; categorizing and classifying names; providing telephone numbers or email addresses to initiate and / or facilitate communications via telephone 138, video conferencing module 139, email 140 or instant messaging 141; and the like.

[0105] 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, phone module 138 is optionally used to enter a sequence of characters corresponding to a phone number, access one or more phone numbers in contact module 137, modify an entered phone number, dial a corresponding phone number, conduct a conversation, and disconnect or hang up when the conversation is complete. As described above, wireless communication optionally uses any of a variety of communication standards, protocols, and technologies.

[0106] In combination with RF circuit 108, audio circuit 110, speaker 111, microphone 113, touch screen 112, display controller 156, optical sensor 164, optical sensor controller 158, touch / motion module 130, graphics module 132, text input module 134, contact module 137 and telephone module 138, video conferencing module 139 includes executable instructions for initiating, executing and terminating a video conference between a user and one or more other participants in accordance with user instructions.

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

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

[0109] In combination with the RF circuit 108, the touch screen 112, the display controller 156, the contact / motion module 130, the graphics module 132, the text input module 134, the GPS module 135, the map module 154 and the music player module, the fitness support module 142 includes executable instructions for creating a fitness (e.g., with time, distance and / or calorie burn goals); communicating with fitness sensors (sports equipment); receiving fitness sensor data; calibrating sensors for monitoring fitness; selecting and playing music for fitness; and displaying, storing and transmitting fitness data.

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

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

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

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

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

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

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

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

[0118] In conjunction with the touch screen 112, display controller 156, contact / motion module 130, graphics module 132 and text input module 134, the notepad module 153 includes executable instructions for creating and managing notes, to-do lists, etc. according to user instructions.

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

[0120] In conjunction with touch screen 112, display controller 156, contact / motion module 130, graphics module 132, audio circuit 110, speaker 111, RF circuit 108, text input module 134, email client module 140, and browser module 147, online video module 155 includes instructions for performing the following operations: allowing a user to access, browse, receive (e.g., by streaming and / or downloading), playback (e.g., on the touch screen or on an external display connected via external port 124), send an email with a link to a specific online video, and otherwise manage online videos in one or more file formats such as H.264. In some embodiments, instant messaging module 141 is used instead of email client module 140 to send a link to a specific online video. Additional descriptions of online video applications can be found in U.S. Provisional Patent Application No. 60 / 936,562, filed on June 20, 2007, entitled “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” and U.S. Patent Application No. 11 / 968,067, filed on December 31, 2007, entitled “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” the contents of which are hereby incorporated by reference in their entirety.

[0121] Each of the modules and applications described above corresponds to an executable instruction set for performing one or more of the functions described above and the methods described in this patent application (e.g., the computer-implemented methods and other information processing methods described herein). These modules (e.g., instruction sets) do not have to be implemented as separate software programs, processes, or modules, and thus various subsets of these modules are optionally combined or otherwise rearranged in various embodiments. For example, a video player module is optionally combined with a music player module into a single module (e.g., Figure 1A In some embodiments, the memory 102 optionally stores a subset of the above modules and data structures. In addition, the memory 102 optionally stores additional modules and data structures not described above.

[0122] In some embodiments, the device 100 is a device on which operation of a predefined set of functions is performed exclusively through a touch screen and / or a touch pad. By using a touch screen and / or a touch pad as the primary input control device for operating the device 100, the number of physical input control devices (e.g., push buttons, dials, etc.) on the device 100 is optionally reduced.

[0123] A predefined set of functions that are performed exclusively through a touch screen and / or a trackpad optionally includes navigation between user interfaces. In some embodiments, the trackpad, when touched by a user, navigates the device 100 from any user interface displayed on the device 100 to a main menu, a Home menu, or a root menu. In such embodiments, a trackpad is used to implement a "menu button." In some other embodiments, the menu button is a physical push button or other physical input control device, rather than a trackpad.

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

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

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

[0127] Event monitor 171 receives event information from peripherals interface 118. Event information includes information about sub-events (e.g., user touches 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 168, and / or microphone 113 (through audio circuit 110). The information that peripherals interface 118 receives from I / O subsystem 106 includes information from touch-sensitive display 112 or a touch-sensitive surface.

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

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

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

[0131] Another aspect of the user interface associated with an application is a set of views, sometimes also referred to herein as application views or user interface windows, in which information is displayed and touch-based gestures occur. The application views (of the respective application) in which a touch is detected optionally correspond to a programmatic level within the programmatic or view hierarchy of the application. For example, the lowest level view in which a touch is detected is optionally referred to as a hit view, and the set of events recognized as correct input is optionally determined at least in part based on the hit view of the initial touch that started the touch-based gesture.

[0132] Hit view determination module 172 receives information related to sub-events of touch-based gestures. When an application has multiple views organized in a hierarchy, hit view determination module 172 identifies the hit view as the lowest view in the hierarchy where the sub-events should be processed. In most cases, the hit view is the lowest level view in which the initiating sub-event (e.g., the first sub-event in a sequence of sub-events that form an event or potential event) occurs. Once a hit view is identified by hit view determination module 172, the hit view typically receives all sub-events related to the same touch or input source identified as the hit view.

[0133] Active event recognizer determination module 173 determines which view or views within the view hierarchy should receive a particular sequence of sub-events. In some embodiments, active event recognizer determination module 173 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, active event recognizer determination module 173 determines that all views that include the physical location of the sub-event are actively participating views, and thereby determines that all actively participating views should receive a particular sequence of sub-events. In other embodiments, even if a touch sub-event is completely confined to an area associated with one particular view, higher views in the hierarchy will still remain as actively participating views.

[0134] Event distributor module 174 distributes event information to event recognizers (e.g., event recognizers 180). In embodiments including active event recognizer determination module 173, event distributor module 174 delivers the event information to the event recognizers determined by active event recognizer determination module 173. In some embodiments, event distributor module 174 stores the event information in an event queue, which is retrieved by corresponding event receivers 182.

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

[0136] 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 occurring within a corresponding view of the user interface of the application. Each application view 191 of application 136-1 includes one or more event recognizers 180. Typically, the corresponding application view 191 includes multiple event recognizers 180. In other embodiments, one or more event recognizers in event recognizers 180 are part of an independent module, which is a higher-level object such as a user interface toolkit (not shown) or application 136-1 from which methods and other properties are inherited. In some embodiments, the corresponding event handler 190 includes one or more of the following: data updater 176, object updater 177, GUI updater 178 and / or event data 179 received from event classifier 170. Event handler 190 optionally utilizes or calls data updater 176, object updater 177 or GUI updater 178 to update application internal state 192. Alternatively, one or more of the application views in the application views 191 include one or more corresponding event handlers 190. In addition, in some embodiments, one or more of the data updater 176, the object updater 177, and the GUI updater 178 are included in the corresponding application view 191.

[0137] A corresponding event identifier 180 receives event information (e.g., event data 179) from event classifier 170 and identifies an event from the event information. Event identifier 180 includes an event receiver 182 and an event comparator 184. In some embodiments, event identifier 180 also includes metadata 183 and at least a subset of event delivery instructions 188 (which optionally include sub-event delivery instructions).

[0138] Event receiver 182 receives event information from event classifier 170. Event information includes information about sub-events such as touch or touch movement. Depending on the sub-event, the event information also includes additional information, such as the location of the sub-event. When the sub-event involves the movement of the touch, the event information optionally also includes the speed and direction of the sub-event. In some embodiments, the event includes the device rotating from one orientation to another orientation (e.g., from a longitudinal orientation to a transverse orientation, or vice versa), and the event information includes corresponding information about the current orientation of the device (also referred to as the device posture).

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

[0140] In some embodiments, event definition 187 includes definitions of events for associated user interface objects. In some embodiments, event comparator 184 performs a hit test to determine which user interface object is associated with a sub-event. For example, in an application view displaying three user interface objects 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, the event comparator uses the result of the hit test to determine which event handler 190 should be activated. For example, event comparator 184 selects an event handler associated with the sub-event and the object that triggered the hit test.

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

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

[0143] In some embodiments, the corresponding event identifier 180 includes metadata 183 having configurable properties, flags, and / or lists that indicate how the event delivery system should perform sub-event delivery to actively participating event identifiers. In some embodiments, metadata 183 includes configurable properties, flags, and / or lists that indicate how event identifiers interact or can interact with each other. In some embodiments, metadata 183 includes configurable properties, flags, and / or lists that indicate whether sub-events are delivered to different levels in a view or programmatic hierarchy.

[0144] In some embodiments, when one or more specific sub-events of an event are identified, the corresponding event recognizer 180 activates an event handler 190 associated with the event. In some embodiments, the corresponding event recognizer 180 delivers event information associated with the event to the event handler 190. Activating the event handler 190 is different from sending (and deferred sending) the sub-events to the corresponding hit view. In some embodiments, the event recognizer 180 issues a flag associated with the identified event, and the event handler 190 associated with the flag obtains the flag and performs a predefined process.

[0145] In some embodiments, 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 sub-event sequence or to an actively participating view. An event handler associated with a sub-event sequence or with an actively participating view receives the event information and performs a predetermined process.

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

[0147] In some embodiments, one or more event handlers 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 the corresponding application 136-1 or application view 191. In other embodiments, they are included in two or more software modules.

[0148] It should be understood that the above discussion of event processing of user touches on a touch-sensitive display also applies to other forms of user input using input devices to operate the multifunction device 100, and not all user input is initiated on the touch screen. For example, mouse movement and mouse button presses, optionally in conjunction with single or multiple keyboard presses or presses; contact movement on a touch pad, such as tapping, dragging, scrolling, etc.; stylus input; movement of the device; verbal commands; detected eye movement; biometric input; and / or any combination thereof are optionally used as input corresponding to sub-events defining the event to be recognized.

[0149] Figure 2A portable multifunction device 100 with a touch screen 112 according to some embodiments is shown. The touch screen optionally displays one or more graphics within a user interface (UI) 200. In this embodiment and in other embodiments described below, a user can select one or more of these graphics by, for example, making gestures on the graphics using one or more fingers 202 (not drawn to scale in the accompanying drawings) or using one or more styluses 203 (not drawn to scale in the accompanying drawings). In some embodiments, when the user interrupts contact with one or more graphics, selection of one or more graphics will occur. In some embodiments, gestures optionally include one or more taps, one or more swipes (from left to right, from right to left, up and / or down) and / or rolling of fingers that have been in contact with the device 100 (from right to left, from left to right, up and / or down). In some specific implementations or in some cases, inadvertent contact with a graphic will not select the graphic. For example, when the gesture corresponding to the selection is a tap, a swipe gesture that sweeps over an application icon optionally does not select the corresponding application.

[0150] The device 100 optionally also includes one or more physical buttons, such as a "Home" or menu button 204. As previously described, the menu button 204 is optionally used to navigate to any application 136 in a set of applications that are optionally executed on the device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI displayed on the touch screen 112.

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

[0152] Figure 3300 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface according to some embodiments. The device 300 need not be portable. In some embodiments, the device 300 is a laptop, a desktop computer, a tablet computer, a multimedia player device, a navigation device, an educational device (such as a children's learning toy), a game system, or a control device (e.g., a home controller or an industrial controller). The device 300 typically includes one or more processing units (CPUs) 310, one or more network or other communication interfaces 360, a memory 370, and one or more communication buses 320 for interconnecting these components. The communication bus 320 optionally includes circuits (sometimes called chipsets) that interconnect system components and control communications between system components. The device 300 includes an input / output (I / O) interface 330 with a display 340, which is typically a touch screen display. The I / O interface 330 also optionally includes a keyboard and / or mouse (or other device) 350 and a touchpad 355, a tactile output generator 357 for generating tactile output on the device 300 (e.g., similar to the above reference). Figure 1A The one or more tactile output generators 167 described above), sensors 359 (e.g., optical sensors, acceleration sensors, proximity sensors, touch sensors, and / or contact intensity sensors (similar to the above referenced Figure 1A The memory 370 optionally includes one or more storage devices located away from the one or more CPUs 310. In some embodiments, the memory 370 stores information related to the portable multifunction device 100 ( Figure 1A ) or a subset thereof. In addition, 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 a drawing module 380, a presentation module 382, ​​a word processing module 384, a website creation module 386, a disk editing module 388, and / or a spreadsheet module 390, while portable multifunction device 100 ( Figure 1A )'s memory 102 optionally does not store these modules.

[0153] Figure 3Each element in the above-mentioned elements in is optionally stored in one or more memory devices of the previously mentioned memory device.Each module in the above-mentioned module corresponds to the instruction set for performing the above-mentioned functions.The above-mentioned modules or programs (e.g., instruction sets) need not be implemented as independent software programs, processes or modules, and therefore the various subsets of these modules are optionally combined or otherwise rearranged in various embodiments.In some embodiments, memory 370 optionally stores the subset of the above-mentioned modules and data structures.In addition, memory 370 optionally stores other modules and data structures not described above.

[0154] Attention is now turned to an embodiment of a user interface that is optionally implemented on, for example, portable multifunction device 100.

[0155] Figure 4A An exemplary user interface of a menu of applications on portable multifunction device 100 according to some embodiments is shown. A similar user interface is optionally implemented on device 300. In some embodiments, user interface 400 includes the following elements, or a subset or superset thereof:

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

[0157] Time 404;

[0158] Bluetooth indicator 405;

[0159] Battery status indicator 406;

[0160] A tray 408 with icons of commonly used applications, such as:

[0161] o an icon 416 of the phone module 138 labeled “Phone” which optionally includes an indicator 414 of the number of missed calls or voice messages;

[0162] o an icon 418 of the email client module 140 labeled “Mail”, which optionally includes an indicator 410 of the number of unread emails;

[0163] o An icon 420 labeled “Browser” of the browser module 147; and

[0164] o an icon 422 labeled “iPod” of a video and music player module 152 (also referred to as an iPod (trademark of Apple Inc.) module 152); and

[0165] Icons for other apps, such as:

[0166] o Icon 424 of IM module 141 labeled “Message”;

[0167] o Icon 426 labeled “Calendar” of calendar module 148;

[0168] o Icon 428 labeled “Photos” of the image management module 144;

[0169] o An icon 430 labeled “Camera” of the camera module 143;

[0170] o Icon 432 labeled “Online Video” of the online video module 155;

[0171] o Icon 434 labeled "Stock Market" of the Stock Market widget 149-2;

[0172] o an icon 436 labeled “MAP” of the map module 154;

[0173] o Icon 438 labeled "Weather" of the Weather widget 149-1;

[0174] o Icon 440 labeled as “Clock” of the alarm clock widget 149-4;

[0175] o an icon 442 labeled “Fitness Support” of the fitness support module 142;

[0176] o An icon 444 labeled "Notepad" of the notepad module 153; and

[0177] o An icon 446 labeled “Settings” for a settings application or module that provides access to settings for the device 100 and its various applications 136.

[0178] Please note that Figure 4A The icon labels shown in are exemplary only. For example, icon 422 of video and music player module 152 is labeled "Music" or "Music Player". Other labels are optionally used for various application icons. In some embodiments, the label of a corresponding application icon includes the name of the application corresponding to the corresponding application icon. In some embodiments, the label of a particular application icon is different from the name of the application corresponding to the particular application icon.

[0179] Figure 4B A touch-sensitive surface 451 (eg, touch screen display 112) is shown having a touch-sensitive surface 451 (eg, Figure 3 tablet or touch pad 355) device (e.g., Figure 3Device 300 also optionally includes one or more contact intensity sensors (e.g., one or more of sensors 359) for detecting intensity of contact on touch-sensitive surface 451, and / or one or more tactile output generators 357 for generating tactile output for a user of device 300.

[0180] Although some of the examples below are given with reference to input on a touch screen display 112 (where a touch-sensitive surface and a display are combined), in some embodiments, the device detects input on a touch-sensitive surface that is separate from the display, such as Figure 4B In some embodiments, the touch-sensitive surface (e.g., Figure 4B 451) has a main axis (e.g., Figure 4B 453) corresponding to the principal axis (for example, Figure 4B According to these embodiments, the device detects a position corresponding to a corresponding position on the display (e.g., Figure 4B 460 corresponds to 468 and 462 corresponds to 470) in contact with touch-sensitive surface 451 (e.g., Figure 4B Thus, when the touch-sensitive surface (e.g., Figure 4B 451) and the display of a multi-function device ( Figure 4B When the user input detected by the device on the touch-sensitive surface (e.g., contacts 460 and 462 and their movement) is separated, the device is used by the device to manipulate the user interface on the display. It should be understood that similar methods are optionally used for other user interfaces described herein.

[0181] In addition, although the following examples are primarily given with reference to finger inputs (e.g., finger contacts, single-finger tap gestures, finger swipe gestures), it should be understood that in some embodiments, one or more of these finger inputs are replaced by input from another input device (e.g., mouse-based input or stylus input). For example, a swipe gesture is optionally replaced by a mouse click (e.g., instead of contact), followed by movement of the cursor along the path of the swipe (e.g., instead of movement of the contact). As another example, a tap gesture is optionally replaced by a mouse click when the cursor is over the location of the tap gesture (e.g., instead of detecting contact, followed by ceasing to detect contact). Similarly, when multiple user inputs are detected simultaneously, it should be understood that multiple computer mice are optionally used simultaneously, or a mouse and finger contact are optionally used simultaneously.

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

[0183] Exemplary techniques for detecting and processing touch intensity are found, for example, in the following related patent applications: International Patent Application Serial No. PCT / US2013 / 040061, filed on May 8, 2013, entitled “Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application,” published as WIPO Patent Publication No. WO / 2013 / 169849; and International Patent Application Serial No. PCT / US2013 / 069483, filed on November 11, 2013, entitled “Device, Method, and Graphical User Interface for Transitioning Between Touch Input to Display Output Relationships,” published as WIPO Patent Publication No. WO / 2014 / 105276, each of which is hereby incorporated by reference in its entirety.

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

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

[0186] In some embodiments, input mechanism 508 is optionally a microphone. Personal electronic device 500 optionally includes various sensors, such as GPS sensor 532, accelerometer 534, orientation sensor 540 (e.g., compass), gyroscope 536, motion sensor 538, and / or combinations thereof, all of which can be operatively connected to I / O portion 514.

[0187] 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 following techniques, including processes 800 and 1000 ( Figure 8 and Fig.10). Computer-readable storage media can be any medium that can tangibly contain or store computer-executable instructions for use by or in conjunction with instruction execution systems, devices, and apparatuses. In some embodiments, the storage medium is a transient computer-readable storage medium. In some embodiments, the storage medium is a non-transitory computer-readable storage medium. Non-transitory computer-readable storage media may include, but are not limited to, magnetic storage devices, optical storage devices, and / or semiconductor storage devices. Examples of such storage devices include magnetic disks, optical disks based on CD, DVD, or Blu-ray technology, and persistent solid-state memories such as flash memory, solid-state drives, and the like. Personal electronic device 500 is not limited to Figure 5B components and configurations, but may include other components or additional components in a variety of configurations.

[0188] As used herein, the term "indicative representation" refers to an optional feature of the apparatus 100, 300, and / or 500 ( Figure 1A , Figure 3 and FIG. 5A to FIG. 5B ) is a user-interactive graphical user interface object displayed on a display screen of a computer. For example, an image (e.g., an icon), a button, and text (e.g., a hyperlink) optionally each constitute an affordance.

[0189] As used herein, the term "focus selector" refers to an input element used to indicate the current portion of a user interface that a user is interacting with. In some implementations that include a cursor or other position marker, the cursor acts as a "focus selector" such that when the cursor is over a particular user interface element (e.g., a button, window, slider, or other user interface element), a focus selector is displayed on a touch-sensitive surface (e.g., Figure 3 Touchpad 355 or Figure 4B In the event that an input (e.g., a press input) is detected on the touch-sensitive surface 451 in the display, the particular user interface element is adjusted according to the detected input. In the case that a touch-screen display (e.g., Figure 1A A touch-sensitive display system 112 or Figure 4AIn some implementations of the touch screen 112 in FIG. 1 , a detected contact on the touch screen acts as a “focus selector” such that when an input (e.g., a press input by the contact) is detected at the location of a particular user interface element (e.g., a button, window, slider, or other user interface element) on the touch screen display, the particular user interface element is adjusted in accordance with the detected input. In some implementations, the focus moves from one area of ​​the user interface to another area of ​​the user interface without corresponding movement of a cursor or movement of a contact on the touch screen display (e.g., by using a tab key or arrow keys to move the focus from one button to another); in these implementations, the focus selector moves in accordance with the movement of the focus between different areas of the user interface. Regardless of the specific form the focus selector takes, the focus selector is typically a user interface element (or contact on the touch screen display) that is controlled by the user to deliver the user's intended interaction with the user interface (e.g., by indicating to the device the element of the user interface with which the user desires to interact). For example, when a press input is detected on a touch-sensitive surface (e.g., a trackpad or touch screen), the position of a focus selector (e.g., a cursor, contact, or selection box) over a corresponding button will indicate that the user intends to activate the corresponding button (rather than other user interface elements shown on the device display).

[0190] As used in the specification and claims, the term "characteristic intensity" of a contact refers to a characteristic of a contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on multiple intensity samples. The characteristic intensity is optionally based on a predefined number of intensity samples or a set of intensity samples collected during a predetermined time period (e.g., 0.05 seconds, 0.1 seconds, 0.2 seconds, 0.5 seconds, 1 second, 2 seconds, 5 seconds, 10 seconds) relative to a predefined event (e.g., after contact is detected, before contact is detected to be lifted off, before or after contact starts to move, before contact ends, before or after contact intensity is detected to increase, and / or before or after contact intensity is detected to decrease). The characteristic intensity of a contact is optionally based on one or more of the following: the maximum value of the intensity of the contact, the mean value of the intensity of the contact, the average value of the intensity of the contact, the value at the top 10% of the intensity of the contact, the half-maximum value of the intensity of the contact, the 90% maximum value of the intensity of the contact, etc. In some embodiments, the duration of the contact is used when determining the characteristic intensity (e.g., when the characteristic intensity is the average value of the intensity of the contact over time). In some embodiments, the feature strength is compared to a set of one or more strength thresholds to determine whether the user has performed an operation. For example, the set of one or more strength thresholds optionally includes a first strength threshold and a second strength threshold. In this example, a contact whose feature strength does not exceed the first threshold results in a first operation, a contact whose feature strength exceeds the first strength threshold but does not exceed the second strength threshold results in a second operation, and a contact whose feature strength exceeds the second threshold results in a third operation. In some embodiments, a comparison between the feature strength and one or more thresholds is used to determine whether to perform one or more operations (e.g., whether to perform the corresponding operation or to abandon the corresponding operation) rather than to determine whether to perform the first operation or the second operation.

[0191] Figure 5C Detecting multiple contacts 552A-552E on touch-sensitive display screen 504 using multiple intensity sensors 524A-524D is shown. Figure 5C Also included is an intensity graph that shows the current intensity measurements of intensity sensors 524A-524D relative to intensity units. In this embodiment, the intensity measurements of intensity sensors 524A and 524D are each 9 intensity units, and the intensity measurements of intensity sensors 524B and 524C are each 7 intensity units. In some implementations, the cumulative intensity is the sum of the intensity measurements of multiple intensity sensors 524A-524D, which is 32 intensity units in this embodiment. In some embodiments, each contact is assigned a corresponding intensity, which is a portion of the cumulative intensity. Figure 5DThe cumulative strength assigned to contacts 552A-552E based on their distance from the center of force 554 is shown. In this embodiment, each of contacts 552A, 552B, and 552E is assigned a contact strength of 8 strength units of the cumulative strength, and each of contacts 552C and 552D is assigned a contact strength of 4 strength units of the cumulative strength. More generally, in some embodiments, each contact j is assigned a corresponding strength Ij, which is a portion of the cumulative strength A, according to a predefined mathematical function Ij=A·(Dj / ΣDi), where Dj is the distance of the corresponding contact j from the center of force, and ΣDi is the sum of the distances of all corresponding contacts (e.g., i=1 to the last) from the center of force. The reference may be performed using an electronic device similar to or equivalent to device 100, 300, or 500. Figure 5C-5D In some embodiments, the characteristic intensity of the contact is based on one or more intensities of the contact. In some embodiments, the intensity sensor is used to determine a single characteristic intensity (e.g., a single characteristic intensity of a single contact). It should be noted that the intensity map is not part of the displayed user interface, but is included in the Figure 5C-5D To help readers.

[0192] In some embodiments, a portion of a gesture is identified for determining characteristic strength. For example, the touch-sensitive surface optionally receives a continuous swipe contact that transitions from a starting position and reaches an end position, where the contact strength increases. In this embodiment, the characteristic strength of the contact at the end position is optionally based only on a portion of the continuous swipe contact, rather than the entire swipe contact (e.g., only the portion of the swipe contact at the end position). In some embodiments, a smoothing algorithm is optionally applied to the intensity of the swipe contact before determining the characteristic strength of the contact. For example, a smoothing algorithm optionally includes one or more of the following: an unweighted sliding average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and / or an exponential smoothing algorithm. In some cases, these smoothing algorithms eliminate narrow peaks or depressions in the intensity of the swipe contact to achieve the purpose of determining the characteristic strength.

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

[0194] An increase in contact feature intensity from an intensity below a light press intensity threshold to an intensity between the light press intensity threshold and the deep press intensity threshold is sometimes referred to as a "light press" input. An increase in contact feature intensity from an intensity below a deep press intensity threshold to an intensity above the deep press intensity threshold is sometimes referred to as a "deep press" input. An increase in contact feature intensity from an intensity below a contact detection intensity threshold to an intensity between the contact detection intensity threshold and the light press intensity threshold is sometimes referred to as detecting contact on the touch surface. A decrease in contact feature intensity from an intensity above the contact detection intensity threshold to an intensity below the contact detection intensity threshold is sometimes referred to as detecting contact lifted 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.

[0195] In some embodiments described herein, one or more operations are performed in response to detecting a gesture that includes a corresponding press input or in response to detecting a corresponding press input performed using a corresponding contact (or multiple contacts), wherein the corresponding press input is detected at least in part based on detecting that the strength of the contact (or multiple contacts) increases to above a press input strength threshold. In some embodiments, the corresponding operation is performed in response to detecting that the strength of the corresponding contact increases to above the press input strength threshold (e.g., a "down stroke" of the corresponding press input). In some embodiments, the press input includes an increase in the strength of the corresponding contact to above the press input strength threshold and the strength of the contact subsequently decreases to below the press input strength threshold, and the corresponding operation is performed in response to detecting that the strength of the corresponding contact subsequently decreases to below the press input threshold (e.g., an "up stroke" of the corresponding press input).

[0196] Figure 5E-Figure 5HDetection of a gesture is shown, the gesture comprising contact 562 with an intensity from below Figure 5E The light press intensity threshold in L ”) increases to a strength higher than Figure 5H The deep compression intensity threshold in D ”). On the displayed user interface 570 including application icons 572A-572D displayed in the predefined area 574, when the cursor 576 is displayed above the application icon 572B corresponding to the application 2, the gesture performed using the contact 562 is detected on the touch-sensitive surface 560. In some embodiments, the gesture is detected on the touch-sensitive display 504. The intensity sensor detects the intensity of the contact on the touch-sensitive surface 560. The device determines that the intensity of the contact 562 is within the deep press intensity threshold (for example, “IT D ”) reaches a peak above. Contact 562 is maintained on touch-sensitive surface 560. In response to detecting the gesture, and according to the intensity increasing to a deep press intensity threshold (e.g., “IT D ”) above contact 562, displays reduced-scale representations 578A-578C (e.g., thumbnails) of documents recently opened for application 2, such as Figure 5F-5H In some embodiments, the intensity is a characteristic intensity of the contact compared to one or more intensity thresholds. It should be noted that the intensity map for contact 562 is not part of the displayed user interface, but is included in the Figure 5E-Figure 5H To help readers.

[0197] In some embodiments, the display of representations 578A-578C includes animation. For example, representation 578A is initially displayed near application icon 572B, such as Fig. 5F As the animation progresses, representation 578A moves upward and representation 578B is displayed near application icon 572B, as shown in FIG. Figure 5G Then, representation 578A moves upward, 578B moves upward toward representation 578A, and representation 578C is displayed near application icon 572B, as shown in FIG. Figure 5H 578A-578C form an array above icon 572B. In some embodiments, the animation progresses according to the intensity of contact 562, such as Figure 5F-5G , where representations 578A-578C appear and increase as the strength of contact 562 approaches a deep press strength threshold (eg, “IT D ”) increases and moves upward. In some embodiments, the intensity according to which the animation progresses is the characteristic intensity of the contact. The reference may be performed using an electronic device similar to or equivalent to device 100, 300, or 500. Figure 5E-Figure 5H The operation described.

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

[0199] For ease of explanation, optionally, a description of an operation performed in response to a press input associated with a press input intensity threshold or in response to a gesture including a press input is triggered in response to detecting any of the following: contact intensity increasing to above the press input intensity threshold, contact intensity increasing from an intensity below a hysteresis intensity threshold to an intensity above the press input intensity threshold, contact intensity decreasing to below the press input intensity threshold, and / or contact intensity decreasing to below a hysteresis intensity threshold corresponding to the press input intensity threshold. Additionally, in examples where an operation is described as being performed in response to detecting that the intensity of the contact decreases below the press input intensity threshold, the operation is optionally performed in response to detecting that the intensity of the contact decreases below a hysteresis intensity threshold that corresponds to and is less than the press input intensity threshold.

[0200] Figure 6 Exemplary devices connected via one or more communication channels to participate in a transaction according to some embodiments are shown. 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). The one or more electronic devices optionally include NFC hardware and are configured to support NFC.

[0201] The electronic device (e.g., devices 100, 300, and 500) is optionally configured to store payment account information associated with each of one or more payment accounts. The payment account information includes, for example, one or more of the following: a person's name or company name, a billing address, a login name, a password, an account number, an expiration date, a security code, a phone number, a bank associated with the payment account (e.g., an issuing bank), 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., a photo taken by the device and / or received by the device). In some embodiments, the electronic device receives user input including at least some payment account information (e.g., receiving a credit card number, a debit card number, an account number or a shopping card number and an 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 a payment card captured by a camera sensor of the device). In some embodiments, the electronic device receives at least some payment account information from another device (e.g., another user device or a server). In some embodiments, the electronic device receives payment account information from a server associated with another service (e.g., an application for renting or selling audio files and / or video files) for which the user or user device's account has previously made a purchase or for which payment account data has been identified.

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

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

[0204] Electronic devices (e.g., 100, 300, 500) are configured to communicate with each other via any of a variety of networks. For example, the devices communicate using a Bluetooth connection 608 (e.g., including a traditional Bluetooth connection or a Bluetooth low energy connection) or using a WiFi network 606. Communications between user devices are optionally adjusted to reduce the possibility of improper sharing of information between devices. For example, communication about payment information requires that the communicating devices be paired (e.g., associated with each other via explicit user interaction) or associated with the same user account.

[0205] In some embodiments, an electronic device (e.g., 100, 300, 500) is used to communicate with a point of sale (POS) payment terminal 600, which optionally supports NFC. The communication is optionally carried out using various communication channels and / or technologies. In some examples, an electronic device (e.g., 100, 300, 500) uses an NFC channel 610 to communicate with a payment terminal 600. In some embodiments, the payment terminal 600 uses a peer-to-peer NFC mode to communicate with an electronic device (e.g., 100, 300, 500). An electronic device (e.g., 100, 300, 500) is optionally configured to transmit a signal to the payment terminal 600, the signal including payment information of a payment account (e.g., a default account or an account selected for a specific transaction).

[0206] In some embodiments, the generation and / or transmission of the signal is controlled by a security element in an electronic device (e.g., 100, 300, 500). Before issuing payment information, the security element optionally requires specific user input. For example, the security element optionally requires: detecting the electronic device being worn, detecting button presses, detecting password input, detecting touch, detecting one or more option selections (e.g., option selections received when interacting with an application), detecting fingerprint signatures, detecting voice or voice commands, and / or detecting gestures or movements (e.g., rotation or acceleration). In some embodiments, if a communication channel (e.g., NFC communication channel) with another device (e.g., payment terminal 600) is established within a defined time period from when the input is detected, the security element issues payment information so that it is transmitted to another device (e.g., payment terminal 600). In some embodiments, the security element is a hardware component that controls the release of security information. In some embodiments, the security element is a software component that controls the release of security information.

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

[0208] The payment terminal 600 optionally uses the payment information to generate a signal for transmission to the payment server 604 to determine whether the payment is authorized. The payment server 604 optionally includes any device or system configured to receive the payment information associated with the payment account and determine whether to authorize the proposed purchase. In some embodiments, the payment server 604 includes a server of the issuing bank. The payment terminal 600 communicates directly with the payment server 604 or indirectly via one or more devices or systems (e.g., a server of the acquiring bank and / or a server of the card network).

[0209] Payment server 604 optionally uses at least some of the payment information to identify the user account from a database of user accounts (e.g., 602). For example, each user account includes payment information. The account is optionally located by locating an account with specific payment information that matches the information from the POS communication. In some embodiments, payment is rejected when the provided payment information is inconsistent (e.g., the expiration date does not correspond to the credit card number, the debit card number, or the shopping card number does not correspond) or when no account includes payment information that matches the information from the POS communication.

[0210] In some embodiments, the user account data further identifies one or more constraints (e.g., credit limit); current or previous balances; previous transaction dates, locations, and / or amounts; account status (e.g., active or frozen), and / or authorization instructions. In some embodiments, the payment server (e.g., 604) uses such data to determine whether to authorize a payment. For example, the payment server denies payment when the purchase amount added to the current balance would cause the account limit to be exceeded, when the account is frozen, when the previous transaction amount exceeds a threshold, or when the number or frequency of previous transactions exceeds a threshold.

[0211] In some embodiments, the payment server 604 responds to the POS payment terminal 600 with an indication of whether the proposed purchase is authorized or rejected. In some embodiments, the POS payment terminal 600 transmits a signal to the electronic device (e.g., 100, 300, 500) to identify the result. For example, when the purchase is authorized (e.g., via a transaction coordination server that manages a transaction application on a user device), the POS payment terminal 600 sends a receipt to the electronic device (e.g., 100, 300, 500). In some cases, the POS payment terminal 600 presents an output (e.g., a visual output or an audio output) indicating the result. The payment may be transmitted to the merchant as part of the authorization process, or may be transmitted later.

[0212] In some embodiments, the electronic device (e.g., 100, 300, 500) participates in a transaction that is completed without involving the POS payment terminal 600. For example, upon detecting that the mechanical input has been received, the secure element in the electronic device (e.g., 100, 300, 500) releases the payment information to allow an application on the electronic device to access the information (e.g., and transmit the information to a server associated with the application).

[0213] In some embodiments, the electronic device (e.g., 100, 300, 500) is in a locked state or an unlocked state. In the locked state, the electronic device is powered on and is operable, but it is blocked from performing a predefined set of operations in response to user input. The predefined set of operations may include navigating between user interfaces, activating or deactivating a predefined set of functions, and activating or deactivating certain applications. The locked state can be used to prevent unconscious or unauthorized use of some functions of the electronic device, or to activate or deactivate some functions on the electronic device. In the unlocked state, the electronic device 100 is powered on and is operable, and is not blocked from performing at least a portion of a predefined set of operations that cannot be performed when in the locked state.

[0214] When the device is in the locked state, the device is said to be locked. In some embodiments, the device in the locked state can respond to a restricted set of user inputs, including inputs corresponding to attempts to convert the device to the unlocked state or inputs corresponding to shutting down the device.

[0215] In some embodiments, the security element is a hardware component (e.g., a secure microcontroller chip) configured to securely store data or algorithms. In some embodiments, the security element provides (or publishes) payment information (e.g., account number and / or transaction-specific dynamic security code). In some embodiments, the security element provides (or publishes) payment information in response to receiving authorization, such as user authentication (e.g., fingerprint authentication; password authentication; when the device is in an unlocked state, and optionally when the device has been continuously on the user's wrist since the device was unlocked by providing authentication credentials to the device, a double press of the hardware button is detected, wherein the device is determined to be continuously present on the user's wrist by periodically checking that the device is in contact with the user's skin). For example, the device detects a fingerprint at the device's fingerprint sensor (e.g., a fingerprint sensor integrated into a button). The device determines whether the fingerprint is consistent with the registered fingerprint. Based on determining that the fingerprint is consistent with the registered fingerprint, the security element provides (or publishes) payment information. Based on determining that the fingerprint is inconsistent with the registered fingerprint, the security element abandons providing (or publishing) payment information.

[0216] Attention is now turned to embodiments of a user interface ("UI") and associated processes implemented on an electronic device, such as portable multifunction device 100, device 300, or device 500.

[0217] Figure 7A-Figure 7O An exemplary user interface for transactions according to some embodiments is shown. The user interface in these figures is used to illustrate the process described below, including Figure 8 process.

[0218] In some embodiments, electronic device 500A includes a display, one or more input devices, and hardware buttons (e.g., mechanical buttons configured to enable a secure payment module to provide payment information for use in a payment transaction). In some embodiments, electronic device 500A is a smartwatch electronic device. In some embodiments, device 500A includes some or all of the features of device 100, device 300, or device 500.

[0219] like Fig. 7A As shown, electronic device 500A displays an application user interface 702 for a corresponding application (e.g., a third-party application) on a display, wherein the application user interface (e.g., 702) includes a transaction enable representation (e.g., 702A) for requesting payment for an activity associated with the corresponding application. In some embodiments, the electronic device displays system user interface elements (e.g., time indicator 704A, date indicator). Fig. 7A In some embodiments, the system user interface element 704A indicates the current time of day. In some embodiments, the system user interface element indicates the day of the month, the name of the currently logged in user account, the current location of the device, and / or a battery level indication of the electronic device 500A. In some embodiments, the electronic device 500A displays an indication 702B of the name of the corresponding application.

[0220] exist Figure 7B At , while displaying the application user interface (e.g., 702), electronic device 500A detects selection of transaction-enabled representation 702A through one or more input devices. In some embodiments, detecting selection of transaction-enabled representation 702A includes detecting a tap input on a touch-sensitive surface of electronic device 500A corresponding to a location of transaction-enabled representation 702A.

[0221] In some embodiments, Figure 7A-7BAs shown, a transaction enable representation (e.g., 702A) displayed in an application user interface (e.g., 702) for a corresponding application is provided by a payment application (e.g., 500A) that is different from the corresponding application (e.g., to the corresponding application in the application user interface) of an electronic device (e.g., 500A) (e.g., the transaction enable representation is a button whose appearance and / or position is determined by the payment application, such as a payment button indicating "Pay with Wallet"). In some embodiments, the payment application is a first-party application provided by the manufacturer of the electronic device. In some embodiments, the payment application is an electronic wallet application that can access personal information of the user of the electronic device, which cannot be accessed by the corresponding application. In some embodiments, the information is payment information (e.g., account number, payment account number) of a payment account (e.g., a credit account) of the electronic wallet application. In some embodiments, the electronic wallet application has access to information for multiple payment accounts associated with the user of the electronic device 500A.

[0222] In some embodiments, such as Figure 7A-7B As shown, a transaction enablement representation (e.g., 702A) is provided by the corresponding application, which, when activated, triggers display of a transaction user interface (e.g., 706) (e.g., by a payment application) (e.g., the transaction enablement representation is a button whose appearance and position are determined by the corresponding application, such as a rideshare payment button that indicates "Request a Ride").

[0223] Figure 7C and Fig.7D An alternative user interface is shown. Figure 7C and Fig.7D As shown, in response to detecting selection of a transaction enabling indication (e.g., 702A), the electronic device 500A displays a transaction user interface (e.g., 706) (e.g., replacing display of the application user interface 702 with display of the transaction user interface 706), which transaction user interface includes simultaneously displaying transaction details for an activity associated with the corresponding application (e.g., a payment account 706B, a payee 706C for payment, the name of the corresponding application, a tax amount, an indication of a variable cost of the activity 706D) and an instruction to activate a hardware button of the device 500A to authorize payment for the activity associated with the corresponding application (e.g., 706A).

[0224] In some embodiments, the corresponding application is a third-party application. In some embodiments, before displaying the application user interface 702 for the corresponding application, the electronic device receives a request provided by the user to download and install the corresponding application. In some embodiments, before displaying the application user interface 702 for the corresponding application, the electronic device receives a request provided by the user to download and install the corresponding application. In some embodiments, the electronic device is configured to allow the corresponding application to be uninstalled or deleted from the electronic device based on a user request.

[0225] In some embodiments, the activity associated with the corresponding application includes one or more of the following: a transportation request, a rideshare request, a purchase of a service, a purchase of a product, and a peer-to-peer transaction. In some embodiments, the activity associated with the corresponding application is a request for transportation. In some embodiments, the activity associated with the corresponding application is a request for a rideshare. In some embodiments, the activity associated with the corresponding application is a purchase of a service. In some embodiments, the activity associated with the corresponding application is a purchase of a product. In some embodiments, the activity associated with the corresponding application is a peer-to-peer transaction.

[0226] In some embodiments, such as Figure 7C As shown, if the activity has a variable cost, the information about the cost of the activity indicates that the transaction has a variable cost (e.g., 706D, a "pending" indication at the top of the user interface 706, and when the UI is scrolled, the total charge amount is displayed at the bottom of the UI). In some embodiments, based on determining that the activity has a variable cost, the transaction details include an indication that the activity has a variable cost (e.g., 706D). For example, information 706D includes the language "pending amount" to indicate that the cost of the activity will be determined after the activity ends (e.g., after the user completes the ride using the ridesharing system). In some embodiments, in response to receiving an input corresponding to an indication of scrolling the transaction user interface 706 (e.g., detecting a scroll gesture on the touch-sensitive surface, detecting rotation of a rotatable input mechanism), the electronic device scrolls the transaction user interface 706 on the display to display the total cost of the payment.

[0227] In some embodiments, such as Fig.7D As shown in , the transaction details include information about the cost of the activity (e.g., 706B). In some embodiments, the transaction details include the total cost of the activity. In some embodiments, the transaction details include the transportation cost for the activity (e.g., the cost of shipping the product).

[0228] In some embodiments, such as Figure 7C-Figure 7EAs shown, displaying a transaction user interface (e.g., 706) also includes (e.g., simultaneously) displaying a graphical representation of a payment account (e.g., 706E), which will be used to pay (e.g., by the electronic device 500A) if authorization to conduct a payment transaction is received (e.g., via a double press of a hardware button by a user). In some embodiments, the payment account is a default payment account. In some embodiments, the payment account is a payment account selected by the user for payment for the activity. In some embodiments, the graphical representation of the payment account includes an illustration of a physical payment card associated with the payment account (e.g., an illustration of an American Express card). In some embodiments, in response to receiving an input corresponding to an instruction to scroll the transaction user interface 706 (e.g., a scroll gesture is detected on a touch-sensitive surface, a rotation of a rotatable input mechanism is detected), the electronic device scrolls the transaction user interface 706 on the display to display a graphical representation of the payment account. In some embodiments, the electronic wallet application of the electronic device stores the payment account (and optionally, one or more additional payment accounts). The payment account (and optionally, one or more additional payment accounts) is an account of a user of the electronic device.

[0229] In some embodiments, such as Figure 7C-Figure 7E As shown in , an instruction (e.g., 706A) is displayed at a position on the display to activate the hardware button. In some embodiments, Figure 7C-Figure 7E As shown in , the location on the display corresponds to (eg, is adjacent to) a hardware button of the electronic device.

[0230] In some embodiments, such as Figure 7E-7F As shown, while displaying a transaction user interface (e.g., 706) including transaction details (e.g., 708A, 708B, contact information, shipping address, taxes, total cost) and an instruction to activate a hardware button (e.g., 706A), an input corresponding to an instruction to scroll the transaction user interface (e.g., 706) (e.g., a user request to the electronic device 500A) is received via one or more input devices (e.g., detecting a scroll gesture on a touch-sensitive surface, detecting rotation of a rotatable input mechanism). In some embodiments, in response to receiving the input corresponding to an instruction to scroll the transaction user interface (e.g., 706): the electronic device 500A displays on the display (e.g., by scrolling the transaction user interface (e.g., 706) to reveal) additional transaction details (e.g., billing address 708A, contact information 708B, shipping address, taxes, total cost) for an activity associated with a corresponding application.

[0231] In some embodiments, even when the user performs a scroll gesture, the electronic device does not scroll the instructions (e.g., 706A) to activate the hardware button. In some embodiments, the instructions (e.g., 706A) to activate the hardware button are displayed on the display at a location determined based on the location of the hardware button. In some embodiments, the instructions (e.g., 706A) are displayed near the hardware button to notify the user that the button can be activated to authorize the payment. In some embodiments, such as Figure 7C-Figure 7E and Figure 7K As shown, based on determining that the hardware button is in a first position (e.g., due to the orientation of the device), electronic device 500A displays instruction 706A on the display at a first position (e.g., above the representation of payment amount 706B and adjacent to the hardware button on device 500A). In some embodiments, as Fig.7O As shown, based on determining that the hardware button is in the second position, the electronic device 500A displays instructions 706A at a second position on the display that is different from the first position (e.g., below the representation of the payment amount 706B and adjacent to the button on the device 500A). In some embodiments, displaying additional transaction details of an activity associated with the corresponding application includes: abandoning the instructions to scroll to activate the hardware button (e.g., maintaining the display of the instructions (e.g., 706A)) to activate the hardware button, and scrolling additional transaction details (e.g., 708A, 708B) on the display (e.g., at the position of the instructions to activate the hardware button). In some embodiments, the instructions to activate the hardware button are maintained at the position on the display (at least initially) when the additional transaction details are scrolled onto the display. In some embodiments, the instructions to activate the hardware button (e.g., 706) fade out on the display (no scrolling) when the additional transaction details are scrolled onto the display. In some embodiments, the electronic device 500A fades out the instructions to activate the hardware button (e.g., 706) when the electronic device scrolls the transaction user interface (e.g., 706) to reveal the additional transaction details. Therefore, the electronic device does not change the position of the instruction to activate the hardware button because the position of the instruction to activate the hardware button is tied to the position of the physical hardware button.

[0232] In some embodiments, the additional transaction details (e.g., 708A, 708B) scroll on top of the instruction (e.g., 706A). In some embodiments, the scrolling causes the additional transaction details (e.g., 708A, 708B) to at least partially cover the instruction (e.g., 706A) and then completely cover the instruction (e.g., 706A). In some embodiments, displaying the additional transaction details of the activity associated with the corresponding application includes: scrolling the additional transaction details (e.g., 708A, 708B) onto the display so that the additional transaction details cover (completely, partially, or replace) the instruction to activate the hardware button. Therefore, the electronic device 500A does not change the position of the instruction to activate the hardware button because the position of the instruction to activate the hardware button is tied to the position of the physical hardware button.

[0233] In some embodiments, such as Figure 7G-Figure 7I As shown, a tap gesture on the additional transaction details (e.g., 708A or 708B) allows the user to select from different options for the additional transaction details. Figure 7G As shown in , when displaying additional transaction details (e.g., 708A, 708B), electronic device 500A detects the first detail (e.g., 708B) of selecting additional transaction details (e.g., 708A, 708B) through one or more input devices. Figure 7H As shown, in response to detecting the selection of a first detail (e.g., 708B) among the additional transaction details (e.g., detecting activation of an affordance corresponding to the first detail), the electronic device 500A displays one or more options (e.g., 710A, 710B, 710C) for the first detail. In some embodiments, displaying one or more options includes replacing the display of the additional transaction details (e.g., 708A, 708B, 710C) with the display of one or more options (e.g., 710A, 710B, 710C).

[0234] In some embodiments, based on the transaction user interface being displayed (e.g., Figure 7C-Figure 7L As in ): the electronic device 500A monitors the hardware button for activation (e.g., monitoring a double press of the hardware button) (e.g., at all times when the transaction user interface is displayed). Fig.7I and Figure 7K As shown, the electronic device detects activation of the hardware button (e.g., detecting a double press of the hardware button). In some embodiments, Fig.7I and Figure 7K, which illustrates that electronic device 500A is able to detect activation of a hardware button while displaying a different user interface (e.g., of a payment application). In some embodiments, activation of a hardware button is detected while the device is in an unlocked state (and optionally, while the device has been continuously on the user's wrist since the device was unlocked by providing authentication credentials to the device, wherein the continued presence of the device on the user's wrist is determined by periodically checking that the device is in contact with the user's skin). In some embodiments, as Figure 7M and Figure 7N As shown, in response to detecting the activation of a hardware button, based on determining that the activation of the hardware button meets the transaction authorization criteria (e.g., a double press input, where the press inputs are received within a predetermined time threshold between each other, and optionally the contact on the button meets the user authentication criteria, such as matching a fingerprint in a fingerprint database or having been unlocked and kept on the user's wrist since unlocking, and, for example, based on determining that the transaction parameters are correct), the electronic device 500A (e.g., using a payment account of an electronic wallet of the electronic device) conducts the transaction of the activity (e.g., makes a payment, transmits payment information). In some embodiments, in response to detecting the activation of a hardware button, based on determining that the activation of the hardware button does not meet the transaction authorization criteria, the electronic device 500A abandons authorizing the transaction, and optionally displays a different user interface corresponding to the activation of the hardware button (e.g., displaying a representation of a group of recently used applications or displaying a representation of multiple contacts of the user in response to a single press of the hardware button). For example, a double press of the hardware button causes the transaction to be conducted, and a single press of the hardware button causes the display of user interfaces for different applications. In some embodiments, the electronic device 500A detects the activation of the hardware button (e.g., a double press), and in response, if the transaction details are "OK", the transaction is conducted (e.g., Figure 7M-Figure 7N If the transaction details are not "confirmed", an error is displayed (such as Figure 7J and Figure 7L shown).

[0235] In some embodiments, such as Fig.7I and Figure 7K As shown, electronic device 500A detects activation of a hardware button (e.g., detects double pressing of a hardware button). Figure 7M-Figure 7NAs shown, in response to detecting activation of the hardware button, the electronic device 500A performs a transaction (e.g., making a payment, transmitting payment information) for the activity (e.g., using a payment account of an electronic wallet of the electronic device) based on a determination that transaction processing criteria have been met, including criteria that transaction parameters are correct (and optionally, activation of the hardware button meets transaction authorization criteria). In some embodiments, activation of the hardware button is detected while the device is in an unlocked state (and optionally, while the device has been continuously on the user's wrist since the device was unlocked by providing authentication credentials to the device, wherein the continued presence of the device on the user's wrist is determined by periodically checking that the device is in contact with the user's skin). Figure 7J and Figure 7L As shown, in response to detecting activation of a hardware button, based on determining that a transaction parameter is erroneous (e.g., thereby failing to comply with a transaction processing standard requiring that the transaction parameters be correct), the electronic device 500A displays an error notification (e.g., 708C, 712) on the display indicating that an error has been detected rather than proceeding with the transaction (e.g., abandoning the transaction for the activity).

[0236] In some embodiments, based on determining that there is an error in the transaction parameters, the electronic device receives user input at electronic device 500A (e.g., from a user) via one or more input devices (e.g., receiving audio via a personal assistant, detecting activation of an affordance corresponding to alternating contacts 710B). In response to receiving the user input at electronic device 500A, the electronic device modifies (e.g., to correct) the transaction parameters based on the user input. In some embodiments, once the error in the transaction parameters is corrected, the device will conduct the transaction in response to detecting input to authorize the transaction (e.g., activation of a hardware button meets transaction authorization criteria). In some embodiments, using reference Figure 9A-9N Described are techniques and methods 1000 for resolving trading errors.

[0237] In some embodiments, based on determining that there is an error in the transaction parameters, the electronic device receives (e.g., from a user) a request to correct the error (e.g., selecting an error notification). In response to receiving the request to correct the error, based on determining that there are potentially compatible transaction parameters on the electronic device 500A (e.g., in a phone contacts application or database), the electronic device 500A displays one or more of the potentially compatible transaction parameters (e.g., 710A, 710B). In some embodiments, the potentially compatible transaction parameters (e.g., 710A, 710B) are displayed along with a selectable option (e.g., 710C) to enter additional transaction parameters on a companion device different from the electronic device (e.g., option 710C, when selected, initiates a transaction described below with reference to Figure 9A-9N and Fig.10In response to receiving the request to correct the error, based on determining that there are no potentially compatible transaction parameters on the electronic device, the electronic device 500A displays a request on a companion device different from the electronic device 500A (e.g., Figure 9G An instruction to enter additional transaction parameters on an electronic device 300 (e.g., as described below with reference to Figure 9A-9N and Fig.10 1000).

[0238] In some embodiments, such as Figure 7K-7L As shown, displaying an error notification (e.g., 708C) on the display indicating that an error has been detected includes replacing the display of the instruction to activate the hardware button (e.g., 706A) with the display of the error notification (e.g., 708C). In some embodiments, displaying the error notification includes changing the display of the transaction details (e.g., changing the color of the payment amount of the payment transaction).

[0239] In some embodiments, a user can switch between payment accounts. In some embodiments, the electronic device 500A receives user input (e.g., a swipe gesture at a location on the touch-sensitive surface corresponding to the graphical representation 706E of the payment account) via one or more input devices, the user input corresponding to an instruction to select a payment account from a plurality of payment accounts in the electronic wallet of the electronic device 500A. In response to detecting the user input corresponding to the instruction to select a payment account from a plurality of payment accounts, the electronic device 500A selects a payment account for the transaction in the activity (e.g., without leaving the transaction user interface). In some embodiments, switching payment accounts includes switching between a plurality of payment accounts associated with different payment cards, and switching between payment accounts includes selecting different representations of the payment card. In some embodiments, switching payment accounts includes switching between a plurality of payment accounts associated with the same payment card (e.g., a checking account, a deposit account, and a credit account associated with the same payment card), and displaying an affordance for selecting an account associated with the payment card. In some embodiments, when switching from a payment account of a first payment card associated with a single account to a payment account for a second payment card associated with multiple accounts (for example, in response to a left swipe on the representation of the first payment card), the device displays the appearance of an animation of an enabling representation for selecting between multiple accounts associated with the second payment card, and when switching from a payment account associated with the first payment card to a payment account associated with the second payment card (for example, in response to a right swipe on the representation of the second payment card), the device displays the disappearance of an animation of an enabling representation for selecting between multiple accounts associated with the second payment card.

[0240] In some embodiments, display of an indication such as a payment instruction replaces display of a system user interface element. In some embodiments, displaying the transaction user interface includes replacing a displayed system user interface element (e.g., time indicator 704A, date indicator) with a payment instruction (e.g., 704B). In some embodiments, the corresponding application does not have the ability to replace the system user interface element (e.g., time indicator 704A, date indicator). Therefore, by replacing the system user interface element (e.g., time indicator 704A, date indicator) when displaying the transaction user interface, the electronic device notifies the user that the transaction is being processed by a trusted application (e.g., a first-party application, a system-level application, an operating system of the electronic device).

[0241] In some embodiments, such as Figure 7M As shown in , conducting a transaction (e.g., making a payment, transmitting payment information) for an activity (e.g., using a payment account of an electronic wallet of an electronic device) includes: (e.g., after detecting activation of a hardware button, and optionally, when the electronic device is in an unlocked state, and optionally, when the device is on the user's wrist, such as by detecting that the device is in contact with the user's skin), requesting a password (e.g., from the user) (e.g., by displaying a request 714 on a display). In some embodiments, conducting a transaction (e.g., making a payment, transmitting payment information) for an activity (e.g., using a payment account of an electronic wallet of an electronic device) also includes detecting a password (e.g., provided by the user) via one or more input devices. In some embodiments, conducting a transaction (e.g., making a payment, transmitting payment information) for an activity (e.g., using a payment account of an electronic wallet of an electronic device) includes transmitting a password (e.g., sending it with the payment information) (e.g., to a remote server, to a payment processing service) for processing the transaction. Thus, in some embodiments, a user authenticates locally (e.g., at the electronic device) by activating a hardware button (e.g., via a double press) (e.g., when the electronic device is unlocked), and the user authenticates to a remote server (e.g., a payment processing service) via a password. In some embodiments, the password is verified locally at the electronic device (rather than transmitting the password for processing the transaction). If the password is consistent with the registered password, the electronic device transmits the payment information to the remote server (e.g., via a wireless network connection) for the transaction. If the password is inconsistent with the registered password, the electronic device abandons transmitting the payment information to the remote server for the transaction, and optionally, prompts the user that the password and the registered password are inconsistent. In some embodiments, before conducting the transaction, the user is requested to provide one or more other forms of authentication (e.g., biometric authentication using a fingerprint sensor on the device or on a companion device) after activating the hardware button.

[0242] In some embodiments, such as Figure 7NAs shown in , electronic device 500A displays an indication of conducting a transaction, providing a payment indication, or transmitting payment information. In some embodiments, in response to conducting a transaction, electronic device 500A displays a user interface including a transaction amount (e.g., 716A) and an indication of successful transaction (e.g., check mark 716B).

[0243] Figure 8 800 is a flow chart illustrating a method for managing transactions using an electronic device according to some embodiments. Method 800 is performed at a device (e.g., 100, 300, 500, 500A) having a display, one or more input devices, and hardware buttons. Some operations in method 800 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

[0244] As described below, method 800 provides an intuitive way to manage transactions. The method reduces the cognitive burden on users to manage transactions, thereby creating a more efficient human-computer interface. For battery-operated computing devices, users are enabled to participate in transactions more efficiently, such as by reducing the number of inputs required from the user at the device, saving power and increasing the time interval between battery charges.

[0245] At box 802, the electronic device displays an application user interface (e.g., 702) for a corresponding application (e.g., a third-party application) on a display, wherein the application user interface (e.g., 702) includes a transaction enablement representation (e.g., 702A) for requesting payment for an activity associated with the corresponding application.

[0246] According to some embodiments, the transaction enabling representation (e.g., 702A) for the corresponding application displayed in the application user interface (e.g., 702) is provided by a payment application of an electronic device (e.g., 500A) that is different from the corresponding application. In some embodiments, the payment application is a first-party application provided by the manufacturer of the electronic device. In some embodiments, the payment application is an electronic wallet application that can access personal information of the electronic device user, which cannot be accessed by the corresponding application. In some embodiments, the information is payment information (e.g., account number or payment account number) of a payment account (e.g., a credit account) of the electronic wallet application. In some embodiments, the electronic wallet application has access to information for multiple payment accounts associated with the user of the electronic device 500A.

[0247] According to some embodiments, a transaction enable indication (e.g., 702A) is provided by the corresponding application, and when activated, the transaction enable indication triggers the display of a transaction user interface (e.g., 706). According to some embodiments, the corresponding application is a third-party application. In some embodiments, before displaying the application user interface for the corresponding application, the electronic device receives a request provided by the user to download and install the corresponding application. In some embodiments, before displaying the application user interface for the corresponding application, the electronic device receives a request provided by the user to download and install the corresponding application. In some embodiments, the electronic device is configured to allow the corresponding application to be uninstalled or deleted from the electronic device based on a user request. According to some embodiments, the activities associated with the corresponding application include one or more of the following: transportation requests, carpooling requests, purchase of services, purchase of products, and conducting peer-to-peer transactions.

[0248] At block 804, the electronic device detects selection of a transaction-enabled representation via one or more input devices while displaying the application user interface (e.g., 702). In some embodiments, detecting selection of a transaction-enabled representation (e.g., 702A) includes detecting a tap input at a location on the touch-sensitive surface corresponding to the transaction-enabled representation (e.g., 702A).

[0249] At block 806, in response to detecting selection of a transaction affordance (e.g., 702A), the electronic device displays a transaction user interface (e.g., 706) (e.g., replacing display of application user interface 702 with transaction user interface 706), the transaction user interface including, at block 808, concurrently displaying transaction details for an activity associated with the respective application (e.g., payment account 706B, payee 706C for payment, name of the respective application, tax amount, indication 706D that the cost of the activity is variable), and, at block 810, an instruction (e.g., 706A) to activate a hardware button of the device to authorize payment for the activity associated with the respective application. Thus, the electronic device indicates to the user that the state of the electronic device has changed by providing a visual indication to the user (e.g., via instruction 706A) that the state of the electronic device has changed to a state in which the transaction (of which transaction details 706B-706D are already displayed) can be authorized by activating a hardware button. In some embodiments, the instruction (e.g., 706A) is displayed at a location on the display to activate the hardware button. In some embodiments, the location on the display corresponds to (e.g., is adjacent to) a hardware button of the electronic device.

[0250] According to some embodiments, displaying a transaction user interface (e.g., 706) also includes displaying a graphical representation of a payment account (e.g., 706E), which will be used to pay if authorization to make a payment transaction is received. In some embodiments, the payment account is a default payment account. In some embodiments, the payment account is a payment account selected by the user for payment for the activity. In some embodiments, the graphical representation of the payment account includes a physical payment card associated with the payment account. In some embodiments, in response to receiving input corresponding to an instruction to scroll the transaction user interface (e.g., 706), the electronic device scrolls the transaction user interface (e.g., 706) on the display to display a graphical representation of the payment account. In some embodiments, the electronic wallet application of the electronic device stores the payment account (and optionally, one or more additional payment accounts). The payment account (and optionally, one or more additional payment accounts) is an account of the electronic device user.

[0251] According to some embodiments, the transaction details include information about the cost of the activity (e.g., 706B). In some embodiments, the transaction details include the total cost of the activity. In some embodiments, the transaction details include the shipping cost of the activity. According to some embodiments, based on determining that the activity has a variable cost, the transaction details include an indication that the activity has a variable cost (e.g., 706D). Thus, the electronic device notifies the user that the cost has not been finalized by providing (via indication 706D) a visual indication that the detected transaction has a variable cost, and the user is able to perform a scrolling operation (e.g., such as Fig. 7E Scroll down to view the pre-charged or pre-authorized amount (e.g. Figure 7F In some embodiments, in response to receiving input corresponding to an instruction to scroll the transaction user interface (e.g., 706), the electronic device scrolls the transaction user interface (e.g., 706) on the display to display the total cost to be paid. In some embodiments, in response to receiving input corresponding to an instruction to scroll the transaction user interface (e.g., 706), the electronic device scrolls the transaction user interface (e.g., 706) on the display to display the pre-authorization amount (or pre-charged amount).

[0252] According to some embodiments, while displaying a transaction user interface (e.g., 706) that includes transaction details (e.g., 708A, 708B, contact information, shipping address, taxes, total cost) and instructions to activate a hardware button (e.g., 706A), the electronic device receives input corresponding to instructions to scroll the transaction user interface (e.g., 706) (e.g., a user's request to the electronic device 500A) via one or more input devices, and in response to receiving input corresponding to instructions to scroll the transaction user interface (e.g., 706), the electronic device displays additional transaction details (e.g., 708A, 708B, contact information, shipping address, taxes, total cost) for an activity associated with the corresponding application.

[0253] According to some embodiments, instructions (e.g., 706A) to activate a hardware button are displayed on the display at a position determined based on the position of the hardware button (e.g., adjacent to the hardware button). In some embodiments, instructions (e.g., 706A) are displayed on the display at a first position based on determining that the hardware button is at the first position, and instructions (e.g., 706A) are displayed on the display at a second position different from the first position based on determining that the hardware button is at the second position. Therefore, by arranging instructions (e.g., 706A) adjacent to the hardware button that should be activated to authorize the transaction, the user is notified that there is an appropriate hardware button (e.g., from multiple buttons) to authorize the transaction, and the user is able to avoid irrelevant (or erroneous) button presses, such as button presses on incorrect buttons that cause the electronic device to transition to a state where activating the hardware button (even if it is the correct hardware button) will not authorize the transaction. According to some embodiments, displaying additional transaction details for an activity associated with a corresponding application includes abandoning the scrolling instructions to activate the hardware button to activate the hardware button, and scrolling additional transaction details (e.g., 708A, 708B) onto the display. In some embodiments, the instructions to activate the hardware button are displayed at a position on the display while the additional transaction details are scrolled onto the display. In some embodiments, when the additional transaction details are scrolled onto the display, the instruction to activate the hardware button (e.g., 706A) fades out on the display. By fading out rather than scrolling the instruction (e.g., 706A), the electronic device avoids misaligning the instruction (e.g., 706A) with the corresponding hardware button, so that the user can avoid irrelevant button presses, such as button presses on incorrect buttons that cause the electronic device to transition to a state where activating the hardware button (even if it is the correct hardware button) will not authorize the transaction. In some embodiments, when the electronic device scrolls the transaction user interface (e.g., 706) to reveal the additional transaction details, the electronic device fades out the instruction to activate the hardware button (e.g., 706A). Therefore, the electronic device does not change the position of the displayed instruction to activate the hardware button (e.g., 706A) because the position of the instruction to activate the hardware button is tied to the position of the physical hardware button. According to some embodiments, displaying the additional transaction details of the activity associated with the corresponding application includes: scrolling the additional transaction details (e.g., 708A, 708B) onto the display so that the additional transaction details cover the instruction to activate the hardware button.

[0254] According to some embodiments, when displaying additional transaction details (e.g., 708A, 708B), the electronic device detects a selection of a first detail (e.g., 708B) of the additional transaction details (e.g., 708A, 708B) via one or more input devices, and in response to detecting the selection of the first detail (e.g., 708B) in the additional transaction details (e.g., 708B) (e.g., detecting activation of an enable indication corresponding thereto), the electronic device displays one or more options (e.g., 710A, 710B, 710C) for the first detail. In some embodiments, displaying one or more options includes replacing the display of the additional transaction details (e.g., 708A, 708B) with the display of one or more options (e.g., 710A, 710B, 710C).

[0255] According to some embodiments, in response to displaying a transaction user interface, the electronic device monitors the activation of the hardware button, detects the activation of the hardware button, and in response to detecting the activation of the hardware button, in response to determining that the activation of the hardware button meets the transaction authorization criteria, conducts the transaction for the activity. In some embodiments, in response to detecting the activation of the hardware button, in response to determining that the activation of the hardware button does not meet the transaction authorization criteria, the electronic device abandons authorization of the transaction and optionally displays a different user interface corresponding to the activation of the hardware button.

[0256] According to some embodiments, the electronic device detects activation of the hardware button, and in response to detecting activation of the hardware button, based on determining that transaction processing criteria have been met (including criteria that transaction parameters are correct (and optionally, that activation of the hardware button meets transaction authorization criteria)), conducts the transaction for the activity, and based on determining that there is an error in the transaction parameters, displays an error notification (e.g., 708C) on the display indicating that an error has been detected instead of conducting the transaction. Thus, the electronic device provides a visual indication (e.g., 708C) that an error condition (e.g., an error in the transaction parameters) has been automatically detected, thereby prompting the user to provide input to correct the error. In some embodiments, using reference Figure 9A-9N The described techniques and methods 1000 resolve transaction errors. In some embodiments, activation of a hardware button is detected while the device is in an unlocked state (and optionally, while the device has been continuously on the user's wrist since the device was unlocked by providing authentication credentials to the device, wherein the continued presence of the device on the user's wrist is determined by periodically checking that the device is in contact with the user's skin).

[0257] According to some embodiments, based on determining that a transaction parameter is incorrect, the electronic device receives user input at the electronic device via one or more input devices (e.g., receiving audio via a personal assistant, detecting activation of an affordance corresponding to alternating contact 710B), and in response to receiving the user input at the electronic device, modifies the transaction parameter based on the user input. Thus, the electronic device reduces the need for the user to perform complex navigation of the user interface to correct the error condition (e.g., the transaction parameter is incorrect) by providing the user with the ability to input to correct the error condition. In some embodiments, once the error in the transaction parameter is corrected, the electronic device conducts the transaction in response to detecting the input to authorize the transaction.

[0258] According to some embodiments, based on determining that a transaction parameter is incorrect, the electronic device receives a request to correct the error, and in response to receiving the request to correct the error, based on determining that there are potentially compatible transaction parameters on the electronic device, displays one or more potentially compatible transaction parameters (e.g., 710A, 710B), and based on determining that there are no potentially compatible transaction parameters on the electronic device, displays instructions for entering additional transaction parameters on a companion device different from the electronic device. In some embodiments, potentially compatible transaction parameters (e.g., 710A, 710B) are displayed along with a selectable option (e.g., 710C) to enter additional transaction parameters on a companion device different from the electronic device (e.g., option 710C, when selected, initiates a process for entering additional transaction parameters on the companion device). Therefore, the electronic device prompts the user to provide input to correct the error by providing the user with a visual indication (e.g., 708C) that an error condition has been automatically detected (e.g., transaction parameters are incorrect, no).

[0259] According to some embodiments, displaying an error notification (e.g., 708C) on the display indicating that an error has been detected includes replacing the display of the instruction to activate the hardware button (e.g., 706A) with the display of the error notification (e.g., 708C). Thus, the electronic device prompts the user to provide input to correct the error by providing the user with a visual indication (e.g., 708C) that an error condition (e.g., a transaction parameter has an error) that has been automatically detected, and indicates to the user that in the current state, the hardware button cannot be used to authorize the transaction due to an error. In some embodiments, using reference Figure 9A-9N The described techniques and methods 1000 resolve errors in transactions. In some embodiments, displaying an error notification (eg, 708C) includes changing the display of transaction details (eg, changing the color of the payment amount of the payment transaction).

[0260] According to some embodiments, the electronic device receives user input (e.g., a swipe gesture, such as a left swipe gesture or a right swipe gesture at a location on the touch-sensitive surface corresponding to the graphical representation 906E of the payment account) via one or more input devices, the user input corresponding to an instruction to select a payment account from a plurality of payment accounts in an electronic wallet of the electronic device, and in response to detecting the user input corresponding to the instruction to select a payment account from a plurality of payment accounts, selects a payment account for use in an active transaction. In some embodiments, switching payment accounts includes switching between a plurality of payment accounts associated with different payment cards, and switching between payment accounts includes selecting different representations of the payment card. In some embodiments, switching payment accounts includes switching between a plurality of payment accounts associated with the same payment card (e.g., a checking account, a deposit account, and a credit account associated with the same payment card), and displaying an affordance for selecting an account associated with the payment card. In some embodiments, when switching from a payment account of a first payment card associated with a single account to a payment account for a second payment card associated with multiple accounts, the device displays an animation of an enabling representation for selecting between multiple accounts associated with the second payment card, and when switching from the payment account associated with the first payment card to the payment account associated with the second payment card, the device displays an animation of an enabling representation for selecting between multiple accounts associated with the second payment card, which disappears.

[0261] According to some embodiments, displaying the transaction user interface includes replacing the displayed system user interface elements (e.g., time indicator 704A, date indicator) with a payment indication (e.g., 704B). Therefore, by replacing the system user interface elements (e.g., time indicator 704A, date indicator) when displaying the transaction user interface, the electronic device notifies the user that the transaction is being processed by a trusted application (e.g., a first-party application, a system-level application, an operating system of the electronic device), and thus the user avoids providing additional input to the electronic device to confirm that the transaction is being processed by the trusted application. In some embodiments, the corresponding application does not have the ability to replace the system user interface elements (e.g., time indicator 704A, date indicator).

[0262] According to some embodiments, conducting a transaction for an activity includes, after detecting activation of a hardware button, and optionally, when the electronic device is in an unlocked state, and optionally, when the device is on the user's wrist, such as by detecting that the device contacts the user's skin, (e.g., by displaying a request 714 on a display), requesting a password, detecting the password via one or more input devices, and sending the password (e.g., together with payment information) (e.g., to a remote server or to a payment processing service) for processing the transaction. In some embodiments, the user authenticates locally (e.g., at the electronic device) by activating the hardware button (e.g., via a double press), and the user authenticates to the remote server (e.g., a payment processing service) via the password. In some embodiments, the password is verified locally at the electronic device. If the password is consistent with the registered password, the electronic device sends the payment information to the remote server for the transaction. If the password is inconsistent with the registered password, the electronic device abandons transmitting the payment information to the remote server for the transaction, and optionally, prompts the user that the password and the registered password are inconsistent. In some embodiments, before conducting the transaction, the user is requested to provide one or more other forms of authentication (e.g., biometric authentication using a fingerprint sensor) after activating the hardware button.

[0263] It should be noted that the process described above with respect to method 800 (eg Figure 8 ) also applies in a similar manner to the methods described below. For example, method 1000 optionally includes one or more features of the various methods described above with reference to method 800. For example, in some embodiments, reference Figure 7A-Figure 7O and Figure 8 The transaction user interface 706 described is similar to that of reference Figure 9A-9N and Fig.10 The transaction user interface 906. For the sake of brevity, these details are not repeated below.

[0264] Figure 9A-9N An exemplary user interface for transactions according to some embodiments is shown. The user interface in these figures is used to illustrate the process described below, including Fig.10 process.

[0265] In some embodiments, electronic device 500B includes a display, one or more input devices, and optional hardware buttons (e.g., mechanical buttons configured to enable the secure payment module to provide payment information for use in a payment transaction). In some embodiments, electronic device 500B is a smartwatch electronic device. In some embodiments, device 500B includes some or all of the features of device 100, device 300, device 500, or device 500B.

[0266] In some embodiments, such as Fig.9AAs shown in , the electronic device 500B displays a transaction user interface (e.g., 906), which includes simultaneously displaying: transaction details of the activity associated with the corresponding application (e.g., payment amount 906B, payee 906C of the payment, name of the corresponding application, tax amount), and an instruction to activate the hardware button of the device to authorize payment for the activity transaction associated with the corresponding application (e.g., 906A). In some embodiments, the electronic device 500B also displays a graphical representation of a payment account (e.g., 906E), and if authorization to conduct a payment transaction is received (e.g., via a double press of the hardware button by the user), the payment will be made using the payment account (e.g., by the electronic device 500B).

[0267] like Fig.9A As shown, electronic device 500B receives (e.g., from a user, based on user input) a request to conduct a transaction (e.g., activation of a hardware button and, optionally, a passcode or fingerprint authentication) using transaction parameters (e.g., a phone number, an email address, a billing address, and / or a shipping address), e.g., as described above with reference to Figure 7A-Figure 7O and Figure 8 The method 800 is as described above.

[0268] In some embodiments, such as Fig. 9B As shown in , in response to the request to conduct a transaction, based on determining that transaction processing criteria have been met (including criteria that transaction parameters are correct), electronic device 500B conducts the transaction (e.g., assuming there are no other obstacles to conducting the transaction). In some embodiments, conducting the transaction includes transmitting payment information to a remote server or payment processing server. In some embodiments, such as Fig. 9B As shown in , electronic device 500B displays an indication of conducting a transaction, a payment indication has been provided, or an indication of payment information has been transmitted. In some embodiments, in response to conducting a transaction, electronic device 500B displays a user interface, which includes a transaction amount (e.g., 906F) and an indication of successful transaction (e.g., check mark 906G).

[0269] In some embodiments, conducting the transaction is further dependent upon determining whether the request to conduct the transaction meets transaction authorization criteria (e.g., a double press input, where the press inputs are received within a predetermined time threshold of each other, and optionally, the contact on the button meets user authentication criteria, such as matching a fingerprint in a fingerprint database or having been unlocked and remaining on the user's wrist since being unlocked), if the request to conduct the transaction does not meet the transaction authorization criteria, the device does not conduct (e.g., abandons conducting) the transaction, and if the request to conduct the transaction meets the transaction authorization criteria, the device conducts the transaction.

[0270] like Fig. 9CAs shown, in response to a request to conduct a transaction, upon determining that the transaction parameters are erroneous (e.g., thereby failing to meet transaction processing standards that require the transaction parameters to be correct), the electronic device displays an error notification (e.g., 908) indicating that an error has been detected. Therefore, the electronic device 500B notifies the user that an error has occurred.

[0271] like Fig.9D As shown, electronic device 500B receives a request to correct an error (eg, detects activation of error notification 908) via one or more input devices.

[0272] like Fig.9E As shown in , in response to receiving a request to correct an error, based on determining that there are potentially compatible transaction parameters on the electronic device (e.g., in a memory of the electronic device, in a contact phone book of the electronic device), the electronic device 500B displays one or more of the potentially compatible transaction parameters on the display (e.g., 910A, 910B).

[0273] In some embodiments, such as Fig.9E As shown, if there are potentially compatible transaction parameters, the electronic device selects the transaction parameters as default transaction parameters. In response to receiving a request to correct an error, based on determining that there are potentially compatible transaction parameters on the electronic device (e.g., in the memory of the electronic device, in the contact phone book of the electronic device), the electronic device 500B updates the transaction parameters to include default transaction parameters of potentially compatible transaction parameters for use in the transaction. In some embodiments, the electronic device displays an indication (such as a check mark) next to the selected default transaction parameters to indicate to the user that the default transaction parameters have been selected. In some embodiments, the electronic device displays one or more affordances (e.g., 910A, 910B) corresponding to one or more corresponding potentially compatible transaction parameters on the display. In some embodiments, the user can activate one of the one or more affordances corresponding to one or more corresponding potentially compatible transaction parameters to cause the electronic device to update the transaction parameters. For example, the electronic device receives activation of an affordance corresponding to a home address and updates the transaction parameters to include the home address for billing purposes.

[0274] like Fig.9FAs shown in , based on determining that there are no potentially compatible transaction parameters on electronic device 500B, electronic device 500B displays on the display an instruction (e.g., 912) to enter additional transaction parameters on a companion device (e.g., 300) different from electronic device 500B. Therefore, by providing a visual indication (e.g., 912) to the user of an automatic detection error condition (e.g., no potentially compatible transaction parameters on electronic device 500B), the electronic device prompts the user to provide input at a separate companion device to correct the error. In some embodiments, the companion device is a smart phone. In some embodiments, the companion device is a laptop.

[0275] In some embodiments, the electronic device 500B transmits a request for a transaction parameter input user interface to the companion device 300. Figure 9G As shown in , in some embodiments, the companion device 300 displays an indication (e.g., 920, 924) regarding a request for transaction parameter input into a user interface.

[0276] In some embodiments, the indication of activating a request for a transaction parameter input user interface enables the user to quickly enter the transaction parameters. Thus, by providing a mechanism for the user to enter transaction parameters, the electronic device reduces the amount of user input required to access the mechanism. Figure 9G As shown, an indication (e.g., 924) of a request for a transaction parameter input user interface is activated on the companion device 300 (e.g., by a user), causing the companion device to display the transaction parameter input user interface (e.g., 922) on the display of the companion device. Thus, the electronic device prompts the user to provide input to correct the error by providing the user with a visual indication (e.g., 924) that an error condition is automatically detected (e.g., an error in the transaction parameter is detected at the electronic device 500B). In some embodiments, the transaction parameter input user interface is a user interface of a configuration application corresponding to the electronic device on the companion device. In some embodiments, the configuration application is used by a user on the companion device to configure the electronic device. In some embodiments, the companion device receives input of the transaction parameters (e.g., using a virtual keyboard displayed on the display of the companion device). In response to receiving the transaction parameters, the companion device transmits the transaction parameters to the electronic device. Thus, the user can use the companion device (in some embodiments, the companion device is larger and has a more convenient user interface for receiving user input) to input information required (or helpful) at the electronic device 500B (e.g., additional transaction parameters).

[0277] In some embodiments, the user enters information using a transaction parameter input user interface (e.g., 922) of the companion device, and then sends the information to the electronic device 500B. In some embodiments, the electronic device 500B receives the corresponding additional transaction parameters (e.g., from the companion device). In some embodiments, the transaction parameters entered (or selected, or otherwise provided) by the user at the companion device are transmitted to the electronic device (e.g., by the companion device) for use in the transaction.

[0278] In some embodiments, such as Fig.9I As shown, in response to receiving the corresponding additional transaction parameters, the electronic device 500B updates the transaction user interface (e.g., 906) on the display according to the corresponding additional transaction parameters (e.g., based on the corresponding additional transaction parameters). Therefore, the electronic device indicates to the user by updating the transaction user interface (e.g., 906) that the electronic device has received an update to the transaction parameters, and optionally, also indicates that the electronic device has transitioned to a state where the hardware button is activated to authorize the transaction. In some embodiments, in response to receiving the transaction parameters, the electronic device 500B updates the display. In some embodiments, in response to receiving the transaction parameters, the electronic device 500B updates the display to stop displaying the error notification (e.g., 908). In some embodiments, in response to receiving the transaction parameters, the electronic device 500B displays the transaction parameters.

[0279] In some embodiments, in response to instructions in the transaction user interface on the electronic device 500B (e.g., 912), the user causes the companion device 300 to open the companion application on the companion device 300 (e.g., 926), and automatically presents the transaction parameter input user interface (e.g., 922) to the user. Thus, by providing the user with a visual indication (e.g., 912) of an automatically detected error condition (e.g., the transaction parameters are incorrect, there are no potentially compatible transaction parameters on the electronic device 500B), the electronic device prompts the user to provide input on the companion device (e.g., 300) to correct the error.

[0280] In some embodiments, in response to receiving a request for a transaction parameter input user interface from the electronic device 500B, the companion device 300 automatically launches the transaction parameter input user interface (e.g., 922) on the companion device 300. Therefore, the companion device (e.g., 300) prompts the user to provide input to correct the error by providing a visual indication (e.g., transaction parameter input user interface 922) of the automatically detected error condition (e.g., the transaction parameter is incorrect, there are no potentially compatible transaction parameters on the electronic device 500B) to the user without the user providing input to launch the transaction parameter input user interface (e.g., 922).

[0281] In some embodiments, such as Figure 9J-Figure 9NAs shown in , companion device 300 displays an indication (e.g., 920) that the user can activate to access the companion application on companion device 300. Thus, the companion device prompts the user to provide input to correct the error and reduces the user input required to correct the error by providing the user with a visual indication (e.g., 708C) that an error condition (e.g., transaction parameters are incorrect) is automatically detected. For example, the companion application is configured to send information to electronic device 500B.

[0282] like Figure 9J As shown, companion device 300 receives (e.g., from a user) a request to open a companion application (e.g., 926). In some embodiments, receiving the request includes detecting activation of an affordance (e.g., 920), such as an affordance displayed on a lock screen or an affordance displayed on a home screen of companion device 300.

[0283] like Figure 9K As shown, the user activates an affordance (e.g., 920) on the companion device 300 corresponding to the companion application. Figure 9K As shown, companion device 300 displays companion application 926, including various settings for electronic device 500B. In some embodiments, companion device 300 detects activation of affordance 926A for accessing electronic wallet settings of electronic device 500B. In response to detecting activation of affordance 926A for accessing electronic wallet settings of electronic device 500B, companion device 300 displays one or more options 928A-928D, including an option (e.g., 928C) to access a transaction parameter input user interface (e.g., 922) on companion device 300, such as Figure 9L As shown in Figure 9M As shown, in response to detecting activation of an option for accessing a transaction parameter input user interface (e.g., 928C), the companion device 300 displays a transaction parameter input user interface (e.g., 922). In some embodiments, the transaction parameter input user interface (e.g., 922) is used by a user on the companion device 300 to configure an electronic device. In some embodiments, the companion device 300 receives input of transaction parameters at the transaction parameter user interface (e.g., using a virtual keyboard displayed on a display of the companion device). In response to receiving the transaction parameters, the companion device 300 transmits the transaction parameters to the electronic device 500B. Thus, the user can use the companion device 300 (in some embodiments, the companion device is larger and has a more convenient user interface for receiving user input) to input information required (or helpful) at the electronic device 500B (e.g., additional transaction parameters).

[0284] In some embodiments, in response to receiving the transaction parameters (e.g., from a companion device), the electronic device 500B updates the transaction parameters to include the corresponding additional transaction parameters for use in the transaction. Thus, for example, the technique reduces the number of inputs required on the electronic device to update the transaction parameters. For example, if the companion device transmits a mailing address to the electronic device, the electronic device will update the transaction parameters to use the corresponding additional transaction parameters. Thus, the corresponding additional transaction parameters are automatically selected for use in a transaction (e.g., a transaction during which a request for a transaction parameter input user interface is transmitted by the electronic device).

[0285] In some embodiments, in response to receiving the corresponding additional transaction parameters (e.g., from a companion device), the electronic device 500B displays an indication of the corresponding additional transaction parameters on a display. Thus, by providing the user with a visual indication (via the indication of the corresponding additional transaction parameters) that the electronic device has automatically detected the corresponding additional transaction parameters, the electronic device indicates to the user that the corresponding additional transaction parameters have been received, and optionally, that the electronic device has become a state in which the transaction can be authorized by activating a hardware button. While displaying the indication of the corresponding additional transaction parameters, the electronic device 500B detects activation of a hardware button of the electronic device (e.g., detects a double press of the hardware button). Based on determining that the updated transaction parameters including the corresponding additional transaction parameters are error-free, the electronic device 500B conducts a transaction (e.g., makes a payment, transmits payment information) for the activity (e.g., using a payment account of an electronic wallet of the electronic device). Based on determining that the updated transaction parameters are erroneous, the electronic device 500B displays a second error notification on the display indicating that an error has been detected (and abandons conducting the transaction for the activity). In some embodiments, if the updated transaction parameters are erroneous, the device repeats the above from Fig.9A or Fig. 9C In some embodiments, activating the hardware button causes the device to conduct the transaction from any portion of the transaction user interface (e.g., even when the user has navigated through one or more menus to change transaction parameters or enter new transaction parameters for the transaction), thereby eliminating the need to display "click to pay" instructions in response to a request to conduct a transaction that meets the transaction processing criteria for the device to conduct the transaction. Thus, the electronic device reduces the amount of user input required to authorize a transaction by not requiring the user to navigate the user interface to a specific display before authorizing the transaction using the hardware button.

[0286] In some embodiments, such as Fig.9IAs shown, in response to receiving the corresponding additional transaction parameters (e.g., from a companion device), the electronic device 500B displays on the display an instruction to activate the hardware button of the electronic device to authorize payment for the transaction (e.g., 906A). Therefore, by providing a visual indication to the user that the electronic device has received the corresponding additional transaction parameters (via instruction 906A), the electronic device indicates to the user that the corresponding additional transaction parameters have been received, and optionally, the electronic device has become a state in which the transaction can be authorized by activating the hardware button. In some embodiments, when displaying the instruction to activate the hardware button of the electronic device to authorize payment for the transaction (e.g., 906A), the electronic device 500B abandons displaying the corresponding additional transaction parameters. In some embodiments, the electronic device 500B detects activation of the hardware button (e.g., detects a double press of the hardware button). In response to detecting activation of a hardware button (e.g., when the electronic device is in an unlocked state, and optionally, when the device is on the user's wrist, such as by detecting that the device is in contact with the user's skin), based on determining that transaction processing standards have been met (including standards that updated transaction parameters are correct), the electronic device 500B conducts a transaction (e.g., makes a payment, transmits payment information) for the activity (e.g., using a payment account of an electronic wallet of the electronic device). In some embodiments, in response to detecting activation of a hardware button (e.g., when the electronic device is in an unlocked state, and optionally, when the device is on the user's wrist, such as by detecting that the device is in contact with the user's skin), based on determining that transaction parameters are incorrect (e.g., thereby not meeting transaction processing standards that transaction parameters are correct), the electronic device 500B displays an error notification (e.g., 708C) on the display, indicating that an error has been detected (and the transaction for the activity is abandoned).

[0287] In some embodiments, in response to a request to conduct a transaction, based on determining that a transaction parameter is in error, the electronic device 500B updates the display characteristics (e.g., position, size, color) of the displayed user interface element (e.g., price 906B) to indicate that an error has been detected. Thus, the electronic device prompts the user to provide input to correct the error by providing the user with a visual indication (e.g., by updating the displayed characteristics) that an error condition (e.g., a transaction parameter is in error) is automatically detected. In some embodiments, when the electronic device determines that a transaction parameter is in error, the price to be paid (e.g., 906B) changes color from blue to red. For example, this indicates to the user that a transaction parameter is in error.

[0288] In some embodiments, in response to receiving a request to correct an error, based on determining that there are potentially compatible transaction parameters on the electronic device (e.g., in the memory of the electronic device, in the contact phone book of the electronic device), the electronic device 500B displays an input enable indication (e.g., 910C) on the display, which, when activated, enables the user to enter the transaction at the electronic device (e.g., via dictation, via user selection from a contact phone application, via a companion device, as described above with reference to Figure 9A-9F and Fig.10 ) provides transaction parameters not included in the potentially compatible transaction parameters.

[0289] In some embodiments, electronic device 500B detects activation of an input enable indication (e.g., 910C). In response to detecting activation of an input enable indication (e.g., 910C), electronic device 500B monitors audio input received via a microphone of electronic device 500B. Electronic device 500B updates transaction parameters based on audio input received via a microphone of the electronic device. For example, electronic device 500B processes audio input to detect words and / or phrases, and transcribes the words and / or phrases for use as transaction parameters, or optionally interprets the words and / or phrases as verbal instructions for retrieving stored data, such as an email address, phone number, physical address used as a transaction parameter.

[0290] In some embodiments, electronic device 500B detects activation of an input enable indication (e.g., 910C). In response to detecting activation of the input enable indication (e.g., 910C), electronic device 500B displays one or more contacts (e.g., addresses, phone numbers) based on contacts stored in a contact application (e.g., addresses, phone numbers). Electronic device 500B receives (e.g., from a user) a selection of a contact from one or more contacts. Electronic device 500B updates transaction parameters based on the selected contact.

[0291] In some embodiments, the electronic device 500B detects activation of an input enable indication (e.g., 910C). In response to detecting the activation of the input enable indication, the electronic device 500B transmits a second request for a second transaction parameter input user interface to the companion device 300. In some embodiments, the companion device 300 displays a second indication of a request for a second transaction parameter input user interface. In some embodiments, the electronic device (e.g., from the companion device) receives transaction parameters (e.g., based on the transmission of the second request). In some embodiments, the transaction parameters entered (or selected, or otherwise provided) by the user at the companion device are transmitted to the electronic device (e.g., by the companion device) for use in the transaction. In some embodiments, in response to receiving the transaction, the electronic device updates the transaction parameters based on the corresponding additional transaction parameters.

[0292] Fig.10 1 is a flow chart illustrating a method for managing transactions using an electronic device according to some embodiments. Method 1000 is performed at a device (e.g., 100, 300, 500, 500B) having a display, one or more input devices, and optional hardware buttons and a microphone. Some operations in method 1000 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

[0293] As described below, method 1000 provides an intuitive way to manage transactions. The method reduces the cognitive burden on users to manage transactions, thereby creating a more efficient human-computer interface. For battery-operated computing devices, users are enabled to participate in transactions more efficiently, such as by reducing the number of inputs required from the user at the device or allowing the user to provide input at different devices, saving power and increasing the time interval between battery charges.

[0294] At block 1002, the electronic device receives a request to conduct a transaction using transaction parameters.

[0295] At box 1004, in response to the request to conduct the transaction, based on determining that the transaction parameters are incorrect, the electronic device displays an error notification (e.g., 908) indicating that an error has been detected. According to some embodiments, in response to the request to conduct the transaction, based on determining that the transaction processing standards (including the standards that the transaction parameters are correct) have been met, the electronic device conducts the transaction. In some embodiments, conducting the transaction includes transmitting payment information to a remote server or a payment processing server. In some embodiments, conducting the transaction further depends on determining whether the request to conduct the transaction meets the transaction authorization standards; if the request to conduct the transaction does not meet the transaction authorization standards, the device will not conduct the transaction, and if the request to conduct the transaction meets the transaction authorization standards, the device conducts the transaction. According to some embodiments, in response to the request to conduct the transaction, based on determining that the transaction parameters are incorrect, the electronic device updates the displayed characteristics (e.g., position, size, color) of the displayed user interface element (e.g., 906B) to indicate that an error has been detected. In some embodiments, when the electronic device determines that the transaction parameters are incorrect, the price to be paid (e.g., 906B) changes color from blue to red, thereby indicating to the user that the transaction parameters are incorrect.

[0296] At block 1006 , the electronic device receives a request to correct an error (eg, activation of error notification 908 ) via one or more input devices.

[0297] At box 1008, in response to receiving a request to correct the error, based on determining that there are potentially compatible transaction parameters on the electronic device, at box 1010, the electronic device displays one or more potentially compatible transaction parameters (e.g., 910A, 910B) on the display, and based on determining that there are no potentially compatible transaction parameters on the device, at box 1012, the electronic device displays on the display an instruction (e.g., 912) to enter additional transaction parameters on a companion device (e.g., 300) that is different from the electronic device.

[0298] According to some embodiments, in response to receiving a request to correct an error, based on determining that there are potentially compatible transaction parameters on the electronic device, the electronic device updates the transaction parameters to include default transaction parameters of the potentially compatible transaction parameters for use in the transaction, and the electronic device displays one or more enabling representations (e.g., 910A, 910B) corresponding to one or more corresponding potentially compatible transaction parameters on a display. In some embodiments, the electronic device displays an indication (e.g., a check mark) next to the selected default transaction parameters to indicate to the user that the default transaction parameters have been selected. In some embodiments, the user can activate one of the one or more enabling representations corresponding to one or more corresponding potentially compatible transaction parameters to cause the electronic device to update the transaction parameters. For example, the electronic device receives activation of an enabling representation corresponding to a home address and updates the transaction parameters to include a home address for billing purposes. According to some embodiments, in response to receiving a request to correct an error, based on determining that there are potentially compatible transaction parameters on the electronic device, the electronic device displays an input enabling representation on a display that, when activated, enables the user to provide a transaction parameter not included in the potentially compatible transaction parameters at the electronic device.

[0299] According to some embodiments, the electronic device detects activation of an input enable indication, monitors audio input received via a microphone of the electronic device in response to detecting activation of the input enable indication, and updates transaction parameters based on the audio input received via the microphone of the electronic device. According to some embodiments, the electronic device detects activation of an input enable indication, displays one or more contacts (e.g., addresses, phone numbers) based on contacts stored in a contact application (e.g., addresses, phone numbers) in response to detecting activation of the input enable indication, receives contact selections of one or more contacts, and updates transaction parameters based on the selected contacts. According to some embodiments, the electronic device detects activation of an input enable indication, and transmits a second request for a second transaction parameter input user interface to a companion device in response to detecting activation of the input enable indication, and the companion device displays a second indication of a request for a second transaction parameter input user interface. In some embodiments, the electronic device receives transaction parameters (e.g., from a companion device). In some embodiments, transaction parameters entered (or selected, or otherwise provided) by a user at the companion device are transmitted to the electronic device (e.g., by the companion device) for use in a transaction. In some embodiments, in response to receiving a transaction, the electronic device updates the transaction parameters based on the corresponding additional transaction parameters.

[0300] According to some embodiments, the electronic device transmits a request for a transaction parameter input user interface to the matching device, and the matching device displays an indication of the request for the transaction parameter input user interface (e.g., 920). According to some embodiments, the indication of the request for the transaction parameter input user interface (e.g., 920) is activated on the matching device, so that the transaction parameter input user interface (e.g., 922) is displayed on the display of the matching device. In some embodiments, the transaction parameter input user interface is a user interface of a configuration application corresponding to the electronic device on the matching device. In some embodiments, the configuration application is used by a user on the matching device to configure the electronic device. In some embodiments, the matching device receives input of transaction parameters (e.g., using a virtual keyboard displayed on the display of the matching device). In response to receiving the transaction parameters, the matching device transmits the transaction parameters to the electronic device. According to some embodiments, in response to receiving the transaction parameters (e.g., from the matching device), the electronic device updates the transaction parameters to include corresponding additional transaction parameters for use in the transaction.

[0301] According to some embodiments, the electronic device receives (e.g., from a companion device) corresponding additional transaction parameters, and in response to receiving the corresponding additional transaction parameters, updates the transaction user interface on the display according to the corresponding additional transaction parameters (e.g., 906). In some embodiments, the transaction parameters entered (or selected, or otherwise provided) by the user at the companion device are transmitted to the electronic device (e.g., by the companion device) for use in the transaction. In some embodiments, when entered on the companion device, the companion device provides the corresponding additional transaction parameters, even if the companion device does not initiate the transaction parameter input user interface based on information from the device. In some embodiments, in response to receiving the transaction parameters, the electronic device updates the display. In some embodiments, in response to receiving the transaction parameters, the electronic device updates the display to stop displaying error notifications (e.g., 908). In some embodiments, in response to receiving the transaction parameters, the electronic device displays the transaction parameters.

[0302] According to some embodiments, in response to receiving the corresponding additional transaction parameters (e.g., from a companion device), the electronic device displays an indication of the corresponding additional transaction parameters on a display, and while displaying the indication of the corresponding additional transaction parameters, the electronic device detects activation of a hardware button of the electronic device (e.g., detects a double press of the hardware button), and based on determining that the updated transaction parameters including the corresponding additional transaction parameters are not erroneous, the electronic device conducts a transaction for the activity, and based on determining that the updated transaction parameters are erroneous, the electronic device displays a second error notification on the display indicating that an error has been detected. In some embodiments, if the updated transaction parameters are erroneous, the device repeats the above from Fig.9A or Fig. 9C Start the process described above. In some embodiments, activating a hardware button causes the device to conduct a transaction from any portion of the transaction user interface.

[0303] According to some embodiments, in response to receiving corresponding additional transaction parameters (e.g., from a companion device), the electronic device displays on a display an instruction to activate a hardware button of the electronic device to authorize payment for the transaction (e.g., 906A), the electronic device detects activation of the hardware button (e.g., detecting a double press of the hardware button), and in response to detecting activation of the hardware button (e.g., when the electronic device is in an unlocked state, and optionally, when the device is on the user's wrist, such as by detecting that the device contacts the user's skin), based on determining that transaction processing criteria have been met (including criteria that the updated transaction parameters are correct), the electronic device conducts a transaction for the activity, and based on determining that the transaction parameters are incorrect, the electronic device displays on a display an error notification indicating that an error has been detected (e.g., 708C). In some embodiments, when displaying an instruction to activate a hardware button of the electronic device to authorize payment for the transaction (e.g., 906A), the electronic device forgoes displaying the corresponding additional transaction parameters.

[0304] Note that the above descriptions with respect to method 1000 (eg, Fig.10 ) also apply in a similar manner to the methods described above. For example, method 800 optionally includes one or more features of the various methods described above with reference to method 1000. For example, in some embodiments, reference Figure 7A-Figure 7O and Figure 8 The transaction user interface 706 described is similar to that of reference Figure 9A-9N and Fig.10 The transaction user interface 906. For the sake of brevity, these details are not repeated below.

[0305] According to some embodiments, Fig.11 An exemplary functional block diagram of an electronic device 1100 configured according to the principles of various described embodiments is shown. According to some embodiments, the functional blocks of the electronic device 1100 are configured to perform the techniques described above. The functional blocks of the device 1100 are optionally implemented by hardware, software, or a combination of hardware and software to perform the principles of various described examples. It should be understood by those skilled in the art that Fig.11 The functional blocks described in the present invention are optionally combined or separated into sub-blocks to implement the principles of various embodiments. Therefore, the description herein optionally supports any possible combination or separation or further limitation of the functional blocks described herein.

[0306] like Fig.11 As shown, the electronic device 1100 includes: a display unit 1102 configured to display a graphical user interface; one or more input device units 1104, a hardware button unit 1108; and a processing unit 1106 coupled to the display unit 1102, the one or more input device units 1104, and the hardware button unit 1108. In some embodiments, the processing unit 1106 includes a display enabling unit 1110, a detecting unit 1112, a receiving unit 1114, a performing unit 1116, a monitoring unit 1118, a modifying unit 1120, and a selecting unit 1122.

[0307] Processing unit 1106 is configured to: (e.g., using display enabling unit 1110) enable display of an application user interface for a corresponding application on display unit 1102, wherein the application user interface includes a transaction enabling indication for requesting payment for an activity associated with the corresponding application; when enabling display of the application user interface, detect selection of the transaction enabling indication via one or more input device units 1104 (e.g., using detection unit 1112); and in response to detecting selection of the transaction enabling indication, enable display of a transaction user interface on display unit 1102 (e.g., using display enabling unit 1110), wherein the transaction user interface includes simultaneously displaying: transaction details for the activity associated with the corresponding application; and instructions for activating hardware button unit 1108 of electronic device 1100 to authorize payment for the activity associated with the corresponding application.

[0308] According to some embodiments, the transaction enable representation displayed in the user interface for the corresponding application is provided by a payment application of the electronic device 1100 that is different from the corresponding application.

[0309] According to some embodiments, the transaction affordance is provided by the corresponding application, and when activated, the transaction affordance triggers display of the transaction user interface. According to some embodiments, the corresponding application is a third-party application.

[0310] According to some embodiments, the activities associated with the respective application include one or more of: requesting transportation, requesting a rideshare, purchasing a service, purchasing a product, and conducting a peer-to-peer transaction.

[0311] According to some embodiments, the transaction details include information about the cost of the activity. According to some embodiments, based on determining that the activity has a variable cost, the transaction details include an indication that the activity has a variable cost.

[0312] According to some embodiments, displaying the transaction user interface also includes displaying a graphical representation of a payment account, which will be used for payment if authorization to conduct the payment transaction is received.

[0313] According to some embodiments, the processing unit 1106 is further configured to: when displaying a transaction user interface including transaction details and instructions to activate the hardware button unit 1108, receive input corresponding to instructions to scroll the transaction user interface via one or more input device units 1104 (for example, using the receiving unit 1114); and in response to receiving input corresponding to instructions to scroll the transaction user interface: enable additional transaction details for activities associated with the corresponding application to be displayed on the display unit 1102 (for example, using the display enabling unit 1110).

[0314] According to some embodiments, instructions to activate hardware button unit 1108 are displayed at a location on display unit 1102 determined based on the location of hardware button unit 1108; displaying additional transaction details for an activity associated with a corresponding application includes: abandoning scrolling instructions to activate hardware button unit 1108; and scrolling additional transaction details onto display unit 1102.

[0315] According to some embodiments, displaying additional transaction details for an activity associated with the corresponding application includes scrolling the additional transaction details onto the display unit 1102 such that the additional transaction details cover the instruction to activate the hardware button unit 1108 .

[0316] According to some embodiments, the processing unit 1106 is further configured to: when displaying additional transaction details, detect a selection of a first detail among the additional transaction details via one or more input device units 1104 (for example, using the detection unit 1112); and in response to detecting the selection of the first detail among the additional transaction details, enable one or more options for the first detail to be displayed on the display unit 1102 (for example, using the display enabling unit 1110).

[0317] According to some embodiments, processing unit 1106 is further configured to: based on displaying a transaction user interface: monitor the hardware button unit for activation (e.g., using monitoring unit 1118); detect activation of the hardware button unit (e.g., using detection unit 1112); and in response to detecting activation of hardware button unit 1108, conduct a transaction for the activity (e.g., using conduct unit 1116) based on determining that the activation of hardware button unit 1108 meets transaction authorization criteria.

[0318] According to some embodiments, the processing unit 1106 is further configured to: detect activation of the hardware button unit 1108 (for example, using the detection unit 1112); and in response to detecting the activation of the hardware button unit 1108: based on determining that transaction processing standards have been met (including standards that transaction parameters are correct), conduct a transaction for the activity (for example, using the conduct unit 1116); and based on determining that the transaction parameters are incorrect, enable an error notification indicating that an error has been detected to be displayed on the display unit 1102 (for example, using the display enable unit 1110) without conducting the transaction.

[0319] According to some embodiments, the processing unit 1106 is further configured to: based on determining that the transaction parameters are incorrect, receive user input via one or more input device units 1104 at the electronic device 1100 (for example, using the receiving unit 1114); and in response to receiving the user input at the electronic device 1100, modify the transaction parameters based on the user input.

[0320] According to some embodiments, the processing unit 1106 is further configured to: based on determining that the transaction parameters are incorrect, receive a request to correct the error (for example, using the receiving unit 1114); and in response to receiving the request to correct the error: based on determining that there are potentially compatible transaction parameters on the electronic device 1100, enable one or more of the potentially compatible transaction parameters to be displayed on the display unit 1102 (for example, using the display enabling unit 1110); and based on determining that there are no potentially compatible transaction parameters on the electronic device 1100, enable instructions for entering additional transaction parameters on a companion device different from the electronic device 1100 to be displayed on the display unit 1102 (for example, using the display enabling unit 1110).

[0321] According to some embodiments, displaying an error notification on the display unit 1102 indicating that an error has been detected includes replacing the display of an instruction to activate a hardware button with the display of the error notification.

[0322] According to some embodiments, the processing unit 1106 is further configured to: receive user input via one or more input device units 1104 (for example, using the receiving unit 1114), the user input corresponding to an instruction to select a payment account from multiple payment accounts in the electronic wallet of the electronic device 1100; and select a payment account for use in the active transaction in response to detecting the user input corresponding to the instruction to select a payment account from multiple payment accounts.

[0323] According to some embodiments, displaying the transaction user interface includes replacing a displayed system user interface element with the payment instructions.

[0324] According to some embodiments, conducting a transaction for the activity includes: requesting a password; detecting the password via one or more input device units 1104; and transmitting the password for processing the transaction.

[0325] References Figure 8 The described operations are optionally performed by Figure 1A-1B or Fig.11112. For example, display operation 802 and detection operation 804 are optionally implemented by event classifier 170, event identifier 180, and event handler 190. Event monitor 171 in event classifier 170 detects contact on touch-sensitive display 112, and event distributor module 174 transmits event information to application 136-1. The corresponding event identifier 180 of application 136-1 compares the event information with the corresponding event definition 186, and determines whether the first contact at the first position on the touch-sensitive surface corresponds to a predefined event or sub-event, such as activation of an enabling representation on a user interface. When a corresponding predefined event or sub-event is detected, event identifier 180 activates an event handler 190 associated with the detection of the event or sub-event. Event handler 190 optionally utilizes or calls data updater 176 or object updater 177 to update the application internal state 192. In some embodiments, event handler 190 accesses the corresponding GUI updater 178 to update the content displayed by the application. Similarly, a person skilled in the art will clearly know how to Figure 1A-1B The components depicted in the figure are used to implement other processes.

[0326] According to some embodiments, Fig.12 An exemplary functional block diagram of an electronic device 1200 configured according to the principles of various described embodiments is shown. According to some embodiments, the functional blocks of the electronic device 1200 are configured to perform the techniques described above. The functional blocks of the device 1200 are optionally implemented by hardware, software, or a combination of hardware and software to perform the principles of various described embodiments. It should be understood by those skilled in the art that Fig.12 The functional blocks described in the present invention are optionally combined or separated into sub-blocks to implement the principles of various embodiments. Therefore, the description herein optionally supports any possible combination or separation or further limitation of the functional blocks described herein.

[0327] like Fig.12 As shown, the electronic device 1200 includes: a display unit 1202 configured to display a graphical user interface; one or more input device units 1204, optionally a hardware button unit 1208, optionally a microphone unit 1224; and a processing unit 1206 coupled to the display unit 1202, the one or more input device units 1204, the optional hardware button unit 1208, and the optional microphone unit 1224. In some embodiments, the processing unit 1206 includes a display enabling unit 1210, a detection unit 1212, a receiving unit 1214, a performing unit 1216, a monitoring unit 1218, a transmission unit 1220, and an updating unit 1222.

[0328] The processing unit 1206 is configured to: (for example, using the receiving unit 1214) receive a request to conduct a transaction using transaction parameters; in response to the request to conduct the transaction, based on determining that the transaction parameters are incorrect, enable an error notification indicating that an error has been detected to be displayed on the display unit 1202 (for example, using the display enabling unit 1210); receive a request to correct the error via one or more input device units 1204 (for example, using the receiving unit 1214); and in response to receiving the request to correct the error: based on determining that there are potentially compatible transaction parameters on the electronic device 1200, enable one or more of the potentially compatible transaction parameters to be displayed on the display unit 1202 (for example, using the display enabling unit 1210); and based on determining that there are no potentially compatible transaction parameters on the electronic device 1200, enable instructions for entering additional transaction parameters on a companion device different from the electronic device 1200 to be displayed on the display unit 1202 (for example, using the display enabling unit 1210).

[0329] According to some embodiments, processing unit 1206 is further configured to: in response to a request to conduct a transaction, conduct the transaction (e.g., using conducting unit 1216) based on determining that transaction processing criteria (including criteria that transaction parameters are correct) have been met.

[0330] According to some embodiments, the processing unit 1206 is further configured to: transmit a request for a transaction parameter input user interface to a companion device (e.g., using the transmission unit 1218); and wherein the companion device displays an indication of the request for a transaction parameter input user interface.

[0331] According to some embodiments, an indication of a request for a transaction parameter input user interface is activated on the companion device, causing the transaction parameter input user interface to be displayed on a display unit of the companion device.

[0332] According to some embodiments, the processing unit 1206 is further configured to: receive corresponding additional transaction parameters (e.g., using the receiving unit 1214); and in response to receiving the corresponding additional transaction parameters, update the transaction user interface on the display unit 1202 according to the corresponding additional transaction parameters (e.g., using the updating unit 1222).

[0333] According to some embodiments, the processing unit 1206 is further configured to: in response to receiving the transaction parameters, update the transaction parameters (e.g., using the updating unit 1222) to include corresponding additional transaction parameters for use in the transaction.

[0334] According to some embodiments, the processing unit 1206 is further configured to: in response to receiving corresponding additional transaction parameters, enable an indication of the corresponding additional transaction parameters to be displayed on the display unit 1202 (for example, using the display enabling unit 1210); and when displaying the indication of the corresponding additional transaction parameters, detect the activation of the hardware button unit 1208 of the electronic device 1200 (for example, using the detecting unit 1212); and based on determining that the updated transaction parameters including the corresponding additional transaction parameters are correct, conduct a transaction for the activity (for example, using the conducting unit 1216); and based on determining that the updated transaction parameters including the corresponding additional transaction parameters are incorrect, enable a second error notification indicating that an error has been detected to be displayed on the display unit 1202 (for example, using the display enabling unit 1210).

[0335] According to some embodiments, the processing unit 1206 is further configured to: in response to receiving corresponding additional transaction parameters, enable (for example, using the display enabling unit 1210) to display on the display unit 1202 an instruction to activate the hardware button unit 1208 of the electronic device 1200 to authorize payment for the transaction; detect (for example, using the detection unit 1212) the activation of the hardware button unit 1208; and in response to detecting the activation of the hardware button unit 1208: based on determining that transaction processing standards have been met (including standards that the updated transaction parameters are correct), conduct the transaction for the activity (for example, using the conducting unit 1216); and based on determining that the transaction parameters are incorrect, enable (for example, using the display enabling unit 1210) to display an error notification indicating that an error has been detected on the display unit 1202.

[0336] According to some embodiments, processing unit 1206 is further configured to: in response to a request to conduct a transaction, based on determining that a transaction parameter is erroneous, update (e.g., using update unit 1222) a displayed characteristic of a displayed user interface element to indicate that an error has been detected.

[0337] According to some embodiments, the processing unit 1206 is further configured to: in response to receiving a request to correct an error: based on determining that there are potentially compatible transaction parameters on the electronic device 1200, update the transaction parameters (for example, using the updating unit 1222) to include default transaction parameters among the potentially compatible transaction parameters for use in the transaction; and enable (for example, using the display enabling unit 1210) one or more enabling representations corresponding to one or more corresponding potentially compatible transaction parameters to be displayed on the display unit 1202.

[0338] According to some embodiments, the processing unit 1206 is further configured to: in response to receiving a request to correct an error: based on determining that there are potentially compatible transaction parameters on the electronic device 1200, enable an input enable indication to be displayed on the display unit 1202 (for example, using the display enable unit 1210), which, when activated, enables a user to provide transaction parameters that are not included in the potentially compatible transaction parameters at the electronic device 1200.

[0339] According to some embodiments, processing unit 1206 is further configured to: detect activation of an input enable indication (e.g., using detection unit 1212); in response to detecting activation of the input enable indication, monitor audio input received via microphone unit 1224 of electronic device 1200 (e.g., using monitoring unit 1218); and update transaction parameters based on the audio input detected via microphone unit 1224 of electronic device 1200 (e.g., using update unit 1222).

[0340] According to some embodiments, processing unit 1206 is further configured to: detect activation of an input enable indication (e.g., using detection unit 1212); in response to detecting activation of the input enable indication, enable display of one or more contacts based on contacts stored in a contacts application on display unit 1202 (e.g., using display enabling unit 1210); receive a selection of one or more contacts of the contact (e.g., using receiving unit 1214); and update transaction parameters based on the selected contact (e.g., using updating unit 1222).

[0341] According to some embodiments, processing unit 1206 is further configured to: detect activation of an input enable indication (for example, using a detection unit); in response to detecting the activation of the input enable indication, transmit a second request for a second transaction parameter input user interface to a companion device (for example, using a transmission unit 1220); and wherein the companion device displays a second indication of the request for a second transaction parameter input user interface.

[0342] References Fig.10 The described operations are optionally performed by Figure 1A-1B or Fig.121002 and the display operation 1004 are implemented by the components depicted in . For example, the receiving operation 1002 and the display operation 1004 are optionally implemented by the event classifier 170, the event identifier 180, and the event handler 190. The event monitor 171 in the event classifier 170 detects the contact on the touch-sensitive display 112, and the event distributor module 174 transmits the event information to the application 136-1. The corresponding event identifier 180 of the application 136-1 compares the event information with the corresponding event definition 186, and determines whether the first contact at the first position on the touch-sensitive surface corresponds to a predefined event or sub-event, such as the activation of an enabling representation on the user interface. When the corresponding predefined event or sub-event is detected, the event identifier 180 activates the event handler 190 associated with the detection of the event or sub-event. The event handler 190 optionally utilizes or calls the data updater 176 or the object updater 177 to update the application internal state 192. In some embodiments, the event handler 190 accesses the corresponding GUI updater 178 to update the content displayed by the application. Similarly, a person skilled in the art will clearly know how to Figure 1A-1B The components depicted in the figure are used to implement other processes.

[0343] Exemplary methods, non-transitory computer-readable storage media, systems, and electronic devices are given in the following:

[0344] 1. A method comprising:

[0345] At an electronic device having a display, one or more input devices, and hardware buttons;

[0346] displaying, on the display, an application user interface for a respective application, wherein the application user interface includes a transaction affordance for requesting payment for an activity associated with the respective application;

[0347] detecting, via the one or more input devices, a selection of the transaction affordance while displaying the application user interface; and

[0348] In response to detecting a selection of the transaction affordance, displaying a transaction user interface, the transaction user interface including simultaneously displaying:

[0349] transaction details for the activity associated with the corresponding application; and

[0350] Instructions for activating the hardware button of the device to authorize payment for the activity associated with the corresponding application.

[0351] 2. A method according to item 1, wherein the transaction enable representation displayed in the application user interface for the corresponding application is provided by a payment application of the electronic device that is different from the corresponding application.

[0352] 3. A method according to any one of items 1-2, wherein the transaction enable indication is provided by the corresponding application, and when activated, the transaction enable indication triggers display of the transaction user interface.

[0353] 4. A method according to any one of items 1-3, wherein the corresponding application is a third-party application.

[0354] 5. A method according to any one of items 1-4, wherein the activities associated with the corresponding application include one or more of the following: transportation requests, ride sharing requests, purchasing services, purchasing products, and conducting peer-to-peer transactions.

[0355] 6. A method according to any one of items 1-5, wherein the transaction details include information about the cost of the activity.

[0356] 7. According to the method of any one of items 1-6, based on determining that the activity has variable costs, the transaction details include an indication that the activity has variable costs.

[0357] 8. A method according to any one of items 1-7, wherein displaying the transaction user interface also includes displaying a graphical representation of a payment account, and if authorization to conduct the payment transaction is received, payment will be made using the payment account.

[0358] 9. The method according to any one of items 1 to 8, further comprising:

[0359] receiving, via the one or more input devices, input corresponding to an instruction to scroll the transaction user interface while displaying the transaction user interface including the transaction details and the instruction to activate the hardware button; and

[0360] In response to receiving the input corresponding to the instruction to scroll the transaction user interface:

[0361] Additional transaction details are displayed for the activity associated with the corresponding application.

[0362] 10. The method according to item 9, wherein:

[0363] displaying the instruction to activate the hardware button on the display at a location determined based on the location of the hardware button;

[0364] Displaying additional transaction details for the activity associated with the corresponding application includes:

[0365] abandoning said instructions to scroll and activate said hardware button; and

[0366] The additional transaction details are scrolled onto the display.

[0367] 11. The method of clause 9, wherein displaying additional transaction details for the activity associated with the corresponding application comprises:

[0368] The additional transaction details are scrolled onto the display such that the additional transaction details obscure the instruction to activate the hardware button.

[0369] 12. The method according to any one of items 9 to 11, further comprising:

[0370] detecting, via the one or more input devices, a selection of a first detail of the additional transaction details while displaying the additional transaction details; and

[0371] In response to detecting a selection of the first detail of the additional transaction details, one or more options for the first detail are displayed.

[0372] 13. The method according to any one of items 1 to 12, further comprising:

[0373] According to the trading UI being displayed:

[0374] monitoring the hardware button for activation;

[0375] detecting activation of the hardware button; and

[0376] In response to detecting activation of the hardware button, a transaction for the activity is conducted based on determining that the activation of the hardware button meets transaction authorization criteria.

[0377] 14. The method according to any one of items 1 to 13, further comprising:

[0378] detecting activation of the hardware button; and

[0379] In response to detecting activation of the hardware button:

[0380] conducting a transaction for the activity based on determining that transaction processing criteria have been met, including that the transaction parameters are correct; and

[0381] Based on determining that the transaction parameters are incorrect, an error notification is displayed on the display indicating that an error has been detected, rather than proceeding with the transaction.

[0382] 15. The method according to item 14, further comprising:

[0383] Based on the determining that the transaction parameter is erroneous, receiving user input at the electronic device via the one or more input devices; and

[0384] In response to receiving the user input at the electronic device, the transaction parameters are modified based on the user input.

[0385] 16. The method according to item 14, further comprising:

[0386] Based on the determination that the transaction parameter is erroneous, receiving a request to correct the error; and

[0387] In response to receiving the request to correct the error:

[0388] Based on determining that there are potentially compatible transaction parameters on the electronic device, displaying one or more of the potentially compatible transaction parameters; and

[0389] Based on determining that there are no potentially compatible transaction parameters on the electronic device, instructions for entering additional transaction parameters on a companion device different from the electronic device are displayed.

[0390] 17. The method of any one of clauses 14-16, wherein displaying the error notification on the display indicating that an error has been detected comprises:

[0391] The display of the instruction to activate the hardware button is replaced with the display of the error notification.

[0392] 18. The method according to any one of items 1 to 17, further comprising:

[0393] receiving, via the one or more input devices, a user input corresponding to an instruction to select a payment account from a plurality of payment accounts in an electronic wallet of the electronic device; and

[0394] In response to detecting the user input corresponding to the instruction to select the payment account from a plurality of payment accounts, the payment account for use in the transaction of the activity is selected.

[0395] 19. A method according to any one of items 1-18, wherein displaying the transaction user interface includes replacing a displayed system user interface element with a payment instruction.

[0396] 20. The method according to any one of items 14 to 19, wherein:

[0397] Conducting said transaction for said activity comprises:

[0398] Request password;

[0399] detecting the password via the one or more input devices; and

[0400] The cryptogram is transmitted for use in processing the transaction.

[0401] 21. A computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device having a display, one or more input devices, and hardware buttons, the one or more programs comprising instructions for executing a method according to any one of items 1-20.

[0402] 22. An electronic device comprising:

[0403] monitor;

[0404] one or more input devices;

[0405] Hardware buttons;

[0406] one or more processors; and

[0407] A memory storing one or more programs configured to be executed by the one or more processors, the one or more programs comprising instructions for executing a method according to any one of items 1-20.

[0408] 23. An electronic device, comprising:

[0409] monitor;

[0410] one or more input devices;

[0411] Hardware buttons; and

[0412] An apparatus for performing the method according to any one of items 1-20.

[0413] 24. A non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device having a display, one or more input devices, and hardware buttons, the one or more programs comprising instructions for:

[0414] displaying, on the display, an application user interface for a respective application, wherein the application user interface includes a transaction affordance for requesting payment for an activity associated with the respective application;

[0415] detecting, via the one or more input devices, a selection of the transaction affordance while displaying the application user interface; and

[0416] In response to detecting a selection of the transaction affordance, displaying a transaction user interface, the transaction user interface including simultaneously displaying:

[0417] transaction details for the activity associated with the corresponding application; and

[0418] Instructions for activating the hardware button of the device to authorize payment for the activity associated with the corresponding application.

[0419] 25. An electronic device comprising:

[0420] monitor;

[0421] one or more input devices;

[0422] Hardware buttons;

[0423] one or more processors; and

[0424] A memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for performing the following operations:

[0425] displaying, on the display, an application user interface for a respective application, wherein the application user interface includes a transaction affordance for requesting payment for an activity associated with the respective application;

[0426] detecting, via the one or more input devices, a selection of the transaction affordance while displaying the application user interface; and

[0427] In response to detecting a selection of the transaction affordance, displaying a transaction user interface, the transaction user interface including simultaneously displaying:

[0428] transaction details for the activity associated with the corresponding application; and

[0429] Instructions for activating the hardware button of the device to authorize payment for the activity associated with the corresponding application.

[0430] 26. An electronic device comprising:

[0431] monitor;

[0432] one or more input devices;

[0433] Hardware buttons;

[0434] means for displaying, on the display, an application user interface for a respective application, wherein the application user interface includes a transaction affordance for requesting payment for an activity associated with the respective application;

[0435] means for detecting, via said one or more input devices, a selection of said transaction affordance while said application user interface is displayed; and

[0436] In response to detecting a selection of the transaction affordance, means for displaying a transaction user interface, the transaction user interface comprising simultaneously displaying:

[0437] transaction details for the activity associated with the corresponding application; and

[0438] Instructions for activating the hardware button of the device to authorize payment for the activity associated with the corresponding application.

[0439] 27. A method comprising:

[0440] At an electronic device having a display and one or more input devices:

[0441] Receive a request to conduct a transaction using transaction parameters;

[0442] In response to the request to conduct the transaction, based on determining that the transaction parameters are incorrect, displaying an error notification indicating that an error has been detected;

[0443] receiving, via the one or more input devices, a request to correct the error; and

[0444] In response to receiving the request to correct the error:

[0445] Based on determining that there are potentially compatible transaction parameters on the electronic device, displaying one or more of the potentially compatible transaction parameters on the display; and

[0446] Based on determining that there are no potentially compatible transaction parameters on the device, instructions for entering additional transaction parameters on a companion device different from the electronic device are displayed on the display.

[0447] 28. The method according to item 27, further comprising:

[0448] In response to the request to conduct the transaction, the transaction is conducted based on a determination that transaction processing criteria have been met, including that the transaction parameters are correct.

[0449] 29. The method according to any one of items 27-28, further comprising:

[0450] transmitting a request for a transaction parameter input user interface to the companion device; and

[0451] Wherein the companion device displays an indication of the request regarding the transaction parameter input user interface.

[0452] 30. A method according to item 29, wherein the indication of the request for the transaction parameter input user interface is activated on the companion device, so that the transaction parameter input user interface is displayed on the display of the companion device.

[0453] 31. The method according to any one of items 27 to 30, further comprising:

[0454] receiving corresponding additional transaction parameters; and

[0455] In response to receiving the corresponding additional transaction parameters, a transaction user interface is updated on the display according to the corresponding additional transaction parameters.

[0456] 32. The method according to item 31, further comprising:

[0457] In response to receiving the transaction parameters, the transaction parameters are updated to include the corresponding additional transaction parameters used in the transaction.

[0458] 33. The method according to any one of items 31-32, further comprising:

[0459] in response to receiving the corresponding additional transaction parameters, displaying an indication of the corresponding additional transaction parameters on the display; and

[0460] detecting activation of a hardware button of said electronic device while displaying said indication of said corresponding additional transaction parameter; and

[0461] Based on determining that the updated transaction parameters including the corresponding additional transaction parameters are correct, conducting the transaction for the activity; and

[0462] Based on determining that the updated transaction parameters are erroneous, a second error notification is displayed on the display indicating that an error has been detected.

[0463] 34. The method according to any one of items 31 to 33, further comprising:

[0464] in response to receiving the corresponding additional transaction parameters, displaying on the display an instruction to activate a hardware button of the electronic device to authorize payment for the transaction;

[0465] detecting activation of the hardware button; and

[0466] In response to detecting activation of the hardware button:

[0467] Conducting a transaction for the activity based on determining that transaction processing criteria have been met, including that the updated transaction parameters are correct; and

[0468] Based on determining that the transaction parameter is incorrect, an error notification is displayed on the display indicating that an error has been detected.

[0469] 35. The method according to any one of items 27 to 34, further comprising:

[0470] In response to the request to conduct the transaction, based on the determination that the transaction parameter is in error, updating a displayed characteristic of a displayed user interface element to indicate that the error has been detected.

[0471] 36. The method according to any one of items 27 to 35, further comprising:

[0472] In response to receiving the request to correct the error:

[0473] According to the determining of the potentially compatible transaction parameters on the electronic device:

[0474] updating the transaction parameters to include default transaction parameters for the transaction of the potentially compatible transaction parameters; and

[0475] One or more affordances corresponding to one or more respective potentially compatible transaction parameters are displayed on the display.

[0476] 37. The method according to item 36, further comprising:

[0477] In response to receiving the request to correct the error:

[0478] According to the determining of the potentially compatible transaction parameters on the electronic device:

[0479] An input enabling indication is displayed on the display, which, when activated, enables the user to provide a transaction parameter at the electronic device that is not included in the potentially compatible transaction parameters.

[0480] 38. The method according to item 37, further comprising:

[0481] detecting activation of the input affordance;

[0482] In response to detecting activation of an input affordance, monitoring audio input received via a microphone of the electronic device; and

[0483] The transaction parameters are updated based on the audio input received via the microphone of the electronic device.

[0484] 39. The method according to any one of items 37-38, further comprising:

[0485] detecting activation of the input affordance;

[0486] In response to detecting activation of the input affordance, displaying one or more contacts based on contacts stored in a contacts application;

[0487] receiving a selection of a contact from the one or more contacts; and

[0488] The transaction parameters are updated based on the selected contacts.

[0489] 40. The method according to any one of items 37-39, further comprising:

[0490] detecting activation of the input affordance;

[0491] In response to detecting activation of the input affordance, transmitting to the companion device a second request for a second transaction parameter input user interface; and

[0492] Wherein the companion device displays a second indication of the request regarding the second transaction parameter input user interface.

[0493] 41. A computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device having a display and one or more input devices, the one or more programs comprising instructions for executing a method according to any one of items 27-40.

[0494] 42. An electronic device comprising:

[0495] monitor;

[0496] one or more input devices;

[0497] one or more processors; and

[0498] A memory storing one or more programs configured to be executed by the one or more processors, the one or more programs comprising instructions for executing a method according to any one of items 27-40.

[0499] 43. An electronic device comprising:

[0500] monitor;

[0501] one or more input devices; and

[0502] An apparatus for performing a method according to any one of items 27-40.

[0503] 44. A non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device having a display and one or more input devices, the one or more programs comprising instructions for:

[0504] Receive a request to conduct a transaction using transaction parameters;

[0505] In response to the request to conduct the transaction, based on determining that the transaction parameters are incorrect, displaying an error notification indicating that an error has been detected;

[0506] receiving, via the one or more input devices, a request to correct the error; and

[0507] In response to receiving the request to correct the error:

[0508] Based on determining that there are potentially compatible transaction parameters on the electronic device, displaying one or more of the potentially compatible transaction parameters on the display; and

[0509] Based on determining that there are no potentially compatible transaction parameters on the device, instructions for entering additional transaction parameters on a companion device different from the electronic device are displayed on the display.

[0510] 45. An electronic device comprising:

[0511] monitor;

[0512] one or more input devices;

[0513] one or more processors; and

[0514] A memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for performing the following operations:

[0515] Receive a request to conduct a transaction using transaction parameters;

[0516] In response to the request to conduct the transaction, based on determining that the transaction parameters are incorrect, displaying an error notification indicating that an error has been detected;

[0517] receiving, via the one or more input devices, a request to correct the error; and

[0518] In response to receiving the request to correct the error:

[0519] Based on determining that there are potentially compatible transaction parameters on the electronic device, displaying one or more of the potentially compatible transaction parameters on the display; and

[0520] Based on determining that there are no potentially compatible transaction parameters on the device, instructions for entering additional transaction parameters on a companion device different from the electronic device are displayed on the display.

[0521] 46. ​​An electronic device comprising:

[0522] monitor;

[0523] one or more input devices;

[0524] means for receiving a request to conduct a transaction using transaction parameters;

[0525] in response to said request to conduct said transaction, upon determining that said transaction parameters are in error, means for displaying an error notification indicating that an error has been detected;

[0526] means for receiving, via the one or more input devices, a request to correct the error; and

[0527] In response to receiving the request to correct the error, means for:

[0528] Based on determining that there are potentially compatible transaction parameters on the electronic device, displaying one or more of the potentially compatible transaction parameters on the display; and

[0529] Based on determining that there are no potentially compatible transaction parameters on the device, instructions for entering additional transaction parameters on a companion device different from the electronic device are displayed on the display.

[0530] 47. An electronic device comprising:

[0531] Display unit;

[0532] one or more input device units;

[0533] Hardware button units; and

[0534] a processing unit, the processing unit being coupled to the display unit, the one or more input device units, and the hardware button unit, the processing unit being configured to:

[0535] enabling display of an application user interface for a respective application on the display unit, wherein the application user interface includes a transaction affordance for requesting payment for an activity associated with the respective application;

[0536] while enabling display of the application user interface, detecting, via the one or more input device elements, selection of the transaction affordance; and

[0537] In response to detecting selection of the transaction affordance, enabling display of a transaction user interface on the display unit, the transaction user interface comprising simultaneously displaying:

[0538] transaction details for the activity associated with the corresponding application; and

[0539] An instruction to activate the hardware button unit of the electronic device to authorize payment for the activity associated with the corresponding application.

[0540] 48. An electronic device according to item 47, wherein the transaction enable representation displayed in the application user interface for the corresponding application is provided by a payment application of the electronic device that is different from the corresponding application.

[0541] 49. An electronic device according to any one of items 47-48, wherein the transaction enable indication is provided by the corresponding application, and when activated, the transaction enable indication triggers display of the transaction user interface.

[0542] 50. An electronic device according to any one of items 47-49, wherein the corresponding application is a third-party application.

[0543] 51. An electronic device according to any one of items 47-50, wherein the activities associated with the corresponding application include one or more of the following: transportation requests, ride sharing requests, purchasing services, purchasing products, and conducting peer-to-peer transactions.

[0544] 52. An electronic device according to any of items 47-51, wherein the transaction details include information about the cost of the activity.

[0545] 53. An electronic device according to any one of items 47-52, wherein the transaction details include an indication that the activity has a variable cost based on determining that the activity has a variable cost.

[0546] 54. An electronic device according to any one of items 47-53, wherein displaying the transaction user interface also includes displaying a graphical representation of a payment account, and if authorization to conduct the payment transaction is received, payment will be made using the payment account.

[0547] 55. The electronic device according to any one of items 47-54, wherein the processing unit is further configured to:

[0548] receiving, via the one or more input device units, an input corresponding to an instruction to scroll the transaction user interface while displaying the transaction user interface including the transaction details and the instruction to activate the hardware button unit; and

[0549] In response to receiving the input corresponding to the instruction to scroll the transaction user interface:

[0550] Additional transaction details for the activity associated with the corresponding application are enabled to be displayed on the display unit.

[0551] 56. The electronic device according to item 55, wherein:

[0552] displaying the instruction to activate the hardware button unit at a position determined based on the position of the hardware button unit on the display unit;

[0553] Displaying additional transaction details for the activity associated with the corresponding application includes:

[0554] abandoning the instruction to scroll and activate the hardware button unit; and

[0555] The additional transaction details are scrolled onto the display unit.

[0556] 57. The electronic device of clause 55, wherein displaying additional transaction details for the activity associated with the corresponding application comprises:

[0557] The additional transaction details are scrolled onto the display unit such that the additional transaction details obscure the instruction to activate the hardware button unit.

[0558] 58. The electronic device according to any one of items 55-57, wherein the processing unit is further configured to:

[0559] detecting, via the one or more input device elements, a selection of a first detail of the additional transaction details while displaying the additional transaction details; and

[0560] In response to detecting selection of the first detail of the additional transaction details, one or more options for the first detail are enabled to be displayed on the display unit.

[0561] 59. The electronic device according to any one of items 47-58, wherein the processing unit is further configured to:

[0562] According to the trading UI being displayed:

[0563] monitoring the hardware button unit for activation;

[0564] detecting activation of the hardware button unit; and

[0565] In response to detecting activation of the hardware button unit, a transaction for the activity is conducted based on determining that the activation of the hardware button unit meets transaction authorization criteria.

[0566] 60. The electronic device according to any one of items 47-59, wherein the processing unit is further configured to:

[0567] detecting activation of the hardware button unit; and

[0568] In response to detecting activation of the hardware button unit:

[0569] conducting a transaction for the activity based on determining that transaction processing criteria have been met, including that the transaction parameters are correct; and

[0570] Based on determining that the transaction parameters are erroneous, an error notification indicating that an error has been detected can be displayed on the display unit instead of conducting the transaction.

[0571] 61. The electronic device according to item 60, wherein the processing unit is further configured to:

[0572] Based on the determination that the transaction parameter is erroneous, receiving user input at the electronic device via the one or more input device units; and

[0573] In response to receiving the user input at the electronic device, the transaction parameters are modified based on the user input.

[0574] 62. The electronic device according to item 60, wherein the processing unit is further configured to:

[0575] Based on the determination that the transaction parameter is erroneous, receiving a request to correct the error; and

[0576] In response to receiving the request to correct the error:

[0577] Based on determining that there are potentially compatible transaction parameters on the electronic device, enabling one or more of the potentially compatible transaction parameters to be displayed on the display unit; and

[0578] Based on determining that there are no potentially compatible transaction parameters on the electronic device, instructions for entering additional transaction parameters on a companion device different from the electronic device can be displayed on the display unit.

[0579] 63. The electronic device according to any one of items 60-62, wherein displaying the error notification indicating that an error has been detected on the display unit comprises:

[0580] The display of the instruction to activate the hardware button unit is replaced with the display of the error notification.

[0581] 64. The electronic device according to any one of items 47-63, wherein the processing unit is further configured to:

[0582] receiving, via the one or more input device units, a user input corresponding to an instruction to select a payment account from a plurality of payment accounts in an electronic wallet of the electronic device; and

[0583] In response to detecting the user input corresponding to the instruction to select the payment account from a plurality of payment accounts, the payment account for use in the transaction of the activity is selected.

[0584] 65. An electronic device according to any of items 47-64, wherein displaying the transaction user interface includes replacing a displayed system user interface element with a payment instruction.

[0585] 66. An electronic device according to any one of items 60-65, wherein:

[0586] Conducting said transaction for said activity comprises:

[0587] Request password;

[0588] detecting the password via the one or more input device units; and

[0589] The cryptogram is transmitted for use in processing the transaction.

[0590] 67. An electronic device comprising:

[0591] Display unit;

[0592] one or more input device units; and

[0593] a processing unit, the processing unit being coupled to the display unit and the one or more input device units, the processing unit being configured to:

[0594] Receive a request to conduct a transaction using transaction parameters;

[0595] in response to the request to conduct the transaction, based on determining that the transaction parameters are in error, enabling display of an error notification on the display unit indicating that an error has been detected;

[0596] receiving, via the one or more input device units, a request to correct the error; and

[0597] In response to receiving the request to correct the error:

[0598] Based on determining that there are potentially compatible transaction parameters on the electronic device, enabling one or more of the potentially compatible transaction parameters to be displayed on the display unit; and

[0599] Based on determining that there are no potentially compatible transaction parameters on the electronic device, instructions for entering additional transaction parameters on a companion device different from the electronic device can be displayed on the display unit.

[0600] 68. The electronic device according to item 67, wherein the processing unit is further configured to:

[0601] In response to the request to conduct the transaction, the transaction is conducted based on a determination that transaction processing criteria have been met, including that the transaction parameters are correct.

[0602] 69. The electronic device according to any one of items 67-68, wherein the processing unit is further configured to:

[0603] transmitting a request for a transaction parameter input user interface to the companion device; and

[0604] Wherein the companion device displays an indication of the request regarding the transaction parameter input user interface.

[0605] 70. An electronic device according to item 69, wherein the indication of the request for the transaction parameter input user interface is activated on the companion device, so that the transaction parameter input user interface is displayed on the display unit of the companion device.

[0606] 71. The electronic device according to any one of items 67-70, wherein the processing unit is further configured to:

[0607] receiving corresponding additional transaction parameters; and

[0608] In response to receiving the corresponding additional transaction parameters, a transaction user interface is updated on the display unit according to the corresponding additional transaction parameters.

[0609] 72. The electronic device according to item 71, wherein the processing unit is further configured to:

[0610] In response to receiving the transaction parameters, the transaction parameters are updated to include the corresponding additional transaction parameters used in the transaction.

[0611] 73. The electronic device according to any one of items 71-72, wherein the processing unit is further configured to:

[0612] responsive to receiving the corresponding additional transaction parameter, enabling display of an indication of the corresponding additional transaction parameter on the display unit; and

[0613] detecting activation of a hardware button unit of said electronic device while displaying said indication of said corresponding additional transaction parameter; and

[0614] Based on determining that the updated transaction parameters including the corresponding additional transaction parameters are correct, conducting the transaction for the activity; and

[0615] Based on determining that the updated transaction parameters are erroneous, a second error notification indicating that an error has been detected is enabled to be displayed on the display unit.

[0616] 74. The electronic device according to any one of items 71-73, wherein the processing unit is further configured to:

[0617] in response to receiving the corresponding additional transaction parameters, enabling display on the display unit of instructions to activate a hardware button unit of the electronic device to authorize payment for the transaction;

[0618] detecting activation of the hardware button unit; and

[0619] In response to detecting activation of the hardware button unit:

[0620] Conducting a transaction for the activity based on determining that transaction processing criteria have been met, including that the updated transaction parameters are correct; and

[0621] Based on determining that the transaction parameter is erroneous, an error notification can be displayed on the display unit indicating that an error has been detected.

[0622] 75. The electronic device according to any one of items 67-74, wherein the processing unit is further configured to:

[0623] In response to the request to conduct the transaction, based on the determination that the transaction parameter is in error, updating a displayed characteristic of a displayed user interface element to indicate that the error has been detected.

[0624] 76. The electronic device according to any one of items 67-75, wherein the processing unit is further configured to:

[0625] In response to receiving the request to correct the error:

[0626] According to the determining of the potentially compatible transaction parameters on the electronic device:

[0627] updating the transaction parameters to include default transaction parameters for the transaction of the potentially compatible transaction parameters; and

[0628] Enabling display on the display unit of one or more affordances corresponding to one or more respective potentially compatible transaction parameters.

[0629] 77. The electronic device according to item 76, wherein the processing unit is further configured to:

[0630] In response to receiving the request to correct the error:

[0631] According to the determining of the potentially compatible transaction parameters on the electronic device:

[0632] An input enable indication is enabled to be displayed on the display unit, and when activated, the input enable indication enables the user to provide a transaction parameter not included in the potentially compatible transaction parameters at the electronic device.

[0633] 78. The electronic device according to item 77, wherein the processing unit is further configured to:

[0634] detecting activation of the input affordance;

[0635] In response to detecting activation of an input affordance, monitoring audio input received via a microphone unit of the electronic device; and

[0636] The transaction parameters are updated based on the audio input received via the microphone unit of the electronic device.

[0637] 79. The electronic device according to any one of items 77-78, wherein the processing unit is further configured to:

[0638] detecting activation of the input affordance;

[0639] in response to detecting activation of the input affordance, enabling display of one or more contacts on the display unit based on contacts stored in a contacts application;

[0640] receiving a selection of a contact from the one or more contacts; and

[0641] The transaction parameters are updated based on the selected contact.

[0642] 80. The electronic device according to any one of items 77-79, wherein the processing unit is further configured to:

[0643] detecting activation of the input affordance;

[0644] In response to detecting activation of the input affordance, transmitting to the companion device a second request for a second transaction parameter input user interface; and

[0645] Wherein the companion device displays a second indication of the request regarding the second transaction parameter input user interface.

[0646] For the purpose of explanation, the preceding description is described by reference to specific embodiments. However, the above exemplary discussion is not intended to be exhaustive or limit the invention to the disclosed precise form. According to the above teachings, many modifications and variations are possible. These embodiments are selected and described in order to best explain the principles of these technologies and their practical applications. Others skilled in the art can thus best utilize these technologies and various embodiments with various modifications suitable for the intended specific use.

[0647] Although the disclosure and examples have been fully described with reference to the accompanying drawings, it should be noted that various changes and modifications will become apparent to those skilled in the art. It should be understood that such changes and modifications are considered to be included within the scope of the disclosure and examples defined by the claims.

[0648] As described above, one aspect of the present technology is to collect and use data from various sources to improve the delivery of inspirational content or any other content that may be of interest to users. The present disclosure contemplates that in some instances, such collected data may include personal information data that uniquely identifies or can be used to contact or locate a specific person. Such personal information data may include demographic data, location-based data, phone numbers, email addresses, home addresses, or any other identifying information.

[0649] The present disclosure recognizes that the use of such personal information data in the present invention technology can be used to benefit users. For example, the personal information data can be used to deliver targeted content that users are more interested in. Therefore, the use of such personal information data enables planned control of the delivered content. In addition, the present disclosure also anticipates other uses of personal information data that benefit users.

[0650] The disclosure also contemplates that entities responsible for the collection, analysis, disclosure, transmission, storage or other purposes of such personal information data will comply with established privacy policies and / or privacy practices. Specifically, such entities should implement and adhere to the use of privacy policies and practices that are recognized as meeting or exceeding the industry or government requirements for maintaining the privacy and security of personal information data. For example, personal information from users should be collected for the legal and reasonable purposes of the entity, and not shared or sold outside these legal uses. In addition, such collection should only be carried out after the user's informed consent. In addition, such entities should take any necessary steps to safeguard and protect access to such personal information data, and ensure that others who can access personal information data comply with their privacy policies and procedures. In addition, such entities can subject themselves to third-party assessments to prove that they comply with widely accepted privacy policies and practices.

[0651] Regardless of the foregoing, the present disclosure also contemplates implementation schemes in which users selectively block the use or access of personal information data. That is, the present disclosure contemplates providing hardware elements and / or software elements to prevent or block access to such personal information data. For example, with respect to an advertising delivery service, the technology of the present invention may be configured to allow a user to choose to "opt in" or "opt out" of participating in the collection of personal information data during registration for the service. For another example, a user may choose not to provide location information for a target content delivery service. For another example, a user may choose not to provide precise location information, but permit the transmission of location area information.

[0652] Thus, while the present disclosure broadly covers the use of personal information data to implement one or more of the various disclosed embodiments, the present disclosure also contemplates that various embodiments may also be implemented without access to such personal information data. That is, various embodiments of the present technology will not fail to function properly due to the lack of all or a portion of such personal information data. For example, content may be selected and delivered to a user by inferring preferences based on non-personal information data or an absolute minimum amount of personal information, such as content requested by a device associated with the user, other non-personal information available to a content delivery service, or publicly available information.

Claims

1. A method comprising: At a wearable electronic device having a display and one or more input devices of the wearable electronic device: Receive a request to conduct a transaction using transaction parameters; In response to the request to conduct the transaction, based on determining that the transaction parameters are erroneous, displaying an error notification on a display of the wearable electronic device indicating that an error has been detected; receiving, via the one or more input devices of the wearable electronic device, a request to correct the error; as well as In response to receiving the request to correct the error: Based on determining that there are potentially compatible transaction parameters on the wearable electronic device, displaying one or more of the potentially compatible transaction parameters on the display; and Based on determining that there are no potentially compatible transaction parameters on the wearable electronic device, displaying on the display instructions to enter additional transaction parameters on a companion application on a handheld companion device different from the wearable electronic device; wherein the handheld companion device includes an input device that is different from one or more input devices of the wearable electronic device; and The companion application is configured to send information to the wearable electronic device.

2. The method according to claim 1, further comprising: In response to the request to conduct the transaction, the transaction is conducted based on a determination that transaction processing criteria have been met, including that the transaction parameters are correct.

3. The method according to claim 1, further comprising: transmitting a request for a transaction parameter input user interface to the companion device; and Wherein the companion device displays an indication of the request regarding the transaction parameter input user interface.

4. The method according to claim 3, wherein the indication of activating the request for the transaction parameter input user interface on the companion device causes the transaction parameter input user interface to be displayed on a display of the companion device.

5. The method according to claim 1, further comprising: Receive corresponding additional transaction parameters; as well as In response to receiving the corresponding additional transaction parameters, a transaction user interface is updated on the display according to the corresponding additional transaction parameters.

6. The method according to claim 5, further comprising: In response to receiving the transaction parameters, the transaction parameters are updated to include the corresponding additional transaction parameters for use in the transaction.

7. The method according to claim 5, further comprising: in response to receiving the corresponding additional transaction parameter, displaying an indication of the corresponding additional transaction parameter on the display; as well as detecting activation of a hardware button of the wearable electronic device while displaying the indication of the corresponding additional transaction parameter; as well as Conducting the transaction for the activity based on determining that the updated transaction parameters including the corresponding additional transaction parameters are correct; as well as Based on determining that the updated transaction parameters are erroneous, a second error notification is displayed on the display indicating that an error has been detected.

8. The method according to claim 5, further comprising: in response to receiving the corresponding additional transaction parameters, displaying on the display an instruction to activate a hardware button of the wearable electronic device to authorize payment for the transaction; detecting activation of the hardware button; as well as In response to detecting activation of the hardware button: Conduct transactions for the activities described, based on a determination that transaction processing criteria have been met, including that updated transaction parameters are correct; as well as Based on determining that the transaction parameter is incorrect, an error notification is displayed on the display indicating that an error has been detected.

9. The method according to claim 1, further comprising: In response to the request to conduct the transaction, based on the determination that the transaction parameter is in error, updating a displayed characteristic of a displayed user interface element to indicate that the error has been detected.

10. The method according to claim 1, further comprising: In response to receiving the request to correct the error: Determining potentially compatible transaction parameters on the wearable electronic device according to the above-mentioned: updating the transaction parameters to include default transaction parameters of the potentially compatible transaction parameters for use in the transaction; and One or more affordances corresponding to one or more respective potentially compatible transaction parameters are displayed on the display.

11. The method according to claim 10, further comprising: In response to receiving the request to correct the error: Determining potentially compatible transaction parameters on the wearable electronic device according to the above-mentioned: An input enablement is displayed on the display, the input enablement enabling a user to provide a transaction parameter at the wearable electronic device that is not included in the potentially compatible transaction parameters when activated.

12. The method according to claim 11, further comprising: detecting activation of the input affordance; In response to detecting activation of an input affordance, monitoring audio input received via a microphone of the wearable electronic device; as well as The transaction parameters are updated based on the audio input received via the microphone of the wearable electronic device.

13. The method according to claim 11, further comprising: detecting activation of the input affordance; In response to detecting activation of the input affordance, displaying one or more contacts based on contacts stored in a contacts application; receiving a selection of a contact from the one or more contacts; as well as The transaction parameters are updated based on the selected contacts.

14. The method according to claim 11, further comprising: detecting activation of the input affordance; In response to detecting activation of the input affordance, transmitting to the companion device a second request for a second transaction parameter input user interface; and Wherein the companion device displays a second indication of the request regarding the second transaction parameter input user interface.

15. The method according to claim 1, wherein receiving the request to correct the error comprises detecting activation of a displayed error notification; and Activation of the displayed error notification causes the companion application to be displayed on the handheld companion device.

16. The method according to claim 1, wherein the companion application on the handheld companion device provides a user interface for user input of transaction parameters; wherein the companion application on the handheld companion device receives user input of the transaction parameters using an input device of the handheld companion device that is different from the one or more input devices of the wearable electronic device; and The companion application transmits the received user input of transaction parameters to the wearable electronic device.

17. The method of claim 1, wherein the request to conduct the transaction comprises two inputs on hardware buttons of the wearable electronic device.

18. The method of claim 1, further comprising: receiving additional transaction parameters from the handheld companion device after transmitting to the handheld companion device a second request for a transaction parameter user input interface; In response to receiving the additional transaction parameters from the handheld companion device, the displayed potentially compatible transaction parameters are updated based on the additional transaction parameters.

19. A computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a wearable electronic device having a display and one or more input devices of the wearable electronic device, the one or more programs comprising instructions for: Receive a request to conduct a transaction using transaction parameters; In response to the request to conduct the transaction, based on determining that the transaction parameters are erroneous, displaying an error notification on a display of the wearable electronic device indicating that an error has been detected; receiving, via the one or more input devices of the wearable electronic device, a request to correct the error; as well as In response to receiving the request to correct the error: Based on determining that there are potentially compatible transaction parameters on the wearable electronic device, displaying one or more of the potentially compatible transaction parameters on the display; and Based on determining that there are no potentially compatible transaction parameters on the wearable electronic device, displaying on the display instructions to enter additional transaction parameters on a companion application on a handheld companion device different from the wearable electronic device; wherein the handheld companion device includes an input device that is different from one or more input devices of the wearable electronic device; and The companion application is configured to send information to the wearable electronic device.

20. The computer-readable storage medium of claim 19, wherein the one or more programs further comprise instructions for: In response to the request to conduct the transaction, the transaction is conducted based on a determination that transaction processing criteria have been met, including that the transaction parameters are correct.

21. The computer-readable storage medium of claim 19, wherein the one or more programs further comprise instructions for: transmitting a request for a transaction parameter input user interface to the companion device; and Wherein the companion device displays an indication of the request regarding the transaction parameter input user interface.

22. A computer-readable storage medium according to claim 21, wherein the indication of activating the request for the transaction parameter input user interface on the companion device causes the transaction parameter input user interface to be displayed on a display of the companion device.

23. The computer-readable storage medium of claim 19, wherein the one or more programs further comprise instructions for: receiving corresponding additional transaction parameters; and In response to receiving the corresponding additional transaction parameters, a transaction user interface is updated on the display according to the corresponding additional transaction parameters.

24. The computer-readable storage medium of claim 23, wherein the one or more programs further comprise instructions for: In response to receiving the transaction parameters, the transaction parameters are updated to include the corresponding additional transaction parameters for use in the transaction.

25. The computer-readable storage medium of claim 23, wherein the one or more programs further comprise instructions for: in response to receiving the corresponding additional transaction parameters, displaying an indication of the corresponding additional transaction parameters on the display; and detecting activation of a hardware button of the wearable electronic device while displaying the indication of the corresponding additional transaction parameter; as well as Conducting the transaction for the activity based on determining that the updated transaction parameters including the corresponding additional transaction parameters are correct; as well as Based on determining that the updated transaction parameters are erroneous, a second error notification is displayed on the display indicating that an error has been detected.

26. The computer-readable storage medium of claim 23, wherein the one or more programs further comprise instructions for: in response to receiving the corresponding additional transaction parameters, displaying on the display an instruction to activate a hardware button of the wearable electronic device to authorize payment for the transaction; detecting activation of the hardware button; as well as In response to detecting activation of the hardware button: Conduct transactions for the activities described, based on a determination that transaction processing criteria have been met, including that updated transaction parameters are correct; as well as Based on determining that the transaction parameter is incorrect, an error notification is displayed on the display indicating that an error has been detected.

27. The computer-readable storage medium of claim 19, wherein the one or more programs further comprise instructions for: In response to the request to conduct the transaction, based on the determination that the transaction parameter is in error, updating a displayed characteristic of a displayed user interface element to indicate that the error has been detected.

28. The computer-readable storage medium of claim 19, wherein the one or more programs further comprise instructions for: In response to receiving the request to correct the error: Determining potentially compatible transaction parameters on the wearable electronic device according to the above-mentioned: updating the transaction parameters to include default transaction parameters of the potentially compatible transaction parameters for use in the transaction; and One or more affordances corresponding to one or more respective potentially compatible transaction parameters are displayed on the display.

29. The computer-readable storage medium of claim 28, wherein the one or more programs further comprise instructions for: In response to receiving the request to correct the error: Determining potentially compatible transaction parameters on the wearable electronic device according to the above-mentioned: An input enablement is displayed on the display, the input enablement enabling a user to provide a transaction parameter at the wearable electronic device that is not included in the potentially compatible transaction parameters when activated.

30. The computer-readable storage medium of claim 29, wherein the one or more programs further comprise instructions for: detecting activation of the input affordance; In response to detecting activation of an input affordance, monitoring audio input received via a microphone of the wearable electronic device; and The transaction parameters are updated based on the audio input received via the microphone of the wearable electronic device.

31. The computer-readable storage medium of claim 29, wherein the one or more programs further comprise instructions for: detecting activation of the input affordance; In response to detecting activation of the input affordance, displaying one or more contacts based on contacts stored in a contacts application; receiving a selection of a contact from the one or more contacts; as well as The transaction parameters are updated based on the selected contacts.

32. The computer-readable storage medium of claim 29, wherein the one or more programs further comprise instructions for: detecting activation of the input affordance; In response to detecting activation of the input affordance, transmitting to the companion device a second request for a second transaction parameter input user interface; and Wherein the companion device displays a second indication of the request regarding the second transaction parameter input user interface.

33. The computer readable storage medium according to claim 19, wherein receiving the request to correct the error comprises detecting activation of a displayed error notification; and Activation of the displayed error notification causes the companion application to be displayed on the handheld companion device.

34. The computer-readable storage medium of claim 19, wherein the companion application on the handheld companion device provides a user interface for user input of transaction parameters; wherein the companion application on the handheld companion device receives user input of the transaction parameters using an input device of the handheld companion device that is different from the one or more input devices of the wearable electronic device; and The companion application transmits the received user input of transaction parameters to the wearable electronic device.

35. The computer-readable storage medium of claim 19, wherein the request to conduct the transaction comprises two inputs on hardware buttons of the wearable electronic device.

36. The computer-readable storage medium of claim 19, wherein the one or more programs further comprise instructions for: receiving additional transaction parameters from the handheld companion device after transmitting to the handheld companion device a second request for a transaction parameter user input interface; In response to receiving the additional transaction parameters from the handheld companion device, the displayed potentially compatible transaction parameters are updated based on the additional transaction parameters.

37. A wearable electronic device comprising: monitor; one or more input devices; one or more processors; as well as A memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: Receive a request to conduct a transaction using transaction parameters; In response to the request to conduct the transaction, based on determining that the transaction parameters are erroneous, displaying an error notification on a display of the wearable electronic device indicating that an error has been detected; receiving, via the one or more input devices of the wearable electronic device, a request to correct the error; as well as In response to receiving the request to correct the error: Based on determining that there are potentially compatible transaction parameters on the wearable electronic device, displaying one or more of the potentially compatible transaction parameters on the display; and Based on determining that there are no potentially compatible transaction parameters on the wearable electronic device, displaying on the display instructions to enter additional transaction parameters on a companion application on a handheld companion device different from the wearable electronic device; wherein the handheld companion device includes an input device that is different from one or more input devices of the wearable electronic device; and The companion application is configured to send information to the wearable electronic device.

38. The wearable electronic device of claim 37, wherein the one or more programs further comprise instructions for: In response to the request to conduct the transaction, the transaction is conducted based on a determination that transaction processing criteria have been met, including that the transaction parameters are correct.

39. The wearable electronic device of claim 37, wherein the one or more programs further comprise instructions for: transmitting a request for a transaction parameter input user interface to the companion device; and Wherein the companion device displays an indication of the request regarding the transaction parameter input user interface.

40. A wearable electronic device according to claim 39, wherein the indication of activating the request for the transaction parameter input user interface on the companion device causes the transaction parameter input user interface to be displayed on a display of the companion device.

41. The wearable electronic device of claim 37, wherein the one or more programs further comprise instructions for: receiving corresponding additional transaction parameters; and In response to receiving the corresponding additional transaction parameters, a transaction user interface is updated on the display according to the corresponding additional transaction parameters.

42. The wearable electronic device of claim 41, wherein the one or more programs further comprise instructions for: In response to receiving the transaction parameters, the transaction parameters are updated to include the corresponding additional transaction parameters for use in the transaction.

43. The wearable electronic device of claim 41 , wherein the one or more programs further comprise instructions for: in response to receiving the corresponding additional transaction parameters, displaying an indication of the corresponding additional transaction parameters on the display; and detecting activation of a hardware button of the wearable electronic device while displaying the indication of the corresponding additional transaction parameter; as well as Conducting the transaction for the activity based on determining that the updated transaction parameters including the corresponding additional transaction parameters are correct; as well as Based on determining that the updated transaction parameters are erroneous, a second error notification is displayed on the display indicating that an error has been detected.

44. The wearable electronic device of claim 41, wherein the one or more programs further comprise instructions for: in response to receiving the corresponding additional transaction parameters, displaying on the display an instruction to activate a hardware button of the wearable electronic device to authorize payment for the transaction; detecting activation of the hardware button; as well as In response to detecting activation of the hardware button: Conduct transactions for the activities described, based on a determination that transaction processing criteria have been met, including that updated transaction parameters are correct; as well as Based on determining that the transaction parameter is incorrect, an error notification is displayed on the display indicating that an error has been detected.

45. The wearable electronic device of claim 37, wherein the one or more programs further comprise instructions for: In response to the request to conduct the transaction, based on the determination that the transaction parameter is in error, updating a displayed characteristic of a displayed user interface element to indicate that the error has been detected.

46. ​​The wearable electronic device of claim 37, wherein the one or more programs further comprise instructions for: In response to receiving the request to correct the error: Determining potentially compatible transaction parameters on the wearable electronic device according to the above-mentioned: updating the transaction parameters to include default transaction parameters of the potentially compatible transaction parameters for use in the transaction; and One or more affordances corresponding to one or more respective potentially compatible transaction parameters are displayed on the display.

47. The wearable electronic device of claim 37, wherein the one or more programs further comprise instructions for: In response to receiving the request to correct the error: Determining potentially compatible transaction parameters on the wearable electronic device according to the above-mentioned: An input enablement is displayed on the display, the input enablement enabling a user to provide a transaction parameter at the wearable electronic device that is not included in the potentially compatible transaction parameters when activated.

48. The wearable electronic device of claim 47, wherein the one or more programs further comprise instructions for: detecting activation of the input affordance; In response to detecting activation of an input affordance, monitoring audio input received via a microphone of the wearable electronic device; and The transaction parameters are updated based on the audio input received via the microphone of the wearable electronic device.

49. The wearable electronic device of claim 47, wherein the one or more programs further comprise instructions for: detecting activation of the input affordance; In response to detecting activation of the input affordance, displaying one or more contacts based on contacts stored in a contacts application; receiving a selection of a contact from the one or more contacts; as well as The transaction parameters are updated based on the selected contacts.

50. The wearable electronic device of claim 47, wherein the one or more programs further comprise instructions for: detecting activation of the input affordance; In response to detecting activation of the input affordance, transmitting to the companion device a second request for a second transaction parameter input user interface; and Wherein the companion device displays a second indication of the request regarding the second transaction parameter input user interface.

51. A wearable electronic device according to claim 37, wherein receiving the request to correct the error comprises detecting activation of a displayed error notification; and Activation of the displayed error notification causes the companion application to be displayed on the handheld companion device.

52. The wearable electronic device according to claim 37, wherein the companion application on the handheld companion device provides a user interface for user input of transaction parameters; wherein the companion application on the handheld companion device receives user input of the transaction parameters using an input device of the handheld companion device that is different from the one or more input devices of the wearable electronic device; and The companion application transmits the received user input of transaction parameters to the wearable electronic device.

53. The wearable electronic device of claim 37, wherein the request to conduct the transaction comprises two inputs on hardware buttons of the wearable electronic device.

54. The wearable electronic device of claim 37, wherein the one or more programs further comprise instructions for: receiving additional transaction parameters from the handheld companion device after transmitting to the handheld companion device a second request for a transaction parameter user input interface; In response to receiving the additional transaction parameters from the handheld companion device, the displayed potentially compatible transaction parameters are updated based on the additional transaction parameters.

55. A wearable electronic device configured to communicate with a display and one or more input devices, the wearable electronic device comprising: Apparatus for performing the method according to any one of claims 1-18.

56. A computer program product comprising one or more programs configured to be executed by one or more processors of a computer system in communication with a display and one or more input devices, the one or more programs including instructions for performing the method according to any one of claims 1-18.

Images