Patent Publication Number: US-10318938-B2

Title: System for routing of process authorization and settlement to a user in process data network based on specified parameters

Description:
BACKGROUND 
     Historically, payment authorization and settlement is performed across traditional payment rails. Such communication channels typically require routing of communications from an acquiring bank to an issuing bank for authorization. Such communications must travel across rails such as those operated by third party credit card providers. Accordingly, a need exists for a distributed network for facilitating authorization and settlement of transactions. 
     BRIEF SUMMARY 
     Embodiments of the present invention address these and/or other needs by providing an innovative system, method and computer program product for operatively connecting with a block chain distributed network and using the block chain distributed network for routing of process authorization and settlement based on specified parameters. 
     According to embodiments of the invention, a system includes a memory device and a processing device operatively coupled to the memory device, where the processing device is configured to execute computer-readable program code to receive a transaction record associated with a payment transaction, wherein the transaction record comprises transaction data indicating a payor, a payee and an amount; access a distributed ledger stored in the memory device, wherein the distributed ledger is updated based on communications from a block chain distributed network; determine, using the accessed distributed ledger, one or more preferences associated with the payee of the transaction data; and route at least one of the process authorization and transaction settlement based on the accessed one or more preferences. 
     In some embodiments, the one or more preferences comprises a settlement routing preference and wherein the processing device is configured to execute computer-readable program code further to route the transaction settlement based on the settlement routing preference. In some such embodiments, routing the transaction settlement comprises determining a payment settlement route from a plurality of network payment rails operatively connected between the system and a payee system. In other such embodiments, routing the transaction settlement comprises determining a payment settlement route comprising one or more network nodes specified by the settlement routing preference. In some embodiments, routing the transaction settlement comprises determining a payment settlement route comprising zero nodes of one or more nodes specified by the settlement routing preference as nodes excluded from settlement routing. In some embodiments, routing the transaction settlement comprises determining a payment settlement route consisting solely of network nodes and/or payment rails specified by the settlement routing preferences. In some embodiments, the settlement routing preference comprises a hierarchy of network nodes indicating priorities of preference for routing settlements among available options. In some such embodiments, the priorities of preference dictate that, if available, a first priority network node is selected for settlement routing, and if the top priority network node is not available, a second priority network node, having a next-highest priority to the first priority network node, is selected for settlement routing. In some embodiments, the one or more preferences comprises an authorization routing preference and wherein the processing device is configured to execute computer-readable program code further to route the authorization based on the authorization routing preference. In some such embodiments, routing the authorization comprises determining an authorization route from a plurality of authorization nodes operatively connected with the block chain distributed network. 
     According to embodiments of the invention, a method for execution on a system operatively connected with a block chain distributed network for using the block chain distributed network for routing of process authorization and settlement based on specified parameters includes receiving, by the system, a transaction record associated with a payment transaction, wherein the transaction record comprises transaction data indicating a payor, a payee and an amount; accessing, by the system, a distributed ledger stored in the memory device, wherein the distributed ledger is updated based on communications from a block chain distributed network; determining, by the system, using the accessed distributed ledger, one or more preferences associated with the payee of the transaction data; and routing, by the system, at least one of the process authorization and transaction settlement based on the accessed one or more preferences. 
     In some embodiments, the one or more preferences comprises a settlement routing preference and wherein the method further comprises routing, by the system, the transaction settlement based on the settlement routing preference. In some such embodiments, routing the transaction settlement comprises determining a payment settlement route from a plurality of network payment rails operatively connected between the system and a payee system. In other such embodiments, routing the transaction settlement comprises determining a payment settlement route comprising one or more network nodes specified by the settlement routing preference. In other such embodiments, routing the transaction settlement comprises determining a payment settlement route comprising zero nodes of one or more nodes specified by the settlement routing preference as nodes excluded from settlement routing. In other such embodiments, routing the transaction settlement comprises determining a payment settlement route consisting solely of network nodes and/or payment rails specified by the settlement routing preferences. 
     In yet other such embodiments, the settlement routing preference comprises a hierarchy of network nodes indicating priorities of preference for routing settlements among available options. In some of these embodiments, the priorities of preference dictate that, if available, a first priority network node is selected for settlement routing, and if the top priority network node is not available, a second priority network node, having a next-highest priority to the first priority network node, is selected for settlement routing. 
     In some embodiments, the one or more preferences comprises an authorization routing preference and wherein the method further comprises routing, by the system, the authorization based on the authorization routing preference, the routing comprising determining an authorization route from a plurality of authorization nodes operatively connected with the block chain distributed network. 
     According to embodiments of the invention, a computer program product for execution on a system operatively connected with a block chain distributed network for using the block chain distributed network for routing of process authorization and settlement based on specified parameters and including at least one non-transitory computer-readable medium having computer-readable program code portions embodied therein, which include an executable portion configured to receive a transaction record associated with a payment transaction, wherein the transaction record comprises transaction data indicating a payor, a payee and an amount; an executable portion configured to access a distributed ledger stored in the memory device, wherein the distributed ledger is updated based on communications from a block chain distributed network; an executable portion configured to determine, using the accessed distributed ledger, one or more preferences associated with the payee of the transaction data; and an executable portion configured to route at least one of the process authorization and transaction settlement based on the accessed one or more preferences. 
     The features, functions, and advantages that have been discussed may be achieved independently in various embodiments of the present invention or may be combined with yet other embodiments, further details of which can be seen with reference to the following description and drawings. 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
       Having thus described embodiments of the invention in general terms, reference will now be made the accompanying drawings, wherein: 
         FIG. 1  provides a block diagram illustrating a smart contract rewards program block chain distributed network system and environment, in accordance with embodiments of the invention; 
         FIG. 2  provides a block diagram illustrating the first user&#39;s mobile computing device of  FIG. 1 , in accordance with embodiments of the invention; 
         FIG. 3  provides a block diagram illustrating the second user&#39;s personal computing device of  FIG. 1 , in accordance with embodiments of the invention; 
         FIG. 4  provides a block diagram illustrating the financial institution system(s) of  FIG. 1 , in accordance with embodiments of the invention; 
         FIG. 5  provides a block diagram illustrating the block chain network systems of  FIG. 1 , in accordance with embodiments of the invention; 
         FIG. 6A  is a diagram illustrating a centralized clearinghouse network configuration, in accordance with embodiments of the invention; 
         FIG. 6B  is a diagram illustrating a decentralized block chain network configuration, in accordance with embodiments of the invention; 
         FIG. 7  is a combined flowchart and diagram illustrating a process and system for using a block chain distributed network for routing of process authorization and settlement based on specified parameters in accordance with embodiments of the invention; 
         FIG. 8  is a flowchart illustrating a method for using a block chain distributed network for routing of settlement based on specified parameters in accordance with embodiments of the invention; 
         FIG. 9  is a flowchart illustrating a method for using a block chain distributed network for routing of process authorization and settlement based on specified parameters in accordance with embodiments of the invention; 
         FIG. 10  is a flowchart illustrating a method for using a block chain distributed network for processing an invalid transaction in accordance with embodiments of the invention; 
         FIG. 11A  presents an illustration of the authentication continuum in accordance to one embodiment of the invention; 
         FIG. 11B  presents an illustration of the application functions permitted continuum in accordance to one embodiment of the invention; 
         FIG. 11C  presents an illustration of the coupling of the application functions permitted continuum and the levels of authentication continuum in accordance to one embodiment of the invention; and 
         FIG. 11D  presents an illustration of the relationship between the functions permitted and the authentication types in accordance to one embodiment of the invention. 
     
    
    
     DETAILED DESCRIPTION OF EMBODIMENTS OF THE INVENTION 
     Embodiments of the present invention will now be described more fully hereinafter with reference to the accompanying drawings, in which some, but not all, embodiments of the invention are shown. Indeed, the invention may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will satisfy applicable legal requirements. Where possible, any terms expressed in the singular form herein are meant to also include the plural form and vice versa, unless explicitly stated otherwise. Also, as used herein, the term “a” and/or “an” shall mean “one or more,” even though the phrase “one or more” is also used herein. Furthermore, when it is said herein that something is “based on” something else, it may be based on one or more other things as well. In other words, unless expressly indicated otherwise, as used herein “based on” means “based at least in part on” or “based at least partially on.” Like numbers refer to like elements throughout. 
     In accordance with embodiments of the invention, the terms “financial institution” and “financial entity” include any organization that processes financial transactions including, but not limited to, banks, credit unions, savings and loan associations, investment companies, stock brokerages, assess management firms, insurance companies and the like. In specific embodiments of the invention, use of the term “bank” is limited to a financial entity in which account-bearing customers conduct financial transactions, such as account deposits, withdrawals, transfers and the like. 
     Embodiments of the present invention provide a system and method for using a block chain configuration to implement routing of process authorization and settlement based on specified parameters, such as by the preference of an issuing bank in a transaction authorization/settlement. 
     Embodiments enable a system operatively connected with a block chain distributed network to use the block chain for routing of process authorization and settlement based on specified parameters. Embodiments receive a transaction record associated with a payment transaction, wherein the transaction record comprises transaction data indicating a payor, a payee and an amount; access a distributed ledger stored in the memory device, wherein the distributed ledger is updated based on communications from a block chain distributed network; determine, using the accessed distributed ledger, one or more preferences associated with the payee of the transaction data; and route at least one of the process authorization and transaction settlement based on the accessed one or more preferences. 
     In some cases, the preferences include a settlement routing preference and the transaction settlement is routed based on the settlement routing preference, e.g., over a payment settlement route operatively connected between the system and a payee system, where the route includes (or intentionally not including) one or more network nodes. In some cases, the preference includes a hierarchy of network nodes indicating priorities of preference for routing settlements among available options, e.g., routing through a first priority network node if available and if not available, routing through a second priority network node. 
     Embodiments also include utilizing preferences that include an authorization routing preference, either in combination with the settlement routing preference or not. The authorization routing preference may route the authorization through nodes operatively connected with the distributed network for authorization based on the issuing bank&#39;s preference. 
     In some embodiments, the block chain database may identify and store in distributed ledger an identification of an entity or user over time. Each time an identification is used or updated for the same entity or user over time the block chain database adds the new identification to the ledger. In this way, any old identification may be used by an entity to identify a user. A user may change names or alias over time and, by using the block chain database, the identification can be validated for purposes of transactions. For example, a user may have been known as ID 7 in the base but is now ID 8. The system can still honor transactions referencing ID 7. The system may determine a validation window dictating how long an old identification may be considered valid and authorizable by the system. The generated chain of identification may track how an identification of the user changes over time. Using the block chain database allows for tracking of the user via a name, alias, or other identification to reorganize and receive resource allocation property by maintaining an ongoing record of end-points for the received resource allocations. This tracks transactions such as payments and the like back to the actual user rather than a trade name, third party proxy, outdated name, alias, or the like. 
     Embodiments of the invention are directed to a system, method, or computer program product for a distributive network system with specialized data feeds associated with the distributive network and specific triggering events associated with the data feeds for user identification. Thus, the system may communicate with, store, and execute code for real-time identification via a block chain database architecture. 
       FIG. 1  provides a unique system that includes specialized servers and system communicably linked across a distributive network of nodes required to perform the functions of user identification. 
     A distributed ledger application may be stored and executed on one or more of the devices and/or systems shown in  FIG. 1 . The distributed ledger application may include an identification application or an identification application may be a separate application. A distributed ledger may also be stored on one or more of the devices/systems shown in  FIG. 1 . In some embodiments, the distributed ledger stores data including, but not limited to, smart identification logic and rules, user identifications, user legal identifications, associated logic and rules, and the like. In one embodiment of the invention, both the identification application and the distributed ledger may associate with applications having computer-executable program code that instructs a processing device to operate a network communication device to perform certain communication functions involving described herein. In one embodiment, the computer-executable program code of an application associated with the distributed ledger and identification application may also instruct the processing device to perform certain logic, data processing, and data storing functions of the application. 
     The processing device is configured to use the communication device to gather data, such as data corresponding to transactions, blocks or other updates to the distributed ledger from various data sources such as other block chain network system. The processing device stores the data that it receives in its copy of the distributed ledger stored in the memory device. 
     In the embodiment illustrated in  FIG. 1  and described throughout much of this specification, the identification application may integrate nodes of the generated block chain database into various systems, determine end-point identifications of the users as end-points, link subsequent identifications for identification chain, generate validity windows, and provide authorization for transactions using identification. 
     In some embodiments, the identification application may integrate nodes of the generated block chain database into various systems. In some embodiments, the identification application may generate a block chain database specifically for identification authentication for transaction completion that connects with user systems, merchant systems, financial institution systems, internet systems management systems, and/or management entities to generate a block chain database with information about user identifications used in the past and currently being used. In this way, the user identities may be one or more of aliases, third party proxies, trade names, maiden names, internet handles, usernames, code names, nick names, or the like that may be associated a user. In other embodiments, the identification application may piggy back off of an existing block chain database and code the database for identification authentication for transaction completion. 
     The block chain database generated is a decentralized block chain configuration that ensures accurate mapping of real-time user identifications that the user may be using and/or used in the past. Accordingly, a block chain configuration may be used to maintain an accurate ledger of identities and to provide validation of identifications for authorizing transactions. The generated block chain database maintains a list of data records, such as real-time and on-going list of identities associated with a user. Furthermore, the block chain database may also maintain rules associated with validity windows. Validity windows include rules that determine a duration of time that the identification is valid for authentication of a transaction. The security of which is enhanced by the distributed nature of the block chain. A block chain typically includes several nodes, which may be one or more systems, machines, computers, databases, data stores or the like operably connected with one another. 
     Furthermore, the identification application may integrate and provide nodes of the block chain distributed database into various systems. In this way, the identification application may code nodes for integration into one or more user systems, merchant systems, financial institution systems, internet systems management systems, and/or management entities. In some embodiments, the identification application may generate nodes that are independent of the systems. As such, the nodes may be separate devices and be coded for recognizing user identifications. 
     In some embodiments, the identification application may determine end-point identifications of the users as end-points. In some embodiments, the initial identification may be the end-point identification such as an original legal name, an initial corporate name registered with a state or county, given birth name, social security number, tax identification number, or the like. The identification application may determine the initial identification by identifying one or more user identifications from the one or more nodes of the block chain database. In this way, users, identification issuers, financial institutions, merchants, entities, or the like may provide identification information to the identification application in real-time, such that a real-time identification information of a user  110  or  120  is provided in an ongoing record of a user  110  or  120  into a distributed ledger in the block chain database. The identification application may determine the initial identification based on the type of identification received. In some embodiments, several identifications may be received by the identification application prior to receiving the initial identification. In other embodiments, the identification application may receive the initial identification first. The identification application may determine the initial identification by identifying an age of the identification, a type of identification, or the like. 
     Once the initial identification of the user is determined, the identification application may store the determined end-point identification in the block chain database distributed ledger. The storage may indicate that the identification is the end-point identification in the distributed ledger and allow for ongoing records to be built off of the end-point of the identification. 
     In some embodiments, the identification application may link subsequent identifications for identification chain. As such, the identification application via nodes may identify subsequent identifications associated with the user  110  or  120 . The subsequent identifications may be received from various nodes associated with the identification application. The identifications may be time and date stamped upon receiving of the identification at the various nodes. These subsequent identifications may be linked the end-point identification in the distributed ledger for the ongoing record of identifications of a user  110  or  120 . 
     In some embodiments, the identification application generate validity windows. The identification application stores a chain of identifications from an original name, to trade names, to internet handles, to aliases, or the like are linked together based on time stamp in the distributed ledger. As such, based on the time stamp the identification application may be able to track a duration of time the identification has been in use. Furthermore, the identification application may also track the last time the user used the identification for transaction authorization. This information may be utilized to generate a validity window. The validity window is a window of time after the last time the user utilized the identification for a transaction authorization that the identification application will allow the user to attempt to use the identification again for authorization. The validity window is time frame is dependent on the type of identification being used. The end-point identification may have no window and be available for use at any time in the future. While internet handles or aliases may have a limited window of a week or a month of time. 
     In some embodiments, the identification application provide authorization for transactions using a user presented previous identification. As such, the identification application  258  may receive an indication that a transaction is attempting to be performed between the user  110  or  120  and a third party. The identification application may receive the identification of the user  110  or  120  presented during that transaction. The identification application may review the identification presented and compare it to the distributed ledger. The identification application determines if the identification presented matches an identification in the distributed ledger and if the identification presented is within a validity window. In some embodiments, when the identification application determines that the identification presented matches and it is within the validity window the identification application may allow the transaction to be completed using the presented identification that is chained in the distributed ledger that is in the validity window. As such, the user  110  or  120  may be able to utilize an outdated identification for completion of a transaction. 
     Block Chain Distributed Ledger System and Environment 
       FIG. 1  provides a block diagram illustrating a block chain distributed ledger system and environment  100 , in accordance with an embodiment of the invention. As illustrated in  FIG. 1 , the environment  100  includes a first user  110  and/or a second user  120  where the users represent customers of one or more financial institution(s). A user of the system may be a person, but may also be a business (e.g., a merchant) or any other entity. 
     The environment  100  also may include a mobile device  200  and a personal computing device  300  for use by the first user  110  and second user  120 , respectively. The personal computing device  300  may be any device that employs a processor and memory and can perform computing functions, such as a personal computer or a mobile device. As used herein, a “mobile device”  200  is any mobile communication device, such as a cellular telecommunications device (i.e., a cell phone or mobile phone), personal digital assistant (PDA), a mobile Internet accessing device, or other mobile device. 
     The mobile device  200  and the personal computing device  300  are configured to communicate over a network  150  with a financial institution system(s)  400  and, in some cases, one or more other financial institution systems  170  and with the blockchain, as represented by the block chain distributed network systems  500 . The first user&#39;s mobile device  200 , the second user&#39;s personal computing device  300 , the financial institution system(s)  400 , the block chain distributed network systems  500 , and any other participating financial institution systems  170  are each described in greater detail below with reference to  FIGS. 2-5 . The network  150  may include a local area network (LAN), a wide area network (WAN), and/or a global area network (GAN). The network  150  may provide for wireline, wireless, or a combination of wireline and wireless communication between devices in the network. In one embodiment, the network  150  includes the Internet. In one embodiment, the network  150  includes a wireless telephone network  152 . 
     In general, a mobile device  200  is configured to connect with the network  150  to log the first user  110  into a block chain interface  492  of the financial institution system(s)  400  and/or the block chain distributed network systems  500  (i.e., “block chain systems  500 ). A user, in order to access the first user&#39;s account(s), online banking application and/or mobile banking application on the financial institution system(s)  400  must authenticate with the financial institution system(s)  400  and/or another system. Similarly, in some embodiments, in order to access the distributed ledger(s) of the block chain systems  500 , a user must authenticate with the financial institution system(s)  400  and/or another system, such as one of the block chain systems  500 . For example, logging into the financial institution system(s)  400  generally requires that the first user  110  authenticate his/her identity using a user name, a passcode, a cookie, a biometric identifier, a private key, a token, and/or another authentication mechanism that is provided by the first user  110  to the financial institution system(s)  400  via the mobile device  200 . 
     The financial institution system(s)  400  are in network communication with other devices, such as other financial institutions&#39; transaction/banking systems  170 , block chain systems  500 , and a personal computing device  300  that is configured to communicate with the network  150  to log a second user  120  into the financial institution system(s)  400 . In one embodiment, the invention may provide an application download server such that software applications that support the financial institution system(s)  400  can be downloaded to the mobile device  200 . 
     In some embodiments of the invention, the application download server is configured to be controlled and managed by one or more third-party data providers (not shown in  FIG. 1 ) over the network  150 . In other embodiments, the application download server is configured to be controlled and managed over the network  150  by the same entity or entities that maintains the financial institution system(s)  400 . 
     In some embodiments of the invention, the block chain systems  500  are configured to be controlled and managed by one or more third-party data providers (not shown), financial institutions or other entities over the network  150 . In other embodiments, the block chain systems  500  are configured to be controlled and managed over the network  150  by the same entity that maintains the financial institution system(s)  400 . 
       FIG. 2  provides a block diagram illustrating a user&#39;s mobile device  200  of  FIG. 1  in more detail, in accordance with embodiments of the invention. In one embodiment of the invention, the mobile device  200  is a mobile telephone. However, it should be understood that a mobile telephone is merely illustrative of one type of mobile device  200  that may benefit from, employ, or otherwise be involved with embodiments of the present invention and, therefore, should not be taken to limit the scope of embodiments of the present invention. Other types of mobile devices  200  may include portable digital assistants (PDAs), pagers, mobile televisions, gaming devices, laptop computers, cameras, video recorders, audio/video player, radio, GPS devices, or any combination of the aforementioned. 
     Some embodiments of the mobile device  200  include a processor  210  communicably coupled to such devices as a memory  220 , user output devices  236 , user input devices  240 , a network interface  260 , a power source  215 , a clock or other timer  250 , a camera  280 , and a positioning system device  275 . The processor  210 , and other processors described herein, generally include circuitry for implementing communication and/or logic functions of the mobile device  200 . For example, the processor  210  may include a digital signal processor device, a microprocessor device, and various analog to digital converters, digital to analog converters, and/or other support circuits. Control and signal processing functions of the mobile device  200  are allocated between these devices according to their respective capabilities. The processor  210  thus may also include the functionality to encode and interleave messages and data prior to modulation and transmission. The processor  210  can additionally include an internal data modem. Further, the processor  210  may include functionality to operate one or more software programs, which may be stored in the memory  220 . For example, the processor  210  may be capable of operating a connectivity program, such as a web browser application  222 . The web browser application  222  may then allow the mobile device  200  to transmit and receive web content, such as, for example, location-based content and/or other web page content, according to a Wireless Application Protocol (WAP), Hypertext Transfer Protocol (HTTP), and/or the like. 
     The processor  210  is configured to use the network interface  260  to communicate with one or more other devices on the network  150 . In this regard, the network interface  260  includes an antenna  276  operatively coupled to a transmitter  274  and a receiver  272  (together a “transceiver”). The processor  210  is configured to provide signals to and receive signals from the transmitter  274  and receiver  272 , respectively. The signals may include signaling information in accordance with the air interface standard of the applicable cellular system of the wireless telephone network  152 . In this regard, the mobile device  200  may be configured to operate with one or more air interface standards, communication protocols, modulation types, and access types. By way of illustration, the mobile device  200  may be configured to operate in accordance with any of a number of first, second, third, and/or fourth-generation communication protocols and/or the like. For example, the mobile device  200  may be configured to operate in accordance with second-generation (2G) wireless communication protocols IS-136 (time division multiple access (TDMA)), GSM (global system for mobile communication), and/or IS-95 (code division multiple access (CDMA)), or with third-generation (3G) wireless communication protocols, such as Universal Mobile Telecommunications System (UMTS), CDMA2000, wideband CDMA (WCDMA) and/or time division-synchronous CDMA (TD-SCDMA), with fourth-generation (4G) wireless communication protocols, with LTE protocols, with 3GPP protocols and/or the like. The mobile device  200  may also be configured to operate in accordance with non-cellular communication mechanisms, such as via a wireless local area network (WLAN) or other communication/data networks. 
     The network interface  260  may also include a block chain network interface  270 . The block chain network interface  270  may include software, such as encryption software, and hardware, such as a modem, for communicating information to and/or from one or more devices on a network  150  and connected with or that are part of the block chain systems  500 . For example, the mobile device  200  may be configured so that it can be used as an interface for interacting with the block chain for inputting information involving a transaction record. For example, the mobile device  200  may wirelessly communicate encrypted transaction information to a terminal of the network  150  or the block chain systems  500  such as a merchant system or point of sale. 
     As described above, the mobile device  200  has a user interface that is, like other user interfaces described herein, made up of user output devices  236  and/or user input devices  240 . The user output devices  236  include a display  230  (e.g., a liquid crystal display or the like) and a speaker  232  or other audio device, which are operatively coupled to the processor  210 . The user input devices  240 , which allow the mobile device  200  to receive data from a user such as the first user  110 , may include any of a number of devices allowing the mobile device  200  to receive data from a user, such as a keypad, keyboard, touch-screen, touchpad, microphone, mouse, joystick, other pointer device, button, soft key, and/or other input device(s). The user interface may also include a camera  280 , such as a digital camera. 
     The mobile device  200  may also include a positioning system device  275  that is configured to be used by a positioning system to determine a location of the mobile device  200 . For example, the positioning system device  275  may include a GPS transceiver. In some embodiments, the positioning system device  275  is at least partially made up of the antenna  276 , transmitter  274 , and receiver  272  described above. For example, in one embodiment, triangulation of cellular signals may be used to identify the approximate location of the mobile device  200 . In other embodiments, the positioning system device  275  includes a proximity sensor or transmitter, such as an RFID tag, that can sense or be sensed by devices known to be located proximate a merchant or other location to determine that the mobile device  200  is located proximate these known devices. Such information may be used by embodiments of the invention in order to influence which validating nodes of the block chain network are used for validation of the transaction record and/or to influence routing of the authorization and/or settlement of transactions. For example, validating nodes in geographic proximity to the transaction may be used or not used. Using validating nodes close in proximity to the transaction may provide a greater chance for successful validation/invalidation of the record. That is, such nodes may have more information on which to base a validation or invalidation of the record. Conversely, in an interest of ensuring minimal bias, validating nodes farther away from a transaction may be used. 
     The mobile device  200  further includes a power source  215 , such as a battery, for powering various circuits and other devices that are used to operate the mobile device  200 . Embodiments of the mobile device  200  may also include a clock or other timer  250  configured to determine and, in some cases, communicate actual or relative time to the processor  210  or one or more other devices. 
     The mobile device  200  also includes a memory  220  operatively coupled to the processor  210 . As used herein, memory includes any computer readable medium (as defined herein below) configured to store data, code, or other information. The memory  220  may include volatile memory, such as volatile Random Access Memory (RAM) including a cache area for the temporary storage of data. The memory  220  may also include non-volatile memory, which can be embedded and/or may be removable. The non-volatile memory can additionally or alternatively include an electrically erasable programmable read-only memory (EEPROM), flash memory or the like. 
     The memory  220  can store any of a number of applications which comprise computer-executable instructions/code executed by the processor  210  to implement the functions of the mobile device  200  and/or one or more of the process/method steps described herein. For example, the memory  220  may include such applications as a conventional web browser application  222  and/or a distributed ledger application  221  that may include an identification application as discussed above. These applications also typically provide a graphical user interface (GUI) on the display  230  that allows the first user  110  to communicate with the mobile device  200 , the financial institution system(s)  400 , and/or other devices or systems. In one embodiment of the invention, when the first user  110  decides to participate in his bank&#39;s mobile banking application, the mobile device  200  downloads or otherwise obtains the distributed ledger application  221  from the financial institution system(s)  400 , from the block chain systems  500  or from a distinct application server. In other embodiments of the invention, the first user  110  interacts with the financial institution system(s)  400  or the block chain systems  500  via the web browser application  222  in addition to, or instead of, the distributed ledger application  221 . 
     The memory  220  can also store any of a number of pieces of information, and data, used by the mobile device  200  and the applications and devices that make up the mobile device  200  or are in communication with the mobile device  200  to implement the functions of the mobile device  200  and/or the other systems described herein. For example, the memory  220  may include such data as user authentication information, etc. 
     Referring now to  FIG. 3 , the personal computing device  300  associated with the second user  120  also includes various features, such as a network communication interface  310 , a processing device  320 , a user interface  330 , and a memory device  350 . The network communication interface  310  includes a device that allows the personal computing device  300  to communicate over the network  150  (shown in  FIG. 1 ). In one embodiment of the invention, a network browsing application  355  provides for a user to establish network communication with a financial institution system(s)  400  and/or the block chain systems  500  (shown in  FIG. 1 ) for the purpose of routing authorization and/or settlement of a transaction based on specified preferences in accordance with embodiments of the invention. 
     As used herein, a “processing device,” such as the processing device  320 , generally refers to a device or combination of devices having circuitry used for implementing the communication and/or logic functions of a particular system. For example, a processing device  320  may include a digital signal processor device, a microprocessor device, and various analog-to-digital converters, digital-to-analog converters, and other support circuits and/or combinations of the foregoing. Control and signal processing functions of the system are allocated between these processing devices according to their respective capabilities. The processing device  320  may further include functionality to operate one or more software programs based on computer-executable program code thereof, which may be stored in a memory. As the phrase is used herein, a processing device  320  may be “configured to” perform a certain function in a variety of ways, including, for example, by having one or more general-purpose circuits perform the function by executing particular computer-executable program code embodied in computer-readable medium, and/or by having one or more application-specific circuits perform the function. 
     As used herein, a “user interface”  330  generally includes a plurality of interface devices and/or software that allow a customer to input commands and data to direct the processing device to execute instructions. For example, the user interface  330  presented in  FIG. 3  may include a graphical user interface (GUI) or an interface to input computer-executable instructions that direct the processing device  320  to carry out specific functions. The user interface  330  employs certain input and output devices to input data received from the first user  110  or second user  120  or output data to the first user  110  or second user  120 . These input and output devices may include a display, mouse, keyboard, button, touchpad, touch screen, microphone, speaker, LED, light, joystick, switch, buzzer, bell, and/or other customer input/output device for communicating with one or more customers. 
     As used herein, a “memory device”  350  generally refers to a device or combination of devices that store one or more forms of computer-readable media for storing data and/or computer-executable program code/instructions. Computer-readable media is defined in greater detail below. For example, in one embodiment, the memory device  350  includes any computer memory that provides an actual or virtual space to temporarily or permanently store data and/or commands provided to the processing device  320  when it carries out its functions described herein. 
       FIG. 4  provides a block diagram illustrating the financial institution system(s)  400 , in greater detail, in accordance with embodiments of the invention. As illustrated in  FIG. 4 , in one embodiment of the invention, the financial institution system(s)  400  include one or more processing devices  420  operatively coupled to a network communication interface  410  and a memory device  450 . In certain embodiments, the financial institution system(s)  400  are operated by a first entity, such as a financial institution, while in other embodiments, the financial institution system(s)  400  are operated by an entity other than a financial institution. 
     It should be understood that the memory device  450  may include one or more databases or other data structures/repositories. The memory device  450  also includes computer-executable program code that instructs the processing device  420  to operate the network communication interface  410  to perform certain communication functions of the financial institution system(s)  400  described herein. For example, in one embodiment of the financial institution system(s)  400 , the memory device  450  includes, but is not limited to, a network server application  470 , an authentication application  460 , a customer account data repository  480  which includes customer authentication data  480  and customer account information  484 , a mobile banking application  490  which includes a block chain interface  492 , a mobile web server application  493 , a downloadable distributed ledger application  494  and other computer-executable instructions or other data. The computer-executable program code of the network server application  470 , the authentication application  460 , or the mobile banking application  490  may instruct the processing device  420  to perform certain logic, data-processing, and data-storing functions of the financial institution system(s)  400  described herein, as well as communication functions of the financial institution system(s)  400 . 
     In one embodiment, the customer account data repository  480  includes customer authentication data  482  and customer account information  484 . The network server application  470 , the authentication application  460 , and the mobile banking application  490  are configured to invoke or use the customer account information  484 , the customer authentication data  482 , and the block chain interface  492  when authenticating a user to the financial institution system(s)  400  and/or the block chain systems  500 . 
     As used herein, a “communication interface” generally includes a modem, server, transceiver, and/or other device for communicating with other devices on a network, and/or a user interface for communicating with one or more customers. Referring again to  FIG. 4 , the network communication interface  410  is a communication interface having one or more communication devices configured to communicate with one or more other devices on the network  450 , such as the mobile device  200 , the personal computing device  300 , the other financial institution banking systems  170 , and the block chain systems  500 . The processing device  420  is configured to use the network communication interface  410  to transmit and/or receive data and/or commands to and/or from the other devices connected to the network  150 . 
       FIG. 5  provides a block diagram illustrating block chain network systems  500 , in accordance with embodiments of the invention. As discussed with reference to  FIG. 6B  below, embodiments of the block chain may include multiple systems, servers, computers or the like maintained by one or many entities.  FIG. 5  merely illustrates one of those systems that, typically, interacts with many other similar systems to form the block chain. In one embodiment of the invention, the block chain network systems  500  are operated by a second entity that is a different or separate entity from the first entity (e.g., the financial institution) that, in one embodiment of the invention, implements the financial institution system(s)  400 . In some embodiments, the financial institution system(s)  400  are part of the block chain. Similarly, in some embodiments, the block chain network systems  500  are part of the financial institution system(s)  400 . In other embodiments, the financial institution system(s)  400  are distinct from the block chain network systems  500 . 
     As illustrated in  FIG. 5 , the one of the block chain network systems  500  generally includes, but is not limited to, a network communication interface  510 , a processing device  520 , and a memory device  550 . The processing device  520  is operatively coupled to the network communication interface  510  and the memory device  550 . In one embodiment of the block chain network systems  500 , the memory device  550  stores, but is not limited to, a distributed ledger program interface  560  and a distributed ledger  570 . In some embodiments, the distributed ledger  570  stores data including, but not limited to, information related to transaction one, transaction two, transaction three, etc. In one embodiment of the invention, both the distributed ledger program interface  560  and the distributed ledger  570  may associate with applications having computer-executable program code that instructs the processing device  520  to operate the network communication interface  510  to perform certain communication functions involving the distributed ledger  570  described herein. In one embodiment, the computer-executable program code of an application associated with the distributed ledger  570  may also instruct the processing device  520  to perform certain logic, data processing, and data storing functions of the application associated with the distributed ledger  570  described herein. 
     The network communication interface  510  is a communication interface having one or more communication devices configured to communicate with one or more other devices on the network  150 . The processing device  520  is configured to use the network communication interface  510  to receive information from and/or provide information and commands to a mobile device  200 , a personal computing device  300 , other financial institution systems  170 , other block chain network systems  500 , the financial institution system(s)  400  and/or other devices via the network  150 . In some embodiments, the processing device  520  also uses the network communication interface  510  to access other devices on the network  150 , such as one or more web servers of one or more third-party data providers. In some embodiments, one or more of the devices described herein may be operated by a second entity so that the second entity controls the various functions involving the block chain network systems  500 . For example, in one embodiment of the invention, although the financial institution system(s)  400  are operated by a first entity (e.g., a financial institution), a second entity operates one or more of the block chain network systems  500  that store various copies of the distributed ledger  570 . 
     As described above, the processing device  520  is configured to use the network communication interface  510  to gather data, such as data corresponding to transactions, blocks or other updates to the distributed ledger  570  from various data sources such as other block chain network systems  500 . The processing device  520  stores the data that it receives in its copy of the distributed ledger  570  stored in the memory device  550 . 
     As discussed above, in some embodiments of the invention, an application server or application download server (not shown) might be provided. The application download server may include a network communication interface, a processing device, and a memory device. The network communication interface and processing device are similar to the previously described network communication interface  410  and the processing device  420  previously described. For example, the processing device is operatively coupled to the network communication interface and the memory device. In one embodiment of the application download server, the memory device includes a network browsing application having computer-executable program code that instructs the processing device to operate the network communication interface to perform certain communication functions of the application download server described herein. In some embodiments of the invention, the application download server provides applications that are to be downloaded to a qualified user&#39;s mobile device or personal computing device. 
     Financial Transaction Authorization/Settlement Routing on the Blockchain 
     Rather than utilizing a centralized ledger as discussed with reference to some embodiments above and as shown in  FIG. 6A , other various embodiments of the invention may use a decentralized block chain configuration or architecture as shown in  FIG. 6B  in order to facilitate authorizing and/or settling financial transactions distributed on a block chain distributed network. Such a decentralized block chain configuration ensures accurate mapping of transactions to financial institutions and/or customers. Accordingly, a block chain configuration may be used to maintain an accurate ledger of financial transactions and to provide validation of such transactions. 
     A block chain or blockchain is a distributed database that maintains a list of data records, the security of which is enhanced by the distributed nature of the block chain. A block chain typically includes several nodes, which may be one or more systems, machines, computers, databases, data stores or the like operably connected with one another. In some cases, each of the nodes or multiple nodes are maintained by different entities. A block chain typically works without a central repository or single administrator. One well-known application of a block chain is the public ledger of transactions for cryptocurrencies such as used in bitcoin. The data records recorded in the block chain are enforced cryptographically and stored on the nodes of the block chain. 
     A block chain provides numerous advantages over traditional databases. A large number of nodes of a block chain may reach a consensus regarding the validity of a transaction contained on the transaction ledger. Similarly, when multiple versions of a document or transaction exits on the ledger, multiple nodes can converge on the most up-to-date version of the transaction. For example, in the case of a virtual currency transaction, any node within the block chain that creates a transaction can determine within a level of certainty whether the transaction can take place and become final by confirming that no conflicting transactions (i.e., the same currency unit has not already been spent) confirmed by the block chain elsewhere. 
     The block chain typically has two primary types of records. The first type is the transaction type, which consists of the actual data stored in the block chain. The second type is the block type, which are records that confirm when and in what sequence certain transactions became recorded as part of the block chain. Transactions are created by participants using the block chain in its normal course of business, for example, when someone sends cryptocurrency to another person), and blocks are created by users known as “miners” who use specialized software/equipment to create blocks. In some embodiments, the block chain system is closed, as such the number of miners in the current system are known and the system comprises primary sponsors that generate and create the new blocks of the system. As such, any block may be worked on by a primary sponsor. Users of the block chain create transactions that are passed around to various nodes of the block chain. A “valid” transaction is one that can be validated based on a set of rules that are defined by the particular system implementing the block chain. For example, in the case of cryptocurrencies, a valid transaction is one that is digitally signed, spent from a valid digital wallet and, in some cases, that meets other criteria. In some block chain systems, miners are incentivized to create blocks by a rewards structure that offers a pre-defined per-block reward and/or fees offered within the transactions validated themselves. Thus, when a miner successfully validates a transaction on the block chain, the miner may receive rewards and/or fees as an incentive to continue creating new blocks. 
     As mentioned above and referring to  FIG. 6B , a block chain  600  is typically decentralized—meaning that a distributed ledger  620  (i.e., a decentralized ledger) is maintained on multiple nodes  610  of the block chain  600 . One node in the block chain may have a complete or partial copy of the entire ledger or set of transactions and/or blocks on the block chain. Transactions are initiated at a node of a block chain and communicated to the various nodes of the block chain. Any of the nodes can validate a transaction, add the transaction to its copy of the block chain, and/or broadcast the transaction, its validation (in the form of a block) and/or other data to other nodes. This other data may include time-stamping, such as is used in cryptocurrency block chains. In some embodiments, the nodes  610  of the system might be financial institutions that function as gateways for other financial institutions. For example, a credit union might hold the account, but access to the distributed system through a sponsor node. 
     Various other specific-purpose implementations of block chains have been developed. These include distributed domain name management, decentralized crowd-funding, synchronous/asynchronous communication, decentralized real-time ride sharing and even a general purpose deployment of decentralized applications. 
     Embodiments enable a system operatively connected with a block chain distributed network to use the block chain for routing of process authorization and settlement based on specified parameters. Embodiments receive a transaction record associated with a payment transaction, wherein the transaction record comprises transaction data indicating a payor, a payee and an amount; access a distributed ledger stored in the memory device, wherein the distributed ledger is updated based on communications from a block chain distributed network; determine, using the accessed distributed ledger, one or more preferences associated with the payee of the transaction data; and route at least one of the process authorization and transaction settlement based on the accessed one or more preferences. 
     In some cases, the preferences include a settlement routing preference and the transaction settlement is routed based on the settlement routing preference, e.g., over a payment settlement route operatively connected between the system and a payee system, where the route includes (or intentionally not including) one or more network nodes. In some cases, the preference includes a hierarchy of network nodes indicating priorities of preference for routing settlements among available options, e.g., routing through a first priority network node if available and if not available, routing through a second priority network node. 
     Embodiments also include utilizing preferences that include an authorization routing preference, either in combination with the settlement routing preference or not. The authorization routing preference may route the authorization through nodes operatively connected with the distributed network for authorization based on the issuing bank&#39;s preference. 
       FIG. 7  is a combined flowchart and diagram illustrating a process and system for using a block chain distributed network for routing of process authorization and settlement based on specified parameters in accordance with embodiments of the invention. A payor system  720  is operatively connected with the blockchain distributed network  710 , which includes or is operatively connected with one or more validating node(s)  740 . The blockchain  710  may also be operatively connected with a payee system  730 . The various payment rails  750  or payment channels may be used to route settlement of transactions according to the preferences of the payee system (i.e., the issuing bank or other entity). The number and identity of the validating node(s)  740  used in authorization of the transaction may also be dictated by the preferences of the payee system or entity. 
       FIG. 8  is a flowchart illustrating a method for using a block chain distributed network for routing of settlement based on specified parameters in accordance with embodiments of the invention. First, as represented by block  810 , is to receive a transaction record associated with a payment transaction. The record includes transaction data indicating a payor, a payee and/or a transaction amount and/or other information about the transaction. Next, as represented by block  820 , is to access a distributed ledger that is updated based on communications from a blockchain distributed network. Next, using the distributed ledger, the system determines one or more preferences associated with the payee of the transaction data, as represented by block  830 . For example, authorization routing preferences and/or settlement routing preferences may be stored on a distributed ledger for access by the blockchain. Finally, as represented by block  840 , the system routes the authorization and/or the transaction settlement based on the preferences. 
       FIG. 9  is a flowchart illustrating a method for using a block chain distributed network for routing of process authorization and settlement based on specified parameters in accordance with embodiments of the invention. First, as represented by block  910 , the system determines a payment settlement route from one or more network nodes and/or a plurality of network payment rails operatively connected between the merchant (or payor) system and a payee system. Next, as represented by block  920 , the system, using the settlement routing preferences, eliminates certain nodes and/or adds certain nodes to the payment settlement route based on implicit rules and/or explicit node identities as specified by the preferences. Finally, as represented by block  930 , the system, using the settlement routing preferences, determines a hierarchy of network nodes indicating priorities of preference for routing settlements among available options. For example, the priorities of preference may dictate that a first priority node is selected if available, and if not available, that a second priority node is selected. 
       FIG. 10  is a flowchart illustrating a method for using a block chain distributed network for processing an invalid transaction in accordance with embodiments of the invention. First, as represented by block  1010 , the system determines a payment authorization route from one or more network nodes and/or a plurality of authorization nodes operatively connected with the blockchain distributed network. Next, as represented by block  1020 , the system, using the authorization routing preferences, eliminates certain nodes and/or adds certain nodes to the payment authorization route. Finally, as represented by block  1030 , the system, using the authorization routing preferences, determines a hierarchy of network nodes indicating priorities of preference for routing authorizations among available options. Similar to the routing of settlements, the priorities of preference may dictate that a first priority node is selected is available, and if not available, then a second priority node is selected, and so forth. 
     In various embodiments, the block chain may be configured with a set of rules to dictate when and how transactions are validated/invalidated/neither, transactions are approved and other details about how the network communicates data and the like. In some embodiments, the rules dictate that an originating node (i.e., a node associated with an issuing bank) must approve all transactions associated with cards issued from the issuing bank. In some embodiments, the rules dictate that some or all transactions may be approved by one or more validator nodes without further input from the originating node. In some such cases, the rules dictate that the issuing bank, when initiating use blockchain for transaction validation and/or settlement places additional information that is useful in determining whether transactions associated with the issuing bank should be approved. In other embodiments, the validating node must reach out to the originating node in certain situations as dictated by the rules. For example, if the transaction must be validated by multiple nodes, then the rules may dictate that the validating node communicate with the originating node to confirm or deny validation of the transaction. 
     In some embodiments, the validator may approve the transaction without communicating with the originating node. In such a case, the validator (or a group or all of validators if multiple or universal validations, respectively, are required by the rules), can approve the transaction based solely on the information contained in the blockchain. Thus, if a transaction is requested and a validator receives the transaction, it can check the transaction&#39;s against its ledger to determine whether an originating node has validated the transaction. If so, then the validator may approve the transaction. In this regard, the transaction may be approved very quickly, and in some cases, in real-time or near real-time. 
     In various embodiments, any of the nodes  610  may be a validator or a miner that validates transactions. In some embodiments, a number of the nodes  610  must validate a transaction in order for the transaction to be approved. For example, in one embodiment, three nodes  610  must validate the authenticity of the transaction and/or one or more characteristics associated with the transaction before the transaction may be approved. As noted above, in some instances, the rules of the blockchain and/or rules specific to particular originating FIs or validators dictate that validators cannot approve transactions without confirming available funds. In some cases, available funds information is already associated with alias mapping on the public blockchain, but in other cases, the validator must communicate with the originating FI in order to request approval of the transaction. 
     In some embodiments logic and/or rules may only be changed by the originating node (maintained by an originating entity or entities, e.g., an issuing bank) to ensure the validity of a transaction. In some cases, particularly in cases where one or more nodes have raised a concern that a transaction is not valid, the originating node may be contacted for verification of the transaction. 
     In various embodiments, the transaction record is stored and considered from one or more systems and is not placed on the public block chain itself. In some embodiments, the transaction record is only stored and executed from a subset of the nodes of the block chain, which, in some embodiments, are synonymous with validator nodes and in other embodiments are not synonymous with the validator nodes. In some embodiments, placeholder(s) for the transaction record, portions of the transaction record and/or pseudo-transactions indicating that the transaction record exists and is accessible from block chain may be placed on the block chain. In some cases, the transaction record may be considered only by the designated one or more systems. Such systems may utilize a key or other security mechanism(s) in order to ensure only certain nodes are allowed access to the transaction record. In some cases, this configuration may result in additional security than placing the transaction record on the block chain for any node to consider. 
     In various embodiments, a transaction record/request placed on the blockchain initiates execution of the transaction validation logic/rules and, once a predetermined threshold number of nodes have agreed that the transaction validation has been satisfied, then the transaction proceeds for further processing, i.e., the transaction may be approved and, subsequently, settled. 
     In various embodiments, one or more qualities or attributes may be used to route process authorization and/or settlement. For example, exposure (wire transfer versus ACH versus other transfer methods), reversibility of a transaction (i.e., how permanent or non-permanent a particular transaction is), whether or not a specific legal entity or type of legal entity is included within the route, how strong the identification authentication is (as discussed further below), debit versus credit transactions or otherwise, the cost to the payee, speed of the route, and/or the like. Further, in various embodiments, the various preferences for routing may be advertised and the payor can choose which model to use based on the advertised preferences. 
     Typically, the user may be required to authenticate identity for access to an application or device as described herein. Likewise one or more nodes, administrators or users of the blockchain or other entities interacting with or using the blockchain may be required to authenticate their identity for access to a particular feature, function or action of an application, device, a smart contract and/or general or specific access to the blockchain network. Numerous types and levels of user authentication exist. For example, a user may authenticate his or her identity using a unique alias such as a username and/or password. Further, in some situations, challenge questions, familiar pictures and/or phrases, biometrics, key fob-based alphanumeric codes and/or collocation, authentication of another application such as a similar application or an “overarching” application, and/or the like may be used as types of identity authentication. 
     The different types of authentication may provide differing degrees of confidence regarding the authentication using such types. For example, if a username by itself is used for a first user authentication, and a username along with a password is used for a second authentication, then the second authentication should provide a higher confidence regarding the authentication because of the additional layer of authentication required. Further, within the types of authentication, varying levels of confidence may be used. For example, when using a password, an administrator may require users to create a password according to strict rules designed to increase the security level of the password, and therefore increase the confidence of any authentication using the password. 
     Accordingly, a continuum of authentication may be used to quantify (or dictate) the levels of authentication. Likewise, a continuum of functions permitted may be used to quantify (or dictate) the number or context in which functions are permitted. 
     Referring to  FIG. 11A , a continuum of authentication  1100 A is illustrated according to embodiments of the invention. On the left-hand side of the continuum, a “zero authentication” requires no authentication credentials. On the right-hand side of the continuum, a “hard authentication” requires full authentication credentials. This means that it requires the strictest combination of credentials. In between the two extremes, “a soft authentication” requires minimal credentials, moderate credentials or most credentials for various points along the continuum. The continuum generally represents the number of credentials required and/or the relative strength of the credentials required for that point on the continuum. As discussed below with reference to  FIG. 11C , the continuum of authentication  1100 A may be coupled with an application functions permitted continuum  1100 B, first illustrated in  FIG. 11B . 
     Referring to  FIG. 11B , the application functions permitted continuum  1100 B illustrates various levels of application functions permitted. Functions may refer to what a user is permitted to “see” (e.g., transactions placed on the block chain, etc.) and/or what the user is permitted to “do” (e.g., validate transactions, stored and/or execute a smart contract, etc.). More specifically, this may refer to whether a specific function is permitted at a certain point on the continuum and/or the context in which a certain function is permitted. The left-hand side of the continuum indicates that no functions are permitted, and the right-hand side of the continuum indicates that all functions are permitted. In between the extremes, minimal functions are permitted, moderate functions are permitted and most functions are permitted. Thus, any given point along the continuum  1100 B corresponds with a certain amount and/or number of functions that are permitted and/or the context in which certain functions are permitted. 
     Referring now to  FIG. 11C , a diagram  1100 C illustrates a coupling of the application functions permitted continuum  1100 B and the levels of authentication continuum  1100 A. As shown, the continua  1100 B and  1100 A may be coupled with one another such that the various points along the continua intersect at specific points of the coupled continuum. For example, one continuum may be moved left or right with respect to the other continuum in order to achieve a different relationship between the functions permitted and the credentials required. Accordingly, for a given coupling, a specific point on continuum  1100 B provides that a particular function or functions may be permitted given that a specified level of authentication credentials are supplied, as indicated by the corresponding point on continuum  1100 A. For example, a financial institution and/or a user may arrange the continua  1100 B and  1100 A with respect to one another and may adjust the arrangement based on changing desires or goals. 
     In some embodiments, one or both the continua  1100 B and  1100 A may have weighted scales such that, as a point on the continuum is moved, the corresponding functions permitted and/or level of authentication required may change exponentially or otherwise. Furthermore, in various embodiments, other representations of the various functions permitted that correspond with the various levels of authentication may be used by the invention. 
     Referring now to  FIG. 11D , a diagram  1100 D illustrates a relationship between the functions permitted and the authentication types. As shown in  FIG. 11D , the soft authentication continuum between zero authentication and hard authentication may include one or more authentication types (A, B, C in the Figure). In one aspect, the one or more authentication types corresponding to the one or more authentication credentials received from the user and one or more functions associated with the application permitted for user access are positively correlated. For example, a username may enable the user to gain access to checking balance, a username and password may enable the user to gain access to checking balance, funds transfer between the user&#39;s first bank account and second bank account, and downloading previous statements, and a username, password and challenge question may enable the user to gain complete access to all the functions of the applications and devices. In one aspect, the user may have to provide authentication credentials corresponding to authentication types A and B to gain access to moderate functions associated with the application. For example, the user may provide a username and password to access a balance check and funds transfer. In another aspect, the user may have to provide authentication credentials corresponding to authentication types A, B, and C to gain access to most function associated with the application. For example, the user may provide a username, password, and a personal identification number to access a balance check, a funds transfer, a deposit, a bill-pay, and access to submitting a transaction request associated with a smart contracts rewards program. In yet another aspect, the user may have to only provide authentication credentials corresponding to authentication type A to gain access to minimal functions associated with the application. For example, the user may provide a username to access a balance check or to confirm that particular rewards were disbursed to the user&#39;s account through the smart contract rewards program. 
     In some embodiments of the invention one or more of the systems described herein may be combined with each other, or otherwise perform the functions of the other systems described herein. In other embodiments of the invention one or more of the applications described herein may be combined with each other, or otherwise perform the functions of the other applications described herein. Furthermore, the applications may be any type of application, such as an application stored on a desktop, server, or other device, a mobile application stored on a mobile device, a cloud application, or other like application. As such, the applications described herein, or portions of the applications described herein may be stored and operated on any of the systems or devices  50  described herein. For example, a portion of the link application  17  may be stored on the user computer systems  20 , or may be included as a portion of financial institution applications, such as an online banking application, in order to achieve the inventions described herein. 
     It should be understood, that the systems and devices  50  described in  FIGS. 1-3 , or other devices not specifically described herein, may be configured to establish a communication link with each other in order to accomplish the steps of the processes described herein. The link may be an internal link within the same entity (e.g., within the same financial institution or device provider) or a link with the other systems of entities (e.g., social networking systems, third-party systems, or the like). In some embodiments, the systems may be configured for monitoring the applications  27  and devices  50  that the user utilizes. The information received from monitoring may be provided via wireless network path portions through the Internet. When the systems or devices  50  are not monitoring a source or are not being monitoring, the information need not be transmitted from the source through the Internet to the destination, although it could be. The sources of information may be made continuously available, however, continuously available does not necessarily mean that the sources actually continuously generates data, but that a source is continuously available to generate and send data real-time (e.g., instantaneously and/or within a few seconds, or the like) of receiving a request for it. In any case, the sources may be continuously available to receive and/or generate information, in some cases in digitized data in Internet Protocol (IP) packet format. In response to continuously monitoring the real-time data feeds from the various systems or devices  50 , the system may be configured to provide target information to the user  4  and/or allow the user to make changes to or control the applications  27  and/or devices  50 , in part in order to reach the target. 
     Moreover, it should be understood that the process flows described herein include transforming the information sent and/or received from the applications of the different systems (e.g., internally or externally) and/or the devices  50  from one or more data formats into a data format associated with the link application  17  for display to the user  4  on the user computer systems  20 . There are many ways in which information is converted within the linked system environment  1 . This may be seamless, as in the case of upgrading to a newer version of a computer program. Alternatively, the conversion may require processing by the use of a special conversion program, or it may involve a complex process of going through intermediary stages, or involving complex “exporting” and “importing” procedures, which may converting to and from a tab-delimited or comma-separated text file. In some cases, a program may recognize several data file formats at the data input stage and then is also capable of storing the output data in a number of different formats. Such a program may be used to convert a file format. If the source format or target format is not recognized, then at times a third program may be available which permits the conversion to an intermediate format, which can then be reformatted. 
     As will be appreciated by one of skill in the art, the present invention may be embodied as a method (including, for example, a computer-implemented process, a business process, and/or any other process), apparatus (including, for example, a system, machine, device, computer program product, and/or the like), or a combination of the foregoing. Accordingly, embodiments of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.), or an embodiment combining software and hardware aspects that may generally be referred to herein as a “system.” Furthermore, embodiments of the present invention may take the form of a computer program product on a computer-readable medium having computer-executable program code embodied in the medium. 
     Any suitable transitory or non-transitory computer readable medium may be utilized. The computer readable medium may be, for example but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device. More specific examples of the computer readable medium include, but are not limited to, the following: an electrical connection having one or more wires; a tangible storage medium such as a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a compact disc read-only memory (CD-ROM), or other optical or magnetic storage device. 
     In the context of this document, a computer readable medium may be any medium that can contain, store, communicate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device. The computer usable program code may be transmitted using any appropriate medium, including but not limited to the Internet, wireline, optical fiber cable, radio frequency (RF) signals, or other mediums. 
     Computer-executable program code for carrying out operations of embodiments of the present invention may be written in an object oriented, scripted or unscripted programming language such as Java, Perl, Smalltalk, C++, or the like. However, the computer program code for carrying out operations of embodiments of the present invention may also be written in conventional procedural programming languages, such as the “C” programming language or similar programming languages. 
     Embodiments of the present invention are described above with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products. It will be understood that each block of the flowchart illustrations and/or block diagrams, and/or combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer-executable program code portions. These computer-executable program code portions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a particular machine, such that the code portions, which execute via the processor of the computer or other programmable data processing apparatus, create mechanisms for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. 
     These computer-executable program code portions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the code portions stored in the computer readable memory produce an article of manufacture including instruction mechanisms which implement the function/act specified in the flowchart and/or block diagram block(s). 
     The computer-executable program code may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the code portions which execute on the computer or other programmable apparatus provide steps for implementing the functions/acts specified in the flowchart and/or block diagram block(s). Alternatively, computer program implemented steps or acts may be combined with operator or human implemented steps or acts in order to carry out an embodiment of the invention. 
     As the phrase is used herein, a processor may be “configured to” perform a certain function in a variety of ways, including, for example, by having one or more general-purpose circuits perform the function by executing particular computer-executable program code embodied in computer-readable medium, and/or by having one or more application-specific circuits perform the function. 
     Embodiments of the present invention are described above with reference to flowcharts and/or block diagrams. It will be understood that steps of the processes described herein may be performed in orders different than those illustrated in the flowcharts. In other words, the processes represented by the blocks of a flowchart may, in some embodiments, be in performed in an order other that the order illustrated, may be combined or divided, or may be performed simultaneously. It will also be understood that the blocks of the block diagrams illustrated, in some embodiments, merely conceptual delineations between systems and one or more of the systems illustrated by a block in the block diagrams may be combined or share hardware and/or software with another one or more of the systems illustrated by a block in the block diagrams. Likewise, a device, system, apparatus, and/or the like may be made up of one or more devices, systems, apparatuses, and/or the like. For example, where a processor is illustrated or described herein, the processor may be made up of a plurality of microprocessors or other processing devices which may or may not be coupled to one another. Likewise, where a memory is illustrated or described herein, the memory may be made up of a plurality of memory devices which may or may not be coupled to one another. 
     While certain exemplary embodiments have been described and shown in the accompanying drawings, it is to be understood that such embodiments are merely illustrative of, and not restrictive on, the broad invention, and that this invention not be limited to the specific constructions and arrangements shown and described, since various other changes, combinations, omissions, modifications and substitutions, in addition to those set forth in the above paragraphs, are possible. Those skilled in the art will appreciate that various adaptations and modifications of the just described embodiments can be configured without departing from the scope and spirit of the invention. Therefore, it is to be understood that, within the scope of the appended claims, the invention may be practiced other than as specifically described herein. 
     INCORPORATION BY REFERENCE 
     To supplement the present disclosure, this application further incorporates entirely by reference the following commonly assigned patent applications: 
     
       
         
           
               
               
               
             
               
                   
               
               
                 U.S. patent 
                   
                   
               
               
                 application Ser. No. 
                 Title 
                 Filed On 
               
               
                   
               
             
            
               
                 14/942,326 
                 TRANSPARENT SELF- 
                 Nov. 16, 2015 
               
               
                 now published as 
                 MANAGING REWARDS 
                   
               
               
                 2017/0140408 
                 PROGRAM USING 
                   
               
               
                   
                 BLOCKCHAIN AND 
                   
               
               
                   
                 SMART CONTRACTS 
                   
               
               
                 15/041,555 
                 BLOCK CHAIN ALIAS FOR 
                 Feb. 11, 2016 
               
               
                 now published as 
                 PERSON-TO-PERSON 
                   
               
               
                 2017/0132630 
                 PAYMENTS 
                   
               
               
                 62/253,935 
                 BLOCK CHAIN ALIAS 
                 Nov. 11, 2015 
               
               
                   
                 PERSON-TO-PERSON 
                   
               
               
                   
                 PAYMENT 
                   
               
               
                 15/041,566 
                 BLOCK CHAIN ALIAS 
                 Feb. 11, 2016 
               
               
                 now published as 
                 PERSON-TO-PERSON 
                   
               
               
                 2017/0132615 
                 PAYMENTS 
                   
               
               
                 15/050,375 
                 SYSTEM FOR 
                 Feb. 22, 2016 
               
               
                 now published as 
                 CONVERSION OF AN 
                   
               
               
                 2017/0244757 
                 INSTRUMENT FROM A 
                   
               
               
                   
                 NON-SECURED 
                   
               
               
                   
                 INSTRUMENT TO A 
                   
               
               
                   
                 SECURED INSTRUMENT 
                   
               
               
                   
                 IN A PROCESS DATA 
                   
               
               
                   
                 NETWORK 
                   
               
               
                 15/050,379 
                 SYSTEM FOR EXTERNAL 
                 Feb. 22, 2016 
               
               
                 now published as 
                 SECURE ACCESS TO 
                   
               
               
                 2017/0243215 
                 PROCESS DATA 
                   
               
               
                   
                 NETWORK 
                   
               
               
                 15/050,358 
                 SYSTEM FOR PROVIDING 
                 Feb. 22, 2016 
               
               
                 now published as 
                 LEVELS OF SECURITY 
                   
               
               
                 2017/0244721 
                 ACCESS TO A PROCESS 
                   
               
               
                   
                 DATA NETWORK 
                   
               
               
                 62/293,585 
                 SYSTEM FOR SECURE 
                 Feb. 10, 2016 
               
               
                   
                 ROUTING OF DATA TO 
                   
               
               
                   
                 VARIOUS NETWORKS 
                   
               
               
                   
                 FROM A PROCESS DATA 
                   
               
               
                   
                 NETWORK 
                   
               
               
                 62/293,620 
                 SYSTEM FOR 
                 Feb. 10, 2016 
               
               
                   
                 CENTRALIZED CONTROL 
                   
               
               
                   
                 OF SECURE ACCESS TO 
                   
               
               
                   
                 PROCESS DATA 
                   
               
               
                   
                 NETWORK 
                   
               
               
                 15/049,605 
                 SYSTEM FOR CONTROL 
                 Feb. 22, 2016 
               
               
                 now published as 
                 OF SECURE ACCESS AND 
                   
               
               
                 2017/0230353 
                 COMMUNICATION WITH 
                   
               
               
                   
                 DIFFERENT PROCESS 
                   
               
               
                   
                 DATA NETWORKS WITH 
                   
               
               
                   
                 SEPARATE SECURITY 
                   
               
               
                   
                 FEATURES 
                   
               
               
                 15/049,716 
                 SYSTEM FOR CONTROL 
                 Feb. 22, 2016 
               
               
                 now published as 
                 OF DEVICE IDENTITY 
                   
               
               
                 2017/0243208 
                 AND USAGE IN A 
                   
               
               
                   
                 PROCESS DATA 
                   
               
               
                   
                 NETWORK 
                   
               
               
                 15/049,777 
                 SYSTEM FOR 
                 Feb. 22, 2016 
               
               
                 now published as 
                 ESTABLISHING SECURE 
                   
               
               
                 2017/0244707 
                 ACCESS FOR USERS IN A 
                   
               
               
                   
                 PROCESS DATA 
                   
               
               
                   
                 NETWORK 
                   
               
               
                 15/049,835 
                 SYSTEM FOR ALLOWING 
                 Feb. 22, 2016 
               
               
                 now U.S. Pat. No. 
                 EXTERNAL VALIDATION 
                   
               
               
                 10,026,118 
                 OF DATA IN A PROCESS 
                   
               
               
                   
                 DATA NETWORK 
                   
               
               
                 15/050,094 
                 SYSTEM FOR 
                 Feb. 22, 2016 
               
               
                 now published as 
                 CONVERSION OF AN 
                   
               
               
                 2017/0214699 
                 INSTRUMENT FROM A 
                   
               
               
                   
                 NON-SECURED 
                   
               
               
                   
                 INSTRUMENT TO A 
                   
               
               
                   
                 SECURED INSTRUMENT 
                   
               
               
                   
                 IN A PROCESS DATA 
                   
               
               
                   
                 NETWORK 
                   
               
               
                 62/287,293 
                 SYSTEM FOR 
                 Jan. 26, 2016 
               
               
                   
                 CONVERSION OF AN 
                   
               
               
                   
                 INSTRUMENT FROM A 
                   
               
               
                   
                 NON-SECURED 
                   
               
               
                   
                 INSTRUMENT TO A 
                   
               
               
                   
                 SECURED INSTRUMENT 
                   
               
               
                   
                 IN A PROCESS DATA 
                   
               
               
                   
                 NETWORK 
                   
               
               
                 15/050,098 
                 SYSTEM FOR TRACKING 
                 Feb. 22, 2016 
               
               
                 now published as 
                 AND VALIDATION OF 
                   
               
               
                 2017/0213221 
                 MULTIPLE INSTANCES OF 
                   
               
               
                   
                 AN ENTITY IN A PROCESS 
                   
               
               
                   
                 DATA NETWORK 
                   
               
               
                 62/287,301 
                 SYSTEM FOR TRACKING 
                 Jan. 26, 2016 
               
               
                   
                 AND VALIDATION OF 
                   
               
               
                   
                 MULTIPLE INSTANCES OF 
                   
               
               
                   
                 AN ENTITY IN A PROCESS 
                   
               
               
                   
                 DATA NETWORK 
                   
               
               
                 15/050,084 
                 SYSTEM FOR TRACKING 
                 Feb. 22, 2016 
               
               
                 now U.S. Pat. No. 
                 AND VALIDATION OF AN 
                   
               
               
                 9,825,931 
                 ENTITY IN A PROCESS 
                   
               
               
                   
                 DATA NETWORK 
                   
               
               
                 62/287,298 
                 SYSTEM FOR TRACKING 
                 Jan. 26, 2016 
               
               
                   
                 AND VALIDATION OF AN 
                   
               
               
                   
                 ENTITY IN A PROCESS 
                   
               
               
                   
                 DATA NETWORK 
                   
               
               
                 15/050,372 
                 SYSTEM FOR ROUTING OF 
                 Feb. 22, 2016 
               
               
                 now published as 
                 PROCESS 
                   
               
               
                 2017/0243217 
                 AUTHORIZATIONS AND 
                   
               
               
                   
                 SETTLEMENT TO A USER 
                   
               
               
                   
                 IN A PROCESS DATA 
                   
               
               
                   
                 NETWORK 
                   
               
               
                 15/050,192 
                 SYSTEM FOR GRANT OF 
                 Feb. 22, 2016 
               
               
                 now published under 
                 USER ACCESS AND DATA 
                   
               
               
                 2017/0243209 
                 USAGE IN A PROCESS 
                   
               
               
                   
                 DATA NETWORK 
                   
               
               
                 15/050,294 
                 SYSTEM FOR 
                 Feb. 22, 2016 
               
               
                 now published as 
                 IMPLEMENTING A 
                   
               
               
                 2017/0243212 
                 DISTRIBUTED LEDGER 
                   
               
               
                   
                 ACROSS MULTIPLE 
                   
               
               
                   
                 NETWORK NODES 
                   
               
               
                 15/049,865 
                 SYSTEM FOR EXTERNAL 
                 Feb. 22, 2016 
               
               
                 now published as 
                 VALIDATION OF 
                   
               
               
                 2017/0244720 
                 PRIVATE-TO-PUBLIC 
                   
               
               
                   
                 TRANSITION PROTOCOLS 
                   
               
               
                 15/049,852 
                 SYSTEM FOR EXTERNAL 
                 Feb. 22, 2016 
               
               
                 now published as 
                 VALIDATION OF 
                   
               
               
                 2017/0243025 
                 DISTRIBUTED RESOURCE 
                   
               
               
                   
                 STATUS 
                   
               
               
                 15/050,316 
                 SYSTEM FOR TRACKING 
                 Feb. 22, 2016 
               
               
                 now published as 
                 TRANSFER OF 
                   
               
               
                 2017/0243214 
                 RESOURCES IN A 
                   
               
               
                   
                 PROCESS DATA 
                   
               
               
                   
                 NETWORK 
                   
               
               
                 15/050,321 
                 SYSTEM FOR MANAGING 
                 Feb. 22, 2016 
               
               
                 now published as 
                 SERIALIZABILITY OF 
                   
               
               
                 2017/0243287 
                 RESOURCE TRANSFERS IN 
                   
               
               
                   
                 A PROCESS DATA 
                   
               
               
                   
                 NETWORK 
                   
               
               
                 15/050,307 
                 SYSTEM TO ENABLE 
                 Feb. 22, 2016 
               
               
                 now published as 
                 CONTACTLESS ACCESS 
                   
               
               
                 2017/0243213 
                 TO A TRANSACTION 
                   
               
               
                   
                 TERMINAL USING A 
                   
               
               
                   
                 PROCESS DATA 
                   
               
               
                   
                 NETWORK