Physical, logical separation of balances of funds
AssigneeSquare, Inc.
InventorBrian GRASSADONIA
Life of this patent
Estimating the term…
Abstract
Users can maintain logical and physical separation of funds maintained in a single account. The account can include the entire balance of a user's funds, but the user can split the funds between several, physically separated sub-accounts that have balances related to the entire balance of the account. Financial transactions, including credit and debit transactions, can then target sub-accounts that the user established.
Claims29
A method for logically creating sub-accounts for processing payments comprising:
- establishing, by a server upon receiving a request from a user computing device executing an application, at least one sub-account associated with an account maintained by a financial institution, the request including a sub-account identifier, wherein the account and the sub-account correspond to a routing transit number, account number, and an account balance, maintained in a record in a system of record server;
- storing, by the server in an account record in a database, the sub-account identifier associated with the sub-account having a sub-account balance, wherein the sub-account balance is an allocated amount of the account balance, wherein the sub-account is associated with the routing transit number and the account number of the account, and wherein the account record maintains a copy of the routing transit number, the account number, and the account balance;
- synchronizing, by the server, the copy of the account balance with the account balance maintained in the record in the system of record server;
- upon receiving a payment request, comprising an amount, from a merchant computing device over a card-issuer network, and before the payment request reaches the system of record server, generating, by the server, a graphical user interface for display by the application, wherein the graphical user interface presents an interactive element for selection of at least one sub-account from which to withdraw funds in response to the payment request;
- receiving, by the server, a selected sub-account identifier from the application executed by the user computing device;
- identifying, by the server, a sub-account associated with the selected sub-account identifier;
- generating, by the server an authorization message based on at least whether the identified sub-account balance is greater than the amount of the payment request;
- transmitting, by the server over the card-issuer network, the authorization message to the merchant computing device;
- upon approving the payment request, simultaneously updating, by the server, the identified sub-account balance associated with the identified sub-account and the copy of the account balance;
- simultaneously transmitting, by the server to the system of record server, a message to reflect the approval of the payment request and update a balance stored in the system of record server;
- and
- synchronizing, by the server, the copy of the account balance with the account balance maintained in the record in the system of record server.
A computer-implemented method comprising:
- upon receiving a plurality of transactions comprising transaction data from a merchant-acquirer server or a system of record server, generating, by a consumer computing system (CCS) server, in a transaction database a transaction record of each transaction, wherein the transaction record of each transaction comprises a credit or a debit to a copy of an account balance, wherein the account balance is maintained by the system of record server;
- identifying, by the CCS server, a first transaction record and a second transaction record in the transaction database having sufficiently similar transaction data to qualify as a recurring transaction, based on one or more predetermined criteria stored in the transaction database;
- generating, by the CCS server if the first transaction and the second transaction qualify as the recurring transaction, a potential transaction record comprising potential transaction data based on the first transaction record and the second transaction record;
- storing, by the CCS server, in the transaction database, the potential transaction record, wherein the potential transaction record comprises an indication that the potential transaction data represents a potential transaction that has not yet occurred;
- receiving, by the CCS server, a payment request from a user computing device or a merchant-acquirer computing device;
- upon determining by the CCS server that the payment request is associated with the potential transaction record:
- identifying, by the CCS server, a sub-account associated with the payment request based upon identification information of the user computing device or the merchant-acquirer computing device;
- upon approving the payment request, simultaneously updating, by the CCS server, a sub-account balance of the identified sub-account and the copy of the account balance;
- simultaneously transmitting, by the CCS server to the system of record server, a message to reflect the approval of the payment request and update the balance stored in the system of record server;
- synchronizing, by the CCS server, the copy of the account balance with the account balance maintained in the record in the system of record server;
- and
- transmitting, by the CCS server to the user computing device, a confirmation message configured to be rendered at the user computing device to indicate that a recurring transaction has been completed.
A computer-readable storage medium storing instructions that, when executed by a computing system, cause the computing system to perform operations comprising:
- receiving, at a server, a financial transaction comprising an amount, a transaction type, and an account number for an account, wherein the account comprises a balance;
- determining, at the server, whether the financial transaction is a credit transaction or a debit transaction based on the transaction type;
- identifying, at the server, one or more sub-accounts to update according to the amount in the financial transaction, wherein each sub-account is associated with the account, wherein the sub-account comprises a balance containing at least a portion of the account balance;
- retrieving, by the server from a database, one or more sub-account records corresponding to the identified one or more sub-accounts;
- crediting, at the server in response to each credit transaction, at least one sub-account balance of the retrieved one or more sub-account records according to the amount in the financial transaction;
- debiting, at the server in response to each debit transaction, at least one sub-account balance of the retrieved one or more sub-account records according the amount in the financial transaction;
- storing, by the server in the database, the retrieved one or more sub-account records comprising the credited or debited at least one sub-account balance;
- and
- simultaneously synchronizing, by the server, the account balance with a copy of the account balance maintained in a record in a system of record server.
A system for separating accounts into sub-accounts comprising:
- a server, comprising a memory, a processor, and a transceiver, configured to:
- receive from a client device one or more requests to open an account and one or more sub-accounts associated with the account;
- communicate with a system of record server to establish the account;
- communicate, with a merchant-acquirer server, transaction data corresponding to a plurality of transactions;
- store the transaction data in one or more transaction records;
- and
- simultaneously communicate with the system of record server the transaction data corresponding to the plurality of financial transactions;
- and
- one or more databases, configured to:
- receive instructions, from the server, to store information corresponding to the account, including sub-account identifiers corresponding to the sub-accounts, in one ore more sub-account records;
- and
- store the transaction data in the one or more transaction records.
Dependencies are inferred from the claim text.