Abstract: Rules can be selectively applied by a user to an access card using a graphical user interface (GUI) of a mobile application. For example, the mobile application can provide a graphical user interface through which the user can select how usage of the access card is to be handled by the service provider. The mobile application can receive, through the graphical user interface, input from the user indicating one or more rules to be applied to the access card. The one or more rules can dictate how usage of the access card is to be handled by the service provider. In response to receiving the input, the mobile application can transmit one or more commands to a computer system associated with the service provider. The computer system can receive the one or more commands and implement the one or more rules selected by the user of the access card.

Abstract: Card controls can be selectively applied by a user to a card using a graphical user interface (GUI). The card controls can dictate whether network requests associated with usage of the card are to be handled using an account subsystem or a service subsystem. For example, the user can input a first selection to the GUI for applying a first card control in relation to a first type of network request. Based on the first selection, the system can be configured to complete network requests of the first type using the service subsystem. The user can also input a second selection to the GUI for applying a second card control in relation to a second type of network request. Based on the second selection, the system can be configured to complete network requests of the second type using the account subsystem.

Abstract: Network requests can be automatically routed between two or more computer subsystems in some examples. In one such example, a system can determine that a user is eligible for a service based on usage data relating to an account of the user. Based on determining that the account is eligible for the service, the system can activate the service for the user by communicating with a service subsystem. Subsequent to activating the service for the user, the system can receive a network request associated with the user and determine that the network request has a characteristic. Based on determining that the network request has the characteristic, the system can forward the request to the service subsystem. The service subsystem can complete the network request using the service.

Abstract: Card controls can be selectively applied by a user to a card using a graphical user interface (GUI). The card controls can dictate whether network requests associated with usage of the card are to be handled using an account subsystem or a service subsystem. For example, the user can input a first selection to the GUI for applying a first card control in relation to a first type of network request. Based on the first selection, the system can be configured to complete network requests of the first type using the service subsystem. The user can also input a second selection to the GUI for applying a second card control in relation to a second type of network request. Based on the second selection, the system can be configured to complete network requests of the second type using the account subsystem.

Abstract: Card controls can be selectively applied by a user to a card using a graphical user interface (GUI). The card controls can dictate whether network requests associated with usage of the card are to be handled using an account subsystem or a service subsystem. For example, the user can input a first selection to the GUI for applying a first card control in relation to a first type of network request. Based on the first selection, the system can be configured to complete network requests of the first type using the service subsystem. The user can also input a second selection to the GUI for applying a second card control in relation to a second type of network request. Based on the second selection, the system can be configured to complete network requests of the second type using the account subsystem.

Abstract: Rules can be selectively applied by a user to an access card using a graphical user interface (GUI) of a mobile application. For example, the mobile application can provide a graphical user interface through which the user can select how usage of the access card is to be handled by the service provider. The mobile application can receive, through the graphical user interface, input from the user indicating one or more rules to be applied to the access card. The one or more rules can dictate how usage of the access card is to be handled by the service provider. In response to receiving the input, the mobile application can transmit one or more commands to a computer system associated with the service provider. The computer system can receive the one or more commands and implement the one or more rules selected by the user of the access card.

Abstract: Rules can be selectively applied by a user to an access card using a graphical user interface (GUI) of a mobile application. For example, the mobile application can provide a graphical user interface through which the user can select how usage of the access card is to be handled by the service provider. The mobile application can receive, through the graphical user interface, input from the user indicating one or more rules to be applied to the access card. The one or more rules can dictate how usage of the access card is to be handled by the service provider. In response to receiving the input, the mobile application can transmit one or more commands to a computer system associated with the service provider. The computer system can receive the one or more commands and implement the one or more rules selected by the user of the access card.

Abstract: Card controls can be selectively applied by a user to a card using a graphical user interface (GUI). The card controls can dictate whether network requests associated with usage of the card are to be handled using an account subsystem or a service subsystem. For example, the user can input a first selection to the GUI for applying a first card control in relation to a first type of network request. Based on the first selection, the system can be configured to complete network requests of the first type using the service subsystem. The user can also input a second selection to the GUI for applying a second card control in relation to a second type of network request. Based on the second selection, the system can be configured to complete network requests of the second type using the account subsystem.

Abstract: Network requests can be automatically routed between two or more computer subsystems in some examples. In one such example, a system can determine that a user is eligible for a service based on usage data relating to an account of the user. Based on determining that the account is eligible for the service, the system can activate the service for the user by communicating with a service subsystem. Subsequent to activating the service for the user, the system can receive a network request associated with the user and determine that the network request has a characteristic. Based on determining that the network request has the characteristic, the system can forward the request to the service subsystem. The service subsystem can complete the network request using the service.

Abstract: Card controls can be selectively applied by a user to a card using a graphical user interface (GUI). The card controls can dictate whether network requests associated with usage of the card are to be handled using an account subsystem or a service subsystem. For example, the user can input a first selection to the GUI for applying a first card control in relation to a first type of network request. Based on the first selection, the system can be configured to complete network requests of the first type using the service subsystem. The user can also input a second selection to the GUI for applying a second card control in relation to a second type of network request. Based on the second selection, the system can be configured to complete network requests of the second type using the account subsystem.

Abstract: Rules can be selectively applied by a user to an access card using a graphical user interface (GUI) of a mobile application. For example, the mobile application can provide a graphical user interface through which the user can select how usage of the access card is to be handled by the service provider. The mobile application can receive, through the graphical user interface, input from the user indicating one or more rules to be applied to the access card. The one or more rules can dictate how usage of the access card is to be handled by the service provider. In response to receiving the input, the mobile application can transmit one or more commands to a computer system associated with the service provider. The computer system can receive the one or more commands and implement the one or more rules selected by the user of the access card.

Abstract: Card controls can be selectively applied by a user to a card using a graphical user interface (GUI). The card controls can dictate whether network requests associated with usage of the card are to be handled using an account subsystem or a service subsystem. For example, the user can input a first selection to the GUI for applying a first card control in relation to a first type of network request. Based on the first selection, the system can be configured to complete network requests of the first type using the service subsystem. The user can also input a second selection to the GUI for applying a second card control in relation to a second type of network request. Based on the second selection, the system can be configured to complete network requests of the second type using the account subsystem.

Abstract: Network requests can be automatically routed between two or more computer subsystems in some examples. In one such example, a system can determine that a user is eligible for a service based on usage data relating to an account of the user. Based on determining that the account is eligible for the service, the system can activate the service for the user by communicating with a service subsystem. Subsequent to activating the service for the user, the system can receive a network request associated with the user and determine that the network request has a characteristic. Based on determining that the network request has the characteristic, the system can forward the request to the service subsystem. The service subsystem can complete the network request using the service.

Abstract: Network requests can be automatically routed between two or more computer subsystems in some examples. In one such example, a system can determine that a user is eligible for a service based on usage data relating to an account of the user. Based on determining that the account is eligible for the service, the system can activate the service for the user by communicating with a service subsystem. Subsequent to activating the service for the user, the system can receive a network request associated with the user and determine that the network request has a characteristic. Based on determining that the network request has the characteristic, the system can forward the request to the service subsystem. The service subsystem can complete the network request using the service.

Abstract: Card controls can be selectively applied by a user to a card using a graphical user interface (GUI). The card controls can dictate whether network requests associated with usage of the card are to be handled using an account subsystem or a service subsystem. For example, the user can input a first selection to the GUI for applying a first card control in relation to a first type of network request. Based on the first selection, the system can be configured to complete network requests of the first type using the service subsystem. The user can also input a second selection to the GUI for applying a second card control in relation to a second type of network request. Based on the second selection, the system can be configured to complete network requests of the second type using the account subsystem.

Abstract: A container for storing and dispensing fluids includes a container body having an upwardly extending annular neck portion defining a container opening and terminating into an annular rim having a generally flat, upwardly facing sealing surface and an inwardly extending flange. A separate spout member includes an annular wall having an inwardly extending portion defining a pour spout and an outwardly extending lip at one end thereof, wherein the lip includes a downwardly facing sealing surface. The annular wall also includes an outwardly extending shoulder below the lip for engaging the rim flange, wherein the annular wall is configured to be received within the container opening and wherein the annular wall shoulder is capable of being snap-fit over the rim flange to create a seal between said rim sealing surface and said lip sealing surface. The container also includes a removable lid that threadedly engages the container neck.

Abstract: A container for the storage and dispensing of a liquid and which incorporates a sealing mechanism includes a blow-molded container body including a neck portion having a series of external threads and defining an annular, non-planar sealing surface, a pouring spout assembled into the body and a unitary closing lid including a series of internal threads constructed and arranged to engage the threads of the neck portion. The unitary closing lid includes the sealing mechanism in the form of a pair of annular sealing lips constructed and arranged to be compressed against the annular, non-planar sealing surface to establish a sealed interface between the closing lid and the body.

Abstract: A unitary capseal for a closure that is installed in a container includes an annular sidewall, a generally circular top panel joined to the sidewall, a snap-on annular rim formed adjacent a lower edge of the sidewall, and an annular sealing lip formed adjacent the annular rim. The cooperating closure includes a serrated flange, a closing plug for threaded receipt by the flange, and a sealing gasket positioned therewith. The container end is formed around the flange interlocking with the flange serrations and creating an outer annular channel that receives the annular rim for a snap-on assembly of the capseal to the container end that in turn positions the capseal over and around the closure. The sealing lip extends radially outwardly from the sidewall and includes a concave surface facing the container end for sealing off the interior portions of the closure from collecting debris.

Abstract: A sealing mechanism for a container for sealing an interface between two or more of the structural members includes a container body and a pouring spout. The pouring spout includes a ridge for securing the spout to the container body and a retention ridge that is positioned near the rim of the container body, once assembled. An angled retention surface on the spout is used to properly position a seal between the pouring spout and the container.

Abstract: An airless dispenser pump assembly includes a pump mechanism with an inlet valve that is configured to efficiently pump viscous fluids and that is able to be pre-primed when the pump mechanism is attached to a container. In one form, the inlet valve includes a seal member that seals an inlet port of the pump and an outer support member that secures the inlet valve to the rest of the pump mechanism. Two or more legs generally extend in a circumferential direction between the support member and the seal member in order to create a large flow opening for fluid flow through the inlet valve when opened and to rapidly close the inlet valve. The pump mechanism further includes an outlet valve that is configured to draw fluid back from a nozzle of the pump after dispensing in order to minimize build up around the nozzle.