WO2018081169A1 - Machines/articles/compositions/processus pour le suivi d'efforts philantropiques et/ou d'autres efforts - Google Patents

Machines/articles/compositions/processus pour le suivi d'efforts philantropiques et/ou d'autres efforts Download PDF

Info

Publication number
WO2018081169A1
WO2018081169A1 PCT/US2017/058146 US2017058146W WO2018081169A1 WO 2018081169 A1 WO2018081169 A1 WO 2018081169A1 US 2017058146 W US2017058146 W US 2017058146W WO 2018081169 A1 WO2018081169 A1 WO 2018081169A1
Authority
WO
WIPO (PCT)
Prior art keywords
funds
attributable
downstream entity
account
transaction data
Prior art date
Application number
PCT/US2017/058146
Other languages
English (en)
Inventor
Ali Arjomand
Kim Cameron
William Gates
Roderick A. Hyde
Muriel Y. Ishikawa
Jordin Kare
Max R. Levchin
Nathan P. Myhrvold
Tony S. PAN
Russ Stein
Clarence T. Tegreene
Aaron Sparks
Maurizio Vecchione
Lowell L. Wood
Victoria Y.H. Wood
Original Assignee
Sunlight Payments, Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US15/331,949 external-priority patent/US20170330250A1/en
Priority claimed from US15/331,948 external-priority patent/US20170046670A1/en
Application filed by Sunlight Payments, Inc. filed Critical Sunlight Payments, Inc.
Publication of WO2018081169A1 publication Critical patent/WO2018081169A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • 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
    • G06Q30/00—Commerce
    • G06Q30/02—Marketing; Price estimation or determination; Fundraising
    • G06Q30/0279—Fundraising management
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • 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
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/04—Payment circuits
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • 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
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G06Q20/401—Transaction verification
    • G06Q20/4016—Transaction verification involving fraud or risk level assessment in transaction processing

Definitions

  • This application is related to attribution of trackable items, e.g., currency, goods, and/or services, which may be used in philanthropic and/or other non-philanthropic efforts, and which may be directed to geographically diverse locations.
  • trackable items e.g., currency, goods, and/or services
  • FIG. 1 shows a high-level system diagram of one or more exemplary environments in which transactions and potential transactions may be carried out, according to one or more embodiments.
  • Fig. 1 forms a partially schematic diagram of an environment(s) and/or an implementation(s) of technologies described herein when Figs. 1-A through 1-L are stitched together in the manner shown in the below table, which is reproduced below in table format.
  • Fig. 1 shows "a view of a large machine or device in its entirety ... broken into partial views ... extended over several sheets” labeled Fig. 1-A through Fig. 1-L (Sheets 1 -12).
  • the "views on two or more sheets form ,in effect, a single complete view, [and] the views on the several sheets ... [are] so arranged that the complete figure can be assembled” from "partial views drawn on separate sheets ... linked edge to edge.
  • the partial view Figs. 1-A through 1-L are ordered alphabetically, by increasing in columns from left to right, and increasing in rows bottom, as shown in the following table:
  • Table 1 Table showing alignment of enclosed drawings to form partial schematic of one or more environments.
  • FIG. 1-A when placed at position (1, 1), forms at least a portion of a partially schematic diagram of an environment(s) and/or an implementation(s) of technologies described herein.
  • FIG. 1-B when placed at position (1 ,2), forms at least a portion of a partially schematic diagram of an environment(s) and/or an implementation(s) of technologies described herein.
  • FIG. 1-C when placed at position (1,3), forms at least a portion of a partially schematic diagram of an environment(s) and/or an implementation(s) of technologies described herein.
  • FIG. 1-D when placed at position (1,4), forms at least a portion of a partially schematic diagram of an environment(s) and/or an implementation(s) of technologies described herein.
  • Fig. 1-E when placed at position (2, 1), forms at least a portion of a partially schematic diagram of an environment(s) and/or an implementation(s) of technologies described herein.
  • Fig. 1-F when placed at position (2,2), forms at least a portion of a partially schematic diagram of an environment(s) and/or an implementation(s) of technologies described herein.
  • Fig. 1-G when placed at position (2,3), forms at least a portion of a partially schematic diagram of an environment(s) and/or an implementation(s) of technologies described herein.
  • Fig. 1-H when placed at position (2,4), forms at least a portion of a partially schematic diagram of an environment(s) and/or an implementation(s) of technologies described herein.
  • Fig. l-I when placed at position (3, 1), forms at least a portion of a partially schematic diagram of an environment(s) and/or an implementation(s) of technologies described herein.
  • Fig. 1-J when placed at position (3,2), forms at least a portion of a partially schematic diagram of an environment(s) and/or an implementation(s) of technologies described herein.
  • Fig. 1-K when placed at position (3,3), forms at least a portion of a partially schematic diagram of an environment(s) and/or an implementation(s) of technologies described herein.
  • Fig. 1-L when placed at position (3,4), forms at least a portion of a partially schematic diagram of an environment(s) and/or an implementation(s) of technologies described herein.
  • Fig. 2A is a depiction of a table showing the difference between data level vs. information level, according to embodiments.
  • Fig. 2B is a depiction of a table showing electronic circuit machine state approximation of human-semantic information.
  • Fig. 2C-1 is a high-level block diagram of an exemplary environment 200C, including a first party machine 220, according to one or more embodiments.
  • Fig. 2C-2 is a high-level block diagram of an exemplary environment 200C-2, including a first party machine 220B, according to one or more embodiments.
  • Fig. 2D is a high-level block diagram of daybreak architecture 250D, according to one or more embodiments.
  • Fig. 2E is a high-level block diagram of daybreak architecture 250E, according to one or more embodiments.
  • Fig. 2F is a diagram of operation of the daybreak architecture 250F according to one or more embodiments.
  • Fig. 2G is a diagram of operation of the daybreak architecture 250F according to one or more embodiments.
  • Fig. 2H is a diagram of operation of the daybreak architecture 250F according to one or more embodiments.
  • Fig. 21 is a diagram of operation of the daybreak architecture 250F according to one or more embodiments.
  • Fig. 2J is a diagram of operation of the daybreak architecture 250F according to one or more embodiments.
  • Fig. 2K is a diagram of operation of the daybreak architecture 250F according to one or more embodiments.
  • Fig. 2L is a diagram of operation of the daybreak architecture 250F according to one or more embodiments.
  • Fig. 2M is a diagram of operation of the daybreak architecture 250F according to one or more embodiments.
  • Fig. 2N is a diagram of operation of the daybreak architecture 250F according to one or more embodiments.
  • Fig. 3A is a high-level block diagram of operation of corporate entity "C" computer 3 10, according to one or more embodiments.
  • Fig. 3B is a high-level block diagram of operation of corporate entity "C" computer 3 10, according to one or more embodiments.
  • Fig. 3C is a high-level block diagram of operation of corporate entity "C" computer 3 10, according to one or more embodiments.
  • Fig. 3D is a high-level block diagram of operation of corporate entity "E" phone 310D, according to one or more embodiments.
  • Fig 4A is a high-level block diagram of fraud detection schemes 400, according to one or more embodiments.
  • Fig. 4B is a high-level block diagram of daybreak architecture 3100, according to one or more embodiments.
  • FIGs. 5A-5J show a high-level block diagram of a processor 251 and/or an at least one input acceptance machine 252, according to one or more embodiments.
  • Figs. 6A-6F shows a high-level block diagram of at least one input acceptance machine 252 and/or an electrical/magnetic/physical storage of at least one original machine state 605, according to one or more embodiments.
  • FIG. 7 shows a high-level block diagram of a processor 251 and/or at least one first track data presentation machine 254 and/or at least one second track data presentation machine 256, according to one or more embodiments.
  • Fig. 8A shows a high-level block diagram of one or more of at least one first track data presentation machine states 710, according to one or more embodiments.
  • Figs. 8B-8C show a high-level block diagram of one or more of at least one tracked first transmission of particular funds within a particular architecture 715, according to one or more embodiments.
  • Fig. 9 shows a high-level block diagram of a processor 251 and/or at least one second track data presentation machine 256, according to one or more embodiments.
  • Fig. 10 is a high-level block diagram of at least one first party machine 220B operating in environment 1000, according to one or more embodiments.
  • Fig. 11 shows a particular perspective of an input acceptance circuit 252B of a first party machine 220B of Fig. 2C-2, according to one or more embodiments.
  • Fig. 12 shows a particular perspective of an first transaction data receiving circuit 254B of a first party machine 220B of Fig. 2C-2, according to one or more embodiments.
  • Fig. 13 shows a particular perspective of an second transaction data receiving circuit 256B of a first party machine 220B of Fig. 2C-2, according to one or more embodiments.
  • Fig. 14 is a high-level logic flowchart of a process, e g., operational flow 1400, including one or more operations of accepting input that regards an attributable account that contains attributable funds operation, a receiving first transaction data operation, and a receiving second transaction data operation, according to an embodiment.
  • Fig. 15A is a high-level logic flow chart of a process depicting alternate implementations of accepting input that regards an attributable account that contains attributable funds operation 1402, according to one or more embodiments.
  • Fig. 15B is a high-level logic flow chart of a process depicting alternate implementations of accepting input that regards an attributable account that contains attributable funds operation 1402, according to one or more embodiments.
  • Fig. 15C is a high-level logic flow chart of a process depicting alternate implementations of accepting input that regards an attributable account that contains attributable funds operation 1402, according to one or more embodiments.
  • Fig. 15D is a high-level logic flow chart of a process depicting alternate implementations of accepting input that regards an attributable account that contains attributable funds operation 1402, according to one or more embodiments.
  • Fig. 15E is a high-level logic flow chart of a process depicting alternate implementations of accepting input that regards an attributable account that contains attributable funds operation 1402, according to one or more embodiments.
  • Fig. 15F is a high-level logic flow chart of a process depicting alternate implementations of accepting input that regards an attributable account that contains attributable funds operation 1402, according to one or more embodiments.
  • Fig. 16A is a high-level logic flow chart of a process depicting alternate implementations of receiving first transaction data operation 1404, according to one or more embodiments.
  • Fig. 16B is a high-level logic flow chart of a process depicting alternate implementations of receiving first transaction data operation 1404, according to one or more embodiments.
  • Fig. 16C is a high-level logic flow chart of a process depicting alternate implementations of receiving first transaction data operation 1404, according to one or more embodiments.
  • Fig. 16D is a high-level logic flow chart of a process depicting alternate implementations of receiving first transaction data operation 1404, according to one or more embodiments.
  • Fig. 16E is a high-level logic flow chart of a process depicting alternate implementations of receiving first transaction data operation 1404, according to one or more embodiments.
  • Fig. 16F is a high-level logic flow chart of a process depicting alternate implementations of receiving first transaction data operation 1404, according to one or more embodiments.
  • Fig. 16G is a high-level logic flow chart of a process depicting alternate implementations of receiving first transaction data operation 1404, according to one or more embodiments.
  • Fig. 16H is a high-level logic flow chart of a process depicting alternate implementations of receiving first transaction data operation 1404, according to one or more embodiments.
  • Fig. 17A is a high-level logic flow chart of a process depicting alternate implementations of receiving second transaction data operation 1406, according to one or more embodiments.
  • Fig. 17B is a high-level logic flow chart of a process depicting alternate implementations of receiving second transaction data operation 1406, according to one or more embodiments.
  • Fig. 17C is a high-level logic flow chart of a process depicting alternate implementations of receiving second transaction data operation 1406, according to one or more embodiments.
  • Fig. 17D is a high-level logic flow chart of a process depicting alternate implementations of receiving second transaction data operation 1406, according to one or more embodiments.
  • Fig. 17E is a high-level logic flow chart of a process depicting alternate implementations of receiving second transaction data operation 1406, according to one or more embodiments.
  • Fig. 17F is a high-level logic flow chart of a process depicting alternate implementations of receiving second transaction data operation 1406, according to one or more embodiments.
  • computationally implemented methods, systems, circuitry, articles of manufacture, ordered chains of matter, and computer program products are designed to, among other things, provide an interface for the environment illustrated in Fig. 1.
  • Fig. 1 shows various implementations of the overall system.
  • Fig. 1 shows various implementations of an attributed digital currency system, in all of its parts.
  • the boxes of Fig. 1 are not labeled as “modules” or “circuits” or “steps” because one of skill in the art would understand that the differences are matters of conventional implementation.
  • VHDL interpreters for example, Xilinx Vivado (described simply at http [colon-slash-slash] www.xilinx.com/products/design-tools/vivado.html). Accordingly, the blocks of Fig.
  • panticles or “all [pan] articles,” and it will be understood to one of skill in the art that these panticles could be implemented as method steps (e.g., and then converted to FPGAs or ASICs as described above) or as circuit/modules of one or more processors. None in this paragraph should be interpreted as limiting an implementation of various embodiments.
  • a philanthropist/user e.g., user 3005
  • User 3005 may be connected with an individual charitable organization 3015.
  • Charitable organization may appear throughout the specification and disclosure, it is not necessary for the organization in question to be a charitable organization. Although charitable organizations may benefit substantially by the arrangement here, there is no technological limitation for non-charitable organizations that wish to keep their funds in an attributable manner.
  • the "charitable organization” here is used as an exemplary implementation and should not be construed as placing any limitations on the entity using or benefitting from the system.
  • Daybreak architecture 3100 and the other entities shown in Fig. 1 are used for commercial purposes, or a mix of charitable and/or commercial purposes.
  • the individual charitable organization 3015 may be omitted completely.
  • the user/philanthropist may wish to use personal funds that are not tied to an organization.
  • the user 3005 may communicate directly with their local bank (described in more detail herein) and create the computationally- attributable account on their own.
  • a charity organization 3015 may request an account, which is account 3030, which, in an embodiment, may be a computationally-attributable account that tracks and/or verifies funds that are contributed to the account 3050. More details about various embodiments of account 3030, which, in an embodiment, may be a computationally-attributable account, will be discussed herein.
  • the request may be sent to the bank, as shown in Fig. 1-A, e.g., local bank 3 100 or national domestic bank 3200.
  • the request for the account 3002 by the philanthropist 3005 may occur in panticle 3050, which may be originated by the philanthropist 3005, the charity organization 3015, or one of the banks 3 100 and 3200.
  • the bank at which the account 3030 was requested may send an agreement that the computationally-attributable account has been created 3052. This agreement may specify the terms of the account 3030.
  • the account 3030 may be created at local bank 3200, national domestic bank 3300, or at external tracking architecture 3 100 running on external architecture application 3 105 (e.g., as shown in Fig. 1- B), which may interface with one or more of the entities in Fig. 1.
  • the account 3030 may be associated with a network account and/or a mobile application 3054.
  • the mobile application 3054 may include a unique identifier and/or password input.
  • the unique identifier may be an anonymous identifier.
  • the mobile application 3054 may utilize two- factor authentication.
  • mobile application 3054 may include a display panticle 3056.
  • the display panticle 3056 may include various components that allow interaction with a display, e.g., an application back end, a device graphics unit, a screen or other input or output device, and the like.
  • Display panticle 3056 may be configured to show various implementations of the computationally-attributable account, for example all of the horizontal and vertical spending details.
  • display panticle 3056 may include facilitating the display of one or more of the account information, spending verification information, account balance, location of funds, goods purchased, allocation of funds, and fees associated with the account.
  • Daybreak App there may be an external tracking application and or/server 3100 (hereinafter interchangeably referred to as the "Daybreak App,” with or without the designation 3100).
  • Daybreak app 3100 is listed in this application as an application and/or server to indicate that in various embodiments, the daybreak app 3100 could be one or more applications, servers, local devices, or a combination thereof.
  • the daybreak app 3100 is a web extension or a web page.
  • daybreak app 3100 includes a server portion 3 1 10 and an application portion 3 105.
  • application portion 3105 may be distributed to various devices and/or servers under the control of one or more of philanthropist/user 3005, charity organization 3015, local bank 3200, and national domestic bank 3300.
  • panticle 3120 represents a creation of an internal account for the computationally-attributable account.
  • the internal account may track payments of money to various entities throughout the life cycle.
  • the internal account tracks money that is transferred between midpoint entities (e.g., not the direct providers of services, but subcontractors, middle men, governments, etc., as will be described in more detail herein), but does not actually take steps to move the money until it reaches its ultimate destination.
  • the internal account may follow an account rule set, shown in more detail in Fig. 1-C.
  • Fig 1 -C shows some of the rule set circuitry for implementing various rules and conditions, which will be discussed in more detail herein.
  • the money will be transferred from the charitable organization 3015 and/or the philanthropist/user 3005 to a banking entity.
  • this transfer may be accomplished by an ACH transfer from an account under the control of one or more of the charitable organization 3015 and/or the philanthropist/user 3005 to a bank which has a relationship with the external tracking app.
  • Panticle 3130 represents the facilitation of a transfer of funds to a local bank 3200 or a national bank 3300, although other banks represented throughout Fig. 1, and other financial institutions generally, may be represented.
  • Fig. 1-C shows external tracking architecture 3100 (which will hereinafter be interchangeably referred to as "Daybreak architecture 3100").
  • Daybreak here is merely an identifier and does not have any specific functional meaning.
  • the Daybreak architecture 3 100 may be separate from the other entities in Fig. 1, e.g., the banks, the users, the organizations, and the endpoint goods and/or services providers.
  • Daybreak architecture may run on a separate server, and may interface with various banking and other entities through various interfaces, e.g., an XML template interface (e.g., as will be described in more detail with respect to panticle 3160).
  • Daybreak architecture 3100 may run on a server 31 10, as shown in Fig. 1-B, and may be associated with one or more banking entities, e.g., national domestic bank 3300.
  • Daybreak architecture 3 100 may have a single account with a banking entity, e.g., national domestic bank 3300, in which all of the various funds contributed from various users 3005 are deposited.
  • the funds in these accounts may be managed by the Daybreak architecture through use of various ledger transactions, e.g., paper transactions that represent tracking money as it moves through various entities, but in which the money itself is not transferred.
  • Daybreak architecture 3100 may effect actual transfers only when money is deposited from an outside source, and when money is "offboarded,” that is transferred to an entity such that it has complied with the distribution rule sets, and is no longer under the control and/or supervision of the Daybreak architecture 3 100.
  • Daybreak architecture may be separate from the other entities shown in Fig. 1, but may use a multitude of accounts, which may be across various banks, and which may, or in other embodiments, may not, have a correlation to the accounts 3030 that are created by the users 3005 and/or the organizations 3015 that have deposited the funds.
  • Daybreak architecture 3100 may create a separate account each time money is transferred from one or more users 3005 and/or organizations 3015.
  • money transferred under the control of Daybreak architecture 3100 may be grouped by how it is to be spent (e.g., different accounts for various services) or where it is to be spent (e.g., different accounts for different known endpoints).
  • Daybreak architecture 3 100 may be integrated into any one or more of the entities shown in Fig. 1, and which will be discussed in more detail herein.
  • Daybreak architecture 3100 may be implemented by national domestic bank 3300, and in an embodiment, other entities that wish to access the Daybreak architecture 3100 may work with national domestic bank 3300. The same applies to any other of the entities shown in Fig. 1, including the user 3005 and the organization 3015.
  • Daybreak architecture 3100 may be implemented by the organization 3015 as a way to track and/or manage its funds and their allocation.
  • the Daybreak architecture 3100 may include an interface that is accessible to any of the entities shown in Fig. 1 , including user 3005 and/or organization 3015.
  • this interface may be app 3015, which may run on the Internet, on other devices, on mobile phones, tablets, "smart" devices, and other similar electronics.
  • various entities in Fig. 1 may have access to various levels of data regarding the flow of funds from account 3030.
  • the user 3005/organization 3015 may have complete access to all entities that are participating in their particular account set up by Daybreak architecture 3 100.
  • each entity may have access only to its own portion of the funds.
  • each entity may have downstream visibility for its funds (e.g., each entity can see the ledger transactions that occur after it receives funds from a ledger transaction, but not what happens before).
  • the distribution rule set may specify the level of access for each of the entities that have access to the Daybreak architecture 3100.
  • Daybreak architecture 3 100 may include panticle 3 120, which may implement the creation of an internal account.
  • the donation 3020 shown in Fig. 1-A
  • the local bank 3200 shown in Fig. 1-E
  • panticle 3120 may implement the creation of an internal account in the daybreak architecture 3100 at panticle 3120 (referring back to Fig. 1 -B).
  • the account rule set may be specified by user 3005, organization 3015, Daybreak architecture 3100 (e.g., which may have a default rule set, or a rule set based on previous rule sets used by user 3005/organization 3015), some other entity shown in Fig. 1 , or some other combination thereof.
  • the internal account created at panticle 3120 may be accessed by any or all of the entities shown in Fig. 1.
  • the creation of (or addition to) internal account by the Daybreak architecture 3100 may trigger a facilitation of the transfer of funds from the user 3005/organization 3015 to a bank, e.g., local bank 3200 or national bank 3300, e.g., as shown in panticle 3130.
  • funds may be transferred from user 3005/organization 3015 to a bank account under the at least partial control of the Daybreak architecture 3100. This transfer may be accomplished through traditional means, e.g., ACH transfer, wire transfer, etc.
  • further moves of the funds may be handled internally, e.g., through what will be referred to throughout this application as "ledger transactions," that is, the money does not move from the account in which it was initially deposited, but transfers of the money are displayed and treated as if the money had actually been moved through the Daybreak architecture.
  • user 3005 may contribute three thousand (3,000) dollars to be used in the system of Fig. 1.
  • the Daybreak architecture 3100 creates an account with three thousand (3,000) dollars in it. In an embodiment, that three thousand dollars is deposited in the existing bank account under the control of the Daybreak architecture 3100.
  • further transactions that are not to the endpoint service providers are recorded as ledger transactions, e.g., as shown in panticle 3 140, but may not include actual transfers of the money.
  • the Daybreak architecture may store, as an example from the previous paragraph, the three thousand (3,000) dollars in an account with local bank 3200, and the money is transferred from a bank account of organization 3015 to the Daybreak architecture 3 100 account. From there, the money is transferred to national bank 3200.
  • this may be a "ledger transaction" in which the money is recorded as transferred to national bank 3300, and national bank 3300 has control of the money (within the Daybreak architecture 3100), but the money is not actually transferred from local bank 3200 to national bank 3300. Rather, each of the intermediary transactions between the final payee and the account under the control of the Daybreak architecture are executed as ledger transactions.
  • the funds may reach an endpoint services provider, e.g., FO/NGO/FI 3800 (which will be discussed in more detail herein), this payee may receive the funds directly.
  • another ledger transaction may be executed from wherever the funds are at the time (e.g., at NU/NE bank 3500) according to the ledger transactions, to the FO/NGO/FI 3800, who is the receiver of the funds.
  • the ledger transaction may also be implemented, e.g., at panticle 3150, as an offboarding of the money, e.g., the actual funds are transmitted from the account with local bank 3200 to the FO/NGO/FI 3800, in addition to the ledger transaction. This may be accomplished, for example, in a specific implementation, by panticle 3 160, which is the implementation of an XML interface that is sent to local bank 3200.
  • the controllers of external tracking architecture 3100 may have a relationship with one or more specific banks at the local or national level.
  • external tracking architecture 3100 may be embedded into local domestic bank 3200 or national domestic bank 3300, and may have one or more components interacting with the various components.
  • the Daybreak architecture 3100 may implement a rule set related to the account and the funds therein.
  • Panticle 4900 shows a variety of exemplary rules that may be applied to the funds, some of which will be additionally listed and/or elaborated upon here. This list of rules that could be part of the rule set is not intended to be exhaustive or limiting, but rather exemplary.
  • rule set 4900 may include metadata that is linked to the account. For example, as the funds are transferred through the ledger transactions, metadata that identifies one or more properties of user 3005 (e.g., who may be a philanthropist, as a specific example). The metadata may identify to whom the money belongs, for example, or any other data that may "travel" with the money. In an embodiment, this may include some form of modified digital currency, e.g., a Bitcoin-like setup, which may be localized or specified for specific accounts.
  • modified digital currency e.g., a Bitcoin-like setup, which may be localized or specified for specific accounts.
  • rule set circuitry panticle 4900 may include geographic location tracking of goods and/or services that are associated with the account or distributed with the account.
  • a rule set may specify that certain funds may only be spent at particular geographic locations.
  • the rule set may specify that the money must be spent in specific locations in Sub-Saharan Africa.
  • the rule set may specify that the money must be spent in locations associated with hospitals, or schools.
  • the rule set may depend on conditions, as well.
  • the rule set may specify that the money may only be spent in locations that have an average GDP per capita below a certain amount.
  • the location tracking may include GPS verification (e.g., when the money is transferred to an entity, that entity's location is recorded), or verification of location through monitoring of satellite pictures, pictures taken onsite, geotagged images, or trusted person/device verification.
  • rule set circuitry panticle 4900 may include an account fee tracking function, e.g., which, in an embodiment, may set limits and/or conditions on how much account fees can be charged by the various banking entities.
  • the amounts and conditions may be changed if the Daybreak architecture 3100 is used versus the money being transferred between one or more of the various midpoints.
  • each amount and/or condition may be different depending on the conditions at the midpoint entity.
  • the amount limits and/or conditions may be dependent upon conditions themselves, e.g., "if X happens, then an escalating limit may be established.”
  • the amount of funds stored/controlled/ledger transferred to the various banks and/or entities may control the limits and/or conditions on the account fees.
  • the rule set may specify changes to the limits and/or conditions when a number of transactions (e.g., true transactions or ledger transactions) are carried out.
  • rule set circuitry panticle 4900 may include a rule set that specifies a requirement for photographic evidence associated with the acquisition/distribution of goods/services.
  • the rule set may specify that, at the point of delivery of goods and/or services, photo documentation must be captured at the time of the transaction for the money to be released (e.g., it may be ledger transacted in the Daybreak architecture 3100, but with separate requirements for an actual transfer of the funds).
  • rule set circuitry panticle 4900 may include implementation of a spending limit associated with the goods and/or services, e.g., as will be discussed in more detail herein.
  • rule set circuitry panticle 4900 may include implementation of a spending linked to the nature of the goods/and or services (e.g., funds are restricted to particular classes of goods, e.g., vaccines, food, clothing, etc.).
  • rule set circuitry panticle 4900 may include implementation of a time stamp for receipt of distribution of funds associated with the delivery of goods and/or services.
  • this time stamp may take the form of a time-tagged photo, a time-tagged post to the internet (e.g., through any medium, via twitter, e-mail, etc.), location (e.g., GPS) confirmation of the location and/or meeting of the parties.
  • rule set circuitry panticle 4900 may include implementation of a system in which payment is given (e.g., which may be the "ledger transaction" payment or the "actual transfer of funds” payment, depending on embodiments).
  • rule set circuitry panticle 4900 may include implementation of a trusted sources system, in which the payment for goods and/or services must be verified by a trusted source, either by previous dealings, outside reputation score, or some other trust-verifi cation system.
  • Daybreak architecture 3100 may implement a trust level system for individuals and/or organizations. In another embodiment, Daybreak architecture may tap into one or more existing systems.
  • rule set circuitry panticle 4900 may include implementation of a limit of funding available to sources based on past history, and a term sheet for specific endpoint entities.
  • rule set circuitry panticle 4900 may include implementation of a system for recouping funds (e.g., forcing return of funds if the agreement for the acquisition and/or the distribution is not met).
  • the ledger transaction that transfers the money may be allowed to go through prior to the actual transfer of funds, and if the conditions specified in the rule set are not met, the actual transfer of funds may be stopped and/or delayed (e.g., in an embodiment, this may use delays in timing of banking processes in order to implement).
  • rule set circuitry panticle 4900 may include implementation of a reputation system for actors, either through Daybreak architecture 3 100, through tapping an existing system, and/or through analysis of social media, an encryption function, e.g., through a multi-part encryption key to be sent through at least two different transmission routes, a currency conversion function (e.g., exchange rate determinations, a currency transfer unit, digital currency protections, and language conversion function.
  • a reputation system for actors either through Daybreak architecture 3 100, through tapping an existing system, and/or through analysis of social media
  • an encryption function e.g., through a multi-part encryption key to be sent through at least two different transmission routes
  • a currency conversion function e.g., exchange rate determinations, a currency transfer unit, digital currency protections, and language conversion function.
  • rule set circuitry panticle 4900 may include implementation of scoring engine that analyzes vendors, transactions, etc., and compares to programmed patterns.
  • a scoring engine may analyze a transaction and drop it into one of three buckets. Bucket 1 is "definitely bad,” bucket 2 is “definitely good,” and bucket 3 is “needs human evaluation for final decision” so the scoring engine will drop it into one of those three buckets.
  • Fig. 1-E shows Box 12, which starts at Fig. 1 -E, and extends through Figs. 1 -F and 1-G, describes that, in an embodiment, actual monetary transfers (e.g., ACH transfers, wire transfers, and the like) may be used at endpoints of various transactions between the philanthropist/user's 3005 bank account, e.g., at local bank 3200, and the foreign organization/NGO/foreign individual 3800 (e.g., as shorthand, "foreign organization/NGO/Foreign Individual 3800" will hereafter be interchangeably referred to as "foreign entity 3800").
  • actual monetary transfers e.g., ACH transfers, wire transfers, and the like
  • endpoint money transfers may be made at local bank 3200 (or one of the other entity banks), and may be made at the foreign entity 3800, with other transactions occurring as "ledger transactions. " In an embodiment, this may except offboarding of funds designated for a specific entity.
  • donation 3020 may be given by the philanthropist/user 3005 (e.g., through the charity organization 3015). Donation 3020 may be received by local bank 3200.
  • local bank 3200 may create an account for the charity funds 3220, e.g., "Fund X" (hereinafter will be interchangeably referred to as "account 3220").
  • Fund X may be the repository for the funds until they are paid out to a specific person, e.g., foreign entity 3800, or appropriated as part of a fee by an intervening entity, e.g., offboarded, e.g., as shown in panticles 3350, 3450, and 3550, which will be discussed in more detail herein.
  • an intervening entity e.g., offboarded, e.g., as shown in panticles 3350, 3450, and 3550, which will be discussed in more detail herein.
  • any movement of funds between other entities, e.g., entities inside the box 12 may occur as ledger transactions.
  • funds may be moved from the local bank 3200 (e.g., Omaha bank) to other banking/management entities as will be described herein. [0102] Referring again to Fig.
  • local bank 3200 may use an existing account 3230, and earmark the charity funds for specific distributions according to their rule set.
  • local bank 3200 may have a single account that uses the daybreak architecture, which may be implemented as external tracking architecture 3100 (e.g., see Fig 1-B, which will be discussed in more detail herein), or by a system similar to external tracking architecture 3100 but implemented partially or wholly internal to local bank 3200.
  • any funds that will be managed by the daybreak architecture 3100 will be placed in the existing account 3230, and can be tracked through ledger transactions and payouts to end recipients of funds, as will be discussed in more detail herein.
  • panticle 3210 includes panticle 3212 of creation of a unique and/or anonymous identifier and password.
  • this identifier/password 3212 may be login information that will be given to user 3005 in order to access the account, change the rule set, and receive reports and/or auditing regarding the account 3220 or 3230.
  • data may be sent to the user 3005. This data may include one or more tools used to access the information, e.g., login credentials for a network application, in an embodiment, or a mobile application for interfacing with bank 3200 and/or daybreak architecture 3100.
  • Fig. 1-E shows a national domestic bank 3300 (e.g., hereinafter interchangeably referred to as "national bank 3300").
  • national domestic bank 3300 may be a nationally-established bank, e.g., Bank of New York.
  • national bank 3300 may receive a request at panticle 3302, e.g., a request from the local bank 3200 (e.g., Omaha bank), which is a request for the bank to accept the tracking and/or verifying account.
  • the local bank 3200 e.g., Omaha bank
  • panticle 3302 may include the request from local bank 3200 for national bank 3300 to register an account with the Daybreak architecture 3100 (e.g., which, as previously described, may be separate from one or more of the figures in this entity, or may be partially or wholly integrated with one or more of the entities in this figure).
  • Daybreak architecture 3100 e.g., which, as previously described, may be separate from one or more of the figures in this entity, or may be partially or wholly integrated with one or more of the entities in this figure.
  • national bank 3300 may, at panticle 3304, send a confirmation that the national bank 3300 will accept the tracking and verification account.
  • panticle 3304 may include the notification of acceptance and/or completion of registration with the Daybreak architecture 3100.
  • registration may mean that the national bank 3300 is newly registered with the Daybreak architecture 3 100, or that the national bank 3300 is adding data to the registration indicating its acceptance of the account created in panticle 3210.
  • national bank 3300 may communicate with Daybreak architecture 3 100 (not shown in panticle 3304).
  • national bank 3300 may, at panticle 3306, receive a donation sent from the local bank 3200.
  • panticle 3306 may represent national bank 3300 receiving an actual transfer of funds into its accounts, e.g., via an ACH or a wire transfer.
  • panticle 3306 may represent a ledger transfer of the funds, as represented in Daybreak architecture 3100, but the location of the funds stays in an account with local bank 3200, e.g., in the Daybreak architecture.
  • a ledger transaction may show a funds transfer to national bank 3300 as performed by the Daybreak architecture 3100, but the actual funds may stay in the account designated by the daybreak architecture 3100 at local bank 3200. Nevertheless, national bank 3300 may be authorized to draw funds from the account for services rendered, e.g., national bank 3300 may be awarded a flat fee of five thousand (5,000) dollars or a percentage of the contents of the account created/used by local bank 3200. In such an embodiment, the national bank's 3300 funds to which they are entitled are "offboarded" at panticle 3350 of Fig. 1-A.
  • offboarded means that the funds to which national bank 3300 is entitled, which are part of the overall funds which have been ledger-transferred to national bank 3300 but are still in possession of an account at local bank 3200, said funds are actually transferred to the national bank 3300 through conventional means, e.g., an ACH transfer or a wire transfer.
  • the account contains one million (1,000,000) dollars that have been ledger transferred from local bank 3200 to national bank 3300, and the national bank 3300 is collecting a five thousand (5,000) dollar payment for services rendered
  • the national bank 3300 is collecting a five thousand (5,000) dollar payment for services rendered
  • another ledger transaction is made from the ledger account at national bank 3300 that contains the one million (1,000,000) dollars, into a personal account under the control of national bank 3300.
  • This ledger transaction is for the five thousand (5,000) dollars and is accompanied by an actual transfer (e.g., wire transfer or ACH transfer) of five thousand (5,000) dollars.
  • Fig. 1 -F shows a European bank 3400, e.g., the Bank of England, according to various embodiments.
  • bank 3400 is labeled "European bank,” bank 3400 is not limited to being located in Europe.
  • Bank 3400 may be any bank external to the United States, regardless of location, that participates in the management and/or distribution of funds from the account 3030 (and/or other accounts that may be established throughout Fig. 1).
  • the national bank 3300 may send the request to European bank 3400 to accept and implement the tracking and/or verifying account.
  • panticle 3402 may include the request (e.g., from local bank 3200, although the request could come from any entity shown in Fig. 1) for national bank 3400 to register an account with the Daybreak architecture 3100 (e.g., which, as previously described, may be separate from one or more of the figures in this entity, or may be partially or wholly integrated with one or more of the entities in this figure).
  • the Daybreak architecture 3100 e.g., which, as previously described, may be separate from one or more of the figures in this entity, or may be partially or wholly integrated with one or more of the entities in this figure.
  • Fig. 1 -F shows European bank with panticle 3404.
  • Panticle 3404 describes European bank 3400 sending a confirmation that European bank 3400 will accept and implement the tracking and/or verification account. In an embodiment, this acceptance may include opening a new account and accepting a monetary transfer (e.g., through wire transfer, ACH, or other means) of the account funds, and managing an account similar to account 3030. In an embodiment, panticle 3404 may include the notification of acceptance and/or completion of registration with the Daybreak architecture 3100.
  • registration may mean that the European bank 3400 is newly registered with the Daybreak architecture 3100, or that the European bank 3400 is adding data to the registration indicating its acceptance of the account created in panticle 3210.
  • European bank 3400 may communicate with Daybreak architecture 3100 (not shown in panticle 3404).
  • European bank 3400 may operate with panticle 3406.
  • panticle 3406 may represent a receiving of a donation sent from the national bank 3300, or, in another embodiment from one or more of the other entities shown in Fig. 1.
  • panticle 3406 may represent European bank 3400 receiving an actual transfer of funds into its accounts, e.g., via an ACH or a wire transfer.
  • panticle 3406 may represent a ledger transfer of the funds, as represented in Daybreak architecture 3100, but the location of the funds stays in an account with local bank 3200, e.g., in the Daybreak architecture.
  • the European bank 3400 may conduct an audit of the funds that have been spent and/or distributed for a given time.
  • the audit may include all of the downstream and/or upstream activity from the European bank 3400.
  • the audit may be conducted through analysis of the ledger transactions executed by the Daybreak architecture 3100. Audit details will be described in more detail further herein.
  • a ledger transaction may show a funds transfer to European bank 3400 as performed by the Daybreak architecture 3100, but the actual funds may stay in the account designated by the daybreak architecture 3 100 at local bank 3200. Nevertheless, European bank 3400 may be authorized to draw funds from the account for services rendered, e.g., European bank 3400 may be awarded a flat fee of five thousand (5,000) dollars or a percentage of the contents of the account created/used by local bank 3200. In such an embodiment, the funds to which European bank 3400 is entitled are "offboarded" at panticle 3350 of Fig. 1-A.
  • offboarded means that the funds to which European bank 3400 is entitled, which are part of the overall funds which have been ledger-transferred to European bank 3400 but are still in possession of an account at local bank 3200, said funds are actually transferred to the European bank 3400 through conventional means, e.g., an ACH transfer or a wire transfer.
  • the account contains one million (1,000,000) dollars that have been ledger transferred from local bank 3200 to European bank 3400, and the European bank 3400 is collecting a five thousand (5,000) dollar payment for services rendered
  • the European bank 3400 is collecting a five thousand (5,000) dollar payment for services rendered
  • another ledger transaction is made from the ledger account at European bank 3400 that contains the one million (1,000,000) dollars, into a personal account under the control of European bank 3400.
  • This ledger transaction is for the five thousand (5,000) dollars and is accompanied by an actual transfer (e.g., wire transfer or ACH transfer) of five thousand (5,000) dollars.
  • European bank 3400 may implement a panticle 4200, which may facilitate the reputation/trustworthiness verification as part of the chain. It is noted that, although these panticles are associated with European bank 3400, this is merely for ease of display, and any of the entities shown in Fig. 1 may implement similar methods and/or systems.
  • panticle 4200 may include panticle 4210, in which the European bank 3400 verifies the reputation and/or trustworthiness of one or more of the other entities shown in Fig. 1.
  • panticle 4210 may implement verification using one or more of reputation score 4212 and/or past accounting and/or reporting history.
  • the verification of the reputation and/or trustworthiness of other entities may include acquisition, analysis, implementation, or other actions taken toward the rule set, if such are not implemented by Daybreak architecture 3100.
  • European bank 3400 may include panticle 4230 in which European bank 3400, alone or in conjunction with Daybreak architecture 3100, may facilitate one or more actions that go with implementing a rule set for the acquisition and/or distribution of funds, to one or more of subcontracting foreign organizations (e.g., subcontracting foreign organization 3700) and Foreign Organization/Non- Governmental Organization/Foreign Individual (FO/NGO/FI), e.g., FO/NGO/FI 3800.
  • subcontracting foreign organizations e.g., subcontracting foreign organization 3700
  • FOG/NGO/FI Foreign Organization/Non- Governmental Organization/Foreign Individual
  • European bank panticle 4230 may receive the rule set from Daybreak architecture 3100.
  • the funds from the account 3030 may not be actually transmitted to European bank panticle 4230, but may be transmitted through ledger transactions.
  • European bank panticle 4230 may implement the rule set from Daybreak architecture 3100 for the funds from the account 3030 that are actually received by European bank 3400.
  • European bank panticle 4230 may include panticle 4232, in which panticle 4232 effects an implementation of an acquisition or a distribution of funds rule set based on a type of goods and/or services (e.g., food, water, potable water, medicine, vaccines, health care services, shelters, clothing, tools, transport services, vehicles, firearms, etc.).
  • a part of the distribution rule set may specify that the funds must be spent on vaccinations or organizations that provide vaccinations.
  • a part of the distribution rule set may specify that certain types of drugs cannot be purchased with funds from the account 3030, e.g., prohibition on Schedule 2 narcotics, for example.
  • European bank panticle 4230 may include panticle 4234, in which panticle 4234 effects an implementation of an acquisition or a distribution of funds rule set based on a distribution area of goods and/or services (e.g., food, water, potable water, medicine, vaccines, health care services, shelters, clothing, tools, transport services, vehicles, firearms, etc.).
  • goods and/or services e.g., food, water, potable water, medicine, vaccines, health care services, shelters, clothing, tools, transport services, vehicles, firearms, etc.
  • the distribution area may be purely geographical (e.g., "between the two rivers," or “within a box defined by specific latitudes and longitudes), political (e.g., within the boundaries of a specific foreign country), or data-based (e.g., "only to areas in which the poverty rate is above 85%,” or “only to areas in which HIV infection is above 22%").
  • a part of the distribution rule set may specify that the funds can only be spent in targeted areas of sub-Saharan Africa.
  • European bank panticle 4230 may include panticle 4236, in which panticle 4236 effects an implementation of an acquisition or a distribution of funds rule set based on a quantity of goods and/or services (e.g., food, water, potable water, medicine, vaccines, health care services, shelters, clothing, tools, transport services, vehicles, firearms, etc.) to be provided.
  • the numbers may be absolute, e.g., "this money must be used to purchase three thousand (3,000) vaccines,") or relative (e.g., "30% of this money must be used to purchase vaccines).
  • European bank 3400 may, in a process of implementing reputation and/or trustworthiness verification, e.g., at panticle 4200, implement a reporting rule set for various downstream entities to report distribution of funds.
  • panticle 4250 may include facilitating implementation of the reporting rule set (which may be similar to the acquisition/distribution rule set, and which may be developed/implemented in conjunction with Daybreak architecture 3 100).
  • implementation of the reporting rule set for one or more entities may include requiring an audit of the various entities upon request, e.g., as described in panticle 4255.
  • European bank 3400 may, in a process of implementing the reporting rule set, at panticle 4260, reporting evidence of the transaction may be required.
  • the reporting evidence may be required as a condition of releasing the funds, which, in an embodiment, may be preventing the ledger transaction of the funds, or preventing an actual underlying transaction of the funds to the endpoint entity.
  • the panticle 4260 that requires reporting evidence may require, e.g., photographic evidence, as part of panticle 4262.
  • Photographic evidence here may include audio, video, still shot, any capture of light and/or motion in any portion of the electromagnetic spectrum, and also may include metadata, e.g., timestamp of photo and/or geolocation tagging of photo (e.g., from a camera device with geolocation/timestamp tagging enabled).
  • metadata e.g., timestamp of photo and/or geolocation tagging of photo (e.g., from a camera device with geolocation/timestamp tagging enabled).
  • European bank 3400 may implement reporting rule set at panticle 4250, which may include panticle 4260 requiring reporting evidence associated with the distribution of goods and/or services prior to payment being made of goods and/or services (e.g., or, in an embodiment, prior to approving the goods and/or services to be carried out/sold), as previously discussed.
  • panticle 4260 may include panticle 4264, which may implement a reporting rule set through use of various monitoring devices, which may be attached to various goods, e.g., food goods, shipping containers, vaccines, clothing, etc.)
  • the monitoring devices may use near-field communication, or may be RFID tags.
  • the monitoring may be accomplished through surveillance, e.g., visual, infrared, or some other form, from localized cameras or satellite cameras, for example.
  • European bank 3400 may implement reporting rule set at panticle 4250, which may include panticle 4260 requiring reporting evidence associated with the distribution of goods and/or services prior to payment being made of goods and/or services (e.g., or, in an embodiment, prior to approving the goods and/or services to be carried out/sold), as previously discussed.
  • panticle 4260 may include panticle 4266, which includes verification from a trusted source as a requirement for reporting.
  • an unknown/untrusted FO/NGO/FI 3800 which may be an endpoint entity, performs a service, and wants to receive compensation, they may seek verification from a trusted source, e.g., which may be a different FO/NGO/FI 3800, or some other entity, which may or may not be associated with the Daybreak architecture 3 100.
  • Daybreak architecture 3 100 may keep the list of trusted sources and require verification from those sources, however, in another embodiment, the trusted sources may become trusted sources through a relationship with European bank 3400 or one of the other banking entities.
  • European bank 3400 may implement reporting rule set at panticle 4250, which may include panticle 4260 requiring reporting evidence associated with the distribution of goods and/or services prior to payment being made of goods and/or services (e.g., or, in an embodiment, prior to approving the goods and/or services to be carried out/sold), as previously discussed.
  • panticle 4260 may include panticle 4268 and/or panticle 4269, which may require real time reporting associated with implementation of the goods and/or services, or real time reporting associated with payment for the implementation of the goods and/or services.
  • Daybreak architecture 3100 may build out at least two different types of rule sets.
  • the first will be to prevent known fraud schemes, e.g., such as use of a phantom vendor, no-bid arrangements, bad acting vendors, imaginary vendors, and the like.
  • a second type of rule set in an embodiment, may be a set of attributes, e.g., characteristics that alone do not mean anything, but may in certain circumstances or in combination with other attributes, may raise flags that require further analysis or may require delaying the transaction until clearance.
  • odd time of day, transactions on holidays, transactions late at night, or structured transactions may, in some various combinations, require additional approval or other steps to be taken to release the funds from the Daybreak architecture 3100 or the other entities shown in Fig. 1.
  • Fig. 1-F shows non-USA/non-European bank (e.g., shown in Fig. 1 as "Central Bank of Kenya,” but this is just an example) 3500 (hereinafter interchangeably referred to as NU/NE "bank 3500").
  • NU/NE bank 3500 may communicate with one or more of the entities shown in Fig. 1.
  • NU/NE bank 3500 is shown in communication with European bank 3400, but in other embodiments, NU/NE bank 3500 may communicate with other entities depicted in Fig. 1 , regardless of whether lines are directly drawn that connect NU/NE bank 3500 to those entities (the same is also true for the other banks discussed previously and discussed herein).
  • the European bank 3400 may send the request for NU/NE bank 3500 to accept and/or implement the tracking and/or verifying account at panticle 3502.
  • this request comes from European bank 3400, but, in other embodiments, the request may come from any other entity depicted in Fig. 1.
  • the European bank 3400 may send the request to NU/NE bank 3500 to accept and implement the tracking and/or verifying account.
  • panticle 3502 may include the request (e.g., from local bank 3200, although the request could come from any entity shown in Fig.
  • NU/NE bank 3500 may include panticle 3504.
  • Panticle 3504 describes NU/NE bank 3500 sending a confirmation that indicates acceptance and/or implementation of a tracking and or verification account. This confirmation may be sent electronically or may be part of a general agreement that governs particular types of accounts or transactions, or may be implemented in a different way.
  • this acceptance may include opening a new account and accepting a monetary transfer (e.g., through wire transfer, ACH, or other means) of the account funds, and managing an account similar to account 3030.
  • panticle 3504 may include the notification of acceptance and/or completion of registration with the Daybreak architecture 3100.
  • registration may mean that the NU/NE bank 3500 is newly registered with the Daybreak architecture 3100, or that the NU/NE bank 3500 is adding data to the registration indicating its acceptance of the account created in panticle 3210.
  • NU/NE bank 3500 may communicate with Daybreak architecture 3100 (not shown in panticle 3404).
  • NU/NE bank 3500 may implement panticle 3506.
  • panticle 3506 may represent reception of account funds (e.g., the donation) from European bank 3400, or, in another embodiment from one or more of the other entities shown in Fig. 1.
  • panticle 3506 may represent a ledger transfer of the funds, as represented in Daybreak architecture 3100, but the location of the funds stays in an account with local bank 3200, e.g., in the Daybreak architecture.
  • NU/NE bank 3500 may conduct an audit of the funds that have been spent and/or distributed for a given time.
  • the audit may include all of the downstream and/or upstream activity from NU/NE bank 3500.
  • the audit may be conducted through analysis of the ledger transactions executed by the Daybreak architecture 3 100. Audit details will be described in more detail further herein.
  • the reporting rule set may be implemented by NU/NE bank 3500, although, in other embodiments, any of the entities in Fig. 1 may implement the reporting rule set, alone or in conjunction with the Daybreak architecture 3 100, or singly by the Daybreak architecture 3 100.
  • NU/NE bank 3500 may include panticle 4300, which may include implementation of the reporting rule set.
  • panticle 4300 may include panticle 4310, in which a request for an audit of the account, e.g., whether the account has followed the rule set implemented by the various entities of Fig.
  • the audit may take any form as requested by the entity requesting the audit, and may include any data to which the requesting entity has access.
  • the audit may be performed by Daybreak architecture 3100, and facilitated or passed along by NU/NE bank 3500.
  • Daybreak architecture 3100 may assist NU/NE bank 3500 in performing the audit, and, in another embodiment, NU/NE bank 3500 may perform the audit without the assistance of Daybreak architecture 3100.
  • reporting rule set panticle 4300 may include a reporting evidence requirement panticle 4350.
  • Panticle 4350 may implement architecture in which reporting evidence of the transaction may be required.
  • the reporting evidence may be required as a condition of releasing the funds, which, in an embodiment, may be preventing the ledger transaction of the funds, or preventing an actual underlying transaction of the funds to the endpoint entity.
  • the panticle 4350 that requires reporting evidence may require, e.g., photographic evidence, as part of panticle 4352.
  • Photographic evidence here may include audio, video, still shot, any capture of light and/or motion in any portion of the electromagnetic spectrum, and also may include metadata, e.g., timestamp of photo and/or geolocation tagging of photo (e.g., from a camera device with geolocation/timestamp tagging enabled).
  • metadata e.g., timestamp of photo and/or geolocation tagging of photo (e.g., from a camera device with geolocation/timestamp tagging enabled).
  • NU/NE bank 3500 may implement reporting rule set at panticle 4300, which may include panticle 4350 requiring reporting evidence associated with the distribution of goods and/or services prior to payment being made of goods and/or services (e.g., or, in an embodiment, prior to approving the goods and/or services to be carried out/sold), as previously discussed.
  • panticle 4350 may include panticle 4354, which may implement a reporting rule set through use of various monitoring devices, which may be attached to various goods, e.g., food goods, shipping containers, vaccines, clothing, etc.)
  • the monitoring devices may use near-field communication, or may be RFID tags.
  • the monitoring may be accomplished through surveillance, e.g., visual, infrared, or some other form, from localized cameras or satellite cameras, for example.
  • NU/NE bank 3500 may implement reporting rule set at panticle 4300, which may include panticle 4350 requiring reporting evidence associated with the distribution of goods and/or services prior to payment being made of goods and/or services (e.g., or, in an embodiment, prior to approving the goods and/or services to be carried out/sold), as previously discussed.
  • panticle 4350 may include panticle 4356, which includes verification from a trusted source as a requirement for reporting.
  • an unknown/untrusted FO/NGO/FI 3800 which may be an endpoint entity, performs a service, and wants to receive compensation, they may seek verification from a trusted source, e.g., which may be a different FO/NGO/FI 3800, or some other entity, which may or may not be associated with the Daybreak architecture 3 100.
  • Daybreak architecture 3 100 may keep the list of trusted sources and require verification from those sources, however, in another embodiment, the trusted sources may become trusted sources through a relationship with NU/NE bank 3500 or one of the other banking entities or other entities shown in Fig. 1.
  • NU/NE bank 3500 may implement reporting rule set at panticle 4300, which may include panticle 4350 requiring reporting evidence associated with the distribution of goods and/or services prior to payment being made of goods and/or services (e.g., or, in an embodiment, prior to approving the goods and/or services to be carried out/sold), as previously discussed.
  • panticle 4350 may include panticle 4358 and/or panticle 4359, which may require real time reporting associated with implementation of the goods and/or services, or real time reporting associated with payment for the implementation of the goods and/or services.
  • FO/NGO/FI 3800 may implement a reporting rule set to report back to one or more entities shown in Fig. 1, e.g., in various embodiments, in conjunction with the Daybreak architecture 3100.
  • FO/NGO/FI 3800 may implement reporting rule set panticle 4400, which includes audit provision panticle 4410 to provide an audit of the account and/or the funds that were spent by FO/NGO/FI 3800 to one or more of the entities shown in Fig. 1.
  • panticle 4400 as implemented by FO/NGO/FI 3800, ay include panticle 4450 for providing the reporting evidence to one or more entities, which has been previously described with respect to receiving that data.
  • panticle 4450 may include one or more of panticle 4452 for providing photographic evidence of the goods and/or services being delivered and/or provided.
  • photographic evidence here may include audio, video, still shot, any capture of light and/or motion in any portion of the electromagnetic spectrum, and also may include metadata, e.g., timestamp of photo and/or geolocation tagging of photo (e.g., from a camera device with geolocation/timestamp tagging enabled).
  • panticle 4450 may include one or more of panticle 4454 for providing the monitoring information related to the goods and/or services (e.g., food goods, shipping containers, vaccines, clothing, etc.).
  • the monitoring devices may use near-field communication, or may be RFID tags.
  • the monitoring may be accomplished through surveillance, e.g., visual, infrared, or some other form, from localized cameras or satellite cameras, for example, and panticle 4456 for providing verification from a trusted source, e.g., in an embodiment, if an unknown/untrusted FO/NGO/FI 3800, which may be an endpoint entity, performs a service, and wants to receive compensation, they may seek verification from a trusted source, e.g., which may be a different FO/NGO/FI 3800, or some other entity, which may or may not be associated with the Daybreak architecture 3 100.
  • Daybreak architecture 3 100 may keep the list of trusted sources and require verification from those sources, however, in another embodiment, the trusted sources may become trusted sources through a relationship with NU/NE bank 3500 or one of the other banking entities or other entities shown in Fig. 1.
  • panticle 4450 may include one or more of panticle 4458 and/or panticle 4459, which may require real time reporting associated with implementation of the goods and/or services, or real time reporting associated with payment for the implementation of the goods and/or services.
  • Fig. 1-G shows some examples of services performed by one or more of the entities shown in Fig. 1.
  • This list is not meant to be exhaustive or exclusionary, but merely exemplary.
  • one or more of the entities in Fig. 1 may include a reputation and/or trustworthiness module.
  • This module described in panticle 3600, may include a panticle 3610 in which the NU/NE bank 3500 (or another entity from Fig. 1 ; NU/NE bank 3500 is used throughout Fig. 1 -G as an example, but any entity from Fig. 1 or other entity may be substituted in various embodiments without changing the overall operation of the system).
  • NU/NE bank 3500 may verify the reputation and/or the trustworthiness of the FO/NGO/FI 3800, through one or more methods, including but not limited to, verification data (e.g., pictures, video, documents, trusted account numbers), pre-existing relationship, identity confirmation, or one or more other techniques which will be discussed in more detail herein.
  • verification data e.g., pictures, video, documents, trusted account numbers
  • panticle 3610 may facilitate verification of reputation through panticle 3612, which tracks a "reputation score" for various FO/NGO/FI entities (e.g., FO/NGO/FI 3800).
  • panticle 3610 may facilitate verification of various FO/NGO/FI entities through panticle 3614 which tracks or receives from a tracking entity a past accounting and/or a reporting history regarding the various FO/NGO/FI entities (e.g., FO/NGO/FI 3800).
  • Fig. 1-G shows some examples of services performed by one or more of the entities shown in Fig. 1. This list is not meant to be exhaustive or exclusionary, but merely exemplary.
  • one or more of the entities in Fig. 1 may include an NU/NE rule set panticle 3650.
  • NU/NE rule set panticle 3650 may, alone or in conjunction with Daybreak architecture 3100, facilitate one or more actions that go with implementing a rule set for the acquisition and/or distribution of funds, to one or more of subcontracting foreign organizations (e.g., subcontracting foreign organization 3700) and Foreign Organization/Non-Governmental Organization/Foreign Individual (FO/NGO/FI), e.g., FO/NGO/FI 3800.
  • subcontracting foreign organizations e.g., subcontracting foreign organization 3700
  • FO/NGO/FI Foreign Organization/Non-Governmental Organization/Foreign Individual
  • the rule set architecture will be described in more detail with respect to panticle 4900 of Fig. 1 -C.
  • NU/NE rule set panticle 3650 may receive the rule set from Daybreak architecture 3100.
  • the funds from the account 3030 may not be actually transmitted to NU/NE rule set panticle 3650, but may be transmitted through ledger transactions.
  • NU/NE rule set panticle 3650 may implement the rule set from Daybreak architecture 3100 for the funds from the account 3030 that are actually received by NU/NE bank 3500. [0140] In an embodiment, referring again to panticle 3650 of Fig.
  • panticle 3650 may include panticle 3652, in which panticle 3652 effects an implementation of an acquisition or a distribution of funds rule set based on a type of goods and/or services (e.g., food, water, potable water, medicine, vaccines, health care services, shelters, clothing, tools, transport services, vehicles, firearms, etc.).
  • a part of the distribution rule set may specify that the funds must be spent on vaccinations or organizations that provide vaccinations.
  • a part of the distribution rule set may specify that certain types of drugs cannot be purchased with funds from the account 3030, e.g., prohibition on Schedule 2 narcotics, for example.
  • panticle 3650 may include panticle 3654, in which panticle 3654 effects an implementation of an acquisition or a distribution of funds rule set based on a distribution area of goods and/or services (e.g., food, water, potable water, medicine, vaccines, health care services, shelters, clothing, tools, transport services, vehicles, firearms, etc.).
  • goods and/or services e.g., food, water, potable water, medicine, vaccines, health care services, shelters, clothing, tools, transport services, vehicles, firearms, etc.
  • the distribution area may be purely geographical (e.g., "between the two rivers," or “within a box defined by specific latitudes and longitudes), political (e.g., within the boundaries of a specific foreign country), or data-based (e.g., "only to areas in which the poverty rate is above 85%,” or “only to areas in which HIV infection is above 22%").
  • a part of the distribution rule set may specify that the funds can only be spent in targeted areas of sub-Saharan Africa.
  • panticle 3650 may include panticle 3656, in which panticle 3656 effects an implementation of an acquisition or a distribution of funds rule set based on a quantity of goods and/or services (e.g., food, water, potable water, medicine, vaccines, health care services, shelters, clothing, tools, transport services, vehicles, firearms, etc.) to be provided.
  • the numbers may be absolute, e.g., "this money must be used to purchase three thousand (3,000) vaccines,”) or relative (e.g., "30% of this money must be used to purchase vaccines).
  • Fig. 1 -G describes a subcontracting foreign organization (SFO) 3700.
  • SFO 3700 may communicate with one or more of the entities shown in Fig. 1.
  • SFO 3700 is shown in communication with NU/NE bank 3500, but SFO 3700 may communicate with other entities depicted in Fig. 1, regardless of whether lines are directly drawn that connect SFO 3700 to those entities (the same is also true for the other banks discussed previously and discussed herein).
  • SFO 3700 may receive funds from the account 3030 to manage and distribute, for example, among other Foreign Organizations, Non-Governmental Organizations, and Foreign Individuals, e.g., FO/NGO/FI 3800.
  • SFO 3700 may be enrolled in the Daybreak architecture 3100 and may manage ledger transactions to and/or from the various entities shown in Fig. 1.
  • SFO 3700 may include implementations of panticle 3710, in which panticle 3710 may implement verification of the reputation and/or the trustworthiness of the FO/NGO/FI 3800, through one or more methods, including but not limited to, verification data (e.g., pictures, video, documents, trusted account numbers), pre-existing relationship, identity confirmation, or one or more other techniques which will be discussed in more detail herein.
  • verification data e.g., pictures, video, documents, trusted account numbers
  • SFO 3700 may include implementations of panticle 3720, in which rule set panticle 3720 may, alone or in conjunction with Daybreak architecture 3100, facilitate one or more actions that go with implementing a rule set for the acquisition and/or distribution of funds, to one or more of subcontracting foreign organizations and/or Foreign Organization/Non-Governmental Organization/Foreign Individuals (FO/NGO/FI), e.g., FO/NGO/FI 3800.
  • the rule set architecture will be described in more detail with respect to panticle 4900 of Fig. 1 -C.
  • SFO rule set panticle 3720 may receive the rule set from Daybreak architecture 3100.
  • the funds from the account 3030 may not be actually transmitted to SFO rule set panticle 3720, but may be transmitted through ledger transactions.
  • NU/NE rule set panticle 3650 may implement the rule set from Daybreak architecture 3100 for the funds from the account 3030 that are actually received by SFO rule set panticle 3720.
  • FIG. 1-H shows Foreign Organization/Non- Governmental Organization/Foreign Individual (FO/NGO/FI) entity 3800.
  • FO/NGO/FI 3800 may be one or more of an end point services delivery entity, e.g., a truck driver, a doctor, a supplier, or a (or another) subcontracting entity, or a management entity, e.g., for a set of workers, or any other entity that is to receive payment of funds.
  • FO/NGO/FI entity 3800 includes panticle 3810.
  • Panticle 3810 is configured to facilitate execution of verification of the reputation and/or the trustworthiness of the FO/NGO/FI 3800, through one or more methods, including but not limited to, verification data (e.g., pictures, video, documents, trusted account numbers), pre-existing relationship, identity confirmation, or one or more other techniques which will be discussed in more detail herein.
  • the verification may continue down the chain to other FO/NGO/FIs that are receiving funds, or, in an embodiment in which FO/NGO/FI 3800 is the endpoint, then panticle 3810 may include taking the action that generates the verification data, or messaging a different entity with instructions to capture the verification data.
  • FO/NGO/FI 3800 may close the ledger for that particular unit of currency.
  • FO/NGO/FI 3800 may implement panticle 3810, as previously discussed.
  • Panticle 3810 may include panticle 3812, which, in an embodiment, may provide a reputation score of FO/NGO/FI 3800, or provide a reputation score of a further subcontracted entity, to one or more of the entities shown in Fig. 1 (it is noted that the reputation score is illustrated as provided to SFO 3700, but SFO 3700 may not be present in various embodiments, or FO/NGO/FI 3800 may provide the reputation score to a different entity, or to the Daybreak architecture 3 100, regardless of the presence of SFO 3700).
  • the reputation score may be numeric or scaled, or may be review-oriented, objective or subjective, or any combination thereof.
  • FO/NGO/FI 3800 may have a reputation score that it provides to various entities, but has no control over (e.g., other entities may change the reputation score, e.g., other entities shown in Fig. 1, other FO/NGO/FIs, or some combination thereof).
  • panticle 3812 may perform management of the reputation score, may verify the reputation score, and may deliver the reputation score.
  • FO/NGO/FI 3800 may implement panticle 3810, as previously discussed.
  • Panticle 3810 may include panticle 3814.
  • Panticle 3814 may, alone or in conjunction with Daybreak architecture 3100, provide past accounting and/or reporting history of FO/NGO/FI 3800, or another entity that reports to and/or has a relationship with FO/NGO/FI 3800.
  • Panticle 3814 may, alone or in conjunction with Daybreak architecture 3100, record, collect, receive, track, or perform other operations related to the accounting and/or reporting history of FO/NGO/FI 3800, for example, previous times that FO/NGO/FI 3800 received a good score for reporting promptly, or a bad score for failing to report promptly, or reporting in a format that was not accepted, or, for example, providing photographic evidence that did not show what was claimed to be shown.
  • FO/NGO/FI 3800 may implement panticle 3820, which may facilitate implementation of acceptance of the acquisition and/or the distribution rule set needed to receive funds.
  • panticle 3820 may include panticle 3822, which may implement verification of the type of goods and services that are to be provided (e.g., provides the data that will be sent to panticle 3650, which may be implemented by, for example, NU/NE bank 3500).
  • Verification of the goods and/or services may include providing verification that the types of goods and services were the types for which the distribution rule set specifies payment.
  • a part of the distribution rule set may specify that the funds must be spent on vaccinations or organizations that provide vaccinations.
  • a part of the distribution rule set may specify that certain types of drugs cannot be purchased with funds from the account 3030, e.g., prohibition on Schedule 2 narcotics, for example.
  • the verification may take various forms, e.g., as described in panticle 4600 with respect to Fig. 1- L.
  • verification may include one or more of photographic evidence, video camera evidence, surveillance camera evidence, satellite camera evidence, GPS verification evidence, RFID/serial number tracking evidence, verification from a trusted and/or known source evidence, or other implementations.
  • panticle 3820 may include panticle 3824, which may implement verification of where (e.g., at what location) the distribution of goods and/or services will occur.
  • panticle 3824 may implement that the distribution area may be purely geographical (e.g., "between the two rivers," or “within a box defined by specific latitudes and longitudes), political (e.g., within the boundaries of a specific foreign country), or data-based (e.g., "only to areas in which the poverty rate is above 85%," or "only to areas in which HIV infection is above 22%").
  • a part of the distribution rule set may specify that the funds can only be spent in targeted areas of sub-Saharan Africa.
  • panticle 3820 may include panticle 3826, which may implement verification of a quantity of goods and/or services that will be distributed.
  • panticle 3826 may implement an absolute, e.g., "this money must be used to purchase three thousand (3,000) vaccines,") or relative (e.g., "30% of this money must be used to purchase vaccines) quantity of goods, and provide verification to one or more other entities, e.g., entities depicted in Fig. 1.
  • panticle 3820 may include panticle 3828, which may implement verification of a source of the goods and/or services that are to be distributed.
  • the "source” may be an unverified location/supplier, and thus the verification implementation may be to verify that the goods and/or services that are received/performed by the FO/NGO/FI are authentic.
  • the source may be a verified shipper (e.g., shipping vaccine components from the United States), and panticle 3828 may implement verification that the goods that were alleged to be shipped for distribution have arrived and been verified.
  • panticle 3820 may include panticle 3829, which may implement the sending of a verification report that details verification that was performed by panticle 3820, e.g., one or more of verifications performed in panticles 3822, 3824, 3826, and 3828.
  • the verification report may detail the work performed by FO/NGO/FI 3800 if FO/NGO/FI 3800 is the endpoint for service performance/goods delivery.
  • the verification report may be kept as part of the Daybreak architecture 3100.
  • Daybreak architecture 3 100 may supplement, verify, confirm, or create (and/or prepare for verification) the report, alone or in conjunction with panticle 3820 of FO/NGO/FI 3800.
  • Fig. 1-L shows implementation of the distribution chain panticle 4600, e.g., by FO/NGO/FI 3800, although in other embodiments, the distribution chain 4600 could be implemented by any of the entities shown in Fig. 1.
  • panticle 4600 includes panticle 4605, which implements an architecture in which the distributor provides evidence with regard to goods and/or services to FO/NGO/FI 3800.
  • panticle 4605 may include panticle 4610 for providing photographic evidence of goods and/or services being distributed.
  • panticle 4610 may include one or more of panticle 4612 for implementing a photograph of the delivery vehicle delivering the goods and/or services, photographs of the license plates of the delivery vehicles or the receiving vehicles, photographs of the delivery persons (e.g., with optionally facial recognition algorithms to confirm identity, e.g., as with trusted sources) and panticle 4614 for implementing a photograph of location-identifying markers, e.g., street signs, mountains, and the like.
  • panticle 4612 for implementing a photograph of the delivery vehicle delivering the goods and/or services
  • photographs of the license plates of the delivery vehicles or the receiving vehicles photographs of the delivery persons (e.g., with optionally facial recognition algorithms to confirm identity, e.g., as with trusted sources)
  • panticle 4614 for implementing a photograph of location-identifying markers, e.g., street signs, mountains, and the like.
  • panticle 4605 may implement an architecture that includes panticle 4620, for location information of goods and services being distributed, e.g., GPS positioning or other location-based services, of, for example, delivery vehicles, goods, medical personnel, delivery personnel, and the like.
  • panticle 4605 may implement an architecture that includes panticle 4630 for monitoring data associated with distribution of goods and/or services, e.g., various monitoring devices, which may be attached to various goods, e.g., food goods, shipping containers, vaccines, clothing, etc.
  • the monitoring devices may use near-field communication, or may be RFID tags.
  • the monitoring may be accomplished through surveillance, e.g., visual, infrared, or some other form, from localized cameras or satellite cameras, for example.
  • panticle 4605 may implement an architecture that includes panticle 4640, that is, a confirmation form a trusted source, e.g., trusted individual information, e.g., at panticle 4642, such as RFID information, serial number information, and the like, a trusted organization/individual at panticle 4644, or an external audit of trustworthiness at panticle 4646.
  • a trusted source e.g., trusted individual information, e.g., at panticle 4642, such as RFID information, serial number information, and the like
  • a trusted organization/individual at panticle 4644 e.g., a trusted organization/individual at panticle 4644, or an external audit of trustworthiness at panticle 4646.
  • FO/NGO/FI 3800 may provide mechanisms for implementation of payment of the funds from the account 3030 (or other accounts with the funds originally donated, in various embodiments), to the FO/NGO/FI 3800 (and/or its specific representatives).
  • FO/NGO/FI 3800 may include a panticle 3830 that implements architecture for registering/creating an account with external payment architecture (e.g., Daybreak architecture) 3100.
  • FO/NGO/FI 3800 may create an account that allows FO/NGO/FI 3800 to receive funds, prepare reports, and ultimately "offboard" the funds from account 3030 (or other accounts) to the persons/entities.
  • Fig. 1 may register with the Daybreak architecture 3 100.
  • user 3005, organization 3015, Daybreak architecture 3 100, or another entity may impose registration with the Daybreak architecture 3100 as a prerequisite for participating in activities involving the funds contributed by user 3005/organization 3015.
  • user 3005, organization 3015, Daybreak architecture 3 100, or another entity may impose registration with the Daybreak architecture 3100 as a prerequisite for endpoint entities to receive funds, that is, it may be a prerequisite for those persons/entities performing the actual services in the locations for which the funds are specified.
  • registration with Daybreak architecture 3100 may be optional for one or more entities shown in Fig. 1.
  • registration with some sort of payment architecture, but not necessarily the Daybreak architecture 3100 may be required.
  • FO/NGO/FI 3800 may include panticle 3832, which may, alone or in conjunction with the Daybreak architecture 3100, verify that any distribution of funds to an endpoint entity (e.g., anyone receiving payment for goods and/or services rendered from the funds) comply with the acquisition and/or distribution rules specified previously by one or more of the entities in Fig. 1.
  • FO/NGO/FI 3800 may specify further conditions on the distribution rule set, in various embodiments.
  • FO/NGO/FI 3800 may include panticle 3834, which may request payment from the entity in possession of the funds, e.g., which may be different from the entity indicated by Daybreak architecture 3100 in the ledger transactions.
  • the ledger transactions may show that NU/NE bank 3500 is in possession of 6500 dollars of 10,000 original dollars (the rest being allocated for other entities in the chain), but in actuality the entirety of the 10,000 original dollars may still be with original account 3030.
  • the payment is received from the bank account (shown in panticle 3836), only one transfer is needed (from the original bank to the destination), although the ledger transactions show the funds passing between multiple, possibly numerous entities.
  • FO/NGO/FI 3800 may not have access to a concrete bank.
  • Daybreak architecture 3 100 may interface with a local endpoint payment delivery system, as shown in panticle 4500.
  • local endpoint payment delivery system 4500 may be a money transfer, financing, or microfinancing service, e.g., M-Pesa, or any other service, e.g., a Know Your Customer (KYC) service.
  • KYC Know Your Customer
  • a payment delivery system may receive payment instructions, e.g., from Daybreak architecture 3100, or from one of the other entities in Fig. 1, or a combination thereof, at panticle 4150.
  • the individual without a bank account may be identified and/or located using the endpoint payment delivery system at panticle 4520 (this panticle includes the process of communicating via the endpoint payment delivery system, e.g., the M-Pesa system).
  • payment is then effected by an external transfer from one of the entities in Fig. 1 to the endpoint payment delivery system, at panticle 4530, and the payment is delivered to the person through the endpoint payment delivery system at panticle 4540.
  • Fig. 1-1 shows some details of the tracking/verification account, which may, in various embodiments, be controlled by Daybreak architecture 3100, or may be implemented at one or more of the entities described throughout Fig. 1, or may be implemented as some combination thereof.
  • panticle 4100 groups some of the details of the tracking and verification account located inside or outside the United States.
  • tracking/verification panticle 4100 includes a user query unit 41 10.
  • User query unit 41 10 may be configured to respond to one or more queries from the user, e.g., user 3005, or another member of the charity organization 3015, or any other representative of an entity depicted in Fig. 1 that has been given access to view the system information.
  • user query unit 41 10 may respond to example queries from an authorized user.
  • a non-exhaustive list of queries is shown inside panticle 41 10.
  • some of the queries handled by user query unit 41 10 include a current location of funds query (e.g., a query requesting location data of some or all of the funds, whether via the ledger transactions or the actual accounts where the funds reside), a current account balance query (e.g., a query that requests the current account balance, from one or more of the entities described in Fig.
  • a current location of funds query e.g., a query requesting location data of some or all of the funds, whether via the ledger transactions or the actual accounts where the funds reside
  • a current account balance query e.g., a query that requests the current account balance, from one or more of the entities described in Fig.
  • a goods and/or services purchased query e.g., a query that requests a detailed report of the goods and/or services that have been purchased from the account to date
  • a goods and/or services distributed query e.g., a query that requests detail regarding to whom the goods and or services purchased by the account have been distributed
  • a verification of goods and/or services distributed query e.g., a query that shows, for example, if any of the goods and/or services were distributed in a manner that does not follow the specified rule sets).
  • panticle 4100 may group some of the details of the tracking and/or verification account, which may be located inside or outside the United States.
  • tracking/verification panticle 4100 may include a recording unit 4120.
  • Recording unit 4120 may record transactions involving the funds in the account 3030, or may record transactions between the various entities shown in Fig. 1, or some combination thereof.
  • recording unit 4120 may record ledger transactions, actual transactions (e.g., ACH transactions or wire transfers), both, or some combination based on characteristics.
  • recording unit panticle 4120 may facilitate one or more actions, such as record a location of funds, e.g., at various intervals, for example, a daily recordation, a monthly recordation, a check every hour, a check every second, or any interval whether repeating or nonrepeating.
  • recording unit panticle 4120 may facilitate one or more actions record a transfer of funds, e.g., each time funds are transferred, e.g., whether an actual funds transfer or a ledger transaction, from any of the entities shown in Fig. 1, to any other entity, or any other transaction that involves account 3030 or the funds contributed by user 3005.
  • the recordation may occur on an ad-hoc basis, or may occur at specific intervals (e.g., every hour, or every day, for example). There may be multiple recordations and/or multiple reports generated in various embodiments.
  • recording unit panticle 4120 may facilitate one or more actions, such as record goods and/or services that are acquired based on funds in the account 3030 or other funds associated with user 3005. For example, when funds are provided for the acquisition of services, whether to the endpoint user (e.g., through a payment system, e.g., M-PESA), or to a middle entity (e.g., a sub-contractor), the goods and/or services that are acquired, or that are alleged to have been acquired, may be recorded. This may include various verification techniques which will be discussed in more detail further herein.
  • a payment system e.g., M-PESA
  • middle entity e.g., a sub-contractor
  • recording unit panticle 4120 may facilitate one or more actions, such as recording fees associated with various accounts, e.g., account 3030 as it passes through one more entities in ledger transactions, or actual account fees, e.g., maintenance fees and/or convenience fees for one or more actual accounts held by one or more entities shown in Fig. 1.
  • panticle 4100 may provide some measure of digital security to one or more transactions, whether actual transactions or ledger transactions, shown in Fig. 1.
  • digital security unit panticle 4130 may be implemented as a digital security unit that facilitates provision of digital security to the account 3030, to another account, to one or more of the entities shown in Fig. 1-1, to one or more specific transactions, or to some combination thereof.
  • digital security unit 4130 may operate inside or outside the United States, or a combination thereof.
  • digital security unit 4130 may include one or more of identity verification, transaction verification, transaction security, and the like.
  • digital security unit panticle 4130 may use digital currency, e.g., Bitcoin, for one or more transactions.
  • digital currency e.g., Bitcoin
  • the use of digital currency may be transparent or may be hidden from the participants in the transaction (e.g., the Bitcoin transaction is an underlying layer.
  • one or more digital currencies may be used, including, for example, a sub-category of digital currencies commonly referred to as cryptocurrencies.
  • cryptocurrencies include, for example, Bitcoin, Ripple, Primecoin, and so forth.
  • Some common features among all of these digital currencies include maintaining a global electronic ledger (e.g., in Bitcoin, this is referred to as a "block chain") that includes records of all global transactions and a requirement that a relatively complex problem (typically a complex mathematical problem), which in Bitcoin is called "proof of work" be solved whenever a bundle of transactions is to be recorded to the global electronic ledger in order to ensure trustworthiness of the recorded transactions.
  • a global electronic ledger e.g., in Bitcoin, this is referred to as a "block chain” that includes records of all global transactions and a requirement that a relatively complex problem (typically a complex mathematical problem), which in Bitcoin is called "proof of work" be solved whenever a bundle of transactions is to be recorded to the global electronic ledger in order to ensure trustworthiness of the recorded
  • each transaction requires a new address to be used for each recipient receiving the spent currency.
  • Each transaction is recorded in a transaction block (e.g., a page in global electronic ledger), and a transaction block will at least identify the account/address that the "spent" digital currency originated from.
  • a transaction block e.g., a page in global electronic ledger
  • a transaction block will at least identify the account/address that the "spent" digital currency originated from.
  • each unit of currency in the bitcoin eco-system can be traced back to its origin even though Bitcoin is often lauded/despised because of its ability to maintain the anonymity of its participates.
  • This anonymity feature exists partially because the users whose addresses where currencies are being deposited/assigned to remain publically anonymous (e.g., only a participant knows the addresses that belong to the participant).
  • Other types of cryptocurrencies function in similar fashion with some relatively subtle differences.
  • digital security unit panticle 4130 may include one or more implementations of a secure pipeline 4134 that ensures security of a transaction between one or more parties.
  • secure pipeline 4134 may include, as a non-limiting example, a Secure Electronic Transaction (SET) system, or a 3-D secure XML- based protocol.
  • Secure pipeline 4134 may include one or more of such implementations as an electronic wallet, a verified digital certificate, a combination of digital certificates and/or digital signatures.
  • Secure pipeline 4134 may implement or ensure the use of such technologies as Secure Sockets Layer (SSL), Secure Transaction Technology (STT), Secure Hypertext Transfer Protocol (S-HTTP).
  • SSL Secure Sockets Layer
  • STT Secure Transaction Technology
  • S-HTTP Secure Hypertext Transfer Protocol
  • tracking/verification panticle 4100 may include a real time tracking/accounting panticle 4140.
  • Real time tracking/accounting panticle 4140 may provide one or more real time functions for, for example, user 3005, although any of the entities shown in Fig. 1 may, in various embodiments, have access to real time tracking and/or real time accounting.
  • real time tracking/accounting panticle 4140 may, in various embodiments, be controlled by Daybreak architecture 3100, or may be implemented at one or more of the entities described throughout Fig. 1, or may be implemented as some combination thereof.
  • real time also may mean “near real time,” that is, not delivered in what is colloquially considered to be “real time,” but near enough to provide a simulation of real time, due to delays in transmission, processing, or displaying the information, for example.
  • tracking/verification panticle 4100 may include implementation details for a reward/penalty unit 4150.
  • Reward/penalty unit 4150 may, in various embodiments, be controlled by Daybreak architecture 3100, or may be implemented at one or more of the entities described throughout Fig. 1 , or may be implemented as some combination thereof.
  • Reward/penalty unit 4150 may be implemented by a rule set specified by one or more of the entities shown in Fig. 1, including user 3005 and organization 3015.
  • reward/penalty unit 4150 may use all or a portion of a default rule set specified by Daybreak architecture 3100 or one or more of the other entities.
  • more than one entity may provide a rule set, and, in an embodiment, multiple rule sets may be honored or attempted to honor.
  • a first rule set may supersede a second rule set.
  • reward/penalty unit panticle 4150 may perform one or more of rewarding prompt reporting, penalizing late reporting, returning funds if graft and/or failure to report and/or misuse of funds is detected, and return of funds if goods and/or services are not provided within a particular time frame. Verification of what is happening at endpoints (e.g., through GPS/photographic evidence/etc.) will be discussed in more detail elsewhere in this application.
  • the First Party Device e.g., a User Device, as Shown in Fig. 2C-1
  • Fig. 2C-1 shows an implementation of a user machine/first party machine 220, according to various embodiments, operating in environment 200.
  • user device 220 may be a device associated with a user 100.
  • user 100 may be an account holder of the attributable account.
  • user 100 may be a philanthropist/philanthropic organization/philanthropic entity who intends to give away portions of his funds to various charitable interests.
  • user 100 may be a for-profit person, business, organization, or other entity.
  • user 100 may be the "first party" referenced herein, although in other embodiments, the "first party" may be any person, entity, being, computer, terminal, or other discrete object/person/machine.
  • First party machine 220 may be a whole or portion of a device, any electronic device, or combination of devices, which may be located together or spread across multiple devices and/or locations.
  • First party machine 220 may be a server device, or may be a user-level device, e.g., including, but not limited to, a laptop computer, a personal computer, cellular phone, a network phone, a smartphone, a tablet, a music player, a walkie-talkie, a radio, an augmented reality device (e.g., augmented reality glasses and/or headphones), wearable electronics, e.g., watches, belts, earphones, or "smart" clothing, earphones, headphones, audio/visual equipment, media player, television, projection screen, flat screen, monitor, clock, appliance (e.g., microwave, convection oven, stove, refrigerator, freezer), a navigation system (e.g., a Global Positioning System ("GPS”) system), a medical alert device, a remote control, a peripheral, an electronic safe, an electronic lock, an electronic security system, a video camera, a personal video recorder, a personal audio recorder, and the like.
  • GPS Global Positioning
  • first party machine 220 may include electrical/magnetic/physical storage 222.
  • electrical/magnetic/physical storage may include any form of storing data, whether temporary or permanent, for example, in the electrical and/or magnetic field, any sort of memory or data storage, including, but not limited to, random access memory (“RAM”), read only memory (“ROM”), flash memory, hard drives, disk-based media, magnetic storage, optical storage, volatile memory, nonvolatile memory, mass storage devices, programmable read-only memory (“PROM”), erasable programmable read-only memory (“EPROM”), electronically- erasable programmable memory (“EEPROM”), cache memory such as random access memory (RAM), flash memory, synchronous random access memory (SRAM), dynamic random access memory (DRAM), and/or other types of memory.
  • RAM random access memory
  • ROM read only memory
  • EPROM erasable programmable read-only memory
  • EEPROM electronically- erasable programmable memory
  • cache memory such as random access memory (RAM), flash memory, synchronous
  • first party machine 220 may include a graphics card with a Graphics Processing Unit (GPU) that may be part of processor 251, and a dedicated memory that may be part of electrical/magnetic/physical storage 222.
  • GPU Graphics Processing Unit
  • physical storage may refer to physical media on which magnetic data are stored, or it may refer to the storage of data coded into physical obj ects, e.g., biological constructs, quantum constructs, and, in a basic sense, physical machines, e.g., a simple example of which would be gears and levers that can maintain data storage, e.g., as in a Difference Engine.
  • physical obj ects e.g., biological constructs, quantum constructs
  • the electrical/magnetic/physical storage may be remote or partially remote from first party machine 220, such as stored in a cloud storage device, or in situations in which first party machine 220 acts as a "thin client" or terminal.
  • first party machine 220 such as stored in a cloud storage device, or in situations in which first party machine 220 acts as a "thin client" or terminal.
  • Figs. 3A-3C for example, such implementations are contemplated by Fig. 2C-1, and such implementations of remote memory should be considered as part of first party machine 220.
  • first party machine 220 may include a processor 251.
  • Processor 251 may include one or more microprocessors, Central Processing Units ("CPU"), a Graphics Processing Units ("GPU"), Physics Processing Units, Digital Signal Processors, Network Processors, Floating Point Processors, and the like.
  • processor 222 may be a server.
  • processor 222 may be a distributed-core processor. Although processor 222 is as a single processor that is part of a single device 220, processor 222 may be multiple processors distributed over one or many devices 220, which may or may not be configured to operate together.
  • processor 251 may be performed remotely, e.g., at a remote site, with first party machine 220 acting as a thin client. Such implementations should be considered as the processor 251 as part of first party machine 220. See, e.g., Figs. 3A-3C.
  • processor 251 may include at least one input acceptance machine 252, which will be discussed in more detail with respect to Fig. 5A herein, at least one first track data presentation machine 254, which will be discussed in more detail with respect to Fig. 7A herein, and/or at least one second track data presentation machine 256 which will be discussed in more detail with respect to Fig. 5C herein.
  • processor 251 may include creation of three or more machines, e.g., within a processor or partially within a processor, that correspond to at least one input acceptance machine 252, which will be discussed in more detail with respect to Fig. 5A herein, at least one first track data presentation machine 254, which will be discussed in more detail with respect to Fig. 5B herein, and or at least one second track data presentation machine 256 which will be discussed in more detail with respect to Fig. 9A herein.
  • first party machine 220 may include a resolution circuit 270.
  • a resolution circuit 270 may, as a simplification, connect one or more parts of the first party machine 220 that are not specific to the workings described in this specification/invention, to the specific machines specified, that is at least one input acceptance machine 252, and at least one first track data presentation machine 254. Resolution circuit 270 will be described in more detail further herein.
  • first party machine 220 may include other machine components 260. It is noted that other machine components 260 may be optional components, that is, not every first party machine 220 will have all or necessarily any of the components listed as other machine components 260.
  • first party machine 220 may include one or more machine hardware and device drivers 262, which may be specific hardware components of first party machine 220, and drivers for the specific hardware components, e.g., video drivers, audio drivers, input device drivers, network communications drivers, mass storage drivers, and their concordant hardware components.
  • first party machine 220 may include a communications network interface 263, in which first party machine 220 may communicate with other devices.
  • communications/network interface 263 may be one or more of an Ethernet card, a LAN card, an antenna (e.g., a 4G LTE antenna), a cable port, a network interface card, or similar. Communications/network interface 263 may be adapted to communicate with a communication network 240.
  • the communication network 240 may include one or more of a local area network (LAN), a wide area network (WAN), a metropolitan area network (MAN), a wireless local area network (WLAN), a personal area network (PAN), a Worldwide Interoperability for Microwave Access (WiMAX), public switched telephone network (PTSN), a general packet radio service (GPRS) network, a cellular network, and so forth.
  • the communication networks 240 may be wired, wireless, or a combination of wired and wireless networks. It is noted that “communication network” as it is used in this application refers to one or more communication networks, which may or may not interact with each other. It is further noted that, throughout this specification, reference may be made to the “two way communication” or “two way connection,” which may utilize communication network 240 regardless of whether communication network 240 is specifically illustrated.
  • first party machine 220 may include one or more input/output interfaces 264.
  • Input/output interface 264 may include one or more of a speaker, microphone, screen, touchscreen, mouse, keyboard, pen, haptic sensor, environment sensor (e.g., that measures temperature, humidity, motion, speed, etc.), and the like.
  • first party machine 220 may include various implemented APIs 265 which may be implemented to allow first party machine 220 to perform various tasks.
  • FIG. 2C-1 shows components separately in first party machine 220, this is merely for convenience.
  • processor 251 may in fact be many processors/subprocessors used throughout first party machine 220, and which may shift through various configurations as specific machine states faster than human comprehension, e.g., two billion times per second (e.g., for a device operating at 2 GHz, for example).
  • the First Party Device e.g., a User Device, as Shown in Fig. 2C-2
  • FIG. 2C-2 shows a more detailed version of a first party machine 220B including a processor 25 IB, which is a different implementation of processor 251, according to another embodiment.
  • processor 25 IB which is a different implementation of processor 251
  • Many of the features of first party machine 220B are similar to first party machine 220, and those portions which are similar to the embodiments shown in Fig. 2C-1 are not be repeated.
  • first party machine 220B may include a processor 25 IB.
  • Processor 25 IB may include one or more microprocessors, Central Processing Units ("CPU"), a Graphics Processing Units ("GPU"), Physics Processing Units, Digital Signal Processors, Network Processors, Floating Point Processors, and the like.
  • processor 25 IB may be a server.
  • processor 25 IB may be a distributed-core processor.
  • processor 25 IB is illustrated in Fig. 2C-2 as a single processor that is part of a single first party machine 220B, processor 25 IB may be multiple processors distributed over one or many first party machine 220B, which may or may not be configured to operate together.
  • Processor 25 IB is illustrated as being configured to execute computer readable instructions in order to execute one or more operations described above, and as illustrated in Fig. 14, Figs. 15A-15F, Figs. 16A-16H, and Figs. 17A-17C.
  • processor 222 is designed to be configured to operate as processing module 251, which may include one or more of an input acceptance circuit 252B, which may be configured to receive input that regards an attributable account that contains attributable funds and that is configured to interface with one or more financial entities, wherein the attributable funds are governed by a distribution rule set, a first transaction data receiving circuit 254B that may be configured to receive first transaction data indicating a first transmission of particular funds from a first downstream entity to a second downstream entity, wherein the particular funds are part of the attributable funds, and a second transaction data receiving circuit 256B configured to receive second transaction data indicating a second transmission of the particular funds from the second downstream entity to the third downstream entity.
  • processing module 251 may include one or more of an input acceptance circuit 252B, which may be configured to receive input that regards an attributable account that contains attributable funds and that is configured to interface with one or more financial entities, wherein the attributable funds are governed by a distribution rule set
  • a first transaction data receiving circuit 254B
  • first party machine 220B may include electrical/magnetic/physical storage 222.
  • electrical/magnetic/physical storage 222 may include processor configuration instructions 222A which cause the processor 25 IB to form various circuits, e.g., input acceptance circuit 252B, first transaction data receiving circuit 254B, and second transaction data receiving circuit 256B.
  • Processor configuration instructions 222A may allow processor 25 IB to use advanced techniques to form the various circuits, including pipelining, instruction-level parallelism, branch prediction, branch delays, instruction scheduling, out-of-order execution, and instruction cache.
  • processor 25 IB may be formed at some point in the cycle, even if different parts of the circuit are broken down and re-purposed according to the instruction unit of processor 25 IB. Such implementations, usually done for processor optimization (although not always) should not be considered as preventing or not implementing the formation of the various circuits of processor 25 IB, e.g., input acceptance circuit 252B, first transaction data receiving circuit 254B, and second transaction data receiving circuit 256B. The same is true for the implementations discussed throughout this application, including with respect to Fig. 2C-1 and elsewhere.
  • Fig. 2D shows an implementation of the daybreak architecture, e.g., daybreak architecture 250D, according to various embodiments. It is noted that, throughout this disclosure, with regards to the daybreak architecture and/or other elements described herein, different numbers may be used to describe similar/the same elements. In such an instance, it is to be understood that such numbering is merely to distinguish embodiments, which may be interchangeable unless logically inconsistent.
  • daybreak architecture 250D has a single attributable account 252D.
  • Attributable account 252D may reside at a bank, either foreign or domestically. Any time funds, e.g., new attributable funds, e.g., attributable funds 253D, are put into the daybreak architecture, the funds are transferred to the attributable account.
  • the funds may (but are not required to) be commingled.
  • attributable funds 249D other unrelated attributable funds 243D and 242D are deposited into the same bank account 248D.
  • the daybreak architecture 250D manages the attributable funds 253D and the other attributable funds 254D and 255D and prevents the funds from becoming entangled.
  • daybreak architecture 250D has multiple attributable accounts, e.g., 252E, 254E, and 255E, which contain attributable funds 253E, 256E, and 257E, respectively.
  • each attributable account represents a separate bank account in an underlying bank, e.g., attributable account 252E may be associated with underlying bank account 248E, other attributable account 254E may be associated with bank account 244E, and other attributable account 255E may be associated with bank account 245E. It is noted that bank accounts 248E, 244E, and 245E need not be lodged with the same bank.
  • the accounts kept at various banks may not match exactly with the accounts managed by the daybreak architecture 250E.
  • the bank associated with bank account 244E offers better terms of service for the account if there is more than ten million dollars in the account, then multiple accounts may be combined or split so that the money "actually" resides in bank account 244E.
  • the location of the funds is managed by daybreak architecture 250E, such that, if movement of funds to/from the underlying accounts is required, the architecture determines which banks from which to withdraw the funds.
  • Figs. 2F to 2N describe a transfer of funds through the daybreak architecture 3100, according to one embodiment. It is noted that this is merely an example embodiment and is not intended to be limiting, but rather to be illustrative of one example of a process executed by the daybreak architecture 3100 and first party machine 220.
  • Fig. 2F shows a first step in the use of the daybreak architecture 250F.
  • a user or organization e.g., user 25 IF
  • the deposit is made internally to the daybreak architecture for 10 million dollars to user 251F's attributable account 252F (1) in Fig. 2F).
  • the ten million dollars is transferred from original bank account 205F to the account associated with the daybreak architecture, e.g., through an ACH or other similar type of transfer (e.g., wire transfer) (e.g., (2) in Fig. 2F).
  • the user 25 IF wants to "transfer six million dollars to a large foreign entity (LFE 280G) for charitable purposes. "
  • LFE 280G a large foreign entity
  • an internal transaction is made from the attributable account 252F to the daybreak architecture account associated with LFE 280G, that is, account 252G. This transaction is checked for compliance with the distribution rule set, and may be approved, denied, or held pending further review.
  • Daybreak Architecture transfers 6 million dollars from the attributable account 252F to an account within daybreak architecture associated with LFE 280G. Regardless of the outcome of the check for compliance with the distribution rule set, no actual funds transfer takes place— e.g., the six million dollars stays with the daybreak architecture account 262F where it was transferred in Fig. 2F.
  • LFE 280G after receiving the six million dollars, LFE 280G wants to transfer two million dollars to a subcontractor 280H, e.g., to build a hospital.
  • two million dollars will be transferred from the daybreak architecture account associated with LFE 280G, that is, daybreak architecture account 252G, to the daybreak architecture account associated with sub 280H, that is daybreak architecture account 252H.
  • Daybreak Architecture transfers 2 million dollars from the Account 252G of LFE 280G to Subcontractor SUB 28 OH who complies with the Distribution Rule Set (1) in Fig. 2H, but (2) no actual funds transfer happens between the various banks. The ten million dollars is still in account 262F.
  • Fig. 21 shows what happens if a proposed transfer does not comply with the distribution rule set.
  • LFE 280G attempts to transfer one million dollars to subcontractor 2801, e.g., who is not on an approved list, or who fails the fraud prevention analysis (e.g., as discussed in more detail in Fig. 5).
  • the transaction is denied for noncompliance with the distribution rule set, and no money is transferred, either within the daybreak architecture or in the actual underlying banks.
  • the daybreak architecture 250F may be set to initially allow the transaction to go through, but then "claw back" the funds, whether by human intervention or failure of one of the automated fraud protection analyses. Due to the daybreak architecture not actually moving the money between bank accounts, this claw back becomes simpler to perform.
  • Sub 280H (who received two million dollars in Fig. 2H), wants to transfer one million dollars to trucking company 280J for purchasing cement mixer trucks. In an embodiment, this transaction is again checked for compliance with the distribution rule set. In an embodiment, the transaction clears the distribution rule set, and one million dollars is transferred from daybreak architecture account 252H to daybreak architecture account 252K, as shown in (1) of Fig. 2J. It is noted, however, that no actual funds transfer takes place (2).
  • TrCo Trucking Company
  • TrCo 280J needs the million dollars to gas up the trucks (for example).
  • Trucking Company is going to use the one million dollars to pay for gas.
  • TrCo 280J makes a request to "offboard" the funds, that is, to remove them from the daybreak architecture 250F.
  • the transaction again may be checked for compliance with the distribution rule set— e.g., the trucking company may be allowed only to spend 100,000 dollars at a time. But, in an embodiment, if the transaction is approved in view of the distribution rule set, the transaction is approved, and recorded within the daybreak architecture (1).
  • funds are then transferred directly from the bank associated with the daybreak architecture 260F to the bank associated with the TrCo 280J.
  • all middle entities are avoided, and fees can be reduced, which may be small if all ACHs are used, but other forms of transfer may be more, to say nothing of fees associated with establishing many accounts at many banks along the way.
  • the Sub 280H may want to spend the funds directly, e.g., to buy large quantities of concrete directly to save money.
  • Sub 280H requests to offboard 500,000 dollars, and the transaction is checked with the distribution rule set. If the transaction clears, then (1) the transfer is recorded within the daybreak architecture and (2) the funds are transferred directly from the attributable account either 1) to the concrete supplier or 2) to the sub 280H account, depending on various embodiments.
  • the Sub 280H may be owed 100,000 dollars in management fees for overseeing the proj ect.
  • this withdrawal complies with the distribution rule set (e.g., management fees are capped at 10% of total imbursement)
  • the withdrawal is recorded within the daybreak architecture (1), and the funds are transferred directly to the Sub 280H bank account, where the funds are no longer tracked by the daybreak architecture because they have been "paid" to the Sub 280H.
  • LFE 260G may be owed 1,000,000 dollars in management fees for overseeing the project.
  • this withdrawal complies with the distribution rule set, then the withdrawal is recorded within the daybreak architecture (1), and the funds are transferred directly to the LFE 280G's bank account 262G, where the funds are no longer tracked by the daybreak architecture.
  • Fig. 3A shows a high level view of various systems that interact in order to facilitate first party machine 220 to operate.
  • a first party device e.g., a computer 310, that is created by a corporate entity "C" is shown.
  • Fig. 3A shows parts or wholes of at least one of (a) driving a state change of a data presentation device within a domestic (United States) jurisdiction; (b) driving a state change of a data communication device within a domestic (United States) jurisdiction; and (c) driving a state change of a data computation device within a domestic (United States) jurisdiction may include receiving a signal of at least one state change outside United States jurisdiction, and in response to the signal of at least one state change outside United States jurisdiction driving a state change of a data presentation device within United States jurisdiction, (b) driving a state change of a data communication device within United States jurisdiction, or (c) driving a state change of a data computation device within United States jurisdiction.
  • receiving a signal of at least one state change outside United States jurisdiction e.g., receiving a signal over two-way connection 392 from corporate entity "A" Computer and program 330 (e.g., "Google Cloud Services Server Farm"), which, in an embodiment, may be placed slightly beyond United States jurisdiction in an effort to avoid some United States patents as drafted (e.g., server farm on a barge in extraterritorial waters or in Canada/Mexico/Trinidad-Tobago, etc.); and in response to the signal of at least one state change outside United States jurisdiction (e.g., the signal received from and transmitted into the Unites States via corporate entity "A" Computer and program 330 (e.g., "Google Cloud Services Server Farm") outside the United States connection with the United States in the form of two-way connection 392), for example, at least one of (a) driving a state change of a data presentation device within United States jurisdiction (e.g., changing a voltage driving a pixel of a display of desktop computer
  • receiving a signal of at least one state change outside United States jurisdiction and in response to the signal of at least one state change outside United States jurisdiction driving a state change of a data presentation device within United States jurisdiction, (b) driving a state change of a data communication device within United States jurisdiction, or (c) driving a state change of a data computation device within United States jurisdiction also constitutes action/presence within United States jurisdiction in that when another endpoint 393B of two-way connection 393, in the ownership or control of another legal entity, e.g., that may be different from person 305, and in which said another legal entity, who in some instances might be outside of United States jurisdiction (e.g., Corporate User/Legal Owner 341 of Corporate Entity "Z" computer & program (e.g., "Amazon Cloud Services Server Farm”) placed slightly outside of U.
  • Fig. 3B shows a high level view of various systems that interact in order to facilitate first party machine 220 to operate.
  • a first party device e.g., a computer 310, which is created by a corporate entity "C" is shown.
  • Fig. 3B Fig.
  • 3B shows that parts and/or wholes of driving a change of matter or energy within the ownership or control of a single legal entity may include at least one of (a) driving a state change of a data presentation device within a domestic (United States) jurisdiction; (b) driving a state change of a data communication device within a domestic (United States) jurisdiction; and (c) driving a state change of a data computation device within a domestic (United States) jurisdiction.
  • Fig. 3C shows a high level view of various systems that interact in order to facilitate first party machine 220 to operate.
  • a first party device e.g., a computer 310, which is created by a corporate entity "C" is shown.
  • Fig. 3C shows that parts and/or wholes of "creating one or more machine states that link at least two parts of ... (e.g., as described in operations notice clause 1) may include driving a change of matter or energy within a domestic (United States) jurisdiction.
  • Fig. 3D shows a high level view of various systems that interact in order to facilitate first party machine 220 to operate.
  • a first party device e.g., a computer 3 10, that is created by a corporate entity "C" is shown.
  • Fig. 3D Fig.
  • 3D shows that parts and/or wholes of "creating one or more machine states that link at least two parts of " (e.g., as described in operations notice clause 1) may include driving a change of matter or energy within the ownership or control of a single legal entity, for example, driving a change of matter or energy within the ownership or control of a single legal entity (e.g.., person within United States jurisdiction 305D, who may be tablet/smartphone computer user) to form a single end 393 A of a two-way communication channel 393 (e.g., fiber optic cable) where the other end 393B might be in the ownership or control of another legal entity different from person/entity 305D (e.g., Corporate User/Legal Owner 34 ID of Corporate Entity "Z” Computer & Program 340, e.g., "Amazon Cloud Services Server Farm," which as illustrated, may in some instances be within United States jurisdiction but which will often more likely be placed slightly beyond United States jurisdiction in an effort to avoid some United States patents as drafted (e.
  • any party so closing/connecting e.g., via closing of an electronic switch or relay such as might be used in fiber optic or wireless communication
  • any party so closing/connecting makes/uses the claimed subject matter and is noticed up that joint/several liability for infringement via such closing/connection is taught and contemplated.
  • Fig. 4A shows some various fraud detection schemes that may be implemented by daybreak architecture 3 100.
  • daybreak architecture 3 100 For example, in an embodiment, there are some "phantom vendor” scheme specific patterns that may be recognized, which will be discussed in more detail herein.
  • the daybreak architecture may, optionally through use of the distribution rule set, perform one or more fraud detection schemes 400.
  • one fraud detection scheme 400 covered by the daybreak architecture is a phantom vendor fraud detection scheme 410.
  • a dirty contractor or entity makes a payment to a vendor that either doesn't exist (and then steals the money), or a "shadow" vendor that will kick back all or a portion of the money to the dirty entity in exchange for releasing the funds to them.
  • each transaction may receive a "score,” based on one or more factors regarding how suspicious the activity is. For example, there may be many factors that, by themselves would not be suspicious, but added up, make the overall transaction suspicious enough to either halt the transaction or call for further review of the transaction prior to allowing the transaction through the daybreak architecture or through offboarding the funds.
  • a transaction is done late at night, on a weekend, with a newly-established vendor, with a vendor that only has a post office box, with a vendor with a middling trust factor, with a vendor with no prior history of authentication, e.g., through RFID tagging, pictures, etc., alone these factors may be insufficient to trigger a refusal, but together they may provide a "score" that indicates to hold or deny the transaction.
  • transaction timing may matter (e.g., transaction timing 422).
  • suspicious vendor activity 424 may matter. An example of this would be at 426, where, upon payment creation, identify payments made to a vendor that had been dormant for 12 months, had vendor details changed, and then received a payment.
  • a dormant vendor one that hasn't had any transactions related to it in, for example, over a year
  • the daybreak architecture would make this a difficult fraud scheme to execute.
  • invoice creation Upon invoice creation, identify invoices for a vendor where that vendor has one user for all of the invoices it submitted, because, in an embodiment, if multiple people deal with a vendor, it may be more difficult to cover up fraudulent activity. If a vendor's invoices are only created or approved by one person, it is riskier than if a vendor has exposure to various users. If an invoice for a vendor that only has one user for all of its invoices is detected, flag the transaction for this analytic.
  • invoice creation Upon invoice creation, identify invoices for a single vendor that are sequentially numbered, or payments to a vendor that have no other customers, or vendors that have a name that consists only of initials, or that is very short, e.g., four or fewer characters).
  • a more generic sounding vendor could provide almost any type of product or service and may be harder to track. If a vendor name is particularly short or contains just initials, flag the transaction for this analytic.
  • daybreak architecture 3100 may receive a signal that offboarding has been requested and approved 450.
  • daybreak architecture now may communicate with the underlying bank 480 of the offboarding entity and/or the bank associated with the attributable account.
  • an XML file is generated 455, and transmitted to the bank 460.
  • the XML file may include instructions for the bank to take certain actions, e.g., execute an ACH.
  • the XML file may be made according to the bank's standard or specification, or a national/group/consortium specification, e.g., Open Financial Exchange (OFX) XML Schema, Interactive Financial Exchange (IFX), and the like.
  • OFX Open Financial Exchange
  • IFX Interactive Financial Exchange
  • one hurdle faced by charitable organizations and for-profit organizations when such organizations distribute funds is the diversion of monetary funds and resources from reaching their intended targets/recipients.
  • the diversion of funds and/or resources may be as a result of many factors including, for example, corruption, incompetence, and so forth.
  • problems are not limited to charitable and commercial interests but may also be faced by private individuals.
  • parents often give their children money for specific purposes (e.g., education, athletic gear, food, etc.).
  • children upon receiving funds from their parents, use the money for other purposes (e.g., drugs, movies, clothes, etc.). This type of problem can also arise in trust/beneficiary situations where a beneficiary spends money intended for use in education for drugs.
  • systems and methods are included that allow for tracking and/or tracing of funds, e.g., attributable funds, e.g., digital currency, to and from various entities, e.g., so that one may determine how, what, who, and/or when one or more units of attributable funds (e.g., digital currency) are spent and or used.
  • funds e.g., attributable funds, e.g., digital currency
  • a source entity e.g., a charity, a business organization, a parent, a citizen investor, etc.
  • the funds e.g., attributable funds, e.g., digital currency
  • this may be accomplished by employing a digital currency that has memory, either through storage of the digital currency itself or through transmissions of the digital currency within a framework, e.g., the Daybreak architecture.
  • the digital currency either separately or within the architecture, may record, among other things, who, when, how, and/or upon what the digital currency was used, e.g., for the exchange of goods and/or services.
  • the systems and methods may be implemented using one or more network devices (e.g., one or more servers, workstations, mass storage, etc.).
  • the systems and methods may be implemented as one or more electronic payment systems, e.g., which may be linked, e.g., through the Daybreak architecture.
  • the Daybreak architecture in one or more embodiments, may be implemented using dedicated circuitry such as an ASIC, or in programmable circuitry (e.g., one or more processors, FPGAs, etc.) executing machine readable instructions (e.g., software).
  • a computationally-implemented method implemented by a network computer system may include receiving a request, e.g., at a device, e.g., accepting input, that regards an attributable account, e.g., to reassign one or more units of a digital currency, e.g., attributable funds, from a first pseudo-identity (e.g., a representation and/or an account or other structure associated with an entity within the Daybreak architecture).
  • a first pseudo-identity e.g., a representation and/or an account or other structure associated with an entity within the Daybreak architecture.
  • the request may be a request for transaction data indicating a first transmission of particular funds (e.g., units of digital currency) from a first downstream entity to a second downstream entity (e.g., a first entity, or a first pseudo-identity of a first entity).
  • the request may include a further request for second transaction data indicating a second transmission of particular funds (e.g., units of digital currency) from the second downstream entity (e.g., a first entity, or a first pseudo-identity of a first entity), to the third downstream entity (e.g., the second entity or the second pseudo-identity of the second entity.
  • Fig. 5 A shows processor 251, according to various embodiments.
  • an at least one input acceptance machine having state set at least in part by switch-state logic may be specified to establish at least one input acceptance machine state 502, which may be implemented as at least one input acceptance machine state defined by at least one machine state of at least one first-party-associated device triggered by detection of at least one machine-state pecuniary flag vector 502.
  • an at least one input acceptance machine 252 may be specified to establish at least one input acceptance machine state defined by at least one machine state of at least one first-party-associated device triggered by detection of at least one machine-state pecuniary flag vector 502 for at least one of an electrical/magnetic/physical storage of at least one original machine state associated with a command directed to an engineering approximation of an attributable account that contains attributable funds and that is configured to interact with one or more financial entity machine states, wherein said engineering approximation of said attributable account is at least partly based on an engineering approximation of a distribution rule set that specifies one or more conditions associated with said attributable funds of said attributable account 504.
  • At least one input acceptance machine state e.g., a machine state of a cell phone device that is multiple transistors ordered on a Qualcomm mobile chip
  • at least one machine state of at least one first-party-associated device e.g., a cellular telephone in the hands of a philanthropist/user
  • at least one machine-state pecuniary flag vector e.g., an engineering approximation/electronic representation of the human experience that the user has inputted a command to the device to perform some action related to the attributable account, e.g., display some detail, view the status, update the distribution rule set, etc.
  • the distribution rule set may be changed by the user, alone or in concert with other entities, depending on the needs of the user, and on other factors (e.g., the use of the funds in the attributable account, the conditions in the area to which the attributable funds are to be applied).
  • processor 251 may include at least one input acceptance machine state defined by at least one machine state of at least one first- party-associated device triggered by detection of at least one machine-state pecuniary flag vector 502.
  • Fig. 5A shows that, in an embodiment, an at least one input acceptance machine having state set at least in part by switch-state logic, may be specified to establish at least one input acceptance machine state 502, which may be at least one input acceptance machine state defined by at least one machine state of at least one first-party- associated device triggered by detection of at least one machine-state pecuniary flag vector.
  • At least one input acceptance machine state defined by at least one machine state of at least one first-party-associated device triggered by detection of at least one machine-state pecuniary flag vector 502 may include at least one of at least one first-party- associated device machine state (e.g., a state indicating that data has been stored at a particular location) that includes at least one accepted command (e.g., "show me how many transactions have been denied because they violated a specific portion of the distribution rule set") directed to the engineering approximation of the attributable account (e.g., the engineering approximation on the device 220 that corresponds to the attributable account details associated with the daybreak architecture 3 100, e.g., which in an embodiment may be received at least in part from the daybreak architecture).
  • at least one first-party- associated device machine state e.g., a state indicating that data has been stored at a particular location
  • at least one accepted command e.g., "show me how many transactions have been denied because they violated a
  • daybreak architecture 3100 may supply information about the account that allows formation of, e.g., the engineering approximation of an attributable account.
  • processor 251 may include at least one input acceptance machine 252.
  • at least one input acceptance machine 252 may be specified to establish at least one input acceptance machine state defined by at least one machine state of at least one first-party-associated device triggered by detection of at least one machine-state pecuniary flag vector 502 for at least one of an electrical/magnetic/physical storage of at least one original machine state associated with a command directed to an engineering approximation of an attributable account that contains attributable funds and that is configured to interact with one or more financial entity machine states, wherein said engineering approximation of said attributable account is at least partly based on an engineering approximation of a distribution rule set that specifies one or more conditions associated with said attributable funds of said attributable account 504.
  • processor 251 may include an engineering approximation of an attributable account 259.
  • an engineering approximation of the attributable account 259 may include 257.
  • the engineering approximation of an attributable account 259 may include an attributable account definition machine state defined at least partly based on an engineering approximation of the distribution rule set that specifies one or more conditions (e.g., one or a set of machine states that specifies the distribution rule set, e.g., "transactions must be under 100,000 dollars," or “transactions may only be conducted with trusted parties,” or “transactions may not be carried out on holiday weekends,” or "the specific known bad actors may not be included as a recipient of funds in any transactions" associated with said attributable funds (e.g., the funds for which the distribution rule set is implemented).
  • the engineering approximation of an attributable account 259 may include.
  • engineering approximation of an attributable account 259 may include an attributable account adjustment machine state defined at least partly based on an engineering approximation of an adjustment (e.g., a withdrawal or a deposit) to be applied to the attributable funds (e.g., the funds that are tracked in the project daybreak architecture 3 100) of the attributable account (e.g., account 3030).
  • Fig. 5C shows one or more implementations of the at least one input acceptance machine 252.
  • at least one input acceptance machine 252 may include at least one input acceptance machine having state set at least in part by switch-state logic 535.
  • the at least one input acceptance machine having state set at least in part by switch-state logic 535 may include an input-processing-and- acceptance-circuit 537.
  • the input-processing-and-acceptance-circuit 537 as shown in Fig. 5C, may be configured to transition to at last one voltage which an integrated circuit data sheet equates to LOGIC TRUE when the conditions shown with dotted lines in Fig.
  • Fig. 5C shows implementations of circuits that are part of machines that are part of the processor 251
  • Fig. 5C also shows the conditions that allow a particular circuit to evaluate to logic-true, which allows processing, e.g., the creation of other circuits within processor 251, to continue.
  • Fig. 5D shows one or more implementations of the at least one input acceptance machine state 502 according to various embodiments.
  • the at least one input acceptance machine state defined by at least one machine state of at least one first-party-associated device triggered by detection of at least one machine-state pecuniary flag vector 502 may be implemented at least in part as a switched circuit having one or more switched states set at least in part by switch-state logic of the at least one first-party-associated device and triggered by detection of the at least one machine-state pecuniary flag vector 530.
  • the at least one input acceptance machine state defined by at least one machine state of at least one first-party-associated device triggered by detection of at least one machine-state pecuniary flag vector 502 may be implemented at least in part as a switched circuit (e.g., a circuit that uses one or more hardware elements, e.g., transistors, to implement so-called "switches," which in an embodiment, are binary representations that can be chained together to represent complex expressions) having one or more switched states (e.g., a state of one or more hardware elements based on the binary states of many switches, e.g., which may be implemented as transistors on a computer chip) set at last in part by switch state logic (e.g., logic that specifies how the transistors are to act, with simple logic building blocks to form complex logical chains, e.g., which may be so vast as to be beyond simple human comprehension) specified to order as the machine state of at least one first-party-associated device (e.g., a wearable computer,
  • the switched circuit having one or more switched states set at least in part by switch-state logic of the at least one first- party-associated device and triggered by detection of the at least one machine-state pecuniary flag vector 530 may be implemented as a transistorized circuit having one or more transistor states set at least in part by special purpose circuitry of the at least one first- party-associated device and triggered by detection of the at least one machine-state pecuniary flag vector 532.
  • the switched circuit having one or more switched states set at least in part by switch-state logic of the at least one first-party-associated device and triggered by detection of the at least one machine-state pecuniary flag vector 530 may be implemented as the transistorized circuit having one or more transistor states set at least in part by special purpose circuitry of the at least one first-party-associated device and triggered by detection of the at least one machine-state pecuniary flag vector that is a machine representation of a change in a real-world state (e.g., money has been withdrawn, offboarded, or moved around within the daybreak architecture 3100, or a status of one of the rules of the distribution rule set has changed) of the attributable account (e.g., an account established by a non-philanthropist that is a construction contractor) 532.
  • a real-world state e.g., money has been withdrawn, offboarded, or moved around within the daybreak architecture 3100, or a status of one of the rules of the distribution rule set
  • the transistorized circuit having one or more transistor states set at least in part by special purpose circuitry of the at least one first-party-associated device and triggered by detection of the at least one machine-state pecuniary flag vector 532 may be implemented as a transistorized circuit having one or more transistor states set at least in part by special purpose logical circuitry specified at least in part by at least one computer program compatible with at least one operating system, the at least one computer program at least partially operably linked to the at least one first-party- associated device and triggered by detection of the at least one machine- state pecuniary flag vector 534.
  • the transistorized circuit having one or more transistor states set at least in part by special purpose circuitry of the at least one first-party- associated device and triggered by detection of the at least one machine-state pecuniary flag vector 532 may be implemented as a transistorized circuit having one or more transistor states set at least in part by special purpose logical circuitry logic specified at least in part by at least one computer program (e.g., an account management computer program, e.g., a standalone application, or an add-in to an existing management program, e.g., QuickBooks) compatible with at least one operating system (e.g., Windows, Apple iOS, Google Android, Linux, etc.), the at least one computer program at least partially operably linked (e.g., the computer program receives data and/or commands and/or configuration and/or user data and/or user profiles and/or instructions) to the at least one first-party-associated device and triggered by detection of the at least one machine-state pecuniary flag vector (e.g., a machine representation
  • a machine representation
  • Fig. 5E shows one or more implementations of the at least one input acceptance machine 252 and the at least one input acceptance machine state defined by at least one machine state of at least one first-party- associated device triggered by detection of at least one machine-state pecuniary flag vector 502 according to various embodiments.
  • transistorized circuit 534 may be implemented as a transistorized circuit having one or more transistor states set at least in part by special purpose logical circuitry specified at least in part by at least one computer program compatible with at least one cloud-based or cloud-affiliated operating system 540.
  • transistorized circuit 540 may be implemented as a transistorized circuit having one or more transistor states set at least in part by special purpose logical circuitry specified at least in part by at least one computer program compatible with at least one cloud-based or cloud-affiliated operating system (e.g., (e.g., Microsoft Azure, VMware vCloud, Amazon Cloud EC2, Google App Engine, etc.).
  • cloud-based or cloud-affiliated operating system e.g., (e.g., Microsoft Azure, VMware vCloud, Amazon Cloud EC2, Google App Engine, etc.).
  • Fig. 5E shows one or more implementations of the at least one input acceptance machine 252 and the at least one input acceptance machine state defined by at least one machine state of at least one first-party- associated device triggered by detection of at least one machine-state pecuniary flag vector 502 according to various embodiments.
  • transistorized circuit 534 may be implemented as a transistorized circuit having one or more transistor states set at least in part by special purpose logical circuitry specified at least in part by at least one computer program compatible with at least one desktop operating system 542.
  • transistorized circuit having one or more transistor states set at least in part by special purpose logical circuitry specified at least in part by at least one computer program compatible with at least one desktop operating system 542 may be implemented as transistorized circuit having one or more transistor states set at least in part by special purpose logical circuitry specified at least in part by at least one computer program compatible with at least one desktop operating system (e.g., Microsoft Windows, Linux, Apple OSX, Google ChromeOS, etc.).
  • Microsoft Windows, Linux, Apple OSX, Google ChromeOS, etc. may be implemented as transistorized circuit having one or more transistor states set at least in part by special purpose logical circuitry specified at least in part by at least one computer program compatible with at least one desktop operating system (e.g., Microsoft Windows, Linux, Apple OSX, Google ChromeOS, etc.).
  • transistorized circuit 534 may be implemented as transistorized circuit having one or more transistor states set at least in part by special purpose logical circuitry specified at least in part by at least one computer program compatible with at least one mobile operating system 544.
  • transistorized circuit having one or more transistor states set at least in part by special purpose logical circuitry specified at least in part by at least one computer program compatible with at least one mobile operating system 544 may be implemented as transistorized circuit having one or more transistor states set at least in part by special purpose logical circuitry specified at least in part by at least one computer program compatible with at least one mobile operating system (e.g., Apple iOS, Google Android, Windows Phone 10, Palm OS).
  • transistorized circuit 534 may be implemented as transistorized circuit having one or more transistor states set at least in part by special purpose logical circuitry specified at least in part by at least one computer program compatible with at least one mainframe and/or server operating system 546.
  • transistorized circuit having one or more transistor states set at least in part by special purpose logical circuitry specified at least in part by at least one computer program compatible with at least one mainframe and/or server operating system 546 may be implemented as a transistorized circuit having one or more transistor states set at least in part by special purpose logical circuitry specified at least in part by at least one computer program compatible with at least one mainframe and/or server operating system (e.g., operating systems used by mainframes of IBM, Hitachi, Hewlett-Packard, Fujitsu, Siemens, Group Boulle, NEC, IBM's z/OS and Parallel Sysplex, or Unisys' XPCL.).
  • mainframe and/or server operating system e.g., operating systems used by mainframes of IBM, Hitachi, Hewlett-Packard, Fujitsu, Siemens, Group Boulle, NEC, IBM's z/OS and Parallel Sysplex, or Unisys' XPCL.
  • Fig. 5F shows various embodiments of at least one input acceptance machine state 502 including transistorized circuit 534, according to embodiments.
  • transistorized circuit 534 may be implemented as transistorized circuit having one or more transistor states set at least in part by special purpose logical circuitry specified at least in part by at least one computer program compatible with at least one virtual machine 548.
  • transistorized circuit having one or more transistor states set at least in part by special purpose logical circuitry specified at least in part by at least one computer program compatible with at least one virtual machine 548 may be implemented as transistorized circuit having one or more transistor states set at least in part by special purpose logical circuitry specified at least in part by at least one computer program compatible with at least one virtual machine (e.g., Java Virtual Machine, VMware, Google Dalvik Machine, Windows Hyper- V).
  • virtual machine e.g., Java Virtual Machine, VMware, Google Dalvik Machine, Windows Hyper- V.
  • transistorized circuit 534 may be implemented as transistorized circuit having one or more transistor states set at least in part by special purpose logical circuitry specified at least in part by at least one computer program compatible with at least one virtualization manager 550.
  • transistorized circuit having one or more transistor states set at least in part by special purpose logical circuitry specified at least in part by at least one computer program compatible with at least one virtualization manager 550 may be implemented as transistorized circuit having one or more transistor states set at least in part by special purpose logical circuitry specified at least in part by at least one computer program compatible with at least one virtualization manager (e.g., Microsoft Hyper- V, Citrix Xen, etc.).
  • transistorized circuit 534 may be implemented as transistorized circuit having one or more transistor states set at least in part by special purpose logical circuitry specified at least in part by at least one computer program supplied by the particular architecture 552.
  • transistorized circuit having one or more transistor states set at least in part by special purpose logical circuitry specified at least in part by at least one computer program supplied by the particular architecture 552 may be implemented as transistorized circuit having one or more transistor states set at least in part by special purpose logical circuitry specified at least in part by at least one computer program supplied by the particular architecture (e.g., the Daybreak architecture may have an application associated with accessing the Daybreak architecture that may be loaded on various devices, e.g., phones, tablets, computers).
  • Fig. 5G shows various implementations of switched circuit having one or more switched states set at least in part by switch-state logic of the at least one first-party-associated device and triggered by detection of the at least one machine- state pecuniary flag vector 530.
  • switched circuit having one or more switched states set at least in part by switch-state logic of the at least one first-party- associated device and triggered by detection of the at least one machine-state pecuniary flag vector 530 may include transistorized circuit having one or more transistor states set at least in part by special purpose logical circuitry specified at least in part by at least one computer program licensed, purchased, and/or leased from a second party independent from the first party associated with the first-party-associated device 560.
  • transistorized circuit 560 may include a transistorized circuit having one or more transistor states set at least in part by special purpose logical circuitry specified at least in part by at least one computer program licensed, purchased, and/or leased from a second party (e.g., an operating system manufacturer, an application manufacturer, etc.) independent from the first party associated with the first-party-associated device (e.g., an Apple iPhone).
  • a second party e.g., an operating system manufacturer, an application manufacturer, etc.
  • transistorized circuit 560 may include transistorized circuit having one or more transistor states set at least in part by special purpose logical circuitry specified at least in part by at least one of browser- computer- program licensed, purchased, and/or leased from a second-party independent from the first- party 562.
  • transistorized circuit 562 may be implemented as a transistorized circuit having one or more transistor states set at least in part by special purpose logical circuitry specified at least in part by at least one of browser- computer-program (e.g., Mozilla Firefox, Windows Internet Explorer, Apple Safari, Google Chrome, Opera) licensed, purchased, and/or leased from a second-party independent from the first-party.
  • browser- computer-program e.g., Mozilla Firefox, Windows Internet Explorer, Apple Safari, Google Chrome, Opera
  • transistorized circuit 562 may include transistorized circuit having one or more transistor states set at least in part by special purpose logical circuitry specified at least in part by at least one of Google Chrome, Internet Explorer, Mozilla Firefox, and/or Apple Safari licensed, purchased, and/or leased from a second-party independent from the first-party 564.
  • transistorized circuit 564 may be implemented as a transistorized circuit having one or more transistor states set at least in part by special purpose logical circuitry specified at least in part by at least one of Google Chrome, Internet Explorer, Mozilla Firefox, and/or Apple Safari licensed, purchased, and/or leased from a second-party independent from the first-party.
  • transistorized circuit 560 may be include transistorized circuit having one or more transistor states set at least in part by special purpose logical circuitry specified at least in part by at least one of work- productivity-suite- program licensed, purchased, and/or leased from a second-party independent from the first- party 566.
  • transistorized circuit 566 may be implemented as transistorized circuit having one or more transistor states set at least in part by special purpose logical circuitry specified at least in part by at least one of a work- productivity-suite-program (e.g., OpenOffice, Apple iWork, Corel WordPerfect, Adobe Photoshop) licensed, purchased, and/or leased from a second-party independent from the first- party (e.g., the party associated with the device).
  • a work- productivity-suite-program e.g., OpenOffice, Apple iWork, Corel WordPerfect, Adobe Photoshop
  • transistorized circuit 566 may include transistorized circuit having one or more transistor states set at least in part by special purpose logical circuitry specified at least in part by at least one of Google Apps, Microsoft Office, and/or Apple iWork licensed, purchased, and/or leased from a second-party independent from the first-party 568.
  • transistorized circuit 568 may be implemented as transistorized circuit having one or more transistor states set at least in part by special purpose logical circuitry specified at least in part by at least one of Google Apps, Microsoft Office, and/or Apple iWork licensed, purchased, and/or leased from a second-party independent from the first-party.
  • transistorized circuit 560 may be include transistorized circuit having one or more transistor states set at least in part by special purpose logical circuitry specified at least in part by at least one of a spreadsheet computer program licensed, purchased, and/or leased from a second-party independent from the first- party 570.
  • transistorized circuit 570 may be implemented as transistorized circuit having one or more transistor states set at least in part by special purpose logical circuitry specified at least in part by at least one of a spreadsheet (e.g., Lotus 1-2-3, OpenOffice, Google Docs, Gnumeric, KSpread, LibreOffice Calc) computer program licensed, purchased, and/or leased from a second-party independent from the first- party.
  • a spreadsheet e.g., Lotus 1-2-3, OpenOffice, Google Docs, Gnumeric, KSpread, LibreOffice Calc
  • transistorized circuit 570 may include transistorized circuit having one or more transistor states set at least in part by special purpose logical circuitry specified at least in part by at least one of Microsoft Excel, Intuit QuickBooks/Quicken, and/or Apple Numbers, licensed, purchased, and/or leased from a second-party independent from the first-party 572.
  • transistorized circuit 572 may be implemented as a ransistorized circuit having one or more transistor states set at least in part by special purpose logical circuitry specified at least in part by at least one of Microsoft Excel, Intuit QuickBooks/Quicken, and/or Apple Numbers, licensed, purchased, and/or leased from a second-party independent from the first-party
  • transistorized circuit 560 may include transistorized circuit having one or more transistor states set at least in part by special purpose logical circuitry specified at least in part by at least one of a social networking computer program licensed, purchased, and/or leased from a second-party independent from the first-party 574.
  • transistorized circuit 574 may, in an exemplary embodiment, be implemented as transistorized circuit having one or more transistor states set at least in part by special purpose logical circuitry specified at least in part by at least one of a social networking computer program (e.g., Facebook, MySpace, Instagram, Twitter, Foursquare, Bumble, Tinder, SnapChat) licensed, purchased, and/or leased from a second-party independent from the first-party
  • a social networking computer program e.g., Facebook, MySpace, Instagram, Twitter, Foursquare, Bumble, Tinder, SnapChat
  • transistorized circuit 574 may include transistorized circuit having one or more transistor states set at least in part by special purpose logical circuitry specified at least in part by at least one of messaging/photo-mobile-operating-system-compatible-computer-program purchased, and/or leased from a second-party independent from the first-party 576.
  • transistorized circuit 576 may be implemented as transistorized circuit having one or more transistor states set at least in part by special purpose logical circuitry specified at least in part by at least one of messaging/photo-mobile-operating-system-compatible-computer- program (e.g., WhatsApp, SnapChat, Instagram, Twitter) purchased, and/or leased from a second-party independent from the first-party.
  • messaging/photo-mobile-operating-system-compatible-computer- program e.g., WhatsApp, SnapChat, Instagram, Twitter
  • transistorized circuit 576 may include transistorized circuit having one or more transistor states set at least in part by special purpose logical circuitry specified at least in part by at least one of Signal, WhatsApp, SnapChat, Instagram, gChat, and Instant Messenger 578.
  • transistorized circuit 576 may be implemented as transistorized circuit having one or more transistor states set at least in part by special purpose logical circuitry specified at least in part by at least one of Signal, WhatsApp, SnapChat, Instagram, gChat, and Instant Messenger.
  • transistorized circuit 574 may include transistorized circuit having one or more transistor states set at least in part by special purpose logical circuitry specified at least in part by a real-time social-networking integrated computer-program purchased, and/or leased from a second-party independent from the first- party 580.
  • transistorized circuit 580 may be implemented as a transistorized circuit having one or more transistor states set at least in part by special purpose logical circuitry specified at least in part by a real-time social-networking (e.g., YikYak, SnapChat, Kik, Burn Note) integrated computer-program purchased, and/or leased from a second-party independent from the first-party.
  • a real-time social-networking e.g., YikYak, SnapChat, Kik, Burn Note
  • transistorized circuit 574 may include transistorized circuit having one or more transistor states set at least in part by special purpose logical circuitry specified at least in part by a social-microblogging integrated computer-program purchased, and/or leased from a second-party independent from the first- party 582.
  • transistorized circuit 582 may be implemented as transistorized circuit having one or more transistor states set at least in part by special purpose logical circuitry specified at least in part by a social-microblogging (e.g., Twitter, Instagram) integrated computer-program purchased, and/or leased from a second-party independent from the first-party.
  • a social-microblogging e.g., Twitter, Instagram
  • transistorized circuit 560 may include transistorized circuit having one or more transistor states set at least in part by special purpose logical circuitry specified at least in part by at least one of a program configured to communicate with the particular architecture that is independent from the first party 584.
  • transistorized circuit 560 may be implemented as a transistorized circuit having one or more transistor states set at least in part by special purpose logical circuitry specified at least in part by at least one of a program configured to communicate with the particular architecture (e.g., the daybreak architecture, e.g., as shown in Figs. 2E-2I) that is independent from the first party (e.g., the user associated with the device).
  • the particular architecture e.g., the daybreak architecture, e.g., as shown in Figs. 2E-2I
  • transistorized circuit 584 may include transistorized circuit having one or more transistor states set at least in part by special purpose logical circuitry specified at least in part by at least one of a program configured to communicate with the particular architecture that is independent from the first party through sending configuration signals to the engineering approximation of the attributable account 586.
  • transistorized circuit 586 may be implemented as a transistorized circuit having one or more transistor states set at least in part by special purpose logical circuitry specified at least in part by at least one of a program configured to communicate with the particular architecture (e.g., the Daybreak architecture) that is independent from the first party through sending configuration signals (e.g., signals that change a state of the various accounts associated with the Daybreak architecture, e.g., signals to move funds from one account to another, to audit compliance with the rule set architecture, to provide a transaction history, etc.) to the engineering approximation of the attributable account (e.g., the account associated with the user that is operating the first party device).
  • configuration signals e.g., signals that change a state of the various accounts associated with the Daybreak architecture, e.g., signals to move funds from one account to another, to audit compliance with the rule set architecture, to provide a transaction history, etc.
  • the engineering approximation of the attributable account e.g., the account associated with the user that is
  • transistorized circuit 584 may include transistorized circuit having one or more transistor states set at least in part by special purpose logical circuitry specified at least in part by special purpose logical circuitry configured by machine instructions received from the machine configured to communicate with the particular architecture that is independent from the first party 588.
  • transistorized circuit 588 may be implemented as a transistorized circuit having one or more transistor states set at least in part by special purpose logical circuitry specified at least in part by at least one of a program configured to communicate with the particular architecture (e.g., the Daybreak architecture) that is independent from the first party through sending machine instructions (e.g., signals that change a state of the various accounts associated with the Daybreak architecture, e.g., signals to move funds from one account to another, to audit compliance with the rule set architecture, to provide a transaction history, etc.) received from the machine (e.g., the circuitry inside the processor that is specified by the program running on the first party device) that is configured to communicate with the particular architecture (e.g., the Daybreak architecture), to the engineering approximation of the attributable account (e.g., the account associated with the user that is operating the first party device).
  • machine instructions e.g., signals that change a state of the various accounts associated with the Daybreak architecture, e.g., signals to move funds from one account
  • Fig. 6A shows processor 251, and at least one input acceptance machine 252, according to various embodiments.
  • Fig. 6 shows that, in an embodiment, at least one input acceptance machine 252 may be specified to establish at least one input acceptance machine state defined by at least one machine state of at least one first-party-associated device triggered by detection of at least one machine-state pecuniary flag vector 502.
  • the input acceptance machine state 502 may be triggered by detection of at least one machine-state pecuniary flag vector for at least one of a an electrical/magnetic/physical storage of at least one original machine state associated with a command directed to an engineering approximation of an attributable account that contains attributable funds and that is configured to interact with one or more financial entity machine states, wherein said engineering approximation of said attributable account is at least partly based on an engineering approximation of a distribution rule set that specifies one or more conditions associated with said attributable funds of said attributable account 605, as shown in Fig. 6A.
  • electrical/magnetic/physical storage of at least one original machine state 605 may be associated with a command 501 that is directed to an account 3030 within the particular architecture, e.g., the Daybreak Architecture, e.g., as shown in Fig. 6A.
  • a command 501 that is directed to an account 3030 within the particular architecture, e.g., the Daybreak Architecture, e.g., as shown in Fig. 6A.
  • Specific examples of commands will be discussed in more detail herein with reference to Figs. 6B-6F.
  • electrical/magnetic/physical storage of at least one original machine state 605 may, in various embodiments, include a switched circuit having one or more switched states set at least in part by switch state logic specified to process the command directed to the engineering approximation of the attributable account that contains attributable funds and that is configured to interact with one or more financial entity machine states 610.
  • switched circuit 610 may be implemented as a switched circuit having one or more switched states set at least in part by switch state logic specified to process the command directed to the engineering approximation of the attributable account that contains attributable funds and that is configured to interact with one or more financial entity machine states (e.g., machine states that represent accounts of entities, e.g., financial entities, e.g., which may have a value, e.g., the value specified by a property of the daybreak architecture account).
  • financial entity machine states e.g., machine states that represent accounts of entities, e.g., financial entities, e.g., which may have a value, e.g., the value specified by a property of the daybreak architecture account.
  • switched circuit 610 may be implemented as transistorized circuit having one or more transistor states set at least in part by special purpose logical circuitry that represents the command directed to the engineering approximation of the attributable account that contains attributable funds and that is configured to interact with one or more financial entity machine states 612.
  • transistorized circuit 612 may be implemented as transistorized circuit having one or more transistor states set at least in part by special purpose logical circuitry that represents the command directed to the engineering approximation of the attributable account that contains attributable funds and that is configured to interact with one or more financial entity machine states (e.g., account representations within the Daybreak architecture).
  • transistorized circuit 612 may be implemented as transistorized circuit having one or more transistor states set at least in part by special purpose logical circuitry specified at least in part by an application 614.
  • transistorized circuit having one or more transistor states set at least in part by special purpose logical circuitry specified at least in part by an application 614 may be configured to process at least one command directed to the engineering approximation of the attributable account that contains attributable funds and that is configured to interact with one or more financial entity machine states 616.
  • a command directed to the engineering approximation of the attributable account that contains attributable funds and that is configured to interact with one or more financial entity machine states 616 may be implemented in various formats.
  • command directed to the engineering approximation of the attributable account that contains attributable funds and that is configured to interact with one or more financial entity machine states 616 may include a request for configuration of presentation hardware to present a transaction history of the attributable account that contains the attributable funds and that is configured to interact with one or more financial entity machine states 618.
  • the request for configuration of presentation hardware to present a transaction history of the attributable account that contains the attributable funds and that is configured to interact with one or more financial entity machine states 618 may include a request for configuration of presentation hardware that to present a list of the last five transactions associated with the attributable account that contains the attributable funds and that is configured to interact with one or more financial entity machine states 620.
  • request for configuration of presentation hardware 620 may be implemented as a request for configuration of presentation hardware that to present a list of the last five transactions associated with the attributable account that contains the attributable funds and that is configured to interact with one or more financial entity machine states.
  • request for configuration of presentation hardware to present a transaction history of the attributable account that contains the attributable funds and that is configured to interact with one or more financial entity machine states 618 may include a request for configuration presentation hardware to present a list of the last five transactions associated with the attributable account that took place within the particular architecture that manages the attributable funds and that is configured to interact with one or more financial entity machine states 622.
  • request for configuration of presentation hardware 620 may be implemented as request for configuration of presentation hardware that to present a list of the last five transactions associated with the attributable account that contains the attributable funds and that is configured to interact with one or more financial entity machine states.
  • Fig. 6C shows further implementations of request for configuration of presentation hardware to present a transaction history of the attributable account that contains the attributable funds and that is configured to interact with one or more financial entity machine states 618.
  • request for configuration of presentation hardware 618 may include request for configuration presentation hardware to present a list of the last five transactions associated with the attributable account that took place within the particular architecture that manages the attributable funds and that is configured to interact with one or more financial entity machine states.
  • request for configuration of presentation hardware 624 may be implemented as request for configuration presentation hardware to present a list of the last five transactions associated with the attributable account that took place within the particular architecture that manages the attributable funds and that is configured to interact with one or more financial entity machine states.
  • request for configuration of presentation hardware to present a transaction history of the attributable account that contains the attributable funds and that is configured to interact with one or more financial entity machine states 618 may include request for configuration presentation hardware to present a list of the last five transactions associated with the attributable account that represent offboarding of funds to outside control of the particular architecture that manages the attributable funds and that is configured to interact with one or more financial entity machine states 626.
  • request for configuration of presentation hardware 626 may be implemented as request for configuration presentation hardware to present a list of the last five transactions associated with the attributable account that represent offboarding of funds to outside control of the particular architecture that manages the attributable funds and that is configured to interact with one or more financial entity machine states.
  • request for configuration of presentation hardware to present a transaction history of the attributable account that contains the attributable funds and that is configured to interact with one or more financial entity machine states 618 may include request for configuration presentation hardware to present a distribution map of the attributable funds between the first downstream entity, the second downstream entity, and the third downstream entity 628.
  • request for configuration of presentation hardware to present a transaction history of the attributable account that contains the attributable funds and that is configured to interact with one or more financial entity machine states 618 may include request for configuration presentation hardware to present a real time or near-real time view of the attributable funds within the particular architecture 630.
  • Fig. 6E shows various implementations of electrical/magnetic/physical storage of at least one original machine state associated with a command directed to an engineering approximation of an attributable account that contains attributable funds and that is configured to interact with one or more financial entity machine states 605, according to various embodiments.
  • electrical/magnetic/physical storage of at least one original machine state 605 may include a switched circuit having one or more switched states set at least in part by switch state logic specified to process the command directed to the engineering approximation of the attributable account that contains attributable funds and that is configured to interact with one or more financial entity machine states 650.
  • switched circuit 650 may be implemented such that wherein said engineering approximation of said attributable account is at least partly based on a switched circuit having one or more switched states that define the distribution rule set that specifies one or more conditions associated with said attributable funds of said attributable account 660.
  • switched circuit 660 may be implemented as a switched circuit having one or more switched states that retrieve the distribution rule set from a remote location associated with the particular architecture 662.
  • switched circuit 662 may be implemented as a switched circuit having one or more switched states that retrieve the distribution rule set (e.g., a rule set that allows for implementation of fraud detection using a vendor rating system) from a remote location (e.g., a server farm which implemented the architecture) associated with the particular architecture (e.g., the Daybreak architecture).
  • switched circuit 662 may be implemented as switched circuit having one or more switched states that retrieve one or more rules of the distribution rule set from the remote location associated with the particular architecture 664.
  • switched circuit 664 may be implemented as a switched circuit having one or more switched states that retrieve one or more rules of the distribution rule set (e.g., transactions are forbidden on weekends after 5pm with vendors that have fewer than four letters in their name) from the remote location (e.g., the server bank that stores the Daybreak architecture) associated with the particular architecture.
  • switched circuit 662 may be implemented as a switched circuit having one or more switched states that retrieve one or more rules of the distribution rule set from a server device associated with the particular architecture 666.
  • switched circuit 666 may be implemented as switched circuit having one or more switched states that retrieve one or more rules of the distribution rule set from a server device associated with the particular architecture.
  • switched circuit 660 may be implemented as switched circuit having one or more switched states associated with the distribution rule set that is stored at a remote server device associated with the particular architecture and that specifies one or more conditions associated with said attributable funds of said attributable account 668.
  • switched circuit 668 may be implemented as switched circuit having one or more switched states associated with the distribution rule set that is stored at a remote server device associated with the particular architecture and that specifies one or more conditions associated with said attributable funds of said attributable account (e.g., the funds must be spent with a particular percentage used for medical goods, food, plants, etc.).
  • switched circuit 668 may be implemented as a switched circuit having one or more switched states associated with the distribution rule set that links metadata to the account and to one or more transactions associated with the account 670.
  • switched circuit 670 may be implemented as a switched circuit having one or more switched states associated with the distribution rule set that links metadata (e.g., pictoral evidence of the transaction taking place) to the account and to one or more transactions associated with the account.
  • metadata e.g., pictoral evidence of the transaction taking place
  • Fig. 6F shows various implementations of switched circuit 668, which is itself an implementation switched circuit 660 on which switched circuit 650 includes an engineering approximation of the attributable account based on switched circuit 668.
  • switched circuit 668 may be implemented as switched circuit having one or more switched states associated with the distribution rule set that links identifier metadata to the attributable account and that links transaction information metadata to each transaction associated with the account 672.
  • switched circuit 672 may be implemented as switched circuit having one or more switched states associated with the distribution rule set that links identifier metadata to the attributable account and that links transaction information metadata to each transaction associated with the account.
  • switched circuit 672 may be implemented as a switched circuit having one or more switched states associated with the distribution rule set that links identifier metadata to the attributable account and that links transaction information metadata to each transaction associated with the account, wherein the transaction information includes a receiving party name, a time of transaction, and an underlying bank data for each bank involved in the transaction 674.
  • 6F shows switched circuit having one or more switched states associated with the distribution rule set that links identifier metadata to the attributable account and that links transaction information metadata to each transaction associated with the account, wherein the transaction information includes a receiving party name, a time of transaction, and an underlying bank data for each bank involved in the transaction.
  • Fig. 7 shows various implementations of processor 251, e.g., processor 251 , which may include one or more of said at least one first track data presentation machine 254 and at least one second track data presentation machine 256.
  • processor 251 e.g., processor 251
  • FIG. 7 shows at least one first track data presentation machine 254, which may, in various embodiments, be implemented as an at least one first track data presentation machine having state set at least in part by switch-state logic 702.
  • Fig. 7 shows at least one second track data presentation machine 256, which, in an embodiment, may be implemented as an at least one second track data presentation machine having state set at least in part by switch-state logic 704.
  • At least one first track data presentation machine 254 may be specified to establish at least one first track data presentation machine state of said first-party-associated device, said at least one first track data presentation machine state set to a value 710.
  • the at least one first track data presentation machine state 710 may be set to a value responsive to at least one of tracked first transmission of particular funds within a particular architecture that are part of said attributable funds managed by the particular architecture, from a first downstream entity to a second downstream entity, wherein the tracked first transmission of particular funds is checked for compliance with the distribution rule set by the particular architecture 715.
  • At least one first track data presentation machine at least one first track data presentation machine 254 may be specified to establish at least one first track data presentation machine state of said first-party- associated device, said at least one first track data presentation machine state set to a value 710.
  • at least one first track data presentation machine state 710 may be implemented as first track data presentation switched circuit having one or more switched states set at least in part by switch-state logic specified at least in part by said tracked first transmission of particular funds within a particular architecture that are part of said attributable funds managed by the particular architecture, from a first downstream entity to a second downstream entity 802.
  • first track data presentation switched circuit 802 may be implemented as first track data transistorized circuit having one or more switched states set at least in part by special purpose circuitry specified at least in part by said tracked first transmission of particular funds within a particular architecture that are part of said attributable funds managed by the particular architecture, from a first downstream entity to a second downstream entity 804.
  • first track data transistorized circuit 802 may be implemented as first track data transistorized circuit having one or more switched states set at least in part by special purpose circuitry specified at least in part by said tracked first transmission of particular funds within a particular architecture that are part of said attributable funds managed by the particular architecture, from a first downstream entity to a second downstream entity 804.
  • first track data presentation switched circuit 802 may be implemented as first track data transistorized circuit having one or more switched states set at least in part by special purpose circuitry specified at least in part by one or more received signals translated into machine code that represent said tracked first transmission of particular funds within a particular architecture that are part of said attributable funds managed by the particular architecture, from a first downstream entity to a second downstream entity 806.
  • Fig. 8B shows various implementations of the tracked first transmission of particular funds within the particular architecture 715 as shown in Fig. 7A
  • tracked first transmission of particular funds within the particular architecture 715 may be implemented as tracked first transmission of particular funds within the particular architecture from the first downstream entity to the second downstream entity, wherein the tracked first transmission of particular funds is checked for compliance with the distribution rule set, wherein the distribution rule set specifies a maximum allowable fraud score for the first transmission 820.
  • the tracked first transmission of particular funds within the particular architecture from the first downstream entity e.g., a U.S.
  • the second downstream entity e.g., a construction subcontractor in Egypt
  • the tracked first transmission of particular funds is checked (e.g., verified against) for compliance with the distribution rule set
  • the distribution rule set specifies a maximum allowable fraud score (e.g., a computer- generated score for the transaction that relates various factors (described elsewhere herein, e.g., with respect to Figs. 4A and 4B) for the first transmission (e.g., the transmission of particular funds from the US bank to the construction subcontractor).
  • a maximum allowable fraud score e.g., a computer- generated score for the transaction that relates various factors (described elsewhere herein, e.g., with respect to Figs. 4A and 4B) for the first transmission (e.g., the transmission of particular funds from the US bank to the construction subcontractor).
  • tracked first transmission of particular funds 820 may include tracked first transmission of particular funds within the particular architecture from the first downstream entity to the second downstream entity, wherein the tracked first transmission of particular funds is checked for compliance with the distribution rule set, wherein the distribution rule set specifies a maximum allowable fraud score for the first transmission that is calculated by the particular architecture 822.
  • tracked first transmission of particular funds 822 may include tracked first transmission of particular funds within the particular architecture from the first downstream entity to the second downstream entity, wherein the tracked first transmission of particular funds is checked for compliance with the distribution rule set, wherein the distribution rule set specifies a maximum allowable fraud score for the first transmission that is at least partly based on a phantom vendor determination scheme 824.
  • the tracked first transmission of particular funds within the particular architecture from the first downstream entity to the second downstream entity wherein the tracked first transmission of particular funds is checked for compliance with the distribution rule set, wherein the distribution rule set specifies a maximum allowable fraud score for the first transmission that is at least partly based on a phantom vendor determination scheme, e.g., a scheme in which funds are transferred between "shell" or "phantom” vendors in an attempt to skim or steal money from an account, e.g., the attributable account, and whose presence may be detected using pattern recognition or other machine intelligence amplification techniques by the particular architecture, which also may control onboarding/offboarding of funds.
  • a phantom vendor determination scheme e.g., a scheme in which funds are transferred between "shell" or "phantom” vendors in an attempt to skim or steal money from an account, e.g., the attributable account, and whose presence may be detected using pattern recognition or other machine intelligence amplification techniques by the particular architecture, which also may control onboarding/off
  • tracked first transmission of particular funds 824 may include tracked first transmission of particular funds within the particular architecture from the first downstream entity to the second downstream entity, wherein the phantom vendor determination scheme is at least partly based on one or more characteristics of the first downstream entity and the second downstream entity 826.
  • the tracked first transmission of particular funds within the particular architecture from the first downstream entity to the second downstream entity wherein the tracked first transmission of particular funds is checked for compliance with the distribution rule set, wherein the distribution rule set specifies a maximum allowable fraud score for the first transmission that is at least partly based on a phantom vendor determination scheme, e.g., a scheme in which funds are transferred between "shell" or "phantom” vendors in an attempt to skim or steal money from an account, e.g., the attributable account, and whose presence may be detected using pattern recognition or other machine intelligence amplification techniques by the particular architecture, which also may control onboarding/offboarding of funds, and which may analyze the first downstream entity and the second downstream entity.
  • a phantom vendor determination scheme e.g., a scheme in which funds are transferred between "shell" or "phantom” vendors in an attempt to skim or steal money from an account, e.g., the attributable account, and whose presence may be detected using pattern recognition or other machine intelligence amplification
  • tracked first transmission of particular funds 826 may include tracked first transmission of particular funds within the particular architecture from the first downstream entity to the second downstream entity, wherein the phantom vendor determination scheme is at least partly based on one or more characteristics of the first downstream entity and the second downstream entity, said characteristics including an entity name length, a time in operation of the entity, a number of invoices to a same vendor by the entity 828.
  • the tracked first transmission of particular funds within the particular architecture from the first downstream entity to the second downstream entity wherein the tracked first transmission of particular funds is checked for compliance with the distribution rule set, wherein the distribution rule set specifies a maximum allowable fraud score for the first transmission that is at least partly based on a phantom vendor determination scheme, e.g., a scheme in which funds are transferred between "shell" or "phantom” vendors in an attempt to skim or steal money from an account, e.g., the attributable account, and whose presence may be detected using pattern recognition or other machine intelligence amplification techniques by the particular architecture, which also may control onboarding/offboarding of funds, and which may analyze the first downstream entity and the second downstream entity for such factors as an entity name length, a time in operation of the entity, a number of invoices to a same vendor by the entity.
  • a phantom vendor determination scheme e.g., a scheme in which funds are transferred between "shell" or "phantom” vendors in an attempt to skim or steal money from
  • tracked first transmission of particular funds 822 may include tracked first transmission of particular funds within the particular architecture from the first downstream entity to the second downstream entity, wherein the tracked first transmission of particular funds is checked for compliance with the distribution rule set, wherein the distribution rule set specifies a maximum allowable fraud score for the first transmission that is at least partly based on a vendor reputation score managed by the particular architecture 830.
  • tracked first transmission of particular funds 830 may be a tracked first transmission of particular funds within the particular architecture from the first downstream entity to the second downstream entity, wherein the tracked first transmission of particular funds is checked for compliance with the distribution rule set, wherein the distribution rule set specifies a maximum allowable fraud score for the first transmission that is at least partly based on a vendor reputation score (e.g., a reputation score managed by the architecture, e.g., with input from other vendors that have interacted with that vendor, persons associated with attributable accounts, and objective reports) managed by the particular architecture (e.g., the Daybreak architecture).
  • a vendor reputation score e.g., a reputation score managed by the architecture, e.g., with input from other vendors that have interacted with that vendor, persons associated with attributable accounts, and objective reports
  • the particular architecture e.g., the Daybreak architecture
  • tracked first transmission of particular funds 822 may include tracked first transmission of particular funds within the particular architecture from the first downstream entity to the second downstream entity, wherein the tracked first transmission of particular funds is checked for compliance with the distribution rule set, wherein the distribution rule set specifies a maximum allowable fraud score for the first transmission that is at least partly based on a transaction score managed by the particular architecture 832.
  • tracked first transmission of particular funds 832 may be implemented as tracked first transmission of particular funds within the particular architecture from the first downstream entity to the second downstream entity, wherein the tracked first transmission of particular funds is checked for compliance with the distribution rule set, wherein the distribution rule set specifies a maximum allowable fraud score for the first transmission that is at least partly based on a transaction score managed by the particular architecture.
  • tracked first transmission of particular funds 832 may include tracked first transmission of particular funds within the particular architecture from the first downstream entity to the second downstream entity, wherein the tracked first transmission of particular funds is checked for compliance with the distribution rule set, wherein the distribution rule set specifies a maximum allowable fraud score for the first transmission that is at least partly based on a transaction score that is based on one or more of a transaction time, an involved transaction entity identity, a transaction amount, a transaction location, and a transaction reputation score 834.
  • tracked first transmission of particular funds 834 may be implemented as tracked first transmission of particular funds within the particular architecture from the first downstream entity to the second downstream entity, wherein the tracked first transmission of particular funds is checked for compliance with the distribution rule set, wherein the distribution rule set specifies a maximum allowable fraud score for the first transmission that is at least partly based on a transaction score that is based on one or more of a transaction time, an involved transaction entity identity, a transaction amount, a transaction location, and a transaction reputation score.
  • At least one second track data presentation machine 256 may include at least one second track data presentation machine having state set at least in part by switch-state logic 704.
  • At least one second track data presentation machine 256 may be specified to establish at least one second track data presentation machine state of said first-party-associated device, said at least one second track data presentation machine state set to a value 720.
  • At least one second track data presentation machine state of said first-party-associated device said at least one second track data presentation machine state set to a value 720 may include a second track data presentation switched circuit having one or more switched states set at least in part by switch-state logic specified at least in part by said tracked second transmission of at least a portion of said particular funds within the particular architecture from said second downstream entity to a third downstream entity different than said first downstream entity 910.
  • At least one second track data presentation switched circuit may be implemented as a second track data presentation switched circuit having one or more switched states set at least in part by switch-state logic specified at least in part by said tracked second transmission of at least a portion of said particular funds within the particular architecture from said second downstream entity to a third downstream entity different than said first downstream entity.
  • second track data presentation switched circuit 910 may include second track data transistorized circuit having one or more switched states set at least in part by special purpose circuitry specified at least in part by said tracked second transmission of at least a portion of said particular funds within the particular architecture from said second downstream entity to a third downstream entity different than said first downstream entity 912.
  • a second track data transistorized circuit may be implemented as a second track data transistorized circuit having one or more switched states set at least in part by special purpose circuitry specified at least in part by said tracked second transmission of at least a portion of said particular funds within the particular architecture from said second downstream entity to a third downstream entity different than said first downstream entity.
  • second track data transistorized circuit 912 may include second track data transistorized circuit having one or more switched states set at least in part by special purpose circuitry specified at least in part by one or more received signals translated into machine code that represent said tracked second transmission of at least a portion of said particular funds within the particular architecture from said second downstream entity to a third downstream entity different than said first downstream entity 914.
  • second track data transistorized circuit 912 may include second track data transistorized circuit having one or more switched states set at least in part by special purpose circuitry specified at least in part by one or more received signals translated into machine code that represent said tracked second transmission of at least a portion of said particular funds within the particular architecture from said second downstream entity to a third downstream entity different than said first downstream entity 914.
  • a second track data transistorized circuit may be implemented as a second track data transistorized circuit having one or more switched states set at least in part by part by one or more received signals translated into machine code that represent said tracked second transmission of at least a portion of said particular funds within the particular architecture from said second downstream entity to a third downstream entity different than said first downstream entity.
  • FIG. 14 various operations may be depicted in a box-within-a-box manner. Such depictions may indicate that an operation in an internal box may comprise an optional example embodiment of the operational step illustrated in one or more external boxes. However, it should be understood that internal box operations may be viewed as independent operations separate from any associated external boxes and may be performed in any sequence with respect to all other illustrated operations, or may be performed concurrently. Still further, these operations illustrated in Fig. 14 as well as the other operations to be described herein may be performed by at least one of a machine, an article of manufacture, or a composition of matter.
  • an implementer may opt for a mainly hardware and/or firmware vehicle; alternatively, if flexibility is paramount, the implementer may opt for a mainly software implementation; or, yet again alternatively, the implementer may opt for some combination of hardware, software, and/or firmware.
  • any vehicle to be utilized is a choice dependent upon the context in which the vehicle will be deployed and the specific concerns (e.g., speed, flexibility, or predictability) of the implementer, any of which may vary.
  • Those skilled in the art will recognize that optical aspects of implementations will typically employ optically-oriented hardware, software, and or firmware.
  • Fig. 10 shows an implementation of a first party machine/user machine 220B, similarly to as disclosed with respect to Fig. 2C-2.
  • first party machine 220B may include one or more of electrical/magnetic/physical storage 222, processor 25 IB, and/or other optional machine circuits and components 260.
  • daybreak architecture 3 100 may include a state machine, e.g., 1002, which, in an embodiment, may generate machine instructions 1004.
  • Those program/machine instructions may be incorporated with processor 25 IB of first party machine 220B in order to form various implementations of input acceptance circuit 252B, first transaction data receiving circuit 254B, and second transaction data receiving circuit 256B.
  • Figs. 1 1-13 illustrate exemplary embodiments of the various modules that form portions of processor 25 IB.
  • the modules represent hardware, either that is hard-coded, e.g., as in an application-specific integrated circuit ("ASIC") or that is physically reconfigured through gate activation described by computer instructions, e.g., as in a central processing unit.
  • ASIC application-specific integrated circuit
  • Fig. 1 1 illustrates an exemplary implementation of the input acceptance circuit 252B.
  • the input acceptance circuit 252B may include one or more sub-logic circuits in various alternative implementations and embodiments.
  • Figs. 1 1A-1 1 G which make up part of a unified Fig. 12 as shown in the lower illustration of each sheet of Fig. 12.
  • Fig. 12 illustrates an exemplary implementation of first transaction data receiving circuit 254B.
  • the first transaction data receiving circuit 254B may include one or more sub-logic modules in various alternative implementations and embodiments.
  • Figs. 12A-12H which make up part of a unified Fig. 12 as shown in the lower illustration of each sheet of Fig. 12.
  • Fig. 13 illustrates an exemplary implementation of second transaction data receiving circuit 256B.
  • the second transaction data receiving circuit 256B may include one or more sub-logic modules in various alternative implementations and embodiments, as shown in Figs. 13A-13G, which make up part of a unified Fig. 13 as shown in the lower illustration of each sheet of Fig. 13.
  • FIG. 14 various operations may be depicted in a box-within-a-box manner. Such depictions may indicate that an operation in an internal box may comprise an optional example embodiment of the operational step illustrated in one or more external boxes. However, it should be understood that internal box operations may be viewed as independent operations separate from any associated external boxes and may be performed in any sequence with respect to all other illustrated operations, or may be performed concurrently. Still further, these operations illustrated in Fig. 14 as well as the other operations to be described herein may be performed by at least one of a machine, an article of manufacture, or a composition of matter.
  • an implementer may opt for a mainly hardware and/or firmware vehicle; alternatively, if flexibility is paramount, the implementer may opt for a mainly software implementation; or, yet again alternatively, the implementer may opt for some combination of hardware, software, and/or firmware.
  • any vehicle to be utilized is a choice dependent upon the context in which the vehicle will be deployed and the specific concerns (e.g., speed, flexibility, or predictability) of the implementer, any of which may vary.
  • Those skilled in the art will recognize that optical aspects of implementations will typically employ optically-oriented hardware, software, and or firmware.
  • Fig. 14 shows operation 1000, e.g., an example operation of message processing device 230 operating in an environment 200.
  • operation 1400 may include operation 1402 depicting input acceptance circuit configured to receive input that regards an attributable account that contains attributable funds and that is configured to interface with one or more financial entities, wherein the attributable funds are governed by a distribution rule set.
  • Fig. 10 e.g., Fig.
  • input acceptance circuit 252B accepting (e.g., receiving, retrieving, facilitating the reception of, interacting with an input/output interface) input
  • input could take many forms, e.g., a person interacting with an input/output device, e.g., a keyboard, mouse, touchscreen, haptic interface, virtual reality interface, augmented reality interface, audio interface, body-motion interface, or similar, or in the form of one device sending a request to another device, for example a monitoring device sending a request for a particular image, or in the form of an internal communication in a device (e.g., a subroutine of a device inputs the request to a different portion of the device (which may use the same CPU and/or other components), or any other form) e.g., of a request (e.g., a command, suggestion, or description, which may be narrow or specific, e.g., "add X funds to this account,” or "transfer funds from part,” or "request
  • operation 1400 may include operation 1404 depicting first transaction data receiving circuit configured to receive first transaction data indicating a first transmission of particular funds from a first downstream entity to a second downstream entity, wherein the particular funds are part of the attributable funds.
  • first transaction data indicating a first transmission of particular funds from a first downstream entity to a second downstream entity, wherein the particular funds are part of the attributable funds.
  • Fig. 10 e.g., Fig.
  • first transaction data receiving circuit 254B receiving first transaction data (e.g., data that indicates a request has been made to move funds, either between two Daybreak architecture accounts, or to offboard some funds from the Daybreak architecture account, or any combination thereof) indicating a first transmission of particular funds from a first downstream entity (e.g., a governmental agency that assigns contracts to for-profit companies to do charitable work) to a second downstream entity (e.g., a solar power construction company), wherein the partiucalr frunds are part of the attributable funds.
  • first transaction data e.g., data that indicates a request has been made to move funds, either between two Daybreak architecture accounts, or to offboard some funds from the Daybreak architecture account, or any combination thereof
  • first downstream entity e.g., a governmental agency that assigns contracts to for-profit companies to do charitable work
  • a second downstream entity e.g., a solar power construction company
  • operation 1400 may include operation 1406 depicting second transaction data receiving circuit configured to receive second transaction data indicating a second transmission of the particular funds from the second downstream entity to the third downstream entity.
  • Fig. 10 e.g., Fig. 10 shows second transaction data receiving circuit 256B receiving second transaction data indicatin a second transmission of the particular funds from the second downstream entity (e.g., the solar power construction company) to the third downstream entity (e.g., a local worker who installs the solar panels and has a bank account associated with her phone, e.g., through an app, or through a system such as M-Pesa or the like).
  • the second downstream entity e.g., the solar power construction company
  • the third downstream entity e.g., a local worker who installs the solar panels and has a bank account associated with her phone, e.g., through an app, or through a system such as M-Pesa or the like.
  • Figs. 15A-15F depict various implementations of operation 1402, depicting input acceptance circuit configured to receive input that regards an attributable account that contains attributable funds and that is configured to interface with one or more financial entities, wherein the attributable funds are governed by a distribution rule set according to embodiments.
  • operation 1402 may include operation 1502 depicting presentation input acceptance circuit configured to accept input that regards that regards a request for presentation of a transaction history of the attributable account that contains attributable funds and that is configured to interface with one or more financial entities, wherein the attributable funds are governed by a distribution rule set.
  • Fig. 1 1, e.g., Fig.
  • FIG. 1 1A shows presentation input acceptance circuit configured to accept input that regards that regards a request for presentation of a transaction history of the attributable account that contains attributable funds and that is configured to interface with one or more financial entities, wherein the attributable funds are governed by a distribution rule set 1 102, accepting input (e.g., receiving a vocal order spoken into a microphone).
  • operation 1402 may include operation 1504 depicting an input receiving circuit operably coupled to the input/output interface circuit and that is configured to receive input that regards the attributable account that contains attributable funds and that is configured to interface with one or more financial entities.
  • Fig. 1 1, e.g., Fig. 1 1 A shows input receiving circuit operably coupled to the input/output interface circuit and that is configured to receive input that regards the attributable account that contains attributable funds and that is configured to interface with one or more financial entities 1 104 receiving input that regards the attributable account that contains attributable funds and that is configured to interface with one or more financial entities (e.g., banks, contractors, individuals, governments, NGOs, etc.)
  • financial entities e.g., banks, contractors, individuals, governments, NGOs, etc.
  • operation 1504 may include operation 1506 depicting an input receiving circuit configured to receive input from a user, said input that regards the attributable account that contains attributable funds and that is configured to interface with one or more financial entities.
  • Fig. 1 e.g., Fig.
  • FIG. 1 1 A shows input receiving circuit configured to receiving input from a user, said input that regards the attributable account that contains attributable funds and that is configured to interface with one or more financial entities 1 106 receiving input from a user (e.g., a human, but not necessarily a human, could be a program, an artificial intelligence, an intelligence amplification, a robot, another entity, etc.), said input that regards the attributable account (e.g., an inputted request for an audit) that contains attributable funds and that is configured to interface with one or more financial entities (e.g., a local bank and a non-governmental entity that is a construction company).
  • a user e.g., a human, but not necessarily a human, could be a program, an artificial intelligence, an intelligence amplification, a robot, another entity, etc.
  • said input that regards the attributable account e.g., an inputted request for an audit
  • one or more financial entities e.g., a local bank and a non
  • operation 1504 may include operation 1508 depicting input receiving circuit configured to receive, at the device that is a first party device, said input that regards the attributable account that contains attributable funds and that is configured to interface with one or more financial entities.
  • Fig. 1 1 e.g., Fig.
  • 1 1 A shows input receiving circuit configured to receive, at the device that is a first party device, said input that regards the attributable account that contains attributable funds and that is configured to interface with one or more financial entities 1 108 receiving input at a first party device (e.g., an Apple-branded iPhone), said input that regards the attributable account (e.g., an inputted request to view the last five transactions and a detailed analysis of how the distribution rule set was applied to the last five transactions) and that is configured to interface with one or more financial entities (e.g., a remote foreign bank and a large multinational bank).
  • a first party device e.g., an Apple-branded iPhone
  • operation 1508 may include operation 1510 depicting input receiving circuit configured to receive input at the first party device, said input that regards the attributable account that contains attributable funds and that is configured to interface with one or more financial entities, wherein the first party device is one or more of a smartphone device, mobile device, laptop computer, desktop computer, wearable device, augmented reality device, in-vehicle device, heads up display, and a thin client.
  • the first party device is one or more of a smartphone device, mobile device, laptop computer, desktop computer, wearable device, augmented reality device, in-vehicle device, heads up display, and a thin client.
  • Fig. 1 1, e.g., Fig.
  • 1 1 A shows input receiving circuit configured to receive input at the first party device, said input that regards the attributable account that contains attributable funds and that is configured to interface with one or more financial entities, wherein the first party device is one or more of a smartphone device, mobile device, laptop computer, desktop computer, wearable device, augmented reality device, in-vehicle device, heads up display, and a thin client 1 1 10 receiving input at the first party device, said input that regards the attributable account (e.g., a request to transfer funds to a specific recipient) hat contains attributable funds and that is configured to interface with one or more financial entities, wherein the first party device is one or more of a smartphone device, mobile device, laptop computer, desktop computer, wearable device, augmented reality device, in- vehicle device, heads up display, and a thin client.
  • the first party device is one or more of a smartphone device, mobile device, laptop computer, desktop computer, wearable device, augmented reality device, in- vehicle device, heads up display, and a thin client.
  • operation 1508 may include operation 1512 depicting input receiving circuit configured to receive input from the user at an input/output interface of the first party device, said input that regards the attributable account that contains attributable funds and that is configured to interface with one or more financial entities.
  • Fig. 1 e.g., Fig.
  • 1 1 A shows input receiving circuit configured to receive input from the user at an input/output interface of the first party device, said input that regards the attributable account that contains attributable funds and that is configured to interface with one or more financial entities 1 1 12 receiving input from the user at an input/output interface (e.g., a touchscreen, keyboard, microphone/speaker, display, mouse, pointer, augmented reality display projection, motion detector, other sensor, or any combination thereof) of the first party device, said input that regards the attributable account that contains attributable funds and that is configured to interface with one or more financial entities.
  • an input/output interface e.g., a touchscreen, keyboard, microphone/speaker, display, mouse, pointer, augmented reality display projection, motion detector, other sensor, or any combination thereof
  • operation 1512 may include operation 1514 depicting input receiving circuit configured to receive input from the user at a touchscreen interface of the first party device, said input that regards the attributable account that contains attributable funds and that is configured to interface with one or more financial entities.
  • Fig. 1 e.g., Fig.
  • 1 1 A shows input receiving circuit configured to receive input from the user at a touchscreen interface of the first party device, said input that regards the attributable account that contains attributable funds and that is configured to interface with one or more financial entities 1 1 14 receiving input from the user at a touchscreen interface of the first party device, said input that regards the attributable account that contains attributable funds and that is configured to interface with one or more financial entities (e.g., a medical supply guarantor working in a remote location with questionable access to supplies).
  • financial entities e.g., a medical supply guarantor working in a remote location with questionable access to supplies.
  • operation 1402 may include operation 1516 depicting input acceptance circuit configured to accept a request related to the attributable account that contains the attributable funds and that is configured to interface with one or more financial entities.
  • Fig. 1 e.g., Fig.
  • 1 1B shows input acceptance circuit configured to accept a request related to the attributable account that contains the attributable funds and that is configured to interface with one or more financial entities 1 1 16 accepting a request related to the attributable account (e.g., a request to change one or more parameters of one or more rules of the distribution rule set, e.g., to change the percentage of a transaction that is allowed to be offboarded to the financial institution that is facilitating that transaction) that contains the attributable funds and that is configured to interface with one or more financial entities (e.g., a supermarket located in a third world country).
  • a request related to the attributable account e.g., a request to change one or more parameters of one or more rules of the distribution rule set, e.g., to change the percentage of a transaction that is allowed to be offboarded to the financial institution that is facilitating that transaction
  • one or more financial entities e.g., a supermarket located in a third world country.
  • operation 1402 may include operation 1518 depicting attributable account view request accepting circuit configured to accept a request to view at least a portion of the attributable account that contains the attributable funds and that is configured to interface with one or more financial entities.
  • Fig. 1 1 e.g., Fig.
  • Attributable account view request accepting circuit configured to accept a request to view at least a portion of the attributable account that contains the attributable funds and that is configured to interface with one or more financial entities 1 1 18 accepting a request to view at least a portion of the attributable account (e.g., the portion being transactions from a specific financial entity, e.g., a specific vendor) that contains the attributable funds and that is configured to interface with one or more financial entities (e.g., one or more vendors).
  • a specific financial entity e.g., a specific vendor
  • operation 1518 may include operation 1520 depicting attributable account view request accepting circuit configured to accept the request to view the last ten transactions carried out in the attributable account that contains the attributable funds and that is configured to interface with one or more financial entities.
  • Fig. 1 1 e.g., Fig.
  • Attributable account view request accepting circuit configured to accept the request to view the last ten transactions carried out in the attributable account that contains the attributable funds and that is configured to interface with one or more financial entities 1 120 accepting the request to view the last ten transactions carried out in the attributable account (e.g., two offboardings and eight internal transactions between entities that have accounts within the Daybreak architecture) that contains the attributable funds and that is configured to interface with one or more financial entities.
  • operation 1518 may include operation 1522 depicting attributable account view request accepting circuit configured to accept the request to view the last ten rej ected transactions requested in the attributable account that contains the attributable funds and that is configured to interface with one or more financial entities, wherein the rej ected transactions were rej ected for failure to comply with the distribution rule set.
  • Fig. 1 1 e.g., Fig.
  • Attributable account view request accepting circuit configured to accept the request to view the last ten rej ected transactions requested in the attributable account that contains the attributable funds and that is configured to interface with one or more financial entities, wherein the rej ected transactions were rej ected for failure to comply with the distribution rule set 1 122 accepting the request to view the last ten rej ected transactions requested in the attributable account that contains the attributable funds and that is configured to interface with one or more financial entities, wherein the rej ected transactions were rej ected for failure to comply with the distribution rule set (e.g., the distribution rule set required the vendor that was to receive the funds to be registered as a licensed medical supplies provider, and none of the transacitons featured a transfer of funds to a licensed medical supplies provider).
  • the distribution rule set e.g., the distribution rule set required the vendor that was to receive the funds to be registered as a licensed medical supplies provider, and none of the transacitons featured a transfer of funds to a licensed medical supplies provider.
  • operation 1518 may include operation 1524 depicting attributable account view request accepting circuit configured to accept accepting the request to view an account balance of the attributable account that contains the attributable funds and that is configured to interface with one or more financial entities.
  • Fig. 1 1 e.g., Fig.
  • Attributable account view request accepting circuit configured to accept accepting the request to view an account balance of the attributable account that contains the attributable funds and that is configured to interface with one or more financial entities 1 124 accepting the request to view an account balance of the attributable account (e.g., a virtual balance, e.g., managed within the daybreak architecture, because money is not specifically moved out of the attriubtalbe account (e.g., the real-world representation of the attributable account) until the funds are offboarded outside the control of the Daybreak architecture) and that is configured to interface (e.g., interact with, e.g., communicate with electronically, e.g., transfer data to and/or from, apply a distribution rule set to, and/or transfer funds to and/or from) with one or more financial entities (e.g., one or more entities that have registered with the Daybreak architecture).
  • a virtual balance e.g., managed within the daybreak architecture, because money is not specifically moved out of the attriubtalbe account
  • operation 1518 may include operation 1526 depicting attributable account view request accepting circuit configured to accept the request to view a distribution map of the attributable funds between the first downstream entity, the second downstream entity, and the third downstream entity.
  • operation 1526 depicting attributable account view request accepting circuit configured to accept the request to view a distribution map of the attributable funds between the first downstream entity, the second downstream entity, and the third downstream entity.
  • Fig. 1 1 e.g., Fig.
  • Attributable account view request accepting circuit configured to accept the request to view a distribution map of the attributable funds between the first downstream entity, the second downstream entity, and the third downstream entity 1 126 accepting the request to view the distribution map (e.g., a visualization of various distributions, e.g., a bar chart, pie chart, or any other graphical or sensory representation in any medium, including virtual and augmented reality) of the attributable funds between the first downstream entity (e.g., a governmental agency of a foreign power), the second downstream entity (e.g., a royal family of a country with a symbolic oligarchy), and the third downstream entity (e.g., a government contractor, e.g., Booz Allen or Halliburton).
  • a distribution map of the attributable funds between the first downstream entity, the second downstream entity, and the third downstream entity 1 126 accepting the request to view the distribution map (e.g., a visualization of various distributions, e.g., a bar chart, pie chart, or
  • operation 1518 may include operation 1528 depicting attributable account view request accepting circuit configured to accept the request to view a real-time or near-real-time tracking of the attributable funds between the first downstream entity, the second downstream entity, and the third downstream entity.
  • operation 1528 depicting attributable account view request accepting circuit configured to accept the request to view a real-time or near-real-time tracking of the attributable funds between the first downstream entity, the second downstream entity, and the third downstream entity.
  • Fig. 1 depicting attributable account view request accepting circuit configured to accept the request to view a real-time or near-real-time tracking of the attributable funds between the first downstream entity, the second downstream entity, and the third downstream entity.
  • FIG. 1 1B shows attributable account view request accepting circuit accepting the request to view a real-time or near-real-time tracking of the attributable funds between the first downstream entity, the second downstream entity, and the third downstream entity 1 128 accepting the request to view a real time or near real time (e.g., close enough to real time so that it appears upon loose inspection to be a real-time system) tracking of the attributable funds between the first downstream entity (e.g., a domestic banking institution), the second downstream entity (e.g., a building subcontractor), and the third downstream entity (e.g., a cement mixer rental company).
  • the first downstream entity e.g., a domestic banking institution
  • the second downstream entity e.g., a building subcontractor
  • the third downstream entity e.g., a cement mixer rental company
  • operation 1518 may include operation 1530 depicting attributable account view request accepting circuit configured to accept the request to view a current location of the attributable funds between the first downstream entity, the second downstream entity, and the third downstream entity, within their representations in a particular architecture.
  • Fig. 1 e.g., Fig.
  • FIG. 1 1C shows attributable account view request accepting circuit configured to accept the request to view a current location of the attributable funds between the first downstream entity, the second downstream entity, and the third downstream entity, within their representations in a particular architecture 1 130 accepting the request to view a current location of the attributable funds between the first downstream entity (e.g., a rural hospital), the second downstream entity (e.g., a medical supply provider), and the third downstream entity (e.g., a nurse contracting agency), within their representations (e.g., within the accounts that represent each entity within the Daybreak architecture) in a particular architecture (e.g., Daybreak architecture 3100 or similar).
  • a particular architecture e.g., Daybreak architecture 3100 or similar.
  • operation 1530 may include operation 1532 depicting attributable account view request accepting circuit configured to accept the request to view the current location of the attributable funds between the first downstream entity, the second downstream entity, and the third downstream entity, within their individual account representations within the particular architecture that has an individual account associated with each downstream entity.
  • Fig. 1 e.g., Fig.
  • l lC shows attributable account view request accepting circuit configured to accept the request to view the current location of the attributable funds between the first downstream entity, the second downstream entity, and the third downstream entity, within their individual account representations within the particular architecture that has an individual account associated with each downstream entity 1 132 accepting the request to view the current location of the attributable funds between the first downstream entity (e.g., a fresh food supplier), the second downstream entity (e.g., a commercial farm), and the third downstream entity (e.g., a refrigerated truck driving company), within their individual account representations within the particular architecture that has an individual account asccoiated with each downstream entity.
  • first downstream entity e.g., a fresh food supplier
  • the second downstream entity e.g., a commercial farm
  • the third downstream entity e.g., a refrigerated truck driving company
  • operation 1518 may include operation 1534 depicting attributable account view request accepting circuit configured to accept the request to view at least a partial list of goods and/or services purchased or directed to purchase with the attributable funds by one or more of the first downstream entity, the second downstream entity, and the third downstream entity, and/or one or more agents of the first downstream entity, the second downstream entity, and the third downstream entity.
  • Fig. 1 1 e.g., Fig.
  • FIG. 1 1 C shows attributable account view request accepting circuit configured to accept the request to view at least a partial list of goods and/or services purchased or directed to purchase with the attributable funds by one or more of the first downstream entity, the second downstream entity, and the third downstream entity, and/or one or more agents of the first downstream entity, the second downstream entity, and the third downstream entity 1 134 accepting the request to view at least a partial list of goods and/or services (e.g., medical supplies; housing parts) purchased or directed to purchase with the attributable funds (e.g., the funds are moved around within the Daybreak architecture and then offboarded after compliance with the distribution rule set is confirmed and/or verified) by one or more of the first downstream entity (e.g., a large rural grocery provider), the second downstream entity (e.g., a contract labor union that supplies workers to grocery stores), and the third downstream entity (e.g., a dairy) and/or one or more agents of the first downstream entity, the second downstream entity, and the third downstream entity (e.g.
  • operation 1518 may include operation 1536 depicting attributable account view request accepting circuit configured to accept the request to view at least a partial list of goods and/or services distributed or directed to distribute with the attributable funds by one or more of the first downstream entity, the second downstream entity, and the third downstream entity, and/or one or more agents of the first downstream entity, the second downstream entity, and the third downstream entity.
  • operation 1536 depicting attributable account view request accepting circuit configured to accept the request to view at least a partial list of goods and/or services distributed or directed to distribute with the attributable funds by one or more of the first downstream entity, the second downstream entity, and the third downstream entity, and/or one or more agents of the first downstream entity, the second downstream entity, and the third downstream entity.
  • Fig. 1 1 e.g., Fig.
  • FIG. 1 1 C shows attributable account view request accepting circuit configured to accept the request to view at least a partial list of goods and/or services distributed or directed to distribute with the attributable funds by one or more of the first downstream entity, the second downstream entity, and the third downstream entity, and/or one or more agents of the first downstream entity, the second downstream entity, and the third downstream entity 1 136 accepting the request to view at least a partial list of goods and/or services distributed or directed to distribute with the attributable funds by one or more of the first downstream entity (e.g., a hospital), the second downstream entity (e.g., an Ebola crisis response team), and the third downstream entity (e.g. a respirator distributor), and/or one or more agents of the first downstream entity (e.g., a hospital), the second downstream entity (e.g., an Ebola crisis response team), and the third downstream entity (e.g. a respirator distributor).
  • the first downstream entity e.g., a hospital
  • the second downstream entity e.g.
  • operation 1518 may include operation 1538 depicting attributable account view request accepting circuit configured to accept the request to view verification information of at least a partial list of goods and/or services associated with the attributable funds by one or more of the first downstream entity, the second downstream entity, and the third downstream entity, and/or one or more agents of the first downstream entity, the second downstream entity, and the third downstream entity.
  • Fig. 1 1 e.g., Fig.
  • 11D shows attributable account view request accepting circuit configured to accept the request to view verification information of at least a partial list of goods and/or services associated with the attributable funds by one or more of the first downstream entity, the second downstream entity, and the third downstream entity, and/or one or more agents of the first downstream entity, the second downstream entity, and the third downstream entity 1 138 accepting the request to view verification information of at least a partial list of goods and/or services associated with the attributable funds by one or more of the first downstream entity (e.g., a school for underprivileged youth), the second downstream entity (e.g., a teachers' association), and the third downstream entity (e.g., a textbook supplier) and/or one or more agents of the first downstream entity (e.g., a school for underprivileged youth), the second downstream entity (e.g., a teachers' association), and the third downstream entity (e.g., a textbook supplier).
  • the first downstream entity e.g., a school for underprivileged youth
  • the second downstream entity e
  • operation 1402 may include operation 1540 depicting input acceptance circuit configured to accept input that regards an attributable account that contains attributable funds that are governed by a distribution rule set that links metadata to the account and to one or more transactions associated with the account.
  • Fig. 1 e.g., Fig.
  • HE shows input acceptance circuit configured to accept input that regards an attributable account that contains attributable funds that are governed by a distribution rule set that links metadata to the account and to one or more transactions associated with the account 1 140 accepting input that regards an attributable account that contains attributable funds that are governed by a distribution rule set that links metadata (e.g., data about the entities) to the account and to one or more transactions associated with the account (e.g., a classification of the vendor and a reputation score are attached as metatdata).
  • metadata e.g., data about the entities
  • operation 1540 may include operation 1542 depicting input acceptance circuit configured to accept input that regards the attributable account that contains attributable funds that are governed by the distribution rule set that links identifier metadata to the attributable account and that links transaction information metadata to each transaction associated with the account.
  • Fig. 1 e.g., Fig.
  • 1 IE shows input acceptance circuit configured to accept input that regards the attributable account that contains attributable funds that are governed by the distribution rule set that links identifier metadata to the attributable account and that links transaction information metadata to each transaction associated with the account 1 142 accepting input that regards the attributable account that contains attributable funds that are governed by the distribution rule set that links identifier metadata to the attributable account and that links transaction information metadata (e.g., time of transaction, name of person who authorized, point of contact at the vendor, etc.) to each transaction associated with the account.
  • transaction information metadata e.g., time of transaction, name of person who authorized, point of contact at the vendor, etc.
  • operation 1542 may include operation 1544 depicting input acceptance circuit configured to accept input accepting input that regards the attributable account that contains attributable funds that are governed by the distribution rule set that links identifier metadata to the attributable account and that links transaction information metadata to each transaction associated with the account, wherein the transaction information includes a receiving party name, a time of transaction, and an underlying bank data for each bank involved in the transaction.
  • Fig. 1 e.g., Fig.
  • HE shows input acceptance circuit configured to accept input accepting input that regards the attributable account that contains attributable funds that are governed by the distribution rule set that links identifier metadata to the attributable account and that links transaction information metadata to each transaction associated with the account, wherein the transaction information includes a receiving party name, a time of transaction, and an underlying bank data for each bank involved in the transaction 1 144 accepting input accepting input that regards the attributable account that contains attributable funds that are governed by the distribution rule set that links identifier metadata to the attributable account and that links transaction information metadata to each transaction associated with the account, wherein the transaction information includes a receiving party name, a time of transaction, and an underlying bank data for each bank involved in the transaction (e.g., a transfer of money to a dairy farm to provide milk to malnourished children).
  • the transaction information includes a receiving party name, a time of transaction, and an underlying bank data for each bank involved in the transaction (e.g., a transfer of money to a dairy farm to provide milk to mal
  • operation 1402 may include operation 1546 depicting input acceptance circuit configured to accept input that regards an attributable account that contains attributable funds that are governed by a distribution rule set that links location data to one or more transactions associated with the account.
  • Fig. 1 e.g., Fig.
  • HE shows input acceptance circuit configured to accept input that regards an attributable account that contains attributable funds that are governed by a distribution rule set that links location data to one or more transactions associated with the account 1 146 accepting input that regards an attributable account that contains attributable funds that are governed by a distribution rule set that links location data to one or more transactions associated with the account (e.g., location of trucks that are leased for transporting concrete to a job site where a school will be built).
  • a distribution rule set that links location data to one or more transactions associated with the account
  • operation 1546 may include operation 1548 depicting input acceptance circuit configured to accept input that regards the attributable account that contains attributable funds that are governed by the distribution rule set that links location data obtained from a global positioning system to locations of one or more transactions associated with the account.
  • Fig. 1 1 e.g., Fig.
  • HE shows input acceptance circuit configured to accept input that regards the attributable account that contains attributable funds that are governed by the distribution rule set that links location data obtained from a global positioning system to locations of one or more transactions associated with the account 1 148 accepting input that regards the attributable account that contains attributable funds that are governed by the distribution rule set that links location data obtained from a global positioning system to locations of one or more transactions associated with the account (e.g., location of where specific vaccines that have remote transmitter tags in their bags are distributed).
  • operation 1548 may include operation 1550 depicting input acceptance circuit configured to accept input that regards the attributable account that contains attributable funds that are governed by the distribution rule set that links location data obtained from tracking beacons associated with one or more goods purchased from attributable funds of the attributable account.
  • Fig. 1 e.g., Fig.
  • HE shows input acceptance circuit configured to accept input that regards the attributable account that contains attributable funds that are governed by the distribution rule set that links location data obtained from tracking beacons associated with one or more goods purchased from attributable funds of the attributable account 1 150 accepting input that regards the attributable account that contains attributable funds that are governed by the distribution rule set that links location data obtained from tracking beacons (e.g., radio signals inside bags of concrete, or electronic devices configured to broadcast their location and usage pattern) associated with one or more goods (e.g., bags of concrete and portable electronics) purchased from attributable funds of the attributable account.
  • tracking beacons e.g., radio signals inside bags of concrete, or electronic devices configured to broadcast their location and usage pattern
  • goods e.g., bags of concrete and portable electronics
  • operation 1402 may include operation 1552 depicting input acceptance circuit configured to accept input that regards an attributable account that contains attributable funds that are governed by a distribution rule set that governs fees that are associated with one or more transactions associated with the attributable funds of the attributable account.
  • Fig. 1 e.g., Fig.
  • FIG. 1 IF shows input acceptance circuit configured to accept input that regards an attributable account that contains attributable funds that are governed by a distribution rule set that governs fees that are associated with one or more transactions associated with the attributable funds of the attributable account 1 152 accepting input that regards an attributable account that contains attributable funds that are governed by a distribution rule set that governs fees that are associated with one or more transactions (e.g., a bank might take a percentage or a flat fee for processing the transaction, which can be controlled by the distribution rule set, or a primary contractor may take a percentage for themselves which is capped by the distribution rule set, or a governmental entity might have a certain percentage earmarked for their own costs in putting the infrastructure in place for the charitable work) associated ith the attributable funds of the attributable account.
  • a distribution rule set that governs fees that are associated with one or more transactions
  • operation 1552 may include operation 1554 depicting input acceptance circuit configured to accept input that regards the attributable account that contains attributable funds that are governed by the distribution rule set that sets a percentage-of-transaction fee limit that is associated with the attributable funds of the attributable account.
  • Fig. 1 e.g., Fig.
  • FIG. 1 IF shows input acceptance circuit configured to accept input that regards the attributable account that contains attributable funds that are governed by the distribution rule set that sets a percentage-of- transaction fee limit that is associated with the attributable funds of the attributable account 1 154 accepting input that regards the attributable account that contains attributable funds that are governed by the distribution rule set that sets a percentage-of-transaction fee limit that is associated with the attributable funds of the attributable account.
  • operation 1402 may include operation 1556 depicting input acceptance circuit configured to accept input that regards the attributable account that contains attributable funds that are governed by the distribution rule set that requires photographic evidence of spending associated with one or more transactions associated with the attributable funds of the attributable account.
  • Fig. 1 e.g., Fig.
  • FIG. 1 IF shows input acceptance circuit configured to accept input that regards the attributable account that contains attributable funds that are governed by the distribution rule set that requires photographic evidence of spending associated with one or more transactions associated with the attributable funds of the attributable account 1 156 accepting input that regards the attributable account that contains attributable funds that are governed by the distribution rule set that requires photographic evidence of spending (e.g., pictures of goods, or pictures of persons at particular sites, or other photographic evidence that can be digitized (or is in digital form) and associated with the transaction and provided on demand to the user, e.g., in an embodiment) associated with one or more transactions associated with the attributable funds of the attributable account.
  • photographic evidence of spending e.g., pictures of goods, or pictures of persons at particular sites, or other photographic evidence that can be digitized (or is in digital form
  • operation 1 156 may include operation 1 158 depicting input acceptance circuit configured to accept input that regards the attributable account that contains attributable funds that are governed by the distribution rule set that requires digital photographic data of evidence of spending associated with one or more transactions associated with the attributable funds of the attributable account to be included with data of the attributable funds.
  • operation 1 158 depicting input acceptance circuit configured to accept input that regards the attributable account that contains attributable funds that are governed by the distribution rule set that requires digital photographic data of evidence of spending associated with one or more transactions associated with the attributable funds of the attributable account to be included with data of the attributable funds.
  • Fig. 1 1, e.g., Fig.
  • 1 IF shows input acceptance circuit configured to accept input that regards the attributable account that contains attributable funds that are governed by the distribution rule set that requires digital photographic data of evidence of spending associated with one or more transactions associated with the attributable funds of the attributable account to be included with data of the attributable funds 1 158 accepting input that regards the attributable account that contains attributable funds that are governed by the distribution rule set that requires digital photographic data of evidence of spending associated with one or more transactions associated with the attributable funds of the attributable account to be included with data of the attributable funds (e.g., the data kept by the Daybreak architecture as a record of the transaction and how it was verified that the transaction complied with the distribution rule set).
  • the distribution rule set that requires digital photographic data of evidence of spending associated with one or more transactions associated with the attributable funds of the attributable account to be included with data of the attributable funds
  • operation 1402 may include operation 1560 depicting input acceptance circuit configured to accept input that regards an attributable account that contains attributable funds that are governed by a distribution rule set that specifies particular spending limits for one or more goods and/or services that are acquired through one or more transactions associated with the attributable funds of the attributable account.
  • Fig. 1 e.g., Fig.
  • 1 IF shows input acceptance circuit configured to accept input that regards an attributable account that contains attributable funds that are governed by a distribution rule set that specifies particular spending limits for one or more goods and/or services that are acquired through one or more transactions associated with the attributable funds of the attributable account 1 160 accepting input that regards an attributable account that contains attributable funds that are governed by a distribution rule set that specifies particular spending limits for one or more goods and/or services that are acquired through one or more transactions (e.g., the purchase of concrete after money is transferred to construction subcontractor) associated with the attributable funds of the attributable account.
  • a distribution rule set specifies particular spending limits for one or more goods and/or services that are acquired through one or more transactions
  • operation 1560 may include operation 1562 depicting input acceptance circuit configured to accept input that regards the attributable account that contains the attributable funds that are governed by the distribution rule set that specifies the particular spending limits for one or more classes of goods that are acquired through one or more transactions associated with the attributable funds of the attributable account.
  • Fig. 1 1 e.g., Fig.
  • 1 IF shows input acceptance circuit configured to accept input that regards the attributable account that contains the attributable funds that are governed by the distribution rule set that specifies the particular spending limits for one or more classes of goods that are acquired through one or more transactions associated with the attributable funds of the attributable account 1 162 accepting input that regards the attributable account that contains the attributable funds that are governed by the distribution rule set that specifies the particular spending limits for one or more classes of goods (e.g., no more than $ 1000 on prescription drugs, no more than $50 on overhead costs, no more than $25/day per diems for contractors, etc.) that are acquired through one or more transactions associated with the attributable funds of the attributable account
  • classes of goods e.g., no more than $ 1000 on prescription drugs, no more than $50 on overhead costs, no more than $25/day per diems for contractors, etc.
  • operation 1560 may include operation 1564 depicting input acceptance circuit configured to accept input that regards the attributable account that contains the attributable funds that are governed by the distribution rule set that specifies the particular spending limits for one or more classes of goods, including food, medicine, construction costs, worker salaries, and concrete supplies.
  • Fig. 1 1 e.g., Fig.
  • FIG. 1 IF shows input acceptance circuit configured to accept input that regards the attributable account that contains the attributable funds that are governed by the distribution rule set that specifies the particular spending limits for one or more classes of goods that are acquired through one or more transactions associated with the attributable funds of the attributable account 1 162 that may be implemented as input acceptance circuit configured to accept input that regards the attributable account that contains the attributable funds that are governed by the distribution rule set that specifies the particular spending limits for one or more classes of goods, including food, medicine, construction costs, worker salaries, and concrete supplies.
  • operation 1562 may include operation 1564 depicting input acceptance circuit configured to accept input that regards the attributable account that contains the attributable funds that are governed by the distribution rule set that specifies the particular spending limits for one or more classes of goods, including food, medicine, construction costs, worker salaries, and concrete supplies.
  • Fig. 1 1, e.g., Fig. 1 IF shows input acceptance circuit configured to accept input that regards the attributable account that contains the attributable funds that are governed by the distribution rule set that specifies the particular spending limits for one or more classes of goods, including food, medicine, construction costs, worker salaries, and concrete supplies.
  • operation 1402 may include operation 1566 depicting input acceptance circuit configured to accept input that regards an attributable account that contains attributable funds that are governed by a distribution rule set that calculates a potential fraud score for each transaction and determines whether to allow access to the attributable funds of the attributable account at least partially based on the fraud score calculation.
  • Fig. 1 e.g., Fig.
  • 1 1G shows input acceptance circuit configured to accept input that regards an attributable account that contains attributable funds that are governed by a distribution rule set that calculates a potential fraud score for each transaction and determines whether to allow access to the attributable funds of the attributable account at least partially based on the fraud score calculation 1 166 accepting input that regards an attributable account that contains attributable funds that are governed by a distribution rule set that calculates a potential fraud score for each transaction and determines whether to allow access to the attributable funds of the attributable account at least partially based on the fraud score calculation (e.g., which may be based on various characteristics of transactions, e.g., as described elsewhere).
  • the fraud score calculation e.g., which may be based on various characteristics of transactions, e.g., as described elsewhere.
  • Figs. 16A-16H depict various implementations of operation 1404, depicting first transaction data receiving circuit configured to receive first transaction data indicating a first transmission of particular funds from a first downstream entity to a second downstream entity, wherein the particular funds are part of the attributable funds, according to embodiments.
  • operation 1404 may include operation 1602 depicting first transaction data receiving circuit configured to receive, from a particular architecture, first transaction data indicating the first transmission of particular funds from the first downstream entity to the second downstream entity, wherein the particular funds are part of the attributable funds.
  • Fig. 12 e.g., Fig.
  • first transaction data receiving circuit configured to receive, from a particular architecture, first transaction data indicating the first transmission of particular funds from the first downstream entity to the second downstream entity, wherein the particular funds are part of the attributable funds 1202 receiving, from a particular architecture (e.g., the Daybreak architecture), first transaction data (e.g., authorizing a payment of 1 ,000,000 to a subcontractor) indicating the first transmission of particular funds from the first downstream entity (e.g., a bank in Africa) to the second downstream entity (e.g., a subcontractor building developer), wherein the particular funds are part of the attributable funds.
  • a particular architecture e.g., the Daybreak architecture
  • first transaction data e.g., authorizing a payment of 1 ,000,000 to a subcontractor
  • the first downstream entity e.g., a bank in Africa
  • second downstream entity e.g., a subcontractor building developer
  • operation 1602 may include operation 1604 depicting first transaction data receiving circuit configured to receive, from the particular architecture that is configured to enable real-time tracking and accounting of transactions involving the attributable funds, first transaction data indicating the first transmission of particular funds from the first downstream entity to the second downstream entity, wherein the particular funds are part of the attributable funds.
  • first transaction data indicating the first transmission of particular funds from the first downstream entity to the second downstream entity, wherein the particular funds are part of the attributable funds.
  • first transaction data receiving circuit configured to receive, from the particular architecture that is configured to enable real-time tracking and accounting of transactions involving the attributable funds, first transaction data indicating the first transmission of particular funds from the first downstream entity to the second downstream entity, wherein the particular funds are part of the attributable funds 1204 receiving, from the particular architecture (e.g., the Daybreak architecture) that is configured to enable real-time tracking and accounting of transactions involving the attributable funds, first transaction data indicating the first transmission of particular funds from the first downstream entity (e.g., a hospital) to the second downstream entity (e.g., a j anitor working on contract with a bank account attached to a phone that is also registered with the Daybreak architecture), wherein the particular funds are part of the attributable funds.
  • the particular architecture e.g., the Daybreak architecture
  • operation 1602 may include operation 1606 depicting first transaction data receiving circuit configured to receive, from the particular architecture that is configured to handle the first transaction data and the second transaction data, first transaction data indicating the first transmission of particular funds from the first downstream entity to the second downstream entity, wherein the particular funds are part of the attributable funds.
  • first transaction data receiving circuit configured to receive, from the particular architecture that is configured to handle the first transaction data and the second transaction data, first transaction data indicating the first transmission of particular funds from the first downstream entity to the second downstream entity, wherein the particular funds are part of the attributable funds.
  • first transaction data receiving circuit configured to receive, from the particular architecture that is configured to handle the first transaction data and the second transaction data, first transaction data indicating the first transmission of particular funds from the first downstream entity to the second downstream entity, wherein the particular funds are part of the attributable funds 1206 receiving, from the particular architecture that is configured to handle the first transaction data (e.g., the data of the first transmission of funds, e.g., the bid amount for the contract for building a school from the governmental organization to the construction contractor) and the second transaction data (e.g., the contract amount to be paid to the concrete subcontractor to lay the foundation for the school, plus the costs to the construction contractor for the overhead in managing the subcontractor) transmission of funds , first transaction data indicating the first transmission of particular funds from the first downstream entity to the second downstream entity, wherein the particular funds are part of the attributable funds.
  • first transaction data e.g., the data of the first transmission of funds, e.g., the bid amount for the contract for building a school from the governmental organization to
  • operation 1606 may include operation 1608 depicting first transaction data receiving circuit configured to receive, from the particular architecture that is configured to handle the first transaction data and the second transaction data entirely internally to the particular architecture, first transaction data indicating the first transmission of particular funds from the first downstream entity to the second downstream entity, wherein the particular funds are part of the attributable funds.
  • first transaction data receiving circuit configured to receive, from the particular architecture that is configured to handle the first transaction data and the second transaction data entirely internally to the particular architecture, first transaction data indicating the first transmission of particular funds from the first downstream entity to the second downstream entity, wherein the particular funds are part of the attributable funds.
  • first transaction data receiving circuit configured to receive, from the particular architecture that is configured to handle the first transaction data and the second transaction data entirely internally to the particular architecture, first transaction data indicating the first transmission of particular funds from the first downstream entity to the second downstream entity, wherein the particular funds are part of the attributable funds 1208 receiving, from the particular architecture that is configured to handle the first transaction data and the second transaction data entirely internally to the particular architecture (e.g., the transactions do not actually physically move the money, the money stays in an account associated with the Daybreak architecture, but the Daybreak architecture records and verifies the transacitons and the money is recorded at its new location where it can be "offboarded" at which time a transfer will take place directly from the Daybreak architecture account to the payee, who may or may not have an account registered with the Daybreak architecture), first transaction data indicating the first transmission of particular funds from the first downstream entity to the second downstream entity, wherein the particular funds are part of the attributable funds.
  • operation 1404 may include operation 1610 depicting first transaction data receiving circuit configured to receive first transaction data indicating the first transmission of particular funds from a representation of the first downstream entity to a representation of the second downstream entity.
  • operation 1610 depicting first transaction data receiving circuit configured to receive first transaction data indicating the first transmission of particular funds from a representation of the first downstream entity to a representation of the second downstream entity.
  • Fig. 12 e.g., Fig.
  • first transaction data receiving circuit configured to receive first transaction data indicating the first transmission of particular funds from a representation of the first downstream entity to a representation of the second downstream entity 1210 receiving first transaction data indicating the first transmission of particular funds from a representation of the first downstream entity (e.g., an account created by a charitable organization who wants to receive some of the particular funds) to a representation of the second downstream entity (e.g., a vaccine producer who registers an account with the Daybreak architecture because they want to particupate in fund dispersal).
  • a representation of the first downstream entity e.g., an account created by a charitable organization who wants to receive some of the particular funds
  • a representation of the second downstream entity e.g., a vaccine producer who registers an account with the Daybreak architecture because they want to particupate in fund dispersal.
  • operation 1610 may include operation 1612 depicting first transaction data receiving circuit configured to receive first transaction data indicating the first transmission of particular funds from the representation of the first downstream entity to the representation of the second downstream entity, wherein the representation of the first downstream entity and the representation of the second downstream entity are part of a particular architecture.
  • first transaction data indicating the first transmission of particular funds from the representation of the first downstream entity to the representation of the second downstream entity, wherein the representation of the first downstream entity and the representation of the second downstream entity are part of a particular architecture.
  • Fig. 12 e.g., Fig.
  • first transaction data receiving circuit configured to receive first transaction data indicating the first transmission of particular funds from the representation of the first downstream entity to the representation of the second downstream entity, wherein the representation of the first downstream entity and the representation of the second downstream entity are part of a particular architecture 1212 receiving first transaction data indicating the first transmission of particular funds from the representation of the first downstream entity (e.g., a hospital account registered with the Daybreak architecture that uses the Daybreak architecture and account to manage its payments to its doctors, who work on contract) to the representation of the second downstream entity (e.g., the account of a particular doctor who is contracted with the hospital to treat Ebola outbreaks in third world countries) wherein the representation of the first downstream entity (e.g., the account that is part of the Daybreak architecture that represents the hospital) and the representation of the second downstream entity (e.g., the account that is part of the Daybreak architecture that represents the doctor) are part of a particular architecture (e.g., the Daybreak architecture, e.g., Daybreak architecture 3100).
  • operation 1612 may include operation 1614 depicting first transaction data receiving circuit configured to receive first transaction data indicating the first transmission of particular funds from the representation of the first downstream entity to the representation of the second downstream entity, wherein the representation of the first downstream entity is an account associated with the first downstream entity, and the representation of the second downstream entity is an account associated with the second downstream entity.
  • first transaction data indicating the first transmission of particular funds from the representation of the first downstream entity to the representation of the second downstream entity
  • the representation of the first downstream entity is an account associated with the first downstream entity
  • the representation of the second downstream entity is an account associated with the second downstream entity.
  • first transaction data receiving circuit configured to receive first transaction data indicating the first transmission of particular funds from the representation of the first downstream entity to the representation of the second downstream entity, wherein the representation of the first downstream entity is an account associated with the first downstream entity, and the representation of the second downstream entity is an account associated with the second downstream entity 1214 receiving first transaction data indicating the first transmission of particular funds from the representation of the first downstream entity to the representation of the second downstream entity, wherein the representation of the first downstream entity is an account associated with the first downstream entity, and the representation of the second downstream entity is an account associated with the second downstream entity (e.g., a schoolteacher who works for a remote school in an underdeveloped nation).
  • first downstream entity is an account associated with the first downstream entity
  • the representation of the second downstream entity is an account associated with the second downstream entity
  • operation 1614 may include operation 1616 depicting first transaction data receiving circuit configured to receive first transaction data indicating the first transmission of particular funds from a first architecture account managed by the particular architecture and associated with the first downstream entity to a second architecture account managed by the particular architecture and associated with the second downstream entity.
  • first transaction data indicating the first transmission of particular funds from a first architecture account managed by the particular architecture and associated with the first downstream entity to a second architecture account managed by the particular architecture and associated with the second downstream entity.
  • Fig. 12 e.g., Fig.
  • first transaction data receiving circuit configured to receive first transaction data indicating the first transmission of particular funds from a first architecture account managed by the particular architecture and associated with the first downstream entity to a second architecture account managed by the particular architecture and associated with the second downstream entity 1216 receiving first transaction data indicating the first transmission of particular funds from a first architecture account (e.g., an account associated with a homebuilding charity) managed by the particular architecture and associated with the first downstream entity (e.g., the homebuilding charity) to a second architecture account managed by the particular architecture (e.g., the Daybreak architecture) and associated with the second downstream entity (e.g., the tool supplier).
  • a first architecture account e.g., an account associated with a homebuilding charity
  • the first downstream entity e.g., the homebuilding charity
  • second architecture account managed by the particular architecture e.g., the Daybreak architecture
  • operation 1404 may include operation 1618 depicting first transaction data request receiving circuit configured to receive first transaction data indicating a received request to transmit particular funds from the first downstream entity to the second downstream entity.
  • Fig. 12 e.g., Fig. 12C
  • first transaction data request receiving circuit configured to receive first transaction data indicating a received request to transmit particular funds from the first downstream entity to the second downstream entity 1218 receiving firstr transaction data indicating a received request to transmit particular funds from the first downstream entity (e.g., a truck driving contractor) to the second downstream entity (e.g., truck drivers, e.g., where the third downstream entity might be the gas station where the truck drivers fill their trucks with gasoline).
  • the first downstream entity e.g., a truck driving contractor
  • truck drivers e.g., where the third downstream entity might be the gas station where the truck drivers fill their trucks with gasoline.
  • operation 1404 may include operation 1620, which may appear in conjunction with operation 1618, operation 1620 depicting first transaction data receiving circuit configured to receive first transaction data indicating a first transmission of particular funds from a representation of the first downstream entity to a representation of the second downstream entity, wherein the particular funds are not transferred from the first downstream entity to the downstream entity.
  • operation 1620 depicting first transaction data receiving circuit configured to receive first transaction data indicating a first transmission of particular funds from a representation of the first downstream entity to a representation of the second downstream entity, wherein the particular funds are not transferred from the first downstream entity to the downstream entity.
  • Fig. 12 e.g., Fig.
  • first transaction data receiving circuit configured to receive first transaction data indicating a first transmission of particular funds from a representation of the first downstream entity to a representation of the second downstream entity, wherein the particular funds are not transferred from the first downstream entity to the downstream entity 1220 receivign a first transaction data indicating a first transmission of particular funds from the representation (e.g., the Daybreak architecture account) of the first downstream entity (e.g., a government entity that assigns bid contracts to construction entities) to a represtnation (e.g., a different Daybreak architecture account) of the second downstream entity (e.g., a construction contractor).
  • representation e.g., the Daybreak architecture account
  • the first downstream entity e.g., a government entity that assigns bid contracts to construction entities
  • represtnation e.g., a different Daybreak architecture account
  • operation 1620 may include operation 1622 depicting first transaction data receiving circuit configured to receive first transaction data indicating the first transmission of particular funds from the representation of the first downstream entity to the representation of the second downstream entity, wherein the representation of the first downstream entity and the representation of the second downstream entity are part of a particular architecture.
  • first transaction data indicating the first transmission of particular funds from the representation of the first downstream entity to the representation of the second downstream entity, wherein the representation of the first downstream entity and the representation of the second downstream entity are part of a particular architecture.
  • Fig. 12 e.g., Fig.
  • first transaction data receiving circuit configured to receive first transaction data indicating the first transmission of particular funds from the representation of the first downstream entity to the representation of the second downstream entity, wherein the representation of the first downstream entity and the representation of the second downstream entity are part of a particular architecture 1222 receiving first transaction data indicating the first transmission of particular funds from the representation of the first downstream entity to the representation of the second downstream entity, wherein the representation of the first downstream entity and the representation of the second downstream entity are part of a particular architecture (e.g., the Daybreak architecture).
  • a particular architecture e.g., the Daybreak architecture
  • operation 1620 may include operation 1624 depicting first transaction data receiving circuit configured to receive first transaction data indicating the first transmission of particular funds from a first architecture account representation of the first downstream entity to a second architecture account representation of the second downstream entity.
  • first transaction data indicating the first transmission of particular funds from a first architecture account representation of the first downstream entity to a second architecture account representation of the second downstream entity.
  • Fig. 12 e.g., Fig.
  • first transaction data receiving circuit configured to receive first transaction data indicating the first transmission of particular funds from a first architecture account representation of the first downstream entity to a second architecture account representation of the second downstream entity 1224 receiving first transaction data indicating the first transmission of particular funds from a first architecture account representation (e.g., an account registered with and tracked by the Daybreak architecture) of the first downstream entity (e.g., a charitable organization) to a second architecture account representation of the second downstream entity (e.g., a subsidiary of the charitable organization).
  • a first architecture account representation e.g., an account registered with and tracked by the Daybreak architecture
  • the first downstream entity e.g., a charitable organization
  • second architecture account representation of the second downstream entity e.g., a subsidiary of the charitable organization
  • operation 1624 may include operation 1626 depicting first transaction data receiving circuit configured to receive first transaction data indicating the first transmission of particular funds from the first architecture account representation of the first downstream entity to the architecture account representation of the second downstream entity, wherein the first architecture account representation of the first downstream entity is an account that was registered with the architecture by the first downstream entity.
  • first transaction data indicating the first transmission of particular funds from the first architecture account representation of the first downstream entity to the architecture account representation of the second downstream entity, wherein the first architecture account representation of the first downstream entity is an account that was registered with the architecture by the first downstream entity.
  • first transaction data receiving circuit configured to receive first transaction data indicating the first transmission of particular funds from the first architecture account representation of the first downstream entity to the architecture account representation of the second downstream entity, wherein the first architecture account representation of the first downstream entity is an account that was registered with the architecture by the first downstream entity 1226 receiving first transaction data indicating the first transmission of particular funds from the first architecture account representation of the first downstream entity to the architecture account representation of the second downstream entity (e.g., a nurses' association), wherein the first architecture account representation of the first downstream entity is an account that was registered with the architecture by the first downstream entity (e.g., a hospital)
  • operation 1624 may include operation 1628 depicting first transaction data receiving circuit configured to receive first transaction data indicating the first transmission of particular funds from the first architecture account representation of the first downstream entity to the architecture account representation of the second downstream entity, wherein the second architecture account representation of the second downstream entity is an account that was registered with the architecture by the second downstream entity.
  • first transaction data indicating the first transmission of particular funds from the first architecture account representation of the first downstream entity to the architecture account representation of the second downstream entity, wherein the second architecture account representation of the second downstream entity is an account that was registered with the architecture by the second downstream entity.
  • first transaction data receiving circuit configured to receive first transaction data indicating the first transmission of particular funds from the first architecture account representation of the first downstream entity to the architecture account representation of the second downstream entity, wherein the second architecture account representation of the second downstream entity is an account that was registered with the architecture by the second downstream entity 1228 receiving first transaction data indicating the first transmission of particular funds from the first architecture account representation of the first downstream entity (e.g., a building contractor) to the architecture account representation of the second downstream entity, wherein the second architecture account representation of the second downstream entity is an account that was registered with the architecture by the second downstream entity (e.g., a landscaping company)
  • operation 1404 may include operation 1630 depicting first transaction data receiving circuit configured to receive first transaction data indicating the first transmission of particular funds from the first downstream entity to the second downstream entity, wherein the particular funds represent a portion of the attributable funds.
  • first transaction data indicating the first transmission of particular funds from the first downstream entity to the second downstream entity, wherein the particular funds represent a portion of the attributable funds.
  • FIG. 12 shows first transaction data receiving circuit configured to receive first transaction data indicating the first transmission of particular funds from the first downstream entity to the second downstream entity, wherein the particular funds represent a portion of the attributable funds 1230 receiving first transaction data indicating the first transmission of particular funds from the first downstream entity (e.g., a building subcontractor) to the second downstream entity (e.g., a lumber supplier), wherein the particular funds represent a portion of the attributable funds.
  • first downstream entity e.g., a building subcontractor
  • the second downstream entity e.g., a lumber supplier
  • operation 1404 may include operation 1632 depicting first transaction data receiving circuit configured to receive first transaction data indicating the first transmission of particular funds from the first downstream entity to the second downstream entity, wherein the particular funds represent a portion of the attributable funds, wherein the attributable funds are owned by a single entity.
  • first transaction data indicating the first transmission of particular funds from the first downstream entity to the second downstream entity
  • the particular funds represent a portion of the attributable funds, wherein the attributable funds are owned by a single entity.
  • Fig. 12 e.g., Fig.
  • first transaction data receiving circuit configured to receive first transaction data indicating the first transmission of particular funds from the first downstream entity to the second downstream entity, wherein the particular funds represent a portion of the attributable funds, wherein the attributable funds are owned by a single entity 1232 receiving first transaction data indicating the first transmission of particular funds from the first downstream entity (e.g., a large government contractor) to the second downstream entity (e.g., a smaller contractor that makes weapons), wherein the particular funds represent a portion of the attributable funds, wherein the attributable funds are owned by a single entity (e.g., all of the attributable funds are owned by a single entity but each particular funds might have a different distribution rule set attached to it, e.g., 500,000 of the funds might be required for food spending, and 150,000 for medical spending, etc., with various conditions and limiters specified as described herein).
  • a single entity 1232 receiving first transaction data indicating the first transmission of particular funds from the first downstream entity (e.g., a large government contractor) to
  • operation 1404 may include operation 1634 depicting first transaction data receiving circuit configured to receive first transaction data indicating the first transmission of particular funds from the first downstream entity to the second downstream entity, wherein the particular funds represent a portion of the attributable funds that are owned by a single entity, and the attributable funds are owned by more than one entity.
  • first transaction data indicating the first transmission of particular funds from the first downstream entity to the second downstream entity
  • the particular funds represent a portion of the attributable funds that are owned by a single entity, and the attributable funds are owned by more than one entity.
  • Fig. 12 e.g., Fig.
  • first transaction data receiving circuit configured to receive first transaction data indicating the first transmission of particular funds from the first downstream entity to the second downstream entity, wherein the particular funds represent a portion of the attributable funds that are owned by a single entity, and the attributable funds are owned by more than one entity 1234 receiving first transaction data indicating the first transmission of particular funds from the first downstream entity to the second downstream entity, wherein the particular funds represent a portion of the attributable funds that are owned by a single entity, and the attributable funds are owned by more than one entity (e.g., the attributable funds are several different persons' money, of which the particular funds are the portion of the attributable funds owned by a single person).
  • operation 1634 may include operation 1636 depicting first transaction data receiving circuit configured to receive first transaction data indicating the first transmission of particular funds from the first downstream entity to the second downstream entity, wherein the particular funds represent a portion of the attributable funds that are owned by a single entity, and the attributable funds are owned by more than one entity but are stored in a single underlying bank account.
  • first transaction data indicating the first transmission of particular funds from the first downstream entity to the second downstream entity
  • the particular funds represent a portion of the attributable funds that are owned by a single entity, and the attributable funds are owned by more than one entity but are stored in a single underlying bank account.
  • Fig. 12 e.g., Fig.
  • first transaction data receiving circuit configured to receive first transaction data indicating the first transmission of particular funds from the first downstream entity to the second downstream entity, wherein the particular funds represent a portion of the attributable funds that are owned by a single entity, and the attributable funds are owned by more than one entity but are stored in a single underlying bank account 1236 receiving first transaction data indicating the first transmission of particular funds from the first downstream entity to the second downstream entity, wherein the particular funds represent a portion of the attributable funds that are owned by a single entity, and the attributable funds are owned by more than one entity but are stored in a single underlying bank account (e.g., all of the attributable funds for various clients are deposited into a single bank account which does not discriminate regarding its funds, and the disposition of the funds and their owners is managed entirely within the Daybreak architecture, except when funds are directly offboarded).
  • first transaction data indicating the first transmission of particular funds from the first downstream entity to the second downstream entity
  • the particular funds represent a portion of the attributable funds that are owned
  • operation 1404 may include operation 1638 depicting first transaction data receiving circuit configured to receive first transaction data that indicates the first transmission of the particular funds from the first downstream entity to the second downstream entity, wherein the first downstream entity is a local domestic bank and the second downstream entity is a national domestic bank.
  • first transaction data that indicates the first transmission of the particular funds from the first downstream entity to the second downstream entity, wherein the first downstream entity is a local domestic bank and the second downstream entity is a national domestic bank.
  • Fig. 12 e.g., Fig.
  • first transaction data receiving circuit configured to receive first transaction data that indicates the first transmission of the particular funds from the first downstream entity to the second downstream entity, wherein the first downstream entity is a local domestic bank and the second downstream entity is a national domestic bank 1238 receiving first transaction data indicating the first transmission of the particular funds from the first downstream entity to the second downstream entity, wherein the first downstream entity is a local domestic bank (e.g., Boeing Employees Credit Union) and the second downstream entity is a national domestic bank (e.g., Wells Fargo).
  • first transaction data that indicates the first transmission of the particular funds from the first downstream entity to the second downstream entity
  • the first downstream entity is a local domestic bank (e.g., Boeing Employees Credit Union)
  • the second downstream entity is a national domestic bank (e.g., Wells Fargo).
  • operation 1404 may include operation 1640 depicting first transaction data receiving circuit configured to receive first transaction data that indicates the first transmission of the particular funds from the first downstream entity to the second downstream entity, wherein the first downstream entity is a national domestic bank and the second downstream entity is a European bank.
  • first transaction data that indicates the first transmission of the particular funds from the first downstream entity to the second downstream entity, wherein the first downstream entity is a national domestic bank and the second downstream entity is a European bank.
  • Fig. 12 e.g., Fig.
  • first transaction data receiving circuit configured to receive first transaction data that indicates the first transmission of the particular funds from the first downstream entity to the second downstream entity, wherein the first downstream entity is a national domestic bank and the second downstream entity is a European bank 1240 receiving first transaction data indicating the first transmission of the particular funds from the first downstream entity to the second downstream entity, wherein the first downstream entity is a national domestic bank (e.g., Bank of America) and the second downstream entity is a European bank (e.g., Bank of London).
  • first transaction data that indicates the first transmission of the particular funds from the first downstream entity to the second downstream entity
  • the first downstream entity is a national domestic bank (e.g., Bank of America)
  • the second downstream entity is a European bank (e.g., Bank of London).
  • operation 1404 may include operation 1642 depicting first transaction data receiving circuit configured to receive first transaction data indicating the first transmission of the particular funds from the first downstream entity to the second downstream entity, wherein the first downstream entity is a European bank and the second downstream entity is a foreign non-European bank.
  • first downstream entity is a European bank
  • second downstream entity is a foreign non-European bank.
  • first transaction data receiving circuit configured to receive first transaction data indicating the first transmission of the particular funds from the first downstream entity to the second downstream entity, wherein the first downstream entity is a European bank and the second downstream entity is a foreign non-European bank 1242 receiving first transaction data indicating the first transmission of the particular funds from the first downstream entity to the second downstream entity, wherein the first downstream entity is a European bank and the second downstream entity is a foreign non-European bank.
  • operation 1404 may include operation 1644 depicting first transaction data receiving circuit configured to receive first transaction data indicating the first transmission of the particular funds from the first downstream entity to the second downstream entity, wherein the first downstream entity is a foreign non-European bank and the second downstream entity is a foreign organization.
  • first transaction data indicating the first transmission of the particular funds from the first downstream entity to the second downstream entity, wherein the first downstream entity is a foreign non-European bank and the second downstream entity is a foreign organization.
  • Fig. 12 e.g., Fig.
  • first transaction data receiving circuit configured to receive first transaction data indicating the first transmission of the particular funds from the first downstream entity to the second downstream entity, wherein the first downstream entity is a foreign non- European bank and the second downstream entity is a foreign organization 1244 receiving first transaction data indicating the first transmission of the particular funds from the first downstream entity to the second downstream entity, wherein the first downstream entity is a foreign non-European bank and the second downstream entity is a foreign organization (e.g., a charitable institution based in Iraq).
  • operation 1404 may include operation 1646 depicting first transaction data receiving circuit configured to receive first transaction data indicating the first transmission of the particular funds from the first downstream entity to the second downstream entity, wherein the first downstream entity is a first foreign organization and the second downstream entity is a second foreign organization.
  • first transaction data indicating the first transmission of the particular funds from the first downstream entity to the second downstream entity, wherein the first downstream entity is a first foreign organization and the second downstream entity is a second foreign organization.
  • Fig. 12 e.g., Fig.
  • first transaction data receiving circuit configured to receive first transaction data indicating the first transmission of the particular funds from the first downstream entity to the second downstream entity, wherein the first downstream entity is a first foreign organization and the second downstream entity is a second foreign organization 1246 receiving first transaction data indicating the first transmission of the particular funds from the first downstream entity to the second downstream entity, wherein the first downstream entity is a first foreign organization and the second downstream entity is a second foreign organization.
  • operation 1404 may include operation 1648 depicting first transaction data receiving circuit configured to receive first transaction data indicating the first transmission of particular funds from the first downstream entity to the second downstream entity, wherein the first transmission of particular funds occurs within a particular architecture.
  • first transaction data indicating the first transmission of particular funds from the first downstream entity to the second downstream entity, wherein the first transmission of particular funds occurs within a particular architecture.
  • Fig. 12 e.g., Fig.
  • FIG. 12E shows first transaction data receiving circuit configured to receive first transaction data indicating the first transmission of particular funds from the first downstream entity to the second downstream entity, wherein the first transmission of particular funds occurs within a particular architecture 1248 receiving first transaction data indicating the first transmission of particular funds form the first downstream entity to the second downstream entity, wherein the first transmission of particular funds occurs within a particular architecture (e.g., the first transmission of funds takes place within the Daybreak architecture, e.g., from a first Daybreak account to a second Daybreak account).
  • the first transmission of funds takes place within the Daybreak architecture, e.g., from a first Daybreak account to a second Daybreak account.
  • operation 1648 may include operation 1650 depicting first transaction data receiving circuit configured to receive first transaction data indicating the first transmission of particular funds from the first downstream entity to the second downstream entity, wherein the first transmission of particular funds occurs within the particular architecture that performs verification of the first transmission before allowing the first transmission.
  • operation 1650 depicting first transaction data receiving circuit configured to receive first transaction data indicating the first transmission of particular funds from the first downstream entity to the second downstream entity, wherein the first transmission of particular funds occurs within the particular architecture that performs verification of the first transmission before allowing the first transmission.
  • first transaction data receiving circuit configured to receive first transaction data indicating the first transmission of particular funds from the first downstream entity to the second downstream entity, wherein the first transmission of particular funds occurs within the particular architecture that performs verification of the first transmission before allowing the first transmission 1250 receiving first transaction data indicating the first transmission of particular funds from the first downstream entity to the second downstream entity, wherein the first transmission of particular funds occurs within the particular architecture that performs verification of the first transmission (e.g., that the transaction complies with the distribution rule set, e.g., the vendor is registered, the timing of the transaction is proper, the amount is not too large, the funds have been earmarked for that specific purpose, the vendor is a trusted vendor, the vendor is on an approved list, the vendor is registered as an approved type) before allowing the first transmission.
  • the distribution rule set e.g., the vendor is registered, the timing of the transaction is proper, the amount is not too large, the funds have been earmarked for that specific purpose, the vendor is a trusted vendor, the vendor is on an approved list, the vendor is
  • operation 1650 may include operation 1652 depicting first transaction data receiving circuit configured to receive first transaction data indicating the first transmission of particular funds from the first downstream entity to the second downstream entity, wherein the first transmission of particular funds occurs within the particular architecture that performs verification of the first transmission for compliance with the distribution rule set before allowing the first transmission.
  • first transaction data indicating the first transmission of particular funds from the first downstream entity to the second downstream entity
  • the first transmission of particular funds occurs within the particular architecture that performs verification of the first transmission for compliance with the distribution rule set before allowing the first transmission.
  • Fig. 12 e.g., Fig.
  • first transaction data receiving circuit configured to receive first transaction data indicating the first transmission of particular funds from the first downstream entity to the second downstream entity, wherein the first transmission of particular funds occurs within the particular architecture that performs verification of the first transmission for compliance with the distribution rule set before allowing the first transmission 1252 receiving first transaction data indicating the first transmission of particular funds from the first downstream entity (e.g., a national bank) to the second downstream entity (e.g., a non-profit organization dedicated to erecting schools), wherein the first transmission of particular funds occurs within the particular architecture (e.g., the transfer of funds takes place from an account within the particular architecture, e.g., the Daybreak architecture, to another account within the Daybreak architecture, without actually physically moving the money from various accounts that may be set up at various banks and across city, state, national, or international lines) that performs verification of the first transmission for compliance with the distribution rule set before allowing the first transmission (e.g., the transmission of funds to the non-profit for use in purchasing textbooks for the schools).
  • the first transmission e
  • operation 1404 may include operation 1654 depicting first transaction data receiving circuit configured to receive first transaction data indicating that the first transmission of particular funds is compliant with the distribution rule set.
  • Fig. 12 e.g., Fig. 12G, shows first transaction data receiving circuit configured to receive first transaction data indicating that the first transmission of particular funds is compliant with the distribution rule set 1254 receiving first transaction data indicating that the first transmission of particular funds is compliant with the distribution rule set.
  • operation 1654 may include operation 1656 depicting first transaction data receiving circuit configured to receive first transaction data indicating that the first transmission of the particular funds is compliant with the distribution rule set that specifies real time reporting associated with actions taken on the particular funds.
  • Fig. 12 e.g., Fig.
  • first transaction data receiving circuit configured to receive first transaction data indicating that the first transmission of the particular funds is compliant with the distribution rule set that specifies real time reporting associated with actions taken on the particular funds 1256 receiving first transaction data indicating tha the first transmission of the particular funds is compliant with the distribution rule set that specifies real time reporting (e.g., the funds are to be reported back to the daybreak architecture as spent as they are being spent) associated with actions taken on the particular funds).
  • operation 1654 may include operation 1658 depicting first transaction data receiving circuit configured to receive first transaction data indicating that the first transmission of particular funds has passed compliance with the distribution rule set that specifies one or more permissible identities of the second downstream entity.
  • Fig. 12 e.g., Fig. 12G
  • permissible identities e.g., hospital, school, food bank, homeless shelter
  • operation 1654 may include operation 1660 depicting first transaction data receiving circuit configured to receive first transaction data indicating that the first transmission of particular funds has passed compliance with the distribution rule set that specifies an amount of data to be collected regarding the first transmission of the particular funds.
  • Fig. 12 e.g., Fig. 12G
  • operation 1660 may include operation 1662 depicting first transaction data receiving circuit configured to receive first transaction data indicating that the first transmission of particular funds has passed compliance with the distribution rule set that specifies photographic evidence and location tracking evidence data to be collected regarding the first transmission of the particular funds.
  • operation 1662 depicting first transaction data receiving circuit configured to receive first transaction data indicating that the first transmission of particular funds has passed compliance with the distribution rule set that specifies photographic evidence and location tracking evidence data to be collected regarding the first transmission of the particular funds.
  • Fig. 12 e.g., Fig.
  • first transaction data receiving circuit configured to receive first transaction data indicating that the first transmission of particular funds has passed compliance with the distribution rule set that specifies photographic evidence and location tracking evidence data to be collected regarding the first transmission of the particular funds 1262 receiving first transaction data indicating that the first transmission of particular funds has passed compliance with the distribution rule set that specifies phographic evidence (e.g., pictures of the employees that were hired for the building of the hospital) and location tracking evidence (e.g., RFID location tags on the bags of concrete brought into the site for use in building the hospital, but which may have been stolen or misappropriated for personal proj ects by bad actors) regarding the first transmission of the particular funds.
  • phographic evidence e.g., pictures of the employees that were hired for the building of the hospital
  • location tracking evidence e.g., RFID location tags on the bags of concrete brought into the site for use in building the hospital, but which may have been stolen or misappropriated for personal proj ects by bad actors
  • operation 1404 may include operation 1664 depicting first transaction data receiving circuit configured to receive first transaction data indicating that the first transmission of particular funds is compliant with the distribution rule set that requires that one or more of the first, second, and third downstream entities are trusted entities.
  • Fig. 12 e.g., Fig.
  • first transaction data receiving circuit configured to receive first transaction data indicating that the first transmission of particular funds is compliant with the distribution rule set that requires that one or more of the first, second, and third downstream entities are trusted entities 1264 receiving first transaction data indicating that the first transmission of particular funds is compliant with the dsitributiion rule set that requires one or more of the first, second, and third downstream entities are trusted entities (e.g., they are listed by the distribution rule set as trusted entities or they meet the conditions specified in the distribution rule set (e.g., length of time in business) to be a trusted entity.
  • trusted entities e.g., they are listed by the distribution rule set as trusted entities or they meet the conditions specified in the distribution rule set (e.g., length of time in business) to be a trusted entity.
  • operation 1664 may include operation 1666 depicting first transaction data receiving circuit configured to receive first transaction data indicating that the first transmission of particular funds is compliant with the distribution rule set that requires that one or more of the first, second, and third downstream entities are trusted entities as established by a particular architecture that tracks one or more reputation scores of the one or more of the first, second, and third downstream entities.
  • Fig. 12 e.g., Fig.
  • first transaction data receiving circuit configured to receive first transaction data indicating that the first transmission of particular funds is compliant with the distribution rule set that requires that one or more of the first, second, and third downstream entities are trusted entities as established by a particular architecture that tracks one or more reputation scores of the one or more of the first, second, and third downstream entities 1266 receiving first transaction data indicating that the first transmission of particular funds is compliant with the distribution rule set that requires that one or more of the first, second, and third downstream entities are trusted entities as established by a particular architecture (e.g., the Daybreak architecture) that tracks one or more reputation scores (e.g., scores based on compliance with distribution rule set, or feedback of entities associated with the Daybreak architecture, or feedback of entities not associated with the Daybreak architecture).
  • a particular architecture e.g., the Daybreak architecture
  • reputation scores e.g., scores based on compliance with distribution rule set, or feedback of entities associated with the Daybreak architecture, or feedback of entities not associated with the Daybreak architecture.
  • Figs. 17A-17C depict various implementations of operation 1406, depicting second transaction data receiving circuit configured to receive second transaction data indicating a second transmission of the particular funds from the second downstream entity to the third downstream entity, according to embodiments.
  • operation 1406 may include operation 1702 depicting second transaction data receiving circuit configured to receive, from a particular architecture, second transaction data indicating the second transmission of particular funds from the second downstream entity to the third downstream entity, wherein the particular funds are part of the attributable funds.
  • Fig. 13 e.g., Fig.
  • FIG. 13 A shows second transaction data receiving circuit configured to receive, from a particular architecture, second transaction data indicating the second transmission of particular funds from the second downstream entity to the third downstream entity, wherein the particular funds are part of the attributable funds 802 receiving, from a particular architecture (e.g., from an account registered with the Daybreak architecture), second transaction data indicating the second transmission (e.g., a viewable second transmission of the same or partially the same funds) from the second downstream entity (e.g., a subcontractor) to the third downstream entity (e.g., a concrete supplier), wherein the particular funds are part of the attributable funds.
  • a particular architecture e.g., from an account registered with the Daybreak architecture
  • second transaction data indicating the second transmission e.g., a viewable second transmission of the same or partially the same funds
  • the second downstream entity e.g., a subcontractor
  • the third downstream entity e.g., a concrete supplier
  • operation 1702 may include operation 1704 depicting second transaction data receiving circuit configured to receive, from the particular architecture that is configured to implement a reward unit, second transaction data indicating the second transmission of particular funds from the second downstream entity to the third downstream entity.
  • second transaction data indicating the second transmission of particular funds from the second downstream entity to the third downstream entity.
  • FIG. 13A shows second transaction data receiving circuit configured to receive, from the particular architecture that is configured to implement a reward unit, second transaction data indicating the second transmission of particular funds from the second downstream entity to the third downstream entity 1704 receiving, from the particular architecture (e.g., the Daybreak architecture), that is configured to implement a reward unit (e.g., part of the architecture can modify the distribution rule set or provide cash or incentive rewards to vendors who follow specific guidelines for the distribution rule set), second transaction data indicating the second transmission of particular funds from the second downstream entity (e.g., a school) to the third downstream entity (e.g., a school computer supplier).
  • the particular architecture e.g., the Daybreak architecture
  • a reward unit e.g., part of the architecture can modify the distribution rule set or provide cash or incentive rewards to vendors who follow specific guidelines for the distribution rule set
  • operation 1704 may include operation 1706 depicting second transaction data receiving circuit configured to receive, from the particular architecture that is configured to implement the reward unit, second transaction data indicating that second transmission of particular funds from the second downstream entity to the third downstream entity, wherein the reward unit is configured to reward inclusion of transaction-related data within a particular timeframe.
  • second transaction data receiving circuit configured to receive, from the particular architecture that is configured to implement the reward unit, second transaction data indicating that second transmission of particular funds from the second downstream entity to the third downstream entity, wherein the reward unit is configured to reward inclusion of transaction-related data within a particular timeframe.
  • FIG. 13 A shows second transaction data receiving circuit configured to receive, from the particular architecture that is configured to implement the reward unit, second transaction data indicating that second transmission of particular funds from the second downstream entity to the third downstream entity, wherein the reward unit is configured to reward inclusion of transaction-related data within a particular timeframe 1306 receiving, from the particular architecture (e.g., the Daybreak architecture) that is configured to implement the reward unit (e.g., part of the architecture can modify the distribution rule set or provide cash or incentive rewards to vendors who follow specific guidelines for the distribution rule set, or increase the reputation score in various tracking mechanisms for that vendor to increase the likelihood that that vendor will get repeat business in other transacitons with potentially unrelated entities), second transaction data indicating that second transmission of the particular funds from the second downstream entity (e.g., a church) to the third downstream entity (e.g., a food kitchen), wherein the reward unit is configured to reward inclusion of transaction-related data (e.g., photographic evidence of the food being purchased by the food kitchen and/or distributed to the needy) within a particular time
  • operation 1706 may include operation 1708 depicting second transaction data receiving circuit configured to receive, from the particular architecture that is configured to implement the reward unit, second transaction data indicating that second transmission of particular funds from the second downstream entity to the third downstream entity, wherein the reward unit is configured to reward inclusion of photographic evidence of effect of the second transmission of particular funds.
  • second transaction data receiving circuit configured to receive, from the particular architecture that is configured to implement the reward unit, second transaction data indicating that second transmission of particular funds from the second downstream entity to the third downstream entity, wherein the reward unit is configured to reward inclusion of photographic evidence of effect of the second transmission of particular funds.
  • FIG. 13A shows second transaction data receiving circuit configured to receive, from the particular architecture that is configured to implement the reward unit, second transaction data indicating that second transmission of particular funds from the second downstream entity to the third downstream entity, wherein the reward unit is configured to reward inclusion of photographic evidence of effect of the second transmission of particular funds 1308 receiving, from the particular architecture that is configured to implement the reward unit (e.g., part of the architecture can modify the distribution rule set or provide cash or incentive rewards to vendors who follow specific guidelines for the distribution rule set, or increase the reputation score in various tracking mechanisms for that vendor to increase the likelihood that that vendor will get repeat business in other transacitons with potentially unrelated entities), second transaction data indicating that second transmission of particular funds from the second downstream entity (e.g., a grocery supplier) to the third downstream entity (e.g., a dairy supplier) , wherein the reward unit is configured to reward inclusion of photographic evidence (e.g., photos of the milk that was purchased that are uploaded ot the Daybreak architecture and associated with the attributable funds for verification and to complete the rules, e
  • operation 1706 may include operation 1710 depicting second transaction data receiving circuit configured to receive, from the particular architecture that is configured to implement the reward unit, second transaction data indicating that second transmission of particular funds from the second downstream entity to the third downstream entity, wherein the reward unit is configured to reward inclusion of photographic evidence of goods that were purchased as a result of the second transmission of particular funds.
  • second transaction data receiving circuit configured to receive, from the particular architecture that is configured to implement the reward unit, second transaction data indicating that second transmission of particular funds from the second downstream entity to the third downstream entity, wherein the reward unit is configured to reward inclusion of photographic evidence of goods that were purchased as a result of the second transmission of particular funds.
  • FIG. 13A shows second transaction data receiving circuit configured to receive, from the particular architecture that is configured to implement the reward unit, second transaction data indicating that second transmission of particular funds from the second downstream entity to the third downstream entity, wherein the reward unit is configured to reward inclusion of photographic evidence of goods that were purchased as a result of the second transmission of particular funds 1310 receiving, from the particular architecture that is configured to implement the reward unit (e.g., part of the architecture can modify the distribution rule set or provide cash or incentive rewards to vendors who follow specific guidelines for the distribution rule set, or increase the reputation score in various tracking mechanisms for that vendor to increase the likelihood that that vendor will get repeat business in other transacitons with potentially unrelated entities), second transaction data indicating that second transmission of particular funds from the second downstream entity (e.g., a grocery supplier) to the third downstream entity (e.g., a cereal box supplier) , wherein the reward unit is configured to reward inclusion of photographic evidence (e.g., photos of the cereal that was purchased that are uploaded to the Daybreak architecture and associated with the attributable funds for verification and requested
  • operation 1706 may include operation 1712 depicting second transaction data receiving circuit configured to receive, from the particular architecture that is configured to implement the reward unit, second transaction data indicating that second transmission of particular funds from the second downstream entity to the third downstream entity, wherein the reward unit is configured to reward inclusion of location tracking data of effect of the second transmission of particular funds.
  • Fig. 13 e.g., Fig.
  • FIG. 13B shows second transaction data receiving circuit configured to receive, from the particular architecture that is configured to implement the reward unit, second transaction data indicating that second transmission of particular funds from the second downstream entity to the third downstream entity, wherein the reward unit is configured to reward inclusion of location tracking data of effect of the second transmission of particular funds 1312 receiving, from the particular architecture (e.g., a non-Daybreak architecture that is implemented directly by a bank that wishes to more tightly control how the money is spent within that bank's jurisdiction) that is configured to implement the reward unit, second transaction data indicating that second transmission of particular funds from the second downstream entity (e.g., a hospital) to the third downstream entity (e.g., a vaccine supplier), wherein the reward unit is configured to reward inclusion of location tracking data (e.g., RFID tags on the various vaccine packs) of effect of the second transmission of particular funds.
  • location tracking data e.g., RFID tags on the various vaccine packs
  • operation 1406 may include operation 1714 depicting second transaction data receiving circuit configured to receive, from the particular architecture that is configured to implement a penalty unit, second transaction data indicating the second transmission of particular funds from the second downstream entity to the third downstream entity.
  • second transaction data indicating the second transmission of particular funds from the second downstream entity to the third downstream entity.
  • FIG. 13C shows second transaction data receiving circuit configured to receive, from the particular architecture that is configured to implement a penalty unit, second transaction data indicating the second transmission of particular funds from the second downstream entity to the third downstream entity 1314 receiving, from the particular architecture (e.g., a non-Daybreak architecture that is implemented directly by a charitable organization that wishes to more tightly control how the money is spent within that charitable organization's jurisdiction) that is configured to implement a penalty unit (e.g., an implementation that penalizes, in the form of decreased score or reputation, decrease in amount of business done, decrease in preferential treatment, decrease in percentage of transaction fees, or actual monetary penalties), second transaction data indicating the second transmission of particular funds from the second downstream entity (e.g., a labor organization) to the third downstream entity (e.g., a day laborer who has an account through his phone with an M-PESA system).
  • a penalty unit e.g., an implementation that penalizes, in the form of decreased score or reputation, decrease in amount of business done, decrease in preferential treatment,
  • operation 1714 may include operation 1716 depicting second transaction data receiving circuit configured to receive, from the particular architecture that is configured to implement the penalty unit, second transmission data indicating the second transmission of particular funds from the second downstream entity to the third downstream entity, wherein the penalty unit is configured to penalize one or more of the second downstream entity and the third downstream entity based on the distribution rule set.
  • Fig. 13 e.g., Fig.
  • FIG. 13B shows second transaction data receiving circuit configured to receive, from the particular architecture that is configured to implement the penalty unit, second transmission data indicating the second transmission of particular funds from the second downstream entity to the third downstream entity, wherein the penalty unit is configured to penalize one or more of the second downstream entity and the third downstream entity based on the distribution rule set 1316 receiving, from the particular architecture (e.g., the Daybreak architecture), that is configured ot implement the penalty unit, second transmission data indicating the second transmission of particular funds form the second downstream entity (e.g., a trucking company) to the third downstream entity (e.g., a trucker employee of the trucking company that has her bank account tied to her mobile phone), wherein the penalty unit is configured to penalize ne or more of the second downstream entity and the third downstream entity based on the distribution rule set (e.g., if GPS data shows the trucker employee left after four hours but collected eight hours of pay, the distribution rule set specifies the penalty, e.g., it may be a first-offense warning).
  • operation 1716 may include operation 1718 depicting second transaction data receiving circuit configured to receive, from the particular architecture that is configured to implement the penalty unit, second transmission data indicating the second transmission of particular funds from the second downstream entity to the third downstream entity, wherein the penalty unit is configured to penalize one or more of the second downstream entity and the third downstream entity for failure to comply with one or more conditions of the distribution rule set.
  • Fig. 13 e.g., Fig.
  • FIG. 13B shows second transaction data receiving circuit configured to receive, from the particular architecture that is configured to implement the penalty unit, second transmission data indicating the second transmission of particular funds from the second downstream entity to the third downstream entity, wherein the penalty unit is configured to penalize one or more of the second downstream entity and the third downstream entity for failure to comply with one or more conditions of the distribution rule set 13 18 receiving, from the particular architecture that is configured to implement the penalty unit, second transmission data indicating the second transmission of particular funds from the second downstream entity to the third downstream entity, wherein the penalty unit is configured to penalize one or more of the second downstream entity (e.g., a hospital) and the third downstream entity (e.g., a doctor employee of the hospital) for failure to comply with one or more conditions of the distribution rule set (e.g., the doctor was paid too much money for the services rendered).
  • the second downstream entity e.g., a hospital
  • the third downstream entity e.g., a doctor employee of the hospital
  • operation 1718 may include operation 1720 depicting second transaction data receiving circuit configured to receive, from the particular architecture that is configured to implement the penalty unit, second transmission data indicating the second transmission of particular funds from the second downstream entity to the third downstream entity, wherein the penalty unit is configured to penalize one or more of the second downstream entity and the third downstream entity for failure to provide photographic and/or location data within a time period specified by the distribution rule set.
  • Fig. 13 e.g., Fig.
  • FIG. 13C shows second transaction data receiving circuit configured to receive, from the particular architecture that is configured to implement the penalty unit, second transmission data indicating the second transmission of particular funds from the second downstream entity to the third downstream entity, wherein the penalty unit is configured to penalize one or more of the second downstream entity and the third downstream entity for failure to provide photographic and/or location data within a time period specified by the distribution rule set 1320 receiving, from the particular architecture (e.g., the Daybreak architecture or similar other embodiemtns) that is configured to implement the penalty unit (e.g., a portion of the architecture, which, in an embodiment, may be part of the distribution rules set), second transmission data indicating the second transmission (e.g., movement within accounts under the control and management of the daybreak architecture) of particular funds from the second downstream entity (e.g., a government contractor) to the third downstream entity (e.g., a building supply contractor), wherein the penalty unit is configured to penalize one or more of the second downstream entitiy and the third downstream entity for failure to provide photographic and/
  • operation 1406 may include operation 1722 depicting second transaction data receiving circuit configured to receive second transaction data indicating that the second transmission of the particular funds from the second downstream entity to the third downstream entity has been approved.
  • Fig. 13 e.g., Fig. 13D
  • the second downstream entity e.g., a medical supply middle man
  • the third downstream entity e.g., a generic drug supplier
  • operation 1406 may include operation 1724, which may appear in conjunction with operation 1722, operation 1724 depicting second transmission data receiving circuit configured to receive second transmission data indicating the second transmission of the particular funds from the second downstream entity to the third downstream entity has been carried out.
  • operation 1724 depicting second transmission data receiving circuit configured to receive second transmission data indicating the second transmission of the particular funds from the second downstream entity to the third downstream entity has been carried out.
  • Fig. 13 e.g., Fig.
  • l3D shows second transmission data receiving circuit configured to receive second transmission data indicating the second transmission of the particular funds from the second downstream entity to the third downstream entity has been carried out 1324 receiving second transmission data indicating the second transmission of the particular funds from the second downstream entity (e.g., a food supplies vendor) to the third downstream entity (e.g., a beef supplier) has been carried out (e.g., the transaction has occurred in the Daybreak architecture and is ready for offboarding, which will involve a direct debiting of the particular funds as a real transaction but will appear in the Daybreak architecture as flowing through the various vendors.
  • the second downstream entity e.g., a food supplies vendor
  • the third downstream entity e.g., a beef supplier
  • operation 1722 may include operation 1726 depicting second transaction data receiving circuit configured to receive second transaction data indicating that the second transmission of the particular funds from the second downstream entity to the third downstream entity has been approved by a particular architecture.
  • Fig. 13 e.g., Fig.
  • FIGD shows second transaction data receiving circuit configured to receive second transaction data indicating that the second transmission of the particular funds from the second downstream entity to the third downstream entity has been approved by a particular architecture 1326 receiving second transaction data indicating that the second transmission of the particular funds (e.g., funds earmarked for penicillin) from the second downstream entity (e.g., a hospital) to the third downstream entity (e.g., a medical supplier) has been approvied by a particular architecture (e.g., the daybreak architecture).
  • a particular architecture e.g., the daybreak architecture
  • operation 1726 may include operation 1728 depicting second transaction data receiving circuit configured to receive second transaction data indicating that the second transmission of the particular funds from the second downstream entity to the third downstream entity has been approved by the particular architecture configured to manage the second transmission internally.
  • Fig. 13 e.g., Fig.
  • FIGD shows second transaction data receiving circuit configured to receive second transaction data indicating that the second transmission of the particular funds from the second downstream entity to the third downstream entity has been approved by the particular architecture configured to manage the second transmission internally 1328 receiving second transaction data indicating that the second transmission of the particular funds from the second downstream entity to the third downstream entity has been approved by the particular architecture configured to manage the second transmission internally (e.g., the transmission occurs solely within the accounts of the Daybreak architecture).
  • operation 1728 may include operation 1730 depicting second transaction data receiving circuit configured to receive second transaction data indicating that the second transmission of the particular funds from the second downstream entity to the third downstream entity has been approved by the particular architecture configured to manage the second transmission internally and to carry out the second transaction internally to the particular architecture.
  • Fig. 13 e.g., Fig.
  • FIG. 13D shows second transaction data receiving circuit configured to receive second transaction data indicating that the second transmission of the particular funds from the second downstream entity to the third downstream entity has been approved by the particular architecture configured to manage the second transmission internally and to carry out the second transaction internally to the particular architecture 1330 receiving second transaction data indicating that the second transmission of the aprticular funds from the second downstream entity to the third downstream entity has been approvied by the particular architecture (e.g., the Daybreak architecture or an embodiment that manages accounts) configured to manage the second transmission internally and to carry out the second transaction internally to the particular architecture (e.g., to a non-Daybreak architecture provided by a government of a foreign country that requires its use to distribute funds within the borders of its country).
  • the particular architecture e.g., the Daybreak architecture or an embodiment that manages accounts
  • operation 1722 may include operation 1732 depicting second transaction data receiving circuit configured to receive second transaction data indicating that the second transmission of the particular funds from the second downstream entity has been approved by a particular architecture configured to carry out transaction analysis of the second transaction data.
  • a particular architecture configured to carry out transaction analysis of the second transaction data.
  • FIGE shows second transaction data receiving circuit configured to receive second transaction data indicating that the second transmission of the particular funds from the second downstream entity has been approved by a particular architecture configured to carry out transaction analysis of the second transaction data 1332 receiving second transaction data indicating that the second transmission of the particular funds from the second downstream entity has been approved by a particular architecture configured to carry out transaction analysis (e.g., an analysis of whether the transaction is likely to be fraudulent, or an analysis to determine whether the transaction complies with a specific part of the distribution rule set, e.g., does the vendor meet the criteria specified in the distribution rule set for a transfer of over ten thousand dollars on a weekday).
  • transaction analysis e.g., an analysis of whether the transaction is likely to be fraudulent, or an analysis to determine whether the transaction complies with a specific part of the distribution rule set, e.g., does the vendor meet the criteria specified in the distribution rule set for a transfer of over ten thousand dollars on a weekday.
  • operation 1722 may include operation 1734 depicting second transaction data receiving circuit configured to receive second transaction data indicating that the second transmission of the particular funds from the second downstream entity has been approved by the particular architecture configured to carry out fraud analysis of the second transaction data.
  • Fig. 13 e.g., Fig.
  • FIG. 13E shows second transaction data receiving circuit configured to receive second transaction data indicating that the second transmission of the particular funds from the second downstream entity has been approved by the particular architecture configured to carry out fraud analysis of the second transaction data 1334 receiving second transaction data indicating that the second transmission of the particular funds from the second downstream entity has been approved by the particular architecture configured to carry out fraud analysis (e.g., an analysis of whether the transaction is likely to be fraudulent, with possible outcomes of "PASS,” which allows the transaction, "DENY,” which denies the transaction, or "FLAG” which holds up the transaction until another system can evaluate the transaction, e.g., a more complex or different fraud analysis that may use more information or apply in a different manner, or a human intervention to manually approve or deny the transaction) of the second transaction data (e.g., a transaction to pay a hospital for syringes and cold storage).
  • fraud analysis e.g., an analysis of whether the transaction is likely to be fraudulent, with possible outcomes of "PASS,” which allows the transaction, "DENY,” which denies the
  • operation 1734 may include operation 1736 depicting second transaction data receiving circuit configured to receive second transaction data indicating that the second transmission of the particular funds from the second downstream entity has been approved by the particular architecture configured to carry out fraud analysis of the second transaction data that detects whether any of the first downstream entity, the second downstream entity, and the third downstream entity, are phantom vendors.
  • operation 1736 depicting second transaction data receiving circuit configured to receive second transaction data indicating that the second transmission of the particular funds from the second downstream entity has been approved by the particular architecture configured to carry out fraud analysis of the second transaction data that detects whether any of the first downstream entity, the second downstream entity, and the third downstream entity, are phantom vendors.
  • Fig. 13 e.g., Fig.
  • FIGE shows second transaction data receiving circuit configured to receive second transaction data indicating that the second transmission of the particular funds from the second downstream entity has been approved by the particular architecture configured to carry out fraud analysis of the second transaction data that detects whether any of the first downstream entity, the second downstream entity, and the third downstream entity, are phantom vendors 1336 receiving second transaction data indicating that the second transmission of the particular funds from the second downstream entity has been approved by the particular architecture configured to carry out fraud analysis of the second transaction data that detects whether any of the first downstream entity, the second downstream entity, and the third downstream entity, are phantom vendors (e.g., shell vendors that do not actually exist except as vehicles by which bad actors can siphon off money and/or funds that are earmarked for specific projects, e.g., charitable work)
  • phantom vendors e.g., shell vendors that do not actually exist except as vehicles by which bad actors can siphon off money and/or funds that are earmarked for specific projects, e.g., charitable work
  • operation 1734 may include operation 1738 depicting second transaction data receiving circuit configured to receive second transaction data indicating that the second transmission of the particular funds from the second downstream entity has been approved by the particular architecture configured to detect one or more phantom vendors.
  • Fig. 13, e.g., Fig. 13F shows second transaction data receiving circuit configured to receive second transaction data indicating that the second transmission of the particular funds from the second downstream entity has been approved by the particular architecture configured to detect one or more phantom vendors 1338 receiving second transaction data indicating that the second transmission of the particular funds from the second downstream entity has been approved by the particular architecture (e.g., the Daybreak architecture) configured to detect one or more phantom vendors.
  • the particular architecture e.g., the Daybreak architecture
  • operation 1738 may include operation 1740 depicting second transaction data receiving circuit configured to receive second transaction data indicating that the second transmission of the particular funds from the second downstream entity has been approved by the particular architecture configured to detect one or more phantom vendors through generation of a suspicion score for each transaction.
  • Fig. 13 e.g., Fig.
  • FIG. 13F shows second transaction data receiving circuit configured to receive second transaction data indicating that the second transmission of the particular funds from the second downstream entity has been approved by the particular architecture configured to detect one or more phantom vendors through generation of a suspicion score for each transaction 1340 receiving second transaction data indicating that the second transmission of the particular funds from the second downstream entity has been approved by the particular architecture configured to detect one or more phantom vendors (e.g., shell vendors that do not actually exist except as vehicles by which bad actors can siphon off money and/or funds that are earmarked for specific projects, e.g., charitable work) through generation of a suspicion score for each transaction.
  • phantom vendors e.g., shell vendors that do not actually exist except as vehicles by which bad actors can siphon off money and/or funds that are earmarked for specific projects, e.g., charitable work
  • operation 1740 may include operation 1742 depicting second transaction data receiving circuit configured to receive second transaction data indicating that the second transmission of the particular funds from the second downstream entity has been approved by the particular architecture configured to detect one or more phantom vendors through generation of a suspicion score for each transaction based on one or more of time of establishment of vendor, vendor mailing address, single invoicee, vendor name characteristics, vendor invoice characteristics, time of transaction, date of transaction, approver credential, and reputation score.
  • Fig. 13 e.g., Fig.
  • 13E shows second transaction data receiving circuit configured to receive second transaction data indicating that the second transmission of the particular funds from the second downstream entity has been approved by the particular architecture configured to detect one or more phantom vendors through generation of a suspicion score for each transaction based on one or more of time of establishment of vendor, vendor mailing address, single invoicee, vendor name characteristics, vendor invoice characteristics, time of transaction, date of transaction, approver credential, and reputation score 1342 receiving second transaction data indicating that the second transmission of the particular funds from the second downstream entity has been approved by the particular architecture configured to detect one or more phantom vendors through generation of a suspicion score for each transaction based on one or more of time of establishment of vendor (e.g., the shorter amount of time a vendor has been in business, the more suspect the vendor is), vendor mailing address (e.g., a nonverifiable address is more suspect), single invoicee, vendor name characteristics (e.g., a shorter name is more suspect), vendor invoice characteristics, time of transaction, date of transaction, approver credential, and reputation score
  • At least one input acceptance machine 252 may be specified to establish at least one track data presentation machine state, which, in an embodiment, may be implemented as at least one second track data presentation machine state of said first-party-associated device, said at least one second track data presentation machine state set to a value 620.
  • At least one first track data presentation machine 254 may be specified to establish at least one track data presentation machine state, which, in an embodiment, may be implemented as at least one second track data presentation machine state of said first-party-associated device (e.g., a wearable computer, e.g., Apple Watch, Microsoft HoloLens, etc.), said at least one second track data presentation machine state set to a value (e.g., a value set responsive to one or more machine states, as described in more detail herein).
  • a wearable computer e.g., Apple Watch, Microsoft HoloLens, etc.
  • a computationally-implemented method comprising:
  • a financial entity is an entity that has registered with the particular architecture.
  • receiving input at a first party device said input that regards the attributable account that contains attributable funds and that is configured to interface with one or more financial entities.
  • said receiving input at a first party device, said input that regards the attributable account that contains attributable funds and that is configured to interface with one or more financial entities comprises:
  • the first party device receives input at the first party device, said input that regards the attributable account that contains attributable funds and that is configured to interface with one or more financial entities, wherein the first party device is one or more of a smartphone device, mobile device, laptop computer, desktop computer, wearable device, augmented reality device, in-vehicle device, heads up display, and a thin client.
  • the first party device is one or more of a smartphone device, mobile device, laptop computer, desktop computer, wearable device, augmented reality device, in-vehicle device, heads up display, and a thin client.
  • accepting input that regards an attributable account that contains attributable funds that are governed by a distribution rule set that links metadata to the account and to one or more transactions associated with the account comprises:
  • accepting input accepting input that regards the attributable account that contains attributable funds that are governed by the distribution rule set that links identifier metadata to the attributable account and that links transaction information metadata to each transaction associated with the account, wherein the transaction information includes a receiving party name, a time of transaction, and an underlying bank data for each bank involved in the transaction.
  • first transaction data indicating the first transmission of particular funds from the first downstream entity to the second downstream entity, wherein the particular funds are part of the attributable funds.
  • first transaction data indicating the first transmission of particular funds from the first downstream entity to the second downstream entity, wherein the particular funds are part of the attributable funds.
  • said receiving first transaction data indicating the first transmission of particular funds from the representation of the first downstream entity to the representation of the second downstream entity, wherein the representation of the first downstream entity and the representation of the second downstream entity are part of a particular architecture comprises:
  • first transaction data indicating the first transmission of particular funds from the representation of the first downstream entity to the representation of the second downstream entity, wherein the representation of the first downstream entity is an account associated with the first downstream entity, and the representation of the second downstream entity is an account associated with the second downstream entity.
  • first transaction data indicating the first transmission of particular funds from a first architecture account managed by the particular architecture and associated with the first downstream entity to a second architecture account managed by the particular architecture and associated with the second downstream entity.
  • said receiving first transaction data indicating the first transmission of particular funds from a first architecture account representation of the first downstream entity to a second architecture account representation of the second downstream entity comprises:
  • first transaction data indicating the first transmission of particular funds from the first architecture account representation of the first downstream entity to the architecture account representation of the second downstream entity, wherein the second architecture account representation of the second downstream entity is an account that was registered with the architecture by the second downstream entity.
  • first transaction data indicating the first transmission of particular funds from the first downstream entity to the second downstream entity, wherein the particular funds represent a portion of the attributable funds that are owned by a single entity, and the attributable funds are owned by more than one entity but are stored in a single underlying bank account.
  • said receiving first transaction data indicating a first transmission of particular funds from a first downstream entity to a second downstream entity, wherein the particular funds are part of the attributable funds comprises: receiving first transaction data indicating that the first transmission of particular funds is compliant with the distribution rule set that requires that one or more of the first, second, and third downstream entities are trusted entities.
  • the penalty unit is configured to penalize one or more of the second downstream entity and the third downstream entity based on the distribution rule set.
  • the penalty unit is configured to penalize one or more of the second downstream entity and the third downstream entity for failure to comply with one or more conditions of the distribution rule set.
  • the penalty unit is configured to penalize one or more of the second downstream entity and the third downstream entity for failure to provide photographic and/or location data within a time period specified by the distribution rule set.
  • receiving second transaction data indicating that the second transmission of the particular funds from the second downstream entity has been approved by the particular architecture configured to carry out fraud analysis of the second transaction data comprises: receiving second transaction data indicating that the second transmission of the particular funds from the second downstream entity has been approved by the particular architecture configured to carry out fraud analysis of the second transaction data that detects whether any of the first downstream entity, the second downstream entity, and the third downstream entity, are phantom vendors.
  • receiving second transaction data indicating that the second transmission of the particular funds from the second downstream entity has been approved by the particular architecture configured to detect one or more phantom vendors comprises:
  • a computationally-implemented system comprising:
  • first transaction data indicating a first transmission of particular funds from a first downstream entity to a second downstream entity, wherein the particular funds are part of the attributable funds
  • said means for receiving input at a first party device, said input that regards the attributable account that contains attributable funds and that is configured to interface with one or more financial entities comprises: means for receiving input at the first party device, said input that regards the attributable account that contains attributable funds and that is configured to interface with one or more financial entities, wherein the first party device is one or more of a smartphone device, mobile device, laptop computer, desktop computer, wearable device, augmented reality device, in-vehicle device, heads up display, and a thin client.
  • first transaction data indicating the first transmission of particular funds from the first downstream entity to the second downstream entity, wherein the particular funds are part of the attributable funds.
  • first transaction data indicating the first transmission of particular funds from the first downstream entity to the second downstream entity, wherein the particular funds are part of the attributable funds.
  • first transaction data indicating the first transmission of particular funds from the first downstream entity to the second downstream entity, wherein the particular funds are part of the attributable funds.
  • first transaction data indicating the first transmission of particular funds from the representation of the first downstream entity to the representation of the second downstream entity, wherein the representation of the first downstream entity is an account associated with the first downstream entity, and the representation of the second downstream entity is an account associated with the second downstream entity.
  • first transaction data indicating the first transmission of particular funds from a first architecture account managed by the particular architecture and associated with the first downstream entity to a second architecture account managed by the particular architecture and associated with the second downstream entity.
  • first transaction data indicating a received request to transmit particular funds from the first downstream entity to the second downstream entity
  • first transaction data indicating a first transmission of particular funds from a representation of the first downstream entity to a representation of the second downstream entity, wherein the particular funds are not transferred from the first downstream entity to the downstream entity
  • first transaction data indicating the first transmission of particular funds from the representation of the first downstream entity to the representation of the second downstream entity, wherein the representation of the first downstream entity and the representation of the second downstream entity are part of a particular architecture.
  • first transaction data indicating the first transmission of particular funds from a first architecture account representation of the first downstream entity to a second architecture account representation of the second downstream entity.
  • first transaction data indicating the first transmission of particular funds from the first architecture account representation of the first downstream entity to the architecture account representation of the second downstream entity, wherein the second architecture account representation of the second downstream entity is an account that was registered with the architecture by the second downstream entity.
  • first transaction data indicating the first transmission of particular funds from the first downstream entity to the second downstream entity, wherein the particular funds represent a portion of the attributable funds that are owned by a single entity, and the attributable funds are owned by more than one entity.
  • Attributable funds represent a portion of the attributable funds that are owned by a single entity, and the attributable funds are owned by more than one entity comprises:
  • first transaction data indicating the first transmission of particular funds from the first downstream entity to the second downstream entity, wherein the particular funds represent a portion of the attributable funds that are owned by a single entity, and the attributable funds are owned by more than one entity but are stored in a single underlying bank account.
  • first downstream entity is a local domestic bank and the second downstream entity is a national domestic bank.
  • first downstream entity is a national domestic bank and the second downstream entity is a European bank.
  • first downstream entity is a European bank and the second downstream entity is a foreign non-European bank.
  • first downstream entity is a foreign non-European bank and the second downstream entity is a foreign organization.
  • first downstream entity is a first foreign organization and the second downstream entity is a second foreign organization.
  • first transaction data indicating the first transmission of particular funds from the first downstream entity to the second downstream entity, wherein the first transmission of particular funds occurs within a particular architecture.
  • first transaction data indicating the first transmission of particular funds from the first downstream entity to the second downstream entity, wherein the first transmission of particular funds occurs within the particular architecture that performs verification of the first transmission before allowing the first transmission.
  • first transaction data indicating that the first transmission of particular funds is compliant with the distribution rule set that requires that one or more of the first, second, and third downstream entities are trusted entities as established by a particular architecture that tracks one or more reputation scores of the one or more of the first, second, and third downstream entities.
  • the penalty unit is configured to penalize one or more of the second downstream entity and the third downstream entity for failure to comply with one or more conditions of the distribution rule set.
  • the penalty unit is configured to penalize one or more of the second downstream entity and the third downstream entity for failure to provide photographic and/or location data within a time period specified by the distribution rule set.
  • means for receiving second transaction data indicating that the second transmission of the particular funds from the second downstream entity has been approved by the particular architecture configured to detect one or more phantom vendors through generation of a suspicion score for each transaction based on one or more of time of establishment of vendor, vendor mailing address, single invoicee, vendor name characteristics, vendor invoice characteristics, time of transaction, date of transaction, approver credential, and reputation score.
  • a computationally-implemented system comprising:
  • circuitry for accepting input that regards an attributable account that contains attributable funds and that is configured to interface with one or more financial entities, wherein the attributable funds are governed by a distribution rule set;
  • circuitry for receiving first transaction data indicating a first transmission of particular funds from a first downstream entity to a second downstream entity, wherein the particular funds are part of the attributable funds
  • circuitry for receiving second transaction data indicating a second transmission of the particular funds from the second downstream entity to the third downstream entity.
  • circuitry for accepting input that regards an attributable account that contains attributable funds and that is configured to interface with one or more financial entities, wherein the attributable funds are governed by a distribution rule set comprises:
  • circuitry for accepting input that regards a request for presentation a transaction history of the attributable account that contains attributable funds and that is configured to interface with one or more financial entities, wherein the attributable funds are governed by a distribution rule set.
  • circuitry for accepting input that regards an attributable account that contains attributable funds and that is configured to interface with one or more financial entities, wherein the attributable funds are governed by a distribution rule set comprises:
  • circuitry for receiving input that regards the attributable account that contains attributable funds and that is configured to interface with one or more financial entities.
  • circuitry for receiving input that regards the attributable account that contains attributable funds and that is configured to interface with one or more financial entities comprises:
  • circuitry for receiving input from a user, said input that regards the attributable account that contains attributable funds and that is configured to interface with one or more financial entities.
  • circuitry for receiving input that regards the attributable account that contains attributable funds and that is configured to interface with one or more financial entities comprises:
  • circuitry for receiving input at a first party device, said input that regards the attributable account that contains attributable funds and that is configured to interface with one or more financial entities.
  • circuitry for receiving input at a first party device, said input that regards the attributable account that contains attributable funds and that is configured to interface with one or more financial entities comprises: circuitry for receiving input at the first party device, said input that regards the attributable account that contains attributable funds and that is configured to interface with one or more financial entities, wherein the first party device is one or more of a smartphone device, mobile device, laptop computer, desktop computer, wearable device, augmented reality device, in-vehicle device, heads up display, and a thin client.
  • circuitry for receiving input at a first party device, said input that regards the attributable account that contains attributable funds and that is configured to interface with one or more financial entities comprises: circuitry for receiving input from the user at an input/output interface of the first party device, said input that regards the attributable account that contains attributable funds and that is configured to interface with one or more financial entities.
  • circuitry for receiving input from the user at an input/output interface of the first party device, said input that regards the attributable account that contains attributable funds and that is configured to interface with one or more financial entities comprises:
  • circuitry for receiving input from the user at a touchscreen interface of the first party device, said input that regards the attributable account that contains attributable funds and that is configured to interface with one or more financial entities.
  • circuitry for accepting input that regards an attributable account that contains attributable funds and that is configured to interface with one or more financial entities, wherein the attributable funds are governed by a distribution rule set comprises:
  • circuitry for accepting a request related to the attributable account that contains the attributable funds and that is configured to interface with one or more financial entities.
  • circuitry for accepting input that regards an attributable account that contains attributable funds and that is configured to interface with one or more financial entities, wherein the attributable funds are governed by a distribution rule set comprises:
  • circuitry for accepting a request to view at least a portion of the attributable account that contains the attributable funds and that is configured to interface with one or more financial entities comprises:
  • circuitry for accepting the request to view the last ten transactions carried out in the attributable account that contains the attributable funds and that is configured to interface with one or more financial entities.
  • circuitry for accepting a request to view at least a portion of the attributable account that contains the attributable funds and that is configured to interface with one or more financial entities comprises:
  • circuitry for accepting the request to view the last ten rejected transactions requested in the attributable account that contains the attributable funds and that is configured to interface with one or more financial entities, wherein the rejected transactions were rejected for failure to comply with the distribution rule set.
  • circuitry for accepting a request to view at least a portion of the attributable account that contains the attributable funds and that is configured to interface with one or more financial entities comprises:
  • circuitry for accepting the request to view an account balance of the attributable account that contains the attributable funds and that is configured to interface with one or more financial entities.
  • circuitry for accepting a request to view at least a portion of the attributable account that contains the attributable funds and that is configured to interface with one or more financial entities comprises:
  • circuitry for accepting the request to view a distribution map of the attributable funds between the first downstream entity, the second downstream entity, and the third downstream entity comprises:
  • circuitry for accepting the request to view a real-time or near-real-time tracking of the attributable funds between the first downstream entity, the second downstream entity, and the third downstream entity.
  • circuitry for accepting a request to view at least a portion of the attributable account that contains the attributable funds and that is configured to interface with one or more financial entities comprises:
  • circuitry for accepting the request to view a current location of the attributable funds between the first downstream entity, the second downstream entity, and the third downstream entity, within their representations in a particular architecture.
  • circuitry for accepting the request to view a current location of the attributable funds between the first downstream entity, the second downstream entity, and the third downstream entity, within their representations in a particular architecture comprises:
  • circuitry for accepting the request to view the current location of the attributable funds between the first downstream entity, the second downstream entity, and the third downstream entity, within their individual account representations within the particular architecture that has an individual account associated with each downstream entity.
  • circuitry for accepting a request to view at least a portion of the attributable account that contains the attributable funds and that is configured to interface with one or more financial entities comprises:
  • circuitry for accepting the request to view at least a partial list of goods and/or services purchased or directed to purchase with the attributable funds by one or more of the first downstream entity, the second downstream entity, and the third downstream entity, and/or one or more agents of the first downstream entity, the second downstream entity, and the third downstream entity.
  • circuitry for accepting a request to view at least a portion of the attributable account that contains the attributable funds and that is configured to interface with one or more financial entities comprises:
  • circuitry for accepting the request to view at least a partial list of goods and/or services distributed or directed to distribute with the attributable funds by one or more of the first downstream entity, the second downstream entity, and the third downstream entity, and/or one or more agents of the first downstream entity, the second downstream entity, and the third downstream entity.
  • circuitry for accepting a request to view at least a portion of the attributable account that contains the attributable funds and that is configured to interface with one or more financial entities comprises:
  • circuitry for accepting the request to view verification information of at least a partial list of goods and/or services associated with the attributable funds by one or more of the first downstream entity, the second downstream entity, and the third downstream entity, and/or one or more agents of the first downstream entity, the second downstream entity, and the third downstream entity.
  • circuitry for accepting input that regards an attributable account that contains attributable funds and that is configured to interface with one or more financial entities, wherein the attributable funds are governed by a distribution rule set comprises:
  • circuitry for accepting input that regards an attributable account that contains attributable funds that are governed by a distribution rule set that links metadata to the account and to one or more transactions associated with the account.
  • circuitry for accepting input that regards an attributable account that contains attributable funds that are governed by a distribution rule set that links metadata to the account and to one or more transactions associated with the account comprises:
  • circuitry for accepting input that regards the attributable account that contains attributable funds that are governed by the distribution rule set that links identifier metadata to the attributable account and that links transaction information metadata to each transaction associated with the account.
  • circuitry for accepting input that regards the attributable account that contains attributable funds that are governed by the distribution rule set that links identifier metadata to the attributable account and that links transaction information metadata to each transaction associated with the account comprises:
  • circuitry for accepting input accepting input that regards the attributable account that contains attributable funds that are governed by the distribution rule set that links identifier metadata to the attributable account and that links transaction information metadata to each transaction associated with the account, wherein the transaction information includes a receiving party name, a time of transaction, and an underlying bank data for each bank involved in the transaction.
  • circuitry for accepting input that regards an attributable account that contains attributable funds and that is configured to interface with one or more financial entities, wherein the attributable funds are governed by a distribution rule set comprises:
  • circuitry for accepting input that regards an attributable account that contains attributable funds that are governed by a distribution rule set that links location data to one or more transactions associated with the account comprises:
  • circuitry for accepting input that regards the attributable account that contains attributable funds that are governed by the distribution rule set that links location data obtained from a global positioning system to locations of one or more transactions associated with the account.
  • circuitry for accepting input that regards an attributable account that contains attributable funds that are governed by a distribution rule set that links location data to one or more transactions associated with the account comprises:
  • circuitry for accepting input that regards the attributable account that contains attributable funds that are governed by the distribution rule set that links location data obtained from tracking beacons associated with one or more goods purchased from attributable funds of the attributable account.
  • circuitry for accepting input that regards an attributable account that contains attributable funds and that is configured to interface with one or more financial entities, wherein the attributable funds are governed by a distribution rule set comprises:
  • circuitry for accepting input that regards an attributable account that contains attributable funds that are governed by a distribution rule set that governs fees that are associated with one or more transactions associated with the attributable funds of the attributable account comprises:
  • circuitry for accepting input that regards the attributable account that contains attributable funds that are governed by the distribution rule set that sets a percentage-of- transaction fee limit that is associated with the attributable funds of the attributable account.
  • circuitry for accepting input that regards an attributable account that contains attributable funds and that is configured to interface with one or more financial entities, wherein the attributable funds are governed by a distribution rule set comprises:
  • circuitry for accepting input that regards the attributable account that contains attributable funds that are governed by the distribution rule set that requires photographic evidence of spending associated with one or more transactions associated with the attributable funds of the attributable account.
  • circuitry for accepting input that regards the attributable account that contains attributable funds that are governed by the distribution rule set that requires photographic evidence of spending associated with one or more transactions associated with the attributable funds of the attributable account comprises:
  • circuitry for accepting input that regards the attributable account that contains attributable funds that are governed by the distribution rule set that requires digital photographic data of evidence of spending associated with one or more transactions associated with the attributable funds of the attributable account to be included with data of the attributable funds.
  • circuitry for accepting input that regards an attributable account that contains attributable funds and that is configured to interface with one or more financial entities, wherein the attributable funds are governed by a distribution rule set comprises:
  • circuitry for accepting input that regards an attributable account that contains attributable funds that are governed by a distribution rule set that specifies particular spending limits for one or more goods and/or services that are acquired through one or more transactions associated with the attributable funds of the attributable account.
  • circuitry for accepting input that regards an attributable account that contains attributable funds that are governed by a distribution rule set that specifies particular spending limits for one or more goods and/or services that are acquired through one or more transactions associated with the attributable funds of the attributable account comprises:
  • circuitry for accepting input that regards the attributable account that contains the attributable funds that are governed by the distribution rule set that specifies the particular spending limits for one or more classes of goods that are acquired through one or more transactions associated with the attributable funds of the attributable account.
  • circuitry for accepting input that regards the attributable account that contains the attributable funds that are governed by the distribution rule set that specifies the particular spending limits for one or more classes of goods that are acquired through one or more transactions associated with the attributable funds of the attributable account comprises:
  • circuitry for accepting input that regards the attributable account that contains the attributable funds that are governed by the distribution rule set that specifies the particular spending limits for one or more classes of goods, including food, medicine, construction costs, worker salaries, and concrete supplies.
  • circuitry for accepting input that regards an attributable account that contains attributable funds and that is configured to interface with one or more financial entities, wherein the attributable funds are governed by a distribution rule set comprises:
  • circuitry for accepting input that regards an attributable account that contains attributable funds that are governed by a distribution rule set that calculates a potential fraud score for each transaction and determines whether to allow access to the attributable funds of the attributable account at least partially based on the fraud score calculation.
  • circuitry for receiving first transaction data indicating a first transmission of particular funds from a first downstream entity to a second downstream entity, wherein the particular funds are part of the attributable funds comprises:
  • circuitry for receiving, from a particular architecture, first transaction data indicating the first transmission of particular funds from the first downstream entity to the second downstream entity, wherein the particular funds are part of the attributable funds.
  • circuitry for receiving, from a particular architecture, first transaction data indicating the first transmission of particular funds from the first downstream entity to the second downstream entity, wherein the particular funds are part of the attributable funds comprises:
  • circuitry for receiving, from the particular architecture that is configured to handle the first transaction data and the second transaction data, first transaction data indicating the first transmission of particular funds from the first downstream entity to the second downstream entity, wherein the particular funds are part of the attributable funds.
  • circuitry for receiving, from the particular architecture that is configured to handle the first transaction data and the second transaction data, first transaction data indicating the first transmission of particular funds from the first downstream entity to the second downstream entity, wherein the particular funds are part of the attributable funds comprises:
  • circuitry for receiving, from the particular architecture that is configured to handle the first transaction data and the second transaction data entirely internally to the particular architecture, first transaction data indicating the first transmission of particular funds from the first downstream entity to the second downstream entity, wherein the particular funds are part of the attributable funds.
  • circuitry for receiving first transaction data indicating a first transmission of particular funds from a first downstream entity to a second downstream entity, wherein the particular funds are part of the attributable funds comprises:
  • circuitry for receiving first transaction data indicating the first transmission of particular funds from a representation of the first downstream entity to a representation of the second downstream entity comprises:
  • circuitry for receiving first transaction data indicating the first transmission of particular funds from the representation of the first downstream entity to the representation of the second downstream entity, wherein the representation of the first downstream entity and the representation of the second downstream entity are part of a particular architecture.
  • circuitry for receiving first transaction data indicating the first transmission of particular funds from the representation of the first downstream entity to the representation of the second downstream entity, wherein the representation of the first downstream entity and the representation of the second downstream entity are part of a particular architecture comprises:
  • circuitry for receiving first transaction data indicating the first transmission of particular funds from the representation of the first downstream entity to the representation of the second downstream entity, wherein the representation of the first downstream entity is an account associated with the first downstream entity, and the representation of the second downstream entity is an account associated with the second downstream entity.
  • circuitry for receiving first transaction data indicating the first transmission of particular funds from the representation of the first downstream entity to the representation of the second downstream entity, wherein the representation of the first downstream entity is an account associated with the first downstream entity, and the representation of the second downstream entity is an account associated with the second downstream entity comprises:
  • circuitry for receiving first transaction data indicating the first transmission of particular funds from a first architecture account managed by the particular architecture and associated with the first downstream entity to a second architecture account managed by the particular architecture and associated with the second downstream entity.
  • circuitry for receiving first transaction data indicating a first transmission of particular funds from a first downstream entity to a second downstream entity, wherein the particular funds are part of the attributable funds comprises:
  • circuitry for receiving first transaction data indicating a received request to transmit particular funds from the first downstream entity to the second downstream entity;
  • circuitry for receiving first transaction data indicating a first transmission of particular funds from a representation of the first downstream entity to a representation of the second downstream entity, wherein the particular funds are not transferred from the first downstream entity to the downstream entity.
  • circuitry for receiving first transaction data indicating a first transmission of particular funds from a representation of the first downstream entity to a representation of the second downstream entity comprises:
  • circuitry for receiving first transaction data indicating the first transmission of particular funds from the representation of the first downstream entity to the representation of the second downstream entity, wherein the representation of the first downstream entity and the representation of the second downstream entity are part of a particular architecture.
  • circuitry for receiving first transaction data indicating a first transmission of particular funds from a representation of the first downstream entity to a representation of the second downstream entity comprises:
  • circuitry for receiving first transaction data indicating the first transmission of particular funds from a first architecture account representation of the first downstream entity to a second architecture account representation of the second downstream entity.
  • circuitry for receiving first transaction data indicating the first transmission of particular funds from a first architecture account representation of the first downstream entity to a second architecture account representation of the second downstream entity comprises:
  • circuitry for receiving first transaction data indicating the first transmission of particular funds from the first architecture account representation of the first downstream entity to the architecture account representation of the second downstream entity, wherein the first architecture account representation of the first downstream entity is an account that was registered with the architecture by the first downstream entity.
  • circuitry for receiving first transaction data indicating the first transmission of particular funds from a first architecture account representation of the first downstream entity to a second architecture account representation of the second downstream entity comprises:
  • circuitry for receiving first transaction data indicating the first transmission of particular funds from the first architecture account representation of the first downstream entity to the architecture account representation of the second downstream entity, wherein the second architecture account representation of the second downstream entity is an account that was registered with the architecture by the second downstream entity.
  • circuitry for receiving first transaction data indicating a first transmission of particular funds from a first downstream entity to a second downstream entity, wherein the particular funds are part of the attributable funds comprises:
  • circuitry for receiving first transaction data indicating the first transmission of particular funds from the first downstream entity to the second downstream entity, wherein the particular funds represent a portion of the attributable funds.
  • circuitry for receiving first transaction data indicating a first transmission of particular funds from a first downstream entity to a second downstream entity, wherein the particular funds are part of the attributable funds comprises:
  • circuitry for receiving first transaction data indicating the first transmission of particular funds from the first downstream entity to the second downstream entity, wherein the particular funds represent a portion of the attributable funds, wherein the attributable funds are owned by a single entity.
  • circuitry for receiving first transaction data indicating a first transmission of particular funds from a first downstream entity to a second downstream entity, wherein the particular funds are part of the attributable funds comprises:
  • circuitry for receiving first transaction data indicating the first transmission of particular funds from the first downstream entity to the second downstream entity, wherein the particular funds represent a portion of the attributable funds that are owned by a single entity, and the attributable funds are owned by more than one entity.
  • circuitry for receiving first transaction data indicating the first transmission of particular funds from the first downstream entity to the second downstream entity, wherein the particular funds represent a portion of the attributable funds that are owned by a single entity, and the attributable funds are owned by more than one entity comprises:
  • circuitry for receiving first transaction data indicating the first transmission of particular funds from the first downstream entity to the second downstream entity, wherein the particular funds represent a portion of the attributable funds that are owned by a single entity, and the attributable funds are owned by more than one entity but are stored in a single underlying bank account.
  • circuitry for receiving first transaction data indicating a first transmission of particular funds from a first downstream entity to a second downstream entity, wherein the particular funds are part of the attributable funds comprises:
  • circuitry for receiving first transaction data indicating the first transmission of the particular funds from the first downstream entity to the second downstream entity, wherein the first downstream entity is a local domestic bank and the second downstream entity is a national domestic bank.
  • circuitry for receiving first transaction data indicating a first transmission of particular funds from a first downstream entity to a second downstream entity, wherein the particular funds are part of the attributable funds comprises:
  • circuitry for receiving first transaction data indicating the first transmission of the particular funds from the first downstream entity to the second downstream entity, wherein the first downstream entity is a national domestic bank and the second downstream entity is a European bank.
  • circuitry for receiving first transaction data indicating a first transmission of particular funds from a first downstream entity to a second downstream entity, wherein the particular funds are part of the attributable funds comprises:
  • circuitry for receiving first transaction data indicating a first transmission of particular funds from a first downstream entity to a second downstream entity, wherein the particular funds are part of the attributable funds comprises:

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Engineering & Computer Science (AREA)
  • Strategic Management (AREA)
  • Finance (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • Theoretical Computer Science (AREA)
  • Development Economics (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Game Theory and Decision Science (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Computer Security & Cryptography (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Abstract

L'invention concerne des machines, des procédés, des compositions de matière et des articles qui comprennent au moins une machine d'acceptation d'entrée et au moins un dispositif de présentation de données de suivi. En outre, d'autres aspects sont décrits dans les revendications, les dessins et le texte.
PCT/US2017/058146 2016-10-24 2017-10-24 Machines/articles/compositions/processus pour le suivi d'efforts philantropiques et/ou d'autres efforts WO2018081169A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US15/331,949 US20170330250A1 (en) 2015-06-02 2016-10-24 Machine/Article/Composition/Process State(s) for Tracking Philanthropic And/or Other Efforts
US15/331,949 2016-10-24
US15/331,948 2016-10-24
US15/331,948 US20170046670A1 (en) 2015-06-02 2016-10-24 Machine/Article/Composition/Process State(s) for Tracking Philanthropic And/or Other Efforts

Publications (1)

Publication Number Publication Date
WO2018081169A1 true WO2018081169A1 (fr) 2018-05-03

Family

ID=60484440

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2017/058146 WO2018081169A1 (fr) 2016-10-24 2017-10-24 Machines/articles/compositions/processus pour le suivi d'efforts philantropiques et/ou d'autres efforts

Country Status (1)

Country Link
WO (1) WO2018081169A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111369096A (zh) * 2019-12-06 2020-07-03 广东联晟通信科技有限公司 一种农村财政资金使用情况核查系统和方法

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150127525A1 (en) * 2013-11-07 2015-05-07 Ebay Inc. Dye pach: systems and methods for ach fund tracking

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150127525A1 (en) * 2013-11-07 2015-05-07 Ebay Inc. Dye pach: systems and methods for ach fund tracking

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111369096A (zh) * 2019-12-06 2020-07-03 广东联晟通信科技有限公司 一种农村财政资金使用情况核查系统和方法

Similar Documents

Publication Publication Date Title
Allessie et al. Blockchain for digital government
US10997251B2 (en) Smart device
Nawari et al. Blockchain and building information modeling (BIM): Review and applications in post-disaster recovery
US20170330250A1 (en) Machine/Article/Composition/Process State(s) for Tracking Philanthropic And/or Other Efforts
Omar et al. Enhancing vendor managed inventory supply chain operations using blockchain smart contracts
Sadouskaya Adoption of blockchain technologyin supply chain and logistics
KR102544052B1 (ko) 코드 체인 기반 모델, 장치, 시스템, 방법 및 애플리케이션
Bagloee et al. Blockchain: The operating system of smart cities
US20170293898A1 (en) Static ctyptographic currency value
US20160358267A1 (en) Machine/article/composition/process state(s) for tracking philanthropic and/or other efforts
US20170046670A1 (en) Machine/Article/Composition/Process State(s) for Tracking Philanthropic And/or Other Efforts
JP2020512614A (ja) 地図アプリケーションのブロックチェーンベースのクラウドソーシング
US20240046230A1 (en) Systems and methods for hyperledger-based payment transactions, alerts, and dispute settlement, using smart contracts
US20160379312A1 (en) Machine/article/composition/process state(s) for tracking philanthropic and/or other efforts
US20230237349A1 (en) Digital consolidation
US20240007506A1 (en) Enterprise account aggregation and visualization system
Șcheau et al. A cryptocurrency spectrum short analysis
WO2016196786A1 (fr) États de machine/article/composition/processus pour le suivi d'efforts philantropiques et/ou d'autres efforts
Boiardi et al. To what extent can blockchain help development co-operation actors meet the 2030 Agenda?
Chandra et al. Blockchain for property
Beck et al. Study on the economic impact of blockchain on the danish industry and labor market
WO2018081169A1 (fr) Machines/articles/compositions/processus pour le suivi d'efforts philantropiques et/ou d'autres efforts
Conley Blockchain as a decentralized mechanism for financial inclusion and economic mobility
Ciuriak Digital Economy Agreements: Where Do We Stand and Where Are We Going?
US11748807B1 (en) Community-based digital transaction authentication

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17805306

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17805306

Country of ref document: EP

Kind code of ref document: A1