Data manifest as a blockchain service

A system comprising:

• a first computing system comprising a first processor and a first non-transitory memory device storing instructions that, when executed by the first processor, cause the first computing system to:
• generate a first data manifest comprising a first count parameter and a first hash parameter associated with a first data exchange transaction between the first computing system and a second computing system, wherein the first data manifest comprises metadata of the first data exchange transaction;
• store the first data manifest to a blockchain data store;
• transfer, via a transport mechanism, a data payload of the first data exchange transaction to the second computing system;
• the second computing system comprising a second processor and a second non-transitory memory device storing instructions that, when executed by the second processor, cause the second computing system to:
• analyze the data payload received via the transport mechanism;
• generate a second data manifest including a second count parameter and a second hash parameter;
• store the second data manifest to the blockchain data store;
• and
• a data manifest as a service (DMAAS) computing system comprising a third processor and a third non-transitory memory device storing instructions that, when executed by the second processor, cause the DMAAS computing system to:
• determine, based on the first data manifest retrieved from the blockchain data store and the second data manifest retrieved from the blockchain data store, whether the data transport mechanism is capable of communicating the first data exchange transaction;
• trigger, based on an indication that a first data transport mechanism is incapable of communicating the first data exchange transaction, selection of a second data transport mechanism;
• cause transfer, after selection of the second data transport mechanism, of the first data exchange transaction via the second data transport mechanism;
• trigger the second computing system to release the data payload to a data consuming application when the DMAAS computing system indicates a successful data transfer and cause posting of an indication of a successful data transfer to the blockchain data store;
• cause posting of a transaction error to the blockchain data store when the DMAAS computing system indicates a transmission error;
• and
• generate, based on an input received from a user device, a drill down visualization screen that shows live data movement information corresponding to each data exchange transaction, identifies one or both of the first data manifest and the second data manifest, pulls information from the blockchain data store associated with one or both of the first data manifest and the second data manifest, and pulls metadata identifying a plurality of data fields used for calculating a hash total.

A data manifest as a service (DMAAS) computing system comprising:

• a processor;
• a non-transitory computing device storing instructions that, when executed by the processor, cause the DMAAS computing system to:
• store, to a blockchain data store via a first application programming interface (API) function, a first data manifest received from a first computing system, the first data manifest corresponding to a first data exchange transaction between the first computing system and a second computing system, wherein the first data manifest comprises metadata of the first data exchange transaction;
• store, to the blockchain data store via a second API function, a second data manifest received from the second computing system;
• determining, based on the first data manifest retrieved from the blockchain data store and the second data manifest retrieved from the blockchain data store, whether a particular data transport mechanism is capable of communicating the first data exchange transaction;
• trigger, based on an indication that a first data transport mechanism is incapable of communicating the first data exchange transaction, selection of a second data transport mechanism;
• cause transfer, based on an indication that the first data transport mechanism is capable of communicating the first data exchange transaction, of the first data exchange transaction via the first data transport mechanism;
• cause transfer, based on an indication that the first data transport mechanism is incapable of communicating the first data exchange transaction, of the first data exchange transaction via the second data transport mechanism;
• compare, via a third API function, the first data manifest to the second data manifest;
• trigger, at the second computing system, import of a data payload received from the first computing system when comparison of the first data manifest to the second data manifest indicates a successful data transfer and cause posting of an indication that the first data exchange transaction between the first computing system and the second computing system completed successfully to the blockchain data store, the blockchain data store comprising an immutable record of each data exchange transaction;
• cause posting of a transaction error to the blockchain data store when analysis by the DMAAS computing system indicates a transmission error;
• and
• generate, based on an input received from a user device, a drill down visualization screen corresponding to the immutable record of each data exchange transaction, wherein the drill down visualization screen identifies one or both of the first data manifest and the second data manifest and pulls information from the blockchain data store associated with one or both of the first data manifest and the second data manifest.