Secure apparatus to share and deploy machine build programs utilizing unique hash tokens

A computer program product for secure apparatuses to share and deploy machine build programs utilizing unique hash tokens, the computer program product comprising a non-transitory computer-readable medium comprising code causing an apparatus to:

• generate a first non-fungible token comprising a resource machine build-program, wherein the resource machine build-program comprises software program designed to execute one or more functions of an automated teller machine (ATM);
• store the first non-fungible token into a Universal Serial Bus (USB) flash drive;
• generate a second non-fungible token during an interaction of a resource machine with the USB flash drive, wherein the second non-fungible token includes data representing an ownership certificate for the resource machine build owned by a vendor;
• generate a resultant integrated third non-fungible token, wherein the third non-fungible token is generated by combining the first non-fungible token and the second non-fungible token;
• confirm an integrity of the first non-fungible token, the second non-fungible token, and the third non-fungible token by computing a hash of data associated with each non-fungible token and comparing the hash to metadata associated with each non-fungible token;
• and
• deploy the resource machine build-program on the resource machine, wherein the activation is triggered by the generation of the third non-fungible token.

A method for secure apparatuses to share and deploy machine build programs utilizing unique hash tokens, the method comprising:

• generating a first non-fungible token comprising a resource machine build-program, wherein the resource machine build-program comprises software program designed to execute one or more functions of an automated teller machine (ATM);
• storing the first non-fungible token into a Universal Serial Bus (USB) flash drive;
• generating a second non-fungible token during an interaction of a resource machine with the USB flash drive, wherein the second non-fungible token includes data representing an ownership certificate for the resource machine build owned by a vendor;
• generating a resultant integrated third non-fungible token, wherein the third non-fungible token is generated by combining the first non-fungible token and the second non-fungible token;
• confirming integrity of the first non-fungible token, the second non-fungible token, and the third non-fungible token by computing a hash of data associated with each non-fungible token and comparing the hash to metadata associated with each non-fungible token;
• and
• deploying the resource machine build-program on the resource machine, wherein the activation is triggered by the generation of the third non-fungible token.