# US 2018/0322489 A1 · System and method for restricted transaction processing > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2018/0322489 A1 - Document ID: US20180322489A1 - Status: Published application - Kind: A1 - Application number: 15/585,674 - Filed: 2017-05-03 - Published: 2018-11-08 - Earliest claimed: 2017-05-03 - Inventors: Meredith Altenhofen; Chris Truelson; Quan Wang - Web page: https://patentgrep.com/patent/US20180322489A1 ## CPC - G06Q 20/3821: {Electronic credentials} - G06Q 20/065: {using e-cash} - G06Q 20/40: Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists - H04L 9/3239: {involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD} - H04L 9/3297: {involving time stamps, e.g. generation of time stamps} - G06Q 2220/00: Business processing using cryptography - H04L 9/50: {using hash chains, e.g. blockchains or hash trees} - H04L 2209/56: Financial cryptography, e.g. electronic payment or e-cash - G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract According to some embodiments of the invention, both open loop and closed loop processing may be implemented by a transaction processor. For general, unrestricted transactions, the transaction processor may direct authorization to an open loop primary authorizing entity associated with a primary account number (PAN). For restricted transactions, the transaction processor may determine the appropriate closed loop authorizing entity (e.g., a transit agency, an insurer, a retailer, etc.). The transaction processor may further create an entry in a multi-access blockchain evidencing the transaction on the closed loop or restricted account with that authorizing entity. Thus, the multi-access blockchain may be kept up-to-date, allowing the closed loop authorizing entities to verify transactions and account balances instantaneously. ## Claims ### Claim 1 A method comprising: receiving, at a server computer, a request to process an interaction between a user and a first authorizing entity computer, the request including a first value, a credential, and a flag; determining, by the server computer, that the flag is in the request; in response to determining that the flag is in the request, determining, by the server computer, an identity of the first authorizing entity computer using the flag; accessing, by the server computer, a multi-access blockchain, the multi-access blockchain storing data representing a plurality of interactions between a plurality of authorizing entity computers and a plurality of users; retrieving, by the server computer, a second value associated with the user and the first authorizing entity computer from the multi-access blockchain based on the identity; determining, by the server computer, that the second value is less than the first value; determining, by the server computer, a primary authorizing entity computer based on the credential: determining, by the server computer, that the primary authorizing entity computer is capable of authorizing a third value, wherein the third value is the difference between the first value and the second value; creating, by the server computer, an entry recording the interaction in the multi-access blockchain, wherein the entry includes the second value and the third value; and facilitating, by the server computer, processing of the third value by the primary authorizing entity computer. ### Claim 2 (depends on 1) The method of claim 1, wherein the credential includes an EID. ### Claim 3 (depends on 1) The method of claim 1, further comprising: translating the credential into an account identifier associated with the user and the first authorizing entity computer, wherein the account identifier is used to retrieve the second value associated with the user and the first authorizing entity computer from the multi-access blockchain. ### Claim 4 (depends on 1) The method of claim 1, further comprising: coordinating fulfillment of the third value from the primary authorizing entity computer to the first authorizing entity computer. ### Claim 5 (depends on 1) The method of claim 1, wherein the user initiates a funding request to associate a fourth value with the user and the first authorizing entity computer, and wherein the first authorizing entity computer thereafter creates a new entry recording the fourth value in the multi-access blockchain. ### Claim 6 (depends on 5) The method of claim 5, wherein the funding request is fulfilled by the primary authorizing entity computer to the first authorizing entity computer. ### Claim 7 (depends on 1) The method of claim 1, wherein the primary authorizing entity computer is implements open loop processing, and wherein the first authorizing entity computer implements closed loop processing. ### Claim 8 (depends on 1) The method of claim 1, wherein the primary authorizing entity computer is associated with an issuer of the credential. ### Claim 9 (depends on 1) The method of claim 1, wherein the first authorizing entity computer is associated with an entity identified by the flag. ### Claim 10 A server computer comprising: a processor; and a memory coupled to the processor, the memory storing instructions, which when executed by the processor, cause the server computer to perform operations including: receiving, at a server computer, a request to process an interaction between a user and a first authorizing entity computer, the request including a first value, a credential, and a flag; determining, by the server computer, that the flag is in the request; in response to determining that the flag is in the request, determining, by the server computer, an identity of the first authorizing entity computer using the flag; accessing by the server computer, a multi-access blockchain, the multi-access blockchain storing data representing a plurality of interactions between a plurality of authorizing entity computers and a plurality of users; retrieving, by the server computer, a second value associated with the user and the first authorizing entity computer from the multi-access blockchain based on the identity; determining, by the server computer, that the second value is less than the first value; determining, by the server computer, a primary authorizing entity computer based on the credential; determining, by the server computer, that the primary authorizing entity computer is capable of authorizing a third value, wherein the third value is the difference between the first value and the second value; creating, by the server computer, an entry recording the interaction in the multi-access blockchain, wherein the entry includes the second value and the third value; and facilitating, by the server computer, processing of the third value by the primary authorizing entity computer. ### Claim 11 (depends on 10) The server computer of claim 10, wherein the credential includes an EID. ### Claim 12 (depends on 10) The server computer of claim 10, wherein the operations further include: translating the credential into an account identifier associated with the user and the first authorizing entity computer, wherein the account identifier is used to retrieve the second value associated with the user and the first authorizing entity computer from the multi-access blockchain. ### Claim 13 (depends on 10) The server computer of claim 10, wherein the operations further include: coordinating fulfillment of the third value from the primary authorizing entity computer to the first authorizing entity computer. ### Claim 14 (depends on 10) The server computer of claim 10, wherein the user initiates a funding request to associate a fourth value with the user and the first authorizing entity computer, and wherein the first authorizing entity computer thereafter creates a new entry recording the fourth value in the multi-access blockchain. ### Claim 15 (depends on 14) The server computer of claim 14, wherein the funding request is fulfilled by the primary authorizing entity computer to the first authorizing entity computer. ### Claim 16 (depends on 10) The server computer of claim 10, wherein the primary authorizing entity computer is implements open loop processing, and wherein the first authorizing entity computer implements closed loop processing. ### Claim 17 (depends on 10) The server computer of claim 10, wherein the primary authorizing entity computer is associated with an issuer of the credential. ### Claim 18 (depends on 10) The server computer of claim 10, wherein the first authorizing entity computer is associated with an entity identified by the flag.