Abstract: Techniques for a secure and flexible distributed job processing between a transaction network of a service provider and a processing endpoint of an entity are described. In an example, a transaction instrument may be used for a transaction and may be registered with the processing endpoint based on a transaction account. The transaction network may store an ownership object associating a token corresponding to the transaction instrument, a user identifier unique to a user account, and a provider identifier unique to the transaction account. The transaction network may identify a membership status of the user account and may customize the transaction based on this status. The transaction, as customized, may be completed by sending the provider identifier and data about the customization to the processing endpoint.

Abstract: Techniques for a secure and flexible distributed job processing between a transaction network of a service provider and a processing endpoint of an entity are described. In an example, a transaction instrument may be used for a transaction and may be registered with the processing endpoint based on a transaction account. The transaction network may store an ownership object associating a token corresponding to the transaction instrument, a user identifier unique to a user account, and a provider identifier unique to the transaction account. The transaction network may identify a membership status of the user account and may customize the transaction based on this status. The transaction, as customized, may be completed by sending the provider identifier and data about the customization to the processing endpoint.

Abstract: Techniques for a secure and flexible distributed job processing between a transaction network of a service provider and a processing endpoint of an entity are described. In an example, a transaction instrument may be used for a transaction and may be registered with the processing endpoint based on a transaction account. The transaction network may store an ownership object associating a token corresponding to the transaction instrument, a user identifier unique to a user account, and a provider identifier unique to the transaction account. The transaction network may identify a membership status of the user account and may customize the transaction based on this status. The transaction, as customized, may be completed by sending the provider identifier and data about the customization to the processing endpoint.

Abstract: A collection of key-value pairs may be maintained by a key-value database management system. Updates to the collection may be provided by a partially trusted entity. The updates to the collection may be stored in a series of transactions that are committed synchronously but associated with a second version of the collection of key-value pairs that is not immediately visible to a data consumer. The second version of the collection may initially be associated with an unaccepted state. The second version may be accepted and made available to the data consumer, or rejected and rolled back to the previous version.

Abstract: A collection of key-value pairs may be maintained by a key-value database management system. Updates to the collection may be provided by a partially trusted entity. The updates to the collection may be stored in a series of transactions that are committed synchronously but associated with a second version of the collection of key-value pairs that is not immediately visible to a data consumer. The second version of the collection may initially be associated with an unaccepted state. The second version may be accepted and made available to the data consumer, or rejected and rolled back to the previous version.

Abstract: A collection of key-value pairs may be maintained by a key-value database management system. Updates to the collection may be provided by a partially trusted entity. The updates to the collection may be stored in a series of transactions that are committed synchronously but associated with a second version of the collection of key-value pairs that is not immediately visible to a data consumer. The second version of the collection may initially be associated with an unaccepted state. The second version may be accepted and made available to the data consumer, or rejected and rolled back to the previous version.

Abstract: A misplaced item service identifies a plurality of inventory storage locations in a materials handling facility associated with a misplaced item. The misplaced item service determines an ordered list of the plurality of inventory storage locations, wherein the inventory storage locations are arranged in the ordered list based at least in part on a location density of the inventory storage locations, a population density of the inventory storage locations and a last inventory storage location inspected.