IP Library Granted Patent US 11,720,983
Granted Patent B2
US 11,720,983 · App. 17/491,935 · Granted Aug 8, 2023

System to text a payment link

Inventor: Touradj Barman (San Diego, CA)
Assignee: UP N' GO
G06Q50/12G06Q20/02G06Q20/102G06Q20/14G06Q20/20G06Q20/24G06Q20/327G06Q20/3223G06Q20/3255G06Q20/3276H04M15/00H04M15/68H04M15/844H04M17/02H04M17/106H04W4/24H04L67/02
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,720,983
App. No.
17/491,935
Granted
Aug 8, 2023
Kind
B2
Abstract

Systems and methods are disclosed to facilitate payment of a restaurant bill via text message. For example, a text message having a restaurant bill code may be sent from a customer device to an MPS phone number. A restaurant network address may be extracted for a restaurant computing system. A query may be sent to the restaurant computing system using the restaurant network address with the restaurant bill code. In response, the restaurant computing system may send restaurant bill data that includes least one restaurant menu item, a price for the at least one restaurant menu item, and a total bill amount. A unique URL may be created that when entered into a web browser presents a webpage that includes at least the restaurant bill data. The unique URL may be used by the customer to pay the restaurant bill.

Claims (51)

1. A token payment method comprising:

receiving, at a token server from a restaurant computing system, a new order, wherein the order comprises a token identifier and a customer phone number;

sending, from the token server to the restaurant computing system, a request for restaurant bill information linked to the token identifier;

receiving, at the token server, the restaurant bill information, wherein the restaurant bill information comprises at least one restaurant menu item and at least one price for the at least one restaurant menu item;

creating, at the token server, a unique webpage that shows the at least one restaurant menu item, the at least one price for the at least one restaurant menu item, and a payment field;

creating, at the token server, a unique URL, wherein the URL comprises the token identifier, and wherein the token identifier identifies the linked restaurant bill information;

sending, from the token server, the unique URL to a customer mobile device using the customer phone number via a text message, such that the URL when entered into a web browser in the customer mobile device displays the unique webpage;

receiving, at the token server from the customer mobile device, a notification of successful payment after receiving payment data from the customer mobile device via the unique webpage;

sending, from the token server, payment confirmation to the restaurant computing system.

2. The method according to claim 1 , wherein the payment field comprises a field for receiving credit card information from the customer mobile device.

3. The method according to claim 1 , wherein the restaurant bill information further comprises a table identifier, an order identifier, a guest identifier, multiple menu items, prices for the multiple menu items, tax, tip, a discount code, and total amount due.

4. The method according to claim 1 , wherein the new order is received at the restaurant computing system through a third-party computing system, wherein the third-party computing system comprises an online reservation system that requires the customer phone number.

5. The method according to claim 1 , wherein the restaurant bill information further comprises items ordered by at least two people for the same token identifier, prices for the items ordered by the at least two people, a table number, restaurant bill code, tips, tax, total amount due, date and time stamps related to the order.

6. The method according to claim 1 , further comprising:

receiving, at the token server from the customer mobile device, a request for a restaurant bill, wherein the restaurant bill comprises the restaurant bill information.

7. The method according to claim 1 , wherein the URL comprises encoded data, wherein the encoded data comprises the customer phone number.

8. The method according to claim 1 , wherein the payment confirmation, sent from the token server to the restaurant computing system, comprises payment information including information identifying one or more payment methods used by the customer.

9. The method according to claim 1 , further comprising:

setting, at the token server, a token status as paid or unpaid, wherein the token status is associated to the token identifier of the order.

10. The method according to claim 9 , further comprising:

sending, from the token server to a token device, the token status via the restaurant payment system, wherein the token device signals the paid or unpaid status of the order with an indicator such as a built-in display or an LED.

11. A payment method comprising:

receiving, at a token server from a restaurant computing system, a restaurant reservation for an order that includes a token identifier, menu items ordered, and a customer phone number;

sending, from the token server to the restaurant computing system, a request for restaurant bill information linked to the token identifier;

receiving, at the token server, the restaurant bill information, wherein the restaurant bill information comprises at least one restaurant menu item of the menu items ordered, at least one price for the at least one restaurant menu item, and total amount due;

creating, at the token server, a series of unique webpages that show the at least one restaurant menu item, the at least one price for the at least one restaurant menu item, the total amount due, and a payment field;

creating, at the token server, a unique URL, wherein the URL comprises the token identifier, and wherein the token identifier identifies the linked restaurant bill information;

sending, from the token server, the unique URL to the customer mobile device using the customer phone number via a text message, such that the URL when entered into a web browser in the customer mobile device displays the series of unique webpages;

receiving, at the token server from the customer mobile device, a notification of successful payment after receiving payment data from the customer mobile device via the series of unique webpages;

sending, from the token server, payment confirmation to the restaurant computing system.

12. The payment method according to claim 11 , wherein the payment field comprises a field for receiving credit card information from the customer mobile device.

13. The payment method according to claim 11 , wherein the URL comprises encoded data, wherein the encoded data comprises the customer phone number.

14. The payment method according to claim 11 , wherein the restaurant bill information further comprises multiple menu items, prices for the multiple menu items, tax, tip, surcharges, reward payment, offer codes, a discount code, a table identifier, an order identifier, and a guest identifier.

15. The payment method according to claim 11 , further comprising:

receiving, at the token server from the customer mobile device, a request for a restaurant bill, wherein the restaurant bill comprises the restaurant bill information.

16. A method of processing a check, the method comprising:

receiving, at a first computing system from a restaurant computing system, an order, an order number for the order, and a customer phone number related to the order;

linking, at the first computing system, the customer phone number and the order number with a specific restaurant bill associated with the order;

creating, at the first computing system, a webpage that shows the restaurant bill;

creating, at the first computing system, a unique URL for the order associated with the order number, such that the URL directs a customer device to the webpage;

sending, from the first computing system, the unique URL to the customer phone number as a text message;

receiving, at the first computing system, an updated order information;

creating, at the first computing system, an updated webpage that shows the updated restaurant bill based on the updated order information;

creating, at the first computing system, an updated URL that directs the customer device to the updated webpage;

resending, from the first computing system, the updated URL to the customer phone number as a text message;

receiving, at the first computing system, payment data from the customer device linked to the customer phone number, via the updated webpage linked to the updated URL;

sending, from the first computing system, an indication to the restaurant computing system that a payment for the order number has been made; and

sending, from the first computing system, a confirmation code to the customer device indicating that a transaction has been completed successfully.

17. The method according to claim 16 , wherein the webpage linked to the URL is a unique webpage or a series of unique webpages, wherein the webpage display comprises the order, the updated order, at least a portion of the restaurant bill data, a signature field, a payment field, and a tip entry field.

18. The method according to claim 16 , further comprising:

sending the webpage with the restaurant bill to the customer device, wherein the restaurant bill comprises at least one restaurant menu item, at least one price for the at least one restaurant menu item, a tip entry field, and a total bill amount that is dynamically calculated based on entries in the tip entry field.

Assignments (2)
CORRECTIVE ASSIGNMENT TO CORRECT THE ERRONEOUS ASSIGNEE UP N' GO WHICH SHOULD HAVE BEEN UPNGO, INC. PREVIOUSLY RECORDED AT REEL: 057859 FRAME: 0790. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded Sep 11, 2023
From: BARMAN, TOURADJ
To: UPNGO, INC.
Reel/Frame 064859/0686 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 19, 2021
From: BARMAN, TOURADJ
To: UP N' GO
Reel/Frame 057859/0790 →
Continuity (7)
Continuation 16878600 · May 19, 2020
Continuation 16683252 · Nov 13, 2019
Continuation 15446849 · Mar 1, 2017
Provisional Application 62953312 · Dec 24, 2019
Provisional Application 62413236 · Oct 26, 2016
Provisional Application 62302472 · Mar 2, 2016
Related Publication 20220020101A1 · Jan 20, 2022