US 12,278,837 B2
Anti-phish network for securing electronic communications
Michael Young, Davidson, NC (US); Vinesh Patel, London (GB); and Melissa Gordon Glenn, Charlotte, NC (US)
Assigned to Bank of America Corporation, Charlotte, NC (US)
Filed by Bank of America Corporation, Charlotte, NC (US)
Filed on Apr. 18, 2022, as Appl. No. 17/722,722.
Prior Publication US 2023/0336587 A1, Oct. 19, 2023
This patent is subject to a terminal disclaimer.
Int. Cl. H04L 9/00 (2022.01); H04L 9/40 (2022.01); H04L 51/212 (2022.01)
CPC H04L 63/1483 (2013.01) [H04L 51/212 (2022.05); H04L 63/0428 (2013.01)] 12 Claims
OG exemplary drawing
 
1. A system for securing electronic communications, the system comprising:
an originating server comprising a hardware processor and memory, said originating server located at an entity location associated with an entity;
an edge server located at the entity location;
a third-party server located at a third-party location;
a database located at the entity location;
wherein during a registration process:
the originating server receives a request from a user, the request to receive an anti-phish, personalized, security token with each electronic communication from the entity;
the originating server displays a plurality of selectable options for the anti-phish, personalized, security token, the plurality of selectable options comprising a dynamically-rotating, digital-artwork file linked to a non-fungible token (“NFT”), said digital-artwork file that rotates on a predetermined schedule;
the originating server receives a selection of an option for the anti-phish, personalized, security token, the option included in the plurality of selectable options;
the originating server registers the selected option as being linked to a profile associated with the user; and
the originating server stores, in the database, the anti-phish, personalized, security token linked to the profile associated with the user;
wherein during an in-use process:
the third-party server generates an electronic communication on behalf of the entity, where a recipient of the electronic communication is the user;
the third-party server forwards the electronic communication to the edge server;
the edge server retrieves, from the database, the anti-phish, personalized, security token linked to the profile associated with the user; and
the edge server populates the electronic communication with the anti-phish, personalized, security token.