US 11,677,737 B2
Browser extension for limited-use secure token payment
Matthew de Ganon, Hartsdale, NY (US); Kunal Arora, Great Falls, VA (US); Thomas Poole, Chantilly, VA (US); Daniel Kahn, San Francisco, CA (US); Dwij Trivedi, Oakton, VA (US); and Paul Moreton, Glen Allen, VA (US)
Assigned to Capital One Services LLC, McLean, VA (US)
Filed by Capital One Services LLC, McLean, VA (US)
Filed on Jul. 6, 2021, as Appl. No. 17/368,385.
Application 17/368,385 is a continuation of application No. 16/899,144, filed on Jun. 11, 2020, granted, now 11,089,003.
Application 16/899,144 is a continuation of application No. 16/700,645, filed on Dec. 2, 2019, granted, now 10,887,299, issued on Jan. 5, 2021.
Application 16/700,645 is a continuation of application No. 15/381,070, filed on Dec. 15, 2016, granted, now 10,498,717, issued on Dec. 3, 2019.
Claims priority of provisional application 62/267,996, filed on Dec. 16, 2015.
Prior Publication US 2021/0336941 A1, Oct. 28, 2021
This patent is subject to a terminal disclaimer.
Int. Cl. G06F 16/954 (2019.01); G06F 21/62 (2013.01); G06F 21/31 (2013.01); G06Q 20/12 (2012.01); G06Q 20/38 (2012.01); G06F 40/174 (2020.01); G06Q 20/40 (2012.01); H04L 9/40 (2022.01)
CPC H04L 63/08 (2013.01) [G06F 16/954 (2019.01); G06F 21/31 (2013.01); G06F 21/6263 (2013.01); G06F 40/174 (2020.01); G06Q 20/12 (2013.01); G06Q 20/38215 (2013.01); G06Q 20/4014 (2013.01); H04L 63/1441 (2013.01); H04L 63/168 (2013.01)] 20 Claims
OG exemplary drawing
 
1. A browser extension server, comprising:
a communication device configured to communicate with (i) a first computing device associated with a user and executing a browser extension application and a web browser application, and (ii) a second computing device executing an authentication application;
a memory storing instructions; and
at least one processor configured to execute the instructions to perform operations comprising:
detecting, via flail the browser extension application, a payment field in a web page received at the first computing device;
providing, to the first computing device, an option to generate a secure token;
receiving, via the second computing device, an acceptance of the option;
in response to receiving the acceptance and to the user being authenticated based on a user authentication response, obtaining, via a server, the secure token mapped to a financial service account associated with the user; and
populating, by the browser extension application and in response to obtaining the secure token, the payment field in the web page with the secure token, wherein the secure token is configured to enable a purchase transaction with a merchant via the web page, and wherein a provider of the financial service account is configured to send a communication authorizing the purchase transaction.