Cloud-based point-of-sale transaction processing

• US 10,489,767 B2
• Filed: 04/26/2019
• Issued: 11/26/2019
• Est. Priority Date: 06/13/2016
• Status: Active Grant

• Current Assignee: Block, Inc. (f/k/a Square, Inc.)
• Original Assignee: Block, Inc. (f/k/a Square, Inc.)
• Inventors: Muller, Eric Dickeson, Renke, Christopher Philip, Wilson, Mathew
• Primary Examiner(s): Rudy, Andrew Joseph
• Application Number:
  US16/396,520
• Publication Number:
  US 20190251536A1
• Time in Patent Office: 214 Days
• Field of Search: 235376-383, 370338
• CPC Class Codes: G06F 9/54 Interprogram communication
• CPC Class Codes: G06Q 20/0457 the tickets being sent electronically
• CPC Class Codes: G06Q 20/12 specially adapted for electronic shopping systems
• CPC Class Codes: G06Q 20/202 Interconnection or interaction of plural electronic cash registers [ECR] or to host computer, e.g. network details, transfer of information from host to ECR or from ECR to ECR
• CPC Class Codes: G06Q 20/40 Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
• CPC Class Codes: G06Q 30/0633 Lists, e.g. purchase orders, compilation or processing

Abstract

Techniques for processing a transaction using one or more service computing devices of a payment service that processes transactions for multiple merchants including a merchant are described. A first point-of-sale device operable by the merchant is configured to (i) receive, from a first point-of-sale (POS) device operable by the merchant, transaction data indicating an amount to charge a customer for at least one item ordered by the customer from the merchant in a transaction, and (ii) send the transaction data to a second POS device operable by the merchant, and the second POS device is configured to (i) receive the transaction data, (ii) generate payment data via a card reader associated with the second POS device, and (iii) transmit the payment data to a payment gateway for processing payment for the transaction.

Claims

1. A system comprising:

one or more service computing devices associated with a payment service that processes transactions for multiple merchants including a merchant, the one or more service computing devices programmed to perform acts comprising;

exposing at least one application programming interface (API) configured to (i) receive transaction data from a first point-of-sale (POS) device operable by the merchant and (ii) send the transaction data to a second POS device operable by the merchant via the one or more service computing devices, the second POS device including a card reader;

receiving, from the first POS device and via the at least one API, the transaction data associated with a transaction between a customer and the merchant, the transaction data indicating an amount to charge using the card reader for at least one item ordered by the customer from the merchant in the transaction; and

sending, to the second POS device, at least a portion of the transaction data to be used by the second POS device and the card reader for generating payment data associated with a payment card of the customer, the payment data being generated for processing payment for the transaction, at least in part, by the payment service.

2. The system as claim 1 recites, the acts further comprising, prior to receiving the transaction data, receiving, via the at least one API, information describing the merchant, wherein the information describing the merchant includes at least one of a name of the merchant or contact information associated with the merchant, and the information describing the merchant is stored in a database associated with the one or more service computing devices.

3. The system as claim 1 recites, the acts further comprising storing, in a database associated with the one or more service computing devices, at least one record representative of at least one transaction conducted by the merchant.

4. The system as claim 1 recites, the acts further comprising receiving, via the at least one API, information describing the customer, wherein the information describing the customer includes at least one of an identifier of the customer or financial account information of the customer, and the information describing the customer is stored in a database associated with the one or more service computing devices.

5. The system as claim 1 recites, the acts further comprising:

receiving additional transaction data associated with at least one additional transaction between the merchant and at least one additional customer; and

storing the transaction data and the additional transaction data in a queue until at least the portion of the transaction data or the additional transaction data is sent to the second POS device.

6. The system as claim 1 recites, the acts further comprising:

prior to sending at least the portion of the transaction data to the second POS device, receiving, from the second POS device, a request for queued transaction data; and

sending at least the portion of the transaction data responsive to receiving the request.

7. The system as claim 1 recites, the acts further comprising:

receiving, from the second POS device, the payment data generated by the second POS device using the card reader to read the payment data from the payment card; and

sending the payment data to a payment gateway.

8. The system as claim 1 recites, the acts further comprising causing a response indicating whether the payment card is authorized for a cost of the transaction to be sent to the second POS device.

9. The system as claim 1 recites, the acts further comprising sending, to the first POS device and via the at least one API, information associated with the processing of the payment for the transaction by the payment service, the first POS device presenting at least a portion of the information via a display associated with the first POS device.

10. The system as claim 9 recites, the acts further comprising:

receiving, from the first POS device and via the at least one API, a universal resource locator (URL) associated with the transaction data, the URL being associated with the first POS device; and

sending the information to the first POS device based at least in part on the URL.

11. The system as claim 9 recites, wherein presenting at least the portion of the information comprises presenting at least the portion of the information via an electronic receipt.

12. The system as claim 9 recites, the acts further comprising:

receiving, from the second POS device, an indication that payment for the transaction has been processed; and

sending the information to the first POS device responsive to receiving the indication.

13. A method comprising:

exposing, by one or more service computing devices associated with a payment service, at least one interface configured to (i) receive transaction data from a first point-of-sale (POS) device operable by a merchant and (ii) send at least a portion of the transaction data to a second POS device operable by the merchant via the one or more service computing devices, the second POS device being associated with a card reader;

receiving, from the first POS device and via the at least one interface, the transaction data associated with a transaction between a customer and the merchant, the transaction data indicating an amount to charge using the card reader for at least one item ordered by the customer from the merchant in the transaction; and

sending, to the second POS device, at least the portion of the transaction data to be used by the second POS device and the card reader for generating payment data associated with a payment card of the customer, the payment data being generated for processing payment for the transaction, at least in part, by the payment service.

14. The method as claim 13 recites, further comprising receiving, via the at least one interface, information describing at least one of the merchant or the customer, wherein:

the information describing the merchant includes at least one of a name of the merchant or contact information associated with the merchant, and the information describing the merchant is stored in one or more databases associated with the one or more service computing devices; and

the information describing the customer includes at least one of an identifier of the customer or financial account information of the customer, and the information describing the customer is stored in the one or more databases.

15. The method as claim 13 recites, further comprising:

receiving additional transaction data associated with at least one additional transaction between the merchant and at least one additional customer; and

storing the transaction data and the additional transaction data in a queue until at least the portion of the transaction data or the additional transaction data is sent to the second POS device.

16. The method as claim 13 recites, further comprising:

prior to sending at least the portion of the transaction data to the second POS device, receiving, from the second POS device, a request for queued transaction data; and

sending at least the portion of the transaction data responsive to receiving the request.

17. The method as claim 13 recites, further comprising:

receiving, from the second POS device, the payment data generated by the second POS device using the card reader to read the payment data from the payment card; and

sending the payment data to a payment gateway.

18. The method as claim 13 recites, further comprising causing a response indicating whether the payment card is authorized for a cost of the transaction to be sent to the second POS device.

19. The method as claim 13 recites, further comprising sending, to the first POS device and via the at least one interface, information associated with the processing of the payment for the transaction by the payment service, the first POS device presenting at least a portion of the information via a display associated with the first POS device.

20. The method as claim 19 recites, further comprising:

receiving, from the first POS device and via the at least one interface, a universal resource locator (URL) associated with the transaction data, the URL being associated with the first POS device; and

sending the information to the first POS device based at least in part on the URL.

21. The method as claim 19 recites, wherein presenting at least the portion of the information comprises presenting at least the portion of the information via an electronic receipt.

22. The method as claim 19 recites, further comprising:

receiving, from the second POS device, an indication that payment for the transaction has been processed; and

sending the information to the first POS device responsive to receiving the indication.

23. One or more non-transitory computer-readable media storing instructions that, when executed by one or more processors, cause the one or more processors to perform operations comprising:

exposing, by one or more service computing devices associated with a payment service, at least one interface configured to (i) receive transaction data from a first point-of-sale (POS) device operable by a merchant and (ii) send at least a portion of the transaction data to a second POS device operable by the merchant via the one or more service computing devices, the second POS device being associated with a card reader;

receiving, from the first POS device and via the at least one interface, the transaction data associated with a transaction between a customer and the merchant, the transaction data indicating an amount to charge using the card reader for at least one item ordered by the customer from the merchant in the transaction; and

sending, to the second POS device, at least the portion of the transaction data to be used by the second POS device and the card reader for generating payment data associated with a payment card of the customer, the payment data being generated for processing payment for the transaction, at least in part, by the payment service.

24. The one or more non-transitory computer-readable media as claim 23 recites, the operations further comprising receiving, via the at least one interface, information describing at least one of the merchant or the customer, wherein:

the information describing the merchant includes at least one of a name of the merchant or contact information associated with the merchant, and the information describing the merchant is stored in one or more databases associated with the one or more service computing devices; and

the information describing the customer includes at least one of an identifier of the customer or financial account information of the customer, and the information describing the customer is stored in the one or more databases,

and wherein the one or more databases further store at least one record representative of at least one transaction conducted by the merchant.

25. The one or more non-transitory computer-readable media as claim 23 recites, the operations further comprising:

receiving additional transaction data associated with at least one additional transaction between the merchant and at least one additional customer; and

storing the transaction data and the additional transaction data in a queue until at least the portion of the transaction data or the additional transaction data is sent to the second POS device.

26. The one or more non-transitory computer-readable media as claim 23 recites, the operations further comprising:

prior to sending at least the portion of the transaction data to the second POS device, receiving, from the second POS device, a request for queued transaction data; and

sending at least the portion of the transaction data responsive to receiving the request.

27. The one or more non-transitory computer-readable media as claim 23 recites, the operations further comprising:

receiving, from the second POS device, the payment data generated by the second POS device using the card reader to read the payment data from the payment card; and

sending the payment data to a payment gateway.

28. The one or more non-transitory computer-readable media as claim 23 recites, the operations further comprising:

causing a response indicating whether the payment card is authorized for a cost of the transaction to be sent to the second POS device.

29. The one or more non-transitory computer-readable media as claim 23 recites, the operations further comprising sending, to the first POS device and via the at least one interface, information associated with the processing of the payment for the transaction by the payment service, the first POS device presenting at least a portion of the information via a display associated with the first POS device, wherein presenting at least the portion of the information comprises presenting at least the portion of the information via an electronic receipt.

30. The one or more non-transitory computer-readable media as claim 29 recites, the operations further comprising:

receiving at least one of;

(i) a universal resource locator (URL) associated with the transaction data from the first POS device and via the at least one interface, the URL being associated with the first POS device;

or

(ii) an indication from the second POS device that payment for the transaction has been processed; and

sending the information to the first POS device based at least in part on (i) the URL or (ii) the indication.