Abstract: A method for coordinating billing requests and payments across different financial institutions includes receiving an electronic enrollment request by a biller exchange computing system from a customer computing device; displaying an interactive control on a user interface of the customer computing device configured to collect customer authentication data for the biller; transmitting the customer authentication data to a remote computing system associated with the biller; causing the remote computing system to generate a customer-biller account authentication token that authorizes the biller exchange computing system to perform financial transactions with the biller on behalf of the customer; and authenticating, by the biller exchange computing system, a transaction request received from the customer computing device for a transaction between the customer and the biller based on the customer-biller account authentication token.

Abstract: Disclosed are example methods, systems, and devices for integrating payment API services provided by a service provider computing system with a client application. The client application running on a user device may allow a user to make payments and/or to submit payments for approval and may communicate payment information to a client computing system. If a payment is submitted for approval via the client application, the client computing system may make API calls to the service provider computing system to, for example, submit, view, and/or cancel payments. Payments may be approved by a second user using a second device. The service provider computing system initiates fund transfers for approved payments. Payments may be submitted within the operating environment of the client application without use of an application or website of the service provider.

Abstract: Disclosed are example methods, systems, and devices for integrating payment API services provided by a service provider computing system with a client application. The client application running on a user device may allow a user to make payments and/or to submit payments for approval and may communicate payment information to a client computing system. If a payment is submitted for approval via the client application, the client computing system may make API calls to the service provider computing system to, for example, submit, view, and/or cancel payments. Payments may be approved by a second user using a second device. The service provider computing system initiates fund transfers for approved payments. Payments may be submitted within the operating environment of the client application without use of an application or website of the service provider.

Abstract: Disclosed are example methods, systems, and devices for integrating payment API services provided by a service provider computing system with a client application. The client application running on a user device may allow a user to make payments and/or to submit payments for approval and may communicate payment information to a client computing system. If a payment is submitted for approval via the client application, the client computing system may make API calls to the service provider computing system to, for example, submit, view, and/or cancel payments. Payments may be approved by a second user using a second device. The service provider computing system initiates fund transfers for approved payments. Payments may be submitted within the operating environment of the client application without use of an application or website of the service provider.

Abstract: A computing device comprises a processing resource, a memory resource, and computer-executable instructions stored thereon and embodied in a biller exchange bill pay application, where the instructions cause the computing device to receive a data set comprising a plurality of billers from a biller exchange computing system, receive an authentication token from the biller exchange computing system, query a computing device property of the computing system, render an optimized version of the biller exchange bill pay application, display a user-interactive page comprising at least one user-interactive control where the at least one user-interactive control comprises at least one property dynamically populated based on the data set comprising the plurality of biller, and perform computing operations specified by the at least one property of the at least one user-interactive control using the authentication token and responsive to detecting a user interaction with the at least one user-interactive control.

Abstract: A computing device includes a processing resource, a memory resource, and computer-executable instructions stored thereon and embodied in a biller exchange bill pay application. The instructions, when executed by the processing resource, cause the computing device to receive, from a remote computing system, a data set comprising a plurality of billers. Each of the plurality of billers is subscribed to a biller exchange structured to allow each of the plurality of billers to deliver and receive payment on customer bills via a biller exchange computing system. A user-interactive page comprising at least one user-interactive control is generated and displayed on the computing device. The user-interactive control includes at least one property dynamically populated based on the data set comprising the plurality of billers (such as, for example, a property binding the user-interactive control to the data set).

Abstract: Disclosed are example methods, systems, and devices for integrating payment API services provided by a service provider computing system with a client application. The client application running on a user device may allow a user to make payments and/or to submit payments for approval and may communicate payment information to a client computing system. If a payment is submitted for approval via the client application, the client computing system may make API calls to the service provider computing system to, for example, submit, view, and/or cancel payments. Payments may be approved by a second user using a second device. The service provider computing system initiates fund transfers for approved payments. Payments may be submitted within the operating environment of the client application without use of an application or website of the service provider.

Abstract: A provider computing system includes a bill pay application circuit configured to receive a request from a user to pay an amount of funds to a biller, determine a customer funds account number for the user, determine a biller funds account number for the biller, and generate a payment request. The provider computing system includes a transaction management system configured to receive the payment request from the bill pay circuit and provide a first post and a second post to a funds account circuit and generate a payment notification. The provider computing system includes a biller posting services circuit configured to receive the payment notification and determine a corresponding customer bill account number. The biller posting services circuit is configured to generate a data object that includes the payment notification and the customer bill account number and cause the data object to be provided to a biller computing system.

Abstract: Provided is software versioning that allows a set of features to be selectively enabled and/or disabled based on a value of a switch associated with each feature of the set of features. The software versioning includes an administrator component that receives a change to a switch associated with at least one application. A toggle component generates a configuration notice based on an indication of the change to the switch. A tool kit component facilitates implementation of the change at the application based on the configuration notice received from the toggle component.

Abstract: Disclosed are example methods, systems, and devices for integrating payment API services provided by a service provider computing system with a client application. The client application running on a user device may allow a user to make payments and/or to submit payments for approval and may communicate payment information to a client computing system. If a payment is submitted for approval via the client application, the client computing system may make API calls to the service provider computing system to, for example, submit, view, and/or cancel payments. Payments may be approved by a second user using a second device. The service provider computing system initiates fund transfers for approved payments. Payments may be submitted within the operating environment of the client application without use of an application or website of the service provider.

Abstract: Provided is software versioning that allows a set of features to be selectively enabled and/or disabled based on a value of a switch associated with each feature of the set of features. The software versioning includes an administrator component that receives a change to a switch associated with at least one application. A toggle component generates a configuration notice based on an indication of the change to the switch. A tool kit component facilitates implementation of the change at the application based on the configuration notice received from the toggle component.

Abstract: Techniques are described for monitoring a plurality of financial transactions of a customer performed across a plurality of financial accounts. The techniques may include determining a subset of the plurality of financial transactions based on a first metric applied to the plurality of financial transactions. The techniques may further include identifying a suggested financial transaction based on a second metric applied to the subset of the plurality of financial transactions. The techniques may further include presenting the suggested financial transaction to the customer via a user interface associated with at least one of the plurality of financial accounts.

Abstract: Provided is software versioning that allows a set of features to be selectively enabled and/or disabled based on a value of a switch associated with each feature of the set of features. The software versioning includes an administrator component that receives a change to a switch associated with at least one application. A toggle component generates a configuration notice based on an indication of the change to the switch. A tool kit component facilitates implementation of the change at the application based on the configuration notice received from the toggle component.

Abstract: Techniques are described for monitoring a plurality of financial transactions of a customer performed across a plurality of financial accounts. The techniques may include determining a subset of the plurality of financial transactions based on a first metric applied to the plurality of financial transactions. The techniques may further include identifying a suggested financial transaction based on a second metric applied to the subset of the plurality of financial transactions. The techniques may further include presenting the suggested financial transaction to the customer via a user interface associated with at least one of the plurality of financial accounts.

Abstract: Provided is software versioning that allows a set of features to be selectively enabled and/or disabled based on a value of a switch associated with each feature of the set of features. The software versioning includes an administrator component that receives a change to a switch associated with at least one application. A toggle component generates a configuration notice based on an indication of the change to the switch. A tool kit component facilitates implementation of the change at the application based on the configuration notice received from the toggle component.