IP Library Granted Patent US 9,589,298
Granted Patent B2
US 9,589,298 · App. 13/773,498 · Granted Mar 7, 2017

Financial account authentication

Inventors: Shubha Pant (Banglore, IN); Nikhil Nadkarni (Fremont, CA); Vinay Nagaraj (Santa Clara, CA); Jordan Reed (Carmichael, CA); Peter Hazlehurst (Foster City, CA)
Assignee: Yodlee, Inc.
G06Q40/00G06Q40/02
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,589,298
App. No.
13/773,498
Granted
Mar 7, 2017
Kind
B2
Abstract

Methods, systems, and apparatus, including computer programs encoded on computer storage media, for account authentication. A method includes receiving a user request to include financial data describing a financial account in an interface, the financial account being associated with a financial institution. The method further includes redirecting the user to a first webpage associated with the financial institution, where the user inputs into the first webpage login credentials for accessing the financial account. The method further includes, in response to the user inputting into the first webpage login credentials for accessing the financial account, receiving, from the financial institution, an access token other than the login credentials for accessing the financial account. The method further includes storing the access token for use in accessing and aggregating financial data describing the financial account.

Claims (66)

1. A computer-implemented method, comprising:

receiving, at a server computer system other than a computer system of a financial institution, a user request from a user device of a user having a financial account at the financial institution to include financial account information, from the financial account of the user at the financial institution, in an interface;

redirecting, by the server computer system, the user to a first webpage associated with the financial institution, wherein the user inputs into the first webpage login credentials to access financial account information of the user on the computer system of the financial institution;

in response to the user inputting into the first webpage login credentials to access the financial account information, receiving, at the server computer system from the computer system of the financial institution, an access token other than the login credentials to access the financial account information; and

storing, at the server computer system, the access token to access and aggregate the financial account information of the user.

2. The method of claim 1 , further comprising:

providing, by the server computer system, the access token to a second webpage associated with the financial institution;

in response to providing the access token to the second webpage, obtaining, from the computer system of the financial institution and at the server computer system, financial account information of the user; and

aggregating, at the server computer system, the obtained financial account information for use in describing the financial account in the interface.

3. The method of claim 2 , wherein the access token is configured to permit obtaining financial account information for a specified time period.

4. The method of claim 3 , further comprising:

determining, at the server computer system, that the specified time period has elapsed;

in response to determining that the specified time period has elapsed, redirecting, by the server computer system, the user to the first webpage associated with the financial institution, wherein the user inputs into the first webpage login credentials to access financial account information of the user on the computer system of the financial institution;

in response to the user inputting into the first webpage login credentials to access the financial account information, receiving, at the server computer system from the computer system of the financial institution, a second access token to access the financial account information; and

storing, at the server computer system, the second access token to access and aggregate the financial account information of the user.

5. The method of claim 2 , wherein the second webpage is configured to be inaccessible through non-whitelisted network connections.

6. The method of claim 5 , wherein the first webpage is configured to be accessible through at least some network connections that are non-whitelisted network connections for the second webpage.

7. The method of claim 1 , wherein the first webpage is not configured to accept access tokens.

8. The method of claim 1 , wherein the access token is invalidated when the user changes the login credentials for accessing the financial account.

9. The method of claim 1 , wherein the access token is invalidated when login credentials for accessing the financial account expire.

10. The method of claim 1 , wherein the access token is configured to limit a level of access within the financial account.

11. The method of claim 1 , wherein the access token is configured to restrict types of data that are accessible to the user.

12. A non-transitory computer storage medium encoded with a computer program, the program comprising instructions that when executed by data processing apparatus cause the data processing apparatus to perform operations comprising:

receiving, at a server computer system other than a computer system of a financial institution, a user request from a user device of a user having a financial account at the financial institution to include financial account information, from the financial account of the user at the financial institution, in an interface;

redirecting, by the server computer system, the user to a first webpage associated with the financial institution, wherein the user inputs into the first webpage login credentials to access financial account information of the user on the computer system of the financial institution;

in response to the user inputting into the first webpage login credentials to access the financial account information, receiving, at the server computer system from the computer system of the financial institution, an access token other than the login credentials to access the financial account information; and

storing, at the server computer system, the access token to access and aggregate the financial account information of the user.

13. The computer storage medium of claim 12 , further comprising:

providing, by the server computer system, the access token to a second webpage associated with the financial institution;

in response to providing the access token to the second webpage, obtaining, from the computer system of the financial institution and at the server computer system, financial account information of the user; and

aggregating, at the server computer system, the obtained financial account information for use in describing the financial account in the interface.

14. The computer storage medium of claim 13 , wherein the access token is configured to permit obtaining financial account information for a specified time period.

15. The computer storage medium of claim 14 , further comprising:

determining, at the server computer system, that the specified time period has elapsed;

in response to determining that the specified time period has elapsed, redirecting, by the server computer system, the user to the first webpage associated with the financial institution, wherein the user inputs into the first webpage login credentials to access financial account information of the user on the computer system of the financial institution;

in response to the user inputting into the first webpage login credentials to access the financial account information, receiving, at the server computer system from the computer system of the financial institution, a second access token to access the financial account information; and

storing, at the server computer system, the second access token to access and aggregate the financial account information of the user.

16. The computer storage medium of claim 13 , wherein the second webpage is configured to be inaccessible through non-whitelisted network connections.

17. The computer storage medium of claim 16 , wherein the first webpage is configured to be accessible through at least some network connections that are non-whitelisted network connections for the second webpage.

18. The computer storage medium of claim 12 , wherein the first webpage is not configured to accept access tokens.

19. The computer storage medium of claim 12 , wherein the access token is invalidated when the user changes the login credentials for accessing the financial account.

20. The computer storage medium of claim 12 , wherein the access token is invalidated when login credentials for accessing the financial account expire.

21. The computer storage medium of claim 12 , wherein the access token is configured to limit a level of access within the financial account.

22. The computer storage medium of claim 12 , wherein the access token is configured to restrict types of data that are accessible to the user.

23. A system comprising one or more computers programmed to perform operations comprising:

receiving, at a server computer system other than a computer system of a financial institution, a user request from a user device of a user having a financial account at the financial institution to include financial account information, from the financial account of the user at the financial institution, in an interface;

redirecting, by the server computer system, the user to a first webpage associated with the financial institution, wherein the user inputs into the first webpage login credentials to access financial account information of the user on the computer system of the financial institution;

in response to the user inputting into the first webpage login credentials to access the financial account information, receiving, at the server computer system from the computer system of the financial institution, an access token other than the login credentials to access the financial account information; and

storing, at the server computer system, the access token to access and aggregate the financial account information of the user.

24. The system of claim 23 , further comprising:

providing, by the server computer system, the access token to a second webpage associated with the financial institution;

in response to providing the access token to the second webpage, obtaining, from the computer system of the financial institution and at the server computer system, financial account information of the user; and

aggregating, at the server computer system, the obtained financial account information for use in describing the financial account in the interface.

25. The system of claim 24 , wherein the access token is configured to permit obtaining financial account information for a specified time period.

26. The system of claim 25 , further comprising:

determining, at the server computer system, that the specified time period has elapsed;

in response to determining that the specified time period has elapsed, redirecting, by the server computer system, the user to the first webpage associated with the financial institution, wherein the user inputs into the first webpage login credentials to access financial account information of the user on the computer system of the financial institution;

in response to the user inputting into the first webpage login credentials to access the financial account information, receiving, at the server computer system from the computer system of the financial institution, a second access token to access the financial account information; and

storing, at the server computer system, the second access token to access and aggregate the financial account information of the user.

27. The system of claim 24 , wherein the second webpage is configured to be inaccessible through non-whitelisted network connections.

28. The system of claim 27 , wherein the first webpage is configured to be accessible through at least some network connections that are non-whitelisted network connections for the second webpage.

29. The system of claim 23 , wherein the first webpage is not configured to accept access tokens.

30. The system of claim 23 , wherein the access token is invalidated when the user changes the login credentials for accessing the financial account.

31. The system of claim 23 , wherein the access token is invalidated when login credentials for accessing the financial account expire.

32. The system of claim 23 , wherein the access token is configured to limit a level of access within the financial account.

33. The system of claim 23 , wherein the access token is configured to restrict types of data that are accessible to the user.

Assignments (3)
RELEASE OF SECURITY INTEREST Recorded Aug 26, 2025
From: ROYAL BANK OF CANADA, AS COLLATERAL AGENT
To: YODLEE, INC.
Reel/Frame 072118/0612 →
GRANT OF SECURITY INTEREST IN PATENT Recorded Nov 25, 2024
From: YODLEE, INC.
To: ROYAL BANK OF CANADA, AS COLLATERAL AGENT
Reel/Frame 069441/0749 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 12, 2013
From: PANT, SHUBHA; NADKARNI, NIKHIL; NAGARAJ, VINAY; REED, JORDAN; HAZLEHURST, PETER
To: YODLEE, INC.
Reel/Frame 030204/0633 →
Continuity (1)
Related Publication 20140236792A1 · Aug 21, 2014