# US 2013/0159121 A1 · System and method for controlling access to an electronic account > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2013/0159121 A1 - Document ID: US20130159121A1 - Status: Published application - Kind: A1 - Application number: 13/325,484 - Filed: 2011-12-14 - Published: 2013-06-20 - Earliest claimed: 2011-12-14 - Inventors: Darrell Reginald May; Raymond Paul Vander Veen; Andrew John Ewanchuk - Web page: https://patentgrep.com/patent/US20130159121A1 ## CPC - G06Q 30/06: Buying, selling or leasing transactions - G06Q 10/00: Administration; Management - G06Q 20/00: Payment architectures, schemes or protocols (apparatus for performing or posting payment transactions G07F7/08, G07F19/00; electronic cash registers G07G1/12) - G06Q 30/04: Billing or invoicing - G06Q 40/02: Banking, e.g. interest calculation or account maintenance (credit or loans G06Q40/03) - G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR ## Abstract The present disclosure described herein relates to a system and method for managing transaction restrictions for an account in a family of accounts through a network. The method comprises: upon receipt of a transaction request from a device in the network at a server, analyzing a restriction field associated with the account against parameters associated the transaction request. When a transaction price associated with the transaction request exceeds a value in the restriction field or when a transaction entity associated with the transaction request is present as a restricted entity in the restriction field, completion of the transaction is denied. When contents of the restriction field relating to restrictions do not match any of the parameters, completion of the transaction is allowed. The method also updates the restriction field to reflect a change request for the transaction restriction for a subsequent transaction upon receipt of the change request. ## Claims ### Claim 1 A method for managing transaction restrictions for an account in a family of accounts through a network, said method comprising: upon receipt of a transaction request associated with said account from a device in said network at a server, analyzing a restriction field associated with said account against parameters associated said transaction request, and when a transaction price associated with said transaction request exceeds a value in said restriction field, denying completion of said transaction; when a transaction entity associated with said transaction request is present as a restricted entity in said restriction field, denying completion of said transaction; and when contents of said restriction field relating to restrictions do not match any of said parameters, allowing completion of said transaction; and upon receipt of a change request from said network for said transaction restriction, updating said restriction field to reflect said change request. ### Claim 2 (depends on 1) The method for managing transaction restrictions for an account as claimed in claim 1, further comprising: when said transaction entity associated with said transaction request is present as an allowed entity in said restriction field, allowing completion of said transaction. ### Claim 3 (depends on 1) The method for managing transaction restrictions for an account as claimed in claim 1, further comprising: when completion of said transaction is denied, generating and sending a deny message to said device through said network. ### Claim 4 (depends on 1) The method for managing transaction restrictions for an account as claimed in claim 1, further comprising: when completion of said transaction is allowed, generating and sending an allow message to said device through said network. ### Claim 5 (depends on 1) The method for managing transaction restrictions for an account as claimed in claim 1, further comprising: when completion of said transaction is allowed, updating a transaction status field associated with said account with a parameter of said parameters associated with said transaction. ### Claim 6 (depends on 5) The method for managing transaction restrictions for an account as claimed in claim 5, further comprising: upon receipt of a subsequent transaction request from said network, analyzing said transaction status field against parameters associated said subsequent transaction request to determine whether said subsequent transaction can be completed. ### Claim 7 (depends on 1) The method for managing transaction restrictions for an account as claimed in claim 1, further comprising: when said server receives a restriction update request for a group of accounts from a supervisor account associated with said group of accounts and when said account is in said group of accounts, revising said transaction field with a parameter related to said restriction update request. ### Claim 8 (depends on 1) The method for managing transaction restrictions for an account as claimed in claim 1, further comprising: updating said restriction field with a revised value upon detection of an update condition for said restriction field. ### Claim 9 (depends on 8) The method for managing transaction restrictions for an account as claimed in claim 8, wherein: said update condition is based on a time event or an occurrence event, said time event and said occurrence event being tracked in a database accessed by said server. ### Claim 10 (depends on 9) The method for managing transaction restrictions for an account as claimed in claim 9, wherein: data for said occurrence event is updated by a supervisor account associated with said account. ### Claim 11 (depends on 1) The method for managing transaction restrictions for an account as claimed in claim 1, further comprising: upon receipt of said transaction request, analyzing a second restriction field associated with said account against parameters associated said transaction request; arbitrating between values in said restriction field and said second restriction field when there is a conflict to determine a dominant restriction value; analyzing said dominant restriction value against said transaction request; when said transaction price exceeds a value in said dominant restriction value, denying completion of said transaction; and when said transaction entity associated with said transaction request is present as said restricted entity in said dominant restriction value, denying completion of said transaction. ### Claim 12 (depends on 1) The method for managing transaction restrictions for an account as claimed in claim 1, further comprising: transferring a value from a credit field in said account to a corresponding credit field in a second account. ### Claim 13 (depends on 12) The method for managing transaction restrictions for an account as claimed in claim 12, wherein: said value is transferred upon either receiving a transfer credit request from said second account or acceptance of an offer for said value from said second account. ### Claim 14 A server for managing transaction restrictions for an account in a family of accounts through a network, said server comprising: a transaction processing module to receive a transaction request from a device associated with said account in said network; analyze a restriction field associated with said account against parameters associated said transaction request; deny completion of said transaction when a transaction price associated with said transaction request exceeds a value in said restriction field; or a transaction entity associated with said transaction request is present as a restricted entity in said restriction field; and allow completion of said transaction when contents of said restriction field relating to restrictions do not match any of said parameters; and an account management module to receive a change request from said network for said transaction restriction; and update said restriction field to reflect said change request. ### Claim 15 (depends on 14) The server for managing transaction restrictions for an account as claimed in claim 14, wherein said transaction processing module further: allows completion of said transaction when said transaction entity associated with said transaction request is present as an allowed entity in said restriction field. ### Claim 16 (depends on 14) The server for managing transaction restrictions for an account as claimed in claim 14, wherein said transaction processing module further: generates and sends a deny message to said device through said network when completion of said transaction is denied; and generates and sends an allow message to said device through said network when completion of said transaction is allowed. ### Claim 17 (depends on 14) The server for managing transaction restrictions for an account as claimed in claim 14, wherein said transaction processing module further: updates a transaction status field associated with said account with a parameter of said parameters associated with said transaction when completion of said transaction is allowed. ### Claim 18 (depends on 17) The server for managing transaction restrictions for an account as claimed in claim 17, wherein said transaction processing module further: analyzes said transaction status field against parameters associated said subsequent transaction request to determine whether a subsequent transaction can be completed upon receipt of said subsequent transaction request from said network.