User interface for stored value accounts

Abstract

This invention is entitled "User Interface for Stored-Value Accounts." This disclosure relates to a computer user interface. In some examples, an account is configured on an electronic device. In some examples, the device receives a value to provide funds to an account configured on the electronic device. In some examples, the electronic device uses the configured account to transact with a contactless transaction terminal and displays instructions for 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 initiating a process to move 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 is 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, entry into the Chinese national phase date February 2, 2018, Chinese national application number 201780002648.4, and invention title "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 incorporated herein by reference in its entirety for all purposes.

[0004] This application relates to U.S. Patent Application Serial No. 61 / 912,727, filed December 6, 2013, entitled “Provisioning and Authenticating Credits on an Electronic Device,” and U.S. Patent Application Serial No. 62 / 004,837, filed May 29, 2014, entitled “Methods for Managing Payment Applets on a Structural to Conducive Mobile Payment Transactions,” the contents of which are incorporated herein by reference. Technical Field

[0005] This disclosure relates generally to computer user interfaces, and more specifically to technologies for managing transactions and accounts. Background Technology

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

[0007] However, some technologies used to manage 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 involve multiple keystrokes or button presses. Similarly, some existing technologies for participating in transactions require users to provide input to specify an account, unlock the device, or authenticate during a transaction. These existing technologies take more time than necessary, wasting both user time and device power. This latter consideration is particularly important in battery-powered devices.

[0008] Therefore, this technology provides electronic devices with faster and more efficient methods and interfaces for managing transactions and accounts. Such methods and interfaces optionally complement or replace other methods used for managing accounts and transactions. These methods and interfaces reduce the cognitive burden on users and result in more efficient human-computer interfaces. For battery-powered computing devices, such methods and interfaces save power and increase the time interval between battery charges. Furthermore, such methods and interfaces reduce the amount of input required at electronic devices such as smartphones and smartwatches.

[0009] According to some embodiments, a method is described performed at an electronic device having one or more input devices and one or more short-range communication radio components. The method includes: receiving a card account number of a card, wherein the card has stored values, by the one or more short-range communication radio components; 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 the successful verification of ownership: 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 values ​​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. This 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 include instructions for performing the following operations: receiving a card account number of a card, wherein the card has stored values, by the one or more short-range communication radio components; 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, upon successful ownership verification: 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 values ​​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. This 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 include instructions for performing the following operations: receiving a card account number of a card, wherein the card has stored values, by the one or more short-range communication radio components; 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 successful ownership verification: 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 values ​​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 a card account number of a card, wherein the card has stored values, by the one or more short-range communication radio components; 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, upon successful verification of ownership: 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 values ​​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; means for: receiving a card account number of a card, wherein the card has stored values, by the one or more short-range communication radio components; means for: requesting verification information to verify ownership of the card; 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; means for: verifying ownership of the card by comparing the verification information with independent information about the card received independently of the verification information; and means for: generating a prompt to perform a value transfer operation for value transfer based on successful ownership verification; and in conjunction with the value transfer operation, transferring at least some of the stored values ​​from the card to a virtual card stored on the electronic device.

[0014] According to some embodiments, a method is described performed 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 prepaid card, wherein the prepaid 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 indicating that the electronic device should be placed within communication range of the prepaid card; receiving identification information from the prepaid card by the one or more short-range communication radio components; verifying ownership of the prepaid card by comparing the verification information and the identification information; and, based on successful ownership verification, transferring at least some of the stored value from the prepaid card to a virtual card stored on the electronic device.

[0015] According to some embodiments, a non-transitory computer-readable storage medium is described. This 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 include instructions for performing the following operations: requesting verification information to verify ownership of a stored-value card, wherein the stored-value card has a 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 indicating that the electronic device should be placed 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 and the identification information; and, based on successful ownership verification, 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. This 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 include instructions for performing the following operations: requesting verification information to verify ownership of a stored-value card, wherein the stored-value card has a 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 indicating that the electronic device should be placed 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 and the identification information; and, based on successful ownership verification, 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 a 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 indicating that the electronic device should be placed 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 and the identification information; and, upon successful verification of ownership, 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 indicating that the electronic device should be placed 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 and 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 if ownership verification is successful.

[0019] According to some implementations, 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 including an activatable top-up option, wherein the electronic device has an e-wallet application including a stored-value account and a payment account; detecting activation of the top-up option via the one or more input devices while the stored-value account representation is displayed; detecting activation of a funds account option via the one or more input devices to top up the stored-value account using the payment account of the e-wallet application; receiving authentication information at the electronic device while a proposed transaction for adding funds from the payment account to the stored-value account is displayed; and in response to receiving the authentication information, and based on determining that the authentication information matches registered authentication information used to perform a payment transaction using the payment account, topping up the stored-value account using the payment account.

[0020] According to some embodiments, a non-transitory computer-readable storage medium is described. This 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 including an activatable top-up option, wherein the electronic device has an e-wallet application including a stored-value account and a payment account; detecting activation of the top-up option via the one or more input devices while displaying the stored-value account representation; detecting activation of a funds account option via the one or more input devices to top up the stored-value account using the payment account of the e-wallet application; receiving authentication information at the electronic device while displaying a proposed transaction for adding 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 matches registered authentication information used to perform a payment transaction using the payment account, topping up the stored-value account using the payment account.

[0021] According to some embodiments, a transient computer-readable storage medium is described. This 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 including an activatable top-up option, wherein the electronic device has an e-wallet application including a stored-value account and a payment account; detecting activation of the top-up option via the one or more input devices while displaying the stored-value account representation; detecting activation of a funds account option via the one or more input devices to top up the stored-value account using the payment account of the e-wallet application; receiving authentication information at the electronic device while displaying a proposed transaction for adding 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 matches registered authentication information used to perform a payment transaction using the payment account, topping 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 including an activatable top-up option, wherein the electronic device has an e-wallet application including a stored-value account and a payment account; detecting activation of the top-up option via the one or more input devices while displaying the stored-value account representation; detecting activation of a funds account option via the one or more input devices to top up the stored-value account using the payment account of the e-wallet application; receiving authentication information at the electronic device while displaying a proposed transaction for adding 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 matches registered authentication information used to perform a payment transaction using the payment account, topping 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 operating: displaying a representation of a stored-value account on the display, the representation including an activatable top-up option, wherein the electronic device has an e-wallet application including a stored-value account and a payment account; means for operating: detecting activation of the top-up option via the one or more input devices when the stored-value account representation is displayed; means for operating: detecting activation of the funds account option via the one or more input devices to top up the stored-value account using the payment account of the e-wallet application; means for operating: receiving authentication information at the electronic device when a proposed transaction for adding funds from the payment account to the stored-value account is displayed; and means for operating: in response to receiving the authentication information, and based on determining that the authentication information matches registered authentication information used to perform a payment transaction using the payment account, to top up the stored-value account using the payment account.

[0024] According to some embodiments, a method is described performed on an electronic device having a display, one or more short-range communication radio components, and an e-wallet application including a stored-value account. The method includes: displaying an indication of available balance in 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 available balance with a display corresponding to an indication of the transaction that transmitted the credentials to the contactless transaction terminal, based on a transaction executed using the credentials of the stored-value account via the contactless transaction terminal, wherein the credentials of the stored-value account 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. This 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 an electronic wallet application including a stored-value account. The one or more programs include instructions for performing the following operations: displaying an indication of available balance in the stored-value account on the display; transmitting credentials of 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 available balance with an indication corresponding to the transaction of transmitting credentials to the contactless transaction terminal based on a transaction executed using the credentials of the stored-value account via the contactless transaction terminal, wherein the credentials of the stored-value account are transmitted to the contactless transaction terminal using the one or more short-range communication radio components.

[0026] According to some embodiments, a transient computer-readable storage medium is described. This 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 an electronic wallet application including a stored-value account. The one or more programs include instructions for performing the following operations: displaying an indication of available balance in the stored-value account on the display; transmitting credentials of 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 available balance with a display corresponding to an indication of the transaction that transmits credentials to the contactless transaction terminal, based on a transaction executed using the credentials of the stored-value account via the contactless transaction terminal, wherein the credentials of the stored-value account are transmitted to the contactless transaction terminal using the one or more short-range communication radio components.

[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 e-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 available balance in the stored-value account on the display; transmitting credentials of 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 available balance with a display corresponding to an indication of the transaction transmitting credentials to the contactless transaction terminal based on a transaction executed using the credentials of the stored-value account via the contactless transaction terminal, wherein the credentials of the stored-value account are 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 radio components; an electronic wallet application including a stored-value account; means for: displaying an indication of the available balance of the stored-value account on the display; means for: transmitting credentials of 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 means for: replacing the display of the indication of the available balance with a display corresponding to an indication of the transaction that transmits credentials to the contactless transaction terminal, based on a transaction executed using the credentials of the stored-value account via the contactless transaction terminal, wherein the credentials of the stored-value account are transmitted to the contactless transaction terminal using the one or more short-range communication radio components.

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

[0030] According to some embodiments, a non-transitory computer-readable storage medium is described. This 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 include instructions for performing the following operations: detecting a radio signal by the one or more short-range communication radio components; transmitting information corresponding to the first account without checking authentication based on determining that the radio signal corresponds to a first type of request; and continuing the transaction corresponding to the radio signal after checking authentication based on determining that the radio signal corresponds to a second type of request.

[0031] According to some embodiments, a transient computer-readable storage medium is described. This 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 include instructions for performing the following operations: detecting a radio signal by the one or more short-range communication radio components; transmitting information corresponding to the first account without checking authentication if the radio signal is determined to correspond to a first type of request; and continuing the transaction corresponding to the radio signal after checking authentication if the radio signal is determined to correspond 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 radio signal by the one or more short-range communication radio components; transmitting information corresponding to the first account without checking authentication if the radio signal is determined to correspond to a first type of request; and continuing the transaction corresponding to the radio signal after checking authentication if the radio signal is determined to correspond 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 authentication based on determining that the wireless signal corresponds to a first type of request; and means for: continuing to perform a transaction corresponding to the wireless signal after checking authentication based on determining that the wireless signal corresponds to a second type of request.

[0034] According to some embodiments, a method is described that is performed at an electronic device having a display and one or more input devices. The method includes: displaying on the display a representation of a plurality of devices associated with a user account, wherein the representation of the plurality of devices includes 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 a transaction account; receiving, via the one or more input devices, a selection corresponding to the displayed representation of the second device; and, based on the received selection corresponding to the displayed representation of the second device: associating the transaction account with the second device; and deassociating the transaction account from the first device.

[0035] According to some embodiments, a non-transitory computer-readable storage medium is described. This 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 include instructions for performing the following operations: displaying on the display a representation of a plurality of devices associated with a user account, wherein the representation of the plurality of devices includes 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 a transaction account; receiving via the one or more input devices a selection corresponding to the displayed representation of the second device; and, based on the received selection corresponding to the displayed representation of the second device: associating the transaction account with the second device; and deassociating the transaction account from the first device.

[0036] According to some embodiments, a transient computer-readable storage medium is described. This 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 include instructions for performing the following operations: 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 a transaction account; receiving via the one or more input devices a selection corresponding to the displayed representation of the second device; and, based on the received selection corresponding to the displayed representation of the second device: associating the transaction account with the second device; and unassociating 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 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 a transaction account; receiving via the one or more input devices a selection corresponding to the displayed representation of the second device; and, based on the received selection corresponding to the displayed representation of the second device: associating the transaction account with the second device; and unassociating the transaction account 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 operating on the display to show 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; means for operating to receive, via the one or more input devices, a selection corresponding to the displayed representation of the second device; and means for operating to associate the transaction account with the second device and, based on the received selection corresponding to the displayed representation of the second device, deassociate the transaction account from the first device.

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

[0040] According to some embodiments, a non-transitory computer-readable storage medium is described. This 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 include instructions for performing the following operations: detecting that one or more payment criteria for making a payment using a stored-value account have been met; in response to detecting that 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 unavailable in the electronic wallet application of the electronic device, requesting payment credentials from a stored-value account of a second device different from the electronic device; and after requesting payment credentials from a stored-value account of the second device when payment credentials for the stored-value account are available at the second device, receiving payment credentials from the stored-value account of 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 include instructions for performing the following operations: detecting that one or more payment criteria for making a payment using a stored-value account have been met; in response to detecting that 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 unavailable in the electronic wallet application of the electronic device, requesting payment credentials from a stored-value account of a second device different from the electronic device; and after requesting payment credentials from a stored-value account of the second device when payment credentials for the stored-value account are available at the second device, receiving payment credentials from the stored-value account of 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 one or more payment criteria for making a payment using a stored-value account have been met; in response to detecting that 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 unavailable in the electronic wallet application of the electronic device, requesting payment credentials from a stored-value account of a second device different from the electronic device; and after requesting payment credentials from a stored-value account of the second device when payment credentials for the stored-value account are available at the second device, receiving payment credentials from the stored-value account of 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 one or more payment criteria for making a payment using a stored-value account have been satisfied; means for: in response to detecting that one or more payment criteria for making a payment using a stored-value account have been satisfied, and based on determining that payment credentials for the stored-value account are unavailable in the electronic wallet application of the electronic device, requesting payment credentials from a stored-value account of a second device different from the electronic device; and means for: after requesting payment credentials from a stored-value account of the second device when payment credentials for the stored-value account are available at the second device, receiving payment credentials from the stored-value account of the second device at the electronic 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 is configured to: receive a card account number of a card from the one or more short-range communication radio units, wherein the card has stored values; 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, upon successful verification of ownership, 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 values ​​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 is 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 the display unit of the electronic device to display a prompt indicating that the electronic device is within communication range of the stored-value card; receive identification information from the stored-value card via the one or more short-range communication radio units; verify ownership of the stored-value card by comparing the verification information and the identification information; and, based on successful ownership verification, 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 is configured to: enable the 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 e-wallet application including a stored-value account and a payment account; upon enabling the 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 funds account option via the one or more input device units to top up the stored-value account using the payment account of the e-wallet application; upon enabling the display of a proposed transaction for adding 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 matches registered authentication information used to perform a payment transaction 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 radio units; an e-wallet application unit including a stored-value account; and a processing unit coupled to the display unit, the one or more short-range communication radio units, and the e-wallet application unit including the stored-value account. The processing unit is configured to: enable the display of an indication of the available balance of the stored-value account on the display unit; transmit credentials of the stored-value account to a contactless transaction terminal separate from the electronic device using the one or more short-range communication radio units; and replace the display of the indication of the available balance with a display of an indication corresponding to the transaction of transmitting credentials to the contactless transaction terminal based on a transaction executed using the credentials of the stored-value account via the contactless transaction terminal, wherein the credentials of the stored-value account are transmitted to the contactless transaction terminal using the one or more short-range communication radio units.

[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; transmit information corresponding to the first account without authentication checks if the wireless signal corresponds to a first type of request; and continue with the transaction corresponding to the wireless signal after authentication checks if the wireless signal corresponds to a second type of request.

[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: display on the display unit a representation of a plurality of devices associated with a user account, wherein the plurality of devices includes 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 a transaction account; receive via the one or more input device units a selection corresponding to the displayed representation of the second device; and, based on receiving the selection corresponding to the displayed representation of the second device: associate the transaction account with the second device; and cause the transaction account to detach 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 one or more payment criteria for making payments using a stored-value account have been met; in response to detecting that one or more payment criteria for making payments using a stored-value account have been met and determining that payment credentials for the stored-value account are unavailable in the electronic wallet application of the electronic device, request payment credentials from a stored-value account of a second device different from the electronic device; and after requesting payment credentials from the stored-value account of the second device when payment credentials for the stored-value account are available at the second device, receive payment credentials from the stored-value account of 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.

[0052] Therefore, faster and more efficient methods and interfaces are provided for managing transactions, thereby improving the effectiveness, efficiency, and user satisfaction of such devices. These methods and interfaces can complement or replace other methods used for managing transactions. Attached Figure Description

[0053] To better understand the various described embodiments of the present invention, reference should be made to the following detailed description in conjunction with the accompanying drawings, in which similar reference numerals indicate corresponding parts throughout the drawings.

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

[0055] Figure 1B This is a block diagram illustrating exemplary components for event handling according to some implementation schemes.

[0056] Figure 2 A portable multi-functional device with a touchscreen is shown according to some embodiments.

[0057] Figure 3 This is a block diagram of an exemplary multifunctional device having a display and a touch-sensitive surface according to some implementation schemes.

[0058] Figure 4A An exemplary user interface for a menu on a portable multifunction device, according to some implementation schemes, is shown.

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

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

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

[0062] Figures 5C-5D Exemplary components of a personal electronic device having a touch-sensitive display and an intensity sensor according to some embodiments are shown.

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

[0064] Figure 6 An exemplary device connected via one or more communication channels according to some implementation schemes is shown.

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

[0066] Figures 8A to 8B This is a flowchart illustrating a method for configuring a card onto an electronic device according to some implementation schemes.

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

[0068] Figure 10 This is a flowchart illustrating a method for configuring a card onto an electronic device according to some implementation schemes.

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

[0070] Figures 12A to 12B This is a flowchart illustrating a method for topping up a stored-value account provided on an electronic device according to some implementation schemes.

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

[0072] Figures 14A to 14B This is a flowchart illustrating a method for transmitting stored-value account credentials to a terminal according to some implementation schemes.

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

[0074] Figures 16A to 16B This is a flowchart illustrating a method for making an account available without checking authentication, according to some implementation schemes.

[0075] Figures 17A to 17H An exemplary user interface for moving a trading account from one device to another is shown according to some implementation schemes.

[0076] Figure 18 This is a flowchart illustrating a method for moving a trading account from one device to another according to some implementation schemes.

[0077] Figures 19A to 19H An exemplary user interface for an account available on one or more of a plurality of devices is shown, according to some implementation schemes.

[0078] Figures 20A to 20B This is a flowchart illustrating a method for managing accounts available on one or more devices across multiple devices, according to some implementation schemes.

[0079] Figures 21 to 27 A functional block diagram based on some implementation schemes is shown. Detailed Implementation

[0080] The following description illustrates exemplary methods, parameters, etc. However, it should be understood that such description is not intended to limit the scope of this 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 increasing productivity. Furthermore, these technologies can reduce processor and battery power that would otherwise be wasted on redundant user input.

[0082] under Figures 1A to 1B , Figure 2 , Figure 3 , Figures 4A to 4B and Figures 5A to 5H A description of an exemplary device for performing technology for managing accounts and transactions is provided. Figure 6 An exemplary device connected via one or more communication channels according to some implementation schemes is shown. Figures 7A to 7P An exemplary user interface for configuring a card onto an electronic device is shown according to some implementation schemes. Figures 8A to 8B This is a flowchart illustrating a method for configuring a card onto an electronic device according to some implementation schemes. Figures 7A to 7PThe user interface in the document is used to display including Figures 8A to 8B The process described below is the process in the middle. Figures 9A to 9N An exemplary user interface for configuring a card onto an electronic device is shown according to some implementation schemes. Figure 10 This is a flowchart illustrating a method for configuring a card onto an electronic device according to some implementation schemes. Figures 9A to 9N The user interface in the document is used to display including Figure 10 The process described below is the process in the middle. Figures 11A to 11N An exemplary user interface for topping up a stored-value account provided on an electronic device is shown according to some implementation schemes. Figures 12A to 12B This is a flowchart illustrating a method for topping up a stored-value account provided on an electronic device according to some implementation schemes. Figures 11A to 11N The user interface in the document is used to display including Figures 12A to 12B The process described below is the process in the middle. Figures 13A to 13N An exemplary user interface for transferring stored-value account credentials to a terminal is shown. Figures 14A to 14B This is a flowchart illustrating a method for transmitting stored-value account credentials to a terminal according to some implementation schemes. Figures 13A to 13N The user interface in the document is used to display including Figures 14A to 14B The process described below is the process in the middle. Figures 15A to 15M An exemplary user interface for making an account available without checking authentication is shown according to some implementation schemes. Figures 16A to 16B This is a flowchart illustrating a method for making an account available without checking authentication, according to some implementation schemes. Figures 15A to 15M The user interface in the document is used to display including Figures 16A to 16B The process described below is the process in the middle. Figures 17A to 17H An exemplary user interface for moving a trading account from one device to another is shown according to some implementation schemes. Figure 18 This is a flowchart illustrating a method for moving a trading account from one device to another according to some implementation schemes. Figures 17A to 17H The user interface in the document is used to display including Figure 18 The process described below is the process in the middle. Figures 19A to 19H An exemplary user interface for an account available on one or more of a plurality of devices is shown, according to some implementation schemes. Figures 20A to 20B This is a flowchart illustrating a method for managing accounts available on one or more devices across multiple devices, according to some implementation schemes. Figures 19A to 19H The user interface in the document is used to display including Figures 20A to 20B The process described below is the process in the middle. Figures 21 to 27 A functional block diagram based on some implementation schemes 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 may be named a second touch and similarly, a second touch may be named a first touch, without departing from the scope of the various described embodiments. Both a first touch and a second touch are touches, but they are not the same touch.

[0084] The terminology used in the description of the various embodiments herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used in the description of the various embodiments and the appended claims, the singular form “a” (“a”, “an”) is intended to include the plural form as well, unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used herein refers to and covers any and all possible combinations of one or more of the items listed in connection with the description. It will also be understood that the terms “includes” (“including”, “comprises”, and / or “comprising”), when used in this specification, specify the presence of the stated features, integers, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0085] Depending on the context, the term "if" may optionally be interpreted as meaning "when" or "upon" or "in response to determination" or "in response to detection". Similarly, depending on the context, the phrases "if it is determined..." or "if [the stated condition or event] is detected" may optionally be interpreted as meaning "in response to determination..." or "in response to detection of [the stated condition or event]".

[0086] This document describes implementations of electronic devices, user interfaces for such devices, and associated processes for using such devices. In some implementations, the device is a portable communication device, such as a mobile phone, that also includes other functionalities such as PDA and / or music player functionality. Exemplary implementations of portable multi-functional devices include, but are not limited to, the iPhone from Apple Inc. (Cupertino, California). ® Devices, iPod Touch ® Devices and iPads ®Device. Optionally, other portable electronic devices may be used, such as laptops or tablets with touch-sensitive surfaces (e.g., touchscreen displays and / or touchpads). It should also be understood that in some embodiments, the device is not a portable communication device, but a desktop computer with touch-sensitive surfaces (e.g., touchscreen displays and / or touchpads).

[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: drawing applications, presentation applications, word processing applications, website creation applications, disk editing applications, spreadsheet applications, game applications, phone applications, video conferencing applications, email applications, instant messaging applications, fitness support applications, photo management applications, digital camera applications, digital video camcorder applications, web browsing applications, digital music player applications, and / or digital video player applications.

[0089] Various applications running on the device optionally use at least one common physical user interface device, such as a touch-sensitive surface. One or more functions of the touch-sensitive surface and the 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 device's common physical architecture (such as the touch-sensitive surface) optionally utilizes a user interface that is intuitive and clear to the user to support various applications.

[0090] The focus is now on implementation schemes for portable devices with touch-sensitive displays. Figure 1AThis is a block diagram illustrating a portable multi-functional device 100 with a touch-sensitive display system 112 according to some embodiments. The touch-sensitive display 112 is sometimes referred to as a “touchscreen” for convenience, and may also be referred to as or called a “touch-sensitive display system.” Device 100 includes a memory 102 (which optionally includes one or more computer-readable storage media), a memory controller 122, one or more processing units (CPUs) 120, a peripheral interface 118, RF circuitry 108, audio circuitry 110, a speaker 111, a microphone 113, an input / output (I / O) subsystem 106, other input control devices 116, and an external port 124. Device 100 optionally includes one or more optical sensors 164. Device 100 optionally includes one or more contact strength sensors 165 for detecting the intensity of contact on device 100 (e.g., a touch-sensitive surface, such as the touch-sensitive display system 112 of device 100). Device 100 optionally includes one or more haptic output generators 167 for generating haptic output on device 100 (e.g., generating haptic output on a touch-sensitive surface such as the touch-sensitive display system 112 of device 100 or the touchpad 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 contact on a tactile surface refers to the force or pressure (force per unit area) of a contact (e.g., finger contact) on a tactile surface, or to a substitute (alternative) for the force or pressure of a contact on a tactile surface. The intensity of contact has a range of values ​​that includes at least four different values ​​and more typically hundreds of different values ​​(e.g., at least 256). The intensity of 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 tactile surface are optionally used to measure the force at different points on the tactile surface. In some embodiments, force measurements from multiple force sensors are combined (e.g., weighted average) to determine an estimated contact force. Similarly, the pressure-sensitive tip of a stylus is optionally used to determine the pressure of the stylus on the tactile surface. Alternatively, the size and / or variation of the contact area detected on the touch-sensitive surface, the capacitance and / or variation of the touch-sensitive surface adjacent to the contact, and / or the resistance and / or variation of the touch-sensitive surface adjacent to the contact are optionally used as substitutes for the force or pressure of the contact on the touch-sensitive surface. In some embodiments, the substitute measurement of the contact force or pressure is used directly to determine whether an intensity threshold (e.g., the intensity threshold is described in units corresponding to the substitute measurement) has been exceeded. In some embodiments, the substitute measurement of the contact force or pressure is converted into an estimated force or pressure, and the estimated force or pressure is used to determine whether an intensity threshold (e.g., the intensity threshold is a pressure threshold measured in units of pressure) has been exceeded. Using the intensity of the contact as an attribute of user input allows the user to access additional device functions that the user might not otherwise access on a smaller device with a limited solid area for (e.g., on a touch-sensitive display) displaying an indication 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 "haptic output" refers to a physical displacement of the device relative to a previous position of the device, a physical displacement of a component of the device (e.g., a touch-sensitive surface) relative to another component of the device (e.g., the housing), or a displacement of a component relative to the center of mass of the device, which is detected by the user using the user's tactile sense. For example, when the device or a component of the device comes into contact with a touch-sensitive surface (e.g., a finger, palm, or other part of the user's hand), the haptic output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in the physical characteristics of the device or a component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or touchpad) may optionally be interpreted by the user as a "press-click" or "release-click" on a physically actuated button. In some cases, the user will feel a tactile sensation, such as a "press-click" or "release-click," even when a physically actuated button associated with the touch-sensitive surface, which has been physically pressed (e.g., displaced) by the user's movement, has not moved. As another example, even when the smoothness of the tactile surface remains unchanged, movement of the tactile surface can optionally be interpreted or sensed by the user as “roughness” of the tactile surface. While such interpretations of touch by the user will be limited by the user’s individualized sensory perception, there are many sensory perceptions of touch that are common to most users. Therefore, when a tactile output is described to correspond to a user’s specific sensory perception (e.g., “release click,” “press click,” “roughness”), unless otherwise stated, the generated tactile output corresponds to a physical displacement of the device or its components that will generate the sensory perception described by a typical (or common) user.

[0093] It should be understood that device 100 is merely an example of a portable multifunctional device, and device 100 may optionally have more or fewer components than shown, may optionally combine two or more components, or may optionally have different configurations or arrangements of these components. Figure 1A The various components shown are implemented in hardware, software, or a combination of both, including one or more signal processing circuits and / or application-specific integrated circuits.

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

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

[0096] RF (Radio Frequency) circuit 108 receives and transmits RF signals, also known as electromagnetic signals. RF circuit 108 converts electrical signals into electromagnetic signals / converts electromagnetic signals into electrical signals, and communicates with communication networks and other communication devices via these electromagnetic signals. RF circuit 108 optionally includes well-known circuitry for performing these functions, including but not limited to antenna systems, RF transceivers, one or more amplifiers, tuners, one or more oscillators, digital signal processors, codec chipsets, Subscriber Identity Module (SIM) cards, memory, etc. RF circuit 108 optionally communicates with networks and other devices wirelessly, such as the Internet (also known as the World Wide Web (WWW)), intranets, and / or wireless networks (such as cellular telephone networks, wireless local area networks (LANs), and / or metropolitan area networks (MANs)). RF circuit 108 optionally includes well-known circuitry for detecting near-field communication (NFC) fields, such as through near-field communication radio components. Wireless communication may optionally employ 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, Pure Data (EV-DO), HSPA, HSPA+, Dual-Unit 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), and 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 Messaging 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 with Extended Utility (SIMPLE), Instant Messaging and Presence Service (IMPS)), and / or Short Message Service (SMS), or any other suitable communication protocol that has not been developed as of the date of this document submission.

[0097] Audio circuitry 110, speaker 111, and microphone 113 provide an audio interface between the user and device 100. Audio circuitry 110 receives audio data from peripheral interface 118, converts the audio data into electrical signals, and transmits the electrical signals to speaker 111. Speaker 111 converts the electrical signals into sound waves that are audible to humans. Audio circuitry 110 also receives electrical signals converted by microphone 113 based on the sound waves. Audio circuitry 110 converts the electrical signals into audio data and transmits the audio data to peripheral interface 118 for processing. Audio data is optionally retrieved by peripheral interface 118 from and / or transmitted to memory 102 and / or RF circuitry 108. In some embodiments, audio circuitry 110 also includes a headset jack (e.g., ...). Figure 2 (212 in the text). The headset jack provides an interface between the audio circuitry 110 and a removable audio input / output peripheral device, such as an output-only headphone or a headset with both output (e.g., mono or binaural headphones) and input (e.g., a microphone).

[0098] I / O subsystem 106 couples input / output peripherals on device 100, such as touchscreen 112 and other input control devices 116, to peripheral interface 118. I / O subsystem 106 optionally includes display controller 156, optical sensor controller 158, intensity sensor controller 159, haptic feedback controller 161, and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive electrical signals from / send electrical signals to other input control devices 116. Other input control devices 116 optionally include physical buttons (e.g., push-buttons, rocker buttons, etc.), dial pads, slide switches, joysticks, click wheels, etc. In some alternative embodiments, one or more input controllers 160 are optionally coupled to (or not coupled to) any of the following: keyboard, infrared port, USB port, and pointing devices such as a mouse. One or more buttons (e.g., Figure 2 Optionally, 208 includes volume up / down buttons for volume control of speaker 111 and / or microphone 113. One or more buttons optionally include push-down buttons (e.g., Figure 2 (206 in the middle).

[0099] A quick press of the down button optionally unlocks the touchscreen 112 or optionally initiates a process of unlocking the device using gestures on the touchscreen, as described in U.S. Patent Application 11 / 322,549 (US Patent 7,657,849), filed December 23, 2005, entitled "Unlocking a Device by Performing Gestures on an Unlock Image," the entire contents of which are incorporated herein by reference. A longer press of the down button (e.g., 206) optionally powers the device 100 on or off. The function of one or more buttons can optionally be customized by the user. The touchscreen 112 is used to implement virtual buttons or soft buttons and one or more soft keyboards.

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

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

[0102] Touchscreen 112 optionally employs LCD (Liquid Crystal Display) technology, LPD (Light Emitting Polymer Display) technology, or LED (Light Emitting Diode) technology, but other display technologies are used in other embodiments. Touchscreen 112 and display controller 156 optionally employ any of a variety of touch sensing technologies currently known or to be developed hereafter, along with other proximity sensor arrays or other elements for determining one or more points of contact with touchscreen 112, to detect contact and any movement or interruption thereof. These various touch sensing technologies include, but are not limited to, capacitive, resistive, infrared, and surface acoustic wave technologies. In one exemplary embodiment, projected mutual capacitance sensing technology, such as that used in Apple Inc.'s (Cupertino, California) iPhone, is used. ®and iPod Touch ® The technology discovered in [the text].

[0103] In some embodiments of the touchscreen 112, the touch-sensitive display optionally resembles a multi-touch sensitive touchpad as 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 touchscreen 112 displays visual output from device 100, while the touch-sensitive touchpad does not provide visual output.

[0104] The touch-sensitive display in some embodiments of the touchscreen 112 is optionally described as in the following patent applications: (1) U.S. Patent Application 11 / 381,313, filed May 2, 2006, entitled “Multipoint TouchSurface 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 No. 11 / 228,758, filed September 16, 2005, entitled “Virtual Input Device Placement On A Touch Screen User Interface”; (7) U.S. Patent Application No. 11 / 228,700, filed September 16, 2005, entitled “Operation Of A Computer With A Touch Screen Interface”; (8) U.S. Patent Application No. 11 / 228,737, filed September 16, 2005, entitled “Activating Virtual Keys Of A Touch-Screen Virtual Keyboard”; and (9) U.S. Patent Application No. 11 / 367,749, filed March 3, 2006, entitled “Multi-Functional Hand-Held Device”. The full text of all these patent applications is incorporated herein by reference.

[0105] Touchscreen 112 optionally has a video resolution exceeding 100 dpi. In some embodiments, the touchscreen has a video resolution of approximately 160 dpi. Users optionally use any suitable object or accessory such as a stylus, finger, etc., to interact with touchscreen 112. In some embodiments, the user interface is designed to work primarily with finger-based contact and gestures, which may be less precise than stylus-based input due to the larger contact area of ​​a finger on the touchscreen. In some embodiments, the device translates coarse finger-based input into precise pointer / cursor positions or commands to perform the user-desired actions.

[0106] In some embodiments, in addition to the touchscreen, 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 differs from the touchscreen and does not display visual output. The touchpad is optionally a touch-sensitive surface separate from the touchscreen 112, or an extension of the touch-sensitive surface formed by the touchscreen.

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

[0108] The device 100 may optionally also include one or more optical sensors 164. Figure 1AAn optical sensor 164 is shown coupled to an 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 projected through one or more lenses from the environment and converts the light into data representing an image. In conjunction with an 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, opposite to a touchscreen display 112 on the front of the device, allowing the touchscreen display to be used as a viewfinder for still image and / or video image acquisition. In some embodiments, the optical sensor is located on the front of the device, allowing images of the user to be optionally acquired for video conferencing while the user views other video conferencing participants on the touchscreen display. In some embodiments, the position of the optical sensor 164 can be changed by the user (e.g., by rotating the lenses and sensors in the device housing), allowing a single optical sensor 164 to be used in conjunction with the touchscreen display for both video conferencing and still image and / or video image acquisition.

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

[0110] The device 100 optionally also includes one or more proximity sensors 166. Figure 1AA proximity sensor 166 is shown coupled to a peripheral device interface 118. Alternatively, the proximity sensor 166 may optionally be coupled to an input controller 160 in an I / O subsystem 106. The proximity sensor 166 may optionally perform as described in the following U.S. patent applications: U.S. Patent Application 11 / 241,839, entitled "Proximity Detector In Handheld Device"; U.S. Patent Application 11 / 240,788, entitled "Proximity Detector In Handheld Device"; U.S. Patent Application 11 / 620,702, entitled "Using Ambient Light Sensor To Augment Proximity Sensor Output"; U.S. Patent Application 11 / 586,862, entitled "Automated Response To And Sensing Of User Activity In Portable Devices"; and U.S. Patent Application 11 / 638,251, entitled "Methods And Systems For Automatic Configuration Of Peripherals", the entire contents of which are incorporated herein by reference. In some implementations, when the multifunction device is placed near the user's ear (e.g., when the user is making a phone call), the proximity sensor is turned off and the touchscreen 112 is disabled.

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

[0112] The device 100 may optionally also include one or more accelerometers 168. Figure 1A An accelerometer 168 coupled to a peripheral device interface 118 is shown. Alternatively, the accelerometer 168 may optionally be coupled to an input controller 160 in an I / O subsystem 106. The accelerometer 168 may optionally perform as described in the following U.S. patent publications: 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 on a touchscreen display in portrait or landscape view based on analysis of data received from one or more accelerometers. In addition to the accelerometer 168, the device 100 optionally includes a magnetometer (not shown) and a GPS (or GLONASS or other global navigation system) receiver (not shown) for obtaining information about the location and orientation (e.g., longitudinal or lateral) of the 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 program (or instruction set) 136. Furthermore, in some embodiments, memory 102 ( Figure 1A ) or 370 ( Figure 3 Storage device / global internal state 157, such as Figure 1A ,and Figure 3 As shown in the diagram, the device / global internal state 157 includes one or more of the following: active application state, which indicates which applications (if any) are currently active; display state, which indicates what applications, views, or other information occupy various areas of the touchscreen display 112; sensor state, which includes information acquired from the device's various sensors and input control devices 116; and position information regarding the device's position and / or orientation.

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

[0115] The communication module 128 facilitates communication with other devices via one or more external ports 124 and includes various software components for processing data received by the RF circuitry 108 and / or the external ports 124. The external ports 124 (e.g., Universal Serial Bus (USB), FireWire, etc.) are adapted to be directly coupled to other devices or indirectly coupled via a network (e.g., the Internet, Wireless LAN, etc.). In some embodiments, the external port is for use with an iPod. ® (Trademark of Apple Inc.) The same or similar and / or compatible multi-pin (e.g., 30-pin) connectors used in Apple Inc. devices.

[0116] The contact / motion module 130 optionally detects contact with the touchscreen 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 a contact has occurred (e.g., detecting a finger press event), determining the intensity of the contact (e.g., the force or pressure of the contact, or an alternative to force or pressure), determining whether there is 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 stopped (e.g., detecting a finger lift event or a contact disconnection). The contact / motion module 130 receives contact data from the touch-sensitive surface. Determining the movement of the contact point optionally includes determining the rate (magnitude), velocity (magnitude and direction), and / or acceleration (change in magnitude and / or direction) of the contact point, the movement of which is represented by a series of contact data. These operations are optionally applied to single-point contact (e.g., single-finger contact) or simultaneous multi-point contact (e.g., "multi-touch" / multiple-finger contact). In some implementations, the contact / motion module 130 and the display controller 156 detect contact on the touchpad.

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

[0118] The touch / motion module 130 optionally detects user gesture input. Different gestures on a touch-sensitive surface have different contact patterns (e.g., different movements, timings, and / or intensities of the detected contact). Therefore, gestures are optionally detected by detecting specific contact patterns. For example, detecting a finger tap gesture includes detecting a finger press event, and then detecting a finger lift-off (lift-away) event at the same (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 a touch-sensitive surface includes detecting a finger press event, then detecting one or more finger drag events, and subsequently detecting a finger lift-off (lift-away) event.

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

[0120] In some implementations, 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 from applications, etc., specifying the graphics to be displayed, and, if necessary, coordinate data and other graphic attribute data, and then generates screen image data to output to the display controller 156.

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

[0122] Optionally, the text input module 134, a component of the graphics module 132, provides a soft keyboard for entering text in various applications, such as contacts 137, email 140, IM 141, browser 147, and any other application that requires text input.

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

[0124] Application 136 optionally includes the following modules (or instruction sets) or subsets or supersets 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] • Camera module 143 for still images and / or video images;

[0132] • Image management module 144;

[0133] • Video player module;

[0134] • Music player module;

[0135] • Browser module 147;

[0136] • Calendar module 148;

[0137] • Desktop mini-program module 149, which optionally includes one or more of the following: weather desktop mini-program 149-1, stock market desktop mini-program 149-2, calculator desktop mini-program 149-3, alarm clock desktop mini-program 149-4, dictionary desktop mini-program 149-5, and other desktop mini-programs obtained by the user, and desktop mini-programs created by the user 149-6.

[0138] • Desktop Mini Program Creator Module 150 for creating user-created desktop mini programs 149-6;

[0139] • Search module 151;

[0140] • Video and music player module 152, which combines a video player module and a 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, speech recognition, and speech duplication.

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

[0146] Combining RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, telephone module 138 is optionally used to input character sequences corresponding to telephone numbers, access one or more telephone numbers in contact module 137, modify entered telephone numbers, dial corresponding telephone numbers, initiate conversations, and disconnect or hang up when a conversation is completed. As described above, wireless communication optionally uses any of a variety of communication standards, protocols, and technologies.

[0147] Combining RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touchscreen 112, display controller 156, optical sensor 164, optical sensor controller 158, contact / motion module 130, graphics module 132, text input module 134, contact module 137, and telephone module 138, video conferencing module 139 includes executable instructions to initiate, conduct, and terminate video conferences between the user and one or more other participants based on user instructions.

[0148] Incorporating RF circuitry 108, touchscreen 112, display controller 156, touch / 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 commands. Combined with image management module 144, email client module 140 makes it very easy to create and send emails containing still images or video images captured by camera module 143.

[0149] In conjunction with RF circuitry 108, touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, and text input module 134, instant messaging module 141 includes executable instructions for: inputting a character sequence corresponding to an instant message; modifying previously input characters; transmitting a corresponding instant message (e.g., using Short Message Service (SMS) or Multimedia Messaging Service (MMS) protocols for telephone-based instant messaging, or using XMPP, SIMPLE, or IMPS for internet-based instant messaging); receiving an instant message; and viewing a received instant message. In some embodiments, the transmitted and / or received instant messages optionally include graphics, photographs, audio files, video files, and / or other attachments supported in MMS and / or Enhanced Messaging Services (EMS). As used herein, "instant message" refers to both telephone-based messages (e.g., messages sent using SMS or MMS) and internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS).

[0150] Incorporating RF circuitry 108, touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, GPS module 135, map module 154, and music player module, fitness support module 142 includes executable instructions for: creating fitness activities (e.g., with time, distance, and / or calorie burning goals); communicating with fitness sensors (exercise equipment); receiving fitness sensor data; calibrating sensors used to monitor fitness; selecting and playing fitness music; and displaying, storing, and transmitting fitness data.

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

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

[0153] Combining RF circuitry 108, touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, browser module 147 includes executable instructions for browsing the Internet (including searching, linking to, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages) according to user instructions.

[0154] Combining RF circuitry 108, touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, email client module 140, and browser module 147, calendar module 148 includes executable instructions to create, display, modify, and store calendars and associated data (e.g., calendar entries, to-dos, etc.) according to user instructions.

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

[0156] Combining RF circuit 108, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, text input module 134 and browser module 147, the desktop applet creator module 150 can optionally be used by the user to create desktop applets (e.g., to transfer user-specified portions of a webpage into a desktop applet).

[0157] In conjunction with the touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, and text input module 134, the search module 151 includes executable instructions to search 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) according to user instructions.

[0158] Incorporating touchscreen 112, display controller 156, touch / 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 allowing users 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 touchscreen 112 or on an external display connected via external port 124). In some embodiments, device 100 optionally includes the functionality of an MP3 player, such as an iPod (a trademark of Apple Inc.).

[0159] Combining the touchscreen 112, display controller 156, touch / 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 items, etc., according to user instructions.

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

[0161] Incorporating touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, text input module 134, email client module 140, and browser module 147, the online video module 155 includes instructions for performing the following operations: allowing users to access, browse, receive (e.g., via streaming and / or downloading), play back (e.g., on the touchscreen 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, an instant messaging module 141 is used instead of the email client module 140 to send links to specific online videos. Further descriptions of online video applications can be found in U.S. Provisional Patent Application No. 60 / 936,562, filed June 20, 2007, entitled “Portable Multifunction Device, Method, and Graphical UserInterface for Playing Online Videos,” and U.S. Patent Application No. 11 / 968,067, filed December 31, 2007, entitled “Portable Multifunction Device, Method, and Graphical UserInterface for Playing Online Videos,” the contents of which are incorporated herein by reference in their entirety.

[0162] Each of the above modules and applications 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., computer-implemented methods and other information processing methods as described herein). These modules (e.g., instruction sets) need not be implemented as separate software programs, processes, or modules, and therefore various subsets of these modules may optionally be combined or otherwise rearranged in various embodiments. For example, a video player module may optionally be combined with a music player module into a single module (e.g., Figure 1A (e.g., video and music player module 152). In some embodiments, memory 102 optionally stores a subset of the above-described modules and data structures. Additionally, memory 102 optionally stores other modules and data structures not described above.

[0163] In some implementations, device 100 is a device on which the operation of a predefined set of functions is performed solely via a touchscreen and / or touchpad. By using a touchscreen and / or touchpad as the primary input control device for the operation of device 100, the number of physical input control devices (such as push-buttons, dial pads, etc.) on device 100 is optionally reduced.

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

[0165] Figure 1B This is a block diagram illustrating exemplary components used for event processing according to some embodiments. In some embodiments, memory 102 ( Figure 1A ) or memory 370 ( Figure 3 This includes an event classifier 170 (e.g., in 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 application view 191 of application 136-1 to which the event information should be delivered. Event classifier 170 includes event monitor 171 and event dispatcher module 174. In some embodiments, application 136-1 includes application internal state 192, which 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 should be delivered.

[0167] In some implementations, the application internal state 192 includes additional information such as one or more of the following: recovery 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 to be displayed by application 136-1, a state queue for enabling the user to return to the previous state or view of application 136-1, and a repeat / undo queue for the user's previous actions.

[0168] Event monitor 171 receives event information from peripheral device interface 118. The event information includes information about sub-events, such as user touches on touch-sensitive display 112 as part of a multi-touch gesture. Peripheral device 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 (via audio circuitry 110)). The information received by peripheral device interface 118 from I / O subsystem 106 includes information from touch-sensitive display 112 or touch-sensitive surfaces.

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

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

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

[0172] Another aspect of the user interface associated with an application is a set of views, sometimes referred to herein as application views or user interface windows, in which information is displayed and touch-based gestures occur. The application view (of the corresponding application) in which a touch is detected optionally corresponds to a procedural level within the application's procedural or view hierarchy. For example, the lowest-level view in which a touch is detected is optionally referred to as the hit view, and the set of events considered as correct input is optionally determined, at least in part, based on the hit view of the initial touch that initiates the touch-based gesture.

[0173] The hit view determination module 172 receives information related to sub-events of touch-based gestures. When an application has multiple views organized in a hierarchical structure, the hit view determination module 172 identifies the hit view as the lowest-level view in the hierarchical structure that handles the sub-events. In most cases, the hit view is the lowest-level view in which the initiating sub-event (e.g., the first sub-event in a sequence of sub-events forming an event or potential event) occurs. Once the hit view is identified by the hit view determination module 172, the hit view typically receives all sub-events related to the same touch or input source to which it is identified as the hit view.

[0174] The activity event recognizer determination module 173 determines which views(s) within the view hierarchy should receive a specific sub-event sequence. In some embodiments, the activity event recognizer determination module 173 determines that only the hit view should receive the specific sub-event sequence. In other embodiments, the activity event recognizer determination module 173 determines that all views including the physical location of the sub-event are actively participating views, and therefore determines that all actively participating views should receive the specific sub-event sequence. In other embodiments, even if the touch sub-event is entirely confined to the area associated with a particular view, higher views in the hierarchy will still remain actively participating views.

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

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

[0177] In some embodiments, application 136-1 includes a plurality of event handlers 190 and one or more application views 191, wherein each application view includes instructions for handling touch events occurring within a corresponding view of the application's user interface. Each application view 191 of application 136-1 includes one or more event recognizers 180. Typically, a corresponding application view 191 includes a plurality of event recognizers 180. In other embodiments, one or more event recognizers among the 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, a corresponding event handler 190 includes one or more of the following: a data updater 176, an object updater 177, a GUI updater 178, and / or event data 179 received from an event classifier 170. Event handlers 190 optionally utilize or invoke the data updater 176, the object updater 177, or the GUI updater 178 to update the application's internal state 192. Alternatively, one or more 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] The corresponding event recognizer 180 receives event information (e.g., event data 179) from the event classifier 170 and identifies events from the event information. The event recognizer 180 includes an event receiver 182 and an event comparator 184. In some embodiments, the event recognizer 180 also includes at least one subset of metadata 183 and event delivery instructions 188 (which optionally include sub-event delivery instructions).

[0179] Event receiver 182 receives event information from event classifier 170. The event information includes information about sub-events, such as touch or touch movement. Depending on the sub-event, the event information also includes additional information, such as the location of the sub-event. When the sub-event involves touch movement, 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 longitudinal orientation to a lateral orientation, or vice versa), and the event information includes corresponding information about the device's current orientation (also referred to as device orientation).

[0180] Event comparator 184 compares 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, event comparator 184 includes event definition 186. Event definition 186 contains definitions of events (e.g., predefined sequences of sub-events), such as event 1 (187-1), event 2 (187-2), and others. In some embodiments, sub-events in event (187) include, for example, touch start, touch end, touch move, touch cancel, and multi-touch. In one example, event 1 (187-1) is defined as a double-click on a displayed object. For example, a double-click includes a first touch (touch start) of a predetermined duration on the displayed object, a first lift of a predetermined duration (touch end), a second touch (touch start) of a predetermined duration on the displayed object, and a second lift of a predetermined duration (touch end). In another example, event 2 (187-2) is defined as a drag on a displayed object. For example, dragging includes a touch (or contact) on a displayed object for a predetermined duration, movement of the touch on the touch-sensitive display 112, and lifting off the touch (touch end). In some embodiments, the event also includes information for one or more associated event handlers 190.

[0181] In some implementations, event definition 187 includes definitions of events for corresponding user interface objects. In some implementations, event comparator 184 performs a hit test to determine which user interface object is associated with the sub-event. For example, in an application view displaying 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 the event handler associated with the sub-event and the object that triggered the hit test.

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

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

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

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

[0186] In some implementations, event delivery instruction 188 includes a sub-event delivery instruction that delivers event information about a sub-event without activating an event handler. Instead, the sub-event delivery instruction delivers 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 the actively participating view receives the event information and performs a predetermined process.

[0187] In some implementations, 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 implementations, 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 touch-sensitive display.

[0188] In some implementations, one or more event handlers 190 include, or have access to, a data updater 176, an object updater 177, and a GUI updater 178. In some implementations, the 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 implementations, they are included in two or more software modules.

[0189] It should be understood that the above discussion regarding event handling for user touch on a touch-sensitive display also applies to other forms of user input used to operate the multifunction device 100 using an input device, and not all user input is initiated on the touchscreen. Examples include mouse movement and mouse button presses optionally combined with single or multiple keyboard presses or holds; touch movements on the touchpad, such as taps, drags, scrolls, etc.; stylus input; device movement; verbal commands; detected eye movements; biometric input; and / or any combination thereof optionally used as input corresponding to a sub-event defining an event to be identified.

[0190] Figure 2A portable multifunction device 100 with a touchscreen 112 is shown according to some embodiments. The touchscreen optionally displays one or more graphics within a user interface (UI) 200. In this embodiment and other embodiments described below, a user can select one or more graphics by gesturing over the graphics, for example using one or more fingers 202 (not drawn to scale in the figures) or one or more styluses 203 (not drawn to scale in the figures). In some embodiments, selection of one or more graphics occurs when the user breaks contact with the graphics. In some embodiments, gestures optionally include one or more taps, one or more swipes (from left to right, from right to left, up and / or down), and / or scrolling (from right to left, from left to right, up and / or down) of a finger already in contact with the device 100. In some embodiments or in some cases, unintentional contact with a graphic does not select the graphic. For example, a swipe gesture over an application icon optionally does not select the corresponding application when the gesture corresponding to selection is a tap.

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

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

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

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

[0195] Now let’s turn our attention to the implementation of the user interface, which is optionally implemented on, for example, a portable multifunction device 100.

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

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

[0198] • Time 404;

[0199] • Bluetooth indicator 405;

[0200] • Battery status indicator 406;

[0201] • Tray 408 with icons for frequently used applications, such as:

[0202] ○ The telephone module 138 has an icon 416 labeled "telephone", which optionally includes an indicator 414 indicating the number of missed calls or voicemails;

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

[0204] ○ The icon 420 labeled "Browser" in browser module 147; and

[0205] ○ The icon 422 labeled "iPod" for the video and music player module 152 (also known as the iPod (a trademark of Apple Inc.) module 152); and

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

[0207] ○ Icon 424 of IM module 141 marked as "Message";

[0208] ○ Calendar module 148, icon 426 marked "Calendar";

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

[0210] ○ The icon 430 of the camera module 143, which is labeled "camera";

[0211] ○ Icon 432 of the online video module 155, labeled "Online Video";

[0212] ○ The icon labeled "Stock Market" in the Stock Market Desktop Mini Program 149-2 (434);

[0213] ○ Map module 154, marked with the "map" icon 436;

[0214] ○ The "Weather" icon (438) in the Weather desktop mini-program 149-1;

[0215] ○ The "clock" icon in the alarm clock desktop mini-program 149-4 (440);

[0216] ○ Icon 442 of the Fitness Support module 142, labeled "Fitness Support";

[0217] ○ Icon 444 of Notepad module 153, labeled "Notepad"; and

[0218] ○ An icon 446 labeled "Settings" is used to set the settings of an application or module, which provides access to the settings of the device 100 and its various applications 136.

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

[0220] Figure 4B A touch-sensitive surface 451 (e.g., separate from the display 450 (e.g., touchscreen display 112)) is shown. Figure 3 Devices such as tablets or touchpads (e.g., 355) Figure 3An exemplary user interface on the device 300. The device 300 also optionally includes one or more contact intensity sensors (e.g., one or more of the sensors 359) for detecting the intensity of contact on the tactile surface 451, and / or one or more tactile output generators 357 for generating tactile outputs for the user of the device 300.

[0221] While some examples of input on a reference touchscreen display 112 (which combines a touch-sensitive surface and a display) are given below, in some implementations the device detects input on a touch-sensitive surface separate from the display, such as... Figure 4B As shown in the diagram. In some embodiments, the touch-sensitive surface (e.g., Figure 4B 451) has a spindle (e.g., on the display (e.g., 450) with the spindle on the display (e.g., 451). Figure 4B The main axis corresponding to 453 in the middle (e.g., Figure 4B (452 in the example). According to these embodiments, the device detects the position corresponding to the corresponding position on the display (e.g., in the example). Figure 4B In the middle, 460 corresponds to 468 and 462 corresponds to 470) the contact with the touch-sensitive surface 451 (e.g., Figure 4B (460 and 462 in the text). Thus, on touch-sensitive surfaces (e.g., Figure 4B 451 in the middle) and the display of the multi-functional device ( Figure 4B When 450 is separated from the touch-sensitive surface, user input detected by the device on the touch-sensitive surface (e.g., touches on 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 may be optionally used for other user interfaces described herein.

[0222] Additionally, while the examples below are primarily given with reference to finger input (e.g., finger touch, single-finger tap, finger swipe), it should be understood that in some implementations, one or more of these finger inputs may be replaced by input from another input device (e.g., mouse-based input or stylus input). For example, a swipe gesture may optionally be replaced by a mouse click (e.g., instead of a touch), followed by movement of the cursor along the swipe path (e.g., instead of movement of the touch). Similarly, a tap gesture may optionally be replaced by a mouse click while the cursor is over the location of the tap gesture (e.g., instead of detection of the touch and subsequent cessation of touch detection). Likewise, when multiple user inputs are detected simultaneously, it should be understood that multiple computer mice may optionally be used simultaneously, or mouse and finger touch may optionally be used simultaneously.

[0223] Figure 5AAn exemplary personal electronic device 500 is illustrated. Device 500 includes a body 502. In some embodiments, device 500 may include components relative to devices 100 and 300 (e.g., Figures 1A-4B The device 500 may include some or all of the features described herein. In some embodiments, the device 500 has a touch-sensitive display 504, referred to below as a touchscreen 504. As an alternative to or complement to the touchscreen 504, the device 500 has a display and a touch-sensitive surface. Similar to the cases of devices 100 and 300, in some embodiments, the touchscreen 504 (or touch-sensitive surface) optionally includes one or more intensity sensors for detecting the intensity of an applied contact (e.g., a touch). The one or more intensity sensors of the touchscreen 504 (or touch-sensitive surface) can provide output data representing the intensity of the touch. The user interface of the device 500 can respond to touches based on the touch intensity, meaning that touches of different intensities can invoke different user interface operations on the 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, filed May 8, 2013, entitled “Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application,” published as WIPO Patent Publication No. WO / 2013 / 169849; and International Patent Application No. PCT / US2013 / 069483, filed November 11, 2013, entitled “Device, Method, and Graphical User Interface for Transitioning Between Touch Input to Display Output Relationships,” published as WIPO Patent Publication No. WO / 2014 / 105276, each of which is incorporated herein by reference in its entirety.

[0225] In some embodiments, device 500 has one or more input mechanisms 506 and 508. Input mechanisms 506 and 508 (if included) may be physical. Examples of physical input mechanisms include push-buttons and rotatable mechanisms. In some embodiments, device 500 has one or more attachment mechanisms. Such attachment mechanisms (if included) allow device 500 to be attached to, for example, hats, glasses, earrings, necklaces, shirts, jackets, bracelets, watch straps, bangles, trousers, belts, shoes, wallets, backpacks, etc. These attachment mechanisms allow device 500 to be worn by a user.

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

[0227] In some examples, the input mechanism 508 is optionally a microphone. The 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 the I / O section 514.

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

[0229] As used herein, the term "power indication" refers optionally to the power indication in devices 100, 300, and / or 500 ( Figures 1A to 1B , Figure 3 and Figures 5A to 5H A user-interactive graphical user interface object displayed on a screen. For example, images (e.g., icons), buttons, and text (e.g., hyperlinks) optionally each constitute a functional representation.

[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 specific implementations that include a cursor or other positional 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), the cursor is positioned on a touch-sensitive surface (e.g., a...). Figure 3 The touchpad 355 or Figure 4B When an input (e.g., a press input) is detected on the touch-sensitive surface 451 of the display, the specific user interface element is adjusted according to the detected input. This applies to touchscreen displays (e.g., those capable of direct interaction with user interface elements on a touchscreen display) that enable direct interaction with user interface elements on the touchscreen display. Figure 1A The touch-sensitive display system 112 or Figure 4A In some embodiments of the touchscreen 112, the detected touch on the touchscreen acts as a "focus selector," such that when input (e.g., a press input by touch) is detected at the location of a particular user interface element (e.g., a button, window, slider, or other user interface element) on the touchscreen display, that particular user interface element is adjusted according to the detected input. In some embodiments, focus moves from one area of ​​the user interface to another without corresponding movement of the cursor or movement of a touch on the touchscreen display (e.g., moving focus from one button to another using tab keys or arrow keys); in these embodiments, the focus selector moves according to focus movement between different areas of the user interface. Regardless of the specific form the focus selector takes, the focus selector is typically a user-controlled user interface element (or a touch on the touchscreen display) that delivers the user-expected interaction with the user interface (e.g., by indicating to the device the element of the user interface that the user expects to interact with). For example, when a press input is detected on a touch-sensitive surface (e.g., a touchpad or touchscreen), the position of the focus selector (e.g., a cursor, touch, or selection box) above the corresponding button will indicate to the user that they expect 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 over 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 lift is detected, before or after contact begins to move is detected, before contact ends is detected, before or after an increase in contact intensity is detected and / or before or after a decrease in contact intensity is detected). The characteristic intensity of the 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 when determining the characteristic intensity (e.g., when the characteristic intensity is the average value of the contact intensity over time). In some implementations, the feature intensity is compared to a set of one or more intensity thresholds to determine whether the user has performed an action. For example, the set of one or more intensity thresholds may optionally include a first intensity threshold and a second intensity threshold. In this example, contact with a feature intensity not exceeding the first threshold results in a first action, contact with a feature intensity exceeding the first intensity threshold but not exceeding the second intensity threshold results in a second action, and contact with a feature intensity exceeding the second threshold results in a third action. In some implementations, the comparison between the feature intensity and one or more thresholds is used to determine whether to perform one or more actions (e.g., whether to perform the corresponding action or abandon its execution), rather than to determine whether to perform the first or second action.

[0232] Figure 5C This demonstrates the use of multiple intensity sensors 524A-524D to detect multiple contacts 552A-552E on a touch-sensitive display 504. Figure 5C It also includes an intensity graph, which 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 embodiments, the cumulative intensity is the sum of the intensity measurements of the multiple intensity sensors 524A-524D, which is 32 intensity units in this example. In some implementations, each contact is assigned a corresponding intensity, i.e., a portion of the cumulative intensity. Figure 5DThe diagram illustrates the allocation of cumulative intensity to contacts 552A-552E based on their distance from the center of force 554. In this example, each of contacts 552A, 552B, and 552E is assigned a contact intensity of 8 intensity units of the cumulative intensity, and each of contacts 552C and 552D is assigned a contact intensity of 4 intensity units of the cumulative intensity. More generally, in some specific implementations, each contact j is assigned a corresponding intensity Ij according to a predefined mathematical function Ij = A·(Dj / ΣDi), which is a portion of the cumulative intensity A, 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. Reference can be performed using electronic devices similar to or equivalent to devices 100, 300, or 500. Figures 5C-5D The operation described above. In some embodiments, the characteristic intensity of the contact is based on one or more contact intensities. In some embodiments, an intensity sensor is used to determine the intensity of a single characteristic (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 within... Figures 5C-5D This is to help readers.

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

[0234] Optionally, the intensity of a contact on a touch-sensitive surface is 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 performs an operation typically associated with clicking a button on a physical mouse or touchpad. In some embodiments, the deep press intensity threshold corresponds to an intensity at which the device performs an operation different from the operation typically associated with clicking a button on a physical mouse or touchpad. In some embodiments, when a contact with a characteristic intensity lower than the light press intensity threshold (e.g., and higher than the nominal contact detection intensity threshold, where contacts lower than the nominal contact detection intensity threshold are no longer detected) is detected, the device will move the focus selector based on the movement of the contact on the touch-sensitive surface without performing the operation associated with the light press intensity threshold or the deep press intensity threshold. Generally, unless otherwise stated, these intensity thresholds are consistent across different groups of user interface figures.

[0235] The intensity of a contact increasing from below a light press intensity threshold to between a light press intensity threshold and a deep press intensity threshold is sometimes referred to as a "light press" input. The intensity of a contact increasing from below a deep press intensity threshold to above a deep press intensity threshold is sometimes referred to as a "deep press" input. The intensity of a contact increasing from below a contact detection intensity threshold to between a contact detection intensity threshold and a light press intensity threshold is sometimes referred to as detecting a contact on the touch surface. The intensity of a contact decreasing from above a contact detection intensity threshold to below a contact detection intensity threshold is sometimes referred to as detecting a contact being lifted off 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 including a corresponding press input or in response to detecting a corresponding press input performed using a corresponding contact (or multiple contacts), wherein the corresponding press input is detected at least in part based on detecting that the intensity of the contact (or multiple contacts) increases to above a press input intensity threshold. In some embodiments, the corresponding operation is performed in response to detecting that the intensity of the corresponding contact increases to above a press input intensity threshold (e.g., a "downward stroke" of the corresponding press input). In some embodiments, the press input includes the intensity of the corresponding contact increasing to above a press input intensity threshold and the intensity of the contact subsequently decreasing to below the press input intensity threshold, and the corresponding operation is performed in response to detecting that the intensity of the corresponding contact subsequently decreases to below the press input threshold (e.g., an "upward stroke" of the corresponding press input).

[0237] Figures 5E-5HThe detection of gestures is shown, including gestures involving contact 562 with an intensity ranging from less than... Figure 5E The light press intensity threshold (e.g., "IT") L The intensity of ) increases to higher than Figure 5H The deep press intensity threshold (e.g., "IT") D The intensity of the press input corresponds to the strength of the press. On the user interface 570, which includes application icons 572A-572D displayed in the predefined area 574, a cursor 576 is displayed above the application icon 572B corresponding to application 2, while the 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 contact 562 is within a deep press intensity threshold (e.g., "IT"). D The intensity reaches its peak at 562. Contact 562 is maintained on the touch-sensitive surface 560. In response to a detected gesture, and based on the intensity increasing to a deep press intensity threshold during the gesture (e.g., "IT"), the intensity is increased to a peak value. D The above contact 562 displays a scaled-down representation 578A-578C (e.g., a thumbnail) of the document recently opened for application 2, such as... Figures 5F-5H As shown. 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... Figures 5E-5H This is to help readers.

[0238] In some implementations, the display of icons 578A-578C includes animation. For example, icon 578A might initially appear near application icon 572B, such as... Figure 5F As shown, as the animation progresses, icon 578A moves upwards, and icon 578B appears near application icon 572B, as shown. Figure 5G As shown in the diagram. Then, representation 578A moves upwards, 578B moves upwards towards representation 578A, and representation 578C is displayed near application icon 572B, as shown. Figure 5H As shown in the diagram. This indicates that 578A-578C form an array above icon 572B. In some implementations, the animation progresses according to the intensity of contact 562, such as... Figures 5F-5G As shown, where 578A-578C appear and increase with the intensity of contact 562 towards the deeper pressing strength threshold (e.g., "IT"). D The animation progresses upwards as it increases in intensity. In some implementations, the intensity upon which the animation progresses is based is the characteristic intensity of the contact. Reference can be performed using electronic devices similar to or equivalent to devices 100, 300, or 500. Figures 5E-5H The aforementioned operation.

[0239] In some implementations, the device employs intensity hysteresis to avoid unintended inputs sometimes referred to as "jitter," wherein the device defines or selects a hysteresis intensity threshold that has a predefined relationship with 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 percentage of the press input intensity threshold). Therefore, in some implementations, a press input includes an increase in the intensity of the corresponding contact above the press input intensity threshold and a subsequent decrease in the intensity of that contact below the hysteresis intensity threshold corresponding to the press input intensity threshold, and an operation is performed in response to detecting that the intensity of the corresponding contact subsequently decreases below the hysteresis intensity threshold (e.g., an "upstroke" of the corresponding press input). Similarly, in some implementations, a press input is detected only when the device detects that the intensity of the contact increases from an intensity equal to or below the hysteresis intensity threshold to an intensity equal to or above the press input intensity threshold and optionally the intensity of the contact subsequently decreases to an intensity equal to or below the hysteresis intensity threshold, and an operation is performed in response to detecting a press input (e.g., depending on the environment, an increase or decrease in the intensity of the contact).

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

[0241] Figure 6 Exemplary devices are illustrated, connected via one or more communication channels to participate in transactions according to some embodiments. One or more exemplary electronic devices (e.g., devices 100, 300, and 500) are configured to optionally detect input (e.g., specific user input, NFC field) and optionally transmit payment information (e.g., using NFC). The one or more electronic devices optionally include NFC hardware and are configured to support NFC.

[0242] Electronic devices (e.g., devices 100, 300, and 500) are optionally configured to store payment account information associated with each of one or more payment accounts. Payment account information includes one or more of the following: a person's or company's name, a billing address, a login name, a password, an account number, an expiration date, a security code, a telephone number, a bank associated with the payment account (e.g., an issuing bank), and a card network identifier. In some examples, payment account information includes images, such as photographs of payment cards (e.g., photographs taken by and / or received by the device). In some examples, the electronic device receives user input that includes at least some payment account information (e.g., receiving a credit card number, debit card number, account number, or shopping card number, and an expiration date entered by the user). In some examples, the electronic device detects at least some payment account information from an image of the payment card (e.g., captured by the device's camera sensor). In some examples, the electronic device receives at least some payment account information from another device (e.g., another user device or server). In some examples, electronic devices receive payment account information from a server associated with another service (e.g., an application for renting or selling audio and / or video files), where the user or the user device's account has previously made purchases for that other service or has identified payment account data.

[0243] In some implementations, a payment account is added to an electronic device (e.g., devices 100, 300, and 500), such that the payment account information is securely stored on the electronic device. In some examples, after 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 (e.g., a payment server) operated by the account's payment network to ensure the validity of the information. The electronic device is optionally configured to receive scripts from a server that allows the electronic device to program the account's payment information onto a secure element.

[0244] In some implementations, communication between devices 100, 300, and 500 facilitates transactions (e.g., general or specific transactions). For example, a first electronic device (e.g., 100) may be used as a configuration or management device and may send new or updated payment account data (e.g., information about new accounts, updated information about existing accounts, and / or warnings about existing accounts) to a second electronic device (e.g., 500). Alternatively, the first electronic device (e.g., 100) may send data to the second electronic device reflecting information about a payment transaction facilitated at the first electronic device. This information may optionally include one or more of the following: payment amount, account used, purchase time, and whether the default account has been changed. The second device (e.g., 500) may optionally use 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 via any of a variety of networks. For example, devices may communicate using Bluetooth connectivity 608 (e.g., including traditional Bluetooth connectivity or Bluetooth Low Energy connectivity) or using a WiFi network 606. Communication between user devices may optionally be tailored to reduce the likelihood of inappropriate sharing of information between devices. For example, communication regarding payment information may require the communicating devices to be paired (e.g., associated with each other via explicit user interaction) or associated with the same user account.

[0246] In some implementations, electronic devices (e.g., 100, 300, 500) communicate with a point-of-sale (POS) payment terminal 600, which optionally supports NFC. This communication may optionally utilize various communication channels and / or technologies. In some examples, the electronic devices (e.g., 100, 300, 500) use NFC channel 610 to communicate with the payment terminal 600. In some implementations, the payment terminal 600 uses a peer-to-peer NFC mode to communicate with the electronic devices (e.g., 100, 300, 500). The electronic devices (e.g., 100, 300, 500) are optionally configured to transmit signals to the payment terminal 600, including payment information for a payment account (e.g., a default account or an account selected for a specific transaction).

[0247] In some implementations, continuing the transaction involves sending a signal including payment information from an account (such as a payment account). In some implementations, continuing the transaction involves reconfiguring an electronic device (e.g., 100, 300, 500) to respond as a contactless payment card (e.g., an NFC-enabled contactless payment card), and then transmitting the account credentials via NFC to, for example, a payment terminal 600. In some implementations, after transmitting the account credentials via NFC, the electronic device is reconfigured not to respond as a contactless payment card (e.g., authorization is required before it can be reconfigured to respond as a contactless payment card via NFC).

[0248] In some implementations, the generation and / or transmission of the signal is controlled by a secure element in an electronic device (e.g., 100, 300, 500). Prior to releasing the payment information, the secure element optionally requests specific user input. For example, the secure element optionally requests: detection of a worn electronic device, detection of a button press, detection of a password input, detection of a touch, detection of one or more option selections (e.g., option selections received during interaction with an application), detection of a fingerprint signature, detection of a voice or voice command, and / or detection of a gesture or movement (e.g., rotation or acceleration). In some examples, if a communication channel (e.g., an NFC communication channel) with another device (e.g., payment terminal 600) is established within a defined time period from the detection of input, the secure element releases the payment information for transmission to the other device (e.g., payment terminal 600). In some examples, the secure element is a hardware component controlling the release of secure information. In some examples, the secure element is a software component controlling the release of secure information.

[0249] In some implementations, the protocols associated with transaction participation depend on, for example, the device type. For instance, the conditions for generating and / or transmitting payment information may differ for wearable devices (e.g., device 500) and telephones (e.g., device 100). For example, the generation and / or transmission conditions for wearable devices may include detecting that a button has been pressed (e.g., after security verification), while the corresponding conditions for telephones do not require a button press but rather require detecting a specific interaction with the application. In some implementations, 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 may optionally require the detection of a fingerprint and / or password on one device (e.g., device 100) and the detection of mechanical input (e.g., button press) on another device (e.g., device 500).

[0250] Payment terminal 600 optionally uses payment information to generate a signal to be transmitted to payment server 604, thereby determining whether the payment is authorized. 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 suggested purchase. In some examples, payment server 604 includes a server of an issuing bank. Payment terminal 600 communicates directly with payment server 604 or indirectly via one or more devices or systems (e.g., the acquiring bank's server and / or the card network's server).

[0251] Payment server 604 optionally uses at least some of the payment information from the payment information to identify user accounts from a database of user accounts (e.g., 602). For example, each user account includes payment information. Accounts are optionally located by locating accounts that have specific payment information that matches the information from the POS communication. In some examples, payment is refused when the provided payment information is inconsistent (e.g., the due date does not match 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 implementations, user account data further identifies one or more restrictions (e.g., credit limit); current or previous 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 this data to determine whether to authorize a payment. For example, the payment server may refuse payment if adding a purchase amount to the current balance would result in exceeding the account limit, if the account is frozen, if previous transaction amounts exceed a threshold, or if the number or frequency of previous unusual transactions exceeds a threshold.

[0253] In some implementations, payment server 604 responds to POS payment terminal 600 with indications regarding whether the suggested purchase is authorized or rejected. In some examples, POS payment terminal 600 signals to electronic devices (e.g., 100, 300, 500) to identify the result. For example, when a purchase (e.g., via a transaction coordination server managing transactions on a user's device) is authorized, POS payment terminal 600 sends a receipt to electronic devices (e.g., 100, 300, 500). In some cases, POS payment terminal 600 presents an output indicating the result (e.g., visual or audio output). Payment may be transmitted to the merchant as part of the authorization process or may be transmitted later.

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

[0255] In some implementations, the electronic device (e.g., 100, 300, 500) is in a locked or unlocked state. In the locked state, the electronic device is powered on and operable, but it is prevented from performing a predefined set of operations in response to user input. This 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 certain functions of the electronic device, or to activate or deactivate certain functions on the electronic device. In the unlocked state, the electronic device 100 is powered on and operable, and is not prevented from performing at least a portion of the predefined set of operations that cannot be performed when in the locked state.

[0256] When a device is in a locked state, it is said to be locked. In some implementations, a locked device can respond to user input from a restricted group, including input corresponding to an attempt to switch the device to an unlocked state or input corresponding to turning off the device.

[0257] In some examples, the 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 publishes) payment information (e.g., account and / or transaction-specific dynamic security codes). In some examples, the secure element provides (or publishes) payment information in response to the device receiving authorization, such authorization being user authentication (e.g., fingerprint authentication; password authentication; detection of a double-click on a hardware button when the device is unlocked, and optionally, when the device has been continuously on the user's wrist due to unlocking by providing authentication credentials to the device, wherein the continuous presence of the device on the user's wrist is determined by periodically checking the 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 the determination that the fingerprint matches a registered fingerprint, the secure element provides (or publishes) payment information. Based on the determination that the fingerprint does not match a registered fingerprint, the secure element abandons providing (or publishing) payment information.

[0258] Now let’s turn our attention to the implementation of user interfaces (“UIs”) on electronic devices, such as portable multifunction devices 100, 300 or 500, and the associated processes.

[0259] Figures 7A to 7P Exemplary user interfaces for configuring cards onto electronic devices (e.g., 100) having one or more input devices and one or more near-range communication radio components (e.g., NFC radio components) according to some embodiments are shown. The user interfaces in these figures are used to illustrate including... Figures 8A to 8B The process described below is the process in the middle.

[0260] In some implementations, a user has access to a stored-value card and wants to transfer stored value from the card to a virtual card stored on an electronic device. Before the value transfer, the electronic device uses an authentication process to help verify that the user is the rightful 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 card, such as the account number or the current value stored on it. The electronic device also receives information about the stored-value card separately (e.g., via a displayed keyboard without using NFC from the user). The electronic device verifies ownership based on both pieces of information. If ownership is verified, the electronic device transfers the stored value from the card (e.g., using NFC) to the virtual card on the electronic device. In some examples, this technology helps provide security for the rightful owner of the stored-value card and prevents users of the electronic device from transferring funds from someone else's stored-value card.

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

[0262] In some implementations, electronic device 100 displays a power indicator (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. Figures 15A to 15M As stated above.

[0263] In some implementations, electronic device 100 displays a selection indicator (e.g., 704) that provides a user with the option to disable Fastpass. For example, by disabling Fastpass, no accounts available on electronic device 100 will be designated as Fastpasses. In some implementations, electronic device 100 receives user input indicating that the user does not wish for an account to be available without authentication (e.g., by receiving user input selecting the "Do not use account" option for the case of use without authentication; by moving the selection indicator to the "Off" position as shown in selection indicator 704), such as references Figures 15A to 15M In response to receiving user input indicating that they do not wish for an account to be available without authentication, electronic device 100 designates a specific account of the virtual card (or all accounts of the electronic device) as unavailable without authentication. Therefore, electronic device 100 provides the user with the option to disable (or enable) a fastpass mode (e.g., using Select Power indicator 704), through which funds can be transferred in a specific transaction without authentication. In some embodiments, when the fastpass feature is enabled (e.g., by moving Select Power indicator 704 to the "On" position), electronic device 100 provides faster access to the account designated as the fastpass account. In some embodiments, when the fastpass feature is disabled (e.g., by moving Select Power indicator 704 to the "Off" position), electronic device 100 provides additional security for the accounts offered on the electronic device.

[0264] In some implementations, electronic device 100 displays a power indication (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 power indication (e.g., 702C) for configuring an account on electronic device 100. In response to detecting activation of the power indication (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., stored-value accounts, and accounts that are not stored-value accounts), such as... Figure 7BAs shown. Therefore, in some embodiments, electronic device 100 displays a power indication (e.g., 706A) for configuring a non-stored-value account and a power indication (e.g., 706B) for configuring a stored-value account. In some embodiments, the 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, 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 implementations, in response to detecting such Figure 7B The activation of the power indicator (e.g., 706B) for configuring a stored-value account is shown. The electronic device 100 displays a prompt (e.g., 708A, 708B) on its display instructing the user to place the electronic device 100 within the communication range of the card with stored value (e.g., within the range of one or more short-range communication radio components), as shown. Figure 7C As shown. For example, a prompt (e.g., 708A, 708B) instructs the user to place the electronic device 100 on the stored-value card such that the back of the electronic device (e.g., the side of the electronic device opposite the display) is as close to the stored-value card as possible. Alternatively or otherwise, the electronic device 100 may provide 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 from the card (e.g., 710) via one or more near-field communication radio components (e.g., NFC radio components), wherein the card has stored values ​​(e.g., Figure 7KThe 728D shown 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 access card, or a stored-value gift card. In some examples, the electronic device 100 uses NFC to receive the card's account number from the card (e.g., 710). In some embodiments, the electronic device 100 presents an indication (e.g., 712) when communicating with the card that the electronic device is receiving the card's account number (e.g., 710). In some embodiments, the card account number includes a mixture of alphanumeric characters. In some examples, the card account number includes numeric characters but not alphanumeric characters.

[0267] Electronic device 100 requests verification information (e.g., from a user) to verify ownership of the card (e.g., 710), such as the card number, the cardholder's account number, or the date of birth of the user who registered the card. For example, electronic device 100 requests the user to enter the card number (e.g., 710). In some implementations, electronic device 100 requests verification information after receiving the cardholder's account number (e.g., 710).

[0268] In some implementation schemes, such as Figures 7E to 7F As shown, electronic device 100 displays an instruction (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, electronic device 100 uses the verification information (e.g., 714C) to confirm that the user actually possesses (or controls) the card (e.g., 710). Figure 7E As shown, electronic device 100 displays a request (e.g., 714A) instructing the user to use a virtual keyboard (e.g., 716) to enter the card account number into a field (e.g., 714B). Figure 7F As shown, electronic device 100 receives input from a user of the device (e.g., not via one or more short-range communication radio components) via one or more input devices, including verification information (e.g., 714C) for verifying ownership of the card (e.g., 710).

[0269] In some implementations, the verification information (e.g., 714C) is information not displayed on the card (e.g., 710). For example, verification information (e.g., 714C) requested by electronic device 100 and entered by the user is not displayed on the card (e.g., 710). In some implementations, the requested (and received) verification information is not displayed on the card, depending on whether the card (e.g., 710) is registered. Therefore, in some examples, verification cannot be performed simply by possessing the card (e.g., 710); the user must possess some additional information corresponding to the card. In some implementations, 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 electronic device 100.

[0270] In some implementation schemes, such as Figures 7G to 7H As shown, electronic device 100 displays an instruction requesting the user to provide verification information (such as the cardholder's date of birth) (e.g., 720A). In some examples, 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, electronic device 100 displays a request (e.g., 720A) instructing the user to use a virtual keyboard (e.g., 716) to enter their date of birth (e.g., 720C) into a field (e.g., 720B). Figure 7H As shown, electronic device 100 receives input from a user of the electronic device (e.g., not via one or more short-range communication radio components) via one or more input devices, including verification information (e.g., 720C) for verifying ownership of the card (e.g., 710). In some embodiments, Figures 7G to 7H The user interface is Figures 7E to 7F An alternative form of user interface. In some implementations, Figures 7G to 7H User interface and Figures 7E to 7F The user interface is used in conjunction with it.

[0271] In some implementations, the verification information (e.g., 720C) is information not displayed on the card (e.g., 710). For example, 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 implementations, the requested (and received) verification information is information not shown on the card, depending on whether the card (e.g., 710) is registered. Therefore, in some examples, verification cannot be performed simply by possessing the card (e.g., 710), and the user must possess some additional information corresponding to the card. In some implementations, the verification information (e.g., 720C) is (or includes) the 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, electronic device 100 verifies ownership of a card (e.g., 710) based on a comparison of verification information (e.g., 714C, 720C) with independent information related to the cardholder's card (e.g., the card's account number, the cardholder's registered date of birth). This independent information related to the card (e.g., 710) is received independently of the verification information (e.g., 714C, 720C). For example, this independent information may be received from a server, service, 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 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 electronic device 100. In some embodiments, the electronic device 100 displays an indication (e.g., 724A) that verification information has been received (e.g., 714C, 720C). In some embodiments, the electronic device 100 displays an indication that ownership verification is being performed (e.g., 724B).

[0273] In some implementations, electronic device 100 sends the card account 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 implementations, this is done before requesting verification information from the user (e.g., 714C, 720C). In some implementations, this is done before receiving input from the user to verify ownership of the card (e.g., 710). In some implementations, 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). Therefore, in some implementations, electronic device 100 operates in "registration mode" (e.g., based on a response received from the server, service, or database indicating that the card is registered), while in some implementations, electronic device 100 operates in "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 the server, service, or database has already registered the card with a specific user or entity. In other examples, a card is registered when the server, service, or database associates the card with a specific user or entity.

[0274] In some embodiments, upon determining that a card (e.g., 710) is registered (e.g., a "registration mode"), electronic device 100 requests (e.g., to a user) verification information to verify ownership of the card (e.g., 710). This process includes requesting information not shown on the card (e.g., the date of birth of the user registered to the card). In some embodiments, electronic device 100 waives the request for 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 implementations, based on the determination that a card (e.g., 710) is registered (e.g., a "registration mode"), electronic device 100 sends (e.g., to a server, service, or database) the card account of the card and receives (e.g., from a server, service, or database) independent information. In some examples, the independent information includes personal information of the user who registered the card (e.g., 710), rather than the card account 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 who registered the card (e.g., 710), a higher level of security is achieved for the registered card. In some implementations, after receiving the card account 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 electronic device 100 via one or more short-range communication radio components, the electronic device waives the receipt of the user-configured card account (e.g., 710) as part of verifying card ownership. Therefore, by using independent information for verification, electronic devices help prevent users' cards from being digitally stolen simply by having an NFC reader scan the user's pocket or wallet containing the card (e.g., 710).

[0276] In some implementations, upon determining that a card (e.g., 710) is not registered (e.g., "anonymous mode"), electronic device 100 (e.g., to the user) requests verification information (e.g., 714C, 720C, the card number, the card account number) to verify ownership of the card, including the information displayed on the card. In some examples, electronic device 100 waives the request for information not shown on the card (e.g., 710). Therefore, in some examples, electronic device 100 can request different information based on whether the card (e.g., 710) is registered or not, and achieve a higher level of security for the registered card user by requesting information specific to the individual registering the card.

[0277] In some implementations, based on the determination that the card (e.g., 710) is not registered (e.g., "anonymous mode"), and before verifying ownership of the card, electronic device 100 requests a card account provided by the user as part of verification information requesting verification of ownership of the card. In some examples, electronic device 100 receives the user-provided card (e.g., 710) account as input from the user of the electronic device (e.g., using a touchscreen keyboard input), rather than receiving the account from one or more short-range communication radio components. The user-provided card (e.g., 710) account includes verification information used to verify ownership of the card. In some examples, electronic device 100 compares the user-provided account with the card account 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 account of the received card. In some examples, based on the determination that the card is registered (e.g., "registered mode"), electronic device 100 does not request (or receive) the user-provided card (e.g., 710) account as part of user input received from verification information used to verify ownership of the card.

[0278] In some implementations, depending on whether the card is registered (e.g., "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 the user of the electronic device receives input including verification information for verifying ownership of the card via one or more input devices. Therefore, in some examples, the user must access the card number (or the account number associated with card 710) through a method outside of 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 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 (e.g., through text input via a displayed virtual keyboard). In some implementations, depending on whether the card (e.g., 710) is registered (e.g., "registered mode"), the electronic device 100 presents (e.g., by displaying on the display of the electronic device) the card's account information before receiving input from the user via one or more input devices, including verification information for verifying ownership of the card.

[0279] In some implementation schemes, such as Figure 7JAs shown, based on the determination that ownership verification has failed, electronic device 100 displays and / or generates feedback to the user (e.g., visual feedback displayed on a display, audio and / or haptic output generated by the device), 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 independent information, the verification information is determined to have failed. In some embodiments, based on the determination that ownership verification has failed, electronic device 100 abandons providing prompts regarding (e.g., the user) performing a value transfer operation for value transfer (e.g., abandons generating feedback, such as visual feedback displayed on a display, audio and / or haptic output generated by the device), and abandons transferring any stored value from a card (e.g., 710) to a virtual card stored on the electronic device. In some embodiments, such as Figure 7J As shown, upon determining that ownership verification has failed, electronic device 100 again (e.g., from the user) requests (e.g., 726B) verification information (e.g., card number, card account, date of birth of the user who registered the card) to verify ownership of the card (e.g., 710). Therefore, electronic device 100 notifies the user that ownership verification has failed.

[0280] In some implementation schemes, such as Figure 7K As shown, upon successful ownership verification, 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, 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, electronic device 100 presents an indication of the username associated with the card (e.g., 710) (e.g., 728C). In some examples, electronic device 100 presents an indication of the current balance of the card (e.g., 710) (e.g., 728D). In some examples, electronic device 100 presents an indication of access plan (or pass) information associated with the card (e.g., 710) (e.g., 728E).

[0281] In some embodiments, electronic device 100 displays a power indicator or input area (e.g., 728F) that includes an indication of the amount of stored value to be transferred from the card (e.g., 710) 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 to be transferred from the card (e.g., 710) to the virtual card stored on the electronic device. In some embodiments, the power indicator (e.g., 728F), when activated, causes the electronic device to display a user interface for the user to select the amount to be transferred from the stored value card (e.g., 710) to the virtual card stored on the electronic device 100. For example, the user may select to transfer the entire stored value of the card (e.g., 710) from the card to the virtual card on the electronic device 100, such as... Figure 7L As shown.

[0282] In some implementation schemes, such as Figure 7L As shown, electronic device 100 displays a power indicator (e.g., 728G) that can be activated by a user to initiate a value transfer process. When activated, the power indicator (e.g., 728G) initiates a process of transferring value from a card (e.g., 710) to a virtual card on electronic device 100. In some embodiments, the power indicator (e.g., 728G) cannot be activated before a value to be transferred is selected (e.g., using power indicator 728F). In some embodiments, when the electronic device has received a transfer value (e.g., using input area 728F), activating the power indicator (e.g., 728G) initiates a process of transferring the entire available balance on the card (e.g., 710). In some embodiments, the power indicator (e.g., 728G) initiates a 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, ownership verification is successful (and in some implementations, such as...). Figure 7L As shown, in response to receiving a user's selection to initiate a value transfer (e.g., 728G), electronic device 100 displays and / or generates feedback (e.g., visual feedback displayed on a monitor, audio and / or haptic 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 electronic device 100 to maintain prolonged contact with a card (e.g., 710), or requests that the electronic device be placed near a card (e.g., 710). In some examples, if the verification information (714C, 720C) received from the user matches independent information (e.g., a match), electronic device 100 determines that ownership verification was successful. Figure 7NAs shown, in conjunction with a value transfer operation (and / or after providing a prompt (or generating feedback) to perform the value transfer operation), electronic device 100 transfers at least some (or all) of the stored values ​​from a card (e.g., 710) 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 electronic device 100. In some embodiments, during the transfer, electronic device 100 displays and / or generates (e.g., to a user) feedback indicating (e.g., indication 732A) that at least some (or all) of the stored values ​​from the card (e.g., 710) are being transferred to the virtual card on the electronic device (e.g., visual feedback displayed on a display, audio and / or haptic output generated by the device), and indications to keep the electronic device in contact with or near the card for an extended period of time while the transfer process is in progress (e.g., 708B, 732B) (e.g., to a user).

[0284] In some implementations, the virtual card is stored on electronic device 100 (e.g., in the 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 implementations, electronic device 100 includes a template virtual card (e.g., a “blank” virtual card) stored on the electronic device that does not contain any value or funds. In some examples, electronic device 100 transfers at least some (or all) of the stored value from the card (e.g., 710) to the template virtual card. Therefore, in some examples, it is not necessary to configure a new virtual card for 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 electronic device 100 because a new virtual card does not need to be created during the configuration process or transfer operation.

[0285] In some implementations, after at least some (or all) of the stored values ​​are successfully transferred from a card (e.g., 710) to a virtual card stored on 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 implementations, transferring at least some (or all) of the stored values ​​from a card (e.g., 710) to a virtual card stored on electronic device 100 includes removing the stored values ​​from the card and transmitting a request (e.g., via a network or internet connection) to a server, service, or database associated with the card to deactivate the card (e.g., deregister the card, rendering it inoperable). For example, all stored values ​​from the card (e.g., 710) are removed and the card becomes inoperable. Therefore, in some implementations, all features and / or values ​​of the physical card (e.g., 710) are moved to a virtual card stored on electronic device 100, thereby replacing the physical card.

[0286] In some implementation schemes, such as Figure 7P As shown, after at least some (or all) of the stored value has been successfully transferred from a card (e.g., 710) to a virtual card stored on 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 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 virtual card (e.g., 736A) and the graphical depiction (e.g., 736B) enable a user to distinguish the virtual card from a different card provided on electronic device 100, and in some examples, the indication of the type of virtual card and the graphical depiction are displayed simultaneously.

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

[0288] In some implementations, after at least some (or all) of the stored values ​​in storage have been successfully transferred from a card (e.g., 710) to a virtual card stored on electronic device 100, the electronic device displays the stored values ​​of the virtual card (e.g., 736D). In some examples, if the electronic wallet application of electronic device 100 includes multiple virtual cards (or accounts) of the same type (e.g., multiple access 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 identify multiple virtual cards stored on (or accessible by) the electronic device and their corresponding stored values.

[0289] In some implementation schemes, such as Figure 7O As shown, based on the determination that the value transfer has failed, electronic device 100 displays and / or generates (e.g., instructs the user) feedback indicating the value transfer failure (e.g., visual, audio, and / or tactile output generated by the device) (e.g., indication 734A). In some embodiments, electronic device 100 displays and / or generates feedback (e.g., visual, audio, and / or tactile output generated by the device) via a second prompt (e.g., 734B, different from the first prompt 730) to repeatedly perform (e.g., performed by the user) 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.

[0290] In some implementations, after at least some (or all) of the stored values ​​are transferred from a card (e.g., 710) to a virtual card stored on electronic device 100, and based on the determination that the electronic device does not have an additional connected access account (e.g., a newly configured access account is the initial (first) access account and / or the only currently valid access account connected to the electronic device), the electronic device designates (either by default or by prompting the user to designate) the account of the virtual card to be available without checking authentication. In some examples, if the virtual card corresponds to a uniquely configured access account of electronic device 100, electronic device 100 designates the virtual card as a fast pass card based on determining that the virtual card is the unique access account of the electronic device's account information application, such as reference Figures 15A to 15M As described above. In some implementations, such as those referenced... Figures 15A to 15M The use of fast pass cards (e.g., for payment or credential transfer) does not require authentication checks in certain situations (e.g., when detected wireless signals correspond to transactions such as requests from transaction terminals or fund requests from pass accounts). Therefore, designating a virtual card as a fast pass card reduces the amount of user input required, making the technology more efficient and saving battery power. Pass transactions also frequently occur in congested 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 negative misidentification where a valid user fails to authenticate correctly (e.g., because the user's fingerprint is not correctly identified 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 the pass transaction terminal (e.g., through transaction terminal signals or other background information) rather than user authorization for a specific transaction reduces the likelihood of inconvenience for users (or other passengers) due to negative misidentification during pass transactions with the device.

[0291] In some implementations, after transferring at least some (or all) of the stored values ​​from a card (e.g., 710) to a virtual card stored on electronic device 100, and based on determining that the electronic device has one or more other connected access accounts, electronic device 100 abandons (or abandons prompting the user to specify) the availability of the virtual card's account without authentication verification. In some implementations, if the virtual card does not correspond to a uniquely configured access account, electronic device 100 designates (or prompts the user to specify) the virtual card's account as unusable without authentication verification. Therefore, in some examples, electronic device 100 does not designate the virtual card as a fast pass card based on determining that the virtual card is not the only access account for the account information application.

[0292] In some implementations, after transferring at least some (or all) of the stored values ​​from a card (e.g., 710) to a virtual card stored on electronic device 100, and based on determining that the electronic device has another connected access account, and further based on receiving user input indicating that the account should not be available without authentication verification (e.g., removing a previous fast pass card from the account information application or rejecting user input to add a previous account as a fast pass card), the electronic device abandons (or abandons prompting the user to specify) the account of the virtual card to be available without authentication verification. In some examples, electronic device 100 designates (or prompts the user to specify) the account of the virtual card to be unusable without authentication verification. Therefore, in some examples, electronic device 100 does not designate the virtual card as a fast pass card based on determining that the virtual card is not the only access account for the account information application, thereby adapting to the user's preference to designate or abandon designating the virtual card as a fast pass card.

[0293] Figures 8A to 8B This is a flowchart illustrating a method for configuring a card onto 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, it enables users to manage transactions faster and more efficiently, saving power and increasing the time interval between battery charges.

[0295] At box 802, the electronic device receives (e.g., via NFC from a card) the card account 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 near-field 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 is received from the card using NFC.

[0296] According to some implementations, at box 804, the card is a stored-value card (e.g., funds and / or data are physically stored on the card in binary-encoded data form). 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 box 806, the electronic device (e.g., from a user) 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 (e.g., 710). In some examples, the electronic device displays an instruction requesting the user to provide verification information (e.g., 714A, 720A). In some examples, the electronic device uses the verification information (e.g., 714C, 720C) to confirm that the user actually possesses (or controls) the card (e.g., 710). By receiving and using verification information to confirm user possession of the card, the electronic device's ability to detect and prevent electronic theft or fraud is enhanced.

[0298] According to some implementations, the verification information (e.g., 714C, 720C) is information not displayed on the card (e.g., 710). For example, verification information entered by the user (e.g., 714C, 720C) will not be displayed on the card (e.g., 710). In some examples, based on the determination that the card is registered (e.g., "registered mode"), the requested (and received) verification information is information not shown 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 value. In such examples, a user with access to the card and knowing its current stored value can transfer at least some (or all) of the stored value from the card (e.g., 710) to a virtual card stored on the electronic device 100.

[0299] According to some implementations, at box 808, based on the determination that the card is registered (e.g., using a server, service, or database) (e.g., "registered mode"), at box 810, (e.g., from the user) a request for 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 requests for information not shown on the card. In some examples, the electronic device waives the request for information shown on the card. By determining whether the card is registered, the electronic device can request specific verification information based on this determination, thereby enhancing the operability of the device by including additional security measures for registering the card.

[0300] According to some implementations, at box 812, based on the determination that the card (e.g., 710) is not registered (e.g., "anonymous mode"), at box 814, verification information (e.g., from the user) is requested to verify ownership of the card (e.g., 714C, 720C, card number, card account number), including requests for information not shown on the card (e.g., 710). In some examples, the electronic device waives the request for information not shown on the card. Therefore, 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 the 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 this determination, thereby enhancing the operability of the device by not displaying requests for information about unregistered cards that the user does not possess, thus reducing the amount of user input required.

[0301] In some implementations (based on determining the card is unregistered (e.g., "anonymous mode")), the electronic device does not present (e.g., on the display of the electronic device) the card's account number until the user of the electronic device receives input from one or more input devices, including verification information (e.g., 714C, 720C) for verifying ownership of the card (e.g., 710). In some examples, the electronic device does not present the card's account number until ownership of the card is verified. 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 printed on the receipt or invoice for the card, or based on the card number printed on the card. In some examples, based on determining the card is registered (e.g., "registered mode"), the electronic device presents (e.g., displays on the display of the electronic device) the card's account number until the user of the electronic device receives input from one or more input devices, including verification information for verifying ownership of the card. By determining whether the card is registered, the electronic device can request specific verification information based on this determination, thereby enhancing the operability of the device and providing additional security for registered cards by avoiding unnecessary requests for unregistered 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 implementations, based on the determination 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 as part of verification information (e.g., 714C, 720C) requested to verify ownership of the card, receives the user-provided card (e.g., 710) account as part of input received from the user of the electronic device (e.g., not via one or more short-range communication radio components) including verification information (e.g., 714C, 720C) for verifying ownership of the card, and compares the user-provided account with the card account 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. In some examples, based on the determination that the card is registered (e.g., "registered mode"), requesting verification information to verify ownership of the card does not include requesting (or receiving) the user-provided card account (e.g., as part of input received from the user of the device including verification information for verifying ownership of the card).

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

[0304] According to some implementation schemes, (e.g., before requesting verification information, before receiving input from the device's user to verify card ownership) based on determining that the card is registered (e.g., "registered mode"), the electronic device transmits (e.g., to a server) the card account information of the card (e.g., 710), and (e.g., from the server) receives separate information. In some examples, the separate information includes the personal information of the card's registered user (e.g., the user's birthday, the user's mailing address, the user's mother's maiden name, rather than the card account number). Therefore, a higher level of security for registered cards can be achieved by requesting the personal information of the card's registered user.

[0305] According to some implementations, the electronic device relinquishes the right to receive (e.g., after receiving the card account via one or more short-range communication radio components and before transferring at least some (or all) of the stored values ​​from the card to a virtual card stored on the device via one or more short-range communication radio components) the card account provided by the user (e.g., as part of verifying ownership of the card).

[0306] According to some implementations, a virtual card is stored on the electronic device (e.g., in an account information application) before the card account number of the receiving card (e.g., 710) and before verifying card ownership. In some examples, the electronic device includes a "blank" virtual card without any value or funds. The electronic device transfers at least some (or all) of the stored value from that card to the blank virtual card. Therefore, it is not necessary to configure a new virtual card for the electronic device, as 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 it. In some examples, this enhances the operability of the device by accelerating 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) that is received separately from the verification information (e.g., 714C, 720C) (e.g., independent information received from the server or from the card).

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

[0309] At box 820, upon successful ownership verification, and at box 824, in conjunction with a value transfer operation (or after generating a prompt to perform the value transfer operation), electronic device 100 transfers at least some (or all) of the stored values ​​from a card (e.g., 710) to a virtual card (e.g., stored in the device's account information application) stored on the electronic device (e.g., via one or more near-field communication radio components, such as one or more NFC radio components). In some examples, the electronic device includes a secure element, and transferring at least some of the stored values ​​from the card to the virtual card stored on the electronic device includes storing information for accessing the stored values ​​of the virtual card in the secure element of the electronic device. Thus, by transferring values ​​to the 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 with funds based on unauthorized cards. 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 implementations, upon determining that a 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, different from the first prompt 730) to perform a value transfer operation (e.g., prolonged contact or proximity to the card) for the value transfer. In some examples, the electronic device presents an indication of value transfer failure to the user. In some examples, the electronic device presents another prompt to the user to perform a value transfer operation (e.g., prolonged contact or proximity to the card). Thus, the user is warned of value transfer failure. In some examples, the second 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 that the electronic device has determined that the value transfer has failed by generating the second prompt, thereby prompting the user to perform the value transfer operation again.

[0311] According to some implementations, at box 826, based on the determination that ownership verification failed (e.g., if the verification information received from the user is inconsistent with independent information), at box 828, the electronic device 100 displays and / or generates an indication (e.g., indication 726A) of ownership verification failure feedback (e.g., visual, audio, and / or haptic output generated by the device). In some examples, based on the determination that ownership verification failed, the electronic device abandons generating (e.g., visual, audio, and / or haptic output generated by the device) prompts (e.g., by the user) to perform a value transfer operation for value transfer, and abandons transferring any stored value from the card to a virtual card stored on the device. In some examples, based on the determination that ownership verification failed, the electronic device again (e.g., from the user) 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. Thus, the user becomes aware of the ownership verification failure. Thus, 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 implementations, after at least some (or all) of the stored value is transferred from a card (e.g., 710) to a virtual card stored on the electronic device, the electronic device displays the stored value of the virtual card on a display (e.g., 728D). For example, when the electronic device's e-wallet application includes multiple virtual cards (or accounts) of the same type, the values ​​of the virtual cards are highlighted to help the user identify 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 identify multiple virtual cards stored on (or accessible to) the electronic device and their corresponding stored values.

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

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

[0315] According to some implementations, transferring at least some (or all) of the stored values ​​from a card to a virtual card stored on an electronic device includes removing the stored values ​​from the card and transmitting a request to a server to deactivate the card (e.g., deregister the card, rendering it inoperable). For example, the electronic device removes all values ​​from the card and renders it inoperable. Thus, 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 if a payment transaction retrieving the information from the secure element is not properly processed.

[0316] According to some implementations, (e.g., after transferring at least some (or all) of the stored values ​​from the card to the stored virtual card) based on the determination that the electronic device does not have another connected access account (e.g., the newly configured access account is the initially (first) configured access account and / or the only currently valid access account connected to the electronic device), the electronic device designates (either by default or by prompting the user to designate) the virtual card's account for use without authentication checks. In some examples, using the virtual card's account to participate in transactions includes releasing information (e.g., transaction information, payment information) from the electronic device's secure element. Therefore, the electronic device designates (based on the determination that the virtual card is the only access account for the account information application) the virtual card as a fast pass card, and the electronic device can use the fast pass card after authentication checks for transactions corresponding to a first type of request (e.g., a request from a transaction terminal, a funds request from the access account). According to some implementations, based on the determination that the electronic device has one or more other connected access accounts, the electronic device abandons designating (or abandons prompting the user to designate) the virtual card's account for use without authentication checks (and / or designates the virtual card's account for unusable without authentication checks). Therefore, electronic devices do not designate the virtual card as a fast pass card (based on the premise that the virtual card is not the only access account for the account information application). Pass transactions frequently occur in congested checkpoints 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 negative misidentification where a valid user fails to authenticate correctly (e.g., because the user's fingerprint is not correctly identified or the user enters an incorrect password, passcode, or pattern). Using a fast pass model that provides security by establishing the identity of the transaction terminal as the pass transaction terminal (e.g., through transaction terminal signals or other background information) rather than user authorization specific to a particular transaction reduces the likelihood of inconvenience for users (or other passengers) due to negative misidentification during pass transactions with the device.

[0317] According to some implementations, (e.g., after transferring at least some (or all) of the stored values ​​from the card to the stored virtual card) based on the determination that the electronic device does not have another connected access account (e.g., the newly configured access account is the initially (first) configured access account and / or the only currently valid access account connected to the electronic device), and based on receiving user input indicating that the account should not be available without authentication (e.g., removing a previous fast pass card from the account information application or rejecting user input to add a previous account as a fast pass card), the electronic device abandons specifying (or prompts the user to specify) that the virtual card's account is available without authentication (and / or specifies that the virtual card's account is not available without authentication). Therefore, the electronic device does not specify (based on the determination that the virtual card is not the only access account for the account information application) the virtual card as a fast pass card. In some examples, based on not receiving user input indicating that the account should not be available without authentication, or based on receiving user input indicating that the account should be available without authentication, the electronic device selects the virtual card's account that is available without authentication. Therefore, the electronic device designates the virtual card as a fast pass card, allowing it to use the fast pass card without undergoing authentication checks on transactions corresponding to the first type of request (e.g., a request from a transaction terminal, a fund request from a pass account). Thus, the electronic device adapts to the user's preference by designating the virtual card as a fast pass card.

[0318] According to some implementations, electronic devices receive user input indicating that they do not want an account to be available without authentication verification (e.g., by receiving user input selecting the "Do not use account" option to make an account available without authentication verification, as per [reference to...]). Figure 15D The device, in response to receiving user input indicating that it does not wish the account to be available without authentication, specifies that the account for that virtual card (or all virtual cards) is unusable without authentication. Therefore, the electronic device provides the user with the option to disable a quickpass mode, which 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 implementations, an electronic device receives user input selecting an account that can be used without authentication verification (e.g., an account corresponding to a virtual card among multiple accounts in an account information application), and in response to receiving user input selecting an account that can be used without authentication verification, specifies that the selected account (e.g., an account in an account information application) is available without authentication verification, such as by reference. Figures 15A to 15MTherefore, electronic devices enable users to select a preferred account for use as a fastpass account. In some examples, fastpass accounts do not require authentication checks in certain situations, thereby reducing the amount of user input required, making the technology more efficient and saving battery power.

[0320] It should be noted that the process described above is relative to method 800 (e.g., Figures 8A to 8B The details of the above 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 The user interface. For example, an account configured using the techniques of methods 800 and 1000 can be used to perform the techniques described in reference methods 1200, 1400, 1600, 1800, and 2000. For example, the techniques of method 1200 can be used to deposit funds into stored-value accounts as described in methods 800, 1000, 1400, 1600, 1800, and 2000. For example, as discussed with respect to methods 1800 and 2000, the account to which funds are deposited can be moved to or from different devices. For the sake of brevity, these details will not be repeated below.

[0321] Figures 9A to 9N Exemplary user interfaces for configuring a card onto an electronic device (e.g., 100) having a display, one or more near-range communication radio components (e.g., one or more NFC radio components), and one or more input devices are illustrated according to some embodiments. The user interfaces in these figures are used to illustrate including... Figure 10 The process described below is the process in the middle.

[0322] In some implementations, a user has access to a stored-value card and wishes to transfer stored value from the card to a virtual card stored on an electronic device. Before the value transfer, the electronic device uses a verification process to help confirm that the user is the rightful 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 receives identification information from the stored-value card separately (e.g., via NFC), such as the card's account number or the current value stored on the 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 card (e.g., using NFC) to the virtual card on the electronic device. In some examples, this technology helps provide security for the rightful owner of the stored-value card and prevents users of the electronic device from transferring funds from someone else's stored-value card.

[0323] Figure 9A User interfaces for electronic device 100 are provided according to some embodiments. In some examples, electronic device 100 displays a power indicator (e.g., 902A) that includes an indication of a previously configured account (e.g., a payment account). In this example, the power indicator (e.g., 902A) corresponds to an American Express account. In some examples, electronic device 100 also displays a power indicator (e.g., 902B) that includes an indication of another previously configured account (e.g., a separate payment account). In this example, the power indicator (e.g., 902B) corresponds to a Mastercard account different from the American Express account. When electronic device 100 detects activation of a power indicator (e.g., 902A) including an indication of a previously configured account or an power indicator (e.g., 902B) including an indication of another previously configured account by, for example, detecting touch input on a touch-sensitive surface of the electronic device at a location corresponding to the respective power indicator, the electronic device displays information corresponding to the respective account (e.g., balance, previous transaction details).

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

[0325] In some implementations, electronic device 100 displays a selection enablement (e.g., 904) that provides a user with the option to disable Fastpass. For example, by disabling Fastpass, none of the accounts configured on electronic device 100 will be designated as Fastpasses. In some implementations, electronic device 100 receives user input indicating that it does not want an account to be available without authentication (e.g., by receiving user input selecting the "Do not use account" option to be available without authentication, by moving the selection enablement to the "Off" position as shown in selection enablement 904), such as references Figures 15A to 15MIn response to receiving user input indicating that an account should not be available without authentication verification, electronic device 100 designates a specific account (or all accounts of electronic device 100) of the virtual card as unavailable without authentication verification. Therefore, electronic device 100 provides the user with the option to disable (or enable) a fastpass mode (e.g., using selectable power indicator 904), through which funds can be transferred in specific transactions without authentication. In some embodiments, when the fastpass feature is enabled (e.g., by moving selectable power indicator 904 to the "on" position), electronic device 100 provides faster and more convenient access to the account designated as the fastpass account. In some embodiments, when the fastpass feature is disabled (e.g., by moving selectable power indicator 904 to the "off" position), electronic device 100 provides additional security for the accounts configured on the electronic device.

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

[0327] In some implementation schemes, such as Figure 9A As shown, the electronic device detects the activation of a power indicator (e.g., 902C) used to configure an account on the electronic device 100. In response to detecting the activation of the power indicator (e.g., 902C) used to configure an account on the electronic device 100, the electronic device displays a user interface for selecting from two types of accounts (e.g., a prepaid account and an account that is not a prepaid account), as shown. Figure 9BAs shown. Therefore, in some embodiments, electronic device 100 (e.g., simultaneously) displays a power indication (e.g., 906A) for configuring a non-stored-value account and a power indication (e.g., 906B) for configuring a stored-value account. In some embodiments, the 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 implementation schemes, such as Figure 9B As shown, electronic device 100 detects the activation of an enablement display (e.g., 906B) used to configure a stored-value account. Figures 9C to 9F A user interface for prompting and receiving verification information is shown according to some embodiments (e.g., a user interface displayed in response to the detection of activation of the enable display 906B). Figures 9C to 9F As shown, electronic device 100 requests (e.g., by displaying a prompt on the electronic device's display) verification information (e.g., 914A to 914B, 920A to 920B) to verify ownership of the stored-value card, and receives input from the 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, funds and / or data associated with the stored-value card are physically stored on the card in binary-encoded data form. 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 access 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 to 914B, 920A to 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) the 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. Therefore, 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. Therefore, 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 of electronic device 100 (e.g., touch-sensitive surface, microphone), which is different from one or more short-range communication radio components.

[0331] In some implementations, the electronic device 100 does not present (e.g., on the display of the electronic device) the account number of the stored-value card until it receives input from the user of the device via one or more input devices, including verification information (e.g., 914C, 920C) to verify ownership of the card. Therefore, in some examples, the user must access the card (or account) number through a method outside of 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 itself (e.g., 910). In some examples, depending on whether the card is determined to be 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 from the user of the device via one or more input devices, including verification information to verify ownership of the card.

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

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

[0334] like Figure 9IAs shown, after receiving the identification information, electronic device 100 verifies ownership of a 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, electronic device 100 (e.g., to the user) presents an indication (e.g., 924A) that identification information has been received from the stored-value card (e.g., 910). In some embodiments, electronic device 100 (e.g., to the user) presents an indication that the electronic device is verifying ownership of the stored-value card (e.g., 910) (e.g., 924B). In some embodiments, after receiving the identification information, 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 the 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 regarding whether the ownership verification was successful (e.g., the values ​​match or correspond). Therefore, ownership determination / verification can be performed at the electronic device or at a remote device.

[0335] In some implementation schemes, such as Figure 9J As shown, upon determining that ownership verification has failed, electronic device 100 displays and / or generates an indication (e.g., indication 920D) as feedback of ownership verification failure (e.g., visual, audio, and / or tactile output generated by the device). Therefore, in some examples, 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 match) the identification information, ownership verification is determined to have failed. In some examples, upon determining that ownership verification has failed, electronic device 100 requests verification information again (e.g., from the user) (e.g., the card number of the stored-value card, date of birth, mailing address) to verify ownership of the stored-value card (e.g., 910). For example, electronic device 100 displays a prompt on the display of the electronic device instructing the user to re-enter the verification information (e.g., 920A, 920B).

[0336] In some implementation schemes, such as Figure 9KAs shown, upon successful ownership verification, electronic device 100 (e.g., on the display of the electronic device) presents an indication of successful verification completion (e.g., 928A, 928B). For example, ownership verification is successful if the verification information corresponds to (or matches) identification information. 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, electronic device 100 uses the identification information (e.g., from a remote server) to retrieve a non-account identifier (e.g., birthday) corresponding to the account number. If the retrieved non-account identifier matches the verification information, the verification information is considered to correspond to the identification information, and verification is successful.

[0337] In some implementations, upon successful ownership verification, electronic device 100 presents (e.g., displays) one or more indications (e.g., 928C to 928E) of one or more information items associated with the verified card (e.g., 910). In some examples, electronic device 100 presents (e.g., displays) an indication of the username (e.g., 928C) associated with the card (e.g., 910). In some examples, 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, electronic device 100 presents (e.g., displays) an indication of access plan (or pass) information (e.g., 928E) associated with the card (e.g., 910).

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

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

[0340] like Figure 9L As shown, electronic device 100 transfers at least some (or all) of the stored value from a 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 e-wallet) of electronic device 100. In some embodiments, during the transfer, electronic device 100 displays and / or generates (e.g., to a 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 (e.g., to a user) an indication (e.g., 908B, 932B) to maintain prolonged contact or proximity between electronic device 100 and the stored value card (e.g., 910) while the transfer process is in progress (e.g., visual, audio, and / or tactile output generated by the device).

[0341] In some implementations, after at least some (or all) of the stored value is successfully transferred from a stored-value card (e.g., 910) to a virtual card stored on 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 implementations, transferring at least some (or all) of the stored value from the stored-value card (e.g., 910) to the virtual card stored on electronic device 100 includes removing the stored value from the stored-value card (e.g., 910) and transmitting a request (e.g., via a network or internet connection) to a server, service, or database associated with the card (e.g., 910) to deactivate the stored-value card (e.g., 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. Therefore, in some implementations, all features and / or values ​​of the physical card (e.g., 910) are moved to a virtual card stored on the electronic device 100, thereby replacing the physical card (e.g., 910).

[0342] In some implementations, a virtual card is stored on electronic device 100 (e.g., in the account information application of electronic device 100) (e.g., as a template virtual card) before the card account number of the stored-value card (e.g., 910) is received and before ownership of the card is verified (and / or before an instruction to verify ownership of the card is received). In some implementations, electronic device 100 includes template virtual cards that already exist on the electronic device and do not contain any value or funds (e.g., “blank” virtual cards). In some examples, 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, it is not necessary to configure a new virtual card for electronic device 100 because the characteristics and / or values ​​of the card (e.g., 910) can be moved to the template virtual card. The use of template virtual cards speeds up the process of transferring funds from the stored-value card (e.g., 910) to electronic device 100 because a new virtual card does not need to be created during the configuration process or transfer operation.

[0343] In some implementation schemes, such as Figure 9MAs shown, based on the determination that the value transfer has failed, electronic device 100 displays and / or generates (e.g., to the user) feedback indicating (e.g., indication 934A) the value transfer failure (e.g., visual, audio, and / or haptic output generated by the device). In some embodiments, 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 repeatedly perform the value transfer operation for the value transfer. In some examples, the second prompt includes visual, audio, and / or haptic feedback prompting the user to interact with the electronic device.

[0344] In some implementation schemes, such as Figure 9N As shown, after at least some (or all) of the stored value has been successfully transferred from a card (e.g., 910) to a virtual card stored on 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 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 virtual card (e.g., 936A) and the graphical depiction (e.g., 936B) enable a user to distinguish the virtual card from a different card provided on electronic device 100.

[0345] In some embodiments, the representation of a virtual card corresponding to a stored-value card provided on electronic device 100 includes a menu (e.g., 940) that includes multiple selectable power indicators (e.g., 940A, 940B, 940C). In some examples, the menu (e.g., 940) includes an information power indicator (e.g., 940A). In some examples, the menu (e.g., 940) includes a transaction power indicator (e.g., 940B). In some examples, the menu (e.g., 940) includes a device power indicator (e.g., 940C). In some embodiments, (e.g., in response to a user's selection of an information power indicator (e.g., 940A), such as...) Figure 9N As shown, the virtual card representation displays one or more information items (e.g., 936C to 936E) about the virtual card corresponding to the configured card (e.g., 910), either individually or simultaneously. In some examples, the electronic device 100 displays the username of the account registered to the virtual card (e.g., 936C). In some examples, the electronic device 100 displays the funds balance on the virtual card (e.g., 936D). In some examples, the electronic device 100 displays the pass information of the virtual card (e.g., 936E) (e.g., monthly pass, 10-ride pass, etc.). One example of the electronic device 100 generating detailed information about 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 detailed information about the virtual card on a display.

[0346] In some implementations, after at least some (or all) of the stored value has been successfully transferred from a stored-value card (e.g., 910) to a virtual card stored on 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 electronic device 100 includes multiple virtual cards (or accounts) of the same type (e.g., multiple access 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 identify multiple virtual cards stored on (or accessible by) the electronic device and their corresponding stored values.

[0347] In some implementations, after at least some (or all) of the stored value is transferred from a stored-value card (e.g., 910) to a virtual card stored on electronic device 100, and based on the determination that the electronic device does not have other connected access accounts (e.g., the newly configured access account is the initially (first) configured access account and / or the only currently valid access account connected to the electronic device), the electronic device designates (either by default or by prompting the user to designate) the account of the virtual card to be available without checking authentication. For example, if the virtual card corresponds to the initially (first) configured access account, then the virtual card corresponds to the uniquely configured access account, and is thus the only currently valid access account. In some examples, if the virtual card corresponds to the uniquely configured access account, electronic device 100 designates the virtual card as a fast pass card based on the determination that the virtual card is the only access account for the electronic device's account information application. In some implementations, such as references Figures 15A to 15M The use of a fast pass card (e.g., for payment or credential transfer) does not require authentication checks in certain situations (e.g., when a detected wireless signal corresponds to a transaction, such as a request from a transaction terminal or a fund request from a pass account). Therefore, designating a virtual card as a fast pass card reduces the amount of user input required, making the technology more efficient and saving battery power.

[0348] In some implementations, after transferring at least some (or all) of the stored value from a stored-value card (e.g., 910) to a virtual card stored on electronic device 100, and based on the determination that the virtual card does not correspond to a unique access account configured on the electronic device's account information application (e.g., e-wallet), the electronic device abandons (or abandons prompting the user to specify) the availability of the virtual card's account without verification. For example, if the virtual card does not correspond to an initially (first) configured access account, then the virtual card does not correspond to a uniquely configured access account and is therefore not the only currently valid access account. In some examples, if the virtual card does not correspond to a uniquely configured access account, the electronic device 100 designates (or prompts the user to specify) the virtual card's account as unusable without verification. Therefore, in some examples, the electronic device 100 does not designate the virtual card as a fast pass card based on the determination that the virtual card is not the unique access account of the account information application.

[0349] In some implementations, after transferring at least some (or all) of the stored value from a stored-value card (e.g., 910) to a virtual card stored on electronic device 100, based on the determination that the electronic device does not have another connected access account (e.g., the newly configured access account is the initially (first) configured access account and / or the only currently valid access account connected to the electronic device), and further based on receiving user input indicating that the account should not be available without authentication verification (e.g., removing a previous fast pass card from the account information application or rejecting user input to add a previous account as a fast pass card), the electronic device abandons (or abandons prompting the user to specify) the account of the virtual card to be available without authentication verification. In some examples, electronic device 100 designates (or prompts the user to specify) the account of the virtual card to be unusable without authentication verification. Therefore, in some examples, electronic device 100 does not designate the virtual card as a fast pass card based on the determination that the virtual card is not the only access account for the account information application. Therefore, in some implementations, electronic device 100 adapts to the user's preference to designate or abandon designating the virtual card as a fast pass card. Passenger transactions frequently occur in congested checkpoints with users (or other passengers) eager to establish a connection. Even with the most accurate and reliable authentication systems, there is a possibility of false positives where a valid user fails to authenticate correctly (e.g., because the user's fingerprint was not correctly identified or the user entered an incorrect password, passcode, or pattern). Using a fast-access transaction model that provides security by establishing the transaction terminal's identity as a pass transaction terminal (e.g., through transaction terminal signals or other background information) rather than user authorization specific to a particular transaction reduces the likelihood of inconvenience for users (or other passengers) due to false positives when conducting pass transactions with devices.

[0350] Figure 10 This is a flowchart 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 may optionally be combined, some operations may optionally be changed in order, and some operations may optionally be 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, it enables users to manage transactions faster and more efficiently, saving power and increasing the time interval between battery charges.

[0352] At box 1002, the electronic device requests (e.g., by displaying a prompt on the electronic device's display) verification information (e.g., 914A to 914B, 920A to 920B) (e.g., the card number, date of birth, and 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 form on the card, NFC-readable stored-value card, stored-value access card, or 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. Therefore, 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 implementations, a stored-value card (e.g., 910) is a stored-value toll card. In some examples, the stored-value toll card stores toll plan (or toll ticket) information. In some examples, the toll plan is a monthly or weekly toll plan. In some examples, the stored-value toll card stores electronic cash. Therefore, in some examples, the electronic device provides the user with the ability to configure an account that can be used to grant the user access to the toll system.

[0354] According to some implementations, the virtual card is a toll virtual card. In some examples, the toll virtual card stores toll plan (or toll ticket) information. In some examples, the toll plan is a monthly or weekly toll plan. In some examples, the toll virtual card stores electronic cash. According to some implementations, 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 provides the user with the ability to use the virtual card to provide the user with access to the toll system.

[0355] In some implementations, the verification information is the card account number of a prepaid card (e.g., 910). In some examples, the verification information is (or includes) the stored value of the prepaid card. Therefore, 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 implementations, the verification information (e.g., 920C) is the personal information of the registered user of the stored-value card. In some examples, the verification information is a non-account identifier (e.g., birthday). In some examples, the verification information is the registered user's birthday. In some examples, the verification information is the registered user's mailing address. Therefore, in some examples, the electronic device provides additional security by requesting the personal information used 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 box 1004, the electronic device receives input from the user of the electronic device via one or more input devices (e.g., rather than via one or more short-range communication radio components), including verification information (e.g., 914C, 920C) for verifying ownership of a card (e.g., 910), wherein the verification information includes information not shown on the card. In some examples, the verification information is received via a first input device of the electronic device (e.g., a touch-sensitive surface, a microphone), which is different from one or more short-range communication radio components.

[0358] According to some implementations, the electronic device does not present (e.g., on the display of the electronic device) the card number of a stored-value card (e.g., 910) until it receives input from a user of the electronic device via one or more input devices, including verification information (e.g., 914C, 920C) to verify ownership of the card. 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 printed on a receipt or invoice on the card. In some examples, depending on whether the card is registered (e.g., "registered mode"), the electronic device presents (e.g., on the display of the electronic device) the card's account number before receiving input from a user of the device via one or more input devices, including verification information to verify ownership of the card.

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

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

[0361] At box 1010, the electronic device verifies ownership of a stored-value card (e.g., 910) by comparing verification information (e.g., 914C, 920C) with identification information. Therefore, by verifying 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 implementations, the virtual card is stored on the electronic device (e.g., in an account information application) before the card account number of the card (e.g., 910) is received and before ownership of the card is verified. 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 that card to the “blank” virtual card. Therefore, it is not necessary to configure a new virtual card for the electronic device, as funds can be provided to an existing virtual card. In some examples, this speeds up the process of transferring funds to the electronic device.

[0362] At box 1012, based on successful ownership verification (e.g., verification information corresponds to (or matches) identification information), at box 1014, the electronic device transfers at least some (or all) of the stored value from a 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 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 retrieving the information from the secure element is not properly processed. Therefore, by transferring the value to the virtual card stored on the electronic device, the electronic device's operability 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., birthday), and the identification information is an account number. Electronic devices use identification information (e.g., from a remote server) to retrieve a non-account identifier (e.g., birthday) corresponding to an account. If the retrieved non-account identifier matches verification information, the verification information is considered to correspond to the identification information and verification is successful.

[0363] According to some implementations, transferring at least some (or all) of the stored values ​​from a stored-value card (e.g., 910) to a virtual card stored on an electronic device includes removing the stored values ​​from the stored-value card (e.g., 910) and transmitting a request to a server to deactivate the stored-value card (e.g., 910) (e.g., deregistering the card, rendering it inoperable). For example, the electronic device removes all values ​​from the stored-value card and renders the card inoperable. Thus, in some examples, all 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 implementations, at box 1016, based on the determination that ownership verification failed (e.g., verification information does not correspond to (or match) identification information (e.g., ownership verification failed)), at box 1018, the electronic device displays and / or generates an indication (e.g., indication 920D) (e.g., displaying a notification on the display of the electronic device) feedback on the ownership verification failure (e.g., visual, audio, and / or tactile output generated by the 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., the 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 prompts the user to provide information again to verify ownership by generating feedback to notify the user that the electronic device has determined ownership verification has failed.

[0365] According to some implementations, after at least some of the stored value is transferred from a 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 device's e-wallet application includes multiple virtual cards (or accounts) of the same type, the values ​​of the virtual cards are highlighted to help the user identify the multiple virtual cards. Thus, the electronic device informs 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 identify multiple virtual cards stored on (or accessible by) the electronic device and their corresponding stored values.

[0366] According to some implementations, after at least some (or all) of the stored value is transferred from a stored-value card (e.g., 910) to a virtual card stored on an electronic device, the electronic device displays the virtual card's access plan information (e.g., monthly pass, 10-ride pass, etc.), 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 electronic device's status, such as what virtual card is stored on the device and what access plan information (if any) is included in that virtual card.

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

[0368] According to some implementation schemes, (e.g., after transferring at least some (or all) of the stored values ​​from the card to the stored virtual card) the electronic device designates the virtual card's account as usable without authentication checks, based on the determination that the electronic device does not have another connected access account (e.g., the newly configured access account is the initially (first) configured access account and / or the only currently valid access account connected to the electronic device). In some examples, using the virtual card's account to participate in transactions includes releasing information (e.g., transaction information, payment information) from the secure element of the electronic device. Therefore, the electronic device designates the virtual card (based on the determination that the virtual card is the only access account for the account information application) as a fast pass card, which the electronic device can use without authentication checks for transactions corresponding to a first type of request (e.g., a request from a transaction terminal, a funds request from the access account). Thus, by automatically designating a virtual card that is usable without authentication checks, the operability of the electronic device is enhanced by reducing the amount of input required to perform transaction operations using the virtual card. According to some implementation schemes, based on the determination that the electronic device has one or more other connected access accounts, the electronic device waives the option to designate (or waives prompting the user to designate) the virtual card's account as available without authentication verification (and / or designates the virtual card's account as unavailable without authentication verification). Therefore, the electronic device does not designate (based on the determination that the virtual card is not the only access account for the account information application) the virtual card as a fast pass card.

[0369] According to some implementations, (e.g., 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 access account (e.g., the newly configured access account is the initially (first) configured access account and / or the only currently valid access account connected to the electronic device), and further based on receiving user input indicating that the account is not desired to be available without authentication (e.g., user input removing a previous fast pass card from the account information application), the electronic device abandons specifying that the virtual card's account is available without authentication (and / or specifying that the virtual card's account is not available without authentication). Therefore, the electronic device does not specify (based on determining that the virtual card is not the only access account for the account information application) the virtual card as a fast pass card. In some examples, based on not receiving user input indicating that the account is not desired to be available without authentication, or based on receiving user input indicating that the account is desired to be available without authentication, the electronic device selects the virtual card's account that is available without authentication. Therefore, when an electronic device designates a virtual card as a fast pass, the electronic device can use the fast pass without undergoing the verification and authentication of a transaction corresponding to a first type of request (e.g., a request from a transaction terminal, or a fund request from a pass account).

[0370] According to some implementations, the electronic device receives user input indicating that it does not want the account to be available without authentication (e.g., by receiving user input selecting the "Do not use account" option to make the account available without authentication), and in response to receiving user input indicating that it does not want the account to be available without authentication, specifies that the virtual card's account is unusable without authentication. Therefore, the user can disable the features of the Fastpass account.

[0371] According to some implementations, an electronic device receives user input selecting an account that can be used without authentication verification (e.g., an account corresponding to a virtual card among multiple accounts in an account information application), and in response to receiving user input selecting an account that can be used without authentication verification, specifies that the selected account (e.g., an account in an account information application) is available without authentication verification, such as regarding... Figures 15A to 15M Therefore, users can specify that the selected account should be a Fastpass account.

[0372] Note that the above reference method 1000 (for example, Figure 10The details of the process described herein 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 The user interface. For example, an account configured using the techniques of methods 800 and 1000 can be used to perform the techniques described in reference methods 1200, 1400, 1600, 1800, and 2000. For example, the techniques of method 1200 can be used to deposit funds into stored-value accounts as described in methods 800, 1000, 1400, 1600, 1800, and 2000. For example, as discussed with respect to methods 1800 and 2000, the account to which funds are deposited can be moved to or from different devices. For the sake of brevity, these details will not be repeated below.

[0373] Figures 11A to 11N Exemplary user interfaces for topping up stored-value accounts configured on electronic devices (e.g., 100) having displays and one or more input devices are shown according to some embodiments. The user interfaces in these figures are used to illustrate... Figures 12A to 12B The process described below is the process in the middle.

[0374] In some implementations, users wish to top up a stored-value account on an electronic device. For example, a user initiates a process of withdrawing funds from a payment account (e.g., a revolving credit account) also stored on the electronic device and transferring those funds to a stored-value account (e.g., a toll account). In some examples, a user can use funds in the stored-value account for transactions (e.g., paying tolls using NFC) and can use the payment account for separate transactions (e.g., paying for retail purchases using NFC).

[0375] Figure 11A An exemplary electronic device 100 is shown. The electronic device 100 has an e-wallet application that includes a stored-value account and a payment account. The electronic device 100 displays a representation of the stored-value account, including activatable top-up options, on its display screen. Figures 11A to 11BThe diagram illustrates a representation of a stored-value account displayed on a display of electronic device 100 according to some embodiments. In some embodiments, the stored-value account is a payment account. In some examples, the payment account corresponds to a revolving credit account or debit account. In some embodiments, the stored-value account is a toll account. In some examples, the toll account stores toll schedule (or toll ticket) information. In some examples, the toll schedule is a monthly or weekly toll schedule. In some examples, the funds in the stored-value account are physically stored on 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 a 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 other 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 implementations, the stored-value account representation includes a menu (e.g., 1140) that includes multiple selectable power indicators (e.g., 1140A, 1140B, 1140C). In some examples, the menu (e.g., 1140) includes an information power indicator (e.g., 1140A). In some examples, the menu (e.g., 1140) includes a transaction power indicator (e.g., 1140B). In some examples, the menu (e.g., 1140) includes a device power indicator (e.g., 1140C). In some implementations (e.g., in response to a user's selection of an information power indicator (e.g., 1140A), such as... Figure 11A As shown), the stored-value account representation displays transfer account options (e.g., 1146B). Therefore, in some examples, electronic device 100 provides the user with the option to move an account from one device to another, such as in reference [reference needed]. Figures 17C to 17H As stated above.

[0377] In some implementations (e.g., in response to a user's selection of an information display representation (e.g., 1140A), such as... Figure 11A As shown), the representation of the stored-value account displays: an indication of the device where the stored-value account is currently located among one or more of the plurality of devices (e.g., associated with the user account) (e.g., 1144); characteristics and / or data of the stored-value account (e.g., current balance, pass information); a selection enable / disable notification representation (e.g., 1148A); and a selection enable / disable notification representation for enabling or disabling the stored-value account without checking authentication (e.g., 1148B), such as references Figures 15A to 15MThe aforementioned; and the optional enablement representation (e.g., 1148C) for specifying or not specifying that a stored value account is available for transaction on two or more devices (e.g., associated with a user account), although the payment credentials of the stored value account are stored only in one of the two or more devices at a time (a limitation of the stored value account as a stored value account), such as reference Figures 19A to 19H As stated above.

[0378] In some embodiments, electronic device 100 receives user input indicating whether or not to receive notifications regarding transactions associated with a stored-value account (e.g., by moving a selectable power indicator to an "on" or "off" position, as shown with respect to selectable power indicator 1148A). In some embodiments, electronic device 100 receives user input indicating whether or not to make the stored-value account available without authentication checks (e.g., by moving a selectable power indicator to an "off" position, as shown with respect to selectable power indicator 1148B), such as references Figures 15A to 15M Therefore, electronic device 100 provides the user with the option to designate or not designate a stored-value account as a quickpass account (e.g., using selectable power indicator 1148B), through which funds can be transferred in a specific transaction without authentication. In some embodiments, when a stored-value account is designated as a quickpass account (e.g., by moving selectable power indicator 1148B to the "on" position), electronic device 100 provides faster access to the stored-value account. In some embodiments, when a stored-value account is not designated as a quickpass account (e.g., by moving selectable power indicator 1148B to the "off" position), electronic device 100 provides additional security for the account provided on the electronic device. In some embodiments, electronic device 100 receives user input designating a stored-value account as an account available on two or more devices (e.g., associated with a user account) (e.g., by receiving input to move a selectable power indicator to the "on" or "off" position, as shown with respect to selectable power indicator 1148C). In some examples, a stored-value account is designated to be usable for transactions on two or more devices (e.g., associated with a user account), although the stored-value account's credentials are stored only on one of the two or more devices at a time (e.g., the stored-value account is a limitation of the stored-value account), such as references Figures 19A to 19H Therefore, in some examples, when a user has specified that a stored-value account is available at the electronic device, the electronic device 100 requests the credentials for the stored-value account.

[0379] In some implementations, electronic device 100 displays a representation of a second payment account on its display that does not include an active top-up option. In some examples, the second payment account is not a stored-value account, and therefore funds cannot be topped up at electronic device 100. In some examples, the representation of the second payment account includes the current balance (e.g., outstanding balance) of the payment account (e.g., revolving credit account), while the represent...

Claims

1. A method to be performed at an electronic device, comprising: On electronic devices with e-wallet applications: It has been detected that one or more payment criteria used for payments made using a stored-value account have been met; In response to detecting that one or more payment criteria for making a payment using the stored value account have been met and determining that the payment credentials for the stored value account are not available in the e-wallet application of the electronic device, a request is made for payment credentials from the stored value account of a second device other than the electronic device. as well as After requesting the payment credential from the stored-value account when it is available at the second device, the electronic device receives the payment credential from the stored-value account of the second device.

2. The method of claim 1, wherein the payment credentials from the stored-value account of the second device are received at the electronic device via device-to-device communication using a near-field wireless network.

3. The method according to any one of claims 1 to 2, wherein when the electronic device receives a request for payment, a first payment standard in the group of one or more payment standards is satisfied.

4. The method according to any one of claims 1 to 2, wherein the electronic device includes one or more short-range communication radio components, and wherein when the electronic device detects a field using the one or more short-range communication radio components, a second payment standard of the group of one or more payment standards is satisfied.

5. The method according to any one of claims 1 to 2, wherein when the electronic device detects a situation indicating that payment will be requested, a third payment standard in the group of one or more payment standards is satisfied.

6. The method according to any one of claims 1 to 2, wherein when the electronic device detects the activation of an option corresponding to the stored-value account, a fourth payment standard in the group of one or more payment standards is satisfied.

7. The method according to any one of claims 1 to 2, wherein when the electronic device determines that the stored-value account has been designated as available at the electronic device, the fifth payment standard in the group of one or more payment standards is satisfied.

8. The method according to any one of claims 1 to 2, wherein the stored value account is a first type account, and wherein when the electronic device receives a request for payment using the first type account, a sixth payment standard of the group of one or more payment standards is satisfied.

9. The method according to any one of claims 1 to 2, wherein requesting payment credentials for the stored-value account from the second device comprises transmitting a request to the second device, wherein the request identifies the stored-value account.

10. The method according to any one of claims 1 to 2, further comprising: In response to detecting that one or more payment criteria for making a payment using the stored value account have been met and that the payment credentials for the stored value account are available in the electronic wallet application of the electronic device, the payment continues using the stored value account.

11. The method according to any one of claims 1 to 2, further comprising: In response to detecting that one or more payment criteria for making a payment using the stored-value account have been met and determining that the payment credentials for the stored-value account are unavailable in the electronic wallet application of the electronic device, and based on the fact that no payment credentials for the stored-value account have been received: Abandoning the use of the stored-value account to continue the payment; and The user is presented with a notification indicating that the stored value account is unavailable for the payment.

12. The method according to any one of claims 1 to 2, further comprising: After receiving payment credentials from the stored-value account of the second device at the electronic device: The funds are transferred from the stored value account to the transaction terminal to make the payment; as well as In response to transferring funds from the stored value account to the transaction terminal, the payment credentials of the stored value account are transmitted from the electronic device to the second device.

13. The method according to any one of claims 1 to 2, further comprising: After receiving payment credentials from the stored-value account of the second device at the electronic device: The funds are transferred from the stored value account to the transaction terminal to make the payment; as well as In response to transferring funds from the stored value account to the transaction terminal, the transmission of payment credentials from the stored value account from the electronic device to the second device is abandoned.

14. The method according to any one of claims 1 to 2, further comprising: After receiving payment credentials from the stored-value account of the second device at the electronic device: Receive a request for payment credentials for the stored-value account from the second device; as well as In response to receiving the request for payment credentials for the stored-value account, the payment credentials for the stored-value account are transmitted from the electronic device to the second device.

15. The method according to any one of claims 1 to 2, further comprising: After receiving payment credentials from the stored-value account of the second device at the electronic device: Determine whether the pre-determined conditions for the scheduled events have been met; Upon confirmation that the predetermined arrangement event conditions are met, the payment credentials for the stored-value account are transmitted from the electronic device to the second device.

16. The method according to any one of claims 1 to 2, wherein the electronic device uses a first communication protocol to receive payment credentials from the stored-value account of the second device and the electronic device uses a second communication protocol different from the first communication protocol to make the payment to the transaction terminal.

17. The method of any one of claims 1 to 2, wherein the electronic device comprises one or more radio units, and wherein the electronic device uses a first set of the one or more radio units of the electronic device to receive payment credentials from the stored-value account of the second device, and wherein the electronic device uses a second set of the one or more radio units, different from the first set of the one or more radio units, to make the payment to the transaction terminal.

18. The method according to any one of claims 1 to 2, further comprising: After receiving payment credentials from the stored-value account of the second device at the electronic device: Presents an instruction to request authentication to make a payment using the payment credentials of the stored value account; Receive authentication information; as well as Based on the determination that the authentication information matches the registration authentication information used for authorized transactions, funds are transferred from the stored value account to the transaction terminal to make the payment.

19. A computer-readable storage medium storing 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: It has been detected that one or more payment criteria used for payments made using a stored-value account have been met; In response to detecting that one or more payment criteria for making a payment using the stored value account have been met and determining that the payment credentials for the stored value account are not available in the e-wallet application of the electronic device, a request is made for payment credentials from the stored value account of a second device other than the electronic device. as well as After requesting the payment credential from the stored-value account when it is available at the second device, the electronic device receives the payment credential from the stored-value account of the second device.

20. The computer-readable storage medium of claim 19, wherein the payment credentials from the stored-value account of the second device are received at the electronic device via device-to-device communication using a near-field wireless network.

21. The computer-readable storage medium according to any one of claims 19 to 20, wherein when the electronic device receives a request for payment, a first payment standard of the group of one or more payment standards is satisfied.

22. The computer-readable storage medium according to any one of claims 19 to 20, wherein the electronic device includes one or more short-range communication radio components, and wherein when the electronic device detects a field using the one or more short-range communication radio components, a second payment standard of the group of one or more payment standards is satisfied.

23. The computer-readable storage medium according to any one of claims 19 to 20, wherein when the electronic device detects a situation indicating that payment will be requested, a third payment standard of the group of one or more payment standards is satisfied.

24. The computer-readable storage medium according to any one of claims 19 to 20, wherein when the electronic device detects activation of an option corresponding to the stored-value account, a fourth payment standard of the group of one or more payment standards is satisfied.

25. The computer-readable storage medium according to any one of claims 19 to 20, wherein when the electronic device determines that the stored-value account has been designated as available at the electronic device, a fifth payment standard of the group of one or more payment standards is satisfied.

26. The computer-readable storage medium according to any one of claims 19 to 20, wherein the stored-value account is a first type of account, and wherein when the electronic device receives a request for payment using the first type of account, a sixth payment standard of the group of one or more payment standards is satisfied.

27. The computer-readable storage medium according to any one of claims 19 to 20, wherein requesting payment credentials for the stored-value account from the second device comprises transmitting a request to the second device, wherein the request identifies the stored-value account.

28. The computer-readable storage medium according to any one of claims 19 to 20, wherein the one or more programs further include instructions for performing the following operations: In response to detecting that one or more payment criteria for making a payment using the stored value account have been met and that the payment credentials for the stored value account are available in the electronic wallet application of the electronic device, the payment continues using the stored value account.

29. The computer-readable storage medium according to any one of claims 19 to 20, wherein the one or more programs further include instructions for performing the following operations: In response to detecting that one or more payment criteria for making a payment using the stored-value account have been met and determining that the payment credentials for the stored-value account are unavailable in the electronic wallet application of the electronic device, and based on the fact that no payment credentials for the stored-value account have been received: Abandoning the use of the stored-value account to continue the payment; and The user is presented with a notification indicating that the stored value account is unavailable for the payment.

30. The computer-readable storage medium according to any one of claims 19 to 20, wherein the one or more programs further include instructions for performing the following operations: After receiving payment credentials from the stored-value account of the second device at the electronic device: Transferring funds from the stored-value account to the transaction terminal to make the payment; and In response to transferring funds from the stored value account to the transaction terminal, the payment credentials of the stored value account are transmitted from the electronic device to the second device.

31. The computer-readable storage medium according to any one of claims 19 to 20, wherein the one or more programs further include instructions for performing the following operations: After receiving payment credentials from the stored-value account of the second device at the electronic device: Transferring funds from the stored-value account to the transaction terminal to make the payment; and In response to transferring funds from the stored value account to the transaction terminal, the transmission of payment credentials from the stored value account from the electronic device to the second device is abandoned.

32. The computer-readable storage medium according to any one of claims 19 to 20, wherein the one or more programs further include instructions for performing the following operations: After receiving payment credentials from the stored-value account of the second device at the electronic device: Receive a request from the second device for payment credentials for the stored-value account; and In response to receiving the request for payment credentials for the stored-value account, the payment credentials for the stored-value account are transmitted from the electronic device to the second device.

33. The computer-readable storage medium according to any one of claims 19 to 20, wherein the one or more programs further include instructions for performing the following operations: After receiving payment credentials from the stored-value account of the second device at the electronic device: Determine whether the pre-determined conditions for the scheduled events have been met; Upon confirmation that the predetermined arrangement event conditions are met, the payment credentials for the stored-value account are transmitted from the electronic device to the second device.

34. The computer-readable storage medium according to any one of claims 19 to 20, wherein the electronic device uses a first communication protocol to receive payment credentials from the stored-value account of the second device and the electronic device uses a second communication protocol different from the first communication protocol to make the payment to the transaction terminal.

35. The computer-readable storage medium according to any one of claims 19 to 20, wherein the electronic device includes one or more radio units, and wherein the electronic device uses a first set of the one or more radio components of the electronic device to receive payment credentials from the stored-value account of the second device, and wherein the electronic device uses a second set of the one or more radio components, different from the first set of the one or more radio components, to make the payment to a transaction terminal.

36. The computer-readable storage medium according to any one of claims 19 to 20, wherein the one or more programs further include instructions for performing the following operations: After receiving payment credentials from the stored-value account of the second device at the electronic device: Presents an instruction to request authentication to make a payment using the payment credentials of the stored value account; Receive authentication information; as well as Based on the determination that the authentication information matches the registration authentication information used for authorized transactions, funds are transferred from the stored value account to the transaction terminal to make the payment.

37. An electronic device comprising: e-wallet applications; One or more processors; and The memory stores 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: It has been detected that one or more payment criteria used for payments made using a stored-value account have been met; In response to detecting that one or more payment criteria for making a payment using the stored value account have been met and determining that the payment credentials for the stored value account are not available in the e-wallet application of the electronic device, a request is made for payment credentials from the stored value account of a second device other than the electronic device. as well as After requesting the payment credential from the stored-value account when it is available at the second device, the electronic device receives the payment credential from the stored-value account of the second device.

38. The electronic device of claim 37, wherein the payment credentials from the stored-value account of the second device are received at the electronic device via device-to-device communication using a near-field wireless network.

39. The electronic device according to any one of claims 37 to 38, wherein when the electronic device receives a request for payment, it satisfies a first payment standard in one or more of the group of payment standards.

40. The electronic device according to any one of claims 37 to 38, wherein the electronic device includes one or more short-range communication radio components, and wherein when the electronic device detects a field using the one or more short-range communication radio components, a second payment standard of the group of one or more payment standards is satisfied.

41. The electronic device according to any one of claims 37 to 38, wherein when the electronic device detects a situation indicating that payment will be requested, a third payment standard of the group of one or more payment standards is satisfied.

42. The electronic device according to any one of claims 37 to 38, wherein when the electronic device detects activation of an option corresponding to the stored-value account, a fourth payment standard in the group of one or more payment standards is satisfied.

43. The electronic device according to any one of claims 37 to 38, wherein when the electronic device determines that the stored-value account has been designated as available at the electronic device, the fifth payment standard of the group of one or more payment standards is satisfied.

44. The electronic device according to any one of claims 37 to 38, wherein the stored-value account is a first type account, and wherein when the electronic device receives a request for payment using the first type account, a sixth payment standard of the group of one or more payment standards is satisfied.

45. The electronic device according to any one of claims 37 to 38, wherein requesting payment credentials for the stored-value account from the second device comprises transmitting a request to the second device, wherein the request identifies the stored-value account.

46. ​​The electronic device according to any one of claims 37 to 38, wherein the one or more programs further include instructions for performing the following operations: In response to detecting that one or more payment criteria for making a payment using the stored value account have been met and that the payment credentials for the stored value account are available in the electronic wallet application of the electronic device, the payment continues using the stored value account.

47. The electronic device according to any one of claims 37 to 38, wherein the one or more programs further include instructions for performing the following operations: In response to detecting that one or more payment criteria for making a payment using the stored-value account have been met and determining that the payment credentials for the stored-value account are unavailable in the electronic wallet application of the electronic device, and based on the fact that no payment credentials for the stored-value account have been received: Abandoning the use of the stored-value account to continue the payment; and The user is presented with a notification indicating that the stored value account is unavailable for the payment.

48. The electronic device according to any one of claims 37 to 38, wherein the one or more programs further include instructions for performing the following operations: After receiving payment credentials from the stored-value account of the second device at the electronic device: Transferring funds from the stored-value account to the transaction terminal to make the payment; and In response to transferring funds from the stored value account to the transaction terminal, the payment credentials of the stored value account are transmitted from the electronic device to the second device.

49. The electronic device according to any one of claims 37 to 38, wherein the one or more programs further include instructions for performing the following operations: After receiving payment credentials from the stored-value account of the second device at the electronic device: Transferring funds from the stored-value account to the transaction terminal to make the payment; and In response to transferring funds from the stored value account to the transaction terminal, the transmission of payment credentials from the stored value account from the electronic device to the second device is abandoned.

50. The electronic device according to any one of claims 37 to 38, wherein the one or more programs further include instructions for performing the following operations: After receiving payment credentials from the stored-value account of the second device at the electronic device: Receive a request from the second device for payment credentials for the stored-value account; and In response to receiving the request for payment credentials for the stored-value account, the payment credentials for the stored-value account are transmitted from the electronic device to the second device.

51. The electronic device according to any one of claims 37 to 38, wherein the one or more programs further include instructions for performing the following operations: After receiving payment credentials from the stored-value account of the second device at the electronic device: Determine whether the pre-determined conditions for the scheduled events have been met; Upon confirmation that the predetermined arrangement event conditions are met, the payment credentials for the stored-value account are transmitted from the electronic device to the second device.

52. The electronic device according to any one of claims 37 to 38, wherein the electronic device uses a first communication protocol to receive payment credentials from the stored-value account of the second device and the electronic device uses a second communication protocol different from the first communication protocol to make the payment to the transaction terminal.

53. The electronic device according to any one of claims 37 to 38, wherein the electronic device comprises one or more radio units, and wherein the electronic device uses a first set of the one or more radio units of the electronic device to receive payment credentials from the stored-value account of the second device, and wherein the electronic device uses a second set of the one or more radio units, different from the first set of the one or more radio units, to make the payment to the transaction terminal.

54. The electronic device according to any one of claims 37 to 38, wherein the one or more programs further include instructions for performing the following operations: After receiving payment credentials from the stored-value account of the second device at the electronic device: Presents an instruction to request authentication to make a payment using the payment credentials of the stored value account; Receive authentication information; as well as Based on the determination that the authentication information matches the registration authentication information used for authorized transactions, funds are transferred from the stored value account to the transaction terminal to make the payment.

55. An electronic device comprising: e-wallet applications; and Apparatus for performing the method according to any one of claims 1 to 18.

56. A computer program product comprising a program code portion configured to perform the method according to any one of claims 1 to 18 when the computer program product is run on one or more computing devices.

Images