# US 12,118,542 B2 · COIN operated digital payments hub > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,118,542 B2 - Document ID: US12118542B2 - Status: Granted - Kind: B2 - Application number: 17/567,660 - Filed: 2022-01-03 - Published: 2022-04-21 - Granted: 2024-10-15 - Earliest claimed: 2016-09-08 - Assignees: ModoPayments, LLC - Applicants: ModoPayments, LLC - Inventors: Bruce Parker; Aaron Wilkinson; Bion J. Oren; Gregory W. Harvey; Matthew R. Leavenworth - Web page: https://patentgrep.com/patent/US12118542B2 ## CPC - G06Q 20/382: {insuring higher security of transaction} - G06Q 20/027: {involving a payment switch or gateway} - G06Q 20/401: {Transaction verification} - G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR ## Abstract A system and method are described for a COIN-based payment event data management system. The COIN can provide a consolidated source of accounting for all parties to a transaction by providing for multi-directional translation, resolution, accounting and other functions. A COIN server can interface with buyers and sellers, requestors and debtors, and other parties. The COIN server can communicate with different API's of various parties. Functionality can include means of analyzing payment and transaction behavior. ## Claims ### Claim 1 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. ### Claim 2 (depends on 1) The system of claim 1, wherein the COIN status can comprise: pressed, wherein pressing the COIN comprises validating one or more sets of credentials and one or more compliance functions; stamped, wherein stamping the COIN comprises authorizing debits and credits associated with a financial transaction; circulated, wherein circulating the COIN comprises communicating money movement instructions to a payment service provider, a bank, and a retailer; certified, wherein certifying the COIN comprises verifying with a system of record that an amount recorded as circulated is equal to an actually circulated amount; encased, wherein encasing the COIN comprises waiting for a dispute period to end and closing all further money movement once the dispute period has ended; and melted, wherein melting the COIN comprises canceling the coin and stopping all further transactions on the COIN. ### Claim 3 (depends on 1) The system of claim 1, wherein the portion comprises the one or more financial account numbers. ### Claim 4 (depends on 1) The system of claim 1, wherein the participant identifying data comprises an email address. ### Claim 5 (depends on 1) The system of claim 1, wherein the participant identifying data comprises an identification number. ### Claim 6 (depends on 1) The system of claim 1, wherein the one or more financial account numbers comprises a participant's bank account number. ### Claim 7 (depends on 1) The system of claim 1, wherein the one or more financial account numbers comprises a credit card account number. ### Claim 8 (depends on 1) The system of claim 1, wherein each update to the status of the COIN is required to result in a COIN that is balanced from an accounting perspective.