Managing information on a computer system

The present disclosure generally relates to methods and user interfaces for managing information on computer systems. In some embodiments, methods and user interfaces for managing display of user interface elements based on movement of the computer system and requesting account information are described. In some embodiments, methods and user interface for provisioning an account onto a computer system are described. In some embodiments, methods and user interfaces for associating a transfer amount with an account are described. In some embodiments, methods and user interfaces for displaying user interface elements corresponding to transaction types are described. In some embodiments, methods and user interfaces for managing one or more pending loans are described. In some embodiments, methods for entering a numeric sequence are described. In some embodiments, methods for locking a computer system while entering a number sequence are described.

FIELD

The present disclosure relates generally to computer user interfaces, and more specifically to techniques for managing information on computer systems.

BACKGROUND

Users often perform operations using personal electronic devices, such as transferring information between devices. Such techniques typically require the user to provide various inputs and authorization to perform the operations.

BRIEF SUMMARY

Some techniques for managing information on computer systems and/or electronic devices, however, are generally cumbersome and inefficient. For example, some existing techniques use a complex and time-consuming user interface, which may include multiple key presses or keystrokes. Existing techniques require more time than necessary, wasting user time and device energy. This latter consideration is particularly important in battery-operated devices.

Accordingly, the present technique provides electronic devices with faster, more efficient methods and interfaces for receiving and provisioning information on electronic devices. Such methods and interfaces optionally complement or replace other methods for receiving and provisioning information on electronic devices. Such methods and interfaces reduce the cognitive burden on a user and produce a more efficient human-machine interface. For battery-operated computing devices, such methods and interfaces conserve power and increase the time between battery charges.

In accordance with some embodiments, a method performed at a computer system that is in communication with a display generation component and one or more input devices is described. The method comprises: detecting, via one or more input devices, user input to initiate a transaction request; in response to detecting the user input to initiate the transaction request, displaying, via the display generation component, a transaction user interface, wherein displaying the transaction user interface includes display: at a first location, via the display generation component, a first graphical user interface element indicating a location of a reader of the computer system, and at a second location different from the first location, via the display generation component, a second graphical user interface element, wherein the second graphical user interface element is displayed in a first orientation; while displaying the transaction user interface, detecting a movement of the computer system; and in response to detecting the movement of the computer system, rotating the second graphical user interface element around a centroid of the second graphical user interface element to a second orientation different from the first orientation, while continuing to display, at the first location, the first graphical user interface element indicating the location of the reader of the computer system.

In accordance with some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system that is in communication with a display generation component and one or more input devices, the one or more programs including instructions for: detecting, via one or more input devices, user input to initiate a transaction request; in response to detecting the user input to initiate the transaction request, displaying, via the display generation component, a transaction user interface, wherein displaying the transaction user interface includes display: at a first location, via the display generation component, a first graphical user interface element indicating a location of a reader of the computer system, and at a second location different from the first location, via the display generation component, a second graphical user interface element, wherein the second graphical user interface element is displayed in a first orientation; while displaying the transaction user interface, detecting a movement of the computer system; and in response to detecting the movement of the computer system, rotating the second graphical user interface element around a centroid of the second graphical user interface element to a second orientation different from the first orientation, while continuing to display, at the first location, the first graphical user interface element indicating the location of the reader of the computer system.

In accordance with some embodiments, a transitory computer-readable storage medium is described. The transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system that is in communication with a display generation component and one or more input devices, the one or more programs including instructions for: detecting, via one or more input devices, user input to initiate a transaction request; in response to detecting the user input to initiate the transaction request, displaying, via the display generation component, a transaction user interface, wherein displaying the transaction user interface includes display: at a first location, via the display generation component, a first graphical user interface element indicating a location of a reader of the computer system, and at a second location different from the first location, via the display generation component, a second graphical user interface element, wherein the second graphical user interface element is displayed in a first orientation; while displaying the transaction user interface, detecting a movement of the computer system; and in response to detecting the movement of the computer system, rotating the second graphical user interface element around a centroid of the second graphical user interface element to a second orientation different from the first orientation, while continuing to display, at the first location, the first graphical user interface element indicating the location of the reader of the computer system.

In accordance with some embodiments, a computer system is described. The computer system comprises one or more processors, wherein the computer system is in communication with a display generation component and one or more input devices; and memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: detecting, via one or more input devices, user input to initiate a transaction request; in response to detecting the user input to initiate the transaction request, displaying, via the display generation component, a transaction user interface, wherein displaying the transaction user interface includes display: at a first location, via the display generation component, a first graphical user interface element indicating a location of a reader of the computer system, and at a second location different from the first location, via the display generation component, a second graphical user interface element, wherein the second graphical user interface element is displayed in a first orientation; while displaying the transaction user interface, detecting a movement of the computer system; and in response to detecting the movement of the computer system, rotating the second graphical user interface element around a centroid of the second graphical user interface element to a second orientation different from the first orientation, while continuing to display, at the first location, the first graphical user interface element indicating the location of the reader of the computer system.

In accordance with some embodiments, a computer system is described. The computer system is in communication with a display generation component and one or more input devices. The computer system comprises: means for detecting, via one or more input devices, user input to initiate a transaction request; means, responsive to detecting the user input to initiate the transaction request, for displaying, via the display generation component, a transaction user interface, wherein displaying the transaction user interface includes display: at a first location, via the display generation component, a first graphical user interface element indicating a location of a reader of the computer system, and at a second location different from the first location, via the display generation component, a second graphical user interface element, wherein the second graphical user interface element is displayed in a first orientation; means, while displaying the transaction user interface, for detecting a movement of the computer system; and means, responsive to detecting the movement of the computer system, for rotating the second graphical user interface element around a centroid of the second graphical user interface element to a second orientation different from the first orientation, while continuing to display, at the first location, the first graphical user interface element indicating the location of the reader of the computer system.

In accordance with some embodiments, a computer program product is described. The computer program product comprises one or more programs configured to be executed by one or more processors of a computer system that is in communication with a display generation component and one or more input devices, the one or more programs including instructions for: detecting, via one or more input devices, user input to initiate a transaction request; in response to detecting the user input to initiate the transaction request, displaying, via the display generation component, a transaction user interface, wherein displaying the transaction user interface includes display: at a first location, via the display generation component, a first graphical user interface element indicating a location of a reader of the computer system, and at a second location different from the first location, via the display generation component, a second graphical user interface element, wherein the second graphical user interface element is displayed in a first orientation; while displaying the transaction user interface, detecting a movement of the computer system; and in response to detecting the movement of the computer system, rotating the second graphical user interface element around a centroid of the second graphical user interface element to a second orientation different from the first orientation, while continuing to display, at the first location, the first graphical user interface element indicating the location of the reader of the computer system.

In accordance with some embodiments, a method performed at a computer system that is in communication with a display generation component and one or more input devices is described. The method comprises: detecting, via one or more input devices, user input to initiate a transaction request; communicating with a user device; in accordance with a determination that an account associated with a provider of the transaction request is available on the user device, requesting, from the user device, the account associated with the provider of the transaction request; and in accordance with a determination that the account associated with the provider of the transaction request is not available on the user device, forgoing requesting, from the user device, the account associated with the provider of the transaction request.

In accordance with some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system that is in communication with a display generation component and one or more input devices, the one or more programs including instructions for: detecting, via one or more input devices, user input to initiate a transaction request; communicating with a user device; in accordance with a determination that an account associated with a provider of the transaction request is available on the user device, requesting, from the user device, the account associated with the provider of the transaction request; and in accordance with a determination that the account associated with the provider of the transaction request is not available on the user device, forgoing requesting, from the user device, the account associated with the provider of the transaction request.

In accordance with some embodiments, a transitory computer-readable storage medium is described. The transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system that is in communication with a display generation component and one or more input devices, the one or more programs including instructions for: detecting, via one or more input devices, user input to initiate a transaction request; communicating with a user device; in accordance with a determination that an account associated with a provider of the transaction request is available on the user device, requesting, from the user device, the account associated with the provider of the transaction request; and in accordance with a determination that the account associated with the provider of the transaction request is not available on the user device, forgoing requesting, from the user device, the account associated with the provider of the transaction request.

In accordance with some embodiments, a computer system is described. The computer system comprises one or more processors, wherein the computer system is in communication with a display generation component and one or more input devices; and memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: detecting, via one or more input devices, user input to initiate a transaction request; communicating with a user device; in accordance with a determination that an account associated with a provider of the transaction request is available on the user device, requesting, from the user device, the account associated with the provider of the transaction request; and in accordance with a determination that the account associated with the provider of the transaction request is not available on the user device, forgoing requesting, from the user device, the account associated with the provider of the transaction request.

In accordance with some embodiments, a computer system is described. The computer system is in communication with a display generation component and one or more input devices. The computer system comprises: means for detecting, via one or more input devices, user input to initiate a transaction request; means for communicating with a user device; means, in accordance with a determination that an account associated with a provider of the transaction request is available on the user device, for requesting, from the user device, the account associated with the provider of the transaction request; and means, in accordance with a determination that the account associated with the provider of the transaction request is not available on the user device, for forgoing requesting, from the user device, the account associated with the provider of the transaction request.

In accordance with some embodiments, a computer program product is described. The computer program product comprises one or more programs configured to be executed by one or more processors of a computer system that is in communication with a display generation component and one or more input devices, the one or more programs including instructions for: detecting, via one or more input devices, user input to initiate a transaction request; communicating with a user device; in accordance with a determination that an account associated with a provider of the transaction request is available on the user device, requesting, from the user device, the account associated with the provider of the transaction request; and in accordance with a determination that the account associated with the provider of the transaction request is not available on the user device, forgoing requesting, from the user device, the account associated with the provider of the transaction request.

In accordance with some embodiments, a method performed at a computer system that is in communication with a display generation component and one or more input devices is described. The method comprises: in response to detecting a sign-in of a user account after a software update: in accordance with a determination that a first set of provision criteria are met, including a first provisioning criterion that is met when an account associated with the user account exceeds a threshold amount, initiating a process to provision the account onto the computer system; and in accordance with a determination that the first set of provisioning criteria are not met, forgoing initiating the process to provision the account onto the computer system.

In accordance with some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system that is in communication with a display generation component and one or more input devices, the one or more programs including instructions for: in response to detecting a sign-in of a user account after a software update: in accordance with a determination that a first set of provision criteria are met, including a first provisioning criterion that is met when an account associated with the user account exceeds a threshold amount, initiating a process to provision the account onto the computer system; and in accordance with a determination that the first set of provisioning criteria are not met, forgoing initiating the process to provision the account onto the computer system.

In accordance with some embodiments, a transitory computer-readable storage medium is described. The transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system that is in communication with a display generation component and one or more input devices, the one or more programs including instructions for: in response to detecting a sign-in of a user account after a software update: in accordance with a determination that a first set of provision criteria are met, including a first provisioning criterion that is met when an account associated with the user account exceeds a threshold amount, initiating a process to provision the account onto the computer system; and in accordance with a determination that the first set of provisioning criteria are not met, forgoing initiating the process to provision the account onto the computer system.

In accordance with some embodiments, a computer system is described. The computer system comprises one or more processors, wherein the computer system is in communication with a display generation component and one or more input devices; and memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: in response to detecting a sign-in of a user account after a software update: in accordance with a determination that a first set of provision criteria are met, including a first provisioning criterion that is met when an account associated with the user account exceeds a threshold amount, initiating a process to provision the account onto the computer system; and in accordance with a determination that the first set of provisioning criteria are not met, forgoing initiating the process to provision the account onto the computer system.

In accordance with some embodiments, a computer system is described. The computer system is in communication with a display generation component and one or more input devices. The computer system comprises: means, responsive to detecting a sign-in of a user account after a software update for: in accordance with a determination that a first set of provision criteria are met, including a first provisioning criterion that is met when an account associated with the user account exceeds a threshold amount, initiating a process to provision the account onto the computer system; and in accordance with a determination that the first set of provisioning criteria are not met, forgoing initiating the process to provision the account onto the computer system.

In accordance with some embodiments, a computer program product is described. The computer program product comprises one or more programs configured to be executed by one or more processors of a computer system that is in communication with a display generation component and one or more input devices, the one or more programs including instructions for: in response to detecting a sign-in of a user account after a software update: in accordance with a determination that a first set of provision criteria are met, including a first provisioning criterion that is met when an account associated with the user account exceeds a threshold amount, initiating a process to provision the account onto the computer system; and in accordance with a determination that the first set of provisioning criteria are not met, forgoing initiating the process to provision the account onto the computer system.

In accordance with some embodiments, a method performed at a computer system that is in communication with a display generation component and one or more input devices is described. The method comprises: receiving a request to associate a transfer amount with an account; displaying a first user interface element associated with a recurring transaction and an individual transaction and a second user interface element associated with an individual transaction and not associated with a recurring transaction; and in response to receiving user input: in accordance with a determination that the user input corresponds to a selection of the first user interface element, configuring the transfer amount for use with recurring transactions and individual transactions; and in accordance with a determination that the user input corresponds to a selection of the second user interface element, configuring the transfer amount for use with individual transactions without configuring the transfer amount for use with recurring transactions.

In accordance with some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system that is in communication with a display generation component and one or more input devices, the one or more programs including instructions for: receiving a request to associate a transfer amount with an account; displaying a first user interface element associated with a recurring transaction and an individual transaction and a second user interface element associated with an individual transaction and not associated with a recurring transaction; and in response to receiving user input: in accordance with a determination that the user input corresponds to a selection of the first user interface element, configuring the transfer amount for use with recurring transactions and individual transactions; and in accordance with a determination that the user input corresponds to a selection of the second user interface element, configuring the transfer amount for use with individual transactions without configuring the transfer amount for use with recurring transactions.

In accordance with some embodiments, a transitory computer-readable storage medium is described. The transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system that is in communication with a display generation component and one or more input devices, the one or more programs including instructions for: receiving a request to associate a transfer amount with an account; displaying a first user interface element associated with a recurring transaction and an individual transaction and a second user interface element associated with an individual transaction and not associated with a recurring transaction; and in response to receiving user input: in accordance with a determination that the user input corresponds to a selection of the first user interface element, configuring the transfer amount for use with recurring transactions and individual transactions; and in accordance with a determination that the user input corresponds to a selection of the second user interface element, configuring the transfer amount for use with individual transactions without configuring the transfer amount for use with recurring transactions.

In accordance with some embodiments, a computer system is described. The computer system comprises one or more processors, wherein the computer system is in communication with a display generation component and one or more input devices; and memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: receiving a request to associate a transfer amount with an account; displaying a first user interface element associated with a recurring transaction and an individual transaction and a second user interface element associated with an individual transaction and not associated with a recurring transaction; and in response to receiving user input: in accordance with a determination that the user input corresponds to a selection of the first user interface element, configuring the transfer amount for use with recurring transactions and individual transactions; and in accordance with a determination that the user input corresponds to a selection of the second user interface element, configuring the transfer amount for use with individual transactions without configuring the transfer amount for use with recurring transactions.

In accordance with some embodiments, a computer system is described. The computer system is in communication with a display generation component and one or more input devices. The computer system comprises: means for receiving a request to associate a transfer amount with an account; means for displaying a first user interface element associated with a recurring transaction and an individual transaction and a second user interface element associated with an individual transaction and not associated with a recurring transaction; and means, responsive to receiving user input, for: in accordance with a determination that the user input corresponds to a selection of the first user interface element, configuring the transfer amount for use with recurring transactions and individual transactions; and in accordance with a determination that the user input corresponds to a selection of the second user interface element, configuring the transfer amount for use with individual transactions without configuring the transfer amount for use with recurring transactions.

In accordance with some embodiments, a computer program product is described. The computer program product comprises one or more programs configured to be executed by one or more processors of a computer system that is in communication with a display generation component and one or more input devices, the one or more programs including instructions for: receiving a request to associate a transfer amount with an account; displaying a first user interface element associated with a recurring transaction and an individual transaction and a second user interface element associated with an individual transaction and not associated with a recurring transaction; and in response to receiving user input: in accordance with a determination that the user input corresponds to a selection of the first user interface element, configuring the transfer amount for use with recurring transactions and individual transactions; and in accordance with a determination that the user input corresponds to a selection of the second user interface element, configuring the transfer amount for use with individual transactions without configuring the transfer amount for use with recurring transactions.

In accordance with some embodiments, a method performed at a computer system that is in communication with a display generation component and one or more input devices is described. The method comprises: receiving a request corresponding to a transaction for a first amount; in accordance with a determination that a first set of conditions is met, displaying, via the display generation component, a first activatable user interface element corresponding to a first quantity of transactions and to the first amount; and in accordance with a determination that a second set of conditions is met, displaying via the display generation component, a second activatable user interface element corresponding to a second quantity of transactions and to a second amount that is different from the first amount.

In accordance with some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system that is in communication with a display generation component and one or more input devices, the one or more programs including instructions for: receiving a request corresponding to a transaction for a first amount; in accordance with a determination that a first set of conditions is met, displaying, via the display generation component, a first activatable user interface element corresponding to a first quantity of transactions and to the first amount; and in accordance with a determination that a second set of conditions is met, displaying via the display generation component, a second activatable user interface element corresponding to a second quantity of transactions and to a second amount that is different from the first amount.

In accordance with some embodiments, a transitory computer-readable storage medium is described. The transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system that is in communication with a display generation component and one or more input devices, the one or more programs including instructions for: receiving a request corresponding to a transaction for a first amount; in accordance with a determination that a first set of conditions is met, displaying, via the display generation component, a first activatable user interface element corresponding to a first quantity of transactions and to the first amount; and in accordance with a determination that a second set of conditions is met, displaying via the display generation component, a second activatable user interface element corresponding to a second quantity of transactions and to a second amount that is different from the first amount.

In accordance with some embodiments, a computer system is described. The computer system comprises one or more processors, wherein the computer system is in communication with a display generation component and one or more input devices; and memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: receiving a request corresponding to a transaction for a first amount; in accordance with a determination that a first set of conditions is met, displaying, via the display generation component, a first activatable user interface element corresponding to a first quantity of transactions and to the first amount; and in accordance with a determination that a second set of conditions is met, displaying via the display generation component, a second activatable user interface element corresponding to a second quantity of transactions and to a second amount that is different from the first amount.

In accordance with some embodiments, a computer system is described. The computer system is in communication with a display generation component and one or more input devices. The computer system comprises: means for receiving a request corresponding to a transaction for a first amount; means, in accordance with a determination that a first set of conditions is met, for displaying, via the display generation component, a first activatable user interface element corresponding to a first quantity of transactions and to the first amount; and means, in accordance with a determination that a second set of conditions is met, for displaying via the display generation component, a second activatable user interface element corresponding to a second quantity of transactions and to a second amount that is different from the first amount.

In accordance with some embodiments, a computer program product is described. The computer program product comprises one or more programs configured to be executed by one or more processors of a computer system that is in communication with a display generation component and one or more input devices, the one or more programs including instructions for: receiving a request corresponding to a transaction for a first amount; in accordance with a determination that a first set of conditions is met, displaying, via the display generation component, a first activatable user interface element corresponding to a first quantity of transactions and to the first amount; and in accordance with a determination that a second set of conditions is met, displaying via the display generation component, a second activatable user interface element corresponding to a second quantity of transactions and to a second amount that is different from the first amount.

In accordance with some embodiments, a method performed at a computer system that is in communication with a display generation component and with one or more input devices is described. The method comprises: detecting, via the one or more input devices, a first user input; in response to detecting the first user input, displaying, via the display generation component, a numeric entry user interface; while displaying the numeric entry user interface, detecting, via the one or more input devices, a second user input that includes a first set of one or more gestures; and in response to detecting a completion of the first set of one or more gestures, entering a numeric digit of a numeric sequence, the numeric digit based on a quantity of gestures in the first set of one or more gestures.

In accordance with some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system with a display generation component and with one or more input devices, the one or more programs including instructions for: detecting, via the one or more input devices, a first user input; in response to detecting the first user input, displaying, via the display generation component, a numeric entry user interface; while displaying the numeric entry user interface, detecting, via the one or more input devices, a second user input that includes a first set of one or more gestures; and in response to detecting a completion of the first set of one or more gestures, entering a numeric digit of a numeric sequence, the numeric digit based on a quantity of gestures in the first set of one or more gestures.

In accordance with some embodiments, a transitory computer-readable storage medium is described. The transitory computer readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system with a display generation component and with one or more input devices, the one or more programs including instructions for: detecting, via the one or more input devices, a first user input; in response to detecting the first user input, displaying, via the display generation component, a numeric entry user interface; while displaying the numeric entry user interface, detecting, via the one or more input devices, a second user input that includes a first set of one or more gestures; and in response to detecting a completion of the first set of one or more gestures, entering a numeric digit of a numeric sequence, the numeric digit based on a quantity of gestures in the first set of one or more gestures.

In accordance with some embodiments, a computer system that is in communication with a display generation component and one or more input devices is described. The computer system comprises: one or more processors; and memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: detecting, via the one or more input devices, a first user input; in response to detecting the first user input, displaying, via the display generation component, a numeric entry user interface; while displaying the numeric entry user interface, detecting, via the one or more input devices, a second user input that includes a first set of one or more gestures; and in response to detecting a completion of the first set of one or more gestures, entering a numeric digit of a numeric sequence, the numeric digit based on a quantity of gestures in the first set of one or more gestures.

In accordance with some embodiments, a computer system configured that is in communication with a display generation component and one or more input devices is described. The computer system comprising: means for detecting, via the one or more input devices, a first user input; means for in response to detecting the first user input, displaying, via the display generation component, a numeric entry user interface; means for while displaying the numeric entry user interface, detecting, via the one or more input devices, a second user input that includes a first set of one or more gestures; and means for in response to detecting a completion of the first set of one or more gestures, entering a numeric digit of a numeric sequence, the numeric digit based on a quantity of gestures in the first set of one or more gestures.

In accordance with some embodiments, a computer program product, comprising one or more programs configured to be executed by one or more processors of a computer system that is in communication with a display generation component one or more input devices is described. The one or more programs including instructions for: detecting, via the one or more input devices, a first user input; in response to detecting the first user input, displaying, via the display generation component, a numeric entry user interface; while displaying the numeric entry user interface, detecting, via the one or more input devices, a second user input that includes a first set of one or more gestures; and in response to detecting a completion of the first set of one or more gestures, entering a numeric digit of a numeric sequence, the numeric digit based on a quantity of gestures in the first set of one or more gestures.

In accordance with some embodiments, a method performed at a computer system is that is in communication with a display generation component and with one or more input devices is described. The method comprises: while the computer system is unlocked and while displaying, via the display generation component, a user interface of a first application, receiving, via the one or more input devices, a first input; in response to receiving the first input: displaying a first numeric keypad; in accordance with a first set of lock conditions being met, locking the computer system; and in accordance with the first set of lock conditions not being met, forgoing locking the computer system; while displaying the first numeric keypad, receiving, via the one or more input devices and using the first numeric keypad, a second input corresponding to a numeric sequence, wherein the computer system does not unlock based on the second input that uses the first numeric keypad regardless of the numeric sequence; and subsequent to receiving the second input and while the computer system is locked, receiving, via the one or more input devices, a third input that does not use the first numeric keypad; and in response to receiving the third input: in accordance with a determination, independent of the numeric sequence corresponding to the second input, that the third input matches an enrolled credential, unlocking the computer system; and in accordance with a determination, independent of the numeric sequence corresponding to the second input, that the third input does not match an enrolled credential, forgoing unlocking the computer system.

In accordance with some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system with a display generation component and with one or more input devices, the one or more programs including instructions for: while the computer system is unlocked and while displaying, via the display generation component, a user interface of a first application, receiving, via the one or more input devices, a first input; in response to receiving the first input: displaying a first numeric keypad; in accordance with a first set of lock conditions being met, locking the computer system; and in accordance with the first set of lock conditions not being met, forgoing locking the computer system; while displaying the first numeric keypad, receiving, via the one or more input devices and using the first numeric keypad, a second input corresponding to a numeric sequence, wherein the computer system does not unlock based on the second input that uses the first numeric keypad regardless of the numeric sequence; and subsequent to receiving the second input and while the computer system is locked, receiving, via the one or more input devices, a third input that does not use the first numeric keypad; and in response to receiving the third input: in accordance with a determination, independent of the numeric sequence corresponding to the second input, that the third input matches an enrolled credential, unlocking the computer system; and in accordance with a determination, independent of the numeric sequence corresponding to the second input, that the third input does not match an enrolled credential, forgoing unlocking the computer system.

In accordance with some embodiments, a transitory computer-readable storage medium is described. The transitory computer readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system with a display generation component and with one or more input devices, the one or more programs including instructions for: while the computer system is unlocked and while displaying, via the display generation component, a user interface of a first application, receiving, via the one or more input devices, a first input; in response to receiving the first input: displaying a first numeric keypad; in accordance with a first set of lock conditions being met, locking the computer system; and in accordance with the first set of lock conditions not being met, forgoing locking the computer system; while displaying the first numeric keypad, receiving, via the one or more input devices and using the first numeric keypad, a second input corresponding to a numeric sequence, wherein the computer system does not unlock based on the second input that uses the first numeric keypad regardless of the numeric sequence; and subsequent to receiving the second input and while the computer system is locked, receiving, via the one or more input devices, a third input that does not use the first numeric keypad; and in response to receiving the third input: in accordance with a determination, independent of the numeric sequence corresponding to the second input, that the third input matches an enrolled credential, unlocking the computer system; and in accordance with a determination, independent of the numeric sequence corresponding to the second input, that the third input does not match an enrolled credential, forgoing unlocking the computer system.

In accordance with some embodiments a computer system configured that is in communication with a display generation component and one or more input devices is described. The computer system comprising: one or more processors; and memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: while the computer system is unlocked and while displaying, via the display generation component, a user interface of a first application, receiving, via the one or more input devices, a first input; in response to receiving the first input: displaying a first numeric keypad; in accordance with a first set of lock conditions being met, locking the computer system; and in accordance with the first set of lock conditions not being met, forgoing locking the computer system; while displaying the first numeric keypad, receiving, via the one or more input devices and using the first numeric keypad, a second input corresponding to a numeric sequence, wherein the computer system does not unlock based on the second input that uses the first numeric keypad regardless of the numeric sequence; and subsequent to receiving the second input and while the computer system is locked, receiving, via the one or more input devices, a third input that does not use the first numeric keypad; and in response to receiving the third input: in accordance with a determination, independent of the numeric sequence corresponding to the second input, that the third input matches an enrolled credential, unlocking the computer system; and in accordance with a determination, independent of the numeric sequence corresponding to the second input, that the third input does not match an enrolled credential, forgoing unlocking the computer system.

In accordance with some embodiments a computer system that is in communication with a display generation component and one or more input devices is described. The computer system comprising: means for while the computer system is unlocked and while displaying, via the display generation component, a user interface of a first application, receiving, via the one or more input devices, a first input; means for in response to receiving the first input: means for displaying a first numeric keypad; means for in accordance with a first set of lock conditions being met, locking the computer system; and means for in accordance with the first set of lock conditions not being met, forgoing locking the computer system; means for while displaying the first numeric keypad, receiving, via the one or more input devices and using the first numeric keypad, a second input corresponding to a numeric sequence, wherein the computer system does not unlock based on the second input that uses the first numeric keypad regardless of the numeric sequence; and means for subsequent to receiving the second input and while the computer system is locked, receiving, via the one or more input devices, a third input that does not use the first numeric keypad; and means for in response to receiving the third input: means for in accordance with a determination, independent of the numeric sequence corresponding to the second input, that the third input matches an enrolled credential, unlocking the computer system; and means for in accordance with a determination, independent of the numeric sequence corresponding to the second input, that the third input does not match an enrolled credential, forgoing unlocking the computer system.

In accordance with some embodiments a computer program product comprising one or more programs configured to be executed by one or more processors of a computer system that is in communication with a display generation component one or more input devices is described. The one or more programs including instructions for: while the computer system is unlocked and while displaying, via the display generation component, a user interface of a first application, receiving, via the one or more input devices, a first input; in response to receiving the first input: displaying a first numeric keypad; in accordance with a first set of lock conditions being met, locking the computer system; and in accordance with the first set of lock conditions not being met, forgoing locking the computer system; while displaying the first numeric keypad, receiving, via the one or more input devices and using the first numeric keypad, a second input corresponding to a numeric sequence, wherein the computer system does not unlock based on the second input that uses the first numeric keypad regardless of the numeric sequence; and subsequent to receiving the second input and while the computer system is locked, receiving, via the one or more input devices, a third input that does not use the first numeric keypad; and in response to receiving the third input: in accordance with a determination, independent of the numeric sequence corresponding to the second input, that the third input matches an enrolled credential, unlocking the computer system; and in accordance with a determination, independent of the numeric sequence corresponding to the second input, that the third input does not match an enrolled credential, forgoing unlocking the computer system.

In accordance with some embodiments, a method performed at a computer system that is in communication with a display generation component and one or more input devices is described. The method comprises: receiving, via the one or more input devices, an indication that a first set of transfer obligations has been generated: receiving, via the one or more input devices, a request to display a transfer summary user interface; in response to receiving the request to display the transfer summary user interface, displaying, via the display generation component, the transfer summary user interface including a quantity of a first type of user interface elements, wherein displaying the transfer summary user interface includes: in accordance with a determination that the first set of transfer obligations includes a first quantity of transfer obligations, displaying, based on the first quantity, at least the first quantity of the first type of user interface elements; and in accordance with a determination that the first set of transfer obligations includes a second quantity of transfer obligations, displaying, based on the second quantity, at least the second quantity of the first type of user interface elements; subsequent to displaying the transfer summary user interface, receiving an indication that a respective transfer obligation in the first set of transfer obligations has been satisfied; and subsequent to receiving the indication that a respective transfer obligation in the first set of transfer obligations has been satisfied, displaying, via the display generation component and based on the indication that the respective transfer obligation in the first set of transfer obligations has been satisfied, the transfer summary user interface with one less than the quantity of the first type of user interface elements.

In accordance with some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system that is in communication with a display generation component and one or more input devices, the one or more programs including instructions for: receiving, via the one or more input devices, an indication that a first set of transfer obligations has been generated; receiving, via the one or more input devices, a request to display a transfer summary user interface; in response to receiving the request to display the transfer summary user interface, displaying, via the display generation component, the transfer summary user interface including a quantity of a first type of user interface elements, wherein displaying the transfer summary user interface includes: in accordance with a determination that the first set of transfer obligations includes a first quantity of transfer obligations, displaying, based on the first quantity, at least the first quantity of the first type of user interface elements; and in accordance with a determination that the first set of transfer obligations includes a second quantity of transfer obligations, displaying, based on the second quantity, at least the second quantity of the first type of user interface elements; subsequent to displaying the transfer summary user interface, receiving an indication that a respective transfer obligation in the first set of transfer obligations has been satisfied; and subsequent to receiving the indication that a respective transfer obligation in the first set of transfer obligations has been satisfied, displaying, via the display generation component and based on the indication that the respective transfer obligation in the first set of transfer obligations has been satisfied, the transfer summary user interface with one less than the quantity of the first type of user interface elements.

In accordance with some embodiments, a transitory computer-readable storage medium is described. The transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system that is in communication with a display generation component and one or more input devices, the one or more programs including instructions for: receiving, via the one or more input devices, an indication that a first set of transfer obligations has been generated, receiving, via the one or more input devices, a request to display a transfer summary user interface; in response to receiving the request to display the transfer summary user interface, displaying, via the display generation component, the transfer summary user interface including a quantity of a first type of user interface elements, wherein displaying the transfer summary user interface includes: in accordance with a determination that the first set of transfer obligations includes a first quantity of transfer obligations, displaying, based on the first quantity, at least the first quantity of the first type of user interface elements; and in accordance with a determination that the first set of transfer obligations includes a second quantity of transfer obligations, displaying, based on the second quantity, at least the second quantity of the first type of user interface elements; subsequent to displaying the transfer summary user interface, receiving an indication that a respective transfer obligation in the first set of transfer obligations has been satisfied; and subsequent to receiving the indication that a respective transfer obligation in the first set of transfer obligations has been satisfied, displaying, via the display generation component and based on the indication that the respective transfer obligation in the first set of transfer obligations has been satisfied, the transfer summary user interface with one less than the quantity of the first type of user interface elements.

In accordance with some embodiments, a computer system configured to communicate with a display generation component and one or more input devices is described. The computer system comprises: one or more processors; and memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: receiving, via the one or more input devices, an indication that a first set of transfer obligations has been generated; receiving, via the one or more input devices, a request to display a transfer summary user interface; in response to receiving the request to display the transfer summary user interface, displaying, via the display generation component, the transfer summary user interface including a quantity of a first type of user interface elements, wherein displaying the transfer summary user interface includes: in accordance with a determination that the first set of transfer obligations includes a first quantity of transfer obligations, displaying, based on the first quantity, at least the first quantity of the first type of user interface elements; and in accordance with a determination that the first set of transfer obligations includes a second quantity of transfer obligations, displaying, based on the second quantity, at least the second quantity of the first type of user interface elements; subsequent to displaying the transfer summary user interface, receiving an indication that a respective transfer obligation in the first set of transfer obligations has been satisfied; and subsequent to receiving the indication that a respective transfer obligation in the first set of transfer obligations has been satisfied, displaying, via the display generation component and based on the indication that the respective transfer obligation in the first set of transfer obligations has been satisfied, the transfer summary user interface with one less than the quantity of the first type of user interface elements.

In accordance with some embodiments, a computer system configured to communicate with a display generation component and one or more input devices is described. The computer system comprises: means for receiving, via the one or more input devices, an indication that a first set of transfer obligations has been generated; means for receiving, via the one or more input devices, a request to display a transfer summary user interface: means, responsive to receiving the request to display the transfer summary user interface, for displaying, via the display generation component, the transfer summary user interface including a quantity of a first type of user interface elements, wherein displaying the transfer summary user interface includes: in accordance with a determination that the first set of transfer obligations includes a first quantity of transfer obligations, displaying, based on the first quantity, at least the first quantity of the first type of user interface elements; and in accordance with a determination that the first set of transfer obligations includes a second quantity of transfer obligations, displaying, based on the second quantity, at least the second quantity of the first type of user interface elements; means, subsequent to displaying the transfer summary user interface, for receiving an indication that a respective transfer obligation in the first set of transfer obligations has been satisfied; and means, subsequent to receiving the indication that a respective transfer obligation in the first set of transfer obligations has been satisfied, for displaying, via the display generation component and based on the indication that the respective transfer obligation in the first set of transfer obligations has been satisfied, the transfer summary user interface with one less than the quantity of the first type of user interface elements.

In accordance with some embodiments, a computer program product is described. The computer program product comprises: one or more programs configured to be executed by one or more processors of a computer system that is in communication with a display generation component and one or more input devices, the one or more programs including instructions for: receiving, via the one or more input devices, an indication that a first set of transfer obligations has been generated; receiving, via the one or more input devices, a request to display a transfer summary user interface; in response to receiving the request to display the transfer summary user interface, displaying, via the display generation component, the transfer summary user interface including a quantity of a first type of user interface elements, wherein displaying the transfer summary user interface includes: in accordance with a determination that the first set of transfer obligations includes a first quantity of transfer obligations, displaying, based on the first quantity, at least the first quantity of the first type of user interface elements: and in accordance with a determination that the first set of transfer obligations includes a second quantity of transfer obligations, displaying, based on the second quantity, at least the second quantity of the first type of user interface elements; subsequent to displaying the transfer summary user interface, receiving an indication that a respective transfer obligation in the first set of transfer obligations has been satisfied; and subsequent to receiving the indication that a respective transfer obligation in the first set of transfer obligations has been satisfied, displaying, via the display generation component and based on the indication that the respective transfer obligation in the first set of transfer obligations has been satisfied, the transfer summary user interface with one less than the quantity of the first type of user interface elements.

Thus, devices are provided with faster, more efficient methods and interfaces for receiving and provisioning information on electronic devices, thereby increasing the effectiveness, efficiency, and user satisfaction with such devices. Such methods and interfaces may complement or replace other methods for receiving and provisioning information on electronic devices.

DESCRIPTION OF EMBODIMENTS

There is a need for electronic devices that provide efficient methods and interfaces for receiving and provisioning information on electronic devices. For example, there is a need to provide efficient methods and interfaces for displaying user interface elements and requesting account information. As another example, there is a need to provide efficient methods and interfaces for provisioning an account onto a computer system. As another example, there is a need to provide efficient methods and interfaces for adding funds from a gift card to an account. As another example, there is a need to provide efficient methods and interfaces for selecting a transaction type. Such techniques can reduce the cognitive burden on a user who needs to receive and provision information on electronic devices, thereby enhancing productivity. Further, such techniques can reduce processor and battery power otherwise wasted on redundant user inputs.

Below,FIGS.1A-1B,2,3,4A-4B, and5A-5Bprovide a description of exemplary devices for performing the techniques for receiving and provisioning information on electronic devices.FIGS.6A-6Eillustrate exemplary user interfaces for managing display of user interface elements based on movement of a computer system and requesting account information, in accordance with some embodiments.FIGS.7A-7Sillustrate exemplary user interfaces for managing display of user interface elements based on movement of a computer system and requesting account information, in accordance with some embodiments.FIG.8is a flow diagram illustrating a method for managing display of user interface elements based on movement of a computer system, in accordance with some embodiments.FIG.9is a flow diagram illustrating a method for requesting account information, in accordance with some embodiments. The user interfaces inFIGS.6A-6EandFIGS.7A-7Sare used to illustrate the processes described below, including the processes inFIGS.8and9.FIGS.10A-10Billustrate example user interfaces for provisioning an SSH account onto a computer system, in accordance with some embodiments.FIGS.11A-11Eillustrate exemplary user interfaces for provisioning an account onto a computer system, in accordance with some embodiments.FIG.12is a flow diagram illustrating a method for provisioning an account onto a computer system, in accordance with some embodiments. The user interfaces inFIGS.10A-10BandFIGS.11A-11Eare used to illustrate the processes described below, including the processes inFIG.12.FIGS.13A-13Billustrate exemplary user interfaces for adding data from a data plan to an account, in accordance with some embodiments.FIGS.14A-14Fillustrate exemplary user interfaces for associating a transfer amount with an account, in accordance with some embodiments.FIG.15is a flow diagram illustrating a method for associating a transfer amount with an account, in accordance with some embodiments. The user interfaces inFIGS.13A-13BandFIGS.14A-14Fare used to illustrate the processes described below, including the processes inFIG.15.FIGS.16A-16Cillustrate exemplary user interfaces for allocating memory, in accordance with some embodiments.FIGS.17A-17Qillustrate exemplary user interfaces for displaying user interface elements corresponding to transaction types, in accordance with some embodiments.FIG.18is a flow diagram illustrating a method for displaying user interface elements corresponding to transaction types, in accordance with some embodiments. The user interfaces inFIGS.16A-16CandFIGS.17A-17Qare used to illustrate the processes described below, including the processes inFIG.18.FIGS.19A-19Uillustrate exemplary user interfaces for entering a numeric sequence and locking a computer system while entering a numeric sequence, in accordance with some embodiments.FIG.20Ais a flow diagram illustrating a method for entering a number sequence, in accordance with some embodiments.FIGS.20B-20Care flow diagrams illustrating a method for locking a computer system while entering a numeric sequence, in accordance with some embodiments. The user interfaces inFIGS.19A-19Uare used to illustrate the processes described below, including the processes inFIGS.20A-20C.FIGS.21A-21Dillustrate exemplary user interfaces for managing photos on a photo server, in accordance with some embodiments.FIGS.22A-22Hillustrate exemplary user interfaces for managing one or more loans, in accordance with some embodiments.FIGS.23A-23Bare flow diagrams illustrating a method for managing information, in accordance with some embodiments. The user interfaces inFIGS.21A-21DandFIGS.22A-22Hare used to illustrate the processes described below, including the processes inFIGS.23A-23B.

The processes described below enhance the operability of the devices and make the user-device interfaces more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) through various techniques, including by providing improved visual feedback to the user, reducing the number of inputs needed to perform an operation, providing additional control options without cluttering the user interface with additional displayed controls, performing an operation when a set of conditions has been met without requiring further user input, and/or additional techniques. These techniques also reduce power usage and improve battery life of the device by enabling the user to use the device more quickly and efficiently.

Although the following description uses terms “first,” “second,” etc. to describe various elements, these elements should not be limited by the terms. In some embodiments, these terms are used to distinguish one element from another. For example, a first touch could be termed a second touch, and, similarly, a second touch could be termed a first touch, without departing from the scope of the various described embodiments. In some embodiments, the first touch and the second touch are two separate references to the same touch. In some embodiments, the first touch and the second touch are both touches, but they are not the same touch.

I/O subsystem106couples input/output peripherals on device100, such as touch screen112and other input control devices116, to peripherals interface118. I/O subsystem106optionally includes display controller156, optical sensor controller158, depth camera controller169, intensity sensor controller159, haptic feedback controller161, and one or more input controllers160for other input or control devices. The one or more input controllers160receive/send electrical signals from/to other input control devices116. The other input control devices116optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, and so forth. In some embodiments, input controller(s)160are, optionally, coupled to any (or none) of the following: a keyboard, an infrared port, a USB port, and a pointer device such as a mouse. The one or more buttons (e.g.,208,FIG.2) optionally include an up/down button for volume control of speaker111and/or microphone113. The one or more buttons optionally include a push button (e.g.,206,FIG.2). In some embodiments, the electronic device is a computer system that is in communication (e.g., via wireless communication, via wired communication) with one or more input devices. In some embodiments, the one or more input devices include a touch-sensitive surface (e.g., a trackpad, as part of a touch-sensitive display). In some embodiments, the one or more input devices include one or more camera sensors (e.g., one or more optical sensors164and/or one or more depth camera sensors175), such as for tracking a user's gestures (e.g., hand gestures and/or air gestures) as input. In some embodiments, the one or more input devices are integrated with the computer system. In some embodiments, the one or more input devices are separate from the computer system. In some embodiments, an air gesture is a gesture that is detected without the user touching an input element that is part of the device (or independently of an input element that is a part of the device) and is based on detected motion of a portion of the user's body through the air including motion of the user's body relative to an absolute reference (e.g., an angle of the user's arm relative to the ground or a distance of the user's hand relative to the ground), relative to another portion of the user's body (e.g., movement of a hand of the user relative to a shoulder of the user, movement of one hand of the user relative to another hand of the user, and/or movement of a finger of the user relative to another finger or portion of a hand of the user), and/or absolute motion of a portion of the user's body (e.g., a tap gesture that includes movement of a hand in a predetermined pose by a predetermined amount and/or speed, or a shake gesture that includes a predetermined speed or amount of rotation of a portion of the user's body).

Device100optionally also includes one or more depth camera sensors175.FIG.1Ashows a depth camera sensor coupled to depth camera controller169in I/O subsystem106. Depth camera sensor175receives data from the environment to create a three dimensional model of an object (e.g., a face) within a scene from a viewpoint (e.g., a depth camera sensor). In some embodiments, in conjunction with imaging module143(also called a camera module), depth camera sensor175is optionally used to determine a depth map of different portions of an image captured by the imaging module143. In some embodiments, a depth camera sensor is located on the front of device100so that the user's image with depth information is, optionally, obtained for video conferencing while the user views the other video conference participants on the touch screen display and to capture selfies with depth map data. In some embodiments, the depth camera sensor175is located on the back of device, or on the back and the front of the device100. In some embodiments, the position of depth camera sensor175can be changed by the user (e.g., by rotating the lens and the sensor in the device housing) so that a depth camera sensor175is used along with the touch screen display for both video conferencing and still and/or video image acquisition.

In some embodiments, a depth map (e.g., depth map image) contains information (e.g., values) that relates to the distance of objects in a scene from a viewpoint (e.g., a camera, an optical sensor, a depth camera sensor). In one embodiment of a depth map, each depth pixel defines the position in the viewpoint's Z-axis where its corresponding two-dimensional pixel is located. In some embodiments, a depth map is composed of pixels wherein each pixel is defined by a value (e.g., 0-255). For example, the “0” value represents pixels that are located at the most distant place in a “three dimensional” scene and the “255” value represents pixels that are located closest to a viewpoint (e.g., a camera, an optical sensor, a depth camera sensor) in the “three dimensional” scene. In other embodiments, a depth map represents the distance between an object in a scene and the plane of the viewpoint. In some embodiments, the depth map includes information about the relative depth of various features of an object of interest in view of the depth camera (e.g., the relative depth of eyes, nose, mouth, ears of a user's face). In some embodiments, the depth map includes information that enables the device to determine contours of the object of interest in a z direction.

Text input module134, which is, optionally, a component of graphics module132, provides soft keyboards for entering text in various applications (e.g., contacts module137, e-mail client module140, IM module141, browser module147, and any other application that needs text input).

GPS module135determines the location of the device and provides this information for use in various applications (e.g., to telephone module138for use in location-based dialing; to camera module143as picture/video metadata; and to applications that provide location-based services such as weather widgets, local yellow page widgets, and map/navigation widgets).

Each of the above-identified elements inFIG.3is, optionally, stored in one or more of the previously mentioned memory devices. Each of the above-identified modules corresponds to a set of instructions for performing a function described above. The above-identified modules or computer programs (e.g., sets of instructions or including instructions) need not be implemented as separate software programs (such as computer programs (e.g., including instructions)), procedures, or modules, and thus various subsets of these modules are, optionally, combined or otherwise rearranged in various embodiments. In some embodiments, memory370optionally stores a subset of the modules and data structures identified above. Furthermore, memory370optionally stores additional modules and data structures not described above.

As used here, the term “affordance” refers to a user-interactive graphical user interface object that is, optionally, displayed on the display screen of devices100,300, and/or500(FIGS.1A,3, and5A-5B). For example, an image (e.g., icon), a button, and text (e.g., hyperlink) each optionally constitute an affordance.

FIG.5Cillustrates exemplary devices connected via one or more communication channels to participate in a transaction in accordance with some embodiments. One or more exemplary electronic devices (e.g., devices100,300, and500) are configured to optionally detect input (e.g., a particular user input, an NFC field) and optionally transmit payment information (e.g., using NFC). The one or more electronic devices optionally include NFC hardware and are configured to be NFC-enabled.

The electronic devices (e.g., devices100,300, and500) are optionally configured to store payment account information associated with each of one or more payment accounts. Payment account information includes, for example, one or more of: a person's or company's name, a billing address, a login, a password, an account number, an expiration date, a security code, a telephone number, a bank associated with the payment account (e.g., an issuing bank), and a card network identifier. In some embodiments, payment account information includes include an image, such as a picture of a payment card (e.g., taken by the device and/or received at the device). In some embodiments, the electronic devices receive user input including at least some payment account information (e.g., receiving user-entered credit, debit, account, or gift card number and expiration date). In some embodiments, the electronic devices detect at least some payment account information from an image (e.g., of a payment card captured by a camera sensor of the device). In some embodiments, the electronic devices receive at least some payment account information from another device (e.g., another user device or a server). In some embodiments, the electronic device receives payment account information from a server associated with another service for which an account for a user or user device previously made a purchase or identified payment account data (e.g., an app for renting or selling audio and/or video files).

In some embodiments, a payment account is added to an electronic device (e.g., device100,300, and500), such that payment account information is securely stored on the electronic device. In some embodiments, after a user initiates such process, the electronic device transmits information for the payment account to a transaction-coordination server, which then communicates with a server operated by a payment network for the account (e.g., a payment server) to ensure a validity of the information. The electronic device is optionally configured to receive a script from the server that allows the electronic device to program payment information for the account onto the secure element.

In some embodiments, communication among electronic devices100,300, and500facilitates transactions (e.g., generally or specific transactions). For example, a first electronic device (e.g.,100) can serve as a provisioning or managing device, and can send notifications of new or updated payment account data (e.g., information for a new account, updated information for an existing account, and/or an alert pertaining to an existing account) to a second electronic device (e.g.,500). In another example, a first electronic device (e.g.,100) can send data to a second election device, wherein the data reflects information about payment transactions facilitated at the first electronic device. The information optionally includes one or more of: a payment amount, an account used, a time of purchase, and whether a default account was changed. The second device (e.g.,500) optionally uses such information to update a default payment account (e.g., based on a learning algorithm or explicit user input).

Electronic devices (e.g.,100,300,500) are configured to communicate with each other over any of a variety of networks. For example, the devices communicate using a Bluetooth connection558(e.g., which includes a traditional Bluetooth connection or a Bluetooth Low Energy connection) or using a WiFi network556. Communications among user devices are, optionally, conditioned to reduce the possibility of inappropriately sharing information across devices. For example, communications relating to payment information requires that the communicating devices be paired (e.g., be associated with each other via an explicit user interaction) or be associated with a same user account.

In some embodiments, an electronic device (e.g.,100,300,500) is used to communicate with a point-of-sale (POS) payment terminal550, which is optionally NFC-enabled. The communication optionally occurs using a variety of communication channels and/or technologies. In some embodiments, electronic device (e.g.,100,300,500) communicates with payment terminal550using an NFC channel560. In some embodiments, payment terminal550communicates with an electronic device (e.g.,100,300,500) using a peer-to-peer NFC mode. Electronic device (e.g.,100,300,500) is optionally configured transmit a signal to payment terminal550that includes payment information for a payment account (e.g., a default account or an account selected for the particular transaction).

In some embodiments, proceeding with a transaction includes transmitting a signal that includes payment information for an account, such as a payment account. In some embodiments, proceeding with the transaction includes reconfiguring the electronic device (e.g.,100,300,500) to respond as a contactless payment card, such as an NFC-enabled contactless payment card, and then transmitting credentials of the account via NFC, such as to payment terminal550. In some embodiments, subsequent to transmitting credentials of the account via NFC, the electronic device reconfigures to not respond as a contactless payment card (e.g., requiring authorization before again reconfigured to respond as a contactless payment card via NFC).

In some embodiments, generation of and/or transmission of the signal is controlled by a secure element in the electronic device (e.g.,100,300,500). The secure element optionally requires a particular user input prior to releasing payment information. For example, the secure element optionally requires detection that the electronic device is being worn, detection of a button press, detection of entry of a passcode, detection of a touch, detection of one or more option selections (e.g., received while interacting 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 embodiments, if a communication channel (e.g., an NFC communication channel) with another device (e.g., payment terminal550) is established within a defined time period from detection of the input, the secure element releases payment information to be transmitted to the other device (e.g., payment terminal550). In some embodiments, the secure element is a hardware component that controls release of secure information. In some embodiments, the secure element is a software component that controls release of secure information.

In some embodiments, protocols related to transaction participation depend on, for example, device types. For example, a condition for generating and/or transmitting payment information can be different for a wearable device (e.g., device500) and a phone (e.g., device100). For example, a generation and/or transmission condition for a wearable device includes detecting that a button has been pressed (e.g., after a security verification), while a corresponding condition for a phone does not require button-depression and instead requires detection of particular interaction with an application. In some embodiments, a condition for transmitting and/or releasing payment information includes receiving particular input on each of multiple devices. For example, release of payment information optionally requires detection of a fingerprint and/or passcode at the device (e.g., device100) and detection of a mechanical input (e.g., button press) on another device (e.g., device500).

Payment terminal550optionally uses the payment information to generate a signal to transmit to a payment server554to determine whether the payment is authorized. Payment server554optionally includes any device or system configured to receive payment information associated with a payment account and to determine whether a proposed purchase is authorized. In some embodiments, payment server554includes a server of an issuing bank. Payment terminal550communicates with payment server554directly or indirectly via one or more other devices or systems (e.g., a server of an acquiring bank and/or a server of a card network).

Payment server554optionally uses at least some of the payment information to identify a user account from among a database of user accounts (e.g.,552). For example, each user account includes payment information. An account is, optionally, located by locating an account with particular payment information matching that from the POS communication. In some embodiments, a payment is denied when provided payment information is not consistent (e.g., an expiration date does not correspond to a credit, debit or gift card number) or when no account includes payment information matching that from the POS communication.

In some embodiments, data for the user account further identifies one or more restrictions (e.g., credit limits); current or previous balances; previous transaction dates, locations and/or amounts; account status (e.g., active or frozen), and/or authorization instructions. In some embodiments, the payment server (e.g.,554) uses such data to determine whether to authorize a payment. For example, a payment server denies a payment when a purchase amount added to a current balance would result in exceeding an account limit, when an account is frozen, when a previous transaction amount exceeds a threshold, or when a previous transaction count or frequency exceeds a threshold.

In some embodiments, payment server554responds to POS payment terminal550with an indication as to whether a proposed purchase is authorized or denied. In some embodiments, POS payment terminal550transmits a signal to the electronic device (e.g.,100,300,500) to identify the result. For example, POS payment terminal550sends a receipt to the electronic device (e.g.,100,300,500) when a purchase is authorized (e.g., via a transaction-coordination server that manages a transaction app on the user device). In some instances, POS payment terminal550presents an output (e.g., a visual or audio output) indicative of the result. Payment can be sent to a merchant as part of the authorization process or can be subsequently sent.

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

In some embodiments, the electronic device (e.g.,100,300,500) is in a locked state or an unlocked state. In the locked state, the electronic device is powered on and operational but is prevented from performing a predefined set of operations in response to the user input. The predefined set of operations may include navigation between user interfaces, activation or deactivation of a predefined set of functions, and activation or deactivation of certain applications. The locked state may be used to prevent unintentional or unauthorized use of some functionality of the electronic device or activation or deactivation of some functions on the electronic device. In the unlocked state, the electronic device100is power on and operational and is not prevented from performing at least a portion of the predefined set of operations that cannot be performed while in the locked state.

When the device is in the locked state, the device is said to be locked. In some embodiments, the device in the locked state may respond to a limited set of user inputs, including input that corresponds to an attempt to transition the device to the unlocked state or input that corresponds to powering the device off.

In some embodiments, a secure element is a hardware component (e.g., a secure microcontroller chip) configured to securely store data or an algorithm. In some embodiments, the secure element provides (or releases) payment information (e.g., an account number and/or a transaction-specific dynamic security code). In some embodiments, the secure element provides (or releases) the payment information in response to the device receiving authorization, such as a user authentication (e.g., fingerprint authentication; passcode authentication; detecting double-press of a hardware button when the device is in an unlocked state, and optionally, while the device has been continuously on a user's wrist since the device was unlocked by providing authentication credentials to the device, where the continuous presence of the device on the user's wrist is determined by periodically checking that the device is in contact with the user's skin). For example, the device detects a fingerprint at a fingerprint sensor (e.g., a fingerprint sensor integrated into a button) of the device. The device determines whether the fingerprint is consistent with a registered fingerprint. In accordance with a determination that the fingerprint is consistent with the registered fingerprint, the secure element provides (or releases) payment information. In accordance with a determination that the fingerprint is not consistent with the registered fingerprint, the secure element forgoes providing (or releasing) payment information.

FIGS.6A-6Eillustrate example user interfaces for transferring a file, in accordance with some embodiments. The user interfaces in these figures are used to illustrate the processes described above, including the processes inFIGS.8and9.

AtFIG.6A, computer system600displays user interface601of an application for a file transfer. Computer system600detects user input650a(e.g., a tap input) which corresponds to the request to begin the file transfer. AtFIG.6B, in response to detecting user input650a, computer system600displays user interface602including space602a, which indicates where an NFC reader is located in computer system600, and user interface element602b, which indicates the file information of the file that is being transferred. AtFIG.6C, the user holding computer system600(e.g., the user transferring the file) rotates (e.g., dips the top of) computer system600down to reveal the display to another user (e.g., the user receiving the file) who is standing opposite the user holding computer system600. After (e.g., in response to) detecting the rotation of computer system600, computer system600rotates one or more elements of user interface602, as shown inFIG.6C. In some embodiments, the file transfer optionally requires account information from the user receiving the file (e.g., a user's name, a user's password, and/or how many times the user has received the file being transferred). AtFIG.6D, computer system605is tapped and/or moved near computer system600. In particular, computer system605is placed near (e.g., tapped on) space602a. This allows computer system600to request data from computer system605, including information about the account being displayed on computer system605as well as other information that computer system600may require to complete an operation. In some embodiments, the information computer system600requests (and, optionally, receives) from computer system605includes one or more of an account information (e.g., username, password, and/or the number of times a user has performed an operation). InFIG.6E, after (e.g., in response to) receiving the account information from computer system605, computer system600updates user interface602to indicate that the operation was completed successfully. Additionally, computer system600displays banner602cin user interface602to indicate that computer system600successfully account information associated with the user receiving the file.

FIGS.7A-7Sillustrate exemplary user interfaces for managing display of user interface elements based on movement of a computer system and requesting account information, in accordance with some embodiments. The devices and user interfaces in these figures are used to illustrate the processes described below, including the processes inFIGS.8and9.

FIG.7Aillustrates computer system700displaying user interface701for processing payment. User interface701includes button701aand amount701b. User interface701is displayed as part of a merchant application to perform a transaction to receive payment for goods selected by a buyer. Accordingly, after computer system700has received (e.g., via user input) indications of the goods/services being purchased by the buyer, user interface701includes the amount701bthat is due for the goods/services and button701afor starting the payment process. While displaying user interface701, computer system700detects user input701con button701a. In some embodiments, user input701cincludes a tap, swipe, and/or other gesture on a touch sensitive screen of computer system700.

In response to detecting user input701con button701acorresponding to a request for a transaction, computer system700displays user interface702as shown inFIG.7B. User interface702includes user interface element702aand request element702b. User interface702comprises particles (e.g., user interface element702a) spread over user interface702to provide an indication that computer system700is not yet ready (e.g., is performing an initialization process) to accept a payment (e.g., an NFC payment). Particles, e.g., user interface element702a, may be dispersed across user interface702. Each particle may be animated and/or colored in a way to distinguish it from other particles on the user interface. In some embodiments, particles, e.g., user interface element702a, have visual characteristics based on the orientation and/or speed of movement of computer system700. In some embodiments, while computer system700is not yet ready to accept a payment, the particles move about user interface702and are not limited to any particular area of user interface702. In some embodiments, the particles are generated randomly or pseudo-randomly. User interface element702bindicates the amount that is being requested in the current payment transaction. In some embodiments, user interface702is a user interface of a payment processor application (e.g., different from the merchant application). In some embodiments, user interface702is a user interface of an application different from the application associated with user interface701. In some embodiments, user interface701is a user interface of a merchant application (e.g., a third-party application installed on the computer system) and user interface702is a user interface of the operating system of computer system700(e.g., a first-party application provided as part of the operating system).

Once computer system700is ready to accept payments (e.g., the initialization process is complete), computer system700updates display of user interface702, as shown inFIG.7C. AtFIG.7C, because computer system700is ready to accept payments, the particles of user interface702transition to being displayed in a certain area (e.g., as indicated by space702e) of the display. This area (e.g., as indicated by space702e) may indicate where an NFC reader or other card reader (e.g., a hardware radio antenna) is located in computer system700. In this example, the particles form an outline of a rectangle to indicate where a card or NFC-enabled device should be placed in order to be read by computer system700. In some embodiments, the particles, e.g., user interface element702a, form the shape of (e.g., outline of) a rectangle at space702e(e.g., at an area of the display) to mimic the shape of a card (e.g., a credit card and/or a loyalty card) which is to be placed (e.g., tapped, brought close to) near the reader indicated by user interface element702a. In other embodiments, the particles, e.g., user interface element702a, may be displayed as a horizontal line at an edge of space702eto indicate an area from the edge of computer system700to the portion of the screen on which a card (or NFC-enabled device, or UWB-enabled device) can be positioned to be read by a reader.

AtFIG.7D, the merchant holding computer system700rotates (e.g., dips the top of) computer system700down to reveal the display to a buyer who is standing opposite the merchant. ThroughoutFIGS.7A-7S, the orientation of computer system700is indicated as shown in the respective figure. After (e.g., in response to) detecting the rotation of computer system700, computer system700rotates one or more elements of user interface702, as shown inFIG.7D. For example, rather than rotating the entire contents of the display as a single unit, or rotating user interface702as a single unit, computer system700rotates individual elements of user interface702such that the elements are rotated but displayed at their previous location. In some embodiments, a first element is rotated around the centroid of the first element and a second element is rotated around the centroid of the second element. For example, the text displayed in space702eis rotated around a centroid of space702eand/or around a centroid of the text such that the text inside of space702eis more easily read by the buyer standing opposite the merchant. Similarly, request element702bis rotated around a centroid of request element702bsuch that text inside request element702bis also more easily read by the buyer standing opposite the merchant. In some embodiments, one or more elements are not rotated (e.g., time and/or a cancellation option (e.g., “X” button).

During the processing of the current requested transaction, computer system700can detect one or more error conditions and display a user interface element in response. In accordance with a determination that the one or more error conditions includes an error of a first type, such as an error associated with the buyer, computer system700updates the display of user interface702, as shown inFIG.7E. InFIG.7E, because the error is a type of error associated with the buyer, the particles of user interface element702atransition to indicate the error and the error is oriented such that the buy can more easily read the error (e.g., is displayed in the same orientation as the text of702a). In this example, the particles fill (e.g., partially, fully, and/or more than before the error) user interface element702aand shake (e.g., side-to-side and/or left-to-right) to indicate that the transaction was not successful. Further, the text displayed at space702eis updated to include “Error Insufficient Funds” to indicate to the buyer the type of error that has occurred. In some embodiments, the particles, e.g., user interface element702a, change color from something neutral, such as black, to a color that indicates an error, such as red. In some embodiments, fewer particles fill space702ewhile computer system700is ready to perform a transaction and is not indicating an error as compared to the number of particles that appear in the same space when computer system700is indicating an error. Exemplary errors associated with the buyer include insufficient funds, a timeout condition due to incomplete account details, an incorrect type of payment being provided, and/or the payment device and/or physical payment card being placed in the incorrect location.

In accordance with a determination that the one or more error conditions includes an error of a second type, such as an error associated with the merchant, computer system700updates the display of user interface702, as shown inFIG.7F. InFIG.7F, because the error is a type of error associate with the merchant, computer system700updates user interface702to (optionally) cease display of space702eand display error element702c. Error element702cis displayed overlaid on the other elements of user interface702, including request element702b. Further, error element702cis oriented towards the merchant such that error element702cis more easily read by the merchant so that the merchant can more quickly address the error. Exemplary errors associated with the merchant include a timeout condition due to failing to detect a payment device and/or physical payment card within a threshold duration of time, a failure to communicate with the payment device and/or physical payment card, the card reader of the merchant's computer system not being enabled, and/or a lack of network connection.

In some embodiments, in response to detecting an error, computer system700includes a user interface element that provides directions to complete the transaction. For example, when the error is detecting incomplete account details during a time out period computer system700may display a user interface element or text that provides directions to try providing the complete account details again. In some embodiments, in response to detecting an error, computer system700provides an audio output indicating the error.

In some embodiments, as shown inFIG.7G, computer system700displays user interface704for requesting information associated with a payment account. In some embodiments, user interface704has been initiated/requested by a first user. User interface704includes user interface element704a, request element704b, and space704e. As described above with respect toFIGS.7C and7D, user interface704includes particles, e.g., user interface element704a, arranged in an outline of a rectangle at space704eto indicate that computer system700is ready to perform the transaction and to indicate the location of an NFC reader or other wireless card reader of computer system700. The text in space704eindicates to a second user providing an account that the second user should place (e.g., tap, bring close, make contact, and/or without making contact) a card or another computer system to the location indicated by the particles at space704eto allow computer system700to look up information (e.g., a past purchase) without performing a payment. Request element704bindicates to the second user that no funds will be requested. Accordingly, request element704bis displayed in an orientation that makes it easy to view for the second user that is providing the requested account information (e.g., while the first user is holding computer system700and dipping computer system700down). In some embodiments, request element704bis rotated (e.g., around a centroid of request element704b) to the orientation shown inFIG.7Gfrom an orientation that is opposite (e.g., rotated 180 degrees) after (e.g., in response to) detecting a rotation of computer system700to the orientation shown inFIG.7G. Further, the text at space704eis rotated around a centroid of space704e. In some embodiments, the particles, e.g., user interface element704a, may be displayed as horizontal line at an edge of space704e(e.g., without forming an outline of a rectangle) to indicate an area (from the edge of computer system700to the horizontal line) on which a card or NFC-enabled device can be positioned to be read by a reader.

InFIG.7H, continuing the payment example ofFIG.7D, computer system705is tapped and/or moved near computer system700. In particular, computer system705is placed near (e.g., tapped on) space702e, which indicates where a NFC reader or other wireless card reader is located in computer system700. This allows computer system700to request data from computer system705, including information about the credit card being displayed on computer system705as well as other information that computer system700may require to complete a transaction. In some embodiments, the information requested from computer system705is used or stored on computer system700without processing (or attempting to process) a payment transaction. In some embodiments, the information requested from computer system705is used to complete a payment transaction. In some embodiments, the information requested from computer system705includes information that is not displayed on computer system705. In some embodiments, the information computer system700requests (and, optionally, receives) from computer system705includes one or more of an account information, an expiration date, and/or a name of an account holder.

In some embodiments, computer system700encounters an error during the payment process. InFIG.7I, in response to encountering an error, computer system700ceases display of space702eand/or user interface element702aand displays error element702cas discussed above, with respect toFIG.7F.

InFIG.7J, computer system700has detected a rotation of computer system700into an orientation so that the merchant can view user interface702. After (e.g., in response to) detecting the rotation of computer system700(e.g., into the orientation depicted inFIG.7J), computer system700rotates request element702baround a centroid of request element of702b. Notably, the portion of request element702bthat is covered and/or blocked by error element702cis different after computer system700has been rotated as shown inFIG.7Jin comparison to the portion of request element702bthat is blocked inFIG.7I. Accordingly, a merchant can rotate computer system700to view error element702cand other elements of user interface702in the same orientation.

InFIG.7K, computer system705is placed near and/or tapped on computer system700and computer system700requests payment in the amount of $48.37 from computer system705. While computer system700is requesting they payment amount from computer system705, computer system700also requests data other than payment data, such as information associated with a non-payment account, loyalty account, or rewards account.

InFIG.7L, after (e.g., in response to) receiving the requested payment and loyalty information from computer system705, computer system700updates user interface702to indicate that the payment was received successfully. In particular, the particles, e.g., user interface element702a, are displayed in an arrangement (e.g., animated) that appears to be exploding out of (e.g., expanding outward from) the previously displayed rectangle inFIG.7Hto indicate that the transaction was successful. In some embodiments, the particles move independent of other particles. In some embodiments, the particles, e.g., user interface element702a, bounce and/or rebound off of the edges of the display of computer system700. In some embodiments, the paths of the particles, user interface element702a, are not restricted within the display of computer system700. In some embodiments, the particles may change color from something neutral (e.g., black) to a color that indicates success such as green. In some embodiments, computer system700provides an audio output in addition to the displayed user interface elements to indicate that the transaction was successful. Request element702bis updated to include the text “funds received” indicating that the transaction was successful. Additionally, computer system displays banner702din user interface702to indicate that computer system700also successfully retrieved loyalty information associated with the buyer. Banner702dis displayed in an orientation towards the merchant holding computer system700to advise the merchant that the loyalty information was received (e.g., when loyalty information was not initially requested but was determined to be available on computer system705). In some embodiments, banner702dis displayed in an orientation consistent with request element702bsuch that the buyer is able to more easily read banner702d.

In some embodiments, in accordance with a determination that a loyalty account associated with the merchant is available on computer system705, computer system700also requests from computer system705information associated with a payment account. In some embodiments, in accordance with a determination that the transaction request is a request for loyalty account information and computer system705provides loyalty account information, computer system700forgoes displaying banner702dand/or another indication that loyalty account information is received. In some embodiments, in accordance with a determination that the transaction request is a request for loyalty account information and computer system705provides payment account information, computer system700displays an error indication (e.g., an error interface element) and does not provide the payment account information to an application associated with the merchant.

In some embodiments, computer system700requests loyalty account information and (e.g., while receiving the loyalty account information) receives payment account information and, in response, computer system700forgoes displaying banner702dor any other indication that loyalty account information was received.

InFIG.7M, as a first user (e.g., holding computer system700) is dipping computer system700down for a second user to view, computer system700displays user interface706requesting loyalty information from the second user. Computer system700displays space706eand request element706bin an orientation towards the second user such that the text at space706eand request element706bis more easily read by the second user. In some embodiments, computer system700rotates the text at space706earound a centroid of space706e(and/or the centroid of the text) and rotates request element706baround a centroid of request element706bafter (e.g., in response to) detecting rotation of (e.g., dipping down of) computer system700to the shown orientation. In response to detecting that the user places loyalty card707in a field of a short-range radio of computer system700(e.g., positioned near/under/adjacent to space706eof user interface706), computer system700receives loyalty information associated with the user from loyalty card707(e.g., via an NFC or UWB transaction).

InFIG.7N, after (e.g., in response to) successfully receiving the loyalty information from loyalty card707, computer system700updates user interface706. Computer system700updates the particles, e.g., user interface element706a, of user interface706such that the particles appear to be exploding out of (e.g., animated, expanding away from) the previously displayed (e.g., outline of) rectangle of space706e. In some embodiments, the particles, e.g., user interface element706a, optionally change color (e.g., from black to green). In some embodiments, computer system700provides an audio and/or tactile output in addition to the displayed user interface elements to indicate that the transaction was successful.

InFIG.7O, computer system700displays user interface708for opening a tab (e.g., a bar tab such that multiple items are added throughout an evening before the tab is settled). Computer system700displays text at space708eand request element708bin an orientation towards the buyer (e.g., the person for whom the tab is to be opened), such that the text at space708eand request element708bare more easily read by the buyer. In some embodiments, computer system700rotates the text at space708earound a centroid of space708e(and/or the centroid of the text) and rotates request element708baround a centroid of request element708bafter (e.g., in response to) detecting rotation of computer system700to the shown orientation. In response to detecting that the user places computer system705in a field of a short-range radio of computer system700(e.g., positioned near/under/adjacent to space708eof user interface708), computer system700receives payment account information associated with the buyer without completing a payment transaction. Computer system700receives information associated with credit card705adisplayed on computer system705, including a credit card number, the buyer's name, the credit card expiration date, and/or other information needed to open a tab for the buyer and/or charge the buyer's account at a later time (e.g., when the tab is settled at the end of the evening).

InFIG.7P, after (e.g., in response to) computer system700receiving the requested information required to open a tab for Jane, computer system700opens the tab and updates user interface708to indicate that the transaction was a success. Computer system700updates the particles, e.g., user interface element708a, such that the particles appear to be exploding out of (e.g., animated, expanding away from) the previously displayed rectangle. In some embodiments, the particles, e.g., user interface element708a, optionally change color (e.g., from black to green). In some embodiments, computer system700provides an audio and/or tactile output in addition to the displayed user interface elements to indicate that the transaction was successful.

InFIG.7Q, computer system700displays user interface709for provisioning a card (e.g., a payment account, a loyalty account, a key account, and/or an identification account) onto computer system700.

InFIG.7R, the user places credit card710in a field of a short-range radio of computer system700(e.g., positioned near/under/adjacent to space709eof user interface709). After (e.g., in response to) detecting that credit card710, computer system700receives account information associated with credit card710. Computer system700receives information associated with credit card710including a credit card number, the account holder's name, the credit card expiration date, and/or other information needed to provision credit card710onto computer system700.

InFIG.7S, after receiving information associated with credit card710, computer system700provisions credit card710onto computer system700and updates user interface709to indicate that the provisioning was a success. Computer system700updates the particles, e.g., user interface element709a, such that the particles appear to be exploding out of (e.g., animated, expanding away from) the previously displayed rectangle. In some embodiments, the particles optionally change color (e.g., from black to green). In some embodiments, computer system700provides an audio and/or tactile output in addition to the displayed user interface elements to indicate that the transaction was successful. Computer system700also updates request element709bto include text indicating that the card was provisioned and updates the text of user interface element709ato indicate that payments (e.g., NFC and/or UWB payments) can be made with computer system700using the newly provisioned account.

In some embodiments, computer system700receives a request to display information associated with an account (e.g., a payment account and/or a non-payment account), including prior transactions or other information that indicates a history of the account. Accordingly, in addition to requesting loyalty information, opening a tab, and/or provisioning a card, as discussed above, the user interface can also display a request for account information which can be used to access other information associated with the account, such as historical or prior transaction data. For example, computer system700can receive information about a payment account and (without processing a payment), displaying past purchases made using the payment account. As a result, the merchant can quickly and efficiently find past transaction information for a buyer.

FIG.8is a flow diagram illustrating a method for displaying user interface elements and requesting account information using a computer system in accordance with some embodiments. Method800is performed at a computer system (e.g.,100,300,500,700,1100,1400,1700) that is in communication with a display generation component (e.g., a display controller and/or a touch-sensitive display system) and one or more input devices (e.g., a button, a rotatable input mechanism, a speaker, a camera, a motion detector (e.g., an accelerometer and/or gyroscope), and/or a touch-sensitive surface). Some operations in method800are, optionally, combined, the orders of some operations are, optionally, changed, and some operations are, optionally, omitted.

As described below, method800provides an intuitive way for managing display of user interface elements based on movement of a computer system. The method reduces the cognitive burden on a user for viewing user interface elements on the computer system, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to display user interface elements and request account information using a computer system faster and more efficiently conserves power and increases the time between battery charges.

The computer system (e.g.,700) (e.g., a smartwatch, a wearable electronic device, a smartphone, a desktop computer, a laptop, or a tablet) detects (802), via one or more input devices, user input (e.g.,701c) to initiate a transaction request (e.g., a request for payment).

In response (804) to detecting the user input (e.g.,701c) to initiate the transaction request, the computer system (e.g.,700) displays (e.g., while the computer system is in a first position), via the display generation component, a transaction user interface (e.g.,702) (e.g., a payment user interface). Displaying the transaction user interface (e.g.,702) includes displaying: at a first location, via the display generation component, a first graphical user interface element (e.g.,702ainFIG.7C) (806) (e.g., an arrow, text box, and/or a plurality of particles) indicating a location of a reader (e.g., a barcode reader, a credit card reader, and/or a camera) of the computer system (e.g.,700), and at a second location different from the first location, via the display generation component, a second graphical user interface element (e.g.,702batFIG.7C) (808) (e.g., an indication of an amount of the transaction and/or an indication of the state of the computer system), wherein the second graphical user interface element is displayed in a first orientation (e.g., towards the user (the retailer) of the computer system).

While displaying the transaction user interface (e.g.,702atFIGS.7C-7D), the computer system detects (810) a movement (e.g., a rotation, a change in orientation, a tilt, and/or a lifting) of the computer system (e.g.,700) (e.g., to a second position).

In response to detecting the movement of the computer system, the computer system rotates (812) (e.g., via a rotation animation and/or a cross-fade animation) the second graphical user interface element (e.g.,702batFIG.7D) (e.g., the indication of an amount of the transaction and/or the indication of the state of the computer system) around a centroid of the second graphical user interface element to a second orientation different from the first orientation, while continuing to display, at the first location, the first graphical user interface element (e.g.,702aatFIG.7D) indicating the location of the reader of the computer system.

Automatically rotating some user interface elements based on movement of the computer system enables users of the computer system to read content on the display without requiring the user to provide additional input to rotate those elements (such that they are properly oriented), thereby reducing the number of inputs needed to perform the operation.

In some embodiments, multiple graphical user interface elements rotate about their respective centroids in response to detecting movement of the computer system. In some embodiments, the first graphical user interface is an animated visual element. In some embodiments, the first graphical user interface does not rotate based on and/or is not affected by the detected movement of the computer system. In some embodiments, the first graphical user interface rotates in response to the movement of the computer system and is displayed (after rotation) at the first location (e.g., continues to be displayed at the same location, though rotated).

In some embodiments, prior to detecting the movement of the computer system, the computer system displays, via the display generation component, a third graphical user interface element in the first orientation. In some embodiments, in response to detecting the movement of the computer system, the computer system rotates (e.g., via a rotation animation and/or a cross-fade animation) the third graphical user interface element (e.g., the indication of an amount of the transaction and/or the indication of the state of the computer system) around a centroid of the third graphical user interface element to the second orientation. Automatically rotating some user interface elements based on movement of the computer system enables users of the computer system to read content on the display without requiring the user to provide additional input to rotate those elements (such that they are properly oriented), thereby reducing the number of inputs needed to perform the operation.

In some embodiments, while the second graphical user interface element is displayed in the second orientation, the computer system detects an error condition. In some embodiments, in response to detecting the error condition: in accordance with a determination that the error condition is a first type of error (e.g., an error directed to the user that initiated the transaction request, an error directed to a merchant (rather than a customer), and/or an error for an individual positioned at a first side of the computer system), the computer system displays, via the display generation component, an indication (e.g., error of text of the error condition in a third orientation (e.g., same as the first orientation and/or different from the second orientation, towards the user that initiated the transaction request, towards the merchant, towards the first side of the computer system) and in accordance with a determination that the error condition is a second type of error (e.g., an error directed to a user that did not initiate the transaction request, an error directed to a customer (rather than merchant), and/or an error for an individual positioned at a second side (different from the first side and/or opposite the first side) of the computer system), the computer system displays, via the display generation component, an indication of the error condition in a fourth orientation (e.g., same as the second orientation and/or different from the first orientation, towards a user that did not initiate the transaction request, towards the customer, towards the second side of the computer system) that is different from the third orientation. Displaying notifications of error conditions oriented differently based on whether the error condition is directed to one user (e.g., a merchant) or another user (e.g., a purchaser) enables users of the computer system to read content on the display without requiring the user to provide additional input to rotate those elements (such that they are properly oriented), thereby reducing the number of inputs needed to perform the operation.

In some embodiments, the error condition is a timeout (e.g.,702catFIG.7F). In some embodiments, the timeout is based on a failure to communicate with a payment terminal and/or payment server to process information (e.g., a payment transaction, a lookup of prior purchases). In some embodiments, the timeout is based on a failure to communicate with a payment device (e.g., a phone (such as an NFC-enabled phone that is armed for payment) and/or a physical payment card (such as a credit card). In some embodiments, communicating includes communicating via short-range radio to read account information (e.g., account number, account expiration date, and/or user account name) of the corresponding account.

In some embodiments, the third orientation is different from the second orientation (e.g.,FIG.7Evs7F).

In some embodiments, the second graphical user interface element (e.g., payment information, transaction amount, a text box, a request for information, a notification, and/or a banner) of the transaction user interface is oriented based on a position of the computer system to increase recognizability (e.g., legibility and/or readability) of the second graphical user interface element for an expected user of the computer system. Orienting displayed user interface elements to increase recognizability of the user interface elements enables users of the computer system to better read content on the display without requiring the user to provide additional input to rotate those elements (such that they are properly oriented), thereby reducing the number of inputs needed to perform the operation.

In some embodiments, detecting user input to initiate the transaction request includes detecting (e.g., via a touch-sensitive surface) activation of (e.g., a tap at a location corresponding to) a displayed request-transaction graphical user interface element (e.g.,701a). In some embodiments, the transaction user interface includes (e.g., in response to and/or after detecting the user input to initiate the transaction) a display of the graphical user interface element (e.g.,702e) indicating the location of the reader (e.g., a sensor, such as a short-range communication component and/or NFC reader) of the computer system for processing the transaction).

In some embodiments, the transaction user interface (e.g.,702) is a user interface of a first application (e.g., a payment application) and the request-transaction graphical user interface element is displayed as part of a user interface of a second application (e.g.,701) (e.g., a payment processor application and/or a retailer application) that is different from the first application. In some embodiments, the first application is an operating system of the computer system (and the second application is not). Using separate applications to initiate the transaction request and to performing the transaction increases security by relying on a secure and/or known application (e.g., an application that is part of the operating system of the computer system) to perform portions of the technique that require higher levels of security.

In some embodiments, the transaction request includes a payment request (e.g., a payment transaction, a receipt of funds (such as a purchase) and/or a refund of funds (such as a return of a purchase)), a loyalty request (e.g., a loyalty transaction that does not include a payment of money), and/or a request to identify prior transactions (e.g., using received account information, such as an account number and/or expiration date (without performing a payment or loyalty transaction)). Initiating a transaction that includes a payment request, a loyalty request, and/or a request to identify prior transactions enables the computer system to receive information required to perform the transaction with requiring the additional user input, thereby reducing the number inputs needed to perform the operation(s).

In some embodiments, the transaction user interface (e.g., prior to and/or while the second graphical user interface element of the transaction user interface is displayed in the second orientation) identifies a type of transaction (e.g., indicates “tap to pay”, “tap to refund”, and/or “tap to collect information” to identify prior transactions). In some embodiments, the request is a request for a payment transaction (e.g., a receipt of funds (such as a purchase) and/or a refund of funds (such as a return of a purchase)). In some embodiments, the request is a request for a loyalty request (e.g., a loyalty transaction that does not include a payment of money). In some embodiments, the request is a request to identify prior transactions (e.g., using received account information, such as an account number and/or expiration date (without performing a payment or loyalty transaction)).

In some embodiments, while displaying the transaction user interface, the computer system detects, via a short-range communication radio (e.g., NFC and/or UWB), account details (e.g., account information, such as account number, account expiration date, name associated with the account) (e.g., as inFIG.7K). In some embodiments, in response to detecting account details and in accordance with a determination that the account details are valid (e.g., the account number is a valid number, the account is not expired, and/or a name associated with the account is available), the computer system transfers one or more (e.g., all or less than all) of the account details to a retailer application (e.g., not a first-party application of the computer system) of the computer system (e.g., without processing the transaction and/or without displaying an error). In some embodiments, the computer system collects account information using a first application (e.g., an operating system and/or an application provided by the manufacturer of the computer system) and passes some or all of the account information to a second application that is different from the first application (e.g., a third-party application). Transferring account details to a retailer application enables the retailer application to use the account details while a separate application (e.g., a more secure application) is responsible for collecting the account details, thereby increasing the security of the computer system.

In some embodiments, in response to detecting account details and in accordance with a determination that the account details are not valid (e.g., the account number is not a valid number, the account is expired, and/or a name associated with the account is not available), the computer system displays (e.g., in the second orientation), via the display generation component, an indication of an error (e.g., as inFIG.7J) (e.g., without transferring one or more (e.g., all or less than all) of the account details to a retailer application (e.g., not a first-party application of the computer system) of the computer system (e.g., without processing the transaction)). Displaying an indication of the error provides the user with visual feedback about the error state of the computer system, thereby providing improved visual feedback to the user.

In some embodiments, detecting account details includes reading (e.g., as inFIG.7M) account details from a physical card (e.g.,707) (e.g., a credit card, a loyalty card, and/or a card that is NFC-enabled). Detecting account details from either a physical card and/or an external computer system without requiring the user to select the source (e.g., physical card or external computer system) of the account details reduces the inputs required to perform the transaction, thereby reducing the number of inputs needed to perform an operation.

In some embodiments, detecting account details includes reading account details from an external computer system (e.g.,705) (e.g., a smartphone that is NFC-enabled). Detecting account details from either a physical card and/or an external computer system without requiring the user to select the source (e.g., physical card or external computer system) of the account details reduces the inputs required to perform the transaction, thereby reducing the number of inputs needed to perform an operation.

In some embodiments, subsequent to transferring one or more (e.g., all or less than all) of the account details to the retailer application (e.g., the second application and/or not a first-party application of the computer system) of the computer system, the computer system processes the transaction (e.g., as inFIG.7N) (e.g., using the retailer application and/or the second application). In some embodiments, the transaction user interface is a user interface of first-party application (e.g., an operating system) and the account details are passed to a different application (e.g., a third-party application and/or a retailer application) to process the transaction. In some embodiments, the transaction user interface is a user interface of first-party application (e.g., an operating system) and the first-party application uses the account details to process the transaction.

In some embodiments, while the second graphical user interface element of the transaction user interface is displayed in the second orientation, the computer system receives input (e.g., movement of the computer system, detecting a change in orientation of the computer system back to facing the merchant, and/or detecting user input on a touch-sensitive surface/display). In some embodiments, in response to receiving the input, the computer system rotates the second graphical user interface element (e.g., payment information, transaction amount, a text box, a request for information, a notification, and/or a banner) of the transaction user interface to the first orientation (e.g., while maintaining in the first orientation the graphical user interface element (e.g.,702e) indicating the location of the reader of the computer system). In some embodiments, the input cases the graphical user interface element to be displayed as it was (e.g., in the first orientation) before the movement of the computer system was detected, thereby allowing the original user of the computer system (e.g., the merchant) to more easily read the elements of the user interface. Rotating a user interface element in response to user input enables the computer system to orient the user interface element to make the user interface element more readily recognizable to the viewer based on the location of the viewer with respect to the computer system, thereby providing improved visual feedback to the user.

In some embodiments, receiving the input includes detecting movement of the computer system (e.g., transition betweenFIGS.7I and7J) (e.g., detecting that the computer system's display is tilted back towards the initial user, such as the merchant). Rotating a user interface element in response to movement of the computer system enables the computer system to orient the user interface element to make the user interface element more readily recognizable to the viewer based on the location of the viewer with respect to the computer system, thereby providing improved visual feedback to the user.

In some embodiments, receiving the input includes detecting activation of a displayed graphical user element (e.g., detecting that a cancel button has been pressed). Rotating a user interface element in response to activation of a displayed graphical user element enables the computer system to orient the user interface element to make the user interface element more readily recognizable to the viewer based on the location of the viewer with respect to the computer system, thereby providing improved visual feedback to the user.

In some embodiments, while the second graphical user interface element of the transaction user interface is displayed in the second orientation, the computer system detects, during a timeout period (e.g., 4 seconds or 8 seconds), incomplete account details (e.g., account information) (e.g., detecting an account number without detecting an expiration date and/or detecting an initiation of communication to receive account information without receiving complete account information). In some embodiments, in response to detecting the incomplete account details during the timeout period, the computer system extends the timeout period and displays, via the display generation component, directions to complete the transaction (e.g., “tap your device and hold until confirmation (tone/haptic) is received” or “tap your card again”). Automatically extending the timeout period when incomplete account details are detected performs an operation when a set of conditions has been met without requiring further user input.

In some embodiments, the computer system detects (e.g., while displaying the transaction user interface with the second graphical user interface element in the second orientation) (e.g., via a short-range communication radio (e.g., NFC and/or UWB) or via a camera of the computer system) account details (e.g., account information, such as account number, account expiration date, name associated with the account). In some embodiments, in accordance with a determination that the transaction has been processed (e.g., account details are valid and process is complete) (and, optionally, in response to detecting account details), the computer system provides a first audio output indicating a successful transaction. In some embodiments, in accordance with a determination that an error is detected (such as an error condition) (and, optionally, that the transaction has not been processed) (and, optionally, in response to detecting account details), providing a second audio output, different from the first audio output, indicating an error. Providing audio output based on a successful transaction or an error enables the computer system to provide the user with the state of the computer system, thereby providing improved audio feedback to the user.

In some embodiments, the transaction request is a request to provision an account onto the computer system and the computer system detects (e.g., while displaying the transaction user interface with the second graphical user interface element in the second orientation), via a short-range communication radio (e.g., NFC and/or UWB), account details (e.g., account number, account expiration date, name associated with the account) (e.g., as inFIG.7S). In some embodiments, subsequent to (e.g., in response to) detecting account details (and, optionally, in accordance with a determination that the account details were received from a physical card (e.g., a debit card, a bank card, and/or a credit card) and not a computer system (e.g., a smart phone or a laptop)), provisioning an account onto the computer system using some (e.g., all or less than all) of the account details. In some embodiments, subsequent to (e.g., in response to) detecting account details and in accordance with a determination that the account details were not received from a physical card, forgoing provisioning the account onto the computer system.

In some embodiments, the computer system detects (e.g., while displaying the transaction user interface with the second graphical user interface element in the second orientation) (e.g., receiving from the user device, via a short-range communication radio (e.g., NFC and/or UWB) or via a camera of the computer system) account details (e.g., account number, account expiration date, name associated with the account). In some embodiments, the computer system performs an operation using some (e.g., all of, not all of) of the account details without attempting to transfer funds (e.g., without processing a payment).

In some embodiments, the operation is a transaction lookup operation that uses some of the account details to identify (and, optionally, display details of) a previously performed transaction.

In some embodiments, the operation adds an amount (and/or an item or service for purchase) to a tab (e.g., a running total of charges that an individual or group accumulates for subsequent settlement, such as a bar tab) associated with (e.g., identified using) some of the account details.

In some embodiments, the graphical user interface element (e.g., space702e) indicating the location of the reader (e.g., a sensor, such as a short-range communication component and/or NFC reader) comprises displayed particles (e.g., a plurality of particles being emitted from one or more particle emitter locations and/or moving on the display) that have visual characteristics (e.g., speed of movement, location of particles) based on orientation and/or speed of movement of the computer system. In some embodiments, the particles move on the display based on the movement (e.g., rotation, dipping, raising, and/or lowering) of the computer system.

In some embodiments, in the graphical user interface element (e.g., space702e) indicating the location of the reader (e.g., a sensor, such as a short-range communication component and/or NFC reader) comprises displayed particles (e.g., a plurality of particles being emitted from one or more particle emitter locations and/or moving on the display) and wherein, subsequent to detecting the user input to initiate the transaction request and prior to the computer system being ready to receive account details (e.g., account information, such as account number, account expiration date, name associated with the account), the displayed particles have a first visual characteristic (e.g.,702ainFIG.7B) (e.g., are scattered, do not form a discernable shape, are not limited to a first area of the display, and/or are a first color, such as white or yellow). Displaying particles with a first visual characteristics provides the user with visual feedback of the state of the computer system (not yet ready to receive account details), thereby providing improved visual feedback to the user.

In some embodiments, subsequent to the computer system being ready to receive account details and prior to receiving the account details (e.g., account information, such as account number, account expiration date, name associated with the account), the displayed particles have a second visual characteristic (e.g.,702ainFIG.7C) (e.g., are limited to the first area of the display, form a discernable shape or outline of a shape such as a rectangle, square, or circle, and/or are a second color, such as blue or purple) different from the first visual characteristic. In some embodiments, once the computer system is ready to receive account details the particles animate to transition from having the first visual characteristic to having the second visual characteristic. Displaying particles with a second visual characteristics provides the user with visual feedback of the state of the computer system (ready to receive account details), thereby providing improved visual feedback to the user.

In some embodiments, in accordance with a determination that an error condition is detected, the computer system displays, via the display generation component, the particles with a third visual characteristic (e.g.,702ainFIG.7E) (e.g., are limited to the first area of the display, fill in the discernable shape such as the rectangle, square, or circle, and/or are a third color, such as red or orange) that is different from the first visual characteristic and the second visual characteristic. In some embodiments, once the computer system is detects the error condition, the particles animate to transition from having the first or second visual characteristic to having the third visual characteristic. In some embodiments, in accordance with a determination that the error condition exists, the computer system displays the particles with the third visual characteristic, provides a tactile output, and/or provides an audio output (to indicate an error). Displaying particles with a third visual characteristics provides the user with visual feedback of the state of the computer system (error detected), thereby providing improved visual feedback to the user.

In some embodiments, in accordance with a determination that account details are successfully detected (e.g., successfully receiving from the user device, via a short-range communication radio (e.g., NFC and/or UWB) or via a camera of the computer system), the computer system displays, via the display generation component, the particles with a fourth visual characteristic (e.g.,702ainFIG.7L) (e.g., particles move away from each other (such as extending beyond the first area of the display) and/or are a fourth color, such as green or gray) that is different from the first visual characteristic, the second visual characteristic, and the third visual characteristic. In some embodiments, once the computer system detects that account details are successfully received, the particles animate to transition from having the first or second visual characteristic to having the fourth visual characteristic (e.g., the particles transition from forming a rectangular outline to moving away from each other, such as to appear like they are exploding away from each other (e.g., animated)). In some embodiments, in accordance with a determination that the error condition exists, the computer system displays the particles with the fourth visual characteristic, provides a tactile output, and/or provides an audio output (to indicate that account details are successfully detected). Displaying particles with a first visual characteristics provides the user with visual feedback of the state of the computer system (account details successfully received), thereby providing improved visual feedback to the user.

Note that details of the processes described above with respect to method800(e.g.,FIG.8) are also applicable in an analogous manner to the methods described below/above. For example, method900optionally includes one or more of the characteristics of the various methods described above with reference to method800. For example, method900may request information as discussed above with reference to method800. As another example, method1200optionally includes one or more of the characteristics of the various methods described above with reference to method800. For example, method1200may provision an account using user interfaces discussed above with reference to method800. As another example, method1500optionally includes one or more of the characteristics of the various methods described above with reference to method800. For example, method1500may receive gift card information through the process discussed above with reference to method800. For example, method1800optionally includes one or more of the characteristics of the various methods described above with reference to method800. For example, method1800may receive payment accounts as discussed above with reference to method800. For brevity, these details are not repeated below. For example, method2000optionally includes one or more various methods described above with reference to method800. For example, during numeric sequence entry computer system1900optionally rotates one of user interface elements in response to detecting movement of computer system1900as described in method800. As another example, method800optionally includes one or more of the various methods described below with reference to method2010. For example, during numeric sequence entry computer system1900optionally rotates one of user interface elements in response to detecting movement of computer system1900as described in method800. As another example, method800optionally includes one or more various methods described below with reference to method2300. For example, a quantity of a first type of user interface elements as described in method2300may rotate in response to detecting movement of the computer system.

FIG.9is a flow diagram illustrating a method for requesting account information using a computer system, in accordance with some embodiments. Method900is performed at a computer system (e.g.,100,300,500,700,1100,1400,1700) that is in communication with a display generation component (e.g., a display controller and/or a touch-sensitive display system) and one or more input devices (e.g., a button, a rotatable input mechanism, a speaker, a camera, a motion detector (e.g., an accelerometer and/or gyroscope), and/or a touch-sensitive surface). Some operations in method800are, optionally, combined, the orders of some operations are, optionally, changed, and some operations are, optionally, omitted.

As described below, method900provides an intuitive way for requesting account information using a computer system. The method reduces the cognitive burden on a user for requesting account information using a computer system, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to display user interface elements and request account information using a computer system faster and more efficiently conserves power and increases the time between battery charges.

The computer system (e.g.,700) (e.g., a smartwatch, a wearable electronic device, a smartphone, a desktop computer, a laptop, or a tablet) detects (902), via one or more input devices, user input (e.g.,701c) to initiate a transaction request (e.g., a request for a loyalty account or for payment).

The computer system (e.g.,700) communicates (904) (e.g., direct and/or via NFC) with a user device (e.g.,705) (e.g., a user smartphone, smartwatch, and/or wearable electronic device).

In accordance with a determination (e.g., via communication (e.g., direct and/or NFC) with a user device) that an account (e.g., a payment account, a loyalty account, a memory account) associated with a provider (e.g., the store, a store associated with the request for payment) of the transaction request is available on the user device (e.g.,705), the computer system requests (906), from the user device, the account associated with the provider of the transaction request.

In accordance with a determination that the account associated with the provider of the transaction request is not available on the user device, the computer system forgoes requesting (908), from the user device, the account associated with the provider of the transaction request. In some embodiments, displaying a banner corresponding to the account associated with the provider of the transaction request when requesting the account. In some embodiments, also requesting payment information (e.g., account). In some embodiments, displaying the banner over a user interface for the payment request. In some embodiments, information corresponding to the account is stored on the computer system (e.g., a user is asking another user for the information (e.g., sharing a loyalty account with another user, starting a tab)). In some embodiments, requesting an account from an external device includes requesting information (e.g., an account number, an expiration date, and/or a name associated with the account) about the account.

Enabling the computer system to access accounts on the user device (e.g., reading the accounts, such as cards (e.g., payment cards), available in an electronic wallet of the user device) to request a specific account when it is available on the user device reduces the need for the user to provide additional inputs at the computer system to specify which account to request, thereby reducing the number of user inputs required to perform an operation.

In some embodiments, the transaction request is for a first type of account (e.g., a payment account, a) and the account associated with the provider of the transaction request is of a second type of account (e.g., a loyalty account) that is different from the first type of account. Enabling the computer system to request a different type of account than the user initially initiated the transaction for reduces the need for the user to provide additional inputs at the computer system to specify which account to request, thereby reducing the number of user inputs required to perform an operation.

In some embodiments, in accordance with a determination that the account associated with the provider of the transaction request is not available on the user device (e.g., the user device is not provisioned with a loyalty account particular to the provider of the transaction request, such as a merchant), the computer system requests, from the user device, the first type of account (e.g., requesting a payment account). Enabling the computer system to access accounts on the user device (e.g., reading the accounts, such as cards (e.g., payment cards), available in an electronic wallet of the user device) to request a specific account when it is available (and not request it when it is not available) on the user device reduces the need for the user to provide additional inputs at the computer system to specify which account to request, thereby reducing the number of user inputs required to perform an operation.

In some embodiments, in accordance with a determination that an account (e.g., a payment account, a loyalty account, a memory account) associated with the provider (e.g., the store, a store associated with the request for payment) of the transaction request is available on the user device, the computer system requests, from the user device, the first type of account (in addition to the account associated with the provider of the transaction request). In some embodiments, the computer system determines (e.g., based on communication with the user device) that the user device has an account that is associated with the provider of the transaction request and, as a result, the computer system requests (from the user device) information (e.g., account number, expiration dates, and/or name associated with account) about both accounts (e.g., a loyalty account and a payment account). Enabling the computer system to access accounts on the user device (e.g., reading the accounts, such as cards (e.g., payment cards), available in an electronic wallet of the user device) to request a specific account when it is available (and not request it when it is not available) on the user device reduces the need for the user to provide additional inputs at the computer system to specify which account to request, thereby reducing the number of user inputs required to perform an operation.

In some embodiments, in accordance with a determination that the transaction request is a request for non-loyalty account information (e.g., that the user of the computer system has selection an option for requesting account information from the user device that is not loyalty information, such as in a retail application) and that the user device provides (e.g., in response to a request from the computer system) loyalty account information, the computer system displays (e.g., via a banner the is displayed at the top of the display), via the display generation component, an indication (e.g.,702d) that loyalty account information was received. Providing visual feedback about the account information that was received indicates the state of the computer system to the user, thereby providing the user with improved visual feedback.

In some embodiments, in accordance with a determination that the transaction request is a request for loyalty account information (e.g., that the user of the computer system has selection an option for requesting loyalty account information from the user device, such as in a retail application) and that the user device provides (e.g., in response to a request from the computer system) loyalty account information, the computer system forgoes displaying an indication that loyalty account information was received.

In some embodiments, in accordance with a determination that the transaction request is a request for non-loyalty account information (e.g., that the user of the computer system has selection an option for requesting account information from the user device that is not loyalty information, such as in a retail application) and that the user device provides (e.g., in response to a request from the computer system) both loyalty account information and non-loyalty account information (e.g., payment information), the computer system displays, via the display generation component, an indication (e.g.,702d) (e.g., via a banner the is displayed at the top of the display) that loyalty account information was received. Providing visual feedback about the account information that was received indicates the state of the computer system to the user, thereby providing the user with improved visual feedback.

In some embodiments, in accordance with a determination that the transaction request is a request for loyalty account information (e.g., that the user of the computer system has selection an option for requesting loyalty account information from the user device, such as in a retail application) and that the user device provides (e.g., in response to a request from the computer system) non-loyalty account information (e.g., payment information) the computer system displays, via the display generation component, an error indication (e.g., based on an error condition) without transferring one or more (e.g., all or less than all) account details (e.g., account information, such as an account number, an account expiration date, and/or a name associated with the account) of the non-loyalty account information to a retailer application (e.g., an application that initiated the request, a second application, and/or not a first-party application of the computer system) of the computer system. Providing visual feedback about an error that was encountered indicates the state of the computer system to the user, thereby providing the user with improved visual feedback.

In some embodiments, in accordance with a determination that the transaction request is a request for loyalty account information (e.g., that the user of the computer system has selection an option for requesting loyalty account information from the user device, such as in a retail application) and that the user device provides (e.g., in response to a request from the computer system) both loyalty account information and non-loyalty account information (e.g., payment information), the computer system forgoes displaying, via the display generation component, an indication (e.g., via a banner the is displayed at the top of the display) that loyalty account information was received. Providing visual feedback about the account information that was received indicates the state of the computer system to the user, thereby providing the user with improved visual feedback.

In some embodiments, detecting, via one or more input devices, user input to initiate the transaction request includes detecting (e.g., via a touch-sensitive surface) activation (e.g.,701c) of (e.g., a tap at a location corresponding to) a displayed request-transaction graphical user interface element (e.g.,701a).

In some embodiments, in response to detecting user input (e.g.,701c) to initiate a transaction request, the computer system displays a request-transaction user interface (e.g.,702) of a first application (e.g., a payment application) and the request-transaction graphical user interface element (e.g.,701a) is displayed as part of a user interface (e.g.,701) of a second application (e.g., a payment processor application and/or a retailer application) that is different from the first application. Using separate applications to initiate the transaction request and to performing the transaction increases security by relying on a secure and/or known application (e.g., an application that is part of the operating system of the computer system) to perform portions of the technique that require higher levels of security.

In some embodiments, the computer system detects (e.g., while displaying the transaction user interface with the one or more elements in the second orientation) (e.g., receiving from the user device, via a short-range communication radio (e.g., NFC and/or UWB) or via a camera of the computer system) account details (e.g., account information, such as account number, account expiration date, and/or name associated with the account). In some embodiments, the computer system performs an operation using some (e.g., all of, not all of) of the account details without attempting to transfer funds (e.g., without processing a payment).

In some embodiments, the operation is a transaction lookup operation that uses some of the account details to identify (and, optionally, display details of) a previously performed transaction.

In some embodiments, the operation is a provisioning operation that uses some of the account details to provision the account onto the computer system (e.g., store details about the account at the computer system such that the computer system can, subsequently, perform transactions (e.g., transmit payment account information, such as to a contactless payment terminal)).

In some embodiments, the operation adds an amount (and/or an item or service for purchase) to a tab (e.g.,FIG.7O) (e.g., a running total of charges that an individual or group accumulates for subsequent settlement, such as a bar tab) associated with (e.g., identified using) some of the account details.

In some embodiments, the operation includes verifying account ownership based on the account details. In some embodiments, the operation is an operation other than performing a transfer of funds.

Note that details of the processes described above with respect to method900(e.g.,FIG.9) are also applicable in an analogous manner to the methods described below/above. For example, method1200optionally includes one or more of the characteristics of the various methods described above with reference to method900. For example, method1200may request information to provision an account as discussed above with reference to method800. As another example, method1500optionally includes one or more of the characteristics of the various methods described above with reference to method900. For example, method1500may receive gift card information through the process discussed above with reference to method900. As another example, method1800optionally includes one or more of the characteristics of the various methods described above with reference to method900. For example, method1800may receive payment accounts as discussed above with reference to method900. For brevity, these details are not repeated below. As another example, method900optionally includes one or more various methods described above with reference to method2000. For example, computer system1900optionally requires entry of a numeric sequence in response to receiving a request corresponding to a transaction for a first amount as described in method2000. As another example, method900optionally includes one or more of the various methods described below with reference to method2010. For example, computer system1900optionally locks in response to receiving a request corresponding to a transaction as described in method2010. As another example, method900optionally includes one or more various methods described below with reference to method2300. For example, computer system1900optionally, in response to receiving a request corresponding to a transaction, displays a quantity of a first type of user interface elements as described in method2300.

FIGS.10A-10Billustrate example user interfaces for provisioning an SSH account onto a computer system, in accordance with some embodiments. The user interfaces in these figures are used to illustrate the processes described above, including the processes inFIG.12.

AtFIG.10A, computer system1000displays user interface1001for signing into computer system1000, wherein computer system1000has at least one SSH key, after computer system1000has completed an update (e.g., an update of the operating system of computer system1000). Computer system1000receives credentials (e.g., login and/or password), as indicated by the content in the username and password fields inFIG.10A. In response to detecting user input1050a(e.g., tap, swipe, and/or other gesture) on sign-in user interface element1001a, computer system1000confirms whether the received credentials are valid and, if the credentials are valid, computer system1000initiates a process to provision the SSH account onto the computer system and displays user interface1002, as shown inFIG.10B. AtFIG.10B, user interface1002is displayed on computer system1000which includes banner1002aindicating that the SSH account associated with the user has automatically been set up on computer system1000.FIG.10Balso includes computer system1015, which is displaying notification1015aindicating that the user's account has been automatically set up on computer system1015.

FIGS.11A-11Eillustrate exemplary user interfaces for provisioning an account onto a computer system, in accordance with some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes inFIG.12.

InFIG.11A, computer system1100displays user interface1101for signing into a user account of computer system1100after computer system1100has completed an update (e.g., an update of the operating system of computer system1100). Computer system1100receives credentials (e.g., login and/or password) for the user account, as indicated by the content in the username and password fields inFIG.11A. In response to detecting user input1101b(e.g., tap, swipe, and/or other gesture) on sign-in user interface element1101a, computer system1100confirms whether the received credentials are valid and, if the credentials are valid, computer system1100displays user interface1102, as shown inFIG.11B.

After (e.g., in response to) detecting that the user has successfully signed into computer system1100after computer system1100has completed an update (e.g., a software update and/or an update to the operating system of computer system1100), computer system1100determines whether a set of provisioning criteria are met. In some embodiments, the set of provisioning criteria is met when all criteria of the set of provisioning criteria are met. In some embodiments, the set of provisioning criteria includes a criterion that is met when an account (e.g., a payment account, a value storage account, a loyalty account, and/or an identification account) associated with the user account (e.g., corresponding to the login/password) exceeds a threshold amount (e.g., exceeds 0, exceeds 100) or includes a balance (e.g., includes some funds). In some embodiments, the set of provisioning criteria includes a criterion that is met when the account associated with the user account has not previously been removed from computer system1100. For example, if the account was previously provisioned onto computer system1100and then removed (e.g., was not provisioned onto computer system1100when the update was initiated at computer system1100), then the account will not be automatically provisioned on computer system1100because the user has indicated they do not want the account to be provisioned onto computer system1100.

When the set of provisioning criteria is met (e.g., the account is carrying a balance), then computer system1100provisions the account associated with the user account onto computer system1100so that the account may be used in conjunction with computer system1100. For example, computer system1100can automatically provision a payment account associated with the user account based on the set of provisioning criteria being met such that the user may utilize the payment account (e.g., make NFC payments and/or transmit payment account information) soon after the update without needing to manually provision the payment account (e.g., without providing details that are specific to the payment account and/or without entering an account number of the payment account). In some embodiments, in response to detecting that the user has successfully signed into computer system1100and in accordance with a determination that the set of provisioning criteria is met, computer system1100proceeds to provision the account onto computer system1100without requiring and/or receiving further user input. In some embodiments, the set of provisioning criteria includes a update criterion that is met when a software (e.g., operating system and/or wallet application) of the computer system has been upgraded. When the set of provisioning criteria is not met, the computer system forgoes automatically provisioning the account onto computer system1100.

InFIG.11B, user interface1102is displayed providing a notification to the user that the account (e.g., a payment account) has been automatically provisioned on computer system1100. User interface1102includes virtual card1102awhich indicates the account that was provisioned onto computer system1100and text1102bindicating to the user that the account was provisioned successfully.

In some embodiments, the user may have another computer system (e.g., a phone, watch, tablet, or computer) associated with (e.g., paired to and/or in a special paired relationship with) computer system1100. Accordingly, the account associated with the user account is also automatically provisioned on the secondary computer system when the set of provisioning criteria is met (e.g., once the set of provisioning criteria is met (and therefore the account will be provisioned onto computer system1100), computer system1100initiates a process to provision the same account onto the secondary computer system). In some embodiments, in accordance with a determination that the set of provisioning criteria is met and that an associated external computer system has also recently been updated, computer system1100initiates the process to provision the account onto the secondary computer system. In some embodiments, in accordance with a determination that the set of provisioning criteria is met (or not met) and that an associated external computer system has not recently been updated, computer system1100forgoes initiating the process to provision the account onto the secondary computer system. InFIG.11Bsecondary computer system1110, which is associated with computer system1100, is also illustrated. Computer system1110is displaying user interface1110aproviding a notification to the user that the account associated with the user account has been automatically provisioned onto computer system1110. In some embodiments, the provisioning of the account on computer system1110is initiated by computer system1100when the set of provisioning criteria is met. In some embodiments, provisioning the account onto a respective computer system includes storing information about the account (e.g., a primary account number, an account number, an expiration date, and/or a name of the user associated with the account) in a secure element of the respective computer system. The respective computer system subsequently (e.g., in response to authentication/authorization) releases (e.g., transmits via short-range communication radio, via NFC, and/or via UWB) account details (e.g., payment account details, loyalty account details) of the account to participate in a transaction (e.g., a payment transaction or a loyalty transaction).

InFIG.11C, user interface1103is displayed on computer system1100which includes banner1103aindicating that the account associated with the user has been provisioned on computer system1100. Banner1103ais displayed over a home user interface and includes the text “Account Provisioned card has been added to account” to notify the user that their account has been automatically provisioned on computer system1100. By providing banner1103arather than user interface1102discussed above with regard toFIG.11Bthe user may see and access other applications of the device while also being notified about the provision of their account. For example, the provisioning process is initiated and proceeds in the background while computer system1100and/or1110are accessed by the user. Once the provisioning process is complete for a respective computer system, the respective computer system provides a notification (e.g.,1103,1115a) indicating that the account has been provisioned onto the respective computer system. Accordingly, the respective computer system can be used for other purposes while the provisioning process progresses and the user is notified of the completion of the provisioning process.

FIG.11Calso includes computer system1115which is displaying notification1115aindicating that the user's account has been automatically provisioned to computer system1115. The user may dismiss notification1115aby providing a touch input (e.g., tap) on the button labeled dismiss or by providing a swipe down or up to display other notifications being provided by computer system1115.

FIGS.11D-11Eillustrate exemplary user interfaces for a technique where the account associated with the user account is provisioned onto computer system1100based on a request to add funds to the account associated with the user account. InFIG.11D, computer system1100displays user interface1104for adding funds to the account associated with the user account (e.g., in response to user input requesting to display a user interface for adding funds). In some embodiments, the account associated with the user account was not previously automatically provisioned onto computer system1100after computer system1100completed an updated (e.g., because the account did not have a balance/funds at that time). Accordingly, computer system1100receives a request to add funds to the account associated with the user account using user interface1104(e.g., of a payment application) via user input1104bon (e.g., a tap on and/or selection of) user interface element1104a.

In response to detecting user input1104b, computer system1100adds the funds to the account associated with the user account and displays user interface1105, as shown inFIG.11E. User interface1105provides the user with information about the account, such as the available funds on the account. In response to detecting user input1104b, computer system1100determines whether a second set of provisioning criteria is met (e.g., that the account associated with the user account was not previously deprovisioned from computer system1100and/or that the account is not already provisioned onto computer system1100). In accordance with a determination that the second set of provisioning criteria is met, computer system1100automatically provisions (or initiates a process to provision) the account onto computer system1100so that the user can utilize the account using computer system1100(e.g., via payments and/or loyalty transactions; using NFC and/or UWB). After automatically provisioning (or initiating the process to provision), in accordance with a determination that the account associated with the user account has been provisioned onto computer system1100, computer system1100displays banner1105aindicating that the account associated with the user has been provisioned on computer system1100, as shown inFIG.11E. In accordance with a determination that the account associated with the user account has not (e.g., yet) been provisioned onto computer system1100, computer system1100forgoes displaying banner1105a. Accordingly, the account associated with the user account is provisioned on computer system1100in response to the user adding funds to the account, thereby enabling easy use of the account on computer system1100.

In some embodiments, in accordance with a determination that the second set of provisioning criteria is not met, computer system1100forgoes automatically provisioning (or initiating the process to provision) the account associated with the user account onto computer system1100, computer system1110, or computer system1115.

In some embodiments, after the account has been provisioned onto computer system1100, computer system1110, and/or computer system1115, an option is provided (e.g., at computer system1100,1110, and/or1115) to remove the account from one or more of computer system1100, computer system1110, and/or computer system1115. In response to receiving user input selecting the option to remove the account from one or more of computer system1100, computer system1110, and/or computer system1115a process is initiated to remove the account from the selected computer system.

In some embodiments, after removing the account from one or more of computer system1100, computer system1110, and/or computer system1115a setting user interface is displayed and a user input to provision the account onto one or more of computer system1100, computer system1110, and/or computer system1115is received. In response to receiving the user input to provision the account associated with the user, a process is initiated to provision the account on the selected computer system. Thus, computer system1100(and, optionally, computer systems1110,1115) enable the user to manually remove and/or add the account (and other payment, loyalty, and/or transaction accounts) to computer system1100(and, optionally,1110and1115).

In some embodiments, the account associated with the user account is a stored-value account to which funds can be transferred and from which funds can be used to make payments. In some embodiments, a gift card can be redeemed to add funds to the account. In some embodiments, a visual representation (e.g.,1102aofFIG.11B) of the account is based on a most recently redeemed gift card and is displayed on one or more of computer system1100, computer system1110, and/or computer system1115. For example, the visual representation of the account can include an image, a background color, and/or other visual elements based on an image, a background color, and/or other visual elements of the redeemed gift card.

FIG.12is a flow diagram illustrating a method for provisioning an account onto a computer system in accordance with some embodiments. Method1200is performed at a computer system (e.g.,100,300,500,700,1100,1400,1700) (e.g., a smartwatch, a wearable electronic device, a smartphone, a desktop computer, a laptop, or a tablet) (e.g., that is in communication with a display generation component (e.g., a display controller and/or a touch-sensitive display system) and one or more input devices (e.g., a button, a rotatable input mechanism, a speaker, a camera, a motion detector (e.g., an accelerometer and/or gyroscope), and/or a touch-sensitive surface)). Some operations in method1200are, optionally, combined, the orders of some operations are, optionally, changed, and some operations are, optionally, omitted.

As described below, method1200provides an intuitive way for provisioning an account onto a computer system. The method reduces the cognitive burden on a user provisioning an account onto a computer system, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to provision an account onto a computer system faster and more efficiently conserves power and increases the time between battery charges.

In response to detecting (1202) a sign-in (e.g., as inFIG.11A) of a user account after a software update (e.g., an update of the operating system, update of a payment application) and in accordance with a determination that a first set of provisioning criteria are met, including a first provisioning criterion that is met when an account (e.g., a payment account, a memory storage account) associated with the user account exceeds a threshold amount (e.g., exceeds a balance of zero, exceeds a balance of one hundred, exceeds a balance of one thousand), the computer system (e.g.,1100) (e.g., a smartwatch, a wearable electronic device, a smartphone, a desktop computer, a laptop, or a tablet) initiates (1204) a process to provision (e.g., assigning the account, making the account available for use) the account onto the computer system. In some embodiments, the computer system forgoes initiating the process to provision the account onto the computer system (e.g., even if the first set of provisioning criteria are met) when the detected sign-in of the user account is not after (e.g., is not the first sign-in of that user's account on the computer system after) a software update. Automatically initiating a process to provision an account onto a computer system after a software update when the first set of provisioning criteria are met reduces the need for the user to provide input to provision the account, thereby reducing the number of inputs needed to perform an operation and performing an operation when a set of conditions has been met without requiring further user input.

In response to detecting (1202) a sign-in of a user account after a software update and in accordance with a determination that the first set of provisioning criteria are not met (e.g., the account associated with the user account does not exceed a threshold amount), the computer system forgoes (1206) initiating the process to provision the account onto the computer system. In some embodiments, the sign-in of the user account after the software update is the first sign-in of the user account since the software update has been installed.

In some embodiments, in response to detecting the sign-in (e.g., as inFIG.11A) of the user account after the software update and in accordance with the determination that first set of provisioning criteria are met, the computer system initiates a process to provision (e.g., assigning the account, making the account available for use) the account onto an external device (e.g.,1110) (e.g., a smart watch or a laptop computer). In some embodiments, the set of provisioning criteria includes a paired criterion that is met when the computer system is paired to (and, optionally, in communication with) an external device. In some embodiments, the same user account is logged into both the computer system and the external device. Automatically initiating a process to provision an account onto an external device of the user after a software update when the first set of provisioning criteria are met reduces the need for the user to provide input to provision the account, thereby reducing the number of inputs needed to perform an operation and performing an operation when a set of conditions has been met without requiring further user input.

In some embodiments, the first set of provisioning criteria includes a second criterion that is met when the account (e.g., a payment account, a memory storage account) associated with the user account has not previously been removed from the computer system. In some embodiments, prior to the software update and while the account associated with the user account is provisioned onto the computer system, the computer system receives user input to remove (deprovision) the account associated with the user account from the computer system. In response to receiving the user input to remove the account associated with the user account from the computer system, the computer system removes (deprovisions) the account associated with the user account from the computer system. Subsequently, the computer system does not automatically provision the account associated with the user account onto the computer system, even in response to detecting a sign-in of the user account after the software update. Forgoing automatically initiating a process to provision the account onto the computer system when the user has previously removed the account prevents the account from being provisioned on the computer system when the user has made intentional inputs to remove the account from the computer system, thereby reducing the need (and inputs) for the user to again remove the account from the computer system.

In some embodiments, subsequent to (e.g., in response to) provisioning (e.g., assigning the account, making the account available for use) the account onto the computer system, the computer system provides a notification (e.g.,1102a,1103a) (e.g., displaying a visual notification via a display generation component, providing an audio notification via a speaker of the computer system, and/or providing a tactile notification via tactile output) that the account has been provisioned onto the computer system (e.g.,1100). Providing a notification that the account has been provisioned provides the user with feedback about the state of the computer system.

In some embodiments, the computer system receives (e.g., subsequent to the software update, prior to the software update) user input (e.g.,1104b) authorizing adding funds to the account associated with the user account. In some embodiments, in response to receiving user input authorizing adding funds to the account associated with the user account and in accordance with a determination that a second set of provisioning criteria are met, including a criterion that is met when the account associated with the user account is not provisioned onto the computer system, the computer system provisions the account onto the computer system. In some embodiments, when the account associated with the user account is already provisioned onto the computer system, the second set of provisioning criteria is not met and the computer system forgoes provisioning the account onto the computer system. Automatically initiating a process to provision the account onto a computer system (e.g., regardless of whether it is after a software update) when the second set of provisioning criteria are met reduces the need for the user to provide input to provision the account, thereby reducing the number of inputs needed to perform an operation and performing an operation when a set of conditions has been met without requiring further user input.

In some embodiments, wherein the second set of provisioning criteria includes a criterion that is met when the account (e.g., a payment account, a memory storage account) associated with the user account has not previously been removed from the computer system. In some embodiments, while the account associated with the user account is provisioned onto the computer system, the computer system receives user input to remove (deprovision) the account associated with the user account from the computer system. In response to receiving the user input to remove the account associated with the user account from the computer system, the computer system removes (deprovisions) the account associated with the user account from the computer system. Subsequently, the computer system does not automatically provision the account associated with the user account onto the computer system, even in response to detecting user input authorizing adding funds to the account associated with the user account. Forgoing automatically initiating a process to provision the account onto the computer system when the user has previously removed the account prevents the account from being provisioned on the computer system when the user has made intentional inputs to remove the account from the computer system, thereby reducing the need (and inputs) for the user to again remove the account from the computer system.

In some embodiments, subsequent to provisioning the account associated with the user account onto the computer system (e.g., automatically provisioning in response to receiving user input authorizing adding funds to the account associated with the user account and/or automatically provisioning in response to detecting the sign-in of the user account after the software update), the computer system provides (e.g., displaying, via the display generation component) an option to remove the account from the computer system. In some embodiments, the computer system receives (e.g., while providing the option to remove the account from the computer system) user input selecting the option to remove the account from the computer system. In some embodiments, in response to receiving user input selecting the option to remove the account from the computer system, the computer system initiates a process to remove (deprovision) the account from the computer system. Enabling the user to manually initiate a process to remove the account from the computer system allows the computer system to free up memory, thereby improving the performance of the computer system.

In some embodiments, subsequent to removing the account from the computer system, the computer system displays a settings user interface. In some embodiments, while displaying the settings user interface, the computer system receives user input to provision the account associated with the user account onto the computer system. In some embodiments, in response to receiving user input to provision the account associated with the user account onto the computer system, initiating a process to provision the account onto the computer system. Enabling the user to manually initiate a process to provision the account onto the computer system allows the computer system to use the account in future transactions, thereby improving the capabilities of the computer system.

In some embodiments, the computer system displays (e.g., as part of an electronic wallet of the computer system and/or after provisioning the account onto the computer system) a visual representation (e.g., the “Jane Appleseed” card as inFIG.11E) of the account that is associated with the user account, wherein the visual representation includes a graphical visual element (e.g., an image, a logo, and/or a background color) that is based on a most recently redeemed gift account (e.g., redeemed gift card and/or redeemed value from a gift account). In some embodiments, the graphical visual element is not an indication of quantity or funds. In some embodiments, the computer system receives user input to access an electronic wallet of the computer system. The electronic wallet includes a visual representation of the newly provisioned account. In some embodiments, the visual representation of the newly provisioned account includes an image, logo, visual style, and/or background color that is based on (e.g., matches) that of a most recently redeemed gift account (e.g., same image, same logo, same style, and/or same background color). Displaying a visual representation of an account (e.g., based on a most recently redeemed gift card) provides the user with visual feedback about the account, such as how it was most recently funded, thereby providing improved visual feedback to the user.

Note that details of the processes described above with respect to method1200(e.g.,FIG.12) are also applicable in an analogous manner to the methods described below/above. For example, method1500optionally includes one or more of the characteristics of the various methods described above with reference to method1200. For example, method1500may automatically provision a gift card through the process discussed above with reference to method1200. As another example, method1800optionally includes one or more of the characteristics of the various methods described above with reference to method1200. For example, method1800may provision payment accounts as discussed above with reference to method1200. For brevity, these details are not repeated below. As another example, method1500optionally includes one or more various methods described below with reference to method2000. For example, computer system1900optionally requires entry of a numeric sequence in response to detecting a sign-in of a user account as described in method1500. As another example, method1500optionally includes one or more of the various methods described below with reference to method2010. For example, computer system1900optionally locks in response to detecting a sign-in of a user account as described in method2010. As another example, method1500optionally includes one or more various methods described below with reference to method2300. For example, computer system1900optionally, in response to detecting a sign-in of a user account, displays a quantity of a first type of user interface elements as described in method2300.

FIGS.13A-13Billustrate exemplary user interfaces for adding data from a data plan to an account, in accordance with some embodiments. The user interfaces in these figures are used to illustrate the processes described above, including the processes inFIG.15.

AtFIG.13A, computer system1300displays camera user interface1301. One or more cameras of computer system1300have been directed towards data plan card1302(a physical data plan card) such that data card1302is in a field-of-view of the one or more cameras and is being displayed in camera user interface1301. In response to detecting a QR code of data card1302, computer system1300displays balance element1301aoverlaid on camera user interface1301. Computer system1300detects user input1350acorresponding to a request to transfer the data plan balance to the balance of the user account. AtFIG.13B, computer system1300displays user interface1303. User interface1303includes data plan summary1303aand data plan summary1303b. In some embodiments, computer system1300detects user input1350c(e.g., a tap or a tap-and-hold) on individual and recurring transaction button1303dindicating that the user wants to add the data card balance to their account for use with both individual (e.g., downloading an app and/or visiting a website) and recurring downloads (e.g., updating an app and/or updating an email inbox). In response to receiving user input1350con individual and recurring downloads button1303d, the data plan card balance is identified as being available for use for both individual downloads and recurring downloads and is, optionally (e.g., without receiving further user inputs or based on additional user inputs), added to the user's data balance and can be used for any download, individual or recurring. In some embodiments, computer system1300detects user input1350bon individual downloads button1303c. In response to receiving user input1350bon individual downloads button1303c, the data plan card balance is identified as being available for use for individual downloads (and not available for use for recurring downloads) and is, optionally (e.g., without receiving further user inputs or based on additional user inputs), added to the user's data balance and can be used for individual downloads.

FIGS.14A-14Fillustrate exemplary user interfaces for adding funds from a gift card to an account (e.g., an account associated with a user account, as described with respect toFIGS.11A-11E), in accordance with some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes inFIG.15.

FIG.14Aincludes computer system1400which is displaying camera user interface1401. One or more cameras of computer system1400have been directed towards gift card1402(a physical gift card) such that gift card1402is in a field-of-view of the one or more cameras. Thus, an image1401cof gift card1402is being captured by the one or more cameras of computer system1400and is being displayed in camera user interface1401(e.g., in a viewfinder of a camera application). In response to detecting a QR code of gift card1402, computer system1400displays balance element1401aoverlaid on camera user interface1401and, optionally, on image1401cof the gift card. In some embodiments, balance element1401ais displayed adjacent to QR code1401d. In some embodiments, as gift card1402and computer system1400move with respect to each other, causing image1401cof gift card1402to also move on the display, computer system1400updates the display location of balance element1401asuch that balance element1401aremains displayed adjacent to QR code1401d, thereby informing the user that the information of displayed as part of balance element1401acorresponds to information gathered based on the QR code. Balance element1401ashows the balance of gift card1402and/or the balance of the account (e.g., a payment account) associated with the user account. Balance element1401aprovides information to the user to make a decision on whether to add the gift card balance to the balance of their account. When the user decides to add the gift card balance to their account, the user provides input1401b(e.g., a tap or a tap-and-hold) on balance element1401adisplayed in camera user interface1401.

In response to receiving user input1401b, computer system1400displays user interface1403for adding the gift card balance inFIG.14B. User interface1403provides the user with different options for adding the gift card balance to their account, including a first option for adding the gift card balance for use with individual transactions (e.g., because the user wants to ensure that their gift card balance is used towards a one-time purchase that they select as a gift) and a second option for adding the gift card balance for use with individual and recurring transactions (e.g., because the user prefers to use the balance from the gift card for all of their purchases). The second option allows the user to specify that the added balance can be used for recurring (e.g., monthly or weekly) transactions such as streaming, gaming, or music services and individual transactions like purchasing a single game or movie or just for the individual transactions.

User interface1403includes card representation1403a, balance element1403b, individual transaction button1403c, and individual and recurring transaction button1403d. Card representation1403aincludes a picture or graphical representation of gift card1402, retrieved based on the QR code that was scanned using camera user interface1401. Balance element1403bincludes the same information provided in camera user interface1401including, optionally, the balance of the gift card to be added and the current balance of the account (e.g., payment account) associated with the user (to which the balance of the gift card will be added).

In some embodiments, computer system1400receives user input1403e(e.g., a tap or a tap-and-hold) on individual transaction button1403cindicating that the user wants to add the gift card balance to their account for use with individual transactions. In response to receiving user input1043eon individual transaction button1403cthe balance of the gift card balance is identified as being preserved for use with individual transactions and not for use with recurring transactions and is, optionally (e.g., without receiving further user inputs or based on additional user inputs), added to the user's account balance (while being preserved for use with individual transactions and not for recurring transactions). Thus, the fifty dollar gift card balance that is added to the user's account will not be used for the next recurring transaction or other recurring transactions that pull funds from the user's account.

After (e.g., in response to) adding the gift card balance for use with individual transactions, computer system1400displays confirmation interface1404as shown inFIG.14C. Confirmation1404aprovides text to the user indicating that the gift card balance has been added for use with individual transactions.

Returning toFIG.14B, in some embodiments, computer system1400receives user input1403f(e.g., a tap or a tap-and-hold) on individual and recurring transaction button1403dindicating that the user wants to add the gift card balance to their account for use with both individual transactions and recurring transactions. In response to receiving user input1403fon individual and recurring transaction button1403d, the gift card balance is identified as being available for use for both individual transactions and recurring transactions and is, optionally (e.g., without receiving further user inputs or based on additional user inputs), added to the user's account balance and can be used for any transaction, individual or recurring. Thus, the fifty dollar gift card balance that is added to the user's account can be accessed when the next request to pull funds from the user's account is received, regardless of the type of transaction (e.g., recurring or not recurring transaction).

After (e.g., in response to) adding the gift card balance for use with individual and recurring transactions, computer system1400displays confirmation interface1405as shown inFIG.14D. Confirmation1405aprovides text to the user indicating that the gift card balance has been added for use with both individual transactions and recurring transactions (in other words, but recurring and non-recurring transactions).

In some embodiments, computer system1400receives an instant message (e.g., a text message, an SMS message, and/or an MMS message) from another user sending a gift card (or gift amount) to the user of computer system1400. In response to receiving the instant message, computer system1400notification1406a, as part of user interface1406as shown inFIG.14E, corresponding to the instant message received from another user which includes a gift card (or gift amount) with an optional indication of the value of the amount (e.g., for fifty dollars). In some embodiments, computer system1400receives user input1406b(e.g., a tap, a tap-and-hold) on notification1406acorresponding to the instant message.

After (e.g., in response to) detecting user input1406bon notification1406a(e.g., when computer system1400is in an unlocked state), computer system1400displays user interface1403for adding the gift card balance to the user's account, as shown inFIG.14F. As discussed above with regard toFIG.14B, user interface1403provides the user with options on how to add the gift card balance including a first option to add the balance for use for individual transactions (and not for recurring transactions) and a second option to add the balance for use for both individual and recurring transactions.

In some embodiments, subsequent to adding the gift card balance to the user's account, a first authorized request is made to the user's account to make a payment for an individual (not recurring) transaction and, in response, the gift card funds are available for the transaction regardless of whether the gift card funds were added with the first option (individual transactions) or the second option (individual and recurring transactions). In some embodiments, subsequent to adding the gift card balance to the user's account, a second authorized request is made to the user's account to make a payment for a recurring transaction (e.g., a monthly music subscription payment, a monthly gym membership payment, a yearly video streaming service payment) and, in response, the gift card funds are available for the transaction if the gift card funds were added with the second option (individual and recurring transactions), but the gift card funds are not available for the transaction if the gift card funds were added with the first option (individual transactions), though other funds of the account are available (e.g., funds previously added without being limited for use with individual transactions). Accordingly, the user can specify whether funds added to an account should be preserved for use for only individual transactions or whether the funds added to the account should be used for both recurring and non-recurring transactions).

FIG.15is a flow diagram illustrating a method for adding funds from a gift card to an account in accordance with some embodiments. Method1500is performed at a computer system (e.g.,100,300,500,700,1100,1400,1700) that is in communication with a display generation component (e.g., a display controller and/or a touch-sensitive display system) and one or more input devices (e.g., a button, a rotatable input mechanism, a speaker, a camera, a motion detector (e.g., an accelerometer and/or gyroscope), and/or a touch-sensitive surface). Some operations in method1500are, optionally, combined, the orders of some operations are, optionally, changed, and some operations are, optionally, omitted.

As described below, method1500provides an intuitive way for associating a transfer amount with an account. The method reduces the cognitive burden on a user adding funds from, for example, a gift card to an account, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user add funds from a gift card to an account faster and more efficiently conserves power and increases the time between battery charges.

The computer system (e.g.,1400) (e.g., a smartwatch, a wearable electronic device, a smartphone, a desktop computer, a laptop, or a tablet) receives a request (e.g.,1401b) (e.g., a request for memory allocation or a request for payment) to associate a transfer amount (e.g., allocated memory, data, a balance, and/or funds) with an account (e.g., a user account and/or a payment account).

The computer system displays (e.g., in response to receiving the request) a first user interface element (e.g.,1403d) associated with a recurring transaction (e.g., a subscription payment plan) and an individual transaction (e.g., one time transaction) and a second user interface element (e.g.,1403c) associated with an individual transaction and not associated with a recurring transaction.

In response to receiving user input (e.g., tapping on the first user interface element or the second user interface element, tapping on the first user interface element or the second user interface element and tapping another affordance (e.g., go, next)) and in accordance with a determination that the user input (e.g.,1403f) corresponds to a selection of the first user interface element (e.g.,1403d), the computer system configures (e.g., assigning, and/or setting up for use) the transfer amount for use with recurring transactions and individual transactions.

In response to receiving user input and in accordance with a determination that the user input (e.g.,1403e) corresponds to a selection of the second user interface element (e.g.,1403c), the computer system configures the transfer amount for use with individual transactions without configuring the transfer amount for use with recurring transactions.

Configuring the transfer amount (e.g., funds from a gift card) for use with individual transactions enables the computer system to automatically forgo using the transfer amount for recurring transactions (even in response to a request for funds (of a recurring transaction) from the account with which the transfer amount has been associated (e.g., transferred to), therefore enabling the computer system to save the transfer amount for later use for an individual purchase (a non-recurring transaction) directed by the user of the account, thereby reducing the need for the user to provide input for each transaction (e.g., recurring transaction) to indicate that the transfer amount should not be used.

In some embodiments, a user receives a gift card from an acquittance that includes a certain amount of funds. When transfer the funds from the gift card to their account, the user can specify whether these funds can be used for recurring transactions. If the user selects to make these funds available for use for recurring transactions, recurring transactions (even if initially initiated prior to transferring the funds from the gift card to the user's account) can be settled using funds from the gift card. If the user selects to not make these funds available for use for recurring transactions, recurring transactions cannot be settled using funds from the gift card, thereby enabling the user to subsequently separately identify an item (e.g., a software, a game, and/or an electronic device) to purchase using the funds without worry that the funds will be used for recurring transactions. Accordingly, the user can recognize that the item was purchased using the funds from the gift card, rather than merely having those funds used to make a payment toward a service (with recurring billing) that was initiated prior to (or after) receiving the gift card.

In some embodiments, receiving the request (e.g., a request for memory allocation or a request for payment) to associate the transfer amount (e.g., allocated memory, data, a balance, and/or funds) with an account includes receiving information (e.g., a QR Code corresponding to funds, an account number of an account providing the transfer amount, a PIN, and/or a verification code) about the transfer amount using a camera of the computer system (e.g., as inFIG.14A). In some embodiments, receiving the request (e.g., a request for memory allocation or a request for payment) to associate the transfer amount includes detecting activation of (e.g., a tap input on or a tap-and-hold input on) a notification displayed concurrently with a representation of a code (e.g., a QR code, a barcode). Using a camera of the computer system to detect information about the transfer amount (e.g., reading a QR code and, optionally, communicating with a server to determine the transfer amount based on the QR code) enables the computer system to access information about the transfer amount and to display the information without requiring additional user input, thereby reducing the number of inputs needed to perform an operation.

In some embodiments, the computer system concurrently displays, via a display generation component a camera viewfinder (e.g.,1401) (e.g., as part of a camera application confirmed to capture images and/or video and/or that includes a field-of-view of one or more cameras of the computer system) of a camera, wherein the camera viewfinder (e.g.,1401) includes a representation of a code (e.g.,1401d) (e.g., a QR code and/or a barcode) in the field-of-view of the camera and a notification (e.g.,1401a) that includes a current available transfer amount (e.g., $50 as inFIG.14A) (e.g., current amount of funds, current amount of memory) corresponding to the code. In some embodiments, the computer system detects the code via the camera and communicates with a remove computer, such as a server, to determine the current available transfer amount associated with the code. For example, the computer system reads the QR code (e.g., which includes a gift card number) and communicates information from the QR code (e.g., the gift card number) to a server. The service provides the amount of available funds associated with the gift card, and the amount of available funds is displayed concurrently with the code. Using a camera of the computer system to detect information about the transfer amount (e.g., reading a QR code and, optionally, communicating with a server to determine the transfer amount based on the QR code) enables the computer system to access information about the transfer amount and to display the information without requiring additional user input, thereby reducing the number of inputs needed to perform an operation.

In some embodiments, a location of the notification (e.g.,1401a) that includes the current available transfer amount correspond to the code is based on the location (e.g., in the viewfinder) of the representation (e.g.,1401d) of the code. In some embodiments, the physical card (e.g.,1402) does not visually include (e.g., on the card) the notification or the current available transfer amount. In some embodiments, the notification is displayed adjacent to the representation of the code. In some embodiments, the notification overlays the viewfinder. In some embodiments, as the computer system and code move with respect to each other, the location (on the display of the computer system) of the representation of the code and the location of the notification both change such that the two elements remain adjacent to each other. Displaying the notification at a location based on the display location of the code enables the computer system to indicate to the user that the notification corresponds to (and is based on) the code, providing improved visual feedback to the user.

In some embodiments, receiving the request (e.g., a request for memory allocation or a request for payment) to associate the transfer amount (e.g., allocated memory, data, a balance, and/or funds) with an account includes receiving information (e.g., an account number of an account providing the transfer amount, a PIN, and/or a verification code) about the transfer amount via a message (e.g.,1406a) (e.g., an instant message of a message conversation) received at the computer system. In some embodiments, receiving the request (e.g., a request for memory allocation or a request for payment) to associate the transfer amount includes detecting activation of (e.g., a tap input on or a tap-and-hold input on) a notification (e.g., of the message). Receiving information about the transfer amount via a message reduces the amount of input the user needs to provide, thereby reducing the number of inputs needed to perform an operation, and enables the computer system to receive information about a transfer amount (e.g., receive a gift card) electronically without needing the user of the computer system to physically receive the information and/or manually enter the information into the computer system.

In some embodiments, subsequent to (e.g., in response to) receiving the request (e.g., a request for memory allocation or a request for payment) to associate the transfer amount (e.g., allocated memory, data, a balance, and/or funds) with the account and in accordance with a determination that a first set of provisioning criteria are met, including a first criterion that is met when the account is not provisioned on the computer system, the computer system provisions (or initiates a process to provision) the account onto the computer system (e.g., in the background, without requiring further user input, and/or without user input requesting the account be provisioned onto the computer system) (and, optionally, associating (e.g., transferring) the transfer amount to the account). Automatically provisioning the account onto the computer system enables the computer system to participate in transactions (e.g., online transactions, NFC transactions, and/or UWB transactions) using funds of the account, including the transfer amount, without requiring the user to enter account information for each transaction, thereby reducing the number of inputs needed to perform an operation.

In some embodiments, subsequent to (e.g., in response to) receiving the request to associate the transfer amount (e.g., allocated memory, data, a balance, and/or funds) with the account, in accordance with a determination that the account is provisioned onto the computer system, associating (e.g., transferring) the transfer amount to the account (without provisioning the account onto the computer system).

In some embodiments, the first set of provisioning criteria includes a second criterion that is met when the account (e.g., a payment account, a memory storage account) has not previously been removed from the computer system. In some embodiments, while the account is provisioned onto the computer system, the computer system receives user input to remove (deprovision) the account associated with the user account from the computer system. In response to receiving the user input to remove the account associated with the user account from the computer system, the computer system removes (deprovisions) the account associated with the user account from the computer system. Subsequently, the computer system does not automatically provision the account onto the computer system, even in response to detecting user input authorizing associating transfer funds with the account. Forgoing automatically initiating a process to provision the account onto the computer system when the user has previously removed the account prevents the account from being provisioned on the computer system when the user has made intentional inputs to remove the account from the computer system, thereby reducing the need (and inputs) for the user to again remove the account from the computer system.

In some embodiments, subsequent to (e.g., in response to) receiving the request (e.g., a request for memory allocation or a request for payment, at the computer system) to associate the transfer amount (e.g., allocated memory, data, a balance, and/or funds) with the account and in accordance with a determination that a second set of provisioning criteria are met, including a first criterion that is met when the account is not provisioned on an external device (e.g., a watch that is in communication with the computer system) that is paired with the computer system, the computer system provisions (or initiates a process to provision) the account onto the external device (e.g., in the background, without requiring further user input, and/or without user input requesting the account be provisioned onto the external system). In some embodiments, the same user account is logged into both the computer system and the external device. Automatically initiating a process to provision an account onto an external device reduces the need for the user to provide input to provision the account, thereby reducing the number of inputs needed to perform an operation and performing an operation when a set of conditions has been met without requiring further user input.

In some embodiments, the computer system receives input to perform a transaction for a recurring transaction. In some embodiments, in response to receiving input to perform a transaction for a recurring transaction and in accordance with a determination that the transfer amount is configured for use with recurring transactions, the computer system uses the transfer amount to perform the transaction for the recurring transaction. In some embodiments, in response to receiving input to perform a transaction for a recurring transaction and in accordance with a determination that the transfer amount is not configured for use with recurring transactions, the computer system forgoes using (e.g., declining to use) the transfer amount (e.g., those funds associated with the account) to perform the transaction for the recurring transaction.

Note that details of the processes described above with respect to method1500(e.g.,FIG.15) are also applicable in an analogous manner to the methods described below/above. For example, method1800optionally includes one or more of the characteristics of the various methods described above with reference to method1500. For example, method1800may add a gift card payment to be used for payments as discussed above with reference to method1500. For brevity, these details are not repeated below. As another example, method1500optionally includes one or more various methods described above with reference to method2000. For example, computer system1900optionally requires entry of a numeric sequence in response to receiving a request to associate a transfer amount with an account as described in method1500. As another example, method1500optionally includes one or more of the various methods described below with reference to method2010. For example, computer system1900optionally locks in response a request to associate a transfer amount with an account as described in method2010. As another example, method1500optionally includes one or more various methods described below with reference to method2300. For example, computer system1900optionally, in response a request to associate a transfer amount with an account, displays a quantity of a first type of user interface elements as described in method2300.

FIGS.16A-16CFIGS.16A-16Cillustrate exemplary user interfaces for allocating memory, in accordance with some embodiments. The user interfaces in these figures are used to illustrate the processes described above, including the processes inFIG.18.

AtFIG.16A, computer system1600displays user interface1614for transferring and/or allocating memory for a server and/or application. User interface1614includes transfer button1614a. In response to detecting user input1650aon transfer button1614a, computer system1600displays user interface1616, as shown inFIG.16S. User interface1616includes transfer memory now button1616aand transfer in installments button1616b. AtFIG.16S, the “transfer memory now” option is selected (e.g., as a default). For transfers completed when the transfer memory now option is selected, a full transfer is made without subsequent transfers. AtFIG.16S, computer system1600detects user input1650b(e.g., a tap input or a tap-and-hold input) on transfer in installments button1616b, selecting a choice to transfer the memory over time rather than in a single transfer. In response to detecting user input1650b, computer system1600displays user interface1618, optionally including different options for transferring for the memory over time. In accordance with a determination that a first set of conditions is met (e.g., memory quantity is above a first threshold and/or below a second threshold), user interface1618includes installment option button1618aassociated with an installment transfer option and in accordance with a determination that a second set of conditions is met (e.g., transfer amount is above a third threshold and/or below a fourth threshold), user interface1618includes a second option button1618bassociated with a second transfer option.

FIGS.17A-17Qillustrate exemplary user interfaces for selecting a transaction type, in accordance with some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes inFIG.18.

FIG.17Aillustrates computer system1700displaying user interface1701associated with a shopping application (e.g., a web browser or a third-party application). Computer system1700displays user interface1701when a user has finished selecting the goods/services they would like to purchase and is ready to provide payment for the purchase. User interface1701includes checkout button1701aalongside information summarizing the user's desired purchase. AtFIG.17A, computer system1700detects user input1701b(e.g., a tap, swipe, and/or other gesture) on checkout button1701a.

In response to detecting user input1701bon checkout button1701, computer system1700displays user interface1702(e.g., partially or full overlaid on user interface1701), as shown inFIG.17B. User interface1702is part of a payment application different from the shopping application displayed in user interface1701and includes pay in full button1702a, pay later button1702b, and information1702cindicating the credit card to be used and the address to ship the purchased goods to when completing a process to pay for the goods in full. AtFIG.17B, the “pay in full” option is selected (e.g., as a default) as indicated by the bolded outline of pay in full button1702a. For transactions completed when the pay in full option is selected, a full payment is made for the transaction without subsequent payments. AtFIG.17B, computer system1700detects user input1702d(e.g., a tap input or a tap-and-hold input) on pay later button1702bselecting a choice to pay for the desired goods over time rather than in a single transaction.

In response to detecting input1702don pay later button1702b, computer system1700displays user interface1703, optionally including different options for paying for the purchase over time. In some embodiments, user interface1703replaces user interface1702without affecting underlying user interface1701. In accordance with a determination that a first set of conditions is met (e.g., purchase price is above a first threshold and/or below a second threshold), user interface1703includes installment option button1703aassociated with an installment payment option and in accordance with a determination that a second set of conditions is met (e.g., purchase price is above a third threshold and/or below a fourth threshold), user interface1703includes monthly option button1703bassociated with a monthly payment option with interest charges.

The installment payment option is based on the total amount of the purchase price, a predetermined number of payments, and/or a predetermined amount of time to complete payment of the purchase price. For example, when the total purchase amount is $1,128 and the predetermined number of payments is four, the installment payment option to pay over time is to pay $282 a total of four times, with payments made every two weeks. Thus, user interface1703includes installment option button1703aindicating that the payment plan of $282 dollars every two weeks. In some embodiments, the installment payment option does not charge interest and thus the total amount paid over the predetermined number of installment charges totals the total purchase price of the goods.

The monthly payment option is based on the total amount of the purchase price, a payment that occurs monthly, a total length of the agreement, and an interest rate. For example, when the total purchase amount is $1,128 and the length of the agreement is one year to be paid monthly, the monthly payment option provides monthly payment amounts by applying a determined interest rate to the outstanding balance as the balance is paid over monthly.

While displaying user interface1703, computer system1700receives user input. In response to receiving the user input and in accordance with a determination that the user input (e.g., user input1703c(e.g., a tap or a tap and hold) on installment option button1703a) corresponds to selection of installment option button1703, computer system1700displays user interface1704as shown inFIG.17D. User interface1704provides the user with information on the installment payment option including the number of payments (4), the frequency of the payments (every two weeks), and that there will be no late fees or other charges. User interface1704further includes button1704afor continuing and button1704bfor going back to the transaction selection screen shown in user interface1703.

After (e.g., in response to) receiving user input1704c(e.g., a tap or a tap and hold) on button1704afor continuing with the installment payment option and in accordance with a determination that user information should be collected and/or needs to be updated or confirmed, computer system1700displays user interface1705requesting user information, as shown inFIG.17E. User interface1705includes information fields1705arequesting information such as the user's first and last name, the user's date of birth, and the user's phone number. In some embodiments, the information requested includes a user's address, a user's e-mail address, a user's social security number or identifier, and/or other information that may be required to open a line of credit.

In some embodiments, information fields1705aare automatically filled based on information already available to computer system1700. For example, computer system1700may already know the user's first and last name, date of birth, and phone number based on a personal account associated with the user that is stored on computer system1700which includes that information. Accordingly, the data for those fields may be retrieved from the user's personal account and provided to the payment application for information fields1705a.

In some embodiments, the user modifies or provides the information for information fields1705avia a speech input or an input on a virtual keyboard and computer system1700displays the received information in information fields1705ain response.

User interface1705further includes button1705bfor moving to the next step of the purchasing process and button1705cfor moving back to the previous step of the purchasing process. Computer system1700receives user input1705don button1705bindicating that the user would like to continue with the purchasing process.

In response to receiving user input1705d, computer system1700optionally confirms that the information provided in information fields1705ais valid (e.g., in a valid format) and displays user interface1706providing an overview of the purchase agreement, as shown inFIG.17F. User interface1706includes a breakdown of the installment payments for the installment payment option, including the amount of each payment, the frequency of the payments, and the total amount that will be paid over the agreement. User interface1706further includes button1706afor agreeing to the installment payment plan. In some embodiments, computer system1700receives user input1706bon button1706a. Notably, the total for the installment payment option is the same as the total purchase amount, since the total for the installment payment option does not include interest charges.

After (e.g., in response to) receiving user input1706b, computer system1700displays user interface1707for providing a payment method, as shown inFIG.17G. In some embodiments, user interface1707is automatically populated with payment methods associated with the user and/or computer system1700(e.g., payment accounts provisioned onto computer system1700, as described with respect toFIG.7Qand/orFIGS.11A-11D), including a debit and/or credit card or a bank account, as shown inFIG.17G. In some embodiments, computer system1700receives user input selecting to add a payment method and computer system1700receives information associated with the payment method and processes the purchase agreement with the provided payment information. AtFIG.17G, computer system1700receives user input1707bon debit card element1707aindicating that the user would like to complete the purchase agreement with the account corresponding to the selected debit card.

After (e.g., in response to) receiving user input1707b, computer system1700displays user interface1708summarizing the purchase agreement and requesting payment authorization, as shown inFIG.17H. User interface1708includes notification1708aindicating the details of the purchase agreement and notification1708brequesting confirmation from the user. Computer system1700receives user input1708dof a press (e.g., a single press or a double-press) of physical button1708c, to indicate that the user confirms the purchase agreement.

After (e.g., in response to) receiving user input1708dpressing physical button1708c, computer system1700performs biometric authentication (e.g., fingerprint authentication, face recognition authentication, and/or iris authentication). In accordance with a determination that the user is not an authorized user, computer system1700forgoes completing the transaction. In accordance with a determination that the user is an authorized user, computer system1700completes the transaction and displays user interface1708with confirmation element1708e, as shown inFIG.17I. This provides a visual confirmation to the user that the purchase agreement has been completed.

Returning toFIG.17C, while displaying user interface1703, computer system1700receives user input. In response to receiving the user input and in accordance with a determination that the user input (e.g., user input1703d(e.g., a tap) on monthly option button1703b) corresponds to selection of monthly option button1703b, computer system1700displays user interface1709, as shown inFIG.17J. User interface1709provides a summary of the monthly payment plan for the current purchase including the payment amount, the number of total payments, the start date for payments, the interest rate, and any applicable late or finance charges. AtFIG.17J, computer system1700receives user input1709bselecting confirmation element109ato proceed with the monthly payment plan. Notably, the total for the monthly payment option is more than the total purchase amount, since the total for the monthly payment option includes (non-zero) interest charges.

After (e.g., in response to) receiving user input1709bselecting confirmation element1709a, computer system1700optionally proceeds through user interfaces1705-1708in substantially the same manner as described above with regard toFIGS.17E-17H. Accordingly, after receiving user input1708dpressing (e.g., single pressing or double-pressing) physical button1708c, computer system1700performs biometric authentication and, if successful, computer system1700displays user interface1708with confirmation element1708e, as shown inFIG.17K.

In some embodiments, when displaying user interface1703, in accordance with a determination that the first set of conditions is met, computer system1700displays installment option button1703aas a selectable option and in accordance with a determination that the second set of conditions is met, computer system1700displays monthly option button1703bas a selection option, as shown and described with respect toFIG.17C. In some embodiments, when displaying user interface1703, in accordance with a determination that the first set of conditions is met, computer system1700displays installment option button1703aas a selectable option and in accordance with a determination that the second set of conditions is not met, computer system1700forgoes displaying monthly option button1703bas a selection option, as shown inFIGS.17L and17M. InFIG.17L, monthly option button1703bis grayed out and is not selectable. InFIG.17M, monthly option button1703bis not displayed (and is therefore not selectable). In some embodiments, when displaying user interface1703, in accordance with a determination that the first set of conditions is not met, computer system1700forgoes displaying installment option button1703aas a selectable option and in accordance with a determination that the second set of conditions is met, computer system1700displays monthly option button1703bas a selection option, as shown inFIG.17N. In some embodiments, when displaying user interface1703, in accordance with a determination that the first set of conditions is not met, computer system1700forgoes displaying installment option button1703aas a selectable option and in accordance with a determination that the second set of conditions is not met, computer system1700forgoes displaying monthly option button1703bas a selection option. For example, the first and/or second set of conditions optionally include a condition that the total purchase amount be over a predefined limit, such as 50 dollars. Thus, when the total purchase amount is $1,128, as discussed above, that condition of the first and second sets of conditions is met and user interface1703optionally displays installment option button1703aand monthly option button1703bas selectable options.

In some embodiments, as discussed above, there is a first set of conditions for displaying installment option button1703aas a selectable option and a second set of conditions for displaying monthly option button1703bas a selectable option. Thus, the first set of conditions can be met without the second set of conditions being met, or vice versa, causing user interface1703to display one of installment option button1703aor monthly option button1703bwithout the other. For example, the first set of conditions for displaying installment option button1703acan include a condition that is met when the payment request (e.g., total purchase amount) is above a threshold limit of 25 dollars, while the second set of conditions for displaying monthly option button1703bcan include a condition that is met when the payment request (e.g., total purchase amount) is above a threshold limit of 50 dollars. Accordingly, when the payment request is for 36 dollars, as shown inFIG.17L, user interface1703displays the installment option button1703aas a selectable option, but does not display monthly option button1703bas a selectable option.

In some embodiments, not displaying either installment option button1703aand/or monthly option button1703bas selectable options includes displaying either installment option button1703aand/or monthly option button1703bwithout allowing the button to be selected. For example, as shown inFIG.17L, monthly option button1703bis displayed in a state where it is not able to be selected by the user. In some embodiments, displaying a button in this manner includes displaying the button in a dimmed state, with an overlay of a color (e.g., grey or white) that partially obscures the button, and/or in a state were the button does not appear to extend out of user interface1703. In this manner, the visual appearance of installment option button1703aand/or monthly option button1703bis changed to indicate to the user that either installment option button1703aand/or monthly option button1703bis not selectable because the set of conditions has not been met.

In some embodiments, not displaying either installment option button1703aand/or monthly option button1703bas selectable options includes displaying user interface1703without installment option button1703aand/or monthly option button1703b.

Exemplary conditions of the first and second sets of conditions include that an amount of the payment request is less than a threshold limit, an amount of the payment request is more than a threshold limit, an amount of concurrent payment plans is less than a threshold amount, an amount of concurrent payment plans is more than a threshold amount, the total amount of money owed by a user is less than a threshold amount, and/or that a credit score associated with the user is above a threshold score.

InFIG.17O, computer system1700displays user interface1710including notification1710ain accordance with a determination that a payment of the payment plan is due on the current date. Notification1710ais optionally displayed on a lock or home screen of computer system1700and indicates to the user that a payment will be made on the current day and that the user can view details of the payment or the payment plan by selecting notification1710a. AtFIG.17N, computer system1700receives user input1710bon notification1710aselecting notification1710a.

InFIG.17P, after (e.g., in response to) receiving user input1710b, computer system1700displays user interface1711providing information about the next payment of the payment plan. User interface1711indicates the date of the next payment in the payment plan and that the payment will be paid automatically. User interface1711further includes selectable button1711afor dismissing user interface1711and selectable button1711bto manage the payment plan. AtFIG.17P, computer system1700receives user input1711con selectable button1711bto manage the payment plan.

In some embodiments, after (e.g., in response to) receiving user input1711con selectable button1711bto manage the payment plan, computer system1700displays one or more user interfaces that provide information to the user about the payment plan or allow the user to make additional (e.g., unscheduled) payments.

InFIG.17Q, after (e.g., in response to) receiving user input1711con selectable button1711bto manage the payment plan, computer system1700displays user interface1712including calendar1712a. Calendar1712aconcurrently provides an overview of the user's payments plans (e.g., payment schedules for multiple purchases/transactions) and the upcoming payments for those payment plans. In this way, the user may review all of the user's payment plans and upcoming payments together when making decisions about whether to make a payment early. In some embodiments, computer system1700receives a user input selecting a day of calendar1712a(and/or a payment on calendar1712a) and, in response, displays a user interface corresponding to the selected payment plan (e.g., with additional details about the payments for the selected payment plan). In some embodiments, computer system1700receives user input1712con button1712band displays a user interface for making an unscheduled payment. Accordingly, the user may select an already displayed payment plan or specify a particular payment plan to make an unscheduled payment.

In some embodiments, the individual payments of the user's payment plans are added to a calendar application of computer system1700. Accordingly, computer system1700can concurrently display the user's upcoming payments alongside the user's scheduled appointments in the calendar application to provide the user with a more complete picture of the user's upcoming commitments.

FIG.18is a flow diagram illustrating a method for selecting a transaction type in accordance with some embodiments. Method1800is performed at a computer system (e.g.,100,300,500,700,1100,1400,1700) that is in communication with a display generation component (e.g., a display controller and/or a touch-sensitive display system) and one or more input devices (e.g., a button, a rotatable input mechanism, a speaker, a camera, a motion detector (e.g., an accelerometer and/or gyroscope), and/or a touch-sensitive surface). Some operations in method1800are, optionally, combined, the orders of some operations are, optionally, changed, and some operations are, optionally, omitted.

As described below, method1800provides an intuitive way for displaying user interface elements corresponding to transaction types. The method reduces the cognitive burden on a user selecting a transaction type, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to select a transaction type faster and more efficiently conserves power and increases the time between battery charges.

The computer system (e.g.,1700) (e.g., a smartwatch, a wearable electronic device, a smartphone, a desktop computer, a laptop, or a tablet) receives (1802) a request (e.g.,1701bor1702d) (e.g., a payment request) corresponding to a transaction for a first amount (e.g., an amount of memory, a payment balance).

In accordance with a determination that a first set of conditions is met (e.g., an amount of the payment request is less than a threshold limit, more than a threshold limit, an amount of concurrent payment plans, a total amount of money owed, and/or a credit score associated with the user is below a threshold), the computer system displays (1804), via the display generation component, a first activatable user interface element (e.g.,1703aatFIG.17C) (e.g., a button and/or pop-up) corresponding to a first quantity of transactions (e.g., an installment transaction) and to the first amount.

In accordance with a determination that a second set of conditions is met, the computer system displays (1806), via the display generation component, a second activatable user interface element (e.g.,1703datFIG.17C) corresponding to a second quantity of transactions and to a second amount (e.g., the first amount and some additional amount) that is different from the first amount. In some embodiments, the additional amount (e.g., amount over the first amount) is based on an interest rate. In some embodiments, the additional amount is a static amount.

Displaying one or more respective activatable user interface elements based on sets of conditions being met for the respective activatable user interface elements provides the user with visual feedback that the respective set of conditions has been met, thereby providing improved visual feedback.

In some embodiments, the quantity of transactions is based on an amount requested. In some embodiments, the quantity of transactions is based on a desired amount for each individual transaction. In some embodiments, the quantity of transactions is based on an interest rate. In some embodiments, the quantity of transactions is predetermined (e.g., four). In some embodiments, the amount of each transaction is based on the total payment requested and the predetermined number of transactions. In some embodiments, receiving user input to set up an account after selecting an option. In some embodiments, the computer system pulls information from already established account after selecting an option.

In some embodiments, the first set of conditions includes a first threshold maximum condition that is met when the first amount is less than a first threshold amount (e.g., $5,000, $300, or a non-zero amount). Displaying one or more respective activatable user interface elements based on certain sets of conditions being met for the respective activatable user interface elements provides the user with visual feedback that the respective set of conditions has been met, thereby providing improved visual feedback.

In some embodiments, the second set of conditions includes a second threshold maximum condition that is met when the first amount is less than a second threshold amount (e.g., $4,000, $200, or a non-zero amount, different from the first threshold amount). Displaying one or more respective activatable user interface elements based on certain sets of conditions being met for the respective activatable user interface elements provides the user with visual feedback that the respective set of conditions has been met, thereby providing improved visual feedback.

In some embodiments, the first set of conditions includes a first threshold minimum condition that is met when the first amount is more than a third threshold amount (e.g., $30, $50, or a non-zero amount). Displaying one or more respective activatable user interface elements based on certain sets of conditions being met for the respective activatable user interface elements provides the user with visual feedback that the respective set of conditions has been met, thereby providing improved visual feedback.

In some embodiments, the second set of conditions includes a second threshold minimum condition that is met when the first amount is more than a fourth threshold amount (e.g., $10, $40, or a non-zero amount, different from the third threshold amount). Displaying one or more respective activatable user interface elements based on certain sets of conditions being met for the respective activatable user interface elements provides the user with visual feedback that the respective set of conditions has been met, thereby providing improved visual feedback.

In some embodiments, the first activatable user interface element corresponds to a first type of transaction and the second activatable user interface element corresponds to a second type of transaction and the second set of conditions includes a threshold pending transactions condition that is met when an account logged into the computer system has less than a threshold number (e.g., 10, 15, or a non-zero number of transactions and/or purchases) of concurrent pending (e.g., active, with payments due) transactions of the second type (e.g., with the service provider to which the account is logged into). In some embodiments, the threshold pending transactions condition (and therefore the set of conditions) is not met when the user is currently participating in (e.g., making payments for) more than a threshold number of other concurrent transactions of the second type. For example, the user is limited to participating in a maximum of 10 transactions of the second type at any time. When the user is participating in 10 transactions of the second type, the user cannot participate in an additional transaction of the second type until one of the pending transactions of the second type is full settled (e.g., paid off through payments). Displaying one or more respective activatable user interface elements based on certain sets of conditions being met for the respective activatable user interface elements provides the user with visual feedback that the respective set of conditions has been met, thereby providing improved visual feedback.

In some embodiments, the first activatable user interface element corresponds to a first type of transaction and the second activatable user interface element corresponds to a second type of transaction and the second set of conditions includes a threshold amount pending condition that is met when an account logged into the computer system has less than a threshold amount pending (e.g., $5,000, $1,500, or a non-zero amount) as part of concurrent pending (e.g., active, with payments due) transactions of the second type (e.g., with the service provider to which the account is logged into). In some embodiments, the threshold amount pending condition (and therefore the set of conditions) is not met when the user is currently participating in (e.g., making payments for) other concurrent transactions of the second type with a sum of amounts that exceeds a threshold amount. For example, when the user has performed multiple transactions of the second type that add up to $5,000 total and has paid $1,000 of the $5,000 as part of scheduled payments, the system compares the remaining $4,000 amount pending to the threshold amount. In some embodiments, if the $4,000 amount pending is higher than the threshold amount, the threshold amount pending condition (and therefore the set of conditions) is not met. Displaying one or more respective activatable user interface elements based on certain sets of conditions being met for the respective activatable user interface elements provides the user with visual feedback that the respective set of conditions has been met, thereby providing improved visual feedback.

In some embodiments, in accordance with a determination that the first set of conditions is not met, the computer system displays, via the display generation component, a third user interface element (e.g.,1703aatFIG.17N) (e.g., grayed out version of the first activatable user interface element that is optionally not activatable), different from the first activatable user interface element, without displaying the first activatable user interface element. In some embodiments, in accordance with a determination that the first set of conditions is not met the computer system forgoes displaying the first activatable user interface element without displaying a replacement user interface element (e.g., without displaying the third user interface element). Displaying user interface elements that are visually different based on whether a sets of conditions is met for the respective user interface elements provides the user with visual feedback that the respective set of conditions has not been met, thereby providing improved visual feedback.

In some embodiments, in accordance with a determination that the second set of conditions is not met, the computer system displays, via the display generation component, a fourth user interface element (e.g.,1703datFIG.17C) (e.g., grayed out version of the second activatable user interface element that is optionally not activatable), different from the second activatable user interface element, without displaying the second activatable user interface element. In some embodiments, in accordance with a determination that the second set of conditions is not met the computer system forgoes displaying the second activatable user interface element without displaying a replacement user interface element (e.g., without displaying the fourth user interface element). Displaying user interface elements that are visually different based on whether a sets of conditions is met for the respective user interface elements provides the user with visual feedback that the respective set of conditions has not been met, thereby providing improved visual feedback.

In some embodiments, the first quantity of transactions (e.g., 4 transactions, 6 transactions) occur on a periodic basis (e.g., every 2 weeks for 8 weeks or every 3 weeks for 12 weeks).

In some embodiments, a first transaction of the first quantity of transactions is equal in value to a second transaction of the first quantity of transactions. In some embodiments, each transaction of the first quantity of transactions is equal. For example, the first amount is $400, the first quantity of transactions is 4, and each transaction is for $100 (e.g., collected two weeks for 6 weeks/4 payments. In some embodiments, an initial $100 transaction occurs on the day of the request (e.g., a payment request) corresponding to the transaction for the first amount is received.

In some embodiments, the first quantity of transaction is a predefined quantity of transactions (e.g., always 4 regardless of the first amount (the cost of the purchase)) and the transactions of the first quantity of transactions are scheduled a predefined duration apart (e.g., payments made towards the purchase are always spaced the same duration apart, such as every 2 weeks).

In some embodiments, a frequency of transactions (e.g., every 2 weeks or every 3 weeks) of the first quantity of transactions is different from a frequency of transactions (e.g., every month or every two months) of the second quantity of transactions.

In some embodiments, a duration between transactions of the first quantity of transactions is less than a duration between transactions of the second quantity of transactions.

In some embodiments, the computer system receives one or more user inputs. In some embodiments, in accordance with a determination that the one or more user inputs include selection of the first activatable user interface element, the computer system adds information (e.g., due dates) about the first quantity of transactions in a calendar of the computer system (without adding information about the second quantity of transactions in the calendar). In some embodiments, in accordance with a determination that the one or more user inputs include selection of the second activatable user interface element, the computer system adds transaction information about the second quantity of transactions in the calendar of the computer system (without adding information about the first quantity of transactions in the calendar). Adding information about the transactions to a calendar of the computer system enables the computer system to provide the user with visual feedback about the timing of the transactions scheduled to be automatically performed, thereby providing the user with improved visual feedback.

In some embodiments, the computer system receives one or more user inputs. In some embodiments, in accordance with a determination that the one or more user inputs include selection of the first activatable user interface element, the computer system displays a timeline (e.g., as inFIG.17F) for transactions of the first quantity of transactions. In some embodiments, the computer system displays a timeline that shows when each payment will be due as part of the first quantity of transactions. Displaying a timeline corresponding to the transactions enables the computer system to provide the user with visual feedback about the timing of the transactions to be scheduled to automatically be performed, thereby providing the user with improved visual feedback.

In some embodiments, the computer system displays, via the display generation component, a third activatable user interface element (e.g.,1702a) corresponding to a single transaction and to the first amount. In some embodiments, the third activatable user interface object corresponds to an option to pay for the purchase in full, without making or scheduling multiple installments/transactions.

In some embodiments, the third activatable user interface element is displayed prior to displaying the first activatable user interface element and/or the second activatable user interface element (e.g., as inFIG.17B). In some embodiments, the default option is to pay for the purchase in full and user input is required (e.g., while displaying the third activatable user interface element) to cause display of the first activatable user interface element and/or the second activatable user interface element.

In some embodiments, the computer system receives selection of the first activatable user interface element or the second activatable user interface element. In some embodiments, subsequent to receiving selection of the first activatable user interface element or the second activatable user interface element, the computer system detects selection (e.g.,1707b) of a payment method (e.g., a particular debit card and/or a particular credit card) for performing the respective quantity of transactions.

In some embodiments, the respective quantity of transactions includes an initial transaction (e.g., payment) using the payment method on the day of selection of the payment method and one or more transactions using the payment method on later days.

In some embodiments, respective quantity of transactions are configured to be performed automatically without further user input (e.g., payments for the respective quantity of transactions are configured to be performed). In some embodiments, a user can provide input at the computer system to disable automatically performing transactions of the respective quantity of transactions. In some embodiments, the computer system receives user input and, in response, disable automatic payment of the transactions of the respective quantity of transactions. Automatically performing the transactions without requiring further user inputs reduces the number of inputs needed to perform the transactions.

In some embodiments, the computer system receives selection of the first activatable user interface element or the second activatable user interface element. In some embodiments, subsequent to receiving selection of the first activatable user interface element or the second activatable user interface element, the computer system requests (e.g., from a server and/or generating locally) a one-time-use account number (e.g., based on a selected payment account) for use in a respective transaction. In some embodiments, the computer system generates a one-time-use account (e.g., PAN) and performs an initial transaction of the first or second quantity of transactions. Requesting (and using) a one-time-use account number provides additional security. In the event that the one-time-use account number is compromised, the one-time-use account number will not be useable after the computer system has used the one-time-use account number in a transaction, thereby providing additional security.

In some embodiments, the computer system receives selection of the first activatable user interface element or the second activatable user interface element to initiate a transaction. In some embodiments, subsequent to receiving selection of the first activatable user interface element or the second activatable user interface element, the computer system detects activation (e.g., a single-press or double-press) of a physical input mechanism of the computer system to authorize a payment as part of the transaction. In some embodiment, authorizing the payment also requires biometric (facial, fingerprint, and/or iris) authentication. Detecting activation of a physical input mechanism to authorize the payment provides additional security by requiring an explicit user input before the transaction is performed, thereby improving device security and avoiding unintentional transactions.

In some embodiments, the computer system receives selection of the first activatable user interface element or the second activatable user interface element to initiate a purchase transaction. In some embodiments, subsequent to receiving selection of the first activatable user interface element or the second activatable user interface element and in accordance with determination that a payment for the purchase transaction is due, the computer system displays a notification (e.g.,1710a) indicating a date and/or amount due. In some embodiments, the notification is displayed regardless of whether automatic payments are enabled or disabled. In some embodiments, multiple notifications are displayed for each payment. In some embodiments, a first notification is displayed a week before the payment is due and a second notification is displayed the day the payment is due. Displaying a notification indicating a date and/or amount due provides the user with improved visual feedback about the state of the computer system and when a transaction will be performed.

In some embodiments, the computer system receives selection of (e.g.,1710b) (e.g., tap on) the notification (e.g.,1710a) indicating the date and/or amount due. In some embodiments, in response to receiving selection of the notification, the computer system displays a management user interface corresponding to the purchase transactions. In some embodiments, the management user interface includes details about the purchase transaction, such as other payment due dates, total amount paid, date or original purchase, and the ability to make payments in advance of their due dates. Display a management user interface corresponding to the purchase transaction when selecting the notification allows a user of the computer system to quickly and efficiently access the relevant transaction without needing to traverse a series of menus or searching for the transaction with a recent due date, thereby reducing the number of inputs needed to perform the operation.

FIGS.19A-19Qillustrate example user interfaces for entering a number sequence according to various examples. The user interfaces in these figures are used to illustrate the processes described below, including the process inFIGS.20A-20C.

AtFIG.19A, computer system1900displays user interface1902of a third-party application for accepting payments (e.g., a merchant application to perform a transaction to receive payment for goods selected by a buyer), such as through via short-range communication (e.g., NFC). In some embodiments, computer system1900is a merchant device (e.g., a smart phone of a merchant) used for processing transactions. User interface1902includes information about the good and/or services being purchased, such as groceries and a gift card. User interface1902also includes indication1902aof the total amount of the purchase ($124) and button1902bto initiate a process to collect the payment. AtFIG.19A, computer system1900detects selection of button1902bvia input1948(e.g., via a tap input and/or via a tap and hold input). AtFIG.19A, the computer system is held by a merchant and while displaying interface1902the computer system is unlocked. In some embodiments, computer system1900includes one or more (e.g., some or all) of the features of devices100,300, and/or500.

AtFIG.19B, in response to detecting selection of button1902b, computer system1900displays user interface702(e.g., the same as user interface702atFIG.7H) and activates a wireless communication radio (e.g., an NFC radio for receiving NFC communications) of computer system1900. In some embodiments, user interface702is a part of the operating system that is different from the third-party application. User interface702includes user interface element702aand request element702b. Request element702bindicates the amount that is being requested in the current payment transaction. AtFIG.19B, computer system1900detects payment input1950a. In some embodiments, payment input1950ais received from computer system705(e.g., a buyer's smart phone). Computer system705is tapped and/or moved near (e.g., within communication range of) computer system1900. In particular, computer system705is placed near (e.g., tapped on) space702e, which indicates where a NFC reader or other wireless card reader is located in computer system1900. This allows computer system1900to request data from computer system705, including information about the credit card or bank card being displayed on computer system705as well as other information that computer system1900may use to complete a transaction (e.g., other than a PIN code for the transaction). In some embodiments, payment input1950ais received from a contactless payment card, such as an NFC-enabled contactless payment card, that has been moved near (e.g., within communication range of) computer system1900, rather than from computer system705.

In some embodiments, and as illustrated inFIG.19B, the merchant holding computer system1900has rotated (e.g., dipped the top of) computer system1900down to reveal the display of computer system1900to the buyer who is standing opposite the merchant. After (e.g., in response to) detecting the rotation of computer system1900, computer system1900rotates one or more elements of user interface702, as shown inFIG.7D. This enables the buyer to more easily view and/or read the contents displayed on computer system1900(e.g., the relevant content is not upside-down for the buyer). In some embodiments, one or more elements are not rotated (e.g., time and/or a cancellation option (e.g., “X” button) after (e.g., in response to) detecting the rotation of computer system1900.

In some embodiments, an authentication passcode (e.g., a PIN, a 4-digit code, a 6-digit code, and/or other numeric code) is not needed to proceed with the payment. In response to detecting payment input1950aand in accordance with a determination that an authentication passcode is not needed, computer system displays user interface1914ofFIG.19Q(e.g., without locking computer system1900). Thus, for transactions where an authentication passcode is not needed to proceed with the payment, computer system1900does not display user interface1906, In some embodiments, for transactions where an authentication passcode is not needed to proceed with the payment, the computer system optionally remains unlocked during the transaction process because computer system1900will likely remain in the possession of the merchant (who potentially has sensitive information, such as a home address and/or personal email information, stored on computer system1900).

Some transactions optionally require an authentication passcode (e.g., a PIN, a 4-digit code, a 6-digit code, and/or other numeric code) for the payment to proceed (e.g., that the payment processor uses to authorize a payment). In response to detecting payment input1950aand in accordance with a determination that an authentication passcode is needed, computer system1900displays user interface1906, as illustrated inFIG.19C. User interface1906includes user interface elements for entering an authentication passcode including keypad1906e(e.g., with digits 0-9), backspace affordance1906b, enter affordance1906c, and accessibility affordance1906d. As illustrated inFIG.19C, the various digits of keypad1906eare associated with respective letters of the alphabet. For example, digit 1 (e.g., a button corresponding to the number 1) of keypad1906eis associated with the letters Q and Z. This additional visual feedback allows a user that has selected an authentication passcode based on their corresponding letters to more easily remember and/or enter the authentication passcode using keypad1906e. Thus, one or more digits of keypad1906ecorrespond to various letters of the alphabet (e.g., the button for number 1 corresponds to “QZ,” 2 corresponds to “ABC,” 7 corresponds to “PRS,” and/or 9 corresponds to WXY”). In some embodiments, the digits of keypad1906e, as illustrated inFIG.19C, correspond to different letters than digits of passcode entry interface1912, as illustrated inFIG.19P.

In some embodiments, in response to detecting payment input1950aand in accordance with a determination that an authentication passcode is needed, computer system1900locks computer system1900, as indicated by lock indication1906a. In some embodiments, the merchant holding computer system1900places computer system1900in the hands of the buyer while the buyer enters an authentication passcode. Handing computer system1900to the buyer better enables the buyer to securely enter the authentication passcode without the merchant viewing the authentication passcode being entered. By locking computer system1900, computer system1900is more secure and the buyer is limited from accessing potentially sensitive information, such as a home address and/or personal email information, stored on computer system1900.

Keypad1906e, backspace affordance1906b, and enter affordance1906ccannot be used to unlock computer system1900. In some embodiments, user interface1906does not include lock indication1906, though computer system1900remains locked while user interface1906is displayed. In some embodiments, the merchant modifies the settings of the third-party application so that computer system1900does not lock when an authentication passcode is needed for the payment to proceed. Accordingly, the merchant can specify whether and/or which certain applications used to initiate the display of user interface702(shown inFIG.7B) should cause the computer system to be locked upon display of keypad1906e.

AtFIG.19D, computer system1900has been handed to the buyer and the buyer has rotated computer system1900and, as a result, computer system1900rotates user interface1906so that user interface1906is in an unrotated orientation. In some embodiments, the merchant holding computer system1900does not rotate (e.g., dips the top of) computer system1900down to reveal the display to a buyer who is standing opposite the merchant, and user interface1906is displayed in an unrotated orientation as seen inFIG.19D. In some embodiments, a user (e.g., the buyer) enters an authentication passcode via user interface1906, such as by tapping on a sequence of digits of keypad1906e. In response to detecting user inputs1950band1950c(e.g., tap inputs and/or tap and hold inputs) corresponding to digit 1 of keypad1906eand digit 5 of keypad1906erespectively, the two digits of the authentication passcode are entered into the computer system. These two entered digits are indicated by digit indicator1906f(e.g., two dots indicating that two digits have been received). Digit indicator1906fdoes not indicate the value of the entered digits. Optionally, the user continues to enter digits and when all digits have been entered, the user selects enter affordance1906cto indicate that entry of the authentication passcode is complete. Optionally, the user selects backspace affordance1906bto clear the most recently entered digit. In response to receiving selection of affordance1906cto indicate that entry of the authentication passcode is complete, computer system transitions (e.g., if computer system1900is locked) to a process to unlock computer system1900, such as by displaying user interface1910ofFIG.19M.

AtFIG.19E, user interface1906is displayed. Optionally, the buyer or the merchant selects accessibility affordance1906dif a buyer is visually impaired and/or has difficultly entering an authentication passcode using user interface1906. Computer system1900detects user input1950d, which corresponds to a selection of accessibility affordance1906d.

AtFIG.19F, after (e.g., in response to) user input1950d, user interface1908is displayed. Thus, rather than using keypad1906e, which uses user inputs that target the various digits of keypad1906e, computer system transitions to user interface1908, which does not include keypad1906e, does not include buttons or keys corresponding to numbers and/or letters, and does not include an enter or backspace button. When computer system1900displays user interface1908, the computer system outputs audio instructions1908a, which describe the process and/or provide instructions for a user (e.g., the buyer) to input digits of an authentication passcode using user interface1908. User interface1908also optionally includes instructions1908d, which describe the process and/or provide instructions for the user to input digits of an authentication passcode using user interface1908. In some embodiments, a digit is entered when a set of tap gestures is detected (e.g., at a touch-sensitive surface and/or at a touchscreen) followed by a pause (e.g., of a predetermined duration) in detecting inputs (e.g., at a touch-sensitive surface and/or at a touchscreen) which demarks the end of the set of tap gestures at (e.g., on the display of) computer system1900. Optionally, a user enters a completed authentication passcode using a swipe gesture (e.g., after entering a plurality of digits, the user provides a swipe gesture), clears the most recently entered digit using a long press gesture, and/or clears all entered digits using two long press gestures.

In some embodiments, user interface1908includes lock indication1908b. As described in relation toFIG.19C, computer system1900optionally locks after detecting payment input1950a. Inputs received via user interface1908will not unlock computer system1900. User interface1908includes accessibility affordance1908cthat, when activated, causes computer system1900to cancel entry of an authentication passcode using user interface1908and return to displaying user interface1906.

AtFIG.19G, a first digit of an authentication passcode is being entered by the buyer. Computer system1900detects four user inputs in sequence:1950e,1950f,1950g, and1950h(e.g., tap inputs and/or tap and hold inputs). User inputs1950e,1950f,1950g, and1950hare not a single four-finger input, but four inputs that are detected one after the other. AtFIG.19H, after detecting user inputs1950e,1950f,1950g, and1950h, computer system1900does not detect additional inputs for a length of time that is more than a predetermined duration. In some embodiments the predetermined duration is 1 second, 2 seconds, 5 seconds, or 10 seconds.

AtFIG.19Iafter detecting user inputs1950e,1950f,1950g, and1950hand not detecting additional input for the predetermined duration, the first digit of the authentication passcode is entered, and is indicated by digit indication1908e. Computer system1900detected four inputs (e.g., four tap inputs) before not detecting additional inputs for the predetermined period of time, and therefore a “4” is entered as the first digit of the authentication passcode. After (e.g., in response to) entering the first digit of the authentication passcode, computer system1900outputs alert1908f(e.g., an audio and/or haptic alert). Alert1908findicates that a digit has been entered but does not indicate the value of digit entered (e.g., alert1908fdoes not announce the number “four” nor does it vibrate four times to indicate the value of the entered digit). In some embodiments alert1908fincludes a single vibration and/or a single chime. In some embodiments alert1908findicates which digit has been entered (e.g., after the first digit alert1908fincludes a single vibration and after the second digit1908fincludes two vibrations).

AtFIG.19J, computer system detects user inputs1950i,1950j, and1950k(e.g., tap inputs and/or tap and hold inputs). User inputs1950i,1950j, and1950kare inputs detected in sequence, one after another other (e.g.,1950i,1950j, and1950kare not a three finger input detected concurrently). After detecting user inputs1950i,1950j, and1950k, computer system1900does not detect additional input for a length of time that is more than the predetermined duration. In some embodiments the predetermined duration is 1 second, 2 seconds, 5 seconds, or 10 seconds. After detecting user inputs1950i,1950j, and1950kand not detecting additional input for a length of time, the second digit of the authentication passcode is entered. Computer system1900detects three inputs (e.g., three tap inputs) before not detecting additional inputs for the predetermined period of time, and therefore a “3” is entered as the second digit of the authentication passcode. After (e.g., in response to) entering the second digit, computer system1900outputs alert1908f(e.g., an audio and/or haptic alert).

AtFIG.19K, digit indication1908eindicates that two digits have been entered. AtFIG.19K, the buyer realizes a mistake was made while entering the authentication passcode and provides user input1950l. The computer system detects user input1950l. In some embodiments user input1950lis a long press gesture (e.g., a tap and hold gesture), a swipe gesture in a first direction, and/or a multi-finger swipe gesture in a first direction. After (e.g., in response to) detecting user input1950lcomputer system1900clears the second entered digit and displays user interfaced1908as shown inFIG.19I. In some embodiments user input1950lis two long press gestures, a swipe gesture in a second direction (e.g., different from the first direction), and/or a multi-finger swipe gesture in a second direction and, in response to detecting user input1950l, computer system1900clears all entered digits and computer system displays user interface1908as shown inFIG.19H.

AtFIG.19Lthe buyer has entered the buyer's complete authentication passcode (e.g., using the same process described when entering the first and second digits) and wishes to submit (e.g., via user input1950m) the authentication passcode for verification. Computer system1900detects user input1950m. In some embodiments, user input1950mis a swipe gesture in a third direction (e.g., different from the first and second directions), and/or a multi-finger swipe gesture in a third direction. After (e.g., in response to) detecting user input1950m, computer system1900submits the authentication passcode for verification to the third-party application and/or to a processing service.

AtFIG.19M, after (e.g., in response to) detecting user input1950mand, optionally, after submitting the authentication passcode for verification, computer system1900initiates a process to unlock computer system1900, such as by displaying user interface1910. User interface1910includes prompt1910a, which describes that the computer system is locked and requires an authentication input (e.g., biometric data and/or a passcode) to unlock computer system1900and, optionally, complete the transaction. User interface1910includes unlock button1910b. In some embodiments, in response to detecting an input on unlock button1910bcomputer system1900displays user interface1912, which is depicted inFIG.19P.

AtFIG.19Ncomputer system1900detects biometric data (e.g., face, iris, and/or fingerprint data) and displays biometric authentication user interface1910c. If the biometric data does not match an authorized user, computer system1900displays failure user interface1910d, as shown inFIG.19O. AtFIG.19O, computer system displays authentication failure message1910d. Optionally, the user (e.g., the merchant) reattempts to unlock computer system1900using biometric authentication or uses a passcode. If biometric data matches an authorized user, computer system1900is unlocked and displays user interface1914as shown inFIG.19Q.

AtFIG.19P, user interface1912is displayed (e.g., in response to multiple fails biometric authentications and/or selection of unlock button1910b). User interface1912is used to unlock computer system1900and includes passcode entry interface1912awhich includes buttons corresponding to digits 0-9, but optionally does not include an enter, backspace, and/or clear button. In some embodiments, a backspace button is displayed as part of passcode entry interface1912aonce one or more digits are entered. The numbers buttons of passcode entry interface1912acorrespond to letters, however some numbers correspond to different letters than the numbers of keypad1906(e.g., 1 corresponds to no letters, 7 corresponds to “PQRS”, and/or 9 corresponds to “WXYZ”). If the entered passcode matches an authorized passcode, computer system1900is unlocked and displays user interface1914. In some embodiments, passcode entry interface1912ais visually different from keypad1906e. In some embodiments, passcode entry interface1912ahas a first color background and keypad1906ehas a second color, different from the first color, background. In some embodiments, passcode entry interface1912ahas third color keys and keypad1906ehas fourth color, different from the third color, keys. In some embodiments, passcode entry interface1912ahas fifth color text in the keys and keypad1906ehas sixth color, different from the fifth color, text in the keys. In some embodiments, user interface1912indicates (e.g., using circles that are not filled in) how many digit should be entered (e.g., because computer system1900is aware of how many digits the passcode is), while user interface1906(e.g., atFIGS.19C and19D) does not indicate how many digits should be entered (e.g., because the authentication passcode may have a variable number of digits that computer system1900does not have access to).

AtFIG.19Q, in response to receiving a valid passcode, computer system1900is unlocked and displays user interface1914of the third-party application. User interface1914includes indication1914aof the total amount of the purchase ($124) and buttons1914bto select the type of receipt sent to the buyer (e.g., email, text message, and/or no receipt). Unlocking computer system1900is not based on the digits entered using user interfaces1906and/or1908are not used.

AtFIG.19R, computer system1900displays user interface1916of an application for a secure operation (e.g., a file transfer, a request for access to wireless network, and/or opening a secured file). Computer system1900detects user input1950n(e.g., an NFC input) which corresponds to a request to begin the secure operation. In some embodiments, in response to detecting user input1950n, computer system1900locks. AtFIG.19S, in response to detecting user input1950n, computer system1900displays user interface1918including keypad1918a, which includes buttons corresponding to numbers and/or letters for entering an authentication passcode. Optionally a user inputs an authentication passcode using keypad1918a, or if a user is visually impaired, optionally selects accessibility options1918bvia user input1950o(e.g., a tap input).

AtFIG.19T, in response to detecting user input1950o, computer system1900displays user interface1920. User interface1920does not include buttons corresponding to numbers and/or letters. Computer system1900detects four user inputs in sequence:1950p,1950q,1950r, and1950s(e.g., tap inputs and/or tap and hold inputs) and after detecting the user inputs computer system1900does not detect additional inputs for a length of time that is more than a predetermined duration. In response to not detecting additional input for a length of time a digit of the authentication passcode is entered. Optionally a user repeats this method to enter additional authentication passcode digits.

AtFIG.19U, after (e.g., in response to) computer system1900detects a completed entered authentication passcode via user interface1918or user interface1920, computer system1900initiates a process to unlock computer system1900, such as by displaying user interface1922which includes prompt1924a, which describes that the computer system is locked and requires an authentication input (e.g., biometric data and/or passcode) to unlock computer system1900and, optionally, complete the secure operation. Computer system1900detects biometric data (e.g., face, iris, and/or fingerprint data) and displays biometric authentication user interface1924c.

As described below, method2000provides an intuitive way for entering a numeric sequence using a computer system. The method reduces the cognitive burden on a user for entering a numeric sequence using a computer system, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to enter a numeric sequence using a computer system faster and more efficiently conserves power and increases the time between battery charges.

FIG.20Ais a flow diagram illustrating a method for entering a numeric sequence using a computer system (e.g.,1900) in accordance with some embodiments. Method2000is performed at computer system (e.g.,1900) (e.g., a smartwatch, a wearable electronic device, a smartphone, a desktop computer, a laptop, and/or a tablet) that is in communication with a display generation component (e.g., a display controller and/or a touch-sensitive display system) and with one or more input devices (e.g., a button, a rotatable input mechanism, a speaker, a camera, a motion detector (e.g., an accelerometer and/or gyroscope), and/or a touch-sensitive surface). Some operations in method2000are optionally, combined, the orders of some operations are, optionally, changed, and some operations are, optionally omitted.

As described, method2000provides an intuitive way for entering a numeric sequence using a computer system (e.g.,1900). The method reduces the cognitive burden on a user for entering a numeric sequence using a computer system, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to for entering a numeric sequence using a computer system faster and more efficiently conserves power and increases the time between battery charges.

The computer system (e.g.,1900) detects (2002), via the one or more input devices, a first user input (e.g.,1950dand/or19500) (e.g., activation of a selectable user interface object, a press of a button, a press or rotation of the rotatable input mechanism, and/or a touch gesture on a touch-sensitive surface). In some embodiments, the first user input corresponds to a selection of a selectable user interface object that is concurrently displayed with a numeric keypad (e.g.,1906dand/or1918b). In some embodiments, selection of the selectable user interface object corresponds to a request to initiate an accessibility mode. In response to detecting the first user input, the computer system displays (2004), via the display generation component, a numeric entry user interface (e.g.,1908and/or1920) (e.g., a user interface that allows a user to input numeric digits). In some embodiments, the numeric entry user interface does not display a numeric keypad (e.g., the number entry user interface does not include selectable digits 0-9, an enter affordance, a cancel affordance, and/or a clear affordance). While displaying the numeric entry user interface, the computer system detects (2006), via the one or more input devices, a second user input that includes a first set of one or more gestures (e.g.,1950e,1950f,1950g,1950h, and/or1950p,1950q,1950r,1950s) (e.g., one or more tap inputs and/or swipe inputs on the one or more input devices (e.g., a touch-sensitive surface)). In some embodiments, the first set of one or more gestures are detected within a predetermined time period. In some embodiments, a second gesture of the first set of the one or more gestures is detected within a predetermined time period after an initial gesture of the first set of the one or more gestures is detected. In response to detecting a completion of (e.g., via a pause in input or an input that indicates completion) (e.g., as illustrated inFIG.19H) the first set of one or more gestures, the computer system enters (2008) (e.g., translating the first of one or more gesture into) a numeric digit (e.g., a numeral between 0-9, inclusive) of a numeric sequence, the numeric digit based on a quantity of gestures in the first set of one or more gestures (e.g., the quantity of gestures in the first set of one or more gestures determines the entered numeric digit (e.g., a set of one gesture corresponds to the digit “1”, a set of four gestures corresponds to the digit “4”, a set of ten gestures corresponds to the digit “0”)). Displaying the numeric entry user interface and entering a digit in response to a set of gestures provides the user with an alternative method of entering a numeric digit based on a quantity of gestures and provides the user with a method of entering a numeric digit that does not require performing a touch gesture in a particular location on the display, thereby providing the user with additional control options without cluttering the user interface with additional displayed controls and enables a vision-impaired user to provide numeric inputs.

In some embodiments, the pause in input (e.g., as illustrated inFIG.19H) is determined to indicate a completion of entry based on the pause being for greater than a predetermined duration. In some embodiments, detecting completion of the first set of one or more gestures includes detecting a lack of inputs for a predetermined duration. In some embodiments, detecting completion of the first set of one or more gestures includes detecting a specific gesture (e.g.,1950mand/or1950l) (e.g., a swipe up gesture and/or a long press gesture) that corresponds to completion of the input. In some embodiments, the quantity of gestures of the set of one or more gestures is determined such that each input that that contacts a touch-sensitive surface (of the one or more input devices) and then ceases to contact the touch-sensitive surface is considered as one gesture (e.g., a tap input is considered as one gesture, a swipe input is considered as one gesture, a double-tap input is considered as two gestures, and/or a triple-tap input is considered as three gestures).

In some embodiments, while displaying, via the display generation component, the numeric entry user interface, the computer system (e.g.,1900) detects, via the one or more input devices (e.g., a button, a rotatable input mechanism, a speaker, a camera, a motion detector (e.g., an accelerometer and/or gyroscope), and/or a touch-sensitive surface), a third user input that includes a second set of one or gestures (e.g.,1950i1950j, and1950k) (e.g., one or more tap inputs and/or swipe inputs on the one or more input devices (e.g., a touch-sensitive surface)). In some embodiments, the second set of one or more gestures are detected within a predetermined time period. In some embodiments, a second gesture of the second set of the one or more gestures is detected within a predetermined time period after an initial gesture of the second set of the one or more gestures is detected. In response to detecting a completion of (e.g., via a pause in input or an input that indicates completion) the second set of one or more gestures, the computer system enters a second numeric digit (e.g., a numeral between 0-9, inclusive) of the numeric sequence, the second numeric digit based on a quantity of gestures in the second set of one or more gestures (e.g., the quantity of gestures in the second set of one or more gestures determines the entered numeric digit (e.g., a set of one gesture corresponds to the digit “1”, a set of four gestures corresponds to the digit “4”, a set of ten gestures corresponds to the digit “0”)). Entering a second numeric digit in response to detecting a completion of the second set of one or more gestures provides the user with an alternative method of entering a numeric digit based on a quantity of gestures and provides the user with a method of entering a numeric digit that does not require performing a touch gesture in a particular location on the display, thereby providing the user with additional control options without cluttering the UI with additional displayed controls and enables a vision impaired user to provide numeric inputs.

In some embodiments, displaying, via the display generation component, the numeric entry user interface (e.g.,1908) (e.g., a user interface that allows a user to input numeric digits) does not include displaying a numeric keypad (e.g.,1906e) (e.g., with displayed selectable buttons corresponding to digits 0-9). Displaying the numeric entry user interface without a numeric keypad provides the user with a method of entering a numeric digit that does not require performing a touch gesture in a particular location on the display, thereby providing the user with additional control options without cluttering the UI with additional displayed controls and enables a vision impaired user to provide numeric inputs. In some embodiments, a numeric keypad is not displayed concurrently with the numeric entry user interface. In some embodiments, the numeric entry user interface does not include location-specific entry locations for entering numeric digits (e.g., on the display generation component or on a touch-sensitive surface). In some embodiments, the computer system (e.g.,1900) detects entry of a first digit (e.g., “5”) at the same location on a touch-sensitive surface as entry of a second digit that is different from the first digit (e.g., “3”).

In some embodiments, the computer system includes one or more output devices (e.g., a tactile generation device and/or an audio output device). In response to detecting the completion (e.g., as illustrated inFIG.19H) of (e.g., via a pause in input or an input that indicates completion) the first set of one or more gestures (e.g.,1950e,1950f,1950g,1950h) (and, optionally, while displaying, via the display generation component, the numeric entry user interface (e.g.,1908) (e.g., a user interface that allows a user to input numeric digits)), the computer system (e.g.,1900) outputs, via the one or more output devices, a non-visual alert (e.g.,1908f) (e.g., an audio and/or a tactile alert). In some embodiments, the same alert is output in response to multiple (e.g., after the first and the second and/or after every) completions of sets of gestures for numeric digit entries. Outputting a non-visual alert in response to detecting completion of the first set of one or more gestures provides the user with feedback that the digit has been entered and further inputs may now be received, thereby providing the user with improved feedback.

In some embodiments, the non-visual alert (e.g.,1908f) does not correspond to a value of the numeric digit (e.g., the non-visual alert does not indicate what value the computer system (e.g.,1900) received/entered). Outputting a non-visual alert after entering the numeric digit of the numeric sequence wherein the alert does not correspond to a value of the numeric digit provides the user with feedback that the digit has been entered without indicating to other people present the value of the numeric digit, thereby providing the user with improved feedback with increased security. In some embodiments, outputting the non-visual alert indicates to the user that a digit was entered by the computer system. In some embodiments, the alert indicates to the user which digit was entered (e.g., how many digits have been entered, and/or the first entered digit may be followed by an alert that includes one auditory chime and/or one haptic vibration and the second recorded digit may be followed by an alert that includes two auditory chimes and/or two haptic vibrations.).

In some embodiments, the computer system (e.g.,1900) includes one or more output devices (e.g., a tactile generation device and/or an audio output device). In response to detecting, via the one or more input devices, the first user input, the computer system outputs audio instructions (e.g.,1908a). Outputting audio instructions provides the user with understanding of how to use the numeric entry user interface without the user needing to read or see the instructions, and therefore without the need to display the instructions, thereby providing the user with improved feedback on how to control the computer system. In some embodiments the audio instructions describe how to interact with the numeric entry user interface (e.g.,1908) (e.g., the computer system will detect a set of taps (e.g.,1950e,1950f,1950g,1950h) followed by a pause (e.g., as illustrated inFIG.19H) to enter a digit, a first touch gesture (e.g., a swipe in a first direction (e.g.,1950m)) will enter the numeric sequence, and/or a second touch gesture (e.g.,1950l) (e.g., a swipe gesture in a second direction) will clear a digit.)

In some embodiments, in response to detecting completion (e.g., via a pause in input (e.g., as illustrated inFIG.19H) or an input that indicates completion) of the first set of one or more gestures, the computer system (e.g.,1900) displays, via the display generation component, an indication that a numeric digit has been entered (1908e). Displaying an indication that a digit has been entered provides the user with feedback that a set of gestures (e.g.,1950e,1950f,1950g, and1950h) has been received and indicates that the computer system is ready to receive additional input, thereby providing the user with improved visual feedback. In some embodiments, the indication does not correspond to the value of the entered digit. In some embodiments, the indication is a black dot (e.g., one black dot for one digit entered and/or two black dots for two digits entered).

In some embodiments, subsequent to entering a one or more (e.g., one or a plurality of) numeric digits of the numeric sequence, the computer system (e.g.,1900) detects, via the one or more input devices, a fourth user input (e.g.,1950m) (e.g., one or more tap inputs and/or swipe inputs on the one or more input devices (e.g., a touch-sensitive surface)). In response to detecting the fourth user input and in accordance with a determination that the fourth user input is of a first type of input (e.g., a type indicating completion (e.g., a swipe input (e.g., swipe up and/or swipe down), a press-and-hold input, and/or a multi-finger input) of the numeric sequence), the computer system enters the numeric sequence (e.g., submitting the numeric sequence for processing and/or no longer enabling the user to enter additional numeric digits). In response to detecting the fourth user input and in accordance with a determination that the fourth user input is not of the first type of input, forgoing entering the numeric sequence (e.g., enabling the user to enter additional numeric digits). Entering the numeric sequence in response to detecting the fourth user input provides the user with a simple way to enter the sequence without the need to display additional user interface elements, thereby providing additional control options without cluttering the user interface with additional displayed controls. In some embodiments the fourth user input is a multi-contact tap and/or swipe input (e.g., a tap gesture with one or more fingers and/or a swipe gesture with one or more fingers). In some embodiments the fourth user input is a tap and hold (e.g., a long press) gesture.

In some embodiments, the first type of input indicating completion of the numeric sequence is a swipe gesture (e.g.,1950m) (e.g., in a particular direction, regardless of the direction, length, and/or duration of the swipe gesture). Entering the numeric sequence in response to detecting a swipe gesture provides the user with a simple way to enter the sequence without the need to display additional user interface elements, thereby providing additional control options without cluttering the user interface. In some embodiments the type of input indicating completion of the numeric sequence is a swipe gesture that includes one or more fingers. In some embodiments the type of input indicating completion of the numeric sequence is a swipe gesture in a first direction and/or a second direction that is different from the first direction.

In some embodiments, detecting the completion of the first set of one or more gestures (e.g.,1950e,1950h,1950g,1950h) includes detecting that no input is detected (e.g., as illustrated inFIG.19H) (e.g., no input corresponding to the numeric entry user interface is detected and/or no input (or no tap input) is detected on a touch-sensitive surface or touch screen of the computer system (e.g.,1900)) for a predetermined period of time after detecting the first set of one or more gestures (e.g., a pause in detecting input after detecting the last gesture of the first set of one or more gestures). Completing the first set of one or more gestures in response to detecting no input for a predetermined period of time provides the user with a simple way to signal that all gestures of a set have been entered and the corresponding digit may now be entered without requiring the user to perform additional input and/or gestures, thereby reducing the number of inputs needed to perform an operation. In some embodiments, the predetermined period of time is 1 second, 3 seconds, 5 seconds, or 8 seconds. In some embodiments, the computer system detects no input for a period of time, and in response to detecting no input for the period of time: in accordance with a determination that the period of time exceeds the predetermined period of time (e.g., a timeout threshold) considers a respective set of one or more gestures complete (e.g., enters a numeric value based on the number of tap inputs received after the last entry and up until the predetermined period of time was exceeded) and in accordance with a determination that the period of time does not exceed the predetermined period of time (e.g., the timeout threshold) does not consider the respective set of one or more gestures complete and continues to wait for additional gestures.

In some embodiments, while displaying, via the display generation component, the numeric entry user interface (e.g.,1908) (e.g., a user interface that allows a user to input numeric digits) the computer system (e.g.,1900) detects, via the one or more input devices, a fifth user input (e.g.,1950l) (e.g., a press and hold gesture, one or more tap inputs, and/or swipe inputs on the one or more input devices (e.g., a touch-sensitive surface)). In response to detecting the fifth user input, the computer system clears a most recently entered numeric digit of the numeric sequence (e.g., the most recently entered digit of the numeric sequence is deleted, optionally without deleting any other previously entered digits or with deleting all previously entered digits). Clearing the last entered numeric digit in response to detecting the fifth user input provides the user with a simple way to clear a digit without needing to provide additional displayed controls, thereby providing additional control options without cluttering the user interface with additional displayed controls. In some embodiments, the fifth user input is a swipe gesture that includes one or more fingers. In some embodiments, the fifth user input is a swipe gesture in a first direction. In some embodiments, the fifth user input is a swipe gesture in a second direction. In some embodiments, the fifth user input is a press and hold gesture. In some embodiments, in response to detecting the fifth user input: in accordance with a determination that the fifth user input is of a second type of user input (e.g., a long press or swipe left), clearing the most recently entered numeric digit of the numeric sequence without deleting any other previously entered numeric digits of the numeric sequences, and in accordance with a determination that the fifth user input is of a third type of user input (e.g., a double-long press or a two finger swipe) different from the second type of user input, clearing a plurality of (e.g., two of or all of) the numeric digits of the numeric sequence.

In some embodiments, the fifth user input (e.g.,1950l) includes (or is) a long press input (e.g., a tap and hold input with one or more fingers and/or swipe and hold input with one or more fingers on the one or more input devices (e.g., a touch-sensitive surface)). Clearing the last entered numeric digit in response to detecting a long press input provides the user with a simple way to clear a numeric digit without needing to provide additional displayed controls, thereby providing additional control options without cluttering the user interface with additional displayed controls.

In some embodiments, the fifth user input (e.g.,1950l) includes (or is) two long press inputs (e.g., a tap and hold input followed by a second tap and hold input and/or a swipe and hold input with one or more fingers on the one or more input devices (e.g., a touch-sensitive surface) followed by a second swipe and hold input with one or more fingers). In response to detecting the fifth user input, the computer system (e.g.,1900) clears a plurality of (e.g., two of or all of) the numeric digits of the numeric sequence. Clearing all entered numeric digits in response to detecting two long press input provides the user with a simple way to clear all entered numeric digits without needing to provide additional displayed controls, thereby providing additional control options without cluttering the user interface with additional displayed controls.

In some embodiments, the first user input (e.g.,1950d) is detected while the computer system (e.g.,1900) displays a numeric keypad (e.g.,1906e) for entering the numeric sequence (e.g., the numeric keypad includes selectable digits 0-9, an enter affordance, a cancel affordance, and/or a clear affordance). Providing a mechanism by which a user of the computer system can access a user interface for entering the numeric sequence without using a numeric keypad (e.g.,1908) provides the user (e.g., a vision impaired user) with the ability to interact with the computer system without relying on displayed content, thereby improving the man-machine interface. In some embodiments, in response to detecting the first user input, the computer system ceases to display the numeric keypad.

In some embodiments, subsequent to entering the numeric digit of the numeric sequence (e.g., subsequent to entering a plurality of numeric digits), the computer system (e.g.,1900) detects, via the one or more input devices, a user input indicating completion of the numeric sequence (e.g.,1950m). In response to receiving the user input indicating completion of the numeric sequence and in accordance with a determination that the quantity of numeric digits of the numeric sequence is within a predefined range (e.g., between 4 and 6 (inclusive), between 4 and 8 (inclusive), or between 6 and 10 (inclusive)), the computer system enters the numeric sequence (e.g., submitting the numeric sequence for processing and/or no longer enabling the user to enter additional numeric digits). In response to receiving the user input indicating completion of the numeric sequence and in accordance with a determination that the quantity of numeric digits of the numeric sequence is not within the predefined range (e.g., between 4 and 6 (inclusive), between 4 and 8 (inclusive), or between 6 and 10 (inclusive)), the computer system forgoes entering the numeric sequence (and, optionally, indicating (e.g., via audio, haptic, and or display) the error to the user).

In some embodiments, the numeric digit entered is not based on a location of the first set of one or more gestures (e.g., the value of the numeric digit is determined by the number of gestures in the first set of one or more gestures, not on where the location of the gestures occurred on the display generation component and/or the one or more input devices (e.g., a touch-sensitive surface)). Determining numeric digit independently of the location of the first set of one more gestures provides the user with a simple way to input digits without requiring a gesture be performed on a specific location on the touch-sensitive surface or touchscreen and provides the user with a method of entering digits without needing to view the display, thereby providing additional control options without cluttering the user interface with additional display controls. In some embodiments, the numeric digit entered is not based on locations corresponding to digits on a keypad.

In some embodiments, the numeric digit is not based on a duration of one or more gestures of the first set of one or more gestures (e.g., the value of the numeric digit is determined by the number of gestures in the first set of one or more gestures, not on whether some of the gestures are longer or shorter than others). Determining numeric digit independently of the duration of the first set of one more gestures provides the user with a simple way to input digits without requiring a user to perform gestures of a specific duration and provides the user with a method of entering digits without needing to view the display, thereby providing additional control options without cluttering the user interface with additional display controls. In some embodiments, the numeric digit is not based on morse code.

In some embodiments, the computer system (e.g.,1900) is in a locked state while the numeric entry user interface (e.g.,1908) is displayed and entry of the numeric sequence using the numeric entry user interface cannot unlock the computer system. Maintaining the computer system in a locked state while the numeric entry user interface is displayed increases the security of the computer system by allowing a non-owner of the computer system to enter the numeric sequence without risking the non-owner accessing unauthorized information on the computer system. In some embodiments, user inputs cannot navigate away from the numeric entry user interface and/or access other functions of the computer system unless the computer system first receives authentication (e.g., a passcode authentication or biometric authentication) to unlock the computer system. In some embodiments, authentication to unlock the computer system is not based on (does not use) the numeric sequence entered using the numeric entry user interface. In some embodiments, the computer system is in a locked state or an unlocked state. In the locked state, the computer system is powered on and operational but is prevented from performing a predefined set of operations in response to user input. The predefined set of operations optionally includes navigation between user interfaces, activation or deactivation of a predefined set of functions, and activation or deactivation of certain applications. The locked state can be used to prevent unintentional or unauthorized use of some functionality of the computer system or activation or deactivation of some functions on the computer system. In some embodiments, in the unlocked state, the computer system is power on and operational and is not prevented from performing at least a portion of the predefined set of operations that cannot be performed while in the locked state. When the computer system is in the locked state, the computer system is said to be locked. When the computer system is in the unlocked state, the computer is said to be unlocked. In some embodiments, the computer system in the locked state optionally responds to a limited set of user inputs, including input that corresponds to an attempt to transition the computer system to the unlocked state or input that corresponds to powering the computer system off.

Note that details of the processes described above with respect to method2000(e.g.,FIG.20A) are also applicable in an analogous manner to the methods described below/above. For example, method800,900,1200,1500,1800,2010, and2300optionally includes one or more of the characteristics of the various methods described above with reference to method2000. For example, method2000optionally includes one or more various methods described above with reference to method800. For example, during numeric sequence entry computer system1900optionally rotates one of user interface elements in response to detecting movement of computer system1900as described in method800. As another example, method2000optionally includes one or more various methods described above with reference to method900. For example, computer system1900optionally requires entry of a numeric sequence in response to initiating a transaction request as described in method900. As another example, method2000optionally includes one or more various methods described above with reference to method1200. For example, computer system1900optionally requires entry of a numeric sequence in response to detecting a sign-in of a user account as described in method1200. As another example, method2000optionally includes one or more various methods described above with reference to method1500. For example, computer system1900optionally requires entry of a numeric sequence in response to receiving a request to associate a transfer amount with an account as described in method1500. As another example, method2000optionally includes one or more various methods described above with reference to method1800. For example, computer system1900optionally requires entry of a numeric sequence in response to receiving a request corresponding to a transaction for a first amount as described in method1800. As another example, method2000optionally includes one or more of the various methods described below with reference to method2010. For example, computer system1900optionally locks during entry of a numeric sequence as described in method2010. As another example, method2000optionally includes one or more various methods described below with reference to method2300. For example, computer system1900optionally, in response to entry of a numeric sequence, displays a quantity of a first type of user interface elements as described in method2300. For brevity, these details are not repeated below.

As described below, method2010provides an intuitive way for locking a computer system while a numeric sequence is entered using a computer system. The method reduces the cognitive burden on a user for locking a computer system while a numeric sequence is entered using a computer system, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to lock a computer system while a numeric sequence is entered using a computer system faster and more efficiently conserves power and increases the time between battery charges.

FIGS.20B-20Care a flow diagram illustrating a method for locking a computer system while a numeric sequence is entered using a computer system in accordance with some embodiments. Method2010is performed at computer system1900(e.g., a smartwatch, a wearable electronic device, a smartphone, a desktop computer, a laptop, a head mounted device (e.g., a head mounted augmented reality and/or extended reality device), and/or a tablet) that is in communication with a display generation component (e.g., a display controller, a head mounted display system, and/or a touch-sensitive display system) and with one or more input devices (e.g., a button, a rotatable input mechanism, a speaker, one or more cameras (e.g., infrared and/or visible light cameras), a motion detector (e.g., an accelerometer and/or gyroscope), and/or a touch-sensitive surface). Some operations in method700are, optionally, combined, the orders of some operations are, optionally, changed, and some operations are, optionally, omitted.

As described below, method2010provides an intuitive way for locking a computer (e.g.,1900) system while a numeric sequence is entered using a computer system. The method reduces the cognitive burden on a user for locking a computer system while a numeric sequence is entered using a computer system thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to for locking a computer system while a numeric sequence is entered using a computer system faster and more efficiently conserves power and increases the time between battery charges.

In method2010, while the computer system (e.g.,1900) is unlocked and while displaying, via the display generation component, a user interface of a first application (e.g.,702,1902, and/or1916) (e.g., a security application and/or a transaction processing application), receiving (2012), via the one or more input devices, a first input (e.g., receiving information via1950aand/or1950n) (e.g., a user input for performing a secure operation, detecting of an external device, and/or near field communication input for a transaction). In some embodiments, the first input includes detecting a payment card within an RF (e.g., a near-field communication) field of the computer system and/or detecting an external device within a predetermined range (e.g.,705) (e.g., distance and/or RF range) of the computer system. In response to receiving the first input (2014), the computer system displays a first numeric keypad (e.g.,1906eand/or1918a) (e.g., of the first application, of a second application different from the first application, of a system application, and/or of an operating system of the computer system). In accordance with a first set of lock conditions being met (e.g., the user has indicated that the device should lock in response to receiving the first input while using the first application), the computer system locks the computer system (2018) (e.g., prevent user navigating away from the transaction numeric keypad). In accordance with the first set of lock conditions not being met, the computer system forgoes locking the computer system (2020). While displaying the first numeric keypad, the computer system receives (2022), via the one or more input devices and using the first numeric keypad, a second input (e.g.,1950b,1950c, and/or input on keys of1918a) (e.g., one or more touch gestures on the touch-sensitive surface at location(s) corresponding to the first numeric keypad displayed via the display generation component) corresponding to a numeric sequence, wherein the computer system does not unlock based on the second input that uses the first numeric keypad regardless of the numeric sequence (e.g., a user input on the first numeric keypad (e.g., a PIN or another number) cannot unlock the device). In some embodiments, the second input is the input of a PIN to proceed with or to complete a transaction (e.g., a secure transaction and/or a payment transaction). Subsequent to receiving the second input and while the computer system is locked, the computer system receives (2024), via the one or more input devices, a third input (e.g., atFIGS.19N and/or19U) (e.g., one or more gestures (e.g., a tap gesture and/or a swipe gesture) on a touch-sensitive surface, and biometric information (e.g., facial information, fingerprint information, and/or iris information) for use for biometric recognition/authentication) that does not use the first numeric keypad (e.g., a passcode (e.g., an alpha-numeric sequence used to unlock a device) on a second numeric keypad and/or the detection of biometric data, such as via a fingerprint sensor, an iris sensor, and/or camera). In some embodiments, the first numeric keypad is not displayed when the third input is received. In response to receiving the third input (2026) and in accordance with a determination, independent of the numeric sequence corresponding to the second input, that the third input matches an enrolled credential (e.g., a stored passcode and/or stored biometric data), the computer system unlocks (2028) the computer system. In response to receiving the third input (2026) and in accordance with a determination, independent of the numeric sequence corresponding to the second input, that the third input does not match an enrolled credential (e.g., a passcode and/or biometric data), the computer system forgoes (2030) unlocking the computer system. Locking the computer system in accordance with a first set of lock conditions being met provides the user with additional security while the numeric sequence is entered without requiring additional input or action on the part of the user, thereby increasing security and performing an operation when a set of conditions has been met without requiring further user input.

In some embodiments, the computer system (e.g.,1900) is in a locked state or an unlocked state. In the locked state, the computer system is powered on and operational but is prevented from performing a predefined set of operations in response to the user input. The predefined set of operations optionally includes navigation between user interfaces, activation or deactivation of a predefined set of functions, and activation or deactivation of certain applications. The locked state can be used to prevent unintentional or unauthorized use of some functionality of the computer system or activation or deactivation of some functions of the computer system. In the unlocked state, the computer system is power on and operational and is not prevented from performing at least a portion of the predefined set of operations that cannot be performed while in the locked state. When the computer system is in the locked state, the computer system is said to be locked. When the computer system is in the unlocked state, the computer is said to be unlocked. In some embodiments, the computer system in the locked state optionally responds to a limited set of user inputs, including input that corresponds to an attempt to transition the computer system to the unlocked state or input that corresponds to powering the computer system off. When the computer system is in the locked state, the computer system is said to be locked.

In some embodiments, the first numeric keypad (e.g.,1906e) is displayed as part of a user interface (e.g.,1906) of a second application (a system application and/or of an operating system of the computer system (e.g.,1900)) that is (optionally) different from the first application. Subsequent to (e.g., in response to) receiving the second input (e.g.,1950b) corresponding to the numeric sequence (e.g., a PIN entry and/or one or more touch gestures on the touch-sensitive surface at location(s) corresponding to the first numeric keypad displayed via the display generation component), the computer system transmits the numeric sequence from the second application to the first application (e.g., a security application and/or a transaction processing application). Passing the numeric sequence from the second application to the first application allows the entering of the numeric sequence to be handled securely and uniformly by the second application without requiring the user to manage multiple applications or inputs, thereby increasing the security of the device.

In some embodiments, subsequent to receiving the second input (e.g.,1950b) (e.g., one or more touch gestures on the touch-sensitive surface at location(s) corresponding to the first numeric keypad displayed via the display generation component), and while the computer system (e.g.,1900) is locked (e.g., the computer system prevents the user navigating away from the transaction numeric keypad), the computer system displays, via the display generation component (e.g., a display controller, a head mounted display system, and/or a touch-sensitive display system), a second numeric keypad (e.g.,1912a), wherein the second numeric keypad is different from the first numeric keypad (e.g., of a second application different from the first application, of a system application, and/or of an operating system of the computer system) (e.g., the first numeric keypad is visually different (e.g., different color and/or different correspondence of letters to numbers) from the second numeric keypad). Receiving the third input includes receiving, using the second numeric keypad (e.g., one or more touch gestures on the touch-sensitive surface at location(s) corresponding to the second numeric keypad displayed via the display generation component), one or more inputs (e.g., one, two, or a plurality of inputs) corresponding to a second numeric sequence. In some embodiments, the second numeric sequence is different from the first numeric sequence. Entering the third input using the second numeric keypad provides the user with visual feedback that the third input will unlock the computer system and further helps differentiate between whether the computer system expects to receive a numeric sequence for the first application or a numeric sequence to unlock the computer system, thereby providing the user with improved visual feedback. In some embodiments, the first numeric keypad includes selectable digits 0-9 (e.g.,1906e), an enter affordance (e.g.,1906c), a cancel affordance, and/or a clear affordance (e.g.,1906b). In some embodiments the selectable digits 0-9 of the first numeric keypad correspond to letters of the alphabet (e.g., each selectable digit corresponds to a set of letters (e.g., numeral 1 corresponds to “Q” and “Z”; numeral 2 corresponds to “A,” “B,” and “C”; and/or numeral 7 corresponds to “P,” “R,” and “S”)). In some embodiments the second numeric keyboard, includes selectable digits 0-9. In some embodiments the second numeric keypad does not include an enter affordance, a cancel affordance, and/or a clear affordance. In some embodiments selectable digits 0-9 of the second numeric keypad correspond to different sets of letters than selectable digits 0-9 of the first numeric keypad (e.g., numeral 1 does not correspond to a set of letters; numeral 2 corresponds to “A,” “B,” and “C”; and/or numeral 7 corresponds to “P,” “Q,” “R,” and “S”).

In some embodiments, the third input is a biometric input (e.g., facial information, fingerprint information, and/or iris information detected via the one or more input devices (e.g., a button, a rotatable input mechanism, one or more cameras (e.g., infrared and/or visible light cameras), a motion detector (e.g., an accelerometer and/or gyroscope), and/or a touch-sensitive surface)).

In some embodiments, the biometric input is a facial input and/or iris input (e.g., facial information and/or iris information (detected via the one or more input devices including a button, a rotatable input mechanism, a speaker, one or more cameras (e.g., infrared and/or visible light cameras), a motion detector (e.g., an accelerometer and/or gyroscope), and/or a touch-sensitive surface)).

In some embodiments, biometric input is a fingerprint input (detected via the one or more input devices including a button, a rotatable input mechanism, one or more cameras (e.g., infrared and/or visible light cameras), and/or a touch-sensitive surface)).

In some embodiments, the first set of lock conditions includes a condition that is met when the first application (e.g., a security application and/or a transaction processing application) is an application of a first type (e.g., the settings of the first application have been set so that the computer system (e.g.,1900) should lock during entry of the numeric sequence while using the first application). Locking the computer system when the first application is an application of a first type provides the user with a way of locking the computer system when transitioning to displaying the first numeric keypad from the application without the need for the user to lock the computer system manually before entering the second input, thereby reducing the number of inputs needed to perform an operation and making the computer system more secure. In some embodiments, the settings of the first application may be set to be of a second type so that the computer system does not lock during entry of the numeric sequence. In some embodiments, the computer system does not lock while using a second application that is of a second type (e.g., the settings of the second application have been set so that the computer system does not lock during entry of the numeric sequence).

In some embodiments, in response to receiving the third input and in accordance with the determination, independent of the numeric sequence corresponding to the second input, that the third input matches the enrolled credential (e.g., a stored passcode and/or stored biometric data) (and subsequent to (e.g., in response to) unlocking the computer system (e.g.,1900)), the computer system displays, via the display generation component (e.g., a display controller, a head mounted display system, and/or a touch-sensitive display system), a second user interface of the first application (e.g.,1914) (e.g., same as or different from the user interface of the first application). Displaying a second user interface of the first application subsequent to unlocking the computer system provides the user with feedback that the computer system is unlocked and further inputs can now be inputted into the computer system, thereby providing the user with improved visual feedback. In some embodiments, in response to receiving the third input and in accordance with the determination, independent of the numeric sequence corresponding to the second input, that the third input does not match the enrolled credential, forgoing displaying the second user interface of the first application.

In some embodiments, while displaying the first numeric keypad (e.g.,1906e) the computer system (e.g.,1900) receives a notification (e.g., of a newly received message or email, of a reminder, of an upcoming calendar event). In response to receiving the notification and in accordance with a determination that the computer system is not locked, displaying, via the display generation component, the notification (e.g., partially overlaid on the first numeric keypad). In accordance with a determination that the computer system is locked, forgoing display of the notification. Forgoing displaying a notification that is received while the computer system is locked and the first numeric keypad remains displayed provides enhanced security for the owner of the computer system because a non-owner using the computer system to enter a PIN using the first numeric keypad would not see the notification, thereby enhancing the security of the computer system. In some embodiments, a notification received while displaying the first numeric keypad is not displayed while the first numeric keypad is displayed, regardless of whether the computer system is locked or unlocked. In some embodiments (when the notification is not displayed while displaying the first numeric keypad), the notification is displayed once the first application is displayed (e.g., concurrently with the second user interface of the first application and/or in response to the computer system being unlocked).

In some embodiments, while displaying, via the display generation component, the first numeric keypad (e.g.,1906e) (and, optionally, one or more other user interface objects), the computer system (e.g.,1900) detects a rotation (e.g., a rotation in a predetermined direction, a rotation above a predetermined threshold, and/or detecting that the computer system is being dipped) of the computer system. In response to detecting the rotation of the computer system, rotating the first numeric keypad (and, optionally, forgoing to rotate the one or more other user interface objects). Rotating the first numeric keypad is response to detecting a rotation of the computer system enables the computer system to allow a secondary user to enter the numeric sequence without requiring the user to manually rotate the orientation of the computer system, thereby reducing the number of inputs needed to perform an operation. In some embodiments the rotation of the computer system includes the computer system been dipped toward a second user (e.g., a customer). In some embodiments, in response to detecting the rotation of the computer system, the first numeric keypad is rotated so that it is not oriented toward a first user (e.g., a merchant and/or owner of the computer system) but is oriented toward the second user (e.g., the customer who needs to enter a PIN using the first numeric keypad). In some embodiments, the orientation of one or more other elements on the display (e.g., an indication of time, an indication of connection to a remote system, and/or an indication of a transactional total) does not rotate in response to detecting the rotation.

In some embodiments the first application is a third-party application. The first application being a third-party application enables the computer system (e.g.,1900) to use the first numeric keypad to collect account information for a third-party application, thereby improving the security of the computer system. In some embodiments, the third-party application is a payment application. In some embodiments, the third-party application is an application that is not provided by the manufacturer of the computer system. In some embodiments, the first numeric keypad is displayed as part of a user interface of a first-party application and/or an operating system application of the computer system.

In some embodiments, the first input is a near-field communication (e.g., a user bringing a second computer system (e.g.,1900) near (e.g., into an RF field of) the first computer system and/or a user bringing a payment card near (e.g., into an RF field of) the first computer system) that includes account credentials (e.g., payment credentials and/or loyalty card credentials). Automatically displaying the first numeric keypad (and, optionally, automatically locking the computer system) when a near-field communication is detected enables the computer system to display the keypad without requiring additional user inputs, thereby reducing the number of user inputs required to perform an operation.

Note that details of the processes described above with respect to method2010(e.g.,FIGS.20B-20C) are also applicable in an analogous manner to the methods described below/above. For example, method800,900,1200,1500,2000, and2300optionally includes one or more of the characteristics of the various methods described above with reference to method2010. For example, method2010optionally includes one or more various methods described above with reference to method800. For example, computer system1900optionally rotates one of user interface elements in response to detecting movement of computer system1900as described in method800. As another example, method2010optionally includes one or more various methods described above with reference to method900. For example, computer system1900optionally locks the computer system in response to initiating a transaction request as described in method900. As another example, method2010optionally includes one or more various methods described above with reference to method1200. For example, computer system1900optionally locks when a first set of provisioning criteria are met as described in method1200. As another example, method2010optionally includes one or more various methods described above with reference to method1500. For example, computer system1900optionally locks in response to receiving user input corresponding to a second for the first user interface element or the second user interface element as described in method1500. As another example, method2010optionally includes one or more various methods described above with reference to method1800. For example, computer system1900optionally locks in response to receiving a request corresponding to a transaction for a first amount as described in method1800. As another example, method2010optionally includes one or more of the various methods described above with reference to method2000. For example, during numeric sequence entry computer system1900optionally locks during entry of a numeric sequence using user interface1908as described in method2000. As another example, method2010optionally includes one or more various methods described below with reference to method2300. For example, computer system1900in response to unlocking the computer system, displays a quantity of a first type of user interface elements as described in method2300. For brevity, these details are not repeated below.

FIGS.21A-21Dillustrate exemplary user interfaces for managing photos on a photo server, in accordance with some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes inFIG.23A-23B.

FIG.21Aillustrates computer system2100displaying photo summary user interface2102. Photo summary user interface2102includes upload summary user interface2110. AtFIG.21A, computer system2100displays upload summary user interface2110without any user interface elements because the user has not uploaded any photos to a photos server. Photo summary user interface2102also includes deletion information2108. Deletion information2108includes cumulative deletion information2108aand scheduled deletion information2108b. Cumulative deletion information2108aprovides an indication of a total number of photos to be deleted and scheduled deletion information2108bindicates a number of photos that need to be deleted in the next 30 days. Because no photos have been uploaded to the photo server, cumulative deletion information2108aindicates that zero photos need to be deleted and scheduled deletion information2108bindicates that zero photos need to be deleted in the next 30 days.

As illustrated inFIG.21A, photos summary user interface2102includes upcoming deletions information2114. Upcoming deletions information2114indicates the dates on which photos that are uploaded to the photo server will be automatically deleted. AtFIG.21A, computer system2100receives an indication that the user has uploaded three photos to the photos server.

AtFIG.21B, in response to receiving the indication that the user has uploaded three photos to the photos server, computer system2100begins to display photo user interface element2120a, photo user interface element2120b, and photo user interface element2120cas animating in (e.g., drop in) from the top of upload summary user interface2110. Each of photo user interface elements2120a,2120b, and2120ccorrespond to a respective photo that the user has uploaded to the photos server.

As illustrated inFIG.21B, cumulative deletion information2108aindicates that a total of three photos now need to be deleted from the photos server and scheduled deletion information2108bindicates that one photo needs to be deleted from the photos server in the next 30 days. Further, as illustrated inFIG.21B, upcoming deletions information2114indicates that one photo will be automatically deleted from the photos server on February 10thand one photo will be automatically deleted from the photos server on March 12th.

AtFIG.21C, computer system2100has completed displaying each of photo user interface elements2120a,2120b, and2120cas animating into the top of upload summary user interface2110. As illustrated inFIG.21C, at the conclusion of the animation, computer system2100displays each of photo user interface elements2120a,2120b, and2120cnear the top of upload summary user interface2110. AtFIG.21C, computer system2100receives an indication that the user has deleted the photo that corresponds to photo user interface element2120afrom the photos server.

AtFIG.21D, in response to receiving the indication that the user has deleted the photo that corresponds to photo user interface element2120afrom the photos server, computer system2100ceases to display photo user interface element2120a. As illustrated inFIG.21D, because computer system2100received an indication that the user has deleted a photo from the photos server, cumulative deletion information2108aindicates that a total of two photos need to be deleted from the photo servers (e.g., one less than the number of photos that cumulative deletion information2108aindicated needed to be deleted atFIG.21C) and scheduled deletion information2108bindicates that zero photos need to be deleted in the next thirty days (e.g., one less than the number of photos that scheduled deletion information2108bindicated needed to be deleted in the next thirty days atFIG.21C).

FIGS.22A-22Hillustrate exemplary user interfaces for managing one or more pending loans, in accordance with some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes inFIG.23A-23B.

FIG.22Aillustrates computer system2200displaying wallet user interface2202. Wallet user interface2202corresponds to a wallet application that is installed on computer system2200. As illustrated inFIG.22A, wallet user interface2202includes set of digital cards2210. The digital cards that are included in set of digital cards2210allow computer system2200to perform a variety of functions such as unlock a car, make a payment (e.g., an in-store payment and/or an online payment), unlock a hotel room, and/or view information regarding one or more loans. Computer system2200displays additional information regarding a respective digital card in response to computer system2200detecting a tap input that corresponds to selection of the respective digital card. Set of digital cards2210includes later digital card2210a. Later digital card2210acorresponds to one or more loan agreements where the user of computer system2200is the loanee. AtFIG.22A, computer system2200detects input2250athat corresponds to selection of later digital card2210a.

As illustrated inFIG.22B, in response to detecting input2250a, computer system2200displays loan user interface2206. Loan user interface2206includes an expanded version of later digital card2210a(e.g., the display of later digital card2210ain loan user interface2206is larger than the display of later digital card2210ain wallet user interface2202). AtFIG.22B, a determination is made that the user of computer system2200is not subject to any pending loan agreements. Because a determination is made that the user of computer system2200is not subject to any pending loan agreements, computer system2200displays later digital card2210aas a blank card (e.g., computer system2200does not display any user interface elements within later digital card2210aas described below in relation toFIG.22D, other than, for example, a title and/or image identifying later digital card2210a). As illustrated inFIG.22B, loan user interface2206includes done affordance2212. AtFIG.22B, computer system2200detects tap input2250bthat corresponds to selection of done affordance2212.

As illustrated inFIG.22C, in response to detecting tap input2250b, computer system2200displays wallet user interface2202(e.g., as described above in relation toFIG.22A). AtFIG.22C, computer system2200receives an indication (e.g., via a wireless signal such as Wi-Fi and/or a cellular signal) that the user of computer system2200has entered into a loan agreement. In some embodiments, the loan agreement is for a total of $80.00 to be paid back in four prescheduled monthly payments of $20.00, with the first payment having been made at the time of the loan. In some embodiments, the loan agreement is for a total of $60.00 to be paid back in three prescheduled monthly payments of $20.00. AtFIG.22C, after computer system2200has received the indication that the user of computer system2200has entered into the loan agreement, computer system2200detects tap input2250cthat corresponds to selection of later digital card2210a. In some embodiments, the loan agreement corresponds to a web based purchase the user of computer system2200has made. In some embodiments, the loan agreement corresponds to an in-store purchase the user of computer system2200has made. In some embodiments, the loan agreement corresponds to a purchase that was made using near field communication technology (e.g., the user places computer system2200in close proximity with a payment terminal (e.g., not pictured inFIG.22C) as part of an in-store payment using a payment account that is provisioned onto computer system2200). In some embodiments, the user of computer system2200is the loanee and the manufacturer of computer system2200is the loaner. In some embodiments, the user of computer system2200is the loanee and a third external party (e.g., a bank) is the loaner. In some embodiments, while displaying wallet user interface2202, computer system2200displays one or more user interface elements (e.g., as described below in relation toFIG.22D) that correspond to each scheduled payment (that has not been paid) in the loan agreement within later digital card2210ain response to receiving the indication that the user of computer system2200has entered into a loan agreement.

As illustrated inFIG.22D, in response to detecting tap input2250c, computer system2200displays loan user interface2206. Because the user of computer system2200is subject to a pending loan agreement, computer system600displays loan user interface2206with information regarding the pending loan agreement. As illustrated inFIG.22D, computer system2200displays user interface element2218a, user interface element2218b, and user interface element2218c, at the top of later digital card2210a. Because each of user interface elements2218a,2218b, and2218care initially displayed atFIG.22D, computer system2200displays each of user interface elements2218a,2218b, and2218cas animating in from the top of later digital card2210a(e.g., computer system2200displays each of user interface elements2218a,2218b, and2218cas dropping in from the top of later digital card2210a) as a part of displaying loan user interface2206.

Each of user interface elements2218a,2218b, and2218crepresent a payment that is due in the pending loan. As explained above in relation toFIG.22C, the user of computer system is subject to a loan agreement for a total of $80.00, with three payments of $20.00 remaining. Accordingly, each of user interface elements2218a,2218b, and2218crepresents a respective $20.00 remaining payment of the loan agreement. Further, as illustrated inFIG.22D, pay later digital card2210aincludes loan balance information2230. Loan balance information2230indicates the remaining balance of the pending loan. In some embodiments, computer system2200sequentially displays each of user interface elements2218a,2218b, and2218cas animating in from the top of later digital card2210a. In some embodiments, computer system2200displays each of user interface elements2218a,2218b, and2218cwithin pay later card2210a(e.g., while displaying pay later card2210acomputer system2200displays each of user interface elements2218a,2218b, and2218cwithin pay later card2210ain response to receiving an indication that the user of computer system2200has entered into a loan agreement).

As illustrated inFIG.22D, loan user interface2206includes payment information2220about the pending loan. Payment information2220incudes cumulative payment information2220aand scheduled payment information2220b. Similar to loan balance information2230, cumulative payment information2220aprovides an indication of the remaining balance of the pending loan. Scheduled payment information2220bprovides an indication of scheduled payments that are due in the next 30 days. Additionally, as illustrated inFIG.22D, loan user interface2206includes upcoming payment information2222. Upcoming payment information2222provides an indication of both the date at which scheduled payments are due and the amount of the scheduled payments. In some embodiments, computer system2200displays payment information2220and upcoming payment information2222when the user of computer system2200is not subject to any loan agreements (e.g., cumulative payment information2220aindicates that zero dollars are due and scheduled payment information2220bindicate that zero dollars are due in the next 30 days). In some embodiments, while displaying loan user interface2206, computer system2200updates the display of cumulative payment information2220aand scheduled payment information2220b(e.g., in real time and/or not in real time) in response to receiving an indication that the user has entered a loan agreement or in response to receiving an indication that the user has made a payment on an existing loan agreement.

AtFIG.22E, computer system2200finishes displaying the animation of user interface elements2218a,2218b, and2218canimating in from the top of later digital card2210a. Computer system2200displays user interface elements that are representative of new loans near the top of later digital card2210a. Accordingly, as illustrated inFIG.22E, computer system2200displays each of user interface elements2218a,2218b, and2218c(optionally) near the top of later digital card2210aat the conclusion of the animation. Computer system2200displays each respective user interface element that corresponds to the same shopping category with the same visual appearance. Each of user interface elements2218a,2218b, and2218ccorresponds to the same shopping category (e.g., entertainment, travel, or shopping) (e.g., because each of user interface elements2218a,2218b, and2218ccorresponds to the same loan). Accordingly, as illustrated inFIG.22E, computer system2200displays each of user interface elements2218a,2218b, and2218cwith the same visual appearance (e.g., same oval shape, same size, same type of hatching, and/or same color). In some embodiments, in accordance with a determination that the loan that corresponds to each of user interface elements2218a,2218b, and2218ccorresponds to an entertainment spending category, computer system2200displays each of user interface elements2218a,2218b, and2218cwith a pink color. In some embodiments, in accordance with a determination that the loan that corresponds to each of user interface elements2218a,2218b, and2218ccorresponds to a travel spending category, computer system2200displays each of user interface elements2218a,2218b, and2218cwith a green color. In some embodiments, in accordance with a determination that that the loan that corresponds to each of user interface elements2218a,2218b, and2218ccorresponds to a shopping spending category, computer system2200displays each of user interface elements2218a,2218b, and2218cwith a yellow color.

Further, as illustrated inFIG.22E, upcoming payment information2222indicates that the next two scheduled payments for the pending loan are due on February 12thand March 12th. AtFIG.22E, computer system2200receives an indication (e.g., via a wireless signal) that the user has a made a $20.00 payment on the loan. In some embodiments, the payment is a manual payment that the user manually initiated. In some embodiments, the payment is an automatic payment that was automatically scheduled.

AtFIG.22F, computer system2200displays loan user interface2206at a later point in time than the display of loan user interface2206atFIG.22E(e.g., six minutes or two hours have elapsed). AtFIG.22F, in response to receiving the indication that the user has made a payment on the pending loan, computer system2200displays later digital card2210awithout user interface element2218c. As explained above, each of user interface elements2218a,2218b, and2218ccorresponds to a respective payment of the pending loan. Accordingly, computer system2200displays later digital card2210awith one fewer user interface element every time the user makes a payment on the pending loan. As illustrated inFIG.22F, loan balance information2230indicates that the current balance on the pending loan is $40.00. AtFIG.22E, loan balance information2230indicated that the current balance on the pending loan was $60.00. AtFIG.22F, because the user made a $20.00 payment on the loan, the amount due on the loan as indicated by loan balance information2230of loan is reduced by $20.00.

As illustrated inFIG.22F, similar to loan balance information2230, cumulative payment information2220aindicates that the pending balance on the loan is $40.00. Because the user made a $20.00 payment on the loan, the amount due on the loan as indicated by cumulative payment information2220ais reduced by $20.00. Further, as illustrated inFIG.22F, scheduled payment information2220bindicates that $0.00 is due on the pending loan in the next 30 days. The user has satisfied their payment obligations for the next 30 days because the user made a $20.00 payment on the loan. Additionally, as illustrated inFIG.22F, upcoming payment information2222indicates that the next two scheduled payments are now due now March 12thand April 12th(e.g., as opposed to February 12thand March 12 as shown inFIG.22E). Because the user made a payment, the scheduled payment for February 12th (e.g., as shown inFIG.22E) has been satisfied. AtFIG.22F, computer system2200receives an indication that the user of computer system2200has entered into a second loan agreement that for a value of $150.00 to be paid off over 15 prescheduled payments. In some embodiments, computer system2200updates cumulative payment information2220a, loan balance information2230, and scheduled payment information2220bin real-time (e.g., computer system2200updates cumulative payment information2220a, loan balance information2230, and scheduled payment information2220bwhile computer system2200displays loan user interface2206in response to receiving the indication that the user has made a payment on the loan).

AtFIG.22G, computer system2200displays loan user interface2206at a later point in time than the display of loan user interface2206atFIG.22F(e.g., six minutes have elapsed). As illustrated inFIG.22G, in response to receiving the indication that the user of computer system2200has entered into a second loan agreement, computer system2200displays set of user interface elements2232within later digital card2210a. Further, as illustrated inFIG.22G, computer system2200displays user interface element2218aand user interface element2218bwithin later digital card2210a, while computer system2200displays set of user interface elements2232.

Set of user interface elements2232corresponds to the second loan agreement. Similar to user interface element2218aand user interface element2218b, each respective user interface element in set of user interface elements2232corresponds to a respective payment in the second loan agreement. Because the second loan agreement is valued at $150.00 remaining (e.g., $200 original loan to be paid over 4 payments, with the first payment made at the time of the loan), to be paid over 3 remaining payments, each user interface element in set of user interface elements2232corresponds to a $50.00 payment. Accordingly, set of user interface elements2232includes three user interface elements. In some embodiments, as described with respect to the initial loan agreement and second loan agreement, each loan represented by loan user interface2206is based on the same number of payments (e.g., each loan is scheduled to be repaid over four payments, with the first payment made at the time of the respective loan). In some embodiments, the number of payments varies for different loans (e.g., a loan can be 4 payments while another loan can be 12 payments). In some embodiments, some (e.g., less than all or all) loans are based on an initial repayment scheduled for the day and/or time that the loan is initiated. In some embodiments, the initial repayment is not scheduled for the day and/or time that the loan is initiated.

Computer system2200displays user interface elements that correspond to newer loans above user interface elements that correspond to older loans. Accordingly, as illustrated inFIG.22G, computer system2200displays user interface element2218aand user interface element2218bbeneath set of user interface elements2232. In some embodiments, computer system2200displays user interface elements that correspond to an older loan as shifting down within later digital card2010awhile computer system2200displays user interface elements as animating in from the top of later digital card2010a.

The second loan is associated with a purchase from a different spending category than the purchase that is associated with the initial loan. Accordingly, set of user interface elements2232corresponds to a spending category that is different than the spending category that corresponds to user interface element2218aand user interface element2218b. Because set of user interface elements2232corresponds to a spending category that is different from the spending category that corresponds to user interface element2218aand user interface element2218b, computer system2200displays each respective user interface element in set of user interface elements2232with a different visual appearance (e.g., different color, size, and/or shape) than the visual appearance of user interface element2218aand user interface element2218b.

AtFIG.22G, cumulative payment information2220aindicates the outstanding amount due from the initial loan and the second loan. As illustrated inFIG.22G, cumulative payment information2220aindicates that the outstanding amount due from the initial loan and second loan is $190.00. $190.00 represents the outstanding $150.00 due from the second loan and the outstanding $40.00 due from the initial loan. Further, similar to cumulative payment information2220a, loan balance information2230indicates that the outstanding amount due from the initial loan and the second loan is $190.00. Further, as illustrated inFIG.22G, scheduled payment information2220bindicates that $50.00 are due in the next 30 days. $50.00 represents the cumulative amount that is due from both the initial loan and the second loan in the next 30 days.

Computer system2200displays each respective user interface element as a smaller size when the number of outstanding payments for a user is greater than a threshold (e.g., 4, 15, 25, or 40 outstanding payments). AtFIG.22G, a determination is made that the number of outstanding payments for the user is greater than the threshold. Because a determination is made that the total number of outstanding payments for the user is greater than the threshold, computer system2200displays each respective user interface element with a smaller size (e.g., in comparison to the size of user interface elements2218aand2218binFIGS.22D-22F). AtFIG.22G, computer system220detects tap input2250gthat corresponds to selection of user interface element2218b.

AtFIG.22H, in response to detecting tap input2250g, computer system2200maintains the display of loan user interface2206. That is, the various user interface elements are not selectable. In some embodiments, computer system2200displays additional information regarding a respective loan in response to detecting a tap input on a user interface element (e.g., computer system2200displays information about the initial loan in response to detecting a tap input (e.g.,2250g) that corresponds to selection of user interface element2218aand/or user interface element2218band/or computer system2200displays information about the second loan in response to detecting a tap input that corresponds to selection of a respective user interface element in set of user interface elements2232.

FIGS.23A-23Bare flow diagrams illustrating a method for managing information, such as one or more pending loans or one or more uploaded photos, using a computer system in accordance with some embodiments. Method2300is performed at a computer system (e.g.,2100or2200) (e.g., a smartwatch, a wearable electronic device, a smartphone, a desktop computer, a laptop, and/or a tablet) that is in communication with a display generation component (e.g., a display controller and/or a touch-sensitive display system) and one or more input devices (e.g., a wireless interface, a touch-sensitive surface, a keyboard, and/or a mouse). Some operations in method2300are optionally, combined, the orders of some operations are, optionally, changed, and some operations are, optionally omitted.

As described below, method2300provides an intuitive way for managing information. The method reduces the cognitive burden on a user for managing information using a computer system, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to manage information using a computer system faster and more efficiently conserves power and increases the time between battery charges.

The computer system receives (2302) (e.g., acquiring, detecting, and/or obtaining) (e.g., detecting via a wireless signal (e.g., Wi-Fi or a cellular signal)), via the one or more input devices, an indication that a first set of transfer obligations has been generated (e.g., receiving data that is representative of the set of transfer obligations) (e.g., a requirement to delete images from a transfer account by a set schedule, a loan with scheduled payments (e.g., scheduled payments every week, 2 weeks, once a month, or every three months) has been generated, a loan where the manufacturer of the computer system is the loaner and the user of the computer system is the loanee, and/or a loan where an external party (e.g., not the user of the computer system and not the manufacturer of the computer system) is the loaner).

The computer system receives (2304), via the one or more input devices, a request (e.g.,2250aand/or2250c) (e.g., a user input (e.g., a tap, a press and hold, a swipe, and/or activation of a hardware button that is coupled to the computer system)) to display a transfer summary user interface (e.g.,2110,2206, and/or2210a) (e.g., a user interface that includes a summary of pending images to be deleted or a user interface that includes a summary of pending loans (e.g., upcoming payment amounts, amount due on the loan, and/or date of scheduled payments) (e.g., loans where the user of the computer system is the loanee)).

In response to receiving the request to display the transfer summary user interface, the computer system displays (2306), via the display generation component, the transfer summary user interface including a quantity of a first type of user interface elements (e.g.,2120a,2120b,2120c,2218a,2218b,2218c, and/or2232), wherein as a part of displaying the transfer summary user interface: in accordance with a determination that the first set of transfer obligations includes a first quantity of transfer obligations, the computer system displays (2308), based on the first quantity, at least the first quantity (and, optionally, no more than and no less than the first quantity) of the first type (e.g., three of the first type of user interface elements or seven of the first type of user interface elements) of user interface elements (e.g., as described above in relation toFIG.22E) (e.g., each user interface element of the first type has the same appearance (e.g., same size, same color, and/or same shape (e.g., oval shaped user interface elements)), a symbol, a shape, and/or non-numerical user interface element, and/or each user interface element represents a respective scheduled payment in the loan) and in accordance with a determination that the first set of transfer obligations includes a second quantity of transfer obligations (e.g., different (e.g., greater than the first quantity or less than the first quantity) from the first quantity), the computer system displays (2310), based on the second quantity, at least the second quantity (and, optionally, no more than and no less than the second quantity) of the first type (e.g., eight of the first type of user interface elements or eleven of the first type of user interface elements) of user interface elements.

Subsequent to displaying the transfer summary user interface, the computer system receives (2312) an indication (e.g., via a wireless signal (e.g., Wi-Fi or a cellular connection signal)) that a respective transfer obligation in the first set of transfer obligations (e.g., a scheduled payment has been paid (e.g., automatically paid or manually paid) or an image scheduled to be deleted has been automatically or manually deleted) has been satisfied (e.g., as described above in relation toFIGS.22E and22F).

Subsequent to receiving the indication that a respective transfer obligation in the first set of transfer obligations has been satisfied, the computer system displays (2314) (e.g., in response to a request to display the transfer summary user interface), via the display generation component and based on the indication that the respective transfer obligation in the first set of transfer obligations has been satisfied, the transfer summary user interface with one less than the quantity of the first type of user interface elements (e.g., as described above in relation toFIG.22F) (e.g., and continuing to display one or more respective interface elements of the first type) (e.g., the transfer summary user interface is displayed in response to the computer system receiving a second request to display the transfer summary user interface). In some embodiments, the first type of user interface elements are displayed while a second type of user interface elements that correspond to a second loan are displayed. In some embodiments, the first type of user interface elements are displayed while additional information (e.g., total amount of payments, upcoming scheduled payments, amount due in an upcoming time period, completed payments, an indication (e.g., graphical indication and/or textual indication) of the purchase that corresponds to the set of transfer obligations) is displayed. In some embodiments, each user interface element of the first type (and/or of the second type) is displayed at a different angular orientation (e.g., oriented randomly or pseudo-randomly). In some embodiments, the display of a first respective user interface element overlaps with the display of a second respective user interface (e.g., a portion of the first respective user interface element is overlaid on top of a portion of the second respective user interface element). In some embodiments, displaying the transfer summary user interface with one less than the quantity of the first type of user interface elements includes fading out a respective first type of user interface element in response to receiving the indication that the respective transfer obligation in the set of transfer obligations has been satisfied. In some embodiments, displaying the user interface elements of the first type includes displaying an animation of the user interface elements of the first type being displayed (e.g., each user interface element of the first type fades in at the same time or each user interface element of the first type fades in sequentially). Displaying a quantity of the first type of user interface elements based on the quantity of outstanding payments (e.g., transfer obligations) in a pending loan allows the computer system to automatically manage the number of user interface elements that are displayed in order to indicate to a user how many outstanding payments are due on a pending loan, thereby providing the user with improved visual feedback. Displaying the transfer summary user interface with one less than the quantity of the first type of user interface elements subsequent to receiving the indication that a respective transfer obligation in the first set of transfer obligations has been satisfied provides the user with visual feedback regarding the state of the computer system (e.g., the computer system has received the indication that the respective transfer obligation has been satisfied), which provides improved visual feedback.

In some embodiments, in accordance with a determination that the first set of transfer obligations corresponds to a first spending category (e.g., as described above in relation toFIG.22E) (e.g., the purchase that corresponds to the first set of transfer obligations (e.g., the loan) belongs to the first spending category (e.g., shopping, entertainment, or travel)), the first type of user interface elements (e.g.,2120a,2120b,2120c,2218a,2218b,2218cand/or2232) are displayed with a first visual appearance (e.g., the appearance of2218a,2218b, and/or2218cor the appearance of2232) (e.g., a respective shape, size, color, and/or orientation that corresponds to the first spending category) and in accordance with a determination that the first set of transfer obligations corresponds to a second spending category (e.g., as described above in relation toFIG.22E) (e.g., that is different from the first spending category), the first type of user interface elements are displayed with a second visual appearance (e.g., the appearance of2218a,2218b, and/or2218cor the appearance of2232) that is different than the first visual appearance. In some embodiments, the first visual appearance and the second visual appearance have overlapping visual characteristics (e.g., same size, same color, same orientation, and/or same shape). In some embodiments, when the set of transfer obligations corresponds to an entertainment spending category (e.g., dining, movies theaters, sports, amusement parks, and/or recreational activities), the first type of user interface elements are displayed with a pink color. In some embodiments, when the set of transfer obligations corresponds to a travel spending category (e.g., airline tickets, cruises, hotel stays, and/or taxis) the first type of user interface elements are displayed with a green color. In some embodiments, when the set of transfer obligations corresponds to a shopping spending category (e.g., purchase of clothes, electronics, home goods and/or sport equipment), the first type of user interface elements are displayed with a yellow color. Displaying the first type of user interface elements with a first appearance when a first set of conditions are met (e.g., in accordance with a determination that the first set of transfer obligations corresponds to a first spending category) and displaying the first type of user interface elements with a second appearance when a second set of conditions are met (e.g., in accordance with a determination that the first set of transfer obligations corresponds to a second spending category) provides the user with visual feedback about which set of conditions have been met.

In some embodiments, the first type of user interface elements are displayed at a first size (e.g., the size of2218a,2218b, or2218catFIGS.22D-22F) (e.g., a length of 0.1 inches, 0.3 inches, or 0.5 inches). In some embodiments, subsequent to displaying the transfer summary user interface (e.g.,2206and/or2210a), the computer system (e.g.,2100and/or2200) receives, via the one or more input devices, an indication that a second set of transfer obligations has been generated (e.g., as described above in relation toFIGS.22C,22D,22F and/or22G) (e.g., a second set of transfer obligations that is different from the first set of transfer obligations (e.g., the second set of transfer obligations corresponds to a second loan)). In some embodiments, the computer system receives (e.g., subsequent to receiving the indication that the second set of transfer obligations has been generated), via the one or more input devices, a second request (e.g.,2250cand/or2250a) (e.g., one or more user inputs) to display the transfer summary user interface. In some embodiments, in response to receiving the second request to display the transfer summary user interface, the computer system displays, via the display generation component, the transfer summary user interface including a third quantity of the first type of user interface elements (e.g.,2218a,2218b, and/or2218catFIGS.22D-22F) (e.g., the third quantity is different than the first quantity and the second quantity) based on the first set of transfer obligations and the second set of transfer obligations (e.g., as described above in relation toFIG.22G) (e.g., each respective user interface element in the third quantity of the first type of user interface elements corresponds to a respective payment obligation in the first set of transfer obligations or the second set of transfer obligations), wherein: in accordance with a determination that the third quantity of the first type of user interface elements is greater than a quantity threshold (e.g., a quantity of 5, 10, 25, 30, 45, or 50 user interface elements), the first type of user interface elements are displayed at a second size (e.g.,2218a,2218b,2218c, and/or2232atFIGS.22G-22H) (e.g., as described above in relation toFIG.22G), that is smaller than the first size (e.g., the second size is smaller than the first size by a multiple (e.g., 2×, 3×, or 4×)) (e.g., the computer system displays the user interface element at a reduced when the total number of displayed user interface elements exceeds a threshold) and in accordance with a determination that the third quantity of the first type of user interface elements is less than the quantity threshold, the first type of user interface elements are displayed at the first size. In some embodiments, the computer system changes the size of the first type of user interface elements from the second size to the first time in real time in accordance with a determination that the third quantity of the displayed first type of user interface elements is below the quantity threshold. In some embodiments, the computer system dynamically changes the size of the first type of user interface elements based on the amount of the first type of user interface elements that are displayed. Displaying the first type of user interface elements at a second size when conditions are met (e.g., in accordance with a determination that the third quantity of the first type of user interface elements is greater than a quantity threshold) allows the computer system to automatically manage the size of the display of the first type of user interface elements such that a user can easily view each respective user interface element of the first type and indicates to the user that there are more than the quantity threshold, thereby providing the user with improved visual feedback.

In some embodiments, the transfer summary user interface (e.g.,2206,2110or2210a) includes a second type of user interface elements (e.g.,2120a,2120b,2120c,2218a,2218b,2218c, and/or2232) that correspond to a third set of transfer obligations (e.g., as described above in relation toFIGS.22F and22G) (e.g., that corresponds to a loan that is different from the loan that corresponds to the first set of transfer obligations), wherein the first type of user interface elements (e.g.,2120a,2120b,2120c,2218a,2218b,2218c, and/or2232) correspond to the first set of transfer obligations, and wherein as a part of displaying the transfer summary user interface: in accordance with a determination that the third set of transfer obligations was generated at a point in time before the first set of transfer obligations (e.g., the computer system received an indication that the user entered into the loan agreement that corresponds to the third set of transfer obligations before the computer system received an indication that the user entered into the loan agreement that corresponds to the first set of transfer obligations), the computer system (e.g.,2100or2200) displays the first type of user interface elements above (e.g., as described above in relation toFIG.22G) (e.g.,2232atFIG.22G) (e.g., closer to a respective side (e.g., the top) of the computer system) the second type of user interface elements (e.g.,2218aand/or2218batFIG.22G) (e.g., the majority of the first type of user interface elements are displayed above the majority of the second type of user interface elements) and in accordance with a determination that the third set of transfer obligations was generated at a point in time after the first set of transfer obligations, the computer system displays the first type of user interface elements below the second type of user interface elements. In some embodiments, the second type of user interface elements is visually distinct from the first type of user interface elements. In some embodiments, the second type of user interface elements are not visually distinct from the first type of user interface elements. In some embodiments, there is no vertical relationship between the first type of user interface elements and the second type of user interface elements when the user enters into the loan agreement that corresponds to the first set of transfer obligations and the loan agreement that corresponds to the second set of transfer obligations at substantially the same time. Displaying the first type of user interface elements above the second type of user interface elements when conditions are met (e.g., in accordance with a determination that the third set of transfer obligations was generated at a point in time before the first set of transfer obligations) allows the computer system to automatically manage the display of two types of user interface elements such that the display of user interface elements that correspond to a newer loan are prioritized over the display of user interface elements that correspond to an older loan, which performs an operation when a set of conditions has been meet without additional user input. Displaying user interface elements representative of payments in a newer loan above user interface elements representative of payments in an older loan provides the user with visual feedback regarding the number of outstanding payments for the newer loan in comparison to the amount of outstanding payment for the older loan, which provides improved visual feedback.

In some embodiments, the second type of user interface elements (e.g.,2120a,2120b,2120c.2218a,2218b,2218c, and/or2232) that correspond to the third set of transfer obligations are displayed at a first location (e.g., the location of2218aand/or2218batFIGS.22E and22F) on the transfer summary user interface (e.g.,2206,2110, and/or2210a) prior to the display of the first type of user interface elements, wherein as a part of displaying the first type of user interface: in accordance with a determination that the third set of transfer obligations was generated at a point in time before the first set of transfer obligations, the computer system (e.g.,2100or2200) moves (e.g., animating) the second type of user interface elements from the first location to a second location (e.g., the location of2218aand/or2218batFIG.22G) (e.g., as described above in relation toFIG.22G) (e.g., the second location is different from the first location), wherein the second location is beneath the first location. In some embodiments, the computer system displays the first type of user interface elements at the first location while the computer system displays second type of user interface elements at the second location. In some embodiments, the computer system moves the second type of user interface elements from the second location to the first location as a part of ceasing to display the first type of user interfaces (e.g., in response to receiving an indication that the user has satisfied every transfer obligation in the set of transfer obligations). In some embodiments, the computer system sequentially displays easy respective user interface element of the second type of user interface elements as moving from the first location on the transfer summary user interface to the second location on the transfer summary user interface. Moving the second type of user interface elements from the first location to the second location when a set of conditions are met (e.g., in accordance with a determination that the third set of transfer obligations was generated at a point in time before the first set of transfer obligations) allows the computer system to automatically manage the display of two types of user interface elements such that the display of user interface elements that correspond to a newer loan are prioritized over user interface elements that correspond to an older loan, which performs an operation when a set of conditions has been meet without additional user input.

In some embodiments, subsequent to displaying the transfer summary user interface (e.g.,2206,2110, and/or2210a), the computer system (e.g.,2100and/or2200) receives, via the one or more input devices, an indication that the first set of transfer obligations has been satisfied (e.g., as described above in relation toFIGS.22E and22F) (e.g., the user has made all of the scheduled payments on the loan (e.g., the user is not subject to any pending loans) and, optionally, there are no other outstanding transfer obligations). In some embodiments, subsequent to receiving the indication that the first set of transfer obligations has been satisfied, the computer system receives receiving (e.g., while the transfer summary user interface is not displayed), via the one or more input devices, a third request (e.g.,2250aand/or2250c) (e.g., one or more user inputs) to display the transfer summary user interface. In some embodiments, in response to receiving the third request to display the transfer summary user interface, the computer system displays, via the display generation component, the transfer summary user interface without the first type of user interface elements (e.g.,2206,2210aatFIG.22Band/or2110atFIG.21A) (e.g., the transfer summary user interface does not include any type of user interface elements that corresponds to scheduled payments for a loan) (e.g., the transfer summary user interface is displayed as a solid color (e.g., black, white, or grey)). Displaying the transfer summary user interface without the first type of user interface elements subsequent to receiving an indication that the first set of transfer obligations has been satisfied provides the user with visual feedback regarding whether the user is currently subject to a pending loan agreement, which provides improved visual feedback.

In some embodiments, subsequent to displaying the transfer summary user interface, the computer system (e.g.,2100and/or2200) receives, via the one or more input devices, an indication that a fourth set of transfer obligations has been generated (e.g., as described above in relation toFIGS.22C,22D,22F and22G) (e.g., that is different from the first set of transfer obligations) (e.g., that corresponds to a loan that is different than the loan that corresponds to the first set of transfer obligations). In some embodiments, the computer system receives, via the one or more input devices, a fourth request (e.g.,2250aand/or2250c) (e.g., one or more inputs) (e.g., while the transfer summary user interface is not displayed) to display the transfer summary user interface (e.g.,2110,2206, and/or2210a). In some embodiments, in response to receiving the fourth request to display the transfer summary user interface, the computer system displays, via the display generation component, the transfer summary user interface, wherein as a part of displaying the transfer summary user interface: the computer system displays the quantity of the first type of user interface elements with a third visual appearance (e.g., the appearance of2218a,2218b, and/or2218c) (e.g., a respective shape, color, and/or size) and the computer system displays based on the fourth set of transfer obligations, a quantity of a third type of user interface elements (e.g., based on the fourth set of transfer obligations) with a fourth visual appearance (e.g., the appearance of2232) that is different than the first visual appearance (e.g., the third type of user interface elements are visually distinct from the first type of user interface elements). In some embodiments, the first type of user interface elements and the third type of user interface elements share a at least one visual characteristic (e.g., size, shape, and/or color). Displaying the first type of user interface elements that correspond to payments of a first loan with a third appearance and displaying the third type of user interface elements that correspond to payments of a second loan with a fourth appearance that is different from the third appearance provides the user with visual feedback regarding the number of outstanding payments due on both the first loan and the second loan by allowing the user to easily distinguish user interface elements that are associated with the first loan and the second loan, which provides improved visual feedback.

In some embodiments, each respective user interface element in the quantity of the first type of user interface elements is not selectable (e.g., as described in relation toFIG.22H). In some embodiments, while the first type of user interface elements are displayed, the computer system receives user input (e.g., a tap input or a tap-and-hold input) at a location corresponding to a respective user interface element and, in response to receiving the user input at the location corresponding to the respective user interface element, the computer system forgoes displaying additional information about the transfer obligation associated with the respective user interface element (and, optionally, the computer system does not display any content in response to receiving the user input). In embodiments where the respective user interface elements are selectable, in response to detecting selection of a respective user interface element, the computer system displays (while maintaining display of the transfer summary user interface) information regarding the loan that corresponds to the selected user interface element (e.g., information about the purchase (e.g., the total cost of the purchase associated with the, date of purchase, what was bought with the purchase, and/or the merchant associated with the purchase), payment due dates for the loan, and/or options for paying the loan off). In some embodiments, the computer system ceases to display the transfer summary user interface in response to detecting selection of a respective user interface element.

Note that details of the processes described above with respect to method2300(e.g.,FIG.23A-23Bare also applicable in an analogous manner to the methods described above. For example, methods800,900,1200,1500,1800,2000and2010optionally includes one or more of the characteristics of the various methods described above with reference to method700. For example, the method of locking the computer system as described above in reference to method2010can be used to lock the computer system upon display of the loan summary user interface. For brevity, these details are not repeated below.