METHODS AND SYSTEMS TO VERIFY ENTITY STATE-QUANTITY VALUES FOR ASYNCHRONOUS OPERATIONS
Disclosed herein are methods and system for improved entity state-quantity value verification for asynchronous operations. In one example, a request for an asynchronous operation corresponding to an entity object may be identified. The entity object may include a set of state-quantity values and each state-quantity value may include a quantity associated with a possible stage in a lifecycle of the corresponding entity. A proposed state-quantity value may be determined based on the request for the asynchronous operation corresponding to the entity object. Additionally, an available state-quantity value may be generated based on at least a portion of the set of state-quantity values of the entity object. The asynchronous operation may be performed when a condition based on the proposed state-quantity value and the available state-quantity value is satisfied.
1 . A method comprising:
identifying a request for an asynchronous operation corresponding to an entity object, the entity object including a set of state-quantity values, and each state-quantity value including a quantity associated with a possible stage in a lifecycle of a corresponding entity;
determining a proposed state-quantity value based on the request for the asynchronous operation corresponding to the entity object;
generating an available state-quantity value based on at least a portion of the set of state-quantity values of the entity object; and
performing the asynchronous operation when a condition based on the proposed state-quantity value and the available state-quantity value is satisfied.
2 . The method of claim 1 , wherein the condition is satisfied when the proposed state-quantity value is less than or equal to the available state-quantity value.
3 . The method of claim 2 , wherein the proposed state-quantity value includes a reversal quantity and the available state-quantity value includes an authorized quantity minus a cleared quantity.
4 . The method of claim 1 , further comprising blocking performance of the asynchronous operation when the condition is not satisfied when the proposed state-quantity value is larger than the available state-quantity value.
5 . The method of claim 1 , further comprising:
identifying a proposed timing condition associated with the asynchronous operation;
updating the entity object to include a timing condition corresponding to the proposed timing condition, and a pending state-quantity value corresponding to the proposed state-quantity value and associated with a particular stage in the lifecycle of the corresponding entity; and
performing the asynchronous operation when the proposed timing condition based on the proposed state-quantity value and the available state-quantity value is satisfied.
6 . The method of claim 5 , further comprising:
determining performance of the asynchronous operation was successful; and
updating the entity object to include a non-pending state-quantity value corresponding to the proposed state-quantity value and associated with the particular stage in the lifecycle of the corresponding entity in response to determining performance of the asynchronous operation was successful.
7 . The method of claim 5 , wherein the request for the asynchronous operation includes a first request for a first asynchronous operation, and the method further comprising:
performing the first asynchronous operation when the proposed timing condition is satisfied;
receiving a second request for a second asynchronous operation corresponding to the entity object prior to a determination the first asynchronous operation was successful; and
responding to the second request by requesting the second request be resubmitted.
8 . The method of claim 5 , wherein the request for the asynchronous operation includes a first request for a first asynchronous operation, and the method further comprising:
receiving a second request for a second asynchronous operation corresponding to the entity object prior to the proposed timing condition being satisfied; and
canceling the timer configured to trigger performance of the first asynchronous operation based on the second asynchronous operation.
9 . A non-transitory computer readable storage medium including instructions that, when executed by a processor, cause the processor to perform operations, the operations comprising:
identifying, by a server system, a request for an asynchronous operation corresponding to an entity object, the entity object including a set of state-quantity values, and each state-quantity value including a quantity associated with a possible stage in a lifecycle of a corresponding entity;
determining, by the server system, a proposed state-quantity value based on the request for the asynchronous operation corresponding to the entity object;
generating, by the server system, an available state-quantity value based on at least a portion of the set of state-quantity values of the entity object; and
performing, by the server system, the asynchronous operation when a condition based on the proposed state-quantity value and the available state-quantity value is satisfied.
10 . The non-transitory computer readable storage medium of claim 9 , the operations further comprising blocking performance of the asynchronous operation when the condition is not satisfied when the proposed state-quantity value is larger than the available state-quantity value.
11 . The non-transitory computer readable storage medium of claim 10 , the operations further comprising:
identifying a proposed timing condition associated with the asynchronous operation;
updating the entity object to include a timing condition corresponding to the proposed timing condition, and a pending state-quantity value corresponding to the proposed state-quantity value and associated with a particular stage in the lifecycle of the corresponding entity; and
performing the asynchronous operation when the proposed timing condition based on the proposed state-quantity value and the available state-quantity value is satisfied.
12 . The non-transitory computer readable storage medium of claim 11 , the operations further comprising:
determining performance of the asynchronous operation was successful; and
updating the entity object to include a non-pending state-quantity value corresponding to the proposed state-quantity value and associated with the particular stage in the lifecycle of the corresponding entity in response to determining performance of the asynchronous operation was successful.
13 . The non-transitory computer readable storage medium of claim 11 , wherein the request for the asynchronous operation includes a first request for a first asynchronous operation, and the operations further comprising:
performing the first asynchronous operation when the proposed timing condition is satisfied;
receiving a second request for a second asynchronous operation corresponding to the entity object prior to a determination the first asynchronous operation was successful; and
responding to the second request by requesting the second request be resubmitted.
14 . The non-transitory computer readable storage medium of claim 11 , wherein the request for the asynchronous operation includes a first request for a first asynchronous operation, and the operations further comprising:
receiving a second request for a second asynchronous operation corresponding to the entity object prior to the proposed timing condition being satisfied; and
canceling a timer configured to trigger performance of the first asynchronous operation based on the second asynchronous operation.
15 . A server computer system, comprising:
a memory; and
a processor coupled to the memory configured to:
identify a request for an asynchronous operation corresponding to an entity object, the entity object including a set of state-quantity values, and each state-quantity value including a quantity associated with a possible stage in a lifecycle of a corresponding entity;
determine a proposed state-quantity value based on the request for the asynchronous operation corresponding to the entity object;
generate an available state-quantity value based on at least a portion of the set of state-quantity values of the entity object; and
performing the asynchronous operation when a condition based on the proposed state-quantity value and the available state-quantity value is satisfied.
16 . The server computer system of claim 15 , wherein the processor coupled to the memory is further configured to:
identify a proposed timing condition associated with the asynchronous operation;
update the entity object to include a timing condition corresponding to the proposed timing condition, and a pending state-quantity value corresponding to the proposed state-quantity value and associated with a particular stage in the lifecycle of the corresponding entity; and
perform the asynchronous operation when the proposed timing condition based on the proposed state-quantity value and the available state-quantity value is satisfied.
17 . The server computer system of claim 16 , wherein the processor coupled to the memory is further configured to:
determine performance of the asynchronous operation was successful; and
update the entity object to include a non-pending state-quantity value corresponding to the proposed state-quantity value and associated with the particular stage in the lifecycle of the corresponding entity in response to determining performance of the asynchronous operation was successful.
18 . The server computer system of claim 16 , wherein the request for the asynchronous operation includes a first request for a first asynchronous operation, and the processor coupled to the memory is further configured to:
perform the first asynchronous operation when the proposed timing condition is satisfied;
receive a second request for a second asynchronous operation corresponding to the entity object prior to a determination the first asynchronous operation was successful; and
respond to the second request by requesting the second request be resubmitted.
19 . The server computer system of claim 16 , wherein the request for the asynchronous operation includes a first request for a first asynchronous operation, and the processor coupled to the memory is further configured to:
receive a second request for a second asynchronous operation corresponding to the entity object prior to the proposed timing condition being satisfied; and
cancel a timer configured to trigger performance of the first asynchronous operation based on the second asynchronous operation.
20 . The server computer system of claim 15 , the processor coupled to the memory is further configured to block performance of the asynchronous operation when the condition is not satisfied when the proposed state-quantity value is larger than the available state-quantity value.