# US 2018/0005323 A1 · Graphical user interface for tracking transactions

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2018/0005323 A1
- Document ID: US20180005323A1
- Status: Published application
- Kind: A1
- Application number: 15/199,724
- Filed: 2016-06-30
- Published: 2018-01-04
- Earliest claimed: 2016-06-30
- Assignees: Square, Inc.
- Applicants: Square, Inc.
- Inventors: Brian GRASSADONIA
- Web page: https://patentgrep.com/patent/US20180005323A1

## CPC

- G06Q 40/12: Accounting
- 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

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.

## Claims

### Claim 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.

### Claim 2 (depends on 1)

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.

### Claim 3 (depends on 1)

The method of claim 1, wherein a color of a polygon represents the scheduled transaction status of the scheduled transaction.

### Claim 4 (depends on 1)

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.

### Claim 5 (depends on 1)

The method of claim 1, wherein the scheduled transaction polygon further includes an indication that the scheduled transaction is a recurring transaction.

### Claim 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.

### Claim 7 (depends on 6)

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.

### Claim 8 (depends on 7)

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.

### Claim 9 (depends on 7)

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.

### Claim 10 (depends on 6)

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.

### Claim 11 (depends on 6)

The one or more computer-readable storage media according to claim 6, wherein the plurality of transactions include messages other than debits and credits.

### Claim 12 (depends on 11)

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.

### Claim 13 (depends on 6)

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.

### Claim 14 (depends on 6)

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.

### Claim 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 a linked object on a user interface, a request to view data for a plurality of the transaction records;
generating, by the server, one or more messages comprising data from the plurality of transaction records;
transmitting, by the server to a client device, the one or more messages comprising data from the plurality of transaction records;
generating, by the client application, a conversational view on the user interface of the data from the plurality of transaction records; and
transmitting, by the client application, instructions to display the data from the plurality of transaction records in the conversational view.

### Claim 16 (depends on 15)

The computer-implemented method of claim 15, wherein the 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.

### Claim 17 (depends on 15)

The computer-implemented method according to claim 15 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 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.

### Claim 18 (depends on 15)

The computer-implemented method according to claim 15 further comprising:
receiving, at the client application, a request to display a predicted balance;
determining, by the client device, a future date for the predicted balance;
summing, by the client device, one or more recurring transactions that are scheduled to occur between a present time and the future date to generate the predicted balance; and
presenting, by the client device, the predicted balance in response to the request to display the predicted balance.

### Claim 19 (depends on 15)

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.

### Claim 20 (depends on 15)

The computer-implemented method according to claim 15, 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.

### Claim 21

A system comprising:
a server comprising:
a server memory;
one or more server processors;
a server transceiver configured to receive a plurality of financial transactions from at least one merchant-acquirer server and a system of record;
a database configured to store transaction data contained in the plurality of financial transactions; and
a client application configured to run on a client device, the client device comprising a processor communicatively coupled to a client memory and operable to execute instructions stored in the client memory, the client application configured to:
communicate with the server to send and to receive the transaction data;
receive a request to display a conversational view of the transaction data; and
present a graphical user interface, in response to the request, including the conversational view of the transaction data, wherein the conversational view includes one or more polygons, with each polygon configured to contain transaction data from the database.

### Claim 22 (depends on 21)

The system according to claim 21, wherein the client application is further configured to receive an input comprising a scheduled financial transaction comprising a payment date, and the client application is further configured to transmit the scheduled financial transaction to the server; and
the one or more server processors and the server memory are further configured to pay the scheduled financial transaction when a current date matches the payment date of the scheduled financial transaction.

### Claim 23 (depends on 22)

The system according to claim 22, wherein the client application is further configured to display an additional polygon corresponding to the scheduled financial transaction to the conversational view.

### Claim 24 (depends on 23)

The system according to claim 23, wherein the server transceiver is further configured to transmit a message to the client device indicating payment of the scheduled financial transaction.

### Claim 25 (depends on 24)

The system according to claim 24, wherein the client application is further configured to update the polygon corresponding to the scheduled financial transaction in response to the message indicating payment of the scheduled financial transaction.

### Claim 26 (depends on 21)

The system according to claim 21, wherein the server transceiver is further configured to receive a payment request, and, in response to the payment request, the server is further configured to determine whether an account corresponding to the client device has sufficient funds to satisfy the payment request.

### Claim 27 (depends on 26)

The system according to claim 26, wherein, if the server determines that the account has insufficient funds to satisfy the payment request, the server is further configured to transmit a message warning of an overdraft to the client application.

### Claim 28 (depends on 27)

The system according to claim 27, wherein the client application is further configured to generate a notification on the client device of the overdraft.

### Claim 29 (depends on 28)

The system according to claim 28, wherein the notification on the client device further comprises a selectable graphical user interface element to deny the payment request.

### Claim 30 (depends on 21)

The system according to claim 21, wherein the client application is further configured to display a polygon indicating a transaction is a recurring transaction.
