Transaction account data maintenance using blockchain

A system, comprising:

• a computing device comprising a processor and a memory;
• and
• machine-readable instructions stored in the memory, that when executed by the processor, cause the computing device to at least:
• receive 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;
• request a credential from a credential issuing authority;
• obtain 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;
• generate a registration account hash based at least in part on the transaction account data;
• generate 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;
• write, via the maintenance smart contract, the account record to a distributed ledger, an identity of the entity associated with the computing device being concealed based at least in part on the credential;
• notify, 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;
• generate a transaction request account hash based at least in part on stored transaction account data in response to receiving a transaction request;
• update 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
• authorize the transaction request based at least in part on the updated transaction account data included in the account record.

A non-transitory computer-readable medium, comprising machine-readable instructions that, when executed by a processor of a computing device, cause the computing device to at least:

• receive 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;
• request a credential from a credential issuing authority;
• obtain 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;
• generate a registration account hash based at least in part on the transaction account data;
• generate 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;
• write, via the maintenance smart contract, the account record to a distributed ledger, an identity of the entity associated with the computing device being concealed based at least in part on the credential;
• notify, 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;
• generate a transaction request account hash based at least in part on stored transaction account data in response to receiving a transaction request;
• update 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
• authorize the transaction request based at least in part on the updated transaction account data included in the account record.