COIN operated digital payments hub

A system for managing data about payment events, comprising:

• one or more servers operable to receive, from an external payment system, data about a payment event including one or more of;
• a participant identifying data, one or more financial account numbers, one or more monetary amounts, and a status of the payment within the external payment system;
• a vault comprising the one or more servers, the vault operable to store said data within a database comprising a predetermined structure comprising a COIN, wherein the COIN serves as an identifier that associates a series of operations into a complete transaction;
• a COIN application programming interface operable to communicate with a payer and a payee related to a payment event;
• a source connector comprising the one or more servers operable to communicate with a source payment system associated with the payer;
• and
• a destination connector comprising the one or more servers operable to communicate with a destination payment system associated with the payee;
• wherein the one or more servers are operable to:
• process said data, wherein processing comprises:
• determining the number of accounting ledgers involved in the payment event;
• creating one or more COIN accounts within the COIN;
• determining a flow path of funds amongst the determined accounting ledgers in order to complete the payment event, wherein the flow path comprises a directed acyclic graph (DAG), the DAG comprising a plurality of vertices and a plurality of edges, with each of the plurality of edges directed from one of the plurality of vertices to another, such that there is no way to start at a vertex and follow a consistently-directed sequence of the plurality of edges that eventually loops back to the vertex;
• making ledger entries in the one or more COIN accounts from one or more monetary amounts in the data;
• and
• determining whether the one or more COIN accounts in the COIN balance using double entry accounting;
• maintain a COIN status to reflect a status of each external payment system and each associated ledger entry;
• encrypt a portion of said data if the portion is determined to be sensitive;
• communicate at least a subset of the data to a second external payment system;
• monitor an updated status of the payment in the second external payment system;
• and
• initiate notifications to the external payment system and other systems based on the COIN status.