Customized tipping flow

• US 10,410,194 B1
• Filed: 08/19/2015
• Issued: 09/10/2019
• Est. Priority Date: 08/19/2015
• Status: Active Grant

• Current Assignee: Block, Inc. (f/k/a Square, Inc.)
• Original Assignee: Block, Inc. (f/k/a Square, Inc.)
• Inventors: Grassadonia, Brian
• Primary Examiner(s): Madamba, Clifford B
• Application Number:
  US14/830,659
• Time in Patent Office: 1,483 Days
• Field of Search: 705 40
• CPC Class Codes: G06Q 20/102 Bill distribution or payments
• CPC Class Codes: G06Q 20/14 specially adapted for billing 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/204 comprising interface for record bearing medium or carrier for electronic funds transfer or payment credit
• CPC Class Codes: G06Q 20/322 Aspects of commerce using mobile devices [M-devices]
• CPC Class Codes: G06Q 20/3223 Realising banking transactions through M-devices
• CPC Class Codes: G06Q 20/326 Payment applications installed on the mobile devices
• CPC Class Codes: G06Q 20/327 Short range or proximity payments by means of M-devices
• CPC Class Codes: G06Q 20/3278 RFID or NFC payments by means of M-devices
• 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 50/12 Hotels or restaurants

Abstract

Disclosed is a technology for customizing the flow of a payment transaction at a payer'"'"'s mobile device, based on parameters associated with a merchant payee to which the payer is making the payment. The payee can be a business entity that conducts transactions involving tips (e.g., restaurant, professional service, etc.). The transaction flow technology involves communication between a mobile application installed on the mobile device and a remote payment service system (PSS). A list of potential payees can be displayed for selection by the payer at the mobile application. The payees can be nearby payees identified by using, e.g., BLE, Bluetooth®, Wi-Fi®, geofence, etc. Upon selection of a particular payee by the payer, the PSS identifies one or more parameters of that payee, e.g., payee type, and generates a transaction flow that includes a tipping flow corresponding to the parameters of the merchant payee.

Claims

1. A method performed by a payment service system for customizing tipping within a payment transaction, comprising:

detecting, by a payment application associated with the payment service system, a mobile device being in proximity to a point-of-sale (POS) device associated with a merchant, the payment application executing on the mobile device, the mobile device associated with a payer;

responsive to said detecting, automatically generating, by the payment service system, a merchant identifier associated with the merchant for display to the payer on a user interface of the payment application executing on the mobile device, wherein the user interface comprises one or more of user-selectable indicators, including a user-selectable indicator corresponding to the merchant identifier, and selection of a user-selectable indicator results in transmitting a selection of the merchant identifier to the payment service system;

receiving, by the payment service system and via the payment application, the selection of the merchant identifier, said selection indicative of selecting the user-selectable indicator corresponding to the merchant identifier and a request of the payer to engage in a payment transaction with the merchant;

accessing, by the payment service system, a database including information associated with multiple merchant identifiers to identify a set of parameters associated with the merchant identifier, wherein the set of parameters comprises a merchant type, wherein the merchant type specifies a type of service or good that the merchant provides;

analyzing, by the payment service system, the set of parameters and responsively generating, for display via the payment application at the mobile device, an invoice for the payment transaction based on the set of parameters, said generating the invoice including;

selecting, from the database of the payment service system in response to identifying the set of parameters, a particular tipping flow from a set of tipping flows included in the invoice, the set of tipping flows being different from one another based on the set of parameters, wherein the particular tipping flow comprises a number of user interfaces, customized based on the merchant type, to complete a payment from the mobile device to the payment service system, and wherein the number is determined based at least in part on the merchant type;

causing, by the payment service system, the particular tipping flow to be initiated automatically at the payment application, the particular tipping flow enabling the payer to pay the invoice and complete the particular tipping flow with the merchant through the payment application, wherein the particular tipping flow is incorporated with the invoice; and

presenting the invoice and the series of user interfaces to the payer at the mobile device;

receiving, by the payment service system, a payment approval for the invoice from the mobile device; and

based at least in part on the payment approval, automatically causing an invoice amount associated with the invoice to be transferred from a financial account associated with the payer to a financial account associated with the merchant.

2. The method of claim 1, wherein the particular tipping flow selected is a first tipping flow, the first tipping flow associated with a first set of parameters corresponding to a restaurant merchant, wherein initiating the first tipping flow comprises:

generating a set of tipping amounts, incorporated with the invoice, for selection by the payer by interacting with the invoice presented at the mobile device, the set of tipping amounts predefined based on the first set of parameters corresponding to the restaurant merchant; and

receiving a particular tipping amount from the set of tipping amounts from the mobile device; and

generating the invoice amount for the invoice based on the particular tipping amount, the invoice amount including the particular tipping amount and a payment amount associated with the payment transaction.

3. The method of claim 1, wherein the particular tipping flow selected is a second tipping flow, the second tipping flow associated with a second set of parameters corresponding to a quick service merchant, wherein initiating the second tipping flow comprises:

determining a predefined tipping amount based on the second set of parameters corresponding to the quick service merchant; and

generating the invoice amount for the invoice based on the predefined tipping amount, the invoice amount including the predefined tipping amount and a payment amount associated with the payment transaction.

4. The method of claim 1, wherein causing the invoice amount to be transferred comprises:

identifying, by the payment service system, the financial account associated with the payer based on a payer identifier associated with the payer, the payer identifier submitted as login credentials for accessing the payment application by the payer at the mobile device;

identifying, by the payment service system, the financial account associated with the merchant based on the merchant identifier; and

transmitting, by the payment service system, funds indicative of the invoice amount from the financial account associated with the payer to the financial account associated with the merchant.

5. The method of claim 1, wherein generating the merchant identifier comprises:

accessing, by the payment service system, the database to identify the merchant identifier based on association data stored in the database, the association data linking the POS device with the merchant identifier; and

presenting, by the payment service system, the merchant identifier via the payment application.

6. The method of claim 1, wherein the mobile device is detected in proximity to the POS device by using any of:

a low energy wireless communication feature associated with the mobile device, a short range wireless communication feature associated with the mobile device, or a wireless communication feature associated with the mobile device.

7. A method, comprising:

receiving, by a payment service system from a user interface of a mobile device, an indication of a request of a payer to engage in a transaction with a payee, wherein the user interface comprises one or more of user-selectable indicators, including a user-selectable indicator corresponding to the payee;

identifying, by the payment service system from a database of the payment service system, a set of parameters associated with the payee, wherein the set of parameters includes a first payee type of a plurality of payee types, wherein the first payee type specifies a type of service or good that the payee provides; and

generating, by the payment service system, an invoice for the transaction;

wherein the invoice comprises a particular invoice type corresponding to the first payee type and a particular tipping flow selected based at least in part on the first payee type, and

wherein the particular tipping flow comprises a number of user interfaces, customized based on the first payee type, to complete a payment from the mobile device to the payment service system, wherein the number is determined based at least in part on the first payee type.

8. The method of claim 7, wherein the set of parameters further include a payee description and a payee transaction history.

9. The method of claim 8, wherein the particular tipping flow selected corresponds to the first payee type, wherein the particular tipping flow includes a set of tipping amounts for selection by the payer, the set of tipping amounts predefined based on the set of parameters.

10. The method of claim 7, wherein the first payee type is any of a restaurant type or a professional service type.

11. The method of claim 9, further comprising:

generating the set of tipping amounts, incorporated with the invoice, for selection by the payer by interacting with the invoice presented at the mobile device; and

receiving a particular tipping amount from the set of tipping amounts from the mobile device; and

generating an invoice amount for the invoice based on the particular tipping amount, the invoice amount including the particular tipping amount and a transaction amount associated with the transaction.

12. The method of claim 8, wherein the particular tipping flow selected corresponds to a second payee type, wherein the particular tipping flow includes a predefined tipping amount determined based on a second set of parameters corresponding to the second payee type.

13. The method of claim 12, wherein the second payee type is any of a quick service type.

14. The method of claim 12, further comprising:

generating an invoice amount for the invoice based on the predefined tipping amount, the invoice amount including the predefined tipping amount and a transaction amount associated with the transaction.

15. The method of claim 7, wherein the indication is received based, at least in part, on the mobile device being in proximity to a payee device associated with the payee.

16. The method of claim 7, wherein the indication is received based, at least in part, on a selection of a payee identifier associated with the payee, said selection received as an input in a payment application executing on the mobile device of the payer.

17. A payment service system, comprising:

a database;

a memory;

a processor coupled to the memory and in communication with the database; and

a transaction flow engine coupled to the processor and configured to;

receive a selection of a payee identifier from a user interface of a mobile device of a payer, wherein the user interface comprises one or more of user-selectable indicators, including a user-selectable indicator corresponding to the payee identifier;

identify a set of parameters associated with the payee, wherein the set of parameters includes a first payee type of a plurality of payee types, wherein the first payee type specifies a type of service or good that the payee provides;

select, from the database in response to identifying the set of parameters, a first tipping flow from a set of tipping flows included in an invoice for a transaction between the payer and the payee, wherein the first tipping flow is selected based on the first payee type, the set of tipping flows being different from one another based on the set of parameters, wherein the first tipping flow comprises a number of user interfaces, customized based on the first payee type, to complete a payment from the mobile device to the payment service system, wherein the number is determined based at least in part on the first payee type;

initiate the first tipping flow to incorporate the first tipping flow into the invoice;

generate a set of tipping amounts, the set of tipping amounts predefined based at least in part on the first payee type;

transmit the invoice with the set of tipping amounts to the mobile device for selection by the payer;

receive a particular tipping amount from the set of tipping amounts from the mobile device; and

generate an invoice amount for the invoice based on the particular tipping amount, the invoice amount including the particular tipping amount and a transaction amount associated with the transaction, wherein the invoice comprises a particular invoice type corresponding to the first payee type.

18. The payment service system of claim 17, wherein the first tipping flow corresponds to a first set of parameters, the first set of parameters corresponding to a restaurant payee, wherein the transaction flow engine is further configured to:

receive a payment approval for the invoice from the mobile device; and

based at least in part on the payment approval, cause the invoice amount to be transferred from a financial account associated with the payer to a financial account associated with the payee.

19. The payment service system of claim 17, wherein the transaction flow engine is further configured to:

select, based on the set of parameters, a second tipping flow from the set of tipping flows included in the invoice for the transaction between the payer and the payee;

initiate the second tipping flow into included in the invoice;

determine a predefined tipping amount based on the set of parameters; and

generate a second invoice amount for the invoice based on the predefined tipping amount, the second invoice amount including the predefined tipping amount and the transaction amount associated with the transaction.

20. The payment service system of claim 17, wherein the set of parameters further include a payee description and a payee transaction history.