Abstract: A nozzle assembly for a cleaning apparatus can include a brushroll, a motor disposed within the brushroll and configured to rotate the brushroll, a debris receptacle comprising a debris inlet. A scraper may be disposed above the debris inlet such that the scraper projects into the brushroll. A ramp can be formed on the scraper. The ramp may extend between an outer edge of the scraper above the debris inlet and into an interior region of the debris receptacle. The ramp can include a runoff surface configured to direct debris and liquid removed from the brushroll by the scraper as the brushroll rotates into the debris receptacle at a negative angle relative to a surface being cleaned. A squeegee assembly may be disposed across a full width of the nozzle assembly.

Abstract: The disclosures herein relate to novel compounds of formula (1) and salts thereof, wherein V; W; X; Y; Z; R1; R2; R3; R4 and R5 are defined herein, and their use in treating, preventing, ameliorating, controlling or reducing the risk of neurological or psychiatric disorders associated with orexin receptors.

Abstract: Techniques for providing access to scope-delimited sensitive data are disclosed. A user provides sensitive data to a first party associated with a payment service provider. The first party stores the sensitive data with the payment service provider, and the payment service provider provides the first party merchant with an encoding of the payment data. The first party provides a purchasing opportunity to the user for goods offered by a third party also associated with the payment service provider. The first party transmits a sensitive data grant request to the payment service provider. In response, the payment service provides a scope-delimited encoding of the sensitive data. The first party provides the scope-delimited encoding of the payment data to the third party. The third party merchant creates a transaction using the scope-delimited encoding of the sensitive data. At some time later, access to the scope-delimited encoding of the sensitive data is revoked.

Abstract: Systems and methods providing, by a third party, input form fields for sensitive data on a web page provided by an organization. A user may request a web page from an organization, such as a merchant's checkout web page, that requires entry of sensitive data. The merchant's checkout web page may include reference to a script file that provides hosted sensitive data form fields. In response to rendering the merchant web page in a web browser of the user, a request to provide sensitive data form fields on the merchant web page may be received. The request may include a call to a function in a scripting file provided by the third party, and the provided file may cause one or more inline frames to be rendered in the web browser, each inline frame including a sensitive data form field. Data entered by the user in the sensitive data form fields may be received by a third party payment processor device.

Abstract: Techniques for providing access to scope-delimited sensitive data are disclosed. A user provides sensitive data to a first party associated with a payment service provider. The first party stores the sensitive data with the payment service provider, and the payment service provider provides the first party merchant with an encoding of the payment data. The first party provides a purchasing opportunity to the user for goods offered by a third party also associated with the payment service provider. The first party transmits a sensitive data grant request to the payment service provider. In response, the payment service provides a scope-delimited encoding of the sensitive data. The first party provides the scope-delimited encoding of the payment data to the third party. The third party merchant creates a transaction using the scope-delimited encoding of the sensitive data. At some time later, access to the scope-delimited encoding of the sensitive data is revoked.

Abstract: Techniques for providing access to scope-delimited sensitive data are disclosed. A user provides sensitive data to a first party associated with a payment service provider. The first party stores the sensitive data with the payment service provider, and the payment service provider provides the first party merchant with an encoding of the payment data. The first party provides a purchasing opportunity to the user for goods offered by a third party also associated with the payment service provider. The first party transmits a sensitive data grant request to the payment service provider. In response, the payment service provides a scope-delimited encoding of the sensitive data. The first party provides the scope-delimited encoding of the payment data to the third party. The third party merchant creates a transaction using the scope-delimited encoding of the sensitive data. At some time later, access to the scope-delimited encoding of the sensitive data is revoked.

Abstract: A system and/or method may be provided to silently authenticate a user. An example method of silently authenticating a user includes receiving a set of device characteristics from a user device and identifying, based on the set of device characteristics, the user device. The method also includes determining whether to trust the user device and determining whether the user device is associated with a user that was previously authenticated. The method further includes in response to determining to trust the user device and that the user device is associated with the user that was previously authenticated, authenticating the user based on the previous authentication.

Abstract: Systems and methods providing, by a third party, input form fields for sensitive data on a web page provided by an organization. A user may request a web page from an organization, such as a merchant's checkout web page, that requires entry of sensitive data. The merchant's checkout web page may include reference to a script file that provides hosted sensitive data form fields. In response to rendering the merchant web page in a web browser of the user, a request to provide sensitive data form fields on the merchant web page may be received. The request may include a call to a function in a scripting file provided by the third party, and the provided file may cause one or more inline frames to be rendered in the web browser, each inline frame including a sensitive data form field. Data entered by the user in the sensitive data form fields may be received by a third party payment processor device.

Abstract: A system and/or method may be provided to silently authenticate a user. An example method of silently authenticating a user includes receiving a set of device characteristics from a user device and identifying, based on the set of device characteristics, the user device. The method also includes determining whether to trust the user device and determining whether the user device is associated with a user that was previously authenticated. The method further includes in response to determining to trust the user device and that the user device is associated with the user that was previously authenticated, authenticating the user based on the previous authentication.

Abstract: A system and/or method may be provided to silently authenticate a user. An example method of silently authenticating a user includes receiving a set of device characteristics from a user device and identifying, based on the set of device characteristics, the user device. The method also includes determining whether to trust the user device and determining whether the user device is associated with a user that was previously authenticated. The method further includes in response to determining to trust the user device and that the user device is associated with the user that was previously authenticated, authenticating the user based on the previous authentication.

Abstract: A system and/or method may be provided to silently authenticate a user. An example method of silently authenticating a user includes receiving a set of device characteristics from a user device and identifying, based on the set of device characteristics, the user device. The method also includes determining whether to trust the user device and determining whether the user device is associated with a user that was previously authenticated. The method further includes in response to determining to trust the user device and that the user device is associated with the user that was previously authenticated, authenticating the user based on the previous authentication.

Abstract: Techniques for providing access to scope-delimited sensitive data are disclosed. A user provides sensitive data to a first party associated with a payment service provider. The first party stores the sensitive data with the payment service provider, and the payment service provider provides the first party merchant with an encoding of the payment data. The first party provides a purchasing opportunity to the user for goods offered by a third party also associated with the payment service provider. The first party transmits a sensitive data grant request to the payment service provider. In response, the payment service provides a scope-delimited encoding of the sensitive data. The first party provides the scope-delimited encoding of the payment data to the third party. The third party merchant creates a transaction using the scope-delimited encoding of the sensitive data. At some time later, access to the scope-delimited encoding of the sensitive data is revoked.

Abstract: A system and/or method may be provided to silently authenticate a user. An example method of silently authenticating a user includes receiving a set of device characteristics from a user device and identifying, based on the set of device characteristics, the user device. The method also includes determining whether to trust the user device and determining whether the user device is associated with a user that was previously authenticated. The method further includes in response to determining to trust the user device and that the user device is associated with the user that was previously authenticated, authenticating the user based on the previous authentication.

Abstract: Systems and methods providing, by a third party, input form fields for sensitive data on a web page provided by an organization. A user may request a web page from an organization, such as a merchant's checkout web page, that requires entry of sensitive data. The merchant's checkout web page may include reference to a script file that provides hosted sensitive data form fields. In response to rendering the merchant web page in a web browser of the user, a request to provide sensitive data form fields on the merchant web page may be received. The request may include a call to a function in a scripting file provided by the third party, and the provided file may cause one or more inline frames to be rendered in the web browser, each inline frame including a sensitive data form field. Data entered by the user in the sensitive data form fields may be received by a third party payment processor device.

Abstract: Systems and methods providing, by a third party, input form fields for sensitive data on a web page provided by an organization. A user may request a web page from an organization, such as a merchant's checkout web page, that requires entry of sensitive data. The merchant's checkout web page may include reference to a script file that provides hosted sensitive data form fields. In response to rendering the merchant web page in a web browser of the user, a request to provide sensitive data form fields on the merchant web page may be received. The request may include a call to a function in a scripting file provided by the third party, and the provided file may cause one or more inline frames to be rendered in the web browser, each inline frame including a sensitive data form field. Data entered by the user in the sensitive data form fields may be received by a third party payment processor device.

Abstract: A system and/or method may be provided to silently authenticate a user. An example method of silently authenticating a user includes receiving a set of device characteristics from a user device and identifying, based on the set of device characteristics, the user device. The method also includes determining whether to trust the user device and determining whether the user device is associated with a user that was previously authenticated. The method further includes in response to determining to trust the user device and that the user device is associated with the user that was previously authenticated, authenticating the user based on the previous authentication.