Abstract: Systems and methods for providing recommendations relating to payment methods include establishing a connection between a first application executing on a first server and a second application executing on a second server where the first and second applications are linked to a first account holder. The first application may receive invoice data of a plurality of invoices from the second application. The first application may identify that at least one recipient is enrolled to accept a second payment type with one or more second account holders. The first application may identify a subset of invoices corresponding to the at least one recipient, compute a difference between a first value corresponding to usage of a first payment type and a second value corresponding to usage of the second payment type, and present a recommendation to enroll the first account holder with the second payment type based on the difference.

Abstract: Systems and methods for providing recommendations relating to payment methods include establishing a connection between a first application executing on a first server and a second application executing on a second server where the first and second applications are linked to a first account holder. The first application may receive invoice data of a plurality of invoices from the second application. The first application may identify that at least one recipient is enrolled to accept a second payment type with one or more second account holders. The first application may identify a subset of invoices corresponding to the at least one recipient, compute a difference between a first value corresponding to usage of a first payment type and a second value corresponding to usage of the second payment type, and present a recommendation to enroll the first account holder with the second payment type based on the difference.

Abstract: Systems and methods for multidirectional integration of diverse unaffiliated processes and subsystems with client applications are disclosed. A method includes: presenting in a client application executing on a user device, a first graphical user interface including a listing of a plurality of unaffiliated applications administered by respective unaffiliated computing systems; receiving a request to integrate an unaffiliated application with the client application; identifying a set of primary data that relates to the unaffiliated application; updating permission settings that authorize transmission of the set of primary data to the unaffiliated computing system; transmitting the set of primary data to the unaffiliated computing system; and presenting the unaffiliated application interface in a second graphical user interface of the client application by providing the executable code to the client application without requiring a user to provide the set of primary data to the unaffiliated application.

Abstract: Systems, methods, and apparatuses for automated population of responses into query fields of a form are discussed. The responses are based on data in a networked user data repository maintained by a first party, and the form is presented by a second party. A login request for access to data in the user data repository may be received from a remote computing device. If access to the data in the user data repository is authorized, descriptors for at least one of the query fields may be received, and based on the descriptors, it may be determined whether any responses to any query fields are contained in the user data repository. Query fields may be populated with responses obtained through the data repository. The user provides the second party with information that is made available to the first party without separately inputting the information into the form of the second party.

Abstract: Systems and methods for receiving an enterprise resource dataset associated with a customer from an enterprise application associated with the customer, the enterprise resource dataset including a plurality of financial inputs captured on or before a first date, a plurality of customer recommendations, and a plurality of recommendation replies, receiving, from a first machine learning model, a predicted customer state including one or more predicted financial outputs corresponding with the predicted customer state at a second date subsequent to the first date, providing the plurality of financial inputs to a second machine learning model trained to predict a customer recommendations, determining, a customer recommendation corresponding to an action to be performed at a third date subsequent to the first date, wherein performing the action causes the first machine learning model to predict an updated customer state differing from the predicted customer state.

Abstract: This disclosure is directed to integrating unaffiliated applications, or the processes and/or subsystems (e.g., application interfaces) of unaffiliated applications, with client applications to enable the client applications to provide new capabilities not otherwise available through the client application. The disclosed approach allows users to access new functionality within the operating environment of the client application, without accessing unaffiliated applications and undergoing separate authentication and data exchange with each unaffiliated application. Functionality of an unaffiliated application can be integrated by, for example, incorporating such processes and subsystems as interactive user interfaces, widgets, applets, plugins, etc., of unaffiliated applications.

Abstract: Systems and methods for receiving an enterprise resource dataset includes a plurality of financial inputs captured associated with a customer from an enterprise application associated with the customer, providing the plurality of financial inputs to a machine learning model trained to predict a customer state using a plurality of training financial inputs and a plurality of training financial outputs, each of the plurality of training financial inputs corresponding to financial data and each of the plurality of training financial outputs corresponding with financial data, determining, responsive to providing the plurality of financial inputs to the machine learning model, a future customer state of the customer, including a predicted financial output, at a fourth date, and generating one or more financial recommendations based at least partially on the determined future customer state of the customer.

Abstract: Disclosed are methods, systems, and devices for facilitating secure and private communications, via a website or application of a third-party computing system (TPCS), between a user device and a service provider computing system (SPCS). The communications may be conducted via a frame in a website served by the TPCS. The TPCS may serve a website that incorporates a customizable SDK component provided by the SPCS. The communications allow the user to, for example, open a new account. The SDK component may be initialized via a script from the SPCS, and authenticated via a session token obtained from the SPCS via the TPCS. The SDK component may provide user information, input into the frame, to the SPCS via API calls to the SPCS. The user does not navigate away from the website while securely engaging the SPCS. The third-party/partner need not develop its own user interface, security protocols, etc.

Abstract: Disclosed are methods, systems, and devices for facilitating secure and private communications, via a website or application of a third-party computing system (TPCS), between a user device and a service provider computing system (SPCS). The communications may be conducted via a frame in a website served by the TPCS. The TPCS may serve a website that incorporates a customizable SDK component provided by the SPCS. The communications allow the user to, for example, open a new account. The SDK component may be initialized via a script from the SPCS, and authenticated via a session token obtained from the SPCS via the TPCS. The SDK component may provide user information, input into the frame, to the SPCS via API calls to the SPCS. The user does not navigate away from the website while securely engaging the SPCS. The third-party/partner need not develop its own user interface, security protocols, etc.

Abstract: Systems and methods for providing access rights may include a first computing system that receives a request to link an enterprise account of the first computing system to a second computing system. The first computing system may authenticate a user, receive a selection of one or more access rights, and one or more accounts of the enterprise account, via an application interface of the second computing system, and generate an access token for transmission to a computing device of the user, where the access token identifies the one or more access rights and the one or more accounts. The first computing system may transmit the access token to the computing device, to provide the computing device access to the one or more accounts according to the one or more access rights, of the first computing system, via the second computing system.

Abstract: This disclosure is directed to integrating unaffiliated applications, or the processes and/or subsystems (e.g., application interfaces) of unaffiliated applications, with client applications to enable the client applications to provide new capabilities not otherwise available through the client application. The disclosed approach allows users to access new functionality within the operating environment of the client application, without accessing unaffiliated applications and undergoing separate authentication and data exchange with each unaffiliated application. Functionality of an unaffiliated application can be integrated by, for example, incorporating such processes and subsystems as interactive user interfaces, widgets, applets, plugins, etc., of unaffiliated applications.

Abstract: Disclosed are methods, systems, and devices for facilitating secure and private communications, via a website or application of a third-party computing system (TPCS), between a user device and a service provider computing system (SPCS). The communications may be conducted via a frame in a website served by the TPCS. The TPCS may serve a website that incorporates a customizable SDK component provided by the SPCS. The communications allow the user to, for example, open a new account. The SDK component may be initialized via a script from the SPCS, and authenticated via a session token obtained from the SPCS via the TPCS. The SDK component may provide user information, input into the frame, to the SPCS via API calls to the SPCS. The user does not navigate away from the website while securely engaging the SPCS. The third-party/partner need not develop its own user interface, security protocols, etc.

Abstract: Disclosed are methods, systems, and devices for facilitating secure and private communications, via a website or application of a third-party computing system (TPCS), between a user device and a service provider computing system (SPCS). The communications may be conducted via a frame in a website served by the TPCS. The TPCS may serve a website that incorporates a customizable SDK component provided by the SPCS. The communications allow the user to, for example, open a new account. The SDK component may be initialized via a script from the SPCS, and authenticated via a session token obtained from the SPCS via the TPCS. The SDK component may provide user information, input into the frame, to the SPCS via API calls to the SPCS. The user does not navigate away from the website while securely engaging the SPCS. The third-party/partner need not develop its own user interface, security protocols, etc.

Abstract: Disclosed are methods, systems, and devices for facilitating secure and private communications, via a website or application of a third-party computing system (TPCS), between a user device and a service provider computing system (SPCS). The communications may be conducted via a frame in a website served by the TPCS. The TPCS may serve a website that incorporates a customizable SDK component provided by the SPCS. The communications allow the user to, for example, open a new account. The SDK component may be initialized via a script from the SPCS, and authenticated via a session token obtained from the SPCS via the TPCS. The SDK component may provide user information, input into the frame, to the SPCS via API calls to the SPCS. The user does not navigate away from the website while securely engaging the SPCS. The third-party/partner need not develop its own user interface, security protocols, etc.

Abstract: Systems and methods for providing access rights may include a first computing system that receives a request to link an enterprise account of the first computing system to a second computing system. The first computing system may authenticate a user, receive a selection of one or more access rights, and one or more accounts of the enterprise account, via an application interface of the second computing system, and generate an access token for transmission to a computing device of the user, where the access token identifies the one or more access rights and the one or more accounts. The first computing system may transmit the access token to the computing device, to provide the computing device access to the one or more accounts according to the one or more access rights, of the first computing system, via the second computing system.

Abstract: Systems, methods, and computer-readable storage media for a digital marketplace add-in. One method includes receiving an entity dataset includes marketplace design preferences that define styling and designs of an online marketplace provided by a marketplace computing system, and generating and presenting, on a user device, a first application user interface based on the marketplace design preferences, the first application user interface including a plurality of interactive elements associated with payment information of a user. The method further includes receiving a preference in response to a selection of a first interactive element of the plurality of interactive elements, and receiving, from the marketplace computing system, transaction information regarding a transaction.

Abstract: Systems and methods for facilitating communication between computing systems may include a device which establishes a connection between a first application executing on a first server and a second application executing on a second server. The first application and the second application may be linked to a common account holder. The first application may transmit, to the second application, at least a portion of data associated with the common account holder and accessible via the first application. The first application may generate populated form fields for a form associated with the first application using data from the second application and the data received by the second application from the first application. The first application may generate a new account for the common account holder using the populated form fields received from the second application.

Abstract: Systems and methods for providing early payment recommendations may include one or more processors establish a connection between a first data source and a second data source, and maintain a machine-learning model trained to ingest data from the first and second data source. The processor(s) may detect a data entry for an invoice between an enterprise and a third party via the connection, extract a trade term from the invoice responsive to detecting the data entry, apply the trade term to the machine-learning model as a first input, and apply data of the account of the second data source to the machine-learning model as second input. The processor(s) may receive, from the machine-learning model, an output including a score for early-payment of the data entry according to the trade term and the data of the account, and transmit a notification for the invoice to a computing device of the enterprise.

Abstract: Systems and methods for receiving an enterprise resource dataset associated with the first entity, the enterprise resource dataset including an invoice data for the first entity, the invoice data including a first data entry including first value and a first maturity date and a second data entry including a second value and second maturity date, determining a predicted future account balance, determining based on the predicted future account balance, the first value, the second value, the first maturity date, the second maturity date, one or more financing options including a first finance option associated with the first data entry included in the invoice data, generating, a user interface display configured to be displayed within the enterprise application, the user interface display including the first finance option a selection of the first finance option, and initiating a first transfer to a second entity associated with the first data entry.

Abstract: Systems, methods, and apparatuses for automated population of responses into query fields of a form are discussed. The responses are based on data in a networked user data repository maintained by a first party, and the form is presented by a second party. A login request for access to data in the user data repository may be received from a remote computing device. If access to the data in the user data repository is authorized, descriptors for at least one of the query fields may be received, and based on the descriptors, it may be determined whether any responses to any query fields are contained in the user data repository. Query fields may be populated with responses obtained through the data repository. The user provides the second party with information that is made available to the first party without separately inputting the information into the form of the second party.