IP Library › Granted Patent US 9,858,617
Granted Patent B2
US 9,858,617 · App. 15/639,195 · Granted Jan 2, 2018

Systems and methods for aggregating and managing financial service accounts

Inventors: Hannes M. Jouhikainen (Arlington, VA); Luke A. Hammock (Washington, DC); Janusz M. Niczyporuk (Vienna, VA)
Assignee: Capital One Financial Corporation
G06Q40/02G06Q20/227G06Q40/025
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 9,858,617
App. No.
15/639,195
Granted
Jan 2, 2018
Kind
B2
Abstract

The disclosed embodiments include methods and systems for providing an aggregated financial service account based on multiple private label financial accounts. In one embodiment, a process is disclosed that may include receiving a first request from a user for a first private label financial account that is usable for purchases associated with a first merchant and approving the first request for the first private label financial account. The method may also include receiving a request from the user for a second private label financial account that is usable for purchases associated with a second merchant and approving the second request for the second private label financial account. In one aspect, the method may also include generating an aggregated financial account based on the first and second private label accounts such that the aggregated financial account may be used for purchases with the first merchant or with the second merchant.

Claims (64)

1. A system for providing an aggregated financial account for a user, the aggregated financial account being associated with a plurality of distinct private label financial accounts, comprising:

one or more memory devices storing:

software instructions;

a plurality of parameters associated with a first private label financial account of the user, the first private label financial account being usable for purchases associated with a first merchant but not for purchases associated with a second merchant; and

a plurality of parameters associated with a second private label financial account of the user, the second private label financial account being usable for purchases associated with the second merchant but not for purchases associated with the first merchant; and

one or more processors configured to execute the software instructions to:

provide an aggregated account record for the aggregated financial account, the aggregated account record including:

a first set of parameters associated with the first private label financial account;

a second set of parameters associated with the second private label financial account; and

a third set of parameters based on an aggregation of a corresponding one or more of the first set of parameters and the second set of parameters;

provide instructions to a user device to display an aggregated account graphical user interface, the interface being configured to access the aggregated account record to display content associated with the aggregated financial account, the first private label financial account, and the second private label financial account;

receive, from the user device, responsive to an input on the aggregated account graphical user interface displayed thereon, a request to perform a first task associated with the first private label financial account; and

provide instructions to the user device to:

display a first account graphical user interface based on the received request; and

enable the first task to be performed with respect to the first private label financial account, the first account graphical user interface including at least one of a logo of the first merchant or first merchant-branded text, such that the first account graphical user interface appears to be associated with the first merchant.

2. The system of claim 1 , wherein the first task provides payment toward a balance associated with the first private label financial account.

3. The system of claim 2 , wherein the one or more processors are configured to adjust a balance parameter of the aggregated account record based on the payment associated with the first private label financial account.

4. The system of claim 1 , wherein the one or more processors are further configured to:

receive, from the user device, responsive to an input on the aggregated account graphical user interface displayed thereon, a request to perform a second task associated with the second private label financial account; and

provide instructions to the user device to:

display a second account graphical user interface based on the received request to perform a second task; and

enable the second task to be performed with respect to the second private label financial account, the second account graphical user interface including at least one of a logo of the second merchant and second merchant-branded text, such that the second account graphical user interface appears to be associated with the second merchant.

5. The system of claim 4 , wherein:

the second task provides payment toward a balance associated with the second private label financial account; and

the one or more processors are configured to adjust a balance parameter of the aggregated account record based on the payment associated with the second private label financial account.

6. The system of claim 1 , wherein the aggregated financial account is usable for purchases with both the first and second merchants.

7. The system of claim 1 , wherein the aggregated financial account is associated with a financial service account card usable for purchases with both the first and second merchants.

8. The system of claim 7 , wherein the financial service account card includes a visible identifier of both the first and second merchants.

9. The system of claim 6 , wherein the aggregated financial account is associated with a financial service account card associated with the first merchant but not the second merchant.

10. The system of claim 1 , wherein the one or more processors are further configured to:

receive, from the user device, responsive to an input on the aggregated account graphical user interface displayed thereon, a request to perform a third task associated with the aggregated financial account, the third task providing payment toward an aggregated balance associated with the aggregated financial account; and

adjust both a balance parameter of the first private label financial account and a balance parameter of the second private label financial account based on the payment toward an aggregated balance associated with the aggregated financial account.

11. A computer-implemented method for providing an aggregated financial account for a user, the aggregated financial account being associated with a plurality of distinct private label financial accounts, comprising:

providing, by one or more processors, an aggregated account record for the aggregated financial account, the aggregated account record including:

a first set of parameters associated with a first private label financial account, the first private label financial account being usable for purchases associated with a first merchant but not for purchases associated with a second merchant;

a second set of parameters associated with the second private label financial account, the second private label financial account being usable for purchases associated with the second merchant but not for purchases associated with the first merchant; and

a third set of parameters based on an aggregation of a corresponding one or more of the first set of parameters and the second set of parameters;

providing instructions to a user device to display an aggregated account graphical user interface, the interface being configured to access the aggregated account record to display content associated with the aggregated financial account, the first private label financial account, and the second private label financial account;

receiving, from the user device, responsive to an input on the aggregated account graphical user interface displayed thereon, a request to perform a first task associated with the first private label financial account; and

providing instructions to the user device to:

display a first account graphical user interface based on the received request; and

enable the task to be performed with respect to the first private label financial account, the first account graphical user interface including at least one of a logo of the first merchant or first merchant-branded text, such that the first account graphical user interface appears to be associated with the first merchant.

12. The method of claim 11 , wherein the receiving the request to perform the first task associated with the first private label financial account includes receiving a request to provide payment toward a balance associated with the first private label financial account, the method further comprising adjusting a balance parameter of the aggregated financial account based on the payment associated with the first private label financial account.

13. The method of claim 11 , wherein the aggregated financial account is usable for purchases with both the first and second merchants.

14. The method of claim 11 , wherein the aggregated financial account is associated with a financial service account card usable for purchases with both the first and second merchants.

15. The method of claim 14 , wherein the financial service account card includes a visible identifier of both the first and second merchants.

16. The method of claim 13 , wherein the aggregated financial account is associated with a financial service account card associated with the first merchant but not the second merchant.

17. The method of claim 11 , wherein the method further comprises:

receiving, from the user device, responsive to an input on the aggregated account graphical user interface displayed thereon, a request to perform a second task associated with the aggregated financial account, the second task providing payment toward an aggregated balance associated with the aggregated financial account; and

adjusting both a balance parameter of the first private label financial account and a balance parameter of the second private label financial account based on the payment toward an aggregated balance associated with the aggregated financial account.

18. A computer-readable storage medium storing instructions that, when executed by a processor, cause the processor to perform operations for providing an aggregated financial account for a user, the aggregated financial account being associated with a plurality of distinct private label financial accounts, the operations comprising:

providing an aggregated account record for the aggregated financial account, the aggregated account record including:

a first set of parameters associated with a first private label financial account, wherein the first private label financial account is usable for purchases associated with a first merchant but not for purchases associated with a second merchant;

a second set of parameters associated with the second private label financial account, wherein the second private label financial account is usable for purchases associated with the second merchant but not for purchases associated with the first merchant; and

a third set of parameters based on an aggregation of a corresponding one or more of the first set of parameters and the second set of parameters;

providing instructions to a user device to display an aggregated account graphical user interface, the interface being configured to access the aggregated account record to display content associated with the aggregated financial account, the first private label financial account, and the second private label financial account;

receiving, from the user device, responsive to an input on the aggregated account graphical user interface displayed thereon, a request to perform a first task associated with the first private label financial account; and

providing instructions to the user device to:

display a first account graphical user interface based on the received request; and

enable the task to be performed with respect to the first private label financial account, the first account graphical user interface including at least one of a logo of the first merchant or first merchant-branded text, such that the first account graphical user interface appears to be associated with the first merchant.

19. The computer-readable storage medium of claim 18 , wherein the instructions further cause the processor to perform operations comprising:

receiving, from the user device, responsive to an input on the aggregated account graphical user interface displayed thereon, a request to perform a second task associated with the aggregated financial account, the second task providing payment toward an aggregated balance associated with the aggregated financial account; and

adjusting both a balance parameter of the first private label financial account and a balance parameter of the second private label financial account based on the payment toward an aggregated balance associated with the aggregated financial account.

20. The computer-readable storage medium of claim 18 , wherein the receiving the request to perform the first task associated with the first private label financial account includes receiving a request to provide payment toward a balance associated with the first private label financial account, the operations further comprising adjusting a balance parameter of the aggregated financial account based on the payment associated with the first private label financial account.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 20, 2019
From: CAPITAL ONE FINANCIAL CORPORATION
To: CAPITAL ONE SERVICES, LLC
Reel/Frame 049530/0899 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 30, 2017
From: JOUHIKAINEN, HANNES M.; HAMMOCK, LUKE A.; NICZYPORUK, JANUSZ M.
To: CAPITAL ONE FINANCIAL CORPORTION
Reel/Frame 043072/0006 →
Continuity (3)
Continuation 14089180 · Nov 25, 2013
Provisional Application 61776284 · Mar 11, 2013
Related Publication 20170301012A1 · Oct 19, 2017