Abstract: The present disclosure provides a multi-tenant loyalty platform for selective configuration of loyalty programs in a multi-tenant environment. An example platform comprises a processor and a memory storing instructions which, when executed by the processor, configure the multi-tenant loyalty platform to: cause presentation of loyalty program options to a first tenant in a multi-tenant environment; receive, from the first tenant, first order data relating to a selected program configuration; cause presentation of loyalty program options to a second tenant; receive, from the second tenant, second order data different from the first order data; store the first and second order data in a loyalty program data structure that includes loyalty program rules specific to each of the first and second tenants and the respective first and second loyalty programs; and configure the first and second loyalty programs using data stored in the loyalty program data structure.

Abstract: In some embodiments, a multi-tenant loyalty program configuration platform is provided for selective configuration of loyalty programs in a multi-tenant environment.

Abstract: A machine may be configured to facilitate partial reductions of an amount by generating and providing a graphical user interface that enables a user to specify one or more partial reductions of the amount, thus defining or otherwise controlling how the amount is to be reduced in stages by such partial reductions. For example, in situations where a total amount is to be reduced in stages by multiple partial reductions, the generated and provided graphical user interface may be operable to specify each stage of reduction by enabling the user to select a corresponding account for each stage of reduction. The corresponding account may be selected from among a set of multiple available accounts, each with a respectively corresponding available amount, any portion or all of which may be available to use in that stage of reducing the total amount.

Abstract: In some embodiments, a method to generate a user interface for a subscription management system may include receiving first order data relating to a first subscription offering, receiving second order data related to a second subscription offering, combining the first and second order data into a subscription data structure that, calculating a combined one-time payment amount for both the first and second subscription offerings based on the quantity data, calculating a combined periodic monthly subscription payment amount for both the first and the second subscription offerings based on the quantity and period data, and/or causing presentation of both the combined one-time payment amount and the combined monthly subscription payment amount in the user interface for the subscription management system.

Abstract: In an example, a proxy server includes a proxy callback interface supporting a plurality of webhook channels, each channel of the plurality of webhook channels being identified by a respective webhook channel address. The proxy callback interface receives a webhook call, the webhook call including a specific webhook channel address identifying a specific webhook channel, and payload callback data. The proxy server also includes a database interface to store a callback record that includes the payload callback data in a proxy server database. The proxy server also includes a query interface to receive a callback query, the callback query identifying the specific webhook channel address. The query interface further identifies a plurality of callback records, associated with the specific webhook channel address, that were stored within the proxy server database subsequent to receipt of a previously-received callback query, and returns the plurality of callback records, responsive to the callback query.

Abstract: In some examples, a method also includes identify, using the callback query, a callback record. The method also includes providing, responsive to the callback query, the payload callback data of the callback record from a query interface to a callback client. The callback query includes a polling number, and the method further includes using the polling number to identify the callback record, detecting that the polling number corresponds to a last record number for callback records associated with the webhook channel identifier, and performing a call termination action responsive to the detecting of the correspondence between the polling number and the last record number for the callback records associated with the webhook channel identifier.

Abstract: A proxy server has a proxy callback interface to receive a webhook call from a callback producer server of a web service, the webhook call including a webhook channel address and payload callback data. A proxy server database stores a callback record comprising the payload callback data in a proxy server database. A query interface receives a callback query from a callback consumer server, the callback query identifying the webhook channel address. The query interface further configured to identify a plurality of callback records associated with the webhook channel address stored within the proxy server database after receipt of a previous callback query from the callback consumer server, and return the plurality of callback records to the callback client responsive to the callback query.

Abstract: A method to process webhook calls is described. The method comprises receiving, from a callback producer server and at a proxy callback interface of a proxy server, a webhook call comprising a webhook channel address and payload callback data. A callback record is stored in a proxy server database, the callback record comprising a sequence number and the payload callback data. A callback query is received, from a callback client and at a query interface of the proxy server, the callback query identifying the webhook channel address. The callback record is identified, using the callback query, the callback record, and provided, responsive to the callback query, from the query interface to the callback client.