US 11,900,372 B2
User interfaces for transactions
Marcel Van Os, San Francisco, CA (US); Oluwatomiwa B. Alabi, Studio City, CA (US); Peter D. Anton, San Francisco, CA (US); Leonardo Cantelmo, San Francisco, CA (US); George R. Dicker, Sunnyvale, CA (US); Morgan Grainger, Nashville, TN (US); Kevin Lynch, Woodside, CA (US); Nicholas Shearer, London (GB); and Simon Tickner, Kent (GB)
Assigned to Apple Inc., Cupertino, CA (US)
Filed by Apple Inc., Cupertino, CA (US)
Filed on May 14, 2021, as Appl. No. 17/320,900.
Application 17/320,900 is a continuation of application No. 15/433,320, filed on Feb. 15, 2017, granted, now 11,037,150.
Claims priority of provisional application 62/349,010, filed on Jun. 12, 2016.
Prior Publication US 2021/0272118 A1, Sep. 2, 2021
Int. Cl. G06Q 20/10 (2012.01); G06Q 20/40 (2012.01); G06Q 20/32 (2012.01)
CPC G06Q 20/401 (2013.01) [G06Q 20/10 (2013.01); G06Q 20/322 (2013.01); G06Q 20/327 (2013.01)] 51 Claims
OG exemplary drawing
 
1. An electronic device, comprising:
a display;
one or more input devices;
a hardware button;
one or more processors; and
a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for:
displaying, on the display, an application user interface for a respective application, wherein the application user interface includes a transaction affordance for requesting payment for activity associated with the respective application;
while displaying the application user interface, detecting, via the one or more input devices, selection of the transaction affordance; and
in response to detecting selection of the transaction affordance, displaying a transaction user interface provided by an application different from the respective application, wherein displaying the transaction user interface includes concurrently displaying:
transaction details for the activity associated with the respective application; and
instructions to activate the hardware button of the device to authorize payment for the activity associated with the respective application; and
while displaying the transaction user interface:
receiving an input, via the one or more input devices, corresponding to an instruction to scroll the transaction user interface; and
in response to receiving the input corresponding to the instruction to scroll the transaction user interface:
displaying additional transaction details f r the activity associated with the respective application; and
forgoing scrolling the instructions to activate the hardware button.