Abstract: A system and method for linking to accounts using credential-less authentication that includes: within a first application context at an account-linking computing service: receiving a request to establish an account link, establishing the account link to a user account of an account service using user credentials, and receiving user identifying information of the first application context and storing the user identifying information in association with the account link; and within a second application context at the account-linking computing service: receiving user identifying information of the second application context, searching and identifying a candidate account link using the user identifying information of the second application context, verifying eligibility for access to the account link, and permitting access to the account link upon successful verification of eligibility.

Abstract: Systems and methods for programmatic access of external financial service systems. An application proxy instance is created that simulates an application of an external financial service system. A normalized account request is received for financial data of the external financial service system for a specified account. The normalized account request is provided by an external financial application system by using a financial data API of the financial platform system. Responsive to the normalized account request, communication is negotiated with the external financial service system by using the application proxy instance to access the requested financial data from the external financial service system by using a proprietary Application Programming Interface (API) of the external financial service system. The financial data is provided to the external financial application system as a response to the normalized account request.

Abstract: Systems and methods for programmatic access of a financial institution system. A normalized API request provided by an application system specifies user information corresponding to at least one account endpoint of an external financial institution system. Responsive to the request, at least one application proxy instance associated with the normalized API request is used to collect transaction information from a corresponding financial institution system by providing the financial institution system with a proprietary API request that specifies at least account credentials associated with the user information. The transaction information is included in at least one proprietary API response provided by the financial institution system. A normalized API response is generated based on the collected transaction information and provided to the application system.

Abstract: A system and method for linking to accounts using credential-less authentication that includes: within a first application context at an account-linking computing service: receiving a request to establish an account link, establishing the account link to a user account of an account service using user credentials, and receiving user identifying information of the first application context and storing the user identifying information in association with the account link; and within a second application context at the account-linking computing service: receiving user identifying information of the second application context, searching and identifying a candidate account link using the user identifying information of the second application context, verifying eligibility for access to the account link, and permitting access to the account link upon successful verification of eligibility.

Abstract: A system and method for secure permissioning of access to user accounts, including secure distribution of aggregated user account data can include generating a financial report based on account information associated with one or more user accounts; receiving a financial report request for the financial report of the user account, wherein the financial report request is identified as being received from a third-party system; generating an audit report token associated with the financial report; sharing the audit token with the first third-party system in response to the financial report request; and providing the first third-party system account access to the financial report through the report token, where the audit report token can be shared with a second third-party system and provided by the second third-party system in order to confirm authorization to the report and integrity of the report.

Abstract: Systems and methods for programmatic access of external financial service systems. An application proxy instance is created that simulates an application of an external financial service system. A normalized account request is received for financial data of the external financial service system for a specified account. The normalized account request is provided by an external financial application system by using a financial data API of the financial platform system. Responsive to the normalized account request, communication is negotiated with the external financial service system by using the application proxy instance to access the requested financial data from the external financial service system by using a proprietary Application Programming Interface (API) of the external financial service system. The financial data is provided to the external financial application system as a response to the normalized account request.

Abstract: A system and method for secure permissioning of access to user accounts, including secure distribution of aggregated user account data can include generating a financial report based on account information associated with one or more user accounts; receiving a financial report request for the financial report of the user account, wherein the financial report request is identified as being received from a third-party system; generating an audit report token associated with the financial report; sharing the audit token with the first third-party system in response to the financial report request; and providing the first third-party system account access to the financial report through the report token, where the audit report token can be shared with a second third-party system and provided by the second third-party system in order to confirm authorization to the report and integrity of the report.

Abstract: Systems and methods for programmatic access of external financial service systems. An application proxy instance is created that simulates an application of an external financial service system. A normalized account request is received for financial data of the external financial service system for a specified account. The normalized account request is provided by an external financial application system by using a financial data API of the financial platform system. Responsive to the normalized account request, communication is negotiated with the external financial service system by using the application proxy instance to access the requested financial data from the external financial service system by using a proprietary Application Programming Interface (API) of the external financial service system. The financial data is provided to the external financial application system as a response to the normalized account request.

Abstract: Systems and techniques are disclosed for accessing accounts associated with a user and estimating a value of an attribute associated with the user based upon the retrieved account information. Transaction data associated with an account at an external user account system is received. The transactions are categorized into transaction groups. For each transaction group, a confidence value that the group is associated with the attribute is estimated, based at least in part upon a distribution of transaction amounts for the transactions of the group over a time period associated with the group. An attribute value is estimated for each group, based at least in part upon the transaction amounts of the transaction of the group. In addition a value of the attribute for a future time period may be predicted based upon the transaction groups.

Abstract: Systems and techniques are disclosed for accessing accounts associated with a user and estimating a value of an attribute associated with the user based upon the retrieved account information. Transaction data associated with an account at an external user account system is received. The transactions are categorized into transaction groups. For each transaction group, a confidence value that the group is associated with the attribute is estimated, based at least in part upon a distribution of transaction amounts for the transactions of the group over a time period associated with the group. An attribute value is estimated for each group, based at least in part upon the transaction amounts of the transaction of the group. In addition a value of the attribute for a future time period may be predicted based upon the transaction groups.

Abstract: A permissions management system is disclosed for enabling a user to securely authorize a third-party system to access user account data and initiate transactions related to a user account, without disclosing to the third-party system account credentials. The system enables the user to also securely de-authorize the third-party system. For example, records may be automatically generated that securely store account information, including one or more permissions related to the account and/or the third-party. A token associated with a record may be shared with the third-party system, but neither the record itself, nor the user account credentials, may be shared with the third-party. Accordingly, the third-party may request user account data and/or initiate transactions by providing the token, but does not itself know, e.g., the user account credentials. Further, the user may set various permissions related to the token, and may also revoke the token (e.g.

Abstract: A permissions management system is disclosed for enabling a user to securely authorize a third-party system to access user account data and initiate transactions related to a user account, without disclosing to the third-party system account credentials. The system enables the user to also securely de-authorize the third-party system. For example, records may be automatically generated that securely store account information, including one or more permissions related to the account and/or the third-party. A token associated with a record may be shared with the third-party system, but neither the record itself, nor the user account credentials, may be shared with the third-party. Accordingly, the third-party may request user account data and/or initiate transactions by providing the token, but does not itself know, e.g., the user account credentials. Further, the user may set various permissions related to the token, and may also revoke the token (e.g.

Abstract: A permissions management system is disclosed for enabling a user to securely authorize a third-party system to access user account data and initiate transactions related to a user account, without disclosing to the third-party system account credentials. The system enables the user to also securely de-authorize the third-party system. For example, records may be automatically generated that securely store account information, including one or more permissions related to the account and/or the third-party. A token associated with a record may be shared with the third-party system, but neither the record itself, nor the user account credentials, may be shared with the third-party. Accordingly, the third-party may request user account data and/or initiate transactions by providing the token, but does not itself know, e.g., the user account credentials. Further, the user may set various permissions related to the token, and may also revoke the token (e.g.

Abstract: A permissions management system is disclosed for enabling a user to securely authorize a third-party system to access user account data and initiate transactions related to a user account, without disclosing to the third-party system account credentials. The system enables the user to also securely de-authorize the third-party system. For example, records may be automatically generated that securely store account information, including one or more permissions related to the account and/or the third-party. A token associated with a record may be shared with the third-party system, but neither the record itself, nor the user account credentials, may be shared with the third-party. Accordingly, the third-party may request user account data and/or initiate transactions by providing the token, but does not itself know, e.g., the user account credentials. Further, the user may set various permissions related to the token, and may also revoke the token (e.g.

Abstract: A user account evaluation system is disclosed for evaluating risk associated with a user account. The system may obtain user account data associated with many user accounts, select a statistically significant subset of the user accounts, and then process (e.g., to determine types of the user accounts, etc.) and analyze the subset of user accounts to generate a plurality of evaluation models. When a new user account is accessed by the system, user account data may be obtained for the new user account, and the new user account may be evaluated based on the plurality of evaluation models. Accordingly, a plurality of evaluation parameter scores may be generated for the new user account, each of which may indicate an amount of risk associated with the user account. Some embodiments of the present disclosure may include machine learning and/or artificial intelligence methods to improve evaluation of the user accounts.

Abstract: A permissions management system is disclosed for enabling a user to securely authorize access to user accounts and/or securely authorize execution of transactions related to user accounts via one or more application programming interfaces (“APIs”) and/or one or more authorization mechanisms.

Abstract: A permissions management system is disclosed for enabling a user to securely authorize access to user accounts and/or securely authorize execution of transactions related to user accounts via one or more application programming interfaces (“APIs”) and/or one or more authorization mechanisms.

Abstract: A system and method for secure permissioning of access to user accounts, including secure distribution of aggregated user account data can include generating a financial report based on account information associated with one or more user accounts; receiving a financial report request for the financial report of the user account, wherein the financial report request is identified as being received from a third-party system; generating an audit report token associated with the financial report; sharing the audit token with the first third-party system in response to the financial report request; and providing the first third-party system account access to the financial report through the report token, where the audit report token can be shared with a second third-party system and provided by the second third-party system in order to confirm authorization to the report and integrity of the report.

Abstract: Systems and methods for programmatic access of a financial institution system. A normalized API request provided by an application system specifies user information corresponding to at least one account endpoint of an external financial institution system. Responsive to the request, at least one application proxy instance associated with the normalized API request is used to collect transaction information from a corresponding financial institution system by providing the financial institution system with a proprietary API request that specifies at least account credentials associated with the user information. The transaction information is included in at least one proprietary API response provided by the financial institution system. A normalized API response is generated based on the collected transaction information and provided to the application system.

Abstract: A permissions management system is disclosed for enabling a user to securely authorize a third-party system to access user account data and initiate transactions related to a user account, without disclosing to the third-party system account credentials. The system enables the user to also securely de-authorize the third-party system. For example, records may be automatically generated that securely store account information, including one or more permissions related to the account and/or the third-party. A token associated with a record may be shared with the third-party system, but neither the record itself, nor the user account credentials, may be shared with the third-party. Accordingly, the third-party may request user account data and/or initiate transactions by providing the token, but does not itself know, e.g., the user account credentials. Further, the user may set various permissions related to the token, and may also revoke the token (e.g.