US 11,720,983 B2
System to text a payment link
Touradj Barman, San Diego, CA (US)
Assigned to UP N' GO, San Diego, CA (US)
Filed by UP N' GO, San Diego, CA (US)
Filed on Oct. 1, 2021, as Appl. No. 17/491,935.
Application 17/491,935 is a continuation of application No. 16/878,600, filed on May 19, 2020, granted, now 11,158,009.
Application 16/878,600 is a continuation of application No. 16/683,252, filed on Nov. 13, 2019, granted, now 10,699,264, issued on Jun. 30, 2020.
Application 16/683,252 is a continuation of application No. 15/446,849, filed on Mar. 1, 2017, abandoned.
Claims priority of provisional application 62/953,312, filed on Dec. 24, 2019.
Claims priority of provisional application 62/413,236, filed on Oct. 26, 2016.
Claims priority of provisional application 62/302,472, filed on Mar. 2, 2016.
Prior Publication US 2022/0020101 A1, Jan. 20, 2022
Int. Cl. G06Q 50/12 (2012.01); G06Q 20/10 (2012.01); G06Q 20/32 (2012.01); G06Q 20/02 (2012.01); H04M 15/00 (2006.01); H04M 17/02 (2006.01); H04W 4/24 (2018.01); G06Q 20/14 (2012.01); H04M 17/00 (2006.01); G06Q 20/20 (2012.01); G06Q 20/24 (2012.01); H04L 67/02 (2022.01)
CPC G06Q 50/12 (2013.01) [G06Q 20/02 (2013.01); G06Q 20/102 (2013.01); G06Q 20/14 (2013.01); G06Q 20/20 (2013.01); G06Q 20/24 (2013.01); G06Q 20/327 (2013.01); G06Q 20/3223 (2013.01); G06Q 20/3255 (2013.01); G06Q 20/3276 (2013.01); H04M 15/00 (2013.01); H04M 15/68 (2013.01); H04M 15/844 (2013.01); H04M 17/02 (2013.01); H04M 17/106 (2013.01); H04W 4/24 (2013.01); H04L 67/02 (2013.01)] 18 Claims
OG exemplary drawing
 
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.