Virtual payment processing system

A system for resolving data transactions, in which data transactions are completed by a hardware matching processor that identifies asynchronously transmitted data transaction requests received from client devices over a data communication network in an arbitrary sequence, matches incoming transaction requests with previously received transaction requests, and, based thereon, transmits electronic data transaction results messages to the client devices, the system comprising:

• at least one processor;
• and
• at least one memory including computer program code for one or more programs the at least one memory and the computer program code configured to, with the at least one processor, cause the system to:
• receive, by the hardware matching processor, an incoming data transaction request from a first client device of a first entity via the data communications network, the incoming data transaction request containing data indicative of an incoming data transaction counter to another transaction from another client device of another entity and received by the hardware matching processor prior or subsequent to receipt of the incoming data transaction, wherein the incoming data transaction request does not contain identifying information associated with the other entity and the other transaction does not contain identifying information associated with the first entity;
• attempt to match the incoming data transaction request with a previously received but not yet resolved data transaction request, which is stored in a transaction message database coupled with the hardware matching processor, to at least partially resolve the incoming data transaction request and/or any matching previously received but not yet resolved data transaction requests;
• identify whether the resolution of the incoming data transaction request and/or any matching previously received but not yet resolved data transaction request is further dependent on resolution of another data transaction request and further determining whether that other data transaction request has been resolved;
• wherein if the incoming data transaction request matches with a previously received but not yet resolved data transaction request and any identified other data transaction requests have been determined to be resolved, resolve the incoming data transaction request with the previously received but not yet resolved data transaction request to at least partially resolve one or both of the incoming data transaction request and the previously received but not yet resolved data transaction request, store any unresolved remainder of the incoming data transaction request or of the matching previously received but not yet resolved data transaction requests in the transaction message database, and determine whether there are any other previously received but not yet resolved data transaction requests stored in the transaction message database which are dependent on the resolution of the incoming data transaction request and/or the matching previously received but not yet resolved data transaction request;
• and
• wherein if no matching previously received but not yet resolved data transaction request is stored in the transaction message database or the identified other data transaction request has not been resolved, store the incoming data transaction request in the transaction message database;
• and
• generate one or more data transaction result messages comprising data indicative of whether the incoming data transaction request matches with a previously received but not yet resolved data transaction request and any identified other data transaction requests have been determined to be resolved and transmitting the generated one or more data transaction result messages to at least to the first client device via the data communications network.

A non-transitory computer readable medium including instructions for resolving data transactions asynchronously transmitted and received in an arbitrary sequence, that when executed, are operable to:

• receive, by the hardware matching processor, an incoming data transaction request from a first client device of a first entity via the data communications network, the incoming data transaction request containing data indicative of an incoming data transaction counter to another transaction from another client device of another entity and received by the hardware matching processor prior or subsequent to receipt of the incoming data transaction, wherein the incoming data transaction request does not contain identifying information associated with the other entity and the other transaction does not contain identifying information associated with the first entity;
• attempt to match the incoming data transaction request with a previously received but not yet resolved data transaction request, which is stored in a transaction message database coupled with the hardware matching processor, to at least partially resolve the incoming data transaction request and/or any matching previously received but not yet resolved data transaction requests;
• identify whether the resolution of the incoming data transaction request and/or any matching previously received but not yet resolved data transaction request is further dependent on resolution of another data transaction request and further determining whether that other data transaction request has been resolved;
• wherein if the incoming data transaction request matches with a previously received but not yet resolved data transaction request and any identified other data transaction requests have been determined to be resolved, resolve the incoming data transaction request with the previously received but not yet resolved data transaction request to at least partially resolve one or both of the incoming data transaction request and the previously received but not yet resolved data transaction request, store any unresolved remainder of the incoming data transaction request or of the matching previously received but not yet resolved data transaction requests in the transaction message database, and determine whether there are any other previously received but not yet resolved data transaction requests stored in the transaction message database which are dependent on the resolution of the incoming data transaction request and/or the matching previously received but not yet resolved data transaction request;
• wherein if no matching previously received but not yet resolved data transaction request is stored in the transaction message database or the identified other data transaction request has not been resolved, store the incoming data transaction request in the transaction message database;
• and
• wherein if one or both of the incoming data transaction request and/or the matched previously received but not yet resolved data transaction request are at least partially resolved, remove the resolved portions of the incoming data transaction request and/or the previously received but not yet resolved data transaction request from the transaction message database, and store a data record of the resolved portions of the incoming data transaction request and/or the previously received but not yet resolved data transaction request in a completed transaction database;
• and
• generate one or more data transaction result messages comprising data indicative of whether the incoming data transaction request matches with a previously received but not yet resolved data transaction request and any identified other data transaction requests have been determined to be resolved and transmitting the generated one or more data transaction result messages to at least to the first client device via the data communications network.