Abstract: Systems, methods and apparatuses for implementing user customizable policies for revenue recognition are described. In some embodiments, user inputs are received from a merchant that specify components of a set of revenue recognition rules to apply to transactions of the merchant on a per transaction basis, wherein each revenue recognition rule specifies a set of conditions to be met to trigger its application, a rule identifier, status, and whether the revenue recognition rule is applied at least one of: a specified product; a specified invoice; a specified customer; a specified payment; a specified refund; and a specified dispute. The user inputs are converted into rules to enable the rules to be matched to the transactions. A transaction is tracked by a server computer system. One or more applicable revenue recognition rules are identified to apply to the transaction, and revenue recognition is performed against the transaction.

Abstract: A method and apparatus for performing cross-platform contract validation are described. In one embodiment, the method for validating compatibility between first and second endpoints, the method comprising: accessing a memory storing a machine-readable contract specifying a request-response pair in a file, the request-response pair consisting of an expected request that the second endpoint expects to receive from the first endpoint and an expected response that should be provided by the second endpoint according to the expected request from the first endpoint; and performing multi-platform contract validation by performing independent tests for the first and second endpoints, using the expected request and expected response specified in the machine-readable contract.

Abstract: Systems, methods and apparatuses for implementing user customizable policies for revenue recognition are described. In some embodiments, a method comprises: tracking, by a network commerce system, a plurality of transactions; determining one or more revenue recognition rules of a plurality of revenue recognition rules that applies to each transaction of the plurality of transactions based on results of matching performed between conditions of each of the plurality of revenue recognition rules and one or more characteristics of said each transaction, the conditions of each rule including an effective time period during which individual transactions are subject to the rule; and automatically performing revenue recognition for each transaction according to one of the one or more revenue recognition rules determined to apply to said each transaction using based on results of matching conditions of one revenue recognition rule and the one or more characteristics of said each transaction.

Abstract: A clock data structure is introduced. An instance of the clock data structure can be attached to a billing data structure, such as a billing data structure that corresponds to a recurring payment. The instance of the clock data structure has a value that represents a frozen time—i.e., a specific time that does not change unless instructed to. The billing data structures to which the clock data structure is attached operate as if the real time is the frozen time on the clock. Since the time is frozen, users wishing to test the billing data structure can update their system configurations at specific times, and subsequently advance the time in the clock data structure instance to see the effects on those configurations, as well as on other parts of the system, including asynchronous messaging and processing, and processes that involve other entities.

Abstract: Systems, methods and apparatuses for implementing user customizable policies for revenue recognition are described. In some embodiments, a method comprises: tracking, by a network commerce system, a plurality of transactions; determining one or more revenue recognition rules of a plurality of revenue recognition rules that applies to each transaction of the plurality of transactions based on results of matching performed between conditions of each of the plurality of revenue recognition rules and one or more characteristics of said each transaction, the conditions of each rule including an effective time period during which individual transactions are subject to the rule; and automatically performing revenue recognition for each transaction according to one of the one or more revenue recognition rules determined to apply to said each transaction using based on results of matching conditions of one revenue recognition rule and the one or more characteristics of said each transaction.

Abstract: A dock data structure is introduced. An instance of the clock data structure can be attached to a billing data structure, such as a billing data structure that corresponds to a recurring payment. The instance of the clock data structure has a value that represents a frozen time—i.e., a specific time that does not change unless instructed to. The billing data structures to which the clock data structure is attached operate as if the real time is the frozen time on the clock. Since the time is frozen, users wishing to test the billing data structure can update their system configurations at specific times, and subsequently advance the time in the clock data structure instance to see the effects on those configurations, as well as on other parts of the system, including asynchronous messaging and processing, and processes that involve other entities.

Abstract: A method and apparatus for performing cross-platform contract validation are described. In one embodiment, the method for validating compatibility between first and second endpoints, the method comprising: accessing a memory storing a machine-readable contract specifying a request-response pair in a file, the request-response pair consisting of an expected request that the second endpoint expects to receive from the first endpoint and an expected response that should be provided by the second endpoint according to the expected request from the first endpoint; and performing multi-platform contract validation by performing independent tests for the first and second endpoints, using the expected request and expected response specified in the machine-readable contract.