Filtered POS processing of services
A system and method are presented that utilizes a primary server having shadow data and benefit bucket data to provide adjudication and payment processing of insurance payment requests without requiring interaction with an insurance server and normal adjudication processes. The primary server can handle adjudication and payment processing for a plurality of insurance providers. An alternate payment method can be identified with a member identifier, allowing both insurance payment adjudication and member payment through the alternate payment method. The primary server can provide benefit processing for retail discounts, and store value benefits for authenticated purchase transactions. A variety of discounts, stored value benefits, insurance benefits, and alternate payment mechanisms can be incorporated into a single transaction and handled in real-time during the transaction.
1. A primary server for facilitating real-time exchanges between a plurality of third-party servers and a point of sale device, the primary server comprising memory and one or more processors communicatively coupled to the memory, the one or more processors configured to:
establish communication with the plurality of third-party servers, wherein each of the plurality of third-party servers stores third-party data that has at least a first structure and is associated with a member plan for a user;
generate, for the user, primary data having a second structure by duplicating a portion of the third-party data having the first structure into the memory that is locally accessible by the primary server without further communication with the plurality of third-party servers, wherein the primary data comprises:
(i) shadow data indicative of a locally duplicated portion of the third-party data stored by the plurality of third-party servers; and
(ii) a plurality of live bucket data items corresponding to the plurality of third-party servers, wherein a live bucket data item of the plurality of live bucket data items:
(1) comprises definition data populated from a particular third-party server of the plurality of third-party servers that manages the live bucket data item, and
(2) defines a live available benefit for a service corresponding to the live bucket data item and that is based on a plurality of user-provider interactions associated with (a) one or more provider computing devices and (b) the service for the user;
receive, originating from the point of sale device, a payment request identifying the service, a provider identifier, and a member identifier that is linked to one or more identifiers respectively corresponding to one or more live bucket data items of the plurality of live bucket data items;
determine, based at least in part on the shadow data and live bucket data item, that:
(i) the service is subject to a frequency limit and that the frequency limit is not exceeded,
(ii) a provider corresponding to the provider identifier is not excluded from payment, and
(iii) a live available benefit for the live bucket data item is less than a reimbursement amount for the service; and
in response to the determining:
(i) initiate, in real time, the performance of an ACH payment (1) to a provider account associated with the provider identifier, (2) from a third-party account associated with a third-party server corresponding to the live bucket data item, and (3) in a payment amount of the live available benefit for the live bucket data item;
(ii) reduce the live available benefit for the live bucket data item by the payment amount;
(iii) identify an alternate payment method for the member identifier;
(iv) initiate, in real time, a payment from the alternate payment method for the reimbursement amount minus the payment amount; and
(v) transmit data regarding the payment request and the payment amount to the third-party server;
initiate, through a user device, a user interface corresponding to at least a portion of the primary data for the user;
receive, originating from the user device, a data request that identifies the live bucket data item; and
in response to the data request, update the user interface to communicate the live available benefit for the live bucket data item, wherein the user interface is updated without communication with the third-party server.
2. The primary server of claim 1 , wherein the shadow data is updated on a periodic basis and the periodic basis is daily and the live bucket data item is updated in real time.
3. The primary server of claim 1 , wherein the data request is a network communication that identifies the service, the provider identifier, or the member identifier that is linked the live bucket data item.
4. A method for facilitating real-time exchanges between a plurality of third-party servers and a point of sale device, the method comprising:
establishing, by one or more processors, communication with the plurality of third-party servers, wherein each of the plurality of third-party servers stores third-party data that has at least a first structure and is associated with a member plan for a user;
generating, by the one or more processors and for the user, primary data having a second structure by duplicating a portion of the third-party data having the first structure into memory that is locally accessible by a primary server without further communication with the plurality of third-party servers, wherein the primary data comprises:
(i) shadow data indicative of a locally duplicated portion of the third-party data stored by the plurality of third-party servers; and
(ii) a plurality of live bucket data items corresponding to the plurality of third-party servers, wherein a live bucket data item of the plurality of live bucket data items:
(1) comprises definition data populated from a particular third-party server of the plurality of third-party servers that manages the live bucket data item, and
(2) defines a particular live available benefit for a service corresponding to the live bucket data item and that is based on a plurality of user-provider interactions associated with (a) one or more provider computing devices and (b) the service for the user;
receiving, by the one or more processors and originating from the point of sale device, a payment request identifying the service, a provider identifier for a particular provider, and a member identifier that is linked to one or more identifiers respectively corresponding to one or more live bucket data items of the plurality of live bucket data items;
determining, by the one or more processors and based at least in part on the shadow data and the live bucket data item, that:
(i) the service is subject to a frequency limit and that the frequency limit is not exceeded,
(ii) a provider corresponding to the provider identifier is not excluded from payment, and
(iii) a live available benefit for the live bucket data item is less than a reimbursement amount for the service; and
in response to the determining:
(i) initiate, in real time, the performance of an ACH payment (1) to a provider account associated with the provider identifier, (2) from a third-party account associated with a third-party server corresponding to the live bucket data item, and (3) in a payment amount of the live available benefit for the live bucket data item;
(ii) reduce the live available benefit for the live bucket data item by the payment amount;
(iii) identify an alternate payment method for the member identifier;
(iv) initiate, in real time, a payment from the alternate payment method for the reimbursement amount minus the payment amount; and
(v) transmit data regarding the payment request and the payment amount to the third-party server;
initiating, through a user device, a user interface corresponding to at least a portion of the primary data for the user;
receiving, originating from the user device, a data request that identifies the live bucket data item; and
in response to the data request, updating the user interface to communicate the live available benefit for the live bucket data item, wherein the user interface is updated without communication with the third-party server.
5. A computing system for facilitating real-time exchanges between a plurality of third-party servers and a point of sale device, the computing system comprising memory and one or more processors communicatively coupled to the memory, the one or more processors configured to:
establish communication with the plurality of third-party servers, wherein each of the plurality of third-party servers stores third-party data that has at least a first structure and is associated with a member plan for a user;
generate, for the user, primary data having a second structure by duplicating a portion of the third-party data having the first structure into the memory that is locally accessible by a primary server without further communication with the plurality of third-party servers, wherein the primary data comprises:
(i) shadow data indicative of a locally duplicated portion of the third-party data stored by the plurality of third-party servers; and
(ii) a plurality of live bucket data items corresponding to the plurality of third-party servers, wherein a live bucket data item of the plurality of live bucket data items:
(1) comprises definition data populated from a particular third-party server of the plurality of third-party servers that manages the live bucket data item, and
(2) defines a particular live available benefit for a service corresponding to the live bucket data item and that is based on a plurality of user-provider interactions associated with (a) one or more provider computing devices and (b) the service for the user;
receive, originating from the point of sale device, a payment request identifying the service, a provider identifier for a particular provider, and a member identifier that is linked to one or more identifiers respectively corresponding to one or more live bucket data items of the plurality of live bucket data items;
determine, based at least in part on the shadow data and the live bucket data item, that:
(i) the service is subject to a frequency limit and that the frequency limit is not exceeded,
(ii) a provider corresponding to the provider identifier is not excluded from payment, and
(iii) a live available benefit for the live bucket data item is less than a reimbursement amount for the service; and
in response to the determining:
(i) initiate, in real time, the performance of an ACH payment (1) to a provider account associated with the provider identifier, (2) from a third-party account associated with a third-party server corresponding to the live bucket data item, and (3) in a payment amount of the live available benefit for the live bucket data item;
(ii) reduce the live available benefit for the live bucket data item by the payment amount;
(iii) identify an alternate payment method for the member identifier;
(iv) initiate, in real time, a payment from the alternate payment method for the reimbursement amount minus the payment amount; and
(v) transmit data regarding the payment request and the payment amount to the third-party server;
initiate, through a user device, a user interface corresponding to at least a portion of the primary data for the user;
receive, originating from the user device, a data request that identifies the live bucket data item; and
in response to the data request, update the user interface to communicate the live available benefit for the live bucket data item, wherein the user interface is updated without communication with the third-party server.