User interface for stored value accounts

Abstract

The present invention is entitled "User Interface for Stored Value Accounts". The present disclosure relates to a computer user interface. In some examples, an account is configured onto an electronic device. In some examples, the device receives a value to fund the account configured on the electronic device. In some examples, the electronic device uses the configured account to conduct a transaction with a contactless transaction terminal and displays an indication of the transaction. In some examples, the electronic device transmits information corresponding to the configured account without checking authentication. In some examples, the device receives user input to initiate a process of moving an account from a first device to a second device. In some examples, the device receives account payment credentials from a second device when a set of payment criteria are met.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application is a divisional application of the invention patent application with international application number PCT / US2017 / 049500, international application date August 30, 2017, date of entry into the Chinese national phase February 2, 2018, Chinese national application number 201780002648.4, and invention name “User interface for stored value accounts”.

[0003] This patent application claims priority to U.S. Provisional Patent Application Serial No. 62 / 384,043, filed on September 6, 2016, entitled “USER INTERFACES FOR STORED-VALUE ACCOUNTS,” which is hereby incorporated by reference in its entirety for all purposes.

[0004] This application is related to U.S. patent application serial number 61 / 912,727, filed on December 6, 2013, entitled “PROVISIONING AND AUTHENTICATING CREDENTIALS ON AN ELECTRONIC DEVICE,” and U.S. patent application serial number 62 / 004,837, filed on May 29, 2014, entitled “METHODS FOR MANAGING PAYMENT APPLETS ON A SECUREELEMENT TO CONDUCT MOBILE PAYMENT TRANSACTIONS,” the contents of which are hereby incorporated by reference. Technical Field

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

[0006] In recent years, the use of electronic devices for managing transactions and accounts has increased significantly. Exemplary techniques for managing transactions include participating in information transactions. Exemplary techniques for managing accounts include adding and removing accounts on smartphone devices. Summary of the Invention

[0007] However, some existing technologies for managing transactions and accounts using electronic devices are often cumbersome and inefficient. For example, some existing technologies use complex and time-consuming user interfaces that may include multiple button presses or keystrokes. Another example is that some existing technologies for participating in transactions require the user to provide input to specify an account, unlock the device, or provide authentication during the transaction. These existing technologies require more time than necessary, wasting the user's time and device energy. This latter consideration is particularly important in battery-powered devices.

[0008] Thus, the present technology provides electronic devices with faster, more efficient methods and interfaces for managing transactions and accounts. Such methods and interfaces optionally supplement or replace other methods for managing accounts and transactions. Such methods and interfaces reduce the cognitive burden on users and create more efficient human-computer interfaces. For battery-powered computing devices, such methods and interfaces conserve power and increase the time between battery charges. Furthermore, such methods and interfaces reduce the amount of input required at electronic devices (e.g., smartphones and smartwatches).

[0009] According to some embodiments, a method is described for performing at an electronic device having one or more input devices and one or more short-range communication radio components. The method includes: receiving, by the one or more short-range communication radio components, a card account number of a card having stored value; requesting verification information to verify ownership of the card; receiving input from a user of the electronic device via the one or more input devices, the input including verification information for verifying ownership of the card; verifying ownership of the card by comparing the verification information with independent information about the card received independently of the verification information; and based on determining that the ownership verification is successful: generating a prompt to perform a value transfer operation for value transfer; and in conjunction with the value transfer operation, transferring at least some of the stored value from the card to a virtual card stored on the electronic device.

[0010] 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 one or more input devices and one or more short-range communication radio components, the one or more programs including instructions for performing the following operations: receiving, by the one or more short-range communication radio components, a card account number of a card having stored value; requesting verification information to verify ownership of the card; receiving input from a user of the electronic device via the one or more input devices, the input including verification information for verifying ownership of the card; verifying ownership of the card by comparing the verification information with independent information about the card received independently of the verification information; and based on determining that the ownership verification is successful: generating a prompt to perform a value transfer operation for value transfer; and in conjunction with the value transfer operation, transferring at least some of the stored value from the card to a virtual card stored on the electronic device.

[0011] 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 one or more input devices and one or more short-range communication radio components, the one or more programs including instructions for performing the following operations: receiving, by the one or more short-range communication radio components, a card account number of a card having stored value; requesting verification information to verify ownership of the card; receiving input from a user of the electronic device via the one or more input devices, the input including verification information for verifying ownership of the card; verifying ownership of the card by comparing the verification information with independent information about the card received independently of the verification information; and based on determining that the ownership verification is successful: generating a prompt to perform a value transfer operation for value transfer; and in conjunction with the value transfer operation, transferring at least some of the stored value from the card to a virtual card stored on the electronic device.

[0012] According to some embodiments, an electronic device is described. The electronic device includes: one or more input devices; one or more short-range communication radio components; 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, by the one or more short-range communication radio components, a card account number of a card having stored value; requesting verification information to verify ownership of the card; receiving input from a user of the electronic device via the one or more input devices, the input including verification information for verifying ownership of the card; verifying ownership of the card by comparing the verification information with independent information about the card received independently of the verification information; and based on determining that the ownership verification is successful: generating a prompt to perform a value transfer operation for value transfer; and in conjunction with the value transfer operation, transferring at least some of the stored value from the card to a virtual card stored on the electronic device.

[0013] According to some embodiments, an electronic device is described. The electronic device includes: one or more input devices; one or more short-range communication radio components; a device for performing the following operations: receiving, by the one or more short-range communication radio components, a card account number of a card, wherein the card has stored value; a device for performing the following operations: requesting verification information to verify ownership of the card; a device for performing the following operations: receiving input from a user of the electronic device via the one or more input devices, the input including verification information for verifying ownership of the card; a device for performing the following operations: verifying ownership of the card by comparing the verification information with independent information about the card received independently of the verification information; and a device for performing the following operations: based on determining that the ownership verification is successful, generating a prompt to perform a value transfer operation for value transfer; and in conjunction with the value transfer operation, transferring at least some of the stored value from the card to a virtual card stored on the electronic device.

[0014] According to some embodiments, a method is described for performing at an electronic device having a display, one or more input devices, and one or more short-range communication radio components. The method includes: requesting verification information to verify ownership of a stored-value card, wherein the stored-value card has stored value; receiving input from a user of the electronic device via the one or more input devices, the input including verification information for verifying ownership of the card, wherein the verification information includes information not shown on the card; displaying a prompt on the display of the electronic device to place the electronic device within communication range of the stored-value card; receiving identification information from the stored-value card by the one or more short-range communication radio components; verifying ownership of the stored-value card by comparing the verification information with the identification information; and upon determining that the ownership verification is successful: transferring at least some of the stored value from the stored-value card to a virtual card stored on the electronic device.

[0015] 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 short-range communication radio components, and one or more input devices, the one or more programs including instructions for performing the following operations: requesting verification information to verify ownership of a stored-value card, wherein the stored-value card has stored value; receiving input from a user of the electronic device via the one or more input devices, the input including verification information for verifying ownership of the card, wherein the verification information includes information not shown on the card; displaying a prompt on the display of the electronic device to place the electronic device within communication range of the stored-value card; receiving identification information from the stored-value card by the one or more short-range communication radio components; verifying ownership of the stored-value card by comparing the verification information with the identification information; and based on determining that the ownership verification is successful: transferring at least some of the stored value from the stored-value card to a virtual card stored on the electronic device.

[0016] 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 short-range communication radio components, and one or more input devices, the one or more programs including instructions for performing the following operations: requesting verification information to verify ownership of a stored-value card, wherein the stored-value card has stored value; receiving input from a user of the electronic device via the one or more input devices, the input including verification information for verifying ownership of the card, wherein the verification information includes information not shown on the card; displaying a prompt on the display of the electronic device to place the electronic device within communication range of the stored-value card; receiving identification information from the stored-value card by the one or more short-range communication radio components; verifying ownership of the stored-value card by comparing the verification information with the identification information; and upon determining that the ownership verification is successful: transferring at least some of the stored value from the stored-value card to a virtual card stored on the electronic device.

[0017] According to some embodiments, an electronic device is described. The electronic device includes: a display; one or more short-range communication radio components; 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: requesting verification information to verify ownership of a stored-value card, wherein the stored-value card has stored value; receiving input from a user of the electronic device via the one or more input devices, the input including verification information for verifying ownership of the card, wherein the verification information includes information not shown on the card; displaying a prompt on the display of the electronic device to place the electronic device within communication range of the stored-value card; receiving identification information from the stored-value card by the one or more short-range communication radio components; verifying ownership of the stored-value card by comparing the verification information with the identification information; and based on determining that the ownership verification is successful: transferring at least some of the stored value from the stored-value card to a virtual card stored on the electronic device.

[0018] According to some embodiments, an electronic device is described. The electronic device includes: a display; one or more short-range communication radio components; one or more input devices; means for requesting verification information to verify ownership of a stored-value card, wherein the stored-value card has stored value; means for receiving input from a user of the electronic device via the one or more input devices, the input including verification information for verifying ownership of the card, wherein the verification information includes information not shown on the card; means for displaying a prompt on the display of the electronic device to place the electronic device within communication range of the stored-value card; means for receiving identification information from the stored-value card by the one or more short-range communication radio components; means for verifying ownership of the stored-value card by comparing the verification information with the identification information; and means for transferring at least some of the stored value from the stored-value card to a virtual card stored on the electronic device based on determining that ownership verification is successful.

[0019] 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: displaying a representation of a stored value account on the display, the representation of the stored value account including an activatable top-up option, wherein the electronic device has an electronic wallet application including the stored value account and a payment account; while displaying the representation of the stored value account, detecting activation of the top-up option via the one or more input devices; detecting activation of a funding account option via the one or more input devices to top-up the stored value account using the payment account of the electronic wallet application; while displaying a proposed transaction to add funds from the payment account to the stored value account, receiving authentication information at the electronic device; and in response to receiving the authentication information and based on determining that the authentication information is consistent with registered authentication information for performing payment transactions using the payment account, top-up the stored value account using the payment account.

[0020] 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: displaying a representation of a stored value account on the display, the representation of the stored value account including an activatable top-up option, wherein the electronic device has an electronic wallet application including the stored value account and a payment account; detecting activation of the top-up option via the one or more input devices while displaying the representation of the stored value account; detecting activation of a funding account option via the one or more input devices to top-up the stored value account using the payment account of the electronic wallet application; receiving authentication information at the electronic device while displaying a proposed transaction to add funds from the payment account to the stored value account; and in response to receiving the authentication information and based on determining that the authentication information is consistent with registered authentication information for performing payment transactions using the payment account, top-up the stored value account using the payment account.

[0021] 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: displaying a representation of a stored-value account on the display, the representation of the stored-value account including an activatable top-up option, wherein the electronic device has an electronic wallet application including the stored-value account and a payment account; detecting activation of the top-up option via the one or more input devices while displaying the representation of the stored-value account; detecting activation of a funding account option via the one or more input devices to top-up the stored-value account using the payment account of the electronic wallet application; receiving authentication information at the electronic device while displaying a proposed transaction to add funds from the payment account to the stored-value account; and in response to receiving the authentication information and based on determining that the authentication information is consistent with registered authentication information for performing payment transactions using the payment account, top-up the stored-value account using the payment account.

[0022] 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: displaying a representation of a stored value account on the display, the representation of the stored value account including an activatable top-up option, wherein the electronic device has an electronic wallet application including the stored value account and a payment account; detecting activation of the top-up option via the one or more input devices when the representation of the stored value account is displayed; detecting activation of a funding account option via the one or more input devices to top-up the stored value account using the payment account of the electronic wallet application; receiving authentication information at the electronic device when displaying a proposed transaction to add funds from the payment account to the stored value account; and in response to receiving the authentication information and based on determining that the authentication information is consistent with registered authentication information for performing payment transactions using the payment account, top-up the stored value account using the payment account.

[0023] According to some embodiments, an electronic device is described. The electronic device includes: a display; one or more input devices; means for displaying a representation of a stored-value account on the display, the representation of the stored-value account including an activatable top-up option, wherein the electronic device has an electronic wallet application including the stored-value account and a payment account; means for detecting activation of the top-up option via the one or more input devices when the representation of the stored-value account is displayed; means for detecting activation of a funding account option via the one or more input devices to top-up the stored-value account using the payment account of the electronic wallet application; means for receiving authentication information at the electronic device when displaying a proposed transaction to add funds from the payment account to the stored-value account; and means for, in response to receiving the authentication information and based on determining that the authentication information is consistent with registered authentication information for performing payment transactions using the payment account, top-up the stored-value account using the payment account.

[0024] According to some embodiments, a method is described for execution at an electronic device having a display, one or more short-range communication radio components, and an electronic wallet application including a stored-value account. The method includes: displaying an indication of available credit for the stored-value account on the display; transmitting credentials for the stored-value account to a contactless transaction terminal separate from the electronic device using the one or more short-range communication radio components; and, based on a transaction performed using the credentials for the stored-value account using the contactless transaction terminal, replacing the display of the indication of available credit with the display of an indication corresponding to the transaction in which the credentials were transmitted to the contactless transaction terminal using the one or more short-range communication radio components.

[0025] 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 short-range communication radios, and an electronic wallet application including a stored-value account, the one or more programs including instructions for performing the following operations: displaying an indication of an available balance of a stored-value account on the display; transmitting credentials for the stored-value account to a contactless transaction terminal separate from the electronic device using the one or more short-range communication radios; and, based on a transaction performed using the credentials for the stored-value account using the contactless transaction terminal, replacing the display of the indication of the available balance with the display of an indication corresponding to the transaction in which the credentials were transmitted to the contactless transaction terminal using the one or more short-range communication radios.

[0026] 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 short-range communication radios, and an electronic wallet application including a stored-value account, the one or more programs including instructions for: displaying an indication of available credit for a stored-value account on the display; transmitting credentials for the stored-value account to a contactless transaction terminal separate from the electronic device using the one or more short-range communication radios; and, based on a transaction performed using the credentials for the stored-value account using the contactless transaction terminal, replacing the display of the indication of available credit with the display of an indication corresponding to the transaction in which the credentials were transmitted to the contactless transaction terminal using the one or more short-range communication radios.

[0027] According to some embodiments, an electronic device is described. The electronic device includes: a display; one or more short-range communication radio components; an electronic wallet application including a stored-value account; 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: displaying an indication of an available balance of the stored-value account on the display; transmitting credentials for the stored-value account to a contactless transaction terminal separate from the electronic device using the one or more short-range communication radio components; and replacing the display of the indication of the available balance with the display of an indication corresponding to a transaction in which the credentials were transmitted to the contactless transaction terminal based on a transaction performed using the credentials for the stored-value account using the contactless transaction terminal, wherein the credentials for the stored-value account were transmitted to the contactless transaction terminal using the one or more short-range communication radio components.

[0028] According to some embodiments, an electronic device is described. The electronic device includes: a display; one or more short-range communication radios; an electronic wallet application including a stored-value account; means for displaying on the display an indication of an available balance of the stored-value account; means for transmitting credentials for the stored-value account to a contactless transaction terminal separate from the electronic device using the one or more short-range communication radios; and means for replacing the display of the indication of the available balance with the display of an indication corresponding to a transaction in which the credentials were transmitted to the contactless transaction terminal based on a transaction performed using the credentials for the stored-value account using the contactless transaction terminal, wherein the credentials for the stored-value account were transmitted to the contactless transaction terminal using the one or more short-range communication radios.

[0029] According to some embodiments, a method is described for execution at an electronic device having one or more short-range communication radios and an account information application including a first account. The method includes: detecting a wireless signal by the one or more short-range communication radios; upon determining that the wireless signal corresponds to a first type of request, transmitting information corresponding to the first account without checking for authentication; and upon determining that the wireless signal corresponds to a second type of request, continuing with a transaction corresponding to the wireless signal after checking for authentication.

[0030] 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 one or more short-range communication radio components and an account information application including a first account, the one or more programs including instructions for performing the following operations: detecting a wireless signal by the one or more short-range communication radio components; transmitting information corresponding to the first account without checking for authentication based on determining that the wireless signal corresponds to a first type of request; and continuing a transaction corresponding to the wireless signal after checking for authentication based on determining that the wireless signal corresponds to a second type of request.

[0031] 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 one or more short-range communication radio components and an account information application including a first account, the one or more programs including instructions for performing the following operations: detecting a wireless signal by the one or more short-range communication radio components; transmitting information corresponding to the first account without checking for authentication based on determining that the wireless signal corresponds to a first type of request; and continuing a transaction corresponding to the wireless signal after checking for authentication based on determining that the wireless signal corresponds to a second type of request.

[0032] According to some embodiments, an electronic device is described. The electronic device includes: one or more short-range communication radio components; an account information application including a first account; 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: detecting a wireless signal by the one or more short-range communication radio components; transmitting information corresponding to the first account without checking for authentication based on determining that the wireless signal corresponds to a first type of request; and continuing a transaction corresponding to the wireless signal after checking for authentication based on determining that the wireless signal corresponds to a second type of request.

[0033] According to some embodiments, an electronic device is described. The electronic device includes: one or more short-range communication radio components; an account information application including a first account; means for detecting a wireless signal by the one or more short-range communication radio components; means for transmitting information corresponding to the first account without checking for authentication based on determining that the wireless signal corresponds to a first type of request; and means for continuing a transaction corresponding to the wireless signal after checking for authentication based on determining that the wireless signal corresponds to a second type of request.

[0034] 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: displaying representations of a plurality of devices associated with a user account on the display, wherein the representations of the plurality of devices include a first representation of a first device and a second representation of a second device, wherein the first device is associated with a transaction account and the second device is not associated with the transaction account; receiving a selection corresponding to the displayed representation of the second device via the one or more input devices; and based on receiving the selection corresponding to the displayed representation of the second device: associating the transaction account with the second device; and disassociating the transaction account from the first device.

[0035] 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: displaying representations of multiple devices associated with a user account on the display, wherein the representations of the multiple devices include a first representation of a first device and a second representation of a second device, wherein the first device is associated with a transaction account and the second device is not associated with the transaction account; receiving a selection corresponding to the displayed representation of the second device via the one or more input devices; and based on receiving the selection corresponding to the displayed representation of the second device: associating the transaction account with the second device; and disassociating the transaction account from the first device.

[0036] 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: displaying representations of multiple devices associated with a user account on the display, wherein the representations of the multiple devices include a first representation of a first device and a second representation of a second device, wherein the first device is associated with a transaction account and the second device is not associated with the transaction account; receiving a selection corresponding to the displayed representation of the second device via the one or more input devices; and based on receiving the selection corresponding to the displayed representation of the second device: associating the transaction account with the second device; and disassociating the transaction account from the first device.

[0037] 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: displaying representations of multiple devices associated with a user account on the display, wherein the representations of the multiple devices include a first representation of a first device and a second representation of a second device, wherein the first device is associated with a transaction account and the second device is not associated with the transaction account; receiving a selection corresponding to the displayed representation of the second device via the one or more input devices; and based on receiving the selection corresponding to the displayed representation of the second device: causing the transaction account to become associated with the second device; and causing the transaction account to become disassociated from the first device.

[0038] According to some embodiments, an electronic device is described. The electronic device includes: a display; one or more input devices; means for displaying on the display representations of a plurality of devices associated with a user account, wherein the plurality of device representations include a first representation of a first device and a second representation of a second device, wherein the first device is associated with a transaction account and the second device is not associated with the transaction account; means for receiving, via the one or more input devices, a selection corresponding to the displayed representation of the second device; and means for associating the transaction account with the second device in accordance with receiving the selection corresponding to the displayed representation of the second device; and disassociating the transaction account from the first device.

[0039] According to some embodiments, a method performed at an electronic device having an electronic wallet application is described. The method includes: detecting that a set of one or more payment criteria for making a payment using a stored-value account have been met; in response to detecting that the set of one or more payment criteria for making a payment using the stored-value account have been met, and based on determining that payment credentials for the stored-value account are not available in the electronic wallet application of the electronic device, requesting payment credentials for a stored-value account from a second device different from the electronic device; after requesting the payment credentials for the stored-value account from the second device when the payment credentials for the stored-value account are available at the second device, receiving the payment credentials for the stored-value account from the second device at the electronic device.

[0040] 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 an electronic wallet application, the one or more programs including instructions for performing the following operations: detecting that a set of one or more payment criteria for making a payment using a stored-value account have been met; in response to detecting that a set of one or more payment criteria for making a payment using a stored-value account have been met, and based on determining that payment credentials for the stored-value account are not available in the electronic wallet application of the electronic device, requesting payment credentials for a stored-value account from a second device different from the electronic device; and after requesting the payment credentials for the stored-value account from the second device when the payment credentials for the stored-value account are available at the second device, receiving the payment credentials for the stored-value account from the second device at the electronic device.

[0041] 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 an electronic wallet application, the one or more programs including instructions for performing the following operations: detecting that a set of one or more payment criteria for making a payment using a stored-value account have been met; in response to detecting that a set of one or more payment criteria for making a payment using a stored-value account have been met, and based on determining that payment credentials for the stored-value account are not available in the electronic wallet application of the electronic device, requesting payment credentials for a stored-value account from a second device different from the electronic device; and after requesting the payment credentials for the stored-value account from the second device when the payment credentials for the stored-value account are available at the second device, receiving the payment credentials for the stored-value account from the second device at the electronic device.

[0042] According to some embodiments, an electronic device is described. The electronic device includes: an electronic wallet application; 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: detecting that a set of one or more payment criteria for making a payment using a stored-value account have been met; in response to detecting that a set of one or more payment criteria for making a payment using a stored-value account have been met, and based on determining that payment credentials for the stored-value account are not available in the electronic wallet application of the electronic device, requesting payment credentials for a stored-value account from a second device different from the electronic device; and after requesting the payment credentials for the stored-value account from the second device when the payment credentials for the stored-value account are available at the second device, receiving the payment credentials for the stored-value account from the second device at the electronic device.

[0043] According to some embodiments, an electronic device is described. The electronic device includes an electronic wallet application; means for detecting that a set of one or more payment criteria for making a payment using a stored-value account have been met; means for requesting payment credentials for a stored-value account from a second device different from the electronic device in response to detecting that the set of one or more payment criteria for making a payment using the stored-value account have been met and based on determining that payment credentials for the stored-value account are not available in the electronic wallet application of the electronic device; and means for receiving, at the electronic device, payment credentials for the stored-value account from the second device after requesting the payment credentials for the stored-value account from the second device when the payment credentials for the stored-value account are available at the second device.

[0044] According to some embodiments, an electronic device is described. The electronic device includes: one or more input device units; one or more short-range communication radio units; and a processing unit coupled to the one or more input device units and the one or more short-range communication radio units, the processing unit being configured to: receive a card account number of a card having stored value by the one or more short-range communication radio units; request verification information to verify ownership of the card; receive input from a user of the electronic device via the one or more input device units, the input including verification information for verifying ownership of the card; verify ownership of the card by comparing the verification information with independent information about the card received independently of the verification information; and based on determining that ownership verification is successful: generate a prompt to perform a value transfer operation for value transfer; and in conjunction with the value transfer operation, transfer at least some of the stored value from the card to a virtual card stored on the electronic device.

[0045] According to some embodiments, an electronic device is described. The electronic device includes: a display unit; one or more input device units; one or more short-range communication radio units; and a processing unit coupled to the display unit, the one or more short-range communication radio units, and the one or more input device units, the processing unit being configured to: request verification information to verify ownership of a stored-value card, wherein the stored-value card has stored value; receive input from a user of the electronic device via the one or more input device units, the input including verification information for verifying ownership of the card, wherein the verification information includes information not shown on the card; enable display of a prompt on the display unit of the electronic device to place the electronic device within communication range of the stored-value card; receive identification information from the stored-value card by the one or more short-range communication radio units; verify ownership of the stored-value card by comparing the verification information with the identification information; and based on determining that the ownership verification is successful: transfer at least some of the stored value from the stored-value card to a virtual card stored on the electronic device.

[0046] 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 coupled to the display unit and the one or more input device units, the processing unit being configured to: enable display of a representation of a stored value account on the display unit, the representation of the stored value account including an activatable top-up option, wherein the electronic device has an electronic wallet application including a stored value account and a payment account; upon enabling display of the representation of the stored value account, detect activation of the top-up option via the one or more input device units; detect activation of a funding account option via the one or more input device units to top-up the stored value account using the payment account of the electronic wallet application; upon enabling display of a proposed transaction to add funds from the payment account to the stored value account, receive authentication information at the electronic device; and in response to receiving the authentication information and based on determining that the authentication information is consistent with registered authentication information for performing payment transactions using the payment account, top-up the stored value account using the payment account.

[0047] According to some embodiments, an electronic device is described. The electronic device includes: a display unit; one or more short-range communication radios; an electronic wallet application unit including a stored-value account; and a processing unit coupled to the display unit, the one or more short-range communication radios, and the electronic wallet application unit including the stored-value account, the processing unit being configured to: enable display of an indication of an available balance of the stored-value account on the display unit; transmit credentials for the stored-value account to a contactless transaction terminal separate from the electronic device using the one or more short-range communication radios; and, based on a transaction performed using the credentials for the stored-value account using the contactless transaction terminal, replace the display of the indication of the available balance with display of an indication corresponding to the transaction in which the credentials were transmitted to the contactless transaction terminal using the one or more short-range communication radios.

[0048] According to some embodiments, an electronic device is described. The electronic device includes: one or more short-range communication radio units; an account information application unit including a first account; and a processing unit coupled to the one or more short-range communication radio units and the account information application unit including the first account, the processing unit being configured to: detect a wireless signal by the one or more short-range communication radio units; upon determining that the wireless signal corresponds to a first type of request, transmit information corresponding to the first account without checking for authentication; and upon determining that the wireless signal corresponds to a second type of request, continue with a transaction corresponding to the wireless signal after checking for authentication.

[0049] 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 coupled to the display unit and the one or more input device units, the processing unit being configured to: enable display of representations of multiple devices associated with a user account on the display unit, wherein the multiple devices include a first representation of a first device and a second representation of a second device, wherein the first device is associated with a transaction account and the second device is not associated with the transaction account; receive a selection corresponding to the displayed representation of the second device via the one or more input device units; and based on receiving the selection corresponding to the displayed representation of the second device: cause the transaction account to become associated with the second device; and cause the transaction account to be separated from the first device.

[0050] According to some embodiments, an electronic device is described. The electronic device includes an electronic wallet application unit and a processing unit configured to: detect that a set of one or more payment criteria for making a payment using a stored-value account has been met; in response to detecting that the set of one or more payment criteria for making a payment using the stored-value account has been met and based on determining that payment credentials for the stored-value account are not available in the electronic wallet application of the electronic device, request payment credentials for a stored-value account from a second device different from the electronic device; and after requesting the payment credentials for the stored-value account from the second device when the payment credentials for the stored-value account are available at the second device, receive the payment credentials for the stored-value account from the second device at the electronic device.

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

[0052] Thus, devices are provided with faster, more efficient methods and interfaces 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

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

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

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

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

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

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

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

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

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

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

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

[0064] Figure 6 Illustrated are example devices connected via one or more communication channels according to some embodiments.

[0065] Figures 7A to 7P An exemplary user interface for configuring a card onto an electronic device according to some embodiments is shown.

[0066] Figures 8A to 8B is a flowchart illustrating a method of configuring a card onto an electronic device according to some embodiments.

[0067] Figures 9A to 9N An exemplary user interface for configuring a card onto an electronic device according to some embodiments is shown.

[0068] Figure 10 is a flowchart illustrating a method of configuring a card onto an electronic device according to some embodiments.

[0069] Figures 11A to 11N An exemplary user interface for recharging a stored-value account provided on an electronic device is shown according to some embodiments.

[0070] FIG. 12A to FIG. 12B is a flow chart illustrating a method of recharging a stored-value account provided on an electronic device according to some embodiments.

[0071] Figures 13A to 13N An exemplary user interface for transmitting credentials for a stored-value account to a terminal is shown.

[0072] FIG. 14A to FIG. 14B is a flow chart illustrating a method of transmitting credentials for a stored-value account to a terminal according to some embodiments.

[0073] Figures 15A to 15M An exemplary user interface is shown for making an account available for use without checking authentication according to some embodiments.

[0074] 16A to 16B is a flowchart illustrating a method of making an account available for use without checking authentication according to some embodiments.

[0075] 17A to 17H An exemplary user interface for moving a transaction account from one device to another is shown, according to some embodiments.

[0076] Figure 18 is a flow chart illustrating a method of moving a transaction account from one device to another, according to some embodiments.

[0077] Figures 19A to 19H An exemplary user interface is shown for accounts available at one or more of multiple devices according to some embodiments.

[0078] FIG. 20A to FIG. 20B is a flowchart illustrating a method of managing accounts available at one or more of a plurality of devices according to some embodiments.

[0079] Figures 21 to 27 A functional block diagram according to some embodiments is shown. DETAILED DESCRIPTION

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

[0081] Electronic devices need to provide more efficient methods and interfaces for managing accounts and transactions. Such technologies can reduce the cognitive burden on users conducting transactions, thereby improving productivity. Furthermore, such technologies can reduce processor and battery power that would otherwise be wasted on redundant user input.

[0082] under Figure 1A to Figure 1B 、 Figure 2 、 Figure 3 、 Figures 4A to 4B and Figures 5A to 5H A description of an exemplary apparatus for performing techniques for managing accounts and transactions is provided. Figure 6 Illustrated are example devices connected via one or more communication channels according to some embodiments. Figures 7A to 7P An exemplary user interface for configuring a card onto an electronic device according to some embodiments is shown. Figures 8A to 8B is a flowchart illustrating a method of configuring a card onto an electronic device according to some embodiments. Figures 7A to 7PThe user interface in the Figures 8A to 8B The process is described below. Figures 9A to 9N An exemplary user interface for configuring a card onto an electronic device according to some embodiments is shown. Figure 10 is a flowchart illustrating a method of configuring a card onto an electronic device according to some embodiments. Figures 9A to 9N The user interface is used to show the Figure 10 The process is described below. Figures 11A to 11N An exemplary user interface for recharging a stored-value account provided on an electronic device is shown according to some embodiments. FIG. 12A to FIG. 12B is a flow chart illustrating a method of recharging a stored-value account provided on an electronic device according to some embodiments. Figures 11A to 11N The user interface in the FIG. 12A to FIG. 12B The process is described below. Figures 13A to 13N An exemplary user interface for transmitting credentials for a stored-value account to a terminal is shown. FIG. 14A to FIG. 14B is a flow chart illustrating a method of transmitting credentials for a stored-value account to a terminal according to some embodiments. Figures 13A to 13N The user interface in the FIG. 14A to FIG. 14B The process is described below. Figures 15A to 15M An exemplary user interface is shown for making an account available for use without checking authentication according to some embodiments. 16A to 16B is a flowchart illustrating a method of making an account available for use without checking authentication according to some embodiments. Figures 15A to 15M The user interface in the 16A to 16B The process is described below. 17A to 17H An exemplary user interface for moving a transaction account from one device to another is shown, according to some embodiments. Figure 18 is a flow chart illustrating a method of moving a transaction account from one device to another, according to some embodiments. 17A to 17H The user interface is used to show the Figure 18 The process is described below. Figures 19A to 19H An exemplary user interface is shown for accounts available at one or more of multiple devices according to some embodiments. FIG. 20A to FIG. 20B is a flowchart illustrating a method of managing accounts available at one or more of a plurality of devices according to some embodiments. Figures 19A to 19H The user interface in the FIG. 20A to FIG. 20B The process is described below. Figures 21 to 27 A functional block diagram according to some embodiments is shown.

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

[0084] The terms used in the description of the various described embodiments herein are for the purpose of describing specific embodiments only and are not intended to be limiting. As used in the description of the various described embodiments and in the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the terms "and / or" used herein refer to and encompass any and all possible combinations of one or more of the items listed in association. It will also be understood that the terms "includes", "including", "comprises", and / or "comprising" when used in this specification specify the presence of stated features, integers, steps, operations, elements, and / or parts, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, parts, and / or groupings thereof.

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

[0086] 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 music player functions. Exemplary embodiments of portable multifunction devices include, but are not limited to, the Apple Watch 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 touch pads), are optionally used. It should also be understood that in some embodiments, the device is not a portable communication device, but rather a desktop computer with a touch-sensitive surface (e.g., touch screen displays and / or touch pads).

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

[0088] The device typically supports a variety of applications, such as one or more of the following applications: 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 telephony 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.

[0089] 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 applications and / or adjusted and / or varied within the respective applications. In this way, the common physical architecture of the device (such as the touch-sensitive surface) optionally supports various applications with a user interface that is intuitive and clear to the user.

[0090] Attention is now directed to embodiments of portable devices having touch-sensitive displays. Figure 1Ais a block diagram illustrating a portable multifunction device 100 with a touch-sensitive display system 112 according to some embodiments. Touch-sensitive display 112 is sometimes referred to as a "touch screen" for convenience, and may sometimes be referred to as or referred to as a "touch-sensitive display system." Device 100 includes 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, RF circuitry 108, audio circuitry 110, a speaker 111, a microphone 113, an input / output (I / O) subsystem 106, other input control devices 116, and external ports 124. Device 100 optionally includes one or more optical sensors 164. Device 100 optionally includes one or more contact force sensors 165 for detecting the intensity of contacts on device 100 (e.g., a touch-sensitive surface such as touch-sensitive display system 112 of device 100). Device 100 optionally includes one or more tactile output generators 167 for generating 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.

[0091] 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) for the force or pressure of a contact on the touch-sensitive surface. The intensity of a contact has a range of values ​​that includes at least four different values ​​and more typically includes hundreds of different values ​​(e.g., at least 256). The intensity of a contact is optionally determined (or measured) using 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, the 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 adjacent to the contact and / or its change, and / or the resistance of the touch-sensitive surface adjacent to the contact and / or its change are optionally used as a surrogate for the force or pressure of the contact on the touch-sensitive surface. In some embodiments, the surrogate measure of contact force or pressure is used directly to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the surrogate measure). In some embodiments, the surrogate measure of contact force or pressure is converted into an estimated force or pressure, and the estimated force or pressure is used to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure). Using the intensity of the contact as an attribute of the user input allows the user to access additional device functionality that the user may not otherwise be able to access on a smaller device with limited real estate for displaying indications (e.g., on a touch-sensitive display) and / or receiving user input (e.g., via a touch-sensitive display, touch-sensitive surface, or physical / mechanical controls such as knobs or buttons).

[0092] 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 a device (e.g., a touch-sensitive surface) relative to another component of the device (e.g., a housing), or a displacement of a component relative to the center of mass of the device that will be detected by a user using the user's sense of touch. For example, when a device or a component of the device is in contact with a surface that is touch-sensitive to a user (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 that corresponds 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" on 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 was physically pressed (e.g., displaced) by the user's movement does not move. As another example, even when the smoothness of the touch-sensitive surface does not change, movement of the touch-sensitive surface may optionally be interpreted or sensed by the user as "roughness" of the touch-sensitive surface. While such interpretation of touch by the user will be limited by the user's individualized sensory perceptions, there are many sensory perceptions of touch that are common to most users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., "up click," "down click," "roughness"), unless otherwise stated, the generated tactile output corresponds to a physical displacement of the device or a component thereof that would generate the described sensory perception for a typical (or average) user.

[0093] It should be understood that device 100 is only one example of a portable multifunction device and that device 100 optionally has more or fewer components than 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 FIG. 5 are implemented in hardware, software, or a combination of hardware and software, including one or more signal processing circuits and / or application specific integrated circuits.

[0094] Memory 102 optionally includes high-speed random access memory and optionally 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 access to memory 102 by other components of device 100.

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

[0096] RF (radio frequency) circuitry 108 receives and transmits RF signals, also known as electromagnetic signals. RF circuitry 108 converts electrical signals into / from electromagnetic signals and communicates with a communication network and other communication devices via the electromagnetic signals. RF circuitry 108 optionally includes well-known circuitry for performing these functions, including but not limited to an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a codec chipset, a subscriber identity module (SIM) card, memory, and the like. RF circuitry 108 optionally communicates with a network and other devices via wireless communications, such as the Internet (also known as the World Wide Web (WWW)), an intranet, and / or a wireless network (such as a cellular telephone network, a wireless local area network (LAN), and / or a metropolitan area network (MAN)). RF circuitry 108 optionally includes well-known circuitry for detecting near-field communication (NFC) fields, such as via a short-range communication radio. The 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.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 Leveraging Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), and / or Short Message Service (SMS), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document.

[0097] 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 humans. 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 headset 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 with both output (e.g., single or dual ear headphones) and input (e.g., a microphone).

[0098] The I / O subsystem 106 couples input / output peripherals on the device 100, such as the touch screen 112 and other input control devices 116, to a peripherals 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 / to other input control devices 116. The other input control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slide switches, joysticks, click wheels, etc. In some alternative embodiments, the 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. The one or more buttons (e.g., Figure 2 208) optionally includes an up / down button for volume control of the speaker 111 and / or microphone 113. The one or more buttons optionally include a push button (e.g., Figure 2 206 in ).

[0099] 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 December 23, 2005, entitled "Unlocking a Device by Performing Gestures on an Unlock Image," also known as U.S. Patent 7,657,849, which is incorporated herein by reference in its entirety. A longer press of the push button (e.g., 206) optionally turns the device 100 on or off. The function of one or more of the buttons can optionally be customized by the user. The touch screen 112 is used to implement virtual or soft buttons and one or more soft keyboards.

[0100] The touch-sensitive display 112 provides an input interface and an output interface between the device and the user. The display controller 156 receives electrical signals from the touch screen 112 and / or sends electrical signals to the touch screen 112. The touch screen 112 displays visual output to the user. The visual output 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.

[0101] The touch screen 112 has a touch-sensitive surface, sensor, or set of sensors that accepts input from the 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 that 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.

[0102] 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 one exemplary embodiment, projected mutual capacitance sensing technology is used, such as that used in the Apple Inc. (Cupertino, California) and iPod Technology found in.

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

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

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

[0106] 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 separate from the touch screen 112 or an extension of the touch-sensitive surface formed by the touch screen.

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

[0108] Device 100 optionally also includes one or more optical sensors 164 . Figure 1AAn optical sensor is shown coupled to the optical sensor controller 158 in the I / O subsystem 106. 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 from the environment projected through one or more lenses 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 still images or video. In some embodiments, the optical sensor is located on the rear of the device 100, facing away from the touch screen display 112 on the front of the device, enabling the touch screen display to be used as a viewfinder for still and / or video image acquisition. In some embodiments, the optical sensor is located on the front of the device, allowing the user to optionally capture an image of the user while viewing 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), allowing a single optical sensor 164 to be used with the touch screen display for both video conferencing and still and / or video image acquisition.

[0109] Device 100 optionally also includes one or more contact intensity sensors 165 . Figure 1A A contact force sensor is shown coupled to force sensor controller 159 in 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 a 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 with 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 back of device 100 opposite touch screen display 112 located on the front of device 100.

[0110] 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 optionally implements as described in the following U.S. patent applications: U.S. patent application Ser. No. 11 / 241,839, entitled “Proximity Detector In Handheld Device”; U.S. patent application Ser. No. 11 / 240,788, entitled “Proximity Detector In Handheld Device”; U.S. patent application Ser. No. 11 / 620,702, entitled “Using Ambient Light Sensor To Augment Proximity Sensor Output”; U.S. patent application Ser. No. 11 / 586,862, entitled “Automated Response To And Sensing Of User Activity In Portable Devices”; and U.S. patent application Ser. No. 11 / 638,251, entitled “Methods And Systems For Automatic Configuration Of Peripherals,” which are incorporated herein by reference in their entireties. 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.

[0111] 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 speakers or other audio components; and / or electromechanical devices for converting energy into linear motion such as motors, solenoids, electroactive polymers, piezoelectric actuators, electrostatic actuators, or other tactile output generating components (e.g., components for converting electrical signals into tactile outputs on the device). The contact force sensor 165 receives tactile feedback generation instructions from the tactile feedback module 133 and generates tactile outputs on the device 100 that can be felt by the user of the device 100. In some embodiments, at least one tactile output generator is juxtaposed or adjacent to a touch-sensitive surface (e.g., touch-sensitive display system 112) and optionally generates tactile outputs by moving the touch-sensitive surface vertically (e.g., inward / outward toward the surface of the device 100) or laterally (e.g., back and forth 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.

[0112] 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: U.S. Patent Publication 20050190059, entitled "Acceleration-based Theft Detection System for Portable Electronic Devices" and U.S. Patent Publication 20060017692, entitled "Methods And Apparatuses For Operating A Portable Device Based On An Accelerometer," both of which are incorporated herein 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 accelerometer 168 for obtaining information about the position and orientation (e.g., portrait or landscape) of device 100.

[0113] 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 indicating which application, if any, is currently active; a display state indicating 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 regarding the device's position and / or posture.

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

[0115] 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 ports 124. The external ports 124 (e.g., Universal Serial Bus (USB), FireWire, etc.) are suitable for coupling directly to other devices or indirectly through a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external ports are connected to (trademark of Apple Inc.) devices.

[0116] The contact / motion module 130 optionally detects contact with the touch screen 112 (in conjunction with the display controller 156) and other touch-sensitive devices (e.g., a touchpad or 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 down event), determining the strength of the contact (e.g., the force or pressure of the contact, or a surrogate for the force or pressure of the contact), determining whether there has been movement of the contact and tracking movement across the touch-sensitive surface (e.g., detecting one or more finger drag events), and determining whether the contact has ceased (e.g., detecting a finger lift event or contact break). 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, with the movement of the contact point 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 contact simultaneously (e.g., "multi-touch" / multiple-finger contact). In some embodiments, the contact / motion module 130 and display controller 156 detect contact on the touchpad.

[0117] In some embodiments, the contact / motion module 130 uses a set of one or more intensity thresholds to determine whether an 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 are 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 the touchpad or touchscreen display 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).

[0118] The contact / motion module 130 optionally detects gesture input from 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). Thus, 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.

[0119] The graphics module 132 includes various known software components for rendering 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.

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

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

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

[0123] 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 a weather widget, local pages widget, and map / navigation widget).

[0124] Application 136 optionally includes the following modules (or instruction sets), or a subset or superset thereof:

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

[0126] Telephone module 138;

[0127] Video conferencing module 139;

[0128] Email client module 140;

[0129] Instant messaging (IM) module 141;

[0130] Fitness support module 142;

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

[0132] Image management module 144;

[0133] Video player module;

[0134] Music player module;

[0135] Browser module 147;

[0136] Calendar module 148;

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

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

[0139] Search module 151;

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

[0141] Notepad module 153;

[0142] Map module 154; and / or

[0143] Online video module 155.

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

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

[0146] 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 character sequence corresponding to a phone number, access one or more phone numbers in contacts module 137, modify an entered phone number, dial the 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.

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

[0148] In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, email client module 140 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.

[0149] In conjunction with the RF circuitry 108, the touch screen 112, the display controller 156, the contact / motion module 130, the graphics module 132, and the text input module 134, the instant messaging module 141 includes executable instructions for entering a character sequence corresponding to an instant message, modifying previously entered characters, transmitting the corresponding instant message (e.g., using the 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 instant messages, and viewing received instant messages. In some embodiments, the transmitted and / or received instant messages optionally include 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).

[0150] 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 workout (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 fitness music and playing it; and displaying, storing, and transmitting fitness data.

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

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

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

[0154] 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 a calendar and data associated with the calendar (e.g., calendar entries, to-do items, etc.) in accordance with user instructions.

[0155] 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 HTML (Hypertext Markup Language) files, CSS (Cascading Style Sheets) files, and JavaScript files. In some embodiments, the desktop widget includes XML (Extensible Markup Language) files and, JavaScript files (e.g., the Yahoo! desktop widget).

[0156] 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., to transfer a user-specified portion of a web page into a desktop widget).

[0157] 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, videos 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.

[0158] 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.).

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

[0160] In combination with the RF circuitry 108, touch screen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147, 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.

[0161] 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 allowing a user to access, browse, receive (e.g., by streaming and / or downloading), play back (e.g., on the touch screen or on an external display connected via external port 124), send emails with links to specific online videos, and otherwise manage online videos in one or more file formats such as H.264. In some embodiments, instant messaging module 141 is used instead of email client module 140 to send links to specific online videos. Additional descriptions of online video applications can be found in U.S. provisional patent application 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 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.

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

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

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

[0165] Figure 1B is a block diagram illustrating exemplary components for event processing according to some embodiments. In some embodiments, memory 102 ( Figure 1A ) or memory 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).

[0166] 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 an event monitor 171 and an event dispatcher module 174. In some embodiments, application 136-1 includes an application internal state 192 that indicates one or more current application views displayed on 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.

[0167] 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 application 136-1 resumes execution, user interface state information indicating information being displayed by application 136-1 or information ready for display by application 136-1, a state queue for enabling a user to return to a previous state or view of application 136-1, and a redo / undo queue of previous actions taken by the user.

[0168] Event monitor 171 receives event information from peripherals interface 118. The event information includes information about sub-events (e.g., a user touch on touch-sensitive display 112 as part of a multi-touch gesture). Peripherals interface 118 transmits information it receives from I / O subsystem 106 or sensors such as proximity sensor 166, one or more accelerometers 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.

[0169] 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).

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

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

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

[0173] Hit view determination module 172 receives information related to sub-events of a contact-based gesture. When an application has multiple views organized in a hierarchy, hit view determination module 172 identifies a hit view as the lowest view in the hierarchy where sub-events should be processed. In most cases, the hit view is the lowest-level view in which an 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 for which it was identified as the hit view.

[0174] 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 therefore determines that all actively participating views should receive a particular sequence of sub-events. In other embodiments, even if a touch sub-event is completely confined to an area associated with one particular view, views higher in the hierarchy will still remain actively participating views.

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

[0176] 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 part of another module stored in memory 102, such as contact / motion module 130.

[0177] In some embodiments, application 136-1 includes multiple event handlers 190 and one or more application views 191, each of which includes instructions for handling touch events that occur within a corresponding view of the application's user interface. 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 of event recognizers 180 are part of a separate module, such as a user interface toolkit (not shown) or a higher-level object from which application 136-1 inherits methods and other properties. In some embodiments, 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 the application internal state 192. Alternatively, one or more of the application views in application view 191 include one or more corresponding event handlers 190. Additionally, in some embodiments, one or more of data updater 176, object updater 177, and GUI updater 178 are included in the corresponding application view 191.

[0178] 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).

[0179] The event receiver 182 receives event information from the event classifier 170. The event information includes information about sub-events such as touches or touch movements. Depending on the sub-event, the event information also includes additional information, such as the location of the sub-event. When the sub-event involves the movement of a touch, the event information optionally also includes the rate and direction of the sub-event. In some embodiments, the event includes a rotation of the device from one orientation to another (e.g., from a portrait orientation to a landscape orientation, or vice versa), and the event information includes corresponding information about the current orientation of the device (also referred to as the device posture).

[0180] The event comparator 184 compares the event information with predefined event or sub-event definitions and, based on the comparison, determines the event or sub-event, or determines or updates the state of the event or sub-event. In some embodiments, the event comparator 184 includes an event definition 186. The 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, the sub-events in event (187) include, for example, touch start, touch end, touch move, touch cancel, and multi-touch. In one example, the definition of event 1 (187-1) is a double-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 (touch end) of a predetermined duration, a second touch (touch start) of a predetermined duration on a displayed object, and a second lift (touch end) of a predetermined duration. In another example, the definition for 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.

[0181] In some embodiments, event definition 187 includes definitions of events for corresponding 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 that displays three user interface objects on touch 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 that is associated with the sub-event and the object that triggered the hit test.

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

[0183] 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 the 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.

[0184] In some embodiments, corresponding event recognizers 180 include metadata 183 having configurable properties, flags, and / or lists that indicate how the event delivery system should perform sub-event delivery for actively participating event recognizers. In some embodiments, metadata 183 includes configurable properties, flags, and / or lists that indicate how event recognizers 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.

[0185] 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 an event handler 190 is different from sending (and deferred sending) sub-events to the corresponding hit view. In some embodiments, the event recognizer 180 throws a flag associated with the identified event, and the event handler 190 associated with the flag obtains the flag and performs a predefined process.

[0186] 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 the sub-event series or to an actively participating view. The event handler associated with the sub-event series or with the actively participating view receives the event information and performs a predetermined process.

[0187] 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 location 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.

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

[0189] It should be understood that the above discussion of event handling for user touches on a touch-sensitive display also applies to other forms of user input for operating the multifunction device 100 using input devices, not all of which are initiated on the touch screen. For example, mouse movement and mouse button presses, optionally combined with single or multiple keyboard presses or holds; contact movement on a touchpad, such as taps, drags, scrolls, etc.; stylus input; movement of the device; spoken commands; detected eye movement; biometric input; and / or any combination thereof, optionally used as input corresponding to a sub-event defining an event to be recognized.

[0190] Figure 2A portable multifunction device 100 with a touch screen 112 is shown according to some embodiments. 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 the graphics by making gestures on the graphics, for example, using one or more fingers 202 (not drawn to scale in the figures) or using one or more styluses 203 (not drawn to scale in the figures). In some embodiments, selection of the one or more graphics occurs when the user breaks contact with the one or more graphics. In some embodiments, the gesture optionally includes one or more taps, one or more swipes (from left to right, from right to left, up and / or down), and / or rolling of a finger that has made contact with the device 100 (from right to left, from left to right, up and / or down). In some implementations or in some cases, inadvertent contact with a graphic does not select the graphic. For example, a swipe gesture that sweeps over an application icon optionally does not select the corresponding application when the gesture corresponding to selection is a tap.

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

[0192] 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 subscriber identity module (SIM) card slot 210, a headset jack 212, and a docking / charging external port 124. The push button 206 is optionally used to: power the device on / off by pressing the button and holding it in a depressed state for a predetermined time; lock the device by pressing the button and releasing it before a predetermined time has passed; 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 via the microphone 113. The device 100 also optionally includes one or more contact force sensors 165 for detecting the intensity of contact on the touch screen 112, and / or one or more tactile output generators 167 for generating tactile output for the user of the device 100.

[0193] Figure 33 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface according to some embodiments. The device 300 does not have to be portable. In some embodiments, the device 300 is a laptop computer, a desktop computer, a tablet computer, a multimedia player device, a navigation device, an educational device (such as a children's learning toy), a gaming 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 a circuit system (sometimes called a chipset) that interconnects the system components and controls communication between the 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 pointing 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 referenced devices). 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 may include one or more storage devices located remotely from the CPU 310. In some embodiments, the memory 370 stores data stored in 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.

[0194] Figure 3Each element in the above-mentioned elements in is optionally stored in one or more memory devices of the memory device mentioned previously.Each module in the above-mentioned modules corresponds to the instruction set for performing the above-mentioned functions.Above-mentioned modules or programs (for example, instruction set) 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 above-mentioned modules and data structure.In addition, memory 370 optionally stores other modules and data structure not described above.

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

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

[0197] Signal strength indicators 402 for wireless communications (such as cellular and Wi-Fi signals);

[0198] Time 404;

[0199] Bluetooth indicator 405;

[0200] Battery status indicator 406;

[0201] A tray 408 with icons for commonly used applications, such as:

[0202] 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;

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

[0204] o an icon 420 labeled "Browser" of the browser module 147; and

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

[0206] Icons for other applications, such as:

[0207] o Icon 424 of the IM module 141 labeled “Messages”;

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

[0209] o an icon 428 labeled “Photos” of the image management module 144;

[0210] o an icon 430 labeled “Camera” of the camera module 143;

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

[0212] o Icon 434 labeled “Stock Market” of the Stock Market widget 149-2;

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

[0214] o Icon 438 labeled “Weather” of the weather widget 149-1;

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

[0216] o Icon 442 of the exercise support module 142 labeled “Exercise Support”;

[0217] o an icon 444 of the Notes module 153 labeled "Notes"; and

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

[0219] Please note that Figure 4A The icon labels shown in are exemplary only. For example, icon 422 for 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 respective application icon includes the name of the application corresponding to the respective application icon. In some embodiments, the label of a particular application icon is different from the name of the application corresponding to the particular application icon.

[0220] Figure 4B A touch-sensitive surface 451 (eg, touch screen display 112) is shown having a touch-sensitive surface 451 (eg, touch screen display 112) that is separate from a display 450 (eg, touch screen display 112). Figure 3 tablet or touchpad 355) of the 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 contacts on touch-sensitive surface 451, and / or one or more tactile output generators 357 for generating tactile output for a user of device 300.

[0221] Although some of the examples below will be given with reference to input on a touch screen display 112 (where the touch-sensitive surface and display are combined), in some embodiments, the device detects input on a touch-sensitive surface that is separate from the display, 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 main 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 ) at contact with touch-sensitive surface 451 (eg, Figure 4B 460 and 462 in ). Thus, on a touch-sensitive surface (e.g., Figure 4B 451) and the display of the multi-function device ( Figure 4B When the user interface 450 in FIG. 1 is separated, the user input detected by the device on the touch-sensitive surface (e.g., contacts 460 and 462 and their movement) is used by the device to manipulate the user interface on the display. It should be understood that similar methods are optionally used for other user interfaces described herein.

[0222] 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). For 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 detection of contact, and then 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 mice and finger contacts are optionally used simultaneously.

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

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

[0225] In some embodiments, the device 500 has one or more input mechanisms 506 and 508. Input mechanisms 506 and 508 (if included) can be physical. Examples of physical input mechanisms include push buttons and rotatable mechanisms. In some embodiments, 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, wristbands, pants, belts, shoes, wallets, backpacks, etc. These attachment mechanisms allow the device 500 to be worn by the user.

[0226] 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 that operatively couples an I / O portion 514 to one or more computer processors 516 and a memory 518. The I / O portion 514 can be connected to a display 504, which can 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 can 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 examples, the input mechanism 508 is optionally a button.

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

[0228] The memory 518 of the personal electronic device 500 may include one or more non-transitory computer-readable storage media for storing computer-executable instructions that, when executed by one or more computer processors 516, may cause the computer processors to perform the following techniques, including processes 800, 1000, 1200, 1400, 1600, 1800, and 2000. The personal electronic device 500 is not limited to Figure 5B Rather, the components and configurations may include other components or additional components in various configurations.

[0229] As used herein, the term "indicator" refers to an indication that is optionally provided on device 100, 300, and / or 500 ( Figure 1A to Figure 1B 、 Figure 3 and Figures 5A to 5H ) 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.

[0230] As used herein, the term "focus selector" refers to an input element used to indicate the current portion of a user interface with which a user is interacting. 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 FIG, the particular user interface element is adjusted according to the detected input. In the case of a touch screen display (e.g., a touch screen display) that enables direct interaction with user interface elements on the touch screen display Figure 1A touch-sensitive display system 112 or Figure 4A In 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 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 according to 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 focus from one button to another); in these implementations, the focus selector moves according to the movement of focus between different areas of the user interface. Regardless of the specific form the focus selector takes, the focus selector is generally a user interface element (or 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 touchpad 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's display).

[0231] As used in the specification and claims, the term "characteristic intensity" of a contact refers to a characteristic of the 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 sampled 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, before or after contact begins to move, before contact ends, before or after contact is detected to increase in intensity, and / or before or after contact is detected to decrease in intensity). The characteristic intensity of a contact is optionally based on one or more of the following: the maximum value of the contact intensity, the mean value of the contact intensity, the average value of the contact intensity, the value at the top 10% of the contact intensity, the half-maximum value of the contact intensity, the 90% maximum value of the contact intensity, etc. In some embodiments, the duration of the contact is used in determining the characteristic intensity (e.g., when the characteristic intensity is the average value of the intensity of the contact over time). In some embodiments, the characteristic intensity is compared to a set of one or more intensity thresholds to determine whether the user has performed an operation. For example, the set of one or more intensity thresholds optionally includes a first intensity threshold and a second intensity threshold. In this example, a contact whose characteristic intensity does not exceed the first threshold causes a first operation, a contact whose characteristic intensity exceeds the first intensity threshold but does not exceed the second intensity threshold causes a second operation, and a contact whose characteristic intensity exceeds the second threshold causes a third operation. In some embodiments, a comparison between the characteristic intensity and one or more thresholds is used to determine whether to perform one or more operations (e.g., whether to perform the corresponding operation or give up performing the corresponding operation), rather than to determine whether to perform the first operation or the second operation.

[0232] Figure 5C Detecting multiple contacts 552A-552E on touch-sensitive display 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 example, the intensity measurements of intensity sensors 524A and 524D are both 9 intensity units, and the intensity measurements of intensity sensors 524B and 524C are both 7 intensity units. In some implementations, the cumulative intensity is the sum of the intensity measurements of multiple intensity sensors 524A-524D, which in this example is 32 intensity units. In some embodiments, each contact is assigned a corresponding intensity, which is a portion of the cumulative intensity. Figure 5D554. The cumulative strengths assigned to contacts 552A-552E based on their distances from the center of force 554 are shown. In this example, 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 implementations, each contact j is assigned a corresponding strength Ij that is a fraction 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 identical to device 100, 300, or 500. Figure 5C-5D In some embodiments, the characteristic intensity of a contact is based on one or more contact intensities. 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.

[0233] In some embodiments, a portion of a gesture is identified for use in 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 strength of the contact increases. In this example, 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, the 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 dips in the intensity of the swipe contact for use in determining characteristic strength.

[0234] The intensity of a 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 a 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 a trackpad. In some embodiments, when a contact is detected with a characteristic intensity below the light press intensity threshold (e.g., and above a nominal contact detection intensity threshold, contacts below the nominal contact detection intensity threshold are no longer detected), the device will move the focus selector in accordance with 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.

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

[0236] In some embodiments described herein, one or more operations are performed in response to detecting a gesture that includes a corresponding press input or in response to detecting a corresponding press input performed using a corresponding contact (or multiple contacts), wherein the corresponding press input is detected at least in part based on detecting an increase in the intensity of the contact (or multiple contacts) to above a press input intensity threshold. In some embodiments, the corresponding operation is performed in response to detecting an increase in the intensity of the corresponding contact to above the press input intensity threshold (e.g., a "down stroke" of the corresponding press input). In some embodiments, the 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 press input intensity threshold, and the corresponding operation is performed in response to detecting a subsequent decrease in the intensity of the corresponding contact to below the press input threshold (e.g., an "up stroke" of the corresponding press input).

[0237] Figure 5E-5HDetection of a gesture is shown, the gesture comprising contact 562 with an intensity from below Figure 5E Light press intensity threshold in L ”) increases to a value higher than Figure 5H The deep press intensity threshold in D ”). On the displayed user interface 570 including application icons 572A-572D displayed in the predefined area 574, a cursor 576 is displayed above the application icon 572B corresponding to application 2, and a gesture performed using 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 above 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 rising to the 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, as shown in FIG. 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-5H To help readers.

[0238] In some embodiments, the display of representations 578A-578C includes animation. For example, representation 578A is initially displayed near application icon 572B, as shown in FIG. Figure 5F As the animation progresses, representation 578A moves upward and representation 578B is displayed near application icon 572B, as shown. 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 In some embodiments, the animation progresses according to the intensity of contact 562, as shown in FIG. Figure 5F-5G , where representations 578A-578C appear and decrease as the intensity of contact 562 moves toward a deep press intensity threshold (e.g., “IT D 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 identical to device 100, 300, or 500. Figure 5E-5H The operation described.

[0239] In some embodiments, the device employs intensity hysteresis to avoid unintended input, 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 a 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 "up stroke" of the corresponding press input). Similarly, in some embodiments, a press input is detected only when the device detects that the intensity of the contact increases from an intensity equal to or less than a hysteresis intensity threshold to an intensity equal to or greater than a press input intensity threshold and, optionally, the intensity of the contact subsequently decreases to an intensity equal to or less than the hysteresis intensity, and a corresponding operation is performed in response to detecting the press input (e.g., an increase in the intensity of the contact or a decrease in the intensity of the contact, depending on the circumstances).

[0240] For ease of explanation, 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 optionally triggered in response to detecting any of the following: the intensity of the contact increasing above the press input intensity threshold, the intensity of the contact increasing from an intensity below a hysteresis intensity threshold to an intensity above the press input intensity threshold, the intensity of the contact decreasing below the press input intensity threshold, and / or the intensity of the contact decreasing 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 the intensity of the contact decreasing below the press input intensity threshold, the operation is optionally performed in response to detecting the intensity of the contact decreasing below a hysteresis intensity threshold that corresponds to and is less than the press input intensity threshold.

[0241] Figure 6 Example devices connected via one or more communication channels to participate in a transaction according to some embodiments are shown. One or more example 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.

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

[0243] 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 examples, 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.

[0244] In some embodiments, communication between devices 100, 300, and 500 facilitates transactions (e.g., general transactions or specific transactions). For example, a first electronic device (e.g., 100) 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 warnings 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).

[0245] Electronic devices (e.g., 100, 300, 500) are configured to communicate with each other over any of a variety of networks. For example, the devices communicate using a Bluetooth connection 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 regulated to reduce the likelihood of inappropriate sharing of information between devices. For example, communication regarding 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.

[0246] 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, the electronic device (e.g., 100, 300, 500) uses an NFC channel 610 to communicate with the payment terminal 600. In some embodiments, the payment terminal 600 uses a peer-to-peer NFC mode to communicate with the electronic device (e.g., 100, 300, 500). The electronic device (e.g., 100, 300, 500) is optionally configured to transmit a signal to the payment terminal 600 that includes payment information of a payment account (e.g., a default account or an account selected for a particular transaction).

[0247] In some embodiments, continuing with the transaction includes sending a signal including payment information of an account (such as a payment account). In some embodiments, continuing with the transaction includes reconfiguring the electronic device (e.g., 100, 300, 500) to respond as a contactless payment card (such as an NFC-enabled contactless payment card) and then transmitting the account credentials via NFC to, for example, a payment terminal 600. In some embodiments, after transmitting the account credentials via NFC, the electronic device is reconfigured to not respond as a contactless payment card (e.g., requiring authorization before being reconfigured to respond as a contactless payment card via NFC again).

[0248] 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 releasing the 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 examples, 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 detecting the input, the security element releases the payment information so that it is transmitted to another device (e.g., payment terminal 600). In some examples, the security element is a hardware component that controls the release of security information. In some examples, the security element is a software component that controls the release of security information.

[0249] In some embodiments, the protocols associated with transaction participation depend 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, the generation conditions and / or transmission conditions for a wearable device include detecting that a button has been pressed (e.g., after security verification), while the corresponding conditions for a phone do not require a button press, but rather require detection of a specific interaction with an application. In some embodiments, the conditions for transmitting and / or releasing 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 passcode at a device (e.g., device 100), and detection of a mechanical input (e.g., a button press) on another device (e.g., device 500).

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

[0251] 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 examples, payment is denied when the provided payment information is inconsistent (e.g., the expiration date does not correspond to the credit card number, debit card number, or shopping card number) or when no account includes payment information that matches the information from the POS communication.

[0252] In some embodiments, the user account data further identifies one or more limits (e.g., credit limit); current or previous period balance; last transaction date, transaction location, and / or amount; account status (e.g., active or frozen); and / or authorization instructions. In some examples, the payment server (e.g., 604) uses such data to determine whether to authorize the payment. For example, the payment server may deny 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.

[0253] 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 denied. In some examples, 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 the 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.

[0254] 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).

[0255] 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 unintentional 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.

[0256] 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 input corresponding to an attempt to transition the device to the unlocked state or input corresponding to turning the device off.

[0257] In some examples, a secure element is a hardware component (e.g., a secure microcontroller chip) configured to securely store data or algorithms. In some examples, the secure element provides (or issues) payment information (e.g., an account number and / or a transaction-specific dynamic security code). In some examples, the secure element provides (or issues) payment information in response to the device receiving authorization, such as user authentication (e.g., fingerprint authentication; password authentication; detecting a double-click of a hardware button when the device is unlocked, and optionally, when the device has been continuously on the user's wrist due to unlocking the device by providing authentication credentials to the device, where the continued presence of the device on the user's wrist is determined by periodically checking for contact between the device and 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 matches a registered fingerprint. Based on determining that the fingerprint matches the registered fingerprint, the secure element provides (or issues) the payment information. Based on determining that the fingerprint does not match the registered fingerprint, the secure element forgoes providing (or issuing) the payment information.

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

[0259] Figures 7A to 7P An exemplary user interface for configuring a card onto an electronic device (e.g., 100) having one or more input devices and one or more short-range communication radio components (e.g., NFC radio components) according to some embodiments is shown. The user interface in these figures is used to illustrate a card including Figures 8A to 8B The process is described below.

[0260] According to some embodiments, a user has access to a stored-value card and wishes to transfer the stored value from the stored-value card to a virtual card stored on an electronic device. Before the value is transferred, the electronic device uses a verification procedure to help confirm that the user is the legal owner of the stored-value card. In some examples, the electronic device communicates with the stored-value card (e.g., using NFC) to receive information about the stored-value card, such as the account number of the stored-value card or the current value stored in the stored-value card. The electronic device also receives information about the stored-value card separately (e.g., via a displayed keyboard without using NFC to receive information from the user). The electronic device verifies ownership based on these two pieces of information. If ownership is verified, the electronic device transfers the stored value from the stored-value card (e.g., using NFC) to the virtual card of the electronic device. In some examples, this technology helps provide security for the legal owner of the stored-value card and prevents users of the electronic device from transferring funds from other people's stored-value cards.

[0261] Figure 7A A user interface for electronic device 100 according to some embodiments is shown. In some examples, electronic device 100 displays an enable representation (e.g., 702A) that includes an indication of a previously provided account (e.g., a payment account). In this example, the enable representation (e.g., 702A) corresponds to an American Express account. In some examples, electronic device 100 also displays an enable representation (e.g., 702B) that includes an indication of another previously provided account (e.g., a payment account). In this example, the enable representation (e.g., 702B) corresponds to a MasterCard account that is different from the American Express account. When electronic device 100 detects activation of an enable representation (e.g., 702A) that includes an indication of a previously provided account, or activation of an enable representation (e.g., 702B) that includes an indication of another previously provided account, by, for example, detecting a touch input at a position corresponding to the corresponding enable representation on the touch-sensitive surface of the electronic device, the electronic device displays information corresponding to the corresponding account.

[0262] In some embodiments, the electronic device 100 displays an enabling indication (e.g., 702D) which, when activated, causes the electronic device to display a user interface for the user to select an account to use without checking authentication, such as a reference to Figures 15A to 15M As stated.

[0263] In some embodiments, the electronic device 100 displays a selection enable representation (e.g., 704) that provides the user with an option to turn off the Express Pass card. For example, by turning off the Express Pass card, none of the accounts provided on the electronic device 100 will be designated as Express Pass cards. In some embodiments, the electronic device 100 receives user input indicating that it is not desirable to make the account available without checking authentication (e.g., by receiving user input that selects the "Do not use account" option for use without checking authentication; by moving the selection enable representation to the "off" position as shown in conjunction with the selection enable representation 704), such as with reference to FIG. Figures 15A to 15M As described. In response to receiving user input indicating that it is not desired to make an account available without checking authentication, the electronic device 100 specifies that a certain account of the virtual card (or all accounts of the electronic device) is not available without checking authentication. Therefore, the electronic device 100 provides the user with the option of disabling (or enabling) a quick pass mode (e.g., using the selection enable indication 704), through which funds can be transferred in a specific transaction without the need for authentication. In some embodiments, when the quick pass feature is enabled (e.g., by moving the selection enable indication 704 to the "on" position), the electronic device 100 provides faster access to accounts designated as quick pass accounts. In some embodiments, when the quick pass feature is disabled (e.g., by moving the selection enable indication 704 to the "off" position), the electronic device 100 brings additional security to the accounts provided on the electronic device.

[0264] In some embodiments, electronic device 100 displays an enable representation (e.g., 702C) for configuring an account on electronic device 100 (or for configuring an account on a device other than electronic device 100). The electronic device detects activation of the enable representation (e.g., 702C) for configuring an account on electronic device 100. In response to detecting activation of the enable representation (e.g., 702C) for configuring an account on electronic device 100, the electronic device displays a user interface for selecting from two (or more) types of accounts (e.g., a stored value account, and an account that is not a stored value account), such as Figure 7BAs shown. Therefore, in some embodiments, the electronic device 100 displays an enable representation for configuring a non-stored value account (e.g., 706A) and an enable representation for configuring a stored value account (e.g., 706B). In some embodiments, a stored value account is an account in which funds or data (in the form of binary-encoded data) associated with the corresponding account are physically stored on a stored value card associated with the stored value account. In some examples, the stored value card is a closed-loop stored value card. In some examples, the stored value card is a pass card (e.g., a stored value pass card). In some examples, the stored value pass account stores pass plan (or pass ticket) information. In some examples, the pass plan is a monthly or weekly pass plan. In some examples, the stored value pass account stores electronic cash. In some examples, the electronic device 100 can use NFC and transfer funds from the configured stored value pass account without accessing an IP network or internet connection, which saves power and allows funds to be transferred from the stored value pass account even when an IP network or internet connection is unavailable.

[0265] In some embodiments, in response to detecting Figure 7B Upon activation of the affordance (e.g., 706B) for configuring a stored-value account, the electronic device 100 displays a prompt (e.g., 708A, 708B) on the display of the electronic device for the user to place the electronic device 100 within communication range (e.g., within range of one or more short-range communication radio components) of a card having stored value, as shown. Figure 7C For example, the prompt (e.g., 708A, 708B) instructs the user to place the electronic device 100 on the stored-value card so that the back of the electronic device (e.g., the side of the electronic device opposite the display) is closest to the stored-value card. Alternatively or in addition, the electronic device 100 provides the prompt via a speaker, tactile vibration, or other technology suitable for prompting the user.

[0266] like Figure 7D As shown, once the electronic device 100 is within the communication range of the card, the electronic device 100 receives the card account number of the card from the card (e.g., 710) via one or more short-range communication radio components (e.g., NFC radio components), wherein the card has a stored value (e.g., Figure 7K728D shown in , which is a stored value greater than 0). For example, the card (e.g., 710) is a stored value card, an NFC-readable stored value card, a stored value pass card, or a stored value gift card. In some examples, the electronic device 100 receives the card account number of the card from the card (e.g., 710) using NFC. In some embodiments, the electronic device 100 presents the following indication (e.g., 712) when communicating with the card: the electronic device is receiving the card account number of the card (e.g., 710). In some embodiments, the card account number includes mixed alphanumeric characters. In some examples, the card account number includes numeric characters but does not include alphabetic characters.

[0267] The electronic device 100 requests (e.g., from the user) verification information (e.g., the card number of the card (e.g., 710), the card account number of the card, or the date of birth of the user who registered the card) to verify the ownership of the card (e.g., 710). For example, the electronic device 100 requests the user to enter the card number of the card (e.g., 710). In some embodiments, the electronic device 100 requests the verification information after receiving the card account number of the card (e.g., 710).

[0268] In some embodiments, as Figures 7E to 7F As shown, the electronic device 100 displays an indication (e.g., 714A) requesting the user to provide verification information (e.g., the card account number of the card (e.g., 710)). In some embodiments, the electronic device 100 uses the verification information (e.g., 714C) to confirm that the user actually holds (or controls) the card (e.g., 710). Figure 7E As shown, the electronic device 100 displays a request (e.g., 714A) for the user to enter the card account number into a field (e.g., 714B) using a virtual keyboard (e.g., 716). Figure 7F As shown, the electronic device 100 receives input from a user of the device via one or more input devices (e.g., not through one or more short-range communication radio components) that includes authentication information (e.g., 714C) for verifying ownership of the card (e.g., 710).

[0269] In some embodiments, the verification information (e.g., 714C) is information not displayed on the card (e.g., 710). For example, the verification information (e.g., 714C) requested by the electronic device 100 and entered by the user is not displayed on the card (e.g., 710). In some embodiments, upon determining that the card (e.g., 710) is registered, the requested (and received) verification information is information not displayed on the card. Therefore, in some examples, verification is not possible simply by possessing the card (e.g., 710); the user must possess some additional information corresponding to the card. In some embodiments, the verification information (e.g., 714C) is (or includes) the stored value of the card (e.g., 710), such as the amount of funds currently stored on the card. In some examples, at least some (or all) of the stored value of the card (e.g., 710) can be transferred from the card (e.g., 710) to a virtual card configured on the electronic device 100.

[0270] In some embodiments, as Figures 7G to 7H As shown, the electronic device 100 displays an indication (e.g., 720A) requesting the user to provide verification information (e.g., the cardholder's date of birth). In some examples, the electronic device 100 uses the verification information (e.g., 720C) to confirm that the user actually owns (or controls) the card (e.g., 710). Figure 7G As shown, the electronic device 100 displays a request (eg, 720A) for the user to enter the date of birth (eg, 720C) into the field (eg, 720B) using the virtual keyboard (eg, 716). Figure 7H As shown, the electronic device 100 receives input including authentication information (e.g., 720C) for verifying ownership of the card (e.g., 710) from a user of the electronic device via one or more input devices (e.g., not through one or more short-range communication radio components). In some embodiments, Figures 7G to 7H The user interface is Figures 7E to 7F In some embodiments, Figures 7G to 7H The user interface and Figures 7E to 7F Used in conjunction with the user interface of .

[0271] In some embodiments, the verification information (e.g., 720C) is information not displayed on the card (e.g., 710). For example, the verification information (e.g., 720C) requested by the electronic device 100 and entered by the user is not displayed on the card (e.g., 710). In some embodiments, based on determining that the card (e.g., 710) is registered, the requested (and received) verification information is information not displayed on the card. Therefore, in some examples, verification is not possible simply by possessing the card (e.g., 710), and the user must possess some additional information corresponding to the card. In some embodiments, the verification information (e.g., 720C) is (or includes) stored values ​​of the card (e.g., 710). In some examples, at least some (or all) of the stored values ​​of the card (e.g., 710) can be transferred from the card to a virtual card configured on the electronic device 100.

[0272] like Figure 7I As shown, the electronic device 100 verifies ownership of the card (e.g., 710) based on the result of comparing the verification information (e.g., 714C, 720C) with independent information related to the card of the cardholder (e.g., the card account number of the card, the birthday of the registered user of the card). The independent information related to the card (e.g., 710) is received independently of the verification information (e.g., 714C, 720C). For example, the independent information is received from a server, a service, a database, or the card (e.g., 710) itself. In some embodiments, the comparison of the verification information (e.g., 714C, 720C) with the independent information related to the cardholder's card (e.g., 710) is performed at a remote server, and the result is sent from the remote server to the electronic device 100. In some embodiments, the comparison of the verification information (e.g., 714C, 720C) with the independent information related to the cardholder's card (e.g., 701) is performed at the electronic device 100. In some embodiments, the electronic device 100 displays an indication (e.g., 724A) that verification information (e.g., 714C, 720C) has been received. In some embodiments, the electronic device 100 displays an indication (e.g., 724B) that ownership verification is being performed.

[0273] In some embodiments, the electronic device 100 sends the card account number to a server, service, or database (e.g., via a network or internet connection) and receives a response from the server, service, or database regarding the registration status of the card (e.g., 710). In some embodiments, this is done before requesting verification information from the user (e.g., 714C, 720C). In some embodiments, this is done before receiving input from the user to verify ownership of the card (e.g., 710). In some embodiments, the electronic device 100 determines whether the card is registered (e.g., registered with the server, service, or database) based on the response received from the server, service, or database regarding the registration status of the card (e.g., 710). Thus, in some embodiments, the electronic device 100 operates in a "registered mode" (e.g., based on a response received from the server, service, or database indicating that the card is registered), while in some embodiments, the electronic device 100 operates in an "anonymous mode" (e.g., based on a response received from the server, service, or database indicating that the card is not registered). In some examples, a card is registered when a server, service, or database has registered the card to a particular user or entity. In some examples, a card is registered when a server, service, or database associates the card with a particular user or entity.

[0274] In some embodiments, upon determining that the card (e.g., 710) is registered (e.g., "registration mode"), the electronic device 100 requests (e.g., from the user) verification information to verify ownership of the card (e.g., 710), which includes requesting information not shown on the card (e.g., the date of birth of the user registered to the card). In some embodiments, the electronic device 100 forgoes requesting verification information shown on the card (e.g., 710). In some embodiments, the requested verification information is information not shown on the card (e.g., 710).

[0275] In some embodiments, upon determining that a card (e.g., 710) is being registered (e.g., in "registration mode"), the electronic device 100 sends (e.g., to a server, service, or database) the card account number of the card and receives (e.g., from the server, service, or database) independent information. In some examples, the independent information includes personal information of the user registering the card (e.g., 710), rather than the card account number of the card. For example, the independent information includes the user's birthday, the user's mailing address, and / or the user's mother's maiden name. By requesting personal information from the user registering the card (e.g., 710), a higher level of security is achieved for the registered card. In some embodiments, after receiving the card account number of the card (e.g., 710) via one or more short-range communication radio components, and before transferring at least some (or all) of the stored values ​​from the card (e.g., 710) to a virtual card stored on the electronic device 100 via one or more short-range communication radio components, the electronic device forgoes receiving the user-configured account number of the card (e.g., 710) as part of verifying ownership of the card. Thus, by using independent information for authentication, the electronic device helps prevent a user's card from being digitally stolen by swiping an NFC reader across the user's pocket or wallet where the card (e.g., 710) is located.

[0276] In some embodiments, based on determining that the card (e.g., 710) is not registered (e.g., "anonymous mode"), the electronic device 100 requests (e.g., from the user) verification information (e.g., 714C, 720C, the card number of the card, the card account number of the card) to verify ownership of the card including the information displayed on the card. In some examples, the electronic device 100 forgoes the requested information (e.g., 710) that is not shown on the card. Thus, in some examples, the electronic device 100 can request different information based on whether the card (e.g., 710) is registered or unregistered, and implement a higher level of security for registered cards by requesting information that is personal to the registered card user.

[0277] In some embodiments, upon determining that a card (e.g., 710) is not registered (e.g., in "anonymous mode"), and prior to verifying ownership of the card, the electronic device 100 requests a user-provided card account number as part of the verification information requested to verify ownership of the card. In some examples, the electronic device 100 receives the user-provided card account number as input from a user of the electronic device (e.g., using a touchscreen keyboard input), rather than receiving the account number from one or more short-range communication radio components. The user-provided card account number includes verification information used to verify ownership of the card. In some examples, the electronic device 100 compares the user-provided account number with the card account number as part of verifying ownership of the card (e.g., 710) by comparing the verification information with independent information, where the independent information includes the received card account number. In some examples, upon determining that the card is registered (e.g., in "registered mode"), the electronic device 100 does not request (or receive) the user-provided card account number as part of the verification information received from the user to verify ownership of the card.

[0278] In some embodiments, based on a determination that the card is not registered (e.g., in "anonymous mode"), the electronic device 100 does not present (e.g., does not display on any display of the electronic device) the card account number of the card (e.g., 710) until input including authentication information for verifying ownership of the card is received from the user of the electronic device via one or more input devices. In some embodiments, based on a determination that the card (e.g., 710) is not registered (e.g., in "anonymous mode"), the electronic device 100 does not present (e.g., does not display on any display of the electronic device) the card account number until ownership of the card is verified. Therefore, in some examples, the user must access the card number (or the account number associated with the card 710) through a method external to the electronic device 100. For example, the user may provide the card number (or the account number associated with the card) to the electronic device 100 (e.g., by providing text input via a displayed virtual keyboard) based on the card number (or the account number associated with the card) printed on a receipt or invoice for the card (e.g., 710) or the card number printed on the card. In some embodiments, based on determining that a card (e.g., 710) has been registered (e.g., "registered mode"), the electronic device 100 presents (e.g., by displaying on a display of the electronic device) the account number of the card before receiving input from the user through one or more input devices including verification information for verifying ownership of the card.

[0279] In some embodiments, as Figure 7JAs shown, based on determining that ownership verification has failed, the electronic device 100 displays and / or generates feedback (e.g., visual feedback displayed on the display, audio and / or tactile output generated by the device) for the user, indicating (e.g., indication 726A) that ownership verification has failed. In some examples, if the verification information received from the user (e.g., 714C, 720C) is inconsistent with the independent information, the verification information is determined to have failed. In some embodiments, based on determining that ownership verification has failed, the electronic device 100 abandons providing a prompt (e.g., to the user) regarding performing a value transfer operation for value transfer (e.g., abandons generating feedback, such as visual feedback displayed on the display, audio and / or tactile output generated by the device), and abandons transferring any stored value from the card (e.g., 710) to a virtual card stored on the electronic device. In some embodiments, as Figure 7J As shown, upon determining that the ownership verification has failed, the electronic device 100 again requests (e.g., from the user) (e.g., 726B) verification information (e.g., card number, card account number, date of birth of the user who registered the card) to verify the ownership of the card (e.g., 710). Therefore, the electronic device 100 notifies the user that the ownership verification has failed.

[0280] In some embodiments, as Figure 7K As shown, based on determining that ownership verification is successful, the electronic device 100 presents (e.g., on the display of the electronic device) an indication of successful verification completion (e.g., 728A, 728B). In some embodiments, the electronic device 100 presents one or more indications of one or more information items (e.g., 728C to 728E) associated with the verified card (e.g., 710). In some examples, the electronic device 100 presents an indication of the user name associated with the card (e.g., 710) (e.g., 728C). In some examples, the electronic device 100 presents an indication of the current balance of the card (e.g., 710) (e.g., 728D). In some examples, the electronic device 100 presents an indication of the pass plan (or pass ticket) information associated with the card (e.g., 710) (e.g., 728E).

[0281] In some embodiments, the electronic device 100 displays an enable indication or input area (e.g., 728F) that includes an indication of the amount of stored value of the card (e.g., 710) to be transferred from the card to a virtual card stored on the electronic device. In some examples, the electronic device receives user input (e.g., input into input area 728F) of the amount of stored value of the card to be transferred from the card (e.g., 710) to the virtual card stored on the electronic device. In some embodiments, the enable indication (e.g., 728F), when activated, causes the electronic device to display a user interface for the user to select the amount of money to be transferred from the stored value card (e.g., 710) to be transferred to the virtual card stored on the electronic device 100. For example, the user may choose to transfer the entire amount of stored value of the card (e.g., 710) from the card to the virtual card on the electronic device 100, as Figure 7L shown.

[0282] In some embodiments, as Figure 7L As shown, electronic device 100 displays an enable indication (e.g., 728G) that can be selected by the user to activate to initiate a value transfer process. The enable indication (e.g., 728G) initiates the process of transferring value from a card (e.g., 710) to a virtual card on electronic device 100 when activated. In some embodiments, the enable indication (e.g., 728G) cannot be activated until the amount of money to be transferred is selected (e.g., using enable indication 728F). In some embodiments, when the electronic device has received the transfer value (e.g., using input area 728F), activating the enable indication (e.g., 728G) initiates the process of transferring the entire available balance on the card (e.g., 710). In some embodiments, the enable indication (e.g., 728G) initiates the process of transferring the entire available balance on the card (e.g., 710) (e.g., even if no transfer value is entered into input area 728F).

[0283] like Figure 7M As shown, based on determining that ownership verification is successful (and in some embodiments, as Figure 7L As shown, in response to receiving a user selection of an enable indication to initiate a value transfer (e.g., 728G), the electronic device 100 displays and / or generates feedback (e.g., visual feedback displayed on a display, audio and / or tactile output generated by the device) (e.g., 708B, 730) to prompt the user to perform (e.g., performed by the user) a value transfer operation for the value transfer. In some examples, the prompt or feedback (e.g., 708B, 730) requests the electronic device 100 to be in contact with the card (e.g., 710) for a prolonged period of time, or requests that the electronic device be placed near the card (e.g., 710). In some examples, if the verification information (714C, 720C) received from the user is consistent with (e.g., matches) the independent information, the electronic device 100 determines that the ownership verification is successful. As Figure 7NAs shown, in conjunction with a value transfer operation (and / or after providing a prompt to perform the value transfer operation (or generating feedback)), the electronic device 100 transfers (e.g., via one or more short-range communication radio components) at least some (or all) of the stored value from the card (e.g., 710) to a virtual card stored on the electronic device. In some embodiments, the virtual card is stored in an account information application (e.g., an electronic wallet) of the electronic device 100. In some embodiments, during the transfer, the electronic device 100 displays and / or generates (e.g., to the user) feedback (e.g., indication 732A) indicating that at least some (or all) of the stored value from the card (e.g., 710) is being transferred to the virtual card on the electronic device, as well as an indication (e.g., 708B, 732B) to keep the electronic device in contact with or close to the card for an extended period of time while the transfer process is ongoing (e.g., to the user).

[0284] In some embodiments, the virtual card is stored on the electronic device 100 (e.g., in an account information application of the electronic device) before the card account number of the card (e.g., 710) is received and before ownership of the card is verified. In some embodiments, the electronic device 100 includes a template virtual card (e.g., a "blank" virtual card) that is stored on the electronic device and does not include any value or funds. In some examples, the electronic device 100 transfers at least some (or all) of the stored values ​​from the card (e.g., 710) to the template virtual card. Therefore, in some examples, there is no need to configure a new virtual card for the electronic device 100 because the features and / or values ​​associated with the card (e.g., 710) can be moved to the template virtual card. The template virtual card speeds up the process of transferring funds from the stored value card (e.g., 710) to the electronic device 100 because a new virtual card does not need to be created during the configuration process or transfer operation.

[0285] In some embodiments, after successfully transferring at least some (or all) of the stored values ​​from the card (e.g., 710) to the virtual card stored on the electronic device 100, the virtual card includes at least some (or all) of the stored values, and the card (e.g., 710) no longer includes at least some (or all) of the stored values. In some embodiments, transferring at least some (or all) of the stored values ​​from the card (e.g., 710) to the virtual card stored on the electronic device 100 includes removing the stored values ​​from the card and transmitting a request to a server, service, or database associated with the card (e.g., via a network or internet connection) to deactivate the card (e.g., to cancel the card, rendering it inoperable). For example, all stored values ​​from the card (e.g., 710) are removed and the card is inoperable. Thus, in some embodiments, all features and / or values ​​of the physical card (e.g., 710) are moved to the virtual card stored on the electronic device 100, thereby replacing the physical card with the virtual card.

[0286] In some embodiments, as Figure 7P As shown, after successfully transferring at least some (or all) of the stored value from the card (e.g., 710) to the virtual card stored on the electronic device 100, the electronic device displays a representation of the virtual card corresponding to the stored-value card. In some embodiments, the representation of the virtual card corresponding to the stored-value card includes an indication of the type of the virtual card (e.g., 736A). In some embodiments, the representation of the virtual card corresponding to the stored-value card includes a graphical depiction of the virtual card (e.g., 736B). The indication of the type of the virtual card (e.g., 736A) and the graphical depiction (e.g., 736B) enable a user to distinguish the virtual card from different cards provided on the electronic device 100, and in some examples, the indication of the type of the virtual card and the graphical depiction are displayed simultaneously.

[0287] In some embodiments, a representation of a virtual card corresponding to a stored-value card provided on electronic device 100 includes a menu (e.g., 740) that includes a plurality of selectable affordances (e.g., 740A, 740B, 740C). In some examples, the menu (e.g., 740) includes an information affordance (e.g., 740A). In some examples, the menu (e.g., 740) includes a transaction affordance (e.g., 740B). In some examples, the menu (e.g., 740) includes a device affordance (e.g., 740C). In some embodiments, (e.g., in response to a user selection of an information affordance (e.g., 740A), as Figure 7P), the representation of the virtual card displays, individually or simultaneously, one or more information items (e.g., 736C to 736E) about the virtual card corresponding to the provided card (e.g., 710). In some examples, the electronic device 100 displays the username of the account for which the virtual card is registered (e.g., 736C). In some examples, the electronic device 100 displays a fund balance (e.g., 736D) on the virtual card (e.g., the amount of funds stored in the virtual card). In some examples, the electronic device 100 displays pass information (e.g., 736E) for the virtual card (e.g., a monthly pass, a 10-ride pass, etc.). By displaying one or more information items (e.g., 736C to 736E) about the virtual card, the electronic device 100 displays and / or generates feedback (e.g., visual, audio, and / or tactile output generated by the device) that includes information about the details of the virtual card corresponding to the provided card (e.g., 710).

[0288] In some embodiments, after successfully transferring at least some (or all) of the stored values ​​in storage from the card (e.g., 710) to the virtual card stored on the electronic device 100, the electronic device displays the stored value of the virtual card (e.g., 736D). In some examples, if the electronic wallet application of the electronic device 100 includes multiple virtual cards (or accounts) of the same type (e.g., multiple pass cards), the value of each of the multiple virtual cards is highlighted. This improved feedback enhances the operability of the electronic device by providing the user with the ability to distinguish multiple virtual cards stored on the electronic device (or accessible to the electronic device) and their corresponding stored values.

[0289] In some embodiments, as Figure 7O As shown, based on determining that the value transfer has failed, the electronic device 100 displays and / or generates (e.g., indicates to the user) feedback (e.g., visual, audio, and / or tactile output generated by the device) that the value transfer has failed (e.g., indication 734A). In some embodiments, the electronic device 100 displays and / or generates feedback (e.g., visual, audio, and / or tactile output generated by the device) through a second prompt (e.g., 734B that is different from the first prompt 730) to repeat (e.g., performed by the user) the value transfer operation for value transfer. In some examples, the second prompt includes visual, audio, and / or tactile feedback that prompts the user to interact with the electronic device.

[0290] In some embodiments, after at least some (or all) of the stored values ​​are transferred from the card (e.g., 710) to the virtual card stored on the electronic device 100, and based on determining that the electronic device does not have another pass account connected (e.g., the newly configured pass account is the initial (first) pass account and / or the only currently valid pass account connected to the electronic device), the electronic device designates (designates by default or prompts the user to designate) the account of the virtual card as available for use without checking authentication. In some examples, if the virtual card corresponds to the only configured pass account of the electronic device 100, the electronic device 100 designates the virtual card as a quick pass card based on determining that the virtual card is the only pass account of the account information application of the electronic device, such as reference Figures 15A to 15M In some embodiments, such as reference Figures 15A to 15M As described, the use of a quick pass card (e.g., for making a payment or transmitting credentials) does not require an authentication check in certain circumstances (e.g., where the detected wireless signal corresponds to a transaction such as a request from a transaction terminal or a request for funds from a pass account). Thus, designating a virtual card as a quick pass card reduces the amount of user input required, making the technology more efficient and saving battery power. Pass transactions are also often conducted in crowded pass stations with users (or other passengers) eager to establish a pass connection. Even with the most accurate and reliable authentication systems, there is the possibility of a false negative result where a valid user fails to authenticate correctly (e.g., because the user's fingerprint is not correctly recognized or the user enters an incorrect password, passcode, or pattern). Using a quick pass transaction model that provides security by establishing the identity of the transaction terminal as a pass transaction terminal (e.g., through a transaction terminal signal or other background information) rather than user authorization for a specific transaction reduces the possibility that a user (or other passenger) will be inconvenienced by a false negative result of authentication when conducting a pass transaction with the device.

[0291] In some embodiments, after transferring at least some (or all) of the stored value from the card (e.g., 710) to the virtual card stored on the electronic device 100, and based on determining that the electronic device has one or more other connected pass accounts, the electronic device 100 forgoes designating (or forgoes prompting the user to designate) the account of the virtual card as available for use without checking for authentication. In some embodiments, if the virtual card does not correspond to a uniquely configured pass account, the electronic device 100 designates (or prompts the user to designate) the account of the virtual card as unusable without checking for authentication. Therefore, in some examples, the electronic device 100 does not designate the virtual card as a quick pass card based on determining that the virtual card is not the only pass account of the account information application.

[0292] In some embodiments, after transferring at least some (or all) of the stored value from the card (e.g., 710) to the virtual card stored on the electronic device 100, and based on determining that the electronic device has an additional connected pass account, and further based on receiving user input indicating that the account does not want to be available for use without checking for authentication (e.g., user input removing a previous Quick Pass card from the account information application or declining to add a previous account as a Quick Pass card), the electronic device forgoes designating (or forgoes prompting the user to designate) the account of the virtual card as available for use without checking for authentication. In some examples, the electronic device 100 designates (or prompts the user to designate) the account of the virtual card as unavailable for use without checking for authentication. Thus, in some examples, the electronic device 100 does not designate the virtual card as a Quick Pass card based on determining that the virtual card is not the only pass account in the account information application, thereby accommodating the user's preference to designate or forgo designating the virtual card as a Quick Pass card.

[0293] Figures 8A to 8B 800 is a flow chart illustrating a method for configuring a card on an electronic device according to some embodiments. Method 800 is performed on a device (e.g., 100, 300, 500) having one or more input devices, one or more short-range communication radio components, and optionally a display. Some operations in method 800 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

[0294] As described below, method 800 provides an intuitive way to manage transactions. This method reduces the cognitive burden on users managing transactions, thereby creating a more efficient human-computer interface. For battery-powered computing devices, this allows users to manage transactions more quickly and efficiently, conserving power and increasing the time between battery charges.

[0295] At block 802, an electronic device receives (e.g., receives from a card via NFC) a card account number of a card (e.g., 710) (e.g., a stored-value card, an NFC-readable stored-value card, a stored-value pass card, a stored-value gift card) via one or more short-range communication radio components (e.g., one or more NFC radio components), wherein the card (e.g., 710) has a stored value (e.g., a stored value 728D greater than 0). In some examples, the card account number is received from the card using NFC.

[0296] According to some embodiments, at block 804, the card is a stored-value card (e.g., funds and / or data are physically stored on the card in the form of binary-encoded data). For example, the card is a closed-loop stored-value card. In some examples, the card is a pass card (e.g., a stored-value pass card). In some examples, the stored-value pass account stores pass plan (or pass ticket) information. In some examples, the pass plan is a monthly or weekly pass plan. In some examples, the stored-value pass account stores electronic cash.

[0297] At block 806, the electronic device requests (e.g., from the user) verification information (e.g., card number, card account number, date of birth of the user who registered the card) to verify ownership of the card (e.g., 710). In some examples, the electronic device displays an indication (e.g., 714A, 720A) requesting the user to provide verification information. In some examples, the electronic device uses the verification information (e.g., 714C, 720C) to confirm that the user physically possesses (or controls) the card (e.g., 710). By receiving and using the verification information to confirm that the user possesses the card, the electronic device's ability to detect and prevent electronic theft or fraud is enhanced.

[0298] According to some embodiments, the verification information (e.g., 714C, 720C) is information not displayed on the card (e.g., 710). For example, the verification information (e.g., 714C, 720C) entered by the user will not be displayed on the card (e.g., 710). In some examples, based on a determination that the card is registered (e.g., "registered mode"), the requested (and received) verification information is information not displayed on the card. Therefore, in some examples, verification is not possible simply by possessing the card. Instead, the user must have some additional information corresponding to the card. In some examples, the verification information is (or includes) the card's stored values. In such examples, a user with access to the card and knowledge of the card's current stored values ​​can transfer at least some (or all) of the stored values ​​from the card (e.g., 710) to a virtual card stored on the electronic device 100.

[0299] According to some embodiments, at box 808, based on determining that the card has been registered (e.g., with a server, service, or database) (e.g., "registered mode"), at box 810, requesting (e.g., from a user) verification information (e.g., 714C, 720C) to verify ownership of the card (e.g., 710) (e.g., the date of birth of the user who registered the card) includes requesting information that is not shown on the card. In some examples, the electronic device forgoes requesting information that is shown on the card. By determining whether the card is registered, the electronic device can request specific verification information based on determining whether the card is registered, thereby enhancing the operability of the device by including additional security measures for registered cards.

[0300] According to some embodiments, at block 812, based on determining that the card (e.g., 710) is not registered (e.g., in "anonymous mode"), at block 814, requesting (e.g., from the user) verification information (e.g., 714C, 720C, card number, card account number) to verify ownership of the card includes requesting information not shown on the card (e.g., 710). In some examples, the electronic device forgoes requesting information not shown on the card. Thus, the electronic device can request different information based on whether the card is registered. For example, a higher level of security for registered cards can be achieved by requesting personal information of the registered user of the card. By determining whether the card is registered, the electronic device can request specific verification information based on determining whether the card is registered, thereby enhancing the operability of the device by not displaying information requests for unregistered cards that the user does not own, thereby reducing the amount of required user input.

[0301] In some embodiments, (based on determining that the card is not registered (e.g., "anonymous mode")), the electronic device does not present (e.g., on a display of the electronic device) the account number of the card before receiving input including authentication information (e.g., 714C, 720C) for verifying ownership of the card (e.g., 710) from the user of the electronic device through one or more input devices. In some examples, the electronic device does not present the account number of the card before verifying ownership of the card. Therefore, the user must access the card (or account) number through a method outside of the electronic device. For example, the user may provide the card number based on the card number printed on a receipt or invoice for the card or based on the card number printed on the card. In some examples, based on determining that the card is registered (e.g., "registered mode"), the electronic device presents (e.g., displays on a display of the electronic device) the account number of the card before receiving input including authentication information for verifying ownership of the card from the user of the electronic device through one or more input devices. By determining whether a card is registered, the electronic device may request specific verification information based on determining whether the card is registered, thereby enhancing the operability of the device by not displaying unnecessary requests for unregistered cards and providing additional security for registered cards.

[0302] In some examples, the electronic device determines whether the card is registered (e.g., using a server, service, or database). According to some embodiments, based on determining that the card (e.g., 710) is not registered (e.g., "anonymous mode") and before verifying ownership of the card, the electronic device requests the user-provided card (e.g., 710) account number as part of the verification information (e.g., 714C, 720C) requesting verification of ownership of the card, receives the user-provided card (e.g., 710) account number as part of receiving input including verification information (e.g., 714C, 720C) for verifying ownership of the card from a user of the electronic device (e.g., not through one or more short-range communication radio components), and compares the user-provided account number with the card account number as part of verifying ownership of the card (e.g., 710) by comparing the verification information with independent information, wherein the independent information includes the received card account number. In some examples, based on determining that the card is registered (e.g., “registered mode”), requesting verification information to verify ownership of the card does not include requesting (or receiving) a user-provided card account number (e.g., as part of receiving input from a user of the device that includes verification information for verifying ownership of the card).

[0303] At block 816, the electronic device receives input from a user of the electronic device via one or more input devices (e.g., via a virtual keyboard input rather than via one or more short-range communication radio components) including authentication information (e.g., 714C, 720C) for verifying ownership of the card (e.g., 710). In some examples, (e.g., before requesting the authentication information and / or before receiving input from the user of the device for verifying ownership of the card), the electronic device 100 transmits the card account number to a server and receives a response from the server regarding the registration status of the card. In some examples, the electronic device determines whether the card is registered (e.g., using a server, service, or database).

[0304] According to some embodiments, (e.g., before requesting verification information, before receiving input from a user of the device for verifying ownership of the card) based on determining that the card has been registered (e.g., "registered mode"), the electronic device transmits (e.g., to a server) the card account number of the card (e.g., 710) and receives (e.g., from the server) independent information. In some examples, the independent information includes personal information of the registered user of the card (e.g., the user's birthday, the user's mailing address, the user's mother's maiden name, but not the card account number). Therefore, a higher level of security for registering a card can be achieved by requesting the personal information of the registered user of the card.

[0305] In some embodiments, the electronic device waives receiving (e.g., after receiving the card account number via one or more short-range communication radio components and before transferring at least some (or all) of the stored value from the card to a virtual card stored on the device via one or more short-range communication radio components) a user-provided card account number (e.g., as part of verifying ownership of the card).

[0306] According to some embodiments, before receiving the card account number of the card (e.g., 710) and before verifying the ownership of the card, the virtual card is stored on the electronic device (e.g., stored in an account information application). In some examples, the electronic device includes a "blank" virtual card that does not have any value or funds. The electronic device transfers at least some (or all) of the stored values ​​from the card to the blank virtual card. Therefore, there is no need to configure a new virtual card for the electronic device because funds can be provided to an existing virtual card. By providing funds to an existing virtual card instead of generating a new card on the device, the electronic device does not need to create a virtual card before transferring funds to the virtual card. In some examples, this enhances the operability of the device by speeding up the process of transferring funds to the electronic device.

[0307] At box 818, the electronic device verifies ownership of the card by comparing the verification information (e.g., 714C, 720C) with independent information about the card (e.g., 710) received separately from the verification information (e.g., 714C, 720C) (e.g., independent information received from a server or from the card) (e.g., the card's account number, the birthday of the registered user of the card).

[0308] At block 820, based on determining that ownership verification is successful (e.g., if the verification information (714C, 720C) received from the user is consistent with the independent information), at block 822, the electronic device displays and / or generates (e.g., a visual, audio, and / or tactile output generated by the device) a prompt (e.g., 708B, 730) for (e.g., by the user) to perform a value transfer operation (e.g., prolonged contact with or proximity to the card) for value transfer. In some examples, the prompt includes visual, audio, and / or tactile feedback prompting the user to interact with the electronic device. In this way, the electronic device notifies the user of the successful ownership verification by generating the prompt, thereby prompting the user to perform the value transfer operation.

[0309] At block 820, based on determining that ownership verification was successful, and at block 824, in conjunction with a value transfer operation (or after generating a prompt to perform a value transfer operation), the electronic device 100 transfers (e.g., via one or more short-range communication radio components, such as one or more NFC radio components) at least some (or all) of the stored value from the card (e.g., 710) to a virtual card stored on the electronic device (e.g., stored in an account information application of the device). In some examples, the electronic device includes a secure element, and wherein transferring at least some of the stored value from the card to the virtual card stored on the electronic device includes storing information for accessing the stored value of the virtual card in the secure element of the electronic device. Thus, by transferring value to a virtual card stored on the electronic device based on verified ownership, the operability of the electronic device is enhanced by preventing the device from being configured based on funds from an unauthorized card. In some examples, after transferring at least some (or all) of the stored values ​​from the card (e.g., 710) to the virtual card stored on the device, the virtual card includes at least some (or all) of the stored values, and the card (e.g., 710) no longer includes at least some (or all) of the stored values.

[0310] According to some embodiments, based on determining that the value transfer has failed, the electronic device displays and / or generates (e.g., visual, audio, and / or tactile output generated by the device) a second prompt (e.g., 734B that is different from the first prompt 730) for (e.g., by the user) to perform a value transfer operation for value transfer (e.g., prolonged contact with or proximity to the card). In some examples, the electronic device presents an indication to the user that the value transfer has failed. In some examples, the electronic device presents another prompt to the user to perform a value transfer operation (e.g., prolonged contact with or proximity to the card). Thus, the user is warned that the value transfer has failed. In some examples, the second prompt includes visual, audio, and / or tactile feedback that prompts the user to interact with the electronic device. In this way, the electronic device notifies the user by generating the second prompt that the electronic device has determined that the value transfer has failed, thereby prompting the user to perform the value transfer operation again.

[0311] According to some embodiments, at block 826, upon determining that ownership verification failed (e.g., if the verification information received from the user is inconsistent with the independent information), at block 828, the electronic device 100 displays and / or generates feedback (e.g., a visual, audio, and / or tactile output generated by the device) indicating that ownership verification failed (e.g., indication 726A). In some examples, upon determining that ownership verification failed, the electronic device forgoes generating (e.g., a visual, audio, and / or tactile output generated by the device) a prompt (e.g., by the user) to perform a value transfer operation for value transfer and forgoes transferring any stored value from the card to the virtual card stored on the device. In some examples, upon determining that ownership verification failed, the electronic device again requests verification information (e.g., the card number, the card account number, the date of birth of the user who registered the card) to verify ownership of the card. In this way, the user becomes aware of the ownership verification failure. In this way, the electronic device notifies the user that the electronic device has determined that ownership verification failed by generating feedback, thereby prompting the user to provide information again to verify ownership.

[0312] According to some embodiments, after at least some (or all) of the stored values ​​are transferred from the card (e.g., 710) to the virtual card stored on the electronic device, the electronic device displays the stored value of the virtual card on the display (e.g., 728D). For example, when the electronic wallet application of the electronic device includes multiple virtual cards (or accounts) of the same type, the value of the virtual card is highlighted to help the user distinguish between the multiple virtual cards. By displaying the stored value of the virtual card (e.g., 728D), the electronic device informs the user how much value is stored on the virtual card. This improved feedback enhances the operability of the electronic device by providing the user with the ability to distinguish multiple virtual cards stored on the electronic device (or accessible to the electronic device) and their corresponding stored values.

[0313] According to some embodiments, after transferring at least some (or all) of the stored values ​​from the card (e.g., 710) to the virtual card stored on the electronic device, the electronic device displays on the display pass plan information (e.g., a monthly pass, a 10-ride ticket, etc.) of the virtual card (e.g., 728E), which is based on at least some (or all) of the transferred stored values. In this way, the user is aware of the pass plan of the virtual card. This improved feedback informs the user of the status of the electronic device, such as what virtual card is stored on the device and what pass plan information (if any) the virtual card includes.

[0314] According to some embodiments, after transferring at least some (or all) of the stored value from the card (e.g., 710) to the virtual card stored on the electronic device, the electronic device displays on the display (e.g., simultaneously) one or more of the following: the balance of the virtual card (e.g., 736D), the username of the account registered for the virtual card (e.g., 736C), and the pass plan information of the virtual card (e.g., a monthly pass, a 10-ride ticket, etc.) (e.g., 736E). In this way, the user understands the details of the virtual card.

[0315] According to some embodiments, at least some (or all) of the stored values ​​are transferred from the card to a virtual card stored on an electronic device, including removing the stored values ​​from the card and transmitting a request to a server to deactivate the card (e.g., canceling the card so that the card is inoperable). For example, the electronic device removes all values ​​from the card and makes the card inoperable. Therefore, in some examples, all features and / or values ​​of the card are moved to the virtual card, and the virtual card replaces the physical card. In some examples, when some or all of the stored values ​​from the card are transferred to the virtual card, information for retrieving values ​​from the virtual card is stored in a secure element to ensure that the stored values ​​cannot be accessed when the payment transaction of retrieving the information from the secure element is not properly processed.

[0316] According to some embodiments, (e.g., after transferring at least some (or all) of the stored value from the card to the stored virtual card), based on a determination that the electronic device does not have another connected pass account (e.g., the newly configured pass account is the initially (first) configured pass account and / or the only currently valid pass account connected to the electronic device), the electronic device designates (by default or prompts the user to designate) the virtual card account as available for use without checking for authentication. In some examples, engaging in a transaction using the virtual card account includes releasing information (e.g., transaction information, payment information) from a secure element of the electronic device. Thus, the electronic device designates (based on determining that the virtual card is the only pass account of the account information application) the virtual card as a quick pass card, which the electronic device can use upon checking for authentication of a transaction in which the detected wireless signal corresponds to a first type of request (e.g., a request from a transaction terminal, a request for funds from the pass account). According to some embodiments, based on a determination that the electronic device has one or more other connected pass accounts, the electronic device forgoes designating (or forgoes prompting the user to designate) the virtual card account as available for use without checking for authentication (and / or designates the virtual card account as unusable without checking for authentication). Therefore, the electronic device does not designate (based on determining that the virtual card is not the only pass account of the account information application) the virtual card as a quick pass card. Pass transactions are often conducted in crowded pass stations with users (or other passengers) who are eager to establish a pass connection. Even with the most accurate and reliable authentication systems, there is a possibility of a negative false recognition result in which a valid user fails to authenticate correctly (for example, because the user's fingerprint is not correctly recognized or the user enters an incorrect password, passcode or pattern). Using a quick pass transaction model that provides security by establishing the identity of the transaction terminal as a pass transaction terminal (for example, through a transaction terminal signal or other background information) rather than user authorization for a specific transaction reduces the possibility that a user (or other passenger) will be inconvenienced by a negative false recognition result of authentication when conducting a pass transaction with the device.

[0317] According to some embodiments, (e.g., after transferring at least some (or all) of the stored value from the card to the stored virtual card), based on determining that the electronic device does not have another connected pass account (e.g., the newly configured pass account is the initially (first) configured pass account and / or the only currently valid pass account connected to the electronic device), and based on receiving user input indicating that the account is not desired to be available for use without checking authentication (e.g., user input that removes a previous Quick Pass card from the account information application or refuses to add a previous account as a Quick Pass card), the electronic device abandons designating (or prompts the user to designate) the virtual card's account as available for use without checking authentication (and / or designates the virtual card's account as unusable without checking authentication). Therefore, the electronic device does not designate (based on determining that the virtual card is not the only pass account in the account information application) the virtual card as a Quick Pass card. In some examples, based on not receiving user input indicating that the account is not desired to be available for use without checking authentication, or based on receiving user input indicating that the account is desired to be available for use without checking authentication, the electronic device selects the virtual card's account as available for use without checking authentication. Therefore, the electronic device designates the virtual card as a Quick Pass card and can use the Quick Pass card without verifying that the detected wireless signal corresponds to a first type of request (e.g., a request from a transaction terminal, a request for funds from a pass account). Thus, the electronic device designates the virtual card as a Quick Pass card in accordance with the user's preference.

[0318] According to some embodiments, the electronic device receives user input indicating that it is not desired that an account be made available for use without checking authentication (e.g., by receiving user input selecting a "Do not use account" option to make it available for use without checking authentication, as described in relation to Figure 15D In some embodiments, the electronic device may be configured to disable a quick pass mode that allows funds to be transferred in certain transactions without authentication. In some examples, this provides additional security for accounts on the electronic device.

[0319] According to some embodiments, the electronic device receives user input selecting an account to be available for use without checking authentication (e.g., an account corresponding to a virtual card among multiple accounts of an account information application), and in response to receiving the user input selecting an account to be available for use without checking authentication, specifies that the selected account (e.g., an account of the account information application) is available for use without checking authentication, such as with reference to Figures 15A to 15MThus, the electronic device enables the user to select a preferred account to use as a Quick Pass account. In some examples, the Quick Pass account does not require authentication in certain circumstances, thereby reducing the amount of user input required, thereby making the technology more efficient and saving battery power.

[0320] It should be noted that the process described above with respect to method 800 (e.g., Figures 8A to 8B ) also apply in a similar manner to the methods described below. For example, methods 1000, 1200, 1400, 1600, 1800, and 2000 optionally include one or more features of the various methods described above with reference to method 800. For example, Figure 7A The user interface can correspond to Figure 9A and Figure 15B . For another example, an account configured using the techniques of method 800 and method 1000 can be used to perform the techniques described with reference to methods 1200, 1400, 1600, 1800, and 2000. For another example, the techniques of method 1200 can be used to add funds to the stored value accounts described with reference to methods 800, 1000, 1400, 1600, 1800, and 2000. For another example, as discussed with reference to method 1800 and method 2000, the funded account can be moved to or from a different device. For the sake of brevity, these details are not repeated below.

[0321] Figures 9A to 9N An exemplary user interface for configuring a card onto an electronic device (e.g., 100) having a display, one or more short-range communication radio components (e.g., one or more NFC radio components), and one or more input devices is shown in accordance with some embodiments. The user interface in these figures is used to illustrate a card including Figure 10 The process is described below.

[0322] According to some embodiments, a user has access to a stored-value card and wishes to transfer the stored value from the stored-value card to a virtual card stored on an electronic device. Before the value is transferred, the electronic device uses a verification procedure to help confirm that the user is the legal owner of the stored-value card. In some examples, the electronic device receives verification information from the user (e.g., via a displayed keyboard, without using NFC). The electronic device separately receives (e.g., via NFC) identification information from the stored-value card, such as the account number of the stored-value card or the current value stored in the stored-value card. The electronic device verifies ownership based on these two pieces of information. If ownership is verified, the electronic device transfers the stored value from the stored-value card (e.g., using NFC) to the virtual card of the electronic device. In some examples, this technology helps provide security for the legal owner of the stored-value card and prevents users of the electronic device from transferring funds from other people's stored-value cards.

[0323] Figure 9A A user interface for electronic device 100 according to some embodiments is shown. In some examples, electronic device 100 displays an enable representation (e.g., 902A) including an indication of a previously configured account (e.g., a payment account). In this example, the enable representation (e.g., 902A) corresponds to an American Express account. In some examples, electronic device 100 also displays an enable representation (e.g., 902B) including an indication of another previously configured account (e.g., a separate payment account). In this example, the enable representation (e.g., 902B) corresponds to a MasterCard account different from the American Express account. When electronic device 100 detects activation of an enable representation (e.g., 902A) including an indication of a previously configured account or activation of an enable representation (e.g., 902B) including an indication of another previously configured account by, for example, detecting a touch input at a position corresponding to the corresponding enable representation on the touch-sensitive surface of the electronic device, the electronic device displays information corresponding to the corresponding account (e.g., balance, previous transaction details).

[0324] In some embodiments, the electronic device 100 displays an enabling indication (e.g., 902D) which, when activated, causes the electronic device to display a user interface for the user to select an account that is available for use without checking authentication, such as a reference to Figures 15A to 15M As stated.

[0325] In some embodiments, the electronic device 100 displays a selection enable representation (e.g., 904) that provides the user with an option to turn off the Express Pass card. For example, by turning off the Express Pass card, none of the accounts configured on the electronic device 100 will be designated as Express Pass cards. In some embodiments, the electronic device 100 receives user input indicating that it is not desired that an account be available for use without checking authentication (e.g., by receiving user input selecting the "Do not use account" option to be available for use without checking authentication, by moving the selection enable representation to the "off" position as shown in conjunction with the selection enable representation 904), such as with reference to FIG. Figures 15A to 15MAs described. In response to receiving user input indicating that an account is not desired to be available for use without checking authentication, the electronic device 100 specifies that a certain account of the virtual card (or all accounts of the electronic device 100) is not available without checking authentication. Therefore, the electronic device 100 provides the user with the option of disabling (or enabling) a quick pass mode (e.g., using the selection enable indication 904), through which funds can be transferred in a specific transaction without the need for authentication. In some embodiments, when the quick pass feature is enabled (e.g., by moving the selection enable indication 904 to the "on" position), the electronic device 100 provides faster and more convenient access to accounts designated as quick pass accounts. In some embodiments, when the quick pass feature is disabled (e.g., by moving the selection enable indication 904 to the "off" position), the electronic device 100 brings additional security to the accounts configured on the electronic device.

[0326] In some embodiments, the electronic device 100 displays an enabling representation (e.g., 902C) for configuring an account on the electronic device (or on another device different from the electronic device). In some embodiments, the virtual card is a pass virtual card. In some examples, the pass virtual card stores pass plan (or pass ticket) information. In some examples, the pass plan is a monthly or weekly pass plan. In some examples, the pass virtual card stores electronic cash. In some embodiments, the virtual card is a stored value virtual card. In some examples, the stored value virtual card stores electronic cash. Therefore, in some examples, the electronic device 100 provides the user with the ability to use a virtual card to provide the user with access to the pass system.

[0327] In some embodiments, as Figure 9A As shown, the electronic device detects activation of an affordance (e.g., 902C) for configuring an account on electronic device 100. In response to detecting activation of an affordance (e.g., 902C) for configuring an account on electronic device 100, the electronic device displays a user interface for selecting from two types of accounts (e.g., a stored value account and an account that is not a stored value account), as shown in FIG. Figure 9BAs shown. Therefore, in some embodiments, electronic device 100 (e.g., simultaneously) displays an enable representation for configuring a non-stored value account (e.g., 906A) and an enable representation for configuring a stored value account (e.g., 906B). In some embodiments, a stored value account is an account in which funds or data (in the form of binary-encoded data) associated with the corresponding account are physically stored on a stored value card associated with the stored value account. Therefore, the stored value card has a stored value. In some examples, the stored value card is a closed-loop stored value card. In some examples, the stored value card is a pass card (e.g., a stored value pass card). In some examples, the stored value pass account stores pass plan (or pass ticket) information. In some examples, the pass plan is a monthly or weekly pass plan. In some examples, the stored value pass account stores electronic cash. In some examples, electronic device 100 can use NFC and transfer funds from the stored value pass account without accessing an IP network or internet connection, which saves power and allows funds to be transferred from the stored value pass account even when an IP network or internet connection is unavailable.

[0328] In some embodiments, as Figure 9B As shown, electronic device 100 detects activation of an affordance (eg, 906B) for configuring a stored value account. Figures 9C to 9F A user interface for prompting and receiving verification information according to some embodiments is shown (e.g., a user interface displayed in response to detecting activation of enable indication 906B). Figures 9C to 9F As shown, the electronic device 100 requests (e.g., by displaying a prompt on a display of the electronic device) verification information (e.g., 914A to 914B, 920A to 920B) to verify ownership of the stored-value card, and receives input from a user via one or more input devices including verification information (e.g., 914C, 920C) for verifying ownership of the card, wherein the input from the user including the verification information is not received via one or more short-range communication radio components of the electronic device and the verification information includes information not shown on the stored-value card. In some examples, the funds and / or data associated with the stored-value card are physically stored on the card in the form of binary-encoded data. In some examples, the stored-value card is an NFC-readable stored-value card. In some examples, the stored-value card is a stored-value pass card. In some examples, the stored-value card is a stored-value gift card.

[0329] like Figure 9C and Figure 9EAs shown, electronic device 100 requests (e.g., by displaying a prompt on the electronic device's display) verification information (e.g., 914A-914B, 920A-920B) to verify ownership of a stored-value card. In some embodiments, the verification information is (or includes) the card number (e.g., 914C) of the stored-value card (e.g., 910). In some embodiments, the verification information is (or includes) personal information of the registered user of the stored-value card (e.g., 920C). In some examples, the verification information is a non-account identifier. In some examples, the verification information includes the date of birth of the registered user of the stored-value card (e.g., 920C). In some examples, the verification information includes the mailing address of the registered user of the stored-value card. Thus, in some examples, electronic device 100 provides additional security by requesting personal information for verification. In some embodiments, the verification information is (or includes) the stored value of the stored-value card. Thus, in some examples, a user who knows the current stored value of the stored-value card and has access to the card can transfer at least some (or all) of the stored value from the stored-value card to a virtual card stored on electronic device 100.

[0330] like Figure 9D and Figure 9F As shown, electronic device 100 receives input from a user via one or more input devices (e.g., virtual keypad 916) including verification information (e.g., 914C, 920C) for verifying ownership of a card, wherein the input from the user including the verification information is not received via one or more short-range communication radio components of the electronic device and the verification information includes information not shown on the stored-value card (e.g., 910). In some examples, the verification information (e.g., 914C, 920C) is received via a first input device (e.g., a touch-sensitive surface, a microphone) of electronic device 100 that is different from the one or more short-range communication radio components.

[0331] In some embodiments, the electronic device 100 does not present (e.g., on a display of the electronic device) the account number of the stored-value card before receiving input including authentication information (e.g., 914C, 920C) for verifying ownership of the card from a user of the device through one or more input devices. Thus, in some examples, the user must access the card (or account) number through a method external to the electronic device 100. For example, the user may provide the card number to the electronic device 100 based on the card number printed on a receipt or invoice for the card or based on the card number printed on the card (e.g., 910). In some examples, based on determining that the card is registered (e.g., "registered mode"), the electronic device presents (e.g., on a display of the electronic device) the account number of the card before receiving input including authentication information for verifying ownership of the card from a user of the device through one or more input devices.

[0332] like Figure 9G As shown, the electronic device 100 displays a prompt (e.g., 908, 930) on the display of the electronic device for the user to place the electronic device within the communication range of the stored-value card (e.g., within the range of one or more short-range communication radio components). For example, the electronic device 100 displays the prompt (e.g., 908, 930) instructing the user to place the electronic device 100 on the stored-value card (e.g., 910) so that the back of the electronic device (e.g., the side of the electronic device opposite the display) is closest to the stored-value card.

[0333] like Figure 9H As shown, in response to a stored-value card (e.g., 910) being placed within range of one or more short-range communication radios of electronic device 100 (e.g., card 910 being placed on the back of the electronic device, as shown in FIG. Figure 9H ), the electronic device 100 receives identification information (e.g., a card number, date of birth, mailing address of the stored-value card) from the stored-value card via one or more short-range communication radio components (e.g., an NFC radio component). In some embodiments, the electronic device 100 presents (e.g., to the user) an indication (e.g., 912) that identification information is being received from the stored-value card (e.g., 910). In some examples, the identification information received is the card number of the stored-value card (e.g., 910). In some examples, the identification information received is the date of birth of a registered user of the stored-value card (e.g., 910). In some examples, the identification information received is the mailing address of a registered user of the stored-value card (e.g., 910). In some embodiments, the electronic device 100 displays and / or generates feedback (e.g., visual, audio, and / or tactile output generated by the device) indicating (e.g., indication 912) (e.g., to indicate to the user) that the electronic device is receiving identification information from the stored-value card (e.g., 910). For example, the electronic device 100 detects a stored-value card (e.g., 910) for identification information via one or more short-range communication radio components (e.g., NFC radio components). Figure 9G As shown, the prompt (e.g., 908, 930) to place the electronic device 100 within the communication range of the stored-value card (e.g., 910) is generated after receiving the verification information, such as Figure 9D and Figure 9F shown.

[0334] like Figure 9IAs shown, after receiving the identification information, the electronic device 100 verifies ownership of the stored-value card (e.g., 910) by comparing verification information (e.g., 914C, 920C entered by the user) with the identification information received from the stored-value card. In some embodiments, the electronic device 100 presents (e.g., to the user) an indication (e.g., 924A) that the identification information has been received from the stored-value card (e.g., 910). In some embodiments, the electronic device 100 presents (e.g., to the user) an indication (e.g., 924B) that the electronic device is verifying ownership of the stored-value card (e.g., 910). In some embodiments, after receiving the identification information, the electronic device 100 transmits the identification information to a remote server. The remote server verifies ownership of the stored-value card (e.g., 910) (e.g., by comparing verification information (e.g., 914C, 920C entered by the user) with the identification information received from the stored-value card), and the remote server sends an indication to the electronic device as to whether the ownership verification was successful (e.g., the values ​​match or correspond to each other). Thus, the determination / verification of ownership may be performed at the electronic device or at a remote device.

[0335] In some embodiments, as Figure 9J As shown, based on determining that ownership verification has failed, the electronic device 100 displays and / or generates feedback (e.g., visual, audio, and / or tactile output generated by the device) indicating that ownership verification has failed (e.g., indication 920D). Therefore, in some examples, the electronic device 100 notifies the user whether the verification information is incorrect. For example, if the verification information received from the user (e.g., 914C, 920C) does not correspond to (or does not match) the identification information, ownership verification is determined to have failed. In some examples, based on determining that ownership verification has failed, the electronic device 100 requests verification information (e.g., card number, date of birth, mailing address of the stored-value card) again (e.g., from the user) to verify ownership of the stored-value card (e.g., 910). For example, the electronic device 100 displays a prompt (e.g., 920A, 920B) on the display of the electronic device instructing the user to enter the verification information again.

[0336] In some embodiments, as Figure 9KAs shown, based on determining that ownership verification is successful, the electronic device 100 (e.g., on a display of the electronic device) presents an indication of successful verification completion (e.g., 928A, 928B). For example, if the verification information corresponds to (or matches) the identification information, then ownership verification is successful. In some examples, the verification information is a non-account identifier (e.g., date of birth) and the identification information is an account number. Therefore, in some examples, the electronic device 100 uses the identification information (e.g., from a remote server) to retrieve a non-account identifier (e.g., birthday) for the account corresponding to the account number. If the retrieved non-account identifier matches the verification information, then it is considered that the verification information corresponds to the identification information and the verification is successful.

[0337] In some embodiments, based on determining that ownership verification is successful, the electronic device 100 presents (e.g., displays) one or more indications of one or more information items (e.g., 928C to 928E) associated with the verified card (e.g., 910). In some examples, the electronic device 100 presents (e.g., displays) an indication of a user name (e.g., 928C) associated with the card (e.g., 910). In some examples, the electronic device 100 presents (e.g., displays) an indication of the current balance (e.g., 928D) of the card (e.g., 910). In some examples, the electronic device 100 presents (e.g., displays) an indication of pass plan (or pass ticket) information (e.g., 928E) associated with the card (e.g., 910).

[0338] In some embodiments, based on determining that ownership verification is successful, the electronic device 100 displays an affordance or input area (e.g., 928F) that includes an indication of the amount of stored value of the card (e.g., 910) to be transferred from the card to a virtual card stored on the electronic device 100. In some examples, the electronic device receives user input (e.g., input into input area 928F) of the amount of stored value of the card to be transferred from the card (e.g., 910) to the virtual card stored on the electronic device. In some embodiments, the affordance (e.g., 928F), when activated, causes the electronic device to display a user interface for the user to select the amount of money to be transferred from the stored-value card (e.g., 910) to the virtual card stored on the electronic device 100. For example, the user may choose to transfer the entire amount of stored value of the card (e.g., 910) from the card to the virtual card on the electronic device 100.

[0339] In some embodiments, upon determining that ownership verification is successful, electronic device 100 displays an enable indication (e.g., 928G) that can be activated by user input to initiate a value transfer process. This enable indication (e.g., 928G), when activated, initiates the process of transferring value from a card (e.g., 910) to a virtual card on the electronic device. In some embodiments, the enable indication (e.g., 928G) for initiating the value transfer process cannot be activated (e.g., by the user) until the amount value to be transferred is selected / received (e.g., into input area 928F). In some embodiments, if the transfer value is selected (e.g., in enable indication 928F), activating the enable indication (e.g., 928F) initiates the process of transferring the entire available balance on the card (e.g., 910). In some embodiments, the enable indication (e.g., 928G) initiates the process of transferring the entire available balance on the card (e.g., 910).

[0340] like Figure 9L As shown, the electronic device 100 transfers at least some (or all) of the stored value from the card (e.g., 910) to a virtual card stored on the electronic device (e.g., via one or more short-range communication radio components). In some embodiments, the virtual card is stored in an account information application (e.g., an electronic wallet) of the electronic device 100. In some embodiments, during the transfer, the electronic device 100 displays and / or generates (e.g., to the user) an indication (e.g., indication 932A) that at least some (or all) of the stored value from the card (e.g., 910) is being transferred to the virtual card on the electronic device and feedback (e.g., visual, audio, and / or tactile output generated by the device) indicating (e.g., to the user) (e.g., 908B, 932B) that the electronic device 100 is in prolonged contact with or close proximity to the stored-value card (e.g., 910) while the transfer process is ongoing.

[0341] In some embodiments, after successfully transferring at least some (or all) of the stored value from the stored-value card (e.g., 910) to the virtual card stored on the electronic device 100, the virtual card includes at least some (or all) of the stored value, and the stored-value card (e.g., 910) no longer includes at least some (or all) of the stored value. In some embodiments, transferring at least some (or all) of the stored value from the stored-value card (e.g., 910) to the virtual card stored on the electronic device 100 includes removing the stored value from the stored-value card (e.g., 910) and transmitting (e.g., via a network or internet connection) a request to a server, service, or database associated with the card (e.g., 910) to deactivate the stored-value card (e.g., to cancel the card, rendering it inoperable). For example, all stored value from the stored-value card (e.g., 910) is removed and the stored-value card (e.g., 910) subsequently becomes inoperable. Thus, in some embodiments, all of the characteristics and / or values ​​of the physical card (e.g., 910) are moved to a virtual card stored on the electronic device 100, whereby the virtual card replaces the physical card (e.g., 910).

[0342] In some embodiments, before receiving the card account number of the stored-value card (e.g., 910) and before verifying ownership of the card (and / or before receiving an indication of ownership verification of the card), the virtual card is stored on the electronic device 100 (e.g., stored in an account information application of the electronic device 100) (e.g., as a template virtual card). In some embodiments, the electronic device 100 includes a template virtual card that already exists on the electronic device and does not include any value or funds (e.g., a "blank" virtual card). In some examples, the electronic device 100 transfers at least some (or all) of the stored value from the stored-value card (e.g., 910) to the template virtual card. Therefore, in some examples, there is no need to configure a new virtual card for the electronic device 100 because the features and / or values ​​of the card (e.g., 910) can be moved to the template virtual card. The use of the template virtual card speeds up the process of transferring funds from the stored-value card (e.g., 910) to the electronic device 100 because a new virtual card does not need to be created during the configuration process or transfer operation.

[0343] In some embodiments, as Figure 9MAs shown, based on determining that the value transfer has failed, the electronic device 100 displays and / or generates (e.g., to the user) feedback (e.g., indication 934A) indicating that the value transfer has failed (e.g., visual, audio, and / or tactile output generated by the device). In some embodiments, the electronic device 100 displays and / or generates (e.g., by the user) a second prompt (e.g., 934B different from the first prompt 930) to repeat the value transfer operation for the value transfer. In some examples, the second prompt includes visual, audio, and / or tactile feedback prompting the user to interact with the electronic device.

[0344] In some embodiments, as Figure 9N As shown, after successfully transferring at least some (or all) of the stored value from the card (e.g., 910) to the virtual card stored on the electronic device 100, the electronic device displays a representation of the virtual card corresponding to the stored-value card. In some embodiments, the representation of the virtual card corresponding to the stored-value card includes an indication of the type of the virtual card (e.g., 936A). In some embodiments, the representation of the virtual card corresponding to the stored-value card includes a graphical depiction of the virtual card (e.g., 936B). The indication of the type of the virtual card (e.g., 936A) and the graphical depiction (e.g., 936B) enable the user to distinguish the virtual card from different cards provided on the electronic device 100.

[0345] In some embodiments, a representation of a virtual card corresponding to a stored-value card provided on electronic device 100 includes a menu (e.g., 940) that includes a plurality of selectable affordances (e.g., 940A, 940B, 940C). In some examples, the menu (e.g., 940) includes an information affordance (e.g., 940A). In some examples, the menu (e.g., 940) includes a transaction affordance (e.g., 940B). In some examples, the menu (e.g., 940) includes a device affordance (e.g., 940C). In some embodiments, (e.g., in response to a user selection of an information affordance (e.g., 940A), as Figure 9N ), the representation of the virtual card displays, individually or simultaneously, one or more information items (e.g., 936C to 936E) about the virtual card corresponding to the configured card (e.g., 910). In some examples, the electronic device 100 displays the username of the account for which the virtual card is registered (e.g., 936C). In some examples, the electronic device 100 displays the balance of funds on the virtual card (e.g., 936D). In some examples, the electronic device 100 displays pass information (e.g., 936E) for the virtual card (e.g., a monthly pass, a 10-ride pass, etc.). One example of the electronic device 100 generating information about the details of the virtual card corresponding to the configured card (e.g., 910) for user perception (e.g., visual, audio, and / or tactile output generated by the device) is displaying information about the details of the virtual card on the display.

[0346] In some embodiments, after successfully transferring at least some (or all) of the stored value from the stored-value card (e.g., 910) to the virtual card stored on the electronic device 100, the electronic device displays the stored value of the virtual card corresponding to the stored-value card (e.g., 936D). For example, if the electronic wallet application of the electronic device 100 includes multiple virtual cards (or accounts) of the same type (e.g., multiple pass cards), the value of each of the multiple virtual cards is highlighted. This improved feedback enhances the operability of the electronic device by providing the user with the ability to distinguish multiple virtual cards stored on the electronic device (or accessible to the electronic device) and their corresponding stored values.

[0347] In some embodiments, after transferring at least some (or all) of the stored value from the stored value card (e.g., 910) to a virtual card stored on the electronic device 100, and based on determining that the electronic device has no other connected pass accounts (e.g., the newly configured pass account is the initially (first) configured pass account and / or the only currently valid pass account connected to the electronic device), the electronic device designates (designates by default or prompts the user to designate) the account of the virtual card as available for use without checking authentication. For example, if the virtual card corresponds to the initially (first) configured pass account, the virtual card corresponds to the only configured pass account and is thus the only currently valid pass account. In some examples, if the virtual card corresponds to the only configured pass account, the electronic device 100 designates the virtual card as a quick pass card based on determining that the virtual card is the only pass account of the account information application of the electronic device. In some embodiments, such as reference Figures 15A to 15M As described above, using an Express Pass card (e.g., for making a payment or transferring credentials) does not require an authentication check in certain circumstances (e.g., where the detected wireless signal corresponds to a transaction such as a request from a transaction terminal or a request for funds from a pass account). Thus, designating a virtual card as an Express Pass card reduces the amount of user input required, making the technology more efficient and conserving battery power.

[0348] In some embodiments, after transferring at least some (or all) of the stored value from the stored-value card (e.g., 910) to a virtual card stored on the electronic device 100, and based on determining that the virtual card does not correspond to a unique pass account configured on the account information application (e.g., e-wallet) of the electronic device, the electronic device abandons designating (or abandons prompting the user to designate) the account of the virtual card as available for use without checking authentication. For example, if the virtual card does not correspond to the initially (first) configured pass account, the virtual card does not correspond to the uniquely configured pass account and is therefore not the only currently valid pass account. In some examples, if the virtual card does not correspond to the uniquely configured pass account, the account designated by the electronic device 100 (or prompting the user to designate) the virtual card is not available for use without checking authentication. Therefore, in some examples, the electronic device 100 does not designate the virtual card as a quick pass card based on determining that the virtual card is not the unique pass account of the account information application.

[0349] In some embodiments, after transferring at least some (or all) of the stored value from the stored-value card (e.g., 910) to the virtual card stored on the electronic device 100, the electronic device forgoes designating (or forgoes prompting the user to designate) the virtual card's account as available for use without authentication based on a determination that the electronic device does not have another connected pass account (e.g., the newly configured pass account is the initially (first) configured pass account and / or the only currently valid pass account connected to the electronic device), and further based on receiving user input indicating that the account does not wish to be available for use without authentication (e.g., user input removing a previous Quick Pass card from the account information application or declining to add a previous account as a Quick Pass card). In some examples, the electronic device 100 designates (or prompts the user to designate) the virtual card's account as unavailable for use without authentication. Thus, in some examples, the electronic device 100 does not designate the virtual card as a Quick Pass card based on a determination that the virtual card is not the only pass account in the account information application. Thus, in some embodiments, the electronic device 100 adapts to the user's preferences to designate or forgo designating the virtual card as a Quick Pass card. Pass transactions are often conducted in crowded pass stations with users (or other passengers) eager to establish a pass connection. Even with the most accurate and reliable authentication systems, there is a possibility of a false negative result where a valid user fails to authenticate properly (for example, because the user's fingerprint is not correctly recognized or the user enters an incorrect password, passcode, or pattern). Using a fast pass transaction model that provides security by establishing the identity of the transaction terminal as a pass transaction terminal (for example, through a transaction terminal signal or other contextual information) rather than user authorization for a specific transaction, reduces the possibility that users (or other passengers) will be inconvenienced by false negative authentication results when conducting a pass transaction with the device.

[0350] Figure 10 1 is a flow chart illustrating a method for configuring an account on an electronic device according to some embodiments. Method 1000 is performed on a device (e.g., 100, 300, 500) having a display, one or more input devices, and one or more short-range communication radio components. Some operations in method 1000 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

[0351] As described below, method 1000 provides an intuitive way to manage transactions. This method reduces the cognitive burden on users managing transactions, thereby creating a more efficient human-computer interface. For battery-powered computing devices, this allows users to manage transactions more quickly and efficiently, conserving power and increasing the time between battery charges.

[0352] At block 1002, an electronic device requests (e.g., by displaying a prompt on a display of the electronic device) verification information (e.g., 914A-914B, 920A-920B) (e.g., a card number, date of birth, mailing address of a stored-value card) to verify ownership of a stored-value card (e.g., 910) (e.g., funds and / or data are physically stored in binary-encoded data on the card, an NFC-readable stored-value card, a stored-value pass, a stored-value gift card), wherein the stored-value card has a stored value. For example, the verification information is used to confirm ownership of the stored-value card. Thus, by verifying ownership, the operability of the electronic device is enhanced by preventing the device from being configured based on funds from an unauthorized card.

[0353] According to some embodiments, the stored-value card (e.g., 910) is a stored-value pass card. In some examples, the stored-value pass card stores pass plan (or pass ticket) information. In some examples, the pass plan is a monthly or weekly pass plan. In some examples, the stored-value pass card stores electronic cash. Thus, in some examples, the electronic device provides the user with the ability to configure an account that can be used to provide the user with access to a pass system.

[0354] According to some embodiments, the virtual card is a transit virtual card. In some examples, the transit virtual card stores transit plan (or pass ticket) information. In some examples, the transit plan is a monthly or weekly transit plan. In some examples, the transit virtual card stores electronic cash. According to some embodiments, the virtual card is a stored-value virtual card. In some examples, the stored-value virtual card stores electronic cash. Thus, in some examples, the electronic device provides the user with the ability to use the virtual card to provide the user with access to the transit system.

[0355] According to some embodiments, the verification information is a card account number of a stored-value card (e.g., 910). In some examples, the verification information is (or includes) the stored value of the stored-value card. Thus, in some examples, a user who knows the current stored value of the card can transfer at least some (or all) of the stored value from the card to a virtual card stored on the device.

[0356] According to some embodiments, the verification information (e.g., 920C) is personal information of a registered user of the stored-value card. In some examples, the verification information is a non-account identifier (e.g., a birthday). In some examples, the verification information is the birthday of the registered user of the stored-value card. In some examples, the verification information is the mailing address of the registered user of the stored-value card. Thus, in some examples, the electronic device provides additional security by requesting personal information for verification. Thus, by using the user's personal information to verify ownership, the operability of the electronic device is enhanced by providing an enhanced level of security to prevent the device from being configured based on funds from unauthorized cards.

[0357] At block 1004, the electronic device receives input from a user of the electronic device via one or more input devices (e.g., other than via one or more short-range communication radio components) including authentication information (e.g., 914C, 920C) for verifying ownership of a card (e.g., 910), wherein the authentication information includes information not shown on the card. In some examples, the authentication information is received via a first input device (e.g., a touch-sensitive surface, a microphone) of the electronic device that is different from the one or more short-range communication radio components.

[0358] According to some embodiments, the electronic device does not present (e.g., on the display of the electronic device) the card account number of the stored-value card (e.g., 910) before receiving input including verification information (e.g., 914C, 920C) for verifying the ownership of the card from the user of the electronic device through one or more input devices. Therefore, the user must access the card (or account) number through a method outside the electronic device. For example, the user may provide the card number based on the card number on the receipt or invoice printed on the card or based on the card number printed on the card. In some examples, based on determining that the card has been registered (e.g., "registered mode"), the electronic device presents (e.g., on the display of the electronic device) the account number of the card before receiving input including verification information for verifying the ownership of the card from the user of the device through one or more input devices.

[0359] At block 1006, the electronic device displays a prompt (e.g., 908, 930) on the display of the electronic device to place the electronic device within communication range (e.g., within communication range of one or more short-range communication radio components) of a stored-value card (e.g., 910). For example, the electronic device displays a prompt instructing the user to place the electronic device on the stored-value card so that the back of the electronic device (e.g., the side of the electronic device opposite the display) is closest to the stored-value card. In some examples, the prompt to place the device within communication range is provided after receiving the identification information. Thus, the electronic device notifies the user that the electronic device is attempting to communicate with the stored-value card by displaying the prompt, thereby prompting the user to place the electronic device near or on the stored-value card.

[0360] At block 1008, the electronic device receives identification information (e.g., a card number, date of birth, mailing address of the stored-value card) from a stored-value card (e.g., 910) via one or more short-range communication radio components (e.g., NFC radio components). For example, the electronic device interrogates the stored-value card to obtain the identification information.

[0361] At box 1010, the electronic device verifies the ownership of the stored-value card (e.g., 910) by comparing the verification information (e.g., 914C, 920C) with the identification information. Thus, by verifying the ownership of the stored-value card, the electronic device provides additional security by preventing individuals from electronically stealing funds from cards that do not belong to them. According to some embodiments, before receiving the card account number of the card (e.g., 910) and before verifying the ownership of the card, the virtual card is stored on the electronic device (e.g., in an account information application). In some examples, the electronic device includes a "blank" virtual card that does not have any value (e.g., funds). The electronic device transfers at least some (or all) of the stored value from the card to the "blank" virtual card. Therefore, there is no need to configure a new virtual card for the electronic device because funds can be provided to the existing virtual card. In some examples, this speeds up the process of transferring funds to the electronic device.

[0362] At block 1012, based on determining that ownership verification is successful (e.g., the verification information corresponds to (or matches) the identification information), at block 1014, the electronic device transfers at least some (or all) of the stored value from the stored-value card (e.g., 910) to a virtual card stored on the electronic device (e.g., to an account stored in an electronic wallet application on the electronic device). In some examples, the electronic device includes a secure element, and wherein transferring at least some of the stored value from the stored-value card to the virtual card stored on the electronic device includes storing information for accessing the stored value of the virtual card in the secure element of the electronic device. In some examples, when some or all of the stored value from the card is transferred to the virtual card, information for retrieving the value from the virtual card is stored in the secure element to ensure that the stored value cannot be accessed if a payment transaction in which the information is retrieved from the secure element is not properly processed. Thus, by transferring the value to the virtual card stored on the electronic device, the operability of the electronic device is enhanced because the device is able to participate in transactions using the newly transferred funds stored on the virtual card. In some examples, the verification information is a non-account identifier (e.g., a birthday), and the identification information is an account number. The electronic device uses the identification information to retrieve a non-account identifier (e.g., birthday) for the account corresponding to the account number (e.g., from a remote server). If the retrieved non-account identifier matches the verification information, the verification information is considered to correspond to the identification information and the verification is successful.

[0363] According to some embodiments, transferring at least some (or all) of the stored value from the stored-value card (e.g., 910) to a virtual card stored on the electronic device includes removing the stored value from the stored-value card (e.g., 910) and transmitting a request to the server to deactivate the stored-value card (e.g., 910) (e.g., cancel the card, rendering it inoperable). For example, the electronic device removes all of the value from the stored-value card and renders the card inoperable. Thus, in some examples, all of the features and / or values ​​of the stored-value card are moved to the virtual card, and the virtual card replaces the physical card.

[0364] According to some embodiments, at box 1016, based on determining that ownership verification failed (e.g., the verification information does not correspond to (or match) the identification information (e.g., ownership verification failed)), at box 1018, the electronic device displays and / or generates feedback (e.g., visual, audio, and / or tactile output generated by the device) indicating that ownership verification failed (e.g., indication 920D) (e.g., displaying a notification on the display of the electronic device), and at box 1020, (again, e.g., from the user) requests (e.g., by displaying a prompt on the display of the electronic device) verification information (e.g., card number, date of birth, mailing address of the stored-value card) to verify ownership of the stored-value card (e.g., 910). Therefore, in some examples, the electronic device notifies the user whether the verification information is incorrect. In this way, the electronic device notifies the user by generating feedback that the electronic device has determined that ownership verification failed, thereby prompting the user to provide information again to verify ownership.

[0365] According to some embodiments, after at least some of the stored values ​​are transferred from the stored-value card (e.g., 910) to a virtual card stored on the electronic device, the electronic device displays the stored value of the virtual card on a display. For example, when the electronic wallet application of the electronic device includes multiple virtual cards (or accounts) of the same type, the value of the virtual card is highlighted to help the user distinguish between the multiple virtual cards. Thus, the electronic device notifies the user of the stored value of the virtual card. This improved feedback enhances the operability of the electronic device by providing the user with the ability to distinguish multiple virtual cards stored on the electronic device (or accessible by the electronic device) and their corresponding stored values.

[0366] According to some embodiments, after transferring at least some (or all) of the stored value from the stored-value card (e.g., 910) to a virtual card stored on the electronic device, the electronic device displays pass plan information (e.g., a monthly pass, a 10-ride ticket, etc.) for the virtual card, which is based on at least some (or all) of the transferred stored value. Thus, the electronic device informs the user of the details of the virtual card. This improved feedback informs the user of the status of the electronic device, such as what virtual card is stored on the device and what pass plan information (if any) the virtual card includes.

[0367] According to some embodiments, after transferring at least some (or all) of the stored value from the stored-value card (e.g., 910) to the virtual card stored on the electronic device, the electronic device (e.g., simultaneously) displays one or more of the following: the balance of the virtual card (e.g., 936D), the username of the account registered for the virtual card (e.g., 936C), and the pass plan information (e.g., monthly pass, 10-ride ticket, etc.) of the virtual card (e.g., 936E). Thus, the electronic device informs the user of the details of the virtual card.

[0368] According to some embodiments, (for example, after transferring at least some (or all) of the stored values ​​from the card to the stored virtual card), based on determining that the electronic device does not have another connected pass account (for example, the newly configured pass account is the initially (first) configured pass account and / or the only currently valid pass account connected to the electronic device), the electronic device designates the account of the virtual card as available for use without checking authentication. In some examples, participating in a transaction using the account of the virtual card includes releasing information (for example, transaction information, payment information) from a secure element of the electronic device. Therefore, the electronic device designates (based on determining that the virtual card is the only pass account of the account information application) the virtual card as a quick pass card, and the electronic device can use the quick pass card without checking authentication for transactions in which the detected wireless signal corresponds to a first type of request (for example, a request from a transaction terminal, a request for funds from a pass account). Therefore, by automatically designating a virtual card as available for use without checking authentication, the operability of the electronic device is enhanced by reducing the number of inputs required to perform transaction operations using the virtual card. According to some embodiments, based on determining that the electronic device has one or more other connected pass accounts, the electronic device forgoes designating (or forgoes prompting the user to designate) the virtual card's account as available for use without checking for authentication (and / or designates the virtual card's account as unusable without checking for authentication). Thus, the electronic device does not designate (based on determining that the virtual card is not the only pass account in the account information application) the virtual card as a quick pass card.

[0369] According to some embodiments, (e.g., after transferring at least some (or all) of the stored value from the card to the stored virtual card), based on determining that the electronic device does not have another connected pass account (e.g., the newly configured pass account is the initially (first) configured pass account and / or the only currently valid pass account connected to the electronic device), and further based on receiving user input indicating that it is not desired that the account be available for use without checking authentication (e.g., user input that removed a previous Quick Pass card from the account information application), the electronic device abandons designating the virtual card's account as available for use without checking authentication (and / or designates the virtual card's account as unusable without checking authentication). Therefore, the electronic device does not designate (based on determining that the virtual card is not the only pass account in the account information application) the virtual card as a Quick Pass card. In some examples, based on not receiving user input indicating that it is not desired that the account be available for use without checking authentication, or based on receiving user input indicating that it is desired that the account be available for use without checking authentication, the electronic device selects the virtual card's account as available for use without checking authentication. Therefore, the electronic device designates the virtual card as a quick pass card, and the electronic device can use the quick pass card without checking and authenticating that the detected wireless signal corresponds to a transaction of the first type of request (e.g., a request from a transaction terminal, a fund request from a pass account).

[0370] According to some embodiments, the electronic device receives user input indicating that the account is not desired to be available for use without checking for authentication (e.g., by receiving user input selecting a "Do not use account" option to make it available for use without checking for authentication), and in response to receiving the user input indicating that the account is not desired to be available for use without checking for authentication, the account designated for the virtual card is not usable without checking for authentication. Thus, the user can disable the feature of the Express Pass account.

[0371] According to some embodiments, the electronic device receives user input selecting an account to be available for use without checking authentication (e.g., an account corresponding to a virtual card among multiple accounts of an account information application), and in response to receiving the user input selecting an account to be available for use without checking authentication, specifies that the selected account (e.g., an account of the account information application) is available for use without checking authentication, such as with respect to Figures 15A to 15M Thus, the user may specify that the selected account should be a QuickPass account.

[0372] Note that the above reference to method 1000 (e.g., Figure 10) also apply in a similar manner to the methods described above and below. For example, methods 800, 1200, 1400, 1600, 1800, and 2000 optionally include one or more features of the various methods described above with reference to method 1000. For example, Figure 7A The user interface can correspond to Figure 9A and Figure 15B . For another example, an account configured using the techniques of method 800 and method 1000 can be used to perform the techniques described with reference to methods 1200, 1400, 1600, 1800, and 2000. For another example, the techniques of method 1200 can be used to add funds to the stored value accounts described with reference to methods 800, 1000, 1400, 1600, 1800, and 2000. For another example, as discussed with reference to method 1800 and method 2000, the funded account can be moved to or from a different device. For the sake of brevity, these details are not repeated below.

[0373] Figures 11A to 11N An exemplary user interface for recharging a stored value account configured on an electronic device (e.g., 100) having a display and one or more input devices according to some embodiments is shown. The user interface in these figures is used to illustrate a system including FIG. 12A to FIG. 12B The process is described below.

[0374] According to some embodiments, a user wishes to add funds to a stored-value account on an electronic device. For example, the user initiates the process of withdrawing funds from a payment account (e.g., a revolving credit account) also stored on the electronic device and transferring the funds to a stored-value account (e.g., a transit account). In some examples, the user can use funds from the stored-value account alone to participate in transactions (e.g., using NFC to pay for a toll), and can use the payment account to participate in separate transactions (e.g., using NFC to pay for a retail purchase).

[0375] Figure 11A An exemplary electronic device 100 is shown. The electronic device 100 has an electronic wallet application including a stored value account and a payment account. The electronic device 100 displays a representation of the stored value account including an activatable top-up option on a display of the electronic device. Figures 11A to 11BA representation of a stored value account displayed on a display of an electronic device 100 according to some embodiments is shown. In some embodiments, the stored value account is a payment account. In some examples, the payment account corresponds to a revolving credit account or a debit account. In some embodiments, the stored value account is a pass account. In some examples, the pass account stores pass plan (or pass ticket) information. In some examples, the pass plan is a monthly or weekly pass plan. In some examples, the funds in the stored value account are physically stored on the electronic device 100 in the form of binary encoded data. In some examples, the stored value account is a closed-loop stored value account. In some examples, the stored value account stores electronic cash. In some embodiments, such as Figure 11A As shown, the representation of the stored value account includes a graphical depiction of the stored value account (e.g., 1142A). The graphical depiction of the stored value account (e.g., 1142A) enables a user to distinguish the stored value account from different accounts configured on the electronic device 100. In some embodiments, the representation of the stored value account includes an indication of the available balance (e.g., available funds) of the stored value account (e.g., 1142B).

[0376] In some embodiments, the representation of the stored value account includes a menu (e.g., 1140) that includes a plurality of selectable affordances (e.g., 1140A, 1140B, 1140C). In some examples, the menu (e.g., 1140) includes an information affordance (e.g., 1140A). In some examples, the menu (e.g., 1140) includes a transaction affordance (e.g., 1140B). In some examples, the menu (e.g., 1140) includes a device affordance (e.g., 1140C). In some embodiments (e.g., in response to a user selection of an information affordance (e.g., 1140A), Figure 11A As shown), the representation of the stored value account displays a transfer account option (e.g., 1146B). Thus, in some examples, the electronic device 100 provides the user with an option to move an account from one device to another, such as with reference to 17C to 17H As stated.

[0377] In some embodiments (e.g., in response to a user selection of an information affordance (e.g., 1140A), Figure 11A ), the representation of the stored-value account displays: an indication of the device (e.g., 1144) on which the stored-value account is currently located among one or more of the plurality of devices (e.g., associated with the user account); characteristics and / or data of the stored-value account (e.g., current balance, pass information); a selectable indication (e.g., 1148A) for enabling or disabling notifications; and a selectable indication (e.g., 1148B) for enabling or disabling the use of the stored-value account without checking for authentication, such as with reference to FIG. Figures 15A to 15Mand a selectable indication (e.g., 1148C) for designating or not designating a stored-value account as available for transactions at two or more devices (e.g., associated with a user account), even though payment credentials for the stored-value account are only stored at one time (a limitation of the stored-value account as a stored-value account) in only one of the two or more devices, such as reference Figures 19A to 19H As stated.

[0378] In some embodiments, the electronic device 100 receives user input indicating a desire to receive or not receive notifications about transactions associated with the stored value account (e.g., by moving a selection enable indication to an “on” or “off” position, as shown with respect to selection enable indication 1148A). In some embodiments, the electronic device 100 receives user input indicating a desire to make the stored value account available for use without checking for authentication (e.g., by moving a selection enable indic...

Claims

1. A method comprising: At an electronic device having a display and one or more input devices: concurrently displaying on the display representations of a plurality of devices associated with a user account, wherein the representations of the plurality of devices include a first representation of a first device and a second representation of a second device, wherein the first device is associated with a transaction account and the second device is not associated with the transaction account; receiving, via the one or more input devices, a selection corresponding to a graphical object associated with the trading account while simultaneously displaying the representations of the plurality of devices associated with a user account and a representation of the trading account; as well as In response to receiving the selection corresponding to the graphical object associated with the trading account: initiating a process for the transaction account to become associated with the second device; as well as A process is initiated to cause the transaction account to become disassociated from the first device. 2 . The method of claim 1 , wherein the first device is an electronic device that causes the transaction account to become associated with the second device and to be disassociated from the first device. 3 . The method of claim 1 , wherein the second device is an electronic device that causes the transaction account to become associated with the second device and to be disassociated from the first device.

4. The method according to any one of claims 1 to 3, wherein the transaction account is a payment account.

5. The method according to any one of claims 1 to 3, wherein the transaction account is a transit account.

6. The method according to any one of claims 1 to 3, wherein the transaction account is a stored value account.

7. The method according to any one of claims 1 to 3, wherein the transaction account is a stored value account, further comprising: prior to displaying the representations of the plurality of devices, displaying a representation of the account, simultaneously displaying an activatable top-up option and an activatable transfer account option; receiving activation of the transfer account option; and Wherein in response to receiving activation of the transfer account option, the representations of the plurality of devices associated with the user account are displayed.

8. The method according to any one of claims 1 to 3, further comprising: User input is received designating the transaction account as an account available for use at two or more of the plurality of devices.

9. The method according to any one of claims 1 to 3, wherein the electronic device is the second device, further comprising: receiving user input designating a third device of the plurality of devices as a device for which the transaction account may be used; After the transaction account becomes associated with the second device and after the transaction account becomes disassociated from the first device: receiving a request for payment credentials for the transaction account from a third device different from the electronic device; and Based on determining that the third device is designated as the device for which the transaction account is available, payment credentials for the transaction account are transmitted from the second device to the third device.

10. The method according to any one of claims 1 to 3, further comprising: Based on the time conditions determined, the conditions have been met: causing the transaction account to become disassociated from the second device; and The transaction account is caused to become associated with the first device.

11. The method of any one of claims 1 to 3, wherein causing the transaction account to become associated with the second device comprises limiting the transaction account at the second device to a maximum payment amount.

12. The method according to any one of claims 1 to 3, wherein causing the transaction account to become associated with the second device comprises restricting the transaction account at the second device to request corresponding prior permission from the first device to make the proposed payment at the second device.

13. The method of any one of claims 1 to 3, wherein the representation of the plurality of devices associated with the user account includes representations of devices logged into a service under the same user account as the electronic device.

14. A method according to any one of claims 1 to 3, wherein the representations of the multiple devices associated with the user account include representations of devices logged into the service using corresponding user accounts associated with the user account utilized by the electronic device to log into the service.

15. The method according to any one of claims 1 to 3, further comprising: After the transaction account becomes associated with the second device and after the transaction account becomes disassociated from the first device: displaying on the display a representation of the plurality of devices, wherein the first device is not associated with the transaction account and the second device is associated with the transaction account; receiving, via the one or more input devices, a corresponding selection corresponding to the first device; and In response to receiving the corresponding selection corresponding to the first device: causing the transaction account to become disassociated from the second device; and The transaction account is caused to become associated with the first device.

16. 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: concurrently displaying on the display representations of a plurality of devices associated with a user account, wherein the representations of the plurality of devices include a first representation of a first device and a second representation of a second device, wherein the first device is associated with a transaction account and the second device is not associated with the transaction account; receiving, via the one or more input devices, a selection corresponding to a graphical object associated with the trading account while simultaneously displaying the representations of the plurality of devices associated with a user account and a representation of the trading account; as well as In response to receiving the selection corresponding to the graphical object associated with the trading account: initiating a process for the transaction account to become associated with the second device; as well as A process is initiated to cause the transaction account to become disassociated from the first device.

17. The computer-readable storage medium of claim 16, wherein the first device is an electronic device that causes the transaction account to become associated with the second device and to be disassociated from the first device.

18. The computer-readable storage medium of claim 16, wherein the second device is an electronic device that causes the transaction account to become associated with the second device and to be disassociated from the first device.

19. The computer-readable storage medium according to any one of claims 16 to 18, wherein the transaction account is a payment account.

20. The computer-readable storage medium of any one of claims 16 to 18, wherein the transaction account is a transit account.

21. The computer-readable storage medium of any one of claims 16 to 18, wherein the transaction account is a stored value account.

22. The computer-readable storage medium of any one of claims 16 to 18, wherein the transaction account is a stored value account, and the one or more programs further comprise instructions for: prior to displaying the representations of the plurality of devices, displaying a representation of the account, simultaneously displaying an activatable top-up option and an activatable transfer account option; receiving activation of the transfer account option; and Wherein in response to receiving activation of the transfer account option, the representations of the plurality of devices associated with the user account are displayed.

23. The computer-readable storage medium of any one of claims 16 to 18, wherein the one or more programs further comprise instructions for: User input is received designating the transaction account as an account available for use at two or more of the plurality of devices.

24. The computer-readable storage medium according to any one of claims 16 to 18, wherein the electronic device is the second device, and the one or more programs further include instructions for performing the following operations: receiving user input designating a third device of the plurality of devices as a device for which the transaction account may be used; After the transaction account becomes associated with the second device and after the transaction account becomes disassociated from the first device: receiving a request for payment credentials for the transaction account from a third device different from the electronic device; and Based on determining that the third device is designated as the device for which the transaction account is available, payment credentials for the transaction account are transmitted from the second device to the third device.

25. The computer-readable storage medium of any one of claims 16 to 18, wherein the one or more programs further comprise instructions for: Based on the time conditions determined, the conditions have been met: causing the transaction account to become disassociated from the second device; and The transaction account is caused to become associated with the first device.

26. The computer-readable storage medium of any one of claims 16 to 18, wherein causing the transaction account to become associated with the second device comprises limiting the transaction account at the second device to a maximum payment amount.

27. The computer-readable storage medium of any one of claims 16 to 18, wherein causing the transaction account to become associated with the second device comprises restricting the transaction account at the second device to request corresponding prior permission from the first device to make the proposed payment at the second device.

28. The computer-readable storage medium of any one of claims 16 to 18, wherein the representation of the plurality of devices associated with the user account includes representations of devices logged into a service under the same user account as the electronic device.

29. A computer-readable storage medium according to any one of claims 16 to 18, wherein the representations of the multiple devices associated with the user account include representations of devices logged into the service using corresponding user accounts associated with the user account utilized by the electronic device to log into the service.

30. The computer-readable storage medium of any one of claims 16 to 18, wherein the one or more programs further comprise instructions for: After the transaction account becomes associated with the second device and after the transaction account becomes disassociated from the first device: displaying on the display a representation of the plurality of devices, wherein the first device is not associated with the transaction account and the second device is associated with the transaction account; receiving, via the one or more input devices, a corresponding selection corresponding to the first device; and In response to receiving the corresponding selection corresponding to the first device: causing the transaction account to become disassociated from the second device; and The transaction account is caused to become associated with the first device.

31. An electronic device comprising: monitor; 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: concurrently displaying on the display representations of a plurality of devices associated with a user account, wherein the representations of the plurality of devices include a first representation of a first device and a second representation of a second device, wherein the first device is associated with a transaction account and the second device is not associated with the transaction account; receiving, via the one or more input devices, a selection corresponding to a graphical object associated with the trading account while simultaneously displaying the representations of the plurality of devices associated with a user account and a representation of the trading account; as well as In response to receiving the selection corresponding to the graphical object associated with the trading account: initiating a process for the transaction account to become associated with the second device; as well as A process is initiated to cause the transaction account to become disassociated from the first device.

32. The electronic device of claim 31, wherein the first device is an electronic device that causes the transaction account to become associated with the second device and to be disassociated from the first device.

33. The electronic device of claim 31, wherein the second device is an electronic device that causes the transaction account to become associated with the second device and to be disassociated from the first device.

34. An electronic device according to any one of claims 31 to 33, wherein the transaction account is a payment account.

35. An electronic device according to any one of claims 31 to 33, wherein the transaction account is a transit account.

36. An electronic device as claimed in any one of claims 31 to 33, wherein the transaction account is a stored value account.

37. The electronic device of any one of claims 31 to 33, wherein the transaction account is a stored value account, and the one or more programs further comprise instructions for: prior to displaying the representations of the plurality of devices, displaying a representation of the account, simultaneously displaying an activatable top-up option and an activatable transfer account option; receiving activation of the transfer account option; and Wherein in response to receiving activation of the transfer account option, the representations of the plurality of devices associated with the user account are displayed.

38. The electronic device of any one of claims 31 to 33, wherein the one or more programs further comprise instructions for performing the following operations: User input is received designating the transaction account as an account available for use at two or more of the plurality of devices.

39. The electronic device according to any one of claims 31 to 33, wherein the electronic device is the second device, and the one or more programs further include instructions for performing the following operations: receiving user input designating a third device of the plurality of devices as a device for which the transaction account may be used; After the transaction account becomes associated with the second device and after the transaction account becomes disassociated from the first device: receiving a request for payment credentials for the transaction account from a third device different from the electronic device; and Based on determining that the third device is designated as the device for which the transaction account is available, payment credentials for the transaction account are transmitted from the second device to the third device.

40. The electronic device of any one of claims 31 to 33, wherein the one or more programs further comprise instructions for performing the following operations: Based on the time conditions determined, the conditions have been met: causing the transaction account to become disassociated from the second device; and The transaction account is caused to become associated with the first device.

41. An electronic device according to any one of claims 31 to 33, wherein causing the transaction account to become associated with the second device comprises limiting the transaction account at the second device to a maximum payment amount.

42. An electronic device according to any one of claims 31 to 33, wherein causing the transaction account to become associated with the second device includes restricting the transaction account at the second device to request corresponding prior permission from the first device to make the proposed payment at the second device.

43. An electronic device according to any one of claims 31 to 33, wherein the representation of the plurality of devices associated with the user account includes representations of devices logged into a service under the same user account as the electronic device.

44. An electronic device according to any one of claims 31 to 33, wherein the representations of the multiple devices associated with the user account include representations of devices logged into the service using corresponding user accounts associated with the user account utilized by the electronic device to log into the service.

45. The electronic device of any one of claims 31 to 33, wherein the one or more programs further comprise instructions for performing the following operations: After the transaction account becomes associated with the second device and after the transaction account becomes disassociated from the first device: displaying on the display a representation of the plurality of devices, wherein the first device is not associated with the transaction account and the second device is associated with the transaction account; receiving, via the one or more input devices, a corresponding selection corresponding to the first device; and In response to receiving the corresponding selection corresponding to the first device: causing the transaction account to become disassociated from the second device; and The transaction account is caused to become associated with the first device.

46. ​​An electronic device comprising: monitor; one or more input devices; and Device for carrying out the method according to any one of claims 1 to 15.

47. A computer program product comprising program code portions for performing a method according to any one of claims 1 to 15 when the computer program product is run on one or more computing devices.

Images