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 |
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.
|