Transaction processing by multiple devices

Patent metadata

Field	Value
Publication number	US-11475431-B2
Application number	US-201916681217-A
Country	US
Kind code	B2
Filing date	Nov 12, 2019
Priority date	Jul 16, 2012
Publication date	Oct 18, 2022
Grant date	Oct 18, 2022

Abstract

Techniques associated with a customer-facing device and a merchant-facing device are described herein. In an example, a system can include a customer-facing device configured with a customer application that is executable on an operating system of the customer-facing device to (i) display information to a customer and (ii) receive input from the customer, wherein the customer-facing device includes a payment reader to read payment data from a payment instrument in association with a payment transaction between the customer and a merchant, and a merchant-facing device configured with a merchant application that is executable on an operating system of the merchant-facing device to (i) display information to the merchant and (ii) receive input from the merchant. In at least one example, the customer-facing device and the merchant-facing device can communicate to process, at least in part, the payment transaction associated with the payment instrument via a remote payment service system.

First claim

What is claimed is:

1. A method comprising:
downloading a first application, provided by a payment service system associated with processing distributed payment transactions, onto a customer-facing device of a payment system;
executing the first application on an operating system of the customer-facing device;
downloading a second application, provided by the payment service system, onto a merchant-facing device of the payment system, wherein at least the merchant-facing device is configured to communicate with the payment service system via an external network,
wherein the first application and the second application (1) are different applications executing on different devices, and (2) are associated with a same merchant account associated with the payment service system, wherein the merchant account is created by the merchant;
executing the second application on an operating system of the merchant-facing device;
receiving, via an input device associated with the customer-facing device and by the first application, payment data associated with a payment instrument presented to satisfy a cost of a transaction between the merchant and a customer;
sending, by the first application via the operating system of the customer-facing device, the payment data to the second application;
receiving, by the second application via the operating system of the merchant-facing device, the payment data from the first application; and
sending, by the second application via the operating system of the merchant-facing device, the payment data directly to the payment service system via the external network, wherein receipt of the payment data causes the payment service system to process payment for the transaction.

2. The method as claim 1 recites, wherein the customer-facing device and the merchant-facing device are connected via a wired connection.

3. The method as claim 1 recites, wherein the customer-facing device and the merchant-facing device communicate via a secure wireless connection.

4. The method as claim 1 recites, further comprising, prior to sending the payment data to the payment service system:
determining, by at least one of the first application via the operating system of the customer-facing device or the second application via the operating system of the merchant-facing device, that the payment service system is not accessible via the external network; and
storing the payment data on the merchant-facing device until the payment service system is accessible via the external network.

5. The method as claim 4 recites, further comprising, prior to storing the payment data:
determining, by the second application via the operating system of the merchant-facing device, a risk associated with the transaction;
determining, by the second application via the operating system of the merchant-facing device and based at least in part on the risk, that the transaction is not approved for the payment by the payment service system if the payment data is not authorized for the cost of the transaction after the payment service system is accessible via the external network; and
storing the payment data on the merchant-facing device responsive to an input approving storage of the payment data.

6. The method as claim 1 recites, further comprising:
receiving, by the second application via the operating system of the merchant-facing device, a response from the payment service system, wherein the response indicates an acceptance or a rejection of the payment; and
presenting, by at least one of the first application via the operating system of the customer-facing device or the second application via the operating system of the merchant-facing device, the response via a display associated with at least one of the customer-facing device or the merchant-facing device.

7. The method as claim 1 recites, wherein the input device comprises a payment instrument reader that is controlled by at least one of the first application or the operating system of the customer-facing device.

8. The method as claim 1 recites, wherein sending the payment data to the payment service system comprises sending, by the second application via the operating system of the merchant-facing device, the payment data via a secure communication over the external network.

9. The method as claim 1 recites, further comprising presenting, by the first application via the operating system of the customer-facing device, at least one of the cost of the transaction, a prompt to provide payment data, or a tip user interface via a display associated with the customer-facing device.

10. The method as claim 1 recites, further comprising presenting, by the second application via the operating system of the merchant-facing device, at least one of information associated with the transaction or an authorization user interface via a display associated with the merchant-facing device.

11. A payment system comprising:
a customer-facing device configured with a first application that is provided by a payment service system and that is executable on an operating system of the customer-facing device to (i) display information to a customer and (ii) receive input from the customer, wherein the customer-facing device includes a payment reader to read payment data from a payment instrument presented in association with a transaction between the customer and a merchant; and
a merchant-facing device configured with a second application that is provided by the payment service system and is executable on an operating system of the merchant-facing device to (i) display information to the merchant and (ii) receive input from the merchant,
wherein the first application and the second application are different applications and are associated with a same merchant account associated with the payment service system, wherein the merchant account is created via interactions between the merchant device and the payment service system, and wherein:
the customer-facing device and the merchant-facing device communicate to generate transaction data associated with the transaction;
the transaction data includes the payment data;
at least the merchant-facing device is configured to communicate with the payment service system via an external network for processing payment for the transaction based at least in part on the transaction data; and
the first application and the second application are associated with an account of the merchant associated with the payment service system.

12. The system as claim 11 recites, wherein the customer-facing device and the merchant-facing device are connected via a wired connection.

13. The system as claim 11 recites, wherein the customer-facing device and the merchant-facing device communicate via a secure wireless connection.

14. The system as claim 11 recites, wherein at least one of the first application is executable by the operating system of the customer-facing device or the second application is executable by the operating system of the merchant-facing device further to determine, prior to sending the transaction data to the payment service system, that the payment service system is not accessible via the external network and wherein the merchant-facing device is further configured to store the transaction data until the payment service system is accessible via the external network.

15. The system as claim 14 recites, wherein the second application is executable by the operating system of the merchant-facing device further to:
determine, prior to storing the transaction data, a risk associated with the transaction;
determine, based at least in p

Assignees

• Block Inc

Inventors

• Ruder Edward
• Puls James
• Mulani Mehdi
• Morel Shawn
• Chen Grace
• Clark Christopher R
• Scott J Bryan
• Monti Eric

Classifications

• G06Q20/322 Primary

  Aspects of commerce using mobile devices [M-devices] · CPC title

• G06Q20/4016

  involving fraud or risk level assessment in transaction processing · CPC title

• G06Q20/12 Primary

  specially adapted for electronic shopping systems · CPC title

• G06Q20/3223

  Realising banking transactions through M-devices · CPC title