US 11,783,342 B1
Blockchain blacklist anti-money laundering system (BBAMLS)
Phillip H. Griffin, Raleigh, NC (US)
Assigned to Wells Fargo Bank, N.A., San Francisco, CA (US)
Filed by Wells Fargo Bank, N.A., San Francisco, CA (US)
Filed on Jul. 9, 2019, as Appl. No. 16/506,498.
Int. Cl. G06Q 20/40 (2012.01); H04L 9/06 (2006.01); H04L 9/32 (2006.01); H04L 9/00 (2022.01)
CPC G06Q 20/4016 (2013.01) [G06Q 20/4014 (2013.01); H04L 9/0637 (2013.01); H04L 9/3263 (2013.01); H04L 9/50 (2022.05); H04L 2209/56 (2013.01)] 30 Claims
OG exemplary drawing
 
1. A method comprising:
receiving, by one or more processors and from an entity device associated with an entity, a request to execute a transaction between a blockchain of a computing system corresponding to an organization associated with the one or more processors and the entity device;
extracting by the one or more processors and from a digital certificate in response to a determination that the blockchain is restricted to predetermined members, a component including a first entity identifier identifying the entity device;
extracting, by the one or more processors and from the digital certificate in response to a determination that the blockchain is compatible with a request from an anonymous entity device, the component including the first key identifier and a first public key;
maintaining, by the one or more processors and in a sanctioned list storage, a sanctioned entity blacklist having one or second key identifiers, second entity identifiers and second public keys each indicating that a respective entity has a sanctioned entity status prohibiting the respective entity from performing a transaction with the blockchain of the computing system;
authenticating, by the one or more processors, the entity device to the blockchain by identifying one or more of a first match between the first key identifier and one of the second key identifiers, a second match between the first public key and one of the second public keys, and a third match between the first entity identifier and one or more the second entity identifiers;
generating, by the one or more processors responsive to one or more of the first match, the second match and the third match, an error condition indicating that the digital certificate failed validation;
blocking, by the one or more processors responsive to the generating the error condition, the transaction between the entity device and the blockchain of the computing system, system; and
inserting, by the one or more processors into a smart contract linked to the entity device responsive to the generating the error condition, code to prevent execution of the smart contract.