A computer-implemented method, comprising: receiving, by a processor, a transaction request comprising merchant-stored transaction account data; generating, by the processor, an account hash comprising a cryptographic hash of at least one data element from the merchant-stored transaction account data; determining, by the processor and in response to invoking a maintenance smart contract, that the account hash matches a primary account hash or a past account hash that is associated with the primary account hash, the primary account hash and the past account hash being stored in a distributed ledger, the past account hash having a primary hash designation prior to the primary account hash being written to the distributed ledger, and the maintenance smart contract being invoked by passing the account hash and at least one data element from the merchant-stored transaction account data to the maintenance smart contract; receiving, by the processor, an updated account hash from the maintenance smart contract in response to the maintenance smart contract determining that the account hash matches the past account hash instead of the primary account hash, the updated account hash corresponding to the primary account hash; transmitting, by the processor, the updated account hash and the account hash to an issuer system, the issuer system being configured to determine an updated transaction account data based at least in part on the updated account hash in response to receiving the updated account hash and the account hash, wherein transmitting the updated account hash and the account hash to the issuer system comprises invoking a private smart contract to establish a communication between a merchant system and the issuer system; updating, by the processor, the merchant-stored transaction account data based at least in part on the updated transaction account data from the issuer system; and authorizing, by the processor, the transaction request in response to receiving the updated transaction account data from the issuer system. receiving, by a processor, a transaction request comprising merchant-stored transaction account data; generating, by the processor, an account hash comprising a cryptographic hash of at least one data element from the merchant-stored transaction account data; determining, by the processor and in response to invoking a maintenance smart contract, that the account hash matches a primary account hash or a past account hash that is associated with the primary account hash, the primary account hash and the past account hash being stored in a distributed ledger, the past account hash having a primary hash designation prior to the primary account hash being written to the distributed ledger, and the maintenance smart contract being invoked by passing the account hash and at least one data element from the merchant-stored transaction account data to the maintenance smart contract; receiving, by the processor, an updated account hash from the maintenance smart contract in response to the maintenance smart contract determining that the account hash matches the past account hash instead of the primary account hash, the updated account hash corresponding to the primary account hash; transmitting, by the processor, the updated account hash and the account hash to an issuer system, the issuer system being configured to determine an updated transaction account data based at least in part on the updated account hash in response to receiving the updated account hash and the account hash, wherein transmitting the updated account hash and the account hash to the issuer system comprises invoking a private smart contract to establish a communication between a merchant system and the issuer system; updating, by the processor, the merchant-stored transaction account data based at least in part on the updated transaction account data from the issuer system; and authorizing, by the processor, the transaction request in response to receiving the updated transaction account data from the issuer system.