US 12,223,500 B2
Transaction account data maintenance using blockchain
Faraz Babar, Paradise Valley, AZ (US); Aimee Cardwell, Plymouth, MA (US); Andras L. Ferenczi, Peoria, AZ (US); Dallas Gale, Scottsdale, AZ (US); Nilesh Yashavant Jadhav, Phoenix, AZ (US); Ashish Kumar, Bangalore (IN); Harish R. Naik, Phoenix, AZ (US); and Lavanya Venkatanarayanan, Phoenix, AZ (US)
Assigned to AMERICAN EXPRESS TRAVEL RELATED SERVICES COMPANY, INC., New York, NY (US)
Filed by American Express Travel Related Services Company, Inc., New York, NY (US)
Filed on Feb. 9, 2022, as Appl. No. 17/667,806.
Application 17/667,806 is a continuation of application No. 16/220,235, filed on Dec. 14, 2018, granted, now 11,282,076.
Prior Publication US 2022/0270089 A1, Aug. 25, 2022
Int. Cl. G06Q 20/38 (2012.01); G06Q 20/40 (2012.01); H04L 9/06 (2006.01)
CPC G06Q 20/3827 (2013.01) [G06Q 20/401 (2013.01); G06Q 20/405 (2013.01); H04L 9/0637 (2013.01)] 20 Claims
OG exemplary drawing
 
1. A method, comprising:
receiving, by at least one computing device, an account registration request from a client device associated with a user, the account registration request comprising transaction account data of a transaction account of the user and an issuer identifier associated with an issuer system, and the transaction account being provided by the issuer system;
requesting, by the at least one computing device, a credential from a credential issuing authority;
obtaining, by the at least one computing device, the credential from the credential issuing authority in response to the credential issuing authority verifying an entity associated with the at least one computing device;
generating, by the at least one computing device, a registration account hash based at least in part on the transaction account data;
generating, by the at least one computing device, an account record by invoking a maintenance smart contract, the maintenance smart contract being invoked by passing the registration account hash, one or more transaction account data, the issuer identifier, and the credential in a call to the maintenance smart contract;
writing, by the at least one computing device and via the maintenance smart contract, the account record to a distributed ledger, an identity of the entity associated with the at least one computing device being concealed based at least in part on the credential;
notifying, by the at least one computing device and via the maintenance smart contract, the issuer system associated with the transaction account that the account record has been written to the distributed ledger, the issuer system being configured to update the account record and associate the account record with an updated account hash in response to an update to the transaction account by the issuer system;
generating, by the at least one computing device, a transaction request account hash based at least in part on stored transaction account data in response to receiving a transaction request;
updating, by the at least one computing device, the stored transaction account data based at least in part on updated transaction account data received from the issuer system in response to the transaction request account hash matching a past account hash and failing to match a primary account hash; and
authorizing, by the at least one computing device, the transaction request based at least in part on the updated transaction account data included in the account record.