identifying, by a first server, an electronic document of a customer device to be validated for use across a plurality of second servers;

determining, by the first server, that the electronic document complies with a rule set for the plurality of second servers;

communicating, by the first server, data associated with the electronic document with the plurality of second servers, responsive to determining that the electronic document complies with the rule set;

validating, by the first server via communication of the data with the plurality of second servers, a record of the electronic document to be appended to a plurality of records on a distributed ledger in accordance a consensus algorithm;

generating, by the first server, responsive to the plurality of second servers successfully validating the record of the electronic document, a token using the electronic document;

appending, by the first server, to the plurality of records on the distributed ledger, the record of the electronic document corresponding to the token;

generating, by the first server, an instruction to store the token on a wallet of the customer device to authorize the use of the electronic document across the plurality of second servers;

identifying, by the first server, the electronic document corresponding to a second record of the plurality of records of the distributed ledger as stale based on a time of addition of the second record to the distributed ledger; and

initiating, by the first server, validation of the electronic document from the customer device, responsive to identifying the electronic document as stale.