US 12,069,037 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 May 2, 2023, as Appl. No. 18/311,017.
Application 18/311,017 is a continuation of application No. 17/368,385, filed on Jul. 6, 2021, granted, now 11,677,737.
Application 17/368,385 is a continuation of application No. 16/899,144, filed on Jun. 11, 2020, granted, now 11,089,003, issued on Aug. 10, 2021.
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 2023/0269243 A1, Aug. 24, 2023
This patent is subject to a terminal disclaimer.
Int. Cl. H04L 9/40 (2022.01); G06F 16/954 (2019.01); G06F 21/31 (2013.01); G06F 21/62 (2013.01); G06F 40/174 (2020.01); G06Q 20/12 (2012.01); G06Q 20/38 (2012.01); G06Q 20/40 (2012.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 system for populating a data field with a secure token, the system comprising one or more processors and a memory storing program instructions that, when executed by the one or more processors, causes the one or more processors to perform operations comprising:
sending, by a browser extension application, a set of messages to a server, the set of messages comprising an indication of a field in a web page and an indication of an account;
receiving an option to generate a secure token, wherein the secure token is mapped to the account;
generating, by the browser extension application, the secure token based on a response indicating an acceptance of the option;
sending the secure token to the server; and
populating, by the browser extension application, the field in the web page with the secure token.