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.
Legal claims defining the scope of protection. Each claim is shown in both the original legal language and a plain English translation.
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.
A system allows a user to connect their financial account to a third-party service (not the financial institution itself). The user requests to include financial information from their bank account in an application interface. The system redirects the user to the bank's webpage where they enter their username/password. The bank then sends back an access token (instead of the username/password) to the system. The system stores this access token to retrieve and combine the user's financial data for display in the app.
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.
The system, as described above, uses the received access token to retrieve financial data. The system sends the access token to a second webpage (or API endpoint) provided by the bank. In return, the bank sends the user's account information to the system. The system then combines this data with other information for the user to see in the application interface, like showing all their account balances in one place.
3. The method of claim 2 , wherein the access token is configured to permit obtaining financial account information for a specified time period.
In the system described in claim 2, the access token has a limited lifespan. It's only valid for a certain period of time, such as one hour. This improves security by reducing the window of opportunity for unauthorized access if the token is compromised.
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.
Building upon claims 3, when the access token's time period expires, the system requires the user to re-authenticate. The system checks if the access token's time is up. If so, the user is redirected to the bank's login page again. After the user logs in again, the bank sends a new access token to the system. The system then stores this new token for accessing and aggregating the financial data, repeating the authentication cycle.
5. The method of claim 2 , wherein the second webpage is configured to be inaccessible through non-whitelisted network connections.
Building on claim 2, the second webpage (or API endpoint) used to retrieve financial data from the bank is restricted. Only connections from pre-approved, "whitelisted" networks can access this page. This adds an extra layer of security, preventing unauthorized access to sensitive financial data even with a valid access token.
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.
Building on claims 5, the bank's initial login webpage, where the user enters their username/password, is more broadly accessible. Users can reach the login page from networks that are not on the "whitelist" required to access the second data retrieval page. This balances security with user convenience, allowing login from various locations while securing data access.
7. The method of claim 1 , wherein the first webpage is not configured to accept access tokens.
The initial login webpage provided by the bank, where the user enters their username and password, is designed to only accept login credentials. It does not accept access tokens as a form of authentication. This ensures that the initial authentication process always requires user credentials and is not bypassed by using access tokens directly.
8. The method of claim 1 , wherein the access token is invalidated when the user changes the login credentials for accessing the financial account.
The access token is linked to the user's login credentials. If the user changes their username or password for their bank account, the access token becomes invalid. This provides an additional security measure, ensuring that the system cannot access the user's financial data with an outdated or compromised access token after they update their credentials.
9. The method of claim 1 , wherein the access token is invalidated when login credentials for accessing the financial account expire.
The access token becomes invalid when the user's login credentials expire. For example, if the bank requires passwords to be changed every 90 days, the access token will stop working when the 90 days are up, forcing the user to re-authenticate and obtain a new access token.
10. The method of claim 1 , wherein the access token is configured to limit a level of access within the financial account.
The access token is configured to limit the level of access to the financial account. For example, the token might only grant read-only access to account balances and transaction history, preventing the system from initiating transfers or making other changes to the account.
11. The method of claim 1 , wherein the access token is configured to restrict types of data that are accessible to the user.
The access token restricts the types of data that the system can access. For example, the token might allow access to account balances and transaction history, but prevent access to sensitive information like credit card numbers or personal identification details.
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.
A computer program stored on a non-transitory medium (like a hard drive or flash drive) allows a user to connect their financial account to a third-party service (not the financial institution itself). The user requests to include financial information from their bank account in an application interface. The system redirects the user to the bank's webpage where they enter their username/password. The bank then sends back an access token (instead of the username/password) to the system. The system stores this access token to retrieve and combine the user's financial data for display in the app.
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.
The computer program from claim 12 uses the received access token to retrieve financial data. The system sends the access token to a second webpage (or API endpoint) provided by the bank. In return, the bank sends the user's account information to the system. The system then combines this data with other information for the user to see in the application interface, like showing all their account balances in one place.
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.
In the computer program described in claim 13, the access token has a limited lifespan. It's only valid for a certain period of time, such as one hour. This improves security by reducing the window of opportunity for unauthorized access if the token is compromised.
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.
Building upon claims 14, when the access token's time period expires, the computer program requires the user to re-authenticate. The system checks if the access token's time is up. If so, the user is redirected to the bank's login page again. After the user logs in again, the bank sends a new access token to the system. The system then stores this new token for accessing and aggregating the financial data, repeating the authentication cycle.
16. The computer storage medium of claim 13 , wherein the second webpage is configured to be inaccessible through non-whitelisted network connections.
Building on claim 13, the second webpage (or API endpoint) used to retrieve financial data from the bank is restricted. Only connections from pre-approved, "whitelisted" networks can access this page. This adds an extra layer of security, preventing unauthorized access to sensitive financial data even with a valid access token.
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.
Building on claim 16, the bank's initial login webpage, where the user enters their username/password, is more broadly accessible. Users can reach the login page from networks that are not on the "whitelist" required to access the second data retrieval page. This balances security with user convenience, allowing login from various locations while securing data access.
18. The computer storage medium of claim 12 , wherein the first webpage is not configured to accept access tokens.
The initial login webpage provided by the bank, where the user enters their username and password, is designed to only accept login credentials, according to the computer program from claim 12. It does not accept access tokens as a form of authentication. This ensures that the initial authentication process always requires user credentials and is not bypassed by using access tokens directly.
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.
The access token is linked to the user's login credentials, according to the computer program from claim 12. If the user changes their username or password for their bank account, the access token becomes invalid. This provides an additional security measure, ensuring that the system cannot access the user's financial data with an outdated or compromised access token after they update their credentials.
20. The computer storage medium of claim 12 , wherein the access token is invalidated when login credentials for accessing the financial account expire.
The access token becomes invalid when the user's login credentials expire, according to the computer program from claim 12. For example, if the bank requires passwords to be changed every 90 days, the access token will stop working when the 90 days are up, forcing the user to re-authenticate and obtain a new access token.
21. The computer storage medium of claim 12 , wherein the access token is configured to limit a level of access within the financial account.
The access token is configured to limit the level of access to the financial account, according to the computer program from claim 12. For example, the token might only grant read-only access to account balances and transaction history, preventing the system from initiating transfers or making other changes to the 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.
The access token restricts the types of data that the system can access, according to the computer program from claim 12. For example, the token might allow access to account balances and transaction history, but prevent access to sensitive information like credit card numbers or personal identification details.
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.
A system comprised of one or more computers allows a user to connect their financial account to a third-party service (not the financial institution itself). The user requests to include financial information from their bank account in an application interface. The system redirects the user to the bank's webpage where they enter their username/password. The bank then sends back an access token (instead of the username/password) to the system. The system stores this access token to retrieve and combine the user's financial data for display in the app.
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.
The system, as described above, uses the received access token to retrieve financial data. The system sends the access token to a second webpage (or API endpoint) provided by the bank. In return, the bank sends the user's account information to the system. The system then combines this data with other information for the user to see in the application interface, like showing all their account balances in one place.
25. The system of claim 24 , wherein the access token is configured to permit obtaining financial account information for a specified time period.
In the system described in claim 24, the access token has a limited lifespan. It's only valid for a certain period of time, such as one hour. This improves security by reducing the window of opportunity for unauthorized access if the token is compromised.
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.
Building upon claims 25, when the access token's time period expires, the system requires the user to re-authenticate. The system checks if the access token's time is up. If so, the user is redirected to the bank's login page again. After the user logs in again, the bank sends a new access token to the system. The system then stores this new token for accessing and aggregating the financial data, repeating the authentication cycle.
27. The system of claim 24 , wherein the second webpage is configured to be inaccessible through non-whitelisted network connections.
Building on claim 24, the second webpage (or API endpoint) used to retrieve financial data from the bank is restricted. Only connections from pre-approved, "whitelisted" networks can access this page. This adds an extra layer of security, preventing unauthorized access to sensitive financial data even with a valid access token.
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.
Building on claim 27, the bank's initial login webpage, where the user enters their username/password, is more broadly accessible. Users can reach the login page from networks that are not on the "whitelist" required to access the second data retrieval page. This balances security with user convenience, allowing login from various locations while securing data access.
29. The system of claim 23 , wherein the first webpage is not configured to accept access tokens.
The initial login webpage provided by the bank, where the user enters their username and password, is designed to only accept login credentials, according to the system in claim 23. It does not accept access tokens as a form of authentication. This ensures that the initial authentication process always requires user credentials and is not bypassed by using access tokens directly.
30. The system of claim 23 , wherein the access token is invalidated when the user changes the login credentials for accessing the financial account.
The access token is linked to the user's login credentials, according to the system described in claim 23. If the user changes their username or password for their bank account, the access token becomes invalid. This provides an additional security measure, ensuring that the system cannot access the user's financial data with an outdated or compromised access token after they update their credentials.
31. The system of claim 23 , wherein the access token is invalidated when login credentials for accessing the financial account expire.
The access token becomes invalid when the user's login credentials expire, according to the system described in claim 23. For example, if the bank requires passwords to be changed every 90 days, the access token will stop working when the 90 days are up, forcing the user to re-authenticate and obtain a new access token.
32. The system of claim 23 , wherein the access token is configured to limit a level of access within the financial account.
The access token is configured to limit the level of access to the financial account, according to the system described in claim 23. For example, the token might only grant read-only access to account balances and transaction history, preventing the system from initiating transfers or making other changes to the account.
33. The system of claim 23 , wherein the access token is configured to restrict types of data that are accessible to the user.
The access token restricts the types of data that the system can access, according to the system described in claim 23. For example, the token might allow access to account balances and transaction history, but prevent access to sensitive information like credit card numbers or personal identification details.
Cooperative Patent Classification codes for this invention. Click any code to explore related patents in that topic.
February 21, 2013
March 7, 2017
Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.