Granted Patent B2

US 11,514,452 · App. 15/942,227 · Granted Nov 29, 2022

Inventors: Sara Sanchez-Llorens (San Francisco, CA); Todor Ristov (San Bruno, CA); Elise Hurwitz (Berkeley, CA); Arnaud Ponchon (Tiburon, CA); Evan Doyle (San Francisco, CA); Isreal Blagdan (San Francisco, CA); Christine Lin (San Francisco, CA); Imran Khan (San Rafael, CA)

Assignee: Block, Inc.

G06Q20/4012G06Q20/204

Abstract

Claims (45)

1. A system for conducting one or more transactions between a merchant and one or more customers, the system comprising:

a customer-facing device comprising one or more first processors, a first display, a payment reader and first non-transitory computer-readable media storing first instructions that, when executed by the one or more first processors, cause the one or more first processors to perform first operations comprising:

presenting, while in a customer state, a customer user interface (UI) on the first display, wherein the customer UI is configured to facilitate one or more customer functionalities associated with the customer state;

detecting a trigger event, wherein the trigger event comprises at least one of a change in orientation of at least a portion of the customer-facing device or a change in position of at least a portion of the customer-facing device; and

based at least in part on detecting the trigger event, transitioning from the customer state to a merchant state; and

a merchant-facing device coupled to the customer-facing device, the merchant-facing device comprising one or more second processors, a second display and second non-transitory computer-readable media storing second instructions that, when executed by the one or more second processors, cause the one or more second processors to perform second operations comprising:

presenting a first merchant UI, wherein the first merchant UI is configured to facilitate at least a first merchant functionality of a plurality of merchant functionalities including a first action;

determining that the customer-facing device has transitioned from the customer state to the merchant state; and

based on the determination, sending an instruction to the customer-facing device to present a second merchant UI, wherein the second merchant UI is configured to facilitate at least a second merchant functionality of the plurality of merchant functionalities including a second action associated with a transaction of the one or more transactions.

2. The system as claim 1 recites, wherein the merchant-facing device comprises a first merchant-facing device, the system further comprising a second merchant-facing device that comprises at least one of firmware or hardware that is substantially identical to the first merchant-facing device.

3. The system as claim 1 recites, wherein the merchant-facing device comprises a first merchant-facing device, wherein the first merchant-facing device is coupled to the customer-facing device at a first time and a second merchant-facing device is coupled to the first merchant-facing device at a second time after the first time based at least in part on the customer-facing device providing a device identifier to the first merchant-facing device.

4. The system as claim 1 recites, wherein the second merchant UI comprises a projection.

5. The system as claim 1 recites, wherein the first action is associated with the transaction.

6. The system as claim 1 recites, wherein the transaction comprises a first transaction, and wherein the first action is associated with a second transaction that is different from the first transaction.

7. The system as claim 1 recites, wherein the customer-facing device is a personal device of a customer of the one or more customers, and the second operations further comprising:

temporarily provisioning the first instructions to the customer-facing device.

8. The system as claim 1 recites, wherein the merchant-facing device is a personal device of the merchant and the second instructions are temporarily provisioned by a remote system to the merchant-facing device.

9. The system as claim 1 recites, wherein the second merchant UI includes a first representation of the first merchant UI and a second representation of the customer UI, presented in a picture-in-picture (PIP) presentation.

10. The system as claim 1 recites, wherein the merchant-facing device comprises a first merchant-facing device, and the second operations further comprising:

storing a first device identifier of the customer-facing device responsive to the first merchant-facing device having been coupled to the customer-facing device at a first time;

receiving a second device identifier of a second merchant-facing device; and

based at least in part on receiving the second device identifier, coupling the second merchant-facing device to the first merchant-facing device.

11. The system as claim 7 recites, the second operations further comprising:

determining a characteristic of a user profile associated with the personal device; and

temporarily provisioning the first instructions to the personal device based at least in part on the characteristic.

12. A method comprising:

presenting, via a merchant application associated with a merchant-facing device associated with a merchant, a first merchant user interface (UI) on a display of the merchant-facing device, wherein the first merchant UI is configured to facilitate at least a first merchant functionality of a plurality of merchant functionalities including a first action;

presenting, via a customer application associated with a customer-facing device and while the customer-facing device is in a customer state, a customer UI on a display of the customer-facing device, wherein the customer UI is configured to facilitate one or more customer functionalities associated with the customer state;

detecting, by the customer application, a trigger event, wherein the trigger event comprises at least one of a change in orientation of at least a portion of the customer-facing device or a change in position of at least a portion of the customer-facing device;

based at least in part on detecting the trigger event, transitioning, by the customer application, the customer-facing device from the customer state to a merchant state;

determining, by the merchant application, that the customer-facing device has transitioned from the customer state to the merchant state; and

based on the determination, sending, by the merchant application to the customer-facing device, instructions to present a second merchant UI, wherein the second merchant UI is configured to facilitate at least a second merchant functionality of the plurality of merchant functionalities including a second action.

13. The method as claim 12 recites, wherein the merchant-facing device comprises a first merchant-facing device, wherein the first merchant-facing device is coupled to the customer-facing device at a first time and a second merchant-facing device is coupled to the first merchant-facing device at a second time after the first time based at least in part on the customer-facing device providing a device identifier to the first merchant-facing device.

14. The method as claim 13 recites, wherein the second merchant-facing device comprises at least one of firmware or hardware that is substantially identical to the first merchant-facing device.

15. The method as claim 12 recites, wherein the first action is associated with a transaction between the merchant and one or more customers.

16. The method as claim 15 recites, wherein the transaction comprises a first transaction, and wherein the second action is associated with a second transaction different from the first transaction.

17. A method comprising:

presenting, via a customer application associated with a customer-facing device and while the customer-facing device is in a customer state, a customer user interface (UI) on a display of the customer-facing device, wherein the customer UI is configured to facilitate one or more customer functionalities associated with the customer state;

detecting, by the customer application, a trigger event, wherein the trigger event comprises a movement of the customer-facing device;

based at least in part on detecting the trigger event, transitioning, by the customer application, the customer-facing device from the customer state to a merchant state; and

receiving, by the customer application and from a merchant application associated with a merchant-facing device of a merchant, instructions to present a merchant UI, wherein the instructions are based at least in part on the merchant application determining that the customer-facing device has transitioned from the customer state to the merchant state, and wherein the merchant UI is configured to facilitate at least one merchant functionality including an action associated with a transaction between the merchant and a customer.

18. The method as claim 17 recites, wherein the merchant UI is presented on the display of the customer-facing device.

19. The method as claim 17 recites, wherein the merchant UI comprises a projection.

20. The method as claim 17 recites, wherein the merchant-facing device comprises a first merchant-facing device, wherein the first merchant-facing device is coupled to the customer-facing device at a first time, and the method further comprising:

based at least in part on the merchant application receiving a device identifier from the customer-facing device, coupling, by the merchant application, a second merchant-facing device to the first merchant-facing device at a second time after the first time.

Assignments (2)

Continuity (1)

Cited By (13)

US 1,057,718 US 1,057,727 US 1,057,728 US 1,086,147 US 1,086,277 US 1,087,092 US 1,087,106 US 1,103,984 US 1,107,031 US 1,107,719 US 1,108,429 US 1,123,923 US 12,632,863