Graphical user interface for tracking transactions
Embodiments of the present disclosure include a server that receives a plurality of financial transactions and stores information corresponding to those transactions in a database. The server can communicate with a client application to communicate transaction data and to display the transaction data in a conversational view. The conversational view includes a graphical user interface having one or more polygons that contain the transaction data.
1. A method comprising:
generating, by a server, in a transaction database a database record of each transaction of a plurality of transactions comprising transaction data from a merchant-acquirer server or a system of record server, wherein the record of each transaction comprises a credit or a debit to an account;
generating, by the server, a graphical user interface for display by an application executing on a user computing device that presents a summary of the transactions in a conversational view, wherein the conversational view comprises two columns, wherein debits and credits are presented in different columns, and wherein each debit or credit is displayed in a corresponding polygon having a field that is populated with transaction data from the transaction database;
determining, by the server, a scheduled transaction status of a scheduled transaction record of the transaction database, wherein the scheduled transaction record comprises a transaction to be scheduled;
generating, by the server, a scheduled transaction polygon of the conversational view on the graphical user interface for display on the user computing device, the scheduled transaction polygon comprising scheduled transaction data from the scheduled transaction record, the scheduled transaction data including a scheduled transaction status, wherein, when the scheduled transaction status is paid, the scheduled transaction polygon comprises text displaying a debit amount and a payee or subject of the transaction, and
wherein, when the scheduled transaction status is unpaid, the scheduled transaction polygon comprises one or more interface elements configured to receive a selection to complete the scheduled transaction from the application executing on the user computing device;
upon receiving, by the server from the user computing device executing the application, an activation of the one or more interface elements indicating the selection to complete the scheduled transaction:
generating, by the server, a transaction request to complete the scheduled transaction;
updating, by the server, the scheduled transaction status of the scheduled transaction record to reflect the generation of the transaction request; and
updating, by the server, the text of the scheduled transaction polygon based upon the updated scheduled transaction status.
2. The method of claim 1 , wherein the selection of the one or more interface elements comprises detecting a touch of the scheduled transaction polygon on the graphical user interface.
3. The method of claim 1 , wherein a color of a polygon represents the scheduled transaction status of the scheduled transaction.
4. The method of claim 1 , further comprising generating a second polygon comprising text displaying a reminder to make a payment, wherein the second polygon further includes a button to enable completing the payment.
5. The method of claim 1 , wherein the scheduled transaction polygon further includes an indication that the scheduled transaction is a recurring transaction.
6. One or more computer-readable storage media storing instructions that, when executed by a computing system, cause the computing system to perform operations comprising:
receiving, at a server, a plurality of transactions from at least one merchant-acquirer server or a system of record server, the transactions associated with an account having an account balance;
recording, by the server, a plurality of transaction records in a database, wherein the plurality of transaction records correspond to respective transactions of the plurality of transactions;
receiving, by the server from a client application executing on a client device, a request to generate a conversational view of at least a portion of the plurality of transaction records;
selecting, by the server, the portion of the plurality of transaction records; and
transmitting, from the server in response to the request, the selected transaction records to the client application executing on the client device for generating the conversational view of the portion of the plurality of transaction records, wherein the conversational view comprises a graphical user interface of a plurality of polygons corresponding to respective transaction records, the conversational view for display by the client application executing on the client device.
7. The one or more computer-readable storage media according to claim 6 , the operations further comprising:
comparing, by the server, the plurality of transactions to determine whether there are one or more matching transactions;
identifying, by the server, one or more groups of the one or more matching transactions;
generating, by the server for each group of the one or more matching transaction records, one or more recurring transactions that are at least similar to a corresponding group of the one or more matching transactions; and
storing, by the server, the one or more recurring transaction records in the database, wherein each recurring transaction record comprises an amount.
8. The one or more computer-readable storage media according to claim 7 , wherein the conversational view includes a recurring transaction in a polygon that identifies the recurring transaction as recurring.
9. The one or more computer-readable storage media according to claim 7 , the operations further comprising:
receiving, at the client application, a request to display a predicted balance, the request comprising a future date of the predicted balance;
retrieving, by the client application, one or more recurring transaction records corresponding to recurring transactions that are scheduled to occur between a present time and the future date;
computing, by the client application, a sum of the account balance and the amounts stored in the retrieved recurring transaction records to generate the predicted balance; and
presenting, by the client application, the predicted balance in response to the request to display the predicted balance.
10. The one or more computer-readable storage media according to claim 6 , wherein the plurality of transactions include debits and credits, and the conversational view presents the debits and credits in separate columns.
11. The one or more computer-readable storage media according to claim 6 , wherein the plurality of transactions include messages other than debits and credits.
12. The one or more computer-readable storage media according to claim 11 , wherein the messages are selected from the group consisting of reminders to pay bills, notices of insufficient funds, messages from third parties, balance updates, notices of upcoming payments, and notices of recurring payments.
13. The one or more computer-readable storage media according to claim 6 , wherein at least one of the plurality of transactions is a reminder to pay a bill, and the reminder to pay the bill includes a selectable graphical user interface element to pay the bill.
14. The one or more computer-readable storage media according to claim 6 , the operations further comprising:
receiving, at the client application from an input device, a selection of one of the plurality of transactions;
retrieving, by the client application, meta data associated with the selected transaction; and
transmitting, by the client device to the display of the client device, the meta data associated with the selected transaction.
15. A computer-implemented method comprising:
receiving, at a server logically located between a merchant-acquirer server and a system of record server, a plurality of financial transactions;
storing, at the server, a transaction record in a database, wherein each transaction record comprises data for a respective financial transaction;
receiving, at a client application upon a selection of an interface element on a user interface, a request to view data for a plurality of the transaction records;
generating, by the server, one or more transaction summary messages, wherein the transaction summary messages are based on previous transaction data from the plurality of transaction records;
generating, by the server, instructions to display one or more transaction summary messages as a conversational view on the user interface of the client application; and
transmitting, by the server to the client application, the instructions so as to cause the conversational view to be displayed by the client application.
16. The computer-implemented method of claim 15 , wherein the transaction summary messages are selected from the group consisting of debits, credits, reminders to pay bills, notices of insufficient funds, messages from third parties, balance updates, notices of upcoming payments, and notices of recurring payments.
17. The computer-implemented method according to claim 15 further comprising:
comparing, by the server, the plurality of financial transactions to determine whether there are one or more matching transactions;
identifying, by the server, one or more groups of the one or more matching transactions;
generating, by the server, for each group of the one or more matching transactions, one or more recurring transactions that are at least similar to a corresponding group of the one or more matching transactions; and
storing, by the server, the one or more recurring transactions in the database.
18. The computer-implemented method according to claim 15 further comprising:
receiving, from the client application, a request to display a predicted balance;
determining, by the server, a future date for the predicted balance;
summing, by the server, one or more recurring transactions that are scheduled to occur between a present time and the future date to generate the predicted balance; and
transmitting, by the server to the client application, the predicted balance in response to the request to display the predicted balance.
19. The computer-implemented method according to claim 15 , wherein the plurality of financial transactions include debits and credits, and the conversational view presents the debits and credits in separate columns.
20. The computer-implemented method according to claim 15 , wherein at least one of the plurality of financial transactions is a reminder to pay a bill, and the reminder to pay the bill, when displayed by the client application includes a selectable graphical user interface element to pay the bill.